Download the PHP package magna-cms/pages without Composer

On this page you can find all versions of the php package magna-cms/pages. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package pages

Magna Pages

A visual page builder for Laravel.
Drag-and-drop pages, templates, menus and global styles — built on Laravel 13 and Filament 5.

Status: alpha Laravel 13 Magna CMS


Magna Pages turns a headless Magna CMS install into a rendered website. It adds pages, reusable templates, headers and footers, navigation menus, a design-token system, and a visual builder for putting it all together — the drag-and-drop editing experience people expect from Webflow or Elementor, running inside a Laravel application you own.

It is a Laravel package. There is no SaaS, no external editor service, and no account to sign up for. Your content lives in your database and renders through your Blade views.

⚠️ This is alpha software

Read this part before you install anything.

Magna Pages is published at 0.1.0-alpha. It is incomplete and it has bugs — some of them known, most of them not yet found. Data formats, block schemas and internal APIs will change in ways that break existing pages. There is no upgrade path between alpha releases.

Use it on a scratch install. Don't put it on a client site yet.

It is published this early because the architecture is worth looking at and discussing, and because real feedback finds problems faster than another six months in private. Issue reports are welcome. Polish is not promised.

What it does

Visual editing on the real page. The builder canvas is not a preview or an approximation — it is your actual rendered page, in an iframe, drawn by the same Blade views a visitor gets. Click a heading in the canvas and edit it in place.

Structure. Pages are a tree of sections, columns and blocks. Drop a row, split it, drag elements between columns, nest containers.

Templates and chrome. Headers and footers are template parts a page can choose, override, or switch off. Design one header and every page picks it up.

Menus. A menu builder with nested items, and a nav block that renders any menu you've defined.

Design tokens and responsive styles. Global colours, type and spacing as tokens; per-node styles that can differ per breakpoint. Light and dark are emitted in one stylesheet, so every visitor is served identical bytes and the page stays cacheable.

Revisions, locks and review. Every change is a revision you can preview and restore. Two editors cannot silently overwrite each other. Editors without publish rights can request publication instead.

Checks built in. Accessibility findings and performance notes are computed for the page you are editing, in the builder, rather than discovered after launch.

Dynamic content. A loop block iterates data sources that plugins register, so an installed plugin's content lands on a visually built page without the builder knowing anything about it.

How the canvas works

Most builders maintain two renderers: one that draws the editor preview and one that renders the published page. They drift, and the drift is where "it looked right in the editor" bugs come from.

Magna Pages has one. The canvas loads the real page through the real route, with the production renderer, and the server stamps data-magna-node attributes onto each node so the editor can map a click back to a document position. Editing is a JSON Patch sent to the server, classified by what it touches — content, structure, style, binding — and authorised per capability before it is applied. An editor with content rights can retype a heading but cannot delete the section it sits in.

The practical consequence: what you see while editing is what ships, because it is the same code path. The trade-off is that the canvas is a full page render, so it is heavier than a virtual DOM preview.

Requirements

No Node.js required to run it. The builder is a Vue 3 + TypeScript application, but the compiled bundle is committed — you only need Node if you want to rebuild the editor yourself.

Install

Then open the admin panel, create a page, and choose Open builder.

Blocks

Ships with the standard library: headings, text, images, galleries, buttons, icons, video, HTML, tables, code, quotes, callouts, file downloads, FAQs, heroes, features, pricing, stats, testimonials, team, logos, search, containers, spacers and dividers — plus dynamic blocks for menus, entry listings and plugin data sources.

Plugins add their own. A plugin implements RegistersBlocks, ships a block schema and a Blade view, and its blocks appear in the Add panel with a working inspector — no change to the builder.

The inspector is driven entirely by that schema, so a third-party block gets a real editing UI without writing any Vue.

Known gaps

Being honest about where it stands:

Tech

Laravel 13 · Filament 5 · Vue 3 · TypeScript · Pinia · Vite · Pest · PHPStan level 9 · Playwright

107 PHP classes, 23 Vue components, 22 Blade views at the time of this release.

License

Source-available, not open source — please don't call it that, and read LICENSE.md before using it.

The short version:

You may earn from what you build. You may not build a product out of this.

Want to do something the license doesn't allow? Open an issue — a commercial license may be available.

Links


All versions of pages with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
magna-cms/plugin-sdk Version ^1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package magna-cms/pages contains the following files

Loading the files please wait ...