Content Worksheets

Export an XLSX workbook that documents your content model and provides a structured template for migration planning, content audits, and stakeholder handoff.

What is a content worksheet?

A content worksheet is an XLSX spreadsheet generated from your Strata project. It contains one pair of sheets for each fieldable bundle in your content architecture — a field mapping sheet that documents every field and its configuration, and a content data sheet with column headers matching the field machine names and blank rows ready for content entry.

The workbook also includes an Instructions sheet explaining how to use it and a Reference sheet listing all field types, widgets, and formatters available in your project's registry.

Content worksheets cover all fieldable bundle types: content types, media types, taxonomy vocabularies, block types, paragraph types, and SDCs (Single Directory Components).

How to export a worksheet

Navigate to the Export & Import page in your project. The Content Worksheet card appears below the standard XLSX and JSON manifest export options.

Click Select bundles & download to open the bundle selection dialog.
Choose which bundles to include (all are selected by default).
Click Download worksheet to generate and download the XLSX file.

The downloaded file is named {project-slug}-content-worksheet-{date}.xlsx. Content worksheet export uses the standard export permission — any member, admin, or owner can export. There is no additional plan gate.

Bundle selection

The bundle selection dialog lists every fieldable bundle in your project, grouped across all bundle tab types. You can select or deselect individual bundles, or use the Select all / Deselect all controls to toggle everything at once.

Only bundles that have at least one field are included in the list. If your project has no bundles with fields, the worksheet card shows a message instead of the download button.

Each selected bundle produces two sheets in the workbook, so choosing a subset keeps the spreadsheet focused on the content types that matter for your current task.

Worksheet structure

The generated workbook contains the following sheets, in order:

Instructions sheet

The first sheet in the workbook. It explains the purpose of the worksheet, describes the different sheet types, and notes when the workbook was generated. This is the sheet your content editors or migration developers see first when they open the file.

Field mapping sheets (one per bundle)

Named {Bundle Label} — Fields. Each row represents a field belonging to that bundle. The columns are split into two groups:

Planning columns (you fill these in)

Source Field	The field name or column from the source system that maps to this destination field
Migration Notes	Free-text notes for transformation logic, edge cases, or content that needs review

Destination field columns (pre-populated from Strata)

Field Label	Human-readable field name
Machine Name	Drupal machine name (e.g. field_summary)
Field Type	Field type from the registry (e.g. text_with_summary, entity_reference)
Widget	Form widget assigned to this field
Required	Whether the field is required (Yes / No)
Cardinality	Number of allowed values (1, 2, ... or Unlimited)
Description	Field help text or description
Allowed Values	For list fields: option labels. For entity references: target type and bundles
Default Value	The field's default value, if configured

Planning columns appear on the left with a blue header highlight, so the workflow reads left-to-right: “what is the source?” then “what is the destination?” then “any notes?”

For content type bundles, base fields (title, status, created, changed, uid, path) appear as greyed-out rows at the top of the sheet before the custom fields.

Content data sheets (one per bundle)

Named {Bundle Label} — Content. Column headers are field machine names. For content types, base field columns appear first. The sheet contains 100 blank rows ready for manual content entry or pasting from an external data source.

Fields with constrained values (list fields, booleans) get dropdown validation applied to the blank rows, so content editors see the allowed options when clicking a cell.

Reference sheet

The last sheet in the workbook. It lists all field types, widgets, and formatters from your project's registry, along with compatibility mappings. This gives anyone working in the spreadsheet a quick lookup without leaving the file.

Data validation and dropdowns

The worksheet applies Excel data validation to several columns, giving users dropdown menus for constrained values:

Field Type — dropdown of all field type machine names from the project's resolved registry
Widget — dropdown of all available widgets
Required — Yes / No
Cardinality — 1 through 5, plus Unlimited

Validation extends 50 rows below the populated data, so if you add new field rows to the sheet they still get dropdown support. On content data sheets, validation covers all 100 blank rows.

Formatting and navigation

The worksheet follows Strata's XLSX conventions:

Header row — bold text with a light grey background and auto-filters enabled on every column
Planning columns — light blue header fill to visually distinguish “fill this in” columns from pre-populated reference data
Frozen panes — the header row and the first two columns are frozen, so field names stay visible while scrolling through wide sheets
Base field rows — greyed-out background with italic styling to distinguish them from custom fields

Use cases

Migration planning

The primary use case. Export the worksheet, fill in the Source Field and Migration Notes columns to document how each destination field maps to the source system. This becomes the reference document for the migration developer writing process plugins and migration YAML.

Content editor handoff

Share the content data sheets with content editors who need to prepare content for the new site. Each sheet has the right columns, correct machine names, and dropdown validation for constrained fields. Editors fill in content row by row without needing access to Strata or the Drupal admin UI.

Content audits

Use the field mapping sheets to audit and document an existing content model. The pre-populated columns give you a complete picture of every field's type, cardinality, and constraints. The planning columns provide space to note issues, gaps, or changes needed.

Stakeholder review

The worksheet is a self-contained XLSX file that anyone can open in Excel or Google Sheets. Share it with project managers, clients, or other stakeholders who need to review the content model without logging into Strata.