Restructure manage-products.md to drop tabs and product usage list#25575
Restructure manage-products.md to drop tabs and product usage list#25575akristen wants to merge 4 commits into
Conversation
Replace the per-product tabs widget with flat H3 sections (tabs aren't appropriate when a reader needs all six products, not just one) and convert the "Monitor product usage" bullet list into a table for consistent formatting across products. 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. |
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The restructuring is clean and well-scoped. Dropping the {{< tabs >}} widget in favour of flat H3 headings is the correct pattern here — admins need all six products, not one-of-many. The new "Monitor product usage" table is a clear improvement over the previous bullet list. The "What's next" section at the bottom is a good home for the manual links.
No issues introduced by this PR were found. One pre-existing HTTP URL (http://app.docker.com/build) exists in the file but was carried over unchanged from the old content — it predates this PR and is out of scope.
Rework the usage table wording and access-control intros to reflect navigating through Docker Home, and simplify the Docker Hub access steps. Co-authored-by: Cursor <cursoragent@cursor.com>
Wrap prose to Docker docs line-length conventions, expand keywords with product names, and fix minor grammar issues. 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: 🟡 NEEDS ATTENTION
This PR restructures well — dropping the tabbed widget in favour of flat H3 headings is the right call for a page where admins need all six products, not one-of-many. The prose is clean and the "What's next" section is a nice addition. Three items worth checking before merge (see inline comments).
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟡 NEEDS ATTENTION
This PR cleanly restructures manage-products.md — dropping the tabs widget in favor of flat H3 sections, converting the usage bullet list to a table, and adding a What's next section. Two navigation accuracy questions are worth verifying before merging.
Convert the page's internal links from absolute /manuals/ paths to relative paths per the style guide, and add the 'select your organization' step to the Docker Hub access procedure to match the Registry Access Management and Image Access Management source procedures. Co-authored-by: Cursor <cursoragent@cursor.com>
2 participants
Summary
enterprise/security/,offload/, orscout/docs.{{< tabs >}}widget (wrong pattern since admins need all six products, not one-of-many) in favor of flat H3s per product. Dropped redundant "Manage" from each H3 title. Converted the "Monitor product usage" bullet list into a table. Moved the top-of-page manual links into a new "What's next" section at the bottom. Rewrote the intro to state the page's actual job (access control + usage monitoring) in 2 sentences.docker buildx bake vale). No content/link accuracy check against live product UIs was done — that would need separate manual verification.Notes on editorial changes
product's access-management subsection previously repeated the phrase. It
now appears once in the "Control access for your organization" intro,
since it applies to every procedure that follows. This cuts redundancy
without losing the permission requirement, and the page's placement in
the
admin/organization/IA already implies owner-level context.regression. Most users land on Docker Home first and navigate to these
dashboards from there. The direct links to
app.docker.com/buildandscout.docker.comare preserved, but calling out the Docker Home pathadds discoverability for the common case. It's called out explicitly
here because these two flows leave
app.docker.comentirely, unlike theother products where the context switch is implied.
usability friction. During testing, this menu icon was hard to locate.
Naming it explicitly orients users who'd otherwise miss it.