Keeping Brand Styles Consistent Across a Help File Maker Project
A product’s documentation is part of how it looks to customers. When the help site uses different fonts from the app, or an old logo, or wording the marketing pages dropped a year ago, it looks neglected. Matching every help page to the brand by hand becomes difficult to manage once a manual grows to dozens of topics. A help file maker applies the look from one place, so the whole manual carries the same colors, fonts, and layout. You set the style once in the project, and it stays as the content grows.
What Brand Consistency Covers
The Visual Elements
Brand consistency in documentation covers more than a color scheme. The fonts should match the product and the website. Headings, links, tables, and code blocks need one consistent style across every page, so a user moving from the app to the help notices no change.
The Wording That Has to Match
Text carries the brand as much as the design. Product names, the company name, and standard phrases have to appear the same way throughout the manual. A feature called one thing on page three and another on page twenty makes a reader doubt the documentation.
Setting the Style in One Place
Templates and Custom CSS
Dr.Explain handles the visual side of the online manual through templates and custom CSS. A pre-built template gives you a starting theme, and custom CSS controls the detail, down to headings, paragraphs, images, and tables. It ships ready-made templates too, including a user manual template and a corporate knowledge base template. Because CHM is built from the same HTML topics, the CSS carries into the CHM output as well, within the limits of its viewer. The table below shows where each part of the styling is set.
| Brand element | Where you set it | Where it shows |
| Colors and fonts | Template and custom CSS | Online help and CHM |
| Page layout and headings | HTML template | Online help and CHM |
| Repeated text, names, contact details | Project variables | Every output format |
| Print appearance | PDF and DOCX export settings | PDF and DOCX |
Reusable Text with Variables
For wording, project variables keep repeated text in one place. You store a product name or a support address once and reference it everywhere. Change the variable in the project, and the updated wording carries into the next web, CHM, PDF, or Word export.
Where Consistency Carries and Where It Changes
Web Help and CHM
The online help and CHM come closest to matching the product’s visual style. Both are built from HTML, so the template and CSS apply to them directly, and users see the same colors, fonts, and layout in each. There is one caveat for the CHM.
Why Modern CSS Can Look Different in a CHM
CHM relies on Microsoft’s older HTML Help technology and Internet Explorer components. CSS that looks fine in a browser can look different in CHM. Colors, fonts, and basic layout usually hold up, but newer CSS features can cause problems. Check the CHM after export before using it as the finished help file.
PDF and Word
Printed formats follow their own rules. CSS styles web pages, while a help file maker controls printed output through separate export settings for page size, headers, and fonts. In Dr.Explain, these print settings are in the PDF and DOCX export options. The content does not differ because the same project and the same variables feed every format. A brand stays consistent across a help file maker project through shared text and coordinated styling, even where the page layout has to change.
