// blog
Practical articles on naming software projects, domains, and products.
A Slack bot has a display name and a username, and they follow different rules. Here is what Slack actually enforces, and what happens when your chosen username is already taken in a workspace.
Read article →Google has strict, specific rules about what you can and cannot call your Chrome extension, and violating them is one of the most common reasons a submission gets flagged. Here is what the rules actually say.
Read article →GitHub Actions have naming rules stricter than most developers expect, plus an unresolved debate about hyphens versus underscores that even GitHub's own team has not settled. Here is how to name yours correctly the first time.
Read article →Your extension has two names, not one, and most developers only think about the one nobody searches for. Here is how naming actually works in the VS Code Marketplace.
Read article →The name of your library is the first thing a developer sees in a README, a search result, and an import statement. Here is what separates names that get starred from names that get skipped.
Read article →You picked a great name. Then you tried to register it as a domain, an npm package, a GitHub repo, and an App Store listing. Here is why SaaS names fail in practice and how to check yours before committing.
Read article →You built it in a weekend. Now it needs a name that survives GitHub, npm, a domain check, and a Google search. Here is what actually works, and what wastes your time.
Read article →A CLI command lives or dies by how it feels to type a hundred times a day. Here are the real rules, with examples of names that worked and names that had to be abandoned.
Read article →Your project's name has to survive contact with GitHub, npm, and Google all at once. Here is how to pick one that does, with real examples of names that failed and why.
Read article →npm package names are permanent once published. Here's exactly what npm allows, what conventions developers actually follow, and how to avoid a name you'll regret in a year.
Read article →Naming a GitHub repo wrong costs you contributors, SEO, and sanity. Here are the naming conventions developers actually follow — with real examples and mistakes to avoid.
Read article →Naming a side project shouldn't take longer than building it. A practical guide to finding a name that sticks — with examples, rules, and free tools.
Read article →