How to Build Joomla Pages and Dynamic Content Collections Faster in SP Page Builder with AI

SP Page Builder makes Joomla design visual, but the repetitive work is still manual: blank pages that need full layouts, Dynamic Content collections that need a schema, records, an index page and a detail page, items with a dozen empty fields, images to source and copy to write. MuRu AI for SP Page Builder adds a Generate AI Page button inside the editor and turns that work into a prompt plus a review. This guide shows what it can do and where it saves the most time, including everything new in version 1.6.0.

In this guide

1. Where SP Page Builder work takes the most time
2. Design full pages from one description
3. Build a Dynamic Content collection in one prompt
4. Fill collection items with AI
5. Generate and place page images
6. Fix and improve pages you already built
7. Stay on-brand automatically
8. Translate and add SEO text
9. Safe by design
10. What's included in version 1.6.0
11. Quick start workflow
12. Frequently asked questions

Where SP Page Builder Work Takes the Most Time

A visual builder removes code, not effort. The slowest jobs in a typical SP Page Builder project are the ones that repeat: laying out a new page section by section, designing a collection schema field by field, creating records one at a time, binding an index and a detail page to real fields, and writing headlines and descriptions in a consistent voice. These are the jobs MuRu AI is built to shorten.

Design Full Pages from One Description

Open any page, click Generate AI Page and describe what you need, for example "A SaaS landing page: hero with two buttons, 3-feature row, pricing, FAQ, contact CTA". You get a complete native layout of sections, columns and addons instead of a blank canvas.

You can replace the whole page or append the result as a new section at the end. Prompts you reuse can be saved as your own templates, and your last 10 prompts are always one click away.

Build a Dynamic Content Collection in One Prompt

A Dynamic Content collection normally means designing the schema, creating records, then building and binding an index page and a detail page. With New Collection with AI, you describe the collection, such as "A book catalogue with title, author, cover image, genre and description", or start from a preset: blog, portfolio, team, products, testimonials, FAQ or events.

1. Schema designed for you: the plugin chooses sensible fields and creates the collection using SP Page Builder's own collection system.
2. Sample records seeded: choose none, 3, 5 or 8 records. Location fields get real coordinates and image fields get real stock photos, so the data looks like real data.
3. Index and detail pages created: the index gets a Collection block with grid or list layout and pagination, and the detail page gets Dynamic Text and Dynamic Media blocks bound to the real fields.
4. Tone applied everywhere: the chosen voice flows into the sample records and both generated pages.

You can also generate directly on an existing collection's index or detail page. The output is bound to that collection's fields, with every existing binding preserved.

Fill Collection Items with AI

Large collections are tedious because every item has many fields. Open any item and click Fill item with AI beside Save. It writes values for the item's empty text fields from the collection name, the item title and an optional hint, then saves through SP Page Builder's own item service.

• Validated against real fields: unknown fields are dropped, option labels are mapped, and emails, dates and numbers are checked.
• Nothing is overwritten: fields that already have values are never changed.
• Sensitive fields skipped: media, relationships, alias and layout fields are left alone and reported.
• Works on the create form: on a new item, MuRu AI creates the item as published and opens it. This needs SP Page Builder create rights.

For a large collection, the practical workflow is to create the item title, click Fill item with AI, review, and move on, instead of typing into twenty fields per record.

Generate and Place Page Images

The Generate window lists every image setting on the page. Each row gives you three options:

• Paste a path to an image you already have.
• Choose a file from Joomla's Media Manager.
• Generate a new one. Describe the image and a DALL-E 3 landscape image is created, verified and saved under images/muruai/.

The page changes only when you click Apply images, and a Version History snapshot is taken first. AI image generation needs an OpenAI key, and Gemini-configured sites get a clear message instead of a broken button.

Fix and Improve Pages You Already Built

Older pages collect the same issues: columns that do not collapse on mobile, headings that do not scale down, carousels with one slide and raw_html blocks where a native addon would work better.

• Improve this page: one click closes responsive gaps, scales mobile typography, fills thin carousels and swaps raw HTML for native addons. Use the prompt box for an optional focus, such as "tighten the pricing section".
• Regenerate one section: pick a section from the outline, describe the change, and only that section is rebuilt in its exact position.

Stay On-Brand Automatically

Set your primary, secondary and accent colors, heading and body fonts and button radius once. They are sent to the model as hard constraints on every generation, so pages arrive wearing your theme. Empty slots can be auto-detected from your template, and manual values always win. On EasyStore Single, Collection and storefront layouts, the model is also told which addon family renders there, so blocks do not land where they would show empty.

Translate Pages and Add SEO Text

• Translate this page: duplicate the open page into another language with identical structure and only the text translated. A structural check rejects any result where the layout drifted, so a broken page is never saved.
• SEO from the same generation: the model can return a title, description and Open Graph text, which are written to the page's settings when you apply.

Safe by Design

• Version History first: every overwrite is snapshotted before it is written, and stale compiled CSS is purged.
• Validation: structural checks mean bad model output produces a clear error, never a silently broken page.
• Activity log: see who generated what, on which page and with which model. Prompt text is never logged.
• Your key, your data: only your prompt and layout rules go to your own AI provider. Improve, Regenerate section, Translate and item autofill also send the content they work on. Nothing is sent for training or telemetry.
• CLI for bulk work: muruai:generate runs scripted page generation with preview-first safety.

What's Included in Version 1.6.0

Everything covered in this guide is available in MuRu AI for SP Page Builder. Here is the full list of what the release adds.

• Review before anything is written: a staged preview with section titles, block lists, counts and quality notes, plus Apply to page or Discard.
• Tone dropdown: Professional, Friendly, Bold, Playful or Formal, with a default tone setting.
• Page outline hint and size estimate: see the open page's sections and blocks, and a rough token estimate next to the model name.
• Regenerate one section: rebuild a single section and swap it back into its exact position.
• Improve this page: fixes responsive gaps, scales mobile typography, fills single-item carousels and swaps raw_html for native addons.
• Brand kit: colors, fonts and button radius sent to the model as hard constraints, with auto-detection from your template.
• EasyStore-aware generation: the model knows which addons render on Single, Collection and storefront layouts.
• Custom prompt templates: save your own, shown under "My templates" in the preset dropdown.
• Prompt history: your last 10 prompts, re-runnable from Recent prompts.
• Prompt-pack import and export: share templates between sites as JSON, with no keys or credentials included.
• Page images from the Media Manager: a Choose button on every image setting, applied with a Version History snapshot first.
• AI-generated page images: a Generate button using DALL-E 3, saved under images/muruai/ (needs an OpenAI key).
• SEO text from the same generation: title, description and Open Graph text written to the page settings on apply.
• Translate this page: duplicate the page into another language with identical structure, protected by a server-side structural check.
• Fill item with AI: autofill empty text fields on existing items, validated against the real field definitions, with existing values never overwritten.
• Fill on the create form: the new item is created as published through SP Page Builder's item service and opened for you.
• New-collection window redesign: two-column layout with collection presets, Tone and a sample-records count of none, 3, 5 or 8.
• Generation activity log: who, which page, which mode, which model and how many sections. Prompt text is never logged.
• Bulk and CLI generation: muruai:generate previews by default and writes only with --confirm.
• Frontend editor support: an opt-in setting, off by default, with the same login, token, edit-rights and license checks.
• Redesigned Generate window: full width with a scrollable body, fixed header and footer, and a two-column Options rail.
• Editor white-screen fix: Improve and Regenerate section no longer crash the editor with e.map is not a function.
• License check update: follows the shared MuRu contract and recognizes the version_mismatch verdict. Valid keys are unaffected.

Quick Start Workflow

Frequently Asked Questions

SP Page Builder gave you visual control over pages. MuRu AI adds speed: describe pages instead of assembling them, generate collections instead of hand-building schemas, and fill items instead of typing into every field, while previews and snapshots keep you in control.