Docs

Changelog

Release history and platform updates for Seedly Sites.

A record of major updates and improvements to Seedly Sites. The most recent changes appear first.

v1.0 (June 2026) - First Release#

The initial release of Seedly Sites: the full platform, proven in production on real client sites before it shipped.

Multi-tenant CMS: unlimited client sites (tenants) managed from one operator login, with per-tenant pages, blog, media, redirects, tracking scripts, locations, and settings
WordPress-style roles (Administrator, Editor, Author, Contributor, Subscriber) plus per-tenant role overrides and a separate deploy permission, enforced at the data layer
White-label delivery: branded client login, no powered-by badge on published sites, custom domain per client
Operator portal: dashboard, per-site management, activity log, backups, and metrics

Drag-and-drop builder on a Section, Row, Column hierarchy with 40 element and block types, including a local-business pack (NAP, hours, service area, service, click-to-call, map)
Native style fields throughout: per-breakpoint column widths, section styles and mobile-first padding, heading and text controls, responsive visibility
16 built-in section presets plus a saved-blocks library for your own reusable sections
Header and footer built in the same builder, with a sticky-header option and mobile drawer navigation
Builder-editable system templates: 404, blog archive, and single post

Pages with drafts, scheduled publishing, password protection, an internal-link picker, and a content and SEO analysis panel
Blog with categories, tags, rich-text editing, and author profiles with real author archive pages and structured data
Per-page SEO fields, local-business structured data, automatic sitemaps and robots controls, redirects with a 404 monitor, and broken-link and orphan-page detection
First-party, consent-gated Website Analytics Dashboard: click maps, scroll depth, attention maps, campaign and UTM attribution, bot watch, and experimental A/B tests (off by default)

Static rendering to one Cloudflare Pages project per client site, provisioned automatically, with media on R2
Manual, operator-controlled deploys with a per-page readiness gate; publishing never silently changes a live site
Per-site sitemap, robots rules, and redirects regenerated on every deploy
Platform preview URLs kept out of search engines so only the client's real domain ranks

The migration pipeline: crawl an existing site and reproduce it closely in the builder, with a deterministic content-parity gate, a visual-difference signal, and a triage board for review
Ports land as drafts and never publish or deploy automatically

Native Stripe billing per tenant: hosted checkout, customer portal, an operator billing dashboard, and configurable non-payment enforcement (freeze editing or suspend the site), with per-tenant overrides

Guided setup with Pixl: a local sandbox first (no accounts required), then provisioning for Railway, Cloudflare Pages, R2, and GitHub, with a doctor command that diagnoses problems in plain English
Numbered setup handbook, operations playbooks (backups and disaster recovery, updating, data export), and a command and environment-variable reference

Was this page helpful?