INTEREST JOURNAL DRUPAL & WEB

Drupal Guide: Chapter 6. Setting Up Content Structure

About 2,000 words 10 min read

Japanese ↗
On this page

Scope: a summary of the official published HTML reviewed on November 4, 2026. The guide landing page ↗ identifies Drupal 11, while the official project ↗ reports broken web publishing. An initial screening against the collected corpus covers all 102 topics, with 43 annotations on 36 topics. See scope and chapter status . Applicability of every procedure on a running site has not been verified.

Chapter overview

Build types, fields, taxonomy and references, then configure input and presentation independently.

Official chapter contents ↗

The introductory guide uses a shared farmers-market scenario. The summaries explain concepts and task flow rather than reproducing every screen or command.

Release comparison status

Initial screening covers 16 topics in this chapter, with 7 selected annotations.

Article, Field UI/Link, image schemes and text formats; taxonomy/reference/display procedures have not been reproduced.

A topic without an annotation means no individual note was selected within this corpus, not a guarantee of unchanged behavior, safety or compatibility. Fix versions identify historical fixes, not pinned update targets. Beta information is not a production recommendation.

Jump to annotations:

Scope and status for all chapters

Detailed topic pages

Sixteen bilingual detailed pages were prepared on November 6, 2026, distinguishing source adaptations from our additions. Procedures have not been tested in Drupal.

Topic Detailed page
6.1 Adding a Content Type
6.2 Deleting a Content Type
6.3 Adding Basic Fields to a Content Type
6.4 Understanding Reference Fields
6.5 Understanding Taxonomy
6.6 Setting Up a Taxonomy
6.7 Adding a Vendor Reference
6.8 Understanding Forms and Widgets
6.9 Changing Content Entry Forms
6.10 Understanding View Modes and Formatters
6.11 Changing Content Display
6.12 Understanding Image Styles
6.13 Setting Up an Image Style
6.14 Understanding Responsive Image Styles
6.15 Understanding Text Formats, Editors and XSS
6.16 Configuring Text Formats and Editors

6.1. Adding a Content Type

Detailed page: guidance, checks and update notes

Uses vendor profiles to introduce content-type configuration, defining a reusable structure and submission behavior rather than entering one item’s data.

Official source: 6.1. Adding a Content Type ↗

Read first: 2.3. Concept: Content Entities and Fields

6.2. Deleting a Content Type

Detailed page: guidance, checks and update notes

Illustrates removing an unneeded Article type. Deleting a structural type is broader than deleting one content item and requires reviewing existing content and dependencies.

Official source: 6.2. Deleting a Content Type ↗

Change annotation:New sites without Article

Scope: 11.4.0 / stable

On new 11.4 Standard sites, Article is absent by default. Skip this exercise if the type does not exist; do not delete a different populated type as a substitute.

Sources: Standard profile content types ↗

Reviewed 2026-11-04 against official sources. No live Drupal test was performed.

Read first: 4.1. Concept: Administrative Overview

6.3. Adding Basic Fields to a Content Type

Detailed page: guidance, checks and update notes

Adds URL and image fields to vendor content, introducing field types, labels, storage and input settings, with the option to reuse existing fields.

Official source: 6.3. Adding Basic Fields to a Content Type ↗

Change annotation:Field UI and Link security fixes

Scope: SA-CORE-2026-014, 015 / fixes: 11.4.10, 11.3.19, 10.6.19

October fixes cover Field UI and Link. Field UI RCE requires contributed/custom-code exploit paths rather than core alone; Link has a separate XSS issue. This does not mean adding a field alone triggers an exploit. Check the advisory against the actual version and extensions.

Sources: SA-CORE-2026-014 ↗ · SA-CORE-2026-015 ↗

Weekly release summaries: 2026-10-12

Reviewed 2026-11-04 against official sources. No live Drupal test was performed.

Read first: 2.3. Concept: Content Entities and Fields

6.4. Concept: Reference Fields

Detailed page: guidance, checks and update notes

Reference fields store relationships to other entities, including content, users and taxonomy terms, allowing connected information without duplicating the referenced record.

Official source: 6.4. Concept: Reference Fields ↗

Read first: 2.3. Concept: Content Entities and Fields

6.5. Concept: Taxonomy

Detailed page: guidance, checks and update notes

Explains terms, vocabularies and flat or hierarchical classification, with taxonomy references connecting classifications to content and other entities.

Official source: 6.5. Concept: Taxonomy ↗

Read first: 2.3. Concept: Content Entities and Fields · 6.4. Concept: Reference Fields

6.6. Setting Up a Taxonomy

Detailed page: guidance, checks and update notes

Creates an ingredient vocabulary and attaches it to recipes, demonstrating multiple values and an input pattern that can create new terms.

Official source: 6.6. Setting Up a Taxonomy ↗

Read first: 2.3. Concept: Content Entities and Fields · 6.5. Concept: Taxonomy · 6.3. Adding Basic Fields to a Content Type

6.7. Adding a Reference Field

Detailed page: guidance, checks and update notes

Adds a recipe-to-vendor reference, selecting an entity target and input configuration so individual records can be connected.

Official source: 6.7. Adding a Reference Field ↗

Read first: 6.3. Adding Basic Fields to a Content Type · 6.4. Concept: Reference Fields · 6.1. Adding a Content Type

6.8. Concept: Forms and Widgets

Detailed page: guidance, checks and update notes

Separates stored field data from its input widget, showing how controls, ordering and visibility shape the editing form.

Official source: 6.8. Concept: Forms and Widgets ↗

Read first: 2.3. Concept: Content Entities and Fields

6.9. Changing Content Entry Forms

Detailed page: guidance, checks and update notes

Changes the recipe ingredient widget to a tag-style autocomplete, improving the form without redefining the underlying stored field.

Official source: 6.9. Changing Content Entry Forms ↗

Read first: 6.1. Adding a Content Type · 6.3. Adding Basic Fields to a Content Type · 6.5. Concept: Taxonomy · 6.8. Concept: Forms and Widgets

6.10. Concept: View Modes and Formatters

Detailed page: guidance, checks and update notes

View modes represent display contexts such as full content or teasers; formatters control field output and are distinct from input widgets.

Official source: 6.10. Concept: View Modes and Formatters ↗

Read first: 6.1. Adding a Content Type

6.11. Changing Content Display

Detailed page: guidance, checks and update notes

Adjusts field order, label visibility and output formatting through display configuration, changing presentation rather than the stored content values.

Official source: 6.11. Changing Content Display ↗

Read first: 2.3. Concept: Content Entities and Fields · 6.10. Concept: View Modes and Formatters

6.12. Concept: Image Styles

Detailed page: guidance, checks and update notes

Image styles apply effects to generate display derivatives from an original image, allowing different presentations without separately uploading each variant.

Official source: 6.12. Concept: Image Styles ↗

Change annotation:Image derivatives on custom file schemes

Scope: SA-CORE-2026-010 / fixes: 11.4.4, 11.3.14, 10.6.13

Access checks were hardened for private image derivatives served through non-core file schemes. This does not classify every image style as a disclosure. Sites using custom stream wrappers should review the extension’s hardening as well as the core update.

Sources: SA-CORE-2026-010 ↗

Weekly release summaries: 2026-07-13

Reviewed 2026-11-04 against official sources. No live Drupal test was performed.

Read first: 6.3. Adding Basic Fields to a Content Type

6.13. Setting Up an Image Style

Detailed page: guidance, checks and update notes

Creates a style with selected image effects and then applies it to an image field’s formatter; defining a style and using it are separate steps.

Official source: 6.13. Setting Up an Image Style ↗

Read first: 6.3. Adding Basic Fields to a Content Type · 6.11. Changing Content Display · 6.12. Concept: Image Styles

6.14. Concept: Responsive Image Styles

Detailed page: guidance, checks and update notes

Maps image styles to responsive breakpoints so suitable image variants can be delivered for different screen sizes and display conditions.

Official source: 6.14. Concept: Responsive Image Styles ↗

Read first: 1.3. Concept: Themes · 6.11. Changing Content Display · 6.12. Concept: Image Styles

6.15. Concept: Text Formats and Editors

Detailed page: guidance, checks and update notes

Distinguishes output filtering from editing tools, linking allowed markup and text-format permissions with cross-site scripting risks.

Official source: 6.15. Concept: Text Formats and Editors ↗

Change annotation:HTMX attribute filtering

Scope: SA-CORE-2026-011 / fixes: 11.4.4, 11.3.14; 10.6.13 hardening

The HTMX XSS fix concerns input containing particular HTML attributes. Drupal 10 core is unaffected; its 10.6 change hardens certain contributed uses. Text-format permissions do not replace checking applicability and installing the relevant update.

Sources: SA-CORE-2026-011 ↗

Weekly release summaries: 2026-07-13

Reviewed 2026-11-04 against official sources. No live Drupal test was performed.

Change annotation:Optional HTML filter conditions and settings

Scope: SA-CONTRIB-2026-309, 314, 315 / optional extensions

Review 309 for Extended HTML Filter and 314/315 for htmLawed. The SQLite/older-library condition belongs to 314, not every issue. Advisory 315 also requires reviewing deny_attribute for data-hx-* in affected text formats after updating. Do not apply these extension-specific conditions universally to core-only filters.

Sources: SA-CONTRIB-2026-309 ↗ · SA-CONTRIB-2026-314 ↗ · SA-CONTRIB-2026-315 ↗

Reviewed 2026-11-05 against official sources. No live Drupal test was performed.

6.16. Configuring Text Formats and Editors

Detailed page: guidance, checks and update notes

Uses a horizontal-rule example to connect editor toolbar configuration with the markup permitted by its associated text format.

Official source: 6.16. Configuring Text Formats and Editors ↗

Change annotation:Editor and extra plugins

Scope: SA-CORE-2026-013 / fixes: 11.4.7, 11.3.17, 10.6.17

The September CKEditor XSS advisory can affect sites even when the attacker can edit content without using CKEditor. Alongside core updates, review extra plugins not bundled with core as directed by the advisory.

Sources: SA-CORE-2026-013 ↗

Weekly release summaries: 2026-09-14

Reviewed 2026-11-04 against official sources. No live Drupal test was performed.

Change annotation:Contributed editor preview endpoint

Scope: SA-CONTRIB-2026-299 / Highlight Js

Sites using Highlight Js should review its CKEditor 5 preview-endpoint reflected-XSS fix, released in 1.3.1. This concerns the contributed module; the guide’s ordinary editor-button exercise alone does not establish exposure.

Sources: SA-CONTRIB-2026-299 ↗

Reviewed 2026-11-05 against official sources. No live Drupal test was performed.

Read first: 6.15. Concept: Text Formats and Editors

Sources and attribution

The source is the Drupal User Guide, copyright its individual contributors; its copyright page ↗ states © 2015–2025. This text is an abridged, reorganized adaptation, not an official edition or an indication of endorsement. The adapted text is shared under the same CC BY-SA 2.0 ; this notice applies to that text rather than the site design or unrelated articles. See official A.1 ↗ for guide-wide credits.

The following links preserve credited people, organizations and source works from each topic’s Attributions. The official page records their specific writing, editing or adaptation roles.

The reviewed topic pages show an April 14, 2025 update timestamp; the review date here is November 4, 2026. Source text, attribution and timestamps were retained for later comparison.

Drupal Guide · Topic index · Glossary reference index

Drupal Guide ↗