Bootstrap upgrade #4825

New Issue

delliott · 2025-02-09T13:56:40Z

delliott commented

2025-02-09 13:56:40 +00:00

At the moment we are on bootstrap v3

We should probably try and move to bootstrap v5.

This involves moving from less to scss.

Some initial attempts were made at that here

There is an automated tool, but it has not been updated in a while and seems to generate scss in a style that is now not advised. Tool is here

At the moment we are on bootstrap v3 We should probably try and move to bootstrap v5. This involves moving from less to scss. Some initial attempts were made at that [here](https://git.fsfe.org/FSFE/fsfe-website/pulls/4461) There is an automated tool, but it has not been updated in a while and seems to generate scss in a style that is now not advised. Tool is [here](https://github.com/debba/less2scss)

delliott commented

2025-02-09 13:59:34 +00:00

Also when upgrading, we should leave things in such a way that its easy to upgrade boostrap versions. Either git submodules to their repo, or download it during the python build script I think would be nice.

Make sure and treat bootstrap itself as a build transient file, so noone goes altering bootstrap internals.

A seperate conversation is that we can probably drop modernizer, but thats a later issue I think.

Also when upgrading, we should leave things in such a way that its easy to upgrade boostrap versions. Either git submodules to their repo, or download it during the python build script I think would be nice. Make sure and treat bootstrap itself as a build transient file, so noone goes altering bootstrap internals. A seperate conversation is that we can probably drop modernizer, but thats a later issue I think.

delliott added the build design disruptive labels 2025-04-27 14:31:42 +00:00

delliott referenced this issue

2025-11-21 14:47:09 +00:00

feat/versions #5512

delliott commented

2025-12-14 18:13:09 +00:00

We now have #5512 which does not upgrade bootstrap, but should at least make it easier to do so when the time comes. It also successfully pares away some js deps we do not need, and I have pared away more in #5513.

This leaves us with only needing to upgrade our small custom bootstrap scripts, and the bootstrap less.

I am kind of wondering about trying to remove all bootstrap entirely? Do we really need it? We frankly do not seem to make much reference to things in it?

At least I would like to drop bootstrap js, as we should really be aiming for a js free site as much as possible.

We now have https://git.fsfe.org/FSFE/fsfe-website/pulls/5512 which does not upgrade bootstrap, but should at least make it easier to do so when the time comes. It also successfully pares away some js deps we do not need, and I have pared away more in https://git.fsfe.org/FSFE/fsfe-website/pulls/5513. This leaves us with only needing to upgrade our small custom bootstrap scripts, and the bootstrap less. I am kind of wondering about trying to remove all bootstrap entirely? Do we really need it? We frankly do not seem to make much reference to things in it? At least I would like to drop bootstrap js, as we should really be aiming for a js free site as much as possible.

tobiasd referenced this issue from a commit

2025-12-24 13:00:49 +00:00

feat/versions (#5512)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FSFE/fsfe-website#4825