มาโครสำหรับมาร์กอัปที่ซ้ำกัน

When the same input field or card markup appears with small tweaks, copying it gets messy. A macro turns that pattern into a reusable function. 🛠️

A macro is a template function: you define markup once with parameters, then call it many times with different arguments.

You declare a macro with a name and parameters, write its markup, and close it with endmacro. It is reusable from then on.

Invoke a macro like a function, passing arguments. Jinja2 renders the macro body with those values right where you call it.

Macro parameters let one definition produce many variations, such as different input types or labels, from a single source of markup.

Give parameters defaults so common calls stay short. Callers override a default only when they need something different.

Store shared macros in a file like forms.html so many templates can import and reuse the same helpers.

After import, call a macro through its namespace. This keeps your macro library separate from the page using it.

Use from import to pull just the macros you need by name, keeping the template clean and the intent obvious.

An include drops fixed markup; a macro takes arguments and varies its output. Reach for macros when the snippet must change per call.

Macros remove copy-paste from your templates: fix the field markup once and every call site updates. That is templating done right. ✨

What makes a macro different from an include?

A macro is a reusable, parameterized template function. Define it once, import it, and call it anywhere to keep templates DRY. 🎯