ICanUp Page Builder Gained a New Generation of Content Blocks
Product

ICanUp Page Builder Gained a New Generation of Content Blocks

ICanUp gained reusable Hero, CTA, Highlight, Cards, Steps, and FAQ blocks, multiple presentation variants, and a generic Model Collection architecture. Complex presentation pages can now be built without dedicated hard-coded templates.

The first ICanUp Pages could already be composed from content blocks, but those blocks primarily solved the basic problem of placing text, headings, images, and other standard content.

In September 2026, that system took its next major step.

ContentBlocks began defining not only page content but also composition: hero sections, cards, process steps, highlights, calls to action, FAQ sections, and dynamic collections.

New blocks for presentation pages

Hero

A strong introductory section with title, supporting content, optional media, and primary actions.

CTA

A dedicated call-to-action block that can be placed within or at the end of a Page.

Highlight

An emphasized section for an important idea, benefit, proposal, or key message.

Cards

Repeatable cards for services, capabilities, benefits, and other structured collections.

Steps

Ordered steps for explaining a process, workflow, or sequence of actions.

FAQ

A structured question-and-answer block with accessible expandable items.

Presentation variants became part of the system

The new blocks are not tied to a single visual representation.

The architecture separates content from presentation configuration such as alignment, spacing, media, action placement, and supported variants.

Variants are intended to represent different use cases rather than minor cosmetic CSS changes.

The same block type can therefore appear in multiple contexts without creating a page-specific copy.

Model Collections became a generic block

Automatic Collection

Records can be resolved automatically using validated filtering, sorting, and limit rules.

Manual Collection

Administrators can explicitly select records and preserve their chosen order.

Cards

A full card grid suitable for a dedicated landing page or large collection section.

Compact

A denser representation designed for collections embedded between other Page sections.

Featured

A stronger visual treatment for a smaller set of selected or important records.

Model-Agnostic Architecture

Post Series was the first use case, while additional public model collections can be registered without creating a new block type.

The builder remained safe and predictable

Generic configuration does not mean a Page can submit arbitrary PHP classes or unrestricted query options.

Each supported collection type is explicitly registered and owns its allowed filters, sorts, layouts, and public presentation rules.

This keeps the generic block independent from individual models and avoids turning the central component into a long chain of model-specific conditions.

Services became the first major real-world test

The new architecture was validated by more than isolated components.

The complete Ukrainian and English Services Page was assembled through the standard ICanUp Page architecture.

It uses Hero, Cards, process Steps, Highlight sections, CTAs, FAQ, and other reusable blocks.

No Services-specific hard-coded public template was introduced. The same mechanism can later build About pages, landing pages, product presentations, and other rich public sections.

The new blocks remained part of the shared platform

The richer presentation capabilities did not create a separate builder exclusively for Services.

Ukrainian and English content continues through the shared ContentBlock localization pipeline. Public rendering supports responsive layouts, light and dark themes, and accessibility requirements.

Pages also continue to reuse the existing ICanUp SEO infrastructure including canonical URLs, hreflang, Open Graph, breadcrumbs, and sitemap integration.