Cookbook Production · Editorial Design · Food Photography · Visual Identity · Urbanism Interludes · Print Preparation
A 275-page Persian cookbook project developed from the ground up in 2017, combining approximately 240 recipes with original editorial design, recipe documentation, food photography, visual production, cover design, and brief architecture / urbanism-inspired interludes.
1. Project Overview
Dream of a Chef was a complete cookbook production project developed in 2017.
The project began with a personal goal: the named author wanted to have a cookbook published under her own name, despite having an academic background in urban planning rather than culinary arts.
The resulting concept combined two different dimensions:
- a large Persian-language recipe collection,
- brief visual interludes related to architecture / urban-planning themes.
The final master file reached approximately:
- 275 pages
- ~240 recipes
- complete cover and spine design
- complete internal page design
- food photography and image sourcing
- editorial structuring
- print preparation
- ISBN acquisition
- private printed copies
The project was executed as a full end-to-end publishing workflow, from raw recipe knowledge to a finished physical book.
2. Professional Positioning
This project is best described as:
An end-to-end cookbook publishing project that transformed family culinary knowledge and practical cooking sessions into a 275-page illustrated Persian publication, with complete editorial design, photography, visual identity, layout, cover production, and print-ready delivery.
A weak description would be:
“Designed a cookbook.”
That would miss most of the actual work.
The real pipeline was closer to:
Family Culinary Knowledge
+
Practical Cooking
+
Recipe Explanation
↓
Recipe Documentation
↓
Food Photography / Image Sourcing
↓
Editorial Structuring
↓
Visual Identity
↓
Page Design
↓
Architecture / Urbanism Interludes
↓
Cover + Spine + Back Cover
↓
ISBN / Print Preparation
↓
Private Physical Copies
3. Project Identity
Title
Dream of a Chef
Persian title:
آرزوی بانوی آشپزخانه
The project was intended to appear under the name of the book’s named author.
The culinary material, however, was created through a broader family knowledge process rather than being the sole original culinary work of one person.
That distinction is important for accurate portfolio presentation.
4. My Role
The production side of the project was handled end-to-end.
My responsibilities included:
- project concept development,
- content collection,
- recipe documentation,
- editorial structuring,
- visual system design,
- internal page design,
- food photography,
- image preparation,
- image sourcing where original photography was not available,
- typography,
- page composition,
- cover design,
- back-cover design,
- spine design,
- illustration and graphic production,
- architecture / urbanism interlude design,
- final Photoshop-based production,
- print preparation,
- and management of the complete master files.
A concise positioning statement is:
The culinary preparation came from the named author and family contributors; the complete editorial, visual, photographic, design, and production workflow was executed by me.
5. Content Creation Model
The recipe content did not begin as a formal manuscript.
The workflow was practical and family-based.
Recipes were gathered from:
- the user’s mother,
- other family members,
- practical cooking sessions,
- spoken explanations,
- and existing culinary knowledge inside the family.
The general process was:
Recipe Idea
↓
Ask Family / Experienced Cook
↓
Prepare the Dish
↓
Receive Step-by-Step Explanation
↓
Document the Recipe
↓
Photograph the Dish When Possible
↓
Design the Recipe Page
This transformed informal household knowledge into a structured publication.
6. Scale
The final master document contained approximately:
- 275 pages
- ~240 recipes
This is a substantial content-production project.
At that scale, the challenge is not merely writing recipes.
The project requires:
- repeatable formatting,
- consistent page structure,
- asset management,
- visual continuity,
- typography discipline,
- image preparation,
- and editorial consistency.
7. Recipe Documentation
The recipe workflow involved translating spoken explanations into structured written instructions.
A recipe page generally needed to contain:
- dish title,
- ingredients,
- quantities,
- preparation steps,
- and visual representation.
The final publication therefore required consistent transformation from:
Informal Verbal Knowledge
into:
Structured Recipe Content
This is another example of converting undocumented or semi-documented knowledge into a reusable information product.
8. Food Photography
Photography was an important part of the cookbook.
When a dish could be prepared specifically for the project, I photographed it directly.
When that was not possible:
- photographs could be obtained from other family members,
- and in some cases external reference imagery was used.
This distinction should remain explicit in public portfolio material.
The project should not claim that every image in the book was original photography.
A defensible statement is:
Produced original food photography for project-prepared dishes and managed additional family-supplied or externally sourced imagery where original photography was unavailable.
9. Visual Example — Recipe Page
A surviving page from the master file demonstrates the recipe-page structure.
The example shows:
- a Persian recipe title,
- ingredient list,
- numbered preparation steps,
- a large food image,
- strong use of whitespace,
- and a clean editorial hierarchy.
The design keeps the written recipe compact while giving the finished dish strong visual emphasis.
This demonstrates that the project had a defined internal editorial system rather than being a collection of unstructured pages.
10. Editorial Design
The book required a coherent design system across hundreds of pages.
Important design decisions included:
- Persian right-to-left layout,
- recipe hierarchy,
- large image areas,
- whitespace,
- page numbering,
- text-image balance,
- chapter organization,
- and consistent visual rhythm.
The challenge was to keep the book readable despite the very large number of recipes.
11. Right-to-Left Publishing
The project was Persian-first.
That required handling:
- right-to-left body text,
- Persian recipe names,
- Persian ingredient lists,
- numbered instructions,
- mixed Latin/Persian elements,
- and page-level composition.
RTL publishing introduces layout constraints that are different from purely Latin-script publications.
This makes the project relevant as an example of multilingual / bidirectional publishing experience.
12. Architecture / Urbanism Concept
The named author had an academic background in urban planning.
Instead of ignoring that background, the project incorporated it as a secondary editorial motif.
The idea was to place brief architecture / urbanism-related visual material inside the cookbook.
These were not intended to turn the book into an academic urban-planning publication.
They functioned as short thematic interludes that connected the owner’s academic identity with the cookbook.
13. Example — “Points of View”
A surviving page titled:
points of view
shows a kitchen interior from multiple visual perspectives together with a plan / diagram.
This is a good example of the scale of the architecture component.
It was:
- visually oriented,
- brief,
- accessible,
- and secondary to the recipes.
The portfolio should therefore describe this accurately as:
short architecture / urbanism-inspired visual interludes
rather than suggesting that the cookbook contained substantial urban-planning research.
14. Cross-Domain Editorial Concept
The unusual aspect of the project was the combination of:
Culinary Publishing
+
Personal Academic Identity
The cookbook remained primarily culinary.
The architecture / urbanism sections acted as a personalization layer.
That makes the project a useful example of editorial concept development.
The goal was not simply to assemble recipes.
The goal was to give the book a recognizable identity.
15. Cover Design
The complete cover system was designed as part of the project.
This included:
- front cover,
- back cover,
- spine,
- visual collage,
- title treatment,
- decorative patterns,
- color system,
- and author presentation.
The surviving cover design uses:
- deep red / burgundy tones,
- Iranian decorative motifs,
- historical and cultural food-related imagery,
- Persian title typography,
- English subtitle,
- and full wraparound book composition.
The cover was designed as a complete physical-book object rather than a standalone front image.
16. Physical Book Design
The surviving physical copies demonstrate that the cover design translated into actual hardcover output.
The book was produced with:
- hard cover,
- printed spine,
- full wraparound artwork,
- and a finished physical presentation.
That is important because the project crossed the full path from digital design to physical artifact.
17. Visual Identity
The project used a strong Persian visual identity.
Elements included:
- traditional decorative patterns,
- Persian cultural imagery,
- culinary imagery,
- historical atmosphere,
- deep red color fields,
- and a gold / turquoise accent palette.
The result was not a neutral international cookbook aesthetic.
It intentionally reflected a Persian cultural character.
18. Design Ownership
All major design decisions were handled directly as part of the project.
This included:
- overall visual concept,
- cover system,
- page design,
- typography,
- content composition,
- image arrangement,
- and final production.
The project therefore demonstrates both creative direction and hands-on production.
19. Tooling
The final production workflow was completed primarily in:
- Adobe Photoshop
but the broader production work also involved multiple supporting tools during the process.
For public portfolio use, the safest description is:
Final production and page composition were completed in Adobe Photoshop, supported by additional design and document-processing tools during the workflow.
Specific additional tools can be added later if archive files confirm their role.
20. Why Photoshop Matters Here
Using Photoshop for a publication of this size is unusual compared with dedicated editorial tools such as InDesign.
That means the workflow required careful manual management of:
- page dimensions,
- typography,
- raster assets,
- alignment,
- repeated layout structure,
- print resolution,
- and export preparation.
The portfolio should not present this as the recommended modern workflow.
Instead, it demonstrates adaptability and the ability to complete a large production project with the available toolchain.
21. Publication Path
The project obtained an ISBN.
A broader print run was considered but did not proceed.
Later, two private physical copies were printed in Finland and presented there.
The correct public wording is therefore:
ISBN obtained; the project remained a private publication, with two physical copies later produced in Finland.
This avoids overstating the project as a commercial mass-market release.
22. Publication Boundary
Do not describe the project as:
- a mass-market published bestseller,
- a commercial print run,
- or a nationally distributed cookbook.
The accurate description is:
- completed book,
- print-ready master,
- ISBN obtained,
- private physical copies produced.
This is already sufficient to demonstrate end-to-end delivery.
23. Intellectual Contribution Boundary
The cookbook should not be positioned as if every recipe was independently invented by the production designer.
The culinary knowledge came from:
- the named author’s cooking activity,
- the user’s mother,
- other family members,
- and broader family knowledge.
My contribution was the complete transformation of that material into a finished publication.
This distinction is essential.
24. Production Architecture
A useful way to model the project is:
Family Recipe Knowledge
↓
Recipe Selection
↓
Dish Preparation
↓
Step-by-Step Explanation
↓
Text Documentation
↓
Photography / Image Acquisition
↓
Image Processing
↓
Page Composition
↓
Chapter Organization
↓
Architecture Interludes
↓
Cover / Spine / Back Cover
↓
Print-Ready Master
↓
Private Physical Copies
25. Information Architecture
With approximately 240 recipes, organization becomes a major concern.
The content required a consistent hierarchy across:
- sections,
- recipe pages,
- visual assets,
- chapter separators,
- and supporting interludes.
This makes the project relevant not only as graphic design but also as information architecture.
26. Image Pipeline
The image workflow had several possible sources:
Project-Specific Photography
+
Family-Contributed Photography
+
External Reference Imagery
↓
Image Selection
↓
Color / Crop / Cleanup
↓
Page Integration
This mixed-source model should be stated accurately.
It reflects the practical realities of producing a large cookbook rather than implying a fully studio-produced food photography project.
27. Editorial Consistency at Scale
A 275-page book creates a repetition problem.
Without a clear page system, a project like this quickly becomes visually inconsistent.
The production therefore depended on repeatable rules for:
- spacing,
- text placement,
- headings,
- ingredient blocks,
- step numbering,
- image placement,
- margins,
- and visual hierarchy.
This is similar to a design system in software:
Reusable Rules
↓
Consistent Output
↓
Lower Production Friction
↓
More Predictable User Experience
28. Product Thinking
The project can be understood as a product rather than simply a file.
It had:
- an intended owner identity,
- a target audience,
- a visual language,
- a content model,
- a physical form,
- and a finished delivery artifact.
The project therefore required product-level decisions about how all of those dimensions should work together.
29. Cultural Design
The cover and decorative system draw on Iranian cultural imagery.
This was a deliberate design choice.
The cookbook was not designed as a generic Western recipe book translated into Persian.
Its identity was rooted in Persian visual culture.
That gave the final artifact a distinctive character.
30. Educational Value
Although the project was not primarily a formal training textbook, each recipe still had an instructional role.
Readers needed to understand:
- ingredients,
- sequence,
- preparation logic,
- and final result.
The page design therefore had to support instruction as well as aesthetics.
31. Evidence from Surviving Files
The current surviving material includes:
- the full 275-page master file,
- recipe-page examples,
- architecture / urbanism interlude examples,
- full cover artwork,
- photographs of physical hardcover copies,
- and project source files retained in the original archive.
This provides strong evidence that the project was actually completed.
32. Evidence Strength
This project is particularly useful as portfolio evidence because it has both:
Digital Source Evidence
+
Physical Output Evidence
Many old creative projects survive only as memories.
This one has tangible artifacts.
33. What the Project Demonstrates
The project demonstrates:
Editorial
- content structuring
- recipe documentation
- long-form publishing
- RTL page design
- consistency across hundreds of pages
Visual
- cover design
- page layout
- cultural visual identity
- image composition
- photography
- image processing
Production
- print preparation
- ISBN workflow
- physical book production
- master-file ownership
Project Execution
- end-to-end ownership
- ambiguous-source transformation
- coordination of family knowledge
- multi-source asset management
- complete product delivery
34. Why This Is More Than Graphic Design
The project should not be reduced to:
“Designed a cookbook cover.”
The real work involved:
Content
+
Photography
+
Editorial Structure
+
Visual System
+
Book Design
+
Print Production
That makes it a significantly broader project.
35. Transferable Professional Value
The domain is culinary publishing, but the transferable capabilities include:
- turning informal knowledge into structured documentation,
- working with incomplete source material,
- designing repeatable content systems,
- managing hundreds of content items,
- combining visual and textual information,
- maintaining consistency at scale,
- and delivering a physical production artifact.
These abilities transfer directly into:
- documentation,
- content platforms,
- knowledge systems,
- educational products,
- design systems,
- product development,
- and technical publishing.
36. Senior-Level Interpretation
The strongest senior-level interpretation is:
I owned the transformation of a loosely defined personal cookbook idea into a complete 275-page publication system, including content capture, photography, editorial architecture, visual identity, physical cover design, print preparation, and final production.
The value lies in ownership under ambiguity.
37. Recommended Website Hero
Dream of a Chef
Cookbook Production · Editorial Design · Food Photography · Visual Identity · Print Preparation
A 275-page Persian cookbook containing approximately 240 recipes, developed end-to-end from family culinary knowledge and practical cooking sessions. The project included recipe documentation, original and sourced food imagery, full editorial and page design, cover/spine/back-cover production, short architecture-inspired interludes, ISBN preparation, and private physical printing.
38. Website Project Card
Dream of a Chef
275 Pages · ~240 Recipes · Editorial Design · Photography · Print Production
Transformed family culinary knowledge into a complete Persian cookbook through recipe documentation, food photography, page design, visual identity, architecture-inspired interludes, cover production, and print-ready delivery.
39. Short Website Card
Dream of a Chef
A 275-page Persian cookbook built from family recipe knowledge, combining ~240 recipes, photography, editorial design, Persian visual identity, and complete physical-book production.
40. CV Entry
Dream of a Chef — Cookbook Publishing & Editorial Production
Produced a 275-page Persian cookbook containing approximately 240 recipes from family culinary knowledge and practical cooking sessions. Led recipe documentation, photography and image preparation, editorial structuring, RTL page design, visual identity, cover/spine/back-cover production, and print-ready delivery; ISBN was obtained and private physical copies were produced.
41. Short CV Entry
Produced a 275-page Persian cookbook with ~240 recipes, managing content documentation, photography, editorial design, visual identity, cover production, and print preparation end-to-end.
42. Portfolio One-Liner
A complete 275-page Persian cookbook production project combining family culinary knowledge, photography, editorial systems, cultural visual design, and physical print delivery.
43. Interview Story
Situation
A family member wanted a cookbook under her name.
The culinary material did not exist as a complete manuscript and had to be assembled through family knowledge, practical cooking, and verbal explanation.
The owner also had an academic background in urban planning and wanted part of that identity represented inside the book.
Task
Turn the idea into a complete physical cookbook.
Action
I collected and structured the recipe material, documented approximately 240 recipes, managed photography and image sourcing, created the internal page system, designed the visual identity, developed short architecture-related interludes, produced the complete cover/spine/back cover, prepared the 275-page master file, and took the project through ISBN and private-print preparation.
Result
The project became a complete print-ready cookbook, with an ISBN and two physical hardcover copies later produced in Finland.
44. Technical / Production Interview Version
“The interesting part of this project was scale and source ambiguity. There was no finished manuscript. Recipes came from my mother, other family members, and practical cooking sessions. I had to turn spoken instructions into consistent recipe pages, manage around 240 recipes across 275 pages, produce or source the imagery, maintain an RTL editorial system, design the complete visual identity and physical cover, and prepare the final book for print. The urban-planning component was intentionally small—short visual interludes, such as a kitchen ‘points of view’ page—because the named author had studied urban planning. The project ultimately received an ISBN and two private hardcover copies were produced in Finland.”
45. Recruiter-Oriented Interpretation
Although this is not a software project, it provides strong evidence of:
End-to-End Ownership
+
Information Architecture
+
Design-System Thinking
+
Content Operations
+
Visual Production
+
Delivery Discipline
It is useful portfolio breadth for roles where ownership and multidisciplinary execution matter.
46. Portfolio Classification
Recommended primary categories:
- Books
- Publishing
- Editorial Design
- Visual Production
Secondary categories:
- Photography
- Information Architecture
- Persian / RTL Publishing
- Creative Production
For a software-architecture CV, this is better treated as portfolio evidence / breadth rather than a core software project.
47. Technology / Tool Tags
Known / defensible tags:
Adobe Photoshop
Editorial Design
RTL Publishing
Food Photography
Image Processing
Print Production
Book Design
Persian Typography
Information Architecture
Content Structuring
Visual Identity
Photography
Additional historic tools should only be added after archive verification.
48. Suggested Website Metadata
Page Title
Dream of a Chef — Persian Cookbook Publishing & Editorial Design
Meta Description
A 275-page Persian cookbook project with approximately 240 recipes, developed through family culinary knowledge, recipe documentation, food photography, editorial design, RTL publishing, visual identity, and print-ready production.
Suggested Slug
/dream-of-a-chef
Alternative:
/books/dream-of-a-chef
49. Evidence Boundaries
Safe public claims:
- completed in 2017,
- 275-page master file,
- approximately 240 recipes,
- complete visual / editorial production handled by me,
- original food photography used where dishes were prepared,
- some imagery came from family or external sources,
- short architecture / urbanism-related visual interludes existed,
- complete cover/spine/back-cover design,
- ISBN obtained,
- two physical copies later printed in Finland,
- original source files remain in my archive.
Avoid claiming:
- authorship of every recipe,
- invention of all culinary content,
- original photography for every image,
- a mass commercial print run,
- national distribution,
- extensive academic urban-planning content.
50. Archive Value
The original source files are still retained.
That means a future portfolio update could include:
- selected interior spreads,
- before/after editorial reconstruction,
- recipe-page samples,
- cover-development examples,
- photo-production examples,
- and a reconstructed digital edition.
This gives the project unusually strong archival potential.
51. Possible Modern V2
If rebuilt today, the project could be transformed into a hybrid publishing product:
Print Book
+
Responsive Web Edition
+
Recipe Search
+
Ingredient Filters
+
Structured Recipe Data
+
Image Gallery
+
Printable Recipe Cards
+
Multilingual Content
Possible data model:
Recipe
├── Title
├── Category
├── Ingredients[]
├── Steps[]
├── Images[]
├── Preparation Time
├── Serving Size
└── Notes
The architecture interludes could become optional editorial articles.
52. Modern V2 — Data-Driven Publishing
A modern rebuild could separate content from presentation.
Structured Recipe Database
↓
Web Application
↓
Print Generator
↓
PDF / EPUB / Web
This would allow the same source content to support:
- website,
- print,
- mobile,
- search,
- and future editions.
53. Modern V2 — Media Workflow
The image pipeline could also be modernized:
Original Media
↓
Asset Management
↓
Automatic Resize / Optimization
↓
Web Variants
↓
Print Variants
This would remove much of the manual image handling required in the original Photoshop-based workflow.
54. Why the Historical Workflow Still Matters
The original workflow was tool-heavy and highly manual by modern standards.
That does not reduce its value.
It demonstrates the ability to deliver a large project before modern content-management and automated-publishing workflows were available in the current form.
The project solved the problem with the tools available at the time.
55. Final Portfolio Statement
Dream of a Chef was a 275-page Persian cookbook production project completed in 2017, containing approximately 240 recipes assembled from family culinary knowledge and practical cooking sessions. I handled the project end-to-end on the production side: recipe documentation, photography and image management, editorial structuring, RTL page design, cultural visual identity, architecture-inspired interludes, complete cover/spine/back-cover production, ISBN preparation, and print-ready delivery. The final project remained a private publication, with two hardcover copies later produced in Finland.
56. One-Line Summary
Built a 275-page Persian cookbook from family culinary knowledge, combining ~240 recipes, photography, editorial systems, RTL design, and complete print production.
57. Ultra-Short Portfolio Label
Dream of a Chef — Cookbook Publishing, Editorial Design & Visual Production