![tutorialspint ruby on rails editor tutorialspint ruby on rails editor](https://www.tutorialspoint.com/ruby-on-rails/images/no-book-message.gif)
Most articles and tutorials date more that 4 years. New Rails features have little coverage online.Some of the problems that I encounter had already been solved 5 years ago.Rails has very good official documentation.In this article, I am creating a very simple blog app with the features that cause me the most trouble as a Rails newbie, such as adding the Active Admin panel, soft-deletes, modifying the Trix editor, and more. At some point, to find the solution to a problem, I had to dig deep online or I end up implementing workaround solutions. Sometimes it was a bit frustrating because all the articles and tutorials I found online were over 5 years old. For this reasons we decided not to complicate the project too much and keep a monolith architecture using Ruby on Rails integrating the React-Rails gem to render some React components.
![tutorialspint ruby on rails editor tutorialspint ruby on rails editor](https://image.slidesharecdn.com/coffeescript-101208211854-phpapp01/95/coffee-script-15-728.jpg)
I like this approach but a couple of months ago in my work we had to make a simple application in a short amount of time, similar to a blog, it had to be fast and simple, and I wanted to try a technology I haven't used before. Which means having to develop and maintain two applications. Lately, the architecture of the web apps that I have been working on had a separate client and server. I've spent the last few years making all kinds of applications, from desktop apps using Java, Python or Qt to web applications using mostly a MERN stack. Rich text with ActionText for Blog content.React component with React-Rails for the comments of the blog.Platform administration panel with Active Admin.The idea of this article is that someone can read it and by executing all the steps have a simple blog with: