ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #pug
Decide whether to use Pug mixins or includes for UI components by comparing dynamic and static use cases, trade‑offs, and a real example.
Pug’s extends and block directives let you define a reusable layout once, eliminating duplicated markup and keeping templates DRY.
Learn how Pug’s extends and block keywords let you reuse a base layout, avoid duplicated markup, and safely evolve HTML templates in Node.js apps.
Build reusable Pug components with mixins: capture caller attributes with the attributes object, accept variable input with rest arguments, and wrap content with blocks — plus the class-merging and indentation traps to avoid.
Pug mixins render but nested content disappears when the mixin lacks a bare <code>block</code>. Diagnose with a table, ordered checks, and fixes for common whitespace and block placement bugs.
Pug’s extends/block inheritance lets you define a single parent layout and override only the sections that differ per page — eliminating copy‑paste duplication while keeping asset injection composable via append/prepend.
Duplicate markup hurts maintainability. Pug mixins let you write reusable fragments once, pass data, and keep templates DRY. This post walks through a concrete example, shows how mixins compile, discusses trade‑offs, and gives next steps for production use.
Learn how to define a reusable card mixin in Pug, pass parameters and optional block content, and understand the trade‑offs of compile‑time reuse.
When Pug templates throw unexpected errors, a systematic diagnostic approach can quickly pinpoint the root cause. This guide walks through the most frequent Pug failure modes and offers ordered checks to resolve issues in Node.js projects.
nodejs
express