Presentation and interaction
Semantic templates, responsive layout, accessibility, navigation and visual states. Changing the theme does not delete business content.
saddam-engineer-portfolio/Engineering system
A WordPress architecture designed to be editable, testable and maintainable.
The theme owns presentation. The companion plugin owns portable content models, workflows and integrations. Native editor tools keep normal content changes accessible to non-technical users.
Ownership boundaries
Each layer has a clear job.
The goal is not separation for its own sake. It is to keep data portable, visual changes safe and editing understandable.
Portable domain behavior
Custom post types, registered metadata, REST routes, privacy tools, lead workflow, caching, WP-CLI and Site Health.
saddam-engineer-core/Safe everyday content editing
Core blocks, reusable patterns and structured fields let editors change copy and media without opening PHP templates.
patterns/ + registered metaEngineering domains
The implementation is organized around responsibilities, not buzzwords.
Each domain below has a practical purpose, a WordPress-native implementation path and an explicit operational concern.
01
Product architecture
Plugins, content models and data ownership
Custom post types are used for editorial records. Registered metadata defines stable fields and REST schemas. A custom table is reserved for lead queries and retention behavior that do not fit normal content storage.
- Custom post types and taxonomies
- Registered meta with sanitization and capabilities
- Custom table with indexed fields and lifecycle handling
class-spcore-cpt.php
class-spcore-meta.php
class-spcore-leads.php02
Contracts and integrations
REST APIs, external services and failure-aware workflows
Public routes use explicit argument schemas, bounded pagination and deliberate response fields. Sensitive health information remains capability-protected. External requests use WordPress HTTP APIs and recoverable failure paths.
- Versioned REST namespace
- Permissions, validation and predictable errors
- Cache keys and explicit invalidation
class-spcore-rest.php
class-spcore-contact.php03
Editor and frontend
Gutenberg, reusable patterns and accessible interfaces
The dynamic engineering block uses block metadata and server rendering. Reusable native patterns cover common client sections. Frontend behavior progressively enhances accessible HTML instead of replacing it.
- block.json and server-side rendering
- Pattern library for common layouts
- Keyboard, focus and reduced-motion support
blocks/engineering-proof/
patterns/
assets/js/main.js04
Production operations
Security, privacy, diagnostics and quality gates
Capabilities, nonces, validation, output escaping and rate limits protect the request boundary. Privacy export/erase support, WP-CLI, Site Health and automated checks create an operational surface beyond the browser.
- Privacy exporter, eraser and retention
- WP-CLI and Site Health diagnostics
- PHPCS, compatibility checks, PHPUnit and CI
class-spcore-privacy.php
class-spcore-health.php
.github/workflows/Client editing model
How a non-technical client edits this kind of site without Elementor.
The editor should see business language and approved layout choices, not implementation details. The architecture uses the simplest editing tool appropriate for each content type.
Open the complete guideNormal page copy and imagesCore blocks
Reusable hero, CTA and feature sectionsBlock patterns
Projects, services and team recordsCustom post types and clear fields
Complex interactive functionalityPurpose-built custom block
Sitewide contact and profile detailsSettings screen
Production readiness
Quality, search clarity and AI features share the same foundation: trustworthy implementation.
No schema or AI feature can replace useful content, crawlable pages, secure code and evidence that matches visible claims.
Review before release
Syntax checks, WordPress Coding Standards, compatibility rules, integration tests and GitHub Actions.
Useful content with technical clarity
Canonical URLs, contextual metadata, accurate JSON-LD, internal links, visible authorship and human-first technical articles.
Progressive enhancement, not dependency
Guided mode works without an API. Optional AI mode keeps keys server-side, limits input and grounds answers in site content.
The full repository documents architecture, tests and release workflows.
Start with the README, then review the theme, companion plugin, tests and quality workflow.