Instead of beginning with an empty canvas, you choose a website whose pages, sections, visual system, and supported capabilities are already designed to work together. You can then adapt its content, imagery, styles, navigation, and supported structure without rebuilding the site from scratch.
A site license activates one website. Eligible licensed websites can be saved, versioned and exported without a recurring StackLiberate builder subscription. Publishing remains a separate service and is not currently enabled.
The StackLiberate model
A StackLiberate website begins with a template.
Templates are more than visual themes. Each one defines a complete starting website: its pages, sections, navigation structure, design system, editable content, and the structural changes that website supports.
This gives the editor a clear contract for how the website can change.
Rather than treating everything visible on the page as freely mutable, StackLiberate exposes the content and structural operations the selected website supports. That keeps changes predictable as the website moves through editing, saving, versioning, publishing, and export.
The basic workflow is:
Choose a website → customize it → activate it when licensing is available → save and version your work → export portable output. In-app publishing and updates will be added through the separately enabled Publish service.
Start from a complete website
Choose a starting website based primarily on the structure you want to end with.
A template may contain one page or several pages depending on its purpose. Its page architecture, sections, navigation, styling, and supported behaviors are designed as one system rather than assembled from unrelated pieces.
You are not choosing placeholder text or colors permanently. Those are meant to change.
You are choosing the underlying website: its information architecture, available sections, supported editing capabilities, and overall design direction.
This is why selecting the right starting point matters more in StackLiberate than choosing an empty canvas and building upward from it.
Learn how to choose a website →
Customize within the website’s supported structure
StackLiberate lets you change the parts of a website that its template defines as editable.
Depending on the website, that can include:
- text and rich content;
- images and branding;
- links and calls to action;
- colors and typography;
- page titles, URLs, and navigation;
- sections and their order;
- repeatable content such as services, team members, or testimonials.
Structural editing is template-aware.
When StackLiberate allows a section to be added, moved, hidden, or removed, that change remains part of the website's actual structure. The same principle applies to supported repeatable content and global website elements.
This is different from arbitrary canvas manipulation. The goal is not to expose every possible mutation of the page. It is to make meaningful changes while preserving a website that remains coherent throughout editing, saving, publishing, and export.
Activate your website
A site license activates one website.
Activation moves the website into its licensed workflow, where its editable state can be persisted and reopened as an ongoing StackLiberate website.
Site licenses are one-time purchases. A licensed website does not require a recurring StackLiberate builder subscription to remain editable.
The license belongs to the website it activates rather than functioning as a recurring account subscription.
This distinction becomes especially important when working with multiple websites or building websites professionally.
Learn about site licenses → (guide planned)
Save, version, and restore your work
StackLiberate treats the website as a complete editable state rather than a collection of unrelated page changes.
As you work on a licensed website, its supported content, structural changes, and website-wide settings can be persisted together.
StackLiberate also separates two different kinds of history:
Undo and redo are for navigating recent editing actions while you work.
Versions are durable snapshots of the website that can be returned to later.
Restoring a version makes that earlier website state current again without turning version history into a destructive overwrite.
This separation makes immediate editing history useful without asking it to serve as the long-term history of the website.
How saving works → (guide planned)
Learn about versions → (guide planned)
Publish your website
In-app publishing is not yet available in this rollout. Vercel is the selected provider for the approved publishing design.
The approved design is Publish Now on StackLiberate’s Vercel account, then a separate customer Claim, followed by customer OAuth and updates to the same project. That workflow has not been implemented or validated end to end; it is not a set of available interface steps.
Hosting duration and final service terms remain to be settled before opening the service. ZIP export stays independent of Vercel and can be hosted on compatible infrastructure under your control.
Publish your website → (guide planned)
Keep editing and publish updates
Publishing does not end the editing lifecycle.
Editing and saving do not automatically update an external website. You can continue to edit an eligible licensed site and export its updated files; a future in-app republish will remain a separate confirmed action.
This creates a simple lifecycle:
Edit → save → export; publishing is a separate step, not a synonym for saving.
The intended in-app republish flow will reuse the existing project after Claim and OAuth. Do not create a second project to resolve an uncertain publication result.
Update a published website → (guide planned)
Export a portable static website
Export is a first-class part of StackLiberate.
When you export a website, StackLiberate materializes the current website state into ordinary static website files, including the HTML, CSS, assets, internal links, and supported website behavior needed by the exported site.
Editor-specific metadata and the StackLiberate editing runtime are not part of the customer-facing website output.
That means the exported website does not require the proprietary StackLiberate application runtime to operate. It can be hosted outside StackLiberate using infrastructure you control.
A website may still use external services intentionally—for example, an external link, map, form destination, or another third-party service configured as part of the site. Portability does not mean removing services the website was intentionally designed to use.
Learn about export → (guide planned)
Own and control the website
StackLiberate keeps several concepts separate because they represent different things:
- the website you edit;
- the site license that activates it;
- the account that owns or has access to it;
- the exported website files;
- the infrastructure where the live website is hosted.
They are related, but they are not the same object.
This separation is intentional.
It allows StackLiberate to provide an editor without requiring the finished website to exist permanently inside a proprietary StackLiberate hosting runtime.
It also creates a foundation for professional workflows where website ownership, editing access, licensing, and client delivery can be handled as distinct responsibilities rather than being collapsed into a single account relationship.
Understand website ownership → (guide planned)
Where to go next
If you are creating your first StackLiberate website, continue with Choose a website.
If you already have one open, see Edit your website.
To understand what changes after activation, read Site licenses (guide planned) and How saving works (guide planned).
When you are ready to make the website live, continue to Publish your website (guide planned).
And if portability and independent ownership are important to your workflow, see Export your website (guide planned) and Website ownership (guide planned).