Skip to content

Requirements & Scope

The development of Pyxis CMS involves several critical engineering phases:

  1. Requirements Analysis: Designing a modular, headless architecture and analyzing system needs.
  2. Backend Implementation: Developing the core logic (Laravel), database structures, and the administration panel (Filament).
  3. Frontend Implementation: Creating a high-performance presentation layer consuming the Headless API.
  4. AI Integration: Implementing artificial intelligence features to assist content workflows via LLMs.
  5. Plugin System: Developing a “Zero-Core Modification” solution for external functionality extensions.
  6. Testing: Conducting functional and security tests to ensure system stability.
  7. Documentation: Preparing comprehensive product and technical documentation in Astro/Starlight.

To ensure stability and performance, the environment must meet the following technical specifications:

  • Docker Engine 24.0+ and Docker Compose v2.20+.
  • Development environment must support multi-container orchestration (Backend, Frontend, Database).
  • PHP 8.4+ (FPM mode recommended).
  • Required Extensions: * intl (Internationalization Support – critical for Filament UI).
    • bcmath (Precise arithmetic).
    • pdo_pgsql (PostgreSQL driver).
    • zip & gd (Media handling).
  • PostgreSQL 16+.
  • Support for JSONB data types is mandatory for the Flexible Content / Dynamic Block Builder architecture.

  • Dynamic Block Builder: Ability to define custom content schemas in the admin panel.
  • Flexible Content: Support for various field types (text, images, selects) dynamically assigned to blocks.
  • Headless Output: Content served as a structured JSON via RESTful API (Laravel Sanctum).
  • Root-Level Admin: The admin panel is served on the root path of its subdomain (e.g., admin.pyxis.test/).
  • Zero-Core Modification: All extensions reside in a dedicated directory (/py-content/plugins) and are loaded dynamically.
  • Event-Driven Architecture: Provision of “Hooks” (Actions and Filters) to intercept and modify system behavior.
  • Automated Content Generation: Built-in tools for generating post drafts, summaries, and SEO metadata.
  • Context-Aware Assistance: LLM-powered processing of existing content for translations or style adjustments.
  • Decoupled Frontend: A starter theme built with Next.js using Server-Side Rendering (SSR).
  • Component Mapping: Automatic matching of backend JSON blocks to frontend React components via a dedicated BlockRenderer.