Fountain part sourcing organized by pump, nozzle, lighting, fittings, compatibility, and replacement project questions.
Config-driven Fountain Parts site architecture with independent metadata, buyer paths, RFQ identity, sitemap, robots, and schema.
Category Architecture
Each category keeps the Fountain Parts buyer context separate from the other DK domains.
Buyer Decision Path
engineering, specification-first, compatibility, replacement part review. The page asks for what can be reviewed now and marks unknown facts as RFQ inputs.
What: product, category, event, part, or recognition program.
How: customization, artwork, compatibility, packaging, version, or application route.
Options: site-specific category paths generated from config.
Order/RFQ: shared backend, isolated site_id=dk-fountainparts.
Core Buyer Pages
Shared components, independent page intent, and no unsupported commercial promises.
Build the Fountain Parts RFQ record
The form keeps domain, site ID, source page, quantity, destination, target date, artwork status, files, and open questions together.
Open RFQ