Features/Designer

Semantic HTML output

Pages render as real, nested HTML tags you chose, with styles in a stylesheet instead of inline style attributes.

What you build in the Designer is output as the same HTML tags on the live site: an h2 stays an h2, a nav stays a nav. Styles are compiled into a CSS file with class selectors and media queries, not written inline on each element.

How it works

  • The visitor renderer writes <tagname attributes> for each element; only embed, body, rich-text, form-widget and membership-form-widget are rendered as div.
  • Element level styles compile to a generated class per element (.t<id>); classes compile to .classname; global tag styles compile to the tag selector.
  • All selectors are scoped under main (tag styles under body main).
  • Breakpoints compile to @media screen and (max-width: Npx), ordered from largest to smallest; the 1920 desktop base has no media query.
  • Color swatches compile to CSS custom properties on main.
  • Custom fonts compile to @font-face rules with font-display: swap.
  • CSS is minified when the build asks for it.

When to use it

  • Ship pages with a clean heading hierarchy for SEO
  • Hand clean markup and CSS to a developer

Limitations

  • Generated per element class names (.tNNN) are not human readable
  • Some tags are not available (see HTML tags support)
  • The alt fallback is the layer name, which may not describe the image

Availability

  • Works in Designer.
  • Included in every plan.

How to use it.

  1. Choose the right tag for each element
  2. Style with classes or element styles
  3. Publish; the CSS build compiles everything into the stylesheet

Questions.

Does Divhunt use inline styles?

Are breakpoints mobile first?

Related features.

No card needed

Build it today.Pay when it goes live.

Every feature is unmetered while you build. Checkout opens the first time you publish.