Move UI Framework docs to elastic.co

[cjcenizal]

Originally from discussion within #8867 (comment).

As a company, we want all docs to be on elastic.co (both for users and contributors). This would, for example, apply to the UI Framework docs and future documentation for the Kibana Plugin API.

I think we can do this with the following steps:

• Talk with our infra team to make a server available.
• Update Jenkins to deploy to this server when master changes.
• Improve landing page to provide a better introduction to the UI Framework.
• Improve navigation to provide a brief summary of each component.

Per @tbragin:

@cjcenizal @epixa @debadair I think it's worthwhile noting that we don't yet have a natural place to put Kibana developer-facing docs in the current Kibana guide. We have a plugin users section (installing/updating/removing plugins): https://www.elastic.co/guide/en/kibana/current/kibana-plugins.html

So this feels like either a net-new section in existing Kibana docs (the way Logstash docs do it) or a whole new "book" for plugin developers (the way Elasticsearch does it).

[cjcenizal]

Just a note that GitHub has some pretty nice docs for their CSS framework, Primer.

[epixa]

Last week I added a section to the docs called "Contributing to Kibana", so I think that would be the logic place to link these docs.

[uboness]

@cjcenizal can part of this work be to remove all server components we have there? There's no real need for it and it'll make things much simpler for hosting

[cjcenizal]

@uboness Which server components are you referring to?

[uboness]

last time I checked (and it was quite a while ago :)) you had to run a server to access the UI framework docs. If it's no longer there - 👍 and forget about my comments

[cjcenizal]

Ah, I see. Yes, you still run a server to live-update your browser as you're developing, but this is only used during the dev process. For deployment, we'll only need to host some static assets.

[cjcenizal]

Closing this as EUI is published via GitHub pages.