Talking Drupal #512 - Member Platform

Today we are talking about The Member Platform, Why it was created, and How you can get involved with guest JD Leonard. We’ll also cover Profile as our module of the week.

For show notes visit: https://www.talkingDrupal.com/512

Topics

• Introduction to Member Platform
• Member Platform: Origin and Vision
• Member Platform Features and MVP
• Post-MVP Vision and Challenges
• SaaS Solutions and Drupal Forge
• CRM Project and Member Platform Vision
• Evaluating CRM Options
• Integrating External CRMs with Drupal
• Targeting Different Market Segments
• Current Progress and Future Plans
• Community Involvement and Contributions
• Getting Involved with Member Platform

Resources

• Member Platform
  • https://www.drupal.org/project/member
  • Drupal Slack #member-platform
  • Sign up for Member Platform news
• CRM
  • https://www.drupal.org/project/crm
  • Drupal Slack #crm
• Drupal forge
• Drupito
  • https://debugacademy.com/
  • https://drupito.com/
• Erpal
• CRM Core
• CIVICRM
• Contributors to Drupal Core

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi JD Leonard - jdleonard

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to store user information in one or more configurable profiles, independent of the user entity itself? There’s a module for that.
• Module name/project name:
  • Profile
• Brief history
  • How old: Project created in Oct 2015 by bojanz (boy-yan Z), but seems to originate in code that was in the 4.0.x branch of Drupal core. Recent releases are by Jonathan Sacksick (jsacksick) or Centarro
  • Versions available: 8.x-1.12, which supports Drupal 9, 10, and 11
• Maintainership
  • Actively maintained
  • Security coverage
  • Test coverage
  • Number of open issues: 125 open issues, 53 of which are bugs
• Usage stats:
  • 34,338 sites
• Module features and usage
  • Profiles are conceptually separate from the user account, and users will even edit their profile in a separate tab, which is a pretty common pattern
  • A site can have multiple profile types, and then use permissions and roles to determine who can create which kind of profile
  • Profile forms can optionally be shown during registration
  • Profile fields can also be set as private, meaning that the value will only be visible to the user and site admins
  • By default profiles will be displayed on the user’s view page, and this can be configured in the “Manage Display” tab on accounts
  • Profiles are also optionally revisionable
  • The project page also notes that profiles are not currently translatable, but there is an issue with a patch, so you can try that if it’s a requirement for you