Plans supporting this feature: Professional Business Enterprise
Fonts play an important role in defining the visual identity and readability of your knowledge base. In Document360, you can configure fonts at both the project level and the article level to ensure a consistent experience for your readers. This article explains how to manage fonts, where to configure them, and how recent updates to font availability may impact your existing setup.
Configuring fonts at the project level
To configure fonts in Document360:
Navigate to Settings () in the left navigation bar.
In the left navigation pane, navigate to Knowledge base site > Site customization.
Locate the Fonts section.
Select from the available font combinations provided by the system.
To create your own combination, click Have a specific font combination in mind?
You can configure the following:
Article titles - Applies to headings in your articles.
Article content - Applies to the body content of your articles.
Site font - Applies to navigation, headers, and other interface elements.
Click Save to finalize your customizations.
These settings are applied at the project level and affect the entire knowledge base site.
.png)
Configuring fonts within an article editor
You can also apply fonts at the article level for specific content.
To change fonts within an article:
Open the desired article in the editor.
Select the text you want to modify.
Use the formatting options in the toolbar.
Choose the required font from the available options.
NOTE
Fonts applied directly within the article editor affect only the selected content. Project-level font changes apply only to content that uses the default font settings.
Changes to font availability
As part of ongoing improvements to ensure cross-browser consistency, long-term platform support, and better performance, Document360 has standardized the fonts available in the knowledge base editor for site themes.
As a result, a small set of fonts has been removed and replaced with suitable alternatives.
These replacement fonts are metrically compatible, meaning they are designed to closely resemble and match the original fonts in terms of:
Character width
Line spacing
Overall readability and layout
This ensures that your content maintains a consistent visual structure even after the change.
How this affects your knowledge base
Existing projects/articles
If your project is using one of the removed fonts:
The font will appear in the format: Font A / Font B.
(where Font A refers to the removed font and Font B refers to the new replacement fallback font)A tooltip will be displayed indicating that font rendering may vary based on system support, which means the original font may appear where available; otherwise, a fallback font will be used.
This ensures a smooth transition without breaking existing configurations.
New projects/articles
If you have not previously used these fonts, no action is required. Only the currently supported fonts will be visible in the font selection options.
NOTE
Newer font options may not appear in Knowledge base site 1.0
Font rendering behavior across systems
Even though the font (Font A) is no longer provided by Document360, it will still render in most of the cases (subject to system’s font package availability).
If a user’s system (for example, Windows/iOS) already supports and has Font A installed, it may continue to display.
If the system does not support Font A, the fallback font (Font B) will be displayed instead.
What you can do next to manage your font preferences
In most cases, no action is required. But, if you still need to align with specific preferences or brand guidelines, you can consider the following options:
Method 1: Choose from available fonts
You can choose from a well-curated set of fonts available in Document360, giving you flexibility to match your preferred style or brand guidelines.
Method 2: Use a licensed font (if required)
If your organization requires a specific font (for example, branding purposes):
Purchase the appropriate font license
Share the font hosting URL with the Document360 team
The font can then be configured for consistent usage across your knowledge base experience.
Method 3: Use custom CSS/JavaScript
If you are familiar with custom styling, you can configure fonts using custom CSS/JavaScript in Document360.
Navigate to Settings () > Knowledge base site > Site customization > Custom CSS & JavaScript, and add the following:
@font-face {
font-family: 'Your Font Name';
font-style: normal;
font-weight: 300 800;
font-stretch: 100%;
src: url('Font URL');
unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;}FAQ
Why do I see two fonts (Font A / Font B) in the font selection?
This indicates that the original font (Font A) has been replaced with a fallback font (Font B). Depending on system support, either the original or fallback font may be displayed in the Knowledge base site.
Will my existing content be affected by this change?
No. Your content will remain unchanged.
Articles created in the past, currently being edited, or newly created will continue to work as expected. However, the way fonts are displayed may vary slightly depending on system support.
Can I continue using the old fonts?
If the font is available on your system, it may still appear and yes, you can continue using it.
However, since it is no longer supported in Document360, it is recommended to use the fallback or other available fonts.
If I replace a font, will it update all articles?
It depends on where the font change is applied.
If you update the font from project-level font settings, the change applies across the knowledge base wherever the default font is used.
If you change the font inside an individual article, only the selected content in that article is updated.
Any content where a font was manually applied inside the editor will continue to use that selected font unless changed again.
Why didn’t some content update when I changed the project font?
Content that uses the default project font updates automatically when the project font settings are changed.
However, any content where a font was manually applied inside the article editor remains unchanged, because manual font formatting overrides the default font setting.
Do I need to update my fonts after this change?
No, in most cases, no action is required.
The fallback fonts have been carefully researched and selected to be metrically compatible with the original fonts, ensuring a very close match in terms of layout, spacing, and readability.
Why don’t I see Font A / Font B in my project?
This is expected behavior, and no action is required. In this article, Font A refers to a previously used (now removed) font, and Font B refers to its new replacement fallback font.
If you don’t see the format Font A / Font B, it means your project is not using any of the removed fonts.
Only projects that were already using those fonts will see this format. For all other projects, only the supported fonts by Document360 will be displayed in the font selection options.