Skip to main content
Washington Field Guide Evidence-backed regional planning

About the project

A travel guide evolving into regional knowledge infrastructure.

Washington Field Guide is an independent project created to make Washington travel planning more practical, supportable, and reusable.

The origin

It began with a simple question: what information actually makes a trip work?

Cascades Field Guide started as a North Cascades tourism website. The most useful pages were rarely generic destination profiles. They were the pages that helped with access, seasonal timing, service gaps, where to stay, realistic routes, and backup plans.

As the research grew, ordinary page-by-page notes became difficult to maintain and reuse. The project began separating facts from prose, attaching sources, tracking unknowns, connecting related places and decisions, and testing whether the same information could support multiple outputs.

That shift created Washington Field Guide: a broader regional platform designed to combine practical publishing with evidence-backed data, governed retrieval, and business-facing visitor resources.

What the project is becoming

Three layers that reinforce one another

Public guide

Decision-first travel planning

Regional guides that help visitors choose realistic routes, bases, activities, seasons, and alternatives.

Knowledge system

Structured visitor intelligence

Reusable regional facts, sources, relationships, status rules, unknowns, and planning logic.

Business layer

Practical hospitality products

Property guides, staff resources, local planning tools, and future regional data services.

What Washington Field Guide is not

Growth is not measured by page count alone.

  • A generic “things to do in Washington” publication
  • A thin automated directory of low-evidence location pages
  • A collection of disconnected regional microsites
  • An autonomous system that publishes whatever it generates

Operating principles

Depth, usefulness, and maintainability come first.

  • Build around decisions and failure points.
  • Preserve regional differences within shared standards.
  • Keep sources, uncertainty, and current status visible.
  • Use automation to reduce repetitive work, not accountability.

Independent and evolving

The strategy is durable, but not frozen.

Washington Field Guide is independently built and maintained.

The project’s handovers, schemas, roadmaps, and standards are living context. New regional work, field verification, business feedback, audits, and better technical designs can supersede earlier recommendations.

That flexibility is intentional. The objective is a system that improves as its assumptions are tested.

Contact the project