Add custom list component and examples for Jekyll with CSS styles

Author: giovanninocco

_includes/custom_list.html

@@ -0,0 +1,57 @@
+<!-- Custom List Component for Jekyll -->
+<!-- Usage: {% include custom_list.html items=list_items type="custom" %} -->
+
+{% assign list_type = include.type | default: "custom" %}
+{% assign items = include.items %}
+{% assign class_name = include.class | default: "" %}
+
+{% case list_type %}
+  {% when "custom" %}
+    <ul class="custom-list {{ class_name }}">
+      {% for item in items %}
+        <li>{{ item }}</li>
+      {% endfor %}
+    </ul>
+
+  {% when "checklist" %}
+    <ul class="checklist {{ class_name }}">
+      {% for item in items %}
+        <li>{{ item }}</li>
+      {% endfor %}
+    </ul>
+
+  {% when "feature" %}
+    <ol class="feature-list {{ class_name }}">
+      {% for item in items %}
+        <li>{{ item }}</li>
+      {% endfor %}
+    </ol>
+
+  {% when "icon" %}
+    <ul class="icon-list {{ class_name }}">
+      {% for item in items %}
+        <li data-icon="{{ item.icon | default: '•' }}">{{ item.text | default: item }}</li>
+      {% endfor %}
+    </ul>
+
+  {% when "highlight" %}
+    <ul class="highlight-list {{ class_name }}">
+      {% for item in items %}
+        <li>{{ item }}</li>
+      {% endfor %}
+    </ul>
+
+  {% when "compact" %}
+    <ul class="compact-list {{ class_name }}">
+      {% for item in items %}
+        <li>{{ item }}</li>
+      {% endfor %}
+    </ul>
+
+  {% else %}
+    <ul class="{{ class_name }}">
+      {% for item in items %}
+        <li>{{ item }}</li>
+      {% endfor %}
+    </ul>
+{% endcase %}

_includes/list_examples.md

@@ -0,0 +1,101 @@
+# Custom List Examples
+
+This document shows how to use the custom list styles in your Jekyll posts.
+
+## 1. Including the CSS
+
+Add this to your layout file or post front matter:
+
+```html
+<link rel="stylesheet" href="/assets/css/custom.css">
+```
+
+## 2. Using Custom Lists in Markdown
+
+### Custom Arrow List
+```html
+<ul class="custom-list">
+  <li>First item with custom arrow</li>
+  <li>Second item</li>
+  <li>Third item</li>
+</ul>
+```
+
+### Checklist Style
+```html
+<ul class="checklist">
+  <li>Completed task one</li>
+  <li>Completed task two</li>
+  <li>Completed task three</li>
+</ul>
+```
+
+### Numbered Feature List
+```html
+<ol class="feature-list">
+  <li>Feature one with circular number</li>
+  <li>Feature two with circular number</li>
+  <li>Feature three with circular number</li>
+</ol>
+```
+
+### Icon List
+```html
+<ul class="icon-list">
+  <li data-icon="🚀">Deployment feature</li>
+  <li data-icon="⚡">Performance optimization</li>
+  <li data-icon="🔒">Security enhancement</li>
+</ul>
+```
+
+### Highlighted List
+```html
+<ul class="highlight-list">
+  <li>Important point one</li>
+  <li>Important point two</li>
+  <li>Important point three</li>
+</ul>
+```
+
+### Compact List
+```html
+<ul class="compact-list">
+  <li>Compact item 1</li>
+  <li>Compact item 2</li>
+  <li>Compact item 3</li>
+</ul>
+```
+
+## 3. Using Jekyll Include
+
+In your post front matter, define your list items:
+
+```yaml
+---
+title: My Post
+features:
+  - "Feature one description"
+  - "Feature two description"
+  - "Feature three description"
+---
+```
+
+Then in your post content:
+
+```liquid
+{% include custom_list.html items=page.features type="feature" %}
+```
+
+Available types:
+- `custom` - Arrow style list
+- `checklist` - Checkmark style
+- `feature` - Numbered circles
+- `icon` - Custom icons
+- `highlight` - Highlighted boxes
+- `compact` - Minimal spacing
+
+## 4. Adding Custom Classes
+
+```liquid
+{% include custom_list.html items=page.items type="custom" class="mt-3 mb-3" %}
+```

_layouts/post.html

@@ -0,0 +1 @@
+<link rel="stylesheet" href="/assets/css/custom.css">

_posts/2025-11-21-solution-architect.md

@@ -50,16 +50,15 @@ In this role, the solution architect is responsible not only for coding the solu
 
 ### Microservices and API Design
 
-Microservices and API Design is the foundation of the software solution.
+Microservice architecture is one of the most popular architectural patterns for building scalable and maintainable software solutions. 
 
-- Microservices are a set of small, independent services that can be developed, deployed, and scaled independently.
-- API Design is the design of the API that will be used to communicate between the services.
+Microservices are a set of small, independent services that can be developed, deployed, and scaled independently. Along with API Design, they form the backbone of modern software architectures.
 
-### Data Strategy and Data Management
+On the other hand, API Design is the design of the API that will be used to communicate between the services.
 
-Data Strategy and Data Management is the foundation of the software solution.
+### Data Strategy and Data Management
 
-- Data Strategy is the strategy for the data management of the software solution.
+Data Strategy is the strategy for the data management of the software solution.
 
 ## Phase 1: Architectural Patterns & Design
 
@@ -69,12 +68,19 @@ _Goal_: **Prove you can design scalable, decoupled systems**.
 
 Be ready to explain when not to use microservices. The `distributed monolith` is a common failure mode interviewers look for.
 
-#### _Domain-Driven Design (DDD)_
+#### ***Domain-Driven Design (DDD)***
 
 - **Bounded Contexts**: How to define service boundaries (this is crucial to avoid tight coupling).
 
 - **Aggregates, Entities, Value Objects**: How to structure internal logic.
 
+Question: _How do you identify bounded contexts in a legacy monolith?_
+Ready Answer: Analyze business capabilities, identify natural seams in the codebase, and look for areas with distinct data models or workflows.
+
+Question: _What define the equality operator for Identity vs Value Object?_
+Ready Answer: Identity objects are compared by their unique identifier (ID), while Value Objects are compared based on their attributes or properties.
+
+
 #### **Design Patterns**
 
 - **CQRS (Command Query Responsibility Segregation)**: Separating reads from writes for performance.
@@ -117,6 +123,24 @@ _Goal_: **Show deep expertise in the primary technology stack**.
 
 - **Tools**: YARP (Yet Another Reverse Proxy) (Microsoft's current standard) or Ocelot.
 
+>
+> **Question**: _When would you use gRPC over REST?_
+>
+> **Ready Answer**: _Use gRPC for high-performance, low-latency communication between internal microservices, especially when you need strong typing and support for streaming. REST is better suited for public APIs where human readability and broad client support are priorities._
+
+
+> **Question**: _What is the difference between Scoped and Transient services in .NET Dependency Injection?_
+>
+> **Ready Answer**: _
+> - Scoped services are created once per client request (or scope), meaning they are shared within that request but not across requests.
+> 
+> - Transient services are created each time they are requested, so a new instance is provided every time they are injected._
+
+> **Question**: _What is a .NET Generics?_
+>
+> **Ready Answer**: _Generics in .NET allow you to define classes, interfaces, and methods with a placeholder for the data type. This enables code reusability and type safety, as you can create data structures and algorithms that work with any data type without sacrificing performance or safety._
+
+
 ## Phase 3: Data Strategy (SQL Server)
 
 _Goal_: **Address the hardest part of distributed systems—state**.
@@ -312,3 +336,10 @@ Contract tests are used to test the contracts of the different units of code. Th
 Component tests are used to test the components of the different units of code. They are typically slower to run and can be run independently. A well known framework is `Testcontainers`. It allows to test the components of the different units of code in a containerized environment.
 
 - [**Testcontainers**](https://testcontainers.com/): A container testing framework for .NET .
+
+
+
+<ul class="checklist">
+  <li>Your checklist item</li>
+  <li>Another item</li>
+</ul>