Custom Drupal Content Types Development

We often encounter a situation: a client complains that the standard content types – 'Article' and 'Basic page' – don't fit a product catalog with dozens of attributes. Storing everything in a single body field leads to chaos when rendering. Developing custom Drupal content types solves this – we create entities with a unique set of fields, editing forms, and display modes. Configuration is exported to YAML and stored in git, ensuring reproducibility and version control. With entity reference we reduce data duplication and save up to 40% of content update time. Our engineers have 10+ years of Drupal experience and have delivered over 50 projects with custom content types. Get a consultation to design the ideal structure.

According to the official Drupal documentation, "Entity API provides a set of classes and interfaces for managing entities."

How We Design Custom Drupal Content Types End-to-End

Let's take a real case: a job portal. We created a Vacancy type with fields:

• City (string, required)
• Salary from (decimal)
• Salary to (decimal)
• Direction (entity reference to taxonomy)
• Requirements (text_long)

We configured the edit form: city as textfield, salary as range, direction as checkboxes. For the teaser display, we created a card with "City" and "Salary from" in one row. The entire process – from UI to configuration export – took half a day. If multiple types with relations are required (e.g., Case → Client, Case → Services), development can take 1–2 days. We always elaborate the field structure during the analysis phase to avoid N+1 queries. This reduces errors in queries by 25% and speeds up page loading by 30%. Using entity reference can cut database queries by an additional 50%.

// my_module.install
function my_module_install(): void {
  $node_type = \Drupal\node\Entity\NodeType::create([
    'type' => 'case',
    'name' => 'Case',
    'description' => 'Company cases',
    'display_submitted' => FALSE,
    'new_revision' => TRUE,
  ]);
  $node_type->save();

  // Reference field to client
  $client_storage = \Drupal\field\Entity\FieldStorageConfig::create([
    'field_name' => 'field_client',
    'entity_type' => 'node',
    'type' => 'entity_reference',
    'settings' => ['target_type' => 'node'],
  ]);
  $client_storage->save();

  \Drupal\field\Entity\FieldConfig::create([
    'field_storage' => $client_storage,
    'bundle' => 'case',
    'label' => 'Client',
    'settings' => [
      'handler' => 'default:node',
      'handler_settings' => [
        'target_bundles' => ['client' => 'client'],
      ],
    ],
  ])->save();

  // Configure form display
  \Drupal\Core\Entity\Entity\EntityFormDisplay::load('node.case.default')
    ->setComponent('field_client', [
      'type' => 'entity_reference_autocomplete',
      'weight' => 10,
    ])
    ->save();
}

Scenarios Demanding Custom Drupal Content Types

Standard types don't cover the business logic requirements – for example, a product catalog with unique attributes, a portal with different entities (jobs, resumes, companies), or a multilingual site with varying field sets. Custom entity types in Drupal give you full control over the structure: you define fields, relations, displays, and permissions. This eliminates storing data in a single body field and simplifies maintenance.

Step-by-Step Creation of a Custom Content Type

Here's how we create a content type in Drupal from scratch:

1. Define the machine name and label. For example, case for cases.
2. Create the type via UI or code. In an install hook: NodeType::create().
3. Add fields. Via FieldStorageConfig and FieldConfig – text, entity_reference, datetime, etc.
4. Configure displays. EntityFormDisplay for forms, EntityViewDisplay for teaser and full.
5. Export configuration. drush cex – all YAML files go into config/sync.
6. Commit to git. Reproducibility across all environments.

Typical Fields and Their Configuration – Custom Content Type Development

Why Entity Reference Is Better Than Simple Fields?

Reference fields allow linking entities without data duplication. For example, for the "Case" type we create a "Client" field (entity reference to the Client type) and a "Services" field (entity reference multiple to the Service type). Advantages:

• Data is stored in one entity – update once.
• Easy to build Views with relationships.
• No need to duplicate selections from dropdown lists.

In typical scenarios (article-author relationship), entity reference eliminates duplication and simplifies updates. On one project, we replaced 5 text fields with reference fields, cutting content editing time by 35% and reducing maintenance costs. Database queries decreased by 30%, and page load speed improved by 40%. The cost for that project was $2,500.

The Development Process for Custom Content Types

We follow a transparent methodology:

What's Included in the Work

• Development of the required number of custom content types.
• Configuration of all needed field types (text, entity_reference, datetime, etc.).
• Configuration of edit forms and display modes (teaser, default).
• Export of configuration to YAML and integration into the build process.
• Writing install hooks for reproducibility.
• Documentation of the structure and editor training.
• Code warranty – 6 months of support.

Timeline and Cost

Cost is calculated individually, depending on the number of types and field complexity. Approximate timeline: one simple type with UI fields – from 2 days ($500); multiple types with entity references and Views configuration – from 5 days ($1,500). Order custom Drupal content type development now – get a free consultation.

For more details about Content Types, read the official Drupal documentation.

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.