<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Addresses #7462 — the labels page only linked to the Dockerfile LABEL
instruction for adding labels to images. Rewrote the section with
inline examples showing how to add, inspect, and filter labels for
each object type, including the docker build --label flag.
Addresses #22199 — users were confused that the `dockerfile` property
in a Bake target resolves relative to the `context` directory, not the
working directory. Added an explicit note and example to the targets
page.
Context deduplication has been automatic in Bake for a long time.
The section documenting the manual workaround is no longer needed.
Closes#24309
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
## Summary
Fixed broken cross-reference link to company creation documentation in
organization general settings.
## Changes
- Updated link in
`content/manuals/admin/organization/general-settings.md` from broken
relative path `new-company.md` to correct path
`/manuals/admin/company/new-company.md`
Fixes#24299
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
## Summary
Fixed broken anchor link in organization FAQ that pointed to a
non-existent heading in the onboarding documentation.
## Changes
- Updated anchor in `content/manuals/admin/faqs/organization-faqs.md`
from `#step-1-identify-your-docker-users-and-their-docker-accounts` to
`#step-one-identify-your-docker-users` to match the actual heading in
the onboarding guide.
Fixes#24281
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
## Summary
Updated organization FAQ to include complete list of enforce sign-in
benefits.
## Changes
- Added missing benefits to the enforce sign-in FAQ answer: subscription
benefits and activity insights
- Updated security features benefit to include specific examples (IAM
and RAM)
- Aligned FAQ content with the main enforce sign-in documentation
Fixes#24283
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
The "Experimental" status column already indicates these agents are not
production-ready, making the "In development" notes redundant and
time-relative.
Closes#24274
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace "Through this partnership, every E2B sandbox" with direct
statement "E2B sandboxes include"
- Change "which comes pre-installed" to "which is pre-installed"
Closes#24266
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The sidebar badge using time-relative "New" text goes stale silently.
The experimental status is already communicated through the content.
Closes#24265
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add AI overview landing page with decision table and relationship overview.
Reframe Gordon as "AI-powered assistant" instead of "AI agent" to avoid
confusion with Docker Agent. Rename sandbox agent page from cagent.md to
docker-agent.md. Add cross-references where products overlap. Fix doubled
"Docker Docker Agent" in agentic AI guide.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Summary
Added timing expectations for diagnostics gathering to help users
understand the process may take several minutes.
## Changes
- Added NOTE callouts in three diagnostics sections explaining that
gathering diagnostics may take several minutes
- Advised users not to close Docker Desktop or terminal while
diagnostics are being collected
- Consistent messaging across "Diagnose from the app", "Diagnose from an
error message", and "Diagnose from the terminal" sections
Fixes#24270
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
This PR captures work for docs in BRIDGE that have >2 but <5 CTAs per
doc.
* Keep most pertinent/urgent/helpful CTAs with a maximum of ~~2~~ 3.
* Some CTAs include security info that should be privileged / override
style guidance
* I've limited scope for this PR to address docs with 4-5 CTAs per doc.
* Find natural home for other CTAs, careful to ensure that the
information is still prominent as the CTAs were likely added because
users need that information.
Follow-up work:
* Some work was started on SCIM and Configure JSON, but both docs need a
deeper look into about their efficacy.
* For SCIM especially, the doc has a lot of relevant call outs.
* I want to confirm with stakeholders about possibly segmenting this doc
into smaller and more topic-focused docs within the provisioning section
* Need to find point person on legacy notices in docs
* Need to find point person on tax compliance notices, as they're quite
noisy. (Not urgent as this is just a personal preference lol)
<!--Delete sections as needed -->
## Description
Refreshes Desktop settings page as it was getting a bit out of hand. No
new content, just made much more efficient and removed dead content (eg
referring to old versions)
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Summary
Fixed inconsistent terminology by standardizing on "company members"
instead of "company users" throughout company management documentation.
## Changes
- Updated front matter in `content/manuals/admin/company/users.md` to
use "company members" in description and keywords
- Updated link text in `content/manuals/admin/company/new-company.md`
from "Manage company users" to "Manage company members"
Fixes#24249
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
