refactor: move to vite-plus workspace and prepare first release#1
Merged
Conversation
Move the host-neutral protocol, browser lifecycle, and shared styles into the private islands bridge. Compile every MDX page through one packaged Python boundary, expose the React and custom-element adapters, and use Vite+ for workspace builds and package assembly.
Configure React, Next.js, and Docusaurus through remarkMarimo, mount one shared React runtime per host, and remove checked-in compiler session output from the fixtures.
Configure Astro, Vue, and Nuxt with remarkMarimo and register the framework-neutral custom element once in each browser host.
Point Fumadocs at the repository-level docs directory, preserve the marimo tutorial corpus, and add focused installation, framework, authoring, JavaScript, and styling references.
Render the documentation beneath its Pages base path, keep server-function payloads available in the static build, mount the React island runtime with each docs page, and route the site root directly to the docs.
Lead with the page-level reactive model, add a working editor=true example, and point each supported framework to its integration fixture.
Document package ownership, the page compiler and browser lifecycle, Vite+ development commands, validation boundaries, pull request expectations, and the recurring tagged release process.
Read the runtime from the repository-level node version file, install through the pinned Vite+ setup action, and run checks, tests, and builds for pushes and pull requests.
Build the static documentation with its workspace dependencies, upload the generated site as a Pages artifact, and deploy it in a separate environment-scoped job.
Build and verify one mdx-marimo tarball, pass it between isolated artifact and publish jobs, authenticate npm through OIDC, and update GitHub release notes after publication succeeds.
Use the vp executable installed by setup-vp for checks, tests, and builds. Enable Corepack only where the release workflow needs pnpm to assemble the npm tarball.
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
1 participant
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.
Summary
@marimo-team/mdx-marimodocs, with Fumadocs acting as the renderer with tanstack instead of nextjsArchitecture
@marimo-team/islands-bridgeowns the host-neutral page protocol, custom element, asset loading, navigation, theme bridging, shared styles, and browser lifecycle.@marimo-team/mdx-marimoowns fence parsing, page identity, Node-to-Python compilation, MDX projection, and the React adapter.mdx-marimotarball.Tooling and release