Project

General

Profile

Bug #15749

Use Bootstrap everywhere on the website

Added by sajolida over 1 year ago. Updated over 1 year ago.

Status:
Confirmed
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
09/21/2016
Due date:
% Done:

0%

Feature Branch:
Type of work:
Website
Blueprint:
Starter:
Affected tool:

Description

Recently, we've used [Bootstrap](https://getbootstrap.com/) on pages where we needed more flexibility on how to structure the content on the page, like:

Bootstrap made this extremelly easy and is still the most popular HTML+CSS framework/library.

There has been some work upstream on making ikiwiki work better with Bootstrap:

Tor is using Bootstrap for their dynamic style guide:


Subtasks

Bug #11821: Have a configuration for compiling our custom version of BootstrapConfirmed


Related issues

Related to Tails - Feature #15800: Have a visual style guide Confirmed 12/04/2018
Related to Tails - Feature #9216: Present and argument in favor of bootstrap to the project Resolved 04/08/2015

History

#1 Updated by sajolida over 1 year ago

  • Description updated (diff)

#2 Updated by sajolida over 1 year ago

  • Description updated (diff)

#3 Updated by u over 1 year ago

I'm all for it. Something like this could be done in a sprint quite easily?

#4 Updated by sajolida over 1 year ago

What's blocking this is having people available to do the work (and ideally money to pay them).

I'm not sure how this relates to developing an updated style guide for Tails, which could include a custom Bootstrap theme like Tor did: http://oniongit.eu/infra/styleguide.git:

  • Switching to Bootstrap after developing the style guide would avoid having us to hack our current CSS to work with Bootstrap. I'm especially worried about the general navigation parts.
  • Switching to Bootstrap before developing the style guide might make it easier to develop the style guide as we'd be able to test it on real content directly.

#5 Updated by sajolida over 1 year ago

#6 Updated by intrigeri over 1 year ago

It recently came to my attention that CSS frameworks can have security issues such as XSS (see e.g. https://security-tracker.debian.org/tracker/source-package/twitter-bootstrap) — I had no clue! On #9216 we've discussed a bit how our copy of Bootstrap would be maintained/upgraded. Back then we had in mind bugfixes but not security issues and regardless, we did not reach any actionable conclusion. Indeed, the last update was in May 2016 (to 3.3.6). Since then only another 3.x was released upstream and the security fixes were applied only in 4.x. So I'm humbly asking that this time, while discussing using Bootstrap more broadly, we do take into account the future maintenance of our copy. Fair enough? :)

#7 Updated by intrigeri over 1 year ago

  • Related to Feature #9216: Present and argument in favor of bootstrap to the project added

Also available in: Atom PDF