Table of contents

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

How to name software products

This document is current until 30 June 2018

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.

Ensure 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 good guidance for naming services, and this will be relevant when naming applications or packages.