Skip to content

fix(website): repair French MDX corrupted by translation sync, unblocking the v2 site build#5744

Merged
leaanthony merged 1 commit into
masterfrom
fix/v2-website-mdx-build
Jul 4, 2026
Merged

fix(website): repair French MDX corrupted by translation sync, unblocking the v2 site build#5744
leaanthony merged 1 commit into
masterfrom
fix/v2-website-mdx-build

Conversation

@leaanthony

@leaanthony leaanthony commented Jul 4, 2026

Copy link
Copy Markdown
Member

The story

wails.io has not deployed since 2026-04-06. Every Cloudflare Pages build of the v2 site (project wails) since then has failed — the live site is a frozen snapshot of the 2026-04-06 content. That's why https://wails.io/img/sponsors.svg still serves the old sponsorskit image and contributors.svg 404s, which in turn is why the credits pages (including https://v3.wails.io/credits/, which hotlinks those images) show old graphics even though #5719 and #5724 are merged.

Root cause

The docs: sync translations commit 8224d70 (2026-04-06) introduced two MDX syntax errors into the French docs:

  1. reference/options.mdx — a footnote gained literal {.footnote-backref} attribute syntax; MDX parses {...} as a JS expression and acorn fails ("Could not parse expression with acorn").
  2. guides/sveltekit.mdx — a code span lost its backticks (opening one escaped as \``, closing one dropped), leaving a bare that MDX treats as an unclosed JSX tag ("Expected a closing tag for`").

Docusaurus aborts on the first error, so only one showed per build.

Fix

Two one-line repairs restoring the structure of the English source. Verified locally: npm run build in website/ (Node 22) now completes successfully for all locales and versions.

Notes

  • Merging this should let the next Cloudflare Pages build of wails succeed and republish three months of pending content, including the new sponsors.svg / contributors.svg.
  • The nightly sponsor-image commit uses [skip ci], which Cloudflare also honours — image-only refreshes will ride along with the next regular commit to master, same as before.
  • Worth considering as a follow-up: a CI job that runs npm run build (or at least MDX-compiles) on PRs/pushes touching website/, so a bad translation sync can't silently freeze the site again; and checking whether the Crowdin source still contains the corrupt strings, in which case the next sync could reintroduce them.

Summary by CodeRabbit

  • Documentation
    • Improved French docs formatting for an inline code example in the SvelteKit guide.
    • Cleaned up a footnote rendering issue in the options reference so the note displays more cleanly.

…king the v2 site build

The 2026-04-06 'docs: sync translations' commit (8224d70) introduced two
MDX syntax errors in the French docs:

- reference/options.mdx: a footnote gained literal '{.footnote-backref}'
  attribute syntax, which MDX parses as a JS expression (acorn error)
- guides/sveltekit.mdx: a code span lost its backticks, leaving a bare
  '<page>' that MDX treats as an unclosed JSX tag

Every Cloudflare Pages build of wails.io has failed since, so the live
site has been frozen at its 2026-04-06 content (stale sponsors.svg,
missing contributors.svg, three months of docs changes unpublished).

Verified: 'npm run build' in website/ now completes for all locales.
@coderabbitai

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8ee925e5-760b-4ecf-b942-d2d16f1b62ea

📥 Commits

Reviewing files that changed from the base of the PR and between c6b6877 and 68b3f15.

📒 Files selected for processing (2)
  • website/i18n/fr/docusaurus-plugin-content-docs/current/guides/sveltekit.mdx
  • website/i18n/fr/docusaurus-plugin-content-docs/current/reference/options.mdx

Walkthrough

Minor Markdown formatting corrections were made to two French documentation files: adjusting inline code escaping in a SvelteKit guide bullet and removing stray footnote backreference HTML in the options reference page. No textual content changed.

Changes

French documentation formatting fixes

Layer / File(s) Summary
Markdown formatting corrections
website/i18n/fr/docusaurus-plugin-content-docs/current/guides/sveltekit.mdx, website/i18n/fr/docusaurus-plugin-content-docs/current/reference/options.mdx
Fixes inline code escaping for a navigation bullet and removes leftover footnote backreference HTML markup; wording remains unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested labels: reviewed ✅

Poem

Two tiny tweaks in French moonlight,
A backtick fixed, a footnote right.
No words were changed, just tidy code,
This bunny hops a lighter road. 🐇✨

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/v2-website-mdx-build

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@leaanthony

Copy link
Copy Markdown
Member Author

So sick of MDX NGL

@leaanthony
leaanthony marked this pull request as ready for review July 4, 2026 10:53
Copilot AI review requested due to automatic review settings July 4, 2026 10:53
@leaanthony
leaanthony merged commit 085944f into master Jul 4, 2026
16 of 17 checks passed
@leaanthony
leaanthony deleted the fix/v2-website-mdx-build branch July 4, 2026 10:54
leaanthony pushed a commit that referenced this pull request Jul 4, 2026
…French MDX corrupted by translation sync, unblocking the v2 site build

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR repairs MDX syntax corruption in the French v2 website docs introduced by a translation sync, unblocking Docusaurus/Cloudflare Pages builds for the v2 site.

Changes:

  • Removes invalid MDX attribute syntax appended to a French footnote definition in reference/options.mdx.
  • Restores correct inline-code backticks around a window.location.href example in guides/sveltekit.mdx to avoid MDX/JSX parsing errors.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
website/i18n/fr/docusaurus-plugin-content-docs/current/reference/options.mdx Removes the corrupted footnote backref attribute fragment that breaks MDX parsing.
website/i18n/fr/docusaurus-plugin-content-docs/current/guides/sveltekit.mdx Fixes the corrupted inline code span so MDX no longer interprets <page> as JSX.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 963 to +964
[^1]: Cela nécessite la prise en charge de WebKit2GTK 2.36+ et votre application doit être construite avec la balise de compilation `webkit2_36` pour activer le support de cette fonctionnalité. Cela augmente aussi la version minnimale de WebKit2GTK à 2.36 pour votre application.
[^2]: Cela nécessite la prise en charge de WebKit2GTK 2.40+ et votre application doit être construite avec la balise de compilation `webkit2_40` pour activer le support de cette fonctionnalité. Cela augmente aussi la version minnimale de WebKit2GTK à 2.40 pour votre application.&#160;[ [ &#8617;](#fnref2:2){.footnote-backref} &#8617;](#fnref:2){.footnote-backref}
[^2]: Cela nécessite la prise en charge de WebKit2GTK 2.40+ et votre application doit être construite avec la balise de compilation `webkit2_40` pour activer le support de cette fonctionnalité. Cela augmente aussi la version minnimale de WebKit2GTK à 2.40 pour votre application.
Comment on lines +111 to 112
- Tout ce qui provoque la navigation de page complète : `window.location.href = '/<some>/<page>'` ou le menu contextuel se recharge lorsque vous utilisez wails dev. Cela signifie que vous pouvez finir par perdre la possibilité d'appeler n'importe quel runtime cassant l'application. Il y a deux façons de contourner ce problème.
- Utilisez `import { goto } de '$app/navigation'` puis appelez `goto('/<some>/<page>')` dans votre +page.svelte. Cela empêchera la navigation de la page complète.
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.

2 participants