Prototype: https://github.com/opencollective/opencollective-frontend/pull/10383 Coda project: https://coda.io/d/Make-Open-Collective_dnHLKv7oLV0/All-Projects_suIYVd_a?searchClick=a29e9ce4-3115-4dfe-ad45-730d0c764d29_nHLKv7oLV0#Projects_tuqM3sx8/r266

Purpose

To deploy a clear and consistent URL approach for unique assets that can work both within and across dashboard and public pages.

Friction

Dashboard

The legacy architecture (before we created the dashboard experience) included public pages for expenses and contributions. These played a central role in both providing (through unique URL’s) a place for these assets and, before dashboard came along, a place for admins to engage with these assets.

However, since we’ve introduced dashboard both of these functions/needs have changed:

Admins (especially fiscal hosts but also collectives) primarily interact with these assets (and navigate between them) inside dashboard.
The remaining public pages have become outdated and are being reviewed and potentially restructured as part of the crowdfunding redesign campaign.

All this leads to a recurring friction that we’ve encountered in dashboard projects: when inside a dashboard (eg: a fiscal host admin) how to link to an asset within dashboard?

Crowdfunding Redesign

Crowdfunding redesign is leading to a review of public pages and their underlying URL structures.

White-labeling

The disassociation from OCI has brought us back to a conversation about enabling hosts and collectives to experience their profiles pages on their own domains.