Skip to main content

The GDS Way and its content is intended for internal use by the GDS community.

How to name software products

Read this guide when you need to name components for your software product, for example applications, software libraries, plugins or frameworks. Your users should understand what something does from its name.

Your product name should be self-descriptive

Avoid using puns or branding for names as this makes it difficult for others to understand what it does.

Make sure you use the same name consistently whenever you’re referring to the same product. For example the name of the Signon application’s GitHub repository is alphagov/signon.

These GDS product names clearly communicate their purpose:

These GDS product names are ambiguous and possibly confusing:

Further reading

The Service Manual has guidance on naming services, and this will be relevant when naming applications or packages.

This page was last reviewed on 3 May 2024. It needs to be reviewed again on 3 November 2024 by the page owner #gds-way .
This page was set to be reviewed before 3 November 2024 by the page owner #gds-way. This might mean the content is out of date.