Torah Tree
Build knowledge together.
Hobby & exploration
The problem
Collaborative Torah writing needs more than a shared text box. Several editors may work at once, sources and discussions need to stay attached to the relevant text, and unfinished work must remain separate from what visitors can read.
Hebrew navigation, a deep topic hierarchy, searchable content and recoverable publication history add constraints across both the editing experience and the underlying data.
The solution
Torah Tree combines real-time collaborative editing with a structured topic tree, anchored citations and inline discussion. Editorial roles and a draft-to-review-to-publication workflow determine who can change material and when it becomes public.
Published versions retain authorship and change history and can be restored. Hebrew-aware search and server-rendered public pages connect the editorial workspace to discoverable reading content, while the collaboration engine merges concurrent edits.
The decisions behind it
- Collaboration versus publication
- Being able to edit together does not mean every change should immediately become public. Review is a separate stage.
- Sources stay in context
- Citations and discussions refer to particular passages, while the surrounding document continues to change.
- History remains recoverable
- Published snapshots, authors and differences make revision an accountable process rather than a replacement of the previous text.
- Live collaborative writing
- Hierarchical knowledge navigation
- Editorial roles and publication review