This project is inspired by the Devel issue Let's generate kick-ass demo content!, and aims to make it possible to use Devel's devel_generate to generate more realistic demo content.


Enable this module and Devel's devel_generate. You will now see portraits used for profile pictures, and stock photos instead of the color blocks generated by devel_generate. All images included in this module are freely licensed (see the README.txt in the directories containing the images).

Extending this module

This project contains two modules:

  • Realistic Dummy Content API (realistic_dummy_content_api), which looks inside every enabled module for files which contain images or text, and replaces available fields.

  • Realistic Dummy Content (realistic_dummy_content), which replaces user pictures and node article images with portraits and stock photography. You can reproduce the realistic_dummy_content/realistic_dummy_content directory structure in your own modules for better control of the realistic dummy content you want to generate. If you don't want the example stock images that ship with this module, you can disable Realistic Dummy Content (realistic_dummy_content) and leave Realistic Dummy Content API (realistic_dummy_content_api) enabled.

Developers can also extend Realistic Dummy Content by implementing hooks defined in api/realistic_dummy_content_api.api.php. Specifically, if you want to be able to define realistic dummy content for a custom field type and the standard technique is not working, you can submit an issue or patch to the issue queue for this module; but you can also implement the field modifier yourself by looking at Realistic Dummy Content API's implementation of hook_realistic_dummy_content_attribute_manipulator_alter(), and the classes which are referenced from there.

Creating recipes

Often, sites require a set number of entities to be created in a specific sequence. For example, if your site defines schools which have entity references to school boards, a realistic scenario may be to generate 3 school boards followed by 20 schools. You can define this type of recipe for your site deployment module (or any module), by creating a file called ./sites/*/modules/mymodule/realistic_dummy_content/recipe/ An example is included herein.

Field meta data

Some fields have special meta data: body fields can have input formats in addition to body text; image fields can have alt text in addition to the image. This can be achieved using a specific naming scheme, and you will find an example in the enclosed data, which looks like:

  - body/
    - ipsum.txt
    - ipsum.txt.format.txt
    - lorem.txt
 - field_image/
    - 1.jpg
    - 2.jpg
    - 2.jpg.alt.txt

In the above example, realistic_dummy_content sees two possible body values, one of which with a specific input format; and two possible images, one of which with a specific alt text. Meta data is never compulsory, and in the case where a meta attribute is needed, a reasonable fallback value is used, for example filtered_html will be used if no format is specified for the body.

Issue queue

See the issue queue if you have questions, bug reports or feature requests.

Docker integration

To test this module you can run:


To create a development environment, you can run:


For more information see A quick intro to Docker for a Drupal project (Dcycle Project, Feb. 18, 2015). These scripts are meant to be used with Docker and CoreOS.

Continuous integration with Circle CI

CircleCI is a continuous integration platform for Drupal projects. In Continuous integration with Circle CI and Docker for your Drupal project (Dcycle project, Feb. 20, 2015), I documented how and why I set up continuous integration with Circle CI and Docker for Realistic Dummy Content.

See CircleCI test results here.

Drupal 8 version

Intial work has been completed on the Drupal 8 version. The roadmap is:

  • Tests are currently not passing. Make sure all tests pass. To run tests locally, install a CoreOS virtual machine, git clone the 8.x-1.x branch, cd into and type ./scripts/ To create a local environment, type ./scripts/
  • A 8.x-1.0-alpha1 version will be published.
  • The critical issues for 8.x-1.x needs to be zero.
  • A 8.x-1.0-beta1 version will be published and recommended for use.


Project Information