GramToSpoon - Kitchen Conversion Tool

The problem

Someone cooking does not search for a converter tool. They search for one specific thing: how many cups is 200 grams of flour. A single calculator page competes badly for that, because the page never contains the phrase the person actually typed. The interesting problem is producing hundreds of specific answer pages without hand-writing hundreds of files, and keeping them consistent when the underlying data changes.

Approach

• Ingredient data is the single source of truth: 47 ingredients, each carrying its grams per cup, per tablespoon and per teaspoon, so every conversion derives from one number rather than a hardcoded table.
• A Node generator reads that data and writes the site: 431 conversion pages, each one dedicated to a specific amount, ingredient and unit, plus an index of all conversions and the updated homepage.
• Which pages get generated is driven by a tier configuration that pairs amount ranges with units, so coverage can be widened or narrowed by editing config instead of writing files.
• The output is plain static HTML with a sitemap and robots file, so the site can be hosted anywhere and indexed cleanly.
• Regenerating is idempotent: correcting one ingredient value updates every page that depends on it in a single run.

What it proves

• 431 individual conversion pages generated from 47 ingredient records.
• Adding an ingredient or fixing a ratio propagates to every affected page automatically.
• Pure static output with sitemap and robots, served from its own domain.
• Demonstrates programmatic content generation, not a single-page calculator.