...
- Provide Documentation for Authoring xsd, xsl, css, xhtml files (unless we have builders allowing end-users to create these)
- Identify 3 key types for portfolios and provide documentation on workflows for creating each and sample data structures
- Rethink immutable design of published items such as forms, matrices, wizards etc. When does it make sense to allow changes to published data structures. (ie) Should it be possible to add on to a matrix once it's already in use? (see 4th bullet point above)
- Provide better differentiation between user's portfolio experience kept in My Workspace and user's interaction created in a group space.Site centric vs User centric portfolio experience.
- Add notification for published data structures (ie you have 1 new wizard assignment)
- Add notification for submitted data structures (ie you have 1 new wizard submission)
- Make Wizards, Matrices and Forms goal aware
| Note | ||
|---|---|---|
| ||
Overall, I'd like to see us focus on making the user experience more integrated and cohesive. My biggest issue with using OSP tools now is that the workflow for doing just about anything is too disparate, requiring users to go through a series of seemingly random steps in multiple different tools to accomplish one end. Ideally, a user should be able to choose the type of portfolio they're creating, select some basic styles, fill in information and be shown or told where the information they're being asked to supply will appear, while understanding where they are in the process. This may mean removing some options and tools that we currently surface for end-users, but steamlining the process would, in my view, go a long way towards improving understanding and use of the tools. |