Init Documentations

.gitignore

@@ -1,3 +1,5 @@
 .idea
 _site/
 .sass-cache/
+
+.jekyll-metadata

README.md

@@ -1,3 +1,18 @@
 # Lviv Dev web site
 
 Visit our site https://lvivdevclub.github.io/
+
+
+## Run locally
+
+To construct and test your site locally, go into the directory and type
+
+```bash
+jekyll build
+```
+
+Type the following in order to “serve” the site.
+
+```bash
+jekyll serve
+```

_applications/RabbitMQ.md

@@ -0,0 +1,9 @@
+---
+layout: app
+title: RabbitMQ
+image: https://www.rabbitmq.com/img/RabbitMQ-logo.svg
+web: https://www.rabbitmq.com/
+tags: [queues, RabbitMQ]
+---
+
+RabbitMQ is an open-source message-broker software (sometimes called message-oriented middleware) that originally implemented the Advanced Message Queuing Protocol (AMQP) and has since been extended with a plug-in architecture to support Streaming Text Oriented Messaging Protocol (STOMP), Message Queuing Telemetry Transport (MQTT), and other protocols.

_config.yml

@@ -12,3 +12,12 @@ theme: jekyll-theme-cayman
 paginate: 5
 plugins:
   - jekyll-feed
+  - jekyll-paginate
+
+collections:
+  documentations:
+    output: true
+  applications:
+    output: true
+  subtopics:
+    output: true

_documentations/Design-of-Event-Driven-applications.md

@@ -0,0 +1,10 @@
+---
+layout: topic
+code: EDA
+title:  Design of Event Driven applications
+intro: "Event-driven architecture (EDA), is a software architecture pattern promoting the production, detection, consumption of, and reaction to events."
+tags: [design, event driven, eda]
+applications: [RabbitMQ]
+---
+
+An event can be defined as "a significant change in state". For example, when a consumer purchases a car, the car's state changes from "for sale" to "sold". A car dealer's system architecture may treat this state change as an event whose occurrence can be made known to other applications within the architecture. From a formal perspective, what is produced, published, propagated, detected or consumed is a (typically asynchronous) message called the event notification, and not the event itself, which is the state change that triggered the message emission. Events do not travel, they just occur. However, the term event is often used metonymically to denote the notification message itself, which may lead to some confusion. This is due to Event-Driven architectures often being designed atop message-driven architectures, where such communication pattern requires one of the inputs to be text-only, the message, to differentiate how each communication should be handled.

_layouts/app.html

@@ -0,0 +1,29 @@
+---
+layout: default
+---
+
+<article class="post" itemscope itemtype="http://schema.org/BlogPosting">
+
+    <header class="post-header">
+        <h1 class="post-title" itemprop="name headline"><a href="/documentations.html">Documentation</a> / {{ page.title | escape }}</h1>
+    </header>
+
+    {% if page.image != blank %}
+        <img src="{{ page.image }}"/><br/>
+    {% endif %}
+
+    {% if page.web != blank %}
+        Website: <a href="{{ page.web }}" target="_blank">{{ page.web }}</a><br/>
+    {% endif %}
+
+    <br/>
+    <div class="post-content" itemprop="articleBody">
+        {{ page.content }}
+    </div>
+
+    <div class="post-tags">Tags:
+        {% for tag in page.tags %}
+        <a href="/tags.html#{{ tag | slugify }}">{{ tag }}</a>,
+        {% endfor %}
+    </div>
+</article>

_layouts/default.html

@@ -12,14 +12,17 @@
 <section class="page-header">
     <h1 class="project-name">{{ site.title | default: site.github.repository_name }}</h1>
     <h2 class="project-tagline">{{ site.description | default: site.github.project_tagline }}</h2>
+    <a href="/" class="btn">Events</a>
+    <a href="/documentations.html" class="btn">Documentation</a>
+    <a href="/tags.html" class="btn">Tags</a>
     <a href="{{ site.githuburl }}" class="btn">View on GitHub</a>
 </section>
 
 <section class="main-content">
     {{ content }}
     <footer class="site-footer">
         <span class="site-footer-credits">
-            Subscribe <a href="{{ site.githuburl }}">on GitHub</a> or
+            Subscribe <a href="{{ page.name }}">on GitHub</a> or
             <a href="{{ "/feed.xml" | relative_url }}">via RSS</a>. Dev Clube learning video
             <a href="http://bit.ly/2VJrorK">playlist on YouTube</a>
             This page was generated by <a href="https://pages.github.com">GitHub Pages</a>.</span>

_layouts/post.html

@@ -2,11 +2,10 @@
 layout: default
 ---
 
-<a href="{{ site.url }}" >Home</a>
 <article class="post" itemscope itemtype="http://schema.org/BlogPosting">
 
     <header class="post-header">
-        <h1 class="post-title" itemprop="name headline">{{ page.title | escape }}</h1>
+        <h1 class="post-title" itemprop="name headline"><a href="/">Events</a> / {{ page.title | escape }}</h1>
         <p class="post-meta">
             <time datetime="{{ page.date | date_to_xmlschema }}" itemprop="datePublished">
                 {% assign date_format = site.minima.date_format | default: "%b %-d, %Y" %}
@@ -20,7 +19,7 @@ <h1 class="post-title" itemprop="name headline">{{ page.title | escape }}</h1>
 
     <div class="post-tags">Tags:
         {% for tag in page.tags %}
-        <a href="/tag.html#{{ tag | slugify }}"> {{ tag }} </a>
+        <a href="/tags.html#{{ tag | slugify }}">{{ tag }}</a>,
         {% endfor %}
     </div>
 </article>

_layouts/subtopic.html

@@ -0,0 +1,37 @@
+---
+layout: default
+---
+
+<article class="post" itemscope itemtype="http://schema.org/BlogPosting">
+
+    {% for d in site.documentations %}
+    {% if d.code == page.parent %}
+    {% assign documentation = d %}
+    {% endif %}
+    {% endfor %}
+
+    <header class="post-header">
+        <h1 class="post-title" itemprop="name headline">
+            <a href="/documentations.html">Documentation</a> /
+            <a href="{{ documentation.url }}">{{ documentation.title }}</a> /
+            {{ page.title | escape }}</h1>
+    </header>
+
+    <div class="post-content" itemprop="articleBody">
+        {{ page.content }}
+    </div>
+
+    <div class="post-tags">
+        <h2>Application</h2>
+        {% for application in page.applications %}
+            <a href="/applications/{{ application }}.html">{{ application }}</a>,
+        {% endfor %}
+    </div>
+
+    <div class="post-tags">
+        <h2>Tags</h2>
+        {% for tag in page.tags %}
+        <a href="/tags.html#{{ tag | slugify }}">{{ tag }}</a>,
+        {% endfor %}
+    </div>
+</article>

_layouts/topic.html

@@ -0,0 +1,42 @@
+---
+layout: default
+---
+
+<article class="post" itemscope itemtype="http://schema.org/BlogPosting">
+
+    <header class="post-header">
+        <h1 class="post-title" itemprop="name headline"><a href="/documentations.html">Documentation</a> / {{ page.title
+            | escape }}</h1>
+    </header>
+
+    <div class="post-intro">
+        {{ page.intro }}
+    </div>
+
+    <div class="post-subtopic">
+        <h2>Sub topics</h2>
+        <ul>
+        {% for subtopic in site.subtopics %}
+            <li><a href="{{ subtopic.url }}">{{ subtopic.title }}</a> {{ subtopic.intro }}
+        {% endfor %}
+        </ul>
+    </div>
+
+    <div class="post-content" itemprop="articleBody">
+        {{ page.content }}
+    </div>
+
+    <div class="post-tags">
+        <h2>Application</h2>
+        {% for application in page.applications %}
+            <a href="/applications/{{ application }}.html">{{ application }}</a>,
+        {% endfor %}
+    </div>
+
+    <div class="post-tags">
+        <h2>Tags</h2>
+        {% for tag in page.tags %}
+        <a href="/tags.html#{{ tag | slugify }}">{{ tag }}</a>,
+        {% endfor %}
+    </div>
+</article>

_subtopics/EDA-Broker-Topology.md

@@ -0,0 +1,10 @@
+---
+layout: subtopic
+parent: EDA
+title:  Broker Topology
+intro: "The broker topology differs from the mediator topology in that there is no central event mediator."
+tags: [design, event driven, pattern, broker, eda]
+applications: [RabbitMQ]
+---
+
+Mediator Topology...

_subtopics/EDA-Mediator-Topology.md

@@ -0,0 +1,11 @@
+---
+layout: subtopic
+parent: EDA
+title:  Mediator Topology
+intro: "The mediator topology is useful for events that have multiple steps and require some level of orchestration 
+to process the event."
+tags: [design, event driven, pattern, mediator, eda]
+applications: [RabbitMQ]
+---
+
+Mediator Topology...

assets/css/style.scss

@@ -3,6 +3,12 @@
 
 @import "{{ site.theme }}";
 
+.main-content{
+  @media screen {
+    max-width: 100%;
+  }
+}
+
 .page-header {
 
   @include large {

documentations.html

@@ -0,0 +1,18 @@
+---
+layout: default
+title: Documentations
+---
+<h1>Documentations</h1>
+
+<h2>Advanced level</h2>
+
+{% for documentation in site.documentations %}
+<h3>{{ documentation.title }}</h3>
+<p>{{ documentation.intro }} <a href="{{ documentation.url }}">Read more...</a></p>
+{% endfor %}
+
+
+<h1>Application</h1>
+{% for application in site.applications %}
+<a href="{{ application.url }}">{{ application.title }}</a>,
+{% endfor %}

index.html

@@ -26,7 +26,7 @@ <h1 class="post-title" itemprop="name headline">
         <div class="post-tags">
             <small>Tags:
                 {% for tag in page.tags %}
-                <a href="/tag.html#{{ tag | slugify }}"> {{ tag }} </a>
+                <a href="/tags.html#{{ tag | slugify }}"> {{ tag }} </a>
                 {% endfor %}
             </small>
         </div>

tags.html

@@ -0,0 +1,53 @@
+---
+layout: default
+title: Tags
+---
+<div class="tags-expo">
+    {% assign postsTags = site.posts | map: 'tags' %}
+    {% assign applicationsTags = site.applications | map: 'tags' %}
+    {% assign documentationsTags = site.documentations | map: 'tags' %}
+    {% assign subtopicsTags = site.subtopics | map: 'tags' %}
+
+    {% assign sortedTags = (postsTags | concat: applicationsTags | concat: documentationsTags | concat: subtopicsTags |
+    uniq | sort:0) %}
+    <div class="tags-expo-list">
+        <h1>Tags</h1>
+        {% for tag in sortedTags %}
+        <a href="#{{ tag | slugify }}" class="post-tag">{{ tag }}</a>,
+        {% endfor %}
+    </div>
+
+    <hr/>
+
+    <div class="tags-expo-section">
+
+        {% for tag in sortedTags %}
+        <h2 id="{{ tag | slugify }}">{{ tag }}</h2>
+        <ul>
+            {% for post in site.documentations %}
+            {% if post.tags contains tag %}
+            <li><a href="{{ post.url }}">{{ post.title }}</a></li>
+            {% endif %}
+            {% endfor %}
+
+            {% for post in site.subtopics %}
+            {% if post.tags contains tag %}
+            <li><a href="{{ post.url }}">{{ post.title }}</a></li>
+            {% endif %}
+            {% endfor %}
+
+            {% for post in site.posts %}
+            {% if post.tags contains tag %}
+            <li><a href="{{ post.url }}">{{ post.title }}</a></li>
+            {% endif %}
+            {% endfor %}
+
+            {% for post in site.applications %}
+            {% if post.tags contains tag %}
+            <li><a href="{{ post.url }}">{{ post.title }}</a></li>
+            {% endif %}
+            {% endfor %}
+        </ul>
+        {% endfor %}
+    </div>
+</div>