 |
 |
Drupal, like CMSs, is at its core, a report writer and CRUD system that is well suited to building a staff directory. The hard part is determining what you want. The execution is quite straightforward. Cary On Thu, Apr 4, 2019 at 1:12 PM Sean Aery <[log in to unmask]> wrote: > Hello Code4Lib, > > At Duke University Libraries, we are planning to design/develop a new > staff directory application this spring. It seems like this would be a > fairly common area of need, but there don’t appear to be any widely-adopted > solutions out there. So we’re interested in learning more about what our > peers (y’all) do to power their staff directories. > > For some added context, we use Drupal 7 for our website and a growing > percentage of the applications we support use Ruby on Rails. We don’t have > much in-house experience with JS frameworks like Vue or React. Whatever we > use to build the directory, it should be able to represent people (with > photo, contact info, bio, etc.), display a browsable hierarchy of > organizational units, and be widely discoverable and accessible. > > Does anyone have a solution they like for their staff directory? What > tooling do you use and why? Any words of advice you could share? > > Many thanks, > Sean > > ~~~~~~~~~~~~~~~~~~~~~~ > Sean Aery > Digital Projects Developer > Software Services > Duke University Libraries > 030U Bostock Library Box 90198 > Durham, NC 27708 > [log in to unmask] > > ~~~~~~~~~~~~~~~~~~~~~~ > -- Cary Gordon The Cherry Hill Company http://chillco.com