... | ... | @@ -33,4 +33,34 @@ CiviCRM classics: |
|
|
Specific in the 'search' extension, with aim for re-usability:
|
|
|
|
|
|
* crm-flex-box
|
|
|
* crm-flex-2 |
|
|
\ No newline at end of file |
|
|
* crm-flex-2
|
|
|
|
|
|
# Potential methods for implementation
|
|
|
|
|
|
1. Write our own CSS
|
|
|
|
|
|
Pro: full control over what is done
|
|
|
|
|
|
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
|
|
|
|
|
|
[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.
|
|
|
|
|
|
Pro: no need to maintain a custom framework
|
|
|
|
|
|
Con: introduces yet another library
|
|
|
|
|
|
3. Generate a mini-Bootstrap to provide this things
|
|
|
|
|
|
https://getbootstrap.com/docs/3.4/customize/
|
|
|
|
|
|
Pro: no need to maintain a custom framework
|
|
|
|
|
|
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
|
|
|
|
|
|
Pro: no need to maintain a custom framework
|
|
|
|
|
|
Con: everyone has to deal with Bootstrap, including and especially those who so far have not wanted it, possibly for compatibility reasons |
|
|
\ No newline at end of file |