licenses#25181
Conversation
Document organization licenses for Docker Offload and AI Governance, including manual and automatic assignment from the Admin Console Members page. Add subscription/licenses overview, admin manage-licenses guide, and update subscription navigation weights.
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
area/subscription
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Relocate subscription seat management under admin/organization/manage so it sits with other org admin tasks. Add a redirect alias for /subscription/manage-seats/ and update cross-references across admin, enterprise, billing, and subscription docs.
Move AI Governance and Docker Offload license overview into Scale your subscription and remove the standalone Licenses hub page. Drop the Licenses card from the subscription index and tweak admin org nav weights.
Simplify license assignment and automated assignment on the Members page doc, link prerequisites to the scale page, and note that AI Governance applies to Docker Sandbox usage.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🔴 CRITICAL
4 findings: 1 high (broken anchor links), 3 medium (style, placeholder content, grammar).
| For example, with an annual Docker Team subscription (500 included minutes), if you purchase 500 additional minutes, only the additional 500 minutes roll over until your annual renewal. | ||
|
|
||
| ## Add Docker Build Cloud build minutes | ||
| ### Docker Build Cloud build minutes |
There was a problem hiding this comment.
[HIGH] Heading demotion breaks existing anchor links
The PR changes ## Add Docker Build Cloud build minutes (H2) to ### Docker Build Cloud build minutes (H3), and similarly for ## Add Docker Testcontainers Cloud runtime minutes. Hugo generates anchor IDs from heading text, so the old anchors #add-docker-build-cloud-build-minutes and #add-docker-testcontainers-cloud-runtime-minutes no longer exist — they become #docker-build-cloud-build-minutes and #docker-testcontainers-cloud-runtime-minutes (the add- prefix is dropped). Any internal or external pages that link to the old anchors will silently land at the top of the page instead of the intended section.
Consider adding aliases entries or updating all links that reference the old anchor IDs.
There was a problem hiding this comment.
@aevesdocker How would I handle redirects for this? 🤔
There was a problem hiding this comment.
For anchor redirects in Hugo, you have two options:
Option 1: Add custom anchor IDs (recommended for this case)
Keep the new H3 structure but preserve the old anchor IDs by explicitly setting them:
### Docker Build Cloud build minutes {#add-docker-build-cloud-build-minutes}
### Docker Testcontainers Cloud runtime minutes {#add-docker-testcontainers-cloud-runtime-minutes}This maintains the old anchors while updating the heading hierarchy.
Option 2: Hugo aliases (for page-level redirects only)
Hugo's aliases field in front matter only works for full page redirects, not anchor redirects within a page, so it won't help here.
I searched the docs repo and found no internal references to the old anchors, but external links (blogs, Stack Overflow, bookmarks) might exist. Option 1 ensures those continue working.
|
|
||
| ## What’s next | ||
|
|
||
| - AI Governance |
There was a problem hiding this comment.
[MEDIUM] "What's next" section contains unlinked placeholder items
Both items in the "What's next" section are bare text with no links:
- AI Governance
- Docker OffloadDocker documentation "What's next" sections are expected to contain hyperlinks to related pages. Unlinked entries provide no navigation value and appear to be placeholders for pages not yet created. Either add the destination links or remove these items until the target pages exist.
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟡 NEEDS ATTENTION
One medium-severity documentation issue found in the new content added by this PR. The remaining findings were low-severity style guide notes.
|
|
||
| ## What’s next | ||
|
|
||
| - AI Governance |
There was a problem hiding this comment.
[MEDIUM] 'What's next' items are plain-text stubs with no links
Lines 43–45 of the new manage-licenses.md file list "AI Governance" and "Docker Offload" as bare bullet points with no hyperlinks:
## What's next
- AI Governance
- Docker OffloadThese look like placeholder stubs that were never turned into actual links. Readers who arrive at the bottom of the page expecting navigation to the next topic will hit a dead end. Each item should link to its corresponding product page (or be removed until those pages exist).
Co-authored-by: Greg Mondello <72952982+gmondello@users.noreply.github.com>
3 participants
Early draft staging for docs that overview licenses and license management for new product + managing Enterprise Offload. Docs are in early draft state and not ready for review.
To Dos: