TemaDeveloper / TemaDeveloper/personal_planner
feat(notes): Synced blocks & page version history
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Size: L — needs design spec.
Synced blocks (edit-once, appear-everywhere) and per-page version history/restore are the remaining heavyweight Notion features, explicitly parked as out-of-scope in the parity backlog and Notes-v2 spec, and not in #39–43.
Scope
File as one epic (or split): (a) synced blocks across pages; (b) per-page version history with restore. Each warrants its own design spec before implementation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Notes-v2 spec and parity backlog, then review issues #39–43 to understand what is already excluded. Define separate design specs for synced blocks across pages and per-page version history with restore; the work is ready when both specifications are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100