Talking Drupal: Talking Drupal #414 - Future of Web Content

Today we are talking about The Future of Content Management, What we see for Drupal in the future, and How AI might factor in with guest John Doyle. We’ll also cover Access Policy as our module of the week.

For show notes visit: www.talkingDrupal.com/414

• Digital Polygon
• Content Management can mean many things, what is our definition
• What factors contribute to the changes moving to a more centralized model
• How do organizations manage content for different channels
• Where do design systems collide with content management
• Why is Drupal a good fit
• How does headless fit in
• Maintaining content architecture long term
• Drupal adaptations over the next 5 years

• Talking Drupal #409 - Data Lakes
• Hey everyone! Our friends at the Linux Foundation are offering Talking Drupal Listeners 25% off on any e-learning course, certification exam or bundle. Good from August 22-Sept 30, 2023. With discount code LFDrupal25 Please note Bootcamps, ILTs and FinOps courses are excluded… Again that code is LFDrupal25 and you can use that at https://training.linuxfoundation.org/ Thank you to the linux foundation!
• Flexible Permissions

John Doyle - digitalpolygon.com _doyle_

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Andy Blum - andy-blum.com - andy_blum

Martin Anderson-Clutz - @mandclu Access Policy

• Brief description:
  • Does your Drupal site need a flexible way to manage access to content? There’s a module for that!
• Brief history
  • How old: created in Nov 2022
  • Versions available: 1.0.0-beta1, works with D9 and 10
• Maintainership
  • Actively maintained, most recent release was in the past week
• Number of open issues:
  • 4, none of which are bugs
• Test coverage
• Usage stats:
  • 12 sites
• Maintainer(s):
  • partdigital
• Module features and usage
  • Allows a site builder to define different policies that can be used to manage content access or editing capabilities based on various factors, all within the Drupal UI
  • Criteria can include field values of the content, field values on the current user’s profile, the time of day, and more
  • The policy can restrict access, for example view acces to only selected people or people with a certain role or field value on their profile. I
  • Once defined, policies can be assigned manually, or automatically applied based on configurable selection criteria
  • The project page describes this as an Attribute Based Access Control (ABAC) architecture, which complements Drupal core’s Role Based Access Control that our listeners are probably familiar with
  • I used it for the first recently, and found that given the power and flexibility the module provides, it’s great that it has in-depth documentation
  • I filed a couple of issues (technically half of the open issues) and partdigital was very responsive
  • The module does also provide an API for defining your own policy type, access rules, rule widgets, and more. So if you need a setup even more custom that what Access Policy can provide out of the box, it’s likely you can extend it to meet your individual use case