Difference between revisions of "Documentation/Dashboard/Ideastorm"
(→Usability) |
(→MindMap) |
||
| Line 4: | Line 4: | ||
===MindMap=== | ===MindMap=== | ||
During the OOoCon20009 Doc presentation, Sophie requested a MindMap extension for the MediaWiki. | During the OOoCon20009 Doc presentation, Sophie requested a MindMap extension for the MediaWiki. | ||
| + | * Which MindMap is this? Sophie mentioned one that WikiPedia uses, but I've not been able to find out which one it is. --[[User:Ccornell|ccornell]] 12:00, 8 November 2009 (UTC) | ||
===Next/Prev Page at Bottom=== | ===Next/Prev Page at Bottom=== | ||
Revision as of 12:00, 8 November 2009
Contents
Infrastructure
Ideas for improving the documentation infrastructure. This can be new toolset proposals, reusing existing tools that are not being used effectively, wiki extensions and so on.
MindMap
During the OOoCon20009 Doc presentation, Sophie requested a MindMap extension for the MediaWiki.
- Which MindMap is this? Sophie mentioned one that WikiPedia uses, but I've not been able to find out which one it is. --ccornell 12:00, 8 November 2009 (UTC)
Next/Prev Page at Bottom
Pet peeve, here: reaching the bottom of a long page in one of the Guides, and having to navigate back to the top, in order to get to the next page.--TJ 09:38, 5 November 2009 (UTC)
Usability
just a little brain dump:
- wiki documents should be given states (e.g. draft/published, similar to oooauthors, but not identical as in the wiki there is no need to retract a document)
- This can be done with the FlaggedRevs extension. I've installed it, but not enabled it as I have some technical probs to resolve first. --ccornell 11:57, 8 November 2009 (UTC)
- end users should by default only see published material
- See FlaggedRevs extension --ccornell 11:57, 8 November 2009 (UTC)
- the wiki needs clear entry points and from there a clear and consistent navigation and search
- end users should by default only see documents from their desired language(s) (defaulting to english if a document is not translated)
- I'm not sure how this could be done unless we rolled out a new DocWiki with full support for language namespaces. This is something we will need to research a bit. --ccornell 11:57, 8 November 2009 (UTC)
- Searches, indexes, categories and so on (may be called user space) should reflect constraints mentioned above
Process
Ideas for improving the documentation process.
Documentation Ownership on the Wiki
Use Categories to attribute documentation ownership/maintainers. Non-english content should always be attributed to a NLC Project by Categories.
Other
Other ideas?
Review internal documents?
Some OO.o internal documents, especially specifications, are available, and even sent out, to users. Might some of the authors be interested in our help, with reviewing and polishing (I'm thinking of proof-reading and light copy-editing, mostly)? --TJ 12:46, 5 November 2009 (UTC)
Just some additional thoughts
- What do we know about our users (in case of documentation - are they called readers?)? Who does need what kind of documentation? Who is satisfied who is not? How could we monitor this 'customer satisfaction'?
- Would it help to define a (small) set of "top ten" or "most needed documents" on which (updating/translating) efforts should focussed to keep them up to date first (and only later writing all the other stuff) - i.e. the question if priorization would help?
- How could we organize users/customers to cooperate creating good documentation? By expressing their needs?
