Living Document Notice
Published 2026-09-11. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.

Recipes as Plain Documents - Stripping Ad Bloat into Inspectable Kitchen Markdown

Recipes as Plain Documents - Stripping Ad Bloat into Inspectable Kitchen Markdown: Warm golden amber P20 vector CRT macro showing advertising noise waveform filtering through sieve into structured kitchen recipe cards

Summary

Modern commercial recipe websites are among the most bloated pages on the internet, frequently loading over fifteen megabytes of video advertisements, behavioral tracking scripts, and narrative filler per page. Attempting to read these pages in a kitchen environment causes layout shifts, screen timeouts, and browser crashes on modest tablet hardware.

FreeMyRecipes extracts structured culinary data directly from standardized Schema.org JSON-LD blocks, transforming cluttered food blog URLs into compact, plain-text Markdown recipe cards. This dispatch reviews the extraction pipeline, parsing fallback heuristics, and the design of durable kitchen-ready documents.

The Overhead of the Modern Food Web

A typical online recipe page delivers less than two kilobytes of actual culinary instruction surrounded by megabytes of third-party JavaScript. Auto-playing video ads consume battery life and scroll tracking scripts trigger unpredictable layout jumps right as a cook attempts to check an ingredient measurement.

If a food blog closes or reorganizes its URL hierarchy, bookmarked recipes vanish. Storing recipes as plain Markdown files in a local directory guarantees perpetual access regardless of server availability.

Plain text recipe documents can be backed up with Git, viewed on e-ink devices, or printed without ad sidebars. The files remain functional even during complete household internet outages.

JSON-LD Schema.org Extraction Pipeline

Most commercial recipe publishers implement Schema.org Recipe metadata to secure rich search results in web engines. FreeMyRecipes leverages this structured data, bypassing presentation HTML entirely.

{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "Sourdough Boule",
  "recipeYield": "1 loaf",
  "prepTime": "PT30M",
  "cookTime": "PT45M",
  "recipeIngredient": [
    "500g bread flour",
    "375g warm water",
    "100g active sourdough starter",
    "10g fine sea salt"
  ],
  "recipeInstructions": [
    { "@type": "HowToStep", "text": "Mix flour and water; rest 45 minutes." },
    { "@type": "HowToStep", "text": "Fold in starter and salt; bulk ferment 4 hours." }
  ]
}

The extraction engine parses this JSON payload in under five milliseconds, extracting ingredients, step-by-step instructions, prep times, and nutritional estimates without executing third-party page scripts.

Heuristic DOM Fallbacks for Unstructured Sites

When a website omits JSON-LD metadata, FreeMyRecipes switches to microdata scrapers and regex ingredient classifiers. The parser identifies ingredient lines by scanning for unit measures (grams, ounces, milliliters, teaspoons) paired with numerical fractions, assembling structured cards even from unannotated blogs.

Extracted recipes are formatted with YAML frontmatter containing original source URLs, yield estimates, and cook times for easy vault filtering. A clean markdown checklist allows cooks to tick off ingredients as they are assembled on the kitchen counter.

Page Weight and Extraction Metrics

The table below details page weight reductions achieved by converting popular online recipe pages into clean Markdown recipe cards.

Source Recipe Site CategoryOriginal Web Page SizeConverted Markdown SizeData Reduction RatioClient Parse Time
Major Food Media Portal18.4 MB2.8 KB6,571x smaller4.2 ms
Independent Food Blog12.1 MB2.1 KB5,761x smaller3.8 ms
Video-Heavy Cooking Site26.8 MB3.4 KB7,882x smaller5.1 ms
International Recipe Archive8.2 MB2.4 KB3,416x smaller3.1 ms

  • Directus Target: freemyrecipes
  • Garden Source Reference: [From Bloated Food Blogs to Portable Markdown Recipe Cards](From Bloated Food Blogs to Portable Markdown Recipe Cards), [The Local-First Data Contract](The Local-First Data Contract), MOC - Data Liberation Workbenches, MOC - Culinary & Domain Workspaces, MOC - The Kitchen Chaos Factor