Weave Code
Visual Laravel Package
bagistoplus/visual
bagistoplus/visual is a Bagisto package that adds a visual page builder to the admin panel, letting merchants create and edit storefront pages, content blocks, and layouts with drag-and-drop controls—no code required. Built for Laravel/PHP.
Bagisto theme framework and visual theme editor
Frequently asked questions about Visual
- What is bagistoplus/visual and what does it do?
- bagistoplus/visual is a Bagisto theme framework and visual theme editor that ships as a Laravel package. It adds a drag-and-drop page builder to the Bagisto admin panel so merchants can create and edit storefront pages, content blocks, and layouts without writing code. Under the hood it layers a block and component registry, a Blade rendering path, and a visual editor on top of Bagisto's existing theme layering. It is best understood as a Bagisto theme framework that happens to ship as a Laravel package, not the reverse.
- How do I install bagistoplus/visual in a Bagisto project?
- Install it with Composer, but pin the literal alpha version rather than using a caret constraint, for example bagistoplus/visual:2.0.0-alpha.31, and commit the lockfile. Expect service provider auto-discovery, a publishable config file, and a Vite/TypeScript asset build step. Verify the provider namespace against the package's own composer.json instead of relying on prose, since the Composer install is trivial but configuration and asset wiring are where the real work sits.
- Does bagistoplus/visual work on plain Laravel without Bagisto?
- Not usefully. The package layers on top of Bagisto's theme layering, admin panel, and storefront rendering path, so on plain Laravel the value proposition narrows sharply. The first question to answer is not whether the package is good but whether your storefront is Bagisto with server-rendered Blade views. If the answer is no, stop evaluating here.
- Which Bagisto and Laravel versions does bagistoplus/visual support?
- The release notes and prose do not clearly state which Bagisto major line this alpha targets, so treat compatibility as unverified until you check. Confirm that PHP and Laravel constraints are actually encoded in the package's composer.json rather than only described in documentation. If the constraints live only in prose, hardening that is your first integration ticket.
- Can I use bagistoplus/visual with a headless or SPA frontend?
- There is no natural consumer for it in a headless or SPA setup. The visual editor, draft preview, and asset endpoints are built around server-rendered Blade views, so on a decoupled frontend they have nothing to render into. Adopt it only when the storefront is Bagisto with Blade-rendered views, where the block registry, editor routes, and theme layering compound instead of conflict.
- How do I add and render a custom block with the visual editor?
- Start with the config block registry rather than the editor UI. Register a single reusable promo block with a title, body, image, and CTA, then render it on a non-critical page such as a category or CMS page, never checkout. Once that works, generate a draft preview URL of an edit and open it without an editor session. If the preview shows the edited, unpublished, uncached content, you have proven the registry, the Blade rendering path, and the cache bypass in one pass.
- Is the draft preview URL in bagistoplus/visual secure for unpublished content?
- That is the biggest open question, because something in the package decides who may render unpublished content and the release notes do not describe signing, expiry, tenant scoping, or replay resistance. Forwarded preview links are the obvious abuse path, so treat preview as a security boundary rather than a convenience feature. Read the source and the middleware before exposing preview URLs outside the admin team, and add your own scoping if the package does not provide it.
- How does the cache bypass middleware work and does it affect my CDN?
- The middleware resolves design and preview mode and bypasses full-page cache so editors see fresh renders, and the alpha.31 release made this middleware-order independent. What it keys on, and whether it fails open or closed, is code rather than a documented contract, so read src/, config/, and routes/ before trusting it. Note that the bypass is Laravel-level only and does not reach a CDN or reverse proxy, so stale edge caches can still break editorial trust.
- Is bagistoplus/visual production ready given the alpha releases?
- Treat the alpha cadence as the main production risk. Thirty-one alphas into a major line with no dependents upstream means your team is effectively the support organisation and every bump is a re-validation pass. Pin the literal version, record the pin and rationale in an ADR with a named owner, and set up a fork-ready posture with a private mirror and a rebasable patch set. Also watch for silent contract drift in the wishlist and compare PHP-to-TypeScript event mirror, which has no error surface and shows up as missing analytics weeks later.
- What are the alternatives to bagistoplus/visual for Bagisto storefronts?
- The native alternative is Bagisto's own theme layering plus hand-built Blade blocks, which gives you full control and no alpha dependency but no merchant-facing editor. If self-serve merchandising is a hard requirement, compare this package against other Bagisto page builder extensions and against building a narrow block registry in-house. For teams without in-house Laravel depth to read the package source, a supported commercial option is often cheaper than owning an alpha.
Weaver
How can I help you explore Laravel packages today?