Package Content WordPress module
Loads published editorial content over configurable HTTPS WordPress REST endpoints.
Content API boundary
WordPressContentClient.ts is the replaceable HTTPS reader for editorial content. It permits the shared UI to consume WordPress posts or configured content endpoints without importing WordPress PHP into the application. This is editorial content only; HSLG account sessions, order drafts and provider payments have separate protected APIs.
Failure and portability
Handle unreachable API origins, malformed payloads, missing/unpublished content and correct venue identity. Do not assume that a WordPress post ID is an HSLG customer or order ID. Keep origin configuration explicit and use tests with representative REST responses; a browser fixture should not be deployed as the native live catalogue.
Review when content changes
Verify the expected endpoint base URL, published status, media availability and safe handling of stale links. Event deep links must resolve the intended record rather than a general list. Content may be cached for display only when the product decision permits it; cached event text or a sample menu must not become authoritative payment availability.
Source files in this module
Maintenance and evidence
Check all affected file references and the matching human-readable user/architecture page when source changes. Run the module’s contract or governance checks; staging, payment and native hardware tests remain independent of source inventory coverage.