A few days ago I wrote about Impact Studio — the offline-first visual builder I am building for solo creators and small studios. The product itself is still in development. But the brand needed a real address on the web.
On June 26, 2026, I set up impactstudios.app with a simple coming soon page. Nothing fancy. Just a clear placeholder while the builder matures.
Same workflow, separate repos
This follows the publishing model I have been describing for Impact Studio itself: the product repository (impactstudio) is not what goes to Cloudflare. The site repository (impactstudios-site) holds static HTML only. Push to GitHub, Cloudflare Pages deploys, custom domain attached, DNS handled automatically.
That separation matters. The app source stays private and messy in the ways real software is messy. The public site stays small, portable, and easy to replace when Impact Studio can publish marketing pages on its own.
What is next
For now it is a holding page. When the builder can export and publish real sites, this repo will be the first candidate for a proper marketing site — designed in Impact Studio, rendered to static files, pushed to GitHub, live on Cloudflare.
Until then, impactstudios.app is proof that the boring path works: own the domain, own the repo, own the deploy.
Status: coming soon page live — June 26, 2026. Site repo: github.com/stevel4857/impactstudios-site