Primary role
Public movement surface Frames the movement, membership path, community structure, and member benefits.About Prosper Movement
A grassroots member organization with practical ambitions.
Prosper Movement is intended to be the member-organization expression of the wider Prosper ecosystem: local-community-first, foundation-aligned, and willing to use aligned software as practical movement capacity rather than treating technology as a separate world.
Guiding posture
Ground the movement locally, connect it responsibly, and keep it useful.
- Keep the movement grounded in real local communities rather than abstract online allegiance.
- Use regional and national structure to support local action, not dominate it.
- Let the Prosper Foundation carry the wider declaration and larger stewardship burden.
- Treat member access to ProsperApps tools as a genuine practical benefit, not decorative marketing copy.
- Build digital systems that help people participate more effectively without forcing lock-in or exclusionary identity rules.
Position in ecosystem
Movement + foundation + product bridge This surface sits between Prosper Foundation stewardship and ProsperApps-enabled practical member capacity.Shared stewardship
Prosper Foundation
Prosper Movement is intended to work directly with Prosper Foundation, especially around the movement’s deeper purpose, declaration alignment, and larger stewardship posture. The site should therefore make that relationship explicit rather than presenting the movement as a detached campaign brand.
Declaration
Declaration and commitments
This public movement surface should still show its stack, licences, standards, and contribution paths. The point is not just movement messaging, but a concrete demonstration that public-facing surfaces in the ecosystem disclose how they are built and where people can contribute.
Movement infrastructure
Why ProsperOrg matters here
Prosper Movement is also a concrete future operating environment for the ProsperOrg platform. That makes the site more than a communication surface; it is part of a larger plan for how chapters, members, roles, dues, events, and community operations can be supported.
Licences & standards
External dependencies, derived assets, and open standards
Every item should link to the relevant licence file, project page or repository, and contribution path so provenance and participation stay visible.
Application stack 5 items
Core open-source frontend stack used to build and host the public movement site.
Resource
Svelte
Component runtime used for the movement site interface.
Resource
SvelteKit
Routing and app-shell framework for the public movement pages.
Resource
TypeScript
Typed content structures and route metadata for the site.
Resource
Vite
Development and build tooling for the movement site.
Resource
Wrangler
Cloudflare deployment tooling used for preview and hosted releases.
Open standards 3 items
Web platform standards that materially shape the movement site and its interoperability.
Resource
HTML
Baseline document structure, navigation, and semantic page layout.
Resource
CSS Custom Properties
Used for shared visual tokens and theme composition.
Resource
SVG
Used for the movement mark and vector-based illustrative assets.
Next step