Placeholder for new web-component apps

[duncdrum]

Placeholder and master ticket for documentation task related to the new web-component core apps.

What is the problem

see eXist-db/existdb-dashboard#7

[joewiz]

From yesterday on HipChat/Existdb:

We'll also need to prepare a corresponding PR with any changes needed to the documentation. For example, screenshots and mentions of the "plug-in" system in http://exist-db.org/exist/apps/doc/dashboard.xml. A search for "dashboard" should give us all of the mentions: http://exist-db.org/exist/apps/doc/search.html?q=dashboard. For example, I see mentions of the "shutdown button" (http://exist-db.org/exist/apps/doc/basic-installation.xml#shutting-down), the "link to download the Java WebStart file" (http://exist-db.org/exist/apps/doc/java-admin-client.xml#launching), the "Collections pane" (http://exist-db.org/exist/apps/doc/uploading-files.xml#with-dashboard), and the "scheduler plugin" (http://exist-db.org/exist/apps/doc/troubleshooting.xml#emergency).

[duncdrum]

@joewiz want to do us the honors?

[duncdrum]

ping @eXist-db/exist-webcomponents docs are still not showing the current dashboard or apps.

[ebeshero]

Remarks on transitioning from v4 to v5:

• It was super useful and actually comforting to have a Shutdown button in the web app. Please bring that back!

• It is a little difficult as admin to find one’s way to things we used to find easily like the package manager.

• No complaints about removing the collections manager, but putting the admin tools we do use back in the main window instead of on the side would be helpful.

• Managing users and groups and collection permissions on the web interface without the Java admin client available by default is error prone and outright horrible. (I managed to lock my admin user out of dba that way without trying to do so, just by attempting to add admin to another group I created.) The Java admin client needs to be available by default. Don’t make us hunt for how to install it.