This PR adds minor adjustments to sign up procedures in prerequisite
sections.
* Adding one word `verified` to instances of `Docker account` in
prerequisite sections is a subtle, unobtrusive change that returning,
verified users can gloss over, while still prompting new users to verify
their email if they haven't yet.
* Changes stick to specific instances in `## Prerequisite` sections and
does not add `verified` to every instance (which would be obtrusive).
* Edits to Create Account doc to remove redundant callouts, consolidate
steps for shorter procedures, and add context about verification.
* If an instance of `Docker account` links to /create-account and not
the sign up page, I did not add `verification`.
* **Note**: we may want to consider a direct link to a sign up page
rather than linking them to a create account page. This can be a
separate PR, however.
<!--Delete sections as needed -->
## Description
Kubernetes moving out of settings. Very little new information, just
moves things about for a better layout and adds a bit on the new view.
## 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
---------
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Description
Replace `docker-compose` with `docker compose` CLI in the Java and
Node.js guides to align with the latest Docker standards and ensure
consistency across the docs.
## Related issues or tickets
Closes#22319
<!-- Related issues, pull requests, or Jira tickets -->
## Description
In this PR I added an article that was missing from several similar
pages.
## Reviews
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
## Description
Fix typo when targeting the `test` stage - it was mentioning a
non-exisiting `--target-test` parameter which could confuse new users:
`unknown flag: --target-test`.
It should be `--target test` or `--target=test`. I went with `--target
test` since that's what is used in the rest of the guide.
## Related issues or tickets
Introduced in https://github.com/docker/docs/pull/19390
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Final PR to improve the DD IA.
Validate test failing due to link that needs fixing in an upstream repo
## 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
---------
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
- Rework the filtering system for guides to drop the use of the
"products", "subjects", and "levels" taxonomies in favor of "tags" and
"languages"
- This change means that the existing taxonomy functionality integrates
better with the guides filtering, and there are fewer parameters to
keep in mind when adding metadata to a guide
- Only two taxonomies instead of three
- Only one of those taxonomies are guides-specific (languages)
- The other taxonomy (tags) works for all content
- Updates how tags and tag pages are rendered in general
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
