Offering to maintain Bootstrap

These offers must be first opened in the project issue queue. If none of the maintainers has replied in 14 days to decline the offer, the issue can be moved to the Drupal.org project ownership. Remember to provide a link for the project page, in that case.

I agree with your suggestion. I've also been considering revamping this theme to Bootstrap 5, and joining forces with Barrio might be the best way forward.

Lovely.

Hello;

Congratulation Alberto for becoming a maintainer of bootstrap. The Drupal community will benefit of the 2 most popular Bootstrap themes (100K & 40K) to join force.

I am one of the maintainer of another Drupal theme : https://www.drupal.org/project/ui_suite_bootstrap → (156 installs) and I believe we may be helpful for future design system related work.

UI components

https://getbootstrap.com/docs/5.3/components

bootstrap theme and barrio theme are currently migrating to SDC. It is a task not as easy as it may look.

ui_suite_bootstrap has SDC-like components since 2020, they benefited of years of improvements from feedbacks and real life usage, and we have a branch for SDC conversion: https://git.drupalcode.org/issue/ui_suite_bootstrap-3412076/-/tree/34120...

Our SDC implementation has some dependencies to the upcoming ui_patterns → 2.0 but they are easy to skip and bootstrap can benefit of those well crafted and tested components (and validated by me, one of the 2 maintainers of the SDC sub-system in Drupal Core ;) ).

We also provide a tool to validate SDC components if you want to keep yours own.

Other UI artfecats

A design system is not only UI components. Bootstrap also expose:

• https://getbootstrap.com/docs/5.3/helpers & https://getbootstrap.com/docs/5.3/utilities/
• CSS variables, which are particularly hard to manage
• theme/mode switch (dark/light but not only)
• icon packs (bootstrap, font awesome...)
• ...

Those artefacts can be managed by custom PHP code in each theme, but we, the UI Suite team, provide generic modules to manage them with simple YAML files and automatically plug them to Drupal API:

• Utilities & helpers: https://www.drupal.org/project/ui_styles →
  Example: https://git.drupalcode.org/project/ui_suite_bootstrap/-/blob/5.0.x/ui_su...
• CSS variables & theme/mode switch: https://www.drupal.org/project/ui_skins →
  Examples: https://git.drupalcode.org/project/ui_suite_bootstrap/-/blob/5.0.x/ui_su... & https://git.drupalcode.org/project/ui_suite_bootstrap/-/blob/5.0.x/ui_su...
• Icon packs: https://www.drupal.org/project/ui_icons →

Don't hesitate to contact us if you want to know more. We can do a demo of our implementations and tools.

Sorry, somehow I missed this. I'm a bit apprehensive about radical new changes to the bootstrap project.

I am one of the co-maintainers of bootstrap and I lack permissions to edit the project page.

It seems that this project is being pulled into several directions.

My priority right now is Drupal 11 compatibility for the 8.x-3.x branch.

Perhaps all of the current co & full maintainers should set up a meeting to discuss what is going on and make sure that we have some common goals.

I've already been preparing a version of the bootstrap 3.x library that aims to be compatible with jQuery4. It is currently undergoing testing. cdns are already available.

https://bootstrap.7pro.ca

@joseph: I also have a B3 theme in D7, but learned in last week that a migration these B5 is not that difficult than I expected it first. It is still a lot of effort to switch from D7 to D10 as all templates need to be redone (this stresses me a lot), but the CSS stuff seems not that difficult to migrate to B5. I love to hear you spend time on the jquery issue when I thought last week - this is not going to happen (as there was a note - D10 is the last that will work with B3), but now I started with B5 and I think - everyone who can or is redoing a site should move and not stick at B3 that is end of all from bootstrap side.

The only reason why people are not upgrading in last 5 years (at least me) is there is no B4/B5 in the project available and I do not like to move to bario or any others. It looks like the previous main bootstrap theme maintainer became very inactive ~5 years ago and this is also the reason why the statistics show that 8.x-3.x is the most active. Nobody can use something that does not exist.

Moving to SDC can only be good.

I fully support the upgrade to use bootstrap 5. There is a reason why Bootstrap 3 is unsupported for more than 5 years and I'm not sure if @joseph.olstad is fully aware of the security implications of his attempt to create Bootstrap 3.4.2. HeroDevs has a Bootstrap NES version where they fix the security problems in older versions of Bootstrap and they are multiple devs being paid by a subscription model to keep that up (for a very small list of CVEs fixed in Bootstrap 3 in July 2024, see https://www.herodevs.com/support/nes-bootstrap?utm_source=Bootstrap_site...), and yes they also have a jQuery NES. I honestly believe that there should never be a supported version of the 3.x branch of this theme that is not an alpha (i.e. 8.x-3.33-alpha1, etc.), to make clear to everyone using that effort that they really have no security coverage and should think about migrating away from Bootstrap 3.

The question however, is how is the upgrade process between version 8.x-3.32 and 5.0.0-beta1? I'm pretty sure it is not a simple step of changing the version number in composer.json...

The question however, is how is the upgrade process between version 8.x-3.32 and 5.0.0-beta1? I'm pretty sure it is not a simple step of changing the version number in composer.json...

This is more or less a rebuild from scratch.

Just from real live - I just banged against views_bootstrap... installed 5.x and several views made for 3.x crash and say a plugin is missing... well that plugin no longer exists in views_bootstrap B5, but the worse issue - I cannot edit the old view at all to fix the issue... I think I need to install views_bootstrap 3.x again, edit the view to a core plugin and than install views_bootstrap 5.x again to follow up. I hope the views_bootstrap team may solve this somehow with an update hook. Just be warned :-)

Automatically closed - issue fixed for 2 weeks with no activity.