STRIDE
STRIDE treats running as a way to read the city with people at your pace, not merely a personal pace dashboard.
01 · Direction
Routes, crews, challenges, and run data follow the sequence a newcomer needs before feeling comfortable at the meeting point.
The brief is to make a membership and community platform that creates desire and helps visitors decide without assembling information from several places. STRIDE is therefore treated as a content and conversion system, not a collection of attractive screens.
The primary action is joining a run matched by pace and place; app installation follows once the calendar has relevance.
“For STRIDE, aesthetics earn their place only when they make people, rules, activity calendar, place, and community outcomes easier to see, understand, and act on.”
- Format
- membership and community platform concept
- Audience
- Newcomers assessing culture, schedule, and fit before joining
- Primary proof
- People, rules, activity calendar, place, and community outcomes
- Primary action
- See the calendar, choose a programme, and become a member
02 · Flow
Flow should tell visitors what is worth remembering.
Flow extends the hero promise into a situation a visitor can picture. For STRIDE, the content needs to show what happens, why the detail differs, and which information matters enough to continue exploring.
In production, this module should offer a short scanning layer, deeper verification for people who need it, and a clear route forward. That structure preserves editorial pace without sacrificing search discovery or accessibility.
Principle: every artboard must add a reason to believe or a reason to act.
03 · Crews
Crews is not filler; it is evidence.
Crews is an evidence layer for STRIDE's positioning. Instead of adding adjectives, the artboard uses people, rules, activity calendar, place, and community outcomes to turn a visual impression into a reason visitors can remember and compare.
Every claim should carry a source, scope, and update date where relevant. That becomes essential when a concept moves towards production: trust comes from verifiable detail, not the volume of brand language.
Principle: every artboard must add a reason to believe or a reason to act.
04 · Challenges
Place challenges at the right moment in the decision.
At the centre of the journey, challenges classifies choices and reduces cognitive load. Primary information should scan in seconds; secondary detail opens after visitors know what they care about.
Headings, image captions, and contextual links also help search engines understand the page without keyword repetition. SEO is the outcome of clear information, not a text layer added after design.
Principle: every artboard must add a reason to believe or a reason to act.
05 · Context
Context connects brand story to action.
Context sits close to the moment a visitor considers “See the calendar, choose a programme, and become a member”. The artboard therefore keeps brand emotion while making conditions, the next step, and the post-click outcome explicit.
A live version should measure the primary action and hesitation signals: returning to an earlier section, opening support information, or leaving at a particular field. Those signals reveal missing content before button colour or CTA wording is optimised.
Principle: every artboard must add a reason to believe or a reason to act.
06 · Download
Close with download, not an empty button.
Download closes the story by recalling value already demonstrated rather than placing a button in empty space. Visitors should see a next action that fits the context and be able to return to decision information without losing position.
The final invitation should retain the spirit of “Run with your city” while stating response time, required information, and alternatives. A good ending lowers uncertainty; it does not create artificial pressure.
Principle: every artboard must add a reason to believe or a reason to act.
Design language
Recognise STRIDE before the logo has to appear.
The design language follows a product showcase treatment, the concept palette, and its native image rhythm. The goal is not novelty in every section but a small set of rules strong enough to support new content.
- 01
Contrast with a job
Accent colour is reserved for attention and primary action; background, type, and imagery stay stable so STRIDE never becomes noise.
- 02
An industry-specific rhythm
Image ratio, paragraph length, and headline placement follow how people actually explore a membership and community platform, not a universal portfolio template.
- 03
Evidence before invitation
People, rules, activity calendar, place, and community outcomes arrives before the CTA, making action a reasonable consequence of the story rather than an interruption.
Colour system
#182840
#001028
#404858
#706060
#f09048
Colours come directly from STRIDE's art direction. Production should validate WCAG contrast for copy, interaction states, and charts instead of assigning every colour equal weight.
Production direction
Turn the concept into a system with content, data, and clear ownership.
The visual design is an opening hypothesis. A live version must be tested with real content, real behaviour, and the technical constraints of the team that will maintain it.
- 01
Inventory content and data
Identify the source, update cadence, and approver for people, rules, activity calendar, place, and community outcomes before finalising page architecture.
- 02
Prototype the primary flow
Test “See the calendar, choose a programme, and become a member” on real devices, including missing data, failure, and interrupted-return states.
- 03
Performance and access
Serve images at display size, preserve semantic HTML, support keyboard use, and respect reduced motion so the experience does not require powerful hardware.
- 04
Measure what matters
Track calendar views, trial registrations, and returning members, exclude internal traffic, and agree event definitions before interpreting results.
Frequently asked questions
Questions to resolve before producing STRIDE.
- Who is STRIDE designed for?
- Newcomers assessing culture, schedule, and fit before joining. Every layout decision serves one primary action: see the calendar, choose a programme, and become a member.
- Why does this detail page differ from the other concepts?
- The product showcase treatment follows how people explore a membership and community platform, its information density, and its particular visual language.
- Could the concept become a real website?
- Yes, after replacing assumptions with real content, data, legal requirements, and the organisation's “See the calendar, choose a programme, and become a member” process.
- How should effectiveness be measured?
- A useful starting set is calendar views, trial registrations, and returning members; final targets must follow the real operating model.
Continue exploring
More concepts in the field, each with a different answer.
From concept to product
Have an idea that needs to become a real website?
ToanKhonTech can shape positioning, content architecture, conversion flow, and an interface system for your actual context—without copying a fictional concept wholesale.