... | ... | @@ -43,7 +43,15 @@ Specific in the 'search' extension, with aim for re-usability: |
|
|
|
|
|
Con: need to maintain a bunch of custom code to do fairly standard things
|
|
|
|
|
|
2. Use a lighter-weight, modular framework to provide these things
|
|
|
2. Use a classless CSS framework
|
|
|
|
|
|
A number of [classless CSS frameworks](https://github.com/dbohdan/classless-css) exist to allow you to use standard rules with your own selectors.
|
|
|
|
|
|
Pro: nearly complete control over what is done, ability to leave much of the existing markup in place
|
|
|
|
|
|
Con: not a drop-in solution, so it will need to be maintained by occasionally updating rules, and developer documentation will need to be more extensive
|
|
|
|
|
|
3. Use a lighter-weight, modular framework to provide these things
|
|
|
|
|
|
[Bulma](https://bulma.io/documentation/overview/modular/) is an example of a framework that's much less heavy-handed and could do a lot of the above things.
|
|
|
|
... | ... | @@ -51,7 +59,7 @@ Specific in the 'search' extension, with aim for re-usability: |
|
|
|
|
|
Con: introduces yet another library
|
|
|
|
|
|
3. Generate a mini-Bootstrap to provide this things
|
|
|
4. Generate a mini-Bootstrap to provide this things
|
|
|
|
|
|
https://getbootstrap.com/docs/3.4/customize/
|
|
|
|
... | ... | @@ -59,7 +67,7 @@ Specific in the 'search' extension, with aim for re-usability: |
|
|
|
|
|
Con: need to maintain a customized subset of Bootstrap and manage how that interacts with the full Bootstrap that may appear in the Bootstrap extension and/or various site themes
|
|
|
|
|
|
4. Require Bootstrap in more circumstances
|
|
|
5. Require Bootstrap in more circumstances
|
|
|
|
|
|
Pro: no need to maintain a custom framework
|
|
|
|
... | ... | |