Skip to main content

Insights and guides

Practical website guides for small teams, not marketing theory.

Short guides and case studies that help you move from “looks fine” to “working better” in ways that fit real world constraints. Each one ends with a small action you can take in the next week, even if we never work together.

Most examples come from tourism, non profits, ag, and education in Western Canada, so the problems and solutions should feel familiar, not abstract.

Looking for something specific? Browse all articles.

Content and messaging

Getting to clear, “good enough” content that you can improve over time.

These pieces help you decide what to say, where to say it, and how to ship a first version without waiting for perfect copy.

Structure and UX

Making paths, not just pages.

These pieces are about how people move through your site, what they see first, and how you help them understand whether they are in the right place.

Coming soon

Designing clear paths for the visitors you care about most

How to map a few key journeys, for example “book a stay”, “understand a program”, “become a member”, and let those drive your navigation and calls to action.

Good if your navigation grew over time and nobody is quite sure what belongs where anymore.

Coming soon

Trimming a busy homepage without losing important content

A guide for teams who keep adding boxes and banners, and want a calmer homepage that still supports internal priorities.

Good if your homepage feels crowded, but nobody wants to remove “their” content block.

SEO and site health

Keeping your site fast, understandable, and free of dead ends.

These pieces focus on the basics that make a noticeable difference to visitors and search engines, without turning your site into an SEO experiment.

Coming soon

A calm approach to local SEO for small organizations

A simple checklist for keeping your local presence consistent and useful, from opening hours and locations to the pages that matter most.

Good if you depend on local visitors or bookings and feel like search is a black box.

Coming soon

Site speed basics for busy teams

How to improve loading times with a few realistic changes before you think about a rebuild.

Good if people complain that your site feels slow on mobile, but you do not know where to start.

Case studies and project notes

Real projects, with just enough detail to be useful.

These pieces sit between a portfolio and a how to guide. They show what changed on a real site, why it mattered, and what you might borrow for your own context.

Tourism and hospitality

Clarifying booking paths for a transportation company in the Rockies

How reorganizing services, simplifying calls to action, and improving mobile layouts reduced confused emails and helped more visitors reach the booking form.

Good if your analytics show people visiting key pages, but staff still spend time answering basic questions.

Read the Banff Transportation project

Education and research

Turning PDF heavy program information into web friendly pages

How structured program pages that surfaced dates, cost, and requirements helped busy professionals decide faster and reduced back and forth emails.

Good if important details are currently buried in documents that few people read.

See the Prentice Institute project

Non profit and bilingual

Publishing in two languages without doubling the work

How a bilingual content model and reusable components helped a small team keep English and French in sync, and share news more often.

Good if you work in more than one language and feel like one version is always behind.

Read the Cinemagine Alberta project

Want help applying a guide

We can look at your site through the lens of one of these pieces.

If a guide feels close to your situation but you are not sure how to apply it, we can look at your site together and decide whether you need a few small changes, an audit, or a new project.

Bring a link to your current site and a sense of what is not working. I bring questions, examples, and a calm review.

A light checklist before you write or change anything

  • Which guide feels closest to your current problem.
  • Which one or two pages on your site that problem shows up on.
  • What “better” would look like for those pages in the next 3 to 6 months.
  • Who inside your organization will own the changes.

Even if you work through this on your own, it should make the guides more concrete and easier to act on.