Application: content-publisher

Publishing application for GOV.UK

• GitHub: content-publisher
• Ownership: #govuk-publishing-experience-tech
• Hosting: AWS, on the backend machine class
• Category: Publishing apps
• Rake tasks: Run a Rake task on Integration, Staging or ⚠️ Production ⚠️
• Links:
  • content-publisher.publishing.service.gov.uk
  • Sentry (error tracking)
  • Puppet configuration
  • Deploy scripts
  • Deployment dashboard

Example pages published by content-publisher

• UKHSA update on scarlet fever and invasive Group A strep
• Up to £600 for pensioners arrive in bank accounts from today
• HM Land Registry arrangements for Royal Mail strikes
• £324 payment to hit bank accounts from today
• Over eight million households to receive second Cost of Living Payment from 8 November
• COVID-19 variants identified in the UK – latest updates
• Over seven million £324 payments made to families by government in last week alone
• State Pension and benefit rates for 2022 to 2023 confirmed
• £150 Disability Cost of Living Payments begin this month
• Administrative Earnings Threshold to rise for Universal Credit Jobseekers

README

A unified publishing application for content on GOV.UK

Nomenclature

• Content - Some text (and related fields) a user wants to publish
• Revision - A version of a piece of content in a particular locale
• Edition - A revision that is in the Publishing API
• Document - All revisions of a piece of content in a particular locale

Technical documentation

This is a Ruby on Rails app, and should follow our Rails app conventions.

You can use the GOV.UK Docker environment to run the application and its tests with all the necessary dependencies. Follow the usage instructions to get started.

Use GOV.UK Docker to run any commands that follow.

Before running the app

The first time you run this application for development, enable debug and pre_release_features permissions:

bundle exec rake development_permissions

To enable them for your GOV.UK account add them to your account in Signon.

Running the test suite

bundle exec rake

To run JavaScript tests (only):

# run JS tests in browser
yarn run jasmine:browser

# run JS tests on command line
yarn run jasmine:ci

Our test environment is setup to render ‘real’ error pages, instead of raising an exception. This can make it hard to debug a test failure, as the actual error won’t appear in the test output. Instead, you can see it in log/test.log.

Further documentation

• Approach to analytics
• Editing change note history
• History mode
• Importing documents from Whitehall
• Removing documents
• Scheduled publishing
• Testing strategy
• User permissions

Licence

MIT License