Align docs/ui.md with www/README.md

[jackgr]

This PR contains changes to docs/ui.md and www/README.md to bring docs/ui.md up to date with #9000, and to align the contents of the two files.

cc @bgrant0607, @bcbroussard, @preillyme

[k8s-bot]

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

[bgrant0607]

/ui now should redirect to the ui.

[jackgr]

Indeed, it does. Nice. Updated the docs accordingly.

[jackgr]

@bcbroussard Not sure which sections of which document your comments address. Can you please clarify?

[bcbroussard]

@jackgr I'm not sure why the code snippets went away, but you can see the comments with code here 97b1866

[jackgr]

@bcbroussard Agree with your point that many people will come here first. However, this document is about working with the UI, not about accessing and using it. We have a document about accessing and using it, which is docs/ui.md.

Moving the section about deploying for production to the top of this document as a way to teach readers how to access the UI would move it out of the parent section about building and deploying the UI, and break the symmetry between development and production in that section.

Rather than try to make this document do double duty, I've added two lines at the top, pointing the reader to docs/ui.md for information on accessing and using the UI. This seems a clean solution, since readers who arrive at docs/ui.md looking for information about working with the UI will likewise find a pointer to this document.

In summary, we have two documents about the UI: docs/ui.md explains how to access and use it, while www/README.md explains how to work with it (i.e., how to configure, build, deploy and update it).

[bcbroussard]

Thanks @jackgr, adding those lines at the top works for me.

What about removing the proxy instructions from docs/ui.md?

[jackgr]

Per my previous comment, the proxy is still a valid way to serve the UI, and people familiar with the old UI will be expecting it. Seems reasonable to keep the proxy instructions, showing how to serve the new UI, and giving them insight, via the pointer to www/README.md, into alternate ways to serve the new UI. In other words, I don't see a good motivation to remove the proxy instructions.

[bgrant0607]

Good enough for now. LGTM.