Support for article-scoped custom HTML, CSS, and JavaScript
N
Nutmeg Porpoise
Authors who want interactive, custom-styled content on a single article currently cannot include style or script tags directly in that article, since these are removed for security reasons. The available workaround applies custom code at the project level, which affects every page rather than one.
Add an editor option that lets authors scope custom HTML, CSS, and JavaScript to one specific article, sandboxed or sanitized in a way that preserves interactivity (for example, calculators, dynamic forms, or custom-styled widgets) without that code running project-wide.
Benefit: Authors could build richer, interactive content on specific pages without changing the styling or behavior of every other page in the knowledge base, and without needing to host and maintain that content on a separate external web server.
Log In