WordPress and Arc XP

A CMS connection lets an editor file a finished web article from Nuvelics into your content management system as an unpublished draft, with its images. Nobody publishes from Nuvelics: a person reviews the draft in the CMS and publishes it there. The steps to create a connection are in the CMS settings tab; the editor's steps to file an article are in Push a story to your newsroom.

The CMS tab also lists WordPress VIP, Brightspot, Contentful, Sanity, Livingdocs, Ghost, Newspack and Adobe Experience Manager / Drupal as Coming soon.

WordPressCopy Anchor Link

What to ask your WordPress administrator forCopy Anchor Link

• Your site's address, as WordPress shows it under Settings > General. It must be https.
• A user account to file as, and its application password, created in WordPress under Users

  Profile > Application Passwords. Nuvelics stores the password encrypted and uses it as the account's login for every push.

• Confirmation that your web server passes the Authorization header through to WordPress. Some self-hosted setups strip it, and WordPress then refuses a correct password. WordPress reports this case under Tools > Site Health.

What is filed, and as whatCopy Anchor Link

Filing creates one draft post with:

Nothing else is set: no categories, tags, author or publication date. The post is never published.

The connection has one option: Credit the featured image in the article body. Turn it on if your theme does not print a featured image's caption, so the credit is filed as the body's first paragraph. Leave it off if your theme does print it, or the credit appears twice.

What has to be true firstCopy Anchor Link

The push is refused, with the reason, when:

• The article is not Ready.
• The article's claim check has open findings, has not been checked, or is out of date. A claim check that failed to run does not block filing, and the filing is recorded as unchecked.
• A field quotes words that belong only to a key quote that was dismissed on the story.
• An image is no longer one of the story's photos, was dismissed, or is past its use-by date.
• This connection already has this version of the article. Each connection takes a given version once; edit or regenerate the article to file it again.

What to expectCopy Anchor Link

• The editor waits while the push runs, which is bounded at 60 seconds. If it fails, nothing is recorded, the images it uploaded are removed, and the connection stays selectable to try again.
• Photos are uploaded once per connection and reused when a later article uses the same photo.
• Photos come from the story's own photos: ones the journalist attached, wire photos, and photos from your archive. Nuvelics reads the photo from where it is kept when it files the article.
• A refused credential is reported in the editor's message. A wrong password and a server that drops the Authorization header look the same to WordPress, so the message names both.
• Each push is recorded under the output's Publish Status and in the audit log.

Arc XPCopy Anchor Link

You can save an Arc XP connection today: a name, your Arc organization ID, the environment (Production, Sandbox, Staging or Development), the Website ID to file into, and an access token. The connection is kept, and the CMS tab marks it Push support coming soon. Nuvelics does not yet file articles to Arc XP: a push to one is refused with a message naming the vendor.

Ask your Arc XP administrator for the organization ID, the Website ID from Site Service, and an access token with at least restricted-access scope. Adding the connection now lets you prepare it ahead of time.

Manage it another wayCopy Anchor Link

• CLI: nuvelics cms-config, and nuvelics story outputs push files an article (nuvelics story).
• API: CMS configs and Outputs.
• AI assistants: the CMS tools, which can also preview what would be filed.