A complete breakdown of what makes "The Roots" by Chef Opel Khan exceptional — and exactly how to replicate and scale it using your cookbook builder.
Gentspark AI built this book as a single self-contained HTML file. Every image is embedded as base64 (no external URLs). Here's what makes it exceptional and what you must replicate in your builder:
Young turnips become sweet and almost creamy when baked gently in salt. Finished with a sharp apple and mustard glaze, this dish is simple, elegant, and quietly dramatic.
Full-page section layout. Each section is exactly 100vh — like turning a real page. Cover → Foreword → Philosophy → Chapter Opener → Recipes → Images → repeat.
One dark palette used throughout: deep brown (#1a1008), sage green accent (#7a8c5e), cream text. Georgia serif everywhere. No colour clashes. Zero generic fonts.
Every recipe has: a poetic headnote (2-3 sentences), precise ingredients with exact measurements, 6-7 numbered steps using professional chef language, and a Chef's Note.
Every recipe is followed by a full-page photo. Images are embedded directly as base64 JPEG — no broken links ever. Photos are fine-dining plated shots, not stock photos.
Fixed right-side dot navigation for jumping between chapters. Active state highlights the current chapter dot. Minimal and non-intrusive — disappears on small screens.
5 chapters (Soil, Forest, Field, Fire, Ferment) — each with a thematic opener page, 6 recipes, and a closing poem. ~30 recipes total, each 350–500 words of content.
Gentspark AI generates the entire book in one prompt — content AND layout AND images in a single HTML file. Your builder generates content and links to external images. Here's the full comparison:
| Feature | Your Current Builder | Gentspark "The Roots" Style |
|---|---|---|
| Image Source | Pexels/Unsplash URLs (can break) | Base64-embedded (never breaks) |
| Image Matching | Keyword lookup from a fixed library | AI-generated or chef-supplied per dish |
| Recipe Writing | Generic template with chapter blocks | Poetic headnote + precise method + chef's note |
| Page Layout | Scrollable webpage with cards | Full-page sections (100vh), book-like |
| Design Consistency | Multiple colours, varied fonts | One palette, one font family, CSS variables |
| Chapter Openers | Plain section headers | Full-page dramatic openers with giant numerals |
| Recipe Format | Ingredient/method blocks | 2-column grid: ingredients left, method right |
| Front Matter | Missing or minimal | Cover → Title → Foreword → Philosophy → How to Use → Pantry Notes |
| Navigation | None / top menu | Fixed right dot-nav per chapter |
| Scale | Manual per book | One prompt → full book → repeat 100x |
Gentspark AI works best when you give it ONE precise, structured master prompt. Below are the prompts that will produce "The Roots" level quality — copy and paste these directly.
Follow this exact workflow to produce one "Roots-quality" book. Then repeat it 100 times with different cuisines.
Before writing any prompt, decide the 5 core elements. This takes 5 minutes and determines everything else.
Author name: Chef Ayesha Rahman
Theme/Cuisine: Pakistani Ancestral
Chapters: Soil → Karahi / Flame → Biryani / River → Dal / Earth → Kebab / Sweet → Mithai
Tone: Poetic, heritage-focused, grandmother's kitchen voice
Accent colour: #8B6914 (turmeric gold)
Ask Gentspark/GPT to generate your full recipe list BEFORE writing the book. This prevents repeats and ensures variety.
Generate 30 unique [Pakistani] recipes grouped into 5 thematic chapters.
For each recipe provide:
- Recipe name (English + Urdu)
- Chapter it belongs to
- Key technique (bhuno / dum / tarka / grill / ferment)
- Main ingredient
- One-line headnote
Return as a numbered list. No repeats. Cover all regions.
Use the Image Matching Prompt (above) to get one unique Pexels URL per recipe. Verify each URL loads before using it.
✅ Chicken Karahi → Pexels #3590433 (cast iron karahi)
✅ Lamb Biryani → Pexels #12737817 (layered rice)
✅ Seekh Kebab → Pexels #1640777 (grilled skewers)
✅ Dal Makhani → Pexels #6367 (dark lentil bowl)
❌ NEVER reuse the same photo ID twice
Now use the Master Prompt with your recipe list and image URLs filled in. Gentspark AI will output one complete HTML file.
Paste the Master Prompt + your recipe list + image URLs.
Gentspark generates: ~15,000 word cookbook HTML file
Time: ~3–5 minutes per book
Output: Single .html file, download and save
Open the HTML file in a browser. Run through this checklist before publishing:
□ All 30 recipe pages display correctly
□ Each recipe has a UNIQUE photo (no repeats)
□ Chapter openers look dramatic (giant numeral + title)
□ Cover image loads properly
□ Dot navigation works (click each dot)
□ All measurements use consistent units (g, ml, tbsp)
□ No recipe contains "N/A" or placeholder text
□ Chef's Notes present on every recipe
□ Index page lists all 30 recipes alphabetically
The HTML file is your product. You can deliver it three ways:
Option A: Publish directly as a web page (works as-is)
Option B: Open in browser → Print → Save as PDF (for ebook sales)
Option C: Upload to your cookbook builder store page
Option D: Use Puppeteer/wkhtmltopdf to auto-convert to PDF at scale
Once you have one perfect template book, scaling to 100 is a systematic process. Here's how to do it without losing quality.
Pakistani, Indian, Japanese, Italian, Mexican, Thai, Mediterranean, French, American, Vegan, Korean, Chinese, Caribbean, African, Greek
Vary the theme: Regional / Heritage / Modern / Quick / Festive / Street Food / Vegetarian
5 chapters × 6 recipes. Keep recipe count consistent for uniform product quality.
With the template ready, each book takes ~5 minutes to generate + 10 minutes to QC = 15 min/book
Create a Master Template Spreadsheet with one row per book: Author Name, Cuisine, Chapter Names, Accent Colour, 30 Recipe Names, 30 Image URLs. Then batch-feed each row into Gentspark AI using the Scale Prompt. You can generate 6–8 books per hour.
Pro tip: Keep the CSS/HTML structure identical across all books. Only change: content, accent colour, cover image, and chapter names. This ensures brand consistency across your entire 100-book catalog.
Study these six rules from the actual file. Every rule is enforced in the HTML/CSS of "The Roots" — break any one and the quality drops noticeably.
"The Roots" uses a very specific dark brown (#1a1008), not generic black. This warmth is what makes it feel like a leather-bound book, not a website. Never use pure #000000.
Sage green (#7a8c5e) appears ONLY on: chapter labels, ingredient headers, chapter numerals, and divider lines. Never use it for body text or backgrounds. One accent = editorial discipline.
Ingredients always go LEFT (1fr), method always goes RIGHT (2fr). This is the most important layout rule. It's what makes each recipe look like a professional print cookbook, not a blog post.
Chapter openers use 12rem Roman numerals with 0.8 opacity. This single design choice communicates "premium editorial" instantly. Never use regular headings for chapter breaks.
"Young turnips become sweet and almost creamy when baked gently in salt." — Every recipe starts with a poetic, sensory 2-sentence headnote. This is the #1 writing quality marker. No generic descriptions.
Every single recipe is followed by a full-page (100vh) photo. Not a small thumbnail — a full bleed image. This pacing is what makes the reading experience feel like turning pages in a real book.
The reason "The Roots" looks so good is not the recipes — it's the pacing and restraint. One recipe, then one full-page photo. One recipe, then one full-page photo. The book breathes. Your builder currently puts everything on one scrollable page. Switching to 100vh page sections is the biggest single improvement you can make.
Do these three things today and you will have your first "Roots-quality" book ready to publish.
Copy the Master Prompt from this guide (Section 3). Fill in your cuisine, author name, and theme. Keep the design specs exactly as written. Let it run — it will generate a complete book HTML file. Download it and open it in your browser.
Open both HTML files in different browser tabs. Check: Do the chapter openers have giant numerals? Does each recipe have a poetic headnote? Is there a full-page photo after every recipe? If anything is missing, add it to your prompt and regenerate.
Create a Google Sheet with columns: Cuisine | Author | Chapter 1-5 Names | Accent Colour | 30 Recipe Names. Fill in all 15 cuisines. This becomes your production pipeline. Each row = one book. You can produce 100 books in ~25 hours of total work.