Whats is the use of Bootstrap sub theme in Drupal 7 and why it is recommended? There is lot of articles out there on "How to Bootstrap sub-theming" but none of them are available for why?
As it is said on Drupal.org:
Sub-themes are just like any other theme, with one difference: They
inherit the parent theme's resources.
A Bootstrap sub-theme allows you to inherit from the Bootstrap framework itself. It brings you several benefits:
No need to download any contrib modules, the Bootstrap sub-theme kit should be enough.
A strong CSS base, with accurate variables customization.
Respect of web standards.
Great modularity.
...
I hope I answered the question.
Related
Not sure it's the right question for this forum, but I couldn't find another place for it.
Our design team built their design system based on fluent ui libraries as described here. They downloaded the design from here.
Unfortunately, our engineering team is using Angular, so we naturally reached for the option of web component but found out to our surprise that the library is completely different - different set of components, abilities, and of course - a completely different design.
I thought that all fluentui platforms are supposed to be an implementation / interface of the same design. Why is this not the case? What am I missing?
Is there a way we can use the design described in here in Angular? (Except actually using the react library inside my Angular project).
Thanks for helping and very sorry if this question is inappropriate for this forum.
fluent web components integrated with angular.
take a look at documents
Need to build an interface. So want to know what is the best and easy way to do it in vue.js
As with a lot of things, there isn't a "best" thing as this is a very subjective matter but we can focus on the "most popular". I will give you an overview of the current state of most popular Vue.js styling solutions:
Vuetify
A complete material design UI framework has a lot of components and is very active, very customizable as well It probably is the most popular UI solution for Vue.js
Quasar Framework
Quasar is also a material based UI framework but it focuses on performance and developer experience, very active and releases often. It also has its own CLI and allows you to target apps using Electron or Cardova, its more of a complete app-bootstrapper than a UI framework.
Bootstrap-Vue
It is like the name suggests, a bootstrap-based UI framework and is the most comprehensive one with full implementation of bootstrap and a lot of custom components as well. It the way to go if you are going with bootstrap-based UIs.
Tailwind CSS
Tailwind is a utility-first CSS framework that uses PostCSS, it is really easy to get started with and very productive, it is my personal favorite because it stays in the CSS and HTML realm, while UI frameworks are very cool and productive, you cannot escape the overhead they introduce and not all designs are based off bootstrap or material anyways. Tailwind manages to stay productive while being very flexible but requires having decent knowledge of CSS and how properties interact.
Again there isn't a "best" framework out there for styling, so you need to study the options and pick the one that "better suits you".
What is the most elegant way to get a riot based UI today?
i'd love the following points to be addressed:
A proper code-mapping for easy debugging
A good way to bundle the application (so far i used Webpack and JSPM)
It would be lovely if it would work elegantly with Typescript.
Is it best to use Tag files, or straight JS? If the later, would it be better to use a class that inherit from riot's tag class? If so, can i place the template code in a different file?
Future compatibility: i saw that there's going to be a change (that "export default" thing) - how would you recommend to write the code for the smoothest migration path?
If you have more items for consideration - please add them....
Thanks for asking these questions. I have tried to answer to all your questions hoping they could be useful also to other Riot.js users
A proper code-mapping for easy debugging
the riot compiler generates simply javascript code without modifying too much the structure of your original source code. Any modern browser should be able to provide with debugger breakpoints and console calls all the debugging tools you need. Check for example the stack trace of this error you don't need much more to figure out where it's coming from.
A good way to bundle the application (so far i used Webpack and JSPM)
In this repo we provide 3 different javascript bundle examples: rollup, webpack, riot-compiler. I personally prefer rollup but you can (and should) use whatever works best for you and your team.
It would be lovely if it would work elegantly with Typescript.
The riot public methods are already available as Typescript interfaces:
- https://www.npmjs.com/package/#types/riot
- https://www.npmjs.com/package/#types/riot-route
I am not a typescript user and that's why I will not invest time in making examples in a technology I don't use but PR are welcome
Is it best to use Tag files, or straight JS? If the later, would it be better to use a class that inherit from riot's tag class? If so, can i place the template code in a different file?
I recommend you to just use Tag files because riot was designed as component library and it embraces completely the philosophy of components composition vs class inheritance. If you have code you share across several components you can either use mixins or import it with your bundler directly in your tags see for example
Future compatibility: i saw that there's going to be a change (that "export default" thing) - how would you recommend to write the code for the smoothest migration path?
Riot 3 will be not compatible with Riot 4. (that will be a full rewrite) I can't recommend any best practice to make your code portable to Riot 4. Remember that Riot 3 will be still supported and your code will run even on IE9 for the next 10 years. Once riot 4 will be released and the API will be stable I can provide more hints about a migration path.
I need to attribute Bootstrap in a new project I am working on. I can not find anything online that explains the proper steps for attributing Bootstrap. What I have right now is:
Built with Bootstrap
And this will go in the footer, or where I can fit it in.
Twitter Bootstrap is released under MIT license, so the only attribution you legally have to comply with is keeping the license file in place.
If you just want to do the good thing and let people know that you are using boostrap the choice of how to do that is yours. Don't think there is any official or even commonly used attribution style.
I want use http://twitter.github.com/bootstrap/ in my application.
I found for yii two extensions:
http://yii-booster.clevertech.biz/
http://www.cniska.net/yii-bootstrap/
Mayby is more then this 2?
Which one is better? What is difference? What with licence? My application is commercial.
Yii-Booster is a library that contains Yii-Bootstrap and many other Yii widgets and components.
If you just want Bootstrap your project Yii-Bootstrap will probably solve your problem, but if you want a more complete library I recommend Yii-Booster.
Example of widgets contained in Yii-Booster:
Select2: http://ivaynberg.github.com/select2/
Editable: http://vitalets.github.com/bootstrap-editable/#options
StickyTableHeaders: https://github.com/jmosbech/StickyTableHeaders
BootGroupGridView: http://groupgridview.demopage.ru/
JQueryUI Bootstrap CSS: http://addyosmani.github.com/jquery-ui-bootstrap/
And many other components:
http://yii-booster.clevertech.biz/components.html
http://yii-booster.clevertech.biz/json-grid.html
http://yii-booster.clevertech.biz/extended-grid.html;
As told you in other answer, both projects use the license New BSD License.
It's all a matter of fitting your needs.
The Yii Booster is one project based on Yii Bootstrap and have some components more.
The projects have the same source code base.
So far, the Yii Bootstrap, solved my problems, however, if you want to use some component unique of the Yii Booster, use it!
Both projects use the license New BSD License.
More informations about the projects you will find the links below:
Yii Bootstrap - Extension Page.
Yii Bootstrap - Discussion Topic.
Yii Booster - Extension Page.
Yii Booster - Discussion Topic.
Another similar extension: Yii Foundation 3.
Yii Foundation 3 - Extension Page.
A more up to date version of Yii-Bootstrap is Yiistrap. Yiistrap has also been written by the author of Yii-Bootstrap and is offered under a BSD-3-Clause license, so commercial use should be fine.
As already pointed out Yii-Booster is simply a prepackaged app with various extensions already in place. An alternative to that would be Yii-App for instance. It contains fewer markup extensions but a number of developer and backend extensions that may help with basic development.