Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(notes): Synced blocks & page version history

Open
#63 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
full-stack

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.

Description

enhancement help wanted

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.

Dominant language
TypeScript
Stars
2
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TemaDeveloper/personal_planner

All issues in TemaDeveloper/personal_planner

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.