Hi Frank, Mark Novembrino gave a good overview of factors in converting the content itself.

Assuming that’s what you had in mind — a wholesale switch of all the existing content — then here’s one way to think about it.

In switching to DITA, you’re not only changing the syntax of the content, you’re also enabling various features in Docs which are designed to work with DITA. Such as library features around conrefs, and the ability to use Draft Space — lots of good stuff.

With that in mind, you could almost look at it as a migration to a newer version (and in practice it is likely this would go with a CMS upgrade anyway). So you’re not switching in place, but rather trying out the remapped content in an all-new Docs version in a dev environment. And also probably taking the opportunity to simplify configurations, maybe even prune some legacy content.

In fact there are customers who were using DITA all along who still chose to do a bit of a fresh start in a new Docs instance after say ten good years and building up quite a lot of legacy outputs, LOV values, redundant statuses, and so on!

So maybe it’s a chance for this kind of spring-clean too?

Hi Frank, Mark Novembrino gave a good overview of factors in converting the content itself.

Assuming that’s what you had in mind — a wholesale switch of all the existing content — then here’s one way to think about it.

In switching to DITA, you’re not only changing the syntax of the content, you’re also enabling various features in Docs which are designed to work with DITA. Such as library features around conrefs, and the ability to use Draft Space — lots of good stuff.

With that in mind, you could almost look at it as a migration to a newer version (and in practice it is likely this would go with a CMS upgrade anyway). So you’re not switching in place, but rather trying out the remapped content in an all-new Docs version in a dev environment. And also probably taking the opportunity to simplify configurations, maybe even prune some legacy content.

In fact there are customers who were using DITA all along who still chose to do a bit of a fresh start in a new Docs instance after say ten good years and building up quite a lot of legacy outputs, LOV values, redundant statuses, and so on!

So maybe it’s a chance for this kind of spring-clean too?