Blog Sections Open
Running Two JotX Instances on One Page Without Style Collisions
Two JotX calls can coexist on one page, but only if their configs, wrappers, and style assumptions are kept separate.
The donor issue involved one JotX instance rendering full comments and another rendering a random sidebar comment. The second config overrode the styling of the first.
Why This Happens
Legacy components often assume one configuration context per page. Once two outputs share global config values, CSS selectors, or wrapper assumptions, one instance can bleed into the other.
Practical Fix Direction
- Separate templates and wrappers clearly for each instance.
- Avoid config names or assets that assume a single output context.
- Inspect generated classes and selectors to see where the style collision begins.
This donor is a good reminder that multiple component instances on one page should be treated as an integration scenario, not as two isolated snippet calls.
Getting Started with the DocManager Module in Evolution CMS
A practical orientation for teams who see DocManager in a custom build but are not sure how it differs from older document management tools.
Assigning Sequential Classes to Wayfinder Menu Items
How to generate class names like mm1, mm2, and mm3 automatically in Wayfinder output instead of hard-coding them in static HTML.