-
Notifications
You must be signed in to change notification settings - Fork 184
cloud account refinement #284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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? |
shainaraskas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably being too picky because this is the first one. important things to note:
- add
appliesto all front matter (including for auto-migrated pages) - be careful with "deployments" language because these pages also possibly apply to serverless customers
|
Co-authored-by: shainaraskas <[email protected]>
|
@shainaraskas : I've done a lot of updates here, I'll wait for your review:
|
…cloud_account_refinement
shainaraskas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a couple more comments for you - very close to ready!!
|
|
||
| # Update your email address [ec-update-email-address] | ||
|
|
||
| Each Elasticsearch Service account has a primary email associated with it. By default, the primary email address is used to sign up for Elasticsearch Service and to log in. If needed, you can change this primary email address: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider splitting this into two child procedures with their own headings for scannability. not critical to do so
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shainaraskas , I don't understand what we are talking about here, sorry!
What should be split?
shainaraskas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a couple more comments for you - very close to ready!!
Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: shainaraskas <[email protected]>
shainaraskas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
committed to fix a couple of visual bugs and remove usage of "Elasticsearch Service". Good to go now! WOO FIRST TOP-LEVEL SECTION DONE
kosabogi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few suggestions for typo fixes and wording improvements for clarity
raw-migrated-files/docs-content/serverless/general-manage-organization.md
Outdated
Show resolved
Hide resolved
Co-authored-by: kosabogi <[email protected]>
Co-authored-by: kosabogi <[email protected]>
…nization.md Co-authored-by: kosabogi <[email protected]>
shainaraskas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fifteenth time's the charm
This PR makes the following changes: - adds the AutoOps and Stack Monitoring comparison ([preview](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1711/deploy-manage/monitor/autoops/autoops-stack-monitoring-comparison)) to the AutoOps docs - references the article on the following pages: - Stack Monitoring ([preview](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1711/deploy-manage/monitor/stack-monitoring)) - AutoOps FAQ ([preview](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1711/deploy-manage/monitor/autoops/ec-autoops-faq)) - makes some clarity edits to the AutoOps FAQ page Closes: [#284](elastic/obs-docs-projects#284)
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