Most service directories answer one question: what exists?
YEG Support is trying to answer a different question first: what should I try next?
That is why the homepage is changing. The first screen was starting to ask two different things at once: do you want to browse resources, or do you want help deciding what to do next? Those are not the same job.
A service list can be useful once you already know the lane. But when someone is scared, tired, in withdrawal, newly homeless, dealing with paperwork, trying to help a friend, or just overwhelmed, a giant set of categories can feel like another task instead of help.
The homepage should do the more human thing first: help someone make a next decision. One first move. One backup. Then the local resources that fit.
A small thank-you belongs here too: CityNews Edmonton covered YEG Support in April 2026, and that story helped more people understand why this kind of local, plain-language support tool needs to exist.
The point is not to replace live navigation
Live navigation still matters. I link to 211 throughout the site because real-time service navigation can be the safest option, especially when hours, beds, intake rules, and eligibility change quickly.
But YEG Support is being built for the moments before and after that call too: when someone does not know what kind of help to ask for, when they need words to say out loud, when they need one backup if the first call does not work, or when they need to compare only the few resources that match the situation.
That is the difference I want the homepage to make. Not bigger than live navigation. Not a replacement for it. A calmer layer around it.
The problem with browse-first help
Browse-first pages assume the person already knows what kind of help they need. That sounds simple until real life gets involved. Someone may not know whether they need detox, urgent care, counselling, shelter, legal help, income support, peer support, or a crisis line. Often they need more than one of those, in a particular order.
That is why the homepage is being rebuilt around a step-by-step helper instead of a category wall. The point is not to hide the service information. The point is to stop asking people to classify their own emergency before the page has helped them think.
A directory and a guided directory do different jobs
A directory is useful when the question is, “Show me the options.” A guided directory is useful when the question is, “What do I do first?”
- A directory lists resources. A guided directory orders them into a first move, a backup, and wider options only when needed.
- A directory assumes the category is known. A guided directory treats “I do not know where to start” as a normal situation, not a failure.
- A directory is strongest for comparison. A guided directory is strongest for sequencing: call this first, keep this ready, use the map only if travel becomes the problem.
- A directory can still leave someone interpreting everything alone. A guided directory tries to carry more of that interpretation on the page.
What changed
- The guide now leads. The first interactive section asks one question at a time and keeps attention on the immediate next decision.
- The old category grid is no longer the centre of the homepage. It is still part of the site, but the homepage no longer opens by asking people to browse every lane.
- Resources appear after the guide has context. Matched listings are meant to follow the answer path, not compete with it.
- The result is a first move plus a backup. A good support page should not give only one fragile option. It should offer the fastest safe step and a second path if the first one does not work.
- Search becomes refinement, not the starting point. Search is useful once someone has a direction. It is less useful when the person does not yet know what words to type.
What this looks like in practice
The old pattern was easy to build but hard to use under stress: choose a category, scan a list, decide what applies, then hope the first option works.
The new pattern is meant to be smaller: answer one question, get a first move, keep a backup visible, and only widen the resource list if the first step gets stuck.
For crisis support, that means the page should not start by asking someone to browse every crisis listing. It should ask whether the person is safe right now, put the fastest live line in front of them, and keep the backup close. For treatment, it should not assume residential care is the only serious path. It should help sort counselling, day programs, outpatient care, medication support, detox, and residential treatment by actual fit. For legal or ID help, it should narrow the problem before opening every legal listing in Edmonton.
That is the product idea in plain language: fewer tabs, fewer guesses, fewer dead ends.
How the new homepage is supposed to feel
The goal is for the page to feel less like a database and more like a calm local helper. It should still be practical. It should still have real Edmonton resources. But the interaction should feel more like: answer what fits, get a first move, then see the services that match.
That matters because the hardest part is often not finding a phone number. The hardest part is knowing which phone number belongs to this moment. If someone is unsafe, the page should not drift into ordinary listings. If someone is medically at risk, the page should point toward medical advice before counselling. If someone needs treatment but not residential care, the page should make room for counselling, day programs, outpatient care, medication support, and peer options.
What happens to the resource list
The listings are not going away. They are becoming the resource layer underneath the guide.
That means the directory work still matters: names, phone numbers, regions, categories, eligibility notes, safer-entry details, and backup options. But on the homepage, those resources should appear in response to the guide instead of sitting there as a separate module that asks for attention too early.
In practice, that means a person can move through the helper and then see matched services for the path they chose. The site should connect the question, the suggested next step, and the actual Edmonton resources in one place.
What YEG Support is trying to add
The site is not trying to win by having the biggest list. It is trying to be useful at the decision point.
- Order: first move, backup, wider options.
- Words: scripts and plain questions someone can use when they call.
- Context: local notes about cost, access, referral, travel, and fit.
- Connection: the guide, map, and listings should work together instead of feeling like separate tools.
- Trust: listings, editorial posts, correction notes, and source limits should be easier to understand.
That is the space where YEG Support can stand apart: not as a giant database, but as a local decision tool with a directory underneath it.
Why this is more than a design change
This is a content decision as much as a layout decision. The site is not only trying to collect links. It is trying to reduce the number of choices someone has to make while already under pressure.
A better homepage should answer practical questions like:
- Is this urgent enough for a crisis line or emergency response?
- Is there a medical risk that should come before counselling or peer support?
- What can someone try tonight?
- What is the backup if the first service is closed, full, or not a fit?
- What words can someone use when they call?
That kind of help is different from simply displaying a large list. A list can be accurate and still leave someone stranded at the decision point.
What still needs work
The homepage is closer, but it is not finished. The guide needs more thoughtful matched resources, especially for counselling, treatment alternatives, legal and ID help, shelter, income supports, and affirming support. The wording also needs to stay plain. If a section starts sounding like a product pitch or a government form, it has missed the point.
The next improvements I want are simple: better matched results, clearer backup steps, less clutter before the person has answered anything, and more local guidance that says what to try first without pretending every situation is the same.
The direction
The homepage should become the place where the site makes its promise clearly: not just more links, but a next step.
If someone already knows what they need, they should still be able to compare services quickly. But if they do not know where to start, the homepage should not punish them for that. It should slow the page down, ask the next useful question, and bring the right resources forward when they are needed.
The promise is simple: fewer tabs, fewer guesses, fewer dead ends. Start with one question. Leave with one next step and one backup.