Docs

DNP documentation exists to address a problem that Divi, news themes, and visual builders do not solve systematically: the absence of editorial criteria applied to design.

Divi makes it possible to build almost anything, but it does not help decide what to build, in what order, or why one structure works better than another when working with real news content. The result is often a collection of pages that look acceptable in isolation but lack coherence, hierarchy, and a clear reading logic.

DNP does not replace Divi or restrict its flexibility. It adds a missing layer: a system of decisions that reduces improvisation and prevents the same structural mistakes from being repeated across projects.

The problem is not technical.
It is structural.

 

What DNP is — and what it is not

DNP is an editorial system applied to the design of digital newspapers built with Divi. It is not a theme, not a plugin, and not a collection of interchangeable templates.

The system defines a specific way of working by separating structure, content, and editorial criteria so design does not depend on constant manual adjustments or ad-hoc decisions.

DNP is built around reusable layouts, shared hierarchy rules, and a reading logic designed for real informational content. Each layout serves a defined editorial role and makes full sense as part of the system.

DNP does not attempt to cover every possible use case or adapt to any type of website. It is designed specifically for digital newspapers, news-driven magazines, and editorial projects where order, consistency, and scalability matter.

It is not a visual builder, a creative design system, a Divi course, or a promise of results. The system is defined and usable from the start. Its evolution expands the set while preserving the same criteria.

 

Why DNP layouts are not interchangeable

DNP layouts are not independent pieces chosen by taste or combined at random. They function as parts of a single system and share common structural decisions.

Each layout corresponds to a specific editorial role within the reading flow: opening a page, structuring categories, supporting continuity, or closing with recent content. They are not designed to fit anywhere, but to perform a clear function in context.

What connects them is not visual style, but internal logic: how cards are structured, how grids are applied, how dynamic content is handled, and how rhythm and hierarchy are maintained.

This shared logic allows coherence across sections, prevents constant redesign, enables content reordering without breaking structure, and lets the project scale without losing identity. Used in isolation, a layout still works, but its value is reduced. The system is where meaning emerges.

 

The card as the core design unit

In DNP, the fundamental design unit is not the page or the full section. It is the card.

A card is the minimal repeating structure within layouts and contains the essential elements of a post: image, title, metadata, and optional excerpts or elements. Instead of designing multiple column variations, DNP defines a single, solid card and lets the system repeat it through loops.

Layouts emerge from the repetition and placement of that card, not from manual variation. This makes it possible to change the number of items without redesigning, reorganize entire blocks easily, and maintain visual coherence across sections while reducing errors and unnecessary adjustments.

DNP does not design pages.
It designs cards organized through editorial criteria.

 

Separating content, design, and editorial criteria

DNP is built on a clear separation between three layers that are often mixed in digital projects: content, design, and editorial criteria.

Content consists of real posts, images, categories, and metadata. It changes constantly and should not force redesign.
Design defines how content is displayed: structures, grids, cards, and visual hierarchy. In DNP, design is defined once and reused.
Editorial criteria determine why a structure makes sense in a given context: what comes first, what supports, what stands out, and what remains secondary.

Keeping these layers separate prevents common problems: design depending on specific content, constant visual adjustments after editorial changes, weekly homepage redesigns, and loss of coherence as the project grows.

In DNP, content moves, design remains stable, and editorial criteria guide decisions.

 

How DNP is used in practice

DNP is not meant to be followed linearly or studied from start to finish. It is used pragmatically, based on the needs of each moment.

In real projects, use does not begin with theory, but with a concrete structure. From there, the system supports decisions without imposing a fixed path. Layouts are selected based on content type, adapted to available material, and adjusted in rhythm and hierarchy to maintain coherence.

Guides explain how to build the structures.
Editorial criteria clarify whether they make sense.
Documentation clarifies the framework when doubts arise.

DNP does not direct the process step by step. It reduces friction so design does not become a recurring problem.

 

Control by reduction, not by excess

DNP is designed to offer control where it adds value and remove it where it creates inconsistency.

The user controls structure, hierarchy, rhythm, and layout combination according to context. At the same time, the system deliberately avoids exposing decisions that tend to generate instability, such as redefining styles module by module or reinventing layout logic on every page.

The system does not impose results, but it sets clear boundaries. Within them, work is flexible and stable. Outside them, DNP does not attempt to provide answers.

The goal is not to have more options, but to need fewer decisions to reach a solid result.

 

Scope and limits of the system

DNP is designed to solve a specific need: building and maintaining coherent, scalable, editorially ordered digital newspapers with Divi.

It is most effective when there is real content volume, multiple sections with distinct roles, frequently changing homepages, and a need for long-term design stability.

DNP is not designed for corporate websites, conversion-focused landing pages, or projects driven by constantly changing visual identities. It does not replace editorial judgment or decide what content matters.

DNP does its job when design stops being a constant concern and becomes a stable foundation. From there, value comes from content and editorial criteria, not from layout decisions.