kestra-io / kestra-io/docs

chore(markdown): iframe fallbacks for the quickstart in both Markdown twins

Open
#5,667 0 comments 0 reactions 0 assignees View on GitHub
area/docs kind/website
Dominant language
Astro
Stars
155
Forks
177
Avg merge
1d 20m
Merged PRs (30d)
192

Description

Part of the Markdown for Agents Phase 1 epic (see #5652). kestra.io has Cloudflare Markdown for Agents enabled: `Accept: text/markdown` converts the SSR HTML at the edge, so defects in the HTML end up in what AI agents read. Cloudflare strips `nav`/`header`/`footer`/scripts/styles/inline SVG, ignores `aria-hidden` and empty `alt`, keeps `.visually-hidden` text and `display:none` content, and renders `

` as separate lines (all verified on production).

## Problem
Two documents exist for the quickstart. `/docs/quickstart.md` (served by `src/pages/docs/[...docsPath].md.ts`) returns the raw body with the literal YouTube and Arcade `` HTML. `/docs/quickstart` requested as Markdown is Cloudflare-converted and the iframes vanish entirely. Same shape in the blog, resources and whitepaper `.md.ts` routes.

## Scope
- Small helper shared by the five `.md.ts` routes that rewrites `<iframe src="…" title="…">` to a Markdown link with the title.
- Add a visible fallback link next to the video and Arcade embeds in the docs HTML (for example under the `video-container`), so the converted twin also carries the URLs.

## Done when
- Both `/docs/quickstart.md` and converted `/docs/quickstart` mention the YouTube and Arcade URLs.

Contributor guide

Open the contributing guide

Research direction

Start with src/pages/docs/[...docsPath].md.ts and locate the corresponding five .md.ts routes that serve documentation, blog, resources, and whitepaper content. Trace the quickstart video-container embeds and the shared iframe-rewriting path, then verify both /docs/quickstart.md and converted /docs/quickstart mention the YouTube and Arcade URLs.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, markdown
Domain
documentation
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
75/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.