Skip to content

[WIP, DO NOT MERGE] [IA option 3] DevOps adoption journey + Operations grouping#3482

Closed
SharpRake wants to merge 14 commits into
chainguard-dev:mainfrom
SharpRake:ia-option-3
Closed

[WIP, DO NOT MERGE] [IA option 3] DevOps adoption journey + Operations grouping#3482
SharpRake wants to merge 14 commits into
chainguard-dev:mainfrom
SharpRake:ia-option-3

Conversation

@SharpRake

Copy link
Copy Markdown
Collaborator

What this is

A scaffold for the team to review — IA option 3 (Proposal C, DevOps persona) for the docs restructure. It builds on the information-architecture work in #3407 and frames Get Started as an adoption journey while adding a light Operations grouping to Platform & Tools. Draft, not for merge — the net-new pages hold placeholder text so we can evaluate structure before writing real content.

This option does not add a new top-level section.

The two moves

1. Get Started as the adoption journey

Reorders Get Started around the path a DevOps team actually walks — sign up, decide, migrate, operate:

  • New Why migrate page (placeholder) on the outcomes that justify the move.
  • Landing lead reframed around the journey.
  • Order becomes: Sign up → Why migrate → Migration → chainctl basics, with Containers Examples demoted (it's a developer aid, secondary here).

2. A light Operations grouping in Platform & Tools

A new Operations entry at the end of Platform & Tools gathers day-two tasks where platform teams look for them. It cross-links the existing docs under Containers → Staying Secure — nothing is duplicated or moved:

  • Updating containers
  • EOL grace period
  • Enforcement
  • Working with scanners

How to review

Read it as a structure proposal, not finished copy:

  • Does framing Get Started as an adoption journey fit how teams adopt Chainguard?
  • Is "Why migrate" the right addition, and does leading with it help?
  • Is an Operations grouping useful in Platform & Tools, or should these stay only under Containers?

Notes

  • The Operations grouping is cross-links only (pointers into existing pages). The only net-new page is "Why migrate."
  • This also sets the Integrations and Operations sidebar weights to plain decimals. The zero-padded 080/090 are invalid octal, so Hugo was treating them as unweighted and sorting them last by date rather than by weight — worth noting for the existing nav.
  • Diff scope: this PR targets main, so it includes the full IA restructure from Split Product Docs into Get Started, Chainguard Products, and Platform & Tools #3407 plus a merge of the latest upstream main. The changes unique to this option are under content/get-started/ and content/platform/.

🤖 Generated with Claude Code

SharpRake and others added 14 commits June 9, 2026 23:11
…m & Tools

Rework the docs left-nav IA: the single crowded "Product Docs" section
(14 buckets) becomes three top-level sections.

- content/get-started/ ("Get Started") — self-serve and migration
- content/chainguard/ ("Chainguard Products", URL unchanged) — Containers,
  Libraries, VMs, OS, Repository, Factory
- content/platform/ ("Platform & Tools") — Administration, Integrations,
  FIPS, API Reference, chainctl Usage, chainctl Reference

Also: drop "Chainguard" from each product bucket's sidebar label via
linktitle (full title kept for headings and SEO); tighten sidebar
spacing so leaf and expandable rows share one rhythm; repoint the
AutoDocs integration action and homepage links to the new paths; add
aliases on hand-authored moved pages.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Mark Drake <mark@chainguard.dev>
# Conflicts:
#	content/platform/administration/cloudevents/events-reference.md
Create a new "Console" bucket under Chainguard Products and move the
Console walkthrough and Notifications guides into it:

- content/chainguard/console/images-directory
- content/chainguard/console/use-chainguard-notifications

Both pages keep aliases to their old how-to-use URLs. Reweight
Repository and OS so the section order is Containers, Libraries, VMs,
Repository, Console, OS, Factory. Repoint inbound links across the docs
to the new /chainguard/console/ paths.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Mark Drake <mark@chainguard.dev>
Relocate getting-started-with-chainctl from Platform & Tools to a
top-level item in the Get Started bucket, ordered between Self-serve and
Migration. Keep its published /chainguard/chainctl-usage/ alias and
repoint inbound links to the new /get-started/ path.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Mark Drake <mark@chainguard.dev>
Signed-off-by: Mark Drake <mark@chainguard.dev>
…work

# Conflicts:
#	content/get-started/migration/migration-checklist.md
#	content/get-started/migration/migration-tips.md
#	content/platform/administration/cloudevents/events-reference.md
#	content/platform/chainctl/chainctl-docs/chainctl_iam_external-group-role-mappings.md
#	content/platform/chainctl/chainctl-docs/chainctl_iam_external-group-role-mappings_create.md
#	content/platform/chainctl/chainctl-docs/chainctl_iam_external-group-role-mappings_delete.md
#	content/platform/chainctl/chainctl-docs/chainctl_iam_external-group-role-mappings_list.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_packages.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_packages_blocked.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_binding.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_binding_create.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_binding_delete.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_binding_list.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_binding_update.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_create.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_delete.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_describe.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_disable.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_enable.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_list.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_policy-gate_update.md
…ions

Move the Chainguard Factory bucket from Chainguard Products into
Platform & Tools, adding aliases from the old /chainguard/factory/
URLs and repointing internal and inbound links to /platform/factory/.

Reweight both sections so their buckets render in alphabetical order:
Chainguard Products (Console, Containers, Libraries, OS, Repository,
VMs) and Platform & Tools (Administration, API Reference, chainctl
Reference, chainctl Usage, Chainguard Factory, FIPS, Integrations).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Mark Drake <mark@chainguard.dev>
Brings in Chainguard Agent Skills docs (chainguard-dev#3395), pnpm trustPolicy
limitation (chainguard-dev#3424), cosign fix (chainguard-dev#3423), and AutoDocs/API regen.

Conflict resolution (AutoDocs-generated chainctl reference): upstream
renamed `chainctl libraries policy-gate` to `chainctl libraries policy`
and added `chainctl actions catalog/list`. Accepted upstream's
regenerated, url-pinned files at our moved content/platform/ path and
dropped the superseded policy-gate files. No aliases (url-pinned).

Signed-off-by: Mark Drake <mark@chainguard.dev>
…urce

Move the Console bucket from Chainguard Products to Platform & Tools
(/chainguard/console/ -> /platform/console/), placed alphabetically at
weight 050; shift Factory, FIPS, and Integrations down to make room.
Repoint 13 inbound links across 11 files. Swap the top-level section
weights so Compliance sits above Open Source.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Mark Drake <mark@chainguard.dev>
…ducts

Set weight 010 so the bucket sorts first in the section, and normalize
the camelCase linkTitle key to linktitle to match the sibling buckets.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Mark Drake <mark@chainguard.dev>
# Conflicts:
#	content/platform/administration/custom-idps/idp-providers/okta/okta-1.png
#	content/platform/administration/custom-idps/idp-providers/okta/okta-2.png
#	content/platform/administration/custom-idps/idp-providers/okta/okta-3.png
#	content/platform/administration/custom-idps/idp-providers/okta/okta-4-5.png
#	content/platform/administration/custom-idps/idp-providers/okta/okta-6.png
#	content/platform/chainctl/chainctl-docs/chainctl_images_helm_refs.md
Render a `crosslinks` list of {title, url} pairs from a section or
subsection _index.md as pointer entries in the sidebar, with an
external-link icon and working active-state. Cross-links are pointers,
not copies: one canonical page, one URL.

First use: a new get-started/containers-examples subsection pointing at
the nginx, PostgreSQL, Python, and Go getting-started guides, plus a
cross-link from Compliance to Selecting a Base Image.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Mark Drake <mark@chainguard.dev>
…base

# Conflicts:
#	.github/actions/integrate-platform-docs/action.yaml
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_artifacts.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_artifacts_count.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_artifacts_list.md
#	content/platform/chainctl/chainctl-docs/chainctl_libraries_artifacts_versions.md
#	content/platform/integrations/kiro.md
Implements Proposal C from persona-analysis-condensed.md as a reviewable
scaffold for the DevOps persona. Two signature moves:

Get Started reframed as the adoption journey:
- New "Why migrate" page (placeholder) on the outcomes of migrating
- Landing lead reframed around the journey
- Reordered: Sign up -> Why migrate -> Migration -> chainctl basics,
  with Containers Examples demoted

Light "Operations" grouping in Platform & Tools:
- New Operations subsection (cross-links only) for day-two tasks:
  updating containers, EOL grace period, enforcement, working with
  scanners (pointers into Containers -> Staying Secure)

Also sets Integrations/Operations weights to unambiguous decimals: the
zero-padded 080/090 are invalid octal and Hugo treated them as
unweighted, sorting them last by date instead of by weight.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Mark Drake <mark@chainguard.dev>
@netlify

netlify Bot commented Jun 27, 2026

Copy link
Copy Markdown

Deploy Preview for ornate-narwhal-088216 ready!

Name Link
🔨 Latest commit 550c521
🔍 Latest deploy log https://app.netlify.com/projects/ornate-narwhal-088216/deploys/6a3f20ee096a030008f5d246
😎 Deploy Preview https://deploy-preview-3482--ornate-narwhal-088216.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@SharpRake SharpRake changed the title [IA option 3] DevOps adoption journey + Operations grouping (scaffold for review) [WIP, DO NOT MERGE] [IA option 3] DevOps adoption journey + Operations grouping Jun 27, 2026
@SharpRake

Copy link
Copy Markdown
Collaborator Author

Superseded by #3499

@SharpRake SharpRake closed this Jul 1, 2026
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