Archive: for small teams and the first month
Delivered drafts sit in an archive inside the account. An editor opens the item, reads the draft with its sources & checks, copies what is needed into the CMS and records the review. No setup, full control, slow at volume. Right for one Stream and a couple of items a day.
Private RSS feed: for CMS importers
Most newsroom systems can import from RSS. A private full-text feed per Stream carries the complete draft, not a teaser, at an address only your organisation knows. Point your CMS importer at it and drafts appear as unpublished items ready for review. Keep the address private: anyone who has it can read the feed. Rotate it if it leaks.
What to check in your importer: that it creates drafts, not published posts; that it keeps the source and image information; that it does not re-import the same item after an update.
API: for deeper integration
When a publishing group wants delivered material inside its own systems, the API returns the same items with their attached context. Typical uses: a custom review queue, routing drafts to different desks, storing the sources record next to the published article. This needs a developer and an API key kept out of the front end.
Whichever channel you use
- Drafts arrive as drafts. Nothing should publish without a person.
- Keep the sources record with the article; you will want it when a reader asks.
- Apply corrections through the same channel they arrive on.
How this works in Doxx
Every Doxx plan delivers through all three channels: the archive in the account, a private full-text RSS feed per Stream and the API. Setup is described on the how it works page. Start with the archive; switch to the feed when reviewing in the CMS becomes faster than copying.
Create a Stream, then connect the feed once the first drafts have arrived.