WordPress
Articles, news, reference pages, SEO metadata, and the editorial workflow.
WordPress REST API
Publication architecture
WordPress — for content. Compute core — for data.
The public website does not duplicate the calculation system or turn the CMS into a registry. It securely combines two verified data streams through an API.
7G
Traceable
Carbon Data Uniqueness · transparency · verifiability
Carbon Data Uniqueness · transparency · verifiability
HTTPS / JSON
Next.js
Multi-page interface, smart search, caching, accessibility, and responsive layout.
SSR / API routes
API Gateway
MRV & Registry Core
Spring Boot, Python/FastAPI, PostgreSQL, MinIO, RabbitMQ, and calculation models.
OAuth 2.0 / KeycloakEditorial content
WordPress is responsible only for publications. This makes it possible to use a familiar editor, categories, versions, and editorial approval workflows.
Registry data
Projects, issuances, transactions, and claims are supplied by a separate core. WordPress cannot modify calculations or unit statuses.
Smart search
A unified search index combines public records, standards, and CMS materials while taking result type and access rights into account.
Security
Service tokens are stored on the server, requests pass through the API Gateway, and administrative access is managed by Keycloak.
Prepared integration points
Integration contracts
- WORDPRESS_API_URL
- Base WordPress REST API URL for publications and pages
- CALCULATION_API_URL
- Compute core gateway for public registry data
- SEARCH_API_URL
- Optional external semantic search; local search works without it
- KEYCLOAK_ISSUER
- Identity provider for protected actions and the operator dashboard