ComingSoonTemplate

Corex\Config\Operations\ComingSoonTemplate · class · Config layer

The coming-soon page itself (spec 101, FR-008 and FR-009): which template it is, where the default comes from, and what is served when the active theme has no block templates at all. The page is a block template named coming-soon. CoreX registers a default under that name, so the mode works under any block theme whether or not it is related to the Corex theme; a theme that ships templates/coming-soon.html replaces it, and a copy edited in the Site Editor replaces both. That precedence is WordPress’s, not this class’s — it is pinned by ComingSoonTemplateSeamTest so a core release that changes it is noticed. This class decides nothing about who is served the page. {@see ComingSoonGuard} does.

Public API

__construct(StandalonePage $page)

register(): void

registerDefault(): void

defaultContent(): string

The default page’s block markup, with its strings translated.

canvas(): string

Resolve the page for this request and return the file WordPress should include to render it, or an empty string when the active theme has no block templates to render with. Call this at the point of rendering, not before: resolving a block template leaves its content in WordPress’s globals for the canvas to print, and the template WordPress resolves for the request’s own query would overwrite it.

standalone(): string

The page as one self-contained document, for a theme with no block templates (FR-009). A whole document that never runs wp_head, so WordPress’s “discourage search engines” setting would not reach it. It is read here instead: the page is indexable unless that setting says otherwise, which is the same rule the block template gets for free (FR-010).