There are a few really big problems with the current jQuery UI site that we need to fix ASAP. Maggie has some time to help out on this effort, so we just need to coordinate with Richard and the rest of the team on how to get this done.

 

Here is the punchlist of triage items, listed in order of priority:

 

1. DONE: Demo page links in the nav and footer should be re-routed to skip the broken looking carousel page and instead navigate directly to the functional demos overview page. Right now, this "under construction" page sets is confusing and makes the site seem broken. Any decent demos from the carousel page can be linked to directly from the relevant plugin page. For example, this slider filter example should be linked to from the slider plugin demo page. We could also consider adding a 4th section in the demo left nav with real-world examples if they are important enough.
2. DONE: The demo section does not have a top navigation bar and an outdated footer and must be fixed.
3. DONE: Update every plugin demo page to the new markup and framework styles. These are all pretty ancient now with Flora themes and outdated options. Can we hook this in so it always shows the latest stable version in SVN or something similiar?
4. DONE: Remove the Download landing page. This seems like a lot of overhead for a few links so instead, we could simply route users directly to the download builder and maybe add a few quick links there for the latest stable and experimental builds and SVN instructions? In the homepage mockup below, these links are seen prominently there too.
5. DONE: Re-vamp UI homepage design to make room for updates to an make calles to action clearer. See mockup below. Coded and in website SVN, ready for launch.
6. IN PROGRESS: New demo landing page layout that looks a bit better than the current version. In the future, this could be snazzed up with icons or thumbnails but this is intented to just re-use current content and make the page look a bit more finished -- see design mockup below. HTML template coming soon from Filament Group.
7. IN PROGRESS:Re-vamp the documentation page so the content appears within the jQuery UI site and has a cleaner navigation and presentation format. Design coming soon for review.
8. DONE: Remove the disabled 'Tutorials" top navigation link until this section is launched. Anyone with access can make this change.
9. IN PROGRESS: Switch ui.jquery.com to jqueryui.com. This will include new subdomains. As much as possible, we want consistency with jquery.com

   - DONE: ui.jquery.com will redirect to jqueryui.com

   - DONE: ui.jquery.com/bugs will redirect to dev.jqueryui.com

   - api.jqueryui.com should be created

   - DONE: blog.jqueryui.com should be created

   - DONE: wiki.jqueryui.com will be the new url for jqueryui.pbwiki.com

10. DONE: Cross-link and persist settings betwen ThemeRoller, Demos and Download builder to allow people to fluidly move between them in a smart way. For example, if you go to the download page, indicate that they will get the default theme (Smoothness) and have a link/button to change the theme which navigates them to the TR page. Introduce checkboxes to hide/show plugins on the TR page that will tie in with the download page so if I unchceck 2 widgets on TR, then press download, I navigate to the Download builder screen with the approriate widgets and dependencies checked. Link to demo pages from TR and Download builder.
11. FUTURE: Re-vamp the plugin demo page to merge in interactive documentation to provide a clear, single view of the plugin. Right now, you need to navigate between multiple sites to see the full picture of a plugin and it's really messy.
    • summarize all the options and methods for a plugin on the demo page and provide links to view detailed info on each from the documentation
    • remove the pre-canned dropdowns and use a Configurator style panel that has every option listed out in an interactive form so people can play with the features and see immediate feedback
    • add theme switcher to each plugin page to allow for exploration of theme presets. Once we're using the updated markup & style, this should be easy to add
    • provide links to relevant real-world examples, planning wiki pages and other relevant tools from each demo page

 

 

 

 

 

 

Download builder page:

 

1. Default configuration:

 

 

2. Choosing a theme: 

 

 

 

3. Custom Theme populated from ThemeRoller Download button:

 

 

4. Download builder with javascript disabled:

 

 

 

 

 

Demo landing page:

 

 

 

 

 

Demo detail page with integrated documentation at bottom:

 

 

 

 

 

Demo detail page with interactive documentation at bottom (future state):

 

 

 

Development center:

 

 

 

Support center: