Your content<\/h3>\n\n- You write\u00a0narrative content.<\/li>\n
- Your content has a \u201cshelf life\u201d of less than two years.<\/li>\n
- The way the content looks to the user is the most important issue.<\/li>\n
- You need to customise outputs for individual documents (such as PDFs).<\/li>\n
- You want the presentation layer embedded (“baked”) with the content layer.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have fewer than four writers.<\/li>\n
- You don\u2019t want to work within\u00a0strict rules regarding how topics are written (where\u00a0content is marked up\u00a0semantically).<\/li>\n
- You need to use the tools used by developers or the marketing department.<\/li>\n<\/ul>\n
Your\u00a0management<\/h3>\n\n- You have limited budgets for tools, training and migration.<\/li>\n
- You want\u00a0to improve the workflow for\u00a0reviewing content.<\/li>\n
- You don\u2019t have the time to deal with the issues around changing working methods.<\/li>\n
- The cost of migrating existing content will be expensive.<\/li>\n
- You want a simple information\u00a0architecture.<\/li>\n<\/ul>\n
(*)<\/h3>\n
Although you might not need DITA, you still might need a better solution than your existing tools and processes.<\/p>\n
You might need DITA* if:<\/h2>\nYour content<\/h3>\n\n- You need to write to (and enforce) a standard.<\/li>\n
- Your content has a “shelf life” or more than two years.<\/li>\n
- You need to localise content into many languages.<\/li>\n
- You want to write semantically.<\/li>\n
- You create many variations of the same document.<\/li>\n
- You want intelligent content that can adapt to different users and contexts.<\/li>\n
- You want\u00a0automated publishing.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have more than four writers.<\/li>\n
- You need to\u00a0re-use content\u00a0in different projects and different contexts, and make those topics accessible to other writing teams who might want to re-use them.<\/li>\n<\/ul>\n
Your management<\/h3>\n\n- You need a more efficient authoring, reviewing and publishing process.<\/li>\n
- You are spending too much time on formatting content.<\/li>\n
- You need to establish a controlled vocabulary and taxonomy.<\/li>\n
- You want content\u00a0validated for consistency.<\/li>\n<\/ul>\n
(*)<\/h3>\n
You might need either DITA or another topic-based structured authoring environment. The solution is likely to be XML-based, using a Component Content Management System. For more information, contact Cherryleaf<\/a>.<\/p>\nYou probably do need DITA if:<\/h2>\n
You face the problems listed in “You might need DITA”, plus:<\/p>\n
Your content<\/h3>\n\n- Your content will need to last more than\u00a030 years.<\/li>\n
- You need to share content with other organisations, who will rebrand it and\/or repurpose it.<\/li>\n
- You want content to be stored in an open\u00a0data standard, independent of any tool.<\/li>\n
- You need transclusion (where an element can replace itself with the content of a like element elsewhere) across a range of\u00a0media.<\/li>\n
- You want to have a way of generalising back to a common standard.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have a large team of writers.<\/li>\n<\/ul>\n
Your management<\/h3>\n\n- You don\u2019t want to be tied into a\u00a0specific\u00a0authoring tool, content management system or publishing\/rendering engine.<\/li>\n<\/ul>\n
Cherryleaf can help you solve the issues around how you create, manage and publish content<\/h2>\n
For more information, see\u00a0Cherryleaf’s Content design and content strategy services<\/a>.<\/p>\n![\"contact](\"https:\/\/www.cherryleaf.com\/images\/head.png\" "\\"Call")
\nWant to discuss your situation, and explore how Cherryleaf can help you? You can tell us about your project, issues and goals. We\u2019re here to help.<\/p>\n
<\/p>\n
Contact us<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Your writers<\/h3>\n\n- You have fewer than four writers.<\/li>\n
- You don\u2019t want to work within\u00a0strict rules regarding how topics are written (where\u00a0content is marked up\u00a0semantically).<\/li>\n
- You need to use the tools used by developers or the marketing department.<\/li>\n<\/ul>\n
Your\u00a0management<\/h3>\n\n- You have limited budgets for tools, training and migration.<\/li>\n
- You want\u00a0to improve the workflow for\u00a0reviewing content.<\/li>\n
- You don\u2019t have the time to deal with the issues around changing working methods.<\/li>\n
- The cost of migrating existing content will be expensive.<\/li>\n
- You want a simple information\u00a0architecture.<\/li>\n<\/ul>\n
(*)<\/h3>\n
Although you might not need DITA, you still might need a better solution than your existing tools and processes.<\/p>\n
You might need DITA* if:<\/h2>\nYour content<\/h3>\n\n- You need to write to (and enforce) a standard.<\/li>\n
- Your content has a “shelf life” or more than two years.<\/li>\n
- You need to localise content into many languages.<\/li>\n
- You want to write semantically.<\/li>\n
- You create many variations of the same document.<\/li>\n
- You want intelligent content that can adapt to different users and contexts.<\/li>\n
- You want\u00a0automated publishing.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have more than four writers.<\/li>\n
- You need to\u00a0re-use content\u00a0in different projects and different contexts, and make those topics accessible to other writing teams who might want to re-use them.<\/li>\n<\/ul>\n
Your management<\/h3>\n\n- You need a more efficient authoring, reviewing and publishing process.<\/li>\n
- You are spending too much time on formatting content.<\/li>\n
- You need to establish a controlled vocabulary and taxonomy.<\/li>\n
- You want content\u00a0validated for consistency.<\/li>\n<\/ul>\n
(*)<\/h3>\n
You might need either DITA or another topic-based structured authoring environment. The solution is likely to be XML-based, using a Component Content Management System. For more information, contact Cherryleaf<\/a>.<\/p>\nYou probably do need DITA if:<\/h2>\n
You face the problems listed in “You might need DITA”, plus:<\/p>\n
Your content<\/h3>\n\n- Your content will need to last more than\u00a030 years.<\/li>\n
- You need to share content with other organisations, who will rebrand it and\/or repurpose it.<\/li>\n
- You want content to be stored in an open\u00a0data standard, independent of any tool.<\/li>\n
- You need transclusion (where an element can replace itself with the content of a like element elsewhere) across a range of\u00a0media.<\/li>\n
- You want to have a way of generalising back to a common standard.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have a large team of writers.<\/li>\n<\/ul>\n
Your management<\/h3>\n\n- You don\u2019t want to be tied into a\u00a0specific\u00a0authoring tool, content management system or publishing\/rendering engine.<\/li>\n<\/ul>\n
Cherryleaf can help you solve the issues around how you create, manage and publish content<\/h2>\n
For more information, see\u00a0Cherryleaf’s Content design and content strategy services<\/a>.<\/p>\n\nWant to discuss your situation, and explore how Cherryleaf can help you? You can tell us about your project, issues and goals. We\u2019re here to help.<\/p>\n
<\/p>\n
Contact us<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Your\u00a0management<\/h3>\n\n- You have limited budgets for tools, training and migration.<\/li>\n
- You want\u00a0to improve the workflow for\u00a0reviewing content.<\/li>\n
- You don\u2019t have the time to deal with the issues around changing working methods.<\/li>\n
- The cost of migrating existing content will be expensive.<\/li>\n
- You want a simple information\u00a0architecture.<\/li>\n<\/ul>\n
(*)<\/h3>\n
Although you might not need DITA, you still might need a better solution than your existing tools and processes.<\/p>\n
You might need DITA* if:<\/h2>\nYour content<\/h3>\n\n- You need to write to (and enforce) a standard.<\/li>\n
- Your content has a “shelf life” or more than two years.<\/li>\n
- You need to localise content into many languages.<\/li>\n
- You want to write semantically.<\/li>\n
- You create many variations of the same document.<\/li>\n
- You want intelligent content that can adapt to different users and contexts.<\/li>\n
- You want\u00a0automated publishing.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have more than four writers.<\/li>\n
- You need to\u00a0re-use content\u00a0in different projects and different contexts, and make those topics accessible to other writing teams who might want to re-use them.<\/li>\n<\/ul>\n
Your management<\/h3>\n\n- You need a more efficient authoring, reviewing and publishing process.<\/li>\n
- You are spending too much time on formatting content.<\/li>\n
- You need to establish a controlled vocabulary and taxonomy.<\/li>\n
- You want content\u00a0validated for consistency.<\/li>\n<\/ul>\n
(*)<\/h3>\n
You might need either DITA or another topic-based structured authoring environment. The solution is likely to be XML-based, using a Component Content Management System. For more information, contact Cherryleaf<\/a>.<\/p>\nYou probably do need DITA if:<\/h2>\n
You face the problems listed in “You might need DITA”, plus:<\/p>\n
Your content<\/h3>\n\n- Your content will need to last more than\u00a030 years.<\/li>\n
- You need to share content with other organisations, who will rebrand it and\/or repurpose it.<\/li>\n
- You want content to be stored in an open\u00a0data standard, independent of any tool.<\/li>\n
- You need transclusion (where an element can replace itself with the content of a like element elsewhere) across a range of\u00a0media.<\/li>\n
- You want to have a way of generalising back to a common standard.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have a large team of writers.<\/li>\n<\/ul>\n
Your management<\/h3>\n\n- You don\u2019t want to be tied into a\u00a0specific\u00a0authoring tool, content management system or publishing\/rendering engine.<\/li>\n<\/ul>\n
Cherryleaf can help you solve the issues around how you create, manage and publish content<\/h2>\n
For more information, see\u00a0Cherryleaf’s Content design and content strategy services<\/a>.<\/p>\n\nWant to discuss your situation, and explore how Cherryleaf can help you? You can tell us about your project, issues and goals. We\u2019re here to help.<\/p>\n
<\/p>\n
Contact us<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
(*)<\/h3>\n
Although you might not need DITA, you still might need a better solution than your existing tools and processes.<\/p>\n
You might need DITA* if:<\/h2>\nYour content<\/h3>\n\n- You need to write to (and enforce) a standard.<\/li>\n
- Your content has a “shelf life” or more than two years.<\/li>\n
- You need to localise content into many languages.<\/li>\n
- You want to write semantically.<\/li>\n
- You create many variations of the same document.<\/li>\n
- You want intelligent content that can adapt to different users and contexts.<\/li>\n
- You want\u00a0automated publishing.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have more than four writers.<\/li>\n
- You need to\u00a0re-use content\u00a0in different projects and different contexts, and make those topics accessible to other writing teams who might want to re-use them.<\/li>\n<\/ul>\n
Your management<\/h3>\n\n- You need a more efficient authoring, reviewing and publishing process.<\/li>\n
- You are spending too much time on formatting content.<\/li>\n
- You need to establish a controlled vocabulary and taxonomy.<\/li>\n
- You want content\u00a0validated for consistency.<\/li>\n<\/ul>\n
(*)<\/h3>\n
You might need either DITA or another topic-based structured authoring environment. The solution is likely to be XML-based, using a Component Content Management System. For more information, contact Cherryleaf<\/a>.<\/p>\nYou probably do need DITA if:<\/h2>\n
You face the problems listed in “You might need DITA”, plus:<\/p>\n
Your content<\/h3>\n\n- Your content will need to last more than\u00a030 years.<\/li>\n
- You need to share content with other organisations, who will rebrand it and\/or repurpose it.<\/li>\n
- You want content to be stored in an open\u00a0data standard, independent of any tool.<\/li>\n
- You need transclusion (where an element can replace itself with the content of a like element elsewhere) across a range of\u00a0media.<\/li>\n
- You want to have a way of generalising back to a common standard.<\/li>\n<\/ul>\n
Your writers<\/h3>\n\n- You have a large team of writers.<\/li>\n<\/ul>\n
Your management<\/h3>\n\n- You don\u2019t want to be tied into a\u00a0specific\u00a0authoring tool, content management system or publishing\/rendering engine.<\/li>\n<\/ul>\n
Cherryleaf can help you solve the issues around how you create, manage and publish content<\/h2>\n
For more information, see\u00a0Cherryleaf’s Content design and content strategy services<\/a>.<\/p>\n\nWant to discuss your situation, and explore how Cherryleaf can help you? You can tell us about your project, issues and goals. We\u2019re here to help.<\/p>\n
<\/p>\n
Contact us<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
- \n
- You need to write to (and enforce) a standard.<\/li>\n
- Your content has a “shelf life” or more than two years.<\/li>\n
- You need to localise content into many languages.<\/li>\n
- You want to write semantically.<\/li>\n
- You create many variations of the same document.<\/li>\n
- You want intelligent content that can adapt to different users and contexts.<\/li>\n
- You want\u00a0automated publishing.<\/li>\n<\/ul>\n
Your writers<\/h3>\n
- \n
- You have more than four writers.<\/li>\n
- You need to\u00a0re-use content\u00a0in different projects and different contexts, and make those topics accessible to other writing teams who might want to re-use them.<\/li>\n<\/ul>\n
Your management<\/h3>\n
- \n
- You need a more efficient authoring, reviewing and publishing process.<\/li>\n
- You are spending too much time on formatting content.<\/li>\n
- You need to establish a controlled vocabulary and taxonomy.<\/li>\n
- You want content\u00a0validated for consistency.<\/li>\n<\/ul>\n
(*)<\/h3>\n
You might need either DITA or another topic-based structured authoring environment. The solution is likely to be XML-based, using a Component Content Management System. For more information, contact Cherryleaf<\/a>.<\/p>\n
You probably do need DITA if:<\/h2>\n
You face the problems listed in “You might need DITA”, plus:<\/p>\n
Your content<\/h3>\n
- \n
- Your content will need to last more than\u00a030 years.<\/li>\n
- You need to share content with other organisations, who will rebrand it and\/or repurpose it.<\/li>\n
- You want content to be stored in an open\u00a0data standard, independent of any tool.<\/li>\n
- You need transclusion (where an element can replace itself with the content of a like element elsewhere) across a range of\u00a0media.<\/li>\n
- You want to have a way of generalising back to a common standard.<\/li>\n<\/ul>\n
Your writers<\/h3>\n
- \n
- You have a large team of writers.<\/li>\n<\/ul>\n
Your management<\/h3>\n
- \n
- You don\u2019t want to be tied into a\u00a0specific\u00a0authoring tool, content management system or publishing\/rendering engine.<\/li>\n<\/ul>\n
Cherryleaf can help you solve the issues around how you create, manage and publish content<\/h2>\n
For more information, see\u00a0Cherryleaf’s Content design and content strategy services<\/a>.<\/p>\n
\nWant to discuss your situation, and explore how Cherryleaf can help you? You can tell us about your project, issues and goals. We\u2019re here to help.<\/p>\n
<\/p>\n
Contact us<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
- You don\u2019t want to be tied into a\u00a0specific\u00a0authoring tool, content management system or publishing\/rendering engine.<\/li>\n<\/ul>\n
- You have a large team of writers.<\/li>\n<\/ul>\n