Baking guides, regional recipes and home kitchen notes
Each month follows the same working order. Nothing here is a schedule you subscribe to, and no step depends on a deadline we set for you. It is simply the sequence the desk uses so that a theme, a recipe and a set of reader notes end up in the same place.
Step one
A short note sets the month's subject and points to a base recipe written in grams, with the pan size and oven shelf named up front.
Step two
Home bakers write in about what their flour, sugar and oven actually did. Weighing first, then describing the crumb, the rise and the browning, is more useful than a photo on its own.
Step three
Reader notes are set against the reference bake. Where crumb, rise or browning diverged, the column says so plainly rather than smoothing it over.
Step four
Fixes are folded into the recipe itself instead of being posted as a separate errata list. If you print the page later, you get the corrected version.
Step five
Reader photos arrive with the notes and are used to show how a bake actually looked, including the uneven ones. Styled results are not the point of this column.
Step six
A short summary gathers what changed, then the next theme is announced. Each month builds on the last instead of starting from zero.
If you want to send a note or a correction, the desk reads everything that arrives.
Write to the editorial desk How the paper is put togetherA few definitions that keep the bake-along cycle honest. Read these before you send a note, so the desk and the reader are talking about the same thing.
A correction is a change to the recipe text itself, not a separate errata note. If your bake shows a different crumb, rise or browning than the reference, the desk folds that into the working recipe so the next reader starts from the updated version. Corrections are credited to the note that raised them.
Each bake-along month runs on a single theme with one base recipe written in grams. The cycle closes when the summary and the next prompt go up. A theme is not a subscription and it does not renew on its own; it simply ends and the following one begins.
Notes are compared against the test kitchen reference bake, not against each other. A standard home oven and a small one with a strong top element will not behave the same way, and that difference is useful rather than a mistake. Say what your oven did and where the pan sat.
Reader photos are used to show real crumb, real browning and real failures. A flat, badly lit shot of a sunken centre is more useful than a styled one. Send what you actually pulled out of the tin.
Bags sold in Johannesburg, Cape Town, Durban and Pretoria do not always absorb the same way. When a note says the dough felt tight or wet, that is treated as a property of the flour in the bag, not as a mistake by the baker.
The editorial desk does not run accounts, paid memberships or a booking system, and it does not promise a reply window. Notes are read and sorted by column. If a note fits the current theme, it may appear in the next summary with the reader's name.
Each cycle moves through the same stages, from the desk's opening prompt to the corrections that get folded back into the recipe text. Nothing here is a subscription schedule or a product roadmap. It is simply the order in which the work happens.
Stage one
The desk opens the month with a theme and one base recipe written in grams. The formula is deliberately plain so that the variable under discussion is the technique, not the shopping list. Oven position and pan size are stated up front.
Stage two
Before any reader note arrives, the test kitchen bakes the recipe once and records what the crumb, rise and browning actually did. That bake becomes the reference the incoming letters get measured against.
Stage three
Home bakers send in what their flour, sugar and oven did. The useful notes are specific: which brand of bread flour, how the batter felt, where the pan sat. Vague reports are read but rarely change anything.
Stage four
The desk compares those notes against the reference bake and flags where crumb, rise or browning diverged. Corrections are folded back into the recipe text itself rather than posted as a separate errata list, so the working version stays in one place.
Stage five
Photos arrive alongside the notes and are used to show real texture: an uneven top, a tight crumb, a slice that tore. Styled results are not the point here, and a plain photo of a flawed bake is often the more useful one.
Stage six
The cycle closes with a short summary of what changed and the theme for the following month. Each round builds on the last, so the archive grows instead of restarting from zero every time.
Readers who want to send a note, a correction or bake-along photos can reach the editorial desk through the contact page. The castella basics guide is the usual starting point for anyone new to the cycle.
We keep a small record of how visitors move through the journal so we can see which stories and recipes are actually useful. Nothing here is sold or shared with advertisers, and you can change your mind at any time. Read the full details in our privacy policy.