Reusable blocks for every Builder project

Start each Builder project from ready-made interface blocks, a full project template, or the components that your colleagues and the Builder community publish to the gallery.

Start from blocks that already work

Builder Components gives you the pieces that an app commonly needs before it can do anything specific to your organization, such as a login form, a navigation bar, a dashboard layout, and a data table. Each piece comes as a tested, responsive block that you can drag into a project and customize, or as part of a full project template. When you build a client portal, you can start from a template that already connects the sign-in, the data tables, and the file management.

Start every project from patterns that already work

Builder Components gives your team ready-made blocks, full project templates, and a gallery of components that your colleagues and the Builder community publish. The steps below show how a project comes together from those pieces.

What you can start a project from

UI blocks for common patterns illustration

A web app usually needs navigation menus, form fields, data tables, card layouts, and modal dialogs. If you rebuild them for every project, you will spend the start of each project on work that every other project repeats.

Builder includes ready-made blocks for authentication forms, navigation bars, sidebars, data tables with sorting and filtering, card grids, file upload areas, image galleries, pricing tables, testimonial sections, and footer layouts. You can drag a block into your project, change its content and styling, and then spend your time on the parts of the app that serve your organization alone.

A SaaS app usually needs sign-in, a dashboard, billing, user settings, and an admin panel, while a client portal needs sign-in, project views, file sharing, and messaging. If you start each project from zero, you will build that same foundation every time.

Each project template is a complete, working app that you start from. Builder has templates for marketing sites, SaaS apps, client portals, internal tools, online stores, event registration sites, documentation sites, and portfolio pages. Every template comes with its pages, navigation, data connections, and workflows connected to one another, so your work starts with the details of your own project.

A generic contact list or file browser looks finished but shows no data until someone on your team connects it to your backend.

Builder Components includes blocks that come connected to Delalify products, such as a contact list that shows contacts from People, a file browser that shows files from OneCloud, and a data table that shows rows from Tables. When you drop one of these components into a project, Builder connects it to your data in that product. Each connection is optional, because every component also works with a custom data source.

If a ready-made component keeps its own hard-coded colors and fonts, you will have to restyle it by hand before it matches the rest of your app.

Every component and template uses the colors, fonts, spacing, and border radius from your project theme, so one edit to the theme changes every component in the project. You can override the styles of any single component where your design calls for something different. Templates start with neutral styling, so they take on your brand once you apply your theme.

Why teams start from components and templates

Start with sign-in and navigation already built

You start from components that already provide sign-in, navigation, data tables, and file management, so your team spends its time on the features that your organization needs.

Templates with every layer connected

A project template comes with its pages, navigation, data connections, and workflows in place, so your first step is to customize an app that already works.

Consistent look across every project

Projects that share a theme use the same colors, fonts, and spacing, because Builder restyles their components whenever someone edits that shared theme.

Share and reuse across your team

Your team can publish the components that it builds to the gallery, so whoever starts the next project can reuse a colleague's solution.

Projects that start from Builder Components

Web agency with five client sites due this quarter

A web agency takes on five new client websites in a quarter. Each client needs a different layout on the same foundation of hero sections, feature grids, pricing tables, contact forms, and footer layouts. The agency starts each project from the marketing site template, swaps in each client's content and brand colors through the theme, and customizes the sections that are unique to that client.

Result

The agency reuses the same navigation, form, and pricing components across all five sites, so its designers build only the sections that differ for each client. When a client asks for new colors, the agency changes that site's theme once, after which Builder restyles every component on the site.

Web agency with five client sites due this quarter

Ten-person startup builds its operations dashboard from a template

A 10-person startup needs an internal dashboard to track its sales pipeline, support tickets, and team tasks. The operations lead starts from the internal tool template, which includes sidebar navigation, data table components connected to Tables, and a chart widget. The operations lead then adds a kanban view for support tickets and a list of team tasks.

Result

The team checks one dashboard for the pipeline, the tickets, and the tasks, so they no longer open three separate tools. The operations lead edits the dashboard directly whenever priorities shift.

Ten-person startup builds its operations dashboard from a template

Interior design studio hands each client a branded project space

An interior design studio wants each client to see their mood boards, their floor plans, and the lead designer's contact details in one place. The studio starts from the client portal template, which includes sign-in, a file browser connected to OneCloud for project files, and a contact card connected to People. The studio's designers add a gallery component for room renderings and change the theme to the studio's colors.

Result

Each client signs in to review the mood boards and download the floor plans, so the designers no longer send each revision back and forth by email. Every page uses the studio's colors, because every component takes them from the theme.

Interior design studio hands each client a branded project space

Nonprofit reuses one registration template for three events a year

A nonprofit that holds three events a year needs registration pages with ticket selection, payment through Wallet, and a confirmation page. The event coordinator starts from the event registration template, updates the event details, connects the payment component to Wallet, and publishes the page on a custom domain. For the next event, the coordinator duplicates the project and replaces the content.

Result

The coordinator builds each event's registration page from the last one, so the nonprofit no longer hires a web developer for each event. Builder saves each attendee as a People contact and adds the registration to Tables.

Nonprofit reuses one registration template for three events a year

Start your next project from a template

Get early access to build from ready-made blocks, full project templates, and the components that your colleagues share.