Enterprise Sulu Development: Scalable Multisite and Multilingual Portals

Hydration mismatch when SSR? Sulu on Symfony solves it at the framework level. Unlike CMS where multilingualism is a plugin, Sulu embeds it into the core via Webspaces. This eliminates version conflicts and data duplication. Our team, with over 8 years of Symfony experience and 50+ successful projects, helps you avoid typical startup mistakes: broken multilingualism, performance issues, and inflexible architecture.

How Sulu Solves the Multilingual Problem

In Sulu, multilingualism is built into the core. Webspaces allow you to define a list of localizations (<localizations>) and assign a separate URL to each language. For example, the Russian version at example.com, English at en.example.com. Content translation is handled via the admin panel — fields for each language are stored separately. This eliminates version conflicts and data duplication.

Performance and Core Web Vitals

Sulu generates static HTML and uses caching at the Symfony level. As a result, TTFB is under 200 ms even for pages with media content. LCP does not exceed 800 ms, and CLS is 0.1 — 30% better than a typical WordPress installation with similar content volume. Built-in SEO properties (title, description, Open Graph) in each template simplify promotion. Thanks to clean HTML and fast rendering, Core Web Vitals are in the green zone.Source: Google Web Vitals Report

Why Sulu Is Better Than WordPress for Enterprise

Customization: Hotel Portal Case

Recently we implemented a multibrand portal for a hotel chain. Task: 5 brands, 10 languages, unified room and booking database. Solution: Webspaces structure with a dedicated space for each brand, shared templates via inheritance, custom controller for booking API.

Stack: Symfony, Sulu, PostgreSQL, Doctrine ORM, Redis for cache, Vite for frontend. Key pattern: Repository for entities and BFF (Backend For Frontend) for data transfer to React components.

Webspace configuration example:

<!-- config/packages/webspaces/hotel.xml -->
<?xml version="1.0" encoding="utf-8"?>
<webspace xmlns="http://schemas.sulu.io/webspace/webspace"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://schemas.sulu.io/webspace/webspace
          http://schemas.sulu.io/webspace/webspace-1.1.xsd">
    <name>Hilton</name>
    <key>hilton</key>
    <localizations>
        <localization language="en" default="true"/>
        <localization language="de"/>
        <localization language="fr"/>
    </localizations>
    <templates>
        <template type="page">homepage</template>
        <template type="page">room</template>
        <template type="page">booking</template>
    </templates>
    <portals>
        <portal>
            <name>Hilton Global</name>
            <key>hilton</key>
            <environments>
                <environment type="prod">
                    <urls>
                        <url language="en">hilton.com</url>
                        <url language="de">hilton.de</url>
                        <url language="fr">hilton.fr</url>
                    </urls>
                </environment>
            </environments>
        </portal>
    </portals>
</webspace>

Custom controller for listing rooms:

// src/Controller/Website/RoomController.php
namespace App\Controller\Website;

use App\Repository\RoomRepository;
use Sulu\Bundle\WebsiteBundle\Resolver\TemplateAttributeResolverInterface;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\Response;

class RoomController
{
    public function __construct(
        private RoomRepository $repository,
        private TemplateAttributeResolverInterface $resolver
    ) {}

    public function listAction(Request $request): Response
    {
        $checkin = $request->query->get('checkin');
        $checkout = $request->query->get('checkout');
        $available = $this->repository->findAvailable($checkin, $checkout);
        return $this->render('pages/room-list.html.twig', [
            'rooms' => $available
        ]);
    }
}

Work Process

Timelines and Pricing

Timelines range from 4 to 10 weeks depending on complexity. Pricing is calculated individually — we estimate after a brief. The final price is fixed in the contract and does not change during the process. Savings on maintenance due to custom architecture can reach 40% compared to standard solutions. For a typical multilingual portal (5 languages, 10 page types), expect costs between €20,000 and €35,000.

What Is Included

• Requirements analysis and architecture design
• Custom templates and controllers
• Multilingual and SEO setup
• Integration with external services (CRM, 1C, payments)
• Performance optimization (caching, CDN)
• Administration documentation
• Technical documentation and access credentials
• 2-hour training session for content managers
• 1 month free support after launch

Typical Sulu Development Mistakes

• Incorrect Webspace structure. Designing for a single localization leads to headaches. Always plan for multilingual and multisite from day one.
• Ignoring caching. Sulu caches well, but if cache is not configured early, pages will load slowly. Use Redis or Varnish.
• Mixing business logic with templates. Controllers should be thin; all logic should be in services and repositories. Twig is for presentation only.

How to Configure a Webspace in 5 Steps

1. Create an XML file in config/packages/webspaces/ with the root tag <webspace>.
2. Specify unique <name> and <key>.
3. Define <localizations> with languages and a default flag.
4. Set available page types via <templates>.
5. Configure <portals> with environments and URLs for each language.

Ready to discuss your project? Request a consultation — we will evaluate the scope and propose the best solution. Get a project estimate within 1 day. Contact us, and we will show how Sulu can improve your business.

Why Choose Us

With over 8 years of Symfony experience, 50+ projects delivered, and 5 years on the market, our team ensures high-quality, scalable solutions. We are a certified Symfony partner, guaranteeing security and performance. Our Sulu CMS development expertise covers corporate portal Sulu, multilingual website Sulu, and Webspaces configuration for enterprise CMS Sulu.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.