trix VS Font-Awesome

Trix is simple and easy to use for basic writing like a blog. It’s what Basecamp and HEY both use (it was built by 37signals and is the default in Rails)

https://trix-editor.org/

Trix was the winner. It was easy to style, is well maintained, has documentation for embedding it into a form, is easy to create custom keyboard shortcuts for, has great examples on how to save/load content or modify it with javascript.

In some case, you may need to allow the user to upload the file in the text editor like Trix editor. However, you current configuration not allowed it, you need to configure the CORS. Here the configuration

I inspected the text editor and it looks like it's something called Trix. The example on their website has a hyperlink button. No idea how to add links in StoryGraph though, besides the workaround the other user mentioned. Maybe ask Nadia on Instagram or Twitter - she's super responsive!

I'm sure something like Trix (used in Ruby on Rails) would probably do the job - https://trix-editor.org/

For this, you can add a small, isolated component to the page. An example from Rails is the Trix rich text editor: it is a standard web component.

I have been implementing a kind of blog builder using ActionText and Trix. However, understanding how Trix works, customizing it, and making image uploads possible, seems not very well documented. Also, looking at Trix's Github page there doesn't seem to be a lot of activity.

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.