Tasks

• Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Demos

  • Create Showcase Framework Demo (data visualization app? Framework Demo (wireframes))

  • Add relevant demos from build site page to Demos page

  • Create new instructional demos where needed

  • Ensure existing instructional demos up-to-date

  • Make sure there are good links to them from other relevant pages

  • Fix links to FSS demos (all linking to 1.3 only)

  • Make a plan for moving instructional demo code into codebase proper (currently in AC's branches)

• Framework Concepts

  • Update links to reference current site (migrate/update content as necessary)

  • Rename pages to be more meaningful

• Think about how to better structure "concepts" documents, to better identify actual concepts and principles from motivation and background.

• Create different "roadmaps" for different audiences: Pages with suggested links based on what reader is probably looking for.

• Pages in wiki space that should be in docs

  • Move Component Lifecycle pages to 1.3 space

    • Maybe move to 1.4 too?

  • Move Component Model Interactions and API somewhere in docs. (moved to Archive)

  • Move test plans out of docs, into wiki

  • Move Pager Overview (and child page) to docs (1.3? trash?)

  • Move Renderer (and child pages) into docs space(s) where appropriate

  • Move The Geometric Manager somewhere into docs space(s), bring up-to-date.

  • Move Writing JavaScript Unit Tests into docs space(s).

• Links from master docs into 1.3/fluid that should be updated

  • FSS demos

  • Links to component APIs on the API page

  • 'custom build' link on Developer Guide page (create "lastest release" and "nightly" versions), rename given that 'download package' will go away

  • get rid of 'download package'

  • How Infusion Works page

    • links to component landing pages: Create new ones!!

    • several framework concepts & the Framework Concepts page itself

    • some FSS links

  • 'commonly appearing options' on Declarative Configuration page

  • Intro text on Renderer page

  • Links on Renderer Component Trees page

  • Links on Renderer Decorators page

  • Links to component tutorials on How-to Guides page

    • Update content of tutorials as appropriate!

• Pages that need updating in general

  • ChangeApplier

• Check all pages for missing includes, images, etc.

• Find a new way to label "boiling"

• Remove references to "New in vX.X"

• Remove references to component decorators (we use grade accumulation now, instead, e.g. Undo: no longer a decorator, now a grade)

• Page to move out of docs back into wiki

  • Contributing Code To Infusion

• Figure out where Using NPM to install infusion and node-jqUnit belongs (context, links to it, etc)

• Do something with DHTML Developer Checklist: Move out of docs? does the content all exist elsewhere now?

• On the 1.3/1.3.x and 1.4 release pages, add links to their relevant docs spaces

• Create an 'archive' space for really old docs:

  • 1.0 demos such as Sorting Lists Demo

  • Integrating the Reorderer and child pages

  • Past release pages, such as Fluid Infusion 0.8

  • Old "Upgrading to vX.X pages" such as Upgrading to Infusion 1.0

  • How to Define a Unit

• Decide if Fluid Versioning Scheme belongs in docs or wiki

• Move Component Status page to docs space(s)

• Consider the v1.4 page Browser Support and its child pages: decide if it belongs in docs, and if latest docs need a version

• Create an appropriately updated version of the 1.3 Components page for other docs spaces
  
  

  • Ensure that the main wiki nav Components link references the latest version (which doesn't exist yet!)