· 9 min read · Updates

The guides page is starting to become a real step-by-step helper, but it still has a long way to go

The guides page is starting to move away from generic advice and toward a more realistic Edmonton-first walkthrough. It still needs a lot of work, but the direction is finally starting to feel useful.

Back to all posts

I have been reworking the guides page because it was not doing enough.

For a long time, it looked like guidance without really being guidance. It had steps, labels, and categories, but too much of it still felt vague, templated, or detached from what someone in Edmonton would actually do next.

That is starting to change.

The page is still very much a work in progress. It still needs more specificity, more local detail, and more human judgement. But the direction is finally becoming clearer: one plain-language page that tries to walk someone through what to do next like a social worker would, while still using the directory and map underneath.

What I am trying to make the guides page do

The goal is not to create another tool full of buttons, toggles, or side routes.

The goal is simpler than that:

  • help someone name what kind of problem they are dealing with
  • help them figure out the first useful next move
  • help them know what to say, what to ask, and what to do if the first thing does not work
  • pull in real Edmonton-region services from the directory instead of talking in abstractions
  • use the map when location or travel actually matters, instead of treating it like a separate disconnected page

In other words, I want it to feel less like a website explaining support, and more like someone sitting beside you saying: start here, say this, ask this, and if that does not work, try this next.

What changed so far

The recent work has been about moving the page away from generic UX patterns and toward actual step-by-step help.

  • The guides result no longer hides useful information behind “show more detail” panels.
  • It is less dependent on sending people out to other guide pages just to keep going.
  • The wording is starting to sound more plain-language and less like a template.
  • Some branches now use real directory-backed services instead of unnamed “support options.”
  • The guide is starting to explain when to use the directory and when to use the map, instead of dropping those links in with no context.

That matters because the directory and map already do a lot of the heavy lifting. The guides page should not compete with them. It should use them well.

What “better” looks like

The best version of this page is not a big decision tree for its own sake.

The best version is a guide that says things like:

  • In Edmonton, start with this call first.
  • If they say they are full, try this second place.
  • If they tell you to come in person, open the map and choose the closest realistic option.
  • If you need to compare only two or three places, open the directory and stay inside this category.
  • If you freeze up, read this exact sentence out loud.

That is the standard I am trying to push it toward.

Where the page is still weak

I do not want to oversell it. The page still has real weaknesses.

  • Some results still sound too generic, especially in the lower sections.
  • Some branches still feel like they were written from a reusable pattern instead of from real local judgement.
  • Some of the legal, treatment, shelter, and withdrawal paths still need stronger Edmonton-specific “what actually happens next” language.
  • The named service suggestions need more cleanup so they only recommend the most appropriate real options.
  • The map integration still needs to get smarter about things like closest shelter tonight, closest detox intake, or closest legal clinic for ID help.

So this is not a finished system. It is a direction that is finally becoming worth building on.

Why I still think this direction matters

A lot of people do not need “more information.” They need help making one decision while stressed, tired, scared, in withdrawal, under time pressure, or trying to help someone else.

That means a useful guide page has to do more than describe categories. It has to help someone act.

The directory is powerful when you need to compare. The map is powerful when location matters. The guides page should become the layer that helps someone understand when to call, when to compare, when to travel, and when to stop reading and just do the first thing.

The direction from here

The next work on the guides page is not about adding more interface.

It is about making the page feel more human, more local, and more honest.

  • More Edmonton-specific first-call guidance.
  • More realistic “if they say no, full, or call back later” flows.
  • More useful directory-backed service suggestions inside each path.
  • Smarter use of the map when location becomes the actual problem.
  • Less robotic wording and more real plain-language sequencing.

That is the work.

If you want to see where this is going, the best place is the guides page itself:

The page is still rough in places. But it is starting to become something more realistic: a step-by-step Edmonton-first way to solve problems without making people do all the interpretation alone.

  • edmonton
  • directory
  • map
  • site-improvements