-
Notifications
You must be signed in to change notification settings - Fork 195
[Contribution initiative] Add tutorial content type #4462
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
base: main
Are you sure you want to change the base?
Conversation
Vale Linting ResultsSummary: 1 warning, 8 suggestions found
|
| File | Line | Rule | Message |
|---|---|---|---|
| contribute-docs/content-types/tutorials.md | 84 | Elastic.DontUse | Don't use 'just'. |
💡 Suggestions (8)
| File | Line | Rule | Message |
|---|---|---|---|
| contribute-docs/content-types/_snippets/templates/tutorial-template.md | 44 | Elastic.EmDashes | Don't put a space before or after a dash. |
| contribute-docs/content-types/tutorials.md | 34 | Elastic.Wordiness | Consider using 'complete' instead of 'successfully complete'. |
| contribute-docs/content-types/tutorials.md | 34 | Elastic.FutureTense | 'they'll learn' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| contribute-docs/content-types/tutorials.md | 34 | Elastic.FutureTense | 'they'll achieve' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| contribute-docs/content-types/tutorials.md | 45 | Elastic.FutureTense | 'will learn' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| contribute-docs/content-types/tutorials.md | 53 | Elastic.FutureTense | 'will learn' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| contribute-docs/content-types/tutorials.md | 101 | Elastic.FutureTense | 'They'll find' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| contribute-docs/content-types/tutorials.md | 101 | Elastic.Exclamation | Use exclamation points sparingly. Consider removing the exclamation point. |
🔍 Preview links for changed docs |
| - **Include checkpoints:** Add verification steps throughout so users can confirm they're on the right track before continuing. | ||
| - **Test your tutorial:** Authors and reviewers should complete the entire tutorial from scratch to identify gaps, errors, or unclear instructions. | ||
| :::{tip} | ||
| Have someone unfamiliar with the feature try your tutorial. They'll find every gap and unclear step! |
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.
Use exclamation points sparingly.
One exclamation point is as sparing as one can be 😄
|
|
||
| ## Examples | ||
|
|
||
| Here are some examples of well-structured tutorials in the Elastic documentation: |
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.
Zero attachments to these specifically, and we wouldn't want two ESQL examples here, but they illustrate the two different flavors I've tried to tease out here (feature-focused versus scenario-driven tutorials) and they hew pretty close to the best practices.
KOTungseth
left a comment
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.
This is shaping up nicely! Thank you for tackling tutorials. I left a bunch of suggestions and recommendations.
We should also add a link to this page on the Elastic Docs content types page.
|
|
||
| # Tutorials | ||
|
|
||
| This page provides guidelines for writing effective tutorials in the Elastic docs. This page and its associated template can be used by humans and LLMs to draft new tutorials, or to evaluate existing pages. |
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.
| This page provides guidelines for writing effective tutorials in the Elastic docs. This page and its associated template can be used by humans and LLMs to draft new tutorials, or to evaluate existing pages. | |
| To create tutorials or improve existing tutorials, use the standards and best practices in the guidelines and template. The guidelines apply to content authored by human contributors and automated systems. |
|
|
||
| This page provides guidelines for writing effective tutorials in the Elastic docs. This page and its associated template can be used by humans and LLMs to draft new tutorials, or to evaluate existing pages. | ||
|
|
||
| Use this page to: |
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.
| Use this page to: | |
| Use the tutorial guidelines and template to complete the following: |
|
|
||
| Use this page to: | ||
|
|
||
| - Draft a new tutorial by copying and pasting the [template](https://github.com/elastic/docs-content/blob/main/contribute-docs/content-types/_snippets/templates/tutorial-template.md) |
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.
| - Draft a new tutorial by copying and pasting the [template](https://github.com/elastic/docs-content/blob/main/contribute-docs/content-types/_snippets/templates/tutorial-template.md) | |
| - Create a tutorial by copying and pasting the [template](https://github.com/elastic/docs-content/blob/main/contribute-docs/content-types/_snippets/templates/tutorial-template.md) |
| Use this page to: | ||
|
|
||
| - Draft a new tutorial by copying and pasting the [template](https://github.com/elastic/docs-content/blob/main/contribute-docs/content-types/_snippets/templates/tutorial-template.md) | ||
| - Understand the structure and best practices for tutorials before you write one |
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.
| - Understand the structure and best practices for tutorials before you write one | |
| - Understand the required structure, scope, and best practices for tutorials |
|
|
||
| - Draft a new tutorial by copying and pasting the [template](https://github.com/elastic/docs-content/blob/main/contribute-docs/content-types/_snippets/templates/tutorial-template.md) | ||
| - Understand the structure and best practices for tutorials before you write one | ||
| - Evaluate existing tutorials or drafts against the standards outlined here |
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.
| - Evaluate existing tutorials or drafts against the standards outlined here | |
| - Evaluate existing tutorials or drafts against the standards |
|
|
||
| ### Required elements | ||
|
|
||
| Every tutorial must include the following elements: |
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.
| Every tutorial must include the following elements: | |
| Review the required elements that every tutorial must include. |
|
|
||
| Every tutorial must include the following elements: | ||
|
|
||
| 1. A consistent **filename:** Use descriptive patterns like `*-tutorial.md`. |
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.
We should eventually link to the not yet documented file/folder name guidelines.
| - Required prior knowledge or skills | ||
| - Software, hardware, or access requirements | ||
| - Data sets or environments to set up | ||
| - Estimated time to complete (optional but helpful) |
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.
Do we want to make this optional?
|
|
||
| 9. **Next steps:** Suggest follow-up tutorials, related features to explore, or ways to expand on what they built. | ||
|
|
||
| 10. **Related pages:** Links to related documentation such as conceptual topics, reference material, how-to guides, or troubleshooting resources. |
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.
What about non docs resources? Such as education content?
| Have someone unfamiliar with the feature try your tutorial. They'll find every gap and unclear step! | ||
| ::: | ||
|
|
||
| ## Template |
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.
Since this is linked above, do we need it here?
Closes https://github.com/elastic/docs-team/issues/114
Generative AI disclosure
2.Tool(s) and model(s) used:
Claude Code, Opus 4.1 for autocomplete on steroids and grunt work automation