Today we are talking about the cost around Drupal, common misconceptions, and how you get what you pay for with guest Jeff Robbins. We’ll also cover Module Instructions as our module of the week.

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

• What is new!
• How did you get started with Drupal
• Selling Drupal and the cost
• How much is the technology vs the complexity of projects that lend themselves to Drupal
• Value of Drupal
• What can the Drupal community do to make it more widely attractive
• Versionless Drupal marketing

• Drupal.org README.md Documentation
• Drupal versioning discussion
• Talking Drupal #390 - Employee Owned Companies
• Talking Drupal #429 - The Drupal Association Board
• Talking Drupal #439 - Drupal 7 Long-Term Support
• Visibox
• Jeff Robbins
• MySQL
• PHP

Jeff Robbins - jjeff.com jjeff

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Ivan Stegic - ten7.com ivanstegic

Martin Anderson-Clutz - mandclu

• Brief description:
  • Have you ever wanted to have easy access to the README, CHANGELOG, and INSTALL files for the contrib modules on your Drupal site? There’s a module for that.
• Module name/project name:
  • Module Instructions
• Brief history
  • How old: created in Apr 2012 by Ales Rebec of Slovenia
  • Versions available: 7.x-1.0 and 2.0.3 versions available, the latter of which works with Drupal 9 and 10
• Maintainership
  • Actively maintained?
  • Security coverage
  • Test coverage
  • Number of open issues: 4 open issues, none of which are bugs against the 2.0.x branch
• Usage stats:
  • 1,238 sites
• Maintainer(s):
  • Current maintainer of the 2.0.x branch is Viktor Holovachek a.k.a Aston Victor of the Ukraine Drupal Community
• Module features and usage
  • The usage of the module is pretty straightforward. Once the module is installed, anyone who has access to the Modules page on a Drupal site will see links on that page to any README, CHANGELOG, or INSTALL files that are available for the contrib modules in the codebase
  • It also provides a cron job and drush command to generate the links, stored in the site state, so the application isn’t doing all the work of parsing through all your contrib modules looking for the files every time someone wants to load the Modules page
  • It does override the template for the module page to add those links, so be aware that if you’re doing something very custom and have overridden that template in something like a custom admin theme, you may need to manually add some extra markup to see the links
  • The module does also define new permissions, to manage the settings for these links, or to view them
  • The settings really consist of specifying which of the links you want to appear, if the relevant files are available. By default it will show all three, but you could, for example, only have it show README links