Contact

Contact should take one minute, not one more layer.

This page should route the next move quickly: start with the reporting when context matters, use the public links hub for outreach, and keep follow or support paths direct.

No fake inbox. No hidden admin layer. No contact theater.

Public routes3

Read, reach out, or support without inventing a fourth lane.

Form fields0

No fake intake layer and no implied private staff queue behind the page.

First moveRead first

Story context stays on site before any public handoff leaves it.

Three public lanes. Three distinct jobs.

Put the route choice first, then get people off this page and into the right place.

Start with the reporting

If the note depends on a current issue, article, or actor, use coverage or search first so the context stays attached to the reporting.

Best when the message only makes sense after reading the story or finding the issue lane.

Browse coverage

Use the links hub

Tips, collaboration questions, and channel-specific outreach should start in the live public directory instead of on a fake contact form.

Best when the question is where to reach the project, not which route to read next.

Open links hub

Stay with the reporting

Use Substack when the next step is delivery, archive continuity, and updates between site visits.

Best when you want the reporting to come to you instead of checking back manually.

Subscribe on Substack

Back the work directly

Use Ko-fi when the clearest next step is helping fund the reporting without adding another layer.

Best when the decision is already made and the next move is direct support.

Support on Ko-fi

If the note starts with a story, start with the story.