add rspec to rails

Author: daniel-carvalho-runtime-revolution

docs/rails/on_boarding/01_base/chapter_I.md

@@ -1,51 +1,68 @@
-# Chapter I
+# Chapter I - Introduction to Ruby
 `(avr. time for this chapter: 1 day)`
 
-Hi. 
-Ruby is an interpreted, high-level, general-purpose programming language which supports multiple programming paradigms. It was designed with an emphasis on programming productivity and simplicity. In Ruby, everything is an object, including primitive data types. It was developed in the mid-1990s by Yukihiro "Matz" Matsumoto in Japan.
+Ruby is an interpreted, high-level, general-purpose programming language that supports multiple programming paradigms. Designed with an emphasis on programming productivity and simplicity, Ruby treats everything as an object, including primitive data types. It was developed in the mid-1990s by Yukihiro "Matz" Matsumoto in Japan.
 
-Ruby is dynamically typed and uses garbage collection and just-in-time compilation. It supports multiple programming paradigms, including procedural, object-oriented, and functional programming. 
+Ruby is dynamically typed and uses garbage collection and just-in-time compilation. It supports procedural, object-oriented, and functional programming paradigms.
 
-In this chapter the objective is to look at the world of ruby, which will serve as a basis for the next chapters where we will be delving into one of the frameworks that work with ruby, Rails.
+In this chapter, the objective is to explore the fundamentals of Ruby, which will serve as the foundation for the next chapters where you will delve into Rails, one of the most popular frameworks built with Ruby.
 
-The idea is to familiarize yourself with the basics.
+## Ruby in Twenty Minutes
 
-***So, let's code***
+A concise Ruby tutorial that should take no more than 20 minutes to complete.
 
+### Steps to implement:
 
-# Let's Start
+1. Ensure Ruby is installed on your system
+2. Complete the quick start tutorial
+3. Experiment with the Interactive Ruby Shell (IRB)
 
-## Ruby in Twenty Minutes (quick start)
+> Reference: [Ruby Quick Start](https://www.ruby-lang.org/en/documentation/quickstart/)
 
-This is a small Ruby tutorial that should take no more than 20 minutes to complete: [https://www.ruby-lang.org/en/documentation/quickstart/](https://www.ruby-lang.org/en/documentation/quickstart/) 
+> Installation Guide: [Ruby Installation](https://www.ruby-lang.org/en/documentation/installation/)
 
-It makes the assumption that you already have Ruby installed. If not, checkout this link: [https://www.ruby-lang.org/en/documentation/installation/] (https://www.ruby-lang.org/en/documentation/installation/)
+## Ruby Koans
 
-## Ruby Koans 
+The Koans guide you along the path to enlightenment in order to learn Ruby. The goal is to understand the Ruby language, syntax, structure, and common functions and libraries through test-driven exercises.
 
-The Koans walk you along the path to enlightenment in order to learn Ruby. The goal is to learn the Ruby language, syntax, structure, and some common functions and libraries.  Testing is not just something we pay lip service to, but something we live. It is essential in your quest to learn and do great things in the language.
-http://rubykoans.com
+### Steps to implement:
 
--   **Recommended Koans**:
-	-   About_arrays.rb
-	-   About_blocks.rb
-	-   About_classes.rb
-	-   About_control_statements.rb
-	-   About_hashes.rb
-	-   About_iteration.rb
-	-   About_methods.rb
-	-   About_strings.rb
-	-   about_symbols.rb
+1. Clone or download the Ruby Koans repository
+2. Run the koans and fix each failing test
+3. Focus on the recommended koans listed below
+
+> Reference: [Ruby Koans](http://rubykoans.com)
+
+### Recommended Koans:
+
+- `about_arrays.rb`
+- `about_blocks.rb`
+- `about_classes.rb`
+- `about_control_statements.rb`
+- `about_hashes.rb`
+- `about_iteration.rb`
+- `about_methods.rb`
+- `about_strings.rb`
+- `about_symbols.rb`
 
 ## Ruby Tutorial
 
-This tutorial has been prepared for beginners to help them understand the basic to advanced concepts related to Ruby Scripting languages.
-https://www.tutorialspoint.com/ruby/index.htm 
+This tutorial covers basic to advanced concepts related to Ruby scripting.
+
+### Steps to implement:
+
+1. Read and practice the following topics
+2. Write small code snippets to reinforce each concept
+3. Understand how these concepts apply to real-world scenarios
+
+> Reference: [TutorialsPoint Ruby](https://www.tutorialspoint.com/ruby/index.htm)
+
+### Topics to cover:
 
--   Ruby - Classes and Objects
--   Ruby - Variables
--   Ruby - Operators
--   Ruby - Methods
--   Ruby - Blocks (same as Koans)
--   Ruby - Modules
--   Ruby - Exceptions
+- Ruby - Classes and Objects
+- Ruby - Variables
+- Ruby - Operators
+- Ruby - Methods
+- Ruby - Blocks
+- Ruby - Modules
+- Ruby - Exceptions

docs/rails/on_boarding/01_base/chapter_II.md

@@ -1,37 +1,54 @@
-
-# Chapter II
+# Chapter II - Introduction to Ruby on Rails
 `(avr. time for this chapter: 2 days)`
 
-Ruby on Rails (simplified as Rails) is a server-side web application framework written in Ruby under the MIT License. Rails is a model–view–controller (MVC) framework, providing default structures for a database, a web service, and web pages. 
+Ruby on Rails (commonly referred to as Rails) is a server-side web application framework written in Ruby under the MIT License. Rails follows the Model-View-Controller (MVC) architectural pattern, providing default structures for databases, web services, and web pages.
+
+In this chapter, the objective is to understand how Rails works. This is primarily a learning phase—you do not need to write extensive code, only what helps reinforce your understanding. Focus on comprehension rather than implementation.
+
+The recommended course has several chapters, but for this onboarding, we focus on the essentials that will prepare you for the practical exercises ahead.
+
+## Udemy Course
+
+We recommend the following comprehensive course for learning Ruby on Rails.
+
+### Steps to implement:
+
+1. Obtain your course credentials from your tutor
+2. Watch the recommended chapters listed below
+3. Take notes on key concepts
+4. Repeat sections if clarification is needed
+
+> Reference: [The Complete Ruby on Rails Developer Course](https://www.udemy.com/course/the-complete-ruby-on-rails-developer-course)
+
+### Recommended Chapters:
+
+**Chapter 2 - Introduction**
+
+- Rails basics Introduction (1st video)
 
-This second chapter is geared towards learning rails. You don't need to write code (just what you think will help you), you need to understand how rails works
+**Chapter 3 - MVC and Application Structure**
 
-The course we offer you has several chapters that you can read, but in this case we are focused on the essentials for the next chapters.
+- Model, View, Controller and Rails App Structure
+- Root route, controller, more MVC and say 'Hello World!'
+- Structure of a Rails application
+- The back-end: CRUD, scaffold and wrap-up
 
-The idea is to pay attention to the chapter you are listening to and repeat it if you have any doubts.
-  
-***So, let's learn some new things***
+**Chapter 4 - Working with Data**
 
+- Tables, migrations and naming conventions
+- Validations
+- Show articles (route, action and view)
+- Articles index
+- Forms - build a new article creation form
+- Edit and update: update existing articles
+- Delete: delete articles
+- DRY (Don't Repeat Yourself) code - refactoring and partials
 
-# Udemy Course
+**Chapter 6 - Associations (Part 1)**
 
-Currently, we use this course: https://www.udemy.com/course/the-complete-ruby-on-rails-developer-course
-> get your credentials with your tutor.
+- One to many association
 
+**Chapter 7 - Associations (Part 2)**
 
--   Rails basics Introduction-> Chapter 2 (1st video)
--   Model, View, Controller and Rails App Structure (Chapter 3)
--   Root route, controller, more MVC and say 'Hello World!' (Chapter 3)
--   Structure of a Rails application (Chapter 3)
--   The back-end: CRUD, scaffold and wrap-up (Chapter 3)
--   Tables, migrations and naming conventions (Chapter 4)
--   Validations (Chapter 4)
--   Show articles (route, action and view) (Chapter 4)
--   Articles index (Chapter 4)
--   Forms - build a new article creation form (Chapter 4)
--   Edit and update: update existing articles (Chapter 4)
--   Delete: delete articles (Chapter 4)
--   DRY (Don't Repeat Yourself) code - refactoring and partials (Chapter 4)
--   One to many association (Chapter 6)
--   Many-to-many association - introduction (Chapter 7)
--   Many-to-many association - back-end implementation (Chapter 7)
+- Many-to-many association - introduction
+- Many-to-many association - back-end implementation

docs/rails/on_boarding/01_base/chapter_III.md

@@ -1,35 +1,58 @@
-
-# Chapter III
+# Chapter III - Practical Exercise: Ebook Store (Part 1)
 `(avr. time for this chapter: 3 to 4 days)`
 
-Moving on from the theoretical part, we move on to the practical part.
+Moving from theory to practice, this chapter presents a hands-on exercise where you will build a Rails application from scratch.
+
+The requirements listed below are intentionally generic. This approach mirrors real-world scenarios where client requirements are often open to interpretation. As an engineer, you are expected to analyze, design, and implement solutions based on the given specifications. If you have questions or need clarification, discuss ideas with your tutor—just as you would in a professional environment.
+
+These topics align with what you learned in the previous chapter, so the implementation should feel familiar.
+
+## Project Setup
+
+### Steps to implement:
+
+1. Create a new Rails application using MVC architecture
+2. Initialize a Git repository and grant access to your tutor
+3. (Optional) Deploy the application to a platform of your choice (e.g., [Render](https://render.com), [Heroku](https://heroku.com))
+
+## Application Requirements
+
+Build an online ebook store application. The platform will have sellers and buyers. You will not implement shopping cart logic, but you will implement functionalities related to purchasing actions.
+
+### Core Features
+
+#### User Management
+
+- Create CRUD operations for Users (can be either seller or buyer)
+- Implement user status management (enable/disable)
+
+#### Ebook Management
 
-You'll find several topics listed below, with very little detail. The details do not exist on purpose, it is in everyone's interest to understand how you can infer, through a practical case, the same thing that would happen in real life with a client. As an engineer you know how to think, and if you have doubts you can always do what you would do in a real project, discuss ideas. You can also design your solution before trying it out.
+- Create CRUD operations for Ebooks
+- Implement status workflow for Ebooks (Draft → Pending → Live)
+- Store PDF preview drafts available for download
 
-These topics are still the most basic so you don't need to build or model a very elaborate system, if you notice they are linked to the course you just saw in the previous chapter. 
+#### Navigation
 
-***So, let's code***
+- Add a navigation menu with links to Ebooks and Users sections
 
-# Let's do some basic code
+### Purchase Functionality
 
-> create a simple rails application MVC
-> open a git repository and give access to your tutor
-> IF you have time deploy it, you can choose the platform (render.com, heroku.com)
+> Note: For email functionality, you do not need to send actual emails. Create the notification logic only, or use [Mailcatcher](https://mailcatcher.me) for local testing.
 
-Let's build an application from scratch. The application will have as its theme the sale of ebooks online. A virtual store where you will have sellers and buyers. You won't have to implement the cart's logic, but some functionalities related to some actions that are performed when buying an item.
+#### Steps to implement:
 
-As previously mentioned, all the points below are generic, it is up to the developer who develops to build an architecture consistent with the proposed objective
+1. Implement an ebook purchase action (without cart logic)
+2. The purchase button should trigger the following actions:
+   - Send an email to the seller with their commission (10% of the book price)
+   - Send an email with ebook statistics (examples below)
+   - Register the purchase in the database
 
- - List item (ebooks)
- - Add navigation menu with ebook and users
- - Create CRUD for the user (seller or a buyer)
- - Update Status of the user (enable or disable) 
- - Create CRUD for Ebooks
- - Update Status for the Ebook (Draft, Pending, Live)
- - Store PDF with the preview draft for download
+#### Suggested Statistics to Track:
 
-> the emails referenced below do not need to be sent, it is only necessary to create the notification logic, or you can use **mailcatcher.me**
+- Number of times the ebook was purchased
+- Number of times the preview PDF was viewed
+- Number of times the ebook page was visited
+- Visitor information (IP, browser, location, etc.)
 
-- buy ebook (**don't apply cart logic**), 
-	- the buy button should trigger 2 actions (send mail to the user with the fee he get from the bought ebook 10% from the book price, send an email with all statistics from that ebook (how many times the ebook was bought, how many times the draft pdf has been viewed, how many times ebook has been seen, IP, browser, location, etc ... )) **note: you can find different metrics and not use these**
-	- Register the book purchase
+> Note: You may define different metrics based on your implementation approach.

docs/rails/on_boarding/01_base/chapter_IV.md

@@ -1,26 +1,50 @@
-
-# Chapter IV
+# Chapter IV - Practical Exercise: Ebook Store (Part 2)
 `(avr. time for this chapter: 3 days)`
 
-This will be the last topic that closes onBoarding.
-The topics are broader, which will force you to think better before starting to implement. Following the previous exercise, here's your challenge
+This chapter concludes the base onboarding with advanced features for your ebook store application. The topics are broader and will require more careful planning before implementation.
+
+Continue building upon the application from Chapter III.
+
+## Project Finalization
+
+### Steps to implement:
+
+1. Create pull requests for your features
+2. Merge all completed code into the main branch
+3. (Optional) Deploy the final application to a platform of your choice (e.g., [Render](https://render.com), [Heroku](https://heroku.com))
+
+## Advanced Features
+
+### Image Management
+
+- Implement user profile image upload and storage
+- Implement ebook cover image upload and storage
+
+### Authentication System
+
+Implement a custom authentication system **without using Devise**.
+
+#### Steps to implement:
+
+1. Create user registration (sign up) functionality
+2. Create user login (sign in) functionality
+3. Implement `sign_in` and `sign_out` helper methods
+4. On successful login, redirect users to their previous location (not the root URL)
+
+### Password Management
+
+- Create a Rake task that forces password updates every 6 months
+- Send a welcome email when a new user registers
 
-***So, let's finish this***
+> Note: For email functionality, create the notification logic only, or use [Mailcatcher](https://mailcatcher.me) for local testing.
 
-# Let's do some basic code
+### Tags System
 
-> commit your pull request and in the end merge all the code into (main/master)
-> IF you have time deploy it, you can choose the platform (render.com, heroku.com, etc ...)
+#### Steps to implement:
 
-- Store user image profile
-- Store ebook image cover profile
-- Implement Authentication  **without devise**. sign up and sign in
-- on Successfully Login redirect to same point where you were and not the root url
-- Force to update password every 6 months
-- send an welcome mail when a new user is registered
-- Implement a Tags System
-	-	Filter Tags on ebooks 
-	-	Filter ebooks by user
+1. Implement a tagging system for ebooks
+2. Add filtering functionality:
+   - Filter ebooks by tags
+   - Filter ebooks by user (seller)
 
-> when a user has no articles it will not show on filters list
-> the emails referenced below do not need to be sent, it is only necessary to create the notification logic, or you can use **mailcatcher.me**
+> Note: Users with no ebooks should not appear in the filter list.