This is the direction of the project, not a contract. Features start as issues. See GOVERNANCE.md for how scope is decided.
- Private bookmark library in a Manifest V3 popup (title, URL, category, tags)
- Collections, with add/edit/delete from the popup
- Accounts in the popup (register, sign in, profile, password, delete)
/api/v1JSON API with Bearer JWT- Automated API tests (
node --test) for auth, bookmarks, and collections, running in CI - Light and dark theme
- Product landing page and privacy policy
- Chrome Web Store
- Microsoft Edge Add-ons
Work that would help the project most, in no strict order:
- Test coverage reporting — a baseline and a documented way to run coverage locally
- Clearer empty and error states in the popup, labeled as
good first issuewhen they are small enough - Token handling — shorter-lived JWTs or a revocation path (see security-audit.md)
- Self-hosted API URLs —
optional_host_permissionsso a custom host does not require a rebuild - Contributor onboarding — keep
good first issueitems specific (file paths and acceptance criteria)
These need an issue and a design discussion before a PR:
- Search and filter across bookmarks
- Import / export a personal library
- Keyboard shortcuts in the popup
- Firefox, if MV3 APIs and store review stay aligned with Chrome/Edge
Curate stays private. A public feed or social sharing is out of scope unless that decision changes in an issue.