Adding premailer.

Author: gfraiteur

Gemfile

@@ -17,3 +17,5 @@ gem "jekyll-feed", "~> 0.17.0"
 # Avoid polling for changes on Windows
 gem 'wdm', '>= 0.1.0' if Gem.win_platform?
 gem "jekyll-toc", "~> 0.19.0"
+
+gem "premailer"

Gemfile.lock

@@ -22,6 +22,8 @@ GEM
     colorator (1.1.0)
     concurrent-ruby (1.3.5)
     connection_pool (2.5.0)
+    css_parser (1.21.1)
+      addressable
     csv (3.3.2)
     drb (2.2.1)
     em-websocket (0.5.3)
@@ -33,6 +35,7 @@ GEM
     google-protobuf (4.29.3-x64-mingw-ucrt)
       bigdecimal
       rake (>= 13)
+    htmlentities (4.3.4)
     http_parser.rb (0.8.0)
     i18n (1.14.7)
       concurrent-ruby (~> 1.0)
@@ -84,6 +87,10 @@ GEM
       racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
+    premailer (1.27.0)
+      addressable
+      css_parser (>= 1.19.0)
+      htmlentities (>= 4.0.0)
     public_suffix (6.0.1)
     racc (1.8.1)
     rake (13.2.1)
@@ -115,6 +122,7 @@ DEPENDENCIES
   jekyll-last-modified-at (~> 1.3)
   jekyll-redirect-from (~> 0.16.0)
   jekyll-toc (~> 0.19.0)
+  premailer
   wdm (>= 0.1.0)
 
 BUNDLED WITH

_layouts/instantly.html

@@ -5,6 +5,10 @@
   pre {
     white-space: pre-wrap;
   }
+  code {
+    font-family: 'Courier New', Courier, monospace;
+    line-height: 1em;
+  }
   blockquote.note {
     background-color: #addde6;
     border-radius: 5px;

_plugins/inline_css.rb

@@ -0,0 +1,39 @@
+require 'premailer'
+require 'nokogiri'
+
+Jekyll::Hooks.register [:pages, :documents], :post_render do |doc|
+  if doc.output_ext == '.html'
+    premailer = Premailer.new(doc.output, with_html_string: true)
+    html = premailer.to_inline_css
+    body_content = html[/<body\b[^>]*>(.*?)<\/body>/mi, 1] || html
+
+    fragment = Nokogiri::HTML::DocumentFragment.parse(body_content)
+    fragment.css('code').each do |code_node|
+      code_node.xpath('.//text()').each do |text_node|
+        content = text_node.content
+        # Replace only space characters with &middot; entity, preserve other whitespace
+        new_nodes = content.chars.map do |char|
+          if char == ' '
+            Nokogiri::XML::EntityReference.new(code_node.document, 'middot')
+          else
+            Nokogiri::XML::Text.new(char, code_node.document)
+          end
+        end
+        next if new_nodes.length == 1 && new_nodes.first.text?
+        new_nodes.reverse_each { |n| text_node.add_next_sibling(n) }
+        text_node.remove
+      end
+    end
+
+    output_html = fragment.to_html
+    # Insert <br> after every </div> or </p>
+    output_html.gsub!(%r{</(div|p)>}i, '</\1><br>')
+
+    # Wrap contiguous &middot; entities with a span for color
+    output_html.gsub!(/((?:&middot;)+)/) do |dots|
+      %Q{<span style="color:#1a1a1a">#{dots}</span>}
+    end
+
+    doc.output = output_html
+  end
+end

metalama-awareness-campaign/01_more_effective_way.md

@@ -1,5 +1,5 @@
 ---
-subject: 'Discover Metalama: A New Code Generation Framework for C#'
+subject: "Discover Metalama: A New Code Generation Framework for C#"
 layout: instantly
 ---
 
@@ -9,7 +9,7 @@ Hi {{firstName}},
 
 I'm **{{sendingAccountFirstName}}**, reaching out on behalf of our founder to gather feedback from experienced .NET engineers like you about [Metalama](https://metalama.net?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email1), an open source meta-programming framework for code generation, architecture validation, and aspect-oriented programming in C#.
 
-As someone who works with .NET, you know how repetitive patterns and boilerplate can slow down development, clutter codebases, and, hinder its maintenanbility -- although maintenance typically counts for 70% of the total cost of enterprise projects. Metalama is designed to help you eliminate that friction by letting you write special custom attributes, called **aspects**, that act as code templates. Here’s a quick look at a simple logging aspect:
+As someone who works with .NET, you know how repetitive patterns and boilerplate can slow down development, clutter codebases, and hinder their maintainability -- although maintenance typically counts for 70% of the total cost of enterprise projects. Metalama is designed to help you eliminate that friction by allowing you to write special custom attributes, called **aspects**, that act as code templates. Here's a quick look at a simple logging aspect:
 
 ```csharp
 using Metalama.Framework.Aspects;
@@ -59,11 +59,11 @@ With Metalama, you can preview and debug generated code, making it easy to see e
 
 **Why choose Metalama?**
 
-**Reduce code and bugs by 15%.** Let the machine handle repetitive tasks so engineers can focus on meaningful work.
+* **Reduce code and bugs by 15%.** Let the machine handle repetitive tasks so engineers can focus on meaningful work.
 
-**Maintain clean and readable code.** Simplify your codebase for better maintainability and collaboration.
+* **Maintain clean and readable code.** Simplify your codebase for better maintainability and collaboration.
 
-**Enforce architectural consistency.** Define validation rules in C# and receive instant feedback directly in your IDE.
+* **Enforce architectural consistency.** Define validation rules in C# and receive instant feedback directly in your IDE.
 
 If you have ever wished for a more effective way to handle logging, validation, or other cross-cutting concerns, Metalama is designed for you. There are [dozens of use cases](https://metalama.net/applications?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email1) in any non-trivial application. Explore our [documentation](https://doc.metalama.net/conceptual/getting-started?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email1) and [commented examples](https://doc.metalama.net/examples?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email1) to learn more.
 
@@ -72,9 +72,12 @@ We would love to hear your thoughts, questions, or feedback. Join the conversati
 Thank you for your time.
 
 Best regards,
+
 **{{sendingAccountFirstName}}**
+
 Community Manager
 
 *P.S. We will send you four more emails about Metalama and then stop. You can unsubscribe at any time.*
 
-{% endraw %}
+{% endraw %}
+  

metalama-awareness-campaign/02_caching.md

@@ -1,5 +1,5 @@
 ---
-subject: 'Here is How to Save Time on Caching'
+subject: "Here is How to Save Time on Caching"
 layout: instantly
 ---
 {% raw %}
@@ -77,7 +77,9 @@ We would love to hear your thoughts, questions, or feedback. Join the conversati
 Thank you for your time.
 
 All the best,
+
 **{{sendingAccountFirstName}}**
+
 Community Manager
 
 *P.S. We will send you three more emails about Metalama and then stop. You can unsubscribe at any time.*

metalama-awareness-campaign/03_ui.md

@@ -1,13 +1,13 @@
 ---
-subject: 'Building UIs with .NET Without Boilerplate'
+subject: "Building UIs with .NET Without Boilerplate"
 layout: instantly
 ---
 
 {% raw %}
 
 Hi {{firstName}},
 
-This is **{{sendingAccountFirstName}}** from Metalama. In my previous emails, I showed how Metalama can help you reduce boilerplate code for DevOps concerns like logging and caching. Today, I’d like to show you how Metalama can simplify common front-end challenges: think observability (`INotifyPropertyChanged`), undo/redo, change tracking, and WPF dependency properties and commands.
+This is **{{sendingAccountFirstName}}** from Metalama. In my previous emails, I showed how Metalama can help you reduce boilerplate code for DevOps concerns like logging and caching. Today, I'd like to show you how Metalama can simplify common front-end challenges: think observability (`INotifyPropertyChanged`), undo/redo, change tracking, and WPF dependency properties and commands.
 
 ## INotifyPropertyChanged
 
@@ -136,7 +136,9 @@ We’d love to hear your thoughts, questions, or feedback. Join the conversation
 Thank you for your time.
 
 All the best,  
+
 **{{sendingAccountFirstName}}**  
+
 Community Manager
 
 *P.S. We will send you two more emails about Metalama and then stop. You can unsubscribe at any time.*

metalama-awareness-campaign/04_patterns.md

@@ -1,17 +1,17 @@
 ---
-subject: 'Classic Design Patterns Without Boilerplate: Builder, Proxy, and More with Metalama'
+subject: "Classic Design Patterns Without Boilerplate: Builder, Proxy, and More with Metalama"
 layout: instantly
 ---
 
 {% raw %}
 
 Hi {{firstName}},
 
-This is **{{sendingAccountFirstName}}** from Metalama, the open-source meta-programming framework for .NET. In my previous emails, I showed how Metalama can help you eliminate boilerplate in DevOps and UI scenarios. Today, I’d like to show you how Metalama can simplify classic design patterns. You’ve already seen the Memento pattern. Let’s look at a few more: Builder, Decorator, and Proxy.
+This is **{{sendingAccountFirstName}}** from Metalama, the open-source meta-programming framework for .NET. In my previous emails, I showed how Metalama can help you eliminate boilerplate in DevOps and UI scenarios. Today, I'd like to show you how Metalama can simplify classic design patterns. You've already seen the Memento pattern. Let's look at a few more: Builder, Decorator, and Proxy.
 
 ## Builder Pattern
 
-The [Builder pattern](https://metalama.net/applications/builder?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4) is a creational design pattern that lets you construct complex objects step by step. It’s especially useful for creating immutable objects with many optional parameters or properties. The Abstract Builder variant adds even more flexibility.
+The [Builder pattern](https://metalama.net/applications/builder?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4) is a creational design pattern that lets you construct complex objects step by step. It's especially useful for creating immutable objects with many optional parameters or properties. The Abstract Builder variant adds even more flexibility.
 
 The main drawback of the Builder pattern is the sheer amount of repetitive code it requires. With Metalama, you can eliminate almost all of this boilerplate.
 
@@ -66,7 +66,7 @@ public partial class Song
 }
 ```
 
-That’s a lot of code you don’t have to write or maintain!
+That's a lot of code you don't have to write or maintain!
 
 For more details, check out these resources:
 
@@ -77,7 +77,7 @@ For more details, check out these resources:
 
 The [Proxy pattern](https://metalama.net/applications/proxy?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4) is a structural design pattern that lets you provide a substitute or placeholder for another object, typically to add new behavior. In C#, proxies are usually based on interfaces.
 
-You can implement the proxy’s added behavior in each member, or abstract it into an _Interceptor_.
+You can implement the proxy's added behavior in each member, or abstract it into an _Interceptor_.
 
 Implementing the Proxy pattern by hand means duplicating all interface members—a lot of boilerplate. With Metalama, you can generate the entire proxy automatically. Use `ProjectFabric` as a compile-time entry point to tell Metalama what to generate or validate:
 
@@ -106,9 +106,9 @@ You can find the full example on [GitHub](https://github.com/metalama/Metalama.S
 
 ## Deep Cloning
 
-Another common pattern is [deep cloning](https://doc.metalama.net/examples/clone/clone-1?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4). Unlike shallow cloning (which just calls `MemberwiseClone`), deep cloning requires recursively cloning child objects—a task that’s tedious and error-prone to do by hand.
+Another common pattern is [deep cloning](https://doc.metalama.net/examples/clone/clone-1?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4). Unlike shallow cloning (which just calls `MemberwiseClone`), deep cloning requires recursively cloning child objects—a task that's tedious and error-prone to do by hand.
 
-.NET doesn’t have a built-in concept of “child” objects, so a common solution is to mark child properties and fields with a `[Child]` attribute. Here’s how it looks:
+.NET doesn't have a built-in concept of "child" objects, so a common solution is to mark child properties and fields with a `[Child]` attribute. Here's how it looks:
 
 ```csharp
 [Cloneable]
@@ -150,7 +150,7 @@ See the [documentation](https://doc.metalama.net/examples/clone?mtm_campaign=awa
 
 ## Why Not Just Use Roslyn Source Generators?
 
-You might wonder: couldn’t all this be done with plain Roslyn source generators? For simple cases, yes. But Metalama is much more powerful and easier to use.
+You might wonder: couldn't all this be done with plain Roslyn source generators? For simple cases, yes. But Metalama is much more powerful and easier to use.
 
 Metalama is a high-level framework built on top of Roslyn generators. In fact, Metalama uses Roslyn generators for its design-time experience. But with Metalama, you get:
 
@@ -163,7 +163,7 @@ To learn more about code generation alternatives, read [this article](https://me
 
 ## Other Patterns
 
-We can’t cover every use case in a single email, but here are more ways Metalama can help:
+We can't cover every use case in a single email, but here are more ways Metalama can help:
 
 - **Design Patterns:** [Singleton](https://metalama.net/applications/classic-singleton?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Memento](https://metalama.net/applications/memento?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Factory](https://metalama.net/applications/factory?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Builder](https://metalama.net/applications/builder?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Decorator](https://metalama.net/applications/decorator?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Proxy](https://metalama.net/applications/proxy?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), ...
 - **UI Patterns:** [INotifyPropertyChanged](https://metalama.net/applications/inotifypropertychanged?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Change Tracking](https://metalama.net/applications/command?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Memoization](https://metalama.net/applications/memoization?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Undo/Redo](https://metalama.net/applications/undo-redo?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Command](https://metalama.net/applications/command?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Dependency Properties](https://metalama.net/applications/dependency-property?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4), [Enum View-Mode](https://doc.metalama.net/examples/enum-viewmodel?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email4) ...
@@ -177,12 +177,14 @@ For even more use cases and open-source aspect implementations, visit the [Metal
 
 Classic design patterns remain essential in modern .NET applications, but many still require a lot of boilerplate code. Metalama helps you generate this code automatically, so you can focus on what matters most: building great software.
 
-We’d love to hear your thoughts, questions, or feedback. Join the conversation on our [GitHub discussion space](https://github.com/orgs/metalama/discussions/categories/q-a), or simply reply to this email and I’ll connect you directly with our engineering team.
+We'd love to hear your thoughts, questions, or feedback. Join the conversation on our [GitHub discussion space](https://github.com/orgs/metalama/discussions/categories/q-a), or simply reply to this email and I'll connect you directly with our engineering team.
 
 Thank you for your time.
 
 All the best,  
+
 **{{sendingAccountFirstName}}**  
+
 Community Manager
 
 *P.S. We will send you two one email about Metalama and then stop. You can unsubscribe at any time.*

metalama-awareness-campaign/05_validating_architecture.md

@@ -1,13 +1,13 @@
 ---
-subject: 'Get your development team to adhere to architecture'
+subject: "Validating Architecture With Metalama: Compile-Time Safety for Your Codebase"
 layout: instantly
 ---
 
 {% raw %}
 
 Hi {{firstName}},
 
-This is **{{sendingAccountFirstName}}** from Metalama. This is my final email in this series. In previous messages, I introduced Metalama's first pillar: code generation, using aspect-oriented programming. Today, I’m excited to introduce Metalama’s second pillar: architecture verification.
+This is **{{sendingAccountFirstName}}** from Metalama. In my previous emails, I showed how Metalama can help you reduce boilerplate code for DevOps, UI, and design patterns. Today, let's talk about how Metalama can help you enforce architecture rules and naming conventions at compile time.
 
 Unlike code generation and aspect-oriented programming, which are open source, architecture verification is a proprietary feature available with a [Metalama Professional](https://metalama.net/premium?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email5) license.
 
@@ -117,7 +117,9 @@ You can learn more about architecture validation in our [online documentation](h
 Thank you for following along! We hope you enjoyed this series. Remember, the vast majority of Metalama’s features (85% of the codebase) are free and open source. Follow our [Getting Started](https://doc.metalama.net/conceptual/getting-started?mtm_campaign=awareness&mtm_source=instantly&mtm_kwd=email5) guide to start your journey against boilerplate code and architecture headaches—or join the conversation on our [GitHub discussion space](https://github.com/orgs/metalama/discussions/categories/q-a). You can also reply to this email and I’ll connect you directly with our engineering team.
 
 All the best,  
+
 **{{sendingAccountFirstName}}**  
+
 Community Manager
 
 *P.S. This was the last email in our series.*

metalama-email-course/010-required-contract.md

@@ -1,7 +1,9 @@
 ---
-subject: Verifying Required Fields and Parameters With Metalama
+subject: "Verifying Required Fields and Parameters With Metalama"
 ---
 
+# Verifying Required Fields and Parameters With Metalama
+
 Welcome to the Metalama e-mail course! In this first email, we will explore one of the most straightforward features of Metalama: code contracts.
 
 Developers frequently need to verify that certain fields, properties, parameters, or return values are not null. Even though the code necessary to perform these checks is not complex, it can lead to clutter in the codebase.