Skip to content
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

[meta] Improve Fleet Server doc experience #1060

Closed
4 of 7 tasks
dedemorton opened this issue Sep 13, 2021 · 1 comment
Closed
4 of 7 tasks

[meta] Improve Fleet Server doc experience #1060

dedemorton opened this issue Sep 13, 2021 · 1 comment
Labels
meta Team:Docs Label for the Observability docs team Team:Elastic-Agent Label for the Agent team

Comments

@dedemorton
Copy link
Contributor

dedemorton commented Sep 13, 2021

Description

We've documented the basic steps for users who need to deploy Fleet Server, but users need more guidance.

Related issues and PRs:

Collaboration

TBD

  • The docs team will lead producing the content
  • The product team will provide the initial content and the docs team will edit / review
  • The docs team will define with product team the structure and location, and the product team will provide the initial content
  • Other (please describe)

Contact Person:

TBD

Suggested Target Release

TBD

Stakeholders

@elastic/obs-docs
@mostlyjason
@nimarezainia

@dedemorton dedemorton added Team:Docs Label for the Observability docs team meta labels Sep 13, 2021
@mostlyjason mostlyjason added the Team:Elastic-Agent Label for the Agent team label Sep 20, 2021
@dedemorton
Copy link
Contributor Author

Closing because we've done all the tasks in the list. I'm not saying we shouldn't do more work, but let's come up with a new meta issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Team:Docs Label for the Observability docs team Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

No branches or pull requests

2 participants