Skip to content

docs(devsecops): normalize structure and wording - #587

Open
mattaereal wants to merge 4 commits into
developfrom
docs/normalize-devsecops
Open

docs(devsecops): normalize structure and wording#587
mattaereal wants to merge 4 commits into
developfrom
docs/normalize-devsecops

Conversation

@mattaereal

Copy link
Copy Markdown
Collaborator

Scope

Normalize docs/pages/devsecops/** (16 hand-authored pages under the root and isolation/) to the SEAL content model.

Why

Apply the structural and editorial contract from the content-normalization standard so DevSecOps matches other frameworks.

Content model

  • Framework overview with Key Takeaway, unheaded intro, full sidebar page map, Related frameworks
  • Leaf pages: contributors chrome, fact-checked role, canonical KT where missing, Further reading
  • Editorial only; no new security claims

Changes

  • Overview: contributors, description band, ordered page map matching vocs.config.ts, Related frameworks
  • All hand pages: add fact-checked: [] where missing; rename ## References## Further reading; description length band
  • IDEs + Data Security Checklist: add Key Takeaway (+ short intro on checklist)
  • Developer Machine Confinement: wire ContributeFooter
  • Isolation hub: include Developer Machine Confinement in section map
  • Governance title suffix Swing | SEAL for length; MD022/MD032 cleanups around headings/lists
  • No vocs.config.ts or generated index changes

Substantive security

None — structure, frontmatter, labels, and chrome only. Guidance bodies preserved.

Intentionally unchanged

  • Generated index.mdx files
  • Procedure/checklist substance and isolation technical depth
  • Sidebar YAML (already complete)

Validation

  • npx markdownlint-cli2 "docs/pages/devsecops/**/*.mdx" — 0 issues
  • pnpm exec cspell "docs/pages/devsecops/**/*.mdx" — 0 issues
  • Signed commit

Dependencies

Depends on (by reference, unmerged): #561 — Content normalization standard. Do not merge this PR in place of #561; apply #561’s content-model / style as review criteria.

Reviewer focus

  • Overview map vs sidebar completeness
  • Empty wrote: [] avoided (overview credits mattaereal from history)
  • No accidental guidance changes in isolation/governance

Align DevSecOps pages with the content model: fact-checked role, canonical
Key Takeaways, overview sidebar map, Further reading headings, and chrome
fixes (footer on developer confinement, IDE/data checklist takeaways).
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 27, 2026

Copy link
Copy Markdown

Deploying frameworks with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4845e31
Status: ✅  Deploy successful!
Preview URL: https://19204d2c.frameworks-573.pages.dev
Branch Preview URL: https://docs-normalize-devsecops.frameworks-573.pages.dev

View logs

Match develop authorship exactly. Clear wrote/reviewed/fact-checked
arrays where normalization invented authors on pages that had none.
Do not attribute chrome-only edits as content authorship.
Child pages missing a canonical further/related H2 failed the updated #561 validator. Add a minimal Further Reading block linking the framework overview.
Neutralize fence comments that look like headings, canonicalize overview page-map titles, clamp descriptions, demote excess H2s, and mark template pages with content-model exceptions.
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