<!--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
<!--Delete sections as needed -->
## Description
Adds a GitHub Actions workflow that posts a Slack notification when a
pull request is opened that modifies the Desktop release notes page
(content/manuals/desktop/release-notes.md).
The workflow uses slackapi/slack-github-action v3.0.1 and sends a
message with a link to the PR and the author's GitHub profile to the
configured Slack channel.
Will need to add the secrets.
## Related issues or tickets
n/a
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [x] Technical review
- [ ] Editorial review
- [ ] Product review
Signed-off-by: Lorena Rangel <lorena.rangel@docker.com>
<!--Delete sections as needed -->
## Description
GA rewrites URLs for cross domain tracking, which breaks docker.com pdf
links
Workaround to create a redirect that will prevent GA from rewriting.
## 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>
<!--Delete sections as needed -->
## Description
Updated DHI CLI reference and how-to topic.
- dhi cli plugin is now part of Desktop 4.65
- pulled the latest version of CLI docs from upstream and updated
`dhictl` examples to `docker dhi`
- updated how-to based on latest cli ref
## 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
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
<!--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
This PR updates SSO documentation to address inconsistencies, per tech
support's jira ticket. I've made some additional changes as well:
- I've removed 4/5ish call outs throughout the doc. Callouts lose
effectiveness if you use them often.
- I've condensed certain redundant UI steps like "Save", "Finish",
"Select X" and created more compound steps. This shortens the procedures
and simplifies the ~weight of each substep.
- Merged Configure and Connect docs into one. Having 1 doc for two steps
when they're necessary for the overall action risks losing users and
adding confusion.
- I've added Prerequisites from the index page to the actual procedures.
Prereqs should always be associated closely with the action users are
taking after establishing those pre-requisites.
---------
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
https://docker.slack.com/archives/C03SR28ANP4/p1774388364841409?thread_ts=1774375828.284229&cid=C03SR28ANP4
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [x] Technical review
- [x] Editorial review
- [ ] Product review
Removed the "Available controls" bullet list — it was left with a single
item after the usage-limits bullet was dropped, and the framing implied
administrators had multiple controls when only enable/disable exists.
Replaced with direct prose.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Usage limits information is no longer accurate or needed in the Gordon
docs. Deleted usage-and-limits.md, removed the "Usage and availability"
section from the index page, and removed the "Set usage limits by
subscription tier" bullet from the data-privacy page.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
## Description
Migrate 17 Testcontainers guides from testcontainers.com into the Docker
docs site, covering Java (14 guides), .NET (2 guides), and Node.js (1
guide). This follows up on PR #24450 which added the initial Go and
Python guides.
Each guide is converted from AsciiDoc to Hugo Markdown, split into
multi-chapter stepper navigation, updated to the latest Testcontainers
API, and verified with passing tests running in containers.
Java guides use testcontainers-java 2.0.4 with the new 2.x Maven
coordinates and package names (e.g., `testcontainers-postgresql`,
`org.testcontainers.postgresql.PostgreSQLContainer`). The Quarkus guide
uses Quarkus 3.22.3 with TC 1.x managed by the Quarkus BOM, since no
released Quarkus version ships TC 2.x yet.
## How to test
All code snippets have been verified by running each guide's source
repository tests inside Docker containers with the Docker socket
mounted.
To re-run the verification, use the `/testcontainers-guides-migrator`
skill included in this PR
(`.claude/skills/testcontainers-guides-migrator/SKILL.md`). The skill's
Step 6 documents the exact container commands and macOS Docker Desktop
workarounds (host override, docker-java API version, etc.) needed to run
each language's tests:
```
/testcontainers-guides-migrator I want you to verify all the guides in this branch.
Do a full review, verifying that all code snippets compile, the code is executable,
and ALL the tests pass. Run them as docker containers, never locally.
```
## Related issues or tickets
Supersedes #24450 (expanded from 2 guides to all 19)
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
## Description
- Update the Compose features page to use `reuse`/`Reusing` instead of
the hyphenated forms.
## Related issues or tickets
- N/A (trivial docs wording fix)
## Reviews
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
## Guideline alignment
- Reviewed `CONTRIBUTING.md` and the PR template before editing.
- Kept the diff to one documentation file with no behavior changes.
## Validation
- Not run (docs-only wording change).
---------
Co-authored-by: rohan436 <rohan.santhoshkumar@googlemail.com>
