MopaBoostrap Documentation / Future of MopaBootStrap

[jonny827]

Goal: Great a centralized discussion on the future of MopaBootsrapBundle and related Sandbox and Documentation. If you see another discussion point, then please let me know and I will add it to the list. Once a direction has been chosen we can create the appropriate Pull Requests that focus on the actual implementation of the needed pieces of the solution.

Major items that should be discussed

• Should we separate documentation from the Sandbox?
• Should we separate bundle from Library?
• Given : MopaBootstrapBundle Issue #1178 - Should we take advantage of the built in Symfony Twig Templates?

Discussions I am trying to centralize by this singular issue

1. MopaBootstrap Bundle Integration with Silex
2. Integrate the basic Bootstrap 3 Symfony form theme #1178
3. Documentation Issues #1072
4. Break bundle into Library+Bundle #953
5. Original Symfony Bootstrap Integration Pull Request - the most commented on Pull Request according to Symfony
6. I will add more as they become available

Requesting Input from:
@phiamo @isometriks @soullivaneuh @afurculita

[jonny827]

I have separated my reply from the Issues at hand to keep the facts and personal opinion separated.

I see we have three roads now that Symfony has released Bootstrap integration.

1. Adopt Symfony Bootstrap Integration and re-factor the bundle around it which may eliminate some code.
2. Separate library and Bundle, therefore ignoring the Symfony Bootstrap Integration so that we can reuse our twig templates and other components through the library in other frameworks like Silex, Laravel, etc.
3. Contributing to the Symfony project any code needed that would essentially EOL-End of Life MopaBoostrap altogether. This would push the support into a larger community as well as the documentation. This would bring new interest to the feature set and share the burden of documentation and support among a larger audience. Additionally, I believe this would force other projects into EOL-End of Life such as Braincrafted Bootstrap Bundle. Which would in the long run build a much strong Symfony view component because of the combined contributors.

Anyone see any other major options to decide from?

[stephanvierkant]

I think the size of the community is very important to a open source project like this. Maybe we can start working together with Braincrafted Bootstrap Bundle? See braincrafted/bootstrap-bundle#463

In the long run this should be integrated into Symfony.

[stephanvierkant]

The other bundle seems completely dead now. Documentation site is offline.

[phiamo]

Yep server was canceled headless ly Am Di., 4. Dez. 2018, 15:26 hat Stephan Vierkant <notifications@github.com> geschrieben:

…

The other bundle seems completely dead now. Documentation site is offline. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#47 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMpuyV1wbXZteZ_pJLAEh8_brTiZJ1kks5u1oYsgaJpZM4JlZ5G> .

[stephanvierkant]

I'm migrating away from this bundle in favor of Symfony's own features. I'm having two problems right now:

1. Symfony's form themes have improved over time. They added a Form field help recently: https://symfony.com/blog/new-in-symfony-4-1-form-field-help. But CollectionType is still hard: [DX][Form] Provide better front end for Collections symfony/symfony#29467
2. KnpMenu(Bundle) doesn't have a Bootstrap template. There are some gists available, but I think KnpMenu should have Bootstrap templates, like Symfony does with it's Bootstrap form themes.

What else should be done to provide an alternative to this bundle? I think the Twig extensions for icons and flash messages aren't a problem.