You can build a landing page in Lara Dashboard without writing a Blade template. The page editor is LaraBuilder, a drag-and-drop block builder that ships with the core. You stack blocks like hero headings, pricing tables, testimonials and FAQs, check the layout at three screen sizes, fill in the SEO fields, and publish.
Disclosure: Lara Dashboard is our open-source, MIT-licensed Laravel CMS and admin. This is our own guide. Every LaraBuilder claim below comes from the LaraBuilder docs and the code in the repo, as of November 2026 (v1.5.0).
Quick answer: marketers build the page, developers own the blocks
LaraBuilder splits the work in a way that suits most Laravel teams. Editors arrange blocks and change text, images and colors in a properties panel. Developers decide which blocks exist, how they render and how they change over time.
That split is the point. A marketer can ship a campaign page on Tuesday without a pull request. A developer can still fix a bug in the button block once and have it apply to every page that uses it. If your team wants both of those things, LaraBuilder is a good fit. If you need pixel-perfect, one-off art direction on every page, hand-coding may still be faster. We cover that in the trade-offs section.
Related reading: what is Lara Dashboard, building modular Laravel applications with Lara Dashboard, and email templates and campaigns inside Lara Dashboard, which uses the same builder.
The core blocks already cover a typical landing page
The core ships with 37 blocks. Not all of them are available everywhere. Each block declares the contexts it works in:
page, email or campaign. A pricing table, for example, is page-only, because it would not render reliably in an email client.Here is how the page blocks map to the usual sections of a landing page:
| Landing page section | LaraBuilder blocks you would use |
|---|---|
| Hero | Section, Heading, Text, Button Group, Image or Video |
| Social proof | Logo Carousel, Testimonial, Star Rating, Stats Item |
| Features | Columns, Feature Box, Icon, Card |
| How it works | Steps, Tabs |
| Pricing | Pricing Table, Badge |
| Urgency | Countdown, Alert Banner |
| FAQ | Accordion |
| Content and blog | Latest Posts, Table of Contents, Time to Read, Markdown, Code |
| Escape hatch | HTML (sanitized on save and load) |
The list is from
resources/js/lara-builder/blocks in the repo. You do not need all of them. A clean landing page usually uses eight or nine.Editing is fast because the boring parts are built in
A builder lives or dies on small details. These are the ones we think matter most, all verified in the code:
Undo and redo. The builder keeps 50 history entries.
Ctrl/Cmd + Z undoes, Ctrl/Cmd + Shift + Z or Ctrl/Cmd + Y redoes.Slash commands. Type
/ to search for a block and insert it without dragging.Device preview. The header has Desktop, Tablet and Mobile preview modes. Use them before every publish. Most broken landing pages are broken on phones.
Duplicate and per-block styling. Any block can be duplicated from its toolbar. Layout controls cover spacing and colors, and a custom CSS field and custom class let a developer add a finishing touch without a new block.
AI drafting. An AI drawer can generate content inside the builder when a provider is configured. The core config lists OpenAI, Anthropic and a local Ollama endpoint. Treat the output as a first draft and edit it.
SEO fields live next to the content
A landing page that cannot rank is an expensive ad. The builder has an SEO drawer, so editors do not need to leave the page to set the basics.
It covers the slug, meta title and description, Open Graph title and description, a canonical URL override and a noindex switch. The noindex switch is useful for paid-campaign variants. You often want a near-duplicate page for an ad, and you do not want it competing with the main page in search.
Pages are served at the site root by slug, for example
/pricing, while posts live under a post path. Pages can also have a parent page and a featured image. Under the appearance settings you can pick any page as the homepage. So the landing page you built in LaraBuilder can become the front of the site with one setting.If you are moving pages over from WordPress, keep the old URLs. Our guide on rebuilding a WordPress site in Laravel without losing rankings covers redirects and URL parity in detail.
Server-side rendering means block fixes reach old pages
This is the part developers should care about most. Many builders save finished HTML. Fix a block later and every old page keeps the old markup until someone re-saves it.
LaraBuilder avoids that for blocks that have a
render.php file. In the page context, the block saves a placeholder with its props, such as <div data-lara-block="heading" data-props='...'></div>. When the page is displayed, BlockRenderer::processContent() finds the placeholders and calls each block's render.php to produce the HTML.The practical result: fix the PHP renderer once and every page that uses that block is fixed. Email is the exception. Email clients cannot call your server, so email output is full HTML, built with table-based helpers.
Blocks also carry a semantic version in
block.json. When you rename or restructure props, you bump the version and add a migration file like v1_0_0_to_v1_1_0.php. Old content is migrated when it is rendered, without a bulk re-save. Run php artisan builder:check-versions to see which blocks are versioned and which have server rendering.Custom blocks take minutes, not a sprint
Sooner or later a landing page needs something the core does not have. A product card, a signup panel, a comparison strip. You add a block instead of hard-coding the section.
Start with the generator:
php artisan make:block pricing-card --category=Marketing --icon=mdi:currency-usd. It creates a folder with block.json, block.jsx, an optional editor.jsx, save.js and index.js.With
--simple, you skip the custom editor. You list fields in block.json (text, textarea, number, url, select, color, toggle, range, image, align and more), and the properties panel is generated from that list. For a lot of marketing blocks, that is all you need.Blocks can also live inside a module with
--module=crm. The type is prefixed with the module name, for example crm-product-card, so two modules cannot collide. That keeps your custom blocks in the same place as the feature they belong to. Our post on modular Laravel apps vs WordPress plugin spaghetti explains why that matters over time.One honest caveat: blocks are React components bundled with Vite. After adding or changing one, you run
npm run build. That is normal for a Laravel app, but it is a build step, not a click in the admin.Editor content is sanitized, including the HTML block
A builder that accepts HTML is a security surface. Since v1.4.9, LaraBuilder content is sanitized before it is stored and again whenever it is loaded. Scripts, event handlers, Alpine and Livewire directives and
javascript: links are stripped. That covers every block type, including module blocks and blocks made with make:block. Renderers also escape colors, sizes and CSS before they reach style attributes.So the HTML block is an escape hatch for markup, not for running code. If a landing page needs a third-party script, such as an analytics tag, put it in the theme or a module, where a developer reviews it. Details are in our v1.5.0 release and security write-up.
Trade-offs: when not to use LaraBuilder for a page
LaraBuilder is the right default for most marketing pages. It is not the right tool for every page.
- The page is really an app screen, like a checkout, a configurator or a dashboard. Build it as a Livewire component or a controller and view.
- Every page needs unique, heavily art-directed layouts. A designer and a developer writing Blade will beat any block set.
- You need inline third-party scripts on the page itself. Sanitizing strips them, by design.
- Your team has no one who can run a Vite build. You can still use the core blocks, but you cannot add new ones.
- You need A/B testing or personalization built in. The core builder does not do that; you would add a tool or build it.
- Your content team is already happy and productive in another CMS and the site works. Do not migrate just for a builder.
If you are still deciding on the bigger platform question, our decision guide on WordPress, headless or Laravel is a better place to start.
Landing page checklist before you publish
Run through this list on every new page. It takes five minutes.
- One clear H1 in the hero and one primary call to action.
- Checked in Desktop, Tablet and Mobile preview.
- Every image has alt text and a sensible file size.
- Slug is short and final, and any old URL redirects to it.
- Meta title and description are filled in, not left to defaults.
- Open Graph title, description and featured image are set.
- Canonical is correct, and campaign duplicates are set to noindex.
- Countdown dates, prices and plan names are correct.
- Links in buttons and cards point to real pages.
- Repeated sections are a reusable custom block, not copied HTML.
Verdict
LaraBuilder gives Laravel teams something WordPress teams take for granted: editors who can ship pages without a developer. It does it without giving up the things developers care about. Blocks are versioned code, server rendering means fixes reach old pages, and content is sanitized.
It is not a design tool and it will not replace custom Blade for app screens. For campaign pages, product pages and a marketing homepage, it is a solid base. If you want to try it, install Lara Dashboard, build one landing page with the core blocks, then add your first custom block with
make:block.FAQ
Is LaraBuilder a separate package or paid add-on?
No. LaraBuilder is part of the Lara Dashboard core, which is MIT-licensed. It is the editor for both posts and pages, and it also powers the email template builder.
Can I use a LaraBuilder page as my homepage?
Yes. Build the page, publish it, then pick it as the homepage in the appearance settings.
Do I need to know React to use LaraBuilder?
Not to build pages. Editors only use the drag-and-drop canvas and the properties panel. You need React and a Vite build only to create new blocks.
What happens to old pages when I change a block?
For blocks with a render.php file, the HTML is generated when the page is shown, so your change appears on every page. If you rename or restructure props, bump the block version and add a migration so old content is upgraded on render.
Can I paste custom HTML or scripts into a page?
You can paste HTML with the HTML block, but it is sanitized. Scripts, event handlers and javascript: links are removed. Put scripts in the theme or a module instead.
Does LaraBuilder work with my modules?
Yes. A module can ship its own blocks with php artisan make:block --module=name. Their types are prefixed with the module name so they do not clash with core or other modules.
