MinistryCentral Europe
1. Purpose of This Guide
This guide explains how to contribute documentation safely and effectively to MinistryCentral Europe.
It is written for:
- General Contributors
- Subject-matter contributors
- Content Editors (as a refresher)
- Occasional helpers and reviewers
It is not a technical or governance manual.
Instead, it answers one core question:
“How can I help without breaking anything?”
2. How Documentation Is Structured (Quick Orientation)
MinistryCentral Europe documentation exists across three layers, each with a specific role:
1. Idea & Draft Layer
(Word, Notion, email, notes)
- Where ideas are formed
- Where drafts are created
- Safe place to write freely
2. Review & Preparation Layer
(Notion)
- Content is refined
- Structure and clarity are improved
- Nothing here is authoritative yet
3. Canonical Publication Layer
(Echo Knowledge Base — help.ministrycentral-europe.org)
- Single source of truth
- Official, approved documentation
- Referenced by the organization
❗ Publishing in Echo KB creates
canonical authority
Notion alone does not
3. Where Contributions Start
Most contributions begin in one of these ways:
- A Word document or Google Doc
- A Notion page or comment
- An email with content or ideas
- Notes from meetings or conversations
All of these are valid starting points.
You are not expected to:
- Publish directly to Echo KB
- Modify canonical documents
- Edit platform structure
4. What You May Change — and What You Must Not
You MAY:
- Draft new content
- Improve clarity or wording in drafts
- Suggest corrections or additions
- Comment on existing documentation
- Propose new articles or sections
You MUST NOT:
- Edit canonical KB articles directly (unless authorized)
- Change structure, titles, or categories in Echo KB
- “Quick-fix” documentation without review
- Assume approval based on good intentions
Golden rule:
If you’re unsure whether you should change something — don’t
Escalate instead.
5. Understanding Status: Draft → Canonical
All documentation follows a defined lifecycle:
- Idea – suggestion or concept
- Draft – written but not authoritative
- Review – evaluated by editors or leads
- Approved – cleared for publication
- Canonical – officially published in Echo KB
- Maintenance – updates follow the same process
Only Canonical documents are considered authoritative.
6. What Happens After You Submit Content
When you submit a contribution:
- A Content Editor reviews it
- Feedback may be requested
- Approved content is prepared for KB
- Canonical publication occurs in Echo KB
- Updates are tracked for future maintenance
You may or may not see your wording used verbatim — clarity and consistency take priority.
7. Common Mistakes to Avoid
- ❌ Editing “just a small thing” in the KB
- ❌ Assuming Notion equals publication
- ❌ Making structural changes without review
- ❌ Skipping the status lifecycle
- ❌ Bypassing editors to “save time”
These mistakes create silent inconsistency, which is far more costly than delay.
8. When to Escalate
Please escalate rather than act directly if your contribution involves:
- Governance or authority statements
- Structural changes to documentation
- Platform or tool instructions
- Canonical definitions
- Policies or official positions
Escalation is a feature, not a failure.
9. Acknowledgement & Completion
Once you have read and understood this guide:
👉 Please acknowledge completion using the link provided in your onboarding checklist.
This helps ensure shared understanding and protects the integrity of the system.
Final Word
MinistryCentral Europe values helpful contribution, but it values clarity and consistency even more.
This guide exists so that:
- Contributors feel safe helping
- Editors can move quickly
- Canonical documentation remains trustworthy
Thank you for contributing thoughtfully.