...
This is a collection of the features we'd most like to see, as a community, in the version 1.0 release of Fluid Infusion, including features we already have on deck for Infusion 0.8. Please feel free to add to and expand upon it.
Documentation
- Easily maintainable and releasable
- Comprehensive for the core features, including API documentation and tutorial for components, the framework, and the renderer
- Why Fluid? overview section
- Nicer looking, with better information architecture
- A stable home for the documenation: maybe fluidproject.org/docs?
Fluid Skinning System
- Review current system and tweak based on feedback
- Identify gaps
- Renaming where necessary
- Remove unnecessary features; add missing requirements
- Create a naming convention for structural vs. presentational class names
- Better documentation and tutorials
- Visual debugging theme
- QA test plans and test files for skin
- Explore the creation or use of a theming tool
...
- Reliable A-Grade browser support
- Gears support
- Implementation of new design features, possibly including:
- Improved error handling designs
- User-friendly upload time calculation
- Cancel/done buttons
- Elegant truncation of long file names
- Renewed Springboard example, including a "low-profile" or simple Uploader
- Tweaks to improve DOM agnosticism
Design Priorities
- Design Handbook – refine and rework, packaging for ease-of-use and generalizability
- Design Patterns – ensure that Fluid Infusion component patterns are in the OSDPL and think forward to those patterns that will assist the work of OpenCast, 3akai, CollectionSpace, and uPortal...
- component design iteration – as work on the above components carrys on for 1.0, design will have some tweaking to do to designs.
- a11y testing – Daphne is working with Landmark College to get them up to speed on testing our components.
- design carrots – carrots are those components that we may have some design work completed by 1.0, but are not complete. These are carrots that need to be chewed on a bit. One such component will be the
- Rich text inline edit.
Other possible carrots are: - date picker
- metadata support for Uploader
- list reorderer
- auto-complete
- list builder
- profile specific view
- free-form reorderer – draw-in layout
- Rich text inline edit.