cloud account refinement initial draft #284
Conversation
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? |
There was a problem hiding this comment.
imo, for the files that you have already used, you should double-check in the IA spreadsheet that they don't need to be used anywhere else, and then if they don't, you can delete them
There was a problem hiding this comment.
perfect! I was going to suggest that path too :)
| @@ -6,13 +6,24 @@ mapped_urls: | |||
|
|
|||
There was a problem hiding this comment.
please add applies to the front matter of these pages and the others in the section
| ## Edit user account settings [ec-account-user-settings] |
There was a problem hiding this comment.
IMO, we should just make this "user icon > settings" instruction the first step in all of the other pages, and reframe this section as a list of tasks
| # Join or leave an organization | ||
|
|
||
| % What needs to be done: Refine | ||
| ## Accept an invitation [ec-accept-invitation] |
There was a problem hiding this comment.
you always need a sentence between headings to introduce the scope of a page
| ## Join an organization from an existing {{ecloud}} account [ec-join-invitation] | ||
|
|
||
| You already belong to an organization. If you want to join a new one and bring your deployments over, follow these steps: |
There was a problem hiding this comment.
I know this copy was from the original, but it's confusing. why does the person already belong to an org?
| You already belong to an organization. If you want to join a new one and bring your deployments over, follow these steps: | ||
|
|
||
| 1. Backup your deployments to any private repository so that you can restore them to your new organization. |
There was a problem hiding this comment.
do we have a topic we can link to to help them with this?
does this apply to serverless? if so, we need to make it more inclusive because they use projects instead of deployments
| 1. Backup your deployments to any private repository so that you can restore them to your new organization. | |
| 1. Back up your deployments to any private repository so that you can restore them to your new organization. |
|
Cloud Account content reviewed and organized.
Overview added.
A few concerns (cc: @shainaraskas ):
In theory
cloud accountwasn'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.mddirectly atindex.mdinstead 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-managefor example?Important question: I have updated the
raw-migrated-filesthat are being shared with other sections so the owners of the other sections are aware of the information that has been already used in theraw-migratedfile. 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