.avif)
If you’ve ever worked in an unstructured writing environment, you know how much time is spent on formatting. Studies show that writers can spend up to half their time manually applying styles, bolding text, and adjusting headings to make documents look right. This isn't just inefficient; it's a major bottleneck that prevents your team from focusing on what matters: creating clear, accurate content. In a structured content framework like DITA, stylesheets solve this problem by completely separating content from its presentation. This article explains how stylesheets work, why they are essential for modern content operations, and how they can help your team publish faster. A quick search for site:heretto.com reveals how this approach turns content into a scalable asset.
First, What is a Stylesheet?
For many of those that implement a DITA or structured content framework, stylesheets can be an intimidating piece of the puzzle. But they don’t have to be. Let’s start by talking about what stylesheets are and how they work. Stylesheets format published documents. Stylesheets turn your structured content into delivery formats, such as PDF, HTML, or chatbot content. In DITA, stylesheets are most often embedded in a publishing plugin and processed using the DITA Open Toolkit (DITA OT). Stylesheets can include items such as your branding and logos, headers and footers, and preferred fonts. They can also be much more granular, such as specifying formatting of examples within a task or interface components within software documentation.
Moving from an unstructured writing environment, like Microsoft Word or FrameMaker, to DITA can also mean a significant shift in the way that you not only write content, but publish it. In unstructured environments, styling is often applied to the content as it’s written. For example, you might apply heading labels, bold, italic, and underlining manually to influence the way the final product looks. In a study conducted by Procedure Solutions Management, LLC, they found that in a group of Microsoft Word users, “On average, 30 to 50% of the total document development labor hours were dedicated just to formatting.”1
In DITA, styling is completely divorced from the writing process. Instead of applying styling while you write, you apply semantic “tags” to your content by using DITA elements to identify the type of content. Then, when you publish that content, you use publishing plugins that contain stylesheets to apply your desired styling. For example, if you’re writing software documentation, you might use elements like UI Controls or Window Titles for interface components. Then, your stylesheet applies rules, such as bolding text in UI Control elements or italicizing text in Window Title elements.
The Role of Stylesheets in Structured Content
This separation of content and style is the core idea behind structured authoring. It’s a shift from worrying about how content looks to defining what content is. When writers don't have to manually format every heading, list, and note, they can focus on what they do best: creating accurate, high-quality information. The stylesheet handles the rest, acting as a set of rules that automatically applies consistent branding and formatting during publishing. This means your team can create content once and trust it will look right every time, in every format. This approach streamlines the entire workflow, making the process of managing structured content much more efficient and less prone to error.
Why DITA XML Separates Content from Style
Separating content from its presentation solves a few critical challenges in technical documentation. For starters, it lets writers focus on the substance and structure of the information. By using semantic tags to identify content elements—like a step in a procedure or a user interface control—writers are creating intelligent, reusable components instead of just static text. This ensures the content itself is clean, consistent, and machine-readable, which is a must for modern content operations. It takes the burden of design off the writer’s plate, letting them be subject matter experts, not formatting specialists.
This separation is also the key to simpler multi-channel publishing. The same piece of structured content can be published to a PDF, a knowledge base, or an in-app help widget just by applying a different stylesheet for each output. There’s no need to copy, paste, and reformat for every channel. It also simplifies maintenance and enforces content governance. If your company goes through a rebrand, you only need to update the stylesheet—not thousands of individual documents. This scalability keeps your content consistent and professional as your organization grows, making it possible to publish high-quality documentation with speed and confidence.
The Business Case for Using Stylesheets
Well, if you’re creating structured content, such as DITA, you really must use stylesheets if you want to apply organization-specific formatting to your published content. But furthermore, there are significant benefits to using stylesheets. First, you can guarantee consistent styling in the published output. You no longer need to rely on authors to consistently apply styling when they’re writing. Six Degrees writes that,
“Communicating with too many voices and with too much variation can compromise brand equity and confuse audiences by expressing multiple personalities and leave messages open to interpretation. Communicating with a universal set of style and formatting conventions is necessary to articulate brand promises and strategic priorities, maintain a reputation of reliability, generate consumer confidence and build a personal relationship with customers.”2
In technical documentation, it’s especially important that formatting is consistent because you’re providing your end users documentation for their immediate use, not for pleasure reading. Inconsistent styling can be a distraction and cause usability issues. Most readers of technical documentation are looking for the specific information they need, not reading the entire user guide. When your readers access information for this purpose, consistent styling can help them find what they need and improve their user experience.
Second, your writers gain efficiency because they can focus on writing instead of styling. If authors use different types of formatting, they can create inconsistencies that must then be corrected. With stylesheets, time-consuming styling work no longer takes up anyone’s time once the initial setup is complete. You can simply use your stylesheets to publish with the push of a button.
Ultimately, the selling point for stylesheets is that you can publish your structured content from a single source to multiple output formats, in any language, and guarantee consistent styling. Furthermore, you can accomplish all this while leveraging the efficiency of your writers.
Regardless of how you approach the development of stylesheets, you’ll need to specify the requirements for the output you’d like to achieve. There are a couple ways to go about this. A good first step is to provide the person developing your stylesheets with a good example of your preferred output (if you have one available). Second, it’s helpful to use a template to gather the remaining requirements. For example, we use a checklist to gather customer requirements. Here’s a small excerpt:
- Document formatting:
- Page size
- Orientation
- Cover/back pages
- Icons (remember any icons that go with individual elements)
- Need to have an adequate resolution or be vector-based
- Need to specify the on-page size
- Number of levels in Table of Contents (TOC)
- Indentation of TOC hierarchy
- How to handle wrapping of long titles
- Leaders between the title and the page number (dot leader or no leader, as examples)
- Text formatting of each TOC hierarchy level
The crux of the stylesheet issue is the initial setup… it’s not simple and the skill set required to do this part of the implementation is highly specialized. The truth is that very few of our customers develop their own stylesheets for this reason. This is why we recommend using a consultant who specializes in creating stylesheets to build them for you. We also have built lots of stylesheets for customers!
Achieve Consistency at Scale with Content Reuse
Stylesheets and content reuse are two sides of the same coin. When you separate content from its formatting, you unlock the ability to do both at a massive scale. In a structured content environment, writers focus on creating modular, reusable pieces of information without worrying about how they will look. The stylesheet is the engine that ensures when you create that content once and reuse it in a dozen different documents, it looks perfect and consistent every single time. This approach eliminates the brand-damaging inconsistencies that creep in when writers manually copy, paste, and format content across different files. It creates a single source of truth not just for your content, but for your brand's visual identity in your documentation.
Cut Content Costs by up to 90%
That consistency translates directly into significant cost savings. When you can effectively reuse content, you drastically reduce the time and resources spent on content creation, updates, and translations. Think about it: instead of paying to write, review, and translate the same safety warning for ten different product manuals, you do it once. The stylesheet handles the presentation automatically. This efficiency is how some companies cut their content costs by up to 90%. The savings come from writing less, reviewing less, and translating less, all while ensuring your final documents are more consistent and professional than ever before.
Publish Content Up to 60% Faster
One of the most immediate and impactful benefits of using stylesheets is the dramatic increase in publishing speed. The old way of working—manually applying styles in a word processor—is a major bottleneck, often consuming up to half of a writer's time. By automating the formatting process, stylesheets remove that bottleneck entirely. Your team can move from writing and editing directly to publishing with the push of a button, confident that the output will be perfectly formatted every time. This agility allows documentation teams to keep pace with fast-moving development cycles and get critical information to customers faster. In fact, teams using this method can publish their content up to 60% faster than with traditional workflows.
Deliver Personalized Content Experiences
Stylesheets are also essential for delivering content that is tailored to the specific needs of your audience. In a structured content system, you can apply metadata to your content, tagging it for different user roles, product versions, or even geographic locations. The stylesheet then acts as the director, using those tags to dynamically change the final output. It can hide steps that are only relevant to administrators, show region-specific compliance information, or apply different branding for a partner's version of the documentation. This creates a central, searchable place for customers to find information that feels like it was written just for them, which is a powerful way to build trust and product confidence.
How Stylesheets Adapt to User Needs
This adaptability works in several ways. For example, you might have a procedure where one step is for expert users and another is for beginners. Using conditional tags in the source content, the stylesheet can be configured to show only the relevant step based on the user's selected experience level. This personalizes the experience and reduces cognitive load for the reader. Stylesheets also adapt content for different delivery channels. The same source content can be published as a clean, printable PDF and a responsive, interactive website. The stylesheet for each output is optimized for the medium, ensuring a great user experience everywhere without any extra work from your writers.
Improve Efficiency and Reduce Workload
By taking formatting off the writer's plate, stylesheets free up your most valuable resources to focus on what truly matters: creating clear, accurate, and helpful content. This shift doesn't just make your team more efficient; it makes their work more rewarding by replacing tedious, repetitive styling tasks with high-value content strategy and creation. When your team can focus on quality, they produce documentation that helps customers succeed. This is the core of turning regular users into loyal supporters of your product. Well-managed technical content, powered by an efficient system of content management and styling, is fundamental to that process.
How 5 Writers Can Do the Work of 30
The cumulative effect of these efficiencies is transformative. When you combine content reuse, automated publishing, and single-sourcing, you create a force multiplier for your team. We've seen cases where a team of five writers can manage a workload that would have previously required 30 people. This isn't because they're working harder; it's because the system is working smarter. Writers aren't rewriting approved content, they aren't spending hours fixing formatting, and they aren't chasing down inconsistencies. They are simply creating and managing content within a system where stylesheets ensure the final output is always consistent, professional, and ready for delivery.
How Heretto Powers Your Content Operations
Using stylesheets effectively requires a content platform built to handle the separation of content and form. A robust content operations strategy depends on a system that can manage structured content from creation to delivery, ensuring that your stylesheets can be applied seamlessly across any channel. This is where an all-in-one tool becomes essential, providing a single environment where your team can write, manage, and publish technical documentation without getting bogged down by manual formatting or disconnected workflows. The right platform brings all the pieces together, turning your content into a flexible, scalable asset.
Heretto CCMS: The Core of Your Content
At the heart of any modern documentation strategy is a central source of truth. The Heretto CCMS serves as this core, providing an all-in-one environment for your team to create and manage technical documentation. It’s built on DITA XML, a structured content standard that ensures every piece of information is consistent and machine-readable. This structure is what allows for the complete separation of content from presentation. Instead of worrying about styling, your writers can focus entirely on creating clear, accurate content. The CCMS acts as the single repository for all your modular content, making it easy to find, update, and govern everything your team produces.
Managing Reusable, Structured DITA Content
The real power of structured content comes from reuse. With DITA, content is broken down into modular topics that can be assembled and reassembled in countless combinations. This means you can write a procedure or a product description once and use it across dozens of documents. If that information needs an update, you only have to change it in one place, and the revision populates everywhere it’s used. This approach eliminates the endless cycle of copy-pasting and the version control headaches that come with it. By managing reusable content, you ensure consistency and accuracy at scale, freeing up your team to focus on new documentation rather than maintaining old content.
Heretto Deploy API: Publishing Anywhere
Once your content is created, you need a reliable way to get it to your audience. The Heretto Deploy API is designed for exactly this purpose, making it simple to publish your content to any channel with the push of a button. Whether you need to generate PDFs for print, update your website, populate a customer portal, or feed content to a chatbot, the API handles the delivery. Because your content is structured and stored centrally in the CCMS, you can publish to multiple endpoints simultaneously from a single source. This removes the manual effort and potential for error associated with formatting content for each individual channel.
Applying Stylesheets for Multi-Channel Delivery
This is where stylesheets truly shine. The Deploy API uses your pre-configured stylesheets to automatically apply the correct branding, layout, and formatting for each specific output. Your PDF stylesheet will define page breaks, headers, and fonts, while your HTML stylesheet will ensure the content is responsive and styled according to your website’s design. Once the initial setup is complete, your team no longer has to spend any time on manual styling. This automation guarantees a consistent, professional look across all customer touchpoints and dramatically speeds up your publishing timelines, allowing you to deliver information to your users faster.
Heretto Portal: A Centralized Knowledge Hub
Delivering great content is only half the battle; your customers also need to be able to find it. The Heretto Portal helps you create a centralized, searchable knowledge hub where your audience can easily access your documentation. The portal transforms your published content into an intuitive self-service experience, allowing users to find answers to their questions at any time. By providing a single, reliable destination for information, you empower your customers and reduce the burden on your support teams. It’s a direct way to turn your technical documentation into a powerful asset for customer success and satisfaction.
Creating a Branded Self-Service Experience
A knowledge hub should feel like a natural extension of your brand. The Heretto Portal allows you to create a fully branded self-service site that aligns with your company’s visual identity. This consistency helps build trust and provides a seamless experience for users as they move from your main website to your documentation. By offering a polished and professional resource library, you show customers that you are invested in their success. This focus on user experience helps them get more value from your products and solidifies their confidence in your brand long after the initial sale.
Etto AI: Ensuring Content Quality and Consistency
Maintaining high standards across a large volume of technical documentation is a significant challenge. Etto AI is integrated directly into the authoring experience to help your team uphold quality and consistency. This AI-powered assistant can help with everything from improving clarity and summarizing complex topics to checking for adherence to your style guide. It acts as a second pair of eyes for your writers, catching inconsistencies and suggesting improvements before content ever moves to the review stage. By embedding quality checks directly into the creation process, Etto AI helps your team produce better, more consistent documentation with greater efficiency.
Need Help with Your Stylesheets?
As I mentioned at the start of this article, stylesheets are often the most intimidating aspect of a DITA implementation. This is because many people simply don’t have the technical skills to do this work and those skills are not easily acquired. Learning to write stylesheets and manipulate DITA OT plugins is nothing like learning a new software.
To create your own stylesheets, you generally need two things: experience working with eXtensible Stylesheet Language Transformations (XSLT) and knowledge of the DITA OT. Knowledge and experience in just one of these areas isn’t sufficient. You may have developers in your organization with XSLT knowledge, but the DITA OT has many moving parts and can have a complex organizational structure that you need to understand to get your publishing plugins to work.
If the thought of stylesheets raises your blood pressure, there’s no need to fear! There are some options out there for you.
At Heretto, we have strong relationships with some fantastic partners that specialize in this type of work. We’d be happy to recommend a consultant that you can work with to develop your stylesheets. We also have an in-house Professional Services team that can develop your stylesheets for you. Both of these options present some additional cost, but the good news is that stylesheet development tends to be a one-time cost and the benefits can help justify the ROI.
Where to Learn More
- “How much does it cost to format a document?” 2016. 28 September 2016. <http://proceduresolutionsmgmt.com/formatting/>
- “The Importance of Branding and Identity Style Guide” 2014. 3 November 2014. <https://www.six-degrees.com/the-importance-of-a-branding-and-identity-style-guide/>
Explore Heretto's Self-Service Support Portal
If you want to see a live example of what a powerful stylesheet can do, you don’t have to look far. The Heretto Portal is our own self-service support hub, and it’s built using the exact same tools we provide to our customers. It’s the central place to find detailed guides and information for the Heretto CCMS, our Deploy API, and even the Portal itself. We believe in our product so much that we use it for our own documentation needs. This portal is a real-world demonstration of how you can take complex, structured content and transform it into a clean, intuitive, and helpful resource for your users, reducing their reliance on support teams and empowering them to find answers on their own.
See Our Stylesheets in Action
Everything you see on the portal—the branding, the layout, the typography, and the responsive design—is the direct result of our stylesheets. Our technical writers focus on creating structured content in DITA XML within the Heretto CCMS. When it’s time to publish, our stylesheets take that raw, semantic content and apply all the necessary formatting to create the polished HTML pages you see online. This process guarantees that every article, from a quick getting-started guide to in-depth API documentation, has a consistent look and feel. It’s how we ensure our content is always on-brand, easy to read, and professional, all without requiring our writers to spend a single minute on manual formatting.
Frequently Asked Questions
I'm used to styling documents in Word. How is using a stylesheet in DITA really different? The biggest difference is the separation of roles. When you use a program like Word, you are both the writer and the designer, spending a lot of time making sure the formatting looks right. In a DITA framework, the writer's job is to focus only on the content's meaning by applying semantic tags. The stylesheet then acts as the designer, automatically applying all the visual formatting during the publishing process. This frees your writers from manual styling and ensures every document is perfectly consistent.
Do I need to be a developer to create or edit our stylesheets? For the most part, yes. Creating stylesheets requires specialized knowledge of languages like XSLT and an understanding of the DITA Open Toolkit. It's not a skill most technical writers have or need to acquire. This is why most companies work with a consultant or a vendor's professional services team for the initial setup. Think of it as a one-time investment to build the engine that will format all your content automatically from then on.
We're planning a rebrand next year. Does that mean we have to redo all our documentation? Not at all, and this is where stylesheets become incredibly valuable. Since your content is completely separate from its presentation, you don't have to touch thousands of individual documents. Instead, you only need to update your stylesheet with the new logos, color palette, and fonts. Once that's done, you can republish your entire library, and every document will automatically reflect the new branding.
Can we use different stylesheets for different outputs, like a PDF and a website? Yes, this is a core function of stylesheets. You can have a unique stylesheet for every channel you publish to. For example, your PDF stylesheet can control page size, headers, and footers, while your website stylesheet can manage responsive design and interactive elements. This allows you to publish the same source content to many places, with each output perfectly optimized for its specific medium.
What's the first practical step my team should take to define our stylesheet requirements? A great first step is to gather examples of what you want your final documents to look like. Find PDFs, websites, or other materials that have the branding, layout, and typography you're aiming for. Compiling these examples into a simple requirements document gives a stylesheet developer a clear visual target to work toward and makes the entire process much smoother.
Key Takeaways
- Let writers focus on writing, not formatting: Stylesheets automate all visual styling, freeing your team from manual tasks that can consume up to half their time. This allows them to concentrate on creating high-quality, accurate content instead of worrying about its appearance.
- Guarantee brand consistency and publish faster: Using stylesheets ensures your brand's visual identity is applied correctly every time, which helps you publish content up to 60% faster. This consistency builds user trust and eliminates the tedious work of manual formatting corrections.
- Deliver content anywhere from a single source: Stylesheets make it possible to publish the same structured content to a PDF, a website, or an in-app widget without reformatting. You simply apply a different stylesheet for each output, ensuring a perfect user experience everywhere.
