Sometimes it may be necessary to republish content to make it show up on the website. For example if we make an update to govspeak that would require us to re-render and save new HTML for content.
This process varies per app and requires
If the documents are in Whitehall, there are Rake tasks you can run as outlined below. Try to pick the one most focused to the scope of what you need to republish to avoid unnecessary load. You can monitor the effect on the publishing queue via these Grafana dashboards:
For organisations, run:
For all of a single document type, run:
You may wish to test first on Integration:
For a short list of Content IDs, run:
For a significant number of Content IDs:
Some preparation is needed for this as a CSV file needs to be in place. The CSV should have a column called content_id that contains all the relevant IDS. This should be added to the whitehall repository at:
Ensure that the CSV is removed again after the job completes.
To republish all documents: Caution: this is a lot of content and will take hours to complete. If it is possible to scope the republish do so and use a different task, but if you have made a change such as something in govspeak that will affect the majority of content, this is available. Before running this job confirm with 2nd line that they are happy for you to proceed as it could cause backed up publishing queues and alerts.
If the document is in content publisher, there is a resync Rake task you can run.
You can resync a single document by passing it a content ID and locale:
or you can resync all documents: