-
Notifications
You must be signed in to change notification settings - Fork 25.5k
[DOCS] Collapse some content in local dev setup for readability #112355
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -125,6 +125,10 @@ The service is started with a trial license. The trial license enables all featu | |
|
||
To connect to the {es} cluster from a language client, you can use basic authentication with the `elastic` username and the password you set in the environment variable. | ||
|
||
.*Expand* for examples | ||
[%collapsible] | ||
============== | ||
|
||
You'll use the following connection details: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the collapsible title indicates to me that you're just hiding examples, but it looks like you're also hiding the default endpoint and auth details here There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ah 💯 I'll reword the text because I actually want to clear as much real estate as possible on this page :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @shainaraskas do you think we could get away with pulling out this text from intro too? Feels like excessive text is clogging up reader's working memory. Want this to really be about copying and running the ~5 commands. When would I use this setup? Use this setup if you want to quickly spin up Elasticsearch (and Kibana) for local development or testing.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like it. people don't have to read it if they don't care - we have scannable headings on the page they can use to jump to the part they are interested in. personally, I don't agree with hiding content behind a collapsible element, but since it pops open when we search it's ok |
||
|
||
* **{es} endpoint**: `http://localhost:9200` | ||
|
@@ -160,6 +164,8 @@ curl -u elastic:$ELASTIC_PASSWORD \ | |
---- | ||
// NOTCONSOLE | ||
|
||
============== | ||
|
||
[discrete] | ||
[[local-dev-next-steps]] | ||
=== Next steps | ||
|
Uh oh!
There was an error while loading. Please reload this page.