ArchieML docs
Text content for pages and embeds should be contained in a separate document, usually written in ArchieML syntax.
ArchieML is a loose markup language developed at the New York Times to quickly create structured data for web pages and graphics. It is designed to be “a format that could survive being edited by users who may never have seen ArchieML or any other markup language at all before.”
You can read more about ArchieML syntax basics on the project’s website.
ArchieML documents are downloaded as JSON files in your project, where they can then be added to pages and graphics as code.
Read more about working with ArchieML in conjunction with our graphics components here.
RNGS.io
RNGS.io is our preferred platform to write ArchieML docs for graphics. It includes a collaborative editor with many extra features for handling ArchieML “blocks” that correspond to our Reuters Graphics components.
Documents are called “stories” and are organised by project on “storyboards”.
When creating a new project, you will be prompted to create a new RNGS.io story and storyboard. You can also create stories using commands from your local project or in RNGS.io, directly.
RNGS.io client commands
sync
Sync all RNGS.io stories configured in your project with local JSON files.
pnpm stories:sync
new
Create a new story in RNGS.io.
pnpm stories:new
connect
Connect your project with a story created in RNGS.io.
pnpm stories:connect
live
Enable live updates from one or more RNGS.io stories. Read more in the section below.
pnpm stories:live
Live RNGS.io stories
You can create a live connection between your project and RNGS.io stories, meaning you won’t need to run the stories:sync
command in your project to update your page.
This is useful for creating preview pages that can be updated directly from RNGS.io by other editors.
Live docs in production
You can also create a live connection to the production version of your page, allowing others to update the content of your page without needing to republish it.
Google docs
Google docs is also a supported ArchieML editing platform.
While Google docs do not have many of the features that make RNGS.io a more powerful tool for publishing graphics pages (especially on deadline), they may be preferred if you need rich versioning features for your document.
To use Google docs, however, you’ll need to configure them yourself.
Configuring Google docs
Google docs are configured in a google.json
file in the root of your project.
To connect Google docs to your project, create one with the following structure.
{ "docs": {}, "sheets": {}}
Now add the docs you’d like to connect as key, value pairs to your config file.
The key should be the relative path to a local JSON file where you’d like to sync your Google doc. The value, the ID of your Google doc, which you can get from its URL.
{ "docs": { "locales/en/content.json": "XXXX_Google_doc_ID_XXXX" }, "sheets": {}}
Configuring Google sheets
You can also connect your project to Google sheets using the same key/value structure.
{ "docs": { "locales/en/content.json": "XXXX_Google_doc_ID_XXXX" }, "sheets": { "locales/en/data.json": "XXXX_Google_sheet_ID_XXXX" }}
Google docs commands
get-google
Fetch the latest text from your Google docs and sheets and save it to the JSON files configured in your google.json
.
pnpm get-google