Using libraries in projects

Every project in Denada is built on top of a library. The library defines which blocks are available and how they look; the project fills in the content. This page covers how libraries and projects work together.

​

Selecting a library

When you create a new project, you choose which library it will use. The library determines the set of blocks you can add and the overall design style. If your team has just one library, Denada uses it automatically; if there are several (for example, one for newsletters and one for promotional emails), a picker appears so you can choose the one that matches what you’re creating.

​

The block picker

Once your project has a library assigned, you add content by inserting blocks from that library.

1. Use the add-block control between blocks in the preview — or the Add first block… button in an empty project — to open the block picker.
2. The picker shows all published blocks in the project’s library.
3. Browse the list or search by name.
4. Click a block to add it to your project.

Each block appears as a preview card so you can see what it looks like before adding it.

​

How parameters get filled in

Every block comes with a set of parameters defined by the library — things like headline text, images, button labels, and colors. When you add a block to a project, these parameters start with default values (or empty, depending on the library design). You fill in parameters in two ways:

• In the editor — select a block and edit its parameters in the sidebar.
• Through chat — describe what you want and Denada fills in the parameters for you.

The library controls which parameters exist and what types they accept. You cannot add new parameters to a block from the project editor — that is done at the library level, in the library editor.

​

Projects keep their own copy

When you create a project, it takes a snapshot of the library at that moment. If the library is updated later (new blocks, design changes, bug fixes), your existing projects are not affected until you choose to update. This means library work never silently changes a campaign that’s already approved.

​

Library versions and updates

The Options tab of the project editor shows which library and version the project is using. When a newer version of the library is available, the library shows an Update available badge. Click the library to see your options:

• Update — pull in the latest library version.
• Change version — browse all available library versions (named releases and automatic checkpoints) and pick the one you want. The current version is labeled so you always know where you are.
• Change library — switch to a different library entirely. Your blocks are kept, but may not match up with the new library.
• View library — open the library in the library editor to see its blocks and structure (requires the Libraries permission).

This gives you full control — you can stay on a stable version for approved campaigns, roll back to a previous version if needed, or pull in the latest changes when you’re ready. Version changes apply to the project and all of its variations together, and they can be undone.

​

How it all fits together

1. Library defines the available blocks, their structure, and their parameters.
2. Project selects a library and assembles blocks in a specific order with filled-in parameter values.
3. Variations (optional) let you create multiple versions of the same project with different parameter values.

This separation means your brand’s design system lives in the library, while individual campaigns live in projects. Update the library once, and every project can pull in the change when it’s ready.