seo(resources): publish governing-ai-generated-workflows - #5486
Open
vfanucci wants to merge 1 commit into
Open
Conversation
Adds /resources/ai/governing-ai-generated-workflows (1222 words), from vfanucci/kestra-seo#360, generated with gemini-2.5-pro. This page was held back because it looked like it might cannibalise the live /resources/ai/ai-governance-workflows. Measured before publishing: zero identical sentences out of 69 vs 138, and 27% vocabulary overlap — against 40% for the migrate-from-cron duplicate we closed. The two pages address different intents: the live page is about governing AI as a discipline (SDLC integration, policy, best practices), this one is about governing pipelines an AI wrote or an agent decides at runtime. Different question, different answer. Editorial pass: - removed 10 banned stems from guidelines/05-anti-patterns.md, including `delve` and `harness` - rewrote the TL;DR from 32 to 59 words (spec is 40-60) and made it state the distinction from the live page explicitly, so the difference is legible in the first block a reader or an LLM sees Also adds the reciprocal internal link on the live ai-governance-workflows page, which pointed nowhere near this topic. The new page already linked to it; the cluster relationship is now declared in both directions. That link uses an absolute path, per INSTRUCTIONS.md R2 — the 22 other internal links on that page are full https://kestra.io URLs and are left untouched here, as they belong to a site-wide problem (1147 occurrences across 71 of the 291 resource pages) that deserves its own sweep. All 16 internal links verified 200. Front-matter complete, metaDescription 147, faq 7, one runnable flow with FQCNs checked against context/plugin-classes.txt, YAML parses, no duplicate link destinations. Known gap: 1222 words against the outline's 1600 target (-24%). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
🔦 Lighthouse Benchmark
Scores (0–100, higher is better)
Core Web Vitals (lower is better)
Legend🟢 improved · 🔻 regressed · (blank) no significant change View full Lighthouse HTML report for a pageFull per-page Lighthouse Results (LHR) are attached as the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
/resources/ai/governing-ai-generated-workflows— 1222 words, from vfanucci/kestra-seo#360,gemini-2.5-pro.Why it was held back, and why it ships now
This page was parked because it looked like it might cannibalise the live
/resources/ai/ai-governance-workflows. Measured before publishing:For comparison, the
migrate-from-cronduplicate we closed sat at 40% with an identical title. These two do not.More importantly they answer different questions. The live page is about governing AI as a discipline — policy, SDLC integration, operating models. This one is about governing pipelines an AI wrote, or that an agent decides at runtime: the control surface when the workflow itself is not human-authored.
Editorial pass
10 banned stems removed per
guidelines/05-anti-patterns.md, includingdelveandharness.TL;DR rewritten, 32 → 59 words (spec is 40–60). It now states the distinction from the live page in the first block a reader — or an LLM — encounters, rather than leaving the two titles to be told apart by chance.
Reciprocal link on the live page
The new page already linked to
ai-governance-workflows; the live page pointed nowhere near this topic. One sentence added in "Agentic AI workflows for execution", so the cluster relationship is declared in both directions. It uses an absolute path per R2.Not fixed here: that page's 22 other internal links are full
https://kestra.io/...URLs. That is not a one-off — 1147 occurrences across 71 of the 291 resource pages, which is a site-wide R2 violation deserving its own sweep rather than a drive-by fix in a content PR.Verified
metaDescription147 ·faq7 entriescontext/plugin-classes.txt; YAML parsesKnown gap
1222 words against the outline's 1600 target (−24%). Same pattern as the rest of the
conceptbatch.🤖 Generated with Claude Code