{"id":107,"date":"2026-01-20T16:41:52","date_gmt":"2026-01-20T16:41:52","guid":{"rendered":"https:\/\/help.ministrycentral-europe.org\/?post_type=epkb_post_type_1&p=107"},"modified":"2026-01-20T16:41:52","modified_gmt":"2026-01-20T16:41:52","slug":"content-editor-playbook","status":"publish","type":"epkb_post_type_1","link":"https:\/\/help.ministrycentral-europe.org\/?epkb_post_type_1=content-editor-playbook","title":{"rendered":"Content Editor Playbook"},"content":{"rendered":"

MinistryCentral Europe<\/strong><\/p>\n

\n

1. Purpose of This Playbook<\/strong><\/h2>\n

This playbook defines how Content Editors operate day to day<\/strong> within MinistryCentral Europe.<\/p>\n

It exists to:<\/p>\n

    \n
  • Enable safe, confident editing<\/li>\n
  • Protect canonical authority<\/li>\n
  • Ensure consistency across documentation<\/li>\n
  • Reduce ambiguity and escalation fatigue<\/li>\n<\/ul>\n

    If you are a Content Editor, this document describes how you work<\/strong>, not just what you are allowed to do.<\/p>\n

    \n

    2. The Content Editor Role (In One Sentence)<\/strong><\/h2>\n

    Content Editors transform reviewed drafts into clear, consistent, canonical documentation \u2014 without changing meaning, authority, or intent.<\/p><\/blockquote>\n

    Editors are stewards of clarity<\/strong>, not authors and not decision-makers.<\/p>\n

    \n

    3. What Content Editors Own<\/strong><\/h2>\n

    Content Editors are responsible for:<\/p>\n

      \n
    • Clarity and readability<\/li>\n
    • Structural coherence<\/li>\n
    • Terminology consistency<\/li>\n
    • Alignment with existing canonical documents<\/li>\n
    • Preparing content for canonical publication<\/li>\n
    • Maintaining editorial standards over time<\/li>\n<\/ul>\n

      Editors ensure documentation is understandable, navigable, and trustworthy<\/strong>.<\/p>\n

      \n

      4. What Content Editors Do NOT Own<\/strong><\/h2>\n

      Content Editors do not<\/strong> own:<\/p>\n

        \n
      • Governance decisions<\/li>\n
      • Canonical definitions<\/li>\n
      • Policy creation<\/li>\n
      • Course design<\/li>\n
      • Instructor relationships<\/li>\n
      • Platform configuration<\/li>\n
      • Publication authority beyond delegated scope<\/li>\n<\/ul>\n

        If a change alters meaning, scope, authority, or policy<\/strong>, it must be escalated.<\/p>\n

        \n

        5. Where Content Editors Work<\/strong><\/h2>\n

        Primary Workspace: Notion<\/strong><\/h3>\n
          \n
        • Draft refinement<\/li>\n
        • Structural cleanup<\/li>\n
        • Editorial comments<\/li>\n
        • Status tracking (Draft \u2192 Review \u2192 Approved)<\/li>\n<\/ul>\n

          Canonical Workspace: Echo Knowledge Base<\/strong><\/h3>\n
            \n
          • Final publication<\/li>\n
          • Minor non-substantive corrections<\/li>\n
          • Maintenance following Change Management Rules<\/li>\n<\/ul>\n

            Editors do not treat Echo KB as a drafting environment.<\/p><\/blockquote>\n

            \n

            6. Editorial Workflow (Step by Step)<\/strong><\/h2>\n

            Step 1 \u2014 Intake<\/strong><\/h3>\n
              \n
            • Content arrives via Notion, Word, or handoff<\/li>\n
            • Status: Draft<\/strong><\/li>\n<\/ul>\n

              Step 2 \u2014 Editorial Pass<\/strong><\/h3>\n

              Editors focus on:<\/p>\n

                \n
              • Headings and flow<\/li>\n
              • Paragraph clarity<\/li>\n
              • Redundancy removal<\/li>\n
              • Terminology alignment<\/li>\n<\/ul>\n

                Meaning and intent must be preserved.<\/p>\n

                \n

                Step 3 \u2014 Alignment Check<\/strong><\/h3>\n

                Verify:<\/p>\n

                  \n
                • No contradiction with canonical documents<\/li>\n
                • Terminology matches existing standards<\/li>\n
                • Scope is appropriate for intended audience<\/li>\n<\/ul>\n

                  Conflicts must be escalated.<\/p>\n

                  \n

                  Step 4 \u2014 Approval Readiness<\/strong><\/h3>\n

                  Before marking Approved<\/strong>, confirm:<\/p>\n

                    \n
                  • Open questions resolved<\/li>\n
                  • Ownership is clear<\/li>\n
                  • Canonical placement is obvious<\/li>\n
                  • Formatting aligns with KB standards<\/li>\n<\/ul>\n
                    \n

                    Step 5 \u2014 Canonical Publication<\/strong><\/h3>\n
                      \n
                    • Content is copied into Echo KB<\/li>\n
                    • Categories and structure applied<\/li>\n
                    • Links verified<\/li>\n
                    • Publication is intentional and deliberate<\/li>\n<\/ul>\n

                      After publication, the KB version becomes canonical<\/strong>.<\/p>\n

                      \n

                      7. What Editors May Change Directly<\/strong><\/h2>\n

                      Editors may directly edit:<\/p>\n

                        \n
                      • Grammar and spelling<\/li>\n
                      • Formatting and layout<\/li>\n
                      • Headings and structure<\/li>\n
                      • Sentence clarity<\/li>\n
                      • Non-substantive clarifications<\/li>\n<\/ul>\n

                        These changes must not alter meaning or authority<\/strong>.<\/p>\n

                        \n

                        8. What Requires Escalation<\/strong><\/h2>\n

                        Always escalate if a change:<\/p>\n

                          \n
                        • Alters meaning or intent<\/li>\n
                        • Introduces policy or authority<\/li>\n
                        • Changes scope or audience<\/li>\n
                        • Affects governance or workflow<\/li>\n
                        • Contradicts another canonical document<\/li>\n<\/ul>\n

                          Escalation is expected and protective.<\/p>\n

                          \n

                          9. Common Editorial Pitfalls<\/strong><\/h2>\n
                            \n
                          • \u274c \u201cJust fixing a small thing\u201d in canonical docs<\/li>\n
                          • \u274c Publishing without alignment checks<\/li>\n
                          • \u274c Assuming intent instead of clarifying<\/li>\n
                          • \u274c Optimizing style at the cost of accuracy<\/li>\n
                          • \u274c Editing governance documents casually<\/li>\n<\/ul>\n

                            When in doubt: pause and escalate<\/strong>.<\/p>\n

                            \n

                            10. Editorial Mindset<\/strong><\/h2>\n

                            Effective Content Editors:<\/p>\n

                              \n
                            • Value clarity over cleverness<\/li>\n
                            • Prefer consistency over creativity<\/li>\n
                            • Optimize for future readers<\/li>\n
                            • Leave clear decision traces<\/li>\n
                            • Protect the system quietly<\/li>\n<\/ul>\n

                              Success is measured by trust and stability<\/strong>, not speed.<\/p>\n

                              \n

                              11. Relationship to Other Documents<\/strong><\/h2>\n

                              Content Editors must be familiar with:<\/p>\n

                                \n
                              • Content, Platform & Documentation Operations Guide<\/strong><\/li>\n
                              • Documentation Workflow<\/strong><\/li>\n
                              • Status Lifecycle & Canonical Rules<\/strong><\/li>\n
                              • Notion \u2192 KB Publishing Rules<\/strong><\/li>\n
                              • Formatting & Style Guidelines<\/strong><\/li>\n
                              • Change Management Rules<\/strong><\/li>\n<\/ul>\n

                                This playbook operationalizes those documents \u2014 it does not replace them.<\/p>\n

                                \n

                                12. Acknowledgement<\/strong><\/h2>\n

                                Content Editors are required to:<\/p>\n

                                  \n
                                • Read this playbook fully<\/li>\n
                                • Follow it consistently<\/li>\n
                                • Acknowledge completion during onboarding<\/li>\n<\/ul>\n

                                  <\/p>\n","protected":false},"excerpt":{"rendered":"

                                  MinistryCentral Europe 1. Purpose of This Playbook This playbook defines how Content Editors operate day to day within MinistryCentral Europe. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"epkb_post_type_1_category":[3],"epkb_post_type_1_tag":[],"class_list":["post-107","epkb_post_type_1","type-epkb_post_type_1","status-publish","hentry","epkb_post_type_1_category-ops_contrib"],"_links":{"self":[{"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=\/wp\/v2\/epkb_post_type_1\/107","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=\/wp\/v2\/epkb_post_type_1"}],"about":[{"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=\/wp\/v2\/types\/epkb_post_type_1"}],"author":[{"embeddable":true,"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=107"}],"version-history":[{"count":1,"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=\/wp\/v2\/epkb_post_type_1\/107\/revisions"}],"predecessor-version":[{"id":108,"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=\/wp\/v2\/epkb_post_type_1\/107\/revisions\/108"}],"wp:attachment":[{"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=107"}],"wp:term":[{"taxonomy":"epkb_post_type_1_category","embeddable":true,"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=%2Fwp%2Fv2%2Fepkb_post_type_1_category&post=107"},{"taxonomy":"epkb_post_type_1_tag","embeddable":true,"href":"https:\/\/help.ministrycentral-europe.org\/index.php?rest_route=%2Fwp%2Fv2%2Fepkb_post_type_1_tag&post=107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}