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.

Sign up for GitHub

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

Jump to bottom

Move Kibana Platform documentation to the Developer Guide #57343

Open
3 of 4 tasks
joshdover opened this issue Feb 11, 2020 · 3 comments
Open
3 of 4 tasks

Move Kibana Platform documentation to the Developer Guide #57343

joshdover opened this issue Feb 11, 2020 · 3 comments
Labels
chore DevDocs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@joshdover
Copy link
Contributor

joshdover commented Feb 11, 2020 •
edited by rudolf

We have a number of documentation files that currently live as markdown inside the repository but are not easily discoverable by external plugin developers.

As part of our effort to start evangilizing the Kibana Platform, we need to be able to have permalinks to documentation that lives on https://docs.elastic.dev/ (aka mdx files inside src/dev_docs).

Docs that should be moved:

We may want to reorganize or consolidate these docs in the future, but we can do that as a separate step.
@joshdover joshdover added chore Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Feb 11, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@stacey-gammon
Copy link
Contributor

Close as dup of #58183 ?

@stacey-gammon stacey-gammon changed the title Move Kibana Platform documentation to asciidoc Move Kibana Platform documentation to the Developer Guide Mar 3, 2022
@stacey-gammon
Copy link
Contributor

Some new teams recently expressed confusion as to all the places there are documents. Can moving this content to the new dev guide be prioritized?

@pgayvallet pgayvallet mentioned this issue Mar 4, 2022
Closed
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore DevDocs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@joshdover @elasticmachine @stacey-gammon