Today we are talking about Drupito, its Business model, and Marketplaces with guest Ashraf Abed. We'll also cover Generate (Social Media) Image as our module of the week.
For show notes visit:
https://www.talkingDrupal.com/563
Topics
- Meet Drupalito and the Mission
- Platform Layers and Roadmap
- Pricing and New Markets
- Marketplace Success Stories
- Exportability and Vendor Lock In
- Growing the Drupal Ecosystem
- Derivatives and Recurring Revenue
- Rebuilding on Drupedo
- Funding Drupal Association
- Global Community Check In
- Migrating Sites to Drupedo
- Marketplace Vision Shift
- Maintenance and Incentives
- Safe Updates Blue Green
- Testing Mindset for Templates
- Official Marketplace Collaboration
- Agency Revenue and Partnerships
- Niche Derivatives and Pricing
- Launch Plans and Vetting
Resources
Hosts
Nic Laflin - nLighteneddevelopment.com nicxvan
John Picozzi - epam.com johnpicozzi
Ashraf Abed - drupito.com ashrafabed
Avi Schwab - froboy.org froboy
MOTW
Correspondent
Avi Schwab - froboy.org froboy
- Brief description:
- Have you ever wanted Drupal to generate dynamic social media images using tokenized node data, similar to the share images on GitHub repos or Reddit threads? There's a module for that
- Module name/project name:
- Brief history
- How old: Created by tfranz of Germany on 22 April 2022
- Versions available: 1.x-dev, 2.0.0-beta2, published a few weeks ago by our own Martin Anderson-Clutz
- Maintainership
- Minimally (although now slightly more actively) maintained
- No Security coverage (yet)
- Passing GitLab CI tests
- Well fleshed out README for docs
- Number of open issues: 8 open issues, 0 of which are bugs against the current branch, but there are lots of feature requests
- Usage stats:
- 1 site reports using this module
- Module features and usage
- GSMI requires an image style that uses a "Text Overlay" effect — this comes from the Image Effects module and lets you burn tokenized (or static) text onto an image. Normally, when Drupal generates an image style derivative, there's no entity in scope — it's just processing a file — so a token like [node:title] would resolve to nothing. GSMI's real contribution is the glue: when it builds a derivative for a specific node, it swaps in the node-resolved text before generating the image. That's what makes entity-aware tokens work inside an effect that otherwise only sees global tokens.
- Once the image style exists, GSMI's settings form lets you pick a source image field on the node — an image field or a media-reference field — plus a fallback image for when that's empty. From there it generates the styled derivative from that source image, for any node of any content type that has the field.
- Finally, GSMI exposes its own token — [node:generate-style], with optional style/field overrides — so you're not locked into the one global style/field pair configured in the settings form. I used that to drop the generated image into Metatag's og_image field for the Session content type on the MidCamp site, getting us dynamically generated session images..
- A couple of gotchas we hit setting this up:
- Text Overlay's layout options have some bugs, and not filling out all of the options will result in an image library error.
- The bigger one: GSMI names the generated derivative file after the source image's filename — extension included — not after whatever format the image style actually outputs. If you try to convert an image to WebP you might get a WebP image with a JPG extension.
- BUUUUT - LinkedIn still doesn't support WebP (at least as per their documentation, so it's still in 2026 not safe to use WebP for a universal og:image. https://www.linkedin.com/help/linkedin/answer/a521928
