- 2 minutes to read
Consistent documentation
New 7.11
Every team has the runbook nobody can read because it doesn't look like the others. With a Nodinite Document Profile, every Article in your knowledge base follows the same structure: the same header, the same sections in the same order, the same footer. Readers find the answer faster, and writers only fill in the parts that are actually theirs.
- ✅ Write an Article where the header, footer, and shared sections are already done
- ✅ Bring the Articles you already have into the same shape, without losing a word
- ✅ Change the structure once and every Article using it follows
The journey
Writing Articles? Start at task 1. Owning your team's documentation? Task 3 is yours.
| # | Task | You'll be able to |
|---|---|---|
| 1 | Write an Article from a Document Profile | Start a new Article with the structure in place, and write only your sections |
| 2 | Move an existing Article onto a Document Profile | Give an older Article the shared structure and keep all its text |
| 3 | Give every Article the same structure | Create your team's own Document Profile, starting from the ready-made example |
What your administrator sets up once
Nodinite ships with a ready-to-use Standard Technical Article Document Profile, so task 1 works from day one. Ask your administrator for:
| For task | Your administrator provides |
|---|---|
| 1, 2 | Access to the Articles pages of the Repository, via your Role |
| 3 | Create and Modify on Articles for your Role. Document Profiles, Templates, and Snippets (the shared sections a profile is built from) use the same Articles permissions, so nothing extra is needed. See Permission Set for the Repository Model |
Curious how it all works under the hood? The full reference is Document Profiles.