If you have an existing article you'd like to convert to a synced article, you can use one of two approaches:
- Copy the permalink for the standalone article, delete the standalone article, and create a new synced article with the same permalink as that deleted standalone article.
- Power users only: Use the API to forcibly convert the existing standalone article to a synced article.
If you're familiar with using the API, convert an existing article to a synced article using these steps:
- Get the ID of the article you'd like to switch to being the synced child and the ID of the article you'd like to make its parent.
- Follow the API endpoint reference guidelines on the
articlesendpoint to Update a single article. - Update the child article and set the
content_articlefield to the parent article's ID.
When you use this approach, if the child article had any existing content:
- You will no longer see Revision History in the UI for changes to the child article's content.
- Even in the API, the child article will not keep revisions moving forward.
- If you have historical revision history for the child article, it won't display in the UI. You can recover or view it using the
articlerevisionAPI endpoint. - If you unlink the articles through the UI or setting the
content_articlefield to be empty, this returns the article to standalone status and will display the pre-sync revision history for the child. The child article won't ever display revision history when it was synced to the parent since revisions are stored on the parent only.