Laravel-powered content core

VelaFold CMS

VelaFold preserves legacy CMS behavior while bringing the public site, admin panel, block editor, media, SEO, security, backups, and core updates into one product-minded platform.

Explore the product Request a demo

Laravel: 13 / PHP 8.4+
Render: Theme + blocks
Operations: Backup + update
API: Public content

What it solves

Content, operations, and publishing in one core.

VelaFold respects the shape of existing CMS data, then moves it forward with modern Laravel services, a theme layer, and testable publishing workflows.

Legacy-aware core

Pages, config, media, languages, stats, and navigation models stay intact; new layers work with the data you already have.

Block and theme system

YAML block contracts, public partials, and theme overrides let teams manage page experiences one structured piece at a time.

Admin operations

Media, SEO, security, cron, backups, audit logs, and dashboard workflows run from one permission-aware panel.

Core update discipline

Manifests, checksums, dry runs, backups, maintenance mode, patches, and rollbacks turn updates into a controlled product flow.

Architecture

Classic CMS comfort, Laravel control.

Public render

The page resolver, language service, block resolver, theme manager, and SEO layer compose the public page together.

Admin panel

Database-driven navigation, permission middleware, modern UI components, and the block editor meet in one surface.

Runtime data

Config, pages, finder, forms, stats, and security records belong to the site; deploys and updates move around them carefully.

Ops confidence

Backups, cron, queues, cache, health probes, and the update server are treated as first-class product pieces.

Editor experience

Page composition stays editable without losing code discipline.

VelaFold's block editor gives content teams speed while leaving developers with clear YAML, Blade partial, and theme contracts.

pages / home

BLOCK BUILDER

Enterprise page flow

Operations

The panel manages system health, not just content.

Security records, 404 behavior, backup and restore, cron, queues, update packages, and post-deploy health checks all live inside the same product mindset.

View the API layer

Security

Firewall, audit, scan, whitelist, login attempt, and 404 records make risk visible from the panel.

Backup

Local and Spatie backups, restore locks, progress state, and Drive broker integration are built into the flow.

Update

Signed metadata, an HMAC gateway, dry runs, manifest policy, and rollback support keep core files controlled.

Content API

Public content keeps the same route contract as the site.

GET /api/v1/content/pages?lang=en&type=service

{
  "data": [
    {
      "title": "Services",
      "url": "https://site.com/services",
      "content": {
        "blocks": []
      },
      "seo": {
        "canonical": "..."
      }
    }
  ]
}

Published content only

Drafts, trash, future publications, and expired records never leak into public API responses.

Language and URL consistency

Active site languages and PageUrlService-generated URLs behave exactly like the public site.

Block data included

Heading, content, blocks, media, taxonomy, and SEO fields return in a separate but readable contract.

Let's build it

Grow the CMS from the data first, then the design.

We can read your current site, admin needs, and publishing workflows together, then introduce VelaFold at the right boundaries.

hello@velafold.com Back to top