angelandClaude Sonnet 5
b9dd4fc0e5
README had drifted: an unresolved merge-conflict marker left over from a past edit, a directory-structure diagram that no longer matches the repo (/internal/site, /internal/domains/platforms/tiktok - actual layout is server/, domains/, etc per AGENTS.md), and a duplicated dev-workflow blurb that AGENTS.md already documents more accurately. Splits the roadmap checklist out to ROADMAP.md and the Etsy API compliance checklist to domains/platforms/etsy/COMPLIANCE.md (next to the code it governs, where someone touching that integration will actually look for it) instead of burying both in one large README. README itself becomes a short front door with a "Where things live" index up top, since scattering docs across files only helps if there's an obvious map to them. Moves the CQRS/event-sourcing architecture note into AGENTS.md's Architecture section (with a new domains/raw_events bullet) rather than leaving it as prose in README, since AGENTS.md is the maintained engineering reference and that's where a reader would already be looking for how the domains are structured. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
39 lines
2.1 KiB
Markdown
39 lines
2.1 KiB
Markdown
# Roadmap
|
|
|
|
- [ ] Etsy (WIP)
|
|
- [ ] GET ETSY AUTH (WIP)
|
|
- [x] move auth state stuff to database (out of cache)
|
|
- [x] only generate a sign up link IF they click the link on the accounts page
|
|
- [ ] get api key approved
|
|
- [ ] automatically clean up access tokens and state when expired
|
|
- [ ] access tokens
|
|
- [ ] state
|
|
- [ ] account-creation page ahead of OAuth (force users to create an account before connecting a store)
|
|
- [ ] collect billing information as part of that account-creation flow
|
|
- [?] Get new access token using refresh token flow
|
|
- [ ] make a FK between the etsy_store_events table and etsy_users table (store_id columns don't match types)
|
|
- [ ] build polling-based order/inventory sync against the live Etsy API - only the OAuth connection flow is implemented so far (see `research/platforms.md`'s Etsy notes: API v3 has no webhook/push system, so this has to be a poll loop)
|
|
- see `domains/platforms/etsy/COMPLIANCE.md` for Etsy API usage obligations to keep satisfied along the way
|
|
- [ ] Auth0
|
|
- [ ] get off dev api key?
|
|
- [x] Get new access token using refresh token flow
|
|
- [ ] test
|
|
- [x] when token is expired, redirect them to the login page, then redirect them back to where they were heading to.
|
|
- [ ] Social connections login
|
|
- [x] automatically clean up access tokens and state when expired
|
|
- [x] access tokens
|
|
- [x] state
|
|
- [ ] Complete this design document?
|
|
- [ ] Complete defining this roadmap checklist
|
|
- [ ] Website displaying an audit of store events
|
|
- [ ] Start with just a list of events for a given store (use a static test store)
|
|
- [ ] ...
|
|
- [ ] Dark mode
|
|
- [ ] don't let a listing be in multiple sync groups
|
|
- [ ] Next platform to build out beyond Etsy - see `AGENTS.md`'s "Platform integration priority" section for the researched, weighted ranking (currently: Shopify, then Amazon, then Tiktok Shop) instead of picking from the raw platform list
|
|
|
|
## Nice to haves
|
|
|
|
- [ ] Drop in a good logger
|
|
- [ ] log all errors caught by the http server
|