Landingi
Landingi is a no-code, cloud-based landing page builder. At Terra, we mainly use it for DAT website projects, usually when speed, simplicity, and marketing flexibility are key requirements.
This guide explains how Landingi works, its main limitations, and the best practices we follow when working with it.
Overview
Section titled “Overview”Landingi is designed around independent landing pages that are created, edited, and published directly from its dashboard.
Unlike traditional CMSs, Landingi:
- does not have a content hierarchy (no posts, templates, or collections)
- does not support staging environments or draft-only publishing
- focuses on speed and simplicity rather than long-term scalability
Because of this, most actions in Landingi have immediate impact on live pages.
Before making changes, always check:
- which page you are editing
- whether it is already published
- whether the change affects only that page or multiple pages
Pages are the core unit in Landingi.
Each page is a standalone landing page with its own layout, content, and URL.
Creating and managing pages
Section titled “Creating and managing pages”- Pages are created directly from the Landingi dashboard.
- Pages can be built from templates or duplicated from existing pages.
- There is no staging, preview-only, or draft publishing flow.
- Once a page is published, it becomes live immediately.
This makes Landingi very fast to work with, but also increases the risk of unintended changes.
Sections
Section titled “Sections”Landingi pages are built using sections. Understanding how sections behave is essential, especially when working with shared content.
There are two types of sections in Landingi: Regular Sections and Smart Sections.
Regular Sections
Section titled “Regular Sections”Regular Sections are page-specific:
- They belong only to the page where they are created.
- Changes affect only that page.
- They are best suited for unique layouts or content that should not be reused.
When in doubt, use Regular Sections.
Smart Sections
Section titled “Smart Sections”Smart Sections are global and reusable:
- A Smart Section can be used across multiple pages.
- Editing a Smart Section updates it everywhere it is used, instantly.
- They are typically used for shared elements such as headers, footers, legal banners, or repeated promotional blocks.
Smart Sections are powerful, but they require extra care.
Editing Smart Sections
Section titled “Editing Smart Sections”Smart Sections often contain custom HTML, CSS, and JavaScript, especially when more advanced layouts or interactions are needed.
Recommended workflow
Section titled “Recommended workflow”To keep changes controlled and predictable:
- Edit the code locally using Visual Studio Code (or another code editor).
- Review and validate the changes locally as much as possible.
- Paste the final version into the Smart Section’s code editor in Landingi.
This helps avoid formatting issues, syntax errors, and accidental partial edits.
Responsive behavior (Endpoints)
Section titled “Responsive behavior (Endpoints)”Landingi provides only two breakpoints:
- Desktop
- Mobile
There is no tablet or intermediate breakpoint.
Tablet layouts are automatically derived from one of these two endpoints.
Because of this limitation:
- mobile layouts often need extra attention
- simple, flexible layouts usually work best
- always review both endpoints before considering a page finished
Best practices
Section titled “Best practices”- Duplicate pages before making major changes.
- Use hard-to-guess slugs for testing pages.
- Prefer Regular Sections unless content must be shared.
- Be extremely cautious when editing Smart Sections.
- Review both desktop and mobile endpoints.
- Assume that most changes affect live content.
Knowledge Check
Test your understanding of this section
Loading questions...