Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PROPOSAL] Drop Bootstrap in Frontend #578

Open
rintisch opened this issue Oct 9, 2024 · 1 comment
Open

[PROPOSAL] Drop Bootstrap in Frontend #578

rintisch opened this issue Oct 9, 2024 · 1 comment
Labels
11.x related to TYPO3 v14

Comments

@rintisch
Copy link
Collaborator

rintisch commented Oct 9, 2024

This is just a base for discussion!

I would like to drop the Bootstrap classes in the Frontend.

The reasons:

  • The current implementation for the Frontend with Bootstrap is not fully responsive.
  • It's quite some work to make it fully responsive and nobody seems to be willing to do so.
  • I have not seen a project where the Templates are used as delivered by the extension. People seem to build their own stuff.
  • It's hard to maintain.
  • It's quite bloated, it's hard to find the classes that are really necessary when building an own project

The solution:
Strip the HTML to what is really necessary as it's down in https://github.com/derhansen/sf_event_mgt/tree/main (see also https://github.com/derhansen/sf_event_mgt/tree/main)

@extcode
Copy link
Owner

extcode commented Oct 14, 2024

I currently use Bootstrap myself for my manual tests. I can implement this reasonably well in the templates for myself.

In general, even if Bootstrap classes will be removed, once will not be able to avoid adapting the templates to use own CSS classes in them. It would only save you from removing CSS classes and div structures.

Classes that are necessary for accessing and processing the extension's JavaScript could be prefixed with js- to give the integrator an indication of which CSS class should be retained.

For this and the next version, I would defer this for the time being. If the automated acceptance tests do not require (a few) manual tests, the topic can be taken up again for TYPO3 v14.

@rintisch rintisch added the 11.x related to TYPO3 v14 label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
11.x related to TYPO3 v14
Projects
None yet
Development

No branches or pull requests

2 participants