Wholefood

Wholefood audio micro-course (transcript)

Three short podcasts about “Wholefood”. Listen with the interactive player.

Podcast 1 — Introduction & meaning

Narrator: Wholefood. The word sounds like a promise — that what you are eating is complete, unaltered, and genuinely itself.

Narrator: Wholefood — sometimes written as two words, whole food — is a noun referring to food that has been processed or refined as little as possible. Vegetables, fruits, legumes, whole grains, nuts, seeds. The defining principle is minimal intervention between the field and the plate: no stripping of fibre, no concentration of sugars, no artificial ingredients added to compensate for the flavour that industrial processing removes.

Narrator: The compound brings together whole, from Old English hāl meaning sound and complete, and food, from Old English fōda, meaning what nourishes. Together they describe nourishment in its complete, unbroken form — before it is refined into something lesser. The dietary concept became culturally prominent in the mid-twentieth century, gathering momentum through the natural food movements of the 1960s and 70s — a direct response to the observation that industrial food was becoming calorie-dense but nutrient-poor.

Narrator: Today wholefood sits comfortably in everyday British speech. A wholefood café. A wholefood diet. A wholefood approach to cooking. The word implies not just nutritional completeness but a certain philosophy — an ethic of simplicity, a respect for ingredients, and an attention to where food actually comes from and what has been done to it on the way to the table.

Narrator: Wholefood is not synonymous with vegan, vegetarian, organic, or raw — though it overlaps with all of these. Its defining criterion is minimal processing, not a particular ethical position about what one does or does not eat.

Narrator: Wholefood. The word for eating what the earth actually grew — before anyone decided to improve on it.

Speaker A: I have been trying to eat more wholefoods but I am genuinely not sure where the line is. When does something stop being wholefood?

Speaker B: A good rule of thumb is to ask: can I picture where this came from in nature, and has it been significantly altered since? An apple is wholefood. Apple juice — even unsweetened — has had its fibre removed. Apple-flavoured drink with added sugar is nowhere close.

Speaker A: So it is really about the number and type of interventions?

Speaker B: Exactly. The fewer steps between the original ingredient and your plate, the more wholefood it is. Brown rice is wholefood. White rice has had the bran and germ polished away. It is not harmful, but it is no longer whole in that sense.

Speaker A: What about wholemeal bread or wholegrain pasta? Those feel borderline.

Speaker B: Wholegrain products retain the bran and germ, so they are significantly closer to wholefood than refined versions. The distinction gets blurry because even wholemeal bread involves milling, mixing, proving, and baking. Strict wholefood advocates would say eat the grain itself, soaked and cooked. Practical wholefood eating allows wholegrain products as a reasonable middle ground.

Speaker A: And wholefood does not mean vegan or vegetarian, right?

Speaker B: Not at all. A grass-fed lamb chop is closer to wholefood than a heavily processed meat substitute that contains twenty ingredients. The principle is about minimal processing, not about excluding animal products.

Speaker A: The word gets used loosely though. Wholefood shops sell things that are really quite processed.

Speaker B: Very true. Organic crisps are still crisps. Reading the ingredient list matters more than trusting the shop's branding. The word wholefood describes an intention — to eat things as close to their natural state as you reasonably can. In practice, it requires judgement rather than a rigid rule.

Speaker A: So it is a philosophy as much as a food category.

Speaker B: Precisely. And that is exactly why the word is useful — it captures both the category and the intention in a single compact term.

Speaker B: Today we anchor prompts in wholefood — building apps and tools for nutrition tracking, recipe management, and ingredient data. Six prompts that treat food data with the same principle as wholefood itself: keep it clean, direct, and unprocessed.

Speaker A: Wholefood as a data philosophy — minimal noise, direct to the source.

Speaker B: Prompt one. Build a wholefood recipe app in React: show a grid of recipes, each with a wholefood score from one to five based on how processed the ingredients are. Add a filter by score and a search by ingredient name. Clicking a recipe opens a detail panel with the full ingredient list and cooking steps.

Speaker A: Wholefood score per recipe — one to five. That single metric makes the concept queryable and visible. The filter lets users find recipes that match their own threshold.

Speaker B: Prompt two. Design a PostgreSQL schema for a wholefood delivery platform: tables for products, ingredients, suppliers, and orders. Add a wholefood_rating column on the products table. Create a view returning all products rated four or five with their supplier name and price.

Speaker A: Wholefood_rating as a first-class column — the concept is built into the data model, not just a label on a screen. The view does the filtering automatically.

Speaker B: Prompt three. Build a Python script: read a CSV of food products with a product_name and ingredients column. For each product, count the number of ingredients. Flag any product with more than five ingredients as not wholefood. Output a cleaned CSV containing only wholefood products.

Speaker A: Five ingredients or fewer as the threshold — memorable, simple, and directly actionable as a data cleaning rule. The script turns a philosophy into a filter.

Speaker B: Prompt four. Build a full meal planner app in a single HTML file with vanilla JS: let users pick seven days of meals from a preset wholefood recipe list. Show the combined shopping list grouped by category — vegetables, grains, legumes, and proteins. Add a Print List button.

Speaker A: Seven-day plan, wholefood recipe list, grouped shopping list, and a print button — the whole user journey in one file. No framework, no build step.

Speaker B: Prompt five. Build a wholefood nutrition tracker in HTML and vanilla JS: let users log meals by selecting from a preset list of fifty wholefoods, each with calorie and macro values. Show daily totals as a bar chart using Chart.js. Save all logs to localStorage.

Speaker A: Preset wholefood list with macros, a bar chart, and localStorage persistence — a complete daily tracker with no backend at all.

Speaker B: Prompt six. Build a Node.js Express API: a GET slash search route that accepts a query parameter and searches a local JSON file of two hundred wholefood ingredients. Return matching results with name, food category, and wholefood score. Add a GET slash top route that returns the ten highest-scoring wholefoods.

Speaker A: Local JSON as the database, search endpoint, and a top-ten route — a lightweight wholefood API ready to power any frontend with no database setup required.

Speaker B: Six prompts. Wholefood teaches us to build food tools that respect the ingredient — minimal layers, direct data, and a clear measure of how close to the source something really is.