Merge branch 'main' into add-local-contrib-guide

* main: (51 commits)
  Use chevrondown icon
  Add missing aliases
  Move how to track new terms
  Improve Node.js documentation clarity
  Use CLI long options
  Sort pages and section by weight
  Rollback how to join federation
  Improve Collections Metadata how to
  Allow markdown in aside link
  Improve collections how to
  Improve Collections creation tutorial
  Split declarations maintenance how to
  Improve minimal terminology copywriting
  Improve title
  Unify vocabulary
  Remove irrelevant and broken link
  Update vocabulary
  Improve terms tracking tutorial
  Unify introductory text for Community section
  Clarify homepage
  ...

Author: Ndpnt

.markdownlint.yml

@@ -14,6 +14,7 @@ no-inline-html:
   allowed_elements:
     - abbr
     - i
+    - filename
 
 no-duplicate-header: false
 

config/_default/module.yaml

@@ -0,0 +1,5 @@
+mounts:
+  - source: assets
+    target: assets
+  - source: node_modules/minireset.css/minireset.css
+    target: assets/css/vendor/minireset.css

content/_index.en.md

@@ -0,0 +1,39 @@
+---
+title: Open Terms Archive documentation
+linkTitle: Homepage
+weight: 1
+---
+
+# Open Terms Archive documentation
+
+Open Terms Archive is a decentralised system that tracks collections of services' terms across multiple servers. Each collection exposes the data it collects through datasets and through its own API. The Federation API unifies search and discovery across collections.
+
+## Required minimal terminology
+
+Before diving into the details, let's first understand the essential terminology used throughout this documentation.
+
+- **Terms:** the contractual documents published by services (such as Terms of Service, Privacy Policy, Community Guidelines…) that users agree to.
+- **Collection:** a set of tracked terms grouped by a specific scope (such as language, jurisdiction, industry…).
+- **Declaration:** a JSON file that defines which terms to track for a service and how to track them.
+- **Snapshot:** the original source document (HTML, PDF…) from which the terms will be extracted.
+- **Version:** the textual content of the terms after filtering out irrelevant content (navigation menu, advertisements…) from a snapshot.
+
+## Documentation structure
+
+This documentation follows the [Diátaxis](https://diataxis.fr) approach and structures content in different categories:
+
+- **Tutorials:** step-by-step learning guides that help beginners get started with Open Terms Archive, providing foundational knowledge and hands-on experience.
+- **How-to guides:** task-focused instructions that help experienced users accomplish specific goals efficiently and effectively.
+- **Reference:** comprehensive technical documentation detailing configuration options and specifications for advanced users.
+- **Explanations:** background knowledge that enables understanding the constraints and how choices that are made.
+
+### Table of contents
+
+- **Analysis:** guidance on how to analyze terms changes, from navigating through the history of tracked documents to publishing memos about significant changes.
+- **Community:** information on how to participate in the Open Terms Archive community.
+- **Terms:** guidance on tracking and maintaining terms declarations.
+- **Collections:** guidance on creating and managing collections of tracked terms.
+- **Federation:** constraints and benefits of joining the Open Terms Archive federation.
+- **Deployment:** guidance on operating an Open Terms Archive instance.
+- **Programmatic access:** documentation on the engine CLI and APIs.
+- **Concepts and principles:** main concepts, terminology and fundamental design principles of Open Terms Archive.

content/_index.md

@@ -0,0 +1,5 @@
+---
+title: "Analysis"
+weight: 2
+---
+

content/analysis/_index.md

@@ -0,0 +1,4 @@
+---
+title: How to
+weight: 1
+---

content/analysis/how-to/_index.md

@@ -1,7 +1,9 @@
 ---
-title: "How to navigate history"
+title: Navigate history
 weight: 1
-aliases: /navigate-history/
+aliases:
+  - /navigate-history/
+  - /terms/how-to-navigate-history/
 ---
 
 # How to navigate history

content/terms/how-to-navigate-history.md …tent/analysis/how-to/navigate-history.mdcontent/terms/how-to-navigate-history.md renamed to content/analysis/how-to/navigate-history.md content/terms/how-to-navigate-history.md renamed to content/analysis/how-to/navigate-history.md

@@ -1,5 +1,6 @@
 ---
-title: "How to publish a memo"
+title: Publish a memo
+aliases: /memos/how-to-publish/
 ---
 
 # How to publish a memo
@@ -10,7 +11,7 @@ No technical skills are required.
 
 ## Prerequisites
 
-- A drafted memo compliant with the [copywriting reference]({{< relref "/memos/copywriting-reference" >}}).
+- A drafted memo compliant with the [copywriting reference]({{< relref "/analysis/reference/copywriting" >}}).
 
 ## 1. Send
 

content/memos/how-to-publish.en.md content/analysis/how-to/publish-memo.mdcontent/memos/how-to-publish.en.md renamed to content/analysis/how-to/publish-memo.md

@@ -0,0 +1,4 @@
+---
+title: Reference
+weight: 2
+---

content/analysis/reference/_index.md

@@ -1,5 +1,6 @@
 ---
-title: "Copywriting reference"
+title: Copywriting
+aliases: /memos/copywriting-reference/
 ---
 
 # Copywriting reference