Store flour weight per loaf and each ingredient's gram weight. A small template helper computes percentages at render time, so the percentages stay in sync with the ingredient weights automatically.

Yes. Add a units column per row or per-ingredient and let the list mapping render whichever the row prefers. Bread sites usually standardize on grams for accuracy, but volume can render alongside for accessibility.

The method column dictates which timing fields are required. A small base-page conditional shows the levain card only when method equals sourdough; yeasted loaves render a simpler timing card. Same template, two faces.

Eligibility depends on valid Recipe schema, image quality, and overall site authority. SleekRank produces compliant JSON-LD from your data fields. The carousel decision is Google's and tends to favor established food domains, but the structured-data prerequisite is met.

Yes. Add a parallel array of image URLs alongside the method array, and a list mapping renders each step with its photo attached. The data only carries URLs; the images stay in your media library or CDN.

Add a notes_altitude or notes_oven column and render it as an optional callout block when present. Recipes without adjustments show nothing; recipes with them get a tidy note without an extra template version.

Yes. Add a techniques column listing slugs (autolyse, stretch-and-fold, cold retard, scoring) and a list mapping renders them as links into a technique pages section. The cross-link graph stays consistent across the corpus.

Build the print view once into the base page using a CSS print stylesheet. Every loaf inherits the print layout automatically, so no per-recipe configuration is needed.