Rogue Valley Now is an independently owned community-information project. It is not a paying client reference or a commissioned municipal website. This record separates owner-supplied context from a dated public-interface inspection.
Proof / owned work
Rogue Valley Now: start with the task.
Owned community-information project. This example examines three distinct entrances: find a dated event, choose an activity, or explore a town.
01 / Proof / owned work
Independently owned work
02 / Proof / owned work
Give different intentions different entrances
The inspected homepage offers a town/date event choice, activity-guide links and a broader idea/town path. Its community-information purpose is owner-supplied; these specific entrances were visible in the public interface.
Reference: Rogue Valley Now: inspected owned project
03 / Proof / owned work
Keep place and time in the content model
Local information has geographic and date context. A reader looking for an event on a particular day has a different task from someone comparing an activity or finding a local resource. The page exposes those distinctions instead of asking every reader to begin with one broad search.
04 / Proof / owned work
Keep attribution precise
| Item | Evidence basis | Limit |
|---|---|---|
| Ownership and broad purpose | Supplied by the owner: independently owned community information, events and practical resources | No municipal commission, client endorsement or business-result claim. |
| Interface and information structure | Public routes and visible content inspected on 21 October 2026 | Observation does not establish all backend behavior, accessibility or completeness. |
| Individual design/code/content credits | No granular credit ledger asserted here | Do not infer that every asset, source or third-party service was created by one person. |
| Photography and outside information | Project pages identify or link their relevant sources | Those underlying rights and authors are separate from ownership of the website. |
05 / Proof / owned work
Inspect the actual route choices
| Entrance | Visible choice | Actual destination / artifact |
|---|---|---|
| Task-led homepage | Town and date controls plus activity and idea paths | Rogue Valley Now homepage |
| Dated event route | An event hub and today-oriented shortcut | Event hub |
| Geographic route | Town/community index grouped by county | Community guides |
06 / Proof / owned work
Examine the visible design choice and its trade-off
| Choice | Useful property | Trade-off |
|---|---|---|
| Three question-led entrances | Lets the reader choose by intent before browsing the full information set | The page must keep labels distinct and avoid duplicating confusing paths. |
| Town and date as explicit dimensions | Makes the requested event context visible | Controls, URL state and empty results require their own ongoing verification. |
| Original-source handoffs | Keeps current details tied to the responsible source | An external destination can change; no claim of complete real-time coverage. |
07 / Proof / owned work
Separate a visible feature from a measured outcome
| Evidence level | What this record can say | What it cannot say |
|---|---|---|
| Published | The linked public interfaces were inspectable on the stated date | Every page or external source is current and complete. |
| Observed | Specific headings, controls, destinations and source cues were visible | Full site certification or every error-state test. |
| Measured business outcome | No analytics baseline or outcome study is asserted | Traffic, revenue, savings, lead lift or causation. |
08 / Proof / owned work
Transfer the task structure, not the subject matter
A service website can distinguish “I know the job,” “help me compare” and “I need a specific answer” without turning every route into the same card. That is an information-design lesson; it does not prove advertising performance or an unrelated automation capability.
09 / Proof / owned work
Talk through a similar navigation problem
Use the actual customer tasks, content sources and acceptance checks to scope the website work.
For a different observed constraint or interface decision: Compare the other owned examples