tests: bootstrap test with minimal acceptable code coverage

Signed-off-by: Emilien Escalle <emilien.escalle@escemi.com>

Author: neilime

.github/dependabot.yml

@@ -3,7 +3,8 @@ version: 2
 updates:
   - package-ecosystem: "npm"
     open-pull-requests-limit: 20
-    directory: "/"
+    directories:
+      - "application/"
     versioning-strategy: increase
     schedule:
       interval: "weekly"
@@ -31,7 +32,8 @@ updates:
 
   - package-ecosystem: github-actions
     open-pull-requests-limit: 20
-    directory: "/"
+    directories:
+      - "/"
     schedule:
       interval: weekly
     groups:
@@ -44,7 +46,13 @@ updates:
     directory: "/"
     schedule:
       interval: weekly
+
+  - package-ecosystem: "docker"
+    open-pull-requests-limit: 20
+    directory: "/"
+    schedule:
+      interval: "weekly"
     groups:
-      devcontainers-dependencies:
+      docker-dependencies:
         patterns:
           - "*"

.github/workflows/__shared-ci.yml

@@ -2,20 +2,25 @@ name: Common Continuous Integration tasks
 
 on:
   workflow_call:
+    outputs:
+      build-artifact-id:
+        description: "The build artifact ID"
+        value: ${{ jobs.continuous-integration.outputs.build-artifact-id }}
 
-permissions:
-  contents: read
-  security-events: write
-  # FIXME: This is a workaround for having workflow ref. See https://github.com/orgs/community/discussions/38659
-  id-token: write
+permissions: {}
 
 jobs:
   continuous-integration:
-    uses: hoverkraft-tech/ci-github-nodejs/.github/workflows/continuous-integration.yml@5c1010a9146952f724730bf79ba8e2e40ba8e474 # 0.11.0
+    uses: hoverkraft-tech/ci-github-nodejs/.github/workflows/continuous-integration.yml@c9d9d041ba4ef35695ee469c4782fa6a8bbebbcc # 0.21.2
+    permissions:
+      contents: read
+      id-token: write
+      packages: read
+      pull-requests: write
+      security-events: write
     with:
       working-directory: application
-      test: false
       build: |
         {
-          "artifact": ["application/dist"]
+          "artifact": ["dist"]
         }

.github/workflows/greetings.yml

@@ -6,11 +6,12 @@ on:
   pull_request_target:
     branches: [main]
 
-permissions:
-  contents: read
-  issues: write
-  pull-requests: write
+permissions: {}
 
 jobs:
   greetings:
-    uses: hoverkraft-tech/ci-github-common/.github/workflows/greetings.yml@95664be4ec235bfc221c4356c7153cbab3fb8f93 # 0.22.3
+    uses: hoverkraft-tech/ci-github-common/.github/workflows/greetings.yml@0.31.7
+    permissions:
+      contents: read
+      issues: write
+      pull-requests: write

.github/workflows/main-ci.yml

@@ -9,18 +9,21 @@ concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true
 
+permissions: {}
+
 jobs:
   ci:
     uses: ./.github/workflows/__shared-ci.yml
     secrets: inherit
     permissions:
       contents: read
-      security-events: write
-      # FIXME: This is a workaround for having workflow ref. See https://github.com/orgs/community/discussions/38659
       id-token: write
+      packages: read
+      pull-requests: write
+      security-events: write
 
   deploy:
-    if: github.ref == 'refs/heads/main'
+    if: github.ref_name == github.event.repository.default_branch
     name: Deploy website
     needs: ci
     runs-on: ubuntu-latest
@@ -30,8 +33,11 @@ jobs:
     environment:
       name: github-pages
       url: ${{ steps.deployment.outputs.url }}
+    outputs:
+      url: ${{ steps.deployment.outputs.url }}
     steps:
       - id: deployment
-        uses: hoverkraft-tech/ci-github-publish/actions/deploy/github-pages@e38260241de6b96a9f21834ca2d399789013e7ff # 0.5.1
+        uses: hoverkraft-tech/ci-github-publish/actions/deploy/github-pages@0.21.0
         with:
-          build-assets-path: application/dist
+          build-path: application/dist
+          build-artifact-id: ${{ needs.ci.outputs.build-artifact-id }}

.github/workflows/need-fix-to-issue.yml

@@ -16,13 +16,14 @@ on:
           before it; to go back further, enter an earlier SHA here"
         required: false
 
-permissions:
-  contents: read
-  issues: write
+permissions: {}
 
 jobs:
   main:
-    uses: hoverkraft-tech/ci-github-common/.github/workflows/need-fix-to-issue.yml@95664be4ec235bfc221c4356c7153cbab3fb8f93 # 0.22.3
+    uses: hoverkraft-tech/ci-github-common/.github/workflows/need-fix-to-issue.yml@0.31.7
+    permissions:
+      contents: read
+      issues: write
     with:
       manual-commit-ref: ${{ inputs.manual-commit-ref }}
       manual-base-ref: ${{ inputs.manual-base-ref }}

.github/workflows/pull-request-ci.yml

@@ -5,17 +5,19 @@ on:
   pull_request:
     branches: [main]
 
-permissions:
-  contents: read
-  security-events: write
-  # FIXME: This is a workaround for having workflow ref. See https://github.com/orgs/community/discussions/38659
-  id-token: write
-
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true
 
+permissions: {}
+
 jobs:
   ci:
     uses: ./.github/workflows/__shared-ci.yml
     secrets: inherit
+    permissions:
+      contents: read
+      id-token: write
+      packages: read
+      pull-requests: write
+      security-events: write

.github/workflows/semantic-pull-request.yml

@@ -7,10 +7,11 @@ on:
       - edited
       - synchronize
 
-permissions:
-  contents: write
-  pull-requests: write
+permissions: {}
 
 jobs:
   main:
-    uses: hoverkraft-tech/ci-github-common/.github/workflows/semantic-pull-request.yml@95664be4ec235bfc221c4356c7153cbab3fb8f93 # 0.22.3
+    uses: hoverkraft-tech/ci-github-common/.github/workflows/semantic-pull-request.yml@0.31.7
+    permissions:
+      contents: write
+      pull-requests: write

.github/workflows/stale.yml

@@ -4,10 +4,11 @@ on:
   schedule:
     - cron: "30 1 * * *"
 
-permissions:
-  issues: write
-  pull-requests: write
+permissions: {}
 
 jobs:
   main:
-    uses: hoverkraft-tech/ci-github-common/.github/workflows/stale.yml@95664be4ec235bfc221c4356c7153cbab3fb8f93 # 0.22.3
+    uses: hoverkraft-tech/ci-github-common/.github/workflows/stale.yml@0.31.7
+    permissions:
+      issues: write
+      pull-requests: write

Makefile

@@ -10,20 +10,17 @@ include .env
 
 setup: ## Prepare stack to run
 	cd application && npm install
-	cd .github/actions/generate-blog-post && npm install
-	cd .github/actions/generate-brand-content && npm install
-	cd .github/actions/validate-manifest && npm install
 
 start: ## Start application in dev mode
 	cd application && npm run start
 
 lint: ## Run linters
-	cd application && npm run lint -- $(filter-out $@,$(MAKECMDGOALS))
+	cd application && npm run lint:ci -- $(filter-out $@,$(MAKECMDGOALS))
 	$(call run_linter,)
 
 lint-fix: ## Run linters
-	cd application && npm audit --omit=dev
-	cd application && npm run humanize:fix
+	cd application && npm audit fix
+	cd application && npx update-browserslist-db@latest
 	cd application && npm run lint:fix
 	$(MAKE) linter-fix
 
@@ -32,9 +29,6 @@ build: ## Build libs and applications
 
 test: ## Run tests
 	cd application && npm run test:ci
-	cd .github/actions/generate-blog-post && npm run test:ci
-	cd .github/actions/generate-brand-content && npm run test:ci
-	cd .github/actions/validate-manifest && npm run test:ci
 
 ci: ## Run tests in CI mode
 	$(MAKE) lint-fix

README.md

@@ -1,8 +1,8 @@
 # Cloud Native Provence — Landing Page
 
-Astro-based conference website with bilingual routing (`fr` / `en`) and translated slugs.
+Conference website for Cloud Native Provence, with bilingual routing (`fr` / `en`) and translated page slugs.
 
-## Development workflow (Makefile-first)
+## Development workflow
 
 Use `make` commands from the repository root.
 
@@ -15,21 +15,28 @@ Main targets:
 - `make setup` — install project dependencies
 - `make start` — start local dev server (`application`)
 - `make build` — production build
+- `make test-app` — run application tests with coverage
 - `make lint` — run linters/checks
 - `make lint-fix` — run fixers
 - `make ci` — lint + build + test pipeline
 
-Do not run `npm run ...` directly unless you are explicitly debugging Makefile behavior.
+## Tests and coverage
+
+Tests run with Vitest from `application/`.
+
+```bash
+make test
+```
 
 ## Dev Container
 
 This repository includes a VS Code Dev Container in `.devcontainer/devcontainer.json`.
 
-### Recommended usage
+Quick start:
 
 1. Open the repository in VS Code.
 2. Run `Dev Containers: Reopen in Container`.
-3. Once inside the container, run:
+3. Inside the container:
 
 ```bash
 make setup
@@ -45,31 +52,36 @@ The dev container provides:
 
 The app is available on port `4321`.
 
-## Current routing model
+## Routing model
 
-Routing is locale-first and centralized.
+Routing is locale-first and centralized:
 
 - `/` redirects to `/fr`
 - `/fr` and `/en` are localized homepages
-- `/{lang}/{translated-slug}` for content pages
+- `/{lang}/{translated-slug}` serves localized content pages
 
 Key files:
 
 - `application/src/pages/index.astro` — root redirect
 - `application/src/pages/[lang]/index.astro` — localized homepage
 - `application/src/pages/[lang]/[page].astro` — localized dynamic pages
-- `application/src/i18n/routes.ts` — route slug mapping + path helpers
+- `application/src/i18n/routes.ts` — slug mapping and path translation helpers
 
-Example translated slugs:
+Translated static pages:
 
-- FR: `/fr/a-propos`, `/fr/charte-graphique`, `/fr/politique-de-confidentialite`
-- EN: `/en/about`, `/en/brand-guidelines`, `/en/privacy-policy`
+- `about` → `/fr/a-propos` / `/en/about`
+- `contact` → `/fr/contact` / `/en/contact`
+- `sponsoring` → `/fr/sponsoring` / `/en/sponsoring`
+- `brand-guidelines` → `/fr/charte-graphique` / `/en/brand-guidelines`
+- `terms` → `/fr/conditions-generales-utilisation` / `/en/terms-of-service`
+- `privacy` → `/fr/politique-de-confidentialite` / `/en/privacy-policy`
 
-## Project structure (current)
+## Project structure
 
 ```text
 /
 ├── .devcontainer/
+├── .github/
 ├── Makefile
 ├── Dockerfile
 ├── README.md
@@ -79,41 +91,37 @@ Example translated slugs:
     ├── public/
     │   ├── _headers
     │   ├── robots.txt
-    │   └── .well-known/appspecific/com.chrome.devtools.json
-    └── src/
-        ├── assets/
-        ├── components/
-        ├── i18n/
-        │   ├── ui.ts
-        │   ├── utils.ts
-        │   └── routes.ts
-        ├── layouts/
-        ├── pages/
-        │   ├── [lang]/
-        │   │   ├── index.astro
-        │   │   └── [page].astro
-        │   ├── [...blog]/
-        │   ├── home/
-        │   ├── about/
-        │   ├── contact/
-        │   ├── sponsoring/
-        │   ├── brand-guidelines/
-        │   ├── terms/
-        │   ├── privacy/
-        │   ├── index.astro
-        │   ├── rss.xml.ts
-        │   └── 404.astro
-        └── utils/
+    │   └── logos/
+    ├── src/
+    │   ├── assets/
+    │   ├── components/
+    │   ├── content/
+    │   ├── data/
+    │   ├── i18n/
+    │   ├── layouts/
+    │   ├── pages/
+    │   │   ├── [...blog]/
+    │   │   ├── [lang]/
+    │   │   ├── about/
+    │   │   ├── brand-guidelines/
+    │   │   ├── contact/
+    │   │   ├── home/
+    │   │   ├── privacy/
+    │   │   ├── sponsoring/
+    │   │   ├── terms/
+    │   │   ├── 404.astro
+    │   │   ├── index.astro
+    │   │   └── rss.xml.ts
+    │   └── utils/
+    └── vendor/
 ```
 
-## Configuration
-
-Primary site configuration: `application/src/config.yaml`.
-
-Astro framework configuration: `application/astro.config.ts`.
+## Configuration and build
 
-## Build output
+- Site and app settings: `application/src/config.yaml`
+- Astro configuration and integrations: `application/astro.config.ts`
+- Static build output: `application/dist/`
 
-Production build output is generated in:
+## CI
 
-- `application/dist/`
+GitHub Actions CI runs from the `application/` directory and builds the static site output in `application/dist`.