Ohhh I think I follow. So we wouldn't need to reference Bootstrap directly at all? We'd just point to opac.css and that would include all the Bootstrap CSS as well as our customizations? That sounds pretty awesome to me. 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 12:17 PM To: Koha Devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Bootstrap 4 upgrade for the OPAC
Can you expand more on that?
Yes. Bootstrap assets would be downloaded in a dev environment during "yarn install" as we do other npm packages. In the OPAC SCSS we can then reference those files when we build the OPAC CSS: /* Bootstrap imports */ @import "../../../../../node_modules/bootstrap/scss/functions"; @import "../../../../../node_modules/bootstrap/scss/variables"; Ultimately opac.css would be the only prebuilt CSS file in version control rather than adding a copy of the Bootstrap CSS. -- 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/