Every crepe recipe has two layers: the batter and the filling. The batter has ingredients, a method, a rest time, a pan size. The filling has its own ingredient list, its own assembly steps, a serving suggestion. Sweet, savory, gluten-free, Breton galette, Nordic pannkakor, Japanese-style. The substance varies; the dual structure stays constant.

SleekRank reads a crepes sheet with separate batter and filling fields and ships one URL per row at /recipes/crepes/{slug}/. Tag mappings handle the title, list mappings render both ingredient lists and both step sequences, selector mappings handle the lead photo and the sweet-or-savory badge.

Editors maintain batter and filling as separate arrays per row. The template renders both sections in the right order without per-page configuration. Sweet and savory cluster automatically through the type column.

Crepe recipes are deceptively varied. The batter changes in subtle ways across regions, the fillings span sweet to savory, and the assembly steps shift depending on whether the crepe folds, rolls, or stacks. Hand-built sites struggle to keep this structured because editors tend to mix batter and filling into a single ingredient list, which obscures the recipe's actual shape.

Programmatic generation forces the separation: batter is its own array, filling is its own array, the template renders both cleanly every time. That structure is what makes the site useful for cooks who want to try a new filling on a batter they already love. Recipe schema stays valid across the corpus, sweet and savory clusters stay distinct, and the archive grows row by row without anyone touching the editor.