essentials-fixtures

Automate fixture data configuration and loading for Silverstripe Essentials projects.

1|Updated May 12, 2026

Search Tags:#fixtures #silverstripe #essentials #template population #elemental

Ready to run

npx skills add https://github.com/jsirish/silverstripe-skills --skill essentials-fixtures-jsirish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: essentials-fixtures
Source: https://github.com/jsirish/silverstripe-skills/tree/main/skills/essentials-fixtures
Command: npx skills add https://github.com/jsirish/silverstripe-skills --skill essentials-fixtures-jsirish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the configuration and implementation of the recipe-silverstripe-essentials-fixtures package, simplifying the population of Element Template records in Essentials projects.

Core Features & Use Cases

Project Configuration: Automates setup of the fixtures-populate.yml and essentials-element-fixtures.yml configuration files.
Fixture Loading: Manages the loading of shared assets and template fixture data.
Element Placeholder Data: Provides placeholder data for Element Templates in the Essentials demo library.
Use Case: Ideal for quickly setting up a new Essentials project with pre-populated Element Templates for testing or development purposes.

Quick Start

Run 'ddev sake dev/build "flush=1"' followed by 'ddev sake dev/tasks/PopulateTask "flush=1"' to populate the fixtures for your Essentials project.

Frequently Asked Questions about essentials-fixtures

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I populate Element Templates with fixture data in Silverstripe Essentials?▼

To populate Element Templates with fixture data in Silverstripe Essentials, run the `dev/tasks/PopulateTask` command after building the database to load shared assets and placeholder content automatically.

What configuration files are required for Silverstripe Essentials fixtures setup?▼

Silverstripe Essentials fixtures setup requires configuring `fixtures-populate.yml` and `essentials-element-fixtures.yml`, along with manual configuration of `app/_config/essentials-styles.yml` before the first run.

Do I need brand guide colors or Figma variables before running Essentials fixture population?▼

Yes, Essentials fixture population requires setup of Figma variables, XD prototype sampling, or brand guide colors beforehand to properly configure the `essentials-styles.yml` file for template styling.

What's the best way to load shared assets and placeholder data for Silverstripe Elemental blocks?▼

The best way to load shared assets and placeholder data for Silverstripe Elemental blocks is using the `recipe-silverstripe-essentials-fixtures` package, which manages fixture loading through `PopulateTask`.

Why are my Silverstripe Essentials Element Templates not showing populated content after dev/build?▼

If Element Templates are not populated after `dev/build`, ensure you run `dev/tasks/PopulateTask` with `flush=1` afterwards, as the build step alone does not load the fixture data.

Can I use Essentials fixtures for testing pre-populated Element Templates in a new Silverstripe project?▼

Yes, Essentials fixtures are ideal for quickly setting up a new Silverstripe project with pre-populated Element Templates, providing shared assets and placeholder data for testing or development purposes.