Ashutosh Bhosale

Name the content format when possible. Words like guide, recap, tutorial, itinerary, and packing list tell the user what formats the template is best suited for.

Indicate the niche. The title or description must help users identify whether the template matches their domain. Together, format and niche communicate the full use case.

Flag customization when it matters. When a template is flexible enough to use beyond its obvious use cases, the description should say so, giving users permission to mix and match.

Most descriptions led with the aesthetic, not the use case. Across most of the descriptions, I led with a brief visual reference before arriving at the use case. For example, "This template's beautiful blue-green palette will let you create helpful travel and backpacking stories" opens with a visual, then pivots immediately to the use case in the same sentence. The use case always got there, but it didn't always come first. In a template gallery where users are scanning quickly, leading with the use case every time (and putting visuals secondary) would serve them better. The three descriptions where I did lead directly with the use case: Summer Fashion Collection, Kitchen Stories, and All About Cars, are the clearest and most immediately scannable of the set.

Some titles were too geographically specific. Titles like "Pizzas in NYC" limit their perceived audience by naming a place. A creator in Mumbai or Lagos is less likely to reach for a template with "New York" in the name, even if it would work perfectly for their content. I'd generalize this to something like "Food Tour Story." It signals the same format, but has a global reach.

A few descriptions described audience outcomes that were incomplete. In a creator tool, mentioning what the audience will feel is legitimate, but the feeling needs to be tied to a specific outcome to be actionable. For example, "visual articles that will enthuse and motivate your audience" starts the right thought but doesn't finish it. Motivated to do what? A stronger version would be "inspire your audience to plan their next city trip." That completes the thought, giving the creator a clear picture of what job this template helps them accomplish.

I'd document the naming rules for future contributors. When you write the first set of template names, you're also implicitly creating the rules for the next hundred. I didn't document those rules at the time. There was no brief going in, and I didn't create one going out. But now I'd write a short naming spec covering: title format (2-4 words, use-case-led), description length limit (2 sentences max), forbidden patterns (no geographic specificity unless intentional, no superlatives without evidence), and localization flags. That would make the system scalable beyond the first batch.