Route-Driven Rendering

One reference host showing every live data family.

This site is the working reference for the current Cloudflare + GitHub + Supabase flow. Every highlighted route below resolves against live Kubota data already synced into Supabase.

Open the products section View a live product page

/product/<product> /products/<path...>/<category> /finance/<finance> /service/<service> /parts/<part>

Template Model

Liquid + data-liquid

Inline values render with `` and repeat/conditional blocks wrap authored elements.

Site Resolution

Hostname Folder

This host lives under `sites/demo.kubota.local/` and previews through `?host=demo.kubota.local`.

Render Source

Supabase Views

Products, finance, service, and parts routes all resolve through worker-side Supabase queries.

Media Contract

`image_url` fields

Dynamic templates now receive normalized image fields so pages can render media without parsing the raw Kubota size maps.

Live route demos

These are the main paths to test while designing future dealer sites and template conventions.

Products

Products landing page

Static authored page at `/products/` used as the entry point into listing and detail flows.

Open products landing

Listing

B Series listing

Deep route resolved through the shared products template, using the final segment `b-series` as the lookup key.

Open B Series

Detail

M7040 SUHD product page

Live detail route using `/product/tractor-m7040-suhd/` against `current_product_render_view`.

Open product page

Finance

B Series Finance

Uses the finance detail route family already loaded from Supabase.

Open finance page

Service

5 Star Program

Service page content rendered from `current_service_render_view`.

Open service page

Parts

Oils & Lubricants

Parts page content rendered from `current_parts_render_view`.

Open parts page

Reference structure

This host is intentionally small. It demonstrates how little authored structure is needed when the worker owns route-to-data resolution.

Static authored files

Home and `/products/` are plain HTML files with no data dependency at render time.

Dynamic templates

One template per route family: `_product_`, `_products_`, `_finance_`, `_service_`, and `_part_`.

Live content source

The worker uses the route path itself to determine which Supabase view to query and what slug to resolve.