// blog
Practical articles on naming software projects, domains, and products.
WordPress's own Plugin Handbook says an unused slug can be reassigned to another developer, and your Text Domain has to match your slug exactly. Here is what the official rules require.
Read article →A Discord bot has an application name and a username, and only one of them follows Discord's strict character rules. Here is what those rules actually are, and a real lesson from an open source project that had too many bots with the same name.
Read article →Figma's own guidelines show exactly what is allowed and what is not when it comes to using their name in your plugin. Here is the rule, the examples, and what else affects whether your plugin gets found.
Read article →Raycast extensions have a name field and a title field that follow different rules, plus commands with their own naming structure. Here is how to name yours clearly, sourced from Raycast's own developer documentation.
Read article →A domain generator proposes candidates; it does not confirm registration status, prior use, trademark conflicts, or renewal terms. Use this due-diligence checklist before buying.
Read article →A practical framework for choosing an app name that is clear, distinctive, easy to search, and suitable for independent store and trademark checks.
Read article →Every startup naming guide asks this question in the abstract. For a developer founder, it is actually four separate technical decisions: your GitHub org, your npm scope, your domain, and your legal entity. Here is how they interact.
Read article →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 →A practical guide to choosing a clear Chrome extension name while following Chrome Web Store branding, metadata, and impersonation policies.
Read article →GitHub Actions have a display name, repository name, and Marketplace listing constraints. This guide explains how to keep those identifiers clear and consistent.
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 →Choose a clear library or SDK name that works in documentation, import statements, package registries, and repository searches.
Read article →A name that tests well in a pitch deck still has to work as a domain, a repo slug, a package name, a CLI command, an App Store listing, a support email address, and something you can say out loud. Here is how to stress-test a SaaS name across every technical environment before you commit to it.
Read article →A micro-SaaS name usually gets picked before the product is validated. Here is how to choose one that can survive a customer pivot, plus a practical keep, adjust, or rename framework for founders who already have users.
Read article →A practical guide to choosing a short, memorable CLI command, with usability checks and examples from established tools.
Read article →An open-source project name may need to work across GitHub, package registries, search results, and documentation. Use this checklist to reduce naming collisions.
Read article →Learn npm's package-name rules, common community conventions, and checks to make before publishing a package.
Read article →A practical guide to choosing a clear GitHub repository name, with common conventions, 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 →