How Arc XP handles uncirculated stories
You can create a story in Arc XP directly in the Composer application or programmatically through Draft API. When you create a story in Composer, the system requires you to circulate the story to one or more websites before publishing. However, when creating a story through Draft API, the circulation requirement is asynchronous. This means that an Arc XP story could exist in an uncirculated state.
In Composer, any uncirculated stories are findable under the default website. Uncirculated stories are not actually associated with the default website. They just appear as if they are.
Note
You set a default website in Site Service. For a single-site configuration, your single site is automatically the default website. For a multi-site configuration, you designate a site as the default in Site Service.
Creating a default website for uncirculated stories
Because seeing uncirculated stories appear under the default website may lead to confusion, a multi-site organization can create a website that is not meant for real publishing use, and use this internal site as the default. This way, while a story exists in an uncirculated state, it doesn't appear in search results alongside published content assigned to in-use websites.
Also, by assigning uncirculated stories to this internal website, you can keep track of stories that might never have been properly circulated and are in danger of being forgotten.
Note
If you create a default website to catch your uncirculated stories, we recommend naming the website something that reflects its purpose, like Uncirculated.