cloud account refinement

[eedugon]

Cloud Account content reviewed and organized.
Overview added.

A few concerns (cc: @shainaraskas ):

• In theory cloud account wasn't going to appear in the navigation menu. Should I update that also now?

• Would it make sense to put all the content of join-and-leave-an-organization.md directly at index.md instead of having it in a separate doc?

• Links: should we use relative paths starting with ../../.. or is it ok to use absolute links starting with /deploy-and-manage for example?

• Important question: I have updated the raw-migrated-files that are being shared with other sections so the owners of the other sections are aware of the information that has been already used in the raw-migrated file. Does that make sense or is it better if we don't touch them? I can discard those changes without issue, please review :)

Closes https://github.com/elastic/docs-projects/issues/291
Closes https://github.com/elastic/docs-projects/issues/304

[shainaraskas]

In theory cloud account wasn't going to appear in the navigation menu. Should I update that also now?

you're right. I'm not sure how the nav will be built, but long term it won't all be appearing in the left hand side like this - instead, I think a custom top nav will be built and things will manually need to be added to it (rather than having it be auto-generated).

@bmorelli25 is there a good way to keep an eye on this as part of applying the designs you got from UX?

[shainaraskas]

probably being too picky because this is the first one. important things to note:

• add applies to all front matter (including for auto-migrated pages)
• be careful with "deployments" language because these pages also possibly apply to serverless customers

[shainaraskas]

Links: should we use relative paths starting with ../../.. or is it ok to use absolute links starting with /deploy-and-manage for example?

you can!

[eedugon]

@shainaraskas : I've done a lot of updates here, I'll wait for your review:

• unneeded raw files have been deleted.
• partially used raw files updated
• join and leave org has been adapted to serverless and cloud hosted
• user settings part of index.md has been converted to a task list
• other minor changes

[shainaraskas]

just a couple more comments for you - very close to ready!!

[shainaraskas]

Consider splitting this into two child procedures with their own headings for scannability. not critical to do so

[shainaraskas]

just a couple more comments for you - very close to ready!!

[shainaraskas]

committed to fix a couple of visual bugs and remove usage of "Elasticsearch Service". Good to go now! WOO FIRST TOP-LEVEL SECTION DONE