---
url: "https://sites.buildspace.studio/block-library"
type: "page"
title: "The block library"
updated: "2026-08-05T00:45:11.935Z"
---

# The block library

## The block library

Reference

Thirty blocks, each one a section an editor drops onto a page. This page is built from them — every section below is an example of the block it describes.

- [Jump to the new blocks](#new-blocks)

## The seven newest blocks {#new-blocks}

These closed the gaps a survey of Wix, Webflow and Squarespace templates exposed: people, places, persuasion structures, and video. This section is itself a Card Grid in its “Icon” style.

- Team
  meta: Grid · Plain · Portrait first
  People with roles, bios and icon links. The single most common section across every template category.
  → See it on the About page: /about
- Contact
  meta: Split · Stacked
  Structured details, opening hours, a keyless map, and the form itself beside them.
  → See it on Contact: /contact
- Card Grid
  meta: 5 styles
  The workhorse. Services, locations, packages, departments, programmes — anything that links somewhere.
- Comparison Table
  meta: Plans · Competitors
  Plan against plan, or us against them. A real table on desktop; one card per column on a phone.
  → See it on Pricing: /pricing
- Timeline
  meta: Vertical · Alternating
  Dated chronology. Not Steps — that is a numbered, forward-looking process, and the two render nothing alike.
  → See it on About: /about
- Newsletter Signup
  meta: Inline · Banner · Split
  One field and one button. Posts to a form on this site, or straight to an email provider.
- Video
  meta: Inline · Full bleed
  Plays a file, not a provider iframe — which is what makes poster frames and muted background loops possible.

## The same block, in its “Image on top” style

One component with five styles rather than five near-identical blocks. That is the whole argument for the Card Grid: there is one thing to keep good instead of six to keep consistent.

- Agency & portfolio — Archetype
  badge: Popular
  The largest category on every template marketplace.
  → See the work demo: /agency-demo
  ![A row of historic gabled houses along a city canal, with a tour boat passing](/api/media/file/demo-coastal-bridge.webp)
- Local service business — Archetype
  Trust signals above the fold, services with prices, and a way to call.
  ![A red suspension bridge disappearing into coastal fog](/api/media/file/demo-mountain-sunset.webp)
- Events & community — Archetype
  A site whose front page is a calendar.
  → See upcoming events: /events
  ![Pink blossom hanging in front of a painted temple eave](/api/media/file/demo-temple-blossoms.webp)

## And in “Image with text over it”

The whole tile is the link in this style — a large image with a small “read more” inside it is a worse target on every device.

- Every block reads the theme — Theme preset
  → Theme presets: /resources
  ![Snow-covered peaks silhouetted against a burning orange sunset](/api/media/file/demo-highland-road.webp)
- Spacing and width are controls, not CSS — Appearance
  → Resources: /resources
  ![Sunlit desert badlands ridged with shadow under a deep blue sky](/api/media/file/demo-desert-ridges.webp)
- Any section can be linked to directly — Anchors
  → Resources: /resources
  ![A wide plateau of golden grass beneath snow-capped mountains](/api/media/file/demo-wide-plateau.webp)

## Questions the library gets asked

The Accordion block. It is also the FAQ block — there is not a separate one.

- How do I add a new block?
  A directory under `src/blocks/`, a `config.ts` that calls `registerBlock()`, a `Component.tsx`, and one import line in `register-core.ts`. Never edit `Pages.ts` — it builds its block list from the registry.
- Why is there no separate FAQ block?
  Because this is it. An FAQ is an accordion with different copy, and a second block would be a second component to keep good for no gain.
- Can a plugin add blocks?
  Yes, and that is how the Event List and Project Grid blocks get here. A `CorePlugin` contributes blocks the same way it contributes collections, so turning the plugin on makes its blocks appear in the builder and turning it off removes them.
- What happens to a block I remove?
  Pages that used it keep the stored data, and the renderer logs a warning in development and renders nothing. Removing a block is a schema change and ships a migration like any other.

## The Embed block, framing a video

- [The Embed block, framing a video](https://www.youtube.com/watch?v=aqz-KE-bpKQ)

_Embedded youtube content._

## The Newsletter Signup block

One field, one button. This one is wired to a real form on this site, so a submission lands under Forms with everything else — the other destination is an email provider’s own URL, which the browser posts to directly.

_An email subscription form. Submitting it requires a browser session._

## For agents

- This document: https://sites.buildspace.studio/block-library/index.md
- As JSON: https://sites.buildspace.studio/block-library/index.md?format=json
- Any page: add `/index.md`, or send `Accept: text/markdown`
- Site index: https://sites.buildspace.studio/llms.txt
- Whole site as text: https://sites.buildspace.studio/llms-full.txt