MinistryCentral Europe
Below is a role-segmented “Introductory Course Guide”, to be:
- Published in Echo KB (Operations & Contributors)
- Used as a self-paced onboarding path
- Referenced by team leads when onboarding new contributors
- Extended later into short Loom walkthroughs or checklists
This is a single master guide, followed by role-specific learning paths.
Contents
- Purpose of This Guide
- How to Use This Guide
- Universal Orientation
- Role-Based Learning Paths
- Learning Philiosophy
- How This Guide Evolves
- Summary
Introductory Operations & Contribution Guide
(Role-Based Learning Paths)
1. Purpose of This Guide
This guide helps contributors, administrators, and creators understand how MinistryCentral Europe operates, what documents matter to them, and in what order they should read them.
It is intentionally role-based:
- Not everyone needs to read everything
- No one should be overwhelmed
- Each role has a clear, minimal learning path
You are not expected to master the whole system—only the part you touch.
2. How to Use This Guide
- Identify your role (or closest match)
- Follow the learning path in order
- Stop when your role’s path ends
- Bookmark the remaining documents for reference only
Each document listed below is part of the Operations & Contributors section of the Knowledge Base.
This Operations Guide provides orientation and context. It does not replace the canonical governance documents listed above.
3. Universal Orientation
All contributors must read these first, in order.
Step 1 — Operating Model & Authority
📄 Content, Platform & Documentation Operations Guide
Why:
Explains how the system works, where truth lives, and how decisions are made.
You will understand:
- What is canonical (Echo KB)
- What Notion is for
- How content flows from idea to publication
- Why guardrails exist
Step 2 — Knowledge Base Structure
📄 How the Platform Works
Why:
Gives you a mental map of the system before you touch anything.
You will understand:
- User vs Operations documentation
- Where your work will appear
- How users experience the system
4. Governance Framework
MinistryCentral Europe documentation is governed by a small set of canonical documents that define authority, lifecycle, workflow, and change control.
For details, see:
- Canonical Authority Model
- Status Lifecycle & Canonical Rules
- Change Management Rules
- Documentation Workflow
5. Role-Based Learning Paths
A. General Contributors
(Occasional helpers, subject-matter contributors, reviewers)
Required Reading (in order)
- 📄 Operating Principles (Excerpt)Focus on:
- Canonical authority
- No silent changes
- Templates-first mindset
- 📄 Documentation Contribution GuideFocus on:
- How to contribute safely
- Word vs Notion vs KB
- What happens after you submit content
- 📄 Status Lifecycle (Draft → Published)Focus on:
- What “Approved” means
- When something becomes official
Optional
- 🎥 Loom: “How documentation moves from idea to KB”
You do NOT need to read:
- Technical governance
- CSS or Elementor rules
B. Content Editors
Required Reading (in order)
- 📄 Content, Platform & Documentation Operations Guide (full)
- 📄 Documentation Contribution Guide
- 📄 Content Editor Playbook
- 📄 Status Lifecycle & Canonical Rules
Focus Areas
- Editorial consistency
- When to edit Notion vs KB
- When changes must be escalated
- How to prepare content for publication
Optional
- 🎥 Loom: “Editing safely in Notion”
- 🎥 Loom: “Common KB cleanup mistakes”
C. Course Coordinators
Required Reading (in order)
- 📄 Operating Model & Authority
- 📄 LearnDash Content Strategy
- 📄 Course Coordinator Guide
- 📄 Video Usage Policy
Focus Areas
- Course structure vs lessons
- When to use video vs text
- Coordination with instructors
- Canonical expectations for learning content
Optional
- 🎥 Loom: “Course structure walkthrough”
D. Instructors / Teachers
Required Reading (in order)
- 📄 Instructor Orientation Guide
- 📄 Video Usage Policy
- 📄 Content Submission Basics
Focus Areas
- What you are responsible for
- What you are not expected to touch
- How your material is processed and published
- Where your content lives long-term
Optional
- 🎥 Loom: “Recording expectations & workflow”
Instructors do NOT need to read:
- Platform governance
- Notion database structure
- KB import mechanics
E. Media & Video Contributors
Required Reading (in order)
- 📄 Video Usage Policy
- 📄 Media Intake & Naming Standards
- 📄 Embedding & Referencing Video in Documentation
Focus Areas
- Loom vs Vimeo usage
- Ownership and lifecycle of video
- Naming conventions
- Where video is embedded vs referenced
F. Web Platform Lead
Required Reading (in order)
- 📄 Content, Platform & Documentation Operations Guide
- 📄 Platform & Technical Governance Guide
- 📄 Elementor Do / Don’t Guide
- 📄 Template & Structure Strategy
- 📄 Change Management Rules
Focus Areas
- Protecting system integrity
- Enabling others without risk
- Enforcing boundaries kindly but firmly
G. Technical Steward / Platform Administrator
Required Reading (in order)
- 📄 Platform & Technical Governance Guide
- 📄 Security, Backups & Performance Policy
- 📄 Plugin & Update Policy
- 📄 CSS Governance Rules
- 📄 Emergency & Rollback Procedures
Focus Areas
- Stability over speed
- Centralized authority
- Risk management
- System recoverability
6. Learning Philosophy
You are not onboarding into a toolset.
You are onboarding into a way of working in the team.
- Read only what your role requires
- Revisit documents as reference, not study
- Ask before improvising
- Trust the guardrails—they exist to help you
7. How This Guide Evolves
- Each section may gain short Loom walkthroughs
- Checklists may be added per role
- No role path should exceed 60–90 minutes total reading time
If a role requires more than that, the system is becoming too complex.
8. Summary (One Sentence per Role)
- Contributors: “I know how to help without breaking anything.”
- Editors: “I know what is canonical and when to escalate.”
- Instructors: “I teach; the system handles the rest.”
- Coordinators: “I manage flow, not technology.”
- Platform Leads: “I protect structure so others can move fast.”