Planning to ship content in OPS
Before creating a project in OPS or moving an existing project to OPS, content owners gather information and make decisions that will impact various points of the conversion and migration effort. This phase is meant to ensure the right questions are asked, the correct people are looped in and the effort is tracked.
To better manage the repos and the sitemaps per repo we are asking teams to not create repos for just couple pages. To utilize our repo and sitemap file capacity please create repo at the minimum of 25 pages unless there is a strong business justification.
- Determine the scope of the content that will move to OPS and the stakeholders.
- If your content is localized, make sure you involve your localization team from the beginning.
- Follow the steps with your stakeholders listed in the tick-tock plan.
Consider your docset organization carefully. If you wind up having to re-organize content at a later date, it's important to realize that it is not possible to redirect document id across docsets. The practical result of this is that content that moves from one docset to another will lose all connection to previous BI data and customer feedback as part of the move.