glimmer-dsl-web 0.2.3 → 0.2.5

data/README.md

@@ -1,15 +1,32 @@
-# [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 />](https://github.com/AndyObtiva/glimmer) Glimmer DSL for Web 0.2.3 (Beta)
-## Ruby in the Browser Web GUI Frontend Library
+# [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 />](https://github.com/AndyObtiva/glimmer) Glimmer DSL for Web 0.2.5 (Beta)
+## Ruby in the Browser Web Frontend Framework
+### Finally, Ruby Developer Productivity, Happiness, and Fun in the Frontend!!!
 [![Gem Version](https://badge.fury.io/rb/glimmer-dsl-web.svg)](http://badge.fury.io/rb/glimmer-dsl-web)
 [![Join the chat at https://gitter.im/AndyObtiva/glimmer](https://badges.gitter.im/AndyObtiva/glimmer.svg)](https://gitter.im/AndyObtiva/glimmer?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
 **(Based on Original [Glimmer](https://github.com/AndyObtiva/glimmer) Library Handling World’s Ruby GUI Needs Since 2007. Beware of Imitators!)**
 
-[Glimmer](https://github.com/AndyObtiva/glimmer) DSL for Web enables building Web GUI frontends using [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c), as per [Matz's recommendation in his RubyConf 2022 keynote speech to replace JavaScript with Ruby](https://youtu.be/knutsgHTrfQ?t=789). It aims at providing the simplest, most intuitive, most straight-forward, and most productive frontend library in existence. The library follows the Ruby way (with [DSLs](https://martinfowler.com/books/dsl.html) and [TIMTOWTDI](https://en.wiktionary.org/wiki/TMTOWTDI#English)) and the Rails way ([Convention over Configuration](https://rubyonrails.org/doctrine)) in building Isomorphic Ruby on Rails Applications. It supports both Unidirectional (One-Way) [Data-Binding](#hello-data-binding) (using `<=`) and Bidirectional (Two-Way) [Data-Binding](#hello-data-binding) (using `<=>`). Dynamic rendering (and re-rendering) of HTML content is also supported via [Content Data-Binding](#hello-content-data-binding). And, modular design is supported with [Glimmer Web Components](#hello-component). You can finally live in pure Rubyland on the Web in both the frontend and backend with [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web)!
+**(Talk Videos: [Intro to Ruby in the Browser](https://youtu.be/4AdcfbI6A4c?si=MmxOrkhIXTDHQoYi) & [Frontend Ruby with Glimmer DSL for Web](https://youtu.be/rIZ-ILUv9ME?si=raygUXVPd_7ypWuE))**
+
+You can finally have Ruby developer happiness and productivity in the Frontend! No more wasting time splitting your resources across multiple languages, using badly engineered, over-engineered, or premature-optimization-obsessed JavaScript libraries, fighting JavaScript build issues (e.g. webpack), or rewriting Ruby Backend code in Frontend JavaScript. With [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c), you can have an exponential jump in development productivity (2x or higher), time-to-release (1/2 or less time), cost (1/2 or cheaper), and maintainability (~50% the code that is simpler and more readable) over JavaScript libraries like React, Angular, Ember, Vue, and Svelte, while being able to reuse Backend Ruby code as is in the Frontend for faster interactions when needed. [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c) finally fulfills every highly-productive Rubyist's dream by bringing Ruby productivity fun to Frontend Development, the same productivity fun you had for years and decades in Backend Development.
+
+[Glimmer](https://github.com/AndyObtiva/glimmer) DSL for Web enables building Web Frontends using [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c), as per [Matz's recommendation in his RubyConf 2022 keynote speech to replace JavaScript with Ruby](https://youtu.be/knutsgHTrfQ?t=789). It supports Rails' principle of the One Person Framework by not requiring any extra developers with JavaScript expertise, yet enabling Ruby (Backend) Software Engineers to develop the Frontend with Ruby code that is better than any JavaScript code produced by JS developers. It aims at providing the simplest, most intuitive, most straight-forward, and most productive frontend framework in existence. The framework follows the Ruby way (with [DSLs](https://martinfowler.com/books/dsl.html) and [TIMTOWTDI](https://en.wiktionary.org/wiki/TMTOWTDI#English)) and the Rails way ([Convention over Configuration](https://rubyonrails.org/doctrine)) in building Isomorphic Ruby on Rails Applications. It provides a Ruby [HTML DSL](#usage), which uniquely enables writing both structure code and logic code in one language. It supports both Unidirectional (One-Way) [Data-Binding](#hello-data-binding) (using `<=`) and Bidirectional (Two-Way) [Data-Binding](#hello-data-binding) (using `<=>`). Dynamic rendering (and re-rendering) of HTML content is also supported via [Content Data-Binding](#hello-content-data-binding). Modular design is supported with [Glimmer Web Components](#hello-component). And, a Ruby CSS DSL is supported with the included [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css). Many [samples](#samples) are demonstrated in the [Rails sample app](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app) (there is a very minimal [Standalone [No Rails] static site sample app](https://github.com/Largo/glimmer-dsl-web-standalone-demo) too). You can finally live in pure Rubyland on the Web in both the frontend and backend with [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web)!
+
+[Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) aims to be a very simple Ruby-based drop-in replacement for your existing JavaScript Frontend library (e.g. React, Angular, Vue, Ember, Svelte) or your JavaScript Frontend layer in general. It does not change how your Frontend interacts with the Backend, meaning you can continue to write Rails Backend API endpoints as needed and make Ajax HTTP requests or read data embedded in elements, but from [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c). Whatever is possible in JavaScript is possible when using Glimmer DSL for Web as it integrates with any existing JavaScript library. The [Rails sample app](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app) demonstrates how to [make Ajax HTTP calls](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app/blob/master/app/assets/opal/sample_selector/models/sample_selector_presenter.rb) and how to [integrate with a JavaScript library](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app/blob/master/app/views/layouts/application.html.erb) (highlightjs) that performs [code syntax highlighting](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app/blob/master/app/assets/opal/sample_selector.rb).
+
+After looking through the [samples](#samples) below, read the [FAQ (Frequently Asked Questions)](#faq) to learn more about how Glimmer DSL for Web compares to other approaches/libraries like Hotwire (Turbo), Phlex, ViewComponent, Angular, Vue, React, Svelte, and other JS frameworks.
+
+Anyone not considering this kind of technology in 2024 is like someone stuck in the dark ages riding horse carriage (e.g. JavaScript developers using frameworks like React) despite flying cars having been invented already and providing exponential jumps in productivity (way more than small linear jumps provided by some JavaScript libraries). Obviously, those who do make this jump will end up winning their work over from customers and beating the competition while delivering the best Frontend value possible to customers.
+
+(Attention Software Engineers, Bloggers, and Contributors: Please use Glimmer DSL for Web in web projects, blog about it, and submit a PR with your article, project, and/or open-source-repo added to the README. Also, I give everyone permission to present this project at their local Ruby user group, local Software Engineering meetup, or Software Conferences outside of North America (e.g. Europe). I am willing to present at Software Conferences in North America and Japan (the birthplace of Ruby) only. If you want to have this project presented elsewhere, like in Europe or South America, feel free to prepare and give your own presentations of the project, and if needed, hit me up for help on the [Glimmer Gitter chat](https://gitter.im/AndyObtiva/glimmer?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge))
 
 **Hello, World! Sample**
 
-Glimmer GUI code in the frontend:
+(Note: in real app development, we build [Glimmer Web Components](#hello-component), but this sample is just introducing basic building blocks towards building [components](#hello-component))
+
+[lib/glimmer-dsl-web/samples/hello/hello_world.rb](/lib/glimmer-dsl-web/samples/hello/hello_world.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -37,9 +54,13 @@ You can also mount the `div` elsewhere by passing the `parent: parent_css_select
 
 **Hello, Button!**
 
+(Note: in real app development, we build [Glimmer Web Components](#hello-component), but this sample is just introducing basic building blocks towards building [components](#hello-component))
+
 Event listeners can be setup on any element using the same event names used in HTML (e.g. `onclick`) while passing in a standard Ruby block to handle behavior. `$$` gives access to JS global scope from Ruby to invoke functions like `alert`.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_button.rb](/lib/glimmer-dsl-web/samples/hello/hello_button.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -71,9 +92,13 @@ Screenshot:
 
 **Hello, Form!**
 
-[Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) gives access to all Web Browser built-in features like HTML form validations, input focus, events, and element functions from a very terse and productive Ruby GUI DSL.
+(Note: in real app development, we build [Glimmer Web Components](#hello-component), but this sample is just introducing basic building blocks towards building [components](#hello-component))
+
+[Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) gives access to all Web Browser built-in features like HTML form validations, input focus, events, and element functions from a very terse and productive Ruby HTML DSL. Also, you can apply CSS styles by including directly in Ruby code as a string, using [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css), or managing CSS completely separately using something like [SCSS](https://sass-lang.com/). The CSS techniques could be combined as well, like by managing common reusable CSS styles separately in SCSS, but adding component specific CSS styles in Ruby when it is more convenient.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_form.rb](/lib/glimmer-dsl-web/samples/hello/hello_form.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -227,9 +252,13 @@ Screenshot:
 
 **Hello, Data-Binding!**
 
+(Note: in real app development, we build [Glimmer Web Components](#hello-component), but this sample is just introducing basic building blocks towards building [components](#hello-component))
+
 [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) intuitively supports both Unidirectional (One-Way) Data-Binding via the `<=` operator and Bidirectional (Two-Way) Data-Binding via the `<=>` operator, incredibly simplifying how to sync View properties with Model attributes with the simplest code to reason about.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_data_binding.rb](/lib/glimmer-dsl-web/samples/hello/hello_data_binding.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -344,11 +373,15 @@ Screenshot:
 
 **Hello, Content Data-Binding!**
 
+(Note: in real app development, we build [Glimmer Web Components](#hello-component), but this sample is just introducing basic building blocks towards building [components](#hello-component))
+
 If you need to regenerate HTML element content dynamically, you can use Content Data-Binding to effortlessly
 rebuild HTML elements based on changes in a Model attribute that provides the source data.
 In this example, we generate multiple address forms based on the number of addresses the user has.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_content_data_binding.rb](/lib/glimmer-dsl-web/samples/hello/hello_content_data_binding.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -479,15 +512,17 @@ Screenshot:
 
 You can define Glimmer web components (View components) to reuse visual concepts to your heart's content,
 by simply defining a class with `include Glimmer::Web::Component` and encasing the reusable markup inside
-a `markup {...}` block. Glimmer web components automatically extend the Glimmer GUI DSL with new keywords
+a `markup {...}` block. Glimmer web components automatically extend the Glimmer HTML DSL with new keywords
 that match the underscored versions of the component class names (e.g. an `OrderSummary` class yields
-the `order_summary` keyword for reusing that component within the Glimmer GUI DSL). 
-You may insert a Glimmer component anywhere into a Rails View using `glimmer_component(component_path, *args)` 
+the `order_summary` keyword for reusing that component within the Glimmer HTML DSL).
+You may insert a Glimmer component anywhere into a Rails View using `glimmer_component(component_path, *args)`
 Rails helper (more about it in [Hello, glimmer_component Rails Helper!](#hello-glimmer_component-rails-helper)).
 Below, we define an `AddressForm` component that generates an `address_form` keyword, and then we
 reuse it twice inside an `AddressPage` component displaying a Shipping Address and a Billing Address.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_component.rb](/lib/glimmer-dsl-web/samples/hello/hello_component.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -567,9 +602,9 @@ end
 # AddressForm Glimmer Web Component (View component)
 #
 # Including Glimmer::Web::Component makes this class a View component and automatically
-# generates a new Glimmer GUI DSL keyword that matches the lowercase underscored version
+# generates a new Glimmer HTML DSL keyword that matches the lowercase underscored version
 # of the name of the class. AddressForm generates address_form keyword, which can be used
-# elsewhere in Glimmer GUI DSL code as done inside AddressPage below.
+# elsewhere in Glimmer HTML DSL code as done inside AddressPage below.
 class AddressForm
   include Glimmer::Web::Component
   
@@ -702,6 +737,8 @@ You may insert a Glimmer component anywhere into a Rails View using
 `glimmer_component(component_path, *args)` Rails helper. Add `include GlimmerHelper` to `ApplicationHelper`
 or another Rails helper, and use `<%= glimmer_component("path/to/component", *args) %>` in Views.
 
+[lib/glimmer-dsl-web/samples/hello/hello_glimmer_component_helper/address_form.rb](/lib/glimmer-dsl-web/samples/hello/hello_glimmer_component_helper/address_form.rb)
+
 Rails `ApplicationHelper` setup code:
 
 ```ruby
@@ -736,7 +773,7 @@ Rails View code:
 </div>
 ```
 
-Glimmer GUI code in the frontend (`app/assets/opal/address_form.rb`):
+Glimmer HTML DSL Ruby code in the frontend (`app/assets/opal/address_form.rb`):
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -901,9 +938,9 @@ Screenshot:
 
 **Hello, Paragraph!**
 
-To facilitate building formatted textual paragraphs in Ruby, thanks to [Glimmer](https://github.com/AndyObtiva/glimmer#dsl-engine), the most advanced DSL engine in Ruby, the Glimmer GUI DSL is advanced enough to intelligently behave differently under different situations, like when using HTML formatting elements: `<br>`, `<strong>`, `<em>`, `<br>`, `<i>`, `<sub>`, `<sup>`, `<del>`, `<ins>`, `<small>`, `<mark>`
+To facilitate building formatted textual paragraphs in Ruby, thanks to [Glimmer](https://github.com/AndyObtiva/glimmer#dsl-engine), the most advanced DSL engine in Ruby, the Glimmer HTML DSL is advanced enough to intelligently behave differently under different situations, like when using HTML formatting elements: `<br>`, `<strong>`, `<em>`, `<br>`, `<i>`, `<sub>`, `<sup>`, `<del>`, `<ins>`, `<small>`, `<mark>`
 
-Instead of returning Ruby objects that are nested as children within their parent, the Glimmer GUI DSL returns `String` objects directly that can be concatenated to or embedded within other `String` objects via interpolation.
+Instead of returning Ruby objects that are nested as children within their parent, the Glimmer HTML DSL returns `String` objects directly that can be concatenated to or embedded within other `String` objects via interpolation.
 
 This enables writing code like:
 
@@ -931,9 +968,11 @@ it returns a `String` to enable code like this:
 
 `p {"#{span('Yesterday, ', style: 'text-decoration: underline;')}Robert suggested adding a new #{em('feature', class: 'very-emphasized')} to our software product.#{br}}`
 
-In any case, below is a full example leveraging the Glimmer GUI DSL alternative approach when utilizing formatting elements underneath a paragraph.
+In any case, below is a full example leveraging the Glimmer HTML DSL alternative approach when utilizing formatting elements underneath a paragraph.
+
+[lib/glimmer-dsl-web/samples/hello/hello_paragraph.rb](/lib/glimmer-dsl-web/samples/hello/hello_paragraph.rb)
 
-Glimmer GUI code in the frontend:
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -994,7 +1033,9 @@ Screenshot:
 
 [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) provides the `observe(model, attribute) { ... }` keyword to employ the [Observer Design Pattern](https://en.wikipedia.org/wiki/Observer_pattern) as per [MVC](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) (Model View Controller), enabling Views to observe Models and update themselves in response to changes. If the `observe` keyword is used from inside a [Component](#hello-component), when the Component is removed or its top-level element is removed, the observer is automatically cleaned up. The need for such explicit observers is significantly diminished by the availablility of the more advanced Unidirectional [Data-Binding](#hello-data-binding) Support and Bidirectional [Data-Binding](#hello-data-binding) Support.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_observer.rb](/lib/glimmer-dsl-web/samples/hello/hello_observer.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1017,48 +1058,81 @@ class HelloObserver
   after_render do
     @number_input.value = @number_holder.number
     @range_input.value = @number_holder.number
-    # Observe Model attribute @number_holder.number for changes and update View
-    # Observer is automatically cleaned up if remove method is called on rendered HelloObserver
-    # or its top-level element
+    
+    # Observe Model attribute @number_holder.number for changes and update View elements.
+    # Observer is automatically cleaned up when `remove` method is called on rendered
+    # HelloObserver web component or its top-level markup element (div)
     observe(@number_holder, :number) do
       number_string = @number_holder.number.to_s
       @number_input.value = number_string unless @number_input.value == number_string
       @range_input.value = number_string unless @range_input.value == number_string
     end
-    # Bidirectional Data-Binding does the same thing automatically
-    # Just disable the observe block above as well as the oninput listeners below
-    # and enable the `value <=> [@number_holder, :number]` lines to try the data-binding version
-    # Learn more about Bidirectional and Unidirectional Data-Binding in hello_data_binding.rb
+    # Bidirectional Data-Binding does the same thing automatically as per alternative sample: Hello, Observer (Data-Binding)!
   end
   
   markup {
     div {
       div {
         @number_input = input(type: 'number', min: 0, max: 100) {
-          # oninput listener updates Model attribute @number_holder.number
+          # oninput listener (observer) updates Model attribute @number_holder.number
           oninput do
             @number_holder.number = @number_input.value.to_i
           end
-          
-          # Bidirectional Data-Binding simplifies the implementation significantly
-          # by enabling the following line and disabling oninput listeners as well
-          # as the after_body observe block observer
-          # Learn more about Bidirectional and Unidirectional Data-Binding in hello_data_binding.rb
-#           value <=> [@number_holder, :number]
         }
       }
       div {
         @range_input = input(type: 'range', min: 0, max: 100) {
-          # oninput listener updates Model attribute @number_holder.number
+          # oninput listener (observer) updates Model attribute @number_holder.number
           oninput do
             @number_holder.number = @range_input.value.to_i
           end
-          
-          # Bidirectional Data-Binding simplifies the implementation significantly
-          # by enabling the following line and disabling oninput listeners as well
-          # as the after_body observe block observer
-          # Learn more about Bidirectional and Unidirectional Data-Binding in hello_data_binding.rb
-#           value <=> [@number_holder, :number]
+        }
+      }
+    }
+  }
+end
+```
+
+Screenshot:
+
+![Hello, Observer!](/images/glimmer-dsl-web-samples-hello-hello-observer.gif)
+
+**Hello, Observer (Data-Binding)!**
+
+This is the data-binding edition of Hello, Observer!, which uses the `<=>` operator to perform bidirectional data-binding between a View property and a Model attribute, thus yield a lot less code that is declarative and is the most minimal code possible to express the requirements.
+
+[lib/glimmer-dsl-web/samples/hello/hello_observer_data_binding.rb](/lib/glimmer-dsl-web/samples/hello/hello_observer_data_binding.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
+
+```ruby
+require 'glimmer-dsl-web'
+
+class NumberHolder
+  attr_accessor :number
+  
+  def initialize
+    self.number = 50
+  end
+end
+
+class HelloObserver
+  include Glimmer::Web::Component
+  
+  before_render do
+    @number_holder = NumberHolder.new
+  end
+  
+  markup {
+    div {
+      div {
+        input(type: 'number', min: 0, max: 100) {
+          value <=> [@number_holder, :number]
+        }
+      }
+      div {
+        input(type: 'range', min: 0, max: 100) {
+          value <=> [@number_holder, :number]
         }
       }
     }
@@ -1074,7 +1148,7 @@ Screenshot:
 
 ![Hello, Observer!](/images/glimmer-dsl-web-samples-hello-hello-observer.gif)
 
-To get started, [Setup](#setup) Ruby gem, read [Usage](#usage) instructions, and check out more [Samples](#samples).
+To get started, [Setup](#setup) Ruby gem, read [Usage](#usage) instructions, and check out more [Samples](#samples) (including playing around with a [Rails sample app](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app)).
 
 --
 
@@ -1089,6 +1163,9 @@ Learn more about the differences between various [Glimmer](https://github.com/An
 - [Glimmer DSL for Web](#)
   - [Prerequisites](#prerequisites)
   - [Setup](#setup)
+    - [Rails 7](#rails-7)
+    - [Rails 6](#rails-6)
+    - [Standalone (No Rails)](#standalone-no-rails)
   - [Usage](#usage)
   - [Supported Glimmer DSL Keywords](#supported-glimmer-dsl-keywords)
   - [Coming from Glimmer DSL for Opal](#coming-from-glimmer-dsl-for-opal)
@@ -1097,7 +1174,9 @@ Learn more about the differences between various [Glimmer](https://github.com/An
       - [Hello, World!](#hello-world)
       - [Hello, Button!](#hello-button)
       - [Hello, Form!](#hello-form)
+      - [Hello, Form (MVP)!](#hello-form-mvp)
       - [Hello, Observer!](#hello-observer)
+      - [Hello, Observer (Data-Binding)!](#hello-observer)
       - [Hello, Data-Binding!](#hello-data-binding)
       - [Hello, Content Data-Binding!](#hello-content-data-binding)
       - [Hello, Component!](#hello-content-data-binding)
@@ -1126,11 +1205,13 @@ Learn more about the differences between various [Glimmer](https://github.com/An
 
 ## Setup
 
+You can setup Glimmer DSL for Web in [Rails 7](#rails-7), [Rails 6](#rails-6), or [Standalone (No Rails)](#standalone-no-rails).
+
 (NOTE: Keep in mind this is a Beta. If you run into issues, try to go back to a [previous revision](https://rubygems.org/gems/glimmer-dsl-web/versions). Also, there is a slight chance any issues you encounter are fixed in master or some other branch that you could check out instead)
 
 ### Rails 7
 
-Please follow the following steps to setup.
+Please follow these steps to setup.
 
 Install a Rails 7 gem:
 
@@ -1147,7 +1228,7 @@ rails new glimmer_app_server
 Add the following to `Gemfile`:
 
 ```
-gem 'glimmer-dsl-web', '~> 0.2.3'
+gem 'glimmer-dsl-web', '~> 0.2.5'
 ```
 
 Run:
@@ -1164,7 +1245,7 @@ Follow [opal-rails](https://github.com/opal/opal-rails) instructions, basically
 bin/rails g opal:install
 ```
 
-To enable the `glimmer-dsl-web` library in the frontend, edit `config/initializers/assets.rb` and add the following at the bottom:
+To enable the `glimmer-dsl-web` gem in the frontend, edit `config/initializers/assets.rb` and add the following at the bottom:
 
 ```ruby
 Opal.use_gem 'glimmer-dsl-web'
@@ -1220,7 +1301,7 @@ Edit and replace `app/assets/opal/opal_application.rb` content with code below (
 ```ruby
 require 'glimmer-dsl-web' # brings opal and other dependencies automatically
 
-# Add more require-statements or Glimmer GUI DSL code
+# Add more require-statements or Glimmer HTML DSL code
 ```
 
 ```ruby
@@ -1229,7 +1310,7 @@ require 'glimmer-dsl-web'
 require 'glimmer-dsl-web/samples/hello/hello_world.rb'
 ```
 
-If the `<body></body>` element (where the Glimmer GUI DSL adds elements by default) is not available when the JS file is loading, you need to put the code inside a `Document.ready? do; end` (but, it is recommended that you load the JS file after the parent element like `<body></body>` is in the page already for faster performance, which is guaranteed automatically by using `glimmer_component`, mentioned in details below):
+If the `<body></body>` element (where the Glimmer HTML DSL adds elements by default) is not available when the JS file is loading, you need to put the code inside a `Document.ready? do; end` (but, it is recommended that you load the JS file after the parent element like `<body></body>` is in the page already for faster performance, which is guaranteed automatically by using `glimmer_component`, mentioned in details below):
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1241,7 +1322,7 @@ end
 
 Example to confirm setup is working:
 
-Glimmer GUI code in the frontend:
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1292,7 +1373,7 @@ HTML:
 ...
 ```
 
-Glimmer GUI code in the frontend:
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1349,7 +1430,7 @@ Next, read [Usage](#usage) instructions, and check out [Samples](#samples).
 
 ### Rails 6
 
-Please follow the following steps to setup.
+Please follow these steps to setup.
 
 Install a Rails 6 gem:
 
@@ -1372,7 +1453,7 @@ Disable the `webpacker` gem line in `Gemfile`:
 Add the following to `Gemfile`:
 
 ```ruby
-gem 'glimmer-dsl-web', '~> 0.2.3'
+gem 'glimmer-dsl-web', '~> 0.2.5'
 ```
 
 Run:
@@ -1389,7 +1470,7 @@ Follow [opal-rails](https://github.com/opal/opal-rails) instructions, basically
 bin/rails g opal:install
 ```
 
-To enable the `glimmer-dsl-web` library in the frontend, edit `config/initializers/assets.rb` and add the following at the bottom:
+To enable the `glimmer-dsl-web` gem in the frontend, edit `config/initializers/assets.rb` and add the following at the bottom:
 
 ```ruby
 Opal.use_gem 'glimmer-dsl-web'
@@ -1451,7 +1532,7 @@ Edit and replace `app/assets/opal/opal_application.rb` content with code below (
 ```ruby
 require 'glimmer-dsl-web' # brings opal and other dependencies automatically
 
-# Add more require-statements or Glimmer GUI DSL code
+# Add more require-statements or Glimmer HTML DSL code
 ```
 
 Example to confirm setup is working:
@@ -1465,7 +1546,7 @@ Initial HTML Markup:
 ...
 ```
 
-Glimmer GUI code in the frontend:
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1533,9 +1614,15 @@ Otherwise, if you still cannot setup successfully (even with the help of the sam
 
 Next, read [Usage](#usage) instructions, and check out [Samples](#samples).
 
+### Standalone (No Rails)
+
+Andreas Idogawa-Wildi ([@Largo](https://github.com/Largo)) created a project that demonstrates how to use Glimmer DSL for Web standalone (without Rails):
+
+[https://github.com/Largo/glimmer-dsl-web-standalone-demo](https://github.com/Largo/glimmer-dsl-web-standalone-demo)
+
 ## Usage
 
-Glimmer DSL for Web offers a GUI DSL ([Graphical User Interface](https://en.wikipedia.org/wiki/Graphical_user_interface) [Domain Specific Language](https://en.wikipedia.org/wiki/Domain-specific_language)) for building HTML Web User Interfaces declaratively in Ruby.
+Glimmer DSL for Web offers a HTML DSL ([Graphical User Interface](https://en.wikipedia.org/wiki/Graphical_user_interface) [Domain Specific Language](https://en.wikipedia.org/wiki/Domain-specific_language)) for building HTML Web User Interfaces declaratively in Ruby.
 
 1- **Keywords (HTML Elements)**
 
@@ -1551,7 +1638,7 @@ Also, if the element has a little bit of text content that can fit in one line,
 
 3- **Content Block (Properties + Listeners + Nested Elements + Text Content)**
 
-Element methods can accept a Ruby content block. It intentionally has a `{...}` style even as a multi-line block to indicate that the code is declarative GUI structure code (intentionally breaking away from Ruby imperative code conventions given this is a declarative GUI DSL ([Domain Specific Language](https://en.wikipedia.org/wiki/Domain-specific_language)), meaning a different language that has its own conventions, embedded within Ruby).
+Element methods can accept a Ruby content block. It intentionally has a `{...}` style even as a multi-line block to indicate that the code is declarative HTML DSL structure code (intentionally breaking away from Ruby imperative code conventions given this is a declarative HTML DSL ([Domain Specific Language](https://en.wikipedia.org/wiki/Domain-specific_language)), meaning a different language that has its own conventions, embedded within Ruby).
 
 You can nest HTML element properties under an element like:
 
@@ -1571,7 +1658,7 @@ button('Add') {
 }
 ```
 
-Given that listener code is imperative, it uses a `do; end` style for Ruby blocks to separate it from declarative GUI structure code and enable quicker readability of the code.
+Given that listener code is imperative, it uses a `do; end` style for Ruby blocks to separate it from declarative HTML DSL structure code and enable quicker readability of the code.
 
 You can nest other HTML elements under an HTML element the same way you do so in HTML, like:
 
@@ -1617,19 +1704,23 @@ Next, check out [Samples](#samples).
 
 ## Coming from Glimmer DSL for Opal
 
-This project is inspired by [Glimmer DSL for Opal](https://github.com/AndyObtiva/glimmer-dsl-opal) and is similar in enabling frontend GUI development with Ruby. [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) mainly differs from Glimmer DSL for Opal by adopting a DSL that follows web-like HTML syntax in Ruby to facilitate leveraging existing HTML/CSS/JS skills instead of adopting a desktop GUI DSL that is webified. As a result, applications written in Glimmer DSL for Opal are not compatible with Glimmer DSL for Web.
+This project is inspired by [Glimmer DSL for Opal](https://github.com/AndyObtiva/glimmer-dsl-opal) and is similar in enabling Web Frontend development with Ruby. [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) mainly differs from Glimmer DSL for Opal by adopting a DSL that follows web-like HTML syntax in Ruby to facilitate leveraging existing HTML/CSS/JS skills instead of adopting a desktop HTML DSL that is webified. As a result, applications written in Glimmer DSL for Opal are not compatible with Glimmer DSL for Web.
 
 ## Samples
 
-This external sample app contains all the samples mentioned below configured inside a Rails [Opal](https://opalrb.com/) app with all the prerequisites ready to go for convenience:
+This external Sample Selector app is built using Rails and Glimmer DSL for Web, including all the samples mentioned below configured inside a Rails [Opal](https://opalrb.com/) web app with all the prerequisites ready to go for convenience (there is a very minimal [Standalone [No Rails] static site sample app](https://github.com/Largo/glimmer-dsl-web-standalone-demo) too):
 
 https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app
 
+![Sample Selector](https://raw.githubusercontent.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app/master/sample-glimmer-dsl-web-rails7-app.png)
+
 ### Hello Samples
 
 #### Hello, World!
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_world.rb](/lib/glimmer-dsl-web/samples/hello/hello_world.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1681,7 +1772,9 @@ You can also mount the `div` elsewhere by passing the `parent: parent_css_select
 
 Event listeners can be setup on any element using the same event names used in HTML (e.g. `onclick`) while passing in a standard Ruby block to handle behavior. `$$` gives access to JS global scope from Ruby to invoke functions like `alert`.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_button.rb](/lib/glimmer-dsl-web/samples/hello/hello_button.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1713,9 +1806,11 @@ Screenshot:
 
 #### Hello, Form!
 
-[Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) gives access to all Web Browser built-in features like HTML form validations, input focus, events, and element functions from a very terse and productive Ruby GUI DSL.
+[Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) gives access to all Web Browser built-in features like HTML form validations, input focus, events, and element functions from a very terse and productive Ruby HTML DSL. Also, you can apply CSS styles by including directly in Ruby code as a string, using [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css), or managing CSS completely separately using something like [SCSS](https://sass-lang.com/). The CSS techniques could be combined as well, like by managing common reusable CSS styles separately in SCSS, but adding component specific CSS styles in Ruby when it is more convenient.
+
+[lib/glimmer-dsl-web/samples/hello/hello_form.rb](/lib/glimmer-dsl-web/samples/hello/hello_form.rb)
 
-Glimmer GUI code in the frontend:
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1867,11 +1962,64 @@ Screenshot:
 
 ![Hello, Form!](/images/glimmer-dsl-web-samples-hello-hello-form.gif)
 
+#### Hello, Form (MVP)!
+
+This is the MVP (Model-View-Presenter) edition of Hello, Form! leveraging Glimmer Web Components and the MVP Architectural Pattern.
+
+Main file:
+
+[lib/glimmer-dsl-web/samples/hello/hello_form_mvp.rb](/lib/glimmer-dsl-web/samples/hello/hello_form_mvp.rb)
+
+Other files:
+
+[lib/glimmer-dsl-web/samples/hello/hello_form_mvp](/lib/glimmer-dsl-web/samples/hello/hello_form_mvp)
+
+Glimmer HTML DSL Ruby code in the frontend:
+
+```ruby
+require 'glimmer-dsl-web'
+
+require_relative 'hello_form_mvp/presenters/hello_form_mvp_presenter'
+
+require_relative 'hello_form_mvp/views/contact_form'
+require_relative 'hello_form_mvp/views/contact_table'
+
+class HelloFormMvp
+  include Glimmer::Web::Component
+  
+  before_render do
+    @presenter = HelloFormMvpPresenter.new
+  end
+  
+  markup {
+    div {
+      h1('Contact Form')
+      
+      contact_form(presenter: @presenter)
+      
+      h1('Contacts Table')
+      
+      contact_table(presenter: @presenter)
+    }
+  }
+end
+
+Document.ready? do
+  HelloFormMvp.render
+end
+```
+
+Screenshot:
+
+![Hello, Form!](/images/glimmer-dsl-web-samples-hello-hello-form.gif)
+
 #### Hello, Observer!
 
 [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) provides the `observe(model, attribute) { ... }` keyword to employ the [Observer Design Pattern](https://en.wikipedia.org/wiki/Observer_pattern) as per [MVC](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) (Model View Controller), enabling Views to observe Models and update themselves in response to changes. If the `observe` keyword is used from inside a [Component](#hello-component), when the Component is removed or its top-level element is removed, the observer is automatically cleaned up. The need for such explicit observers is significantly diminished by the availablility of the more advanced Unidirectional [Data-Binding](#hello-data-binding) Support and Bidirectional [Data-Binding](#hello-data-binding) Support.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_observer.rb](/lib/glimmer-dsl-web/samples/hello/hello_observer.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -1894,48 +2042,85 @@ class HelloObserver
   after_render do
     @number_input.value = @number_holder.number
     @range_input.value = @number_holder.number
-    # Observe Model attribute @number_holder.number for changes and update View
-    # Observer is automatically cleaned up if remove method is called on rendered HelloObserver
-    # or its top-level element
+    
+    # Observe Model attribute @number_holder.number for changes and update View elements.
+    # Observer is automatically cleaned up when `remove` method is called on rendered
+    # HelloObserver web component or its top-level markup element (div)
     observe(@number_holder, :number) do
       number_string = @number_holder.number.to_s
       @number_input.value = number_string unless @number_input.value == number_string
       @range_input.value = number_string unless @range_input.value == number_string
     end
-    # Bidirectional Data-Binding does the same thing automatically
-    # Just disable the observe block above as well as the oninput listeners below
-    # and enable the `value <=> [@number_holder, :number]` lines to try the data-binding version
-    # Learn more about Bidirectional and Unidirectional Data-Binding in hello_data_binding.rb
+    # Bidirectional Data-Binding does the same thing automatically as per alternative sample: Hello, Observer (Data-Binding)!
   end
   
   markup {
     div {
       div {
         @number_input = input(type: 'number', min: 0, max: 100) {
-          # oninput listener updates Model attribute @number_holder.number
+          # oninput listener (observer) updates Model attribute @number_holder.number
           oninput do
             @number_holder.number = @number_input.value.to_i
           end
-          
-          # Bidirectional Data-Binding simplifies the implementation significantly
-          # by enabling the following line and disabling oninput listeners as well
-          # as the after_body observe block observer
-          # Learn more about Bidirectional and Unidirectional Data-Binding in hello_data_binding.rb
-#           value <=> [@number_holder, :number]
         }
       }
       div {
         @range_input = input(type: 'range', min: 0, max: 100) {
-          # oninput listener updates Model attribute @number_holder.number
+          # oninput listener (observer) updates Model attribute @number_holder.number
           oninput do
             @number_holder.number = @range_input.value.to_i
           end
-          
-          # Bidirectional Data-Binding simplifies the implementation significantly
-          # by enabling the following line and disabling oninput listeners as well
-          # as the after_body observe block observer
-          # Learn more about Bidirectional and Unidirectional Data-Binding in hello_data_binding.rb
-#           value <=> [@number_holder, :number]
+        }
+      }
+    }
+  }
+end
+
+Document.ready? do
+  HelloObserver.render
+end
+```
+
+Screenshot:
+
+![Hello, Observer!](/images/glimmer-dsl-web-samples-hello-hello-observer.gif)
+
+#### Hello, Observer (Data-Binding)!
+
+This is the data-binding edition of Hello, Observer!, which uses the `<=>` operator to perform bidirectional data-binding between a View property and a Model attribute, thus yield a lot less code that is declarative and is the most minimal code possible to express the requirements.
+
+[lib/glimmer-dsl-web/samples/hello/hello_observer_data_binding.rb](/lib/glimmer-dsl-web/samples/hello/hello_observer_data_binding.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
+
+```ruby
+require 'glimmer-dsl-web'
+
+class NumberHolder
+  attr_accessor :number
+  
+  def initialize
+    self.number = 50
+  end
+end
+
+class HelloObserver
+  include Glimmer::Web::Component
+  
+  before_render do
+    @number_holder = NumberHolder.new
+  end
+  
+  markup {
+    div {
+      div {
+        input(type: 'number', min: 0, max: 100) {
+          value <=> [@number_holder, :number]
+        }
+      }
+      div {
+        input(type: 'range', min: 0, max: 100) {
+          value <=> [@number_holder, :number]
         }
       }
     }
@@ -1955,7 +2140,9 @@ Screenshot:
 
 [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) intuitively supports both Unidirectional (One-Way) Data-Binding via the `<=` operator and Bidirectional (Two-Way) Data-Binding via the `<=>` operator, incredibly simplifying how to sync View properties with Model attributes with the simplest code to reason about.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_data_binding.rb](/lib/glimmer-dsl-web/samples/hello/hello_data_binding.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -2128,7 +2315,9 @@ If you need to regenerate HTML element content dynamically, you can use Content
 rebuild HTML elements based on changes in a Model attribute that provides the source data.
 In this example, we generate multiple address forms based on the number of addresses the user has.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_content_data_binding.rb](/lib/glimmer-dsl-web/samples/hello/hello_content_data_binding.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -2259,15 +2448,17 @@ Screenshot:
 
 You can define Glimmer web components (View components) to reuse visual concepts to your heart's content,
 by simply defining a class with `include Glimmer::Web::Component` and encasing the reusable markup inside
-a `markup {...}` block. Glimmer web components automatically extend the Glimmer GUI DSL with new keywords
+a `markup {...}` block. Glimmer web components automatically extend the Glimmer HTML DSL with new keywords
 that match the underscored versions of the component class names (e.g. an `OrderSummary` class yields
-the `order_summary` keyword for reusing that component within the Glimmer GUI DSL).
-You may insert a Glimmer component anywhere into a Rails View using `glimmer_component(component_path, *args)` 
+the `order_summary` keyword for reusing that component within the Glimmer HTML DSL).
+You may insert a Glimmer component anywhere into a Rails View using `glimmer_component(component_path, *args)`
 Rails helper (more about it in [Hello, glimmer_component Rails Helper!](#hello-glimmer_component-rails-helper)).
 Below, we define an `AddressForm` component that generates an `address_form` keyword, and then we
 reuse it twice inside an `AddressPage` component displaying a Shipping Address and a Billing Address.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_component.rb](/lib/glimmer-dsl-web/samples/hello/hello_component.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -2347,9 +2538,9 @@ end
 # AddressForm Glimmer Web Component (View component)
 #
 # Including Glimmer::Web::Component makes this class a View component and automatically
-# generates a new Glimmer GUI DSL keyword that matches the lowercase underscored version
+# generates a new Glimmer HTML DSL keyword that matches the lowercase underscored version
 # of the name of the class. AddressForm generates address_form keyword, which can be used
-# elsewhere in Glimmer GUI DSL code as done inside AddressPage below.
+# elsewhere in Glimmer HTML DSL code as done inside AddressPage below.
 class AddressForm
   include Glimmer::Web::Component
   
@@ -2482,6 +2673,8 @@ You may insert a Glimmer component anywhere into a Rails View using
 `glimmer_component(component_path, *args)` Rails helper. Add `include GlimmerHelper` to `ApplicationHelper`
 or another Rails helper, and use `<%= glimmer_component("path/to/component", *args) %>` in Views.
 
+[lib/glimmer-dsl-web/samples/hello/hello_glimmer_component_helper/address_form.rb](/lib/glimmer-dsl-web/samples/hello/hello_glimmer_component_helper/address_form.rb)
+
 Rails `ApplicationHelper` setup code:
 
 ```ruby
@@ -2516,7 +2709,7 @@ Rails View code:
 </div>
 ```
 
-Glimmer GUI code in the frontend (`app/assets/opal/address_form.rb`):
+Glimmer HTML DSL Ruby code in the frontend (`app/assets/opal/address_form.rb`):
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -2681,9 +2874,9 @@ Screenshot:
 
 #### Hello, Paragraph!
 
-To facilitate building formatted textual paragraphs in Ruby, thanks to [Glimmer](https://github.com/AndyObtiva/glimmer#dsl-engine), the most advanced DSL engine in Ruby, the Glimmer GUI DSL is advanced enough to intelligently behave differently under different situations, like when using HTML formatting elements: `<br>`, `<strong>`, `<em>`, `<br>`, `<i>`, `<sub>`, `<sup>`, `<del>`, `<ins>`, `<small>`, `<mark>`
+To facilitate building formatted textual paragraphs in Ruby, thanks to [Glimmer](https://github.com/AndyObtiva/glimmer#dsl-engine), the most advanced DSL engine in Ruby, the Glimmer HTML DSL is advanced enough to intelligently behave differently under different situations, like when using HTML formatting elements: `<br>`, `<strong>`, `<em>`, `<br>`, `<i>`, `<sub>`, `<sup>`, `<del>`, `<ins>`, `<small>`, `<mark>`
 
-Instead of returning Ruby objects that are nested as children within their parent, the Glimmer GUI DSL returns `String` objects directly that can be concatenated to or embedded within other `String` objects via interpolation.
+Instead of returning Ruby objects that are nested as children within their parent, the Glimmer HTML DSL returns `String` objects directly that can be concatenated to or embedded within other `String` objects via interpolation.
 
 This enables writing code like:
 
@@ -2711,9 +2904,11 @@ it returns a `String` to enable code like this:
 
 `p {"#{span('Yesterday, ', style: 'text-decoration: underline;')}Robert suggested adding a new #{em('feature', class: 'very-emphasized')} to our software product.#{br}}`
 
-In any case, below is a full example leveraging the Glimmer GUI DSL alternative approach when utilizing formatting elements underneath a paragraph.
+In any case, below is a full example leveraging the Glimmer HTML DSL alternative approach when utilizing formatting elements underneath a paragraph.
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_paragraph.rb](/lib/glimmer-dsl-web/samples/hello/hello_paragraph.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -2774,7 +2969,9 @@ Screenshot:
 
 #### Hello, Input (Date/Time)!
 
-Glimmer GUI code in the frontend:
+[lib/glimmer-dsl-web/samples/hello/hello_input_date_time.rb](/lib/glimmer-dsl-web/samples/hello/hello_input_date_time.rb)
+
+Glimmer HTML DSL Ruby code in the frontend:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -2879,7 +3076,9 @@ Screenshot:
 
 #### Button Counter
 
-Glimmer GUI code in the frontend demonstrating MVC + Glimmer Web Components (Views) + Data-Binding:
+[lib/glimmer-dsl-web/samples/regular/button_counter.rb](/lib/glimmer-dsl-web/samples/regular/button_counter.rb)
+
+Glimmer HTML DSL Ruby code in the frontend demonstrating MVC + Glimmer Web Components (Views) + Data-Binding:
 
 ```ruby
 require 'glimmer-dsl-web'
@@ -2958,7 +3157,7 @@ Screenshot:
 
 - The Ruby Way (including TIMTOWTDI: There Is More Than One Way To Do It)
 - The Rails Way Convention over Configuration via smart defaults and automation of low-level details
-- Requiring the least amount of syntax possible to build highly interactive web pages
+- Requiring the least amount of code possible to build highly interactive web pages
 - Declarative syntax that visually maps to the DOM (Document Object Model) hierarchy
 - Ability to mix declarative and imperative code conveniently in one language
 - Computers serve Software Engineers (not Software Engineers serve Computers)
@@ -2981,11 +3180,35 @@ Learn more by reading the [GPG](https://github.com/AndyObtiva/glimmer/blob/maste
 
 ## Help
 
+### FAQ
+
+F.A.Q. (Frequently Asked Questions):
+
+**How does Glimmer DSL for Web compare to Rails Hotwire (Turbo)?**
+
+Glimmer DSL for Web is a Frontend library, meaning it replaces the JavaScript layer in a web application (e.g. Rails app) with Ruby code. On the other hand, Rails Hotwire (Turbo) is mostly a Backend-driven technology that enables automatically replacing HTML DOM elements with HTML markup sent over the wire from a Rails Backend. So, the two technologies are mostly orthogonal, but can be used in the same Rails web application, albeit exclusively on separate web pages at the moment. In the future, we might explore supporting the ability to combine both technologies in the same pages, but until then, use on separate pages. Glimmer DSL for Web can handle any sort of Frontend interactions even without making HTTP calls to the Backend, so it can implement more use-cases than Hotwire. Using Glimmer DSL for Web with Rails API end-points is simpler than using Hotwire overall. That is because Glimmer Content Data-Binding is a simpler version of Turbo Frames that does not require worrying about setting and using element IDs (as that is handled automatically) and that operates at a more correct abstraction level for how we think about View component updates in relation to Model changes (we make updates at the Model layer, and they automatically get reflected in the View through data-binding). Also, Glimmer DSL for Web supports Glimmer Web Components, which enable better division of View code with higher readability than ERB. It is true that Hotwire is an improvement over using JavaScript frameworks like React when there is not much logic beyond updating elements with Server-Side rendered HTML. And, Glimmer DSL for Web is the next big advancement that brings a big improvement over the Hotwire approach.
+
+**How does Glimmer DSL for Web compare to Phlex or ViewComponent?**
+
+Glimmer DSL for Web is a Frontend library, meaning it replaces the JavaScript layer in a web application (e.g. Rails app) with Ruby code while providing its own View-layer component support using [`Glimmer::Web::Component`](#hello-component). On the other hand, Phlex and ViewComponent are Backend View-layer component libraries, so they serve 100% orthogonal needs, and can be used side by side with Glimmer DSL for Web if needed (e.g. Phlex components can consist of Backend HTML elements + Glimmer components that are rendered in the Frontend). That said, Phlex came out years after previous Glimmer libraries like Glimmer DSL for SWT, and Phlex's component system is very similar to Glimmer's component system in Glimmer DSL for SWT (perhaps inspired by it unconsciously or consciously). So, if you like Phlex in the Backend, you'll love Glimmer DSL for Web in the Frontend.
+
+**How does Glimmer DSL for Web compare to Angular, React, Vue, Svelte, or other JS frameworks?**
+
+Without delving into details, Glimmer DSL for Web is meant to be a Ruby-based drop-in replacement for Angular, React, Vue, Svelte, and other JS frameworks. Additionally, it enables writing both structure code and logic code in the same language (Ruby), greatly simplifying maintainability and improving productivity by eliminating multi-language dissonance and friction that drags down productivity as there is no need anymore to think in multiple languages unnecessarily, use XML based solutions (e.g. JSX), or use templating solutions (e.g. Mustache). Lastly, Glimmer DSL for Web supports familiar Software Engineering architectural patterns like Model-View-Controller and Model-View-Presenter, enabling Software Engineers to write the lightest and simplest code possible for building Web frontends in Ruby, with the best separation of concerns. Software Engineers can finally become happy Ruby developers by writing Ruby code in the Frontend too now in addition to the Backend.
+
+**How do I have a Glimmer Web Component re-render in a similar way to how React components re-render?**
+
+[Content Data-Binding](#hello-content-data-binding) supports re-rendering dynamic parts of a Glimmer Web Component (or the full component if all of it is dynamic). Glimmer DSL for Web simplifies Frontend Development significantly over React by not re-rendering everything if not needed (regardless of use of Virtual DOM) yet only re-rendering the parts of a component that do change dynamically. As a result, Software Engineers do not have to worry about the ripple effect of full re-renders or the possibility of breaking some parts of a page when making small changes to a single component in a hierarchy of page components. And, if only an element property changes, [Content Data-Binding](#hello-content-data-binding) is not even needed. It is much simpler to rely on simple [Property Data-Binding](#hello-data-binding) in that case. This makes reasoning about Glimmer DSL for Web Ruby code a lot simpler than reasoning about React component JavaScript code.
+
+**How do I reuse React components from Glimmer DSL for Web?**
+
+In the future, support for HTML Web Components will be added, and that will enable reuse of React components by using a library that converts them to HTML Web Components first like [react-to-web-component](https://github.com/bitovi/react-to-web-component) or [react-webcomponent](https://github.com/adobe/react-webcomponent).
+
 ### Issues
 
-You may submit [issues](https://github.com/AndyObtiva/glimmer-dsl-web /issues) on [GitHub](https://github.com/AndyObtiva/glimmer-dsl-web /issues).
+You may submit [issues](https://github.com/AndyObtiva/glimmer-dsl-web/issues) on [GitHub](https://github.com/AndyObtiva/glimmer-dsl-web/issues).
 
-[Click here to submit an issue.](https://github.com/AndyObtiva/glimmer-dsl-web /issues)
+[Click here to submit an issue.](https://github.com/AndyObtiva/glimmer-dsl-web/issues)
 
 ### Chat
 
@@ -3009,7 +3232,7 @@ These features have been suggested. You might see them in a future version of Gl
 
 * [Andy Maleh](https://github.com/AndyObtiva) (Founder)
 
-[Click here to view contributor commits.](https://github.com/AndyObtiva/glimmer-dsl-web /graphs/contributors)
+[Click here to view contributor commits.](https://github.com/AndyObtiva/glimmer-dsl-web/graphs/contributors)
 
 ## License