Your live-inheriting starter site (Arrival board)

The Starter Site lane on the Arrival Board picks the canonical live-inheriting Site Template for your vertical and offers it as a one-click install when you create your org. You don't open the Builder to an empty canvas — your site comes up populated with the same theme, pages, and blocks as every other org in your vertical, and stays in sync with the template author's updates over time.

The two toggles:

• **Install on create** — default ON. Unchecking means your new org gets the empty-canvas experience instead. You can still install any template from the Marketplace later.

• **Live inheritance — ON** — default ON. When the template author publishes an updated version (a new homepage block, refreshed copy, a redesigned footer), your site receives the update automatically through the onSiteTemplateWritten Cloud Function. Pages you edit locally are preserved — only blocks that haven't been customized inherit. Flip OFF to fork your site as a one-shot snapshot at install time.

How "live inheritance" actually works:

Every Page in a template carries a stable templatePageId. When the upstream template version bumps, the fan-out trigger walks every inheriting site and matches pages by templatePageId — adding new ones, updating ones you haven't touched locally, and leaving locally-authored pages alone. You can flip live inheritance OFF at any time from the Builder editor (Site settings → Live updates toggle); turning OFF doesn't break your site, it just stops receiving updates.

How a template becomes "featured":

A platform admin marks one template per vertical (Restaurant, Lodging, Outdoor, Retail, Services, Federal, Nonprofit, Events, Portfolio) with the isFeaturedForVertical flag. The Arrival board uses that pick by default. If no template is featured for a vertical yet, the Arrival board falls back to the highest install-count public template — still a useful starting point, but the live-inheritance promise depends on the author actually maintaining the template, so featured picks are the curated choice.

What if I don't like the featured pick?

After your org is created, head to /marketplace?view=templates and install a different one. Your existing Builder site stays put — install a different template into a fresh site, or use the "Save as template" path to fork from someone else's start.

Why default ON?

Live inheritance default-on is how Turtini ships fresh-looking sites for free. A Wix-style refugee who built their old site once and never touched it gets a Turtini site that keeps improving as the template author iterates — same effort, better outcome over time.