Migrate website to Rspress and Zephyr

[zackarychapple]

Summary

• Replace the Next.js/Nextra website with an Rspress v2 site configured for Zephyr Cloud deployment.
• Move static assets under the Rspress content root and convert navigation/sidebar metadata to Rspress JSON metadata.
• Add Rspress compatibility components, client redirects for legacy routes, and a static compatibility redirect for the previously broken /docs/getting-started/getting-started.html URL.
• Replace the old Vercel footer branding with "Powered by Zephyr Cloud".
• Update the root build script so Zephyr builds the swc-site package without running the unrelated plugins app Turbo build.

Why

Zephyr needs the Rspress SSG output to include all static files. The site now builds with ssg: true, uses zephyr-rspress-plugin, and deploys the rendered doc_build output.

The broad client redirect rule for /docs was also rewriting valid docs paths into nested paths like /docs/getting-started/getting-started.html; the redirect patterns are now exact-path regexes, and that nested path has a real static redirect file for compatibility.

Validation

• pnpm build
• Zephyr deployment: https://zackary-chapple-15396-swc-site-website-swc-projec-a590b2345-ze.zephyrcloud.app
• Verified /docs/getting-started/getting-started.html redirects to /docs/getting-started.html and renders the Getting Started page.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
website	Error		Jul 8, 2026 5:33am

[vercel]

@zackarychapple is attempting to deploy a commit to the SWC Project Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​rspress/​plugin-client-redirects@​2.0.16
	zephyr-rspress-plugin@​1.1.2
	@​rspress/​core@​2.0.16
	react@​19.2.7
	react-chartjs-2@​5.3.1
	chart.js@​4.5.1
	react-dom@​19.2.7

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/next@15.4.9 → npm/zephyr-rspress-plugin@1.1.2 → npm/@rspress/core@2.0.16 → npm/sharp@0.33.5 → npm/eslint-config-next@15.3.0 → npm/@emnapi/runtime@1.11.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/zephyr-rspress-plugin@1.1.2 → npm/webpack@5.108.4 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.108.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report