Schema-controlled fields
Each template clarifies exactly which fields an editor should fill in.
Inspect details →ContentSections Demo
A live demo page that showcases every Content Section template in Kompanse CMS on one route.
This page demonstrates how every active Kompanse CMS Content Sections template can be orchestrated on a single route.

Template 01
A lead section editors can update in seconds while developers consume it with full schema safety.


Template 02
Content managers can refresh the headline, copy, and CTA set without opening the codebase.
Template 03
It is ideal for product, service, or capability launches that need copy and imagery in balance.

Template 04
Each card can carry its own icon, narrative, and destination link for multiple scenarios.
Each template clarifies exactly which fields an editor should fill in.
Inspect details →Publish dozens of different stories through the same frontend component system.
Sample page →When a campaign changes, the CMS record is the only place you need to touch.
Contact →It works well across landing pages, product launches, and corporate storytelling.
Template fields create a shared contract between backend and frontend.
Editors work with structured, intentional blocks instead of free-form guesswork.
Marketing, content, and engineering collaborate around the same block model.
Launch new page sections much faster once the template is already in place.
Conversion, publishing speed, reuse, and team velocity metrics all land well inside this block.
29
Template count
Many presentation patterns within the same module.
2
Active locales
TR and EN content is managed inside the same structure.
1x
Renderer logic
One frontend layer consumes every block.
0 code
Editor update
No deploy is required for copy updates.
A lightweight but effective template for repeating image-based references.

Template 08
It fits blog-style pages, product storytelling, and corporate narratives equally well.
This template is ideal when you need more than a headline and supporting sentence.
A strong format for contrasting an old workflow with a new CMS-driven one.
Before: hard-coded content

After: template-driven structure

A practical choice for campaign videos, onboarding flows, and product explainers.
Especially useful for content production, approval, and publishing workflows.
Pick a hero, card, FAQ, or media-based block according to the page need.
Populate headlines, images, rich text, and CTA slots from the CMS.
Review the same section record across multiple locales.
Carry the same block logic into other landing pages.
Why Content Sections?
The Content Sections module lets teams build marketing pages from reusable, localized, template-driven blocks without engineering handoffs.
Ideal for portfolios, product collections, or reference screenshots.




A great fit for SaaS, service packages, or consulting offers.
$299
/ project
Landing page setup with 3 production sections.
$749
/ project
Multiple templates, dual locale support, and richer content flows.
$1,490
/ project
Full-module rollout, enablement, and long-term content operations.
Useful when multiple packages, solutions, or delivery models need to be compared at once.
Use it for promotional showcases that echo the product catalog without depending on it directly.

A starter set that combines hero, cards, and information blocks in one flow.
View products →
Ideal for promoting a new season, campaign, or category collection.
Read the journal →
Blocks that strengthen the commercial story outside the strict product detail page.
Contact sales →Practical for technical details, package inclusions, or concise benefit lists.
Field type
Text, image, link, number, boolean
Publishing state
Draft / Published
Localization
Locale-specific content values
Reuse
The same structure across multiple page flows
A useful layout for corporate pages, agency crews, or product teams.



Template 18
Turn customer, partner, or internal feedback into strong social proof.

Merve A.
Marketing lead · Demo team
“Content Sections lets us refresh campaign pages without waiting in the engineering queue.”

Deniz T.
Frontend developer · Platform team
“The template schema removes surprises for the frontend team.”

Sena P.
Content manager · Growth studio
“Managing translations, CTAs, and media in one record made the whole workflow dramatically faster.”
Use it for roadmaps, project phases, or product evolution arcs.
Phase 01
The first phase isolated repeatable blocks and mapped their field schemas.
Phase 02
Every template received a live, multilingual demo record.
Phase 03
Real components were connected for every template code.
Phase 04
The full Content Sections inventory became visible under one route.
Template 20
It gathers recurring questions neatly, especially on conversion-focused pages.
Yes. You can create additional section records from the same template and reuse them on other pages.
Yes. This very demo page mixes heroes, rich text, gallery, pricing, and FAQ blocks in one flow.
The renderer maps the templateCode coming from the public API to the matching UI component.
Well suited for multilingual store, office, or service-point listings.
Maslak, Sariyer / Istanbul
+90 212 000 00 01
istanbul@kompanse.com
Soho, London
+44 20 0000 0000
london@kompanse.com
Fully distributed team model
+90 850 000 00 00
support@kompanse.com
A good default for concise, CTA-friendly contact sections.
Address
Maslak, Istanbul / TurkiyePhone
+90 850 000 00 00Hours
Weekdays 09:00 - 18:00

A clean structure for logo, short description, and brand tone in the lower part of a page.
The template inventory is now ready. The next step is mapping it to your own brand and content flow.
Plan a demo call