DCT cheat sheet

If like us, you are working (or have worked) on a large sized CMS implementation, you will understand the value behind this. If you haven’t, please know that this type of visual help or guide, comes handy when you are dealing with an implementation that requires development of multiple Data Capture Templates, with different requirements for each branch or work areas of such project. Especially when it comes to an implementation of HP Autonomy TeamSite. Instead of building the DCT wire frame in an Excel sheet, you can very well take our cheat sheets as a guide and start your work from there, coming back to the essentials in case you are lost.

Of course, there are different levels of challenge and each CMS platform will have its own approach to any of the areas represented here, however, with these DCT cheat sheets you can find your dct cheat sheetnorth. We’ll be posting more as soon as they come along, so if they are greyed out below, they are on our road map.

Each DCT cheat sheet is a very simple and straight forward XML element or block and the tag naming convention is self explanatory, however, we do have a tag naming convention document, with all information needed. These elements may be extended with greater details and sub elements as the requirements of the project dictate. We align our code to W3C HTML standards. Only required and most used attributes are captured.

Please note that within these examples we capture the minimum requirements for each field. For example, a text area that captures a Header, will just be called <header> and no other attributes nor sub elements of this field will be captured, such as style, label, description, etc. As well, each root node <DCT> contains an attribute and corresponding value, which will define the template data type.

For example:

<DCT type='post-article'>
//Some nested elements here

All cheat sheets are stored in our Powoweb Git repository.

  • Article
    • This is the typical article (post) DCT. It contains a Header, which usually is a textbox with a limited amount of allowed characters and a content area. Both fields can be extended with a TinyMCE instance or your favorite rich text editor.
  • Metadata
    • Metadata is an extensive subject that cannot (should not) be covered by one template. The template structured here includes basic fields that most CMS installs will require. It is usual that author facing metadata templates involve many types or a mix of metadata and not only business specific.
  • Link
    • A Link DCT, is an XML version of an <a> tag. In a CMS, this can be escalated to a list of links with ease.
  • Tab content
  • Toggle content
  • Footer

Upon request, we can extended a DCT cheat sheet.

If there is something you don’t understand, think that can be communicated better, have your own cheat sheet you’d like to share with the world or just want to send us some love, please feel free to leave a comment below.


Leave a Reply

Your email address will not be published. Required fields are marked *