How site structure works

This is a test site for verifying website-brief parsing and structure, not a real customer-facing product or domain-specific business site.

See overview

Site planning starts with scope

The method defines category scope first, then chooses page types that fit that scope without forcing fixed assumptions. When the input brief is ambiguous, the page keeps the uncertainty visible and uses guidance-led rules instead of pretending the answer is settled.

How the site structure works

Category definition

Set the category boundary from the input_brief so the site has a usable planning frame before any page is assigned.

Page type selection

Choose the page type that best matches the task, such as an index or directory hub page — method-overview, instead of jumping to a final layout.

Research backlog visibility

Keep unresolved items visible as backlog so the site can move forward while the next comparison or evidence check stays open.

What stays open in the strategy

Research backlog items stay attached to the site strategy so unresolved scope, comparison points, and classification gaps remain visible while planning continues. The next step is to compare the open assumptions against the input_brief and decide what needs research before the structure can be treated as settled.

Review the method, then test the input

This page explains the structure logic and shows what still needs research, so you can check whether the site plan is being parsed and classified correctly without treating it as exhaustive or fully verified.

See overview