Add overview pages for org setup and manage sections#25580
Conversation
The admin > organization > setup and manage _index pages were hidden stubs (build: render: never), so the sidebar rendered them as non-clickable expand-only entries. Turn them into landing pages that follow the pattern used by sibling section overviews. - Add title, linkTitle, description, keywords, and a grid of child-page cards to both pages so they render and become clickable in the sidebar - Add a short overview of the setup phases (create/convert, onboard, maintain), noting which tasks are sequential and which are not - Add a seats-vs-licenses comparison table to the manage overview to clarify the distinction between the two entitlements Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Wrap prose to 80 characters and tighten wording across the org setup and manage overview pages. Replace a semicolon with two sentences, remove parentheses and redundant phrasing, and fix awkward wording for clarity and style-guide compliance. Co-authored-by: Cursor <cursoragent@cursor.com>
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
All findings are low-severity style suggestions. No breaking issues were found. The front matter, grid shortcode usage, and page structure correctly follow the established pattern used by sibling section overview pages.
| 1. You can create a new organization, or convert an existing user account | ||
| into one. Choose the option that fits how you already use Docker. You | ||
| don't need both. | ||
| 1. After creating your organization, you must onboard it by inviting members, |
There was a problem hiding this comment.
[LOW] Redundant phrase: "whenever it changes at any time"
"At any time" is redundant with "whenever it changes" — both convey the same idea. Consider:
You can update your organization's general information whenever it changes.
| ## Setting up your organization | ||
|
|
||
| You set up your organization from [Docker Home](https://app.docker.com) and | ||
| must be assigned the |
There was a problem hiding this comment.
[LOW] Vague transitional phrase "in broad phases"
"In broad phases" is vague. Per Docker style, prefer direct, specific language. Consider:
Setting up an organization involves these steps:
| and product usage. You can invite members, group them into teams, assign or | ||
| revoke licenses and seats, and change access to Docker products. | ||
|
|
||
| ## Managing your organization |
There was a problem hiding this comment.
[LOW] Heading "Managing your organization" restates the page title
The heading ## Managing your organization closely mirrors the page title "Manage your organization" and contains only a single sentence. Per Docker style guidelines, headings should add value beyond restating the title. Consider removing this heading and folding the sentence into the opening paragraph, or replacing it with a more specific heading (e.g., "Prerequisites").
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
Both new overview pages are well-structured and follow the established sibling section pattern. Required front matter (title, description, keywords) is present in both files, build: render: never is correctly removed, no redirects are needed (the old stubs were never published), and there are no AI-isms, no bold misuse, and no markdown errors.
Minor style observations (no action required):
## Setting up your organization(setup/_index.md:38) and## Managing your organization(manage/_index.md:30) use a gerund form and mirror the page title — a more descriptive heading like## Setup phases/## Management taskswould add more navigational value, but this is a minor point."Explore the following sections to set up/manage your organization."(setup/_index.md:55, manage/_index.md:51) is light meta-commentary that STYLE.md suggests dropping — the grid shortcode stands on its own without a lead-in sentence.
These are low-priority observations; the pages are ready to publish as-is.
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The PR promotes two previously hidden (build: render: never) organization landing pages into fully published overview pages. The changes follow established patterns in the codebase:
- Front matter is complete (
title,linkTitle,description,keywords,grid) - Grid tile links use the correct short URL convention (no
/manuals/prefix) - Body-text internal links use the established
/manuals/prefix convention, consistent with 100+ sibling files - No aliases/redirects needed — the pages were never previously published
- No AI-isms, marketing language, or style guide violations detected
- Hugo shortcode usage (
{{< grid >}}) is correct - Scope is well-matched to the document type (section overview/landing page)
2 participants
Summary
The admin > organization Setup and Manage section landing pages
(
_index.md) were hidden stubs (build: render: never). Because Hugo doesn'tpublish those pages, the sidebar rendered both sections as non-clickable,
expand-only entries. This PR turns them into proper overview pages that follow
the pattern used by sibling section overviews (Organization, Company, etc.).
title,linkTitle,description,keywords) and a gridof child-page cards to both pages, so they render and become clickable in the
sidebar.
that clarifies which tasks are sequential and which aren't.
the two entitlements.