I started GWT-Bootstrap with the goal of linking the JS and CSS bootstrap to the reusable GWT components, otherwise you will probably have to replicate the code, which will probably end up creating your own code, which will probably be very similar in GWT-Bootstrap.
It also has some features for event binding, etc.
But, answering your main question: it depends. If you do not trust the community and / or have a lot of time, you can make your own gwt-bootstrap as a project, but probably integrated with your project, at least this is what happened in my case ... therefore, I started GWT-Bootstrap and some guys like this, and the big story is short: now this is what it is. It needs a lot of improvements, updates, better documents and a lot of things, but itโs true: I donโt have much time for this.
So, if I were you, I would probably help the GWT-Bootstrap community instead of reinventing the wheel, but thatโs just my opinion.
Happy learning.
EDIT add the @IAmYourFaja thing in the comments.
Injection, because you mean (or, I believe, you mean), is not centralized.
We have a ResourceInjector that injects some resources, customizes the viewport, etc., and a Resource.gwt.xml module that injects CSS files. We also have component classes that install JS plugins (if necessary) and CSS classes. If you want, take a look at TabPanel .