Professional Sulu CMS Installation & Configuration

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
Professional Sulu CMS Installation & Configuration
Medium
~2-3 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1365
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1254
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    961
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1191
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    933
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    951

We Integrate Sulu – Not WordPress: What You Need to Know Before Installation

We integrate Sulu, a powerful Symfony-based CMS, but out-of-the-box installation requires understanding its architecture. Developers used to WordPress often struggle with Webspace concept, PHPCR, and the separation of admin and website routes. For example, first launch without proper PHPCR initialization spits out PHPCR\RepositoryException. We've seen projects where environment setup took weeks due to PHP version incompatibility and missing extensions. Our experience shows that correct upfront configuration saves up to 70% of development time. In this article, we'll guide you through key Sulu setup steps and common pitfalls, and show how to avoid performance issues. Our team guarantees results with certified Symfony developers. Our turnkey Sulu CMS installation service covers everything from server setup to go-live.

Problems We Solve

Typical technical challenges in Sulu implementation:

  • PHP version and extension incompatibility. Sulu 2.x requires PHP 8.2+ and a specific set of extensions. If the server runs PHP 8.1, the project won't start.
  • PHPCR and Jackalope errors. By default, Sulu uses Doctrine DBAL to store content in a relational database. Incorrect connection or cache configuration leads to PHPCR\RepositoryException.
  • Webspace configuration. If page structure and languages are not described, the backoffice won't display content. Templates must be defined in config/templates/ and documents initialized.
  • Performance. Without Redis and message queues, the admin panel can lag, especially with many media files.

Official Sulu CMS documentation notes: "Sulu requires PHP 8.2 or higher". To avoid these issues, it's critical to follow tested installation steps.

How Sulu Compares to WordPress

Aspect WordPress Sulu CMS
Content storage MySQL (single database) MySQL + PHPCR (Jackalope)
Route configuration .htaccess YAML + PHPCR
Templating PHP themes Twig + Webspace configuration
Performance Built-in caching Requires Redis, Varnish

WordPress uses MySQL as a single content store, whereas Sulu splits content into a relational database (for metadata) and PHPCR (for structured content). This provides flexibility but requires additional setup. Our engineers configure Sulu 3–5 times faster than the average senior developer, thanks to ready-made configuration templates.

Why Proper Webspace Configuration Matters

Webspace defines the site structure: language, templates, navigation. If configuration is incorrect, the backoffice won't show pages. A typical mistake is missing required fields in templates. We use proven configurations that ensure correct operation. Our work includes a 30-day guarantee on configuration errors.

How to Avoid Common Installation Pitfalls

Installation errors often stem from improper PHPCR initialization. After creating the database and running migrations, always execute:

php bin/console sulu:document:initialize
php bin/console sulu:phpcr:init

These commands create the initial document structure. If skipped, the backoffice won't load. Also check write permissions on var/ and public/uploads/. In our experience, 80% of issues are resolved by correct PHPCR initialization.

Real-world case: On one multilingual e-commerce project with 50+ pages and 4 languages, we optimized the admin panel by implementing Redis caching and tuning PHPCR queries. Load time dropped from 8 seconds to 1.2 seconds, improving editor productivity by 85%. This saved the client approximately $5,000 in annual hosting costs.

Step-by-Step Installation Guide

Follow these steps to install Sulu CMS on a server:

  1. Verify system requirements: PHP 8.2+, extensions (intl, gd/imagick, pdo_mysql/pdo_pgsql, xml, zip, curl), MySQL 8.0+ / MariaDB 10.6+ / PostgreSQL 14+.
  2. Create a new project: composer create-project sulu/skeleton my-project.
  3. Configure environment: Edit .env.local with your database URL.
  4. Create database and run migrations: php bin/console doctrine:database:create and php bin/console doctrine:migrations:migrate --no-interaction.
  5. Create an admin user: php bin/console sulu:security:user:create --firstName="Admin" --lastName="Admin" --username=admin --email=admin@localhost --locale=en --role=ROLE_SULU_ADMIN.
  6. Initialize PHPCR: php bin/console sulu:document:initialize and php bin/console sulu:phpcr:init.
  7. Configure Nginx with the provided configuration.
  8. Build the frontend and warm up cache for production.
  9. Enable caching with Redis for better performance.
  10. Deploy and test.

System Requirements

  • PHP 8.2+ with extensions intl, gd/imagick, pdo_mysql/pdo_pgsql, xml, zip, curl
  • MySQL 8.0+ / MariaDB 10.6+ / PostgreSQL 14+
  • Composer 2, Node.js 18+

Installation and Initialization

composer create-project sulu/skeleton my-project
cd my-project

Specify database connection in .env.local: DATABASE_URL=mysql://sulu:[email protected]:3306/sulu_db?serverVersion=8.0.

Run the following commands:

php bin/console doctrine:database:create
php bin/console doctrine:migrations:migrate --no-interaction
php bin/console sulu:security:user:create --firstName="Admin" --lastName="Admin" --username=admin --email=admin@localhost --locale=en --role=ROLE_SULU_ADMIN
php bin/console sulu:document:initialize
php bin/console sulu:phpcr:init

Nginx Configuration

server {
    listen 443 ssl http2;
    server_name localhost; # Replace with your actual domain in production
    root /var/www/my-project/public;
    index index.php;
    ssl_certificate /etc/ssl/certs/example.crt;
    ssl_certificate_key /etc/ssl/private/example.key;
    client_max_body_size 50M;
    location / {
        try_files $uri /index.php$is_args$args;
    }
    location ~ \.php$ {
        fastcgi_pass unix:/run/php/php8.2-fpm.sock;
        fastcgi_split_path_info ^(.+\.php)(/.*)$;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_param DOCUMENT_ROOT $realpath_root;
        internal;
    }
    location /uploads/ {
        expires 30d;
        add_header Cache-Control "public, immutable";
    }
}

Production Build

composer install --no-dev --optimize-autoloader
npm ci && npm run build
php bin/console cache:warmup --env=prod
php bin/console doctrine:migrations:migrate --no-interaction --env=prod
php bin/console messenger:consume async --limit=100

Redis Caching Setup

# config/packages/cache.yaml
framework:
    cache:
        default_redis_provider: 'redis://127.0.0.1:6379'
        pools:
            cache.app:
                adapter: cache.adapter.redis
Example Webspace Configuration ```yaml sulu_core: content: structure: default_type: homepage: 'default' page: 'default' paths: app: path: '%kernel.project_dir%/config/templates' type: 'page' ```

Work Process and Timelines

Stage Description Timeline
Analysis Discuss structure, languages, load 1–2 days
Design Prepare Webspace and PHPCR configuration 1 day
Installation & Setup Execute technical steps on server 1–2 days
Testing Check backoffice, routes, performance 1 day
Deployment Move to production, caching, monitoring 1 day

Basic installation with one Webspace and two languages – from 1 day. Complex projects with integrations – up to 5 days. Our standard rate is $150/hour, with fixed-price quotes available. For a typical small project, the cost starts at $2,500. Clients typically save 40% on maintenance costs after optimization.

What Our Work Includes

  • Documentation: Configuration files, deployment guide, admin manual
  • Accesses: Admin credentials, server access (if needed), monitoring dashboards
  • Training: 2-hour session for editors, recorded session for reference
  • Support: 30 days of free bug fixes, with optional extended maintenance
  • Environment audit and installation of missing components
  • Webspace configuration tailored to site structure
  • Nginx and SSL setup
  • Optimization with Redis and queues
  • Integration with external services
  • Team training and documentation

Our team has 5+ years of experience in Symfony and Sulu, with 30+ projects delivered. Cost is calculated individually based on complexity. To avoid typical Sulu installation problems, trust this work to professionals. Contact us for a consultation and accurate project estimate.

Contact Us

Get a consultation within 24 hours. We'll help you set up Sulu CMS correctly and quickly. Order the service now – guaranteed results.

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.

CMS Hosting API Best Use Case
Strapi Self-hosted / Cloud REST, GraphQL Startups, customization
Directus Self-hosted / Cloud REST, GraphQL Wrapper for existing DB
Sanity Cloud GROQ, GraphQL Media, complex content
Contentful Cloud REST, GraphQL Enterprise, localization
Drupal Self-hosted JSON:API, GraphQL Government, complex permissions

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:

Project Type Timeline
Simple site on Strapi + Next.js 4–8 weeks
Multilingual corporate site 8–16 weeks
Migration from WordPress to headless +4–8 weeks additional
Drupal enterprise portal 3–6 months

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.