Page is broken

Most rendering problems have one of a few causes. Ask the agent to check them in order.

The page shows a plain layout, or a listing is empty

When no template matches a page, Delta shows a plain layout: the site name as the header, the title and content, and a simple copyright footer. A new site looks like this everywhere, because Delta ships no templates.

• “List the display conditions and tell me which template wins for this page.” If nothing wins, give an existing template a condition that covers the page, or ask the agent to build the missing templates.
• If a listing is empty, there may be no published content of that type yet.

The page shows content but looks unstyled

The markup uses a class that has no rule in the site’s stylesheets.

• “Check whether these classes exist in site.css or components.css.” The fix is to add the missing styles, ideally as a component so they are reusable.

Styles from one template change the whole page

A class name in the template is also a class WordPress puts on <body>, such as single-post or archive. The rule then styles the whole page, header and footer included.

• Rename the class to one WordPress does not use: post-single instead of single-post, listing instead of archive. The save still succeeds, but the agent receives a wp_body_class warning that names the class.

The header or footer is narrower than the page

The outer element of the header or footer template has a maximum width and automatic side margins, so it shrinks to fit its content.

• Put the maximum width and margin-inline: auto on an inner wrapper, or give the outer element inline-size: 100%. The agent receives a flex_root_auto_margin warning for this pattern.

A blog-style loop shows up as literal {{#posts}} text

Main-query loops only work in templates. In a single page’s own HTML, use {{#query:post_type}} instead. The agent knows this rule and corrects the page when you point it out.

One block is broken

A broken block no longer stops the blocks after it. The page renders the rest, and the write that saved the block warns about it, so ask the agent what the warning said.

Send us a report

Ask the agent: “Run get-status and copy the output.” Then email 21Press Support with:

1. That status output (theme and WordPress versions)
2. The name of the ability that failed and the full error message
3. The page URL and which template renders it

A complete report lets us reproduce the problem the first time. Without the ability name and the error text we have to guess.