Education Team

The Education Team is responsible for the Forum, Mautic Documentation and Internationalization. The team’s mission is to keep the forum clean and constructive, the documentation to be of high quality; understandability and accurate, and to ensure multilingual availability.

Missions and expectations

To improve the resources available for new and established users to learn how to use Mautic

General Tasks

  • Help marketers to contribute their existing content to the Mautic Knowledgebase
  • Ensure that the documentation is up to date when new releases are made
  • Improve the experience of Mautic users by ensuring that the documentation is of high quality and comprehensive
  • Moderate the Mautic Community Forums and provide content to answer FAQs
  • Improve the resources available for new and established users to learn how to use Mautic

Forum

  • Quality of contributions

    • Are the answers to asked questions correct? (ensure they are marked as a solution)
    • Is it an often asked question? → Add to documentation
    • Are there multiple posts about the same thing? → Merge into a mega-post
  • Forum Rules

    • Which rules are appropriate
    • Which rules are relevant / needed to keep the forum working fine
  • Moderate Forum / Assign Moderators

    • Moderate posts by themselves
    • Elect moderators who moderate the forum for them
  • Redirect all Support questions from Slack to Forums

    • Very visible hint in Slack (how? “Pinned message”, Slackbot, …?)
    • Manually moderating Slack & moving stuff to forums
    • Automatically moving stuff to forums?

Documentation

  • Sources

    • User Documentation describes key concepts of Mautic and provides instructions for using and contributing to Mautic.
    • Knowledgebase provides a database of tutorials, FAQs, and how-to articles.
    • Developer Documentation details about the Mautic API, Webhooks, themes and plugin development.
    • Community Handbook central point of call for how the Mautic community is organised and managed.
  • Quality

    • Maintaining a high quality
    • Review accuracy of the documentation
    • Keeping it easy to understand
  • Completeness

    • Add missing topics to the documentation
      • Proactively reviewing site/google searches and identifying topics to write if there are missing areas
      • Manage issue queue on Github.com/mautic/documentation and github.com/mautic/developer-documentation
    • Adding highly requested forum questions
  • Up to date

    • Ensuring that the documentation is kept up to date with major releases
    • Document changes coming with those releases
    • Merge PR’s when they come in for new features
  • Languages

    • Keeping native translations accurate (FR/JP)
    • If necessary add more translations
  • Style Guide

    • The Mautic Style Guide recommends best practices that aims to bring about a consistent style, voice, and tone across all documentation
    • Any Technical Writer (or other contributor) can make suggestions for documentation style updates

    Educational blog content

  • Curating and writing content to be used in the community blog

  • Cuarting and writing how-to articles, tutorials for Mautic Knowledgebase

    Mautic app (and website/marketing?) internationalization

  • Own Transifex and appropriate workflows

  • Manage multilingual marketing materials (e.g. website, fliers, etc)

  • Work tightly with Community, Product and Marketing teams

Profiles of contributors needed in this team

We need insights from:

  • New users
  • Established users
  • Administrators
  • Developers
  • Theme builders
  • Business owners considering Mautic
  • Business buyers/procurements

We need people with skills as:

  • Trainers
  • Marketers
  • Video producers
  • Content creators
  • Documentation writers
  • Editors
  • Translators

Would you like to be involved in this team? Join #t-education on Slack!

Found errors? Think you can improve this documentation? edit this page