micromark VS Font-Awesome

You mean when fetching the data on the client, you don't want it to come along with the styling? Is it in a tag?

I just want to wrap my head around the problem more properly, and what you're trying to solve

Also, if the blog post data was created with styling in the first place then what's the purpose for removing the styling? The only reason I can imagine is that the same blog post data would be used for two different purposes, one needing the styled version while the other would need the unstyled version. Otherwise, if the data is only ever going to be used without styles, I would just make sure they're added without styles in the first

Also, if you want to store markdown instead of html in the database, you can parse it into HTML on the client using a library like micromark (https://github.com/micromark/micromark) or similar

React markdown vs remark react-markdown is a library that provides the React component to render the Markdown markup while remark is a markdown preprocessor built on micromark. It inspects, parses and transforms markdowns.

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.