1. Account
Give PluralBridge the account and membership foundation needed before private System data can be saved or edited.
What PluralBridge is building
A browser-based place for preserved Simply Plural data to land.
PluralBridge is moving from emergency preservation toward the first browser-based release. The current focus is the release spine: account setup, Simply Plural import preview before saving, and member profiles that can be viewed, added, and updated.
Once that spine is complete, the public Preview can open without sending users to an old proof-of-concept or asking anyone to risk private System data.
Preview is intentionally gated.
The public Preview should open after the first release spine is ready: account setup, import review, and editable member profiles.
Until then, PluralBridge is not asking users to upload exports, enter tokens, send screenshots, or move private System data into the project.
The first release spine
- Account: establish who is using PluralBridge.
- System and membership: establish what System the account belongs to and what access it has.
- Import preview: let users review a preserved Simply Plural export before anything is saved.
- Member profiles: let users view, add, and update member profiles in the browser.
- Privacy boundary: keep private System data under clear user control.
Why this comes first
Account and import complete the project spine. After that, PluralBridge has the core shape of a real replacement path: a user can sign in, connect to a System, review preserved data, and work with member profiles.
Later features can build outward from that foundation instead of trying to compensate for a missing spine.
What the first release should do
- Run in a modern web browser.
- Support account setup and sign-in.
- Resolve account, System, and membership access.
- Let users review a Simply Plural export before saving anything.
- Show member profiles in a readable browser view.
- Let users add and update member profiles.
- Avoid exposing private System data through public examples, logs, screenshots, or support paths.
2. Import preview
Inspect preserved Simply Plural export data before importing it into PluralBridge.
3. Member profiles
View, add, and update member profiles in the browser after data has somewhere to land.
Why browser-based
A browser-based release can run on Windows, Mac, Linux, phones, tablets, and anything else with a modern browser. That matters because plural Systems should not need one specific device type or operating system to reach preserved data.
Browser-based does not mean careless with privacy. The PluralBridge path still needs deliberate import, explicit review, account boundaries, membership checks, and clear control over System data.
What comes after the spine
Once account, import, and member profiles are coherent, later work can build outward: stronger privacy controls, richer import coverage, groups, notes, avatars, fronting history, delete and retention behavior, audit reporting, account lifecycle cleanup, and compatible interfaces where feasible.
That is why the current development priority is account and import.
How to help
PluralBridge needs developers, reviewers, testers, documentation helpers, accessibility reviewers, security-minded contributors, and privacy-minded contributors.
Use synthetic data for public project work. Do not send or publish real exports, tokens, screenshots, notes, member records, avatars, fronting history, logs, database files, or private System data.