Admatic Stack
Documentation for release 5.14.2
Search, install, operate and repair the coordinated Elementor website-production stack.
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.
Design & Media
Learn how references, the central template corpus, native Elementor composition and project-owned media work together to produce a design that remains editable and traceable.
Reference-first planning
References are analyzed before the site plan is locked. Visible geometry and responsive behavior take priority; the licensed template corpus supplies composition grammar and range guardrails rather than copied branding or content.
Geometry
Header height, hero proportion, content width, section rhythm, card grids, footer depth and responsive typography.
Structure
Section order, hierarchy, media placement, grid behavior, navigation and conversion flow.
Surface treatment
Color relationships, borders, radius, restrained shadows, whitespace and content density.
Design Intelligence
- Licensed template ZIPs are uploaded once under Admatic Core → Design Intelligence → Template Corpus.
- Core analyzes them centrally and approves one global corpus revision.
- Staging receives only selected metadata snapshots, not source archives, branding, copy, photography or the full corpus database.
- The builder retrieves whole-page and region-level patterns, then reconstructs them with native Elementor controls.
- Reference screenshots remain project QA evidence and can be imported into staging Media Library.
License reference
For fully in-house components, a public license URL is not required to run the builder. Internal provenance and ownership should still be recorded. External templates and photography must retain truthful source, provider and credit metadata.
Media rules
Local media first
- Production images must be inside the project ZIP under
/assets/images/. - Every image must have a stable reference, local path, filename, alt text and import/rewrite instructions.
- Remote URLs may be retained as source or credit metadata but not as live Elementor image sources.
- Core can download validated HTTPS production images into project-owned storage before packaging.
- Missing logos become native text wordmarks. Placeholder media cannot be released.
Upload behavior
- Use the project media uploader for logos, reference screenshots and content images.
- Uploaded files should enter WordPress Media Library immediately and remain attached to the current project manifest.
- Use stable semantic references such as
brand-logo,hero-photoordesign-reference-home. - Content photos cannot satisfy brand-logo controls.
Responsive and visual QA
- Desktop: 1440 × 1200.
- Tablet: 834 × 1200.
- Mobile: 390 × 1100.
- Six weighted regions: header, hero, sections, typography, imagery and footer.
- Mobile horizontal overflow is forbidden.
- Corrections map back to native Elementor controls and rerender the same project.
No silent generic fallback
Missing measured evidence must not silently become a generic header, hero, section or footer. The builder should either prove an approved match, create a bounded native composition, or report a blocking issue.