Editions and publishing

Editions and weekly change sets as PDF, web and JSON

Freeze approved paragraphs into a dated set, run the checks, and publish PDF, web pages and JSON from the same approved source.

Editions and weekly sets: group approved paragraphs with exact versions recorded

An edition is a full publication. A weekly change set holds only what changed that week. Both record the exact paragraph versions they contain.

Create the edition or weekly change set
Open Editions, select Create an edition, choose edition or weekly set, then set the label and the period it covers.
Add approved paragraphs in order
Add paragraphs in reading order. The list accepts only paragraphs with status approved. If a paragraph is still in draft or in review, send it for approval first.
Compare the set with the last published edition
Open the edition detail, compare it with the last edition, and read the linked change requests. Confirm each paragraph version is the one you want to publish.
Run the checks and lock the set
Run Checks for geography, chart numbers, broken references, headings, alt text and language. Fix each blocking item in the paragraph, re-run the check, then lock the set.
Publish it as one unit, and correct it in a new set
Publish the locked set. A published edition is locked, so a correction always creates a new edition or weekly set rather than editing the published one.

Choose the outputs for the locked set, run the checklist, preview, and publish. One source produces each output as a separate transform.

Choose the edition or weekly set
Open Publishing, choose the locked edition or weekly set, and confirm every paragraph in it is approved.
Choose PDF, web pages, JSON or more than one
Select the formats you need. PDF is for print, web pages are for reading on a phone or computer, and JSON is for downstream data users.
Run the approval and completeness checklist
Confirm approval is recorded for every paragraph, required fields are complete, and blocking checks have passed. Publishing is blocked while any item fails.
Preview, then publish
Preview the output, check the edition date and paragraph order, then select Publish. The build records the snapshot it was built from.
Confirm the files produced
Open Output history, confirm each file name, format and date, and download a copy. Each output shows the snapshot it came from so it can be reproduced.
When a build fails, fix it and try again
Open the failed build log, read what failed and which paragraphs were involved, fix those paragraphs, then run the build again. The prior published files stay live until the new build succeeds.

Print ready pages for reading and printing, built from the locked snapshot with the same edition date as the web pages and JSON.

Readable pages by chapter and paragraph, with geography, chart numbers, edition date and a report a change link on each page.

A data file with paragraph text, type, geography, chart numbers, edition and change date for downstream systems, from the same snapshot.

Every save keeps a version. Restore an earlier version as a new version, so history is never lost.

Open the paragraph history
Open the paragraph, select History, and read each version with author, date and reason.
Compare two versions
Select two versions to compare them side by side before you decide what to restore.
Restore as a new version
Select Restore on the version you want. The restored text becomes the new current version, and later history stays in the list.
Trace a change request to its edition
Open the change request, follow the link to the paragraph version, then follow that version to the edition or weekly set that published it.

Collect approved paragraphs, run the checks, compare the set, and mark it ready to publish.