SITE EDITOR · LIVE ON PRODUCTION

Edit the live
production app.
Right where it runs.

No CMS. No staging. No tickets. Marketing edits copy, images, layouts, multi-language fields and audience variations directly on the running site.

In-context CMS

The editor lives inside
your running app.

A traditional CMS is a separate tool that stores content. The Site Editor is a panel inside the deployed app. You see the production page, click any element, change it.

Traditional CMS / Headless setup

Edit a copy of the data.
Hope it shows up right.

Marketing logs into a separate admin. Updates a field. Triggers a build. Waits for staging. Asks dev to deploy. Refreshes production. Discovers the layout broke.

Marketing
CMS admin tool 2
API / build tool 3
Live site
Weezzi Site Editor

Edit the page itself.
Changes are live.

Authorized users open the running app, switch to Edit mode, click any element, change it. The application model updates. The page reflects it. No staging. No build. No tickets.

Marketing
Site Editor (in-context) live
Live site
Capabilities

Everything marketing needs
to operate the live app.

Eight surfaces, one editor. Built into the application, not bolted on.

01 · CONTENT

Inline content editing

Click any text on the live page and rewrite it. Headlines, body copy, CTAs, microcopy — all editable in place.

02 · MEDIA

Image & media swap

Replace photography, illustrations and video posters without leaving the page. Crops, alt text and responsive variants travel with the asset.

03 · LAYOUT

Layout adjustments

Reorder sections, swap component blocks and adjust spacing. Production stays consistent — the app model enforces the rules.

04 · LOCALE

Multi-language fields

Every editable field is locale-aware. Switch language, edit, publish. Translation memory and missing-locale flags surface automatically.

05 · VARIANTS
A
B
C

A/B testing

Create variations on any block, split traffic, watch the winner emerge. Statistical significance computed live; promote with one click.

06 · PERSONALIZATION
enterprise
SMB · returning
trial day-7
EU buyer
audience

Audience variations

Show different content to different segments — by source, geography, account type, lifecycle stage, or any signal in the application model.

07 · SCHEDULE
M
T
W
T
F
S
S
1
2
3
4
5
6
7
8
9
10
11
12
13
14

Scheduled publishing

Queue content drops for product launches, sales windows and seasonal campaigns. Scheduling is per-locale and per-audience.

08 · WORKFLOWS DRAFT REVIEW APPROVED LIVE

Approval workflows

Optional draft → review → approve → publish gates per content type. Roles, permissions and audit trail are part of the application model.

Insights on the canvas

See what works.
Change it on the spot.

Heatmaps and engagement metrics overlay the page you're editing. The decision and the change happen on the same canvas.

Heatmap Clicks Scroll
Last 7 days · 24,381 sessions
Get started → Watch demo
CTA · 8.4% CTR
Card 2 · 1,240 clicks
Page engagement
68.2% ↑ 4.1pp
Hero CTA — variant B
+18% vs control
Avg. time on page
2:14 ↑ 22s
Interest system

Every action is a signal.
The page learns who's reading.

The interest system observes what each visitor reads, clicks, opens and skips — building an interest profile inside the application model. Marketing uses those signals to shape what each visitor sees next.

  • Page views, dwell time, scroll depth, repeated visits
  • Tagged content categories — products, topics, industries, content types
  • Manual signals — newsletter sign-ups, downloads, content saves
  • Interests feed personalization, recommendations and segmentation
Visitor · sess #4821
Observed activity
read pricing
visit ×3
scroll 80%
click demo
Inferred interests
SMB tier
price-sensitive
demo-ready
Page action
show SMB testimonial
surface "book demo" CTA
Bronze · welcome
earned
★★
Silver · returning
620 / 1000 pts
★★★
Gold · advocate
340 / 1000 pts
Inner circle · invite-only
locked
Loyalty system

Reward the behaviour
you want more of.

The loyalty system tracks points, tiers, badges and benefits as part of the application model. Marketing decides what counts, what unlocks, and what each tier sees on the live site.

  • Points for any application event — purchase, referral, content engagement
  • Tiers, badges and benefits configured directly from the editor
  • Tier-aware content — show locked content, exclusive offers, perks per tier
  • Newsletter, email and in-app messaging segments by tier
Who uses it

Built for the people who
actually run the site.

Marketing, content and operations — three roles, one editor, zero developer tickets between them and the live page.

Marketing

Owns the funnel. Ships campaigns, launches pages, runs experiments — all on the live production app.

  • Launch landing pages and campaigns same-day
  • Run A/B tests and personalization without engineering
  • Read engagement metrics on the same canvas as the edit

Content & editorial

Owns the words and the locales. Drafts, translates, schedules, publishes — across every market.

  • Multi-language editing with translation memory
  • Draft → review → approve workflows per content type
  • Content calendar across audiences and locales

Ops & agency PMs

Manages clients, retainers and post-launch life of the product. The editor is what they hand off — not a dev backlog.

  • Hand the live editor to clients with safe, scoped permissions
  • Audit trail, rollback, and version history per element
  • Build retainers around content, optimization and personalization
How it differs from a CMS

Same job. Different
place to do it.

A CMS sits beside the app. The Site Editor sits inside it. That single architectural choice changes everything downstream.

Capability
Traditional CMS / Headless
Weezzi Site Editor
Where you edit
Separate admin tool
The running production page itself
Time to publish
Build + deploy cycle
Click → save → live
Layout safety
Edits can break the page
Application model enforces structure
Multi-language
Plugin or separate vendor
Native field-level locales
A/B testing
Bolt-on tool (extra contract)
Built into every editable block
Personalization
Separate engine, integration project
Native to the application model
Heatmaps & analytics
Hotjar / GA4 / Mixpanel — separate
Overlay on the canvas you're editing
Loyalty & interests
Custom build, often skipped
First-class part of the platform
Developer tickets per change
Many
Zero, by design
Pilot · Q2 2026

Stop opening tickets.
Start editing the live site.

Join the pilot and put the Site Editor in front of your marketing team this quarter.