A Admatic StackDocumentation 5.14.2

Admatic Stack

Documentation for release 5.14.2

Search, install, operate and repair the coordinated Elementor website-production stack.

Search

Browse

Version note

This site documents stack 5.14.2. The stack is expected to evolve, so update the version badge and changed procedures when publishing a new coordinated bundle.

Using the Builder

Follow the protected workflow from brief to release. The system is designed to continue one explicit project rather than create replacements whenever a validation or materialization issue occurs.

Standard project workflow

  1. Confirm Core and staging health.
  2. Open Kit Factory Prompt Manager and enter the client/project brief.
  3. Add the required pages, real content, logo, production media and design references.
  4. Generate a fresh prompt so it contains the current content-variable and planning contracts.
  5. Use the prompt with the central Admatic ChatGPT connection.
  6. Core creates or continues the explicit project draft, configures design tokens and media, and locks a reference-resolved page plan.
  7. Core compiles and validates one immutable Kit Factory ZIP.
  8. Remote Worker verifies the package and starts Kit Factory on staging.
  9. Kit Factory builds pages, menus, global header/footer and site settings.
  10. Review package validation, screenshots and the release gate.

What the builder creates

Pages

Published Elementor pages with unique titles, real content, one H1, explicit backgrounds and Theme Builder-compatible layouts.

Global templates

Elementor Pro header and footer templates assigned to the entire site with required frontend markers.

Menus

Primary and footer WordPress menus with page or custom URL items.

Media

Local package assets imported into Media Library, deduplicated, given alt text and rewritten to final attachment IDs and URLs.

Design system

Elementor Site Settings, global colors, typography, spacing, radius and native responsive controls.

QA evidence

Validation report, execution trace, desktop/tablet/mobile screenshots, comparison results and release-gate status.

Manual upload fallback

Normal operation sends the package from Core to the paired Worker automatically. When transport is unavailable, download the compiled package, open Kit Factory on staging, upload the ZIP and choose Upload & Build.

Do not upload the complete stack bundle

Kit Factory expects a project package containing project.json, Elementor content and local assets. The stack bundle itself contains plugins and is installed through WordPress/Site Installer instead.

Rebuild and recovery behavior

  • Clean replacement: Kit Factory removes only content marked as generated by Kit Factory. Manual content without ownership markers is preserved.
  • Change preview: Existing builds receive a deterministic preview of created, updated and removed pages, templates, sections, media, menus and settings.
  • Safety snapshot: Modern rebuilds create a scoped restore point by default.
  • Same project: Repair and corrective rerenders continue the existing project. Do not create duplicates merely to retry.
  • Idempotent delivery: Package upload verifies digest and imports once.

Release gate

The release gate becomes ready after package validation and all required authoritative QA pass. Reference-led builds also require complete rendered reference comparison evidence.
The project remains intact. The workflow reports the exact failing region or missing reference, applies bounded corrections where supported, rerenders the same project and uses no more than three passes.
They are optional unless a project contract explicitly requires them. Package validation remains authoritative, while screenshot/reference QA can block release when it is required by the project.