Build & extend

Elementor templates

How the theme binds library templates to the header, footer, archives, and single pages.

The model

EstatePoint keeps layout in Elementor library templates and binds them to slots in the theme. There is one owner per slot, so nothing competes:

Demo import installs all of them and marks each one for its slot, which is how the theme knows what to bind without you choosing post IDs.

Editing a bound template

Two routes, same result:

• Elementor → Templates → Saved Templates, then open the template.
• EstatePoint → Theme Options → Property (or Blog), then Edit in Elementor on the binding card.

Every page bound to that slot changes when you press Update. That is the point — edit once, applied everywhere.

Layout authority

When your library templates declare their slots — as the kit templates do — Elementor owns the structure and Theme Options stops offering structural editors. The Property and Blog tabs then show binding cards with:

• The bound template, with Edit in Elementor
• A layout preset: Left sidebar, Full width (no sidebar), Right sidebar
• Sticky sidebar
• Restore default template
• An optional pinned template ID

A status banner at the top of the tab states which mode you are in. Elementor Pro’s Theme Builder also takes authority when it is active.

Legacy sites that never imported the kit keep the older editable block lists, which compile into the linked template on save.

Restore default template

Re-imports the bundled version of that template, discarding your edits to it. Use it when a template is broken past repair — a deleted widget you cannot re-add, a layout you cannot untangle.

Your listings, pages, and settings are untouched; only that one template resets.

Elementor Free vs Pro

Every EstatePoint widget registers on Elementor Free. The theme renders bound library templates itself, so archive, single, header, and footer layouts all work without Pro.

Elementor Pro adds its own Theme Builder — display conditions, its own template types, and its own widget set. If you use it, Pro takes layout authority and EstatePoint steps aside. Both paths work; do not mix two owners for the same slot.

Creating your own template for a slot

1. Elementor → Templates → Add New and build the layout with the matching EstatePoint widgets — for example Archive — Property for a property archive.
2. Publish it.
3. Open Theme Options → Property and pin its template ID on the binding card, if the theme has not already picked it up.

The theme prefers templates that declare a slot, then compatible ones by title. Pinning is the manual override when you keep several variants around.

Working in the editor

Property and archive blocks show placeholders. They need a real listing or query for context; in the library template they render sample or empty states. Always verify on a real front-end URL.

Regenerate CSS after imports. Elementor → Tools → Regenerate CSS & Data after importing or restoring templates, or you will chase styling ghosts that are only stale generated files.

Do not paste kit templates between sites by hand. Export/import through Elementor’s own template tools, or re-run demo import on the target site.

Related

• Widget library — every widget and which template it belongs in
• Header & footer
• Single property layouts