Webflow

Every page uses one fictitious scenario, Fernbrook Gardens, a botanical garden whose site is built step by step. The site has Home, Visit, Plants, Events, Shop, Garden Journal, About and 404 pages and a password-protected Volunteers area. Its design system holds a brand variable collection with Day and Night modes, utility classes and the PlantCard, EventBanner and SiteHeader components. Its CMS holds Plants, Zones, Events, Journal and Staff. Operations add a group-visit enquiry form, Spanish and German locales, redirects from an old site and a seed shop. The developer work adds fernbrook-sync, a Node.js and TypeScript script (with a Python variant) that imports plants from a fictitious nursery feed, a webhook receiver, and Plant Label Kit, a Designer Extension that grows into a hybrid app. No real names, tokens or credentials appear anywhere; secrets are always placeholders.

Webflow is software as a service and has no version numbers, so its facts are dated: everything in this sub-section was checked against the official documentation on 2026-10-28, and plans are named by tier only (Starter, Basic, Premium, Team, Enterprise and the Ecommerce tiers) without prices. The developer examples are pinned to these versions:

Product Changes and Deprecations explains how to follow what has changed since the check date.

Every source below is the official site, repository, standard or documentation page of the product, library or service it supports, and each entry links to it. The links were collected on 2026-10-28 from the == References section of every page in this sub-section, where each page lists the exact pages its facts and examples derive from. Webflow publishes no version numbers, so its sources are dated rather than versioned, and its documentation changes often: open an entry and confirm its content, plan names and limits before you rely on it. Where this bibliography and a page’s own == References section appear to disagree, the official documentation linked from the page wins.