Your account
HOL-D083Story implementation: In progress

Explore public organization pages

people · Proposed launch phase 2

Start from Home

Review as Visitor

User story

As a visitor, I want to explore public organization pages and their connected people and work so I can understand who is involved in the Backcountry community.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Read organization directory/detail/categories and currently public reciprocal relations from existing published backend projections. Use canonical work/place/event/person links and current consent; no stale static merge or private contact/claim/account identifiers.
  • Browse a public Organizations directory and filter by manufacturer/brand, gear outfitter, tour company, retailer or another clearly named organization category; one organization may have multiple categories.
  • Open a stable, person-independent organization page with approved name, logo/image, description, category, public business location or broad service area, website and relevant offerings. Optional fields may be absent without leaving broken sections.
  • Navigate approved relationships such as Guide → tour company and Athlete → brand in both directions. Show a meaningful label such as works with, guide at, supported by or event host; sponsorship is never inferred from a generic affiliation.
  • Open related published stories, galleries, videos, people, places and events from the organization page. Public profiles remain available while each linked item retains its own content entitlement, participation rules and commercial disclosure.
  • Find organizations through directory/category filters and universal search; results show approved public fields only and open the same canonical page. Organization search is new acceptance owned here, separate from the earlier Done search slice in D018.
  • Make website links clearly external; an offerings list describes the organization and does not create an in-app booking, retailer checkout or purchase commitment.
  • Provide loading, no-results, missing/unpublished profile and removed-affiliation states with a route back to discovery. A listed organization is not automatically a paid partner, verified expert or HOL endorsement.
  • Visitors browse without sign-in; follow prompts for a free account and returns to this organization. Verified registered users and paid members can follow/unfollow through D021; no trial or paid upgrade is needed for public profiles.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin on Visitor Home while signed out. If an account is active, use the account/workspace menu → Sign out. Public browsing does not require an account.

Navigation from public entry

  1. 01Begin on Visitor Home, without signing in.
  2. 02On the selected visitor Home use footer Explore → Organizations.
  3. 03Open Organizations using its canonical dev destination.

Feature checks start here

Public organization pages

Public-content reads are available for dev review; full story acceptance and stakeholder approval remain separate. Current public pages and supported account links are connected in dev. Only the visible workflow described here is available; credentials, privacy edge cases and unrelated editorial/operator workflows require separate acceptance and remain incomplete.

  1. 04From Home use footer Explore → Organizations. Filter organizations by category and use Search organizations; clear filters between examples.
  2. 05Open North Ridge Outfitters, Teton Meadow Guides and Alpine Field Co. Compare broad business areas, offerings, connected people and the independent-listing or fictional-event-partner disclosure.
  3. 06Follow connected work, events, people and places, preserving each content access gate. A sparse profile omits unsupported optional fields; private/unpublished pages must not become public search results.
  4. 07For a Visitor, Follow organization requests free registration; confirm the continuation returns to the exact organization. A verified free/paid account can follow directly and use Your Following to return to that organization.
  5. 08Ownership uses Manage organization for an authorized representative and Represent this organization? for an applicant. Those are separate from public discovery and following.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Selected authorization is the public read/content-seeding slice only. Existing write, participation, editorial management, event operations, gift redemption, payment and delivery requirements below are separate later work unless already authorized elsewhere.
  • Read organization directory/detail/categories and currently public reciprocal relations from existing published backend projections. Use canonical work/place/event/person links and current consent; no stale static merge or private contact/claim/account identifiers.
  • Store organization ID/slug, multiple allowed categories, approved descriptive fields, public business location/broad service area, external website, offerings and image references separately from private contacts, contracts and commercial partner records.
  • Serve only the current approved published organization revision in public detail, directory, search and place/event responses; reject drafts, private contacts, unpublished records and forged publication fields at the server.
  • Use versioned typed associations between canonical person/organization/content/place/event IDs, including relationship label, approval and withdrawal state. Validate relation targets and expose only public approved associations in each direction.
  • Index approved public fields and maintain stable URLs/redirect policy. Correct, merge or unpublish a record without orphaning credits or exposing stale/private cached fields; organization publicity never changes subscription entitlement.
  • Use D021 owner-scoped, idempotent organization follow/unfollow and authenticated return targets; public reads do not require an account. An organization record is not itself a login principal or permission role.

How to verify in dev

  1. Verify published-only anonymous projection, no private/protected payload, stable IDs and links, missing/unpublished records, empty/loading/error UI, and no silent static fallback. Idempotent seed rerun preserves edited records; authenticated/dummy Home entry remains unchanged.
  2. Browse/filter organization pages signed out and follow related people/work/place/event links; unavailable/unpublished targets must disappear or show a safe unavailable state.
  3. Read the same fictional organization as signed-out Visitor, verified free account and paid account; compare public fields and independent linked-content gates.
  4. Attempt direct API/search access to drafts/private fields and writes from an unrelated account; verify denial even when client role or URL is forged.
  5. Publish a revision, correct/withdraw an affiliation, unpublish the organization, then revisit detail/search/place/reverse-person links; verify a consistent approved result.
  6. Repeat follow/unfollow, reload and sign in after a Visitor prompt; verify one owner relationship and the intended return destination.

Before this can work

  • Begin on Visitor Home while signed out. If an account is active, use the account/workspace menu → Sign out. Public browsing does not require an account.
  • Use fictional examples for a manufacturer/brand, gear outfitter, tour company, retailer and another named organization type; include a multi-category example.
  • Include an independent non-sponsor listing, an explicitly disclosed sponsor, an unpublished record, withdrawn affiliation and public/premium linked-work examples.

Connected stories