Page MenuHomePhabricator

Figure out which parts of OOjs UI documentation should be improved, and where they should live
Open, MediumPublic

Description

Good documentation has several parts. Which parts do we want to focus on? Where should they live? Should we break down this task?


API Documentation

I'd say this is in pretty good state right now. Though the jsduck interface can be a bit hard to use sometimes, it does have a lot of information. Places where this documentation can live


Guides and tutorials

What we have

What we need

  • More gadget specific guides
  • Specific tutorials like
    • How to make a dialog and retrieve information from it
    • How to make your own widgets (Part 1 of 42)

Where this should live

  • jsduck lets you make guides
  • mediawiki
  • links to people's blogs from mediawiki
  • ???

Demos

We currently have a demo page that we use mostly for testing. The page does not do much good to showcase the library or to help learn how to use it. There are also editable live code examples inside the API docs (for example the CheckboxInputWidget, try changing the code and clicking live preview), but they are hard to discover and the UI isn't great either.

@Volker_E recently had an idea of using codepen or something like it exclusively for demos. This is a great idea because it makes helping others easy. Also forking existing codepens is a good starting point when learning.

Where this should live


Questions and answers

A single place where everyone asks their queries, it helps other people find answers without asking.

Where this should live


See also

Event Timeline

I think a tutorial is essential for beginners. The linked tutorial seems nice, however it is CC-BY-NC; I assume we can't use that. A tutorial would greatly combine with Codepen or the like (see above for its use in connection to demos) – embedded in a tutorial it would allow a smooth transition from finding out about OOJS to exploring it.

I think a tutorial is essential for beginners. The linked tutorial seems nice, however it is CC-BY-NC; I assume we can't use that. A tutorial would greatly combine with Codepen or the like (see above for its use in connection to demos) – embedded in a tutorial it would allow a smooth transition from finding out about OOJS to exploring it.

If you mean the tutorial on my website, I wrote it, and will gladly change the license if needed. I usually defer to the current license, but I can definitely change if that's unsuitable for our needs. It is also available on github so feel free to fork or submit pull requests (https://github.com/mooeypoo/todo-app-ooui-tutorial)

Qgil renamed this task from Figure out which parts of documentation should be improved, and where they should live to Figure out which parts of OOjs UI documentation should be improved, and where they should live.Feb 20 2017, 4:58 PM

Bump! Any preferences, anyone? @Volker_E could the decision be taken by the Front-end-Standards-Group?

From today's Front-end-Standards-Group meeting, we agree to

  • having tutorials as part of the documentation
  • possibly changing demo functionality over to being able to directly copy example code out of demo
  • having documentation on usage of OOjs UI in different context, as in how to let it play together with certain frameworks

From today's Front-end-Standards-Group meeting, we agree to

And as mentioned in the meeting, we'll start off with this unless there are any other/better suggestions on this task before the month ends.