Everything it does, in detail
This page is long because the product is. Nothing below is a roadmap item — it is what happens when you type a sentence into the box on the home page.
From a sentence to a sitemap
Nothing here is a template being filled in. The model reads what you wrote, works out what kind of business it is, and designs a site for it from a blank start.
Whole-site planning
It returns routes, not a page. A clinic gets services and contact pages; a studio gets work and process; a product gets pricing and an FAQ. The sitemap is part of the answer, not something you assemble afterwards.
Copy written in context
Headings, body text, list items and calls to action are written for your business — your services, your audience, your tone — rather than pasted from a generic pool and lightly renamed.
Design chosen to match
A palette and a type pairing are selected for the sector, then applied as design tokens across the whole site. Change either one later and everything follows.
Structure decided per page
How much to explain, where proof belongs, when to ask for the enquiry — worked out from your description rather than applied from a fixed running order.
It never returns nothing
Hallucinated section names, malformed content, duplicate singletons, an API outage — every failure path resolves to a working document with a note about what was substituted. The floor is a usable site.
Deterministic identity
Section ids are minted locally, never by the model, so a retried completion cannot produce two sections claiming to be the same one.
Templates as a second door
Prefer to start from something concrete? A template produces the identical shape of site and joins the flow at the same point, so nothing about the rest of the product changes.
Output with the details already handled
The reason a generated page usually looks generated is that the small things are missing. These are the ones the model does not get to skip, because they are built into everything it can produce.
Genuinely different structures
Two businesses described differently get pages that are laid out differently — not the same running order in another colour. That is the difference between designing and recolouring.
Content-preserving redesigns
Ask for another treatment of any part of the page and your words come with it. Only the design changes, so exploring costs you nothing you have already written.
Mobile-first, every layout
Phone, tablet and desktop are three designs, checked at each width. Nothing is a desktop layout squeezed down at the last minute.
Motion that was designed in
Fade, rise, blur, zoom, tilt and staggered children, all as CSS keyframes behind a reduced-motion guard — and they survive publishing and export intact.
Both colour schemes, always
Everything references design tokens rather than fixed colours, which is what lets one site render correctly in light and dark without a second set of layouts.
Clean semantics underneath
One landmark per region, a single h1, headings in order. It sounds pedantic until you meet a generated page whose outline is forty nested divs deep.
Direct manipulation, with guardrails
The canvas is the site. There is no separate preview to fall out of sync, because the editor and the published page render from the same document through the same components.
Inline text editing
Click a heading and type. Text edits happen on the canvas rather than in a side panel, so you are always looking at the real typography at the real size.
Drag to reorder, insert anywhere
Sections drag into place, and there is an insert point between every pair of them. Adding a testimonial block halfway down a page is two clicks.
Per-element overrides
Select any element and adjust typography, fill, effects, spacing, layout, size and offsets — separately for phone, tablet and desktop, and separately for the hover state.
Complete undo history
Every mutation goes through a single reducer, which is what makes undo trustworthy. There is no shortcut path that silently drops a change from history.
Snapshots you can restore
Save a version of the whole site before an experiment and roll back to it if the experiment does not work out.
Multi-page, with real SEO fields
Add pages, rename routes, and set a title and description per page rather than one for the whole site.
Layers panel
A long page is easier to navigate as a list than as a scroll. Jump to any section, see what is selected, and reorder from there.
True-width responsive preview
Phone, tablet and desktop are rendered at their real widths and scaled to fit, so the desktop breakpoint actually fires. Fitting the frame to the space instead is how a builder shows you a layout your visitors will never see.
Image picking without a download
Search stock photography or upload your own, and drop it straight into an image slot.
Tokens, not hardcoded colours
The theme is a small set of custom properties every section reads. That indirection is what makes a palette switch instant and a dark mode real rather than an inverted screenshot.
Six palettes, light and dark
Each palette defines both schemes together. A section that reached past the tokens for a fixed colour would break the toggle, so none of them do.
Six type pairings
A display face and a text face chosen to work together, loaded only on the pages that use them.
Radius and motion settings
Corner rounding and whether entrance animations run at all are site-level switches, not per-section decisions you have to remember to repeat.
Overrides that clean up after themselves
Clearing a style deletes the key rather than storing an empty value. A section styled and then un-styled is byte-identical to one never touched, so no dead CSS ends up in your published pages.
Static output, nothing to boot up
A published Framewise site is HTML with the stylesheet inlined. There is no framework to download, no hydration step, and nothing between the visitor and the content.
Zero JavaScript bundle
The mobile navigation and the FAQ accordions use native HTML elements. Entrance animations are CSS. The only script on the page is the few lines that set the colour scheme before first paint.
No flash of the wrong theme
That pre-paint script is why a visitor who prefers dark mode never sees a white page first.
SEO files generated for you
Per-page titles and descriptions, Open Graph tags, sitemap.xml, robots.txt, and a favicon derived from your brand colour.
Private share links
Send a link to a client or a colleague before the site is public, and revoke it when you are done.
Custom domains
Start on a Framewise address and point your own domain at it when you are ready.
A codebase, not a zip of HTML
Export writes a real Next.js project into your own GitHub repository. If you never come back, the site keeps working and the code keeps making sense.
One component per section
Readable TypeScript React components composed by the page, not a single file of generated markup. You can open any one of them and change it.
The whole project
package.json, tsconfig, next.config, PostCSS, globals.css, the app router files, a README and a .gitignore. Everything needed to run npm install and npm run build.
No Framewise dependency
Nothing in the exported project imports anything of ours. We prove it by generating an export in CI and building it from scratch.
Private by default
The repository it creates is private unless you say otherwise.
The parts you should not have to think about
Performance, accessibility and privacy are not features you turn on. They are decisions made once, at the bottom of the stack, so that every site produced inherits them.
Accessibility
Semantic landmarks, a single h1 per page, labelled controls, visible focus rings, and colour pairings checked for contrast in both schemes.
Reduced motion, honoured properly
The hidden starting state of every animation lives inside the prefers-reduced-motion query. Get that backwards and a reader who asked for stillness gets a blank page instead.
Ownership enforced by the database
Project access is decided by row-level security on every query, not by application code remembering to filter. Even the admin panel reads through it.
Analytics without addresses
Visitor IPs are salted and hashed before storage, and dropped entirely when no salt is configured — an unsalted hash of an IPv4 address is reversible, which makes it a record dressed up as anonymised data.
Graceful degradation everywhere
Each integration checks its own configuration and fails on its own. A missing key takes out the feature that needs it, never the pages that do not.
A few more answers
The general questions live on the home page FAQ. These are the ones specific to what the product can and cannot do.
- No account required to generate a site
- Nothing you build is locked to us
- Every plan can export
Can I use Framewise for client work?
What if I need something genuinely custom?
Does the editor work on a tablet?
What happens to my site if I stop paying?
Reading about it takes longer than doing it
One sentence, about eight seconds, and a complete site to argue with.