Migrate website from Docusaurus to Revolution + Staticalize#319
Merged
Migrate website from Docusaurus to Revolution + Staticalize#319
Conversation
Replace the Docusaurus-based website with a Revolution server that matches the pattern used by thefrontside/effection/www and thefrontside/frontside.com. - No build step: `deno run -A main.tsx` starts the server directly - No client-side router: pure server-rendered HTML - Sitemap generated from route definitions via sitemapPlugin - Staticalizes cleanly to static HTML Key changes: - Remove website/ (Docusaurus, Node.js, yarn) - Add www/ with Revolution server, Tailwind CSS, MDX pipeline - API docs generated at runtime via @deno/doc from package sources - Replace website.yaml and deploy-api-docs.yml with www.yaml workflow - Add www to deno workspace, enable nodeModulesDir for Tailwind
Contributor
Package Changes Through ebd9062There are 1 changes which include @interactors/core with patch Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
Tailwind v4 requires theme values in CSS @theme directives, not just the JS config. The font-family and color palette were not being picked up from tailwind.config.ts alone.
jbolda
approved these changes
Apr 10, 2026
cowboyd
added a commit
to thefrontside/frontside.com
that referenced
this pull request
Apr 10, 2026
No longer needed since thefrontside/interactors#319 replaced Docusaurus, which had the base URL baked into its client-side JS and required root rewriting to compensate.
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The current website is built with Docusaurus, which requires a Node.js build step, Yarn, Volta, and a separate TypeDoc build for API docs. This is out of step with how other Frontside projects (effection, frontside.com) build their websites using Revolution + Staticalize — a Deno-native approach with no build step and server-rendered HTML.
Approach
Replace the
website/directory (Docusaurus) with awww/directory using the same Revolution + Staticalize setup asthefrontside/effection/wwwandthefrontside/frontside.com:main.tsx) serves all routes with no build step — justdeno run -A main.tsxpackages/html/mod.tsandpackages/material-ui/mod.tsusing@deno/doc— no separate TypeDoc buildsitemapPluginwww.yaml) replaces bothwebsite.yamlanddeploy-api-docs.yml— serves, staticalizes, and deploys to Deno DeployVisual design preserves the Interactors brand (pink/violet/blue gradient header, Proxima Nova, navy text) while converging on the effection structural patterns (sticky gradient header, grid footer, tailwind utilities).
Alternate Designs
Could have kept Docusaurus and just updated the deployment, but that would not satisfy the "no build step" constraint and would remain inconsistent with the other Frontside web properties.
Possible Drawbacks or Risks
TODOs and Open Questions
interactorsaccepts the new deploymentDEPLOY_API_HTML_V1/DEPLOY_API_MUI_V4secretsLearning