> 🤖 Generated with [Claude Code](https://claude.com/claude-code)
## Summary
`theme.js` unconditionally wrote the resolved preference to
`localStorage` on every page load, permanently locking in a concrete
`"light"` or `"dark"` value even for first-time visitors — making it
impossible to track OS preference changes after any site visit. Removed
the unconditional `localStorage.setItem` from `theme.js` so the early
script only reads (never writes); the Alpine.js toggle in `header.html`
now cycles through three states (light → dark → auto), with "auto"
removing the `theme-preference` key and resolving from
`prefers-color-scheme` with a live `matchMedia` change listener so the
theme updates immediately when the OS preference changes. A contrast
icon indicates auto mode; all three icon spans are driven by Alpine
`x-show` directives rather than pure CSS dark-mode classes.
**Verified:** logic matches the standard three-state pattern;
`prefers-color-scheme` media query and `matchMedia` change listener are
the canonical browser APIs for system-preference tracking.
**Checked:** no other files reference `theme-preference` or the theme
toggle; no CSS changes required.
Closes#23177
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
## Description
The prerequisites section states "Docker Desktop 4.26.0 or later" as a
download requirement, which becomes stale as new versions are released.
This rephrases the version reference as a historical fact ("Private
marketplace support was introduced in Docker Desktop 4.26.0") rather
than a prerequisite, making it resistant to staleness.
Fixes#24547
---------
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Description
The documentation uses time-relative language ("for Docker Desktop
versions 4.34 and earlier") when mentioning the old `settings.json` file
name, which becomes increasingly stale over time.
This rephrases it as a historical fact: the file was renamed from
`settings.json` to `settings-store.json` in Docker Desktop 4.35.
Fixes#24546
---------
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Description
Update with more information about the MSI bug for versions between 4.59
and 4.65.
## Related issues or tickets
https://docker.atlassian.net/browse/DKP-2697
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
Clarified the prerequisites structure in the DHI Enterprise guide. The
previous wording incorrectly listed Docker Desktop 4.65+ as part of "one
of the following" options, making it appear optional or mutually
exclusive with the subscription/trial requirement.
Changed:
- Restructured prerequisites to show Docker Desktop 4.65+ is always
required (not optional) for CLI
Clarified that "one of the following" applies only to the
subscription/trial choice
- Made it clear there are 3 distinct prerequisites:
- Organization owner access (required)
- DHI Select/Enterprise subscription OR trial (required - pick one)
- Docker Desktop 4.65+ (required for cli)
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
Adds core skills for working with docker/docs - catches common issues
and improves agent task execution. These tasks were derived from a
self-learning harness setup I've used separately; but a separate harness
doesn't exactly work well as a collaboration platform. So this PR merges
the main features of the harness into the canonical repo.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Remove individual subpages (agents, architecture, get-started,
network-policies, workflows, templates, migration, troubleshooting)
and replace with a single docker-desktop.md page. Update _index.md
as a minimal landing page for the section.
## Description
The note about Windows container builds uses passive voice ("the legacy
builder is used") which makes the behavior unclear. Readers can't tell
if this is expected behavior or a temporary limitation.
Rewritten in active voice to make the cause and workaround clear: the
`docker build` command uses a legacy builder, and here is how to switch
to BuildKit to see builds in the Builds view.
Fixes#24453
Replace "currently experimental and needs further work" with
"experimental" and "not yet integrated" with "not integrated"
per STYLE.md conventions.
Fixes#24568
Add a "Best for..." statement to the semantic-embeddings description,
matching the pattern used by chunked-embeddings and BM25, so readers
can compare strategies at a glance.
Fixes#24571
Remove "on the roadmap" and "currently" from the extension security
vetting FAQ entry, keeping a timeless factual statement per STYLE.md
conventions.
Fixes#24490
Rephrase the version-specific workaround to clearly state which
versions require the manual deletion step and that version 4.60+
no longer needs it.
Fixes#24545
Add context that Docker Desktop 4.54 is the minimum version for vLLM
support, making the version reference self-explanatory and resistant
to staleness.
Fixes#24532
<!--Delete sections as needed -->
## Description
Added a get-started with DHI Select & Enterprise topic to show a
complete end-to-end workflow with a real example. Current location is in
how-to in order to keep the primary community get-started upfront for
now.
Updated the community get-started.
## Related issues or tickets
ENGDOCS-3217
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
---------
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
## Description
The Slack notification workflow for Desktop release notes PRs fails when
the PR is opened from a fork because GitHub doesn't expose repository
secrets to `pull_request` events from forks.
This PR splits the workflow into two:
1. **Release Notes PR Trigger** — runs on `pull_request`, saves PR
details (URL, title, author) as an artifact. No secrets needed.
2. **Notify Slack on Desktop Release Notes PR** — runs on `workflow_run`
after the trigger completes, downloads the artifact, and sends the
Slack notification. Has access to secrets since `workflow_run` runs in
the context of the base repository.
## Related issues or tickets
Fixes the `SlackError: Missing input! A token must be provided` error
in the notify-release-notes-pr workflow.
## Reviews
- [x] Technical review
Signed-off-by: Lorena Rangel <lorena.rangel@docker.com>
