routing test

Signed-off-by: Rieks <RieksJ@users.noreply.github.com>
tno-terminology-design · Apr 17, 2024 · bfedbe3 · bfedbe3
1 parent 971b36b
commit bfedbe3
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/docs/terms/mve.md b/docs/terms/mve.md
@@ -14,6 +14,12 @@ formPhrases: [ "mimimal viable example{ss}", "mimimum viable example{ss}", "mve{
 
 A **Minimal Viable Example (MVE)** is a very simple version of a GitHub repo that includes the minimal stuff for using the [TEv2 tools](@tev2) and demonstrating its results.
 
-# Example
+This includes:
+- the actual documentation that is to be published;
+- the files needed for generating the static website (e.g., the [workflow file](@);
+- any other artifacts needed by the static website generate (e.g., CSS files, plugins, etc.)
+- and, of course, the set of directories and files that [TEv2 tools](@tev2) need;
+
+## Example
 
 One example of an [MVE](@) is [the repo of which this page is a part](https://github.com/tno-terminology-design/tev2-mve).
diff --git a/docs/terms/workflow-file.md b/docs/terms/workflow-file.md
@@ -16,7 +16,7 @@ The contents of that file follows the [workflow syntax for GitHub Actions](https
 
 You may consult [GitHub's documentation about workflows](https://docs.github.com/en/actions/using-workflows/about-workflows) to get more backgrounds on this.
 
-# Example
+## Example
 
 Here is an example of a [workflow file](@) that can be used
 to compile and deploy the static website of an [MVE](@)