File: content/manuals/docker-hub/repos/manage/trusted-content/dvp-program.md
Issue
The document states that benefits are granted "based on participation tier" but never defines what these tiers are:
The program grants the following perks based on participation tier:
This is followed by a list of benefits (Enterprise-grade infrastructure, Verified publisher badge, Repository logo, etc.) but there's no explanation of:
- What tiers exist (e.g., Basic, Standard, Premium?)
- Which benefits are available at which tier
- How to determine which tier an organization is on
Why this matters
Readers evaluating the DVP program cannot understand what they would actually receive. A potential publisher reading this documentation cannot determine:
- Whether all benefits are available to all participants
- If they need to upgrade to access certain features
- What differentiates one tier from another
This makes the documentation incomplete for its primary purpose: helping publishers understand the program.
Suggested fix
Either:
- Define the tiers and map benefits to each tier in a table, or
- Remove the phrase "based on participation tier" if all benefits are available to all DVP participants
If tiers do exist, add a section like:
## Program tiers
The DVP program offers the following tiers:
| Tier | Benefits | Requirements |
|------|----------|--------------|
| Core | [list] | [requirements] |
| Premium | [list] | [requirements] |
Found by nightly documentation quality scanner
File:
content/manuals/docker-hub/repos/manage/trusted-content/dvp-program.mdIssue
The document states that benefits are granted "based on participation tier" but never defines what these tiers are:
This is followed by a list of benefits (Enterprise-grade infrastructure, Verified publisher badge, Repository logo, etc.) but there's no explanation of:
Why this matters
Readers evaluating the DVP program cannot understand what they would actually receive. A potential publisher reading this documentation cannot determine:
This makes the documentation incomplete for its primary purpose: helping publishers understand the program.
Suggested fix
Either:
If tiers do exist, add a section like:
Found by nightly documentation quality scanner