
Security News
vlt 1.5.0 Adds Agent Skills Management
vlt 1.5.0 links skills from JavaScript dependencies to coding agents, with lockfile versioning and Socket data to filter out known malicious packages.
@ilo-org/twig
Advanced tools
This package provides the implementation of the Design System using Twig. It also includes a Storybook project for documentation and development of the components in the system. Storybook and twig integration is done by the internal Maestro. It has dependencies on the following other @ilo-org packages:
Before running any of the commands below, make sure to:
pnpm install from the monorepo root to install all dependenciespnpm build:libs from the monorepo root to build all necessary packages| Command | Description |
|---|---|
pnpm build:lib | Builds the library |
pnpm build:docs | Generates static Storybook documentation |
pnpm storybook | Starts Storybook development server on port 6006 |
pnpm start:theme | Starts Docker containers in detached mode(Used in tests) |
pnpm cr:theme | Rebuilds Drupal cache inside Docker container(Used in tests) |
pnpm cy:open | Opens Cypress test runner(Used in tests) |
pnpm test | Runs Cypress tests in headless mode(Used in tests) |
pnpm lint | Runs ESLint to check code quality |
pnpm lint:fix | Runs ESLint with automatic fixes |
Each component is located in the src/components folder. Each component has its own folder named after the component. Inside each component folder, you will find:
[component].twig: The Twig template file for the component. (Required)[component].component.yml: UI Patterns definition for the component. This file will be used for the story generation too. (Required)[component].js: The JavaScript file for the component. (Optional)[component].behavior.js: The Drupal behavior runner for attaching the JS bundle to the component. (Optional)accordion component for reference)The storybook is a source of truth for the components. Each component will have its own stories file located in the stories/[component].stories.js file. The stories are generated from the UI Patterns definition file using the Maestro.
Here is an example of a story file for the button component:
import Button from "../src/components/button/button.twig"; // Twig template
import ButtonPatterns from "../src/components/button/button.component.yml"; // UI Patterns definition
import { Maestro } from "@ilo-org/maestro";
const story = Maestro.create(Button, ButtonPatterns); // Generates a meta and stories from the UI Patterns definition
const Meta = {
title: "Components/User Interface/Button",
tags: ["autodocs"],
...story.meta,
};
const [Default] = story.stories; // Extracts the generated story
export default Meta;
export { Default };
For more details about the Maestro check the Maestro documentation.
We are using Cypress for component testing. To achieve this, we have a Drupal instance running inside a Docker container. The Drupal instance has the ILO Base Theme installed and configured. The components are rendered using the Base Theme and then tested using Cypress.
You can start the Docker containers using the following command:
pnpm run start:theme
After that you can check the localhost:8082 to see the Drupal instance running.
To open the Cypress test runner, you can use the following command:
pnpm run cy:open
You can find the tests in the cypress/e2e folder. Each component will have its own test file named after the component.
For contribution guidelines, please refer to the Main Documentation.
FAQs
Twig components for the ILO's Design System
We found that @ilo-org/twig demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.

Security News
vlt 1.5.0 links skills from JavaScript dependencies to coding agents, with lockfile versioning and Socket data to filter out known malicious packages.

Security News
Rust 1.100 will add opt-in dependency cooldowns to Cargo, giving security scanners and maintainers time to catch malicious crate releases.

Security News
Cloudflare is acquiring Deno’s team, which will provide another year of bug fixes and security updates before ending support for the runtime.