diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 2f92c77..b620b25 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -1,6 +1,3 @@
-# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
-# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
-
name: Node.js CI
on:
diff --git a/.linkinator.config.json b/.linkinator.config.json
deleted file mode 100644
index 9e9aa3f..0000000
--- a/.linkinator.config.json
+++ /dev/null
@@ -1,11 +0,0 @@
-{
- "recurse": true,
- "skip": "^(https://.*linkedin.com),^(https://.*youtube.com),^(https://.*twitter.com)",
- "verbosity": "error",
- "timeout": 0,
- "markdown": true,
- "directoryListing": true,
- "retry": true,
- "retryErrors": true,
- "retryErrorsCount": 3
-}
diff --git a/.prettierignore b/.prettierignore
new file mode 100644
index 0000000..2e03d40
--- /dev/null
+++ b/.prettierignore
@@ -0,0 +1,19 @@
+public/
+node_modules/
+.cache
+.history
+dist
+coverage
+docs/app
+__mocks__
+userguide/
+.release-please-manifest.json
+CHANGELOG.md
+.vscode/
+assets/js/drawio.js
+assets/js/markmap.js
+assets/js/mermaid.js
+assets/js/plantuml.js
+assets/js/base.js
+static/js/deflate.js
+static/js/swagger*.js
diff --git a/.prettierrc b/.prettierrc
new file mode 100644
index 0000000..4ec6626
--- /dev/null
+++ b/.prettierrc
@@ -0,0 +1,22 @@
+{
+ "plugins": [
+ "prettier-plugin-go-template"
+ ],
+ "trailingComma": "es5",
+ "tabWidth": 2,
+ "semi": false,
+ "singleQuote": true,
+ "bracketSpacing": true,
+ "editorconfig": true,
+ "htmlWhitespaceSensitivity": "ignore",
+ "overrides": [
+ {
+ "files": [
+ "*.html"
+ ],
+ "options": {
+ "parser": "go-template"
+ }
+ }
+ ]
+}
\ No newline at end of file
diff --git a/.vscode/settings.json b/.vscode/settings.json
new file mode 100644
index 0000000..4dd3d89
--- /dev/null
+++ b/.vscode/settings.json
@@ -0,0 +1,6 @@
+{
+ "cSpell.words": [
+ "isset",
+ "pygments"
+ ]
+}
diff --git a/archetypes/default.md b/archetypes/default.md
index 00e77bd..c6f3fce 100644
--- a/archetypes/default.md
+++ b/archetypes/default.md
@@ -1,6 +1,5 @@
----
-title: "{{ replace .Name "-" " " | title }}"
-date: {{ .Date }}
-draft: true
----
-
++++
+title = '{{ replace .File.ContentBaseName "-" " " | title }}'
+date = {{ .Date }}
+draft = true
++++
diff --git a/assets/icons/logo.svg b/assets/icons/logo.svg
new file mode 100644
index 0000000..2f2adca
--- /dev/null
+++ b/assets/icons/logo.svg
@@ -0,0 +1,4 @@
+
diff --git a/content/Change Log/_index.md b/content/Change Log/_index.md
deleted file mode 100644
index 680d711..0000000
--- a/content/Change Log/_index.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Change Log
-description: ""
-weight: 100
----
-
-## Changes to the core practices
-
-| Date | Change | Description |
-|------------|----------------------------------------------------------------------------------------------------|-----------------------|
-| 2021-10-27 | [v2.0.0](https://github.com/Minimum-CD/cd-manifesto/releases/tag/2.0 ) | We have moved from the default GitHub page auto-generated Jekyll site to Hugo. This allows us to improve the traceability of changes to the content by decoupling the signatures from the main content. Also helps make content more discoverable and enables search. |
-| 2021-10-12 | [v1.0.0](https://github.com/Minimum-CD/cd-manifesto/tree/6e9d68c442c0e9c9a4bfd9a4edae347fe4a7ce4f) | Dave Farley signature |
-| 2021-10-08 | [v0.0.1](https://github.com/Minimum-CD/cd-manifesto/tree/7c4e098ee19d5fbe1b7d80b2726e8e04e6fff186) | Initial commit |
diff --git a/content/ExperienceReports/_index.md b/content/ExperienceReports/_index.md
index eda9292..00af668 100644
--- a/content/ExperienceReports/_index.md
+++ b/content/ExperienceReports/_index.md
@@ -1,7 +1,12 @@
---
title: Community Experiences
+linkTitle: "Experiences"
description: CD in the real world
weight: 5
+type: docs
+menu:
+ main:
+ weight: 20
---
## CD in the Real World
@@ -18,13 +23,13 @@ It's true, some people still think CD is just tools. Here are some reports from
## Feedback
-{{% panel footer="Dave Farley, Author: Continuous Delivery" %}}
+{{% card footer="Dave Farley, Author: Continuous Delivery" %}}
MinimumCD is a fantastic way to get to the meat of CD quickly. It's a clear, focused, no-holds-barred statement of what it takes to achieve CD. This matters because CD works, and it works better than any other way of delivering software that anyone has found so far.
If you aren't practicing CD in the way that MinimumCD describes it, then you are building worse software more slowly. The trouble is, CD is difficult to adopt. MinimumCD cuts through distracting or confusing complications. If you can do what MinimumCD says, you will be doing a better job. It gives us a clear, simple focus on the essentials of CD that can help teams to understand what really matters to build better software faster.
-{{% /panel %}}
+{{% /card %}}
## MinimumCD in the Media
-- [CodingBlocks Podcast, February 27, 2022](https://www.codingblocks.net/podcast/minimum-viable-continuous-delivery/): The host discuss their impressions of the project
+- [CodingBlocks Podcast, February 27, 2022](https://www.codingblocks.net/podcast/minimum-viable-continuous-delivery/): The hosts discuss their impressions of the project
- [Tiny DevOps #21: Minimum Viable CD](https://jhall.io/archive/2021/11/30/minimum-viable-continuous-delivery/): Jonathan Hall talks to one of the core team about the goals of the project
diff --git a/content/FAQ/_index.md b/content/FAQ/_index.md
index 8d9804c..35cbc87 100644
--- a/content/FAQ/_index.md
+++ b/content/FAQ/_index.md
@@ -1,8 +1,12 @@
---
title: Frequent Questions
-description: FAQ
+linkTitle: "FAQ"
+description:
weight: 5
-draft: false
+type: docs
+menu:
+ main:
+ weight: 99
---
## Why does this exist?
@@ -57,7 +61,7 @@ config](https://12factor.net/config) definitions where "config" is environment s
Central to CD is that we are validating the delivered artifact with the pipeline. It is built once and deployed to all
environments. A common anti-pattern is building an artifact for each environment. This is why trunk-based development is
-so important. More can be found [here](../minimumcd/immutable/).
+so important. More can be found [here](/minimumcd/immutable/).
## What do we mean by "definition of deployable"?
diff --git a/content/Journey/_index.md b/content/Journey/_index.md
index 940f810..079c667 100644
--- a/content/Journey/_index.md
+++ b/content/Journey/_index.md
@@ -1,8 +1,13 @@
---
title: Starting the Journey
+linkTitle: "Starting Out"
description: Suggested improvement paths
weight: 1
draft: false
+type: docs
+menu:
+ main:
+ weight: 20
---
So, where do we start? It's a bad idea to go from "we can't safely commit changes to the trunk" to "deploy every change to production immediately" in one step. It's a journey that requires methodically solving problems in the context of your organization. Here we will discuss some of the common challenges that frequently need to be overcome.
@@ -27,7 +32,7 @@ You may have some others on the list that as you start implementing will come in
Every process we add needs to add value. There's obvious value in doing performance testing unless we are demanding performance at a level that isn't required for the use case. However, before we define CAB documentation as required for "deployable", why does that process exist? One common reason for that meeting is a compliance rule for "two sets of eyes on every change". However, that can be validated by automation without the need to bundle changes and wait for a meeting.
-{{%alert info%}}
+{{% alert %}}
We wanted to investigate the impact of change approval processes on software delivery performance. Thus, we asked about four possible scenarios:
- All production changes must be approved by an external body (such as a manager or CAB).
@@ -35,16 +40,18 @@ We wanted to investigate the impact of change approval processes on software del
- We rely on peer review to manage changes.
- We have no change approval process.
-The results were surprising. We found that approval only for high-risk changes was not correlated with software delivery performance. Teams that reported no approval process or used peer review achieved higher software delivery performance. Finally, teams that required approval by an external body achieved lower performance.
-{{%/alert%}}
+The results were surprising. We found that approval only for high-risk changes was not correlated with software delivery
+performance. Teams that reported no approval process or used peer review achieved higher software delivery performance.
+Finally, teams that required approval by an external body achieved lower performance.
-Excerpt from *Accelerate* by Nicole Forsgren Ph.D., Jez Humble & Gene Kim
+__-- *Accelerate* by Nicole Forsgren Ph.D., Jez Humble & Gene Kim__
+{{% /alert %}}
## Solving the Challenge of CI
The first challenge for the team is [continuous integration](https://www.martinfowler.com/articles/continuousIntegration.html). CD requires CI and CI is very effective at uncovering most of the problems many teams have that impact quality. Martin Fowler has an [excellent blog post on introducing CI](https://www.martinfowler.com/articles/continuousIntegration.html#IntroducingContinuousIntegration) into the workflow. Over the years, we've seen many common problems that teams have.
-You may find more. Notice that tooling is rarely the problem. Always, "why can't we deliver working changes to the trunk today?", is the roadmap of problems to solve.
+You may find more. Notice that tooling is rarely the problem. Always, "Why can't we deliver working changes to the trunk today?", is the roadmap of problems to solve.
### Code review takes too long / has too many approvers
@@ -68,7 +75,7 @@ Teams are not good at testing initially for the same reason they aren't good at
### Individual tasks are too big
-CI means we are integrating partially completed features continuously. TDD helps us learn how to decompose tasks into very small, releasable changes that do not break existing behaviors. However, the initial habit is often to wait to integrate changes until they are "complete". This results in large change-sets that are more difficult to code review. This makes code review take more time, requires more re-work, and reduces the ability of the reviewer to spot problems. [Evolutionary coding methods](../minimumcd/ci/#recommended-practices) allows the release of incomplete features until they are ready and allow us to drive down the size of changes. By focusing as a team to decompose tasks into hours of work rather than days and using engineering techniques to control release, we have improved clarity, smaller change-sets, and higher quality.
+CI means we are integrating partially completed features continuously. TDD helps us learn how to decompose tasks into very small, releasable changes that do not break existing behaviors. However, the initial habit is often to wait to integrate changes until they are "complete". This results in large changesets that are more difficult to code review. This makes code review take more time, requires more re-work, and reduces the ability of the reviewer to spot problems. [Evolutionary [coding methods](/minimumcd/ci/#recommended-practices) allow the release of incomplete features until they are ready and allow us to drive down the size of changes. By focusing as a team to decompose tasks into hours of work rather than days and using engineering techniques to control release, we have improved clarity, smaller change-sets, and higher quality.
### Stories are too big & lack testable acceptance criteria
diff --git a/content/MinimumCD/AppConfig/_index.md b/content/MinimumCD/AppConfig/_index.md
index a3966e8..65a12ac 100644
--- a/content/MinimumCD/AppConfig/_index.md
+++ b/content/MinimumCD/AppConfig/_index.md
@@ -3,4 +3,5 @@ title: Application Configuration
description: Application configuration deploys with artifact
weight: 5
draft: true
+type: docs
---
diff --git a/content/MinimumCD/CI/_index.md b/content/MinimumCD/CI/_index.md
index b2a1735..4f70b89 100644
--- a/content/MinimumCD/CI/_index.md
+++ b/content/MinimumCD/CI/_index.md
@@ -2,6 +2,7 @@
title: Continuous Integration
description: Start here
weight: 2
+type: docs
---
## Definition
diff --git a/content/MinimumCD/Deployable/_index.md b/content/MinimumCD/Deployable/_index.md
index 41e2b43..d88d0a5 100644
--- a/content/MinimumCD/Deployable/_index.md
+++ b/content/MinimumCD/Deployable/_index.md
@@ -3,5 +3,6 @@ title: Definition of Deployable
description: Pipeline artifacts always meet the organization's definition of deployable
weight: 5
draft: true
+type: docs
---
diff --git a/content/MinimumCD/Deterministic/_index.md b/content/MinimumCD/Deterministic/_index.md
index 8a9a61b..6653522 100644
--- a/content/MinimumCD/Deterministic/_index.md
+++ b/content/MinimumCD/Deterministic/_index.md
@@ -3,4 +3,5 @@ title: Deterministic Pipeline
description: The pipeline decides the releasability of changes
weight: 5
draft: true
+type: docs
---
diff --git a/content/MinimumCD/Immutable/_index.md b/content/MinimumCD/Immutable/_index.md
index aabec5e..0253580 100644
--- a/content/MinimumCD/Immutable/_index.md
+++ b/content/MinimumCD/Immutable/_index.md
@@ -2,6 +2,7 @@
title: Immutable Artifact
description: No human changes after commit.
weight: 5
+type: docs
---
Central to CD is that we are validating the artifact with the pipeline. It is built once and deployed to all environments. A common anti-pattern is building an artifact for each environment. The pipeline should generate immutable, versioned artifacts.
diff --git a/content/MinimumCD/ProdLike/_index.md b/content/MinimumCD/ProdLike/_index.md
index fcadd6a..3e4a4ea 100644
--- a/content/MinimumCD/ProdLike/_index.md
+++ b/content/MinimumCD/ProdLike/_index.md
@@ -2,6 +2,7 @@
title: Prod-Like Test Environment
description: Leveraging production-like test environments in your CI/CD pipeline enables reliable testing.
weight: 5
+type: docs
---
## Definition
diff --git a/content/MinimumCD/Rollback/_index.md b/content/MinimumCD/Rollback/_index.md
index 876713d..15868be 100644
--- a/content/MinimumCD/Rollback/_index.md
+++ b/content/MinimumCD/Rollback/_index.md
@@ -3,5 +3,6 @@ title: Rollback On-demand
description: Why these practices are important
weight: 5
draft: true
+type: docs
---
diff --git a/content/MinimumCD/SinglePath/_index.md b/content/MinimumCD/SinglePath/_index.md
index 63d1166..8bf2af2 100644
--- a/content/MinimumCD/SinglePath/_index.md
+++ b/content/MinimumCD/SinglePath/_index.md
@@ -3,4 +3,5 @@ title: Only Path to Any Environment
description: Build once, deploy everywhere
weight: 5
draft: true
+type: docs
---
diff --git a/content/MinimumCD/StopOnRed/_index.md b/content/MinimumCD/StopOnRed/_index.md
deleted file mode 100644
index 5a4668f..0000000
--- a/content/MinimumCD/StopOnRed/_index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Stop on red
-description: All feature work stops when the pipeline is red
-weight: 5
-draft: true
----
-
diff --git a/content/MinimumCD/TBD/_index.md b/content/MinimumCD/TBD/_index.md
index de55200..cc5c258 100644
--- a/content/MinimumCD/TBD/_index.md
+++ b/content/MinimumCD/TBD/_index.md
@@ -2,13 +2,14 @@
title: Trunk Based Development
description: Death of merge hell
weight: 1
+type: docs
---
{{%alert info%}}
-"Trunk-based development has been shown to be a predictor of high performance in software development and delivery. It is characterized by fewer than three active branches in a code repository; branches and forks having very short lifetimes (e.g., less than a day) before being merged into master; and application teams rarely or never having "code lock" periods when no one can check in code or do pull requests due to merging conflicts, code freezes, or stabilization phases."
+"Trunk-based development has been shown to be a predictor of high performance in software development and delivery. It is characterized by fewer than three active branches in a code repository; branches and forks having very short lifetimes (e.g., less than a day) before being merged; and application teams rarely or never having "code lock" periods when no one can check in code or do pull requests due to merging conflicts, code freezes, or stabilization phases."
-{{%/alert%}}
+{{% /alert %}}
Excerpt from *Accelerate* by Nicole Forsgren Ph.D., Jez Humble & Gene Kim
@@ -24,5 +25,5 @@ It is important to note that release branches are an intermediate step that some
- **We must test**: TBD requires us to implement tests as part of the development process.
- **Better teamwork**: We need to work more closely as a team. This has many positive impacts, not least we will be more focused on getting the team's highest priority done. We will stop starting and start finishing work.
- **Better work definition**: Small changes require us to decompose the work into a level of detail that helps uncover things that lack clarity or do not make sense. This provides much earlier feedback on potential quality issues.
-- **Replaces process with engineering**: Instead of creating a process where we control the release of features with branches, we can control the release of features with engineering techniques called [evolutionary coding methods](../../minimumcd/ci/#recommended-practices). These techniques have additional benefits related to stability that cannot be found when replaced by process.
+- **Replaces process with engineering**: Instead of creating a process where we control the release of features with branches, we can control the release of features with engineering techniques called [evolutionary coding methods](/minimumcd/ci/#recommended-practices). These techniques have additional benefits related to stability that cannot be found when replaced by process.
- **Reduces risk**: There are two risks with long-lived branches that happen frequently. First, the change will not integrate cleanly and the merge conflicts result in broken or lost features. Second, the branch will be abandoned. This is usually because of the first reason. Sometimes because all of the knowledge about what is in that branch resides in the mind of someone who decided to leave before it was integrated.
diff --git a/content/MinimumCD/_index.md b/content/MinimumCD/_index.md
index 01c2b6d..f21444f 100644
--- a/content/MinimumCD/_index.md
+++ b/content/MinimumCD/_index.md
@@ -1,17 +1,21 @@
---
title: Minimum Viable CD
-description: ""
+linkTitle: "Minimum CD"
+
+description: Problems to solve to improve your organization
weight: 1
+type: docs
---
-{{% notice %}}
+{{% alert %}}
"Continuous delivery improves both delivery performance and quality, and also helps improve culture and reduce burnout and deployment pain."
--- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
-{{% /notice %}}
+__-- *Accelerate* by Nicole Forsgren Ph.D., Jez Humble & Gene Kim__
+_
+{{% /alert %}}
-![MinimumCD](/images/minimumCD-logo-hex.png?height=150px)
+{{< figure src="/images/minimumCD-logo-hex.webp" alt="MinimumCD">}}
We, [the undersigned](#signatories), believe that a minimal definition of continuous delivery (CD) is required to improve the flow of delivery and achieve the outcomes above. While our contexts may be different, there are universal practices common in all. By defining them we can:
@@ -35,13 +39,13 @@ The minimum activities required for CD are:
- The [application
pipeline](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract)
is the only way to deploy to any environment
-- The pipeline decides the releasability of changes, its verdict is [definitive](../faq/#why-should-the-pipeline-be-definitive-for-deploy)
-- Artifacts created by the pipeline always meet the organization's [definition of deployable](../faq/#what-do-we-mean-by-definition-of-deployable)
-- [Immutable artifact](../minimumcd/immutable/) (no human changes after commit)
+- The pipeline decides the releasability of changes, its verdict is [definitive](/faq/#why-should-the-pipeline-be-definitive-for-deploy)
+- Artifacts created by the pipeline always meet the organization's [definition of deployable](/faq/#what-do-we-mean-by-definition-of-deployable)
+- [Immutable artifact](/minimumcd/immutable/) (no human changes after commit)
- All feature work stops when the pipeline is red
-- [Production-like test environment](../minimumcd/prodlike/)
+- [Production-like test environment](/minimumcd/prodlike/)
- Rollback on-demand
-- [Application configuration](../faq/#what-is-application-configuration) deploys with artifact
+- [Application configuration](/faq/#what-is-application-configuration) deploys with artifact
## Continuous Integration
@@ -58,7 +62,7 @@ The minimum activities required for CI are:
## Trunk-based Development
-[Trunk-based development](../minimumcd/tbd) is the branching pattern required to meet the definition
+[Trunk-based development](/minimumcd/tbd) is the branching pattern required to meet the definition
of CI. It prevents lost work, the risk of corruption that comes from merge conflict resolution, and also reduces movement
waste that increases batch size.
@@ -72,11 +76,11 @@ The minimum activities required for TBD are:
## Why did we build this?
-For background on Minimum CD and answers to other common questions, please [read the FAQs](../faq).
+For background on Minimum CD and answers to other common questions, please [read the FAQs](/faq).
## Starting the Journey
-Questions on where to start? Check out some [recommendations](../journey).
+Questions on where to start? Check out some [recommendations](/journey).
## Contributing
diff --git a/content/Practices/SmallBatches/_index.md b/content/Practices/SmallBatches/_index.md
index 7e3be8f..c7cd70a 100644
--- a/content/Practices/SmallBatches/_index.md
+++ b/content/Practices/SmallBatches/_index.md
@@ -2,6 +2,7 @@
title: Work in Small Batches
description: Specific advice for an often misunderstood principle of continuous delivery.
weight: 1
+type: docs
---
We need to reduce batch size because smaller batches of work are easier to verify, they tend to fail small, we are less likely to suffer from sunk-cost fallacy, we amplify feedback loops, etc. How small should they be? As small as we can make them to get production feedback on what we are trying to learn. Working to reduce batch size acts as a forcing function for exposing and removing hidden waste in upstream processes. There are several batch sizes we are trying to reduce.
@@ -20,15 +21,16 @@ This comes from a misunderstanding of what CD is for. Yes, we can deliver featur
### Commit Smaller Changes
-{{% notice %}}
+{{% alert %}}
"Following our principle of working in small batches and building quality in, high-performing teams keep branches short-lived (less than one day's work) and integrate them into trunk/master frequently. Each change triggers a build process that includes running unit tests. If any part of this process fails, developers fix it immediately."
--- Accelerate: Forsgren, et al
-{{% /notice %}}
+**-- *Accelerate* by Nicole Forsgren Ph.D., Jez Humble & Gene Kim**
+
+{{% /alert %}}
How small is small? One change a day is big. Smaller than that. These are not feature complete changes. They are small, tested changes that can be delivered to production if certified by the pipeline.
-Solving the problems required to meet the [definition of CI](../../minimumcd/#continuous-integration) is foundational for the efforts to improve the organization. It is very effective at uncovering that we need to improve testing, learn how to use evolutionary coding practices, understand trunk-based development, learn to decompose work better, and learn how to work as a team better. It's also effective at shining a light on upstream issues.
+Solving the problems required to meet the [definition of CI](/minimumcd/#continuous-integration) is foundational for the efforts to improve the organization. It is very effective at uncovering that we need to improve testing, learn how to use evolutionary coding practices, understand trunk-based development, learn to decompose work better, and learn how to work as a team better. It's also effective at shining a light on upstream issues.
### Refine Smaller Stories
@@ -36,11 +38,11 @@ How small is small? It's typical for teams who have only been taught Scrum to re
In 2012, Paul Hammant, author of "Trunk-Based Development and Branch by Abstraction" made the following suggestion:
-{{% notice %}}
+{{% alert %}}
"Story sizes should average as close to one day as possible. If they don't, your Agile project is going to be harder for nearly everyone involved. If your average is significantly greater than that one day, then change something until you get there."
--- [Call to Arms: Average Story Size of One Day](https://paulhammant.com/2012/04/24/call-to-arms-average-story-sizes-of-one-day/)
-{{% /notice %}}
+-- **[Call to Arms: Average Story Size of One Day](https://paulhammant.com/2012/04/24/call-to-arms-average-story-sizes-of-one-day/)**
+{{% /alert %}}
This may sound unachievable, but we have seen how effective this is in the enterprise Dojos. A primary workflow for Dojos is the "hyper-sprint". A hyper-sprint lasts for 2.5 days and includes refining work, doing the work, delivering the work, and retrospecting on how to do it better next time. Teams fail for a few weeks but then learn the skills and teamwork required to slice stories into much thinner value increments with fully testable acceptance criteria and deliver them as a team. Coding moves from exploration to implementation and quality feedback and throughput accelerate. It's very common for a team's throughput to double in 6-8 weeks with the right guidance. Again, this acts as a forcing function for uncovering and removing upstream impediments with missing product information, external hard dependencies with other teams, Change Advisory Board compliance theater, or other organizational issues.
diff --git a/content/Practices/_index.md b/content/Practices/_index.md
index aaa5c64..71500b7 100644
--- a/content/Practices/_index.md
+++ b/content/Practices/_index.md
@@ -1,7 +1,10 @@
---
title: Recommended Practices
+linkTitle: "Practices"
description: ""
weight: 5
+type: docs
+menu:
+ main:
+ weight: 20
---
-
-{{% children style="h2" depth="1" description="true" /%}}
diff --git a/content/References/_index.md b/content/References/_index.md
index 98304e6..13f1289 100644
--- a/content/References/_index.md
+++ b/content/References/_index.md
@@ -1,7 +1,12 @@
---
title: Beyond the Minimums
+linkTitle: "Resources"
description: Recommended Resources
weight: 5
+type: docs
+menu:
+ main:
+ weight: 20
---
Minimum CD is not the first step in a maturity model. However, it is still the bare minimum upon which many more practices should be built as appropriate to your context. To aid your journey in going beyond Minimum CD, we maintain a list of resources that focus on Continuous Delivery which we have found very useful in our own journeys.
diff --git a/content/Translations/Finnish/_index.md b/content/Translations/Finnish/_index.md
index a40f22f..867f82f 100644
--- a/content/Translations/Finnish/_index.md
+++ b/content/Translations/Finnish/_index.md
@@ -2,6 +2,7 @@
title: Suomi
description: "Vähäisin toimiva jatkuva toimittaminen"
weight: 3
+type: docs
---
## Vähäisin toimiva jatkuva toimittaminen
@@ -10,7 +11,7 @@ weight: 3
-- Accelerate
-Me, [allekirjoittaneet](../../minimumcd/#signatories), uskomme, että jatkuvalle toimittamiselle (engl. continuous delivery, CD) tarvitaan määritelmä, jotta toimitusvirtaa voidaan parantaa. Riippumatta erilaisista olosuhteistamme, on olemassa yleispäteviä käytäntöjä. Määrittelemällä nämä käytännöt voimme:
+Me, [allekirjoittaneet](/minimumcd/#signatories), uskomme, että jatkuvalle toimittamiselle (engl. continuous delivery, CD) tarvitaan määritelmä, jotta toimitusvirtaa voidaan parantaa. Riippumatta erilaisista olosuhteistamme, on olemassa yleispäteviä käytäntöjä. Määrittelemällä nämä käytännöt voimme:
- Perehdyttää uudet harjoittajat yhdenmukaisella tavalla
- Keskustella ohjelmistotuotannon käytännöistä, joista CD muodostuu
@@ -31,13 +32,13 @@ Jatkuvan toimittamisen minimivaatimukset ovat:
- [Jatkuva integraatio](#jatkuva-integraatio)
- [Sovelluksen toimitusputki](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract)
on ainoa tie tuotantoonvientiin.
-- Toimitusputki määrää muutosten julkaisukelpoisuuden, sen lausunto on [ehdoton](../../faq/#why-should-the-pipeline-be-definitive-for-deploy)
+- Toimitusputki määrää muutosten julkaisukelpoisuuden, sen lausunto on [ehdoton](/faq/#why-should-the-pipeline-be-definitive-for-deploy)
- [Organisaation tuotantoonvientikelpoisen määritelmä täyttyy aina](https://www.youtube.com/watch?v=bHKHdp4H-8w)
-- [Artifakti on muuttumaton](../../minimumcd/immutable/). Ei ihmisen tekemiä muutoksia versionhallintaan tallentamisen jälkeen.
+- [Artifakti on muuttumaton](/minimumcd/immutable/). Ei ihmisen tekemiä muutoksia versionhallintaan tallentamisen jälkeen.
- Kaikki uuskehitys loppuu, kun toimitusputki on punaisella
- Tuotannonkaltainen testiympäristö
- Tuotantoonviennin peruutus tarvittaessa
-- [Sovelluksen konfiguraatio](../../faq/#what-is-application-configuration) viedään tuotantoon artifaktin kanssa
+- [Sovelluksen konfiguraatio](/faq/#what-is-application-configuration) viedään tuotantoon artifaktin kanssa
## Jatkuva integraatio
@@ -45,7 +46,7 @@ Jatkuva integraatio (CI) on toimintatapa, jossa työ integroidaan päähaaraan e
Jatkuvan integraation minimivaatimukset ovat:
-- Päähaarassa kehittäminen ([Trunk-based development](../../minimumcd/tbd/))
+- Päähaarassa kehittäminen ([Trunk-based development](/minimumcd/tbd/))
- Työ integroidaan päähaaraan vähintään päivittäin
- Työ testataan automaattisesti ennen päähaaraan yhdistämistä
- Työ testataan muun työn kanssa automaattisesti haaroja yhdistettäessä
@@ -54,7 +55,7 @@ Jatkuvan integraation minimivaatimukset ovat:
## Päähaarassa kehittäminen (Trunk-based Development)
-Päähaarassa kehittäminen eli [Trunk-based development](../../minimumcd/tbd/) on versionhallinnan haarauttamistapa, joka vaaditaan jatkuvan integraation määritelmään. Se estää työn katoamisen, työn korruptoitumisen haarojen yhdistämiseen liittyvissä konflikteissa ja vähentää liike-hukkaa, joka johtaa suuriin eräkokoihin.
+Päähaarassa kehittäminen eli [Trunk-based development](/minimumcd/tbd/) on versionhallinnan haarauttamistapa, joka vaaditaan jatkuvan integraation määritelmään. Se estää työn katoamisen, työn korruptoitumisen haarojen yhdistämiseen liittyvissä konflikteissa ja vähentää liike-hukkaa, joka johtaa suuriin eräkokoihin.
Päähaarassa kehittämisen minimivaatimukset ovat:
@@ -70,11 +71,11 @@ Minimi-CD ei ole ensimmäinen askel kypsyysmallissa. Siitä huolimatta se on vä
Näistä lähteistä löytyy sekä perusasiat että tiedot, joilla voi tulla "eliitti"-CD-organisaatioksi. Ne keskittyvät ratkaisemaan ongelman: "Miksei me voida mennä tuotantoon tänään?"
-[Lue lista](../../references/).
+[Lue lista](/references/).
## Miksi teimme tämän?
-Lisää taustatietoa Minimi-CD:stä ja vastauksia yleisimpiin kysymyksiin löytyy [usein kysytyistä kysymyksistä](../../faq/).
+Lisää taustatietoa Minimi-CD:stä ja vastauksia yleisimpiin kysymyksiin löytyy [usein kysytyistä kysymyksistä](/faq/).
## Haluatko osallistua tai allekirjoittaa?
@@ -82,7 +83,7 @@ Lue [osallistumisohje](https://github.com/Minimum-CD/cd-manifesto/blob/master/CO
## Allekirjoittajat
-Allekirjoittajat ovat allekirjoittaneet [englanninkielisen alkuperäisdokumentin](../../minimumcd/#signatories) ja ajantasainen nimilista julkaistaan ainoastaan sen yhteydessä.
+Allekirjoittajat ovat allekirjoittaneet [englanninkielisen alkuperäisdokumentin](/minimumcd/#signatories) ja ajantasainen nimilista julkaistaan ainoastaan sen yhteydessä.
## Käännös
diff --git a/content/Translations/French/_index.md b/content/Translations/French/_index.md
index 7c38d1c..2335044 100644
--- a/content/Translations/French/_index.md
+++ b/content/Translations/French/_index.md
@@ -2,6 +2,7 @@
title: Francais
description: "Le minimum viable de la Livraison Continue"
weight: 3
+type: docs
---
## Le minimum viable de la Livraison Continue
@@ -10,9 +11,9 @@ weight: 3
-- Accelerate
-![MinimumCD](/images/minimumCD-logo-hex.png?height=150px)
+{{< figure src="/images/minimumCD-logo-hex.png" alt="MinimumCD" width="20%" >}}
-Nous, [les signataires](../../minimumcd/#signatories), estimons qu'une définition minimale de la Livraison Continue (Continuous Delivery, CD) est requise afin d'améliorer les flux de livraisons. Bien que chaque contexte soit unique, il y a des pratiques universelles. En les définissant, nous pouvons :
+Nous, [les signataires](/minimumcd/#signatories), estimons qu'une définition minimale de la Livraison Continue (Continuous Delivery, CD) est requise afin d'améliorer les flux de livraisons. Bien que chaque contexte soit unique, il y a des pratiques universelles. En les définissant, nous pouvons :
- Présenter les choses aux nouveaux arrivants de manière cohérente
- Discuter des pratiques d'ingénierie qui composent le CD (Continuous Delivery)
@@ -36,13 +37,13 @@ Les activités minimales requises pour la Livraison Continue sont :
- [L'intégration continue](#intégration-continue)
- Le [pipeline de déploiement](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract)
est le seul chemin qui permet de déployer en production.
-- Le pipeline décide de la diffusion des modifications, son verdict est [définitif](../../faq/#why-should-the-pipeline-be-definitive-for-deploy)
+- Le pipeline décide de la diffusion des modifications, son verdict est [définitif](/faq/#why-should-the-pipeline-be-definitive-for-deploy)
- Les artefacts créés par le pipeline répondent toujours à la [définition de Déployable](https://www.youtube.com/watch?v=bHKHdp4H-8w) de l'organisation
-- [L'artefact ne change jamais](../../minimumcd/immutable/). Il n'y a aucun changement humain après le commit.
+- [L'artefact ne change jamais](/minimumcd/immutable/). Il n'y a aucun changement humain après le commit.
- Tous les travaux sur les fonctionnalités s'arrêtent lorsque le pipeline est rouge
- L'environnement de test est proche de l'environnement de production
- On peut revenir en arrière (rollback) à la demande
-- [La configuration de l'application](../../faq/#what-is-application-configuration) est déployée avec l'artefact
+- [La configuration de l'application](/faq/#what-is-application-configuration) est déployée avec l'artefact
## Intégration Continue
@@ -51,7 +52,7 @@ dépôt de code, et à vérifier que ce travail est, à notre connaissance, prop
Les activités minimales requises pour CI sont :
-- [Le développement basé sur un tronc commun](../../minimumcd/tbd/)
+- [Le développement basé sur un tronc commun](/minimumcd/tbd/)
- Le travail est intégré au tronc commun au moins une fois par jour
- Le travail est testé automatiquement avec d'être fusionné au tronc commun
- Le travail est testé avec celui des autres automatiquement lors de la fusion
@@ -60,7 +61,7 @@ Les activités minimales requises pour CI sont :
## Le développement basé sur un tronc commun (Trunk-based Development, TBD)
-[Le développement basé sur un tronc commun](../../minimumcd/tbd/) est le modèle de branche requis pour répondre à la définition d'Intégration Continue.
+[Le développement basé sur un tronc commun](/minimumcd/tbd/) est le modèle de branche requis pour répondre à la définition d'Intégration Continue.
Il évite la perte de travail, le risque de corruption qui provient des résolutions de conflits lors des fusions, et
réduit également le gaspillage d'énergie induit par la taille des lots/
@@ -74,11 +75,11 @@ Les activités minimales requises pour le TBD sont :
## Pourquoi avons-nous construit ce manifeste ?
-Pour plus d'informations sur la Livraison Continue Minimale et des réponses à d'autres questions courantes, [veuillez lire la FAQ](../../faq/).
+Pour plus d'informations sur la Livraison Continue Minimale et des réponses à d'autres questions courantes, [veuillez lire la FAQ](/faq/).
## Vous souhaitez contribuer ou devenir signataire ?
-Les signataires ont signé le [document original en anglais](../../minimumcd/#signatories), et la liste des noms sera tenue à jour uniquement sur celui-ci.
+Les signataires ont signé le [document original en anglais](/minimumcd/#signatories), et la liste des noms sera tenue à jour uniquement sur celui-ci.
## Traduction
diff --git a/content/Translations/French/references.md b/content/Translations/French/references.md
index d5d719b..1a28bcb 100644
--- a/content/Translations/French/references.md
+++ b/content/Translations/French/references.md
@@ -2,6 +2,7 @@
title: Au-delà des minimums
description: Ressources recommandées
weight: 5
+type: docs
---
## Au-delà des minimums
@@ -14,4 +15,4 @@ livraison continue, que nous que nous avons trouvées très utiles dans nos prop
Ces ressources contiennent les bases, mais aussi les connaissances nécessaires pour devenir une organisation de Livraison Continue « d'élite ».
Elles sont dédiées à la résolution du problème « pourquoi ne pouvons-nous pas passer en production aujourd'hui ? »
-[Lire la liste](../../../references/).
+[Lire la liste](/references/).
diff --git a/content/Translations/German/_index.md b/content/Translations/German/_index.md
index 9819273..b2471cc 100644
--- a/content/Translations/German/_index.md
+++ b/content/Translations/German/_index.md
@@ -2,24 +2,17 @@
title: Deutsch
description: "Minimale nutzbare kontinuierliche Lieferung"
weight: 3
+type: docs
---
-{{% notice %}}
+{{% alert %}}
"Kontinuierliche Lieferung vebessert die Geschwindigkeit und Qualität der Auslieferung, und hilft zugleich die Kultur zu verbessern, Burnout und Mühsal in der Entwicklung zu vermeiden."
-- Das Mindset von DevOps. Accelerate: 24 Schlüsselkompetenzen, um leistungsstarke Technologieunternehmen zu entwickeln und zu skalieren
-{{% /notice %}}
+{{% /alert %}}
-![MinimumCD](/images/minimumCD-logo-hex.png?height=150px)
-
-Minimum Viable CD
-
-"Kontinuierliche Lieferung verbessert sowohl die Lieferleistung als auch die Qualität und trägt außerdem zur Verbesserung der Unternehmenskultur und zur Verringerung von Burnout und Lieferungsschmerzen bei.
-
-- Accelerate: Die Wissenschaft von schlanker Software und DevOps: Aufbau und Skalierung hochleistungsfähiger Technologieorganisationen
-
-MinimumCD
+{{< figure src="/images/minimumCD-logo-hex.png" alt="MinimumCD" width="20%" >}}
Wir, [die Unterzeichner](#unterzeichner), sind der Meinung, dass eine Minimale Definition von Continuous Delivery (CD) erforderlich ist, um den Ablauf der Software-Lieferung zu verbessern und die oben genannten Ergebnisse zu erzielen. Obwohl unsere Kontexte unterschiedlich sein mögen, gibt es universelle Praktiken, die allen Situationen und Teams gemeinsam sind. Indem wir diese definieren, können wir:
@@ -39,13 +32,13 @@ Die für CD erforderlichen Mindestaktivitäten sind:
- [Kontinuierliche Integration](#kontinuierliche-integration) verwenden
- Die [Anwendungspipeline](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract) ist die einzige Möglichkeit zur Lieferung in einer beliebigen Umgebung.
-- Die Pipeline entscheidet über die Freigabefähigkeit von Änderungen, ihr Urteil ist [endgültig](../../faq/#why-should-the-pipeline-be-definitive-for-deploy)
-- Die von der Pipeline erstellten Artefakte entsprechen immer der der organisationseigenen ["Definition für deploybar"](../../faq/#what-do-we-mean-by-definition-of-deployable).
-- [Unveränderliche Artefakte](../../minimumcd/immutable/). Keine menschlichen Änderungen nach der Übergabe an cas CD-System.
+- Die Pipeline entscheidet über die Freigabefähigkeit von Änderungen, ihr Urteil ist [endgültig](/faq/#why-should-the-pipeline-be-definitive-for-deploy)
+- Die von der Pipeline erstellten Artefakte entsprechen immer der der organisationseigenen ["Definition für deploybar"](/faq/#what-do-we-mean-by-definition-of-deployable).
+- [Unveränderliche Artefakte](/minimumcd/immutable/). Keine menschlichen Änderungen nach der Übergabe an cas CD-System.
- Jegliche Arbeiten an Features werden eingestellt, wenn die Pipeline defekt ist.
- Produktionsähnliche Testumgebung
- Rollback bei Bedarf
-- [Anwendungskonfiguration](../../faq/#what-is-application-configuration) wird gemeinsam mit dem Artefakt ausgeliefert
+- [Anwendungskonfiguration](/faq/#what-is-application-configuration) wird gemeinsam mit dem Artefakt ausgeliefert
## Kontinuierliche Integration
@@ -62,7 +55,7 @@ Die für CI erforderlichen Mindestaktivitäten sind:
## Trunk-basierte Entwicklung
-Die [trunk-basierte Entwicklung](../../minimumcd/tbd/) ist das branching Modell, das erforderlich ist, um die Definition von CI zu erfüllen. Es verhindert den Verlust von Arbeit, das Risiko von verfälschtem oder defektem Code bei der Lösung von Merge-Konflikten besteht und auch die (Lean-) Verschwendung durch Bewegung, die die Batchgröße erhöht.
+Die [trunk-basierte Entwicklung](/minimumcd/tbd/) ist das branching Modell, das erforderlich ist, um die Definition von CI zu erfüllen. Es verhindert den Verlust von Arbeit, das Risiko von verfälschtem oder defektem Code bei der Lösung von Merge-Konflikten besteht und auch die (Lean-) Verschwendung durch Bewegung, die die Batchgröße erhöht.
- Die für TBD erforderlichen Mindestaktivitäten sind:
- Alle Änderungen werden in den Stamm integriert.
@@ -73,11 +66,11 @@ Die [trunk-basierte Entwicklung](../../minimumcd/tbd/) ist das branching Modell,
## Warum haben wir das gebaut?
-Für Hintergrundinformationen zu Minimum CD und Antworten auf andere häufige Fragen, lesen Sie bitte die [FAQs](../../faq/).
+Für Hintergrundinformationen zu Minimum CD und Antworten auf andere häufige Fragen, lesen Sie bitte die [FAQs](/faq/).
## Die Reise beginnen
-Haben Sie Fragen, wo Sie anfangen sollen? Sehen Sie sich einige [Empfehlungen](../../journey/) an.
+Haben Sie Fragen, wo Sie anfangen sollen? Sehen Sie sich einige [Empfehlungen](/journey/) an.
## Beitragen
diff --git a/content/Translations/Italian/_index.md b/content/Translations/Italian/_index.md
index 59a7a3a..a1aa1a4 100644
--- a/content/Translations/Italian/_index.md
+++ b/content/Translations/Italian/_index.md
@@ -2,6 +2,7 @@
title: Italiano
description: "Implementazione minima della Continuous Delivery"
weight: 3
+type: docs
---
## Implementazione minima della Continuous Delivery
@@ -10,7 +11,7 @@ weight: 3
-- Accelerate `(Unofficial translation)`
-Noi, [i firmatari](../../minimumcd/#signatories), riteniamo che la definizione di un'implementazione minima della Continuous Delivery (CD) sia necessaria per migliorare il flusso di rilascio del software. Sebbene i contesti in cui lavoriamo possano essere diversi, esistono pratiche universali. Definendo tali pratiche possiamo:
+Noi, [i firmatari](/minimumcd/#signatories), riteniamo che la definizione di un'implementazione minima della Continuous Delivery (CD) sia necessaria per migliorare il flusso di rilascio del software. Sebbene i contesti in cui lavoriamo possano essere diversi, esistono pratiche universali. Definendo tali pratiche possiamo:
- Introdurre alla Continuous Delivery nuovi praticanti in modo coerente
- Discutere le pratiche ingegneristiche che costituiscono CD
@@ -30,13 +31,13 @@ Il set minimo di attività richieste per la CD sono:
- [Continuous integration](#continuous-integration-integrazione-continua) (Integrazione Continua)
- La [application pipeline](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract) è l'unico percorso per il rilascio in produzione
-- La pipeline decide la rilasciabilità delle modifiche software, e il suo verdetto è [definitivo](./faq/#perch%C3%A9-la-pipeline-dovrebbe-dettare-legge-per-il-rilascio)
+- La pipeline decide la rilasciabilità delle modifiche software, e il suo verdetto è [definitivo](/translations/italian/faq/#perch%C3%A9-la-pipeline-dovrebbe-dettare-legge-per-il-rilascio)
- Gli artefatti creati dalla pipeline soddisfano sempre la definizione di rilasciabilità [definition of deployable](https://www.youtube.com/watch?v=bHKHdp4H-8w) della specifica organizzazione
-- Artefatti immutabili ([Immutable artifact](./faq/#cosa-significa-artefatti-immutabili)): nessuna modifica manuale dopo i commit
+- Artefatti immutabili ([Immutable artifact](/translations/italian/faq/#cosa-significa-artefatti-immutabili)): nessuna modifica manuale dopo i commit
- Tutto il lavoro si ferma se la pipeline fallisce
- Utilizzare ambienti di test il più possibile simili all'ambiente di produzione
- Rollback su richiesta
-- La [configurazione dell'applicazione](./faq/#cosa-significa-artefatti-immutabili) viene distribuita assieme agli artefatti
+- La [configurazione dell'applicazione](/translations/italian/faq/#cosa-significa-artefatti-immutabili) viene distribuita assieme agli artefatti
## Continuous Integration (Integrazione continua)
@@ -44,7 +45,7 @@ La CI è l'attività che ci consente di integrare continuamente il lavoro di cia
Le attività minime richieste dalla CI sono:
-- [Trunk-based development](../../minimumcd/tbd/)
+- [Trunk-based development](/minimumcd/tbd/)
- Il lavoro viene integrato nel trunk almeno una volta al giorno
- Una suite di test automatici verifica il lavoro prima che venga integrato nel trunk
- Una suite di test automatici verifica il lavoro dopo essere stato integrato nel trunk
@@ -53,7 +54,7 @@ Le attività minime richieste dalla CI sono:
## Trunk-based Development
-Il [Trunk-based Development](../../minimumcd/tbd/) è il modello di branching necessario a soddisfare la definizione della CI. La CI evita la perdita delle modifiche, il rischio di corruzione che deriva dall'integrazione e dalla risoluzione dei conflitti, e riduce lo spreco dovuto ad attività che potrebbero aumentare la dimensione degli insiemi di modifiche.
+Il [Trunk-based Development](/minimumcd/tbd/) è il modello di branching necessario a soddisfare la definizione della CI. La CI evita la perdita delle modifiche, il rischio di corruzione che deriva dall'integrazione e dalla risoluzione dei conflitti, e riduce lo spreco dovuto ad attività che potrebbero aumentare la dimensione degli insiemi di modifiche.
- Le attività minime richieste dal TBD sono:
- Tutte le modifiche devono essere integrate nel trunk
@@ -69,11 +70,11 @@ La CD minima non è il primo passo in un modello di maturità, tuttavia è il mi
Queste risorse contengono sia conoscenze di base, sia conoscenze necessarie a farvi diventare un'organizzazione CD "d'élite".
Sono risposte specifiche alla domanda "Cosa ci impedisce di andare in produzione oggi?"
-[Vedi la lista](../../references/).
+[Vedi la lista](/references/).
## Perche abbiamo costruito questa lista?
-Per maggiori dettagli sulla CD minima e risposte su altre domande comuni, vi rimandiamo alle [FAQs](./faq/).
+Per maggiori dettagli sulla CD minima e risposte su altre domande comuni, vi rimandiamo alle [FAQs](/translations/italian/faq/).
## Per contribuire o diventare firmatari
@@ -81,7 +82,7 @@ Vedere [linee guida per contribuire](https://github.com/Minimum-CD/cd-manifesto/
## Firmatari
-I firmatari hanno firmato la [versione originale in inglese](../../minimumcd/#signatories) e la lista corrente dei nomi è pubblicata solo in quella versione
+I firmatari hanno firmato la [versione originale in inglese](/minimumcd/#signatories) e la lista corrente dei nomi è pubblicata solo in quella versione
## Traduzione
diff --git a/content/Translations/Italian/faq.md b/content/Translations/Italian/faq.md
index b731f6b..e753111 100644
--- a/content/Translations/Italian/faq.md
+++ b/content/Translations/Italian/faq.md
@@ -1,6 +1,7 @@
---
title: Domande Frequenti (FAQ)
description: "Implementazione minima della Continuous Delivery"
+type: docs
---
## Motivazioni
diff --git a/content/Translations/Portuguese-BR/_index.md b/content/Translations/Portuguese-BR/_index.md
index 7919a7e..bdcd914 100644
--- a/content/Translations/Portuguese-BR/_index.md
+++ b/content/Translations/Portuguese-BR/_index.md
@@ -2,22 +2,23 @@
title: "Português Brasileiro"
description: "Mínimo viável para a Entrega Contínua"
weight: 3
+type: docs
---
## Mínimo viável para a Entrega Contínua
-{{% notice %}}
+{{% alert %}}
"A entrega contínua não só melhora a qualidade e capacidade de entrega, bem como ajuda na evolução da cultura, reduz a estafa e as dificuldades na implantação."
-- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (Tradução não oficial)
-{{% /notice %}}
+{{% /alert %}}
-![MinimumCD](/images/minimumCD-logo-hex.png?height=150px)
+{{< figure src="/images/minimumCD-logo-hex.png" alt="MinimumCD" width="20%" >}}
-Nós, [os abaixo-assinados](../../minimumcd/#signatories), acreditamos que é necessária uma definição mínima de entrega contínua (_Continuous Delivery_, CD) para a melhoria do fluxo de entrega e cumprimento dos resultados supracitados. Embora os nossos contextos possam ser diferentes, existem práticas universais consideradas comuns. Ao defini-las, é possível:
+Nós, [os abaixo-assinados](/minimumcd/#signatories), acreditamos que é necessária uma definição mínima de entrega contínua (_Continuous Delivery_, CD) para a melhoria do fluxo de entrega e cumprimento dos resultados supracitados. Embora os nossos contextos possam ser diferentes, existem práticas universais consideradas comuns. Ao defini-las, é possível:
- Introduzi-las aos novos praticantes, de forma consistente
- Discutir as práticas de engenharia que abrangem a entrega contínua
@@ -37,13 +38,13 @@ As atividades mínimas exigidas para o CD são:
- Uso de [Integração contínua](#integração-contínua)
- O [_delivery pipeline_](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract) é a única forma possível de fazer _deploy_ para qualquer ambiente
-- O _pipeline_ decide se as mudanças atendem ou não os requisitos para entrada em produção. Esse veredicto é [definitivo](../../faq/#why-should-the-pipeline-be-definitive-for-deploy)
-- Os artefatos criados pelo _pipeline_ respeitam sempre a [definição de _deployable_](../../faq/#what-do-we-mean-by-definition-of-deployable) da organização
-- [Artefato imutável](../../minimumcd/immutable/) (não existem mudanças manuais após o _commit_)
+- O _pipeline_ decide se as mudanças atendem ou não os requisitos para entrada em produção. Esse veredicto é [definitivo](/faq/#why-should-the-pipeline-be-definitive-for-deploy)
+- Os artefatos criados pelo _pipeline_ respeitam sempre a [definição de _deployable_](/faq/#what-do-we-mean-by-definition-of-deployable) da organização
+- [Artefato imutável](/minimumcd/immutable/) (não existem mudanças manuais após o _commit_)
- Todo o desenvolvimento de funcionalidades é suspenso quando o _pipeline_ falha
- Ambiente de testes semelhante ao ambiente produtivo
- _Rollback_ sob demanda
-- A [configuração da aplicação](../../faq/#what-is-application-configuration) é implantada junto com o artefato
+- A [configuração da aplicação](/faq/#what-is-application-configuration) é implantada junto com o artefato
## Integração Contínua
@@ -60,7 +61,7 @@ As atividades mínimas necessárias ao CI são:
## Trunk-Based Development
-O [_Trunk-based development_](../../minimumcd/tbd/) (versão inglesa) (TBD) é um padrão de _branching_ mandatório para cumprimento dos requisitos de CI. Evita a perda de trabalho, o risco de mudanças corrompidas devido à resolução de conflitos do _merge_ e também reduz o desperdício de movimento que aumenta o tamanho do _batch_ de mudanças.
+O [_Trunk-based development_](/minimumcd/tbd/) (versão inglesa) (TBD) é um padrão de _branching_ mandatório para cumprimento dos requisitos de CI. Evita a perda de trabalho, o risco de mudanças corrompidas devido à resolução de conflitos do _merge_ e também reduz o desperdício de movimento que aumenta o tamanho do _batch_ de mudanças.
As atividades mínimas necessárias para o TBD são:
@@ -72,11 +73,11 @@ As atividades mínimas necessárias para o TBD são:
## Por que construímos este manifesto?
-Para obter informações acerca do Mínimo CD e respostas a outras questões comuns, por favor [leia o FAQ](../../faq/) (versão inglesa).
+Para obter informações acerca do Mínimo CD e respostas a outras questões comuns, por favor [leia o FAQ](/faq/) (versão inglesa).
## Começando a jornada
-Dúvidas sobre como começar? Confira algumas [recomendações](../../journey/) (versão inglesa).
+Dúvidas sobre como começar? Confira algumas [recomendações](/journey/) (versão inglesa).
## Contribuindo
@@ -86,7 +87,7 @@ Leia as nossas [diretrizes de contribuição](https://github.com/Minimum-CD/cd-m
## Signatários
-Os signatários assinaram a [versão original em inglês](../../minimumcd/#signatories) e a lista atual de nomes é publicada apenas nessa versão.
+Os signatários assinaram a [versão original em inglês](/minimumcd/#signatories) e a lista atual de nomes é publicada apenas nessa versão.
## Tradução
diff --git a/content/Translations/Portuguese/_index.md b/content/Translations/Portuguese/_index.md
index 05fc880..958c265 100644
--- a/content/Translations/Portuguese/_index.md
+++ b/content/Translations/Portuguese/_index.md
@@ -2,22 +2,23 @@
title: "Português"
description: "Mínimo viável para a Entrega Contínua"
weight: 3
+type: docs
---
## Mínimo viável para a Entrega Contínua
-{{% notice %}}
+{{% alert %}}
"A entrega contínua não só melhora a qualidade e capacidade de entrega, bem como ajuda na evolução da cultura, reduz o cansaço e as dores do desenvolvimento/release."
-- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (Tradução não oficial)
-{{% /notice %}}
+{{% /alert %}}
-![MinimumCD](/images/minimumCD-logo-hex.png?height=150px)
+{{< figure src="/images/minimumCD-logo-hex.png" alt="MinimumCD" width="20%" >}}
-Nós, [os abaixo-assinados](../../minimumcd/#signatories), acreditamos que é necessária uma definição mínima de entrega contínua (_Continuous Delivery_, CD) para a melhoria do fluxo de entrega e cumprimento dos resultados supracitados. Embora os nossos contextos possam ser diferentes, existem práticas universais consideradas comuns. Ao defini-las, é possível:
+Nós, [os abaixo-assinados](/minimumcd/#signatories), acreditamos que é necessária uma definição mínima de entrega contínua (_Continuous Delivery_, CD) para a melhoria do fluxo de entrega e cumprimento dos resultados supracitados. Embora os nossos contextos possam ser diferentes, existem práticas universais consideradas comuns. Ao defini-las, é possível:
- Introduzi-las aos novos praticantes, de forma consistente
- Discutir as práticas de engenharia que abrangem a entrega contínua
@@ -37,13 +38,13 @@ As atividades mínimas exigidas para o CD são:
- Uso de [Integração contínua](#integração-contínua)
- A [_pipeline_ aplicational](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract) é a única forma possível de fazer _deploy_ para qualquer ambiente
-- A _pipeline_ decide a possibilidade dessas mudanças serem replicadas para o ambiente produtivo. Esse veredicto é [definitivo](../../faq/#why-should-the-pipeline-be-definitive-for-deploy)
-- Os artefactos criados pela _pipeline_ respeitam sempre a [definição de _deployable_](../../faq/#what-do-we-mean-by-definition-of-deployable) da organização
-- [Artefacto imutável](../../minimumcd/immutable/) (não existem mudanças manuais após o _commit_)
+- A _pipeline_ decide a possibilidade dessas mudanças serem replicadas para o ambiente produtivo. Esse veredicto é [definitivo](/faq/#why-should-the-pipeline-be-definitive-for-deploy)
+- Os artefactos criados pela _pipeline_ respeitam sempre a [definição de _deployable_](/faq/#what-do-we-mean-by-definition-of-deployable) da organização
+- [Artefacto imutável](/minimumcd/immutable/) (não existem mudanças manuais após o _commit_)
- Todo o desenvolvimento de funcionalidades é suspenso quando a _pipeline_ se encontra em falha (em vermelho)
- Ambientes de teste semelhantes ao ambiente produtivo
- _Rollback_ conforme necessário
-- A [configuração da aplicação](../../faq/#what-is-application-configuration) é _deployed_ com o artefacto
+- A [configuração da aplicação](/faq/#what-is-application-configuration) é _deployed_ com o artefacto
## Integração Contínua
@@ -60,7 +61,7 @@ As atividades mínimas necessárias ao CI são:
## Trunk-Based Development
-O [_Trunk-based development_](../../minimumcd/tbd/) (versão inglesa) (TBD) é um padrão de _branching_ essencial para cumprimento dos requisitos de CI. Impede a perda de trabalho, o risco de mudanças corrompidas devido à resolução de conflitos do _merge_ e também reduz o desperdício de movimento que aumenta o tamanho do _batch_ de mudanças.
+O [_Trunk-based development_](/minimumcd/tbd/) (versão inglesa) (TBD) é um padrão de _branching_ essencial para cumprimento dos requisitos de CI. Impede a perda de trabalho, o risco de mudanças corrompidas devido à resolução de conflitos do _merge_ e também reduz o desperdício de movimento que aumenta o tamanho do _batch_ de mudanças.
Os atividades mínimas essenciais para o TBD são:
@@ -72,11 +73,11 @@ Os atividades mínimas essenciais para o TBD são:
## Por que construímos este manifesto?
-Para obter informações acerca do Mínimo CD e respostas a outras questões comuns, por favor [lê as FAQ](../../faq/) (versão inglesa).
+Para obter informações acerca do Mínimo CD e respostas a outras questões comuns, por favor [lê as FAQ](/faq/) (versão inglesa).
## Começando a jornada
-Dúvidas sobre como começar? Confira algumas [recomendações](../../journey/) (versão inglesa).
+Dúvidas sobre como começar? Confira algumas [recomendações](/journey/) (versão inglesa).
## Contribuindo
@@ -86,7 +87,7 @@ Lê as nossas [diretrizes de contribuição](https://github.com/Minimum-CD/cd-ma
## Signatários
-Os signatários assinaram a [versão original em inglês](../../minimumcd/#signatories) e a lista atual de nomes é publicada apenas nessa versão.
+Os signatários assinaram a [versão original em inglês](/minimumcd/#signatories) e a lista atual de nomes é publicada apenas nessa versão.
## Tradução
diff --git a/content/Translations/Sinhala/_index.md b/content/Translations/Sinhala/_index.md
index fd7368f..9615072 100644
--- a/content/Translations/Sinhala/_index.md
+++ b/content/Translations/Sinhala/_index.md
@@ -2,20 +2,21 @@
title: Sinhala
description: "අඛණ්ඩ බෙදාහැරීමට හැකි මෘදුකාංග නිපදවීමට අවමයෙන් කලයුතු සහ කලහැකිදේ"
weight: 3
+type: docs
---
## අඛණ්ඩ බෙදාහැරීමට හැකි මෘදුකාංග නිපදවීමට අවමයෙන් කලයුතු සහ කලහැකිදේ
-{{% notice %}}
+{{% alert %}}
"අඛණ්ඩ බෙදාහැරීමට හැකි මෘදුකාංග නිපදවීමේ ක්රියාවලිය මගින් මෘදුකාංග බෙදාහැරීමේ කාර්ය සාධනය සහ ගුණාත්මකභාවය යන දෙකම වැඩිදියුණු කරන අතර, එම නිපදවන පරිසරයේ අභිවර්ධනයක්ද ඇතිකරයි. තවද මේ බෙදාහැරීමේ කටයුතු සීග්ර වීමත් සමග එම කාර්ය කරන්නන් ධනාත්මක මානසිකත්වයෙන් පසුවේ."
-- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (නිල නොවන පරිවර්තනය)
-{{% /notice %}}
+{{% /alert %}}
-![MinimumCD](/images/minimumCD-logo-hex.png?height=150px)
+{{< figure src="/images/minimumCD-logo-hex.png" alt="MinimumCD" width="20%" >}}
අපි, [පහළින් අත්සන් කර ඇත්තන්](#signatories), අඛණ්ඩව බෙදාහැරීමට හැකි මෘදුකාංග නිපදවීමේ ප්රවාහය (CD) වැඩිදියුණු කිරීමට සහ ඉහත ප්රතිඵල සාක්ෂාත් කර ගැනීමට අවම අර්ථ දැක්වීමක් අවශ්ය බව අපි විශ්වාස කරමු.
@@ -38,14 +39,14 @@ CD සඳහා අවශ්ය අවම ක්රියාකාරක
- [Continuous Integration](#continuous-integration)භාවිතා කලයුතුවේ
- එම [මෘදුකාංග යෙදුම් මාර්ගය pipeline](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract)
මෘදුකාංග බෙදාහැරීමේ එකම මාර්ගය වේ
-- එම යෙදුම් මාර්ගය (pipeline) වෙනස්කම්වල මුදා හැරීම තීරණය කරයි, එහි තීන්දුව [නිශ්චිත තීන්දුවවේ](../../faq/#why-should-the-pipeline-be-definitive-for-deploy)
+- එම යෙදුම් මාර්ගය (pipeline) වෙනස්කම්වල මුදා හැරීම තීරණය කරයි, එහි තීන්දුව [නිශ්චිත තීන්දුවවේ](/faq/#why-should-the-pipeline-be-definitive-for-deploy)
-- එම මාර්ගයෙන් නිර්මාණය කරන ලද වස්තුන් සෑම විටම ආයතනයේ [බෙදාහැරිය හැකි අර්ථ දැක්වීම සපුරාලයි](../../faq/#what-do-we-mean-by-definition-of-deployable)
-- [විචල්ය නොවන වස්තුන්](../../minimumcd/immutable/) (සැකසීමෙන් පසු කිසි පුද්ගලයෙකුට මේ වස්තුන් වෙනස් කල නොහැක)
+- එම මාර්ගයෙන් නිර්මාණය කරන ලද වස්තුන් සෑම විටම ආයතනයේ [බෙදාහැරිය හැකි අර්ථ දැක්වීම සපුරාලයි](/faq/#what-do-we-mean-by-definition-of-deployable)
+- [විචල්ය නොවන වස්තුන්](/minimumcd/immutable/) (සැකසීමෙන් පසු කිසි පුද්ගලයෙකුට මේ වස්තුන් වෙනස් කල නොහැක)
- මෘදුකාංග යෙදුම් මාර්ගය (pipeline) රතු වූ විට සියලුම සියලු වැඩ නතර වේ
- Production-වලට සමාන පරීක්ෂණ පරිසර
- සැණකින් ප්රකූර්ති තත්වයට පත්කල හැකි පරීක්ෂණ පරිසර
-- [යෙදුම් වින්යාසය](../../faq/#What-is-application-configuration)වස්තුන් සමඟ එකට බෙදාහැරේ
+- [යෙදුම් වින්යාසය](/faq/#What-is-application-configuration)වස්තුන් සමඟ එකට බෙදාහැරේ
## Continuous Integration
@@ -62,7 +63,7 @@ CI සඳහා අවශ්ය අවම ක්රියාකාරක
## Trunk Based Development
-[Trunk-based සංවර්ධනය](../../minimumcd/tbd) යනු නිර්වචනය වන්නේ මූලාශ්ර පාලනයට අවශ්ය එක අත්තක් විතරක් බාවිතාකරන රටාවයි, වෙනත් විදියකට CI ක්රියාවලිය කල නොහැක. මෙම විදිය code ඒකාබද්ධ වීමේදී සිදුවෙන දුෂිතවීම් වලක්වයි
+[Trunk-based සංවර්ධනය](/minimumcd/tbd) යනු නිර්වචනය වන්නේ මූලාශ්ර පාලනයට අවශ්ය එක අත්තක් විතරක් බාවිතාකරන රටාවයි, වෙනත් විදියකට CI ක්රියාවලිය කල නොහැක. මෙම විදිය code ඒකාබද්ධ වීමේදී සිදුවෙන දුෂිතවීම් වලක්වයි
TBD සඳහා අවශ්ය අවම ක්රියාකාරකම් වන්නේ:
@@ -74,11 +75,11 @@ TBD සඳහා අවශ්ය අවම ක්රියාකාරක
## ඇයි අපි මේක හැදුවේ?
-අවම CD පසුබිම සහ අනෙකුත් පොදු ප්රශ්නවලට පිළිතුරු සඳහා, කරුණාකර [නිති අසන ප්රශ්න කියවන්න](../../faq).
+අවම CD පසුබිම සහ අනෙකුත් පොදු ප්රශ්නවලට පිළිතුරු සඳහා, කරුණාකර [නිති අසන ප්රශ්න කියවන්න](/faq).
## ගමන ආරම්භ කිරීම
-ආරම්භ කළ යුත්තේ කොතැනින්ද යන්න පිළිබඳ ප්රශ්න? සමහර [නිර්දේශ](../../journey/). බලන්න.
+ආරම්භ කළ යුත්තේ කොතැනින්ද යන්න පිළිබඳ ප්රශ්න? සමහර [නිර්දේශ](/journey/). බලන්න.
## දායක වීම
diff --git a/content/Translations/Spanish/_index.md b/content/Translations/Spanish/_index.md
index 70d6da3..858663e 100644
--- a/content/Translations/Spanish/_index.md
+++ b/content/Translations/Spanish/_index.md
@@ -2,17 +2,18 @@
title: Español
description: "Entrega Continua Mínima Viable"
weight: 3
+type: docs
---
## Entrega Continua Mínima Viable
-{{% notice %}}
+{{% alert %}}
"La entrega continua mejora tanto el rendimiento como la calidad de la entrega, y también ayuda a mejorar la cultura y a reducir el agotamiento y el dolor del despliegue."
-- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (Traducción no oficial)
-{{% /notice %}}
+{{% /alert %}}
-Nosotros, [los abajo firmantes](../../minimumcd/#signatories), creemos que se requiere una definición mínima de entrega continua (CD por sus siglas en inglés) para mejorar el flujo de entrega y lograr los resultados anteriores. Si bien nuestros contextos pueden ser diferentes, existen prácticas universales. Al definirlos podemos:
+Nosotros, [los abajo firmantes](/minimumcd/#signatories), creemos que se requiere una definición mínima de entrega continua (CD por sus siglas en inglés) para mejorar el flujo de entrega y lograr los resultados anteriores. Si bien nuestros contextos pueden ser diferentes, existen prácticas universales. Al definirlos podemos:
- Introducir a los nuevos profesionales de forma coherente
- Discutir las prácticas de ingeniería que abarca CD
@@ -32,13 +33,13 @@ Las actividades mínimas requeridas para CD son:
- [Integración continua](#integración-continua).
- El [pipeline de la aplicación](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract) es el único camino para desplegar en producción.
-- El pipeline decide la posibilidad de entrega de los cambios, el veredicto es [definitivo](../../faq/#why-should-the-pipeline-be-definitive-for-deploy).
-- Los artefactos creados por el pipeline siempre cumplen los requisitos de [definición de desplegable](../../faq/#what-do-we-mean-by-definition-of-deployable) de la organización.
-- [Artefacto inalterable](../../minimumcd/immutable/). No hay cambios hechos por personas después de la confirmación.
+- El pipeline decide la posibilidad de entrega de los cambios, el veredicto es [definitivo](/faq/#why-should-the-pipeline-be-definitive-for-deploy).
+- Los artefactos creados por el pipeline siempre cumplen los requisitos de [definición de desplegable](/faq/#what-do-we-mean-by-definition-of-deployable) de la organización.
+- [Artefacto inalterable](/minimumcd/immutable/). No hay cambios hechos por personas después de la confirmación.
- Todo el trabajo de funcionalidades se detiene cuando el pipeline está en rojo
- Entorno de prueba similar a producción
- Revertir bajo demanda.
-- La [configuración de la aplicación](../../faq/#what-is-application-configuration) se despliega con el artefacto.
+- La [configuración de la aplicación](/faq/#what-is-application-configuration) se despliega con el artefacto.
## Integración Continua
@@ -46,7 +47,7 @@ Integración continua (CI por sus siglas en inglés) es la actividad de integrar
Las actividades mínimas requeridas para CI son:
-- [Desarrollo basado en rama principal](../../minimumcd/tbd/)
+- [Desarrollo basado en rama principal](/minimumcd/tbd/)
- El trabajo se integra a la rama principal como mínimo cada día
- El trabajo tiene pruebas automatizadas antes de fusionarse con la rama principal
- El trabajo se prueba con otro trabajo automáticamente al fusionarse
@@ -55,7 +56,7 @@ Las actividades mínimas requeridas para CI son:
## Desarrollo Basado en Rama Principal
-[Desarrollo Basado en Rama Principal](../../minimumcd/tbd/) (TBD por sus siglas en inglés) es el patrón de ramificación requerido para cumplir con la definición de CI. Previene el trabajo perdido, el riesgo de corrupción que proviene de la resolución de conflictos fusionados, y también reduce el desperdicio de movimiento que incrementan el volumen de cambios.
+[Desarrollo Basado en Rama Principal](/minimumcd/tbd/) (TBD por sus siglas en inglés) es el patrón de ramificación requerido para cumplir con la definición de CI. Previene el trabajo perdido, el riesgo de corrupción que proviene de la resolución de conflictos fusionados, y también reduce el desperdicio de movimiento que incrementan el volumen de cambios.
- Las actividades mínimas requeridas para TBD son:
- Todos los cambios se integran en la rama principal
@@ -66,7 +67,7 @@ Las actividades mínimas requeridas para CI son:
## ¿Por qué construimos esto?
-Para obtener más información sobre el CD mínimo y respuestas a otras preguntas comunes, por favor [lea las preguntas más frecuentes](../../faq/).
+Para obtener más información sobre el CD mínimo y respuestas a otras preguntas comunes, por favor [lea las preguntas más frecuentes](/faq/).
## ¿Quieres contribuir?
@@ -74,7 +75,7 @@ Lee nuestra [pauta de contribución](https://github.com/Minimum-CD/cd-manifesto/
## Firmantes
-Los firmantes avalan la [versión original en inglés](../../minimumcd/#signatories) y la lista actual de nombres solo se publica con esa versión.
+Los firmantes avalan la [versión original en inglés](/minimumcd/#signatories) y la lista actual de nombres solo se publica con esa versión.
## Traducción
diff --git a/content/Translations/Texan/_index.md b/content/Translations/Texan/_index.md
index 154ad98..d257dff 100644
--- a/content/Translations/Texan/_index.md
+++ b/content/Translations/Texan/_index.md
@@ -2,16 +2,17 @@
title: Texan
description: "The bare minimum for makin' work suck less"
weight: 3
+type: docs
---
-{{% notice %}}
+{{% alert %}}
"Continuous delivery improves both delivery performance and quality, and also helps improve culture and reduce burnout and deployment pain."
-- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
-{{% /notice %}}
+{{% /alert %}}
-![MinimumCD](/images/minimumCD-logo-hex.png?height=150px)
+{{< figure src="/images/minimumCD-logo-hex.png" alt="MinimumCD" width="20%" >}}
We, [the undersigned](#signatories), reckon that parin' down continuous delivery (CD) to its core is required if we
wanna improve the flow of delivery and achieve the outcomes above. While our contexts may vary, there are universal
@@ -38,13 +39,13 @@ The minimum activities required for CD are:
- The [application
pipeline](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract)
is the only way to deploy to any environment
-- The pipeline decides the releasability of changes. [Whatever it says, goes](../../faq/#why-should-the-pipeline-be-definitive-for-deploy)
-- Artifacts created by the pipeline always meet the organization's [definition of deployable](../../faq/#what-do-we-mean-by-definition-of-deployable)
-- [Immutable artifact](../../minimumcd/immutable/) (no human changes after commit)
+- The pipeline decides the releasability of changes. [Whatever it says, goes](/faq/#why-should-the-pipeline-be-definitive-for-deploy)
+- Artifacts created by the pipeline always meet the organization's [definition of deployable](/faq/#what-do-we-mean-by-definition-of-deployable)
+- [Immutable artifact](/minimumcd/immutable/) (no human changes after commit)
- All feature work stops when the pipeline is red
- Production-like test environment
- Rollback on-demand
-- [Application configuration](../../faq/#what-is-application-configuration) deploys with artifact
+- [Application configuration](/faq/#what-is-application-configuration) deploys with artifact
## Continuous Integration
@@ -62,7 +63,7 @@ The bare minimums for CI are:
## Trunk-based Development
-[Trunk-based development](../../minimumcd/tbd/) is the branchin' pattern we need to meet the definition
+[Trunk-based development](/minimumcd/tbd/) is the branchin' pattern we need to meet the definition
of CI. It prevents lost work, the risk of corruption that comes from conflictin' changes, and reduces back-and-forth
commiseratin' that makes changes bigger.
@@ -76,11 +77,11 @@ The minimum activities required for TBD are:
## Why'd we build this?
-We wrote that down along with some other stuff to [help y'all out](../../faq/).
+We wrote that down along with some other stuff to [help y'all out](/faq/).
## Headin' Down the Trail
-Wanna know where to start? Check out some [ideas](../../journey/) that've worked for us.
+Wanna know where to start? Check out some [ideas](/journey/) that've worked for us.
## Contributin'
diff --git a/content/Translations/_index.md b/content/Translations/_index.md
index c47f5f1..9e5f09c 100644
--- a/content/Translations/_index.md
+++ b/content/Translations/_index.md
@@ -1,7 +1,8 @@
---
title: Translations
-description: ""
-weight: 10
+linkTitle: "Translations"
+type: docs
+menu:
+ main:
+ weight: 20
---
-
-{{% children style="h2" depth="1" description="true" /%}}
diff --git a/content/_layout/footer/_index.md b/content/_layout/footer/_index.md
deleted file mode 100644
index 8de07f5..0000000
--- a/content/_layout/footer/_index.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-description: Footer
-title: Footer
----
-
-
-
Licensed MIT
-
diff --git a/favicon.png b/favicon.png
new file mode 100644
index 0000000..873df98
Binary files /dev/null and b/favicon.png differ
diff --git a/go.mod b/go.mod
new file mode 100644
index 0000000..6ddbf4a
--- /dev/null
+++ b/go.mod
@@ -0,0 +1,9 @@
+module cd-manifesto
+
+go 1.22.1
+
+require (
+ github.com/FortAwesome/Font-Awesome v0.0.0-20240108205627-a1232e345536 // indirect
+ github.com/google/docsy v0.9.1 // indirect
+ github.com/twbs/bootstrap v5.3.3+incompatible // indirect
+)
diff --git a/go.sum b/go.sum
new file mode 100644
index 0000000..c9a1516
--- /dev/null
+++ b/go.sum
@@ -0,0 +1,7 @@
+github.com/FortAwesome/Font-Awesome v0.0.0-20240108205627-a1232e345536 h1:LFS9LpoSZYhxQ6clU0NIVbaGR08BlxAs4b+9W+7IGVQ=
+github.com/FortAwesome/Font-Awesome v0.0.0-20240108205627-a1232e345536/go.mod h1:IUgezN/MFpCDIlFezw3L8j83oeiIuYoj28Miwr/KUYo=
+github.com/google/docsy v0.9.1 h1:+jqges1YCd+yHeuZ1BUvD8V8mEGVtPxULg5j/vaJ984=
+github.com/google/docsy v0.9.1/go.mod h1:saOqKEUOn07Bc0orM/JdIF3VkOanHta9LU5Y53bwN2U=
+github.com/twbs/bootstrap v5.2.3+incompatible/go.mod h1:fZTSrkpSf0/HkL0IIJzvVspTt1r9zuf7XlZau8kpcY0=
+github.com/twbs/bootstrap v5.3.3+incompatible h1:goFoqinzdHfkeegpFP7pvhbd0g+A3O2hbU3XCjuNrEQ=
+github.com/twbs/bootstrap v5.3.3+incompatible/go.mod h1:fZTSrkpSf0/HkL0IIJzvVspTt1r9zuf7XlZau8kpcY0=
diff --git a/hugo.toml b/hugo.toml
index 28fef6a..589d752 100644
--- a/hugo.toml
+++ b/hugo.toml
@@ -1,81 +1,126 @@
-baseURL = 'https://minimumcd.org/'
-defaultContentLanguage = "en"
-languageCode = "en-US"
-title = 'MinimumCD.org'
+baseURL = 'https://minimumcd.org/'
+title = 'Minimum CD'
-theme = "docport"
+enableGitInfo = true
+enableRobotsTXT = true
-pygmentsCodeFences = true
-pygmentsStyle = "monokai"
+disableKinds = [
+ "taxonomy",
+ "term"
+]
-defaultContentLanguageInSubdir = false
-enableMissingTranslationPlaceholders = false
+# You can add your own taxonomies
+[taxonomies]
+ category = "categories"
+ tag = "tags"
-googleanalytics = "G-KVLFMQXEF1"
+# Configure how URLs look like per section.
+[permalinks]
+ blog = "/:section/:year/:month/:day/:slug/"
-disableKinds = [
- "RSS",
- "taxonomy"
-]
+# Image processing configuration.
+[imaging]
+ anchor = "Smart"
+ quality = 75
+ resampleFilter = "CatmullRom"
-# Keep this as is
+[markup]
+ [markup.goldmark]
+ [markup.goldmark.parser.attribute]
+ block = true
+[markup.goldmark.renderer]
+ unsafe = true
+[markup.highlight]
+ # See a complete list of available styles at https://xyproto.github.io/splash/docs/all.html
+ style = "tango"
+ # Uncomment if you want your chosen highlight style used for code blocks without a specified language
+ # guessSyntax = "true"
+
+ # Everything below this are Site Params
+
+# Comment out if you don't want the "print entire section" link enabled.
[outputs]
- home = [
+ section = [
"HTML",
- "JSON",
- "RSS"
+ "RSS",
+ "print"
]
-# Site params
[params]
- color_main = "#477bbf"
- color_second = "#b30000"
- disableNavChevron = false # set true to hide next/prev chevron, default is false
- disableSearch = false # default is false
- menushortcutsnewtab = false # set true to open shortcuts links to a new tab/window
- ordersectionsby = "weight" # ordersectionsby = "title"
+ # gcs_engine_id = "c68e6136e96d14a0f"
+ homePage = "/minimumcd"
+
+ github_branch = "master"
+ github_project_repo = "https://github.com/Minimum-CD/cd-manifesto"
+ github_repo = "https://github.com/Minimum-CD/cd-manifesto"
+
+ # Google Custom Search Engine ID. Remove or comment out to disable search.
+ # gcs_engine_id = "d72aa9b2712488cc3"
+
+ # Enable Lunr.js offline search
+ offlineSearch = true
+
+ prism_syntax_highlighting = true
+ pygmentsCodeFences = true
+ pygmentsStyle = "tango"
+ pygmentsUseClasses = false
+ pygmentsUseClassic = false
custom_js = [
"https://buttons.github.io/buttons.js"
]
- editURL = "https://github.com/Minimum-CD/cd-manifesto/blob/master/content/"
- enableGitInfo = true
- github_repo = 'Minimum-CD/cd-manifesto'
- logo = '/images/minimumCD-logo-hex.png'
-
-[mediaTypes]
- [mediaTypes."application/netlifyconfig"]
- suffixes = [
- "yml"
+
+ [params.taxonomy]
+ # set taxonomyCloud = [] to hide taxonomy clouds
+ taxonomyCloud = [
+ "categories",
+ "tags"
]
-[outputFormats]
- [outputFormats.netlifyyaml]
- isHTML = false
- isPlainText = true
- mediaType = "application/netlifyconfig"
- notAlternative = true
+ # If used, must have same length as taxonomyCloud
+ taxonomyCloudTitle = [
+ "Categories",
+ "Tag Cloud"
+ ]
-[markup.goldmark.renderer]
- unsafe = true
+ # set taxonomyPageHeader = [] to hide taxonomies on the page headers
+ taxonomyPageHeader = [
+ "categories",
+ "tags"
+ ]
-# Code highlight configuration
-[markup.highlight]
- codeFences = true
- guessSyntax = true
- hl_Lines = ""
- lineNoStart = 1
- lineNos = false
- lineNumbersInTable = true
- noClasses = true
- style = "monokai"
- tabWidth = 2
-
-[[menu.shortcuts]]
- identifier = "ds"
- name = "Github"
- url = "https://github.com/Minimum-CD/cd-manifesto"
- weight = 10
-
-[create-footer-md]
- other = "Licensed MIT"
+ [params.copyright]
+ authors = "MinimumCD Authors | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0) | "
+ from_year = 2020
+
+ [params.ui]
+ breadcrumb_disable = false
+ navbar_logo = '/icons/logo.svg'
+ navbar_translucent_over_cover_disable = false
+ show_nav_title = true
+ sidebar_cache_limit = 10
+ sidebar_menu_compact = true
+ sidebar_menu_foldable = true
+ sidebar_search_disable = false
+
+ [params.links]
+ [[params.links.developer]]
+ desc = "Contribute!"
+ icon = "fab fa-github"
+ name = "GitHub"
+ url = "https://github.com/Minimum-CD/cd-manifesto"
+
+ [params.ui.feedback]
+ enable = false
+
+ [params.ui.readingtime]
+ enable = false
+
+[services]
+ [services.googleAnalytics]
+ id = "G-KVLFMQXEF1"
+
+[module]
+ proxy = "direct"
+ [[module.imports]]
+ path = "github.com/google/docsy"
diff --git a/layouts/home.html b/layouts/home.html
new file mode 100644
index 0000000..e7514fb
--- /dev/null
+++ b/layouts/home.html
@@ -0,0 +1,17 @@
+{{ define "main" }}
+ {{ $site := . }} {{/* Save the global context */}}
+ {{ if not
+ .Site.Params.homePage
+ }}
+ {{ with .Content }}{{ . }}{{ end }}
+ {{ else }}
+ {{ with .Site.Params.homePage }}
+
+
+
+
+
+
+ {{ end }}
+ {{ end }}
+{{ end }}
diff --git a/layouts/partials/body-header.html b/layouts/partials/body-header.html
deleted file mode 100644
index 5a8e8fc..0000000
--- a/layouts/partials/body-header.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/_layout/sidebar-before/_index.md b/themes/docport/exampleSite/content/_layout/sidebar-before/_index.md
deleted file mode 100644
index c3223ae..0000000
--- a/themes/docport/exampleSite/content/_layout/sidebar-before/_index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-date: "2020-08-20T11:08:17.209Z"
-description: Sidebar before
-title: Sidebar before
----
-[//]: # (This a comment)
-
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/_index.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/_index.md
deleted file mode 100644
index 92cee4a..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/_index.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-creatordisplayname: Valere JEANTET
-creatoremail: valere.jeantet@gmail.com
-date: "2020-09-08T22:49:36.481Z"
-description: This page tells you how to use the theme to add and structure your site
- content.
-head: ""
-hidden: false
-lastmodifierdisplayname: Valere JEANTET
-lastmodifieremail: valere.jeantet@gmail.com
-layout: ""
-pre: ""
-tags:
-- tag1
-- tag2
-title: Adding content
-weight: 1
----
-{{% notice %}}This page tells you how to use the theme to add and structure your site content.{{% /notice %}}
-
-## Content root directory
-
-You add content for your site under the `content` root directory of your Hugo site project.
-The files in your content root directory are typically grouped in subdirectories corresponding to your site’s sections.
-
-We’ll look at in the following chapter.
-
-## Content sections
-
-With docport, **Each content page composes the site and navigation structure**, they shape the structure of your website.
-
-Create a folder for each section and their sub sections, and a `_index.md` in each folder which will act as the section's content.
-{{%notice%}}You can add any other page.md in section folder, they will be treated as "[subpages]({{< ref "#subpages" >}})"{{%/notice%}}
-
-To link pages to each other, place them in a folders hierarchy.
-
-```text
- content
- └── section-one/
- ├── _index.md
- └── section-one-two/
- ├── _index.md
- ├── section-one-two-three-A/
- │ ├── _index.md
- └── section-one-two-three-B/
- ├── _index.md <-- section's page
- ├── pageA.md <-- "subpages"
- └── pageB.md <-- "subpages"
-```
-
-## Subpages
-
-Subpages are contents which belong to the section, and are displayed bellow section's title in the page. \
-Subpages are not displayed in left menu.
-
-If you look at the current page title, you will see 3 links which reference its 3 subpages.
-![](subpages.png?height=60px&classes=border,shadow)
-
-## Page frontmatter
-
-Each page file in a Hugo site has metadata frontmatter that tells Hugo about the page. You specify page frontmatter in TOML, YAML, or JSON. \
-Use the frontmatter to specify the page title, description, creation date, link title, template, menu weighting, and even any resources such as images used by the page. You can see a complete list of possible page frontmatter in [Front Matter](https://gohugo.io/content-management/front-matter/).
-
-On top of the [existing ones](https://gohugo.io/content-management/front-matter/), DocPort comes with additional params to control what and how to display your content, their entry in left menu or behaviour.
-
-```yaml
----
-title: "Adding content"
-
-# order sections
-weight: 10
-
-# Hide some page components
-hide:
-- header
-- nav
-- breadcrumb
-- toc
-- nextpage
-- footer
-
-# subpage
-subpage: false # usefull when you want to force a sub section to be considered as a subpage
-
-# Redirect to another content
-# Set a full URL or a .md path
-# examples :
-# redirect = "https://github.com/vjeantet"
-# redirect = "folder"
-# redirect = "folder/_index.md"
-redirect: "folder/_index.md"
-
-# Do not include this page in search results
-nosearch: true
----
-```
-
-{{%alert success%}}More frontmatter params exists to control how to display you content in the navigation, see [Navigation & Search]({{%relref "02-navigation-search" %}}) in the left menu.{{%/alert%}}
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/myslide/index.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/myslide/index.md
deleted file mode 100644
index 08f1544..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/myslide/index.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-date: "2017-04-24T18:36:24+02:00"
-hidden: true
-revealOptions:
- center: true
- controls: true
- history: false
- progress: true
- transition: concave
-theme: league
-title: My Slide ! fullscreen
-type: slide
----
-
-# In the morning
-
-___
-
-## Getting up
-
-- Turn off alarm
-- Get out of bed
-
-___
-
-## Breakfast
-
-- Eat eggs
-- Drink coffee
-
----
-
-# In the evening
-
-___
-
-## Dinner
-
-- Eat spaghetti
-- Drink wine
-
-___
-
-## Going to sleep
-
-- Get in bed
-- Count sheep
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-images/_index.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-images/_index.md
deleted file mode 100644
index 0b6eacc..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-images/_index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-date: "2017-04-24T18:36:24+02:00"
-hidden: false
-subpage: true
-title: images
-weight: 10
----
-
-Images have a similar syntax to markdown links but include a preceding exclamation point.
-```
- ![myImage](image.jpeg)
-```
-![myImage](image.jpeg)
-
-## Resizing image
-
-Add HTTP parameters `width` and/or `height` to the link image to resize the image. Values are CSS values (default is `auto`).
-
-```
- ![myImage](image.jpeg?height=80px)
-```
-![myImage](image.jpeg?height=80px)
-
-
-## Add CSS classes
-
-Add a HTTP `classes` parameter to the link image to add CSS classes. `shadow` and `border` are available but you could define other ones.
-```
- ![myImage](image.jpeg?classes=border,shadow)
-```
-![myImage](image.jpeg?classes=border,shadow)
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-images/image.jpeg b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-images/image.jpeg
deleted file mode 100644
index 08f2e1d..0000000
Binary files a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-images/image.jpeg and /dev/null differ
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/_index.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/_index.md
deleted file mode 100644
index f8fd798..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/_index.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-hidden: true
-date: "2017-04-24T18:36:24+02:00"
-description: ""
-title: As a Skwad
-weight: 190
-post: " beta"
----
-
-A basic .md file can be rendered as a form/checklist/questionnaire.
-
-{{% notice %}}
-**A page rendered as a Skwad** is a page with a special rendered TOC, and a LOAD/DOWNLAOD form results buttons.
-\
-[{{%icon aspect_ratio%}} click here to view an example]({{%ref "ex-checklist/_index.md"%}})
-
-{{%/notice%}}
-
-To tell Hugo to consider a page as a skwad, just add `skwad` options in the frontmatter of your page.
-
-```yaml
----
-skwad:
- clientside: true # Display Load From File and Save To File buttons
- mode: form # set "form" for standard form submission or "api" to use Skwad API
- url: https://localhost:5555/ # Form Action URL (mode=form) or Skwad base API (mode=api)
- spaceName: appsec # spaceName for Api
----
-```
-
-## Dedicated shortcodes
-* c/text - a line or box input type
-* c/choices - a radiogroup or a checkboxgroup
-* c/list - a select or a multiselect
-* c/check - a checkbox
-* c/switch - a switch
-* c/show - display a part with a condition using user inputs
-* c/hidden - set a hidden value
-
-## Examples & Demos
-
-{{%children style="li" description="true" showhidden="true"%}}
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/__article-sidebar-after.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/__article-sidebar-after.md
deleted file mode 100644
index a8d29df..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/__article-sidebar-after.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
----
-
-
-
-{{%notice info%}}
-This checklist was made from the VSAQ Vendor Security Assessment Questionnaire, licensed with Apache License 2.0 -- More info here : https://github.com/google/vsaq
-{{%/notice %}}
-
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/_index.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/_index.md
deleted file mode 100644
index 411e59b..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/_index.md
+++ /dev/null
@@ -1,270 +0,0 @@
----
-description: Very long and Complex example, with file save/load on client side
-hidden: true
-hide:
-- nextpage
-- nav
-- breadcrumb
-
-title: WebApp Security Assessment
-weight: 99
-
-skwad:
- clientside: true
----
-
-{{%notice success%}}
-This is a demo of a [skwad page]({{%ref "content-and-customization/00-adding-content/page-skwad"%}})
-{{%/notice %}}
-
-## Application Metadata
-{{%include "webappsec/01_appmetadata.md"%}}
-
-
-## Vulnerability Reporting and Management
-{{%include "webappsec/02_vulnerabilityreporting.md"%}}
-
-
-## HTTPS and Mixed-Content Risks
-{{%include "webappsec/03_https.md"%}}
-
-
-## Authentication and Authorization
-{{%include "webappsec/04_authz.md"%}}
-
-
-## Common Web Vulnerabilities
-{{%include "webappsec/05_commonvuln.md"%}}
-
-
-## Testing, QA, and Monitoring
-{{%include "webappsec/06_testing.md"%}}
-
-## Additional Notes
-Provide any additional information about the security of your application:
-{{}}
-
-## Security Contacts
-List the email addresses of people we should contact about any security issues in the application:
-{{}}
-
-## Feedback
-Congratulations! You've made it to the end of this questionnaire. If you can spare another minute, please let us know how we can improve it. Your feedback is highly appreciated.
-{{}}
-
----
-
-{{%notice info%}}
-**Licence Info :** this checklist was made from the VSAQ Vendor Security Assessment Questionnaire, licensed with Apache License 2.0 -- More info here : https://github.com/google/vsaq
-{{%/notice %}}
-
-{{}}
-## Show
-{{}}
-* (aa) Show a block.
-* (no) Another block
-* (foo) No Block
-* (two) Show the two blocks
-{{}}
-
-### show 1
-
-{{}}
-{{%notice%}}
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-{{%/notice%}}
-{{}}
-
-{{}}
-{{%alert%}}No Alert selected !{{%/alert%}}
-{{}}
-
-
-
-## text
-
-Quel est le code du projet ?
-
-
-
-{{}}
-**Simple**
-{{}}
-<--->
-**Multiple**
-{{}}
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua.
-{{}}
-{{}}
-
-## Choices
-
-Les enjeux de sécurité ont été identifiés par la SSI ?
-
-{{}}
-**Simple**
-
-{{}}
- * (yes) Yes, we have a published security email contact, or we provide another way for users to report security issues. Incoming reports are timely reviewed and triaged.
- * (no) No, we do not currently offer a way to report security vulnerabilities for priority handling
- * i don't know
-{{}}
-
-<--->
-
-**Multiple**
-
-
-{{}}
- * (yes) Yes, we have a published security email contact, or we provide another way for users to report security issues. Incoming reports are timely reviewed and triaged.
- * (no) No, we do not currently offer a way to report security vulnerabilities for priority handling
- * i don't know
-{{}}
-{{}}
-
-{{}}
-{{%alert danger%}}OK !{{%/alert%}}
-{{}}
-
-
-## List
-{{}}
-**Simple**
-{{}}
- * (czero) C0
- * (cun) C1
- * (cdeux) C2
-{{}}
-
-<--->
-
-**Multiple**
-{{}}
- * All
- * (czero) C0
- * (cun) C1
- * (cdeux) C2
-{{}}
-{{}}
-
-## Checkbox
-
-{{%c/check mycheck %}}J'ai tout compris 1{{%/c/check %}}
-
-## switch
-
-{{%c/switch myswitch %}}Activer le truc{{%/c/switch %}}
-
-
-
-
-
-
-## Code
-{{%expand%}}
-Change on any element form
-```js
- var form = document.querySelector('form');
- form.addEventListener('change', function(e,v) {
- console.log("element changed", e.target,v)
- });
-
-````
-
-Get all data
-```js
- $("form[name=myform]").serializeArray()
-```
-
-Download file :
-* date
-* ref
-* url
-* data
-* hash or signature
-```js
-function downloadFile() {
- var obj = {a: 123, b: "4 5 6"};
- var filename = "download.json";
- var blob = new Blob([JSON.stringify(obj)], {type: 'text/plain'});
- if (window.navigator && window.navigator.msSaveOrOpenBlob) {
- window.navigator.msSaveOrOpenBlob(blob, filename);
- } else{
- var e = document.createEvent('MouseEvents'),
- a = document.createElement('a');
- a.download = filename;
- a.href = window.URL.createObjectURL(blob);
- a.dataset.downloadurl = ['text/plain', a.download, a.href].join(':');
- e.initEvent('click', true, false, window, 0, 0, 0, 0, 0, false, false, false, false, 0, null);
- a.dispatchEvent(e);
- }
-}
-````
-
-load file 1 :
-```js
-input.addEventListener('change', () => {
- let files = input.files;
-
- if (files.length == 0) return;
-
- /* If any further modifications have to be made on the
- Extracted text. The text can be accessed using the
- file variable. But since this is const, it is a read
- only variable, hence immutable. To make any changes,
- changing const to var, here and In the reader.onload
- function would be advisible */
- const file = files[0];
-
- let reader = new FileReader();
-
- reader.onload = (e) => {
- const file = e.target.result;
-
- // This is a regular expression to identify carriage
- // Returns and line breaks
- const lines = file.split(/\r\n|\n/);
- textarea.value = lines.join('\n');
-
- };
-
- reader.onerror = (e) => alert(e.target.error.name);
-
- reader.readAsText(file);
-});
-````
-
-load file 2 :
-```js
-function onFileLoad(elementId, event) {
- document.getElementById(elementId).innerText = event.target.result;
-}
-
-function onChooseFile(event, onLoadFileHandler) {
- if (typeof window.FileReader !== 'function')
- throw ("The file API isn't supported on this browser.");
- let input = event.target;
- if (!input)
- throw ("The browser does not properly implement the event object");
- if (!input.files)
- throw ("This browser does not support the `files` property of the file input.");
- if (!input.files[0])
- return undefined;
- let file = input.files[0];
- let fr = new FileReader();
- fr.onload = onLoadFileHandler;
- fr.readAsText(file);
-}
-```
-```html
-
-
-```
-{{%/expand%}}
-{{}}
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/confirm.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/confirm.md
deleted file mode 100644
index 12b9670..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/confirm.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-hide:
-- nextpage
-
-title: Thank You
-weight: 99
-hidden: true
-
----
-
-Thank You !
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/test.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/test.md
deleted file mode 100644
index 5014b1c..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/test.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-hide:
-- nextpage
-
-title: Test Form
-weight: 99
-
-checklist: true
----
-
-{{}}
-{{}}
-{{}}
-
-Name ?
-{{}}
-
-A brief description:
-{{}}
-Lorem placeholder
-{{}}
-
-
-
-**Do you ?**
-{{}}
- * (yes) Yes, we have a published security email contact, or we provide another way for users to report security issues. Incoming reports are timely reviewed and triaged.
- * (no) No, we do not currently offer a way to report security vulnerabilities for priority handling.
-{{}}
-
-
-{{}}
-* (SAML2) SAML 2.0
-* (OpenIDConnectOAuth2) OpenID Connect / OAuth2 Login
-* (OpenID2) OpenID 2.0
-* (LDAP) LDAP / Active Directory
-* (other) Other
-* (none) None of the above
-{{}}
-
-
-
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/01_appmetadata.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/01_appmetadata.md
deleted file mode 100644
index 5c21612..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/01_appmetadata.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-
-The name of the application: {{}}
-
-
-A brief description:
-{{}}
-Lorem placeholder
-{{}}
-
-
-What frameworks (if any) does this application require?
-{{}}
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/02_vulnerabilityreporting.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/02_vulnerabilityreporting.md
deleted file mode 100644
index ac6e5dc..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/02_vulnerabilityreporting.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-Because no system is entirely free of security issues, it's important to provide ways for external users to offer input and report vulnerabilities.
-
-**Do you have an easily discoverable way for external researchers to report security vulnerabilities in your systems?**
-{{}}
- * (yes) Yes, we have a published security email contact, or we provide another way for users to report security issues. Incoming reports are timely reviewed and triaged.
- * (no) No, we do not currently offer a way to report security vulnerabilities for priority handling.
-{{}}
-
-
-{{}}
-{{}}
-{{%notice warning%}}
-**Warning — possible medium-risk issue**\
-\
-Make it easy for others to let you know about security issues in your products. That way you'll learn about vulnerabilities earlier and can respond to them quickly. Also, without an easy way to report issues directly to you, external researchers might publish issues widely instead.
-\
-\
-If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:
-{{}}
-Lorem placeholder
-{{}}
-{{%/notice%}}
-{{}}
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/03_https.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/03_https.md
deleted file mode 100644
index 5a5cae5..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/03_https.md
+++ /dev/null
@@ -1,139 +0,0 @@
----
-hidden: true
-ignoresearch: true
-
----
-
-
-**Select the option that best describes your web application:**
-{{}}
-* (https) The web application is reachable exclusively over HTTPS. Even if the user manually edits the URL to start with `http://`, it won't work or it will redirect to `https://`.
-* (http_https) The web application is flexible — users can reach it over HTTP or over HTTPS.
-* (http_only) The web application supports HTTP only, and can't be reached over HTTPS even if you edit the URL.
-{{}}
-
-{{}}
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-It's often extremely easy for attackers to eavesdrop on packets transmitted between users and web applications (for example, on public Wi-Fi networks). To avoid exposing sensitive data in transit, any application that allows users to log in — or contains anything but public data — should be available solely over HTTPS. It's also fine to use a web server that listens on port 80 (plain HTTP) and redirects users to the SSL version; this method can make it easier for users to access the application.
-\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below.**
-{{}}
-
-{{%/notice%}}
-{{}}
-
-{{}}
-
-### Configuring SSL/TLS
-
-**Have you recently reviewed your SSL configuration to ensure that only secure protocols and ciphers are offered to clients?**
-
-{{}}
-* (yes) Yes, we regularly review the cipher suite advertised by the server and the protocols it uses.
-* (not_sure) We're not sure whether our SSL/TLS configuration is secure.
-{{}}
-
-{{}}
-{{%notice%}}
-**Tip**\
-\
-Detailed guidance on SSL/TLS and cipher suites is beyond the scope of this questionnaire. A very good and well-maintained resource is [Mozilla's SSL/TLS configuration wiki page](https://wiki.mozilla.org/Security/Server_Side_TLS), which gives up-to-date recommendations for the most common use cases. Another good resource for reviewing the security of your SSL/TLS server is [SSL Labs' server test](https://www.ssllabs.com/ssltest/).
-{{%/notice%}}
-{{}}
-
-
-**Does your server offer [forward secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) for clients that support it?**
-
-{{}}
-* (yes) Yes, the server supports ECDHE and DHE ciphers that offer forward secrecy.
-* (no) No, no ciphers providing forward secrecy are enabled.
-{{}}
-{{}}
-{{%notice%}}
-**Tip**\
-\
-In ciphers that support forward secrecy, an ephemeral key is negotiated for each connection, using the Diffie-Hellman algorithm. This key is used for a limited period of time, after which it is "forgotten." Even if the private SSL key is later compromised, an attacker who recorded conversations between the server and clients won't be able to decrypt those conversations without also breaking the associated ephemeral keys. Enabling ciphers that offer forward secrecy can protect your users against future disclosure of the information transmitted between them and your server.
-{{%/notice%}}
-{{}}
-
-
-**Are your SSL/TLS private keys appropriately protected on your web servers?**
-{{}}
-* (yes) Yes, we have taken all necessary steps to protect our private keys.
-* (no) I'm not sure how well protected they are.
-{{}}
-{{}}
-{{%notice%}}
-**Tip**\
-\
-Make sure private SSL/TLS keys are, at a minimum, protected through file system permissions. It's important to make sure the user account that's used to serve web pages does not have access; otherwise, a vulnerability in the web app could easily lead to a compromise of the keys. If you are using an SSL certificate with a wildcard CN (e.g., *.example.net), ensure that the private key is well protected on all the servers it resides on (not just your most important server).
-{{%/notice%}}
-{{}}
-
-
-**Where is the SSL connection between the user and your application terminated?**
-{{}}
-* (appserver) At the application server
-* (loadbalancer) At the load balancer
-* (somewhere) Somewhere else
-{{}}
-
-{{}}
-**Provide more details on the termination point:**
-{{}}
-{{}}
-
-
-{{}}
-**How is traffic between the load balancer and the application servers protected?**
-{{}}
-* (encrypted) Traffic is encrypted and certificates between load balancer and application servers are validated.
-* (unencrypted-trusted) Traffic is unencrypted, but all networks transited between load balancers and application servers are owned and exclusively used by us.
-* (unencrypted-untrusted) Traffic is unencrypted, and traffic has to transit through networks not owned and exclusively used by us.
-* (other) Through other means.
-{{}}
-{{}}
-
-{{}}
-{{%notice%}}
-**Tip**\
-\
-Because user traffic appears to transit networks behind your load balancer that are not fully owned and operated by you, we strongly recommend that you establish another SSL/TLS connection between the load balancer and the servers that actually serve the application. Otherwise, an attacker who can listen in on the traffic behind your load balancers will be able to see unencrypted user data.
-{{%/notice%}}
-{{}}
-
-{{}}
-**Describe how the traffic is protected:**
-{{}}
-{{}}
-
-
-
-**Applications served over SSL may still be vulnerable to attacks if resources (often JavaScript, style sheets, or other active content) are included over plain HTTP. This defeats the purpose of SSL, because the active content loaded through plain HTTP will have access to the DOM of content protected by SSL. Make sure no resources are included from plain HTTP sites. Typically, browsers will help identify cases where resources from non-SSL sites are included, by displaying [mixed content](https://developer.mozilla.org/en-US/docs/Security/MixedContent) warnings.**
-
-**To avoid these issues, do you have checks in place to ensure that all references to resources either point to SSL or are protocol-relative?**
-{{}}
-* (yes) Yes, we are very careful and have specific controls in place to prevent mixed-content issues.
-* (no) It wouldn't be too difficult for something to fall through the cracks and introduce mixed-content bugs.
-{{}}
-
-{{}}
-{{}}
-{{%notice warning%}}
-**Warning — possible medium-risk issue**\
-\
-Mixed content is a big deal, and it's becoming more problematic as an increasing number of users roam on public Wi-Fi and other insecure networks. We recommend cleaning up your codebase to avoid this kind of issue, and establishing procedures to help guard against new instances.
-\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below.**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-
-{{}}
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz.md
deleted file mode 100644
index 2a31fa5..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-
-**To get started, tell us a little about your application so we can ask you the right questions.**
-{{}}
-* (login_required) Our application requires regular users to log in. Most features aren't available without logging in.
-* (isolated_admin_ui) In addition to an interface for regular users, our application provides an administration interface.
-* (rbac_model) Our application features complex user management. Various roles can be assigned to user accounts.
-{{}}
-
-{{}}
-**Briefly describe the different roles your application provides. If your application also offers custom role definitions, be sure to mention that.**
-{{}}
-{{}}
-
-
-
-
-{{}}
-**Is your application integrated with any of the following single sign-on (SSO) mechanisms?**
-{{}}
-* (SAML2) SAML 2.0
-* (OpenIDConnectOAuth2) OpenID Connect / OAuth2 Login
-* (OpenID2) OpenID 2.0
-* (LDAP) LDAP / Active Directory
-* (other) Other
-* (none) None of the above
-{{}}
-
-{{}}
-**What other SSO mechanisms does the application support?**
-{{}}
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-OpenID 2.0 has been replaced by OpenID Connect (also called OAuth2 Login). We recommend updating your application's SSO integration to support OpenID Connect.
-{{%/notice%}}
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Integrating with LDAP and/or Active Directory has a significant downside: any application that integrates with it has to receive the user's SSO password. As a result, a vulnerability in any integrated application puts the password at risk for all other applications. We recommend using an SSO mechanism that does not require the password to be sent anywhere other than a central authentication system.
-{{%/notice%}}
-{{}}
-
-{{}}
-### OAuth2 Login
-{{%include 04_authz_OAuth2Login.md%}}
-{{}}
-
-
-
-
-
-**Does any part of the application employ username/password-based authentication?**
-{{}}
-* (yes) Yes
-* (no) No, all authentication is based on single sign-on (SSO).
-{{}}
-
-{{}}
-### Username/Password Authentication
-{{%include 04_authz_UsernamePasswordAuthentication.md%}}
-{{}}
-
-{{}}
-
-
-
-
-
-
-
-
-
-
-
-
-
-{{}}
-### Authentication Cookies and Sessions
-{{%include 04_authz_AuthenticationCookiesandSessions.md%}}
-{{}}
-
-
-
-
-{{}}
-### Authorization
-{{%include 04_authz_Authorization.md%}}
-{{}}
-
-
-
-
-
-
-{{}}
-### Authorization-Related Web Vulnerabilities
-{{%include 04_authz_AuthorizationRelatedWebVulnerabilities.md %}}
-{{}}
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_AuthenticationCookiesandSessions.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_AuthenticationCookiesandSessions.md
deleted file mode 100644
index 32abede..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_AuthenticationCookiesandSessions.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-**Cookies can be decorated with a special keyword, `HttpOnly`. If this keyword is set, the browser will not allow JavaScript to access the cookie. Even if the application has a cross-site scripting vulnerability, this keyword makes it much harder for an attacker to steal the session cookie.**
-
-{{}}
-* (handled) The `HttpOnly` keyword is set for all our authentication cookies.
-* (no) Our application does not make use of this defense-in-depth mechanism.
-{{}}
-
-{{}}
-{{%notice warning%}}
-**Warning — possible medium-risk issue**\
-\
-Setting the `HttpOnly` attribute is a very simple defense-in-depth mechanism. We highly recommended making use of it.
-\
-**If there are specific reasons why this is not possible in your case please explain below**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-**Session IDs can be constructed in many ways. Select the methods used in your application:**
-{{}}
-* (framework) The web application framework we use has a built-in session ID mechanism.
-* (randomalphanum) Our session IDs are randomly generated strings or numbers.
-* (signedcookie) We store a signed token as a cookie to indicate that the user is successfully logged in.
-* (other) We use some other mechanism.
-{{}}
-
-{{}}
-**Describe the mechanism you're using**
-{{}}
-{{}}
-
-{{}}
-**What's the name of the framework that generates your session IDs**
-{{}}
-{{}}
-
-{{}}
-**Do sessions automatically time out after a specified period of inactivity**
-{{}}
-* (yes) Yes
-* (no) No
-{{}}
-
-{{}}
-**How long is the session timeout?**
-{{}}
-{{}}
-
-{{}}
-
-{{}}
-{{%notice warning%}}
-**Warning — possible medium-risk issue**\
-\
-If you don't specify a session timeout, an attacker who has stolen a session ID once will have a permanent back door to the application. Be sure to implement a timeout — even if it's fairly long, it's still better than no timeout at all).
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-
-{{}}
-**Does the application use a secure [cryptographic pseudo random number generator](https://en.wikipedia.org/wiki/Pseudorandom_number_generator#Cryptographically_secure_pseudorandom_number_generators) (PRNG) to generate session IDs? The PRNG should not allow the state of the generator to be recalculated from its output, and the entropy of the session ID should be sufficient to make brute-forcing infeasible.**
-{{}}
-* (yes) Yes, we use a PRNG that meets these criteria
-* (no) No, we don't use a PRNG, or our PRNG doesn't meet these criteria.
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-If you're not using a cryptographic PRNG, an attacker can recalculate the state of the generator in order to guess subsequent session IDs and steal those users' sessions. Many programming languages already have a secure PRNG built in (e.g., Java has `java.security.SecureRandom`; C# has `System.Security.Cryptography.RNGCryptoServiceProvider`; Python has `os.urandom`), and in most cases it is as easy to use as a less secure option.\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
-{{}}
-
-
-**Does your application offer a "log out" button or link that, when clicked, not only terminates the session (deletes cookies from the client) but also invalidates the entire session ID?**
-{{}}
-* (yes) Yes
-* (no) No
-{{}}
-
-{{}}
-{{%notice warning%}}
-**Warning — possible medium-risk issue**\
-\
-Unless sessions are invalidated on logout, an attacker who has stolen a session ID will have access to the user's data until the session expires. Make sure all logout actions invalidate the session ID.\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_Authorization.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_Authorization.md
deleted file mode 100644
index 2563877..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_Authorization.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-In most applications, certain information should only be accessible to certain users. For example, in most applications that require authentication, only the currently logged-in user should be able to change master data (such as the username, the associated email address, or the account password). When an application has data that should not be available to other users or should be restricted to certain roles, authorization must be enforced on the server side.
-
-
-**Horizontal Access Control: Horizontal access control refers to isolation between users of the same role. For example, consider an application that allows users to access their payroll statements. The application must ensure that a user cannot access another user's statements; i.e., if the user's statement for the month of May is found at `statement.html?id=8372&month=5`, it shouldn't be possible to see someone else's pay stub simply by loading `statement.html?id=8373&month=5`.**
-{{}}
-* (handled) Our application enforces these restrictions on the server side. We have processes in place to make sure nothing slips through the cracks.
-* (no) It's possible that we missed checks like this in a few places.
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Applications must have controls in place that help protect all data from unauthorized access. We recommend that you thoroughly audit your code for vulnerabilities resulting from inadequate access control.\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-
-
-
-**Vertical Access Control: When an application supports multiple roles, users should not be able to gain privileges or perform unauthorized actions by loading pages or features that should only be available to users in a different role. Throughout your application, have you ensured that users can perform only those actions that are appropriate for their roles?**
-{{}}
-* (handled) Our application enforces these restrictions on the server side. We have processes in place to make sure nothing slips through the cracks.
-* (no) It's possible that we missed checks like this in a few places.
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Applications must have controls in place that protect all functionality from unauthorized access. We recommend that you thoroughly audit your code for vulnerabilities resulting from inadequate access control.\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_AuthorizationRelatedWebVulnerabilities.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_AuthorizationRelatedWebVulnerabilities.md
deleted file mode 100644
index b84d687..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_AuthorizationRelatedWebVulnerabilities.md
+++ /dev/null
@@ -1,124 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-#### Cross Site Request Forgery
-Applications must protect all state-changing actions against cross-site request forgery (XSRF). In this attack, a malicious user forces the victim to send a request to the application, for example by luring the user to a page under the attacker's control. Because the browser automatically attaches available authentication cookies, the request will appear to be authorized if the user is logged in to the application.
-
-For example, consider an online banking application that allows users to transfer money to another account. The URL for transfers might look something like this:
-
-`https://www.example.com/bank-transfer.html?dest_account=123456&amount=99.90&submit=true`
-
-If an attacker manages to lure the victim to a malicious site, the site could include HTML that causes such a request to be sent:
-
-``
-
-If the user is logged in to the online banking portal, the application will receive that request and check for authentication cookies — which will be present, since the request was sent from the authorized user's browser.
-
-**Does your application protect all state-changing actions against XSRF?**
-{{}}
-* (yes) Yes, all state-changing actions are protected. We have a way to ensure that no actions are missed (such as enforcing XSRF-token checks in a central place).
-* (no) Some actions might not be protected against XSRF.
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Web applications used to process private or confidential information should protect against XSRF. We recommend that you thoroughly audit your code for XSRF vulnerabilities, and put procedures in place so that future code is also protected.\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
-{{}}
-**What strategy do you use to protect against XSRF?**
-{{}}
-* (token) We protect requests that change the state with tokens that are bound to the user they were generated for, and that expire after a certain amount of time.
-* (header) We use a custom fixed header that we add to requests.
-* (post) The application does one of the following: verifies the referrer header; requires all state-changing actions to be POST requests; employs another mechanism to protect against XSRF
-{{}}
-{{}}
-
-{{}}
-{{%notice%}}
-**Tip**\
-\
-Various browser plugins (such as Flash and Java) have had security vulnerabilities that allowed an attacker to set arbitrary custom headers on cross-domain requests. We highly recommend the use of tokens instead of headers.
-{{%/notice%}}
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Unfortunately, using POST requests does not protect against XSRF. Attackers can perform cross-domain POST requests by submitting a form with the appropriate `action` parameter, via JavaScript. Referrer checks are similarly ineffective because attackers can get around them through open redirects.\
-\
-**If you are using an alternative, effective method to protect against XSRF, describe it:**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-
-
-
-
-
-
-#### Cross-Site Script Inclusion
-**Many web applications use AJAX to exchange data in the background, using a syntax that can be automatically interpreted as JavaScript by the user's browser. Unfortunately, this leads to [cross-site script inclusion](http://capec.mitre.org/data/definitions/111.html) (XSSI) vulnerabilities: the JavaScript can be included from a different origin, and any variables set at the other origin can be read.**
-
-For example, consider a contact management application that transmits the user's contacts in a JSON file (contacts.js):
-
-`var contacts = {"name": "John Doe", "address": "jdoe@example.com", ... }`
-
-An attacker can include the following script from their own site, so that when the user visits the attacker's site while logged in to the contact management application, the attacker can read the variable contacts and get access to all of the victim's contact information.
-
-``
-
-**Do either of the following statements describe your application?**
-{{}}
-* (jsonp) Our application makes use of [JSONP](http://en.wikipedia.org/wiki/JSONP).
-* (no) Our application uses another format that sets variables or calls functions with non-public information.
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Web applications that transmit private information must be protected against XSSI, to prevent attackers from stealing the private data.\
-\
-**If you are using an alternative, effective method to protect against XSSI, describe it:**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-
-
-
-
-#### Clickjacking
-**Depending on the nature of your application and the actions that can be taken in it, you may need to protect against [clickjacking](https://www.owasp.org/index.php/Clickjacking).**
-
-**If you don't typically need to frame web pages, your application should use the [X-Frame-Options response header](https://developer.mozilla.org/en/the_x-frame-options_response_header) to tell the browser not to render any page that's framed from a different origin:**
-
-`X-Frame-Options: SAMEORIGIN`
-
-{{}}
-* (handled) Our application employs protections against clickjacking (such as using the `X-Frame-Options` header).
-* (no) Our application does not have such protections.
-{{}}
-
-{{}}
-{{%notice%}}
-**Tip**\
-\
-Clickjacking is difficult to address. But in high-risk applications, clickjacking protection is essential.\
-\
-**Explain why you consider clickjacking protection unnecessary**
-{{}}
-{{%/notice%}}
-{{}}
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_OAuth2Login.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_OAuth2Login.md
deleted file mode 100644
index 2046e05..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_OAuth2Login.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-
-**Implementing OAuth2 Login / OpenID Connect from scratch is fairly complex and error-prone, and mistakes can result in security vulnerabilities. Select the option that best describes your implementation:**
-{{}}
-* (very_secure) Very secure: We're using a standard OAuth2 library, and we update it when security fixes are released.
-* (secure) Secure: We implemented OAuth2 on our own, but our employees are experts and we're convinced that it is implemented securely.
-* (own_impl) Not sure: We implemented OAuth2 on our own, and it seemed simple at the time. I'm not sure about the security of our implementation
-{{}}
-
-
-{{}}
-{{%notice%}}
-**Tip**\
-\
-If your employees really are OAuth2 experts, you're probably fine. But note that even standard libraries have had vulnerabilities due to the intricacies of the standard. Be sure to ask your penetration testing provider to take a look at the OAuth2 implementation.
-{{%/notice%}}
-{{}}
-
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Implementing OAuth2 on your own is extremely dangerous. Even the experts on the OAuth2 standards panel concluded that the only way to securely implement it is through a well-known and well-tested library. Some of these libraries are very easy to use (e.g., the [Google Identity Toolkit](https://developers.google.com/identity/toolkit/)), so replacing your custom implementation should be feasible.\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_UsernamePasswordAuthentication.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_UsernamePasswordAuthentication.md
deleted file mode 100644
index 4f0901e..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/04_authz_UsernamePasswordAuthentication.md
+++ /dev/null
@@ -1,143 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-**What username/password-based logins does the application use? For example, if there's a separate administrator authentication, mention that.**
-{{}}
-
-**Does your application allow users to change their passwords?**
-{{}}
-* (yes) Yes
-* (no) No
-{{}}
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Allowing users to change their passwords is important. A user might be recovering from a compromise, or might have accidentally typed the password elsewhere.
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-**Does the application enforce minimum password security requirements (e.g., a certain length, character classes, etc.)?**
-{{}}
-* (yes) Yes
-* (no) No
-{{}}
-{{}}
-{{%notice warning%}}
-**Warning — possible medium-risk issue**\
-\
-Please help protect users from themselves by enforcing certain minimum password requirements. It's up to you to determine the details of these requirements, but they should account for the sensitivity of the information and should conform to industry standards.
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-
-
-#### Password Storage
-**How does the application store passwords?**
-{{}}
-* (plaintext) In plain text (unencrypted)
-* (reversible) Using reversible encryption (e.g., DES, 3DES, AES, etc.).
-* (hashnosalted) Using a secure cryptographic one-way hash function (such as SHA-256) of the password, without the use of a salt
-* (hashsalted) Using a secure cryptographic one-way hash function (such as SHA-256) of the salted password
-* (keyderivationcypher) Using a dedicated password-based key derivation function, such as bcrypt, PBKDF2 or scrypt
-* (none) None of the above
-{{}}
-
-{{}}
-**Explain how your application stores passwords:**
-{{}}
-{{}}
-
-{{}}
-{{%alert danger%}}**Warning — possible critical-risk issue**{{%/alert%}}
-{{%notice danger%}}
-Passwords should be stored in such a way that the original passwords cannot be easily recovered, even if an attacker manages to get access to the storage location (e.g., through a SQL injection vulnerability). At a minimum, passwords should be secured using a cryptographic one-way hash function and a salt. We strongly recommended using password-based key derivation function like bcrypt PBKDF2 or scrypt instead; they were specifically designed for this use case and make it significantly harder for attackers to crack password hashes.\
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
-
-
-
-
-
-
-#### Setting an Initial Password
-**How do users get their initial passwords?**
-{{}}
-* (selfset) Users self-register and set their passwords online directly within the application.
-* (linktoset) The initial password or a link to set the initial password is sent to users by email.
-* (physical) The initial password is provided in a (physical) letter sent to a verified address.
-* (none) None of the above.
-{{}}
-
-{{}}
-**Explain how users get their initial passwords:**
-{{}}
-{{}}
-
-{{}}
-{{%notice%}}
-**Tip**\
-\
-If passwords are sent by email, make sure users are required to change their initial passwords when they first log in.
-{{%/notice%}}
-{{}}
-
-
-**When the user gets their initial password, will their account be prepopulated with any confidential information? For example, in an online payroll portal, a user can typically access previous pay statements even when the account is brand new.**
-{{}}
-* (yes) Yes, when users log in for the first time, confidential information will already be present.
-* (no) No, at the initial login, no confidential information will be available to the user.
-{{}}
-
-
-
-
-#### Account Recovery
-**When the user gets their initial password, will their account be prepopulated with any confidential information? For example, in an online payroll portal, a user can typically access previous pay statements even when the account is brand new.**
-{{}}
-* (questions) The user is asked questions that were set up when the account was created.
-* (resetlink) A password reset link is sent via email to the user's registered email address.
-* (newpassbymail) A new password is sent via email to the user's registered email address.
-* (none) None of the above.
-{{}}
-
-{{}}
-**Describe your password recovery mechanism:**
-{{}}
-{{}}
-
-{{}}
-{{%notice danger%}}
-**Warning — possible high-risk issue**\
-\
-Recovery questions alone should not be sufficient for resetting a password. The answers to these questions are often not as secret as they might seem; in particular, friends and family can often easily guess the answers.
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-\
-{{}}
-{{%/notice%}}
-{{}}
-
-{{}}
-{{%notice warning%}}
-**Warning — possible medium-risk issue**\
-\
-Sending passwords by email is rarely a good idea. Email is generally unencrypted, so it should not be used for sensitive information. Instead, we recommend sending a token that can be used to set the actual password. Although an attacker with the token could still reset the password, the user would at least become aware of the reset when they later attempted to log in.
-\
-**If you have compensating controls in place or feel that this issue does not constitute a risk in your specific circumstances, please explain below. If you're working to address this issue, include an estimate of when it will be resolved:**
-{{}}
-{{%/notice%}}
-{{}}
-
diff --git a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/05_commonvuln.md b/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/05_commonvuln.md
deleted file mode 100644
index d28f38d..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/00-adding-content/page-skwad/ex-checklist/webappsec/05_commonvuln.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-hidden: true
-ignoresearch: true
----
-
-**Certain features can result in security issues, if used incorrectly. To help us identify potential issues, select the statements that describe your application:**
-{{}}
-* (db) The application uses a database back end, or any other persistence back end that can be queried with SQL or a related language (e.g., GQL, FQL, SOQL, etc.).
-* (plugin) The application requires a plugin, such as Java, Flash, Silverlight, etc.
-* (upload) The application has a file upload feature.
-* (3rdpartycontent) The application loads active content, such as scripts, applets, or style sheets, from third-party servers (i.e., any server that is not under your direct control).
-* (xml) The application processes or manipulates user-provided XML.
-* (crypto) The application uses cryptography to encrypt data or protect its integrity.
-{{}}
-
-{{}}
-{{%notice warning%}}
-**Warning — possible medium-risk issue**\
-\
-Loading content from other sites is dangerous under certain circumstances; security issues in the other sites might also affect the security of your application. Scripts, for example, have full access to the DOM of the site on which they're included — so if one of the servers that hosts your third-party JavaScript gets compromised, the attacker also gains access to all of your users' data, simply by injecting a bit of code.\
-\
-Unless you trust the third party completely (not only to not do something malicious, but also to be secure enough to adequately protect their infrastructure against attackers), it's best not to load scripts or style sheets (e.g., via `
-```
-
-Then override the style your want to change in `static/css/custom.css` (in this case, to avoid altering the casing of titles):
-```css
-h2 {
- text-transform: none;
-}
-```
-
-And execute some additional JavaScript from `static/js/custom.js` (note that jQuery is already loaded by the theme):
-```javascript
-function tweakPage() {
- // make some changes here
-}
-
-$(tweakPage)
-```
-
-now feel free to add the JS, CSS code you want :)
-
-## Add custom HTML before and after key elements of this theme
-
-* @see [site placeholders]({{%relref "02-navigation-search"%}})
-
-## Overide existing CSS or JS
-
-Create the matching file in your static folder, hugo will use yours instead of the theme's one.
-
diff --git a/themes/docport/exampleSite/content/content-and-customization/03-look-and-feel/disable/_index.md b/themes/docport/exampleSite/content/content-and-customization/03-look-and-feel/disable/_index.md
deleted file mode 100644
index a46790a..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/03-look-and-feel/disable/_index.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-subpage: true
-title: Disable features
----
-
-You can disable feature in docport by changing some params in `config.toml`
-
-
-## Hide Next Page Chevrons
-
-![](chevrons.png?classes=border,shadow)
-
-```toml
- [params]
- disableNavChevron = true
-```
diff --git a/themes/docport/exampleSite/content/content-and-customization/03-look-and-feel/disable/chevrons.png b/themes/docport/exampleSite/content/content-and-customization/03-look-and-feel/disable/chevrons.png
deleted file mode 100644
index 2d8a08b..0000000
Binary files a/themes/docport/exampleSite/content/content-and-customization/03-look-and-feel/disable/chevrons.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/content-and-customization/04-shortcodes/_index.md b/themes/docport/exampleSite/content/content-and-customization/04-shortcodes/_index.md
deleted file mode 100644
index b56611e..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/04-shortcodes/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-description: Use DocPort Hugo shortcodes to quickly build site pages.
-redirect: shortcodes
-title: Shortcodes
-weight: 50
----
-
-
-
-
diff --git a/themes/docport/exampleSite/content/content-and-customization/_index.md b/themes/docport/exampleSite/content/content-and-customization/_index.md
deleted file mode 100644
index dfb5ec1..0000000
--- a/themes/docport/exampleSite/content/content-and-customization/_index.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-description: ""
-hide:
- - toc
-title: Content and Customization
-weight: 30
----
-
-{{%children style="h2" description="true" %}}
diff --git a/themes/docport/exampleSite/content/docport-theme/_index.md b/themes/docport/exampleSite/content/docport-theme/_index.md
deleted file mode 100644
index 95beee1..0000000
--- a/themes/docport/exampleSite/content/docport-theme/_index.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-date: "2020-09-08T22:11:57.883Z"
-description: first page
-title: DocPort Theme for Hugo
-weight: 1
----
-[DocPort](https://github.com/vjeantet/hugo-theme-docport), a professional documentation theme built for Hugo. \
-It provides a simple navigation, automatic search engine, a high level of configuration and a bunch of shortcodes crafted for documentation (attachment, presentations, child pages, notice, alerts, diagrams...).
-
-{{%notice%}}DocPort works with a "page tree structure" to organize content : All contents are pages, which belong to other pages. [read more about this]({{%relref "content-and-customization"%}}). {{%/notice%}}
-
-## Main features
-
-* [Search Engine]({{%relref "content-and-customization/02-navigation-search/search" %}})
-* **Unlimited menu levels**, [subpages]({{%relref "content-and-customization/00-adding-content/#subpages"%}})
-* [Placeholders]({{%relref "content-and-customization/02-navigation-search/" %}}) to inject HTML, CSS, JS in theme without modifying it.
-* Responsive, [Customizable look and feel, colors]({{%relref "content-and-customization/03-look-and-feel/colors/" %}})
-* [RevealJS presentation]({{%relref "content-and-customization/00-adding-content/page-slide/"%}}) from markdown (embededed or fullscreen page)
-* [Image resizing, shadow...]({{%relref "content-and-customization/00-adding-content/page-images/" %}})
-* A bunch of shortcodes
- * [Mermaid diagram]({{%relref "shortcodes/mermaid/_index.md" %}}) (flowchart, sequence, gantt)*
- [Attachments files]({{%relref "shortcodes/attachments/_index.md" %}}), [Icons]({{%relref "shortcodes/icon/_index.md" %}}), [Buttons]({{%relref "shortcodes/button/_index.md" %}}), [Alerts]({{%relref "shortcodes/alert/_index.md" %}}), [Panels]({{%relref "shortcodes/panel/_index.md" %}}), [Tip/Note/Info/Warning boxes]({{%relref "shortcodes/notice/_index.md" %}}), [Expand]({{%relref "shortcodes/expand/_index.md" %}}), [List child pages]({{%relref "shortcodes/children/_index.md" %}}), \
- [Badges]({{%relref "shortcodes/badge/_index.md" %}}) {{% badge success%}}new{{% /badge %}}
- * [Excerpt]({{%relref "shortcodes/excerpt/_index.md"%}}) ! Include segment of content from one page in another*
- [columns]({{%relref "shortcodes/columns/_index.md"%}}), [tabs]({{%relref "shortcodes/tabs/_index.md"%}})
-
-## Contribute to this documentation
-
-Use the "**improve this page**" button on the right side on each page to edit (in browser) and submit your change. (or git fork and pull request)\
-{{%alert%}}Your modification will be deployed automatically when merged in git repo!{{%/alert%}}
-
-## Documentation website
-
-This current documentation has been statically generated with Hugo with a simple command : `hugo -t docport` -- source code is [available here at GitHub](https://github.com/vjeantet/hugo-theme-docPort).
-
-## Static + content management
-
-I author this current documentation via Netlify CMS.\
-Docport theme seamless works with [Netlify CMS](https://www.netlifycms.org/)
-
-{{% badge %}}Help{{% /badge %}} Try the improve this page button on the right side of each page
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/docport-theme/credits/_index.md b/themes/docport/exampleSite/content/docport-theme/credits/_index.md
deleted file mode 100644
index df40038..0000000
--- a/themes/docport/exampleSite/content/docport-theme/credits/_index.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: Credits
-description: Contributors and packages used by hugo-theme-docport
-date: 2020-09-10T19:54:04.751Z
-hide:
- - toc
-subpage: true
----
-
-
-## Contributors
-
-
-
-
-
-## Packages and libraries
-* [jQuery](https://jquery.com) - The Write Less, Do More, JavaScript Library
-* [mermaid](https://knsv.github.io/mermaid) - generation of diagram and flowchart from text in a similar manner as markdown
-* [reveal-js](http://lab.hakim.se/reveal-js) - The HTML Presentation Framework
-* [lunr](https://lunrjs.com) - Lunr enables you to provide a great search experience without the need for external, server-side, search services...
-* [javaScript-autoComplete](https://github.com/Pixabay/JavaScript-autoComplete) - An extremely lightweight and powerful vanilla JavaScript completion suggester.
-* [font awesome](http://fontawesome.io/) - the iconic font and CSS framework
-
-
-## Tooling
-* [Hugo](https://gohugo.io/)
-* [Netlify CMS](https://www.netlifycms.org/)
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/examples/_index.md b/themes/docport/exampleSite/content/examples/_index.md
deleted file mode 100644
index 44c9d50..0000000
--- a/themes/docport/exampleSite/content/examples/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-hide:
- - toc
-title: Examples
-weight: 50
----
-
-some examples
-
-{{% children description="true" %}}
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/examples/page with raw content/_index.md b/themes/docport/exampleSite/content/examples/page with raw content/_index.md
deleted file mode 100644
index bc5b3ae..0000000
--- a/themes/docport/exampleSite/content/examples/page with raw content/_index.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-description: Nothing but your content ! usefull for special pages
-type: raw
-title: A page with raw content
-weight: 99
----
-
- COUCOU
-
-
-
-{{%panel header="page's frontmatter"%}}
-```yaml
----
-title: A page with raw content
-type: raw
----
-```
-{{%/panel%}}
-
-
-
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/examples/page without footer/_index.md b/themes/docport/exampleSite/content/examples/page without footer/_index.md
deleted file mode 100644
index 2bb7da3..0000000
--- a/themes/docport/exampleSite/content/examples/page without footer/_index.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-hide:
- - footer
-title: A page without footer
-weight: 20
----
-
-
-{{%panel header="page's frontmatter"%}}
-```yaml
----
-title: A page without footer
-hide:
- - footer
----
-```
-{{%/panel%}}
-
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/examples/page without header/_index.md b/themes/docport/exampleSite/content/examples/page without header/_index.md
deleted file mode 100644
index c385ba2..0000000
--- a/themes/docport/exampleSite/content/examples/page without header/_index.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-hide:
- - header
-title: A page without header
-weight: 10
----
-{{%panel header="page's frontmatter"%}}
-```yaml
----
-title: A page without header
-hide:
- - header
----
-```
-{{%/panel%}}
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/examples/page without next page/_index.md b/themes/docport/exampleSite/content/examples/page without next page/_index.md
deleted file mode 100644
index ce40035..0000000
--- a/themes/docport/exampleSite/content/examples/page without next page/_index.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-description: hide everything
-hide:
- - nextpage
-title: A page without "NEXT PAGE"
-weight: 80
----
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-{{%panel header="page's frontmatter"%}}
-```yaml
----
-title: A page without "NEXT PAGE"
-hide:
- - nextpage
----
-```
-{{%/panel%}}
-
-## Chapter 2
-
-[Click here to GOTO to the next example]({{%relref "page-without-any"%}})
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
diff --git a/themes/docport/exampleSite/content/examples/page without sidebar and toc/_index.md b/themes/docport/exampleSite/content/examples/page without sidebar and toc/_index.md
deleted file mode 100644
index 4cb638c..0000000
--- a/themes/docport/exampleSite/content/examples/page without sidebar and toc/_index.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-hide:
- - toc
- - nav
-title: A page without sidebar and toc
-weight: 20
----
-
-{{%panel header="page's frontmatter"%}}
-```yaml
----
-title: A page without sidebar and toc
-hide:
- - toc
- - nav
----
-
-```
-{{%/panel%}}
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-
-# A Responsive theme
-
-## Iphone 6/7/8
-![iphone-horizontal](iphone-horizontal.png?classes=border,shadow)
-![iphone-vertical](iphone-vertical.png?classes=border,shadow)
-
-## Tablet
-![ipad-vertical](ipad-vertical.png?classes=border,shadow)
-![ipad-horizontal](ipad-horizontal.png?classes=border,shadow)
-
-## Tablet like Ipad Pro
-![ipad-pro-vertical](ipad-pro-vertical.png?classes=border,shadow)
-![ipad-pro-horizontal](ipad-pro-horizontal.png?classes=border,shadow)
-
-## BigScreen
-![bigscreen](bigscreen.png?classes=border,shadow)
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/examples/page without sidebar and toc/bigscreen.png b/themes/docport/exampleSite/content/examples/page without sidebar and toc/bigscreen.png
deleted file mode 100644
index 6284e22..0000000
Binary files a/themes/docport/exampleSite/content/examples/page without sidebar and toc/bigscreen.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-horizontal.png b/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-horizontal.png
deleted file mode 100644
index ad0bbd0..0000000
Binary files a/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-horizontal.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-pro-horizontal.png b/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-pro-horizontal.png
deleted file mode 100644
index c0ee44f..0000000
Binary files a/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-pro-horizontal.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-pro-vertical.png b/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-pro-vertical.png
deleted file mode 100644
index 482f4a0..0000000
Binary files a/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-pro-vertical.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-vertical.png b/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-vertical.png
deleted file mode 100644
index c1563a6..0000000
Binary files a/themes/docport/exampleSite/content/examples/page without sidebar and toc/ipad-vertical.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/examples/page without sidebar and toc/iphone-horizontal.png b/themes/docport/exampleSite/content/examples/page without sidebar and toc/iphone-horizontal.png
deleted file mode 100644
index 098d037..0000000
Binary files a/themes/docport/exampleSite/content/examples/page without sidebar and toc/iphone-horizontal.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/examples/page without sidebar and toc/iphone-vertical.png b/themes/docport/exampleSite/content/examples/page without sidebar and toc/iphone-vertical.png
deleted file mode 100644
index f72517c..0000000
Binary files a/themes/docport/exampleSite/content/examples/page without sidebar and toc/iphone-vertical.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/examples/page without toc/_index.md b/themes/docport/exampleSite/content/examples/page without toc/_index.md
deleted file mode 100644
index 352cbaf..0000000
--- a/themes/docport/exampleSite/content/examples/page without toc/_index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-hide:
- - toc
-title: A page without table of contents
-weight: 20
----
-
-{{%panel header="page's frontmatter"%}}
-```yaml
----
-title: A page without table of contents
-hide:
- - toc
----
-
-```
-{{%/panel%}}
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/examples/page-without-any/_index.md b/themes/docport/exampleSite/content/examples/page-without-any/_index.md
deleted file mode 100644
index be59633..0000000
--- a/themes/docport/exampleSite/content/examples/page-without-any/_index.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-description: hide everything
-hide:
-- header
-- nav
-- breadcrumb
-- footer
-title: A page with only TOC and next page
-weight: 90
----
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-{{%panel header="page's frontmatter"%}}
-```yaml
----
-title: A page with only TOC and next page
-hide:
-- header
-- nav
-- breadcrumb
-- footer
----
-
-```
-{{%/panel%}}
-
-
-
-## Chapter 2
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-## Chapter 3
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-## Chapter 4
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-### Chapter 4.1
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-### Chapter 4.2
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-## Chapter 5
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/getting-start/_index.md b/themes/docport/exampleSite/content/getting-start/_index.md
deleted file mode 100644
index 9a3c6fb..0000000
--- a/themes/docport/exampleSite/content/getting-start/_index.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-alwaysopen: true
-date: "2020-08-20T16:42:11.812Z"
-description: Getting started
-head:
-hide:
-- toc
-post: " \U0001F44B"
-title: Getting started
-weight: 2
----
-
-## Requirements
-
-Download [Hugo binary](https://gohugo.io/overview/installing/) for your OS (Windows, Linux, Mac) : it’s that simple
-
-{{%children style="h2" description="true"%}}
diff --git a/themes/docport/exampleSite/content/getting-start/configuration/_index.md b/themes/docport/exampleSite/content/getting-start/configuration/_index.md
deleted file mode 100644
index c1ce77f..0000000
--- a/themes/docport/exampleSite/content/getting-start/configuration/_index.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-description: ""
-title: Configuration
-weight: 2
----
-
-
-There are a few configuration options that you can add to your `config.toml` file.
-
-{{%notice tip%}}
-**Tip**
-\
-Use the sample [config.toml](https://github.com/vjeantet/hugo-theme-docport/blob/master/exampleSite/config-template.toml) from docPort example site as a blueprint for your Hugo project:
-{{%/notice%}}
-
-## Use the docport theme
-When building the website, you can set a theme by passing the `--theme` argument on command line.
-We suggest you to edit your config.toml configuration file and set the theme by default.
-```
-theme = "docport"
-```
-
-## Create content and customize the theme
-
-Find out how to [create]({{%relref "create-page/_index.md"%}}) and [customize the theme to fit your needs]({{%relref "customization/_index.md"%}}) .
diff --git a/themes/docport/exampleSite/content/getting-start/installation/As-git-clone/_index.md b/themes/docport/exampleSite/content/getting-start/installation/As-git-clone/_index.md
deleted file mode 100644
index f61f74c..0000000
--- a/themes/docport/exampleSite/content/getting-start/installation/As-git-clone/_index.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-description: ""
-subpage: true
-title: with git clone
-weight: 1
----
-
-## Install DocPort with a git clone
-
-Navigate to your hugo root folder in your Hugo site and use perform one of following scenarios.
-
-This method results that files are checked out locally, but won't be visible from parent git repo. Probably you will build site locally with `hugo` command and use result from `public/` on your own.
-
-```
-$ git clone https://github.com/vjeantet/hugo-theme-docport.git themes/docport
-```
-
-## Configuration
-
-[Follow instructions here]({{%relref "getting-start/configuration/_index.md"%}})
diff --git a/themes/docport/exampleSite/content/getting-start/installation/_index.md b/themes/docport/exampleSite/content/getting-start/installation/_index.md
deleted file mode 100644
index ac84721..0000000
--- a/themes/docport/exampleSite/content/getting-start/installation/_index.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-description: ""
-title: Installation
-weight: 1
----
-
-{{% alert theme="warning" %}}HUGO **v0.50** minimum required to use this theme (prefer extended version if you want to modify this theme source{{%/alert%}}
-
-{{% alert theme="info" %}}Last version of HUGO is recomended, tests are always done with the last version.{{%/alert%}}
-
-The following steps are here to help you initialize your new website. If you don’t know Hugo at all, we strongly suggest you to train by following this [great documentation for beginners](https://gohugo.io/overview/quickstart/).
-
-
-
-
-We assume that all changes to Hugo content and customizations are going to be tracked by git (GitHub, Bitbucket etc.). Develop locally, build on remote system.
-
-## Prepare empty Hugo site
-
-Create empty directory, which will be root of your Hugo project. Navigate there and let Hugo to create minimal required directory structure:
-```
-$ hugo new site .
-```
-After that, initialize this as git directory where to track further changes
-```
-$ git init
-```
-
-## Install DocPort as git submodule
-
-{{%alert%}}
-**Alernatives to submodules**
-\
-There are other ways to install DocPort. If submodule is no-go, use [install as git clone]({{%ref "as-git-clone/_index.md"%}}) or [install from a zip archive]({{%ref "direct copy/_index.md"%}})
-{{%/alert%}}
-
-DocPort will be added like a dependency repo to original project. When using CI tools like Netlify, Jenkins etc., submodule method is required, or you will get `theme not found` issues. Same applies when building site on remote server trough SSH.
-
-
-
-On your root of Hugo execute:
-
-```
-$ git submodule add https://github.com/vjeantet/hugo-theme-docport.git themes/docport
-```
-Next initialize submodule for parent git repo:
-
-```
-$ git submodule init
-$ git submodule update
-```
-
-Now you are ready to add content and build your documentatyion.
-{{%notice warning%}}Do not change any file inside themes directory.{{%/notice%}}
-
-## Configuration
-
-[Follow instructions here]({{%relref "getting-start/configuration/_index.md"%}})
diff --git a/themes/docport/exampleSite/content/getting-start/installation/direct copy/_index.md b/themes/docport/exampleSite/content/getting-start/installation/direct copy/_index.md
deleted file mode 100644
index f962d2e..0000000
--- a/themes/docport/exampleSite/content/getting-start/installation/direct copy/_index.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-description: ""
-subpage: true
-title: from zip archive
-weight: 1
----
-
-## Install DocPort from a zip archive
-
-Navigate to your hugo root folder in your Hugo site and use perform one of following scenarios.
-
-All files from theme will be tracked inside parent repo, to update it, have to override files in theme. [{{%icon cloud_download%}} download zip](https://github.com/vjeantet/hugo-theme-docport/archive/master.zip) and extract inside `themes/`.
-
-```
-https://github.com/vjeantet/hugo-theme-docport/archive/master.zip
-```
-
-Rename `hugo-theme-docport-master` folder to `docport`, to match configuration in next step.
-
-Name of theme in next step will be `docport`.
-
-## Configuration
-
-[Follow instructions here]({{%relref "getting-start/configuration/_index.md"%}})
diff --git a/themes/docport/exampleSite/content/shortcodes/_index.md b/themes/docport/exampleSite/content/shortcodes/_index.md
deleted file mode 100644
index fe708bb..0000000
--- a/themes/docport/exampleSite/content/shortcodes/_index.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-date: "2017-04-24T18:36:24+02:00"
-description: ""
-hide:
-- toc
-title: Shortcodes
-weight: 30
----
-
-A bunch of Shortcodes are available with this theme :
-
-{{%children style="card" description="true" %}}
diff --git a/themes/docport/exampleSite/content/shortcodes/alert/_index.md b/themes/docport/exampleSite/content/shortcodes/alert/_index.md
deleted file mode 100644
index 56dc667..0000000
--- a/themes/docport/exampleSite/content/shortcodes/alert/_index.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-description: The alert shortcode allows you to highlight information in your page.
-title: alert
----
-
-The `alert` shortcode allow you to highlight information in your page. They create a colored box surrounding your text, like this:
-
-{{%alert%}}**This is** an alert !{{%/alert%}}
-## Usage
-
-| Parameter | Default | Description |
-|:--|:--|:--|
-| theme | `info` | `primary`,`success`, `info`,`warning`,`danger`,`dark`,`light`,`secondary` |
-
-{{%alert info%}}
-**Tips :** setting only the theme as argument works too :
-`{{%/*alert warning*/%}}` instead of `{{%/*alert theme="warning"*/%}}`
-{{%/alert%}}
-
-## Basic examples
-
-```
- {{%/* alert primary */%}}**this** is a primary{{%/* /alert */%}}
- {{%/* alert theme="info" */%}}**this** is a text{{%/* /alert */%}}
- {{%/* alert theme="success" */%}}**Yeahhh !** is a text{{%/* /alert */%}}
- {{%/* alert theme="warning" */%}}**Be carefull** is a text{{%/* /alert */%}}
- {{%/* alert danger */%}}**Beware !** is a text{{%/* /alert */%}}
- {{%/* alert dark */%}}**Dark !** is a dark{{%/* /alert */%}}
- {{%/* alert light */%}}**oooh !** is a light{{%/* /alert */%}}
- {{%/* alert secondary */%}}**Wait !** is a secondary{{%/* /alert */%}}
-```
-{{% alert primary %}}**this** is an primary{{% /alert %}}
-{{% alert theme="info"%}}**this** is an info{{% /alert %}}
-{{% alert theme="success" %}}**Yeahhh !** is a success{{% /alert %}}
-{{% alert theme="warning" %}}**Be carefull** is a warning{{% /alert %}}
-{{% alert danger %}}**Beware !** is a danger{{% /alert %}}
-{{% alert dark %}}**Dark !** is a dark{{% /alert %}}
-{{% alert light %}}**oooh !** is a light{{% /alert %}}
-{{% alert secondary %}}**Wait !** is a secondary{{% /alert %}}
\ No newline at end of file
diff --git a/themes/docport/exampleSite/content/shortcodes/attachments/_files/Carroll_AliceAuPaysDesMerveilles.pdf b/themes/docport/exampleSite/content/shortcodes/attachments/_files/Carroll_AliceAuPaysDesMerveilles.pdf
deleted file mode 100644
index 97377e9..0000000
Binary files a/themes/docport/exampleSite/content/shortcodes/attachments/_files/Carroll_AliceAuPaysDesMerveilles.pdf and /dev/null differ
diff --git a/themes/docport/exampleSite/content/shortcodes/attachments/_files/adivorciarsetoca00cape.pdf b/themes/docport/exampleSite/content/shortcodes/attachments/_files/adivorciarsetoca00cape.pdf
deleted file mode 100644
index fc1c865..0000000
Binary files a/themes/docport/exampleSite/content/shortcodes/attachments/_files/adivorciarsetoca00cape.pdf and /dev/null differ
diff --git a/themes/docport/exampleSite/content/shortcodes/attachments/_files/hugo.png b/themes/docport/exampleSite/content/shortcodes/attachments/_files/hugo.png
deleted file mode 100644
index 48acf34..0000000
Binary files a/themes/docport/exampleSite/content/shortcodes/attachments/_files/hugo.png and /dev/null differ
diff --git a/themes/docport/exampleSite/content/shortcodes/attachments/_files/movieselectricsheep-flock-244-32500-2.mp4 b/themes/docport/exampleSite/content/shortcodes/attachments/_files/movieselectricsheep-flock-244-32500-2.mp4
deleted file mode 100644
index 9f1fe56..0000000
Binary files a/themes/docport/exampleSite/content/shortcodes/attachments/_files/movieselectricsheep-flock-244-32500-2.mp4 and /dev/null differ
diff --git a/themes/docport/exampleSite/content/shortcodes/attachments/_files/zip.mp3 b/themes/docport/exampleSite/content/shortcodes/attachments/_files/zip.mp3
deleted file mode 100644
index 33df837..0000000
Binary files a/themes/docport/exampleSite/content/shortcodes/attachments/_files/zip.mp3 and /dev/null differ
diff --git a/themes/docport/exampleSite/content/shortcodes/attachments/_index.md b/themes/docport/exampleSite/content/shortcodes/attachments/_index.md
deleted file mode 100644
index a2d113c..0000000
--- a/themes/docport/exampleSite/content/shortcodes/attachments/_index.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-description: The Attachments shortcode displays a list of files attached to a page.
-title: attachments
----
-
-The Attachments shortcode displays a list of files attached to a page.
-Example :
-{{%alert success%}}
-{{%attachments /%}}
-{{%/alert%}}
-
-
-## Usage
-
-The shortcurt lists files found in the **_files folder**.
-
-2. If your page is a **folderA**, attachements must be place in a **'_files'** subfolder.
-
-```
-content
-└── folderA
- ├── _index.md
- └── _files
- ├── attachment.pdf
- └── attachment.pdf
-```
-
-That's all !
-
-{{%alert info%}}**Tip** : Look at this documentation source code on github{{%/alert%}}
-
-### parameters
-
-| Parameter | Default | Description |
-|:--|:--|:--|
-| title | "Attachments" | List's title |
-| pattern | ".*" | A regular expressions, used to filter the attachments by file name.
{{%alert warning%}}The **pattern** parameter value must be [regular expressions](https://en.wikipedia.org/wiki/Regular_expression).
-
-For example:
-
-* To match a file suffix of 'jpg', use **.*jpg** (not *.jpg).
-* To match file names ending in 'jpg' or 'png', use **.*(jpg|png)**
-
-{{%/alert%}}|
-
-
-## Demo
-### List of attachments ending in pdf or mp4
-```
- {{%/*attachments title="Related files" pattern=".*(pdf|mp4)"/*/%}}
-```
-renders as
-
-{{%attachments title="Related files" pattern=".*(pdf|mp4)"/%}}
-
diff --git a/themes/docport/exampleSite/content/shortcodes/badge/_index.md b/themes/docport/exampleSite/content/shortcodes/badge/_index.md
deleted file mode 100644
index 20e8f7d..0000000
--- a/themes/docport/exampleSite/content/shortcodes/badge/_index.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-description: Disclaimers to help you structure your page
-title: badge
----
-
-{{% badge %}}primary _(default)_{{% /badge %}}
-{{% badge warning %}}In progress{{% /badge %}}
-{{% badge secondary %}}docport{{% /badge %}}
-{{% badge success %}}beta{{% /badge %}}
-{{% badge danger %}}danger{{% /badge %}}
-{{% badge warning %}}warning{{% /badge %}}
-{{% badge info %}}info{{% /badge %}}
-{{% badge light %}}light{{% /badge %}}
-{{% badge dark %}}dark{{% /badge %}}
-
-## Shortcode markup {{% badge warning %}}new{{% /badge %}}
-```
- {{%/* badge %}}primary _(default)_{{% /badge %}}
- {{% badge warning %}}In progress{{% /badge %}}
- {{% badge secondary %}}docport{{% /badge %}}
- {{% badge success %}}beta{{% /badge %}}
- {{% badge danger %}}danger{{% /badge %}}
- {{% badge warning %}}warning{{% /badge %}}
- {{% badge info %}}info{{% /badge %}}
- {{% badge light %}}light{{% /badge %}}
- {{% badge dark %}}dark{{% /badge */%}}
-```
-
-
-
-
-
-## Usage
-```
- {{%/*badge $style %}}Lorem ipsum{{%/badge*/%}}
-```
-
-| Parameter | Description |
-|:--|:--|
-| $style | type/color of badge |
-
diff --git a/themes/docport/exampleSite/content/shortcodes/button/_index.md b/themes/docport/exampleSite/content/shortcodes/button/_index.md
deleted file mode 100644
index f908e9c..0000000
--- a/themes/docport/exampleSite/content/shortcodes/button/_index.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-description: Display an actionable button in your page.
-title: button
----
-
-Display an actionable button in your page.
-
-{{