Build a weekly change set
Publication managers can build a weekly set that is ready to publish. The set gathers approved paragraphs only and records the exact versions it contains.
Steps
Plan the week first, then freeze the set so every output is built from the same approved source.
Create the weekly change set
Open Editions, choose New weekly change set, select the publication, and set the label and the period the set covers.
Collect approved paragraphs
Add approved paragraphs in order. Only paragraphs that show as approved can enter the set. Add each paragraph version exactly as it was approved.
Run checks
Run the pre publish checks for geography, chart numbers, broken references, headings, text alternatives, language, contrast and keyboard use. Fix each blocking item in the paragraph and run the check again.
Compare with the last edition
Open the diff against the last published edition. Confirm each change matches a resolved change request or an approved edit, and that no draft or returned text is included.
Lock the set
Confirm the readiness list is clear, then lock the set. A locked set cannot be edited. A correction after publish creates a new set.
Check
Confirm the set is frozen and approved before you publish it.
- Every paragraph in the set shows as approved.
- Each item records the exact paragraph version it contains.
- The checks list passes with no blocking item open.
- The diff shows only the approved changes for the week.
- The set shows as locked and ready to publish.
- The last published edition is untouched.
Edition compared with weekly set
Two kinds of release, one rule for approval.
Edition
A named release of a publication that freezes many approved paragraphs. A published edition is locked and a correction creates a new edition or set.
Weekly change set
A smaller release for the week that gathers the approved changes as one unit, so readers can see what changed and when.
Outputs from one source
PDF, web pages and JSON are built from the same approved snapshot. Each output records the snapshot it was built from so it can be reproduced.
Publish steps: Publish an edition. Feature detail: Editions and publishing.
What a reader can check
Every public page and file carries the edition date and the paragraph reference, so a reader can tell what changed and when. Draft text is kept out of public search, downloads and links.
- Accessibility checks run before publish and the result is kept on the release record.
- Change requests that drove the edits link to the paragraphs they changed.
Plan your weekly cycle
Ask for a walkthrough that covers the weekly set from collection to published files.