Classify Templates

⤢

MWD4 War Dungeon — Homepage — Editorial Restraint

homepage · suggested from BBWD2: Full-page Gutenberg

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD5 War Dungeon — Homepage — Maximalist Industrial Approved

homepage · suggested from BBWD3: Full-page Gutenberg

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD9 War Dungeon — Product Page — Maximalist Industrial Approved

product-page · suggested from BBWD8: WooCommerce + Gutenberg Content

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD14 War Dungeon — Category mini-homepage — Space Marines (desktop-first) Approved

category-page · suggested from BBWD11: WooCommerce + Full-page Gutenberg

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD15 War Dungeon — Shop Archive — Combat Patrols (desktop-first) Approved

category-page · suggested from BBWD12: WooCommerce

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD16 War Dungeon — Army Builder landing Approved

profile-page · suggested from BBWD13: Full-page Gutenberg

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD17 War Dungeon — Battle Simulator landing Approved

profile-page · suggested from BBWD14: Full-page Gutenberg

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD19 War Dungeon — Tutorials hub Approved

category-page

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD21 War Dungeon — How-To Guides hub (font fix) Approved

category-page

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD22 War Dungeon — Painting Showcase hub (font fix) Approved

category-page

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD23 War Dungeon — Creator Partner area Approved

category-page

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD24 War Dungeon — Loyalty programme Approved

category-page

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD25 War Dungeon — Cart Approved

cart-checkout · suggested from BBWD20: WooCommerce

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD26 War Dungeon — Checkout Approved

cart-checkout · suggested from BBWD21: WooCommerce

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD27 War Dungeon — Order Confirmation Approved

cart-checkout

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD28 War Dungeon — My Account Dashboard Approved

my-account · suggested from BBWD23: WooCommerce

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD29 War Dungeon — My Account Orders list Approved

my-account · suggested from BBWD24: WooCommerce

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD31 War Dungeon — Contact Approved

content-page

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD32 War Dungeon — Generic Content Page Approved

content-page

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD34 War Dungeon — Form Field Reference Approved

developer-reference

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD35 War Dungeon — Gutenberg Block Reference Approved

developer-reference

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD36 War Dungeon — About Approved

content-page

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).

⤢

MWD37 War Dungeon — Search Results Approved

search-results · suggested from BBWD28: Standard

WooCommerce ?WooCommerce-owned template. Product page, cart, checkout, my-account, shop archive. Rendered via wc_get_template() from the theme's woocommerce/*.php overrides — different template engine + query engine from plain WP. Pick this for anything served by WC. Standard ?Plain PHP template with a fixed layout — no block editor content area, no the_content() slot. All markup coded in the template file. Pick this for pages whose layout never varies (login, thank-you, custom landing pages with locked structure). Gutenberg Content ?PHP template that wraps a the_content() slot rendering block editor content, surrounded by fixed PHP-rendered chrome (sidebar, hero, footer band). Editor content is Gutenberg but the template scaffolding is coded. Pick this when editorial content lives in the middle of a fixed shell. Full-page Gutenberg ?Template is a thin PHP shell that just calls the_content() — entire page composed via block editor. No fixed PHP-rendered sections. Pick this when the whole page is operator-composable from blocks + patterns. Pattern Guide ?NOT a shipping template — a mockup that's the source of block patterns / components rather than a page. Contributes to the Consolidator + reusable pattern pool but never lands as a WP template file. Pick this for form-field references, editorial primitives, brand-pattern showcases.

WP template file ?The filename this mockup will become in the theme (no .php extension). Examples: page-ppc-landing, single-product, category-lightsabers, front-page. Follows WP's naming convention — the "kind" field below decides whether WP picks it up by hierarchy or the operator assigns it via Page Attributes.

Auto-route (WP template hierarchy) ?File is picked automatically by WordPress based on filename convention — page-{slug}.php, single-{cpt}.php, category-{slug}.php, etc. No admin action needed once the file lands in the theme; WP loads it for the matching URL. Custom Page Template (admin-assignable) ?File carries a `Template Name:` header and appears in the admin's Page Attributes → Template dropdown. Operator has to explicitly assign it to a page in wp-admin for it to render. Pick this for templates that don't have a natural hierarchy match (custom landing pages, marketing pages, ad-hoc layouts).