What Is NoteVault for Project Documentation?
NoteVault is GitScrum's project-linked documentation system with revision history. Keep technical docs, meeting notes, and decisions directly connected to your project board.
3 min de lecture
What is NoteVault for project documentation?
NoteVault is GitScrum's built-in documentation feature that stores project notes with full revision history. Unlike separate wiki tools, NoteVault lives inside your project, ensuring documentation stays connected to actual work. It supports rich text, visibility controls (public/private), and tracks all changes with author attribution [Source: GitScrum Documentation].
NoteVault features
| Feature | Description |
|---|---|
| Rich text editor | Format docs with headers, lists, code blocks |
| Revision history | Track all changes with timestamps |
| Author attribution | See who changed what |
| Visibility controls | Public or private notes |
| Project-linked | Lives inside your project |
| Searchable | Find notes quickly |
What to store in NoteVault:
Why integrated documentation works better
| Separate Wiki | NoteVault |
|---|---|
| Different tool, different login | Same tool as tasks |
| Easy to forget to update | Natural to update alongside work |
| Disconnected from context | Linked to project |
| No revision tracking in PM tool | Full history |
| Teams stop using it | Teams actually use it |
| 40% docs become stale in 6 months | Stays current with project |
How to organize NoteVault notes
| Category | Notes |
|---|---|
| Getting Started | Setup guide, access instructions |
| Architecture | System overview, ADRs |
| Processes | Development workflow, review guidelines |
| Technical | API docs, database schema |
| Operations | Runbooks, deployment |
| Meetings | Sprint notes, retros |
NoteVault best practices
- One note per topic - Keep notes focused
- Update during work - Don't wait until later
- Use descriptive titles - Searchable names
- Review quarterly - Check for stale content
- Assign owners - Each doc has a maintainer