## Description
- Part 1 admin freshness, admin section is huge so I am breaking it up
into several PRs to make review a little easier :)
## Reviews
- [ ] Editorial 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
## Description
- Updated FAQ and callouts to include UK VAT collection date, May 1 2025
## Related issues or tickets
https://docker.atlassian.net/browse/ENGDOCS-2647
## Reviews
- [ ] Editorial review
## Description
Core experiences is planning to deprecate org management in Docker Hub
in a few months (~2ish months). This will remove org management from the
following DH pages:
- Members
- Teams
- Activity Logs
- Settings - General
- Settings - Security
- Settings - Image Access
- Settings Registry Access
- Settings - Deactivate org
This PR:
- Adds an include for the hub management callouts
- Adds the new include to all docs that mention deprecated flows/pages
for hub org management (docs across Admin and Security mostly)
- Restructuring docs w/ Admin Console vs. Docker Hub tabs, leading with
Admin Console
- Some other small nits while I was in this area
_I am still waiting on confirmation about Team repo management. This is
not currently in the Admin Console._
## Related issues or tickets
- [ENGDOCS-2516](https://docker.atlassian.net/browse/ENGDOCS-2516)
## Reviews
- [ ] Editorial review
- [ ] Product review
[ENGDOCS-2516]:
https://docker.atlassian.net/browse/ENGDOCS-2516?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
The down command used with profile will stop the services with a given
profile but also all the services without any profiles
## Description
Correct the section of stopping services with a specific profile in the
how-to profile documentation page
## Related issues or tickets
https://github.com/docker/compose/issues/12648
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
## Description
- There is a bug in Hugo that is not parsing includes that begin with a
shortcode correctly
- The fix here replaces the admin-early-access.md include with our
summary bar solution
- Summary bar shortcode updated to support text in the `availability`
field, this will allow us more flexibility with customizing this field
while still supporting the iconography
- NOTE: We will not be able to add the summary bar inside
{{tab}}/{{tabs}} layouts because it messes up the rendering
## Related issues or tickets
## 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>
With the recent change in moving content to the /manuals section, and
manipulating content permalinks to use `/:sections[1:]/:slugorfilename`,
source filenames with dots in them did not receive a .html extension in
the site output directory. This seems to be a quirk (bug?) with the
`:slugorfilename` permalink token in Hugo.
To work around this, I have removed the dots in markdown filenames and
replaced them with dashes.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
build-push-action uses Git context by default. No need for checkout
action unless you tamper with repo files before build.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
