Skip to content

Conversation

@eedugon
Copy link
Contributor

@eedugon eedugon commented Feb 3, 2025

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
Copy link
Collaborator

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?

Copy link
Collaborator

@shainaraskas shainaraskas left a 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 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
Copy link
Collaborator

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 eedugon requested a review from shainaraskas February 4, 2025 09:58
@eedugon
Copy link
Contributor Author

eedugon commented Feb 4, 2025

@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

@eedugon eedugon changed the title cloud account refinement initial draft cloud account refinement Feb 4, 2025
@eedugon eedugon requested a review from shainaraskas February 5, 2025 09:39
Copy link
Collaborator

@shainaraskas shainaraskas left a 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:
Copy link
Collaborator

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

Copy link
Contributor Author

@eedugon eedugon Feb 10, 2025

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?

Copy link
Collaborator

@shainaraskas shainaraskas left a 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!!

eedugon and others added 4 commits February 5, 2025 22:30
@eedugon eedugon requested a review from shainaraskas February 5, 2025 22:12
Copy link
Collaborator

@shainaraskas shainaraskas left a 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

shainaraskas

This comment was marked as duplicate.

shainaraskas

This comment was marked as duplicate.

@eedugon eedugon requested a review from kosabogi February 7, 2025 22:15
Copy link
Contributor

@kosabogi kosabogi left a 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

shainaraskas
shainaraskas previously approved these changes Feb 10, 2025
Copy link
Collaborator

@shainaraskas shainaraskas left a 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

@eedugon eedugon merged commit b18688f into elastic:main Feb 10, 2025
4 checks passed
@eedugon eedugon deleted the cloud_account_refinement branch February 10, 2025 19:56
wajihaparvez added a commit that referenced this pull request Jun 16, 2025
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants