Anywhere structured. Google Sheets and Airtable work well for editor-first teams, a MySQL or PostgreSQL table works well when ingredient data overlaps with a larger recipe system, and a flat JSON file in the repo works well for static catalogs. SleekRank reads any of them via the matching data source type.

Yes, when the Recipe JSON-LD block is populated correctly. SleekRank renders that block from the same row that feeds the visible page, so as long as fields like name, ingredients, and recipeInstructions are present, the schema is valid and rich-result eligible.

Either a variations array on the same row, or one row per variation linked through a parent slug. The first keeps the page focused; the second creates more indexable URLs. Most catalogs use the parent-slug pattern because each variation pulls its own long-tail traffic.

Store quantities as numbers per serving, then render a small client-side scaler in the base page. The data does not change; the template multiplies on render. SleekRank only handles the per-row data; serving math stays in the template.

An optional image_url field renders the photo when present and falls back to a default pattern when absent. The template handles the conditional so the source stays consistent across rows that have photos and rows that don't yet.

Either store calculated values per row (simplest, no runtime cost), or call a nutrition API from a build step and cache the result on the row. SleekRank reads whatever is on the row at cache time, so the calculation strategy lives in the source pipeline.

Yes, that is the point of separating data from layout. Editors work in Google Sheets, Airtable, or whatever source the team uses. The WordPress side handles only the template, so testers and recipe developers never need a CMS account.

Revision history lives in the source. Google Sheets keeps a version history, Airtable has revision snapshots, and JSON in git gets full commit history. SleekRank reads the current state on each cache cycle and the source system owns history.