What is Font Awesome and what are its top alternatives?
Top Alternatives to Font Awesome
- Google Fonts
A library of 915 free licensed fonts, an interactive web directory for browsing the library, and APIs for conveniently using the fonts via CSS and Android. ...
Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...
Premium designed icons for use in web, iOS, Android, and desktop apps. Support for SVG and web font. Completely open source and MIT licensed. ...
- Material Design
Material Design is a unified system that combines theory, resources, and tools for crafting digital experiences. ...
It is an online service which offers a subscription library of high-quality fonts. The fonts may be used directly on websites or synced via Adobe Creative Cloud to applications on the subscriber's computers. ...
It is the art and technique of arranging type to make written language legible, readable, and appealing when displayed. This term is also applied to the style, arrangement, and appearance of the letters, numbers, and symbols created by the process. ...
It is a set of 450+ free MIT-licensed high-quality SVG icons for you to use in your web projects. Available as basic SVG icons and via first-party React and Vue libraries. ...
- JetBrains Mono
It is the free and open-source typeface for developers that makes it easier to read code. ...
Font Awesome alternatives & related posts
- Restrict character set7
related Google Fonts posts
Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:
- Vue Styleguidist as our style guide and pool of developed Vue.js components
- Vuetify as Material Component Framework (for fast app development)
- TypeScript as programming language
- Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
- ESLint, TSLint and Prettier for coding style and code analyzes
- Jest as testing framework
- Google Fonts and Font Awesome for typography and icon toolkit
- NativeScript-Vue for mobile development
The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:
- Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
- Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
- Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
- Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
- Large scaling. Vue.js can help to develop pretty large reusable templates.
- Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
- UI components1.2K
- Great docs779
- HTML, CSS, and JS framework472
- Open source411
- Widely used374
- HTML framework242
- Mobile first77
- Easy setup77
- Great grid system58
- Great community52
- Future compatibility38
- Very powerful foundational front-end framework28
- Build faster prototypes19
- Good for a person who hates CSS9
- Easy to setup and learn4
- Love it4
- Rapid development4
- Great and easy to use3
- Provide angular wrapper2
- Great and easy2
- Powerful grid system, Rapid development, Customization2
- Great customer support2
- Clean and quick frontend development2
- Great and easy to make a responsive website2
- Sprzedam opla2
- Easy to use2
- Responsive design1
- Painless front end development1
- Design Agnostic1
- So clean and simple1
- Numerous components1
- Love the classes?1
- Pre-Defined components1
- It's fast1
- Felxible, comfortable, user-friendly1
- The fame1
- Easy setup21
- Not tied to jQuery1
- Every site uses the defaults16
- Grid system break points aren't ideal15
- Too much heavy decoration in default look14
- Verbose styles8
- Super heavy1
related Bootstrap posts
I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.
I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).
As per my work experience and knowledge, I have chosen the followings stacks to this mission.
Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.
Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.
Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.
Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.
Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.
Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.
Happy Coding! Suggestions are welcome! :)
For Etom, a side project. We wanted to test an idea for a future and bigger project.
What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.
You kind of need a map to work as a proxy between the software and Google Maps API.
We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.
Thanks to all the people behind Create React App it's easier to start any React application.
We also chose a module called Reactstrap which is Bootstrap UI in React components.
An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to
Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.
- Ui Components2
- Looks Amazing1
related Ionicons posts
- They really set a new bar in design4
- An intuitive design3
- Simply, And Beautiful2
- Many great libraries2
- Sometimes, it can hang the browser2
related Material Design posts
TL;DR: Shall I keep developing with Nuxt.js 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?
Long version: We have an old web application running on AngularJS and Bootstrap for frontend. It is mostly a user interface to easily read and post data to our engine.
We want to redo this web application. Started from scratch using the newest version of Angular 2+ and Material Design for frontend. We haven't even finished rewriting half of the application and it is becoming dreadful to work on.
- The cold start takes too much time
- Every little change reload the whole page. Seconds to minutes of development lost looking at a loading blank page just changing css
- Code maintainability is getting worse... again... as the application grows, since we must create everytime 5 files for a new page (html, component.ts, module.ts, scss, routing.ts)
I'm currently trying to code a Proof of Concept using Nuxt.js and Tailwind CSS. But the thing is, Vue.js 3 is out and has interesting features such as the composition API, teleport and fragments. Also we wish to use the Vite frontend tooling, to improve our time developing regardless of our application size. It feels like a better alternative to Webpack, which is what Nuxt 2 uses.
I'm already trying Nuxt.js with the nuxt-vite experimental module, but many nuxt modules are still incompatible from the time I'm posting this. It is also becoming cumbersome not being able to use teleport or fragments, but that can be circumvented with good components.
What I'm asking is, what should be the wisest decision: keep developing with Nuxt 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?
I am a bit confused when to choose Bootstrap vs Material Design or Tailwind CSS, and why? I mean, in which kind of projects we can work with bootstrap/Material/Tailwind CSS? If the design is made up on the grid, we prefer bootstrap, and if flat design, then material design. Similarly, when do we choose tailwind CSS?
Any suggestion would be appreciated?