mirror of https://github.com/docker/docs.git
Remove unneeded <br> HTML tags
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
This commit is contained in:
parent
d17f279abc
commit
2482f8ce04
|
@ -19,17 +19,14 @@ Use the [Docker Material UI Theme](https://www.npmjs.com/package/@docker/docker-
|
|||
- Ensure the extension has both a light and dark theme. Using the components and styles as per the Docker style guide ensures that your extension meets the [level AA accessibility standard.](https://www.w3.org/WAI/WCAG2AA-Conformance)
|
||||
|
||||

|
||||
<br>
|
||||
|
||||
- Ensure that your extension icon is visible both in light and dark mode.
|
||||
|
||||

|
||||
<br>
|
||||
|
||||
- Ensure that the navigational behavior is consistent with the rest of Docker Desktop. Add a header to set the context for the extension.
|
||||
|
||||

|
||||
<br>
|
||||
|
||||
- Avoid embedding terminal windows. The advantage we have with Docker Desktop over the CLI is that we have the opportunity to provide rich information to users. Make use of this interface as much as possible.
|
||||
|
||||
|
@ -50,7 +47,6 @@ Use the [Docker Material UI Theme](https://www.npmjs.com/package/@docker/docker-
|
|||
- If a flow is too complicated or the concept is abstract, break down the flow into multiple steps with one simple call-to-action in each step. This helps when onboarding novice users to your extension
|
||||
|
||||

|
||||
<br>
|
||||
|
||||
- Where there are multiple call-to-actions, ensure you use the primary (filled button style) and secondary buttons (outline button style) to convey the importance of each action.
|
||||
|
||||
|
|
|
@ -5,24 +5,24 @@ keywords: Docker, extensions, design
|
|||
---
|
||||
|
||||
## Provide actionable guidance
|
||||
|
||||
We anticipate needs and provide simple explanations with clear actions so people are never lost and always know what to do next. Recommendations lead users to functionality that enhances the experience and extends their knowledge.
|
||||
<br>
|
||||
|
||||
## Create value through confidence
|
||||
|
||||
People from all levels of experience should feel they know how to use our product. Experiences are familiar, unified, and easy to use so all users feel like experts.
|
||||
<br>
|
||||
|
||||
## Infuse productivity with delight
|
||||
|
||||
We seek out moments of purposeful delight that elevate rather than distract, making work easier and more gratifying. Simple tasks are automated and users are left with more time for innovation.
|
||||
<br>
|
||||
|
||||
## Build trust through transparency
|
||||
|
||||
We always provide clarity on what is happening and why. No amount of detail is withheld; the right information is shown at the right time and is always accessible.
|
||||
<br>
|
||||
|
||||
## Scale with intention
|
||||
|
||||
Our products focus on inclusive growth and are continuously useful and adapt to match changing individual needs. We support all levels of expertise by meeting users where they are with conscious personalization.
|
||||
<br>
|
||||
|
||||
## What's next?
|
||||
|
||||
|
|
|
@ -35,8 +35,9 @@ To add Docker Extensions:
|
|||
1. Open Docker Desktop.
|
||||
2. From the Dashboard, select **Add Extensions** in the menu bar.
|
||||
The Extensions Marketplace opens.
|
||||
2. Browse the available extensions.
|
||||
3. Click **Install**.<br>
|
||||
3. Browse the available extensions.
|
||||
4. Click **Install**.
|
||||
|
||||
From here, you can click **Open** to access the extension or install additional extensions. The extension also appears in the menu bar.
|
||||
|
||||
## See containers created by extensions
|
||||
|
|
|
@ -18,8 +18,6 @@ Download Docker Desktop for Mac on Apple silicon:
|
|||
>
|
||||
> [Mac with Apple chip](https://desktop.docker.com/mac/main/arm64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-mac-arm64){: .button .primary-btn }
|
||||
|
||||
<br>
|
||||
|
||||
### System requirements
|
||||
|
||||
Beginning with Docker Desktop 4.3.0, we have removed the hard requirement to install **Rosetta 2**. There are a few optional command line tools that still require Rosetta 2 when using Darwin/AMD64. See the Known issues section below. However, to get the best experience, we recommend that you install Rosetta 2. To install Rosetta 2 manually from the command line, run the following command:
|
||||
|
|
|
@ -335,7 +335,7 @@ in the Apple documentation, and Docker Desktop [Mac system requirements](../inst
|
|||
- Magento
|
||||
- Zend Framework
|
||||
- PHP applications that use [Composer](https://getcomposer.org) to install
|
||||
dependencies in a ```vendor``` folder<br><br>
|
||||
dependencies in a `vendor` folder
|
||||
|
||||
As a workaround for this behavior, you can put vendor or third-party library
|
||||
directories in Docker volumes, perform temporary file system operations
|
||||
|
@ -343,4 +343,3 @@ in the Apple documentation, and Docker Desktop [Mac system requirements](../inst
|
|||
synchronize between container directories and bind-mounted directories. We are
|
||||
actively working on performance improvements using a number of different
|
||||
techniques. To learn more, see the [topic on our roadmap](https://github.com/docker/roadmap/issues/7){: target="_blank" rel="noopener" class="_" }.
|
||||
|
||||
|
|
|
@ -39,8 +39,6 @@ The following video walks you through the process of managing access tokens.
|
|||
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/Qs5xGj85Aek" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
|
||||
<br>
|
||||
|
||||
To create your access token:
|
||||
|
||||
1. Log in to [hub.docker.com](https://hub.docker.com){: target="_blank" rel="noopener" class="_"}.
|
||||
|
|
|
@ -35,14 +35,10 @@ By default, all activities that occur at organization and repository levels are
|
|||
|
||||
{:width="600px"}
|
||||
|
||||
<br />
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> Activities created by the Docker Support team as part of resolving customer issues appear in the audit log as **dockersupport**.
|
||||
|
||||
<br />
|
||||
|
||||
Click the **All Activities** drop-down list to view activities that are specific to an organization or a repository. After choosing **Organization** or **Repository**, you can further refine the results using the **All Actions** drop-down list. If you select the **Activities** tab from the **Repository** view, you can only filter repository-level activities.
|
||||
|
||||
{:width="600px"}
|
||||
|
|
|
@ -14,8 +14,6 @@ The following video walks you through the process of configuring Image Access Ma
|
|||
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/phFp0iqzwRQ" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
|
||||
<br>
|
||||
|
||||
### Detailed instructions
|
||||
|
||||
To configure Image Access Management permissions, perform the following steps:
|
||||
|
|
|
@ -504,5 +504,3 @@ Help us improve this topic by providing your feedback. Let us know what you
|
|||
think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"}
|
||||
GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"}
|
||||
to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -347,5 +347,3 @@ In the next module, we’ll look into some options for doing so:
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs ](https://github.com/docker/docker.github.io/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -11,5 +11,3 @@ description: Learn how to deploy your application
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs ](https://github.com/docker/docker.github.io/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -745,5 +745,3 @@ In the next module, we’ll take a look at one possible approach to running func
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -29,5 +29,3 @@ You can containerize your own Go application using the examples and resources pr
|
|||
Let's get started!
|
||||
|
||||
[Build your Go image](build-images.md){: .button .outline-btn}
|
||||
|
||||
<br />
|
||||
|
|
|
@ -203,5 +203,3 @@ In this module, we learned how to run containers and publish ports. We also lear
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs ](https://github.com/docker/docker.github.io/issues/new?title=[Golang %20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -107,5 +107,3 @@ In the next module, we’ll take a look at how to set up a CI/CD pipeline using
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -38,5 +38,3 @@ Learn how to set up your Docker environment and start containerizing your applic
|
|||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<br />
|
||||
|
|
|
@ -248,5 +248,3 @@ In this module, we took a look at setting up our example Java application that w
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -301,5 +301,3 @@ You can also consider deploying your application. For detailed instructions, see
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -11,5 +11,3 @@ description: Learn how to deploy your application
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -21,5 +21,3 @@ After completing the Java getting started modules, you should be able to contain
|
|||
Let’s get started!
|
||||
|
||||
[Build your first Java image](build-images.md){: .button .primary-btn}
|
||||
|
||||
<br />
|
||||
|
|
|
@ -181,5 +181,3 @@ In the next module, we’ll learn how to run a database in a container and conne
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -216,5 +216,3 @@ In the next module, we’ll take a look at how to set up a CI/CD pipeline using
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -276,5 +276,3 @@ In this module, we took a look at setting up our example Node application that w
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -243,5 +243,3 @@ You can also consider deploying your application. For detailed instructions, see
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs ](https://github.com/docker/docker.github.io/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -11,5 +11,3 @@ description: Learn how to deploy your application
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -227,5 +227,3 @@ In the next module, we’ll take a look at how to run unit tests in Docker. See:
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -20,5 +20,3 @@ After completing the Node.js getting started modules, you should be able to cont
|
|||
Let's get started!
|
||||
|
||||
[Build your Node.js image](build-images.md){: .button .primary-btn}
|
||||
|
||||
<br />
|
||||
|
|
|
@ -198,5 +198,3 @@ In this module, we took a look at running containers, publishing ports, and runn
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -292,5 +292,3 @@ In the next module, we’ll take a look at how to set up a CI/CD pipeline using
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -239,5 +239,3 @@ In this module, we took a look at setting up our example Python application that
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Python%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -243,5 +243,3 @@ You can also consider deploying your application. For detailed instructions, see
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Python%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -11,5 +11,3 @@ description: Learn how to deploy your application
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Python%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
|
@ -22,5 +22,3 @@ After completing the Python getting started modules, you should be able to conta
|
|||
Let's get started!
|
||||
|
||||
[Build your first Python image](build-images.md){: .button .primary-btn}
|
||||
|
||||
<br />
|
||||
|
|
|
@ -185,5 +185,3 @@ In this module, we took a look at running containers, publishing ports, and runn
|
|||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Python%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
Loading…
Reference in New Issue