Leveraging Drupal for Native Plant Databases and Interactive Signage - Presented by Acquia
summary
Builds a Drupal-powered plant database that manages photos, taxonomies and availability for about 80 species and auto-generates laminated field signs with QR links back to the site. Uses Views and Layout Builder, exposes JSON REST exports consumed by the Squarespace site for real‑time stock, and uses the Entity Print PDF generation module to render print‑ready signs — which works but requires heavy CSS tweaking. QR codes prove reliable in the field; NFC tags fail on metal signs and in older phones.
AI-written summary · about
chapters (19)
- 0:00Introduction and background
- 1:29Why Drupal for native plants
- 3:18Plant signage challenges
- 5:25Choosing Drupal over alternatives
- 8:52Plant database implementation
- 11:00Signage design and PDF generation
- 15:32Layout Builder and UX choices
- 20:05Entity Print module struggles
- 23:39Aquia Cloud IDE and workflow
- 27:11API integration with Squarespace
- 31:05QR codes vs NFC tags
- 33:35API ordering and performance issues
- 38:13Printing and sign size limitations
- 41:26Future improvements and wishlist
- 43:36Code Studio and Drupal updates
- 46:06Plant sales and inventory tracking
- 47:28UX and search functionality
- 48:33Moving from Squarespace to Drupal
- 51:26Q&A and closing remarks
