Skip to content

Conversation

@leemthompo
Copy link
Contributor

@leemthompo leemthompo commented Dec 29, 2025

Closes https://github.com/elastic/docs-team/issues/114

  • Drafted main guide page
  • Disambiguation snippet included in both how-tos.md and tutorials.md
  • Two example tutorials linked (provisionally ES|QL threat hunting and ES|QL search, will hive mind for alternative examples 😀)
  • Template

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

2.Tool(s) and model(s) used:

Claude Code, Opus 4.1 for autocomplete on steroids and grunt work automation

@github-actions
Copy link
Contributor

github-actions bot commented Dec 29, 2025

Vale Linting Results

Summary: 1 warning, 8 suggestions found

⚠️ Warnings (1)
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.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 29, 2025

- **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!
Copy link
Contributor Author

@leemthompo leemthompo Dec 29, 2025

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:
Copy link
Contributor Author

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.

Copy link
Contributor

@KOTungseth KOTungseth left a 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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`.
Copy link
Contributor

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)
Copy link
Contributor

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.
Copy link
Contributor

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
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants