Commit provider code
Connect
SPIRITT
PlasmicPlasmic
Visual pages, wired to your app
SPIRITT connects Plasmic to the real app behind it. It writes your React providers, generates the global context configuration for the Plasmic loader and ships the code, so visual pages run with live auth, data and state.
What you can do with Plasmic.
Providers registered correctly
Generate the globalContexts configuration for your Plasmic loader from the providers you define.
Real app state for designers
Expose auth, carts, themes or feature flags so Plasmic pages work with live context.
Shipped, not just snippets
SPIRITT writes the providers, commits the setup and deploys it with your app.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the Plasmic-powered site or app you are building.
02
Connect Plasmic
Connect Plasmic, plus the repository and hosting your app runs on.
03
Delegate an outcome
Say what designers should be able to use in Plasmic. SPIRITT builds the providers, registers them and ships.
Hand over a mission.
Choose a mission. Make it yours.
Put Plasmic to work.
Visual pages, wired to your app
Questions
Plasmic, with SPIRITT.
01What does the Plasmic connection do?+
It generates the globalContexts configuration for the Plasmic loader from the list of providers you want registered.
02Can it add new actions later?+
Yes. When your app gains a feature, SPIRITT writes the provider, regenerates the globalContexts config and redeploys, so designers can use it right away.
03What can a global context give designers?+
Any data or action your React provider exposes, such as login state, a cart, a theme, flags or form submission.
04Which apps does this fit?+
React apps that load Plasmic pages through the Plasmic loader, including Next.js projects.
05Can it deploy the result?+
Yes. With your repository and hosting connected, SPIRITT commits the change and deploys it.
06Do I need a developer for this?+
No. SPIRITT writes the provider code, registers it and ships it.