Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
Developer Documentation
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 74
    • Issues 74
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Documentation
  • Docs
  • Developer Documentation
  • Issues
  • #501

Closed
Open
Opened Mar 22, 2018 by Michael McAndrew@michaelmcandrewDeveloper

Reference Flexmailer in CiviMail documentation

"FlexMailer (org.civicrm.flexmailer) is an email delivery engine for CiviCRM v4.7+. It replaces the internal guts of CiviMail. It is a drop-in replacement which enables other extensions to provide richer email features."

Flexmailer has fairly comprehensive documentation here: https://docs.civicrm.org/flexmailer/en/latest/ but it is not mentioned in https://docs.civicrm.org/dev/en/latest/framework/civimail.

Given that Flexmailer is designed to be the future of mail in CiviCRM, and the place where developers should be focusing their efforts (rather than hacking CiviMail) we should reference the flexmailer documentation in https://docs.civicrm.org/dev/en/latest/framework/civimail and let people know that they should focus their efforts there.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: documentation/docs/dev#501