Tagixo Developer Documentation

This documentation is for engineering teams integrating Tagixo into Laravel applications.

Tagixo is the framework-agnostic visual builder core used to build:

• Web pages
• Form experiences
• Mail templates
• PDF templates
• Slider experiences (through page + layout variant)

You can run Tagixo in two main ways:

1. Standalone integration inside your Laravel app.
2. SDK integration through panel ecosystems such as Primix (and Filament when using its SDK package).

What this section includes

This documentation section is intentionally split into multiple pages so you can onboard new developers quickly:

• Installation and prerequisites
• Laravel bootstrap and configuration
• Standalone implementation workflow
• Builder API endpoints and payload contracts
• Data model, persistence, rendering, and preview flow
• Contexts and layout variants
• Primix and Filament integration paths
• Props, PropTypes, and custom modules
• Production checklist and troubleshooting

Recommended reading order

1. Overview
2. Installation and Prerequisites
3. Laravel Bootstrap and Configuration
4. Standalone Page Builder Integration
5. Builder API and Endpoints
6. Storage Model and Data Shape
7. Rendering and Preview Workflow

Then continue with SDK-specific and extension pages.

Architecture boundary

A key design rule:

• Tagixo core owns registries, rendering pipeline, API contracts, and module systems.
• SDK adapters own admin/panel glue code, page/resource wiring, and host-framework UI integration.

Implement capabilities in the core first, then expose them in SDKs.

Compatibility assumptions

• PHP 8.2+ (project currently uses PHP 8.3)
• Laravel 12/13 compatible environments
• Modern Vite-based frontend pipeline

If your project has stricter security middleware, check route middleware configuration in the dedicated configuration page.