Skip to content

Release v1.2.0#128

Merged
wazolab merged 48 commits intomainfrom
develop
Apr 1, 2026
Merged

Release v1.2.0#128
wazolab merged 48 commits intomainfrom
develop

Conversation

@wazolab
Copy link
Copy Markdown
Member

@wazolab wazolab commented Apr 1, 2026

Summary

Release develop → main for v1.2.0

Highlights

  • Mobile sidebar navigation for docs and header
  • CTA button linking to Clearance app
  • SVG schema mobile fallback
  • Responsive fixes across footer, cards, steps, typography, and spacing
  • Docs restructure with prev/next navigation
  • Full FR/EN/ES content for 'how-it-works' section
  • Lighthouse CI integration
  • Various content and bug fixes

wazolab and others added 30 commits March 26, 2026 22:42
The raw <img> tag did not prepend NUXT_APP_BASE_URL, breaking logos
when deployed under a subpath (e.g. /clearance-website/ on GitHub Pages).
Add a parallel Lighthouse CI job that runs performance, accessibility,
best-practices, and SEO audits against the generated static site.
Thresholds set at 0.9 for all categories.

Closes #82
useI18n() in the root component has no parent scope, causing
"Not found parent scope" warning. Explicitly set useScope: 'global'.
- Audit 3 distinct page layouts: home, contact, and docs
- Downgrade performance assertion to warn (CI runner variance)
- Document intentional NUXT_APP_BASE_URL omission in workflow
Parse LHCI assertion results and open an issue with failure details,
report links, and run context when the audit fails.
treosh/lighthouse-ci-action doesn't accept githubToken. Use a dedicated
step that parses manifest.json and posts a score table as a PR comment.
Parse scores from manifest.json summary field instead of individual
report files. Filter to representative runs only (median of 3).
feat(ci): add Lighthouse audit to CI pipeline
Update nav labels, docs index titles/descriptions, and landing page
secondaryLabel across all 3 locales (fr, en, es).

Closes #84
docs(i18n): rename nav label from 'Documentation' to 'How it works?'
- Delete 1.getting-started/ directories (all 3 locales)
- Delete 2.going-further/4.roadmap.md (moved to how-it-works)
- Create 1.how-it-works/ with 6 placeholder pages per locale
- Update routeRules redirects: /docs → how-it-works/replication
- Add legacy redirects for getting-started/overview
- Update prerender routes to match new structure

Closes #85
docs: restructure page hierarchy for 'how-it-works' section
Write all 6 French documentation pages from the reference text:
- replication: réplication OSM sous contraintes de qualité
- locha: validation contextuelle et groupes de changements logiques
- semantic: lecture sémantique des changements
- rules: les 7 validateurs configurables
- feedback-loop: boucle d'amélioration continue
- roadmap: évolutions à venir

Closes #86
docs(fr): write FR content for 'how-it-works' section
Translate all 6 documentation pages from FR to EN:
- replication, locha, semantic, rules, feedback-loop, roadmap

Closes #87
docs(en): translate 'how-it-works' section to English
Translate all 6 documentation pages from FR to ES:
- replication, locha, semantic, rules, feedback-loop, roadmap

Closes #88
docs(es): translate 'how-it-works' section to Spanish
Fix broken links after directory restructure:
- getting-started/* → how-it-works/*
- going-further/roadmap → how-it-works/roadmap

Updated across all 3 locales (fr, en, es).

Closes #89
docs: update cross-links in 'going-further' section
Add { useScope: 'global' } to all useI18n() calls in pages, layouts,
and components to suppress intlify SSR warnings.

Add ESLint rule to prevent bare useI18n() calls without useScope in
future code.
The warning comes from vue-i18n internals during SSR, not from our
code. The useScope: 'global' option and ESLint rule did not suppress
it. Revert to clean useI18n() calls.
Use queryCollectionItemSurroundings and UContentSurround to provide
automated prev/next page navigation on all docs pages, replacing
the manually maintained cross-link sections.

Closes #105
Request 2 items in each direction from surround API and skip
redirect/index pages, so cross-section navigation links to actual
content pages. Also revert unrelated blank line additions to index.md
files.
feat(docs): replace See Also sections with prev/next navigation
Filter surround results to only include pages within /docs/,
preventing the contact page from appearing as prev link on the
first docs page.
Display a friendly error page with the app header/footer, a large
status code, localized message, and a back-to-home button.
wazolab and others added 15 commits March 31, 2026 16:53
* fix: add mobile navigation drawer to header

Add #body slot to UHeader with vertical nav items and language
switcher. Set mode="drawer" for a slide-up panel on mobile.
Hide horizontal navigation below md breakpoint.

Closes #107

* refactor: extract language switcher into AppLanguageSwitcher component

* fix: remove language switcher from mobile drawer
- Remove slug.test.ts: tests expected inline fallback removed in be65063
- Fix lighthouserc.cjs: replace non-existent getting-started/overview
  with valid docs path (how-it-works/replication)
- Guard CI issue-creation step against missing LHCI results
- Add tests sync guideline to CLAUDE.md

Closes #109
Remove the 2.going-further directory and all its pages (integration,
deployment, references) across all locales (en, fr, es) and clean up
the corresponding prerender routes in nuxt.config.ts.

Closes #111
* feat: add CTA button in header nav linking to Clearance app

Add an "Open App" button in the header navigation that links to
https://clearance.teritorio.xyz. The button appears on both desktop
(between the nav menu and the language switcher) and in the mobile
drawer. Includes i18n translations for all three locales.

Closes #114

* fix: add rel="noopener" and close drawer on CTA click

- Add rel="noopener" to both CTA buttons for security
- Close the mobile drawer when the Open App button is clicked,
  since external links don't trigger a route change
…#117)

Replace h3 headings + paragraphs with a compact bullet list for the
validators section across all three locales.

Closes #116
…rm, and docs layout (#125)

Closes #118, closes #121, closes #122, closes #123, closes #124
Add a USlideover triggered by a menu button visible below lg: breakpoint,
containing the same docs navigation. Auto-closes on route change.

Closes #119
Hide the SVG diagram below sm: and show a simplified vertical flow
using HTML elements that remains legible on small screens.

Closes #120
Replace duplicated section title with Clearance logo + name in the
slideover header. Add visually hidden description to resolve Reka UI
DialogTitle/DialogDescription accessibility warnings.
…mit button width

- Add responsive padding and gap to UContentSurround for mobile
- Add top margin to separate surround from content
- Revert full-width submit button on contact form (bad UX)
When a PR targets develop, both push and pull_request triggers fire,
running every job twice. Add concurrency group keyed on PR number
(or ref for direct pushes) with cancel-in-progress to ensure only
one run per event.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

Lighthouse Report

URL Performance Accessibility Best Practices SEO
/fr 55 96 100 100
/fr/contact 87 96 100 100
/fr/docs/how-it-works/replication 79 94 100 100

PR number vs ref gave different keys for push and pull_request events
on the same commit. Using SHA ensures both triggers for the same commit
share a group, so one gets cancelled.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

Lighthouse Report

URL Performance Accessibility Best Practices SEO
/fr 56 96 100 100
/fr/contact 87 96 100 100
/fr/docs/how-it-works/replication 78 94 100 100

github.sha is a temporary merge commit for pull_request events, so
push and pull_request for the same commit got different keys. Use
pull_request.head.sha (falls back to github.sha for push events)
to correctly deduplicate.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

Lighthouse Report

URL Performance Accessibility Best Practices SEO
/fr 55 96 100 100
/fr/contact 85 96 100 100
/fr/docs/how-it-works/replication 79 94 100 100

Only trigger CI on pull_request events. This eliminates the duplicate
runs that occurred when both push and pull_request events fired for the
same commit on a PR.
@wazolab wazolab merged commit 254d03a into main Apr 1, 2026
2 checks passed
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

Lighthouse Report

URL Performance Accessibility Best Practices SEO
/fr 53 96 100 100
/fr/contact 85 96 100 100
/fr/docs/how-it-works/replication 78 94 100 100

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

Lighthouse Report

URL Performance Accessibility Best Practices SEO
/fr 54 96 100 100
/fr/contact 86 96 100 100
/fr/docs/how-it-works/replication 75 94 100 100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant