Google Fonts VS Font-Awesome

I first checking out any good fonts on Google font that fits the theme of the website. I select the Nunito as I could feel the playful vibe behind it.

Visit Google Fonts and search for Lusitana to see what options are available.

Next I spruced up my form's visuals a bit by heading to Google Fonts and finding one that had camping vibes - eventually landing on Amatic SC. Then I had the wild idea of making the form look like a piece of paper, so that I could make the submit button fold the paper up into an envelope or paper airplane and fly off screen if it was submitted successfully (This was EXTREMELY high hopes and I didn't even get around to trying to start this animation in the time I allotted myself 😂). I started by trying to find a crumpled paper look on sites like Hero Patterns, but eventually found myself on this codepen:

BeerCSS supports Material Fonts by default, here is the list of all icons: https://fonts.google.com/

Google Fonts (https://fonts.google.com/)

Google Fonts

==>Click here to access Google Fonts!

==> Click here to visit Google Fonts! ==> Click here to visit Adobe Fonts!

the i element is the icon of the button, I'm using fontawesome.com for the icon, the class fa-apple retrives Apple icon for us.

Icons: Fontawesome Development: HTML, SCSS, JavaScript Deployment: Github + Netlify

1. Font Awesome

For generic icons (i.e. you just need a d6 and not a system-specific d6 option), Foundry has Font Awesome which are easy to search, then copy and insert, and always look good inline.

The following is an example of defining Font Awesome:

Of course, we have many different ways of solving this problem. Some of the most common include pre-existing third-party icon libraries (such as Font Awesome), icons bundled into a third-party component library (like the Kendo UI Icons), or a completely custom set of icons designed and maintained by your design team. Obviously, going 100% custom will require more work (on both the design and dev side), but might be worth it to achieve a truly unique look – or if the UI will require icons for uncommon symbols or concepts.

The featured GitHub projects are dynamically retrieved through the power of the GitHub GraphQL API. The blog posts are seamlessly pulled in using the Dev.to API. Additionally, Redis is used to cache the GitHub and Dev.to API responses for 1 hour to reduce the number of API calls. Icons are provided by Font Awesome through their kit from the CDN. I've also implemented the new View Transition API feature to enhance the user experience.

Firstly, unlike the name https://fontawesome.com/ isn't for fonts.