Skip to content

PRD: calitp.org #471

Description

@leelas-pm

Overview

CA Mobility Marketplace (MobiMart) is currently in the process of a redesign to better represent the needs of its' users, including a significant overhaul of the information architecture. As its counterpart, calitp.org will likely need to adapt in some small ways alongside MobiMart to ensure a cohesive web presence for Cal-ITP.

Problem

Much moreso than MobiMart, Calitp.org is temporary. It should be flexible enough to accommodate changes to Cal-ITP, and it is also likely the information on calitp.org will eventually be dispersed and diffused across various Caltrans sites. Making significant changes to the existing site it not a good investment given its inherent transient nature. At the same time, it is currently the only place we have to quickly upload live links to Cal-ITP stakeholders for resources such as case studies, one-pagers, and toolkits as they arise.

Given it's temporary status, it doesn't make sense to invest too much into calitp.org's design and information architecture in the same way as MobiMart, which will have a life as its own web-presence longer-term. However, there is still a need to keep it updated and equipped to best serve the evolving needs of Cal-ITP.

High-Level Approach

Moving forward, calitp.org will return more to its original intention: a "living press release" or splash page. It's primary purpose is to tell the story of Cal-ITP, answering the question: "What is Cal-ITP and what has it done to achieve its goals?"

The audience for this site is primarily legislators and media, with some secondary interest in the following groups: higher-ups within Caltrans who might need a refresher on Cal-ITP, the general public, and out of state/non-CA transit agencies who may be interested in our model and accomplishments.

It should primarily house press releases, case studies, and news items. It should NOT house tools or resources created specifically to support transit agencies. Those belong on MobiMart.

Goals

  1. Simplify the site down to its original purpose/use case
  2. Reduce number of documents required to be included in "Resources" to align only with the intended audience for calitp.org (legislators, media, general public) and put in place a plan for transitioning any agency-specific content to MobiMart
  3. Set up guidance and strategy aligned with comms review process to maintain separation between documents/resources prepared for agencies vs. the general public

Non-Goals

  • Full redesign
  • No additive features (e.g. new information architecture, new pages, etc.)

Metrics

TBD. Discovery in progress.

User stories

As a legislator or lobbyist, I would like to easily access case studies, press releases, and reports that support the aims of transit advocacy in Caliornia.

As a Caltrans or CalSTA executive, I need a high-level overview of the goals and achievements of Cal-ITP I can reference for internal communications.

As a member of the general public, I need a simple, easy to navigate website that provides a high level overview of the goals and achievements of Cal-ITP.

As a transit agency outside of CA, I would like to understand more about how California is approaching modernizing public transit.

Timeline

TBD. Target Q2 for further conversations and planning.

Future considerations

  • Ease of transition/handoff for dispersal of calitp.org content to other Caltrans locations.

Key challenges and considerations

  • calitp.org is a temporary website, and therefore operates with a set of constraints that may not solve near-term problems.
  • Timeline for maintenance of calitp.org is undetermined - we do not yet know when it will be sunset.

Reference

Key milestones

TBD.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    initiativeA high-level contextual issue that organizes all the sub-issues to complete it

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions