Initial push for getting knode.io in a happy place.

knode_tasks.md

Listed in order of priority for now, but please take a gander and do what seems fitting. Topics generally reflect an existing repo. Please see these for further information or existing issues for further context.

Please indicate in the comments below what you're working on so we don't stomp on each other's toes. THANKS!

Visit #pdxnode on freenode.irc.net to ask questions or offer help

Possible modules

• json stream to list page
• json stream to detail page

Miscellaneous but important

• create map of locations in json stream
  • this will be used on different pages of the site to pin locations of the listings
• create design/styling for sub-pages
• add sub-page navigation on main page as strip underneath big header
• link sub-pages to main page

Meetups

• create meetups page
  • Use index.js from knode/meetups to render the markdown from each file within a directory as a listing
  • should contain large map that plots listed meetups. When I click on the pin, page should focus on that event.

Speakers

• create speakers list page using listings(.md files) by location in knode/speakers
  • write markdown -> json for speakers(see script instruction above)
  • listings should be in alphabetical order by location, alphabetical order within location by speaker last name.
  • contains large map that plots listed speakers. When I click on the pin, page should focus on that speaker.
  • each speaker has an image as part of the listing. Use knode logo otherwise.

Questions

• Add link to knode/questions repo on main page through a sentence or short callout
• write instructions(as the README.md) for Q&A workflow using Issues. Read this for context

CFP

• create cfp page
  • Move CFP to Google Forms using http://jlord.github.io/sheetsee.js/ to allow for submissions of the Call for Proposals
  • write markdown -> json for cfp(see Script above)
  • contains large map that plots listed Calls. When I click on the pin, page should focus on that Call.

Contribute

• Create contributing doc
• Add package.json with "scripts": {"start": ""}

Analytics

• Google Analytics please and thank you

HOLD OFF ON THIS FOR NOW Node-meatspace

• create node-meatspace page on knode.io(this should be a different site of files than the external page)
• contains large map that plots listed meetups. When I click on the pin, page should focus on that event.

I think these are the things you need.

• write markdown -> json for speakers
• write markdown -> json for cfp
• json stream to list page
• json stream to detail page
• map of locations in json stream
• design
• github issues into list page
• github issues into detail page?

markdown -> json is like https://github.com/knode/meetups/blob/master/index.js and you'd need one of those for each repo.

You need someone who can do the basic design (eg: a non-dynamic listing / detail pages on each speaker, for instance).

Once the markdown -> json piece and the design are done, someone should marry those two so that the result of the json stream outputs into a template. This can then be deployed to the live site.

The Questions thing seems to mean speaking with the github API in some way to update, which will probably have to be dynamic because you won't want to have to recompile your entire website every time someone files an issue.

Currently looking at templating engines to use. Will also start on the templates for sub-pages.

1pm update: we're using Handlebars.

• starting on meetups basic html now
• will do speakers next
• will use knode/style for css
• will integrate handlebars after this

Working on the part that shuffles the json stream into a template

calling dibs on the speaker markdown to json stream.

calling dibs on cfp

http://commitcoffee.com/ awesome example of map on a page we should take a gander at. Also http://8bitcity.com/map?Portland is also badass but would prob be really crazy to implement. PLEASE DO THIS. This idea is courtesy @meandavejustice