// blog
Practical articles on naming software projects, domains, and products.
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 →