Last modified: 2014-08-19 14:35:04 UTC
The OOjs UI library has a useful demos directory, which shows off each of the widgets available. Similarly, VisualEditor also has a demos directory, and I imagine other projects do (or would if it became an established pattern. It would be really great if we could somehow expose these alongside their projects' documentation, so we can point people to a living thing rather than telling them to checkout the repo and play. Something like… https://doc.wikimedia.org/VisualEditor/master/ https://doc.wikimedia.org/VisualEditor/master/demos/ https://doc.wikimedia.org/VisualEditor/0.1.0/ https://doc.wikimedia.org/VisualEditor/0.1.0/demos/ https://doc.wikimedia.org/OOjs-UI/master/ https://doc.wikimedia.org/OOjs-UI/master/demos/ https://doc.wikimedia.org/OOjs-UI/1.0.6/ https://doc.wikimedia.org/OOjs-UI/1.0.6/demos/
Do the demo require a server side backend or are they 100% executing in the browser? If we need to serve content, that would need to be done on another server. Else, it is "just" about enhancing the doc jobs to publish the demo to the document root.
(In reply to comment #1) > Do the demo require a server side backend or are they 100% executing in the > browser? If we need to serve content, that would need to be done on another > server. Else, it is "just" about enhancing the doc jobs to publish the demo > to > the document root. Fully stand-alone client-side JS only, providing static files. Theoretically they could just be linked off beta's bits – e.g. http://bits.beta.wmflabs.org/static-master/extensions/VisualEditor/lib/ve/demos/ve/eventLogger.html – but this is ugly (and doesn't work for OOjs UI because it's only deployed in compiled form without demos).
This is similar to bug 58620. Since the OOjs UI demos require nodejs/npm setup similar to building the KSS documentation, fixing this will require similar steps as hashar outlined in comment 1 there.
