Skip to content

Workflows lookup reference: add glossary and expand cheat-sheet gotchas#6826

Draft
benironside wants to merge 1 commit into
mainfrom
1159-workflows-glossary-cheat-sheet
Draft

Workflows lookup reference: add glossary and expand cheat-sheet gotchas#6826
benironside wants to merge 1 commit into
mainfrom
1159-workflows-glossary-cheat-sheet

Conversation

@benironside

Copy link
Copy Markdown
Contributor

Closes elastic/docs-content-internal#1159.

Summary

Two deliverables for the Workflows lookup-reference surface:

  1. New glossary at explore-analyze/workflows/reference/glossary.md — 48 terms adapted from the PM internal docset, with cross-links into the canonical reference pages.
  2. Cheat-sheet expansion — a worked-example YAML snippet under each of the 10 gotchas that support one. Gotcha 1 (alert trigger needs rule Action attachment) is UI-driven and has no YAML form.

Glossary scope

55 terms in the PM source → 48 ship → 7 cut.

Cut (7): CI (devops-generic), EDR (security-category), NL authoring (experimental, not documented in docs-content), SIEM / SLO / SOAR / SOC (security and observability category labels, not Workflows-specific).

PM-source corrections applied during conversion:

  • "Composition" — dropped "Tech Preview in 9.4"; uses applies_to instead.
  • "Event-driven trigger" — dropped "In 9.4, the only one is workflows.failed".
  • "Streams" — dropped "are in Tech Preview"; uses applies_to.
  • "Tech Preview" — rewritten to reference our applies_to system instead of the PM-site badging.
  • "Terminal state" — updated to include timed_out (matches the lifecycle-table fix shipped in PR #6669).
  • "Trigger" — dropped "Four types in 9.4"; lists supported types neutrally.
  • "workflows.failed" — dropped "(Tech Preview)" prose; uses applies_to.

Plus PM-site relative paths rewritten to docs-content paths.

Files changed (5)

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes — Claude Opus 4.7 / Cursor
  • No

Closes docs-content-internal#1159.

Two deliverables in one PR:

1. New explore-analyze/workflows/reference/glossary.md (48 terms).
   Adapted from the PM internal docset (elastic/workflows-internal-
   docs, reference/glossary.md). One H3 per term with per-term
   anchor; alphabetical groups (A-B, C, D-E, F-H, I-K, L, N-O, P-R,
   S, T, V-W, Y) mirror the PM source. Cross-links rewritten from
   PM-site relative paths to docs-content paths.

   Cut 7 terms not Workflows-specific (devops/security/observability
   acronyms): CI, EDR, NL authoring (experimental, not documented),
   SIEM, SLO, SOAR, SOC.

   Fixed version-prose in 5 PM-source entries (Composition, Event-
   driven trigger, Streams, Tech Preview, Trigger, workflows.failed)
   — moved version info to applies_to directives, dropped "in 9.4"
   qualifiers. Updated Terminal state to include timed_out (matches
   the lifecycle-table fix that shipped in PR #6669).

2. Cheat-sheet expansion: added a worked-example YAML snippet under
   each of the 10 gotchas that support one (gotcha 1 is purely UI-
   driven and has no YAML form). Each snippet is 3-12 lines, shows
   either wrong/right comparison or a single correct shape. Patterns
   anchored in existing reference pages, not invented.

TOC: added glossary.md to the Reference sub-parent in explore-
analyze/toc.yml; alphabetized the existing entries (cheat-sheet,
context-variables, glossary, liquid-filters, step-types).

Cross-links: glossary added to cheat-sheet's Related section, a
terminology pointer added near the top of pass-data-handle-errors,
and a Glossary signpost added to the workflows.md landing-page
Learn-more section.

Co-authored-by: Cursor <cursoragent@cursor.com>
@benironside benironside self-assigned this Jun 3, 2026
@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

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.

1 participant