About

Every guide on this site is researched, edited, and maintained under one editorial signature: Ali Ocak.

Ali Ocak is the pen name of the site's editor. Behind it is a small independent project with one obsession: understanding why each kebab tradition works — reading regional sources, comparing how the same dish is described by cookbooks, local institutions and the cooks in the reference videos, and adapting every recipe so it can be cooked honestly in a normal home kitchen.

Recipe and atlas pages list the references they were checked against in a Sources section at the bottom. Most cite two or more; a page with only one solid reference lists just that one rather than padding the list. Pages are corrected whenever a reader points out a mistake through the contact page.

Research comes first. Each dish page starts from regional references — municipal and tourism institutions, cookbooks, academic food studies, encyclopedias — and those references are listed on the page. Cooking videos shown on a page belong to the cooks who made them and are credited to their channels.

Writing: page drafts are prepared with the help of AI writing tools, then checked against the cited references, and each page's text is checked against its own recipe card so the two never disagree. When a page turns out to describe a dish wrongly, it is rewritten from the sources rather than patched.

Images: photographs are open-licence photos of the right dish, credited on the page and on the Image Credits page. When no honest photo of the right dish exists, the page shows an illustration generated with AI and labelled as such — it is never presented as a photograph. The ingredient boards are AI illustrations too, with the ingredient names added by us. Photos and videos found to show a different dish were removed.

What this site does not do: no star ratings or reviews (there is no tasting panel to back them), no invented personal stories, no paid placements disguised as recommendations.

The site covers kebab recipes, bread systems, sauce systems, wrap assembly, grilling technique, and comparison guides across Turkish, Balkan, Persian, Greek, Levantine, Indian, and vegetarian traditions — plus the Kebab Atlas, a reference of more than 260 grilled-meat dishes from every region, each with its origin, its method and the references it was checked against.

The goal is not to publish isolated ingredient lists. The goal is to help home cooks understand why a dish works, what bread belongs with it, which garnish matters, and how to get a believable result in a normal home kitchen.

That means a recipe page may be supported by flatbread pages, sauce pages, regional hubs, and troubleshooting notes rather than standing alone as a thin one-off article.

Pages are written as original editorial guides using recipe research, regional references, comparative reading, and practical home-cooking adaptation. Each page is meant to answer the next useful question, not only the first one.

When a dish depends on bread, onion salad, sauce, or grill handling, the page should say so clearly. That is why the site keeps linking recipes into systems instead of pretending every kebab can be cooked and served the same way.

The editorial standard is simple: if a page cannot help a reader choose the right meat, understand the texture goal, and plate the result properly, the page is not finished yet.

A recipe is considered ready when it gives readers enough information to make decisions without guessing: the cut of meat, the role of fat, the texture target, resting time, heat source, bread pairing, sauce pairing, and likely failure points.

Thin recipes that only list ingredients are treated as incomplete. A strong recipe page should help the reader understand what to look for, what to avoid, and how to correct the method if the texture, moisture, or shape starts going wrong.

Pages continue to be updated when better process photos, clearer method notes, stronger sourcing, or more useful serving context become available.

If a reader spots a mistake, missing credit, weak explanation, or broken page, the site should be corrected rather than left to drift. Feedback, image questions, and sourcing issues can be sent through the contact page.

The site continues to update high-priority pages as new support content is added, especially for breads, sauces, equipment, and troubleshooting, where readers ask the most follow-up questions.