How we choose resources
A resource belongs here when it helps a reader perform a task, understand an option or find a relevant specialist. Inclusion is not a guarantee of quality, availability or suitability. Verify current details directly with the provider.
Websites, software and technology
Webforless.ca
A Canadian web resource that can be evaluated when comparing website development and maintenance options.
compare Canadian small-business website development optionsSoftware-Development.ca
A custom software resource for businesses evaluating systems beyond standard off-the-shelf tools.
explore custom software development for business workflowsComputerComponent.ca
General informational material on computer components, upgrades and hardware planning.
review computer hardware and component planning informationVancouver Web Design
An additional regional website-design resource to compare alongside other providers.
compare Vancouver website design and development resourcesTransportation and regional planning
Transportation examples are placed in the regional and event guides where route, vehicle and service context matters. Start with the event transportation guide, Metro Vancouver guide, Fraser Valley guide or Whistler planning guide.
Use primary sources for rules and current conditions
For licences, taxes, road closures, public transit, airport procedures and event permits, use the responsible government, airport, municipality or agency as the primary source. Commercial guides can explain the decision, but official sources should confirm current requirements.
How to compare any commercial resource
Check current ownership, contact information, service scope, published policies and whether the business can explain the exact work you need. For technical projects, ask who owns the domain, code, accounts and data. For local services, confirm availability, insurance and cancellation terms before paying a deposit.
Suggesting a resource
A useful suggestion should identify the guide it belongs in and the reader problem it solves. A request that consists only of a preferred anchor phrase or a reciprocal-link proposal is not enough reason to add a resource.