Custom HTML, CSS and JavaScript

Override a section with your own code when the built-in options genuinely cannot do it.

لم يُترجم هذا الدليل بعد، لذا يظهر بالإنجليزية.

من يمكنه ذلكowneradmin

Each section's Advanced tab takes custom HTML, CSS and JS, and there is a Custom section type for arbitrary markup.

This is the escape hatch, not a starting point. Custom code is not covered by revision history in the way section content is, it can break your layout on mobile, and it will not adapt when you change your theme. Use a built-in section wherever one will do.

Steps

Open Page editor and select the section.
Open the Advanced tab.
Add Override HTML, Custom CSS, Custom JS or a Custom class.
Page editor advanced tab with the custom HTML, CSS and JS fields
Save code, then check the preview on every device size.

Reasonable uses

An embed a section type does not cover: a video player, a map, a partner's widget.
A small style fix — nudging one heading, adjusting spacing a preset does not reach.
Analytics or a conversion tag, if you cannot add it another way.
A layout genuinely not expressible with existing section types.

Unreasonable uses

Rebuilding something that exists. Your agenda, speakers and registration form all have sections that pull live data. Hand-coded copies go stale and drift out of sync.
Restyling the whole site. That is the theme.
Anything you cannot maintain. If you leave, someone else has to work out what this does.

If you write custom CSS

Scope it. Use the Custom class on the section and target that, so you do not restyle the rest of the site by accident.
Test RTL if you run Arabic. Hard-coded left and right break in Arabic — use logical properties or test both directions.
Test on mobile. Fixed pixel widths are the usual cause of a page that scrolls sideways on a phone.

If you write custom JS

Assume it may run before or after the rest of the page.
Do not depend on evenclo's own class names or markup; they can change.
Anything essential — registering, paying, checking in — must never depend on your script. If it fails, people must still be able to register.

What happens next

Custom code is part of your draft until you publish. Check every device size and both languages first.

Common problems

The page scrolls sideways on mobile. A fixed width in your CSS. Use percentages or max-width: 100%.

Your CSS restyled other sections. Not scoped. Add a Custom class and target it.

The layout breaks in Arabic. Hard-coded left/right in your CSS.

Your script does nothing. Check the browser console for errors.

An embed does not appear. Many providers block being embedded on other domains. Check with the provider.

You want to undo it. Clear the fields and save. Custom code is not versioned like section content, so keep your own copy of anything substantial.