Ashutosh Bhosale

Lead with the use case, not the aesthetic. Users scan by content type: travel, food, tech, fitness. The title had to answer "what is this for?" before anything else.

Name the content format when possible. Words like guide, recap, tutorial, itinerary, and packing list tell the user what to make and how to structure it.

Descriptions answer "what can I make?", and not "what does this look like?" Visual style is secondary. The description's primary job is to help users picture themselves using the template.

Reference visuals only when they serve the use case. I only mentioned a design element, like a color palette, a layout feature, or a sticker, when it directly helped the user understand what the template was built for, or what kind of content it suited best.

Plain, global English throughout. The plugin is used worldwide. No idioms, no culturally specific references unless the template itself was explicitly themed.

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

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.