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.