maturity signals

deploy/webhook/Dockerfile

@@ -25,7 +25,7 @@ RUN git clone "${DOCSY_URL}" . && \
 
 # Download Hugo
 FROM alpine:3.10 as download-hugo
-ENV HUGO_VERSION 0.58.3
+ENV HUGO_VERSION 0.59.1
 ENV HUGO_URL https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_Linux-64bit.tar.gz
 RUN wget -O- "${HUGO_URL}" | tar xz
 

docs/content/en/docs/design/api.md

@@ -2,6 +2,13 @@
 title: "Skaffold API"
 linkTitle: "Skaffold API"
 weight: 60
+
+maturity: alpha
+
+infopanel: true
+applicability: true
+dev: true
+debug: true
 ---
 When running [`skaffold dev`]({{< relref "/docs/workflows/dev" >}}) or [`skaffold debug`]({{< relref "/docs/workflows/debug" >}}), 
 Skaffold starts a server that exposes an API over the lifetime of the Skaffold process.
@@ -81,6 +88,7 @@ Skaffold's API exposes the three main endpoints:
 * Control API - control build/deploy/sync
 
 ### Events API
+{{< alpha >}}
 
 Skaffold provides a continuous development mode [`skaffold dev`]({{< relref "/docs/workflows/dev" >}}) which rebuilds and redeploys
 your application on changes. In a single development loop, one or more container images
@@ -151,6 +159,7 @@ a string description of the event in `LogEntry.entry` field.
 
 
 ### State API
+{{< beta >}}
 
 The State API provides a snapshot of the current state of the following components:
 
@@ -224,6 +233,7 @@ func main() {
 {{% /tab %}}
 {{% /tabs %}}
 
-### Controlling Build/Sync/Deploy
+### Control API
+{{< alpha >}}
 
 TODO: https://github.com/GoogleContainerTools/skaffold/issues/3143

docs/content/en/docs/design/global-config.md

@@ -2,6 +2,12 @@
 title: "Global configuration"
 linkTitle: "Global configuration"
 weight: 50
+
+maturity: beta
+
+infopanel: true
+applicability: true
+all: true
 ---
 
 Some context specific settings can be configured in a global configuration file, which defaults to `~/.skaffold/config`. Options can be configured globally or for specific Kubernetes contexts.

docs/content/en/docs/pipeline-stages/builders.md

@@ -3,9 +3,10 @@ title: "Build"
 linkTitle: "Build"
 weight: 10
 
+maturity: GA
+
 infoPanel: true
 applicability: true
-maturity: GA
 dev: true
 debug: true
 build: true

docs/content/en/docs/pipeline-stages/deployers.md

@@ -2,8 +2,10 @@
 title: "Deploy"
 linkTitle: "Deploy"
 weight: 30
+
+maturity: GA
+
 infoPanel: true
-maturity: GA 
 applicability: true
 dev: true
 deploy: true

docs/content/en/docs/pipeline-stages/filesync.md

@@ -3,8 +3,9 @@ title: "File sync"
 linkTitle: "File sync"
 weight: 40
 
-infoPanel: true
 maturity: alpha 
+
+infoPanel: true
 applicability: true
 dev: true
 ---

docs/content/en/docs/pipeline-stages/logging.md

@@ -2,9 +2,11 @@
 title: "Logging"
 linkTitle: "Logging"
 weight: 40
+
+maturity: GA
+
 infoPanel: true
 applicability: true
-maturity: GA
 dev: true
 debug: true
 run: true

docs/content/en/docs/pipeline-stages/port-forwarding.md

@@ -2,9 +2,11 @@
 title: "Port forwarding"
 linkTitle: "Port forwarding"
 weight: 50
+
+maturity: beta
+
 infoPanel: true
 applicability: true
-maturity: beta
 dev: true
 debug: true
 ---

docs/content/en/docs/pipeline-stages/taggers.md

@@ -2,9 +2,11 @@
 title: "Tag"
 linkTitle: "Tag"
 weight: 15
+
+maturity: GA
+
 infoPanel: true
 applicability: true
-maturity: GA
 dev: true
 debug: true
 build: true

docs/content/en/docs/pipeline-stages/testers.md

@@ -2,8 +2,11 @@
 title: "Test"
 linkTitle: "Test"
 weight: 20
+
+maturity: beta
+
+infoPanel: true
 applicability: true
-maturity: GA
 dev: true
 build: true
 run: true

docs/content/en/docs/workflows/ci-cd.md

@@ -2,6 +2,16 @@
 title: "CI/CD with Skaffold"
 linkTitle: "CI/CD with Skaffold"
 weight: 30
+
+maturity: beta
+
+infoPanel: true
+applicability: true
+
+build: true
+deploy: true
+render: true
+run: true
 ---
 
 Skaffold offers several sub-commands for its workflows that make it quite flexible when integrating with CI/CD pipelines.
@@ -46,7 +56,8 @@ Starting deploy...
  - pod/getting-started configured
 ```
 
-## `skaffold render`
+## `skaffold render` 
+{{< alpha >}}
 
 Skaffold also has another built-in command, `skaffold render`, that will perform builds on all artifacts in your project, template the newly built image tags into your Kubernetes deployment configuration files (based on your configured deployer), and instead of sending these through the deployment process, print out the final deployment artifacts. This allows your to snapshot your project's builds, but also integrate those builds into your deployment configs to snapshot your deployment as well. This can be very useful when integrating with GitOps based workflows: these templated deployment configurations can be committed to a Git repository as a way to deploy using GitOps.
 
@@ -86,3 +97,4 @@ pod/getting-started configured
 ```
 
 ## Waiting for Skaffold deployments using `healthcheck`
+{{< beta >}}

docs/content/en/docs/workflows/debug.md

@@ -2,15 +2,14 @@
 title: "Debugging with Skaffold"
 linkTitle: "Debugging"
 weight: 20
-infoPanel: true
+
 maturity: alpha 
+
+infoPanel: true
 debug: true
 applicability: true 
 ---
 
-
-## Debugging with Skaffold
-
 `skaffold debug` acts like `skaffold dev`, but it configures containers in pods
 for debugging as required for each container's runtime technology.
 The associated debugging ports are exposed and labelled so that they can be port-forwarded to the

docs/content/en/docs/workflows/dev.md

@@ -2,6 +2,12 @@
 title: "skaffold dev"
 linkTitle: "Continuous development"
 weight: 10
+
+maturity: GA
+
+infoPanel: true
+applicability: true
+dev: true
 ---
 
 `skaffold dev` enables continuous local development on an application.

docs/layouts/shortcodes/alpha.html

@@ -0,0 +1 @@
+{{  $maturity := "alpha"}}<sup style="background: var(--maturity-{{$maturity}})">&nbsp;{{ $maturity}}&nbsp;</sup>

docs/layouts/shortcodes/beta.html

@@ -0,0 +1 @@
+{{  $maturity := "beta"}}<sup style="background: var(--maturity-{{$maturity}})">&nbsp;{{ $maturity}}&nbsp;</sup>