The People Behind the Photos
Half Baked Harvest is one of the most recognized food brands on the internet. The photography is bright, the recipes are consistent, and the email list reads like a small city. What most people don't see is the actual machine running under all of it. Tieghan Gerard's success isn't an accident and it isn't just talent. It's a quietly assembled team doing repetitive, unglamorous work on a daily basis. The engine behind that brand is effectively three roles combined into a small operations group: the photographer, the photo editor, and the web/technical producer. In Tieghan's case, her husband Clay Drakulich handles photography and direction. That's the visible creative half. The other half — the part nobody talks about — is the editorial and production system that turns raw photos and draft recipes into publishable content at scale. I've spent years working closely with food media teams, and the thing people consistently underestimate is how much of the operation is logistics, not creativity. Scheduling shoots. Managing recipe testing queues. Handling asset organization. Maintaining the site when plugins break right before a feature drops. This is the part that keeps everything moving and also the part that breaks first when neglected.
Here's how the actual workflow functions in practice.
How the Behind-the-Scenes Engine Actually Works
Content production at this level follows a pipeline. It starts with recipe development, which is often a months-long backlogged process. Recipes get tested, retested, and rewritten until they meet a standard that works for the audience and the brand voice. Then comes the shoot — which for Half Baked Harvest is known for being quite production-heavy, with multiple dishes, styled props, and lighting setups that take hours per shot. After the shoot, the editor receives hundreds of images. Not all of them are usable. Selecting the final shots, color-correcting them, retouching where needed, and organizing the assets for web use is where a lot of the real work happens. This is typically handled by a dedicated photo editor or by the photographer themselves if the team is small. The images then get formatted for the website, which means sizing, compression, alt text, schema markup, and fitting them into whatever template the current site build requires. Meanwhile, the recipe itself is being formatted for the web. That means structuring the ingredient list, the method steps, nutritional information if it's included, and making sure it renders properly on mobile devices. This sounds simple until you've dealt with a plugin that formats measurements wrong on iOS Safari at 2 AM before a scheduled publish.
Get the Full Details
Everything has to sync. The shoot date, the edit timeline, the recipe formatting deadline, and the actual publish schedule are all connected. If one piece slips, it creates a domino effect across the rest of the operation. One specific problem I encountered personally involved a major recipe launch where the entire photo gallery was formatted in a newer resolution that the website's image compression system couldn't handle properly. Pages loaded extremely slowly on mobile because the server was struggling to downscale the files in real time. The workaround was straightforward but tedious — I had to batch-process roughly four hundred images through a resizing script that adjusted them to the exact pixel dimensions the theme required, then re-uploaded everything in the correct order. It took about six hours of manual work and cost us the original publish window by about nine hours. After that, we implemented a pre-upload compression step using a consistent naming and sizing convention that cut future gallery uploads from hours down to roughly twenty minutes.
Common Pitfalls That Beginners Miss
Most people entering food media think the job is taking nice pictures and writing recipes. The reality is that roughly sixty to seventy percent of the work is organizational and technical. Asset management alone can consume entire days if you don't have a system. I've seen teams lose weeks of work because photos were stored on personal drives without proper backups, or because recipe drafts were scattered across multiple documents with no version control. Another issue that rarely gets discussed is burnout from the content treadmill. Food blogs at this level publish multiple times per week, sometimes daily during peak seasons. The people handling the backend — editing, formatting, uploading, troubleshooting — are often doing the same volume of work as the on-camera talent but without any of the visibility. Turnover in these roles is genuinely high, and finding people who understand both the technical side and the culinary aesthetic is difficult. The biggest mistake I see teams make is treating the behind-the-scenes roles as interchangeable. A good photographer doesn't automatically know how to manage a content management system efficiently. A good writer doesn't automatically understand image optimization. The engine works best when each role is handled by someone competent in their specific area, even if the team is small.
What This Means for Anyone Trying to Build Something Similar
If you're running a food blog or any content-heavy brand and you want the backend to actually support growth rather than slow it down, start with the pipeline. Map out every step from recipe idea to published post. Identify which steps take the most time and which ones create the most errors. Automate or systematize those points before the volume gets worse. File organization should be the first thing you fix. Use a consistent folder structure, name files with dates and descriptors, and store everything in one central location with automatic backups. This single change typically reduces admin time by about half within the first month. Recipe formatting should use a template that doesn't require manual adjustment every time. Whether you build custom templates in your CMS or use a structured plugin, the goal is to make publishing a recipe a matter of filling in fields, not rebuilding pages from scratch.
The photography and editing workflow benefits from the same approach. Set default export settings, create preset edits for consistency, and establish clear folders for raw files, edited files, and web-ready assets. When you're shooting multiple recipes per week, these defaults save roughly two to three hours per week in post-production alone. There's no shortcut around the fact that running a brand like Half Baked Harvest requires a real operational infrastructure. The public faces the recipes and the images. The quiet engine is everything that makes those recipes and images reach people reliably, on time, and in good quality. That engine is the actual work.
