bootstrap-vue
Tailwind CSS
Our great sponsors
bootstrap-vue | Tailwind CSS | |
---|---|---|
43 | 1,277 | |
14,456 | 78,166 | |
0.1% | 2.1% | |
5.1 | 9.4 | |
3 months ago | 7 days ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bootstrap-vue
-
10 UI Libraries You Should Explore for Your Next Vue.js Project
4. Bootstrap Vue Bootstrap Vue combines the power of Bootstrap, a popular CSS framework, with Vue.js. It provides a wide range of components and styling options. Check out the Bootstrap Vue website to learn more.
-
[AskJS] UI libraries either backed by enterprises/quick fix of issues/has almost no issues with default styling that is customizable
Vue (BootstrapVue)
-
What is the story with BootstrapVue now?
You say that Afaik is the creator? I didn't see him listed as a major contributor on github: https://github.com/bootstrap-vue/bootstrap-vue/graphs/contributors . Do you happen to have his Github profile link?
- Vue 3 UI Framework recommendations?
-
Vue or React? Which one is easier to pick up?
For me personally one of the dealbrakers was bootstrap-vue still being stuck with Vue v2 / Bootsrap v4 to this day. react-bootstrap supports Bootstrap v5 since 2021 october.
-
Top UI libraries for Vue JS in 2023
Bootstrap-Vue: A UI library that provides a range of components based on the popular Bootstrap framework, including forms, buttons, and navbars.
- Fragen bezüglich Flask, Zahlungsgateway, Design und JavaScript
-
Noob question: What do you use to build your front ends?
BootstrapVue is the bundle: https://bootstrap-vue.org/
-
Don't be that open-source user, don't be me
Yes. Please have the courtesy to feedback with a roadmap or prio of the issue. Especially for popular issues.
Asking, politely, for this should not label you as entitled freeloader. It is important input to make an informed decision wether one should just wait for the fix, workaround it, contribute a PR yourself, fork the component or drop it and consider alternatives.
One has to be careful with estimates though so they don’t become false promises. All respect to these maintainers but if I have to give one concrete example, consider following issue in a very popular Vue component, https://github.com/bootstrap-vue/bootstrap-vue/issues/5196 creating a upgrade deadlock for almost the entire Vuejs community. It’s the type of dependency that get so entrenched in everybody’s application that upgrading or moving away from it becomes very expensive and requires long term planning. As such, hundreds of comments there asking for estimates and also dozens of heavy names offering help in forms of PRs, forks or donations, all on a very polite level, but the maintainers kept promising it will be done “very soon” for almost 2 years straight. It appears the last months the war has been adding more obstacles so all respect for that, but even before the roadmap was hopelessly unpredictable.
I get it, as a volunteer other things in life often have higher prio, estimates tend to be optimistic and you might want to work on things in no particular order at all. What’s important is to be transparent, polite and communicate.
-
Why We Switched from Python to Go
What's wrong with Angular? It being largely "batteries included" seemed pretty nice and I really liked the fact that TypeScript was a first class citizen - React and Vue both feel like it's been kind of tacked on, especially when a lot of additional libraries out there don't really have proper bindings.
That said, personally I also think that React kind of went downhill for a bit due to the hooks (after seeing a few projects become really nightmarish to debug due to render loops without clear causes for them, after people sprinkled one too many hooks in there).
Oh, and the Vue 2 to 3 migration is also a bit problematic because still many UI component libraries haven't been migrated over - currently actually using PrimeVue on a project because BootstrapVue still doesn't have proper support https://github.com/bootstrap-vue/bootstrap-vue/issues/5196
Tailwind CSS
-
Customer service pages for e-commerce built with Tailwind CSS
Tailwind CSS
-
The best testing strategies for frontends
With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.
-
ChatCrafters - Chat with AI powered personas
This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository
-
Mojo CSS vs. Tailwind: Choosing the best CSS framework
Unlike Tailwind, which has over 77,000 stars on GitHub, Mojo CSS has about 200 stars on GitHub. But the Mojo CSS documentation is fairly good and you can find most of the information you’ll need there.
-
Collab Lab #66 Recap
JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite
-
Show HN: Brutalisthackernews.com – A HN reader inspired by brutalist web design
- Performance is a feature.
Another common interpretation of brutalism is aesthetic, reacting to overly complicated user interfaces by creating simpler, more direct ones. Tailwind CSS (https://tailwindcss.com), one of today's most popular CSS libraries, promotes this approach in its component examples. There's also a neat library I've seen recently called "Neobrutalism Components" for React that I like (https://neobrutalism-components.vercel.app), providing components with a similar look and feel to Gumroad. This might more accurately be called 'Neo-Brutalism,' as noted in the comments.
A more engineering-centric interpretation of Brutalism focuses on form, structure, and efficiency, drawing significantly from brutalist architecture principles. Apart from the user interface itself, most mobile, desktop, and web applications are extremely bloated and often perform worse than sites from 10 years ago did. While one HTML file might be "less brutalist" than the original HN site, it is substantially more brutalist than any HN mobile app in existence, and offers nearly identical functionality.
A broader interpretation of brutalism, which could be termed 'Meta-Brutalism,' is embodied in the overall experience on this site through UX flows. Yes, in the strictest sense, the original HN site is more Brutalist in many ways, but it only shows 30 articles at a time and does not function as a PWA. For this site, the experience of reading 10 stories is arguably less brutalist, but for quickly browsing through several pages and skimming articles (which is how I read HN) it is a lot faster, and in my opinion, more Brutalist.
My primary inspiration was addressing software and tool bloat in UIs rather than strictly adhering to every principle set forth by David Bryant Copeland. I don't find it convincing that this site "isn't brutalist" compared to really any other experience apart from the Main HN site, and I would argue the overall experience is more brutalist in its performance and scrolling behavior.
As a side note: I generally don't like Brutalist architecture that much although I believe it is unfairly maligned. I visited the Salk Institute once and enjoyed it though (https://www.archdaily.com/61288/ad-classics-salk-institute-l...).
-
Ask HN: Who is hiring? (April 2024)
- Staff Software Engineer ($275k/yr): https://tailwindcss.com/careers/staff-software-engineer
We're small, independent, and profitable, with a team of just 6 people doing millions in revenue, and growing sustainably every year. You'd work directly with the founders on open-source software used by millions of people.
If you like the idea of working on a small team that cares about craft and isn't trying to achieve VC scale, I think this is a pretty awesome place to do your best work.
-
Deploy a Golang serverless function for a demo form with htmx
Instead of Booststrap, I used Tailwind CSS as the CSS library.
-
Shared Tailwind Setup For Micro Frontend Application with Nx Workspace
Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.
-
Building a Dynamic Job Board with Issues Github, Next.js, Tailwind CSS and MobX-State-Tree
Basic knowledge of Tailwind CSS and MobX-State-Tree
What are some alternatives?
primevue - Next Generation Vue UI Component Library
flowbite - Open-source UI component library and front-end development framework based on Tailwind CSS
vite - Next generation frontend tooling. It's fast!
antd - An enterprise-class UI design language and React UI library
bootstrap-vue-next - Early (but lovely) implementation of Vue 3, Bootstrap 5 and Typescript
unocss - The instant on-demand atomic CSS engine.
Quasar Framework - Quasar Framework - Build high-performance VueJS user interfaces in record time
windicss - Next generation utility-first CSS framework.
ant-design-vue - 🌈 An enterprise-class UI components based on Ant Design and Vue. 🐜
emotion - 👩🎤 CSS-in-JS library designed for high performance style composition
buefy - Lightweight UI components for Vue.js based on Bulma
Material UI - Ready-to-use foundational React components, free forever. It includes Material UI, which implements Google's Material Design.