INCLUDED IN PRO / NATIVE FRAMER
Reusable content cards, process steps and alternate section compositions. Edit the text controls on an instance, or change the native layers in its component definition. These examples use this template’s existing type and colour system.
01 / EDITORIAL STATEMENT
A workspace shaped around the work.
An adaptable solutions page for a fictional collaboration product. Explain the user’s context, show the workflow and connect the next action to a real product destination.
02 / DETAILED CONTENT CARDS
Make the detail easy to scan.
SMALL TEAMS
Keep the handover close
Bring the brief, a clear owner and the next action into one place. A useful handover explains what changed and what decision is needed next.
Example workflow: intake → plan → review → handover. Replace each step with screenshots and features your real product supports.
INDEPENDENT STUDIOS
Make the project legible
Organize parallel projects without turning every update into a meeting. Show the current stage, the open question and the person moving it forward.
Example content: project brief, decision log and weekly review. Client sharing and permissions require a real product implementation.
OPERATIONS
Give recurring work a rhythm
Turn a repeatable process into an understandable sequence. Make exceptions visible and record the reason behind a changed decision.
Example content: recurring checklist, named owner and review date. Scheduling, automation and integrations are not implemented by this website template.
03 / NUMBERED PROCESS
Give the next step a clear place.
01
Lead with the change
Name the behavior the reader can now see or use.
02
Explain the consequence
State how it affects an existing workflow, including any limitation.
03
Make action explicit
Say whether the user needs to update, reconnect or migrate anything.
04 / A FOCUSED CALL TO ACTION
Begin with a useful conversation.
Use one action with a clear destination. Replace this example with the next step that makes sense for your real service or product.