Every Emovart help center ships with a set of stable, prefixed CSS classes. When you write rules in the custom CSS integration, target these .kn-* selectors — they are part of our styling contract and won't be renamed without notice, unlike the auto-generated utility classes you may spot in the page source.
Here are the classes you'll reach for most often:
.kn-header— the top bar with your logo, navigation, and search..kn-search— the search field in the header and on the home page..kn-nav-tabs— the collection tabs shown in the Documentation layout..kn-sidebar— the grouped article sidebar in the Documentation layout..kn-breadcrumbs— the breadcrumb trail above article titles..kn-category-card— the collection cards on the Help Center home page..kn-article— the wrapper around an article's rendered body..kn-article-title— the article's main heading..kn-article-description— the italic subtitle under the title..kn-toc— the "On this page" table of contents beside articles..kn-callout— callout blocks rendered from your Notion callouts..kn-reactions— the "Did this answer your question?" feedback box..kn-contact-button— the Contact button in the header..kn-footer— the site footer..kn-widget-launcher— the floating launcher button of the embeddable widget.
A quick example that rounds the category cards, tints callouts, and hides the footer:
/* Softer category cards */
.kn-category-card {
border-radius: 14px;
box-shadow: 0 2px 10px rgba(15, 40, 30, 0.08);
}
/* Brand-tinted callouts */
.kn-callout {
border-left: 3px solid #1D4A36;
background: #f2f7f4;
}
/* No footer, thanks */
.kn-footer {
display: none;
}Your rules apply to both layouts. Classes that only exist in one layout — like .kn-sidebar — are simply ignored in the other, so you can switch layouts without touching your stylesheet.
If you want to style something that doesn't have a .kn-* class yet, tell us through the Contact button on this site — we're happy to add stable hooks where they're missing.