Template fields are reusable pieces of content that live across all your guides and all your clients. Change it in one place, it updates everywhere.
Why this matters
Some content in your guides is universal. Your planning process graphic, a disclaimer, an explanation of how you think about asset allocation. You don't want to recreate that for every client or update it in 50 places when it changes.
Other content is client-specific but follows the same structure. Maybe you want a spot in every guide for a screenshot from another tool, but the screenshot is different for each client. Template fields handle both cases.
How I think about it
I use template fields two ways:
As universal content. I upload an image of my planning process and add it to my overview guide. Every client sees the same image. When I update the image in the template field section, it updates across all clients automatically.
As placeholders. I create a template image field called "Guardrails" and leave it empty. I add it to a guide. When I open that guide inside a specific client's file, there's an upload box where I can drop in that client's guardrails screenshot. The placeholder exists in the template. The content is per-client.
Text fields work the same way. You can write a default paragraph that appears in every guide, or leave it blank and fill it in per-client.
How it works in Kerdora
Template fields are created in the Templates section. Each field has a name, a type (text or image), and optional default content.
Once created, you add a template field to any guide by dragging a "custom text" or "custom image" component into the layout and linking it to the field. The field's content renders wherever it's placed.
If you need something truly one-off (content for a single client that doesn't need to exist as a reusable field), you can add a custom text or image block directly in the client's guide by clicking the pencil icon in the Overview tab.