HERO

Tool Page Template (Conversion-first)

One-line value: Use Tool Page Template (Conversion-first) as an execution-ready playbook, not a note.

When to use: Use this tool when you need an immediately executable output, not theory.

QUICK RESULT

If you only do one thing → run the 5-minute checklist and publish one concrete output today.

For you if

• You need a repeatable process with low ambiguity.
• You are shipping under time pressure and need clear decisions.
• You want a template that teammates can reuse.

Not for you if

• You want deep background research before acting.
• You are not ready to capture before/after outcomes.

Concrete benefits

• Cuts setup time by turning intent into a ready-to-run sequence.
• Improves consistency across operators and handoffs.
• Reduces avoidable errors with explicit checks.
• Makes outcomes auditable with clear proof points.

ACTION CHECKLIST

• [ ] Define the output artifact you need (doc, draft, decision, or fix).
• [ ] Gather only required inputs; skip optional data on first pass.
• [ ] Execute each step in order and note decisions inline.
• [ ] Verify quality with one acceptance check before publishing.
• [ ] Save final output and a reuse note for the next run.

EXAMPLE / DEMO

Bad: You skim the page, improvise steps, and miss a verification gate.

Good: You follow the checklist, capture evidence, and ship a result teammates can trust.

Real use cases

• Creating a production-safe content update runbook.
• Auditing workflow output before publish.
• Turning rough operator notes into a standardized deliverable.

WHY IT WORKS

• Moves quickly from reading to doing.
• Uses explicit quality gates.
• Produces reusable artifacts, not one-off work.

NEXT ACTION

• Copy this checklist into your current task and complete the first two boxes now.

Source notes (kept for context)

Tool page template

Use layout: layouts/tool.njk and this frontmatter shape:

---
title: [Tool Name]
description: [Short value statement]
layout: layouts/tool.njk
primaryCta:
  label: [Primary CTA label]
  href: [/tools/... or external URL]
  external: false
fitFor:
  - [Who this is best for #1]
  - [Who this is best for #2]
  - [Who this is best for #3]
notFor:
  - [Who should avoid this]
  - [Constraint #2]
  - [Constraint #3]
benefits:
  - title: [Benefit 1]
    copy: [Benefit detail]
  - title: [Benefit 2]
    copy: [Benefit detail]
  - title: [Benefit 3]
    copy: [Benefit detail]
alternatives:
  - title: [Alternative 1]
    copy: [Why choose it]
    href: [/tools/...]
    cta: [CTA text]
  - title: [Alternative 2]
    copy: [Why choose it]
    href: [/tools/...]
    cta: [CTA text]
relatedHub:
  title: [Hub Name]
  label: [Hub CTA Label]
  href: [/hubs/...]
nextStep:
  primaryHref: [/start/ or /hubs/...]
  primaryLabel: [Primary next step label]
  secondaryHref: [/tools/...]
  secondaryLabel: [Secondary next step label]
---

Minimum quality rules

• Keep each section short and scannable.
• Reuse the same primary CTA language on repeated blocks.
• Include a related hub and explicit next-step options.
• Avoid filler paragraphs; prefer bullets and actions.