-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Improvements to our developer guide #67764
Improvements to our developer guide #67764
Conversation
Maybe it makes more sense to have a generic "Developing plugins" section that is applicable to both scenarios and a "Developing plugins in the Kibana repo" section that is specific to 1st party plugins. Otherwise I feel like these two sections just overlap a lot. |
49500f9
to
6c30f3a
Compare
cb05e5e
to
be6929a
Compare
ac34d6f
to
28170ab
Compare
28170ab
to
fd52ea7
Compare
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.
Looks great, I like the new top level headings. I spent some time in the rendered docs and it feels pretty intuitive. There were a few minor issues with rendering, links etc. I left some review comments for those.
* To **NOT** include your changes in the Release Notes, use `release_note:skip`. | ||
|
||
.... | ||
# Dev Docs |
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.
Should this be removed? It looks out of place in the rendered doc.
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.
@KOTungseth - what do you think about this section? I think you recently added it to the CONTRIBUTING guide and I moved here. Maybe give a title "For example, include these sections in your git issue:"?
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.
I agree with Peter, we probably don't need it here. I think this is more for breaking changes.
Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com>
Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com>
Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com>
Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com>
… into 2020-05-28-dev-docs
Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com>
I suggested some changes in stacey-gammon#15 as an example. If you like those changes, let me know and I can look at the rest of the sections too. |
repo as a sibling of your {kib} repo. Follow the instructions in that project's | ||
README for getting the docs tooling set up. | ||
|
||
**To build the docs and open them in your browser:** |
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.
Can you specify that node scripts/docs.js --open
builds the Kibana docs? There are other product devs that tried to use this command on their own docs, and it didn't work.
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.
So just leave out the part about this command opening the docs up in the browser?
* To **NOT** include your changes in the Release Notes, use `release_note:skip`. | ||
|
||
.... | ||
# Dev Docs |
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.
I agree with Peter, we probably don't need it here. I think this is more for breaking changes.
23a969e
to
c709e51
Compare
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.
There are so many great improvements in this PR! Thank you for making these changes. LGTM.
* contributing guide -> asciidoc * Update docs/developer/contributing/index.asciidoc Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * Update CONTRIBUTING.md Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * Update docs/developer/best-practices/stability.asciidoc Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * Update docs/developer/contributing/index.asciidoc Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * address code review comments * Update docs/developer/contributing/development-documentation.asciidoc Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * review comment updates * fix bad ref Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> # Conflicts: # CONTRIBUTING.md # docs/developer/contributing/development-functional-tests.asciidoc # docs/developer/contributing/development-unit-tests.asciidoc
* master: (28 commits) skip flaky suite (elastic#71361) [Ingest Manager] Add UI to enroll standalone agent (elastic#71288) Node options from cfg file for production (elastic#62468) [APM] Improvements to the ML Settings page (elastic#71309) add old .chromium to gitignore to prevent it from being accidentally committed [Ingest Manager] Simplify add/edit package config (integration) form (elastic#71187) Ensure Other bucket works on scripted fields. (elastic#71329) [APM] Anomaly detection setup link with alert if job doesn't exist (elastic#71229) [APM] Anomaly detection integration with transaction duration chart (elastic#71230) inclusive language (elastic#71438) [Ingest Manager] During fleet setup create an enrollment for every config (elastic#71308) Improvements to our developer guide (elastic#67764) [SIEM][Detections] Fixes index patterns order (elastic#71270) [Metrics + Logs UI] Add test for logs and metrics telemetry (elastic#70858) [Maps] Inclusive language (elastic#71427) [Logs UI] Unskip log highlight api integration test (elastic#71058) [Security_Solution][Resolver] Style adjustments per UX (elastic#71179) [Functional test] Increase the timeout to click new vis function (elastic#71226) [Discover] Migrate async import of embeddable factory to actual embeddable (elastic#70920) fix overflow (elastic#70723) ...
* contributing guide -> asciidoc * Update docs/developer/contributing/index.asciidoc Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * Update CONTRIBUTING.md Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * Update docs/developer/best-practices/stability.asciidoc Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * Update docs/developer/contributing/index.asciidoc Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * address code review comments * Update docs/developer/contributing/development-documentation.asciidoc Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> * review comment updates * fix bad ref Co-authored-by: Peter Schretlen <peter.schretlen@gmail.com> # Conflicts: # CONTRIBUTING.md # docs/developer/contributing/development-functional-tests.asciidoc # docs/developer/contributing/development-unit-tests.asciidoc
Dev Docs
Updated developer guide
Improves our developer guide:
Sections removed
I removed the following sections as the contents are outdated or specific to legacy plugin development and/or angular:
Communicating with Elasticsearch
Modules and Autoloading
Restructuring the format
Previously separate into two categories:
New outline:
I will quickly follow this up by moving the source of the content outside
kibana/docs/developer
and intokibana/dev_docs