Help Center
Glossary
Plain-English definitions of the terms used across Seedly Sites - tenants, sections, publish vs deploy, static sites, and more.
Plain-English definitions of the words used across this documentation, alphabetized.
| Term | Meaning |
|---|---|
| Agency | The white-label parent a group of sites can belong to: its logo, color, and site allowance. Also just: you, the business running the platform |
| Block | A ready-made content piece you place in a column, like the NAP card or the HTML embed. See the Element Reference |
| Brand DNA | A site's captured brand: colors, fonts, styles, and reusable component classes, so every page you build stays on-brand. See Brand DNA |
| Build | Turning content into the finished static files a site serves. Clicking Deploy runs a build |
| Builder (visual builder) | The drag-and-arrange editor where you lay out pages from sections, rows, columns, and elements |
| CMS | Content Management System - your admin, logins, the portal, and the API. Runs as the cms service on Railway |
| Custom domain | The real domain a client site is served on (their own name, not a platform URL) |
| Deploy | Publishing a site's built files to the live internet. Deploys are deliberate: you click Deploy; publishing content alone never deploys anything |
| DNS | The internet's phonebook, mapping domain names to servers. Set at your domain registrar |
| Element | The smallest building unit on a page: a heading, a paragraph, an image, a button |
| Environment variable | A named setting or secret the platform reads at runtime. See env-vars |
| Media library | A site's uploaded images and files, stored durably in R2 and scoped per site |
| Migration (database) | A change to the shape of the database, run once when updating versions. See Updating |
| Migration / port (site) | Reproducing an existing live website inside the builder so a client can move onto your platform. See Port a Site |
| Operator | You: the login that manages every client site on the platform |
| Pages (Cloudflare Pages) | Cloudflare's static hosting. Each client site is one Pages project |
| Parity | How closely a ported page matches its source, measured by the migration pipeline's checks |
| Pixl | The Seedly Sites hedgehog, and the guided setup companion you run with npx pnpm run setup |
| Publish | Marking content live in the CMS. A published page is ready for the next deploy, but publishing by itself changes nothing on the live site |
| R2 | Cloudflare's file storage; holds the images clients upload |
| Railway | The service that runs the platform: the cms service, Postgres, and the studio |
| Row / Column | The layout grid inside a section: rows hold columns, columns hold elements. See Rows & Columns |
| Saved block / preset | A section you saved for reuse, or one of the built-in section presets. See Presets & Saved Blocks |
| Section | A full-width horizontal band of a page, and the top of the layout hierarchy. Pages are stacks of sections |
| Static site | A site served as pre-built HTML, CSS, and images, with no server code at request time. Fast by construction, and portable |
| Studio (pagebuilder) | The service that serves the visual builder and page preview; the CMS proxies to it in production |
| superAdmin | The operator-level permission that sees and manages everything on the platform. See Users & Roles |
| Tenant | One client's website inside your platform: its pages, blog, media, settings, and domain. You can host many |
| The doctor | The readiness check, npx pnpm run setup:check. Reports READY or NOT READY and names any gaps |
| Tracking script | A third-party snippet (like GA4) added to a site under its Tracking tab |
Was this page helpful?