Table of contents

Name a new application or gem

This describes how you should name an application or gem on GOV.UK. It was first proposed in RFC 63.

Naming applications

Firstly, the service manual has good guidance on naming things.

The most important rules:

  • The name should be self-descriptive. No branding or puns.
  • Use dashes for the URL and GitHub repo
  • The name of the app should be the same on GitHub, Puppet and hostname

Publishing applications

Applications that publish things are named x-publisher.


  • specialist-publisher
  • manuals-publisher

Not so good:

  • publisher (too generic)
  • contacts-admin (could be contacts-publisher)

Frontend applications

Applications that render content to end users on GOV.UK are named x-frontend


  • government-frontend
  • email-alert-frontend

Not so good:

  • collections (could be collections-frontend)
  • frontend (too generic)


Applications that just expose an API are named x-api.


  • publishing-api
  • email-alert-api
  • router-api

Not so good:

  • rummager (should be search-api)

Admin applications

Applications that “manage” things can be called x-manager or x-admin or thing-doer.


  • search-admin
  • local-links-manager
  • content-tagger

No so good:

  • signonotron2000
  • maslow (needs-manager)

Naming gems

  • Use the official Rubygems naming convention
  • Use underscores for multiple words
  • Use govuk_ prefix if the gem is only interesting to projects within GOV.UK


  • govuk_sidekiq
  • govuk_content_models
  • govuk_admin_template
  • vcloud-edge_gateway

Not so good:

  • slimmer
  • plek
  • gds-sso (should be gds_sso, or govuk_sso)
This page was last reviewed . It needs to be reviewed again by the page owner #2ndline.