Almost everybody who looks into plant-based eating gives up during the research phase. Not because the information is hard to find — because there is too much of it, all of it is long, and most of it wants something. A book. A subscription. A commitment to an identity before you have made a single meal.

Plant Based Minutes takes the opposite approach: one 60-second video a day, published to YouTube, with a full written guide sitting behind each one. Sixty seconds is the whole pitch. It is short enough that nobody has to decide whether it is worth the time.

Two formats, one piece of content

The interesting structural decision here is that every topic exists twice.

The video is the hook. It is fast, it lives on YouTube where discovery actually happens, and it makes one point. The written guide is the substance — the version you read when the sixty seconds worked and you want the detail. There are 41 written guides live.

Most content operations pick one of these and treat the other as an afterthought. A video channel with a neglected blog, or a blog with some videos embedded because someone said video was important. Both halves end up weaker than they should be.

Pairing them properly means the site has a real content model rather than a page-per-post list. A topic is an entity. It has a video, it has a guide, and both need to render well on their own — because the two halves are found in completely different ways. The video is found by YouTube's recommendation system. The guide is found by search. Neither audience should land on something that reads like the leftover half of something else.

Six categories that are genuinely different

The content spans six categories: Recipe, Nutrition, Health, Environment, Animals, and Humour.

That last one is the tell. A taxonomy that runs Recipe / Nutrition / Health / Environment / Animals is a wellness content plan. Adding Humour to it changes what the whole thing is.

The five serious categories map to the five distinct reasons people actually arrive at this subject — practical cooking, macro and micronutrient questions, personal health, environmental impact, and animal welfare. Those are not variations on a theme; someone deep in the environmental argument may have zero interest in recipes, and vice versa. Treating them as one undifferentiated stream serves nobody well.

Humour exists because this topic has a well-earned reputation for being preachy, and a category that can laugh at itself is a structural defence against that. It is a content decision, but it is also a product decision, and it shapes the tone of everything around it.

Building on the YouTube Data API

The site uses the YouTube Data API, and that choice carries consequences worth being explicit about.

The upside is obvious: YouTube stays the system of record for video. Uploads happen there, playback happens there, the recommendation engine works on the publisher's behalf, and the site never has to solve video hosting, transcoding, bandwidth, or a player. For a daily publishing cadence that is a very large amount of infrastructure not built.

The cost is that a daily-publishing site now depends on a third-party API. Any integration like this has to be built defensively. API responses have to be treated as data that can be late, rate-limited, or temporarily unavailable, and the site cannot fall over on any of those. When you are publishing once a day, every day, an integration that fails ungracefully is not an edge case — it is a matter of when.

Getting that boundary right is unglamorous work that nobody notices when it is done properly, which is exactly the profile of the work that separates a site that survives its first year from one that quietly breaks.

The 30-day challenge is the product

A daily video is a stream. A stream is easy to sample and easy to drift away from — there is no beginning, no end, and no reason today's episode matters more than yesterday's.

The 30-day challenge converts that stream into something with a shape. It has a start, a finish, and a reason to come back tomorrow specifically. It turns passive consumption into a commitment the visitor makes to themselves, which is a fundamentally different relationship with a site.

Structurally it is also the thing that justifies the email list. An email list attached to a content stream is a newsletter nobody asked for. An email list attached to a 30-day challenge is the mechanism that makes the challenge work — it is the reminder, and the reminder is the product. Same feature, completely different value, depending entirely on what it is wrapped around.

Topic collections do similar work from another angle, giving someone who arrived for one recipe a curated path through related material instead of dropping them back into a reverse-chronological feed.

What kind of build this is

Plant Based Minutes is a website-plus-app project. It looks like a content site, and a lot of it is one, but there is real product underneath: a two-format content model, an external API integration on the critical path, a challenge structure with its own state, collections, and an email capture that has a job to do.

None of that is platform-scale. There are no accounts to manage, no user-generated content to moderate, no marketplace, no billing. Recognising the difference is what keeps a project like this affordable — a daily-publishing content business does not need the infrastructure of a social network, and building it that way would consume the entire budget before the first video shipped.

One video a day, 41 guides, six categories, and a challenge that gives it all somewhere to go.