---
title: "OroCommerce Frontend: Beyond the Twig and Layouts Bottleneck"
canonical_url: "https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck"
locale: en
meta:
description: "OroCommerce storefront theming runs on YAML layout updates, Twig block themes and SCSS builds. How B2B teams keep Oro logic and let marketers edit visually."
"og:description": "OroCommerce storefront theming runs on YAML layout updates, Twig block themes and SCSS builds. How B2B teams keep Oro logic and let marketers edit visually."
"og:title": "OroCommerce Frontend: Beyond the Twig and Layouts Bottleneck"
---
# OroCommerce Frontend: Out of the Twig and Layouts Bottleneck
Table of contents
1. [1.How the OroCommerce storefront is built](#how-the-orocommerce-storefront-is-built)
2. [2.Where the bottleneck forms in day-to-day work](#where-the-bottleneck-forms-in-day-to-day-work)
3. [3.What marketers can already do in Oro, and where it stops](#what-marketers-can-already-do-in-oro-and-where-it-stops)
4. [4.Keeping the Oro B2B logic, moving the presentation layer](#keeping-the-oro-b2b-logic-moving-the-presentation-layer)
5. [5.What changes for development teams](#what-changes-for-development-teams)
6. [6.A practical path from layout update to component](#a-practical-path-from-layout-update-to-component)
7. [7.FAQ](#faq)
8. [8.Conclusion](#conclusion)
1. [1.How the OroCommerce storefront is built](#how-the-orocommerce-storefront-is-built)
2. [2.Where the bottleneck forms in day-to-day work](#where-the-bottleneck-forms-in-day-to-day-work)
3. [3.What marketers can already do in Oro, and where it stops](#what-marketers-can-already-do-in-oro-and-where-it-stops)
4. [4.Keeping the Oro B2B logic, moving the presentation layer](#keeping-the-oro-b2b-logic-moving-the-presentation-layer)
5. [5.What changes for development teams](#what-changes-for-development-teams)
6. [6.A practical path from layout update to component](#a-practical-path-from-layout-update-to-component)
7. [7.FAQ](#faq)
8. [8.Conclusion](#conclusion)
The OroCommerce frontend is a server-rendered storefront built from Symfony bundles, OroLayouts and Twig block themes, and most visible changes go through a developer, a YAML layout update and a theme build. Teams that want to move faster do not have to give up Oro: the B2B logic stays in the backend, while a separate frontend layer takes over presentation and lets marketers compose pages visually. This article looks at where the theming effort actually comes from and how to decouple it step by step.
## How the OroCommerce storefront is built
OroCommerce is a Symfony application, and the [storefront quick start in the official Oro documentation](https://doc.oroinc.com/6.1/frontend/storefront/quick-start/) makes clear that all storefront code lives in bundles. Every page is described by a layout: a tree of blocks, each with a block type and options. That tree is not edited in a template file but modified through layout updates, which are YAML files with actions such as `@add`, `@move`, `@remove`, `@setOption` and `@setBlockTheme`. To target a single page, the update sits in a folder named after the Symfony route, for example `oro_product_frontend_product_view`.
Rendering happens in Twig. Each block maps to a Twig block, and changing its markup means locating the right block with the Twig Inspector, overriding it in a matching path inside a custom bundle and attaching the new block theme through a layout update. Styling is SCSS, declared per theme in `assets.yml` and compiled with an npm build that takes the theme name as a parameter.
Themes inherit from each other. According to the [Oro theming documentation](https://doc.oroinc.com/6.1/frontend/storefront/theming/), a custom theme declares a parent in `theme.yml`, usually the default theme, so that core files stay untouched. Some theme options can be exposed in the back office as theme configuration, which gives administrators a few switches without code.
This architecture is deliberate and powerful. It lets integrators change almost any part of the storefront without forking the core, and it keeps upgrades manageable. The price is that the skills needed for everyday frontend work are broad: PHP and Symfony, YAML, Twig, SCSS, npm builds and the Symfony Profiler for debugging the layout tree.
## Where the bottleneck forms in day-to-day work
The layout system was designed for developers, and that is where friction appears once a B2B storefront grows. A typical request from sales or marketing, such as a new teaser above the product list for one customer group, follows a predictable path:
1. Marketing describes the change in a ticket, often with a screenshot.
2. A developer finds the relevant blocks in the layout tree for the right route.
3. The developer writes or extends a YAML layout update and, if markup changes, a Twig block theme.
4. SCSS is adjusted and the theme assets are rebuilt.
5. The change goes through review, staging and deployment like any other code change.
6. Marketing checks the result and, more often than not, asks for a second iteration.
None of these steps is unreasonable on its own. Together they turn small content and layout changes into development tasks that compete with integration work, ERP interfaces and pricing logic. In B2B projects, the same developers are often responsible for customer-specific price lists, quote workflows and account hierarchies. Frontend requests queue behind them.
A second effect is knowledge concentration. Layout updates are spread across many bundles, and the effective page is only visible at runtime. Teams that rely on an external OroCommerce agency for frontend development often find that only a few people can predict what a given layout change will affect. That is not a weakness of Oro, it is the natural result of a flexible, inheritance based theming model applied over years.
## What marketers can already do in Oro, and where it stops
It would be wrong to say OroCommerce has no editor for marketers. The [WYSIWYG field documented by Oro](https://doc.oroinc.com/6.1/bundles/commerce/CMSBundle/WYSIWYG-field/) is based on GrapesJS and is used by default for landing pages and content blocks. Content teams can build CMS pages and place content blocks without touching Twig.
The limit is the commerce pages themselves. Product detail pages, product lists, the shopping list and checkout are defined by layouts and block themes. Rearranging sections there, adding a new component type or creating a variant for a specific customer group is still a code change. In practice, marketers have a visual editor for the content corners of the storefront, while the pages that drive B2B revenue remain developer territory.
| Change type | Native Oro storefront | Frontend layer on the Oro API |
| --- | --- | --- |
| Landing page or content block | WYSIWYG editor (GrapesJS) | Visual editing in Studio |
| Reordering sections on a product page | YAML layout update, deployment | Drag and drop in Studio, publish |
| New component type | Block type, Twig block theme, SCSS | New component in the shared library, then reusable everywhere |
| Variant for one customer group | Layout condition or custom code | Page variant composed visually, data from Oro |
| Styling across brands or websites | Child theme per website, asset build | Design tokens and shared components |
| B2B logic (prices, quotes, accounts) | Stays in Oro | Stays in Oro, read via API |
## Keeping the Oro B2B logic, moving the presentation layer
The decisive point for most Oro customers is that the backend is not the problem. Customer hierarchies, customer-group price lists, requests for quote, shopping lists and multi-website setups are exactly why companies chose OroCommerce. A frontend modernization should not touch any of that.
Oro supports this separation itself. The [storefront REST API](https://doc.oroinc.com/6.1/backend/api/storefront/) exposes storefront resources over HTTP, with a sandbox for exploring them and an optional guest API for anonymous visitors. That makes it possible to render the storefront outside the Symfony application while Oro stays the system of record.
This is where Laioutr comes in as a Frontend Management Platform. The [Composable Headless Frontend](https://www.laioutr.com/en/composable-headless-frontend) runs as a Nuxt application in front of OroCommerce and reads catalog, prices, cart and account data through the API. Orchestr normalizes that data into one model, so frontend components do not depend on Oro specific response structures. The [headless frontend for OroCommerce](https://www.laioutr.com/en/headless-frontend-for-oro-commerce) describes which B2B features can be rendered this way, provided the corresponding API resources are available in the project.
On top of that layer, marketers work in the [Composable Visual Page Builder](https://www.laioutr.com/en/composable-visual-page-builder). Developers define components and guardrails once, marketers compose product, category and campaign pages from them and publish without a deployment. Laioutr reports around 65 percent shorter time to launch for new landing pages compared with a classic headless setup.
## What changes for development teams
Moving the presentation layer does not remove developers from the frontend. It changes what they spend time on.
- **Components instead of layout patches.** Instead of maintaining YAML updates per route, developers build reusable components in Vue and Nuxt. Laioutr ships 70+ components as a starting point.
- **One data model.** Components consume normalized data. If the backend landscape changes later, the component library stays. Laioutr connects to 50+ backends.
- **Fewer asset builds per change.** Content and layout changes no longer trigger a theme build and deployment.
- **Clearer ownership.** Oro developers focus on pricing, workflows and integrations, frontend developers on components and performance, marketers on pages.
- **Performance as a platform property.** Core Web Vitals are handled in the layer, which is covered on the [Performance and Core Web Vitals](https://www.laioutr.com/en/product/performance-core-web-vitals) page.
Teams planning the move usually start with a limited scope. The [phased approach to replatforming an OroCommerce frontend](https://www.laioutr.com/en/blog/oro-commerce-replatforming-headless-frontend) describes how route groups can move one at a time with a rollback path. For a broader comparison of default theme, custom build and frontend platform, see [headless frontend options for OroCommerce compared](https://www.laioutr.com/en/blog/oro-commerce-headless-frontend-options-compared).
## A practical path from layout update to component
A good way to start is an audit of existing layout updates and block themes. Grouping them answers three questions: which changes are pure presentation, which encode business rules, and which only exist because marketers had no other way to make a change.
1. **Inventory.** List custom bundles, layout updates per route and overridden Twig block themes.
2. **Classify.** Mark each item as presentation, business logic or workaround.
3. **Map to components.** Presentation items become component candidates with clear props.
4. **Check the API.** Confirm that every data point the components need is exposed by the storefront API, and plan API extensions in Oro where it is not.
5. **Move content routes first.** Landing pages and category entry pages are a low risk start.
6. **Follow with product and list pages.** Once the component library is stable, the high traffic pages follow.
7. **Keep checkout logic in Oro.** Checkout and quote flows move last and only when every rule is covered by the API.
The result is a storefront where Oro remains the B2B engine and the frontend team stops maintaining layout patches for changes that marketing could make on its own.
## FAQ
### Does a headless frontend replace OroCommerce?
No. OroCommerce stays the backend for catalog, prices, customers, quotes and orders. Only the presentation layer moves to a separate frontend that reads data through the storefront REST API.
### Can existing Twig templates be reused?
Not directly. Twig block themes render inside the Symfony application. Their structure and design decisions are a valuable reference, though, and the layout audit usually turns them into a clear component list.
### Is the Oro WYSIWYG editor not enough for marketing?
For landing pages and content blocks it often is. The gap is on commerce pages such as product lists and product detail pages, where structure is defined by layouts and changes require development.
### Do B2B features like customer-group prices and quotes still work?
They stay in Oro and are read through the API. Whether a specific feature can be rendered depends on the API resources available in the project, which is why the API check belongs early in planning.
## Conclusion
The OroCommerce layout system gives developers precise control, and that precision is why routine storefront changes end up in the development backlog. Teams that want to keep Oro as their B2B backend can move presentation into a Frontend Management Platform, give marketers visual control over commerce pages and let developers focus on components and integrations instead of layout patches.
### More from the Laioutr Platform
- [Headless frontend for OroCommerce](https://www.laioutr.com/en/headless-frontend-for-oro-commerce)
- [Composable Visual Page Builder](https://www.laioutr.com/en/composable-visual-page-builder)
- [Composable Headless Frontend](https://www.laioutr.com/en/composable-headless-frontend)
- [Performance and Core Web Vitals](https://www.laioutr.com/en/product/performance-core-web-vitals)
- [B2B Growth Kit](https://www.laioutr.com/en/growth-kit/b2b)
---
Share this article
[Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Forocommerce-frontend-twig-layouts-bottleneck) [Share on X](https://x.com/intent/post?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Forocommerce-frontend-twig-layouts-bottleneck&text=) [Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Forocommerce-frontend-twig-layouts-bottleneck) [Share on Pinterest](https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Forocommerce-frontend-twig-layouts-bottleneck&description=) [Share via email](mailto:?subject=&body=%0A%0Ahttps%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Forocommerce-frontend-twig-layouts-bottleneck)
## More articles on frontend and headless
Practical know-how for frontend development, smart agents, and headless
[To the blog](https://www.laioutr.com/en/blogs/insights)
[Several AI Agents, One Storefront: Coordination Without Collisions
When several AI agents work on the same storefront, conflicts rarely happen between the agents thems…](https://www.laioutr.com/en/blog/frontend-operations-multi-agent-coordination-storefront-2026)
[Measuring AI Agents by Outcomes: Agentic Frontend Management Metrics
AI agents in the frontend should be measured by outcomes, not by activity. The number of prompts, ge…](https://www.laioutr.com/en/blog/frontend-operations-measuring-ai-agents-outcomes-2026)
[The Execution Gap in the Frontend: Finding Is Cheap, Shipping Is Not
The execution gap in the frontend is the time, and the number of handoffs, between "we know wha…](https://www.laioutr.com/en/blog/frontend-operations-execution-gap-detect-vs-deploy-2026)
[Adding an AI Layer to an Existing Commerce Stack Without Replatforming
An AI layer can be added to an existing commerce stack without replacing the shop system. The most p…](https://www.laioutr.com/en/blog/frontend-operations-ai-layer-existing-stack-without-replatforming-2026)
[The Hidden Cost of Manual Storefront Changes and How to Cut It
Manual frontend changes are the many small edits that keep a storefront running day to day: a new ba…](https://www.laioutr.com/en/blog/frontend-operations-hidden-cost-manual-storefront-changes-2026)
[Which Frontend Tasks Should AI Agents Take Over? Role and Risk Map
AI agents should first take over the frontend tasks that come up often, involve a lot of manual work…](https://www.laioutr.com/en/blog/frontend-operations-agent-task-map-role-risk-2026)
[Frontend Monitoring Beyond Uptime: Signals a Storefront Needs
Frontend monitoring beyond uptime means checking a storefront not only for availability but for what…](https://www.laioutr.com/en/blog/frontend-operations-monitoring-beyond-uptime-2026)
[Root Cause in the Frontend: When Revenue Drops Start in the Storefront
When revenue or conversion rate drops suddenly, the cause often is not traffic, pricing or the comme…](https://www.laioutr.com/en/blog/frontend-operations-root-cause-revenue-drop-storefront-2026)
[Laioutr Academy Is Live: The Video Manual for Laioutr
Since October 15, 2026, the Laioutr Academy has been live at academy.laioutr.com. It is the user man…](https://www.laioutr.com/en/blog/laioutr-academy-launch-video-manual-certification)
[Tailwind + Alpine vs. Component-Based Frontends for Magento
Hyvä renders Magento pages on the server with PHP templates and layout XML, adds interactivity throu…](https://www.laioutr.com/en/blog/tailwind-alpine-magento-vs-component-based-frontend-2026)
[OroCommerce Frontend: Out of the Twig and Layouts Bottleneck
The OroCommerce frontend is a server-rendered storefront built from Symfony bundles, OroLayouts and …](https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck)
[One Magento Backend, Many Channels: Personalization in Practice
Personalization across web, mobile and voice on a single Magento backend does not start with a featu…](https://www.laioutr.com/en/blog/magento-multichannel-personalization-web-mobile-voice-2026)
[Edge Hosting for Storefronts: Caching That Holds Under Peak Load
Edge hosting keeps a storefront fast under load when most requests never reach the origin: pages and…](https://www.laioutr.com/en/blog/edge-hosting-storefronts-peak-traffic-caching-2026)
[Composable Commerce 2027: What Shifted and What Comes Next
Composable commerce enters 2027 with a different agenda than a year ago. The architecture question i…](https://www.laioutr.com/en/blog/composable-commerce-2027-outlook)
[AI Engagement and Conversion: Personalization on the Frontend
AI-driven engagement and conversion on the frontend rests on five mechanics: segments decide who see…](https://www.laioutr.com/en/blog/ai-engagement-conversion-frontend-personalization)
## Apps for the Laioutr platform
[View all apps](https://www.laioutr.com/en/apps)
[](https://www.laioutr.com/en/apps/shopify)
Laioutr
[Shopify](https://www.laioutr.com/en/apps/shopify)
Shopify is a commerce platform for selling online and in physical retail.
[](https://www.laioutr.com/en/apps/shopware)
Laioutr
[Shopware](https://www.laioutr.com/en/apps/shopware)
Shopware is a flexible ecommerce platform from Europe for product catalogs and omnichannel commerce.
[](https://www.laioutr.com/en/apps/adobe-commerce)
Laioutr
[Adobe Commerce](https://www.laioutr.com/en/apps/adobe-commerce)
Adobe Commerce is an enterprise commerce platform for complex, global B2C and B2B scenarios.
Planned
[](https://www.laioutr.com/en/apps/b2b-sellers)
Laioutr
[B2Bsellers](https://www.laioutr.com/en/apps/b2b-sellers)
B2B suite for Shopware that turns an online store into a professional B2B commerce platform.
Planned
[](https://www.laioutr.com/en/apps/commerce-layer)
Laioutr
[Commerce Layer](https://www.laioutr.com/en/apps/commerce-layer)
Commerce Layer is a headless commerce platform for making inventory and catalogs available online.
[](https://www.laioutr.com/en/apps/commercetools)
Laioutr
[Commercetools](https://www.laioutr.com/en/apps/commercetools)
Commercetools is a SaaS-based headless ecommerce platform used worldwide.
[](https://www.laioutr.com/en/apps/emporix)
Laioutr
[Emporix](https://www.laioutr.com/en/apps/emporix)
Emporix is a composable, API-first commerce platform for scalable B2B and B2C scenarios.
Planned
[](https://www.laioutr.com/en/apps/hcl-software)
Laioutr
[HCL Software](https://www.laioutr.com/en/apps/hcl-software)
Enterprise suite for digital commerce and experience with extensive configurability.
Planned
[](https://www.laioutr.com/en/apps/intershop)
Laioutr
[Intershop](https://www.laioutr.com/en/apps/intershop)
Enterprise commerce platform for complex B2B and B2C business models.
Planned
[](https://www.laioutr.com/en/apps/magento-2)
Laioutr
[Magento 2](https://www.laioutr.com/en/apps/magento-2)
Widely used, extensible commerce platform for B2C and B2B scenarios.
[](https://www.laioutr.com/en/apps/oxid-eshop)
Laioutr
[OXID eShop](https://www.laioutr.com/en/apps/oxid-eshop)
OXID eShop is an extensible commerce platform for complex B2B and B2C requirements.
Planned
[](https://www.laioutr.com/en/apps/patchworks)
Laioutr
[Patchworks](https://www.laioutr.com/en/apps/patchworks)
Patchworks is a low-code iPaaS that connects ecommerce, ERP, WMS, 3PL, and marketplaces.
Planned
[](https://www.laioutr.com/en/apps/PrestaShop)
Laioutr
[Prestashop](https://www.laioutr.com/en/apps/PrestaShop)
Open-source commerce platform for small and midsize merchants in Europe and beyond.
Planned
[](https://www.laioutr.com/en/apps/saleor)
Laioutr
[Saleor](https://www.laioutr.com/en/apps/saleor)
Open-source, API-first commerce platform built on GraphQL for custom storefronts.
Planned
[](https://www.laioutr.com/en/apps/salesforce-commerce-cloud)
Laioutr
[Salesforce Commerce Cloud](https://www.laioutr.com/en/apps/salesforce-commerce-cloud)
Salesforce Commerce Cloud is a cloud-based enterprise commerce platform for businesses of any size.
Planned
[](https://www.laioutr.com/en/apps/sap-commerce-cloud)
Laioutr
[SAP Commerce Cloud](https://www.laioutr.com/en/apps/sap-commerce-cloud)
Enterprise commerce platform for complex catalogs, pricing models, and omnichannel journeys.
Planned
[](https://www.laioutr.com/en/apps/scayle)
Laioutr
[Scayle](https://www.laioutr.com/en/apps/scayle)
SCAYLE is a commerce engine that helps brands and retailers scale their business.
Planned
[](https://www.laioutr.com/en/apps/spryker)
Laioutr
[Spryker](https://www.laioutr.com/en/apps/spryker)
Composable commerce platform for sophisticated B2B and B2C business models.
[](https://www.laioutr.com/en/apps/sylius)
Laioutr
[Sylius](https://www.laioutr.com/en/apps/sylius)
Sylius is a developer-friendly ecommerce framework for B2C and B2B shopping experiences.
Planned
[](https://www.laioutr.com/en/apps/vendure)
Laioutr
[Vendure](https://www.laioutr.com/en/apps/vendure)
Vendure is a headless commerce platform for businesses with complex requirements.
Coming Soon
[](https://www.laioutr.com/en/apps/vtex)
Laioutr
[VTEX](https://www.laioutr.com/en/apps/vtex)
Cloud-native, composable commerce platform for B2B and B2C at scale.
Planned
[](https://www.laioutr.com/en/apps/websale)
Laioutr
[Websale](https://www.laioutr.com/en/apps/websale)
Stable, enterprise-ready commerce backend for complex retail environments.
Strategy call
## The frontend as a control layer
A conversation about stack, roadmap and replatforming scenario. The outcome: a clear picture of how Laioutr fits, what it costs and how fast the go-live can happen.
*"After 30 minutes, we knew Laioutr makes our replatforming feasible."*
*Daniel B., CEO,* [*hygibox.de*](https://hygibox.de)
[Book a demo](https://www.laioutr.com/en/contact)
## Structured Data
```json
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://www.laioutr.com/#identity",
"name": "Laioutr",
"legalName": "Laioutr GmbH",
"url": "https://www.laioutr.com/",
"logo": {
"@type": "ImageObject",
"url": "https://www.laioutr.com/laioutr-logo.png",
"width": 400,
"height": 400
},
"email": "info@laioutr.com",
"telephone": "+49 30 75435715",
"address": {
"@type": "PostalAddress",
"streetAddress": "Münchweilersteig 5",
"postalCode": "12559",
"addressLocality": "Berlin",
"addressCountry": "DE"
},
"vatID": "DE450905846",
"sameAs": [
"https://www.linkedin.com/company/laioutr",
"https://www.youtube.com/@Laioutr",
"https://x.com/laioutr"
]
},
{
"@type": "WebSite",
"@id": "https://www.laioutr.com/en/#website",
"url": "https://www.laioutr.com/en/",
"name": "Laioutr",
"inLanguage": "en",
"publisher": {
"@id": "https://www.laioutr.com/#identity"
}
},
{
"@type": "BlogPosting",
"@id": "https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck#article",
"headline": "OroCommerce Frontend: Out of the Twig and Layouts Bottleneck",
"description": "OroCommerce storefront theming runs on YAML layout updates, Twig block themes and SCSS builds. How B2B teams keep Oro logic and let marketers edit visually.",
"image": [
"https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvaiaokow8v906leia28cwal"
],
"datePublished": "2026-10-16T18:06:51.136271+00:00",
"dateModified": "2026-10-16T18:06:33.505621+00:00",
"inLanguage": "en",
"articleSection": "Insights",
"keywords": "Composable, Visual Editing, Frontend Engineering, OroCommerce",
"author": {
"@id": "https://www.laioutr.com/#identity"
},
"publisher": {
"@id": "https://www.laioutr.com/#identity"
},
"mainEntityOfPage": {
"@id": "https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck#webpage"
},
"isPartOf": {
"@id": "https://www.laioutr.com/en/#website"
}
},
{
"@type": "WebPage",
"@id": "https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck#webpage",
"url": "https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck",
"name": "OroCommerce Frontend: Out of the Twig and Layouts Bottleneck",
"description": "OroCommerce storefront theming runs on YAML layout updates, Twig block themes and SCSS builds. How B2B teams keep Oro logic and let marketers edit visually.",
"inLanguage": "en",
"isPartOf": {
"@id": "https://www.laioutr.com/en/#website"
},
"breadcrumb": {
"@id": "https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck#breadcrumb"
},
"primaryImageOfPage": {
"@type": "ImageObject",
"url": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmvaiaokow8v906leia28cwal"
},
"datePublished": "2026-10-16T18:06:51.136271+00:00",
"dateModified": "2026-10-16T18:06:33.505621+00:00",
"mainEntity": {
"@id": "https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck#article"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://www.laioutr.com/en/blog/orocommerce-frontend-twig-layouts-bottleneck#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Laioutr",
"item": "https://www.laioutr.com/en/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Insights",
"item": "https://www.laioutr.com/en/blogs/insights"
},
{
"@type": "ListItem",
"position": 3,
"name": "OroCommerce Frontend: Out of the Twig and Layouts Bottleneck"
}
]
}
]
}
```