Delivery Circle - 13th May 2026

Gaetan

  • Security: Done manual mitigation, but keeping the two issues (one and two) open as a reminder to check if new fixes are released

  • Rails upgrade: one last issue to fix, almost done

  • Next priority: shop grid view or UK digital inclusion? Will ask in slack channel

David

Mario

  • finalised product refactor analysis, will wrap up with a short summary soon

  • working on status update for roadmap

  • working on next issue for grid view, potentially some colour/font/icons changes to come as part of the shopfront uplift

Ahmed

  • The major design discrepancy in the generated invoices before and after migrating the gem to FerrumPDF was fixed. On local, it looked major discrepancies, but when I deployed it to staging for a test, it’s almost identical.

  • The root cause here was that the CSS was not getting loaded properly on local

  • There were still some minor discrepancies, those have been resolved as well

  • Now I’m majorly working on the ofn-install scripts to install the chromium on the staging servers before we can finalize it for QA.

  • Hopefully I’ll pick up the multiple images work this week.

1 Like

@Mario I mentioned the idea of using a templating language for the homepage and/or shop pages. But I’m pretty sure now that it’s a bad idea:

  • Homepage: apart from the menu at the top of the page, this has no application features and is simply content. So instance managers would be better off having a way of editing that content (eg a WSIWYG editor, perhaps with Wordpress)
  • Shopfront general (edited only by instance managers): Any time we add or change features or data structure, it could affect the template. So there would be a whole new layer of support required to report these changes, and for instance managers to ensure their templates are updated. All changes would need to have backwards compatibility for a smooth transition.
  • Individual shopfronts: definitely I would not suggest this, too hard to support.
1 Like