Change to View or Edit

Author: smashedr

.vitepress/config.mts

@@ -45,6 +45,7 @@ export default defineConfig({
   description: settings.description.short,
   head: [
     ['link', { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' }],
+    // ['link', { rel: 'icon', type: 'image/svg', sizes: 'any', href: '/images/logo/logo.svg' }],
     ['link', { rel: 'apple-touch-icon', type: 'image/png', sizes: '180x180', href: '/apple-touch-icon.png' }],
     ['link', { rel: 'icon', type: 'image/png', sizes: '32x32', href: '/images/logo/logo32.png' }],
     ['link', { rel: 'icon', type: 'image/png', sizes: '16x16', href: '/images/logo/logo16.png' }],
@@ -148,7 +149,7 @@ export default defineConfig({
 
     editLink: {
       pattern: `${settings.docs_repo}/blob/master/docs/:path`,
-      text: 'View on GitHub',
+      text: 'View or Edit on GitHub',
     },
 
     lastUpdated: {

docs/guides/features.md

@@ -10,8 +10,7 @@ using a [Remote Context](#remote-context). This deploys the stack from the curre
 - [Job Summary](#job-summary) with deployment output, including errors.
 - Supports multiple compose [files](../docs/inputs.md#file) and stack deployments.
 - Allows setting custom [arguments](../docs/inputs.md#args) for the deployment command.
-
-See the [Inputs Documentation](../docs/inputs.md) for more options.
+- **To view all features see the [Inputs Documentation](../docs/inputs.md).**
 
 You can [get started here](get-started.md) or view [workflow examples](examples.md).
 

docs/guides/get-started.md

@@ -43,22 +43,6 @@ If using the `workflow_dispatch` trigger you can [manually run the job](https://
 
 > See the [Inputs Documentation](../docs/inputs.md) for more options to customize your deployment.
 
-## Secrets
-
-You should store your credentials in [GitHub Actions Secrets](https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets).
-
-The [SSH key](../docs/inputs.md#ssh_key) should be copied and pasted exactly as it appears in the private key file.
-
-You do not need to add all values as a secret. However, be aware that any inputs not added as a secret,
-will be visible in the [GitHub Actions Logs](https://docs.github.com/en/actions/how-tos/monitor-workflows/use-workflow-run-logs).
-
-Likewise, if you add your GitHub username or the port number 22 as a secret,
-these values will be replaced with `***`'s anywhere they appear in the logs, including repository names.
-
-If working within an [GitHub Organization](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations)
-you can create these secrets in the organization and make them available to all your repositories.
-_This is why I use the [cssnr](https://github.com/cssnr) organization._
-
 ## Command
 
 The command used to deploy the stack is generated depending on mode.
@@ -81,6 +65,22 @@ You can view the full deployment script on GitHub: [src/main.sh](https://github.
 
 > See the [Inputs Documentation](../docs/inputs.md) for more options to customize the deployment.
 
+## Secrets
+
+You should store your credentials in [GitHub Actions Secrets](https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets).
+
+The [SSH key](../docs/inputs.md#ssh_key) should be copied and pasted exactly as it appears in the private keyfile.
+
+You do not need to add all values as a secret. However, be aware that any inputs not added as a secret,
+will be visible in the [GitHub Actions Logs](https://docs.github.com/en/actions/how-tos/monitor-workflows/use-workflow-run-logs).
+
+Likewise, if you add your GitHub username or the port number 22 as a secret,
+these values will be replaced with `***`'s anywhere they appear in the logs, including repository names.
+
+If working within an [GitHub Organization](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations)
+you can create these secrets in the organization and make them available to all your repositories.
+_This is why I use the [cssnr](https://github.com/cssnr) organization._
+
 ## Portainer
 
 If you use Portainer, you should deploy directly to [Portainer](https://www.portainer.io/resources/get-started/install) for full control.
@@ -89,8 +89,7 @@ For this you should use: [cssnr/portainer-stack-deploy-action](https://github.co
 
 - https://github.com/marketplace/actions/portainer-stack-deploy-action
 
-For more details see the [README.md](https://github.com/cssnr/portainer-stack-deploy-action?tab=readme-ov-file#readme) on GitHub.
-[Support](https://github.com/cssnr/portainer-stack-deploy-action?tab=readme-ov-file#Support) is also available.
+For more details visit the website: https://portainer-deploy.cssnr.com/
 
  
 

docs/guides/resources.md

@@ -19,8 +19,8 @@ This action was built from the ground up to deploy a Docker swarm stack
 then updated to allow Docker compose deployments.
 
 The goal of this action is to be the ultimate Docker deployment action on GitHub.
-To date every [issue](https://github.com/cssnr/stack-deploy-action/issues) has been fixed
-and all [feature requests](https://github.com/cssnr/stack-deploy-action/discussions/categories/feature-requests) have been added.
+To date all [issue](https://github.com/cssnr/stack-deploy-action/issues) have been fixed
+and all [feature requests](https://github.com/cssnr/stack-deploy-action/discussions/categories/feature-requests) added.
 
 ::: warning
 None of these actions have been tested. This is an exhaustive list of published actions.