* Moved CSS, JS, Images into an assets folder
* Adjusted the file structure a bit for CSS, JS, Images.
* Added a fonts folder
* Cleaned up the config a bit so it's easier to read through
* Added some KSS placeholders to tinker with a bit
* Added zepto.js so we can be a bit more friendly on mobile devices/modern browsers
* Added some basic responsive breakpoints
* Added a scaffold.css and theme.css so we can separate out layout pieces from the theme. This will let us retheme the site easier, or have multiple themes if we're feeling frisky
* Removed some HTML5 boilerplate pieces that we don't need
* Added some basic structural css partials
We're thinking getting up and running should be a two step process. We're presenting people with an option on the homepage to get running using a GUI or the command line. From there each option has a quickstart guide to make things easy.
Prioritized what we think is possible to accomplish the Dec 1 Deadline.
* We removed tutorials, resources, examples. We can offload that information to the community for version 1 until we have enough people to maintain and contribute to those sections consistently.
* We removed items from the documentation area that would be better fitted for the community
* We created the community section that will take over on the tutorials and resources
* Created a slimmed down navigation to meet the overall goals for v1
* Added a footer to hold secondary information
* Moved the extra original sitemap items into another section so we know some of sections of the site we want to achieve at a later release.
FAQ/Help sections aren't a good fit for the main naviation. Moved important links into the footer (ie. IRC, Twitter). Didn't feel FAQ's would be very useful along side having actual examples, tutorials, etc. If feels like the FAQ would just rehash existing information.
