Knowledge

Component content management system

Source 📝

25: 188:
Each component has its own lifecycle (owner, version, approval, use) and can be tracked individually or as part of an assembly. Component content management is typically used for multi-channel customer-facing content (marketing, usage, learning, support). The solution can be a separate system or be
184:
Each component is only stored one time in the content management system, providing a single, trusted source of content (referential). These components are then reused (rather than copied and pasted) within a document or across multiple documents. This ensures that content is consistent across the
135:
The CCMS must be able to track "not only versions of topics and graphics but relationships among topics, graphics, maps, publications, and deliverables." More often than not, the CCMS also contains the publishing engine to create the final outputs for print, web and e-readers.
282: 126:
that manages content at a granular level (component) rather than at the document level. Each component represents a single topic, concept or asset (for example an image, table, product description, a procedure).
139:
Components can be as large as a chapter or as small as a definition or even a word. Components in multiple content assemblies (content types) can be viewed as components or as traditional documents.
204:
Unlike a "simple" management system, the CCMS tracks the components. It tracks indirect and direct linking so that the author can safely reuse content and check the applicability of changes.
142:
Various forms of XML are used in CCMSs to provide document and file structure. The most popular forms are SGML, XML and XHTML. Document format standards for these languages include:
286: 185:
entire documentation set. The use of components can also reduce the amount of time it takes to update and maintain content as changes only need to be made once, in one component.
93: 532: 65: 72: 416: 79: 492: 319: 354: 181:, that is shifting from writing book-shaped, linear documentation to writing modular, structured and reusable content component. 35: 61: 462: 146: 359: 517: 557: 537: 502: 467: 437: 603: 572: 472: 567: 86: 42: 542: 507: 379: 50: 409: 198: 194: 46: 613: 300: 527: 452: 442: 618: 371: 123: 317:
Component content management: Overlooked by analysts; required by technical publications departments
487: 447: 402: 344: 178: 426: 8: 385: 316: 190: 375: 349: 323: 278: 170: 597: 512: 372:
DITA Best Practices: A Roadmap to Writing, Editing, and Architecting in DITA
608: 562: 497: 577: 522: 312: 236:
Version and control over the documents and the contents - reused or not.
173:(the ISO/IEC 29500:2008 standard XML format used by e.g. Microsoft Word) 167:
Shareable Content Object Reference Model (training and learning content)
283:"Why CCM is not a CMS: Or Why You Shouldn't Confuse a Whale and a Fish" 394: 24: 285:. The Center for Information-Development Management. Archived from 457: 152: 301:
Crash Course for Content Management: What is content management?
158: 360:
The Language of Technical Communication, Ray Gallon, XML Press
582: 552: 477: 164: 482: 547: 339: 232:
Benefits of using a component content management system:
374:. Laura Bellamy, Michelle Carey, Jenifer Schlotfeldt. 242:
Improved collaboration and automation with workflows.
212:Benefits of managing contents at components level: 595: 16:System that manages content at a granular level 410: 177:Challenges for the technical writers include 51:introducing citations to additional sources 277: 417: 403: 239:Check impacts on reused content changes. 41:Relevant discussion may be found on the 596: 424: 248:Ease of links and content maintenance. 147:Darwin Information Typing Architecture 398: 62:"Component content management system" 18: 116:component content management system 13: 14: 630: 365: 251:Further reduce translation costs. 216:Greater consistency and accuracy. 34:relies largely or entirely on a 23: 306: 293: 271: 245:Manage documentation releases. 149:(DITA) (generic and adaptable) 1: 382:IBM Press (30 September 2011) 195:enterprise content management 7: 350:Oasis Committee for DocBook 207: 189:a functionality of another 130: 10: 635: 333: 225:Reduced translation costs. 219:Reduced maintenance costs. 193:system type (for example, 433: 326:". The Rockley Group Inc. 260:Integration with editors. 124:content management system 345:OASIS Official DITA page 340:S1000D Official homepage 264: 604:Technical communication 222:Reduced delivery costs. 161:(defense, aerospace...) 386:DITA For Practitioners 199:web content management 254:Higher collaboration. 179:topic-based authoring 315:and Steve Manning. " 257:Improved modularity. 47:improve this article 614:XML-based standards 322:2008-07-24 at the 303:". Vasont Systems. 191:content management 591: 590: 289:on June 24, 2016. 112: 111: 97: 626: 619:Markup languages 419: 412: 405: 396: 395: 327: 310: 304: 297: 291: 290: 275: 107: 104: 98: 96: 55: 27: 19: 634: 633: 629: 628: 627: 625: 624: 623: 594: 593: 592: 587: 429: 423: 392: 388:. Eliot Kimber. 368: 336: 331: 330: 324:Wayback Machine 311: 307: 298: 294: 279:Howard Schwartz 276: 272: 267: 210: 171:Office Open XML 133: 108: 102: 99: 56: 54: 40: 28: 17: 12: 11: 5: 632: 622: 621: 616: 611: 606: 589: 588: 586: 585: 580: 575: 570: 565: 560: 555: 550: 545: 540: 535: 530: 525: 520: 515: 510: 505: 500: 495: 490: 485: 480: 475: 470: 465: 460: 455: 450: 445: 440: 434: 431: 430: 422: 421: 414: 407: 399: 390: 389: 383: 367: 366:External links 364: 363: 362: 357: 352: 347: 342: 335: 332: 329: 328: 305: 292: 269: 268: 266: 263: 262: 261: 258: 255: 252: 249: 246: 243: 240: 237: 230: 229: 226: 223: 220: 217: 209: 206: 175: 174: 168: 162: 156: 150: 132: 129: 110: 109: 45:. Please help 31: 29: 22: 15: 9: 6: 4: 3: 2: 631: 620: 617: 615: 612: 610: 607: 605: 602: 601: 599: 584: 581: 579: 576: 574: 571: 569: 566: 564: 561: 559: 556: 554: 551: 549: 546: 544: 541: 539: 536: 534: 531: 529: 526: 524: 521: 519: 516: 514: 513:SOAP-over-UDP 511: 509: 506: 504: 501: 499: 496: 494: 491: 489: 486: 484: 481: 479: 476: 474: 471: 469: 466: 464: 461: 459: 456: 454: 451: 449: 446: 444: 441: 439: 436: 435: 432: 428: 425:Standards of 420: 415: 413: 408: 406: 401: 400: 397: 393: 387: 384: 381: 377: 373: 370: 369: 361: 358: 356: 353: 351: 348: 346: 343: 341: 338: 337: 325: 321: 318: 314: 309: 302: 296: 288: 284: 280: 274: 270: 259: 256: 253: 250: 247: 244: 241: 238: 235: 234: 233: 228:Traceability. 227: 224: 221: 218: 215: 214: 213: 205: 202: 200: 196: 192: 186: 182: 180: 172: 169: 166: 163: 160: 157: 154: 151: 148: 145: 144: 143: 140: 137: 128: 125: 121: 117: 106: 95: 92: 88: 85: 81: 78: 74: 71: 67: 64: –  63: 59: 58:Find sources: 52: 48: 44: 38: 37: 36:single source 32:This article 30: 26: 21: 20: 563:WS-Discovery 498:OpenDocument 391: 308: 295: 287:the original 273: 231: 211: 203: 187: 183: 176: 141: 138: 134: 119: 115: 113: 100: 90: 83: 76: 69: 57: 33: 313:Ann Rockley 598:Categories 380:0132480522 103:March 2009 73:newspapers 155:(generic) 43:talk page 320:Archived 208:Benefits 131:Overview 558:WS-BPEL 458:DocBook 334:Sources 153:DocBook 122:) is a 87:scholar 378:  159:S1000D 89:  82:  75:  68:  60:  583:XACML 553:XLIFF 523:TOSCA 478:ebXML 427:OASIS 355:SCORM 265:Notes 165:SCORM 94:JSTOR 80:books 573:WSRP 568:WSRF 538:WSDM 533:UDDI 518:SPML 503:SAML 493:KMIP 483:EDXL 473:DPWS 468:DSML 463:DITA 438:AMQP 376:ISBN 120:CCMS 66:news 609:XML 578:WSS 548:XDI 543:XRI 528:UBL 508:SDD 488:EML 453:DSS 448:CAP 443:CAM 201:). 197:or 49:by 600:: 281:. 114:A 418:e 411:t 404:v 299:" 118:( 105:) 101:( 91:· 84:· 77:· 70:· 53:. 39:.

Index


single source
talk page
improve this article
introducing citations to additional sources
"Component content management system"
news
newspapers
books
scholar
JSTOR
content management system
Darwin Information Typing Architecture
DocBook
S1000D
SCORM
Office Open XML
topic-based authoring
content management
enterprise content management
web content management
Howard Schwartz
"Why CCM is not a CMS: Or Why You Shouldn't Confuse a Whale and a Fish"
the original
Crash Course for Content Management: What is content management?
Ann Rockley
Component content management: Overlooked by analysts; required by technical publications departments
Archived
Wayback Machine
S1000D Official homepage

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.