**Creating and using views with ERB and HAML** In this topic, we will explore the world of views in Ruby on Rails, focusing on ERB (Embedded RuBy) and HAML (HTML Abstraction Markup Language). We will delve into the benefits of using views, learn how to create and use them, and discover how to optimize your code organization. **What are Views in Ruby on Rails?** In Ruby on Rails, views are responsible for rendering the user interface of your application. They receive data from your controllers and display it to the user in a format that is easy to understand. Think of views as the "face" of your application, presenting the data in a way that is visually appealing and user-friendly. **ERB (Embedded RuBy) Templating** ERB is a templating engine that allows you to embed Ruby code within your HTML templates. This provides a powerful way to dynamically generate content on the fly. ERB templates are written in a syntax that is similar to Ruby code, making it easy to learn and use. **Example of an ERB Template** ```erb <h1><%= title %></h1> <ul> <% users.each do |user| %> <li><%= user.name %></li> <% end %> </ul> ``` In this example, the `title` variable is passed from the controller to the view, and the `users` array is also passed. The `each` method is used to iterate over the array, and the `name` attribute of each user is displayed. **HAML (HTML Abstraction Markup Language)** HAML is a templating engine that allows you to write HTML code in a more concise and readable way. It uses a syntax that is similar to Ruby code, but with a focus on HTML structure. **Example of a HAML Template** ```haml %html %head %title= title %body %ul - users.each do |user| %li= user.name ``` In this example, the `title` variable is passed from the controller to the view, and the `users` array is also passed. The `each` method is used to iterate over the array, and the `name` attribute of each user is displayed. **Benefits of Using Views** Using views in your Ruby on Rails application provides several benefits, including: * Separation of Concerns: Views are responsible for rendering the user interface, while controllers handle business logic and models handle data storage. * Code Organization: Views help to organize your code in a logical and maintainable way. * Reusability: Views can be reused across multiple controllers and applications. **Best Practices for Creating Views** When creating views, keep the following best practices in mind: * Keep your views concise and focused on rendering the user interface. * Use variables and parameters to pass data from your controllers to your views. * Use templates to separate your view logic from your presentation logic. * Use HAML or ERB to write your templates in a concise and readable way. **Practical Takeaways** * Use views to separate your presentation logic from your business logic. * Use variables and parameters to pass data from your controllers to your views. * Use templates to organize your view logic and make it more maintainable. **Exercise** Create a new view for a simple user list page. Use ERB or HAML to render the user list, and pass the `users` array from your controller to the view. **Leave a comment or ask for help if you have any questions or need further clarification on any of the concepts covered in this topic.** **Next Topic:** Layouts and partials for better code organization. In this next topic, we will explore how to use layouts and partials to improve the organization and maintainability of your code. We will learn how to create layouts, partials, and use them to render common templates and components.