WordPress CMS
Pages, news, FAQs, standards, editorial roles, versions, and publication workflow.
Technology architecture
Publishing, interface, and calculations.
Three independent layers.
WordPress remains a convenient CMS for the content team. Carbon CBAM receives published materials through the API, while confidential calculations are performed in a separate secure core.
Target architecture
Next.js / Carbon CBAM
Multi-page interface, SEO, responsive design, smart search, and integration of data from two APIs.
Compute core
Spring Boot + Python/FastAPI + PostgreSQL. Methodologies, factors, calculations, versions, and audit.
Critical rule: WordPress does not store calculation models, primary production data, or results that require access control. The CMS is responsible only for publication content.
Integration contracts
Stable APIs
instead of tight coupling
Each layer can be updated independently. Contracts are versioned, and CMS failures do not stop the calculation core.
| Interface | Direction | Purpose |
|---|---|---|
| WordPress REST API / WPGraphQL | CMS → website | Pages, publications, FAQs, reference materials, and SEO metadata |
| Calculation API v1 | Website ↔ core | Calculation jobs, statuses, methodology versions, and signed results |
| Search indexing webhook | CMS → search | Reindexing after publication or content updates |
| OIDC / Keycloak | Single sign-on | Users, roles, organizations, and access control |
| MinIO / signed URL | Core ↔ files | Evidence and reports without transferring binary data through the CMS |
WordPress readiness
Structured records
Standard, guidance, sector, FAQ, publication, and regulatory update are separate content types.
Domain-independent configuration
CMS and calculation API addresses are configured through environment variables for dev, test, and production.
Resilient interface
Cached published content and proper error states do not affect calculation processes.