You add a blog on a development site, export configuration, and deploy it. The new content type appears on production, but its articles are missing. This is a common source of confusion: the structure of a website and the material inside that structure have different deployment needs.
Think of structure and entries separately
Drupal’s configuration management documentation describes settings such as content types, fields, vocabularies, and Views as configuration. Articles and other content entities need their own content-transfer or editorial workflow.
For a blog, the category vocabulary is structure; a particular category term is an entry in that structure. An image field is structure; an uploaded image includes a file entity and a binary file. This distinction helps explain why a configuration archive is not a complete site backup.
Write a deployment inventory
Before a release, list what changed. An example inventory might include a new field, an updated listing, three starter articles, two images, and a navigation link. Give each item a transfer method and an owner. That small document can prevent a technically successful deployment from producing an empty page.
Protect production editorial work
We recommend avoiding a development database replacement as a routine way to ship articles. A development copy may be missing submissions, accounts, and editorial changes that arrived later on production. For starter material, a repeatable importer with stable identifiers can create missing entries while preserving existing edits.
Review configuration differences too. A settings change made directly on production can be overwritten if the next import contains an older value. Agree how urgent production changes are brought back into the development workflow.
Check the result as an editor
After deployment, open the content listing, edit a representative entry, and view the public page. Confirm that images resolve and references point to the intended content. These checks validate the relationship between configuration and content, which a successful import message cannot fully demonstrate.
For a maintainable content model and deployment process, see our web development and consulting services.