Can you expand more on that? At the moment, don't you compile the SCSS files, and commit those to the git repo? Would the Bootstrap assets be downloaded by npm for that process then thrown away (and a CDN used instead on the OPAC) or...? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Owen Leonard Sent: Thursday, 4 June 2020 4:12 AM To: Koha Devel <koha-devel@lists.koha-community.org> Subject: [Koha-devel] Bootstrap 4 upgrade for the OPAC Hi all, I've been working on a Bootstrap 4 upgrade to the OPAC (Bug 20168, https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20168). My work in progress is here: https://gitlab.com/koha-dev/koha-dev/-/tree/wip-2020-05-14-opac-bootstrap-4 One of the differences between this version and master is that Bootstrap assets will be added by npm and the OPAC's SCSS files built using those. This seems to make more sense than adding the entire Bootstrap library to our repo and building from there. I think the same should probably be done for jQuery and jQueryUI. I'm curious if anyone has comments on that. Thanks, Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/