Jump to content

INQUEST digital archive - showcase for 40th anniversary


millipedia
 Share

Recommended Posts

This one's been a long time coming, but this week we launched a site for the UK charity INQUEST who provide support for families involved in state related deaths.

This was part of their 40th Anniversary and the site showcases significant milestones and events from their archive over the last 40 years. There's an interactive timeline, case studies and oral histories. Even given the difficult subject matter we're really pleased with the result:

inquest_home.thumb.jpg.589f09d6e514059a16b478ac99fa71c6.jpg

inquest_timeline.thumb.jpg.3ad60305f70ede8f8583bda439bfae04.jpg

 

Behind the scenes, the modules we used were mostly the usual suspects, Tracy Debugger, ProCache etc. Also RockFrontend specifically for the ajax routing (would love that as a separate module @bernhard ) which we used with HMTX in various places. Not sure we really needed to use HTMX on this one but hey, it is very handy.

One module we made use of which we hadn't used before was @Richard Jedlička's PDF fieldtype so that we could generate thumbnails of PDF documents. There are a lot of historical documents on the site and having the thumbnails generated automatically was really handy.

The site seems to have gone down really well. And we actually had a launch party - it's been years since that happened...

https://history.inquest.org.uk/

Oh, and it does very nicely in Lighthouse and gets A+ in Observatory as well 🙂

inquest_lighthouse.thumb.png.9844d018bf64b546a4bc23b713c84518.png

 

  • Like 4
  • Thanks 1
Link to comment
Share on other sites

  On 3/28/2025 at 12:46 PM, millipedia said:

Also RockFrontend specifically for the ajax routing (would love that as a separate module @bernhard ) which we used with HMTX in various places.

Expand  

Hey @millipedia congrats. I understand that but it's not as easy as it may sound. I'd either have to add RockFrontend as a dependency then or have several features duplicated across both modules that I need to support... Or I'd have to extract it to yet another module and add that as a dependency for both RockFrontend and RockAjaxWhatever... Neither option is better than having it in RockFrontend and working on making its footprint as small as possible so that even if you just use a fraction of what the module has to offer it will still be safe, stable and fast. Any help in that direction will happily be merged (but don't know of any performance penalties when using the module).

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...