Add the certifications page

.github/styles/config/vocabularies/Doc/accept.txt

@@ -1,13 +1,18 @@
 add-on
+allowlist
+allowlists
 ANSI
 Ant
 APIs
 app_id
 Astro
 AstroWind
+auditability
 Azimutt
+Bao
 Blackfire
 boto
+Bpifrance
 Caddy
 Caddyfile
 callout
@@ -25,33 +30,43 @@ CRDs
 cron
 CVE
 Cyberduck
+cybersecurity
+Datadog
+declaratively
 Deno
 DNS
 Dockerfile
+dotenv
 downtimes
 Entra
 EOL
 ESLint
 failover
 Filestash
 FileZilla
+Fluentd
 FPM
 FrankenPHP
 FSBucket
 Gemfile
 GlassFish
 Gradle
 Grafana
+hardcode
 hardcoded
+hardcoding
 healthcheck
 Heptapod
 Hextra
 Hono
 hostname
 Infinispan
+IONOS
+IPSec
 jarName
 JBoss
 JSDoc
+Kestra
 Keycloak
 kubectl
 Laravel
@@ -62,9 +77,11 @@ LTS
 Lume
 Materia
 Matomo
+Maudit
 Maven
 Metabase
 middleware
+misconfiguration
 Monolog
 monorepo
 monorepository
@@ -78,6 +95,8 @@ Nuxt
 OAuth
 Okta
 Otoroshi
+Outline
+OVHcloud
 packageManager
 Payara
 Percona
@@ -92,14 +111,19 @@ rclone
 Redict
 redirections
 RSS
+runtime's
 runtimes
 sbt
 scalers
+Scaleway
 SCMs
 serverless
 Servlet
+SFTPGo
 shortcode
 Sidekiq
+subcommand
+subcommands
 Symfony
 syslog
 Telegraf
@@ -108,6 +132,8 @@ toolchain
 tooltip
 tooltips
 URIs
+uv
+Veritas
 VS Code
 WAF
 webroot

.gitignore

@@ -5,7 +5,6 @@ Thumbs.db
 
 # Configuration files
 .clever.json
-.vale.ini
 
 # Build/cache files/folders
 /.hugo_build.lock

.markdownlint-cli2.jsonc

@@ -0,0 +1,6 @@
+{
+  "gitignore": true,
+  // Hugo templates for the Markdown output format carry a .md suffix but are Go
+  // templates, not Markdown. See layouts/page.markdown.md and layouts/_partials/.
+  "ignores": ["layouts/**"]
+}

.markdownlint.jsonc

@@ -1,16 +1,28 @@
 {
-    "MD041": false,
-    "MD013": false,
-    "MD051": false,
-    "MD029": false,
-    // MD033/no-inline-html : Inline HTML : https://github.com/DavidAnson/markdownlint/blob/v0.32.1/doc/md033.md
-    "MD033": {
+  "MD004": {
+    "style": "dash"
+  },
+  "MD013": false,
+  "MD029": false,
+  // MD033/no-inline-html : Inline HTML : https://github.com/DavidAnson/markdownlint/blob/v0.32.1/doc/md033.md
+  "MD033": {
     // Allowed elements
     "allowed_elements": [
       "br",
-      "cc-smart-container",
-      "cc-pricing-product",
       "cite"
     ]
+  },
+  // MD034/no-bare-urls : shortcode attributes such as {{< card link="https://..." >}}
+  // are not Markdown, but markdownlint reads them as bare URLs. Wrapping the value in
+  // <> silences the rule and makes Go reject the URL, rendering href="#ZgotmplZ".
+  // Keep URLs bare in shortcode attributes.
+  "MD034": false,
+  "MD041": false,
+  "MD051": false,
+  "MD055": {
+    "style": "leading_and_trailing"
+  },
+  "MD060": {
+    "style": "aligned"
   }
-}
+}

.vale.ini

@@ -7,11 +7,11 @@ MinAlertLevel = suggestion
 Packages = Hugo, Google
 
 [*.md]
-BasedOnStyles = Clever, Vale, Google, Guides
+BasedOnStyles = Clever, Vale, Google
 Google.Headings = NO
 Vale.Terms = NO
 Google.Parens = NO
 Google.Ellipses = NO
 
 [*.xml]
-Transform = docbook-xsl-snapshot/html/docbook.xsl
+Transform = docbook-xsl-snapshot/html/docbook.xsl

AGENTS.md

@@ -5,20 +5,23 @@ This file provides repository-wide guidance to coding agents working on Clever C
 ## Common Development Commands
 
 ### Hugo Site Development
+
 - **Install development dependencies**: `mise install` - Installs the tools declared in `mise.toml`
-- **Local development**: `hugo server` - Serves site at http://localhost:1313 with live reload
+- **Local development**: `hugo server` - Serves site at <http://localhost:1313> with live reload
 - **Build for production**: `hugo` - Outputs to `public/developers/`
 - **Preview drafts**: `hugo server --buildDrafts` - Include draft content in local preview
 - **Update CLI reference**: `./update-cli-reference.sh` - Fetches latest clever-tools documentation
 
 ### Content Generation
+
 - **New guide**: `hugo new content guides/<framework>.md`
 - **New documentation**: `hugo new content/doc/administrate/<feature>.md`
 - **New application runtime**: `hugo new content --kind applications doc/applications/<runtime>.md`
 
 ## Project Architecture
 
 ### Content Organization
+
 This is a Hugo-based documentation site using the Hextra theme with the following structure:
 
 - **`/content/`** - All documentation content:
@@ -36,7 +39,9 @@ This is a Hugo-based documentation site using the Hextra theme with the followin
 - **`/layouts/`** - Hugo templates and shortcodes for content rendering
 
 ### Content Types and Front Matter
+
 Content uses Hugo front matter with fields such as:
+
 - `type: docs` - Content layout type
 - `weight` - Sidebar ordering (integer)
 - `linkTitle` - Short title for sidebar navigation
@@ -47,18 +52,30 @@ Content uses Hugo front matter with fields such as:
 - `excludeSearch: true` - Excludes from search index (recommended for changelog)
 
 For changelog entries, also include:
+
 - `date: YYYY-MM-DD` - Publication date
 - `tags` - Array of product tags (lowercase)
 - `authors` - Array with `name`, `link`, `image` fields
 
+### Moving or Merging Content
+
+When a page moves to another URL, or when its content is merged into another page:
+
+- Always add the old URL to the destination page's `aliases`, so Hugo keeps serving a redirect
+- Carry over every alias the removed page already declared; they must keep resolving
+- Update internal links to target the new URL directly instead of relying on the redirect, especially in `shared/` blocks included by many pages
+- Check each redirect in the build output before committing
+
 ### Shared Content System
+
 - Include shared content: `{{% content "filename" %}}`
 - Include shared content with shortcodes: `{{% content-raw "filename" %}}`
 - Shared files should not contain headings (breaks ToC generation)
 
 ## Quality Standards
 
 ### Content Quality Requirements
+
 - Use second person ("you") addressing readers directly
 - Write in active voice, avoid passive constructions
 - Use `organisation` and `organisations`, rather than `organization` and `organizations`; this isn't a general British-spelling requirement
@@ -67,45 +84,57 @@ For changelog entries, also include:
 - Explain prerequisites and non-obvious behaviour, while keeping the main task path concise
 
 ### Prohibited Elements
+
 - First-person pronouns: I, me, my, we, us, our, let's
 - Placeholder phrases: "please note", "at this time", "it should be noted"
 - Overconfident claims: "simply", "just", "easily", "quickly", "obviously"
 - Time-dependent promises: "soon", "in the future", "coming next month"
 
 ### Markdown and Editorial Standards
+
 - **Markdown linting**: Run `markdownlint-cli2 "**/*.md"` with config in `.markdownlint.jsonc`
 - **Editorial checks**: Run Vale with `vale <files>` for style and terminology
 - **Build verification**: Always test with `hugo` before committing
 - **Structure**: Use 2-4 well-developed paragraphs per section, minimize bullet lists
 - **Paragraphs**: Aim for 3-6 lines for optimal readability
 
 ### Callouts
+
 - Prefer GitHub-style callouts with a concise title on the marker line, as supported by the theme:
+
   ```markdown
   > [!NOTE] Current behaviour
   > This information helps readers understand the current behaviour
 
   > [!WARNING] Back up your data
   > Back up your application database before upgrading
   ```
+
 - Use the Hugo `{{< callout >}}` shortcode only when GitHub-style syntax can't provide the required rendering or behaviour
 - Limit callouts to one or two per page
 
 ### Commit Messages
+
 - For content updates, use `section(page): commit message`, for example:
   - `addons(postgresql): document pg_partman support`
   - `applications(nodejs): clarify pnpm configuration`
-  - `changelog(metabase): announce 0.63.14 security update`
   - `guides: add SvelteKit` for a new deployment guide
+- For changelog entries, use `changelog: what you announce`. Name the product and its version, or the change itself, instead of starting with a verb:
+  - `changelog: Keycloak 26.7.3`
+  - `changelog: MySQL 8.0.46 and 8.4.10`
+  - `changelog: PostgreSQL 18 by default`
+  - `changelog: images updates, 2026W34`
+- Commit a changelog entry with the documentation pages and data files it relies on, so an announcement never lands before the pages it links to
 - For documentation structure, Hugo, deployment, CI, tooling, or dependency changes, use standard Conventional Commits, for example:
   - `feat(hugo): add a shortcode for version tables`
   - `fix(ci): run Vale on shared content`
   - `refactor(layouts): simplify changelog rendering`
   - `chore(deps): update the Hextra theme`
 - Split content and structural changes into separate commits when possible
-- Start the subject with a lowercase imperative verb
+- Start the subject with a lowercase imperative verb, except for changelog entries
 
 ### Code and Technical Examples
+
 - Always provide complete, runnable code examples
 - Keep commands literally copyable: don't put shell-invalid placeholders or bracketed optional arguments in executable code blocks
 - Show optional flags in separate examples or explain where to add them
@@ -145,11 +174,13 @@ The site is configured for Clever Cloud hosting with the `static` runtime and th
 `CC_DISABLE_MISE` prevents Clever Cloud from installing the local development dependencies because the platform manages the deployment tools directly.
 
 ## Data Management
+
 Runtime versions and software compatibility information is maintained in `/data/runtime_versions.yml` and should be kept current with platform capabilities. The site generates various output formats including standard HTML and a special LLMS output format at `/llms.txt` for AI consumption.
 
 ## Hugo Shortcodes and Features
 
 ### Content Shortcodes
+
 - `{{% content "filename" %}}` - Include shared content from `/shared/` directory
 - `{{% content-raw "filename" %}}` - Include shared content containing shortcodes
 - `{{% steps %}}` - Create step-by-step instructions for guides
@@ -159,17 +190,20 @@ Runtime versions and software compatibility information is maintained in `/data/
 - `{{< hextra/hero-subtitle >}}` - Add engaging subtitles in guides
 
 ### Hugo Content Types
+
 - **Documentation pages**: Use `type: docs` in front matter
 - **Guides**: Use step-by-step structure, hero subtitles, and cards when they improve the guide
 - **Changelog entries**: Include date, tags, and author information
 - **API documentation**: Structured reference content
 
 ### Hextra Theme Features
+
 - **Search**: Full-text search using FlexSearch
 - **Dark mode**: Automatic theme switching
 - **Responsive navigation**: Sidebar and mobile-friendly menus
 - **Edit links**: Direct GitHub editing integration
 - **Syntax highlighting**: Code block highlighting with copy functionality
 
 ## File Standards
+
 All text files must end with a newline.

CONTRIBUTING.md

@@ -107,12 +107,22 @@ For content updates, use `section(page): commit message`. The section and page i
 ```text
 addons(postgresql): document pg_partman support
 applications(nodejs): clarify pnpm configuration
-changelog(metabase): announce 0.63.14 security update
 guides: add SvelteKit
 ```
 
 Use `guides: add Product` when adding a deployment guide. Start the subject with a lowercase imperative verb.
 
+Changelog entries are the exception. Use `changelog: what you announce`, naming the product and its version or the change itself rather than starting with a verb:
+
+```text
+changelog: Keycloak 26.7.3
+changelog: MySQL 8.0.46 and 8.4.10
+changelog: PostgreSQL 18 by default
+changelog: images updates, 2026W34
+```
+
+Commit a changelog entry together with the documentation pages and data files it relies on, so an announcement never lands before the pages it links to.
+
 For changes to the documentation structure, Hugo configuration or templates, deployment, CI, tooling, or dependencies, use the standard Conventional Commits format `type(scope): commit message`:
 
 ```text