I built Runometry, a running shoe database and price comparator (841 shoes, 16 brands, 6 locales), mostly with Claude Code and parallel agents. Notes on the stack and the workflow.
Angular + AnalogJS: static rendering and file-based routing, a good fit for catalog pages generated from data. Signals and standalone components make modern Angular a joy.
Spartan (spartan.ng): shadcn-style, accessible UI components for Angular. Consistent design system, fully customizable.
Tailwind for styling.
Cloudflare for static hosting, with images served as WebP from a CDN.
hreflang and localized routes from day one.
Page types generated from the catalog Shoe, brand and category pages, A vs B comparator pages restricted to comparable pairs (to avoid thin or nonsensical pages), guides and blog.
Clear conventions up front (structure, naming, component patterns), so agents produce code that fits the project.
Parallel agents on independent areas: comparator logic, templates, translations, data validation.
Me reviewing diffs, running the build, and checking anything factual.
Small, frequent commits so every agent change is easy to review or revert.
What I'd do the same way Keep the stack I know best. Agents shine when you can judge their output quickly.
What's next Daily price collection as a time series: price history, a price drop radar, alerts. I'm weighing feeds vs APIs vs scraping and would love input.
Live: runometry.com