-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sections #2
Comments
I created a wiki page to follow up on the sitemap. I tidied up the sections a little so we can have fewer top-level menus:
|
New sections look good, i want to discuss two issues. 1 Order of sections I propose this: But it's out of my butt, general idea is to order them by usefulness to the newcomer, and blog always last so it stands out. We can sit on this a bit till GA collects some data and we can see which sections are most clicked... 2 Moving lists to JSON |
both sound good to me, I haven't looked that much in to Jekyll much but I On Thu, Apr 4, 2013 at 9:44 AM, Thanasis Polychronakis <
|
Here are my suggestions for sections I'd like to see:
The Tools -> would have a page with a list that gives a one sentence overview of the tools and related download links (so a download link to the latest compiler etc). Then a paragraph that explains how to install/run/test that they are working.
Build Tools -> links and text about the different build tools such as plovr, yeomen generator, grunt & plugins. maven
3rd party -> split in to frameworks, libraries and other tools like leak finder
IDE -> links to different IDEs and their plugins
Blog -> it'd be great if we could get people to write blog posts that are relevant, or even just get them to allow us to cross post from their blog on to here.
Announcements -> things like new releases of the tools, other tools people are releasing, upcoming talks, etc.
Resources -> so links to the library source, tutorials, blogs
Tutorials* -> not sure if this should be it's own section or just put in as blog posts and linked to from the resources page (and links between the relevant blog posts).
The text was updated successfully, but these errors were encountered: