From 425e8cf859b5445318e40259b29d3f5c34fbfb33 Mon Sep 17 00:00:00 2001
From: Vitalii Oliinyk <ilovepinkpony1@gmail.com>
Date: Thu, 16 Jan 2025 23:29:49 +0200
Subject: [PATCH 01/62] [PR-23724]: added new theme, updated files

---
 requirements.txt                              |   2 +
 source/_static/talkable.css                   | 697 +-----------------
 source/_templates/search.html                 |  65 --
 .../converting_into_localization.rst          |   4 -
 source/advanced_features/coupons.rst          |   8 +-
 .../customer_service_portal/overview.rst      |   4 -
 .../customer_service_portal/terminology.rst   |   4 -
 .../customer_service_portal/use_case_1.rst    |   4 -
 .../customer_service_portal/use_case_2.rst    |   4 -
 .../customer_service_portal/use_case_3.rst    |   4 -
 .../customer_service_portal/use_case_4.rst    |   4 -
 .../customer_service_portal/use_case_5.rst    |   4 -
 .../customer_service_portal/use_case_6.rst    |   4 -
 source/advanced_features/file_encryption.rst  |   4 -
 .../advanced_features/passing_custom_data.rst |   4 -
 .../personal_coupon_sharing.rst               |   9 +-
 source/advanced_features/reg_ex.rst           |   4 -
 source/advanced_features/segments.rst         |   5 -
 source/advanced_features/single_sign_on.rst   |   4 -
 .../subscribing_to_events.rst                 |   4 -
 source/advanced_features/url_parameters.rst   |   4 -
 source/advanced_features/utm_tags.rst         |   4 -
 source/android_sdk/advanced.rst               |   4 -
 source/android_sdk/api.rst                    |   4 -
 source/android_sdk/deep_linking.rst           |   4 -
 source/android_sdk/getting_started.rst        |   4 -
 .../android_sdk/integration/post_purchase.rst |   4 -
 source/android_sdk/integration/standalone.rst |   4 -
 source/android_sdk/testing.rst                |   4 -
 source/android_sdk/upgrade.rst                |   4 -
 source/campaigns.rst                          |  24 +-
 source/conf.py                                |  24 +-
 source/integration/custom/overview.rst        |  26 +-
 source/ios_sdk/advanced.rst                   |   4 -
 source/ios_sdk/api_integration.rst            |   4 -
 source/ios_sdk/example.rst                    |   4 -
 source/ios_sdk/integration/post_purchase.rst  |   4 -
 source/ios_sdk/integration/standalone.rst     |   4 -
 .../campaign_placements_description.rst       |  65 +-
 source/web_hooks/check_unsubscribe.rst        |   4 -
 source/web_hooks/claim_signup.rst             |   4 -
 source/web_hooks/create_coupon.rst            |   4 -
 source/web_hooks/event.rst                    |   5 -
 source/web_hooks/offer_signup.rst             |   4 -
 source/web_hooks/post_share.rst               |   4 -
 source/web_hooks/referral.rst                 |   4 -
 source/web_hooks/reward.rst                   |   4 -
 source/web_hooks/unsubscribe.rst              |   4 -
 48 files changed, 100 insertions(+), 978 deletions(-)
 delete mode 100644 source/_templates/search.html

diff --git a/requirements.txt b/requirements.txt
index afee09fd6..ffd6786dc 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,2 +1,4 @@
+furo
+sphinx-copybutton
 Sphinx==8.1.3
 sphinx-sitemap==2.6.0
diff --git a/source/_static/talkable.css b/source/_static/talkable.css
index 47296eb48..25b0c2481 100644
--- a/source/_static/talkable.css
+++ b/source/_static/talkable.css
@@ -1,695 +1,34 @@
-@import url("basic.css");
-@import url(https://fonts.googleapis.com/css?family=Roboto:400,500,700,300,400italic);
+/* @import url("basic.css"); */
+/* @import url(https://fonts.googleapis.com/css?family=Roboto:400,500,700,300,400italic); */
 
-/* -- page layout ----------------------------------------------------------- */
-html {
-    background-color: #EDF0F3;
-    min-height: 100%;
-}
-
-body {
-    font: 300 16px/1.45 "Roboto", sans-serif;
-    color: #3e4f6c;
-    margin: 0;
-    padding: 0;
-}
-
-div.admonition,
-div.topic,
-blockquote,
-pre, div[class*="highlight-"] {
-  clear: none;
-}
-
-div.sidebar::after,
-div.topic::after,
-div.admonition::after,
-blockquote::after,
-div.section::after {
-  clear: none;
-}
-
-.clearfix {
-    *zoom: 1;
-}
-
-.clearfix:before,
-.clearfix:after {
-    display: table;
-    content: "";
-}
-
-.clearfix:after {
-    clear: both;
-}
-
-.content-container {
-    margin: auto;
-    max-width: 960px;
-    box-sizing: border-box;
-}
-
-a, .a, a:visited {
-    color: #D36835;
-    cursor: pointer;
-    text-decoration: none;
-}
-
-.current > a,
-a.current,
-a:hover {
-    color: #3e4f6c;
-}
-
-abbr {
-    letter-spacing: 0.08em;
-}
-
-.inline {
-    display: inline-block;
-}
-
-.button {
-    background: #f0632f;
-    border: 1px solid #c04f26;
-    border-radius: 4px;
-    color: #fff;
-    cursor: pointer;
-    display: inline-block;
-    font: 300 14px/normal "Roboto", sans-serif;
-    padding: 8px 15px 9px;
-}
-
-.button:hover,
-.button:focus {
-    background-color: #db5523;
-}
-
-.button:active {
-    background-color: #cb4616;
-}
-
-.textfield {
-    border: 2px solid #c5cbd4;
-    border-radius: 4px;
-    font: 300 14px/normal "Roboto", sans-serif;
-    height: 36px;
-    padding: 9px 10px;
-    width: 100%;
-    -moz-box-sizing: border-box;
-    -webkit-box-sizing: border-box;
-    box-sizing: border-box;
-    transition: border-color .25s;
-}
-
-.textfield::-moz-placeholder {
-    color: #ddd;
-}
-
-.textfield::-webkit-input-placeholder {
-    color: #ddd;
-}
-
-.textfield:focus {
-    border-color: #90a1b5;
-}
-
-.bodywrapper {
-    background-color: #fff;
-    border-radius: 6px;
-    margin-left: 243px;
-    margin-bottom: 60px;
-}
-
-.bodywrapper ol,
-.bodywrapper ul {
-    margin-left: 0;
-    padding-left: 23px;
-}
-
-.bodywrapper blockquote {
-    margin: 0;
-}
-
-.body {
-    line-height: 1.5;
-    padding: 22px 30px 30px;
-}
-
-.body img {
-    border: 1px solid #ddd;
-    border-radius: 4px;
-    box-shadow: 0 5px 15px rgba(0, 0, 0, .2);
-}
-
-.body img.is-minimal {
-    border: none;
-    border-radius: 0;
-    box-shadow: none;
-    margin: 20px 0;
-}
-
-.nav {
-    float: left;
-    line-height: 1.35;
-    padding: 27px 20px 40px 0;
-    width: 243px;
-}
-
-.nav ul {
-    list-style-type: none;
-    margin: 0;
-    padding: 0;
-}
-
-.nav li {
-    margin-bottom: 5px;
-}
-
-.nav ul ul {
-    font-size: 14px;
-    margin: 5px 0 5px 20px;
-}
-
-.nav ul ul.simple {
-    margin-bottom: 0;
-    margin-top: 0;
-}
-
-/* SEARCH FORM */
-.search-form {
-    display: inline-block;
-    vertical-align: middle;
-    width: 50%;
-}
-
-.search-form-field {
-    margin-right: 1%;
-    width: 75%;
-}
-
-/* HEADER */
-.header {
-    margin: 0 auto;
-    max-width: 960px;
-    padding: 20px 0;
-}
-
-.header .button {
-    width: 23%;
-}
-
-.header-disclaimer {
-    float: right;
-    padding-top: 9px;
-}
-
-.header-logo {
-    background: url("img/logo.svg") no-repeat;
-    color: transparent;
-    display: inline-block;
-    font-size: 0;
-    height: 32px;
-    margin-right: 50px;
-    text-indent: -99999em;
-    vertical-align: middle;
-    width: 189px;
-    background-size: 100%;
+.sidebar-brand-text {
+  display: none;
 }
 
-blockquote.epigraph {
-    display: inline-block;
-    zoom: 1;
-    margin: 0 -30px 0 -30px;
-    padding: 30px 70px;
-    background: #FFE9CE;
+.sidebar-logo {
+  margin: 0;
 }
 
 table.docutils {
-    width: 100%;
+  box-shadow: none;
+  width: 100%;
 }
 
-table.docutils th,
 table.docutils td {
-    border-bottom: 2px solid #e0e0e0;
-    padding: 8px 8px 8px 0px;
-    vertical-align: top;
-}
-
-.ptable table {
-    width: 100%;
-    margin: 1em 0 1em 0;
-}
-
-.ptable table tr td:first-child,
-.ptable table tr th:first-child {
-    width: 20%;
-}
-
-/* -- body styles ----------------------------------------------------------- */
-p {
-    margin: 0.8em 0 0.5em 0;
-}
-
-h1, h2, h3, h4, h5, h6 {
-    font-weight: 200;
-}
-
-h1 {
-    font-size: 250%;
-    margin: 0;
-    padding: 0 0 0.3em 0;
-    line-height: 1.2em;
-}
-
-h2 {
-    font-size: 200%;
-    margin: 1.3em 0 0.2em 0;
-    padding: 0 0 10px 0;
-}
-
-h3 {
-    font-size: 160%;
-    margin: 1em 0 -0.3em 0;
-    padding-bottom: 5px;
-}
-
-h4 {
-    font-size: 140%;
-    margin: 1em 0 -0.3em 0;
-    padding-bottom: 5px;
-}
-
-div.body h1 a,
-div.body h2 a,
-div.body h3 a,
-div.body h4 a,
-div.body h5 a,
-div.body h6 a {
-    color: #657B83 !important;
-    font-size: 16px;
-    margin-left: 10px;
-    vertical-align: middle;
-}
-
-h1 a.anchor,
-h2 a.anchor,
-h3 a.anchor,
-h4 a.anchor,
-h5 a.anchor,
-h6 a.anchor {
-    display: none;
-    margin: 0 0 0 0.3em;
-    padding: 0 0.2em 0 0.2em;
-    color: #aaa !important;
-}
-
-h1:hover a.anchor,
-h2:hover a.anchor,
-h3:hover a.anchor,
-h4:hover a.anchor,
-h5:hover a.anchor,
-h6:hover a.anchor {
-    display: inline;
-}
-
-h1 a.anchor:hover,
-h2 a.anchor:hover,
-h3 a.anchor:hover,
-h4 a.anchor:hover,
-h5 a.anchor:hover,
-h6 a.anchor:hover {
-    color: #777;
-    background-color: #eee;
-}
-
-cite, code, tt {
-    font-family: 'Source Code Pro', monospace;
-    font-size: 0.9em;
-    letter-spacing: 0.01em;
-    background-color: #FFF9DA;
-    font-style: normal;
-    word-break: break-all;
-}
-
-hr {
-    border: 1px solid #eee;
-    margin: 2em 0;
-}
-
-.highlight {
-    border-left: 4px solid #DADADA;
-    background: none !important;
-}
-
-pre {
-    font-family: 'Source Code Pro', monospace;
-    font-style: normal;
-    font-size: 14px;
-    line-height: 1.4;
-    padding: 15px 20px;
-    white-space: pre-wrap;       /* css-3 */
-    white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
-    white-space: -pre-wrap;      /* Opera 4-6 */
-    white-space: -o-pre-wrap;    /* Opera 7 */
-    word-wrap: break-word;       /* Internet Explorer 5.5+ */
-}
-
-pre a {
-    color: inherit;
-    text-decoration: underline;
-}
-
-td.linenos pre {
-    padding: 0.5em 0;
-}
-
-div.quotebar {
-    background-color: #f8f8f8;
-    max-width: 250px;
-    float: right;
-    padding: 2px 7px;
-    border: 1px solid #ccc;
-}
-
-div.topic {
-    background-color: #f8f8f8;
-}
-
-table {
-    border-collapse: collapse;
-    margin: 0;
-}
-
-table td, table th {
-    padding: 0.2em 0.5em 0.2em 0.5em;
-}
-
-div.admonition {
-    border-left: 4px solid #D36835;
-    margin: 2em 0;
-    padding: 15px 20px;
-}
-
-div.admonition p {
-    margin: 0.5em 0;
-}
-
-div.admonition pre {
-    margin: 0.4em 0;
-}
-
-div.admonition p.admonition-title {
-    color: #D36835;
-    margin: 0 0 5px;
-    font-weight: bold;
-}
-
-div.warning,
-div.important {
-    border-left-color: red;
-}
-
-div.warning p.admonition-title,
-div.important p.admonition-title {
-    color: red;
-}
-
-div.hint,
-div.tip {
-    border-left-color: #3e4f6c;
-}
-
-div.hint p.admonition-title,
-div.tip p.admonition-title {
-    color: #3e4f6c;
-}
-
-div.caution,
-div.attention,
-div.danger,
-div.error {
-    border-left-color: #dc322f;
-}
-
-div.caution p.admonition-title,
-div.attention p.admonition-title,
-div.danger p.admonition-title,
-div.error p.admonition-title {
-    color: #dc322f;
-}
-
-div.admonition ul, div.admonition ol {
-    margin: 0.1em 0.5em 0.5em 3em;
-    padding: 0;
-}
-
-div.versioninfo {
-    margin: 1em 0 0 0;
-    border: 1px solid #eee;
-    background-color: #ddeaf0;
-    padding: 8px;
-    line-height: 1.3em;
-    font-size: 0.9em;
-}
-
-div.viewcode-block:target {
-    background-color: #f4debf;
-    border-top: 1px solid #eee;
-    border-bottom: 1px solid #eee;
-}
-
-ol > li {
-  margin-top: 15px;
-}
-
-ol > li:first-child {
-  margin-top: 0;
-}
-
-.reference.internal em {
-    font-style: normal;
-}
-
-div.hidden {
-    display: none;
-}
-
-.underline {
-  text-decoration: underline;
-}
-
-.mtn, .mvn, .man {
-  margin-top: 0px;
-}
-
-.mrn, .mhn, .man {
-  margin-right: 0px;
-}
-
-.mbn, .mvn, .man {
-  margin-bottom: 0px;
-}
-
-.mln, .mhn, .man {
-  margin-left: 0px;
-}
-
-.mtx, .mvx, .max {
-  margin-top: 3px;
-}
-
-.mrx, .mhx, .max {
-  margin-right: 3px;
-}
-
-.mbx, .mvx, .max {
-  margin-bottom: 3px;
-}
-
-.mlx, .mhx, .max {
-  margin-left: 3px;
-}
-
-.mts, .mvs, .mas {
-  margin-top: 5px;
-}
-
-.mrs, .mhs, .mas {
-  margin-right: 5px;
-}
-
-.mbs, .mvs, .mas {
-  margin-bottom: 5px;
-}
-
-.mls, .mhs, .mas {
-  margin-left: 5px;
-}
-
-.mtm, .mvm, .mam {
-  margin-top: 10px;
-}
-
-.mrm, .mhm, .mam {
-  margin-right: 10px;
-}
-
-.mbm, .mvm, .mam {
-  margin-bottom: 10px;
-}
-
-.mlm, .mhm, .mam {
-  margin-left: 10px;
-}
-
-.mtl, .mvl, .mal {
-  margin-top: 20px;
-}
-
-.mrl, .mhl, .mal {
-  margin-right: 20px;
-}
-
-.mbl, .mvl, .mal {
-  margin-bottom: 20px;
-}
-
-.mll, .mhl, .mal {
-  margin-left: 20px;
-}
-
-.mtxl, .mvxl, .maxl {
-  margin-top: 30px;
-}
-
-.mrxl, .mhxl, .maxl {
-  margin-right: 30px;
-}
-
-.mbxl, .mvxl, .maxl {
-  margin-bottom: 30px;
-}
-
-.mlxl, .mhxl, .maxl {
-  margin-left: 30px;
-}
-
-.mtxxl, .mvxxl, .maxxl {
-  margin-top: 40px;
-}
-
-.mrxxl, .mhxxl, .maxxl {
-  margin-right: 40px;
-}
-
-.mbxxl, .mvxxl, .maxxl {
-  margin-bottom: 40px;
-}
-
-.mlxxl, .mhxxl, .maxxl {
-  margin-left: 40px;
-}
-
-.page-break-after,
-.header-printable {
-  display: none;
+  vertical-align: top;
+  padding: 1px 16px 24px 5px;
 }
 
-/* FIREFOX SPECIFIC */
-@-moz-document url-prefix() {
-    .button {
-        padding-bottom: 8px;
-        padding-top: 6px;
-    }
+body[data-theme="light"] .highlight,
+body[data-theme="light"] .highlight button.copybtn,
+body[data-theme="light"] .highlight button.copybtn.success:after {
+  background: #f2f2f2 !important;
 }
 
-/* MQ */
-@media only screen and (max-width: 980px) {
-    .header {
-        padding-left: 20px;
-        padding-right: 20px;
-    }
-
-    .header-disclaimer {
-        font-size: 80%;
-    }
-
-    .content-container {
-        padding: 0 20px;
-    }
+.highlight button.copybtn:hover {
+  stroke: var(--color-link);
 }
 
-@media only print {
-  html {
-    background-color: transparent;
-  }
-
-  .nav,
-  .search-form {
-    display: none !important;
-  }
-
-  .header {
-    padding-top: 0;
-    margin-bottom: 40px;
-  }
-
-  .header-logo {
-    background-image: none;
-  }
-
-  .header-logo:after {
-    content: url(img/logo.svg);
-  }
-
-  .section li {
-    position: relative;
-    page-break-inside: avoid;
-  }
-
-  .admonition {
-    position: relative;
-    page-break-inside: avoid;
-    page-break-before: avoid;
-  }
-
-  .section,
-  .section li {
-    widows: 2;
-    orphans: 2;
-  }
-
-  .body h1,
-  .body h2,
-  .body h3,
-  .body h4,
-  .body h5,
-  .body h6 {
-    display: block;
-    position: relative;
-    page-break-after: avoid;
-  }
-
-  .body h1 {
-    text-align: center;
-  }
-
-  .body img {
-    display: block;
-    position: relative;
-    page-break-before: avoid;
-    max-height: 700px;
-    margin: 20px 0;
-  }
-
-  .body p {
-    font-size: 20px;
-  }
-
-  .page-break-after {
-    display: block;
-    position: relative;
-    page-break-after: always;
-  }
+.headerlink {
+  visibility: hidden !important;
 }
diff --git a/source/_templates/search.html b/source/_templates/search.html
deleted file mode 100644
index 431014260..000000000
--- a/source/_templates/search.html
+++ /dev/null
@@ -1,65 +0,0 @@
-{#
-  basic/search.html
-  ~~~~~~~~~~~~~~~~~
-
-  Template for the search page.
-
-  :copyright: Copyright 2007-2023 by the Sphinx team, see AUTHORS.
-  :license: BSD, see LICENSE for details.
-#}
-{%- extends "layout.html" %}
-{% set title = _('Search') %}
-{%- block scripts %}
-  {{ super() }}
-  <script src="{{ pathto('_static/searchtools.js', 1) }}"></script>
-  <script src="{{ pathto('_static/language_data.js', 1) }}"></script>
-{%- endblock %}
-{% block extrahead %}
-  <script src="{{ pathto('searchindex.js', 1) }}" defer></script>
-  {{ super() }}
-{% endblock %}
-{% block body %}
-  <h1 id="search-documentation">{{ _('Search') }}</h1>
-  {% block scriptwarning %}
-    <noscript>
-      <div class="admonition warning">
-        <p>
-          {% trans %}Please activate JavaScript to enable the search
-          functionality.{% endtrans %}
-        </p>
-      </div>
-    </noscript>
-  {% endblock %}
-  {% block searchtext %}
-    <p>
-      {% trans %}Searching for multiple words only shows matches that contain
-      all words.{% endtrans %}
-    </p>
-  {% endblock %}
-  {% block searchbox %}
-    <form action="" method="get">
-      <input type="text" name="q" aria-labelledby="search-documentation" value="" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
-      <input type="submit" value="{{ _('search') }}" />
-      <span id="search-progress" style="padding-left: 10px"></span>
-    </form>
-  {% endblock %}
-  {% block searchresults %}
-    {% if search_performed %}
-      <h2>{{ _('Search Results') }}</h2>
-      {% if not search_results %}
-        <p>{{ _('Your search did not match any documents. Please make sure that all words are spelled correctly and that you\'ve selected enough categories.') }}</p>
-      {% endif %}
-    {% endif %}
-    <div id="search-results">
-      {% if search_results %}
-        <ul>
-          {% for href, caption, context in search_results %}
-            <li><a href="{{ pathto(item.href) }}">{{ caption }}</a>
-              <div class="context">{{ context|e }}</div>
-            </li>
-          {% endfor %}
-        </ul>
-      {% endif %}
-    </div>
-  {% endblock %}
-{% endblock %}
diff --git a/source/advanced_features/converting_into_localization.rst b/source/advanced_features/converting_into_localization.rst
index 25e586161..dabd7e40a 100644
--- a/source/advanced_features/converting_into_localization.rst
+++ b/source/advanced_features/converting_into_localization.rst
@@ -191,7 +191,3 @@ In order to chieve this AB test we need to
     All other nested children can be styled following this pattern.
 
   4. Once you’re done with styling it is very easy to set up an AB test, just go back to Campaign Editor and click "Add A/B test variant" link. Once a Campaign goes Live it will start rotating both variants following AB test distribution rules (50:50 by default).
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/coupons.rst b/source/advanced_features/coupons.rst
index f16c3f50f..09c959b25 100644
--- a/source/advanced_features/coupons.rst
+++ b/source/advanced_features/coupons.rst
@@ -45,10 +45,6 @@ Shopify coupon auto-sync
 
 Read :ref:`Shopify coupon auto-sync documentation <advanced_features/shopify_coupons_auto_sync>` for details.
 
-.. container:: hidden
-
-   .. toctree::
-
 Requirements
 ------------
 
@@ -71,6 +67,6 @@ We do not want people confusing 8 with B, 1 with I, 0 with O, L with 1, etc.
 
    # Generates a random string from a set of easily readable characters
    def generate_activation_code(size = 6)
-     charset = ["2", "3", "4", "6", "7", "9", "A", "C", "D", "E", "F", "G", "H", "J", "K", "M", "N", "P", "Q", "R", "T", "V", "W", "X", "Y", "Z"]
-     (0...size).map { charset[rand(charset.size)] }.join
+      charset = ["2", "3", "4", "6", "7", "9", "A", "C", "D", "E", "F", "G", "H", "J", "K", "M", "N", "P", "Q", "R", "T", "V", "W", "X", "Y", "Z"]
+      (0...size).map { charset[rand(charset.size)] }.join
    end
diff --git a/source/advanced_features/customer_service_portal/overview.rst b/source/advanced_features/customer_service_portal/overview.rst
index be446365d..be93ac40b 100644
--- a/source/advanced_features/customer_service_portal/overview.rst
+++ b/source/advanced_features/customer_service_portal/overview.rst
@@ -30,7 +30,3 @@ To see more personal details, select a user from the list.
 Example of Customer Service Portal person lookup:
 
 .. image:: /_static/img/advanced_features/customer_service_portal/person_lookup.png
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/customer_service_portal/terminology.rst b/source/advanced_features/customer_service_portal/terminology.rst
index db831d078..f69be86fb 100644
--- a/source/advanced_features/customer_service_portal/terminology.rst
+++ b/source/advanced_features/customer_service_portal/terminology.rst
@@ -59,7 +59,3 @@ This is what the person gets as a result of some action (incentive). Available r
 
 - **Blocked/No reward**: there was no reward created either because the associated referral was blocked according to
   Fraud Settings or because of other reasons: incentive criteria has blocked it, or the person was blocklisted.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_1.rst b/source/advanced_features/customer_service_portal/use_case_1.rst
index 6bf5173d9..277d1e8b0 100644
--- a/source/advanced_features/customer_service_portal/use_case_1.rst
+++ b/source/advanced_features/customer_service_portal/use_case_1.rst
@@ -48,7 +48,3 @@ Let’s also expand fraud filters section to check the details:
 
 This looks like a valid referral. Let’s move on to
 :ref:`Use case #2 <advanced_features/customer_service_portal/use_case_2>`.
-
-.. container:: hidden
-
-   .. toctree::
\ No newline at end of file
diff --git a/source/advanced_features/customer_service_portal/use_case_2.rst b/source/advanced_features/customer_service_portal/use_case_2.rst
index 0cb4b70f8..218871358 100644
--- a/source/advanced_features/customer_service_portal/use_case_2.rst
+++ b/source/advanced_features/customer_service_portal/use_case_2.rst
@@ -59,7 +59,3 @@ Here is what email statuses mean:
 - **Clicked**: Stephanie has clicked on the CTA inside the email.
 - **Scheduled**: the email will be sent on a specified date.
 - **Rejected**: the email was rejected by some reason.
-
-.. container:: hidden
-
-   .. toctree::
\ No newline at end of file
diff --git a/source/advanced_features/customer_service_portal/use_case_3.rst b/source/advanced_features/customer_service_portal/use_case_3.rst
index 7a0fa6ae7..c6153e03c 100644
--- a/source/advanced_features/customer_service_portal/use_case_3.rst
+++ b/source/advanced_features/customer_service_portal/use_case_3.rst
@@ -94,7 +94,3 @@ occurs when an Advocate shares with a Friend who purchases and that same Friend
 in an attempt to get both the Advocate and Friend rewards.
 
 We identify this in the same way as described above.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_4.rst b/source/advanced_features/customer_service_portal/use_case_4.rst
index 1924dec80..b86418a3d 100644
--- a/source/advanced_features/customer_service_portal/use_case_4.rst
+++ b/source/advanced_features/customer_service_portal/use_case_4.rst
@@ -51,7 +51,3 @@ flagged/blocked ones. We see that the blocked reason in this case is “Matching
 “Similar email match”:
 
 .. image:: /_static/img/advanced_features/customer_service_portal/marked_as_fraud.jpg
-
-.. container:: hidden
-
-   .. toctree::
\ No newline at end of file
diff --git a/source/advanced_features/customer_service_portal/use_case_5.rst b/source/advanced_features/customer_service_portal/use_case_5.rst
index a57d186e8..b21b5d69f 100644
--- a/source/advanced_features/customer_service_portal/use_case_5.rst
+++ b/source/advanced_features/customer_service_portal/use_case_5.rst
@@ -44,7 +44,3 @@ How do I UnBlocklist a user?
 If you realize that you made a mistake in Blocklisting a user who should actually be receiving rewards,
 all you have to do to take a user off the blocklist is to delete their email or IP from the list and then hit
 “Save Changes” again. It’s that easy.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_6.rst b/source/advanced_features/customer_service_portal/use_case_6.rst
index a79bc0599..624f1b558 100644
--- a/source/advanced_features/customer_service_portal/use_case_6.rst
+++ b/source/advanced_features/customer_service_portal/use_case_6.rst
@@ -50,7 +50,3 @@ After creating the referral manually you will be taken to the newly created refe
 
 Advocate reward may be blocked due to incentive criteria, make sure to check the Advocate’s reward status as shown
 on the screenshot above.
-
-.. container:: hidden
-
-   .. toctree::
\ No newline at end of file
diff --git a/source/advanced_features/file_encryption.rst b/source/advanced_features/file_encryption.rst
index 1d47ae910..9a677ddc0 100644
--- a/source/advanced_features/file_encryption.rst
+++ b/source/advanced_features/file_encryption.rst
@@ -66,7 +66,3 @@ To decrypt a file simply call GPG on it:
    gpg file_name.asc
 
 .. _How To Use GPG to Encrypt and Sign Messages: https://www.digitalocean.com/community/tutorials/how-to-use-gpg-to-encrypt-and-sign-messages#set-up-gpg-keys
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/passing_custom_data.rst b/source/advanced_features/passing_custom_data.rst
index 0f3b5db64..699c3c23b 100644
--- a/source/advanced_features/passing_custom_data.rst
+++ b/source/advanced_features/passing_custom_data.rst
@@ -83,7 +83,3 @@ Key-Value pairs can be referenced calling the desired data key, such as:
 
     Any ``custom_properties`` data passed through is tied to the |advocate|, |friend|, or |loyalty_member|.
     If Talkable receives a custom property that was previously defined for the user, the property gets overwritten with a new value.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/personal_coupon_sharing.rst b/source/advanced_features/personal_coupon_sharing.rst
index be0c91a09..4e818b1b4 100644
--- a/source/advanced_features/personal_coupon_sharing.rst
+++ b/source/advanced_features/personal_coupon_sharing.rst
@@ -7,8 +7,8 @@ Advocate Personal Coupon Sharing
 ================================
 
 .. note::
-  This is an experimental feature, please ask your Customer Success Manager
-  to apply it into your campaigns.
+   This is an experimental feature, please ask your Customer Success Manager
+   to apply it into your campaigns.
 
 At Talkable Advocates can invite Friends in two ways:
 
@@ -125,8 +125,3 @@ A: Here is a list of validation rules that are defined globally for any coupons:
   #. Coupon length is between 3 and 255 characters
 
 Any UTF8 characters are allowed (including spaces).
-
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/reg_ex.rst b/source/advanced_features/reg_ex.rst
index 1e03ae270..5c73de3cb 100644
--- a/source/advanced_features/reg_ex.rst
+++ b/source/advanced_features/reg_ex.rst
@@ -130,7 +130,3 @@ formats:
      * `http://site.com/test/products/one`
      * `http://stage.com/products/two`
      * `http://test.com/test/products/one/deep?utm=test`
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/segments.rst b/source/advanced_features/segments.rst
index bf249f1c7..3df0b41a6 100644
--- a/source/advanced_features/segments.rst
+++ b/source/advanced_features/segments.rst
@@ -101,8 +101,3 @@ In this example, `segment1`, `segment2`, and `segment3` attributes are passed th
    Segments can also be passed in `register_affiliate`, `register_purchase`, and `register_event`, providing flexibility for different integration scenarios.
 
 This approach simplifies custom data handling for customers, allowing for unified data across various methods and optimizing segmentation management without additional calls.
-
-.. container:: hidden
-
-   .. toctree::
-
diff --git a/source/advanced_features/single_sign_on.rst b/source/advanced_features/single_sign_on.rst
index 1d70168e8..cfb325dea 100644
--- a/source/advanced_features/single_sign_on.rst
+++ b/source/advanced_features/single_sign_on.rst
@@ -92,7 +92,3 @@ Once you've configured SSO, you can test it as followed:
 2. Visit the SP-Initiated SSO URL (provided on the SSO configuration page in Talkable)
 
    .. image:: /_static/img/advanced_features/sso_sp_initiated_url.png
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/subscribing_to_events.rst b/source/advanced_features/subscribing_to_events.rst
index 5bba0a677..3175930c7 100644
--- a/source/advanced_features/subscribing_to_events.rst
+++ b/source/advanced_features/subscribing_to_events.rst
@@ -51,7 +51,3 @@ Talkable campaigns are equipped with the following set of events:
   6. `share_succeeded` — fires each time |advocate| shares. `data.channel` tells which sharing channel was used for the share.
   7. `email_gating_passed` — fires when |friend| passes email gating on :ref:`Friend Claim Page <campaigns/views/offers_claim>`.
   8. `email_gating_failed` — fires when |friend| fails to pass email gating on :ref:`Friend Claim Page <campaigns/views/offers_claim>`.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/advanced_features/url_parameters.rst b/source/advanced_features/url_parameters.rst
index bda339fa0..9cfadfa2d 100644
--- a/source/advanced_features/url_parameters.rst
+++ b/source/advanced_features/url_parameters.rst
@@ -28,7 +28,3 @@ integration.
 .. note::
 
    Don’t forget to escape URL parameters with URI parameter encoder.
-
-.. container:: hidden
-
-  .. toctree::
diff --git a/source/advanced_features/utm_tags.rst b/source/advanced_features/utm_tags.rst
index 78c008c5f..6bf581a0d 100644
--- a/source/advanced_features/utm_tags.rst
+++ b/source/advanced_features/utm_tags.rst
@@ -23,7 +23,3 @@ Example of usage:
 .. code-block:: text
 
    https://example1.com/friends?refer=friends&utm_source=example_source&utm_medium=example_medium
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/android_sdk/advanced.rst b/source/android_sdk/advanced.rst
index a7f61f3b9..853d9002f 100644
--- a/source/android_sdk/advanced.rst
+++ b/source/android_sdk/advanced.rst
@@ -192,7 +192,3 @@ your Android application.
 .. _`handle configuration changes`: https://developer.android.com/guide/topics/resources/runtime-changes.html
 .. _`Fragment`: https://developer.android.com/guide/fragments
 .. _`Fragment Transactions`: https://developer.android.com/guide/fragments/transactions
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/android_sdk/api.rst b/source/android_sdk/api.rst
index 039e5d2ef..152cdd32d 100644
--- a/source/android_sdk/api.rst
+++ b/source/android_sdk/api.rst
@@ -230,7 +230,3 @@ Use the ``createSocialShare`` method to track a social share.
            // Process error
        }
    });
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/android_sdk/deep_linking.rst b/source/android_sdk/deep_linking.rst
index 218cc4149..b5e6e26a7 100644
--- a/source/android_sdk/deep_linking.rst
+++ b/source/android_sdk/deep_linking.rst
@@ -225,7 +225,3 @@ The SDK supports Android 4.1 and later.
 .. _`GetSocial.im`: https://www.getsocial.im
 .. _`Android App Links docs`: https://developer.android.com/training/app-links/index.html
 .. _`Finding SHA256 fingerprint for Android signing keys`: https://docs.getsocial.im/knowledge-base/android-signing-key-sha256/
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/android_sdk/getting_started.rst b/source/android_sdk/getting_started.rst
index 0a44dce7b..eb2ea895c 100644
--- a/source/android_sdk/getting_started.rst
+++ b/source/android_sdk/getting_started.rst
@@ -162,7 +162,3 @@ Requirements
 The SDK supports Android 4.1 and later.
 
 .. _`Talkable SDK framework`: https://talkable-downloads.s3.amazonaws.com/android-sdk/talkable-sdk.aar
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/android_sdk/integration/post_purchase.rst b/source/android_sdk/integration/post_purchase.rst
index 0ca3ef434..d58f58b73 100644
--- a/source/android_sdk/integration/post_purchase.rst
+++ b/source/android_sdk/integration/post_purchase.rst
@@ -58,7 +58,3 @@ Here is an example of a Purchase capturing, this action should be triggered on t
    If Post Purchase campaign does not show up when testing make sure you have it Live
    on the Campaigns listing with `android-post-purchase` tag or the tag you specified
    in `setCampaignTag`.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/android_sdk/integration/standalone.rst b/source/android_sdk/integration/standalone.rst
index b072b19ca..35c42f115 100644
--- a/source/android_sdk/integration/standalone.rst
+++ b/source/android_sdk/integration/standalone.rst
@@ -65,7 +65,3 @@ flow and show the :ref:`Advocate Share Form <campaigns/views/offers_show>`.
       }
   });
   ...
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/android_sdk/testing.rst b/source/android_sdk/testing.rst
index 1bba47163..9be7f8167 100644
--- a/source/android_sdk/testing.rst
+++ b/source/android_sdk/testing.rst
@@ -36,7 +36,3 @@ will be applied only if debug is set to `true`.
 .. warning::
 
    Debug mode must be turned off for release builds. Leaving it enabled will break the referral cycle and expose you to fraud.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/android_sdk/upgrade.rst b/source/android_sdk/upgrade.rst
index 64f4b898a..f0fe7b90c 100644
--- a/source/android_sdk/upgrade.rst
+++ b/source/android_sdk/upgrade.rst
@@ -283,7 +283,3 @@ Look in :ref:`installation section <main_activity_setup>` for more detailed info
 -----
 
 It’s initial release, nothing to do.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/campaigns.rst b/source/campaigns.rst
index 980d8a001..b8f5b5876 100644
--- a/source/campaigns.rst
+++ b/source/campaigns.rst
@@ -41,12 +41,12 @@ To start editing Views simply visit ``Editor`` page from the Campaign dashboard.
 
   <h2>Campaign Structure</h2>
 
-+-------------------------------+-----------------------------+
-| .. toctree::                  |                             |
-|   :maxdepth: 2                |                             |
-|                               |                             |
-|   campaigns/views             |                             |
-+-------------------------------+-----------------------------+
++-------------------------------+
+| .. toctree::                  |
+|   :maxdepth: 2                |
+|                               |
+|   campaigns/views             |
++-------------------------------+
 
 .. raw:: html
 
@@ -65,9 +65,9 @@ To start editing Views simply visit ``Editor`` page from the Campaign dashboard.
 
   <h2>Designer Guide</h2>
 
-+-------------------------------+-----------------------------+
-| .. toctree::                  |                             |
-|   :maxdepth: 2                |                             |
-|                               |                             |
-|   campaigns/designer          |                             |
-+-------------------------------+-----------------------------+
++-------------------------------+
+| .. toctree::                  |
+|   :maxdepth: 2                |
+|                               |
+|   campaigns/designer          |
++-------------------------------+
diff --git a/source/conf.py b/source/conf.py
index 857a33319..9ba32d7fc 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -28,7 +28,7 @@
 # Add any Sphinx extension module names here, as strings. They can be
 # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
 # ones.
-extensions = ['sphinx_sitemap']
+extensions = ['sphinx_sitemap', 'sphinx_copybutton']
 sitemap_url_scheme = "{link}"
 
 # Add any paths that contain templates here, relative to this directory.
@@ -100,20 +100,22 @@
 
 # The theme to use for HTML and HTML Help pages.  See the documentation for
 # a list of builtin themes.
-html_theme = 'basic'
-html_style = 'talkable.css'
+html_theme = "furo"
+# html_style = 'talkable.css'
 
 # Theme options are theme-specific and customize the look and feel of a theme
 # further.  For a list of options available for each theme, see the
 # documentation.
-#html_theme_options = {}
+
+html_copy_source = False
+html_show_sourcelink = False
 
 # Add any paths that contain custom themes here, relative to this directory.
 #html_theme_path = []
 
 # The name for this set of Sphinx documents.  If None, it defaults to
 # "<project> v<release> documentation".
-html_title = u'Talkable Documentation'
+html_title = u''
 
 # A shorter title for the navigation bar.  Default is the same as html_title.
 #html_short_title = None
@@ -131,6 +133,18 @@
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
 html_static_path = ['_static']
+html_css_files = [
+    'talkable.css',
+]
+html_theme_options = {
+    "light_logo": "img/logo.svg",
+    "dark_logo": "img/logo.svg",
+    "light_css_variables": {
+        "color-brand-primary": "#D36835",
+        "color-brand-content": "#D36835",
+        "color-brand-visited": "#D36835",
+    },
+}
 
 # Add any extra paths that contain custom files (such as robots.txt or
 # .htaccess) here, relative to this directory. These files are copied
diff --git a/source/integration/custom/overview.rst b/source/integration/custom/overview.rst
index 8ba24a744..24cbd6ef6 100644
--- a/source/integration/custom/overview.rst
+++ b/source/integration/custom/overview.rst
@@ -10,15 +10,15 @@ Integration High-Level Overview
 Integrating Talkable referral marketing platform to e-commerce sites is done in
 a few quick steps by adding the below scripts to your site.
 
- .. note::
+.. note::
 
-    All design and referral campaign setup is done inside the Talkable platform,
-    then via ‘iframe’ referral campaign content is injected into the e-commerce
-    site. The below scripts also handle the collection of specific necessary user
-    data for Talkable to service the referral campaigns.
+   All design and referral campaign setup is done inside the Talkable platform,
+   then via ‘iframe’ referral campaign content is injected into the e-commerce
+   site. The below scripts also handle the collection of specific necessary user
+   data for Talkable to service the referral campaigns.
 
-    Site-specific integration scripts are found after logging in at
-    ``https://www.admin.talkable.com/sites/<YOUR-TALKABLE-SITE-ID>/integration/other``
+   Site-specific integration scripts are found after logging in at
+   ``https://www.admin.talkable.com/sites/<YOUR-TALKABLE-SITE-ID>/integration/other``
 
 .. raw:: html
 
@@ -35,14 +35,14 @@ a few quick steps by adding the below scripts to your site.
    Surface purchase detail variables as described in more detail in
    :ref:`Integration Components <integration/custom/integration_components>`.
 
- .. note::
+.. note::
 
-    If a business has both one-time purchases and subscription transactions, or
-    the business has a strictly subscription or SaaS model we recommend integrating
-    the ‘Post Purchase’ through Events. :ref:`Learn more <advanced_features/events>`.
+   If a business has both one-time purchases and subscription transactions, or
+   the business has a strictly subscription or SaaS model we recommend integrating
+   the ‘Post Purchase’ through Events. :ref:`Learn more <advanced_features/events>`.
 
-    Post Purchase step is the only step which changes for subscription business
-    model integration - other steps remain the same.
+   Post Purchase step is the only step which changes for subscription business
+   model integration - other steps remain the same.
 
 3. To host the Invite Standalone campaign, create a new HTML page with standard
    header/footer. Best practice is to create this page on ``www.your-site.com/share``
diff --git a/source/ios_sdk/advanced.rst b/source/ios_sdk/advanced.rst
index 5ec35562b..fb2e55349 100644
--- a/source/ios_sdk/advanced.rst
+++ b/source/ios_sdk/advanced.rst
@@ -148,7 +148,3 @@ See all debugging information in your console which can help you to understand w
     #import <TalkableSDK/Talkable.h>
     // ...
     [Talkable manager].debug = YES;
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/ios_sdk/api_integration.rst b/source/ios_sdk/api_integration.rst
index a810d8604..73655b57b 100644
--- a/source/ios_sdk/api_integration.rst
+++ b/source/ios_sdk/api_integration.rst
@@ -193,7 +193,3 @@ to fetch the Offer.
   [[Talkable manager] retrieveOffer:shortUrlCode withHandler:^(NSDictionary* response, NSError* error) {
       NSDictionary* offerParams = [response objectForKey:TKBLOfferKey];
   }];
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/ios_sdk/example.rst b/source/ios_sdk/example.rst
index 243dec7b8..ff2ddabea 100644
--- a/source/ios_sdk/example.rst
+++ b/source/ios_sdk/example.rst
@@ -9,7 +9,3 @@ In case you want to take a look at the actual code and see it in action we creat
 If you have any questions, don’t hesitate to email us at support@talkable.com. Happy hacking!
 
 .. _`here`: https://talkable-downloads.s3.amazonaws.com/ios-sdk/talkable_sdk_demo.zip
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/ios_sdk/integration/post_purchase.rst b/source/ios_sdk/integration/post_purchase.rst
index 41376cc2c..0e2926c14 100644
--- a/source/ios_sdk/integration/post_purchase.rst
+++ b/source/ios_sdk/integration/post_purchase.rst
@@ -39,7 +39,3 @@ Here is an example of a Purchase capturing, this action should be triggered on t
   If Post Purchase campaign does not show up when testing, make sure you have it
   Live on the Campaigns listing with a default tag (`ios-post-purchase`) or with
   a tag you specified in the `registerOrigin` call.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/ios_sdk/integration/standalone.rst b/source/ios_sdk/integration/standalone.rst
index 74ccce780..005e0f0b8 100644
--- a/source/ios_sdk/integration/standalone.rst
+++ b/source/ios_sdk/integration/standalone.rst
@@ -37,7 +37,3 @@ Note that `params` are empty, in this case user will see Signup form on :ref:`Ad
     }
   };
   [[Talkable manager] registerOrigin:TKBLAffiliateMember params:params];
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/partials/campaign_placements_description.rst b/source/partials/campaign_placements_description.rst
index 83dd9540e..3a79a4b16 100644
--- a/source/partials/campaign_placements_description.rst
+++ b/source/partials/campaign_placements_description.rst
@@ -6,7 +6,9 @@ The list of all Campaign Placements can be found by going to the All Site Settin
 
   <img src="../_static/img/campaign_placements/path.png" />
 
-**Managing Placements**.
+Managing Placements
+-------------------
+
 By default you already have all types of Placements created automatically.
 Campaigns that you create will attach to one of these Placements based on their types.
 If you want you can create a new Standalone Placement for your site matching another URL and attach another
@@ -16,19 +18,25 @@ Standalone Campaigns there.
   Placements are strictly tied to their Campaign types.
   You cannot attach Post Purchase Campaign to Standalone Placement because it expects Campaigns that are going to be embedded not being shown as a popup.
 
-**Priority**.
+Priority
+--------
+
 The Placements in the list are ordered by priority. In order to show a Campaign, Talkable matches
 the URL of a Campaign Placement inclusion (marked as “Shown on”) and a URL that comes with each request that
 users initiate, for example: `https://[your-site]/share`. Whenever multiple Campaign Placements fit the requested URL
 Talkable picks the first Placement that sits up top out of the suitable ones. Other Placements that sit below it are
 ignored in this case.
 
-**Visibility**.
+Visibility
+----------
+
 It is possible to indicate on which specific pages the Campaigns attached to the Placement should or should not be shown.
 It allows you to show the Campaign on all pages of your site except few specified in the "Hidden on" section, for example.
 Also, you can use :ref:`regular expressions<advanced_features/reg_ex>` to select pages you want to not show Talkable campaigns on.
 
-**Custom Property Criteria**.
+Custom Property Criteria
+------------------------
+
 A Placement can have a set of criteria defined based on :ref:`custom properties <advanced_features/passing_custom_data>`.
 If all of the criteria are met, the placement will show a campaign.
 
@@ -41,13 +49,12 @@ The criteria can be defined using one of the following operators:
 .. note::
   Custom Property Criteria require integration version 5.1.4 or higher to work.
 
-|hr|
-
-.. raw:: html
 
-  <h2>Referral Placements</h2>
+Referral Placements
+~~~~~~~~~~~~~~~~~~~
 
-  <h3>Standalone</h3>
+Standalone
+^^^^^^^^^^
 
 Campaign will show up on the standalone page on your site, for example: |br|
 `https://[your-site]/share`.
@@ -56,9 +63,8 @@ Campaign will be rendered as an inline block in a corresponding Talkable DIV tag
 
 :ref:`Learn more about Standalone Placement <campaigns/campaign_placements/standalone>`
 
-.. raw:: html
-
-  <h3>Post Purchase</h3>
+Post Purchase
+^^^^^^^^^^^^^
 
 Campaign will show up on a successful purchase made by the customer on your site.
 Usually this is an order confirmation page after checkout.
@@ -66,9 +72,8 @@ The campaign will look like a popup with an overlay and a close button.
 
 :ref:`Learn more about Post Purchase Placement <campaigns/campaign_placements/post_purchase>`
 
-.. raw:: html
-
-  <h3>Floating Widget</h3>
+Floating Widget
+^^^^^^^^^^^^^^^
 
 Campaign will show up on every page as a floating button in a corner of the screen so customers are able to access
 Talkable campaigns from anywhere on your site.
@@ -77,9 +82,8 @@ and a close button.
 
 :ref:`Learn more about Floating Widget Placement <campaigns/campaign_placements/floating_widget>`
 
-.. raw:: html
-
-  <h3>Claim by Name Widget</h3>
+Claim by Name Widget
+^^^^^^^^^^^^^^^^^^^^
 
 Campaign will show up as a floating button in a corner of the screen on the cart or checkout page on your site,
 for example: |br|
@@ -89,20 +93,19 @@ Clicking on a Claim by Name widget opens a popup with an overlay and a close but
 
 :ref:`Learn more about Claim by Name Placement <campaigns/campaign_placements/claim_by_name>`
 
-.. raw:: html
-
-  <h3>Gleam</h3>
+Gleam
+^^^^^
 
 Campaign will show up on every page as a floating bar that shows your customers their coupon codes
 after they have been rewarded within any other of your Talkable Campaigns.
 
 :ref:`Learn more about Gleam Placement <campaigns/campaign_placements/gleam>`
 
-.. raw:: html
-
-  <h2>Loyalty Placements</h2>
+Loyalty placements
+~~~~~~~~~~~~~~~~~~
 
-  <h3>Loyalty Dashboard</h3>
+Loyalty Dashboard
+^^^^^^^^^^^^^^^^^
 
 Campaign will show up on the loyalty page on your site, for example: |br|
 `https://[your-site]/loyalty`.
@@ -111,9 +114,8 @@ Campaign will be rendered as an inline block in a corresponding Talkable DIV tag
 
 :ref:`Learn more about Loyalty Dashboard Placement <campaigns/campaign_placements/loyalty_dashboard>`
 
-.. raw:: html
-
-  <h3>Loyalty Widget</h3>
+Loyalty Widget
+^^^^^^^^^^^^^^
 
 Campaign will show up on every page as a floating widget that allows your customers to convert their points into coupons.
 
@@ -124,11 +126,8 @@ If a customer is not signed in, the widget prompts them to join the loyalty prog
 .. note::
   When both Loyalty Dashboard and Loyalty Widget are matched on the same URL, only Dashboard will be shown.
 
-|hr|
-
-.. raw:: html
-
-  <h2>Campaigns Rotating</h2>
+Campaigns Rotating
+~~~~~~~~~~~~~~~~~~
 
 It is worth mentioning that you can also attach multiple Campaigns into one Placement.
 In this case Talkable will always show only one Campaign based on a random rotation.
diff --git a/source/web_hooks/check_unsubscribe.rst b/source/web_hooks/check_unsubscribe.rst
index fdd982b59..142f3193c 100644
--- a/source/web_hooks/check_unsubscribe.rst
+++ b/source/web_hooks/check_unsubscribe.rst
@@ -50,7 +50,3 @@ View category can be one of the following:
 * advocate_rewards_confirmation
 * advocate_rewards_paid
 * friend_rewards_paid
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/web_hooks/claim_signup.rst b/source/web_hooks/claim_signup.rst
index a2c36b2b6..55ad8c28d 100644
--- a/source/web_hooks/claim_signup.rst
+++ b/source/web_hooks/claim_signup.rst
@@ -37,7 +37,3 @@ Friend Email Gating form example:
    <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Friend Email Gating Webhook is available here: `Friend Email Gating Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Friend%20Email%20Gating/post_your_api_claim_signup_web_hook_path>`_.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/web_hooks/create_coupon.rst b/source/web_hooks/create_coupon.rst
index f2114591f..ba003c5ca 100644
--- a/source/web_hooks/create_coupon.rst
+++ b/source/web_hooks/create_coupon.rst
@@ -81,7 +81,3 @@ Create Coupon Webhook can now be set up.
    <h2>Payload parameters provided by Create Coupon Webhook</h2>
 
 The sample payload with parameters for Create Coupon Webhook is available here: `Create Coupon Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Create%20Coupon/post_your_api_create_coupon_web_hook_path>`_.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/web_hooks/event.rst b/source/web_hooks/event.rst
index 16815c0e5..77f3bf667 100644
--- a/source/web_hooks/event.rst
+++ b/source/web_hooks/event.rst
@@ -30,8 +30,3 @@ or using the :ref:`Talkable backend API <api_v2/origins>`.
    <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Event Webhook is available here: `Event Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Event/post_your_api_event_web_hook_path>`_.
-
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/web_hooks/offer_signup.rst b/source/web_hooks/offer_signup.rst
index 5f735b616..011bb396c 100644
--- a/source/web_hooks/offer_signup.rst
+++ b/source/web_hooks/offer_signup.rst
@@ -37,7 +37,3 @@ Advocate Signup Form example:
    <h2>Payload parameters provided for Advocate Signup Webhook</h2>
 
 The sample payload with parameters for Advocate Signup Webhook is available here: `Advocate Signup Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Advocate%20Signup/post_your_api_advocate_signup_web_hook_path>`_.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/web_hooks/post_share.rst b/source/web_hooks/post_share.rst
index a83fb68a7..4dacab6fa 100644
--- a/source/web_hooks/post_share.rst
+++ b/source/web_hooks/post_share.rst
@@ -43,7 +43,3 @@ The sample payload with parameters for Post Share Webhook is available here: `Po
    first shown to the Advocate. It could be ``null``. For the most up-to-date
    information about the Advocate, use ``sharer_info`` property which is updated
    with the email address the Advocate has entered on the Advocate Signup/Share Page.
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/web_hooks/referral.rst b/source/web_hooks/referral.rst
index bb2b4e04f..ccc44caee 100644
--- a/source/web_hooks/referral.rst
+++ b/source/web_hooks/referral.rst
@@ -62,7 +62,3 @@ The sample payload with parameters for Referral Webhook is available here: `Refe
 .. include:: /partials/coupon_as_reward.rst
 
 .. include:: /partials/incentive_types.rst
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/web_hooks/reward.rst b/source/web_hooks/reward.rst
index 24dd1d351..5756470b1 100644
--- a/source/web_hooks/reward.rst
+++ b/source/web_hooks/reward.rst
@@ -104,7 +104,3 @@ Reward reason can be of 5 following general types.
 .. include:: /partials/incentive_types.rst
 
 .. include:: /partials/coupon_as_reward.rst
-
-.. container:: hidden
-
-   .. toctree::
diff --git a/source/web_hooks/unsubscribe.rst b/source/web_hooks/unsubscribe.rst
index f4b66c7c5..7686cec00 100644
--- a/source/web_hooks/unsubscribe.rst
+++ b/source/web_hooks/unsubscribe.rst
@@ -29,7 +29,3 @@ Talkable sent email.
    <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Unsubscribe Webhook is available here: `Unsubscribe Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Unsubscribe/post_your_api_unsubscribe_web_hook_path>`_.
-
-.. container:: hidden
-
-   .. toctree::

From 9652fd3bc6ff59570d071da761849590a70bccae Mon Sep 17 00:00:00 2001
From: Vitalii Oliinyk <ilovepinkpony1@gmail.com>
Date: Fri, 17 Jan 2025 13:13:41 +0200
Subject: [PATCH 02/62] [PR-23724]: updated styles

---
 source/_static/talkable.css | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/source/_static/talkable.css b/source/_static/talkable.css
index 25b0c2481..ca2bb9c1e 100644
--- a/source/_static/talkable.css
+++ b/source/_static/talkable.css
@@ -32,3 +32,7 @@ body[data-theme="light"] .highlight button.copybtn.success:after {
 .headerlink {
   visibility: hidden !important;
 }
+
+.hidden {
+  display: none;
+}

From 506bae7de681ec120202eaf7d44f98a4ff04e1a3 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Wed, 22 Jan 2025 19:46:56 +0300
Subject: [PATCH 03/62] added venv didrectories to exclusions

---
 .gitignore | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/.gitignore b/.gitignore
index 14ec1a9a3..e76bee5da 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,7 +1,11 @@
 /build
+_build
 /.bundle
 Gemfile.lock
 source/_static/test
 .pivotalrc
 .idea
 *.log
+
+.env
+.venv
\ No newline at end of file

From d003f91001fd03cad37bf538e48af814e58546bf Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Wed, 22 Jan 2025 19:49:27 +0300
Subject: [PATCH 04/62] refactoring

---
 Dockerfile           | 26 ++++++++++++++++++++++++++
 README-dev.md        |  5 +++++
 docker-compose.yml   |  0
 requirements-dev.txt |  5 +++++
 requirements.txt     |  3 +++
 5 files changed, 39 insertions(+)
 create mode 100644 Dockerfile
 create mode 100644 README-dev.md
 create mode 100644 docker-compose.yml
 create mode 100644 requirements-dev.txt

diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 000000000..c11bb7d0e
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,26 @@
+# Use the official Python 3.13 Alpine image as the base
+FROM python:3.13-alpine3.21
+
+# Set environment variables to prevent Python from writing .pyc files
+ENV PYTHONDONTWRITEBYTECODE=1
+ENV PYTHONUNBUFFERED=1
+
+# Install system dependencies
+RUN apk add --no-cache \
+    build-base \
+    libffi-dev \
+    openssl-dev \
+    git
+
+# Install Sphinx and common dependencies
+RUN pip install --upgrade pip && \
+    pip install sphinx sphinx_rtd_theme myst_parser
+
+# Create and set the working directory
+WORKDIR /docs
+
+# Copy documentation source files into the container
+COPY . /docs
+
+# Default command to build the Sphinx documentation
+CMD ["sphinx-build", "-b", "html", ".", "_build"]
\ No newline at end of file
diff --git a/README-dev.md b/README-dev.md
new file mode 100644
index 000000000..706e953f8
--- /dev/null
+++ b/README-dev.md
@@ -0,0 +1,5 @@
+Run shinx so it builds teh directory for every page to hide `.html` extension from the path
+
+```bash
+sphinx-autobuild -b dirhtml source _build/html
+```
\ No newline at end of file
diff --git a/docker-compose.yml b/docker-compose.yml
new file mode 100644
index 000000000..e69de29bb
diff --git a/requirements-dev.txt b/requirements-dev.txt
new file mode 100644
index 000000000..7315bc22c
--- /dev/null
+++ b/requirements-dev.txt
@@ -0,0 +1,5 @@
+furo
+sphinx-copybutton
+# sphinx
+sphinx-sitemap
+sphinx-autobuild
\ No newline at end of file
diff --git a/requirements.txt b/requirements.txt
index ffd6786dc..3c134f214 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -2,3 +2,6 @@ furo
 sphinx-copybutton
 Sphinx==8.1.3
 sphinx-sitemap==2.6.0
+
+
+sphinx-autobuild
\ No newline at end of file

From 418cb1aacd4b3a73b39486b2dce5da20e36208ac Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Thu, 23 Jan 2025 17:42:33 +0300
Subject: [PATCH 05/62] creanup from the ruby way of deployment

---
 .circleci/config.yml             |  38 -----------
 .github/PULL_REQUEST_TEMPLATE.md |   9 ---
 .gitignore                       |  10 +--
 .ruby-gemset                     |   1 -
 .ruby-version                    |   1 -
 CNAME                            |   1 -
 Gemfile                          |  11 ----
 Guardfile                        |  14 ----
 Procfile                         |   2 -
 README-dev.md                    |   5 --
 Rakefile                         | 109 -------------------------------
 robots.txt                       |   3 -
 12 files changed, 3 insertions(+), 201 deletions(-)
 delete mode 100644 .circleci/config.yml
 delete mode 100644 .github/PULL_REQUEST_TEMPLATE.md
 delete mode 100644 .ruby-gemset
 delete mode 100644 .ruby-version
 delete mode 100644 CNAME
 delete mode 100644 Gemfile
 delete mode 100644 Guardfile
 delete mode 100644 Procfile
 delete mode 100644 README-dev.md
 delete mode 100644 Rakefile
 delete mode 100644 robots.txt

diff --git a/.circleci/config.yml b/.circleci/config.yml
deleted file mode 100644
index 72d4b3d46..000000000
--- a/.circleci/config.yml
+++ /dev/null
@@ -1,38 +0,0 @@
-version: 2.1
-
-executors:
-  default:
-    docker:
-      - auth:
-          username: $DOCKERHUB_USERNAME
-          password: $DOCKERHUB_ACCESS_TOKEN
-        image: cimg/python:3.12
-
-orbs:
-  python: circleci/python@2.1.1
-
-jobs:
-  build:
-    executor: default
-
-    steps:
-      - checkout
-
-      - python/install-packages:
-          app-dir: ~/project
-
-      - run:
-          name: Build documentation
-          command: sphinx-build -nW -b html -d build/doctrees source build/html
-
-workflows:
-  workflow:
-    jobs:
-      - build:
-          context:
-            - org-global
-          filters:
-            branches:
-              ignore:
-                - gh-pages
-                - /.*-gh-pages/
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 5d752ddc8..000000000
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<!--- Provide a general summary of your changes in the Title above -->
-
-## Demo
-<!--- Please provide a link to a demo -->
-https://deploy-preview-{{id}}--talkable-docs.netlify.app/
-
-## Related Stories
-<!--- If this pull request is related to JIRA story, please link to the story here -->
-[![](http://proxies.talkable.com/talkable/PR-1234)](https://talkable.atlassian.net/browse/PR-1234)
diff --git a/.gitignore b/.gitignore
index e76bee5da..e0b54580d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,11 +1,7 @@
-/build
-_build
-/.bundle
-Gemfile.lock
-source/_static/test
-.pivotalrc
 .idea
 *.log
 
 .env
-.venv
\ No newline at end of file
+.venv
+
+_build
\ No newline at end of file
diff --git a/.ruby-gemset b/.ruby-gemset
deleted file mode 100644
index 10b85f5b3..000000000
--- a/.ruby-gemset
+++ /dev/null
@@ -1 +0,0 @@
-talkable-docs
diff --git a/.ruby-version b/.ruby-version
deleted file mode 100644
index 47b322c97..000000000
--- a/.ruby-version
+++ /dev/null
@@ -1 +0,0 @@
-3.4.1
diff --git a/CNAME b/CNAME
deleted file mode 100644
index fe80f6e25..000000000
--- a/CNAME
+++ /dev/null
@@ -1 +0,0 @@
-docs.talkable.com
diff --git a/Gemfile b/Gemfile
deleted file mode 100644
index 11fcd5bc1..000000000
--- a/Gemfile
+++ /dev/null
@@ -1,11 +0,0 @@
-source 'https://rubygems.org'
-
-ruby file: '.ruby-version'
-
-gem 'base64' # Removed from standard library in Ruby 3.4
-gem 'foreman'
-gem 'guard-livereload'
-gem 'guard-shell'
-gem 'rake'
-gem 'reline' # Removed from standard library in Ruby 3.5
-gem 'webrick'
diff --git a/Guardfile b/Guardfile
deleted file mode 100644
index dfe8ecf09..000000000
--- a/Guardfile
+++ /dev/null
@@ -1,14 +0,0 @@
-guard 'shell' do
-  watch(%r{(.*)\.rst}) do |m|
-    system("sphinx-build -b html -d build/doctrees source build/html")
-  end
-
-  watch(%r{^source/_static/}) do |m|
-    system("rsync -az source/_static build/html")
-  end
-end
-
-guard 'livereload' do
-  watch(%r{(.*)\.rst})
-  watch(%r{^source/_static/})
-end
diff --git a/Procfile b/Procfile
deleted file mode 100644
index 2da95c518..000000000
--- a/Procfile
+++ /dev/null
@@ -1,2 +0,0 @@
-web: ruby -run -e httpd -- --port=5001 build/html
-guard: bundle exec guard
diff --git a/README-dev.md b/README-dev.md
deleted file mode 100644
index 706e953f8..000000000
--- a/README-dev.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Run shinx so it builds teh directory for every page to hide `.html` extension from the path
-
-```bash
-sphinx-autobuild -b dirhtml source _build/html
-```
\ No newline at end of file
diff --git a/Rakefile b/Rakefile
deleted file mode 100644
index f47ca6c00..000000000
--- a/Rakefile
+++ /dev/null
@@ -1,109 +0,0 @@
-# frozen_string_literal: true
-require 'mkmf'
-
-SPHINX_BUILD = ENV['SPHINX_BUILD'] || 'sphinx-build'
-SOURCE_DIR   = 'source'
-BUILD_DIR    = 'build'
-SPHINX_OPTS  = "-b html -d #{BUILD_DIR}/doctrees #{SOURCE_DIR} #{BUILD_DIR}/html"
-
-task :default => :help
-task :help do
-  system 'rake --tasks'
-end
-
-desc 'Set up deploys'
-task :setup do
-  sh 'git remote add staging git@github.com:talkable/void-talkable-docs.git'
-end
-
-task :environment do
-  ENV['LANG'] = ENV['LC_ALL'] = 'en_US.UTF-8'
-  find_executable(SPHINX_BUILD) || abort("The '#{SPHINX_BUILD}' command was not found. Make sure you have Sphinx installed, then set the SPHINX_BUILD environment variable to point to the full path of the '#{SPHINX_BUILD}' executable. Alternatively you can add the directory with the executable to your PATH. If you do not have Sphinx installed, grab it from http://sphinx-doc.org/")
-
-  regexp = /(\d+\.)?(\d+\.)?(\*|\d+)/
-  required = File.read('requirements.txt').match(regexp).to_s
-  installed = `#{SPHINX_BUILD} --version`.match(regexp).to_s rescue ''
-  if !required.empty? && !installed.empty? && Gem::Version.new(required) > Gem::Version.new(installed)
-    abort "\nYou are running an outdated version of Sphinx #{installed}. Required version is #{required}. Run `pip3 install -r requirements.txt --break-system-packages` to upgrade Sphinx."
-  end
-end
-
-desc 'Run build in test mode'
-task :test => :environment do
-  sh "#{SPHINX_BUILD} -nW #{SPHINX_OPTS}"
-end
-
-task :build => :environment do
-  sh "#{SPHINX_BUILD} #{SPHINX_OPTS}"
-
-  Rake::FileList["#{BUILD_DIR}/html/**/*.html"].each do |filename|
-    File.open(filename, "r+") do |file|
-      old_content = file.read
-      new_content = old_content.gsub(%r{<a(.+)href="(https?://(?!(?:www\.)?talkable\.com).*?)"}, '<a\1rel="nofollow" href="\2"')
-      file.tap(&:rewind).write(new_content) if old_content != new_content
-    end
-  end
-
-  puts "\nBuild finished. The HTML pages are in #{File.expand_path("#{BUILD_DIR}/html")}."
-end
-
-task :clean do
-  sh "rm -rf #{BUILD_DIR}/*"
-end
-
-desc 'Make standalone HTML files'
-task :preview => [:clean, :build]
-
-desc 'Run the server on localhost:5001 and open a browser'
-task :server => :preview do
-  sh '(sleep 2 && open "http://localhost:5001")&'
-  sh 'bundle exec foreman start'
-end
-
-desc 'Commit and deploy changes to https://docs.talkable.com'
-task :deploy => :'deploy:production'
-
-namespace :deploy do
-  def deploy(domain:, html_branch:, source_branch:, disallow_robots:, push_command:)
-    sh "git checkout #{html_branch}"
-    sh 'git pull'
-    sh "find . -not -path './.git' -not -path './.git/*' -not -path './Rakefile' -not -path './.circleci' -not -path './.circleci/*' -delete"
-    sh "git checkout #{source_branch} #{SOURCE_DIR} .gitignore requirements.txt"
-    sh 'git reset HEAD'
-    Rake::Task[:build].invoke
-    sh "(cd #{BUILD_DIR}/html && tar c ./) | (cd ./ && tar xf -)"
-    sh "rm -rf #{BUILD_DIR} #{SOURCE_DIR} .buildinfo"
-    File.write('.nojekyll', '')
-    File.write('CNAME', domain)
-    File.write('robots.txt', "User-agent: *\nDisallow: /") if disallow_robots
-    sh 'git add -A'
-    sh "git commit -m \"Generated gh-pages for `git log #{source_branch} -1 --pretty=short --abbrev-commit`\" && #{push_command} ; git checkout #{source_branch}"
-
-    puts "\nDeployment finished. Check updated docs at https://#{domain}"
-  end
-
-  task :production do
-    deploy(
-      domain: 'docs.talkable.com',
-      html_branch: 'gh-pages',
-      source_branch: 'master',
-      disallow_robots: false,
-      push_command: 'git push origin gh-pages'
-    )
-  end
-
-  desc 'Commit and deploy changes to https://void-docs.talkable.com'
-  task :staging do
-    sh 'git remote show staging' do |ok, _|
-      Rake::Task[:setup].invoke unless ok
-    end
-
-    deploy(
-      domain: 'void-docs.talkable.com',
-      html_branch: 'void-gh-pages',
-      source_branch: 'void',
-      disallow_robots: true,
-      push_command: 'git push -f origin void-gh-pages && git push -f staging void-gh-pages:gh-pages'
-    )
-  end
-end
diff --git a/robots.txt b/robots.txt
deleted file mode 100644
index 60ed3d057..000000000
--- a/robots.txt
+++ /dev/null
@@ -1,3 +0,0 @@
-User-agent: *
-Disallow: 
-

From 191f97db8b17e347377964e796097d21999ed629 Mon Sep 17 00:00:00 2001
From: Vitalii Oliinyk <ilovepinkpony1@gmail.com>
Date: Thu, 23 Jan 2025 17:08:53 +0200
Subject: [PATCH 06/62] [PR-23724]: moved docs name hide to conf

---
 source/_static/talkable.css | 7 -------
 source/conf.py              | 1 +
 2 files changed, 1 insertion(+), 7 deletions(-)

diff --git a/source/_static/talkable.css b/source/_static/talkable.css
index ca2bb9c1e..963b18aa1 100644
--- a/source/_static/talkable.css
+++ b/source/_static/talkable.css
@@ -1,10 +1,3 @@
-/* @import url("basic.css"); */
-/* @import url(https://fonts.googleapis.com/css?family=Roboto:400,500,700,300,400italic); */
-
-.sidebar-brand-text {
-  display: none;
-}
-
 .sidebar-logo {
   margin: 0;
 }
diff --git a/source/conf.py b/source/conf.py
index 9ba32d7fc..827941e0a 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -139,6 +139,7 @@
 html_theme_options = {
     "light_logo": "img/logo.svg",
     "dark_logo": "img/logo.svg",
+    "sidebar_hide_name": True,
     "light_css_variables": {
         "color-brand-primary": "#D36835",
         "color-brand-content": "#D36835",

From c5dafe36cedc54d3a560b09689f15ff6ca1c0777 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Fri, 24 Jan 2025 10:39:56 +0300
Subject: [PATCH 07/62] move robots.txt to nginx level

---
 nginx/robots-local.txt      | 2 ++
 nginx/robots-production.txt | 4 ++++
 nginx/robots-staging.txt    | 2 ++
 source/robots.txt           | 3 ---
 4 files changed, 8 insertions(+), 3 deletions(-)
 create mode 100644 nginx/robots-local.txt
 create mode 100644 nginx/robots-production.txt
 create mode 100644 nginx/robots-staging.txt
 delete mode 100644 source/robots.txt

diff --git a/nginx/robots-local.txt b/nginx/robots-local.txt
new file mode 100644
index 000000000..77470cb39
--- /dev/null
+++ b/nginx/robots-local.txt
@@ -0,0 +1,2 @@
+User-agent: *
+Disallow: /
\ No newline at end of file
diff --git a/nginx/robots-production.txt b/nginx/robots-production.txt
new file mode 100644
index 000000000..0580d3269
--- /dev/null
+++ b/nginx/robots-production.txt
@@ -0,0 +1,4 @@
+User-agent: *
+Disallow:
+
+Sitemap: https://docs.talkable.com/sitemap.xml
\ No newline at end of file
diff --git a/nginx/robots-staging.txt b/nginx/robots-staging.txt
new file mode 100644
index 000000000..77470cb39
--- /dev/null
+++ b/nginx/robots-staging.txt
@@ -0,0 +1,2 @@
+User-agent: *
+Disallow: /
\ No newline at end of file
diff --git a/source/robots.txt b/source/robots.txt
deleted file mode 100644
index f3fc00670..000000000
--- a/source/robots.txt
+++ /dev/null
@@ -1,3 +0,0 @@
-User-agent: *
-
-Sitemap: https://docs.talkable.com/sitemap.xml

From 8baf0080488eeb90f9c261a955d761c97e8da8a6 Mon Sep 17 00:00:00 2001
From: Vitalii Oliinyk <ilovepinkpony1@gmail.com>
Date: Fri, 24 Jan 2025 19:21:09 +0200
Subject: [PATCH 08/62] [PR-23724]: updated campaign placements image tag

---
 source/partials/campaign_placements_description.rst | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/source/partials/campaign_placements_description.rst b/source/partials/campaign_placements_description.rst
index 3a79a4b16..54a902756 100644
--- a/source/partials/campaign_placements_description.rst
+++ b/source/partials/campaign_placements_description.rst
@@ -2,9 +2,7 @@ Campaign Placements are the places (pages) on your site where the Campaigns are
 
 The list of all Campaign Placements can be found by going to the All Site Settings page from the header Menu (top right corner) and choosing the Placements section:
 
-.. raw:: html
-
-  <img src="../_static/img/campaign_placements/path.png" />
+.. image:: /_static/img/campaign_placements/path.png
 
 Managing Placements
 -------------------

From a373777c2bfec0dec1534289cac679472eb3f4ac Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Fri, 24 Jan 2025 21:03:37 +0300
Subject: [PATCH 09/62] dockerized deployment introduction

---
 Dockerfile                                    |  26 +--
 README.md                                     | 188 ++++++++++++------
 docker-compose.yml                            |  34 ++++
 nginx/conf.d/default.conf                     |  25 +++
 .../development.txt}                          |   0
 .../production.txt}                           |   2 +-
 .../staging.txt}                              |   0
 requirements-dev.txt                          |   4 +-
 requirements.txt                              |  10 +-
 source/conf.py                                | 115 ++++++-----
 10 files changed, 260 insertions(+), 144 deletions(-)
 create mode 100644 nginx/conf.d/default.conf
 rename nginx/{robots-local.txt => robots/development.txt} (100%)
 rename nginx/{robots-production.txt => robots/production.txt} (85%)
 rename nginx/{robots-staging.txt => robots/staging.txt} (100%)

diff --git a/Dockerfile b/Dockerfile
index c11bb7d0e..70a1c498f 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,26 +1,6 @@
-# Use the official Python 3.13 Alpine image as the base
 FROM python:3.13-alpine3.21
 
-# Set environment variables to prevent Python from writing .pyc files
-ENV PYTHONDONTWRITEBYTECODE=1
-ENV PYTHONUNBUFFERED=1
-
-# Install system dependencies
-RUN apk add --no-cache \
-    build-base \
-    libffi-dev \
-    openssl-dev \
-    git
-
-# Install Sphinx and common dependencies
-RUN pip install --upgrade pip && \
-    pip install sphinx sphinx_rtd_theme myst_parser
-
-# Create and set the working directory
+# Install dependencies
 WORKDIR /docs
-
-# Copy documentation source files into the container
-COPY . /docs
-
-# Default command to build the Sphinx documentation
-CMD ["sphinx-build", "-b", "html", ".", "_build"]
\ No newline at end of file
+ADD requirements.txt /docs
+RUN python3 -m pip install -r requirements.txt
\ No newline at end of file
diff --git a/README.md b/README.md
index 6f23ceb9c..394178994 100644
--- a/README.md
+++ b/README.md
@@ -1,21 +1,134 @@
 Talkable Documentation
 ======================
 
-[![Build Status](https://circleci.com/gh/talkable/talkable-docs.svg?style=svg&circle-token=cc33458158e7b0c1f6f8cbf1bcbf74f00ee28a8e)](https://circleci.com/gh/talkable/workflows/talkable-docs)
+Overview
+--------
 
 This GitHub repository represents Talkable’s documentation site, located at [docs.talkable.com](https://docs.talkable.com).
 
 The Talkable documentation uses [reStructuredText](https://docutils.sourceforge.io/rst.html) as its markup language and is built using [Sphinx](https://www.sphinx-doc.org).
 
-Sphinx
-------
-
 For more details see [The Sphinx Documentation](https://www.sphinx-doc.org).
 
-reStructuredText
-----------------
+Concepts
+--------
+
+#### reStructuredText
+
+An easy-to-read, what-you-see-is-what-you-get plaintext markup syntax.
+All reStructuredText formatting capabilities can be found at [The reST Quickref](https://docutils.sourceforge.io/docs/user/rst/quickref.html).
+
+#### Documentation Builder
+
+Dockerized set of Sphinx and Nginx containers. Used to build the static pages from .rst and other format files into html static pages (Sphinx) and populate tyem in form of the documentation pages (Nginx) available to the user.
+
+#### Documentation Building Process
+
+The .rst files need to be buit to static html files. That doesn't require any involvement from developers since is handled by the [sphinx-autobuild](https://github.com/sphinx-doc/sphinx-autobuild) package included in to the Documentation Builder set mentoned above.
+
+#### Changes Deployment
+
+The local deployment doesn't require any efforts since available instantly after the files are changed on the local machine storage. The Builder buils teh changes just after indicated the change.
+The staging and producxtion deployment are handled by the corresponding Jenkins jobs just after the changes are pushed to the proper branch (staging or master) 
+
+Environments
+------------
+
+### Local
+
+Used to make teh local changes on developer's machine before pushing them to staging environment for testing by QA.
+Deployed in form of docker container on the developer's machine.
+Code managed in the dedicated github branch created from `master` branch.
+
+### Staging
+
+Used by QA team to test the documentation before pushing it to master branch/production environment.
+Deployed in dockerised AWS infrastructure.
+Code managed in `staging-bastion` branch.
+Available under the following url `url to be provided` 
+
+### Production
+
+The public version of the documentation available to the users.
+Deployed in dockerised AWS infrastructure.
+Code managed in `master` branch.
+Available under the following url `url to be provided` 
+
+Workflows
+---------
+
+### General Flow:
+
+1. Pull changes from master
+2. Checkout your new branch from master
+3. Deploy local Sphinx container
+4. Make changes, test your changes locally
+5. Commit the changes to staging branch
+6. Get the documentation tested by QA
+7. Create a Pull Request to "main" branch, providing the staging URL to the changed page in Pull Request’s description.
+8. Merge pull request once it passes the review
+
+### Builder Container Deployment
+
+0. Install Docker
+
+   Follow the [official Docker documentation](https://docs.docker.com/compose/install/)
+  
+
+1. Navigate to the repo root directory. 
+   
+   Make sure `docker-compose.yaml` file is located there.
+
+2. Create `.env` file and set the value of the port you want the documentation to be available on your local machine. Use `.env.example` file as a template.
+   
+    ```
+    NGINX_PORT=8080
+    ENVIRONMENT=local
+    ```
+
+    Set the port number to the value you want to use as a port number while browsing the documentation locally.
+    For teh example above you would use `http://localhost:8080`. Chose whichever free port.
+
+    Possible values for `ENVIRONMENT` variable:
+      - `local` for local development environment deployment
+      - `staging` for staging
+      - `production` for production 
+
+3. Run the local environment deployment
+
+    Run the command to deploy the Builder
 
-For more details see [The reST Quickref](https://docutils.sourceforge.io/docs/user/rst/quickref.html).
+    ```
+    docker-compose up -d
+    ```
+
+4. Check the successfull deployment
+
+    Try follow the link [http://localhost:8080](http://localhost:8080)
+    Make sure you use the port number define din `.env` file
+    If you've done everything right the documentation will open.
+    If it doesn't check teh Troubleshooting section
+
+Troubleshooting
+---------------
+
+#### Can't view the documentation locally in browser
+
+1. Make sure you use correct post number and protocol.
+    The port number should equal the number you've provided in `.env` as `NGINX_PORT` value
+
+2. Check `nginx` logs:
+    ```shell
+    docker logs -f nginx
+    ```
+
+3. Check `Sphinx` logs
+    ```shell
+    dcoker logs -f sphinx
+    ```
+
+Formatting examples
+-------------------
 
 ### Sections
 
@@ -57,65 +170,12 @@ Here is a reference to "talkable section": :ref:`talkable-section` which will ha
 name "Talkable Section".
 ```
 
-Build the documentation
------------------------
-
-First install [Sphinx](https://www.sphinx-doc.org). See below.
-
-### Installing Sphinx on macOS
-
-* Install [Homebrew](https://brew.sh).
-
-* Install Ruby and [Bundler](https://bundler.io), and run `bundle install` to install dependencies.
-
-* Install Python (>= 3.9) and pip:
-
-  ```
-  brew install python
-  ```
-
-  More information in case of trouble: https://docs.brew.sh/Homebrew-and-Python
-
-* Install dependencies:
-
-  ```
-  pip3 install -r requirements.txt --break-system-package
-  ```
-
-  If you have problems, try adding `-I` flag (`--ignore-installed`) to the `pip install` command.
-
-If you get the error "unknown locale: UTF-8" when generating the documentation,
-the solution is to define the following environment variables:
-
-    export LANG=en_US.UTF-8
-    export LC_ALL=en_US.UTF-8
-
-### Building
-
-Run `rake preview` from "master" branch.
-
-#### Setting up LiveReload
-
-Run `rake server` from "master" branch and open `http://localhost:5000` in browser.
-
-### Deploying
-
-If you’re deploying for the first time make sure you have `gh-pages` branch locally. Otherwise run the following command to create it: `git checkout -b gh-pages origin/gh-pages`.
-
-General flow:
-1. Pull changes from master
-2. Checkout your new branch from master
-3. Make changes
-4. Deploy your changes to staging (see the instruction below)
-4. Create a Pull Request to "master" branch, providing the demo URL to the changed page in Pull Request’s description.
-5. Merge pull request once it passes the review
-6. Deploy
 
-If you did everything right, deploying is as easy as `rake deploy` from "master" branch.
+Deployment
+----------
 
-#### Deploying to Staging
+#### Local Enviro
 
-If it’s your first time deploying to staging, run `rake setup` to setup git remote.
 
 1. Switch to local branch "void" and pull the latest changes from the remote:
   `git checkout void; git pull`
@@ -123,8 +183,6 @@ If it’s your first time deploying to staging, run `rake setup` to setup git re
   `git merge YOUR_BRANCH_NAME`
 3. Push the changes to the remote branch "void":
   ```git push origin void```
-4. Deploy:
-  ```rake deploy:staging```
 
 ---
 
diff --git a/docker-compose.yml b/docker-compose.yml
index e69de29bb..eedfc3839 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -0,0 +1,34 @@
+services:
+
+  sphinx:
+    build:
+      context: .
+      dockerfile: Dockerfile
+    container_name: sphinx
+    volumes:
+      - ./source:/docs/source
+    environment:
+      - ENVIRONMENT=${ENVIRONMENT}
+      - NGINX_PORT=${NGINX_PORT}
+    command: sphinx-autobuild -b dirhtml --host 0.0.0.0 /docs/source /docs/_build
+    networks:
+      - docs_net
+    
+  nginx:
+    image: nginx:1.27.3-alpine3.20
+    container_name: nginx
+    volumes:
+      - ./nginx/conf.d:/etc/nginx/conf.d
+    networks:
+      - docs_net
+    ports:
+      - ${NGINX_PORT}:80
+    depends_on:
+      - sphinx
+
+networks:
+  docs_net:
+    name: docs_net
+    driver: bridge
+
+
diff --git a/nginx/conf.d/default.conf b/nginx/conf.d/default.conf
new file mode 100644
index 000000000..2ab66a10c
--- /dev/null
+++ b/nginx/conf.d/default.conf
@@ -0,0 +1,25 @@
+server {
+    listen 80;
+    server_name _;
+
+    # root /var/www/html;
+    # index index.html;
+
+    # Redirect URLs ending with /path/index.html to /path/
+    location ~* ^(.*/)?index\.html$ {
+        return 301 $scheme://$http_host$1;
+    }
+
+    # Redirect all other .html URLs to corresponding directory
+    location ~* ^(.+)\.html$ {
+        return 301 $scheme://$http_host$1/;
+    }
+
+    location / {
+        proxy_pass http://sphinx:8000;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+    }
+}
\ No newline at end of file
diff --git a/nginx/robots-local.txt b/nginx/robots/development.txt
similarity index 100%
rename from nginx/robots-local.txt
rename to nginx/robots/development.txt
diff --git a/nginx/robots-production.txt b/nginx/robots/production.txt
similarity index 85%
rename from nginx/robots-production.txt
rename to nginx/robots/production.txt
index 0580d3269..85f681f30 100644
--- a/nginx/robots-production.txt
+++ b/nginx/robots/production.txt
@@ -1,4 +1,4 @@
 User-agent: *
-Disallow:
+Allow: /
 
 Sitemap: https://docs.talkable.com/sitemap.xml
\ No newline at end of file
diff --git a/nginx/robots-staging.txt b/nginx/robots/staging.txt
similarity index 100%
rename from nginx/robots-staging.txt
rename to nginx/robots/staging.txt
diff --git a/requirements-dev.txt b/requirements-dev.txt
index 7315bc22c..83c514c9d 100644
--- a/requirements-dev.txt
+++ b/requirements-dev.txt
@@ -1,5 +1,5 @@
 furo
 sphinx-copybutton
-# sphinx
 sphinx-sitemap
-sphinx-autobuild
\ No newline at end of file
+sphinx-autobuild
+sphinx-favicon
\ No newline at end of file
diff --git a/requirements.txt b/requirements.txt
index 3c134f214..e358dfdf7 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,7 +1,5 @@
-furo
-sphinx-copybutton
-Sphinx==8.1.3
+furo==2024.8.6
+sphinx-copybutton==0.5.2
 sphinx-sitemap==2.6.0
-
-
-sphinx-autobuild
\ No newline at end of file
+sphinx-autobuild==2024.10.3
+sphinx-favicon==1.0.1
\ No newline at end of file
diff --git a/source/conf.py b/source/conf.py
index 9ba32d7fc..91d996d65 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -13,87 +13,105 @@
 # serve to show the default.
 
 # import sys
-# import os
+import os
+
+environment = os.getenv("ENVIRONMENT", "production")
+nginx_port = os.getenv("NGINX_PORT", "")
+
+
+def get_baseurl(environment) -> str:
+    if environment == "development":
+        return f"http://localhost:{nginx_port}/"
+    elif environment == "staging":
+        return "https://void-docs.talkable.com/"
+    else:
+        return "https://docs.talkable.com/"
+
 
 # If extensions (or modules to document with autodoc) are in another directory,
 # add these directories to sys.path here. If the directory is relative to the
 # documentation root, use os.path.abspath to make it absolute, like shown here.
-#sys.path.insert(0, os.path.abspath('.'))
+# sys.path.insert(0, os.path.abspath('.'))
 
 # -- General configuration ------------------------------------------------
 
 # If your documentation needs a minimal Sphinx version, state it here.
-#needs_sphinx = '1.0'
+# needs_sphinx = '1.0'
 
 # Add any Sphinx extension module names here, as strings. They can be
 # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
 # ones.
-extensions = ['sphinx_sitemap', 'sphinx_copybutton']
+extensions = [
+    "sphinx_sitemap",
+    "sphinx_copybutton",
+    "sphinx_favicon",
+]
+
 sitemap_url_scheme = "{link}"
 
 # Add any paths that contain templates here, relative to this directory.
-templates_path = ['_templates']
+templates_path = ["_templates"]
 
 # The suffix of source filenames.
-source_suffix = '.rst'
+source_suffix = ".rst"
 
 # The encoding of source files.
-#source_encoding = 'utf-8-sig'
+# source_encoding = 'utf-8-sig'
 
 # The master toctree document.
-master_doc = 'index'
+master_doc = "index"
 
 # General information about the project.
-project = u'Talkable'
-copyright = u'Talkable Inc.'
-author = u'Talkable Inc.'
+project = "Talkable"
+copyright = "Talkable Inc."
+author = "Talkable Inc."
 
 # The version info for the project you’re documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
 # The short X.Y version.
-version = u'1.0'
+version = "1.0"
 # The full version, including alpha/beta/rc tags.
-release = u'1.0'
+release = "1.0"
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
-#language = None
+# language = None
 
 # There are two options for replacing |today|: either, you set today to some
 # non-false value, then it is used:
-#today = ''
+# today = ''
 # Else, today_fmt is used as the format for a strftime call.
-#today_fmt = '%B %d, %Y'
+# today_fmt = '%B %d, %Y'
 
 # List of patterns, relative to source directory, that match files and
 # directories to ignore when looking for source files.
-exclude_patterns = ['_build', 'partials', 'samples', '.DS_Store']
+exclude_patterns = ["_build", "partials", "samples", ".DS_Store"]
 
 # The reST default role (used for this markup: `text`) to use for all
 # documents.
-#default_role = None
+# default_role = None
 
 # If true, '()' will be appended to :func: etc. cross-reference text.
-#add_function_parentheses = True
+# add_function_parentheses = True
 
 # If true, the current module name will be prepended to all description
 # unit titles (such as .. function::).
-#add_module_names = True
+# add_module_names = True
 
 # If true, sectionauthor and moduleauthor directives will be shown in the
 # output. They are ignored by default.
-#show_authors = False
+# show_authors = False
 
 # The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
+pygments_style = "sphinx"
 
 # A list of ignored prefixes for module index sorting.
-#modindex_common_prefix = []
+# modindex_common_prefix = []
 
 # If true, keep warnings as "system message" paragraphs in the built documents.
-#keep_warnings = False
+# keep_warnings = False
 
 
 # -- Options for HTML output ----------------------------------------------
@@ -111,30 +129,36 @@
 html_show_sourcelink = False
 
 # Add any paths that contain custom themes here, relative to this directory.
-#html_theme_path = []
+# html_theme_path = []
 
 # The name for this set of Sphinx documents.  If None, it defaults to
 # "<project> v<release> documentation".
-html_title = u''
+html_title = ""
 
 # A shorter title for the navigation bar.  Default is the same as html_title.
-#html_short_title = None
+# html_short_title = None
 
 # The name of an image file (relative to this directory) to place at the top
 # of the sidebar.
-#html_logo = None
+# html_logo = None
 
 # The name of an image file (within the static path) to use as favicon of the
 # docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
 # pixels large.
-#html_favicon = None
+# html_favicon = None
+
+favicons = {
+    "rel": "icon",
+    "href": "img/favicon.ico",
+    "type": "image/vnd.microsoft.icon",
+}
 
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ['_static']
+html_static_path = ["_static"]
 html_css_files = [
-    'talkable.css',
+    "talkable.css",
 ]
 html_theme_options = {
     "light_logo": "img/logo.svg",
@@ -149,7 +173,7 @@
 # Add any extra paths that contain custom files (such as robots.txt or
 # .htaccess) here, relative to this directory. These files are copied
 # directly to the root of the documentation.
-html_extra_path = ['robots.txt']
+html_extra_path = ["robots.txt"]
 
 # If not None, a 'Last updated on:' timestamp is inserted at every page bottom,
 # using the given strftime format.
@@ -158,26 +182,26 @@
 
 # If true, SmartyPants will be used to convert quotes and dashes to
 # typographically correct entities.
-#html_use_smartypants = True
+# html_use_smartypants = True
 
 # Custom sidebar templates, maps document names to template names.
-#html_sidebars = {}
+# html_sidebars = {}
 
 # Additional templates that should be rendered to pages, maps page names to
 # template names.
-#html_additional_pages = {}
+# html_additional_pages = {}
 
 # If false, no module index is generated.
-#html_domain_indices = True
+# html_domain_indices = True
 
 # If false, no index is generated.
 html_use_index = False
 
 # If true, the index is split into individual pages for each letter.
-#html_split_index = False
+# html_split_index = False
 
 # If true, links to the reST sources are added to the pages.
-#html_show_sourcelink = True
+# html_show_sourcelink = True
 
 # If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
 html_show_sphinx = False
@@ -188,26 +212,23 @@
 # If true, an OpenSearch description file will be output, and all pages will
 # contain a <link> tag referring to it.  The value of this option must be the
 # base URL from which the finished HTML is served.
-#html_use_opensearch = ''
+# html_use_opensearch = ''
 
 # This is the file name suffix for HTML files (e.g. ".xhtml").
-#html_file_suffix = None
+# html_file_suffix = None
 
 # Output file base name for HTML help builder.
-htmlhelp_basename = 'Talkabledoc'
+htmlhelp_basename = "Talkabledoc"
 
 # The URL which points to the root of the HTML documentation.
 # It is used to indicate the location of document like canonical_url.
-html_baseurl = 'https://docs.talkable.com/'
+html_baseurl = get_baseurl(environment)
 
 # -- Options for manual page output ---------------------------------------
 
 # One entry per manual page. List of tuples
 # (source start file, name, description, authors, manual section).
-man_pages = [
-    (master_doc, 'talkable', u'Talkable Documentation',
-     [author], 1)
-]
+man_pages = [(master_doc, "talkable", "Talkable Documentation", [author], 1)]
 
 # If true, show URL addresses after external links.
-#man_show_urls = False
+# man_show_urls = False

From ad0d42a7deb7386d4e0671f13360ffc8089f9a23 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Sat, 25 Jan 2025 19:39:30 +0300
Subject: [PATCH 10/62] refactoring + documentation completion

---
 .env.template             |  10 +++
 .gitignore                |   3 +-
 README-devops.md          |  78 +++++++++++++++++
 README.md                 | 171 ++++++++++++++------------------------
 docker-compose.yml        |  25 +++---
 nginx/conf.d/default.conf |  41 ++++++---
 nginx/robots/staging.txt  |   4 +-
 source/_utils/__init__.py |   1 +
 source/_utils/baseurl.py  |  15 ++++
 source/conf.py            |  24 ++----
 10 files changed, 218 insertions(+), 154 deletions(-)
 create mode 100644 .env.template
 create mode 100644 README-devops.md
 create mode 100644 source/_utils/__init__.py
 create mode 100644 source/_utils/baseurl.py

diff --git a/.env.template b/.env.template
new file mode 100644
index 000000000..161f4b646
--- /dev/null
+++ b/.env.template
@@ -0,0 +1,10 @@
+# The port to use to populate the documentation on your local machine or server
+LOCAL_PORT=8080
+
+# Possible values: development, staging, production
+ENVIRONMENT=development
+
+# Base urls used for the canonical urls compilation
+DEVELOPMENT_HOST=localhost
+STAGING_HOST=bastion-docs.talkable.com
+PRODUCTION_HOST=docs.talkable.com
\ No newline at end of file
diff --git a/.gitignore b/.gitignore
index e0b54580d..e1d1a7ce4 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,4 +4,5 @@
 .env
 .venv
 
-_build
\ No newline at end of file
+_build
+__pycache__
\ No newline at end of file
diff --git a/README-devops.md b/README-devops.md
new file mode 100644
index 000000000..0dc56da33
--- /dev/null
+++ b/README-devops.md
@@ -0,0 +1,78 @@
+## Overview
+
+The Talkable documentation stack is a containerized system that uses Docker to simplify deployment and management. It is designed to generate, serve, and manage static documentation across multiple environments, such as staging and production.
+
+## Key Features
+
+1. **Containerized Components**:
+   - **Nginx**: Handles HTTP requests, serves static HTML files, manages URL redirection, and dynamically serves environment-specific `robots.txt` files.
+   - **Sphinx Autobuilder**: Generates static HTML files from source documentation and stores them in a persistent volume shared with Nginx.
+
+2. **Environment-Specific Behavior**:
+   - Configured via a `.env` file for flexibility.
+   - Supports dynamic environment-specific behavior, such as serving different `robots.txt` files based on the `ENVIRONMENT` variable.
+
+3. **Efficient Architecture**:
+   - Deployed on Amazon AWS Virtual Private Servers (VPS) with an AWS load balancer directing user traffic to the appropriate environment.
+   - Sphinx generates content on a persistent volume that Nginx serves directly.
+
+## Deployment Process
+
+### Prerequisites
+
+- Ensure Docker and Docker Compose are installed on the target VPS.
+- Clone the repository containing the stack configuration.
+
+### Steps
+
+1. **Clone the Repository**:
+   ```bash
+   git clone https://github.com/talkable/talkable-docs.git
+   ```
+
+2. **Switch to the Appropriate Branch**:
+   - Use the `master` branch for production.
+   ```bash
+   git checkout master
+   ```
+   - Use the `staging-bastion` branch for staging.
+   ```bash
+   git checkout staging-bastion
+   ```
+
+3. **Create and Configure the `.env` File**:
+   - Copy `.env.template` to `.env`:
+     ```bash
+     cp .env.template .env
+     ```
+   - Update the following variables:
+     - **`ENVIRONMENT`**: Set to `development`, `staging`, or `production`.
+     - **`LOCAL_PORT`**: Adjust if the default port (`8080`) is already in use.
+     - Leave `_HOST` variables unchanged unless domain names for staging or production servers are updated.
+
+4. **Deploy the Stack**:
+   ```bash
+   docker-compose up -d
+   ```
+
+## Environment-Specific Configuration
+
+### Handling `robots.txt`
+
+- The repository includes separate `robots.txt` files for each environment.
+- The correct file is dynamically selected based on the `ENVIRONMENT` variable and mapped to the container:
+  ```yaml
+  volumes:
+    - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
+  ```
+- Nginx serves the file at `/var/www/robots.txt` in response to `robots.txt` requests.
+
+## Persistent Data Sharing
+
+- **Static HTML Files**:
+  - Generated by Sphinx and stored in a shared volume.
+  - Served by Nginx without regeneration.
+
+- **Volume Management**:
+  - Shared volumes allow seamless access and updates between containers.
+  - Ensures efficient and consistent behavior across environments.
diff --git a/README.md b/README.md
index 147387d89..45ea5cb41 100644
--- a/README.md
+++ b/README.md
@@ -1,128 +1,74 @@
-# Talkable Documentation
+## What is Talkable Documentation?
 
-## Overview
+The set of articles describing Talkable's capabilities, publicly available at [docs.talkable.com](https://docs.talkable.com).
 
-This GitHub repository represents Talkable’s documentation site, located at [docs.talkable.com](https://docs.talkable.com).
+It uses [reStructuredText](https://docutils.sourceforge.io/rst.html) as its markup language, an easy-to-read, what-you-see-is-what-you-get plaintext markup syntax. All reStructuredText formatting capabilities can be found in [The reST Quickref](https://docutils.sourceforge.io/docs/user/rst/quickref.html).
 
-The Talkable documentation uses [reStructuredText](https://docutils.sourceforge.io/rst.html) as its markup language and is built using [Sphinx](https://www.sphinx-doc.org).
+It is built using [Sphinx](https://www.sphinx-doc.org), an open-source documentation generation tool that transforms plain text files into beautifully formatted documentation. For more details, see [The Sphinx Documentation](https://www.sphinx-doc.org).
 
-For more details see [The Sphinx Documentation](https://www.sphinx-doc.org).
+## Where is it stored?
 
-## Concepts
+It's stored in a dedicated GitHub repository ([talkable-docs](https://github.com/talkable/talkable-docs)).
 
-#### reStructuredText
+The repository consists of the following branches:
+- [master](https://github.com/talkable/talkable-docs/tree/master): The main branch used to keep the most recent stable version available at [docs.talkable.com](https://docs.talkable.com).
+- [staging-bastion](https://github.com/talkable/talkable-docs/tree/staging-bastion): A staging branch used for testing by QA. It is available at [bastion-docs.talkable.com](https://bastion-docs.talkable.com).
+- Feature branches created from `master` by individual contributors/developers.
 
-An easy-to-read, what-you-see-is-what-you-get plaintext markup syntax.
-All reStructuredText formatting capabilities can be found at [The reST Quickref](https://docutils.sourceforge.io/docs/user/rst/quickref.html).
+## What is the documentation update workflow?
 
-#### Documentation Builder
+1. Pull changes from `master`.
+2. Checkout a new branch from `master`.
+3. Deploy the local/development environment.
+4. Make changes and test them locally.
+5. Commit the changes to the `staging` branch.
+6. Get the documentation tested by QA.
+7. Create a pull request to the `master` branch, providing the staging URL of the changed page in the pull request description.
+8. Merge the pull request once it passes the review.
 
-Dockerized set of Sphinx and Nginx containers. Used to build the static pages from .rst and other format files into html static pages (Sphinx) and populate tyem in form of the documentation pages (Nginx) available to the user.
+## How to deploy the local environment?
 
-#### Documentation Building Process
+0. **Install Docker**
 
-The .rst files need to be buit to static html files. That doesn't require any involvement from developers since is handled by the [sphinx-autobuild](https://github.com/sphinx-doc/sphinx-autobuild) package included in to the Documentation Builder set mentoned above.
+   Follow the [official Docker documentation](https://docs.docker.com/compose/install/).
 
-#### Changes Deployment
+1. **Navigate to the repository root directory.**
 
-The local deployment doesn't require any efforts since available instantly after the files are changed on the local machine storage. The Builder buils teh changes just after indicated the change.
-The staging and producxtion deployment are handled by the corresponding Jenkins jobs just after the changes are pushed to the proper branch (staging or master)
+   Ensure the `docker-compose.yaml` file is located there.
 
-## Environments
+2. **Create an `.env` file by copying `.env.template`.**
+   
+   Review and update the variable values if needed.
+   
+   For a **development/local environment**, all default settings should work out of the box. The only value you may need to change is `LOCAL_PORT` if `8080` is already in use on your local machine.
 
-### Local
+3. **Run the local environment deployment.**
 
-Used to make teh local changes on developer's machine before pushing them to staging environment for testing by QA.
-Deployed in form of docker container on the developer's machine.
-Code managed in the dedicated github branch created from `master` branch.
+   Run the command:
 
-### Staging
-
-Used by QA team to test the documentation before pushing it to master branch/production environment.
-Deployed in dockerised AWS infrastructure.
-Code managed in `staging-bastion` branch.
-Available under the following url `url to be provided`
-
-### Production
-
-The public version of the documentation available to the users.
-Deployed in dockerised AWS infrastructure.
-Code managed in `master` branch.
-Available under the following url `url to be provided`
-
-## Workflows
-
-### General Flow:
-
-1. Pull changes from master
-2. Checkout your new branch from master
-3. Deploy local Sphinx container
-4. Make changes, test your changes locally
-5. Commit the changes to staging branch
-6. Get the documentation tested by QA
-7. Create a Pull Request to "main" branch, providing the staging URL to the changed page in Pull Request’s description.
-8. Merge pull request once it passes the review
-
-### Builder Container Deployment
-
-0. Install Docker
-
-   Follow the [official Docker documentation](https://docs.docker.com/compose/install/)
-
-1. Navigate to the repo root directory.
-
-   Make sure `docker-compose.yaml` file is located there.
-
-2. Create `.env` file and set the value of the port you want the documentation to be available on your local machine. Use `.env.example` file as a template.
-
-   ```
-   NGINX_PORT=8080
-   ENVIRONMENT=local
-   ```
-
-   Set the port number to the value you want to use as a port number while browsing the documentation locally.
-   For teh example above you would use `http://localhost:8080`. Chose whichever free port.
-
-   Possible values for `ENVIRONMENT` variable:
-
-   - `local` for local development environment deployment
-   - `staging` for staging
-   - `production` for production
-
-3. Run the local environment deployment
-
-   Run the command to deploy the Builder
-
-   ```
+   ```bash
    docker-compose up -d
    ```
 
-4. Check the successfull deployment
+   If everything is set up correctly, the documentation will be available at [http://localhost:8080](http://localhost:8080). Make sure you use the port number defined in the `.env` file.
 
-   Try follow the link [http://localhost:8080](http://localhost:8080)
-   Make sure you use the port number define din `.env` file
-   If you've done everything right the documentation will open.
-   If it doesn't check teh Troubleshooting section
+   If the documentation does not load, check the **Troubleshooting** section.
 
-## Troubleshooting
+## How to deploy changes to production and staging?
 
-#### Can't view the documentation locally in browser
+You should not deploy it manually!
 
-1. Make sure you use correct post number and protocol.
-   The port number should equal the number you've provided in `.env` as `NGINX_PORT` value
+The deployment is handled by Jenkins jobs. 
 
-2. Check `nginx` logs:
+All you need to do is commit your changes to the corresponding branch to deploy them to the appropriate server:
+- Commit to the [staging-bastion](https://github.com/talkable/talkable-docs/tree/staging-bastion) branch => [bastion-docs.talkable.com](https://bastion-docs.talkable.com/).
+- Commit to the [master](https://github.com/talkable/talkable-docs/tree/master) branch => [docs.talkable.com](https://docs.talkable.com/).
 
-   ```shell
-   docker logs -f nginx
-   ```
+## How do I make the actual changes?
 
-3. Check `Sphinx` logs
-   ```shell
-   dcoker logs -f sphinx
-   ```
+Navigate to the [source](./source/) directory and update the files using `reStructuredText` syntax. Refer to [The reST Quickref](https://docutils.sourceforge.io/docs/user/rst/quickref.html) for syntax details.
 
-## Formatting examples
+Here are some formatting examples:
 
 ### Sections
 
@@ -164,21 +110,28 @@ Here is a reference to "talkable section": :ref:`talkable-section` which will ha
 name "Talkable Section".
 ```
 
-## Deployment
+## Troubleshooting
+
+#### Can't view the documentation locally in the browser?
+
+1. Ensure you are using the correct port number and protocol.
+   The port number should match the value provided in `.env` as `LOCAL_PORT`.
 
-#### Local Enviro
+2. Check `nginx` logs:
 
-1. Switch to local branch "void" and pull the latest changes from the remote:
-   `git checkout void; git pull`
-2. Merge your branch into local branch "void":
-   `git merge YOUR_BRANCH_NAME`
-3. Push the changes to the remote branch "void":
-   `git push origin void`
+   ```bash
+   docker logs -f nginx
+   ```
 
----
+3. Check `Sphinx` logs:
 
-See "master" branch: https://github.com/talkable/talkable-docs
+   ```bash
+   docker logs -f sphinx
+   ```
 
-See "gh-pages" branch: https://github.com/talkable/talkable-docs/tree/gh-pages
+## Links
 
-See GitHub Page (auto generated): https://docs.talkable.com
+- GitHub "staging" branch: [staging-bastion](https://github.com/talkable/talkable-docs/tree/staging-bastion)
+- Staging web server: [bastion-docs.talkable.com](https://bastion-docs.talkable.com/)
+- GitHub "production" branch: [master](https://github.com/talkable/talkable-docs/tree/master)
+- Production web server: [docs.talkable.com](https://docs.talkable.com/)
\ No newline at end of file
diff --git a/docker-compose.yml b/docker-compose.yml
index eedfc3839..bbf7b1bc5 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -7,28 +7,27 @@ services:
     container_name: sphinx
     volumes:
       - ./source:/docs/source
+      - docs_build:/docs/_build
     environment:
       - ENVIRONMENT=${ENVIRONMENT}
-      - NGINX_PORT=${NGINX_PORT}
-    command: sphinx-autobuild -b dirhtml --host 0.0.0.0 /docs/source /docs/_build
-    networks:
-      - docs_net
+      - LOCAL_PORT=${LOCAL_PORT}
+      - PRODUCTION_HOST=${PRODUCTION_HOST}
+      - STAGING_HOST=${STAGING_HOST}
+      - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
+    command: sphinx-autobuild -b dirhtml /docs/source /docs/_build
     
   nginx:
     image: nginx:1.27.3-alpine3.20
     container_name: nginx
     volumes:
+      - docs_build:/var/www/html
       - ./nginx/conf.d:/etc/nginx/conf.d
-    networks:
-      - docs_net
+      - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
     ports:
-      - ${NGINX_PORT}:80
+      - ${LOCAL_PORT}:80
     depends_on:
       - sphinx
 
-networks:
-  docs_net:
-    name: docs_net
-    driver: bridge
-
-
+volumes:
+  docs_build:
+    driver: local
diff --git a/nginx/conf.d/default.conf b/nginx/conf.d/default.conf
index 2ab66a10c..9e41dbfca 100644
--- a/nginx/conf.d/default.conf
+++ b/nginx/conf.d/default.conf
@@ -2,24 +2,39 @@ server {
     listen 80;
     server_name _;
 
-    # root /var/www/html;
-    # index index.html;
+    root /var/www/html;
+    index index.html;
 
-    # Redirect URLs ending with /path/index.html to /path/
-    location ~* ^(.*/)?index\.html$ {
-        return 301 $scheme://$http_host$1;
+    # Helps preserve the port in redirects when not on :80/:443
+    absolute_redirect off;
+    port_in_redirect on;
+
+    # Single location to catch ANY URL ending in .html
+    location ~* ^/.+\.html$ {
+        # Avoid redirect loops if this is an internal sub-request (fallback)
+        if ($uri != $request_uri) {
+            break;
+        }
+
+        # 1) If it ends with "index.html", remove "index.html"
+        #    e.g. /path/index.html => /path/
+        #    e.g. /index.html => /
+        rewrite "^/(.*)index\.html$" /$1 permanent;
+
+        # 2) Otherwise remove ".html" and append slash
+        #    e.g. /overview.html => /overview/
+        rewrite "^/(.+)\.html$" /$1/ permanent;
     }
 
-    # Redirect all other .html URLs to corresponding directory
-    location ~* ^(.+)\.html$ {
-        return 301 $scheme://$http_host$1/;
+    # Serve robots.txt from a specific file
+    location = /robots.txt {
+        alias /var/www/robots.txt;
+        access_log off;
+        log_not_found off;
     }
 
+    # Default static-file behavior
     location / {
-        proxy_pass http://sphinx:8000;
-        proxy_set_header Host $host;
-        proxy_set_header X-Real-IP $remote_addr;
-        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-        proxy_set_header X-Forwarded-Proto $scheme;
+        try_files $uri $uri/ =404;
     }
 }
\ No newline at end of file
diff --git a/nginx/robots/staging.txt b/nginx/robots/staging.txt
index 77470cb39..e3c680508 100644
--- a/nginx/robots/staging.txt
+++ b/nginx/robots/staging.txt
@@ -1,2 +1,4 @@
 User-agent: *
-Disallow: /
\ No newline at end of file
+Disallow: /
+
+Sitemap: https://bastion-docs.talkable.com/sitemap.xml
\ No newline at end of file
diff --git a/source/_utils/__init__.py b/source/_utils/__init__.py
new file mode 100644
index 000000000..5712dd70e
--- /dev/null
+++ b/source/_utils/__init__.py
@@ -0,0 +1 @@
+from .baseurl import baseurl
diff --git a/source/_utils/baseurl.py b/source/_utils/baseurl.py
new file mode 100644
index 000000000..d15df347d
--- /dev/null
+++ b/source/_utils/baseurl.py
@@ -0,0 +1,15 @@
+import os
+
+local_port = os.getenv("LOCAL_PORT")
+environment = os.getenv("ENVIRONMENT")
+production_host = os.getenv("PRODUCTION_HOST")
+staging_host = os.getenv("STAGING_HOST")
+development_host = os.getenv("DEVELOPMENT_HOST")
+
+baseurl_json = {
+    "development": f"http://{development_host}:{local_port}/",
+    "staging": f"https://{staging_host}/",
+    "production": f"https://{production_host}/",
+}
+
+baseurl = baseurl_json.get(environment)
diff --git a/source/conf.py b/source/conf.py
index b76ffba3d..296acbe88 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -12,26 +12,16 @@
 # All configuration values have a default; values that are commented out
 # serve to show the default.
 
-# import sys
+import sys
 import os
 
-environment = os.getenv("ENVIRONMENT", "production")
-nginx_port = os.getenv("NGINX_PORT", "")
-
-
-def get_baseurl(environment) -> str:
-    if environment == "development":
-        return f"http://localhost:{nginx_port}/"
-    elif environment == "staging":
-        return "https://void-docs.talkable.com/"
-    else:
-        return "https://docs.talkable.com/"
-
-
 # If extensions (or modules to document with autodoc) are in another directory,
 # add these directories to sys.path here. If the directory is relative to the
 # documentation root, use os.path.abspath to make it absolute, like shown here.
-# sys.path.insert(0, os.path.abspath('.'))
+sys.path.insert(0, os.path.abspath("."))
+
+# Import Talkable custom code
+from _utils import baseurl
 
 # -- General configuration ------------------------------------------------
 
@@ -174,7 +164,7 @@ def get_baseurl(environment) -> str:
 # Add any extra paths that contain custom files (such as robots.txt or
 # .htaccess) here, relative to this directory. These files are copied
 # directly to the root of the documentation.
-html_extra_path = ["robots.txt"]
+# html_extra_path = ["robots.txt"]
 
 # If not None, a 'Last updated on:' timestamp is inserted at every page bottom,
 # using the given strftime format.
@@ -223,7 +213,7 @@ def get_baseurl(environment) -> str:
 
 # The URL which points to the root of the HTML documentation.
 # It is used to indicate the location of document like canonical_url.
-html_baseurl = get_baseurl(environment)
+html_baseurl = baseurl
 
 # -- Options for manual page output ---------------------------------------
 

From eb557d05ff2374cd247f839bf3888394b6162477 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Sat, 25 Jan 2025 20:20:16 +0300
Subject: [PATCH 11/62] doc refactoring

---
 README-devops.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/README-devops.md b/README-devops.md
index 0dc56da33..8268d3d6e 100644
--- a/README-devops.md
+++ b/README-devops.md
@@ -5,14 +5,17 @@ The Talkable documentation stack is a containerized system that uses Docker to s
 ## Key Features
 
 1. **Containerized Components**:
+   
    - **Nginx**: Handles HTTP requests, serves static HTML files, manages URL redirection, and dynamically serves environment-specific `robots.txt` files.
    - **Sphinx Autobuilder**: Generates static HTML files from source documentation and stores them in a persistent volume shared with Nginx.
 
 2. **Environment-Specific Behavior**:
+   
    - Configured via a `.env` file for flexibility.
    - Supports dynamic environment-specific behavior, such as serving different `robots.txt` files based on the `ENVIRONMENT` variable.
 
 3. **Efficient Architecture**:
+   
    - Deployed on Amazon AWS Virtual Private Servers (VPS) with an AWS load balancer directing user traffic to the appropriate environment.
    - Sphinx generates content on a persistent volume that Nginx serves directly.
 
@@ -26,22 +29,29 @@ The Talkable documentation stack is a containerized system that uses Docker to s
 ### Steps
 
 1. **Clone the Repository**:
+   
    ```bash
    git clone https://github.com/talkable/talkable-docs.git
    ```
 
 2. **Switch to the Appropriate Branch**:
+   
    - Use the `master` branch for production.
+   
    ```bash
    git checkout master
    ```
+   
    - Use the `staging-bastion` branch for staging.
+   
    ```bash
    git checkout staging-bastion
    ```
 
 3. **Create and Configure the `.env` File**:
+   
    - Copy `.env.template` to `.env`:
+   
      ```bash
      cp .env.template .env
      ```
@@ -51,6 +61,7 @@ The Talkable documentation stack is a containerized system that uses Docker to s
      - Leave `_HOST` variables unchanged unless domain names for staging or production servers are updated.
 
 4. **Deploy the Stack**:
+   
    ```bash
    docker-compose up -d
    ```
@@ -61,10 +72,12 @@ The Talkable documentation stack is a containerized system that uses Docker to s
 
 - The repository includes separate `robots.txt` files for each environment.
 - The correct file is dynamically selected based on the `ENVIRONMENT` variable and mapped to the container:
+  
   ```yaml
   volumes:
     - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
   ```
+
 - Nginx serves the file at `/var/www/robots.txt` in response to `robots.txt` requests.
 
 ## Persistent Data Sharing

From 0dda506a15aae008fcb47d6ed8bae9a00a43c63c Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Sat, 25 Jan 2025 20:30:04 +0300
Subject: [PATCH 12/62] docs reformat

---
 README-devops.md | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/README-devops.md b/README-devops.md
index 8268d3d6e..bda87f345 100644
--- a/README-devops.md
+++ b/README-devops.md
@@ -38,15 +38,15 @@ The Talkable documentation stack is a containerized system that uses Docker to s
    
    - Use the `master` branch for production.
    
-   ```bash
-   git checkout master
-   ```
+      ```bash
+      git checkout master
+      ```
    
    - Use the `staging-bastion` branch for staging.
    
-   ```bash
-   git checkout staging-bastion
-   ```
+      ```bash
+      git checkout staging-bastion
+      ```
 
 3. **Create and Configure the `.env` File**:
    
@@ -55,7 +55,9 @@ The Talkable documentation stack is a containerized system that uses Docker to s
      ```bash
      cp .env.template .env
      ```
+   
    - Update the following variables:
+  
      - **`ENVIRONMENT`**: Set to `development`, `staging`, or `production`.
      - **`LOCAL_PORT`**: Adjust if the default port (`8080`) is already in use.
      - Leave `_HOST` variables unchanged unless domain names for staging or production servers are updated.

From 97b67e13ef15c144854f874535b1dc1777da8747 Mon Sep 17 00:00:00 2001
From: Vitalii Oliinyk <ilovepinkpony1@gmail.com>
Date: Sun, 26 Jan 2025 22:47:23 +0200
Subject: [PATCH 13/62] [PR-23724]: fixed color for auto theme mode

---
 source/_static/talkable.css | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/source/_static/talkable.css b/source/_static/talkable.css
index 963b18aa1..887465952 100644
--- a/source/_static/talkable.css
+++ b/source/_static/talkable.css
@@ -18,6 +18,14 @@ body[data-theme="light"] .highlight button.copybtn.success:after {
   background: #f2f2f2 !important;
 }
 
+@media (prefers-color-scheme: light) {
+  body[data-theme="auto"] .highlight,
+  body[data-theme="auto"] .highlight button.copybtn,
+  body[data-theme="auto"] .highlight button.copybtn.success:after {
+    background: #f2f2f2 !important;
+  }
+}
+
 .highlight button.copybtn:hover {
   stroke: var(--color-link);
 }

From 2a3f5724ee402878a9ecedf2a42c55b4a032053b Mon Sep 17 00:00:00 2001
From: Enver <enver.ablyaev@gmail.com>
Date: Mon, 27 Jan 2025 20:41:35 +0300
Subject: [PATCH 14/62] [PR-23781] Migrate docs to Jenkins (#358)

Co-authored-by: Bohdan Zhuravel <bohdan@zhuravel.bz>
---
 .circleci/config.yml                          |  16 +-
 .env.template                                 |  10 +
 .github/PULL_REQUEST_TEMPLATE.md              |   4 -
 .gitignore                                    |  20 +-
 .ruby-gemset                                  |   1 -
 .ruby-version                                 |   1 -
 CNAME                                         |   1 -
 Dockerfile                                    |  14 ++
 Gemfile                                       |  11 -
 Guardfile                                     |  14 --
 Procfile                                      |   2 -
 README-devops.md                              |  93 ++++++++
 README-maintainer.md                          | 215 ++++++++++++++++++
 README.md                                     | 192 +++++++---------
 Rakefile                                      | 109 ---------
 docker-compose.yml                            |  32 +++
 nginx/conf.d/default.conf                     |  69 ++++++
 robots.txt => nginx/robots/development.txt    |   3 +-
 .../robots.txt => nginx/robots/production.txt |   1 +
 nginx/robots/staging.txt                      |   4 +
 packages.txt                                  |   9 +
 requirements.txt                              |  38 +++-
 source/_utils/__init__.py                     |   1 +
 source/_utils/baseurl.py                      |  15 ++
 source/conf.py                                | 107 +++++----
 25 files changed, 666 insertions(+), 316 deletions(-)
 create mode 100644 .env.template
 delete mode 100644 .ruby-gemset
 delete mode 100644 .ruby-version
 delete mode 100644 CNAME
 create mode 100644 Dockerfile
 delete mode 100644 Gemfile
 delete mode 100644 Guardfile
 delete mode 100644 Procfile
 create mode 100644 README-devops.md
 create mode 100644 README-maintainer.md
 delete mode 100644 Rakefile
 create mode 100644 docker-compose.yml
 create mode 100644 nginx/conf.d/default.conf
 rename robots.txt => nginx/robots/development.txt (53%)
 rename source/robots.txt => nginx/robots/production.txt (87%)
 create mode 100644 nginx/robots/staging.txt
 create mode 100644 packages.txt
 create mode 100644 source/_utils/__init__.py
 create mode 100644 source/_utils/baseurl.py

diff --git a/.circleci/config.yml b/.circleci/config.yml
index 72d4b3d46..ba6254a5c 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -6,10 +6,12 @@ executors:
       - auth:
           username: $DOCKERHUB_USERNAME
           password: $DOCKERHUB_ACCESS_TOKEN
-        image: cimg/python:3.12
+        image: cimg/python:3.13
+        environment:
+          ENVIRONMENT: production
 
 orbs:
-  python: circleci/python@2.1.1
+  python: circleci/python@3.0.0
 
 jobs:
   build:
@@ -18,12 +20,11 @@ jobs:
     steps:
       - checkout
 
-      - python/install-packages:
-          app-dir: ~/project
+      - python/install-packages
 
       - run:
           name: Build documentation
-          command: sphinx-build -nW -b html -d build/doctrees source build/html
+          command: sphinx-build -nW -b dirhtml -d build/doctrees source build/html
 
 workflows:
   workflow:
@@ -31,8 +32,3 @@ workflows:
       - build:
           context:
             - org-global
-          filters:
-            branches:
-              ignore:
-                - gh-pages
-                - /.*-gh-pages/
diff --git a/.env.template b/.env.template
new file mode 100644
index 000000000..7d3d25946
--- /dev/null
+++ b/.env.template
@@ -0,0 +1,10 @@
+# The port to use to populate the documentation on your local machine or server
+LOCAL_PORT=8080
+
+# Possible values: development, staging, production
+ENVIRONMENT=development
+
+# Base urls used for the canonical urls compilation
+DEVELOPMENT_HOST=localhost
+STAGING_HOST=staging-docs.talkable.com
+PRODUCTION_HOST=docs.talkable.com
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 5d752ddc8..cca63a8aa 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,9 +1,5 @@
 <!--- Provide a general summary of your changes in the Title above -->
 
-## Demo
-<!--- Please provide a link to a demo -->
-https://deploy-preview-{{id}}--talkable-docs.netlify.app/
-
 ## Related Stories
 <!--- If this pull request is related to JIRA story, please link to the story here -->
 [![](http://proxies.talkable.com/talkable/PR-1234)](https://talkable.atlassian.net/browse/PR-1234)
diff --git a/.gitignore b/.gitignore
index 14ec1a9a3..c3f20a68f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,7 +1,19 @@
+# IDE
+.idea
+.vscode
+
+# Local
+*.log
+.env
+
+# Sphinx
+_build
+
+# Python
+.venv
+__pycache__
+
+# Ruby
 /build
 /.bundle
 Gemfile.lock
-source/_static/test
-.pivotalrc
-.idea
-*.log
diff --git a/.ruby-gemset b/.ruby-gemset
deleted file mode 100644
index 10b85f5b3..000000000
--- a/.ruby-gemset
+++ /dev/null
@@ -1 +0,0 @@
-talkable-docs
diff --git a/.ruby-version b/.ruby-version
deleted file mode 100644
index 47b322c97..000000000
--- a/.ruby-version
+++ /dev/null
@@ -1 +0,0 @@
-3.4.1
diff --git a/CNAME b/CNAME
deleted file mode 100644
index fe80f6e25..000000000
--- a/CNAME
+++ /dev/null
@@ -1 +0,0 @@
-docs.talkable.com
diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 000000000..7697fa96f
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,14 @@
+FROM python:3.13-alpine3.21
+
+# Install dependencies
+WORKDIR /docs
+ADD requirements.txt /docs
+RUN python3 -m pip install -r requirements.txt
+
+CMD if [ "$ENVIRONMENT" = "development" ]; then \
+        echo "Running Sphinx in Development mode"; \
+        sphinx-autobuild -b dirhtml /docs/source /docs/_build; \
+    else \
+        echo "Running Sphinx in Staging/Production mode"; \
+        sphinx-build -b dirhtml /docs/source /docs/_build; \
+    fi
\ No newline at end of file
diff --git a/Gemfile b/Gemfile
deleted file mode 100644
index 11fcd5bc1..000000000
--- a/Gemfile
+++ /dev/null
@@ -1,11 +0,0 @@
-source 'https://rubygems.org'
-
-ruby file: '.ruby-version'
-
-gem 'base64' # Removed from standard library in Ruby 3.4
-gem 'foreman'
-gem 'guard-livereload'
-gem 'guard-shell'
-gem 'rake'
-gem 'reline' # Removed from standard library in Ruby 3.5
-gem 'webrick'
diff --git a/Guardfile b/Guardfile
deleted file mode 100644
index dfe8ecf09..000000000
--- a/Guardfile
+++ /dev/null
@@ -1,14 +0,0 @@
-guard 'shell' do
-  watch(%r{(.*)\.rst}) do |m|
-    system("sphinx-build -b html -d build/doctrees source build/html")
-  end
-
-  watch(%r{^source/_static/}) do |m|
-    system("rsync -az source/_static build/html")
-  end
-end
-
-guard 'livereload' do
-  watch(%r{(.*)\.rst})
-  watch(%r{^source/_static/})
-end
diff --git a/Procfile b/Procfile
deleted file mode 100644
index 2da95c518..000000000
--- a/Procfile
+++ /dev/null
@@ -1,2 +0,0 @@
-web: ruby -run -e httpd -- --port=5001 build/html
-guard: bundle exec guard
diff --git a/README-devops.md b/README-devops.md
new file mode 100644
index 000000000..b09d2e06a
--- /dev/null
+++ b/README-devops.md
@@ -0,0 +1,93 @@
+## Overview
+
+The Talkable documentation stack is a containerized system that uses Docker to simplify deployment and management. It is designed to generate, serve, and manage static documentation across multiple environments, such as staging and production.
+
+## Key Features
+
+1. **Containerized Components**:
+   
+   - **Nginx**: Handles HTTP requests, serves static HTML files, manages URL redirection, and dynamically serves environment-specific `robots.txt` files.
+   - **Sphinx Autobuilder**: Generates static HTML files from source documentation and stores them in a persistent volume shared with Nginx.
+
+2. **Environment-Specific Behavior**:
+   
+   - Configured via a `.env` file for flexibility.
+   - Supports dynamic environment-specific behavior, such as serving different `robots.txt` files based on the `ENVIRONMENT` variable.
+
+3. **Efficient Architecture**:
+   
+   - Deployed on Amazon AWS Virtual Private Servers (VPS) with an AWS load balancer directing user traffic to the appropriate environment.
+   - Sphinx generates content on a persistent volume that Nginx serves directly.
+
+## Deployment Process
+
+### Prerequisites
+
+- Ensure Docker and Docker Compose are installed on the target VPS.
+- Clone the repository containing the stack configuration.
+
+### Steps
+
+1. **Clone the Repository**:
+   
+   ```bash
+   git clone git@github.com:talkable/talkable-docs.git
+   ```
+
+2. **Switch to the Appropriate Branch**:
+   
+   - Use the `master` branch for production.
+   
+      ```bash
+      git checkout master
+      ```
+   
+   - Use the `staging` branch for staging.
+   
+      ```bash
+      git checkout staging
+      ```
+
+3. **Create and Configure the `.env` File**:
+   
+   - Copy `.env.template` to `.env`:
+   
+     ```bash
+     cp .env.template .env
+     ```
+   
+   - Update the following variables:
+  
+     - **`ENVIRONMENT`**: Set to `development`, `staging`, or `production`.
+     - **`LOCAL_PORT`**: Adjust if the default port (`8080`) is already in use.
+     - Leave `_HOST` variables unchanged unless domain names for staging or production servers are updated.
+
+4. **Deploy the Stack**:
+   
+   ```bash
+   docker compose up -d --build
+   ```
+
+## Environment-Specific Configuration
+
+### Handling `robots.txt`
+
+- The repository includes separate `robots.txt` files for each environment.
+- The correct file is dynamically selected based on the `ENVIRONMENT` variable and mapped to the container:
+  
+  ```yaml
+  volumes:
+    - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
+  ```
+
+- Nginx serves the file at `/var/www/robots.txt` in response to `robots.txt` requests.
+
+## Persistent Data Sharing
+
+- **Static HTML Files**:
+  - Generated by Sphinx and stored in a shared volume.
+  - Served by Nginx without regeneration.
+
+- **Volume Management**:
+  - Shared volumes allow seamless access and updates between containers.
+  - Ensures efficient and consistent behavior across environments.
diff --git a/README-maintainer.md b/README-maintainer.md
new file mode 100644
index 000000000..e9891b437
--- /dev/null
+++ b/README-maintainer.md
@@ -0,0 +1,215 @@
+# Talkable Documentation Maintenance Routine
+
+This documentation provides instructions for maintaining the Sphinx Builder **framework** used to generate the Talkable Documentation.
+
+It outlines the routine for maintaining the framework and associated workflows.
+
+> **Note**: 
+> 
+> This guide does not cover updating the documentation content. 
+> Refer to [README.md](README.md) for details on updating the Talkable documentation source, which is available at [https://docs.talkable.com/](https://docs.talkable.com/).
+
+## Scope
+
+The maintenance routine includes the following tasks:
+
+- Updating dependencies:
+  - Sphinx and other Python packages
+  - Nginx container (application server)
+  - Python container
+- Adding new extensions
+- Introducing Talkable-specific customizations (Python scripts)
+
+## Preparations
+
+1. Clone the documentation repository.
+
+    ```bash
+    git clone git@github.com:talkable/talkable-docs.git
+    cd talkable-docs
+    ```
+
+2. Create a new branch from `master`.
+
+    ```bash
+    git branch new-branch
+    git checkout new-branch
+    ```
+
+3. Generate a `.env` file from the `.env.template`.
+
+    ```bash
+    cp .env.template .env
+    ```
+
+## Updating Packages
+
+The goal is to update `requirements.txt` with the latest versions of dependencies.
+
+1. Replace `requirements.txt` with the `packages.txt` file.
+
+    ```bash
+    cp packages.txt requirements.txt
+    ```
+
+2. Build the Sphinx container.
+
+    ```bash
+    docker compose up -d --build
+    ```
+
+    This starts the framework and allows you to load the documentation at http://localhost:8080.
+
+    If the documentation fails to load, check the Sphinx container logs:
+
+    ```bash
+    docker logs -f sphinx
+    ```
+
+    ...and the Nginx logs:
+
+    ```bash
+    docker logs -f nginx
+    ```
+
+3. Test and freeze `requirements.txt`.
+
+    Ensure everything works as expected locally. Once confirmed, update `requirements.txt` to include all installed dependencies with their versions.
+
+    > **Note:**
+    >
+    > In addition to the packages listed in [packages.txt](packages.txt), `requirements.txt` will include transitive dependencies.
+
+    Save the dependencies with the following command:
+
+    ```bash
+    docker exec sphinx pip freeze > requirements.txt
+    ```
+
+4. Stop the containers.
+
+    Once the documentation is fully functional, stop the containers:
+
+    ```bash
+    docker compose down -v
+    ```
+
+5. Push the updated `requirements.txt` to GitHub.
+
+    Commit and push the updated `requirements.txt` for testing and production.
+
+## Updating the Nginx Version
+
+The goal is to update the `docker-compose.yml` file with the latest Nginx image tag.
+
+1. Check the DockerHub Nginx page for newer versions: https://hub.docker.com/_/nginx.
+
+    > **Note:** 
+    >
+    > Use only Alpine-based images.
+
+2. Update the `docker-compose.yml` file with the new version tag:
+
+    ```yaml
+    image: nginx:1.27-alpine3.20
+    ```
+
+3. Deploy the updated image.
+
+    Test the new image:
+
+    ```bash
+    docker compose up -d --build
+    ```
+
+    Verify that the documentation loads at http://localhost:8080.
+
+4. Finalize the update.
+
+    Commit the updated `docker-compose.yml` to the repository for testing and production.
+
+    Stop the containers:
+
+    ```bash
+    docker compose down -v
+    ```
+
+## Updating the Python Container
+
+The Sphinx framework uses a Python Docker image from DockerHub.
+
+1. Check for the latest Python image on DockerHub: https://hub.docker.com/_/python.
+
+2. Update the image name in the [Dockerfile](./Dockerfile):
+
+    ```dockerfile
+    FROM python:3.13-alpine3.21
+    ```
+
+3. Test the deployment.
+
+    Deploy the Sphinx container to verify the updates:
+
+    ```bash
+    docker compose up -d --build
+    ```
+
+    Confirm that the documentation loads at http://localhost:8080.
+
+4. Finalize the update.
+
+    Commit the updated `Dockerfile` to the repository for testing and production.
+
+    Stop the containers:
+
+    ```bash
+    docker compose down -v
+    ```
+
+## Adding New Extensions
+
+Sphinx is a highly customizable documentation framework. You can extend its functionality with official or third-party extensions.
+
+Here are some resources:
+
+- https://sphinx-extensions.readthedocs.io/en/latest/
+- https://www.sphinx-doc.org/en/master/development/index.html
+- https://github.com/sphinx-contrib
+
+To add extensions, follow these steps:
+
+1. [Install additional Python packages](#installing-additional-packages).
+2. [Adjust the conf.py file](#modifying-configuration-files).
+3. Add Python scripts to the [./source/](./source/) directory if necessary.
+
+Start by deploying the framework container:
+
+```bash
+docker compose up -d --build
+```
+
+### Installing Additional Packages
+
+1. Add the package to `requirements.txt`.
+
+    Append the package name to `requirements.txt` (version specification is optional at this stage).
+
+    > **Note:**
+    >
+    > Version pinning can be done later.
+
+2. Rebuild the container.
+
+    Rebuild the container after modifying `requirements.txt`:
+
+    ```bash
+    docker compose up -d --build
+    ```
+
+### Modifying Configuration Files
+
+Most changes involve editing the [./source/conf.py](./source/conf.py) file or other files in the [./source/](./source/) directory.
+
+> **Note:**
+>
+> Rebuilding the container is unnecessary for changes to [./source/conf.py](./source/conf.py) or [./source/](./source/). These changes are applied automatically within 1 second.
diff --git a/README.md b/README.md
index f2c07f7a8..ed2a8ba2c 100644
--- a/README.md
+++ b/README.md
@@ -1,30 +1,83 @@
-Talkable Documentation
-======================
+## What is Talkable Documentation?
 
-[![Build Status](https://circleci.com/gh/talkable/talkable-docs.svg?style=svg&circle-token=cc33458158e7b0c1f6f8cbf1bcbf74f00ee28a8e)](https://circleci.com/gh/talkable/workflows/talkable-docs)
+The set of articles describing Talkable's capabilities, publicly available at [docs.talkable.com](https://docs.talkable.com).
 
-This GitHub repository represents Talkable’s documentation site, located at [docs.talkable.com](https://docs.talkable.com).
+It uses [reStructuredText](https://docutils.sourceforge.io/rst.html) as its markup language, an easy-to-read, what-you-see-is-what-you-get plaintext markup syntax. All reStructuredText formatting capabilities can be found in [The reST Quickref](https://docutils.sourceforge.io/docs/user/rst/quickref.html).
 
-The Talkable documentation uses [reStructuredText](https://docutils.sourceforge.io/rst.html) as its markup language and is built using [Sphinx](https://www.sphinx-doc.org).
+It is built using [Sphinx](https://www.sphinx-doc.org), an open-source documentation generation tool that transforms plain text files into beautifully formatted documentation. For more details, see [The Sphinx Documentation](https://www.sphinx-doc.org).
 
-Sphinx
-------
+## Where is it stored?
 
-For more details see [The Sphinx Documentation](https://www.sphinx-doc.org).
+It's stored in a dedicated GitHub repository ([talkable-docs](https://github.com/talkable/talkable-docs)).
 
-reStructuredText
-----------------
+The repository consists of the following branches:
+- [master](https://github.com/talkable/talkable-docs/tree/master): The main branch used to keep the most recent stable version available at [docs.talkable.com](https://docs.talkable.com).
+- [staging](https://github.com/talkable/talkable-docs/tree/staging): A staging branch used for testing by QA. It is available at [staging-docs.talkable.com](https://staging-docs.talkable.com).
+- Feature branches created from `master` by individual contributors/developers.
 
-For more details see [The reST Quickref](https://docutils.sourceforge.io/docs/user/rst/quickref.html).
+## What is the documentation update workflow?
+
+1. Pull changes from `master`.
+2. Checkout a new branch from `master`.
+3. Deploy the local/development environment.
+4. Make changes and test them locally.
+5. Commit the changes to the `staging` branch.
+6. Get the documentation tested by QA.
+7. Create a pull request to the `master` branch, providing the staging URL of the changed page in the pull request description.
+8. Merge the pull request once it passes the review.
+
+## How to deploy the local environment?
+
+0. **Install Docker**
+
+   Follow the [official Docker documentation](https://docs.docker.com/compose/install/).
+
+1. **Navigate to the repository root directory.**
+
+   Ensure the `docker-compose.yml` file is located there.
+
+2. **Create an `.env` file by copying `.env.template`.**
+   
+   Review and update the variable values if needed.
+   
+   For a **development/local environment**, all default settings should work out of the box. The only value you may need to change is `LOCAL_PORT` if `8080` is already in use on your local machine.
+
+3. **Run the local environment deployment.**
+
+   Run the command:
+
+   ```bash
+   docker compose up -d
+   ```
+
+   If everything is set up correctly, the documentation will be available at [http://localhost:8080](http://localhost:8080). Make sure you use the port number defined in the `.env` file.
+
+   If the documentation does not load, check the **Troubleshooting** section.
+
+## How to deploy changes to production and staging?
+
+You should not deploy it manually!
+
+The deployment is handled by Jenkins jobs. 
+
+All you need to do is commit your changes to the corresponding branch to deploy them to the appropriate server:
+- Commit to the [staging](https://github.com/talkable/talkable-docs/tree/staging) branch => [staging-docs.talkable.com](https://staging-docs.talkable.com/).
+- Commit to the [master](https://github.com/talkable/talkable-docs/tree/master) branch => [docs.talkable.com](https://docs.talkable.com/).
+
+## How do I make the actual changes?
+
+Navigate to the [source](./source/) directory and update the files using `reStructuredText` syntax. Refer to [The reST Quickref](https://docutils.sourceforge.io/docs/user/rst/quickref.html) for syntax details.
+
+Here are some formatting examples:
 
 ### Sections
 
 Section headings are very flexible in reST. We use the following convention in the Talkable documentation:
 
-* `#` for module headings
-* `=` for sections
-* `-` for subsections
-* `.` for subsubsections
+- `#` for module headings
+- `=` for sections
+- `-` for subsections
+- `.` for subsubsections
 
 ### Cross-referencing
 
@@ -57,103 +110,28 @@ Here is a reference to "talkable section": :ref:`talkable-section` which will ha
 name "Talkable Section".
 ```
 
-### General Formatting Rules for Documentation
-
-**Directives (`..` syntax)**:
-
-* All directives starting with `..` (e.g., `.. image::`, `.. note::`) must have **2 spaces** indentation for their content. Examples:
-
-    ```rst
-    .. meta::
-      :description: This is an example of a meta directive.
-
-    .. image:: /_static/img/example.jpg
-      :alt: Example Image
-
-    .. note::
-      This is an important note.
-    
-    .. code-block:: html
-      <h1>Hello world!</h1>
-    ```
-
-#### Empty Line at the End of Files
-
-Always ensure there is a blank line at the end of each file to adhere to formatting standards.
-
-Build the documentation
------------------------
-
-First install [Sphinx](https://www.sphinx-doc.org). See below.
-
-### Installing Sphinx on macOS
-
-* Install [Homebrew](https://brew.sh).
-
-* Install Ruby and [Bundler](https://bundler.io), and run `bundle install` to install dependencies.
-
-* Install Python (>= 3.9) and pip:
-
-  ```
-  brew install python
-  ```
-
-  More information in case of trouble: https://docs.brew.sh/Homebrew-and-Python
-
-* Install dependencies:
-
-  ```
-  pip3 install -r requirements.txt --break-system-package
-  ```
-
-  If you have problems, try adding `-I` flag (`--ignore-installed`) to the `pip install` command.
-
-If you get the error "unknown locale: UTF-8" when generating the documentation,
-the solution is to define the following environment variables:
-
-    export LANG=en_US.UTF-8
-    export LC_ALL=en_US.UTF-8
-
-### Building
-
-Run `rake preview` from "master" branch.
-
-#### Setting up LiveReload
-
-Run `rake server` from "master" branch and open `http://localhost:5000` in browser.
-
-### Deploying
-
-If you’re deploying for the first time make sure you have `gh-pages` branch locally. Otherwise run the following command to create it: `git checkout -b gh-pages origin/gh-pages`.
-
-General flow:
-1. Pull changes from master
-2. Checkout your new branch from master
-3. Make changes
-4. Deploy your changes to staging (see the instruction below)
-4. Create a Pull Request to "master" branch, providing the demo URL to the changed page in Pull Request’s description.
-5. Merge pull request once it passes the review
-6. Deploy
+## Troubleshooting
 
-If you did everything right, deploying is as easy as `rake deploy` from "master" branch.
+#### Can't view the documentation locally in the browser?
 
-#### Deploying to Staging
+1. Ensure you are using the correct port number and protocol.
+   The port number should match the value provided in `.env` as `LOCAL_PORT`.
 
-If it’s your first time deploying to staging, run `rake setup` to setup git remote.
+2. Check `nginx` logs:
 
-1. Switch to local branch "void" and pull the latest changes from the remote:
-  `git checkout void; git pull`
-2. Merge your branch into local branch "void":
-  `git merge YOUR_BRANCH_NAME`
-3. Push the changes to the remote branch "void":
-  ```git push origin void```
-4. Deploy:
-  ```rake deploy:staging```
+   ```bash
+   docker logs -f nginx
+   ```
 
----
+3. Check `Sphinx` logs:
 
-See "master" branch: https://github.com/talkable/talkable-docs
+   ```bash
+   docker logs -f sphinx
+   ```
 
-See "gh-pages" branch: https://github.com/talkable/talkable-docs/tree/gh-pages
+## Links
 
-See GitHub Page (auto generated): https://docs.talkable.com
+- GitHub "staging" branch: [staging](https://github.com/talkable/talkable-docs/tree/staging)
+- Staging web server: [staging-docs.talkable.com](https://staging-docs.talkable.com/)
+- GitHub "production" branch: [master](https://github.com/talkable/talkable-docs/tree/master)
+- Production web server: [docs.talkable.com](https://docs.talkable.com/)
diff --git a/Rakefile b/Rakefile
deleted file mode 100644
index f47ca6c00..000000000
--- a/Rakefile
+++ /dev/null
@@ -1,109 +0,0 @@
-# frozen_string_literal: true
-require 'mkmf'
-
-SPHINX_BUILD = ENV['SPHINX_BUILD'] || 'sphinx-build'
-SOURCE_DIR   = 'source'
-BUILD_DIR    = 'build'
-SPHINX_OPTS  = "-b html -d #{BUILD_DIR}/doctrees #{SOURCE_DIR} #{BUILD_DIR}/html"
-
-task :default => :help
-task :help do
-  system 'rake --tasks'
-end
-
-desc 'Set up deploys'
-task :setup do
-  sh 'git remote add staging git@github.com:talkable/void-talkable-docs.git'
-end
-
-task :environment do
-  ENV['LANG'] = ENV['LC_ALL'] = 'en_US.UTF-8'
-  find_executable(SPHINX_BUILD) || abort("The '#{SPHINX_BUILD}' command was not found. Make sure you have Sphinx installed, then set the SPHINX_BUILD environment variable to point to the full path of the '#{SPHINX_BUILD}' executable. Alternatively you can add the directory with the executable to your PATH. If you do not have Sphinx installed, grab it from http://sphinx-doc.org/")
-
-  regexp = /(\d+\.)?(\d+\.)?(\*|\d+)/
-  required = File.read('requirements.txt').match(regexp).to_s
-  installed = `#{SPHINX_BUILD} --version`.match(regexp).to_s rescue ''
-  if !required.empty? && !installed.empty? && Gem::Version.new(required) > Gem::Version.new(installed)
-    abort "\nYou are running an outdated version of Sphinx #{installed}. Required version is #{required}. Run `pip3 install -r requirements.txt --break-system-packages` to upgrade Sphinx."
-  end
-end
-
-desc 'Run build in test mode'
-task :test => :environment do
-  sh "#{SPHINX_BUILD} -nW #{SPHINX_OPTS}"
-end
-
-task :build => :environment do
-  sh "#{SPHINX_BUILD} #{SPHINX_OPTS}"
-
-  Rake::FileList["#{BUILD_DIR}/html/**/*.html"].each do |filename|
-    File.open(filename, "r+") do |file|
-      old_content = file.read
-      new_content = old_content.gsub(%r{<a(.+)href="(https?://(?!(?:www\.)?talkable\.com).*?)"}, '<a\1rel="nofollow" href="\2"')
-      file.tap(&:rewind).write(new_content) if old_content != new_content
-    end
-  end
-
-  puts "\nBuild finished. The HTML pages are in #{File.expand_path("#{BUILD_DIR}/html")}."
-end
-
-task :clean do
-  sh "rm -rf #{BUILD_DIR}/*"
-end
-
-desc 'Make standalone HTML files'
-task :preview => [:clean, :build]
-
-desc 'Run the server on localhost:5001 and open a browser'
-task :server => :preview do
-  sh '(sleep 2 && open "http://localhost:5001")&'
-  sh 'bundle exec foreman start'
-end
-
-desc 'Commit and deploy changes to https://docs.talkable.com'
-task :deploy => :'deploy:production'
-
-namespace :deploy do
-  def deploy(domain:, html_branch:, source_branch:, disallow_robots:, push_command:)
-    sh "git checkout #{html_branch}"
-    sh 'git pull'
-    sh "find . -not -path './.git' -not -path './.git/*' -not -path './Rakefile' -not -path './.circleci' -not -path './.circleci/*' -delete"
-    sh "git checkout #{source_branch} #{SOURCE_DIR} .gitignore requirements.txt"
-    sh 'git reset HEAD'
-    Rake::Task[:build].invoke
-    sh "(cd #{BUILD_DIR}/html && tar c ./) | (cd ./ && tar xf -)"
-    sh "rm -rf #{BUILD_DIR} #{SOURCE_DIR} .buildinfo"
-    File.write('.nojekyll', '')
-    File.write('CNAME', domain)
-    File.write('robots.txt', "User-agent: *\nDisallow: /") if disallow_robots
-    sh 'git add -A'
-    sh "git commit -m \"Generated gh-pages for `git log #{source_branch} -1 --pretty=short --abbrev-commit`\" && #{push_command} ; git checkout #{source_branch}"
-
-    puts "\nDeployment finished. Check updated docs at https://#{domain}"
-  end
-
-  task :production do
-    deploy(
-      domain: 'docs.talkable.com',
-      html_branch: 'gh-pages',
-      source_branch: 'master',
-      disallow_robots: false,
-      push_command: 'git push origin gh-pages'
-    )
-  end
-
-  desc 'Commit and deploy changes to https://void-docs.talkable.com'
-  task :staging do
-    sh 'git remote show staging' do |ok, _|
-      Rake::Task[:setup].invoke unless ok
-    end
-
-    deploy(
-      domain: 'void-docs.talkable.com',
-      html_branch: 'void-gh-pages',
-      source_branch: 'void',
-      disallow_robots: true,
-      push_command: 'git push -f origin void-gh-pages && git push -f staging void-gh-pages:gh-pages'
-    )
-  end
-end
diff --git a/docker-compose.yml b/docker-compose.yml
new file mode 100644
index 000000000..0795ce5c1
--- /dev/null
+++ b/docker-compose.yml
@@ -0,0 +1,32 @@
+services:
+
+  sphinx:
+    build:
+      context: .
+      dockerfile: Dockerfile
+    container_name: sphinx
+    volumes:
+      - ./source:/docs/source
+      - docs_build:/docs/_build
+    environment:
+      - ENVIRONMENT=${ENVIRONMENT}
+      - LOCAL_PORT=${LOCAL_PORT}
+      - PRODUCTION_HOST=${PRODUCTION_HOST}
+      - STAGING_HOST=${STAGING_HOST}
+      - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
+    
+  nginx:
+    image: nginx:1.27-alpine3.20
+    container_name: nginx
+    volumes:
+      - docs_build:/var/www/html
+      - ./nginx/conf.d:/etc/nginx/conf.d
+      - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
+    ports:
+      - ${LOCAL_PORT}:80
+    depends_on:
+      - sphinx
+
+volumes:
+  docs_build:
+    driver: local
diff --git a/nginx/conf.d/default.conf b/nginx/conf.d/default.conf
new file mode 100644
index 000000000..5eb1145ca
--- /dev/null
+++ b/nginx/conf.d/default.conf
@@ -0,0 +1,69 @@
+server {
+    listen 80;
+    server_name _;
+
+    root /var/www/html; 
+    index index.html;
+
+    # Basic security headers
+    add_header X-Frame-Options "SAMEORIGIN";
+    add_header X-Content-Type-Options "nosniff";
+    add_header X-XSS-Protection "1; mode=block";
+
+    # Gzip settings
+    gzip on;
+    gzip_types
+        text/plain
+        text/css
+        application/json
+        application/javascript
+        text/xml
+        application/xml
+        application/xml+rss
+        text/javascript
+        image/svg+xml
+        font/ttf
+        font/woff
+        font/woff2;
+
+    # Helps preserve the port in redirects when not on 80/443
+    absolute_redirect off;
+    port_in_redirect on;
+
+    # Rewrite .html → no .html
+    location ~* ^/.+\.html$ {
+        # Avoid redirect loops if this is an internal sub-request (fallback)
+        if ($uri != $request_uri) {
+            break;
+        }
+
+        # If it ends with "index.html", remove "index.html"
+        # e.g. /path/index.html => /path/
+        # e.g. /index.html => /
+        rewrite "^/(.*)index\.html$" /$1 permanent;
+
+        # Otherwise remove ".html" and append slash
+        # e.g. /overview.html => /overview/
+        rewrite "^/(.+)\.html$" /$1/ permanent;
+    }
+
+    # Serve static assets with long cache
+    location ~* \.(?:css|js|jpe?g|png|gif|ico|svg|woff2?|ttf|eot|otf|webp)$ {
+        expires 1y;
+        add_header Cache-Control "public, max-age=31536000, immutable";
+        access_log off;
+        try_files $uri =404;
+    }
+
+    # Serve robots.txt from a specific file
+    location = /robots.txt {
+        alias /var/www/robots.txt;
+        access_log off;
+        log_not_found off;
+    }
+
+    # Default static-file behavior
+    location / {
+        try_files $uri $uri/ =404;
+    }
+}
diff --git a/robots.txt b/nginx/robots/development.txt
similarity index 53%
rename from robots.txt
rename to nginx/robots/development.txt
index 60ed3d057..1f53798bb 100644
--- a/robots.txt
+++ b/nginx/robots/development.txt
@@ -1,3 +1,2 @@
 User-agent: *
-Disallow: 
-
+Disallow: /
diff --git a/source/robots.txt b/nginx/robots/production.txt
similarity index 87%
rename from source/robots.txt
rename to nginx/robots/production.txt
index f3fc00670..4acb8d432 100644
--- a/source/robots.txt
+++ b/nginx/robots/production.txt
@@ -1,3 +1,4 @@
 User-agent: *
+Allow: /
 
 Sitemap: https://docs.talkable.com/sitemap.xml
diff --git a/nginx/robots/staging.txt b/nginx/robots/staging.txt
new file mode 100644
index 000000000..ed8d11f01
--- /dev/null
+++ b/nginx/robots/staging.txt
@@ -0,0 +1,4 @@
+User-agent: *
+Disallow: /
+
+Sitemap: https://staging-docs.talkable.com/sitemap.xml
diff --git a/packages.txt b/packages.txt
new file mode 100644
index 000000000..cca18c7b5
--- /dev/null
+++ b/packages.txt
@@ -0,0 +1,9 @@
+# This is a list of packages used in the framework
+# Used by the documentation maintainer
+# Add the package name here if you add some to the framework
+
+furo
+sphinx-copybutton
+sphinx-sitemap
+sphinx-autobuild
+sphinx-favicon
diff --git a/requirements.txt b/requirements.txt
index ffd6786dc..7b2f8fbf9 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,4 +1,38 @@
-furo
-sphinx-copybutton
+alabaster==1.0.0
+anyio==4.8.0
+babel==2.16.0
+beautifulsoup4==4.12.3
+certifi==2024.12.14
+charset-normalizer==3.4.1
+click==8.1.8
+colorama==0.4.6
+docutils==0.21.2
+furo==2024.8.6
+h11==0.14.0
+idna==3.10
+imagesize==1.4.1
+Jinja2==3.1.5
+MarkupSafe==3.0.2
+packaging==24.2
+Pygments==2.19.1
+requests==2.32.3
+sniffio==1.3.1
+snowballstemmer==2.2.0
+soupsieve==2.6
 Sphinx==8.1.3
+sphinx-autobuild==2024.10.3
+sphinx-basic-ng==1.0.0b2
+sphinx-copybutton==0.5.2
+sphinx-favicon==1.0.1
 sphinx-sitemap==2.6.0
+sphinxcontrib-applehelp==2.0.0
+sphinxcontrib-devhelp==2.0.0
+sphinxcontrib-htmlhelp==2.1.0
+sphinxcontrib-jsmath==1.0.1
+sphinxcontrib-qthelp==2.0.0
+sphinxcontrib-serializinghtml==2.0.0
+starlette==0.45.3
+urllib3==2.3.0
+uvicorn==0.34.0
+watchfiles==1.0.4
+websockets==14.2
diff --git a/source/_utils/__init__.py b/source/_utils/__init__.py
new file mode 100644
index 000000000..5712dd70e
--- /dev/null
+++ b/source/_utils/__init__.py
@@ -0,0 +1 @@
+from .baseurl import baseurl
diff --git a/source/_utils/baseurl.py b/source/_utils/baseurl.py
new file mode 100644
index 000000000..d15df347d
--- /dev/null
+++ b/source/_utils/baseurl.py
@@ -0,0 +1,15 @@
+import os
+
+local_port = os.getenv("LOCAL_PORT")
+environment = os.getenv("ENVIRONMENT")
+production_host = os.getenv("PRODUCTION_HOST")
+staging_host = os.getenv("STAGING_HOST")
+development_host = os.getenv("DEVELOPMENT_HOST")
+
+baseurl_json = {
+    "development": f"http://{development_host}:{local_port}/",
+    "staging": f"https://{staging_host}/",
+    "production": f"https://{production_host}/",
+}
+
+baseurl = baseurl_json.get(environment)
diff --git a/source/conf.py b/source/conf.py
index 827941e0a..296acbe88 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -12,88 +12,96 @@
 # All configuration values have a default; values that are commented out
 # serve to show the default.
 
-# import sys
-# import os
+import sys
+import os
 
 # If extensions (or modules to document with autodoc) are in another directory,
 # add these directories to sys.path here. If the directory is relative to the
 # documentation root, use os.path.abspath to make it absolute, like shown here.
-#sys.path.insert(0, os.path.abspath('.'))
+sys.path.insert(0, os.path.abspath("."))
+
+# Import Talkable custom code
+from _utils import baseurl
 
 # -- General configuration ------------------------------------------------
 
 # If your documentation needs a minimal Sphinx version, state it here.
-#needs_sphinx = '1.0'
+# needs_sphinx = '1.0'
 
 # Add any Sphinx extension module names here, as strings. They can be
 # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
 # ones.
-extensions = ['sphinx_sitemap', 'sphinx_copybutton']
+extensions = [
+    "sphinx_sitemap",
+    "sphinx_copybutton",
+    "sphinx_favicon",
+]
+
 sitemap_url_scheme = "{link}"
 
 # Add any paths that contain templates here, relative to this directory.
-templates_path = ['_templates']
+templates_path = ["_templates"]
 
 # The suffix of source filenames.
-source_suffix = '.rst'
+source_suffix = ".rst"
 
 # The encoding of source files.
-#source_encoding = 'utf-8-sig'
+# source_encoding = 'utf-8-sig'
 
 # The master toctree document.
-master_doc = 'index'
+master_doc = "index"
 
 # General information about the project.
-project = u'Talkable'
-copyright = u'Talkable Inc.'
-author = u'Talkable Inc.'
+project = "Talkable"
+copyright = "Talkable Inc."
+author = "Talkable Inc."
 
 # The version info for the project you’re documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
 # The short X.Y version.
-version = u'1.0'
+version = "1.0"
 # The full version, including alpha/beta/rc tags.
-release = u'1.0'
+release = "1.0"
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
-#language = None
+# language = None
 
 # There are two options for replacing |today|: either, you set today to some
 # non-false value, then it is used:
-#today = ''
+# today = ''
 # Else, today_fmt is used as the format for a strftime call.
-#today_fmt = '%B %d, %Y'
+# today_fmt = '%B %d, %Y'
 
 # List of patterns, relative to source directory, that match files and
 # directories to ignore when looking for source files.
-exclude_patterns = ['_build', 'partials', 'samples', '.DS_Store']
+exclude_patterns = ["_build", "partials", "samples", ".DS_Store"]
 
 # The reST default role (used for this markup: `text`) to use for all
 # documents.
-#default_role = None
+# default_role = None
 
 # If true, '()' will be appended to :func: etc. cross-reference text.
-#add_function_parentheses = True
+# add_function_parentheses = True
 
 # If true, the current module name will be prepended to all description
 # unit titles (such as .. function::).
-#add_module_names = True
+# add_module_names = True
 
 # If true, sectionauthor and moduleauthor directives will be shown in the
 # output. They are ignored by default.
-#show_authors = False
+# show_authors = False
 
 # The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
+pygments_style = "sphinx"
 
 # A list of ignored prefixes for module index sorting.
-#modindex_common_prefix = []
+# modindex_common_prefix = []
 
 # If true, keep warnings as "system message" paragraphs in the built documents.
-#keep_warnings = False
+# keep_warnings = False
 
 
 # -- Options for HTML output ----------------------------------------------
@@ -111,30 +119,36 @@
 html_show_sourcelink = False
 
 # Add any paths that contain custom themes here, relative to this directory.
-#html_theme_path = []
+# html_theme_path = []
 
 # The name for this set of Sphinx documents.  If None, it defaults to
 # "<project> v<release> documentation".
-html_title = u''
+html_title = ""
 
 # A shorter title for the navigation bar.  Default is the same as html_title.
-#html_short_title = None
+# html_short_title = None
 
 # The name of an image file (relative to this directory) to place at the top
 # of the sidebar.
-#html_logo = None
+# html_logo = None
 
 # The name of an image file (within the static path) to use as favicon of the
 # docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
 # pixels large.
-#html_favicon = None
+# html_favicon = None
+
+favicons = {
+    "rel": "icon",
+    "href": "img/favicon.ico",
+    "type": "image/vnd.microsoft.icon",
+}
 
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ['_static']
+html_static_path = ["_static"]
 html_css_files = [
-    'talkable.css',
+    "talkable.css",
 ]
 html_theme_options = {
     "light_logo": "img/logo.svg",
@@ -150,7 +164,7 @@
 # Add any extra paths that contain custom files (such as robots.txt or
 # .htaccess) here, relative to this directory. These files are copied
 # directly to the root of the documentation.
-html_extra_path = ['robots.txt']
+# html_extra_path = ["robots.txt"]
 
 # If not None, a 'Last updated on:' timestamp is inserted at every page bottom,
 # using the given strftime format.
@@ -159,26 +173,26 @@
 
 # If true, SmartyPants will be used to convert quotes and dashes to
 # typographically correct entities.
-#html_use_smartypants = True
+# html_use_smartypants = True
 
 # Custom sidebar templates, maps document names to template names.
-#html_sidebars = {}
+# html_sidebars = {}
 
 # Additional templates that should be rendered to pages, maps page names to
 # template names.
-#html_additional_pages = {}
+# html_additional_pages = {}
 
 # If false, no module index is generated.
-#html_domain_indices = True
+# html_domain_indices = True
 
 # If false, no index is generated.
 html_use_index = False
 
 # If true, the index is split into individual pages for each letter.
-#html_split_index = False
+# html_split_index = False
 
 # If true, links to the reST sources are added to the pages.
-#html_show_sourcelink = True
+# html_show_sourcelink = True
 
 # If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
 html_show_sphinx = False
@@ -189,26 +203,23 @@
 # If true, an OpenSearch description file will be output, and all pages will
 # contain a <link> tag referring to it.  The value of this option must be the
 # base URL from which the finished HTML is served.
-#html_use_opensearch = ''
+# html_use_opensearch = ''
 
 # This is the file name suffix for HTML files (e.g. ".xhtml").
-#html_file_suffix = None
+# html_file_suffix = None
 
 # Output file base name for HTML help builder.
-htmlhelp_basename = 'Talkabledoc'
+htmlhelp_basename = "Talkabledoc"
 
 # The URL which points to the root of the HTML documentation.
 # It is used to indicate the location of document like canonical_url.
-html_baseurl = 'https://docs.talkable.com/'
+html_baseurl = baseurl
 
 # -- Options for manual page output ---------------------------------------
 
 # One entry per manual page. List of tuples
 # (source start file, name, description, authors, manual section).
-man_pages = [
-    (master_doc, 'talkable', u'Talkable Documentation',
-     [author], 1)
-]
+man_pages = [(master_doc, "talkable", "Talkable Documentation", [author], 1)]
 
 # If true, show URL addresses after external links.
-#man_show_urls = False
+# man_show_urls = False

From 6893b6a0e192990a33c106d08196b31269845a4b Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Mon, 27 Jan 2025 22:16:11 +0300
Subject: [PATCH 15/62] rename staging-docs.talkable.com to
 docs.bastion.talkable.com

---
 .env.template            | 2 +-
 README.md                | 6 +++---
 nginx/robots/staging.txt | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/.env.template b/.env.template
index 7d3d25946..4bfe1792a 100644
--- a/.env.template
+++ b/.env.template
@@ -6,5 +6,5 @@ ENVIRONMENT=development
 
 # Base urls used for the canonical urls compilation
 DEVELOPMENT_HOST=localhost
-STAGING_HOST=staging-docs.talkable.com
+STAGING_HOST=docs.bastion.talkable.com
 PRODUCTION_HOST=docs.talkable.com
diff --git a/README.md b/README.md
index ed2a8ba2c..8f88f8b56 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ It's stored in a dedicated GitHub repository ([talkable-docs](https://github.com
 
 The repository consists of the following branches:
 - [master](https://github.com/talkable/talkable-docs/tree/master): The main branch used to keep the most recent stable version available at [docs.talkable.com](https://docs.talkable.com).
-- [staging](https://github.com/talkable/talkable-docs/tree/staging): A staging branch used for testing by QA. It is available at [staging-docs.talkable.com](https://staging-docs.talkable.com).
+- [staging](https://github.com/talkable/talkable-docs/tree/staging): A staging branch used for testing by QA. It is available at [docs.bastion.talkable.com](https://docs.bastion.talkable.com).
 - Feature branches created from `master` by individual contributors/developers.
 
 ## What is the documentation update workflow?
@@ -61,7 +61,7 @@ You should not deploy it manually!
 The deployment is handled by Jenkins jobs. 
 
 All you need to do is commit your changes to the corresponding branch to deploy them to the appropriate server:
-- Commit to the [staging](https://github.com/talkable/talkable-docs/tree/staging) branch => [staging-docs.talkable.com](https://staging-docs.talkable.com/).
+- Commit to the [staging](https://github.com/talkable/talkable-docs/tree/staging) branch => [docs.bastion.talkable.com](https://docs.bastion.talkable.com/).
 - Commit to the [master](https://github.com/talkable/talkable-docs/tree/master) branch => [docs.talkable.com](https://docs.talkable.com/).
 
 ## How do I make the actual changes?
@@ -132,6 +132,6 @@ name "Talkable Section".
 ## Links
 
 - GitHub "staging" branch: [staging](https://github.com/talkable/talkable-docs/tree/staging)
-- Staging web server: [staging-docs.talkable.com](https://staging-docs.talkable.com/)
+- Staging web server: [docs.bastion.talkable.com](https://docs.bastion.talkable.com/)
 - GitHub "production" branch: [master](https://github.com/talkable/talkable-docs/tree/master)
 - Production web server: [docs.talkable.com](https://docs.talkable.com/)
diff --git a/nginx/robots/staging.txt b/nginx/robots/staging.txt
index ed8d11f01..45813aeac 100644
--- a/nginx/robots/staging.txt
+++ b/nginx/robots/staging.txt
@@ -1,4 +1,4 @@
 User-agent: *
 Disallow: /
 
-Sitemap: https://staging-docs.talkable.com/sitemap.xml
+Sitemap: https://docs.bastion.talkable.com/sitemap.xml

From 19a0a87d8ac5d11dcca84a216b99356c1873d88f Mon Sep 17 00:00:00 2001
From: Enver <enver.ablyaev@gmail.com>
Date: Mon, 27 Jan 2025 22:55:12 +0300
Subject: [PATCH 16/62] rename staging-docs.talkable.com to
 docs.bastion.talkable.com (#360)

---
 .env.template            |  2 +-
 README.md                | 24 ++++--------------------
 nginx/robots/staging.txt |  2 +-
 3 files changed, 6 insertions(+), 22 deletions(-)

diff --git a/.env.template b/.env.template
index 7d3d25946..4bfe1792a 100644
--- a/.env.template
+++ b/.env.template
@@ -6,5 +6,5 @@ ENVIRONMENT=development
 
 # Base urls used for the canonical urls compilation
 DEVELOPMENT_HOST=localhost
-STAGING_HOST=staging-docs.talkable.com
+STAGING_HOST=docs.bastion.talkable.com
 PRODUCTION_HOST=docs.talkable.com
diff --git a/README.md b/README.md
index 505e69e69..f89a948fb 100644
--- a/README.md
+++ b/README.md
@@ -13,10 +13,7 @@ It's stored in a dedicated GitHub repository ([talkable-docs](https://github.com
 The repository consists of the following branches:
 
 - [master](https://github.com/talkable/talkable-docs/tree/master): The main branch used to keep the most recent stable version available at [docs.talkable.com](https://docs.talkable.com).
-  <<<<<<< HEAD
-- # [staging-bastion](https://github.com/talkable/talkable-docs/tree/staging-bastion): A staging branch used for testing by QA. It is available at [bastion-docs.talkable.com](https://bastion-docs.talkable.com).
-- [staging](https://github.com/talkable/talkable-docs/tree/staging): A staging branch used for testing by QA. It is available at [staging-docs.talkable.com](https://staging-docs.talkable.com).
-  > > > > > > > vo-PR-23724
+- [staging](https://github.com/talkable/talkable-docs/tree/staging): A staging branch used for testing by QA. It is available at [docs.bastion.talkable.com](https://docs.bastion.talkable.com).
 - Feature branches created from `master` by individual contributors/developers.
 
 ## What is the documentation update workflow?
@@ -38,12 +35,7 @@ The repository consists of the following branches:
 
 1. **Navigate to the repository root directory.**
 
-<<<<<<< HEAD
-Ensure the `docker-compose.yaml` file is located there.
-=======
-Ensure the `docker-compose.yml` file is located there.
-
-> > > > > > > vo-PR-23724
+  Ensure the `docker-compose.yml` file is located there.
 
 2. **Create an `.env` file by copying `.env.template`.**
 
@@ -56,11 +48,7 @@ Ensure the `docker-compose.yml` file is located there.
    Run the command:
 
    ```bash
-   <<<<<<< HEAD
-   docker-compose up -d
-   =======
    docker compose up -d
-   >>>>>>> vo-PR-23724
    ```
 
    If everything is set up correctly, the documentation will be available at [http://localhost:8080](http://localhost:8080). Make sure you use the port number defined in the `.env` file.
@@ -74,11 +62,7 @@ You should not deploy it manually!
 The deployment is handled by Jenkins jobs.
 
 All you need to do is commit your changes to the corresponding branch to deploy them to the appropriate server:
-<<<<<<< HEAD
-
-- # Commit to the [staging-bastion](https://github.com/talkable/talkable-docs/tree/staging-bastion) branch => [bastion-docs.talkable.com](https://bastion-docs.talkable.com/).
-- Commit to the [staging](https://github.com/talkable/talkable-docs/tree/staging) branch => [staging-docs.talkable.com](https://staging-docs.talkable.com/).
-  > > > > > > > vo-PR-23724
+- Commit to the [staging](https://github.com/talkable/talkable-docs/tree/staging) branch => [docs.bastion.talkable.com](https://docs.bastion.talkable.com/).
 - Commit to the [master](https://github.com/talkable/talkable-docs/tree/master) branch => [docs.talkable.com](https://docs.talkable.com/).
 
 ## How do I make the actual changes?
@@ -149,6 +133,6 @@ name "Talkable Section".
 ## Links
 
 - GitHub "staging" branch: [staging](https://github.com/talkable/talkable-docs/tree/staging)
-- Staging web server: [staging-docs.talkable.com](https://staging-docs.talkable.com/)
+- Staging web server: [docs.bastion.talkable.com](https://docs.bastion.talkable.com/)
 - GitHub "production" branch: [master](https://github.com/talkable/talkable-docs/tree/master)
 - Production web server: [docs.talkable.com](https://docs.talkable.com/)
diff --git a/nginx/robots/staging.txt b/nginx/robots/staging.txt
index ed8d11f01..45813aeac 100644
--- a/nginx/robots/staging.txt
+++ b/nginx/robots/staging.txt
@@ -1,4 +1,4 @@
 User-agent: *
 Disallow: /
 
-Sitemap: https://staging-docs.talkable.com/sitemap.xml
+Sitemap: https://docs.bastion.talkable.com/sitemap.xml

From 4095278df515ef527cf993bbe35bfbdfc284092f Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Mon, 27 Jan 2025 23:57:47 +0200
Subject: [PATCH 17/62] deploy on jenkins

---
 .gitignore         |  90 ++++++++++++++++++++++++++++++++++++++
 deploy/Jenkinsfile | 105 +++++++++++++++++++++++++++++++++++++++++++++
 deploy/deploy.sh   |   0
 3 files changed, 195 insertions(+)
 create mode 100644 deploy/Jenkinsfile
 create mode 100755 deploy/deploy.sh

diff --git a/.gitignore b/.gitignore
index c3f20a68f..65a67ae36 100644
--- a/.gitignore
+++ b/.gitignore
@@ -17,3 +17,93 @@ __pycache__
 /build
 /.bundle
 Gemfile.lock
+
+### Intellij+all ###
+# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm and Rider
+# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
+
+# User-specific stuff
+.idea/**/workspace.xml
+.idea/**/tasks.xml
+.idea/**/usage.statistics.xml
+.idea/**/dictionaries
+.idea/**/shelf
+
+# AWS User-specific
+.idea/**/aws.xml
+
+# Generated files
+.idea/**/contentModel.xml
+
+# Sensitive or high-churn files
+.idea/**/dataSources/
+.idea/**/dataSources.ids
+.idea/**/dataSources.local.xml
+.idea/**/sqlDataSources.xml
+.idea/**/dynamic.xml
+.idea/**/uiDesigner.xml
+.idea/**/dbnavigator.xml
+
+# Gradle
+.idea/**/gradle.xml
+.idea/**/libraries
+
+# Gradle and Maven with auto-import
+# When using Gradle or Maven with auto-import, you should exclude module files,
+# since they will be recreated, and may cause churn.  Uncomment if using
+# auto-import.
+# .idea/artifacts
+# .idea/compiler.xml
+# .idea/jarRepositories.xml
+# .idea/modules.xml
+# .idea/*.iml
+# .idea/modules
+# *.iml
+# *.ipr
+
+# CMake
+cmake-build-*/
+
+# Mongo Explorer plugin
+.idea/**/mongoSettings.xml
+
+# File-based project format
+*.iws
+
+# IntelliJ
+out/
+
+# mpeltonen/sbt-idea plugin
+.idea_modules/
+
+# JIRA plugin
+atlassian-ide-plugin.xml
+
+# Cursive Clojure plugin
+.idea/replstate.xml
+
+# SonarLint plugin
+.idea/sonarlint/
+
+# Crashlytics plugin (for Android Studio and IntelliJ)
+com_crashlytics_export_strings.xml
+crashlytics.properties
+crashlytics-build.properties
+fabric.properties
+
+# Editor-based Rest Client
+.idea/httpRequests
+
+# Android studio 3.1+ serialized cache file
+.idea/caches/build_file_checksums.ser
+
+### Intellij+all Patch ###
+# Ignore everything but code style settings and run configurations
+# that are supposed to be shared within teams.
+
+.idea/*
+
+!.idea/codeStyles
+!.idea/runConfigurations
+
+# End of https://www.toptal.com/developers/gitignore/api/intellij+all
diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
new file mode 100644
index 000000000..e8d930eed
--- /dev/null
+++ b/deploy/Jenkinsfile
@@ -0,0 +1,105 @@
+#!/usr/bin/env groovy
+
+// Upgrades or installs nginx containers for WordPress.
+def dockerContainerUpdate(String hostEnv) {
+    sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-helm/Docker/wp-nginx && \
+        git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
+        docker-compose ls && docker ps && \
+        docker-compose down && docker-compose up -d --remove-orphans && \
+        docker-compose ls && docker ps' """
+}
+
+pipeline {
+    agent {
+        label "staging"
+    }
+    environment {
+        GITHUB_ACC = credentials('talkable-bot-deploy-token')
+        JENKINS_BUILD_USER_ID = ""
+//        CHANGESET_REGEXP = "^nginx/.*"
+    }
+    triggers {
+        pollSCM('* * * * *') // Polls SCM every minute
+    }
+    options {
+        buildDiscarder(logRotator(numToKeepStr: '15', daysToKeepStr: '14'))
+        disableConcurrentBuilds()
+        parallelsAlwaysFailFast()
+        ansiColor('xterm')
+    }
+    stages {
+        stage('Preparation') {
+            steps {
+                script {
+                    wrap([$class: 'BuildUser']) {
+                        JENKINS_BUILD_USER_ID = "${BUILD_USER_ID}"
+                        currentBuild.displayName = "${JOB_BASE_NAME}-${BUILD_NUMBER}"
+                        currentBuild.description = "Build by ${JENKINS_BUILD_USER_ID}"
+                    }
+                    if (env.BRANCH_NAME == 'master') {
+                        env.HOST_ENV = '10.200.1.200'
+                        env.JENKINS_CRED_ID = 'ssh-jenkins-to-prod1-wp-nginx'
+                    } else if (env.BRANCH_NAME == 'staging') {
+                        env.HOST_ENV = '10.1.2.12'
+                        env.JENKINS_CRED_ID = 'ssh-jenkins-to-bastion-wp-nginx'
+                    } else {
+                        echo "Hello from ${BRANCH_NAME} branch! We only build the following branches of the Talkable repository: master, staging."
+                        error("Non-supported branch for build")
+                    }
+                }
+            }
+        }
+        stage('Build') {
+            when {
+                beforeAgent true
+                changeset pattern: "${CHANGESET_REGEXP}", comparator: "REGEXP"
+            }
+            steps {
+                script {
+                    withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
+                        dockerContainerUpdate('$HOST_ENV')
+                    }
+                }
+            }
+        }
+        stage('Manual-build') {
+            when {
+                not
+                        {
+                            triggeredBy 'SCMTrigger'
+                        }
+            }
+            steps {
+                script {
+                    withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
+                        dockerContainerUpdate('$HOST_ENV')
+                    }
+                }
+            }
+        }
+    }
+    post {
+        success {
+            echo 'Build was a success'
+        }
+        failure {
+            echo 'Build failed'
+        }
+        unstable {
+            echo 'Build is unstable'
+        }
+        aborted {
+            echo 'Build was aborted'
+        }
+        cleanup {
+            echo 'Performing cleanup'
+            cleanWs cleanWhenFailure: false,
+                    cleanWhenUnstable: true,
+                    cleanWhenAborted: true,
+                    cleanWhenNotBuilt: true,
+                    cleanWhenSuccess: true,
+                    deleteDirs: true,
+                    notFailBuild: true
+        }
+    }
+}
diff --git a/deploy/deploy.sh b/deploy/deploy.sh
new file mode 100755
index 000000000..e69de29bb

From a35a542377b44236a18f952fd04798d2383558b7 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:02:05 +0200
Subject: [PATCH 18/62] deploy on jenkins-2

---
 deploy/Jenkinsfile | 1 -
 1 file changed, 1 deletion(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index e8d930eed..a43a720e4 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -16,7 +16,6 @@ pipeline {
     environment {
         GITHUB_ACC = credentials('talkable-bot-deploy-token')
         JENKINS_BUILD_USER_ID = ""
-//        CHANGESET_REGEXP = "^nginx/.*"
     }
     triggers {
         pollSCM('* * * * *') // Polls SCM every minute

From 962343692ca82acf7de6acc8105ff8f8c6e79653 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:04:15 +0200
Subject: [PATCH 19/62] deploy on jenkins-3

---
 deploy/Jenkinsfile | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index a43a720e4..13d279f2a 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -16,6 +16,7 @@ pipeline {
     environment {
         GITHUB_ACC = credentials('talkable-bot-deploy-token')
         JENKINS_BUILD_USER_ID = ""
+//        CHANGESET_REGEXP = "^nginx/.*"
     }
     triggers {
         pollSCM('* * * * *') // Polls SCM every minute
@@ -49,10 +50,10 @@ pipeline {
             }
         }
         stage('Build') {
-            when {
-                beforeAgent true
-                changeset pattern: "${CHANGESET_REGEXP}", comparator: "REGEXP"
-            }
+//            when {
+//                beforeAgent true
+//                changeset pattern: "${CHANGESET_REGEXP}", comparator: "REGEXP"
+//            }
             steps {
                 script {
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {

From cb35118cbd5cf4c39cb5bbb021992d754121f378 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:05:37 +0200
Subject: [PATCH 20/62] deploy on jenkins-4

---
 deploy/Jenkinsfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 13d279f2a..de078ada8 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -2,7 +2,7 @@
 
 // Upgrades or installs nginx containers for WordPress.
 def dockerContainerUpdate(String hostEnv) {
-    sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-helm/Docker/wp-nginx && \
+    sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
         git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
         docker-compose ls && docker ps && \
         docker-compose down && docker-compose up -d --remove-orphans && \

From 4db2f04eaa145fbb96cdeaf2e5e3d33597c37a51 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:16:20 +0200
Subject: [PATCH 21/62] deploy on jenkins-5

---
 deploy/Jenkinsfile | 5 +++++
 docker-compose.yml | 1 +
 2 files changed, 6 insertions(+)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index de078ada8..650657d6c 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -16,6 +16,7 @@ pipeline {
     environment {
         GITHUB_ACC = credentials('talkable-bot-deploy-token')
         JENKINS_BUILD_USER_ID = ""
+        LOCAL_PORT="8080"
 //        CHANGESET_REGEXP = "^nginx/.*"
     }
     triggers {
@@ -39,9 +40,13 @@ pipeline {
                     if (env.BRANCH_NAME == 'master') {
                         env.HOST_ENV = '10.200.1.200'
                         env.JENKINS_CRED_ID = 'ssh-jenkins-to-prod1-wp-nginx'
+                        env.ENVIRONMENT="production"
+                        env.PRODUCTION_HOST="docs.talkable.com"
                     } else if (env.BRANCH_NAME == 'staging') {
                         env.HOST_ENV = '10.1.2.12'
                         env.JENKINS_CRED_ID = 'ssh-jenkins-to-bastion-wp-nginx'
+                        env.ENVIRONMENT="staging"
+                        env.STAGING_HOST="docs.bastion.talkable.com"
                     } else {
                         echo "Hello from ${BRANCH_NAME} branch! We only build the following branches of the Talkable repository: master, staging."
                         error("Non-supported branch for build")
diff --git a/docker-compose.yml b/docker-compose.yml
index 4a23ddfe9..90e107e3c 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,4 +1,5 @@
 services:
+
   sphinx:
     build:
       context: .

From 272b1395650b193100209a721317482703ae7200 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:19:35 +0200
Subject: [PATCH 22/62] deploy on jenkins-6

---
 deploy/Jenkinsfile | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 650657d6c..ae1bd7784 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -61,6 +61,7 @@ pipeline {
 //            }
             steps {
                 script {
+                    sh 'printenv | sort'
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
                         dockerContainerUpdate('$HOST_ENV')
                     }
@@ -75,6 +76,7 @@ pipeline {
                         }
             }
             steps {
+                sh 'printenv | sort'
                 script {
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
                         dockerContainerUpdate('$HOST_ENV')

From 30af536590184754776060ab4d972038f1d459ab Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:34:08 +0200
Subject: [PATCH 23/62] deploy on jenkins-7

---
 deploy/Jenkinsfile | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index ae1bd7784..7a986545f 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -2,8 +2,15 @@
 
 // Upgrades or installs nginx containers for WordPress.
 def dockerContainerUpdate(String hostEnv) {
+    def envFile = """
+ENVIRONMENT=${env.ENVIRONMENT}
+STAGING_HOST=${env.STAGING_HOST ?: ''}
+PRODUCTION_HOST=${env.PRODUCTION_HOST ?: ''}
+LOCAL_PORT=${env.LOCAL_PORT ?: '8080'}
+"""
     sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
         git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
+        echo "${envFile.trim()}" > .env && \
         docker-compose ls && docker ps && \
         docker-compose down && docker-compose up -d --remove-orphans && \
         docker-compose ls && docker ps' """

From 15ef8f9d004a00e6885009be9402b35ebb537713 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:37:27 +0200
Subject: [PATCH 24/62] deploy on jenkins-8

---
 deploy/Jenkinsfile | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 7a986545f..08dc6cf76 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -6,11 +6,13 @@ def dockerContainerUpdate(String hostEnv) {
 ENVIRONMENT=${env.ENVIRONMENT}
 STAGING_HOST=${env.STAGING_HOST ?: ''}
 PRODUCTION_HOST=${env.PRODUCTION_HOST ?: ''}
+DEVELOPMENT_HOST=${env.DEVELOPMENT_HOST ?: 'localhost'}
 LOCAL_PORT=${env.LOCAL_PORT ?: '8080'}
 """
     sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
         git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
         echo "${envFile.trim()}" > .env && \
+        cat .env && \
         docker-compose ls && docker ps && \
         docker-compose down && docker-compose up -d --remove-orphans && \
         docker-compose ls && docker ps' """

From f58976ec5a90b4df6e8a5a218802958bf09d55c1 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:40:37 +0200
Subject: [PATCH 25/62] deploy on jenkins-9

---
 deploy/Jenkinsfile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 08dc6cf76..87771ed37 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -56,6 +56,7 @@ pipeline {
                         env.JENKINS_CRED_ID = 'ssh-jenkins-to-bastion-wp-nginx'
                         env.ENVIRONMENT="staging"
                         env.STAGING_HOST="docs.bastion.talkable.com"
+                        env.PRODUCTION_HOST="docs.talkable.com"
                     } else {
                         echo "Hello from ${BRANCH_NAME} branch! We only build the following branches of the Talkable repository: master, staging."
                         error("Non-supported branch for build")

From c06d27710a9753ee1733e7c921e69fb30365ce1f Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:46:03 +0200
Subject: [PATCH 26/62] deploy on jenkins-10

---
 deploy/Jenkinsfile |  2 --
 docker-compose.yml | 11 ++++++++---
 2 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 87771ed37..876fd0746 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -6,7 +6,6 @@ def dockerContainerUpdate(String hostEnv) {
 ENVIRONMENT=${env.ENVIRONMENT}
 STAGING_HOST=${env.STAGING_HOST ?: ''}
 PRODUCTION_HOST=${env.PRODUCTION_HOST ?: ''}
-DEVELOPMENT_HOST=${env.DEVELOPMENT_HOST ?: 'localhost'}
 LOCAL_PORT=${env.LOCAL_PORT ?: '8080'}
 """
     sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
@@ -56,7 +55,6 @@ pipeline {
                         env.JENKINS_CRED_ID = 'ssh-jenkins-to-bastion-wp-nginx'
                         env.ENVIRONMENT="staging"
                         env.STAGING_HOST="docs.bastion.talkable.com"
-                        env.PRODUCTION_HOST="docs.talkable.com"
                     } else {
                         echo "Hello from ${BRANCH_NAME} branch! We only build the following branches of the Talkable repository: master, staging."
                         error("Non-supported branch for build")
diff --git a/docker-compose.yml b/docker-compose.yml
index 90e107e3c..33581a98d 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -9,11 +9,16 @@ services:
       - ./source:/docs/source
       - docs_build:/docs/_build
     environment:
-      - ENVIRONMENT=${ENVIRONMENT}
-      - LOCAL_PORT=${LOCAL_PORT}
+      - ENVIRONMENT=staging
+      - LOCAL_PORT=8080
       - PRODUCTION_HOST=${PRODUCTION_HOST}
-      - STAGING_HOST=${STAGING_HOST}
+      - STAGING_HOST=docs.bastion.talkable.com
       - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
+#      - ENVIRONMENT=${ENVIRONMENT}
+#      - LOCAL_PORT=${LOCAL_PORT}
+#      - PRODUCTION_HOST=${PRODUCTION_HOST}
+#      - STAGING_HOST=${STAGING_HOST}
+#      - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
 
   nginx:
     image: nginx:1.27-alpine3.20

From f95ee9ef677ef6446cb344c45d7667ab9a16d8cd Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 00:52:03 +0200
Subject: [PATCH 27/62] deploy on jenkins-11

---
 docker-compose.yml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 33581a98d..53d6b4bd8 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -4,7 +4,7 @@ services:
     build:
       context: .
       dockerfile: Dockerfile
-    container_name: sphinx
+    container_name: docs-sphinx-${ENVIRONMENT}
     volumes:
       - ./source:/docs/source
       - docs_build:/docs/_build
@@ -22,7 +22,7 @@ services:
 
   nginx:
     image: nginx:1.27-alpine3.20
-    container_name: nginx
+    container_name: docs-nginx-${ENVIRONMENT}
     volumes:
       - docs_build:/var/www/html
       - ./nginx/conf.d:/etc/nginx/conf.d
@@ -34,4 +34,4 @@ services:
 
 volumes:
   docs_build:
-    driver: local
+    driver: bridge

From 50c62e339cfece7521d2796e17cce6cda02451f4 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:03:58 +0200
Subject: [PATCH 28/62] deploy on jenkins-11

---
 docker-compose.yml | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 53d6b4bd8..621e42b30 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -5,6 +5,9 @@ services:
       context: .
       dockerfile: Dockerfile
     container_name: docs-sphinx-${ENVIRONMENT}
+    restart: unless-stopped
+    networks:
+      - docs-nginx
     volumes:
       - ./source:/docs/source
       - docs_build:/docs/_build
@@ -21,8 +24,11 @@ services:
 #      - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
 
   nginx:
-    image: nginx:1.27-alpine3.20
+    image: nginx:1.27.3-alpine3.20
     container_name: docs-nginx-${ENVIRONMENT}
+    restart: unless-stopped
+    networks:
+      - docs-nginx
     volumes:
       - docs_build:/var/www/html
       - ./nginx/conf.d:/etc/nginx/conf.d
@@ -30,8 +36,13 @@ services:
     ports:
       - ${LOCAL_PORT}:80
     depends_on:
-      - sphinx
+      - docs-sphinx-${ENVIRONMENT}
 
 volumes:
   docs_build:
+    driver: local
+
+networks:
+  docs-nginx:
+    name: docs-nginx
     driver: bridge

From e6713770f9e65ad7942fb052a99fd0bd96fe3424 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:04:52 +0200
Subject: [PATCH 29/62] deploy on jenkins-14

---
 docker-compose.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 621e42b30..3144905bd 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -36,7 +36,7 @@ services:
     ports:
       - ${LOCAL_PORT}:80
     depends_on:
-      - docs-sphinx-${ENVIRONMENT}
+      - sphinx
 
 volumes:
   docs_build:

From d8d082078b214bc7622a42bc4e9b5fe1692010a0 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:07:47 +0200
Subject: [PATCH 30/62] deploy on jenkins-15

---
 deploy/Jenkinsfile |  8 --------
 docker-compose.yml | 11 +++--------
 2 files changed, 3 insertions(+), 16 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 876fd0746..ae1bd7784 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -2,16 +2,8 @@
 
 // Upgrades or installs nginx containers for WordPress.
 def dockerContainerUpdate(String hostEnv) {
-    def envFile = """
-ENVIRONMENT=${env.ENVIRONMENT}
-STAGING_HOST=${env.STAGING_HOST ?: ''}
-PRODUCTION_HOST=${env.PRODUCTION_HOST ?: ''}
-LOCAL_PORT=${env.LOCAL_PORT ?: '8080'}
-"""
     sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
         git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
-        echo "${envFile.trim()}" > .env && \
-        cat .env && \
         docker-compose ls && docker ps && \
         docker-compose down && docker-compose up -d --remove-orphans && \
         docker-compose ls && docker ps' """
diff --git a/docker-compose.yml b/docker-compose.yml
index 3144905bd..fd8ed9aff 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -12,16 +12,11 @@ services:
       - ./source:/docs/source
       - docs_build:/docs/_build
     environment:
-      - ENVIRONMENT=staging
-      - LOCAL_PORT=8080
+      - ENVIRONMENT=${ENVIRONMENT}
+      - LOCAL_PORT=${LOCAL_PORT}
       - PRODUCTION_HOST=${PRODUCTION_HOST}
-      - STAGING_HOST=docs.bastion.talkable.com
+      - STAGING_HOST=${STAGING_HOST}
       - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
-#      - ENVIRONMENT=${ENVIRONMENT}
-#      - LOCAL_PORT=${LOCAL_PORT}
-#      - PRODUCTION_HOST=${PRODUCTION_HOST}
-#      - STAGING_HOST=${STAGING_HOST}
-#      - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
 
   nginx:
     image: nginx:1.27.3-alpine3.20

From 7ca13031a5d618e2a2958733dfff3878f6b7f3f7 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:11:25 +0200
Subject: [PATCH 31/62] deploy on jenkins-16

---
 deploy/Jenkinsfile | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index ae1bd7784..5f17ff5b6 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -2,8 +2,16 @@
 
 // Upgrades or installs nginx containers for WordPress.
 def dockerContainerUpdate(String hostEnv) {
+    def envFile = """
+ENVIRONMENT=${env.ENVIRONMENT}
+STAGING_HOST=${env.STAGING_HOST ?: ''}
+PRODUCTION_HOST=${env.PRODUCTION_HOST ?: ''}
+LOCAL_PORT=${env.LOCAL_PORT ?: '8080'}
+"""
     sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
         git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
+        echo "${envFile.trim()}" > .env && \
+        cat .env && \
         docker-compose ls && docker ps && \
         docker-compose down && docker-compose up -d --remove-orphans && \
         docker-compose ls && docker ps' """
@@ -61,7 +69,6 @@ pipeline {
 //            }
             steps {
                 script {
-                    sh 'printenv | sort'
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
                         dockerContainerUpdate('$HOST_ENV')
                     }
@@ -76,7 +83,6 @@ pipeline {
                         }
             }
             steps {
-                sh 'printenv | sort'
                 script {
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
                         dockerContainerUpdate('$HOST_ENV')

From 38ae580935ee88e330308964d8fb2be975874631 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:18:40 +0200
Subject: [PATCH 32/62] deploy on jenkins-18

---
 deploy/Jenkinsfile | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 5f17ff5b6..685860bd3 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -2,16 +2,8 @@
 
 // Upgrades or installs nginx containers for WordPress.
 def dockerContainerUpdate(String hostEnv) {
-    def envFile = """
-ENVIRONMENT=${env.ENVIRONMENT}
-STAGING_HOST=${env.STAGING_HOST ?: ''}
-PRODUCTION_HOST=${env.PRODUCTION_HOST ?: ''}
-LOCAL_PORT=${env.LOCAL_PORT ?: '8080'}
-"""
     sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
         git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
-        echo "${envFile.trim()}" > .env && \
-        cat .env && \
         docker-compose ls && docker ps && \
         docker-compose down && docker-compose up -d --remove-orphans && \
         docker-compose ls && docker ps' """
@@ -68,6 +60,7 @@ pipeline {
 //                changeset pattern: "${CHANGESET_REGEXP}", comparator: "REGEXP"
 //            }
             steps {
+                sh "printenv | sort"
                 script {
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
                         dockerContainerUpdate('$HOST_ENV')

From 54de3e51f3171ea5ad22039201faf7a3296899c8 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:23:10 +0200
Subject: [PATCH 33/62] deploy on jenkins-20

---
 deploy/Jenkinsfile | 9 ++++++++-
 docker-compose.yml | 8 ++------
 2 files changed, 10 insertions(+), 7 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 685860bd3..5f17ff5b6 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -2,8 +2,16 @@
 
 // Upgrades or installs nginx containers for WordPress.
 def dockerContainerUpdate(String hostEnv) {
+    def envFile = """
+ENVIRONMENT=${env.ENVIRONMENT}
+STAGING_HOST=${env.STAGING_HOST ?: ''}
+PRODUCTION_HOST=${env.PRODUCTION_HOST ?: ''}
+LOCAL_PORT=${env.LOCAL_PORT ?: '8080'}
+"""
     sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
         git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
+        echo "${envFile.trim()}" > .env && \
+        cat .env && \
         docker-compose ls && docker ps && \
         docker-compose down && docker-compose up -d --remove-orphans && \
         docker-compose ls && docker ps' """
@@ -60,7 +68,6 @@ pipeline {
 //                changeset pattern: "${CHANGESET_REGEXP}", comparator: "REGEXP"
 //            }
             steps {
-                sh "printenv | sort"
                 script {
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
                         dockerContainerUpdate('$HOST_ENV')
diff --git a/docker-compose.yml b/docker-compose.yml
index fd8ed9aff..60c96b465 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -8,15 +8,11 @@ services:
     restart: unless-stopped
     networks:
       - docs-nginx
+    env_file:
+      - ./.env
     volumes:
       - ./source:/docs/source
       - docs_build:/docs/_build
-    environment:
-      - ENVIRONMENT=${ENVIRONMENT}
-      - LOCAL_PORT=${LOCAL_PORT}
-      - PRODUCTION_HOST=${PRODUCTION_HOST}
-      - STAGING_HOST=${STAGING_HOST}
-      - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
 
   nginx:
     image: nginx:1.27.3-alpine3.20

From 242f19977775079b330928429400a640e7e795b2 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:34:26 +0200
Subject: [PATCH 34/62] deploy on jenkins-22

---
 deploy/Jenkinsfile |  8 --------
 docker-compose.yml | 10 ++++++++--
 2 files changed, 8 insertions(+), 10 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 5f17ff5b6..650657d6c 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -2,16 +2,8 @@
 
 // Upgrades or installs nginx containers for WordPress.
 def dockerContainerUpdate(String hostEnv) {
-    def envFile = """
-ENVIRONMENT=${env.ENVIRONMENT}
-STAGING_HOST=${env.STAGING_HOST ?: ''}
-PRODUCTION_HOST=${env.PRODUCTION_HOST ?: ''}
-LOCAL_PORT=${env.LOCAL_PORT ?: '8080'}
-"""
     sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
         git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
-        echo "${envFile.trim()}" > .env && \
-        cat .env && \
         docker-compose ls && docker ps && \
         docker-compose down && docker-compose up -d --remove-orphans && \
         docker-compose ls && docker ps' """
diff --git a/docker-compose.yml b/docker-compose.yml
index 60c96b465..c18c3dac0 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -8,11 +8,17 @@ services:
     restart: unless-stopped
     networks:
       - docs-nginx
-    env_file:
-      - ./.env
+#    env_file:
+#      - ./.env
     volumes:
       - ./source:/docs/source
       - docs_build:/docs/_build
+    environment:
+      - ENVIRONMENT=${ENVIRONMENT}
+      - LOCAL_PORT=${LOCAL_PORT}
+      - PRODUCTION_HOST=${PRODUCTION_HOST}
+      - STAGING_HOST=${STAGING_HOST}
+      - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
 
   nginx:
     image: nginx:1.27.3-alpine3.20

From b133cd888df6d24a96c5f8154c796e61e6543392 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:39:03 +0200
Subject: [PATCH 35/62] deploy on jenkins-23

---
 deploy/Jenkinsfile | 20 --------------------
 1 file changed, 20 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index 650657d6c..b3c807eba 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -17,7 +17,6 @@ pipeline {
         GITHUB_ACC = credentials('talkable-bot-deploy-token')
         JENKINS_BUILD_USER_ID = ""
         LOCAL_PORT="8080"
-//        CHANGESET_REGEXP = "^nginx/.*"
     }
     triggers {
         pollSCM('* * * * *') // Polls SCM every minute
@@ -55,25 +54,6 @@ pipeline {
             }
         }
         stage('Build') {
-//            when {
-//                beforeAgent true
-//                changeset pattern: "${CHANGESET_REGEXP}", comparator: "REGEXP"
-//            }
-            steps {
-                script {
-                    withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
-                        dockerContainerUpdate('$HOST_ENV')
-                    }
-                }
-            }
-        }
-        stage('Manual-build') {
-            when {
-                not
-                        {
-                            triggeredBy 'SCMTrigger'
-                        }
-            }
             steps {
                 script {
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {

From 344157fa67d2a540af95ddbe3a595c6a228f0d3e Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:43:47 +0200
Subject: [PATCH 36/62] deploy on jenkins-23

---
 docker-compose.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docker-compose.yml b/docker-compose.yml
index c18c3dac0..d8ee3e51a 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,6 +1,7 @@
 services:
 
   sphinx:
+    image: talkable-docs-sphinx:${BUILD_ID}
     build:
       context: .
       dockerfile: Dockerfile

From 56eae6cb499f8462469e9a070f645b73ec524429 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 28 Jan 2025 01:45:55 +0200
Subject: [PATCH 37/62] deploy on jenkins-24

---
 docker-compose.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index d8ee3e51a..535e194f0 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,7 +1,7 @@
 services:
 
   sphinx:
-    image: talkable-docs-sphinx:${BUILD_ID}
+    image: talkable-docs-sphinx:${BUILD_ID:-tagname}
     build:
       context: .
       dockerfile: Dockerfile

From 992d40d77cd560ad668134a8031deccd50b82b7e Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 11:25:31 +0300
Subject: [PATCH 38/62] install and run nginx and sphinx within the same
 container

---
 Dockerfile                            |  19 ++++-
 docker-compose.yml                    |  25 +++----
 nginx/{conf.d => http.d}/default.conf |   3 +-
 nginx/nginx.conf                      | 104 ++++++++++++++++++++++++++
 4 files changed, 132 insertions(+), 19 deletions(-)
 rename nginx/{conf.d => http.d}/default.conf (98%)
 create mode 100644 nginx/nginx.conf

diff --git a/Dockerfile b/Dockerfile
index 5dba08b0b..b6aace6c5 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,14 +1,27 @@
 FROM python:3.13-alpine3.21
 
-# Install dependencies
 WORKDIR /docs
+
 ADD requirements.txt /docs
 RUN python3 -m pip install -r requirements.txt
 
+RUN apk add --no-cache \
+    # gcc \
+    # musl-dev \
+    # libffi-dev \
+    # openssl-dev \
+    # make
+    nginx
+
+# Create necessary directories for Nginx
+RUN mkdir -p /run/nginx
+
 CMD if [ "$ENVIRONMENT" = "development" ]; then \
         echo "Running Sphinx in Development mode"; \
-        sphinx-autobuild -b dirhtml /docs/source /docs/_build; \
+        sphinx-autobuild -b dirhtml --port 8000 --host 0.0.0.0 /docs/source /docs/_build; \
     else \
         echo "Running Sphinx in Staging/Production mode"; \
-        sphinx-build -b dirhtml /docs/source /docs/_build; \
+        sphinx-build -b dirhtml /docs/source /var/www/html; \
+        echo "Starting Nginx"; \
+        nginx -g "daemon off;"; \
     fi
diff --git a/docker-compose.yml b/docker-compose.yml
index 4a23ddfe9..c9c2c6241 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,31 +1,26 @@
 services:
-  sphinx:
+  talkable-docs:
     build:
       context: .
       dockerfile: Dockerfile
-    container_name: sphinx
+    container_name: talkable-docs
     volumes:
+      # Sphinx
       - ./source:/docs/source
-      - docs_build:/docs/_build
+      # Nginx
+      - ./nginx/http.d:/etc/nginx/http.d
+      - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro
+      - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
+      # Build volume to keep the docs available
+      - docs_build:/var/www/html
     environment:
       - ENVIRONMENT=${ENVIRONMENT}
       - LOCAL_PORT=${LOCAL_PORT}
       - PRODUCTION_HOST=${PRODUCTION_HOST}
       - STAGING_HOST=${STAGING_HOST}
       - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
-
-  nginx:
-    image: nginx:1.27-alpine3.20
-    container_name: nginx
-    volumes:
-      - docs_build:/var/www/html
-      - ./nginx/conf.d:/etc/nginx/conf.d
-      - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
     ports:
-      - ${LOCAL_PORT}:80
-    depends_on:
-      - sphinx
+      - ${LOCAL_PORT}:8000
 
 volumes:
   docs_build:
-    driver: local
diff --git a/nginx/conf.d/default.conf b/nginx/http.d/default.conf
similarity index 98%
rename from nginx/conf.d/default.conf
rename to nginx/http.d/default.conf
index 5eb1145ca..a01a45c23 100644
--- a/nginx/conf.d/default.conf
+++ b/nginx/http.d/default.conf
@@ -1,5 +1,6 @@
 server {
-    listen 80;
+    
+    listen 8000;
     server_name _;
 
     root /var/www/html; 
diff --git a/nginx/nginx.conf b/nginx/nginx.conf
new file mode 100644
index 000000000..f4a3741b6
--- /dev/null
+++ b/nginx/nginx.conf
@@ -0,0 +1,104 @@
+# /etc/nginx/nginx.conf
+
+user nginx;
+
+# Set number of worker processes automatically based on number of CPU cores.
+worker_processes auto;
+
+# Enables the use of JIT for regular expressions to speed-up their processing.
+pcre_jit on;
+
+# Configures default error logger.
+# error_log /var/log/nginx/error.log warn;
+error_log /dev/stderr info;
+
+# Includes files with directives to load dynamic modules.
+include /etc/nginx/modules/*.conf;
+
+# Include files with config snippets into the root context.
+include /etc/nginx/conf.d/*.conf;
+
+events {
+	# The maximum number of simultaneous connections that can be opened by
+	# a worker process.
+	worker_connections 1024;
+}
+
+http {
+	# Includes mapping of file name extensions to MIME types of responses
+	# and defines the default type.
+	include /etc/nginx/mime.types;
+	default_type application/octet-stream;
+
+	# Name servers used to resolve names of upstream servers into addresses.
+	# It's also needed when using tcpsocket and udpsocket in Lua modules.
+	#resolver 1.1.1.1 1.0.0.1 [2606:4700:4700::1111] [2606:4700:4700::1001];
+
+	# Don't tell nginx version to the clients. Default is 'on'.
+	server_tokens off;
+
+	# Specifies the maximum accepted body size of a client request, as
+	# indicated by the request header Content-Length. If the stated content
+	# length is greater than this size, then the client receives the HTTP
+	# error code 413. Set to 0 to disable. Default is '1m'.
+	client_max_body_size 1m;
+
+	# Sendfile copies data between one FD and other from within the kernel,
+	# which is more efficient than read() + write(). Default is off.
+	sendfile on;
+
+	# Causes nginx to attempt to send its HTTP response head in one packet,
+	# instead of using partial frames. Default is 'off'.
+	tcp_nopush on;
+
+
+	# Enables the specified protocols. Default is TLSv1 TLSv1.1 TLSv1.2.
+	# TIP: If you're not obligated to support ancient clients, remove TLSv1.1.
+	ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
+
+	# Path of the file with Diffie-Hellman parameters for EDH ciphers.
+	# TIP: Generate with: `openssl dhparam -out /etc/ssl/nginx/dh2048.pem 2048`
+	#ssl_dhparam /etc/ssl/nginx/dh2048.pem;
+
+	# Specifies that our cipher suits should be preferred over client ciphers.
+	# Default is 'off'.
+	ssl_prefer_server_ciphers on;
+
+	# Enables a shared SSL cache with size that can hold around 8000 sessions.
+	# Default is 'none'.
+	ssl_session_cache shared:SSL:2m;
+
+	# Specifies a time during which a client may reuse the session parameters.
+	# Default is '5m'.
+	ssl_session_timeout 1h;
+
+	# Disable TLS session tickets (they are insecure). Default is 'on'.
+	ssl_session_tickets off;
+
+
+	# Enable gzipping of responses.
+	#gzip on;
+
+	# Set the Vary HTTP header as defined in the RFC 2616. Default is 'off'.
+	gzip_vary on;
+
+
+	# Helper variable for proxying websockets.
+	map $http_upgrade $connection_upgrade {
+		default upgrade;
+		'' close;
+	}
+
+
+	# Specifies the main log format.
+	log_format main '$remote_addr - $remote_user [$time_local] "$request" '
+			'$status $body_bytes_sent "$http_referer" '
+			'"$http_user_agent" "$http_x_forwarded_for"';
+
+	# Sets the path, format, and configuration for a buffered log write.
+	# access_log /var/log/nginx/access.log main;
+    access_log /dev/stdout;
+
+	# Includes virtual hosts configs.
+	include /etc/nginx/http.d/*.conf;
+}

From 99e7e8772c67c66471bd9724d9c7f2cc1d64e6e1 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 11:42:32 +0300
Subject: [PATCH 39/62] docker compose refactoring

---
 docker-compose.yml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index dbaa8cca4..1293a681b 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -3,7 +3,8 @@ services:
     build:
       context: .
       dockerfile: Dockerfile
-    container_name: talkable-docs
+    container_name: docs-sphinx-${ENVIRONMENT}
+    restart: unless-stopped
     volumes:
       # Sphinx
       - ./source:/docs/source

From 301e3abf5a0e17c455df8b4c5ac27dfb279fb9c0 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 14:41:00 +0300
Subject: [PATCH 40/62] update the readme files to sync with one container
 design (python instead of nginx and python)

---
 README-maintainer.md | 49 +++-----------------------------------------
 README.md            | 12 +++--------
 2 files changed, 6 insertions(+), 55 deletions(-)

diff --git a/README-maintainer.md b/README-maintainer.md
index e9891b437..c53e39e09 100644
--- a/README-maintainer.md
+++ b/README-maintainer.md
@@ -15,7 +15,6 @@ The maintenance routine includes the following tasks:
 
 - Updating dependencies:
   - Sphinx and other Python packages
-  - Nginx container (application server)
   - Python container
 - Adding new extensions
 - Introducing Talkable-specific customizations (Python scripts)
@@ -60,16 +59,10 @@ The goal is to update `requirements.txt` with the latest versions of dependencie
 
     This starts the framework and allows you to load the documentation at http://localhost:8080.
 
-    If the documentation fails to load, check the Sphinx container logs:
+    If the documentation fails to load, check the container logs:
 
     ```bash
-    docker logs -f sphinx
-    ```
-
-    ...and the Nginx logs:
-
-    ```bash
-    docker logs -f nginx
+    docker logs -f docs-sphinx-development
     ```
 
 3. Test and freeze `requirements.txt`.
@@ -83,7 +76,7 @@ The goal is to update `requirements.txt` with the latest versions of dependencie
     Save the dependencies with the following command:
 
     ```bash
-    docker exec sphinx pip freeze > requirements.txt
+    docker exec docs-sphinx-development pip freeze > requirements.txt
     ```
 
 4. Stop the containers.
@@ -98,42 +91,6 @@ The goal is to update `requirements.txt` with the latest versions of dependencie
 
     Commit and push the updated `requirements.txt` for testing and production.
 
-## Updating the Nginx Version
-
-The goal is to update the `docker-compose.yml` file with the latest Nginx image tag.
-
-1. Check the DockerHub Nginx page for newer versions: https://hub.docker.com/_/nginx.
-
-    > **Note:** 
-    >
-    > Use only Alpine-based images.
-
-2. Update the `docker-compose.yml` file with the new version tag:
-
-    ```yaml
-    image: nginx:1.27-alpine3.20
-    ```
-
-3. Deploy the updated image.
-
-    Test the new image:
-
-    ```bash
-    docker compose up -d --build
-    ```
-
-    Verify that the documentation loads at http://localhost:8080.
-
-4. Finalize the update.
-
-    Commit the updated `docker-compose.yml` to the repository for testing and production.
-
-    Stop the containers:
-
-    ```bash
-    docker compose down -v
-    ```
-
 ## Updating the Python Container
 
 The Sphinx framework uses a Python Docker image from DockerHub.
diff --git a/README.md b/README.md
index f89a948fb..1b4939068 100644
--- a/README.md
+++ b/README.md
@@ -48,7 +48,7 @@ The repository consists of the following branches:
    Run the command:
 
    ```bash
-   docker compose up -d
+   docker compose up -d --build
    ```
 
    If everything is set up correctly, the documentation will be available at [http://localhost:8080](http://localhost:8080). Make sure you use the port number defined in the `.env` file.
@@ -118,16 +118,10 @@ name "Talkable Section".
 1. Ensure you are using the correct port number and protocol.
    The port number should match the value provided in `.env` as `LOCAL_PORT`.
 
-2. Check `nginx` logs:
+2. Check logs:
 
    ```bash
-   docker logs -f nginx
-   ```
-
-3. Check `Sphinx` logs:
-
-   ```bash
-   docker logs -f sphinx
+   docker logs -f docs-sphinx-development
    ```
 
 ## Links

From 95a2602fd1d304d235b36ac67217eb1807875253 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 15:44:39 +0300
Subject: [PATCH 41/62] [PR-23789] "empty screen on empty search" fix

---
 nginx/http.d/default.conf | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/nginx/http.d/default.conf b/nginx/http.d/default.conf
index a01a45c23..d282b08a7 100644
--- a/nginx/http.d/default.conf
+++ b/nginx/http.d/default.conf
@@ -56,6 +56,14 @@ server {
         try_files $uri =404;
     }
 
+    # Redirect requests starting with /search/?q=& to /
+    # Fix of the Furo theme bug described here https://talkable.atlassian.net/browse/PR-23789
+    location /search/ {
+        if ($arg_q = "") {
+            return 301 /;
+        }
+    }
+
     # Serve robots.txt from a specific file
     location = /robots.txt {
         alias /var/www/robots.txt;

From 8edf02455c15b21293a174c008228a49a0262152 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 15:56:17 +0300
Subject: [PATCH 42/62] legacy requirements-dev.txt cleanup

---
 requirements-dev.txt | 5 -----
 1 file changed, 5 deletions(-)
 delete mode 100644 requirements-dev.txt

diff --git a/requirements-dev.txt b/requirements-dev.txt
deleted file mode 100644
index 83c514c9d..000000000
--- a/requirements-dev.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-furo
-sphinx-copybutton
-sphinx-sitemap
-sphinx-autobuild
-sphinx-favicon
\ No newline at end of file

From 5755c7e8894a0f5439832168c89cf439b973cd64 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 16:46:30 +0300
Subject: [PATCH 43/62] lists fixes

---
 source/advanced_features/subscribing_to_events.rst  | 6 ++----
 source/advanced_features/tremendous.rst             | 1 -
 source/partials/campaign_placements_description.rst | 7 +++----
 3 files changed, 5 insertions(+), 9 deletions(-)

diff --git a/source/advanced_features/subscribing_to_events.rst b/source/advanced_features/subscribing_to_events.rst
index c90ba5129..61ed5a2c9 100644
--- a/source/advanced_features/subscribing_to_events.rst
+++ b/source/advanced_features/subscribing_to_events.rst
@@ -31,9 +31,8 @@ Knowing the container `name` attribute of the iframe is `talkable-offer-iframe`
   });
 
 Notice two arguments passed in the callback:
-
-  1. `data` object — the data passed by the iframe upon firing the event
-  2. `iframe` object — iframe’s `HTML DOM reference`_
+  - `data` object — the data passed by the iframe upon firing the event
+  - `iframe` object — iframe’s `HTML DOM reference`_
 
 .. _HTML DOM reference: https://www.w3schools.com/jsref/dom_obj_frame.asp
 
@@ -41,7 +40,6 @@ Iframe Events List
 ------------------
 
 Talkable campaigns are equipped with the following set of events:
-
   1. `offer_loaded` — Talkable iframe DOM ready event which is in fact the very first event that you can use to determine if the iframe is loaded.
   2. `responsive_iframe_height` — fires every time iframe size gets changed. You can use it to detect changes in iframe size.
      You can read more :ref:`here <responsive-views>`. Previously named as ``curebit_offer_iframe_broadcast``.
diff --git a/source/advanced_features/tremendous.rst b/source/advanced_features/tremendous.rst
index 1e0fb2a75..2ab74ea04 100644
--- a/source/advanced_features/tremendous.rst
+++ b/source/advanced_features/tremendous.rst
@@ -10,7 +10,6 @@ Tremendous Integration
 Reward advocates with gift cards from various retailers provided by Tremendous.
 
 Tremendous integration consists of several parts:
-
   1. A campaign in Tremendous with the selected rewards for customers.
 
   3. A "Tremendous" application installed from Talkable App Store. This application is responsible
diff --git a/source/partials/campaign_placements_description.rst b/source/partials/campaign_placements_description.rst
index 54a902756..f4a790c0f 100644
--- a/source/partials/campaign_placements_description.rst
+++ b/source/partials/campaign_placements_description.rst
@@ -39,10 +39,9 @@ A Placement can have a set of criteria defined based on :ref:`custom properties
 If all of the criteria are met, the placement will show a campaign.
 
 The criteria can be defined using one of the following operators:
-
-* `eq`
-* `not_eq`
-* `regex` (performs a case-insensitive match)
+  - `eq`
+  - `not_eq`
+  - `regex` (performs a case-insensitive match)
 
 .. note::
   Custom Property Criteria require integration version 5.1.4 or higher to work.

From 9d3883ad88c99b08f7ca62592ccd6acff608ae30 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 18:31:31 +0300
Subject: [PATCH 44/62] [PR-23796] add missing ","

---
 source/partials/purchase_script.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/partials/purchase_script.rst b/source/partials/purchase_script.rst
index c862b358c..82f83745e 100644
--- a/source/partials/purchase_script.rst
+++ b/source/partials/purchase_script.rst
@@ -10,7 +10,7 @@
         coupon_code: '', // Coupon code that was used at checkout (pass multiple as an array). Example: 'SAVE20'
         currency_iso_code: '', // Required for multi-currency sites. Example: 'USD'
         shipping_zip: '', // Used for fraud protection by address. Example: '02222'
-        shipping_address: '' // Full address of the order, make sure to strictly follow a format: 'Apt #, Street address, City, State, ZIP, Country'
+        shipping_address: '', // Full address of the order, make sure to strictly follow a format: 'Apt #, Street address, City, State, ZIP, Country'
         segment1: '', // Segment 1: Represents custom segment (e.g., location, age group, source channel, platform, gender, interests).
         segment2: '', // Segment 2: Represents custom segment (e.g., location, age group, source channel, platform, gender, interests).
         segment3: '', // Segment 3: Represents custom segment (e.g., location, age group, source channel, platform, gender, interests).

From 3f00f08c5b408c5458a04663d2a3b16042c5926c Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 19:30:31 +0300
Subject: [PATCH 45/62] Revert "install and run nginx and sphinx within the
 same container"

This reverts commit 992d40d77cd560ad668134a8031deccd50b82b7e.
---
 Dockerfile                            |  19 +----
 docker-compose.yml                    |  24 +++---
 nginx/{http.d => conf.d}/default.conf |   3 +-
 nginx/nginx.conf                      | 104 --------------------------
 4 files changed, 18 insertions(+), 132 deletions(-)
 rename nginx/{http.d => conf.d}/default.conf (98%)
 delete mode 100644 nginx/nginx.conf

diff --git a/Dockerfile b/Dockerfile
index b6aace6c5..5dba08b0b 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,27 +1,14 @@
 FROM python:3.13-alpine3.21
 
+# Install dependencies
 WORKDIR /docs
-
 ADD requirements.txt /docs
 RUN python3 -m pip install -r requirements.txt
 
-RUN apk add --no-cache \
-    # gcc \
-    # musl-dev \
-    # libffi-dev \
-    # openssl-dev \
-    # make
-    nginx
-
-# Create necessary directories for Nginx
-RUN mkdir -p /run/nginx
-
 CMD if [ "$ENVIRONMENT" = "development" ]; then \
         echo "Running Sphinx in Development mode"; \
-        sphinx-autobuild -b dirhtml --port 8000 --host 0.0.0.0 /docs/source /docs/_build; \
+        sphinx-autobuild -b dirhtml /docs/source /docs/_build; \
     else \
         echo "Running Sphinx in Staging/Production mode"; \
-        sphinx-build -b dirhtml /docs/source /var/www/html; \
-        echo "Starting Nginx"; \
-        nginx -g "daemon off;"; \
+        sphinx-build -b dirhtml /docs/source /docs/_build; \
     fi
diff --git a/docker-compose.yml b/docker-compose.yml
index 1293a681b..b7ec791fd 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,27 +1,31 @@
 services:
-  talkable-docs:
+  sphinx:
     build:
       context: .
       dockerfile: Dockerfile
     container_name: docs-sphinx-${ENVIRONMENT}
     restart: unless-stopped
     volumes:
-      # Sphinx
       - ./source:/docs/source
-      # Nginx
-      - ./nginx/http.d:/etc/nginx/http.d
-      - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro
-      - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
-      # Build volume to keep the docs available
-      - docs_build:/var/www/html
+      - docs_build:/docs/_build
     environment:
       - ENVIRONMENT=${ENVIRONMENT}
       - LOCAL_PORT=${LOCAL_PORT}
       - PRODUCTION_HOST=${PRODUCTION_HOST}
       - STAGING_HOST=${STAGING_HOST}
       - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
+
+  nginx:
+    image: nginx:1.27-alpine3.20
+    container_name: nginx
+    volumes:
+      - docs_build:/var/www/html
+      - ./nginx/conf.d:/etc/nginx/conf.d
+      - ./nginx/robots/${ENVIRONMENT}.txt:/var/www/robots.txt
     ports:
-      - ${LOCAL_PORT}:8000
+      - ${LOCAL_PORT}:80
+    depends_on:
+      - sphinx
 
 volumes:
-  docs_build:
\ No newline at end of file
+  docs_build:
diff --git a/nginx/http.d/default.conf b/nginx/conf.d/default.conf
similarity index 98%
rename from nginx/http.d/default.conf
rename to nginx/conf.d/default.conf
index d282b08a7..5788ccada 100644
--- a/nginx/http.d/default.conf
+++ b/nginx/conf.d/default.conf
@@ -1,6 +1,5 @@
 server {
-    
-    listen 8000;
+    listen 80;
     server_name _;
 
     root /var/www/html; 
diff --git a/nginx/nginx.conf b/nginx/nginx.conf
deleted file mode 100644
index f4a3741b6..000000000
--- a/nginx/nginx.conf
+++ /dev/null
@@ -1,104 +0,0 @@
-# /etc/nginx/nginx.conf
-
-user nginx;
-
-# Set number of worker processes automatically based on number of CPU cores.
-worker_processes auto;
-
-# Enables the use of JIT for regular expressions to speed-up their processing.
-pcre_jit on;
-
-# Configures default error logger.
-# error_log /var/log/nginx/error.log warn;
-error_log /dev/stderr info;
-
-# Includes files with directives to load dynamic modules.
-include /etc/nginx/modules/*.conf;
-
-# Include files with config snippets into the root context.
-include /etc/nginx/conf.d/*.conf;
-
-events {
-	# The maximum number of simultaneous connections that can be opened by
-	# a worker process.
-	worker_connections 1024;
-}
-
-http {
-	# Includes mapping of file name extensions to MIME types of responses
-	# and defines the default type.
-	include /etc/nginx/mime.types;
-	default_type application/octet-stream;
-
-	# Name servers used to resolve names of upstream servers into addresses.
-	# It's also needed when using tcpsocket and udpsocket in Lua modules.
-	#resolver 1.1.1.1 1.0.0.1 [2606:4700:4700::1111] [2606:4700:4700::1001];
-
-	# Don't tell nginx version to the clients. Default is 'on'.
-	server_tokens off;
-
-	# Specifies the maximum accepted body size of a client request, as
-	# indicated by the request header Content-Length. If the stated content
-	# length is greater than this size, then the client receives the HTTP
-	# error code 413. Set to 0 to disable. Default is '1m'.
-	client_max_body_size 1m;
-
-	# Sendfile copies data between one FD and other from within the kernel,
-	# which is more efficient than read() + write(). Default is off.
-	sendfile on;
-
-	# Causes nginx to attempt to send its HTTP response head in one packet,
-	# instead of using partial frames. Default is 'off'.
-	tcp_nopush on;
-
-
-	# Enables the specified protocols. Default is TLSv1 TLSv1.1 TLSv1.2.
-	# TIP: If you're not obligated to support ancient clients, remove TLSv1.1.
-	ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
-
-	# Path of the file with Diffie-Hellman parameters for EDH ciphers.
-	# TIP: Generate with: `openssl dhparam -out /etc/ssl/nginx/dh2048.pem 2048`
-	#ssl_dhparam /etc/ssl/nginx/dh2048.pem;
-
-	# Specifies that our cipher suits should be preferred over client ciphers.
-	# Default is 'off'.
-	ssl_prefer_server_ciphers on;
-
-	# Enables a shared SSL cache with size that can hold around 8000 sessions.
-	# Default is 'none'.
-	ssl_session_cache shared:SSL:2m;
-
-	# Specifies a time during which a client may reuse the session parameters.
-	# Default is '5m'.
-	ssl_session_timeout 1h;
-
-	# Disable TLS session tickets (they are insecure). Default is 'on'.
-	ssl_session_tickets off;
-
-
-	# Enable gzipping of responses.
-	#gzip on;
-
-	# Set the Vary HTTP header as defined in the RFC 2616. Default is 'off'.
-	gzip_vary on;
-
-
-	# Helper variable for proxying websockets.
-	map $http_upgrade $connection_upgrade {
-		default upgrade;
-		'' close;
-	}
-
-
-	# Specifies the main log format.
-	log_format main '$remote_addr - $remote_user [$time_local] "$request" '
-			'$status $body_bytes_sent "$http_referer" '
-			'"$http_user_agent" "$http_x_forwarded_for"';
-
-	# Sets the path, format, and configuration for a buffered log write.
-	# access_log /var/log/nginx/access.log main;
-    access_log /dev/stdout;
-
-	# Includes virtual hosts configs.
-	include /etc/nginx/http.d/*.conf;
-}

From a7ff19b6e812dc39ea47a07df525dc5b7ee76c56 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 19:32:25 +0300
Subject: [PATCH 46/62] add ENVIRONMENT variable to nginx container name

---
 docker-compose.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index b7ec791fd..4c4f50605 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -17,7 +17,7 @@ services:
 
   nginx:
     image: nginx:1.27-alpine3.20
-    container_name: nginx
+    container_name: nginx-${ENVIRONMENT}
     volumes:
       - docs_build:/var/www/html
       - ./nginx/conf.d:/etc/nginx/conf.d

From 2872eb89833a3dd422973202c5da9598f90cd048 Mon Sep 17 00:00:00 2001
From: Vitalii Oliinyk <ilovepinkpony1@gmail.com>
Date: Tue, 28 Jan 2025 18:42:43 +0200
Subject: [PATCH 47/62] [PR-23724]: updated views

---
 .../converting_into_localization.rst          | 65 +++++++++----------
 .../shopify_coupons_auto_apply.rst            | 15 ++---
 .../shopify_coupons_auto_sync.rst             |  6 --
 .../shopify_purchase_syncing.rst              | 10 ++-
 source/advanced_features/single_sign_on.rst   |  1 -
 .../white_labeling/godaddy.rst                | 11 +---
 .../white_labeling/shopify.rst                |  8 +--
 source/android_sdk/api.rst                    | 10 +--
 source/android_sdk/getting_started.rst        |  2 +-
 source/campaigns/editor/partials.rst          | 26 ++++----
 .../campaigns/views/friend_rewards_paid.rst   |  8 +--
 .../campaigns/views/notifier_offers_email.rst |  7 +-
 .../views/notifier_offers_share_via_email.rst |  2 +-
 ...tifier_offers_share_via_email_reminder.rst |  6 +-
 .../custom_app.rst                            |  2 -
 .../klaviyo.rst                               |  1 -
 .../custom/integration_components.rst         |  1 -
 .../ecommerce_platforms/magento/magento1.rst  |  1 -
 .../ecommerce_platforms/magento/magento2.rst  |  7 --
 .../ecommerce_platforms/shopify.rst           | 61 +++--------------
 source/integration/loyalty.rst                |  6 +-
 source/integration/loyalty/custom_app.rst     |  1 -
 .../loyalty/integration_components.rst        |  1 -
 .../loyalty/shopify_integration.rst           | 13 +---
 source/ios_sdk/advanced.rst                   | 37 +++++------
 source/ios_sdk/getting_started.rst            | 23 ++++---
 source/ios_sdk/social_sharing.rst             |  5 +-
 source/web_hooks/check_unsubscribe.rst        |  9 ++-
 source/web_hooks/post_share.rst               | 20 ++----
 29 files changed, 132 insertions(+), 233 deletions(-)

diff --git a/source/advanced_features/converting_into_localization.rst b/source/advanced_features/converting_into_localization.rst
index da30f6484..d6de47f44 100644
--- a/source/advanced_features/converting_into_localization.rst
+++ b/source/advanced_features/converting_into_localization.rst
@@ -10,7 +10,6 @@ Converting Into Localization
 If you don’t know what is Localization inside Talkable :ref:`read this article <campaigns/localization>`.
 
 Few benefits you get out of using Localizations:
-
   1. It is extremely easy to set up an AB test if your copy is coded up as a Localization.
   2. For non-technical people it is easier to change the copy inside Localization Editor because they are afraid to code.
 
@@ -66,23 +65,23 @@ It is highly unlikely that your campaign is not equipped with Subject line as a
 
 Subject line is unique because its default value is set on the Advocate Signup/Share Page along with other email sharing fields (email body, reminder checkbox value), not Friend Share email as it might sounded logical. Here is the plan:
 
-  1. Create Subject Line as a Localization on the Advocate Signup/Share Page, provide its default value, it will be used inside `value` attribute of the "subject" form field:
+1. Create Subject Line as a Localization on the Advocate Signup/Share Page, provide its default value, it will be used inside `value` attribute of the "subject" form field:
 
-    .. image:: /_static/img/advanced_features/subject_line_setup_inside_share_page.png
+   .. image:: /_static/img/advanced_features/subject_line_setup_inside_share_page.png
 
-    .. code-block:: html
+   .. code-block:: html
 
       <input name="email_subject" type="text" class="textfield" value="{{ 'friend_share_email_subject' | localize: 'Your friend [[ advocate_info.first_name ]] [[ advocate_info.last_name ]] gave you [[ friend_incentive.description ]]' | replace: '   ', ' ' | replace: '  ', ' ' }}" />
 
-    This code creates new Localization named "Friend share email subject" that you are able to change on the Advocate Signup/Share Page.
+  This code creates new Localization named "Friend share email subject" that you are able to change on the Advocate Signup/Share Page.
 
-  2. Navigate to Friend Share email → Extra fields to see Email Subject field:
+2. Navigate to Friend Share email → Extra fields to see Email Subject field:
 
-    .. image:: /_static/img/advanced_features/campaign_editor_subject.png
+   .. image:: /_static/img/advanced_features/campaign_editor_subject.png
 
-  3. Put the following code in there:
+3. Put the following code in there:
 
-    .. code-block:: liquid
+   .. code-block:: liquid
 
       {% if custom_message_subject == blank %}
         {{ 'friend_share_email_subject' | localize }}
@@ -90,20 +89,20 @@ Subject line is unique because its default value is set on the Advocate Signup/S
         {{ custom_message_subject }}
       {% endif %}
 
-    The code snippet above checks if the Advocate provided any Subject at all. If not we take default Subject copy so Friend Share email does not come with a blank subject.
+  The code snippet above checks if the Advocate provided any Subject at all. If not we take default Subject copy so Friend Share email does not come with a blank subject.
 
 Color As Localization
 ---------------------
 
 Another example would be localizing font color of a headline, all copy at once, or a background color of a button. You can use `color` trait of a Localization for that.
 
-  1. Navigate to HTML & CSS editor of the View you want to add a color Localization on:
+1. Navigate to HTML & CSS editor of the View you want to add a color Localization on:
 
-    .. image:: /_static/img/advanced_features/campaign_navigation_html_css_editor.png
+   .. image:: /_static/img/advanced_features/campaign_navigation_html_css_editor.png
 
-  2. At the very bottom of the HTML area add ``<style></style>`` tag with CSS that will override default styling of the element you want to localize:
+2. At the very bottom of the HTML area add ``<style></style>`` tag with CSS that will override default styling of the element you want to localize:
 
-    .. code-block:: text
+   .. code-block:: text
 
       .button {
         background-color: {{ "advocate_share_page_button_color" | localize: "#f94d08", trait: "color" }};
@@ -112,22 +111,22 @@ Another example would be localizing font color of a headline, all copy at once,
 
     In the code example above we created new Color Localization with default HEX color `#f94d08` which is used for `background-color` and `border-color` CSS properties of `.button` selector. Whenever you set a new color inside Campaign Editor it will be changed across both places because we’re using the same Localization identifier in both places.
 
-  3. New Color Localization appears under "Color" tab inside Campaign Editor:
+3. New Color Localization appears under "Color" tab inside Campaign Editor:
 
-    .. image:: /_static/img/advanced_features/editor_colors_tab.png
+   .. image:: /_static/img/advanced_features/editor_colors_tab.png
 
 Image As Localization
 ---------------------
 
 Localizing Image asset can be handy if you want to AB test it. Here is how to do that:
 
-  1. Navigate to HTML & CSS editor of the View you want to add a color Localization on:
+1. Navigate to HTML & CSS editor of the View you want to add a color Localization on:
 
-    .. image:: /_static/img/advanced_features/campaign_navigation_html_css_editor.png
+   .. image:: /_static/img/advanced_features/campaign_navigation_html_css_editor.png
 
-  2. Inside HTML area find an image you want to localize. An image can be either within CSS or within HTML area (`<img />`, inline styles, etc.). If the image is set within CSS you need to extract it into HTML area using inline styles:
+2. Inside HTML area find an image you want to localize. An image can be either within CSS or within HTML area (`<img />`, inline styles, etc.). If the image is set within CSS you need to extract it into HTML area using inline styles:
 
-    .. code-block:: text
+   .. code-block:: text
 
       <div class="container" style="background-image: url('{{ "share_page_background" | localize: "share-page-background.jpg", trait: "asset" }}');">
         ...
@@ -135,9 +134,9 @@ Localizing Image asset can be handy if you want to AB test it. Here is how to do
 
     In the example above `share_page_background` is a name of an Image Localization. `share-page-background.jpg` is a name of an Asset (Files tab within HTML & CSS Editor).
 
-  3. Now we can see newly created Image Localization under "Images" tab:
+3. Now we can see newly created Image Localization under "Images" tab:
 
-    .. image:: /_static/img/advanced_features/editor_images_tab.png
+   .. image:: /_static/img/advanced_features/editor_images_tab.png
 
 Custom Option (Configuration) Localization
 ------------------------------------------
@@ -146,17 +145,17 @@ In addition to localizing Images, Colors, and static copy Talkable allows you to
 
 An example can be to create an AB test for Equal Emphasis (all 3 sharing channels look visually equal) vs. Email Emphasis where email sharing form stands out:
 
-  .. image:: /_static/img/advanced_features/share_page_equal_emphasis.png
-    :height: 250 px
+   .. image:: /_static/img/advanced_features/share_page_equal_emphasis.png
+      :height: 250 px
 
-  .. image:: /_static/img/advanced_features/share_page_email_emphasis.png
-    :height: 250 px
+   .. image:: /_static/img/advanced_features/share_page_email_emphasis.png
+      :height: 250 px
 
 In order to chieve this AB test we need to
 
-  1. Build two separate layouts using CSS cascades to style all nested children within a container block that holds all the content:
+1. Build two separate layouts using CSS cascades to style all nested children within a container block that holds all the content:
 
-    .. code-block:: text
+   .. code-block:: text
 
       {% assign share_page_layout = "share_page_layout" | localize: "Equal Emphasis", "Email Emphasis" %}
       <div class="container is-{{ share_page_layout | downcase | split: " " | join: "-" }}">
@@ -166,13 +165,13 @@ In order to chieve this AB test we need to
     The code above creates a local Liquid variable named `share_page_layout` and assigns `share_page_layout` Configuration Localization to it.
     Then we optimize the variable value to be set as an HTML `class` attribute (downcase, replace spaces with hyphens) and set it as a part of a `class` attribute.
 
-  2. Now inside Campaign Editor we can see newly created Configuration Localization:
+2. Now inside Campaign Editor we can see newly created Configuration Localization:
 
-    .. image:: /_static/img/advanced_features/editor_configuration_tab.png
+   .. image:: /_static/img/advanced_features/editor_configuration_tab.png
 
-  3. Let’s switch back to HTML & CSS editor and start applying CSS styling to both layouts. Knowing their final classes inside HTML: `class="container is-equal-emphasis"` and `class="container is-email-emphasis"` we can easily style both layouts inside CSS area like so (SCSS is also allowed and is shown as an example for code simplicity):
+3. Let’s switch back to HTML & CSS editor and start applying CSS styling to both layouts. Knowing their final classes inside HTML: `class="container is-equal-emphasis"` and `class="container is-email-emphasis"` we can easily style both layouts inside CSS area like so (SCSS is also allowed and is shown as an example for code simplicity):
 
-    .. code-block:: scss
+   .. code-block:: scss
 
       .container {
         &.is-equal-emphasis {
@@ -190,4 +189,4 @@ In order to chieve this AB test we need to
 
     All other nested children can be styled following this pattern.
 
-  4. Once you’re done with styling it is very easy to set up an AB test, just go back to Campaign Editor and click "Add A/B test variant" link. Once a Campaign goes Live it will start rotating both variants following AB test distribution rules (50:50 by default).
+4. Once you’re done with styling it is very easy to set up an AB test, just go back to Campaign Editor and click "Add A/B test variant" link. Once a Campaign goes Live it will start rotating both variants following AB test distribution rules (50:50 by default).
diff --git a/source/advanced_features/shopify_coupons_auto_apply.rst b/source/advanced_features/shopify_coupons_auto_apply.rst
index 5bf06ebd3..53b72d54e 100644
--- a/source/advanced_features/shopify_coupons_auto_apply.rst
+++ b/source/advanced_features/shopify_coupons_auto_apply.rst
@@ -44,16 +44,11 @@ This method involves including the discount code in the URL. This way, when a cu
      :class: is-minimal
 
    **Breakdown:**
-
-     - `{{ site_setup.url }}/discount/{{ coupon.code }}`: This applies the coupon code to the cart.
-
-     - `?redirect={{ site_setup.url }}`: This redirects the customer back to your store.
-
-     - `&utm_source=talkable&utm_medium={{ sharing_channel }}&utm_content={{ campaign_setup.name | encode_query_argument }}&utm_campaign={{ campaign_setup.id }}`: These are default UTM parameters used for tracking.
-
-     - `&tkbl_cvuuid={{ visitor_uuid }}&talkable_visitor_offer_id={{ friend_offer.id }}`: These parameters are specific to Talkable, to identify customer.
-
-     - `{% if coupon.code %}{% endif %}` - condition to check if we have coupon.
+    - `{{ site_setup.url }}/discount/{{ coupon.code }}`: This applies the coupon code to the cart.
+    - `?redirect={{ site_setup.url }}`: This redirects the customer back to your store.
+    - `&utm_source=talkable&utm_medium={{ sharing_channel }}&utm_content={{ campaign_setup.name | encode_query_argument }}&utm_campaign={{ campaign_setup.id }}`: These are default UTM parameters used for tracking.
+    - `&tkbl_cvuuid={{ visitor_uuid }}&talkable_visitor_offer_id={{ friend_offer.id }}`: These parameters are specific to Talkable, to identify customer.
+    - `{% if coupon.code %}{% endif %}` - condition to check if we have coupon.
 
 #. **Advocate destination URL:**
 
diff --git a/source/advanced_features/shopify_coupons_auto_sync.rst b/source/advanced_features/shopify_coupons_auto_sync.rst
index 961a3727b..a4e7cf9c9 100644
--- a/source/advanced_features/shopify_coupons_auto_sync.rst
+++ b/source/advanced_features/shopify_coupons_auto_sync.rst
@@ -113,17 +113,11 @@ Shopify Price Rule Changed Email Notification
 If you modify a Price Rules on Shopify, it could make them incompatible with the coupon lists they are attached to. In order to find out about such changes as early as possible, we have a daily monitoring job that checks that Price Rules have no critical differences from respective coupon lists.
 
 Attributes that are checked in this job are the following:
-
   - `allocation_method` - must always be "across"
-
   - `usage_limit` - must always be 1
-
   - `value` - must correspond to coupon list amount
-
   - `value_type` - must correspond to coupon list type
-
   - `ends_at` - must be greater than or equal to coupon list expiration (and absent if coupon list has no expiration)
-
   - `prerequisite_subtotal_range` - must match coupon list minimum subtotal
 
 If any of these attributes differ from what they are expected to be and Talkable cannot fix that by updating a coupon list (see **Coupon list sync**), Talkable sends an email notification.
diff --git a/source/advanced_features/shopify_purchase_syncing.rst b/source/advanced_features/shopify_purchase_syncing.rst
index 54c46bf0b..0d32c5daf 100644
--- a/source/advanced_features/shopify_purchase_syncing.rst
+++ b/source/advanced_features/shopify_purchase_syncing.rst
@@ -63,10 +63,8 @@ In this setup Purchase Syncing is just ensuring that attributes passed with Java
 and notifies Talkable Integrations team in case it is not.
 
 Here is detailed explanation of this logic:
+   - Purchase Syncing tries to find Purchase in Talkable by Order Number (Shopify Purchase ID).
+   - If there is no such Purchase, the one will be registered with attributes described in `Shopify Webhook payload and Talkable Purchase attributes mapping`
+   - If such Purchase exists, Purchase Syncing compares **Email** and **Subtotal** with Shopify Webhook payload.
 
-  - Purchase Syncing tries to find Purchase in Talkable by Order Number (Shopify Purchase ID).
-
-  - If there is no such Purchase, the one will be registered with attributes described in `Shopify Webhook payload and Talkable Purchase attributes mapping`
-
-  - If such Purchase exists, Purchase Syncing compares **Email** and **Subtotal** with Shopify Webhook payload.
-    In case these attributes differ, Talkable Integrations team will is notified. Otherwise, nothing happens and the existing Purchase data is kept unmodified.
+In case these attributes differ, Talkable Integrations team will is notified. Otherwise, nothing happens and the existing Purchase data is kept unmodified.
diff --git a/source/advanced_features/single_sign_on.rst b/source/advanced_features/single_sign_on.rst
index a29e3fea0..5f6ba27a8 100644
--- a/source/advanced_features/single_sign_on.rst
+++ b/source/advanced_features/single_sign_on.rst
@@ -63,7 +63,6 @@ Manual Configuration
 Uncheck the box for “Automatically Configure from Metadata”.
 
 Fill in the following fields:
-
   * IdP Issuer (Entity ID)
   * IdP SSO Target URL
   * X.509 Certificate OR Certificate Fingerprint
diff --git a/source/advanced_features/white_labeling/godaddy.rst b/source/advanced_features/white_labeling/godaddy.rst
index b9f76bc66..c55ba215e 100644
--- a/source/advanced_features/white_labeling/godaddy.rst
+++ b/source/advanced_features/white_labeling/godaddy.rst
@@ -7,15 +7,8 @@ Adding DNS records in GoDaddy
 =============================
 
 .. note::
-
-  The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
-
-`GoDaddy docs <https://www.godaddy.com/help/manage-dns-records-680>`_
-
-.. note::
-  This instruction applies to domains that have GoDaddy name servers.
-  If you purchased a GoDaddy domain, but use other service's name servers,
-  you should add DNS records in the name server account.
+  - The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain. `GoDaddy docs <https://www.godaddy.com/help/manage-dns-records-680>`_
+  - This instruction applies to domains that have GoDaddy name servers. If you purchased a GoDaddy domain, but use other service's name servers, you should add DNS records in the name server account.
 
 #. Click **My Account** → **Domains**.
 
diff --git a/source/advanced_features/white_labeling/shopify.rst b/source/advanced_features/white_labeling/shopify.rst
index 1d1fc3d79..5d2423f17 100644
--- a/source/advanced_features/white_labeling/shopify.rst
+++ b/source/advanced_features/white_labeling/shopify.rst
@@ -7,12 +7,8 @@ Adding DNS records in Shopify
 =============================
 
 .. note::
-  The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
-
-.. note::
-  This instruction applies to domains that are transferred to Shopify
-  or registered there in the first place.
-  Third-party domains connected to Shopify should be managed in respective domain registries.
+  - The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
+  - This instruction applies to domains that are transferred to Shopify or registered there in the first place. Third-party domains connected to Shopify should be managed in respective domain registries.
 
 For delegated setup,
 
diff --git a/source/android_sdk/api.rst b/source/android_sdk/api.rst
index a5edb9049..e99f5d30e 100644
--- a/source/android_sdk/api.rst
+++ b/source/android_sdk/api.rst
@@ -13,7 +13,7 @@ Create visitor
 It’s the simplest method. You don’t need anything to create `Visitor`.
 But you can do anything you need with just create one.
 
-  .. code-block:: java
+.. code-block:: java
 
     import com.talkable.sdk.TalkableApi;
 
@@ -39,10 +39,10 @@ You need to build `Origin` to create. There are three subclasses of this class.
 Hierarchy
 .........
 
-    * `Origin` (Abstract)
-        * `AffiliateMember`
-        * `Event`
-            * `Purchase`
+* `Origin` (Abstract)
+    * `AffiliateMember`
+    * `Event`
+        * `Purchase`
 
 Building Origin
 ...............
diff --git a/source/android_sdk/getting_started.rst b/source/android_sdk/getting_started.rst
index ce223f268..1e40be602 100644
--- a/source/android_sdk/getting_started.rst
+++ b/source/android_sdk/getting_started.rst
@@ -113,7 +113,7 @@ Installation
 Here is an example of ``AndroidManifest.xml`` file (with ``"demo-site"`` site
 ID) you should setup after steps above:
 
-  .. code-block:: xml
+.. code-block:: xml
 
     <?xml version="1.0" encoding="utf-8"?>
     <manifest xmlns:android="http://schemas.android.com/apk/res/android"
diff --git a/source/campaigns/editor/partials.rst b/source/campaigns/editor/partials.rst
index 0d5b18853..c2015b47d 100644
--- a/source/campaigns/editor/partials.rst
+++ b/source/campaigns/editor/partials.rst
@@ -19,11 +19,11 @@ To add a new Liquid partial, follow these steps:
 1. **Navigate to the Partials modal**: Navigate to the HTML & CSS section of the Editor. Click on the `Partials` button.
 2. **Create a Partial**: Click on the `Create Partial` button. This will open a new form where you can define your partial.
 
-  - **Name**: Provide a unique name for your partial. This name will be used to reference the partial in your main templates. The name could be separated by underscores.
-  - **Type**: Select the type of content you want to include in your partial. This can be either `HTML` or `CSS`. The content of the partial will be rendered as HTML or CSS based on the type you select.
-  - **Insert to current position**: This option will insert the partial at the current cursor position in the editor.
+   - **Name**: Provide a unique name for your partial. This name will be used to reference the partial in your main templates. The name could be separated by underscores.
+   - **Type**: Select the type of content you want to include in your partial. This can be either `HTML` or `CSS`. The content of the partial will be rendered as HTML or CSS based on the type you select.
+   - **Insert to current position**: This option will insert the partial at the current cursor position in the editor.
 
-  .. image:: /_static/img/editor/partial-modal.png
+   .. image:: /_static/img/editor/partial-modal.png
 
 Including a Partial in a Main Template
 ======================================
@@ -43,19 +43,19 @@ Here is an example of how to create and use a Liquid partial:
 
 1. **Create a Partial**:
 
-  - **Name**: `header`
-  - **Type**: `HTML`
-  - **Content**:
+   - **Name**: `header`
+   - **Type**: `HTML`
+   - **Content**:
 
-    .. code-block:: liquid
+   .. code-block:: liquid
 
-      <header>
-        <h1>{{ site.title }}</h1>
-      </header>
+    <header>
+      <h1>{{ site.title }}</h1>
+    </header>
 
 2. **Render the Partial in a Main Template**:
 
-  .. code-block:: liquid
+   .. code-block:: liquid
 
     <body>
       {% render 'header' %}
@@ -66,7 +66,7 @@ Here is an example of how to create and use a Liquid partial:
 
 3. **Variables assigned using variable tags can be passed to a template by listing them as parameters on the render tag**:
 
-  .. code-block:: liquid
+   .. code-block:: liquid
 
     {% assign my_variable = 'apples' %}
     {% render 'header', my_variable: my_variable, my_other_variable: 'oranges' %}
diff --git a/source/campaigns/views/friend_rewards_paid.rst b/source/campaigns/views/friend_rewards_paid.rst
index 39d1caa47..bdacd94a1 100644
--- a/source/campaigns/views/friend_rewards_paid.rst
+++ b/source/campaigns/views/friend_rewards_paid.rst
@@ -48,10 +48,10 @@ By default is sent immediately after the reward is created, but can be delayed b
 
 Main email sending criteria (unable to change):
 
-- The Email **will not** be sent only if all three conditions meet:
+1. The Email **will not** be sent only if all three conditions meet:
 
-  1. Reward type is Click
-  2. ‘Allow coupon in the Friend Share Email' is enabled inside Campaign Rules
-  3. Friend Share Email is already sent
+   1. Reward type is Click
+   2. ‘Allow coupon in the Friend Share Email' is enabled inside Campaign Rules
+   3. Friend Share Email is already sent
 
 In all other scenarious the email will be sent immediately unless delayed by configuration.
diff --git a/source/campaigns/views/notifier_offers_email.rst b/source/campaigns/views/notifier_offers_email.rst
index 9710305b4..fbfbb5e17 100644
--- a/source/campaigns/views/notifier_offers_email.rst
+++ b/source/campaigns/views/notifier_offers_email.rst
@@ -31,9 +31,10 @@ By default is sent immediately after the offer is created, but can be delayed by
 
 1. Talkable creates an offer based on the following criteria:
 
-  - Purchase creation
-  - Affiliate member signup. |advocate| can sign up manually by entering their email, or their email is passed via JS integration (or URL). For example, a customer signs up to refer-a-friend on a /share page. This triggers an affiliate member signup.
+   1. Purchase creation
+   2. Purchase creation
+   3. Affiliate member signup. |advocate| can sign up manually by entering their email, or their email is passed via JS integration (or URL). For example, a customer signs up to refer-a-friend on a /share page. This triggers an affiliate member signup.
 
 2. Main email sending criteria (unable to change):
 
-  - If |advocate| offer is active
+   1. If |advocate| offer is active
diff --git a/source/campaigns/views/notifier_offers_share_via_email.rst b/source/campaigns/views/notifier_offers_share_via_email.rst
index 82bddbb88..887c90841 100644
--- a/source/campaigns/views/notifier_offers_share_via_email.rst
+++ b/source/campaigns/views/notifier_offers_share_via_email.rst
@@ -35,4 +35,4 @@ By default is sent immediately after the offer is shared, but can be delayed by
 
 1. Main email sending criteria (unable to change):
 
-  - Only one email for recipient with the same offer (if |advocate| shares twice with one |friend| Talkable sends only one share email)
+   1. Only one email for recipient with the same offer (if |advocate| shares twice with one |friend| Talkable sends only one share email)
diff --git a/source/campaigns/views/notifier_offers_share_via_email_reminder.rst b/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
index 28bbfd889..3c02522e5 100644
--- a/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
+++ b/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
@@ -33,6 +33,6 @@ By default the email is sent in 72 hours after the offer is shared.
 
 1. Main email sending criteria (unable to change):
 
-  - If |friend| offer is active
-  - Recipient (|friend|) was not referred by this offer yet
-  - Current offer is the last one shared with the recipient (if were delayed few reminders Talkable sends the last one)
+   1. If |friend| offer is active
+   2. Recipient (|friend|) was not referred by this offer yet
+   3. Current offer is the last one shared with the recipient (if were delayed few reminders Talkable sends the last one)
diff --git a/source/email_marketing_and_automation/custom_app.rst b/source/email_marketing_and_automation/custom_app.rst
index 3f95d1362..5b3e81c77 100644
--- a/source/email_marketing_and_automation/custom_app.rst
+++ b/source/email_marketing_and_automation/custom_app.rst
@@ -42,9 +42,7 @@ To verify the signature, you should complete the following steps:
   Create a JSON string from the payload of the request.
 
 **2. Determine the expected signature**
-
   - Compute an hex encoded **HMAC** with the **SHA256** hash function. Use the **Webhook security key** as a key, and use the `payload_json` string as a message.
-
   - Encode a computed hash with **Base64**
 
 Your Talkable **Webhook security key** can be found in the Webhook set up page by navigating to **Menu** then **Webhooks**.
diff --git a/source/email_marketing_and_automation/klaviyo.rst b/source/email_marketing_and_automation/klaviyo.rst
index 2a3ac830a..b72f7dabd 100644
--- a/source/email_marketing_and_automation/klaviyo.rst
+++ b/source/email_marketing_and_automation/klaviyo.rst
@@ -10,7 +10,6 @@ Klaviyo
 With ESP apps clients can synchronize emails that Talkable acquires with their ESP. Here are the conditions when Talkable acquires emails:
 
 1. Advocate signs up and opts in for Talkable marketing emails:
-
   .. image:: /_static/img/email_marketing_and_automation/subscribe.png
     :alt: Subscribe
 
diff --git a/source/integration/custom/integration_components.rst b/source/integration/custom/integration_components.rst
index 6e62e8e49..25971f9e3 100644
--- a/source/integration/custom/integration_components.rst
+++ b/source/integration/custom/integration_components.rst
@@ -15,7 +15,6 @@ Talkable is composed of the following components:
    that spans every page. All other integration components are dependent on the Init script.
 
    **Data Capture.** The Initialization Script should pass variables for logged in users:
-
     - Email
     - Phone Number
     - First Name
diff --git a/source/integration/ecommerce_platforms/magento/magento1.rst b/source/integration/ecommerce_platforms/magento/magento1.rst
index 288865c57..57b87b8b0 100644
--- a/source/integration/ecommerce_platforms/magento/magento1.rst
+++ b/source/integration/ecommerce_platforms/magento/magento1.rst
@@ -53,7 +53,6 @@ integration. The extension currently supports Magento versions 1.5+
   <h2>Troubleshooting</h2>
 
 In case you cannot find Talkable extension in the sidebar try clearing cache:
-
    * In Admin Panel, go to **System** → **Cache Management**.
    * Click **Flush Magento Cache**.
    * Then click **Select All**, select action *"Refresh"* and click **Submit**.
diff --git a/source/integration/ecommerce_platforms/magento/magento2.rst b/source/integration/ecommerce_platforms/magento/magento2.rst
index e73367985..7b420312e 100644
--- a/source/integration/ecommerce_platforms/magento/magento2.rst
+++ b/source/integration/ecommerce_platforms/magento/magento2.rst
@@ -35,19 +35,16 @@ Installation
    This guide shows example outputs for Terminal, but these steps can be modified for any command line tool of your choice.
 
 3. Run the following command to access the latest version of the Talkable extension.
-
     .. code-block:: bash
 
       composer require talkable/magento2-integration
 
 4. Run the following command to enable the Talkable extension you just downloaded:
-
     .. code-block:: bash
 
       php bin/magento module:enable Talkable_Integration --clear-static-content
 
    You should see the following output:
-
     .. code-block::
 
       The following modules have been enabled:
@@ -60,13 +57,11 @@ Installation
       Generated static view files cleared successfully.
 
 5. As displayed in the sample output, you must now enable any additional modules. Run the following command to enable them:
-
     .. code-block:: bash
 
       php bin/magento setup:upgrade
 
 6. To ensure that the CSS and JS on your Magento 2 store continues to work properly, you’ll need to run a static content deploy command.
-
     .. code-block:: bash
 
       php bin/magento setup:static-content:deploy -f
@@ -94,7 +89,6 @@ Configuring Talkable Extension
 ------------------------------
 
 The extension configuration screen consists of three sections: Integration_, Campaigns_ and `Page URLs`_.
-
    .. image:: /_static/img/magento2/configure1.jpg
 
 |page_break|
@@ -104,7 +98,6 @@ Integration
 
 The Integration section allows you to change the Talkable Site ID, which is used to connect your store
 to your Talkable account.
-
    .. image:: /_static/img/magento2/configure2.jpg
 
 .. warning::
diff --git a/source/integration/ecommerce_platforms/shopify.rst b/source/integration/ecommerce_platforms/shopify.rst
index 01b1604d3..e36b8f817 100644
--- a/source/integration/ecommerce_platforms/shopify.rst
+++ b/source/integration/ecommerce_platforms/shopify.rst
@@ -12,8 +12,7 @@ Shopify Integration
 Automatic integration
 ---------------------
 
-  .. note::
-
+.. note::
     If you have previously integrated with Talkable, make sure you remove the manual
     Talkable integration script located in the Additional Content & Scripts section before
     you start the Automatic integration process. See `Manual integration`_ for details.
@@ -29,8 +28,7 @@ Automatic integration
 5. Create, set up, and launch Campaigns (Invite, Advocate Dashboard, etc.)
 6. Verify your integration using :ref:`Verifying Integration instructions <integration/verify>`
 
-  .. note::
-
+.. note::
     Post Purchase campaign is located at the “Thank you” page after Checkout.
 
     To check how Standalone Campaign looks visit */pages/share* or */pages/invite* links of your store.
@@ -55,7 +53,6 @@ please follow the instructions below.
 6. Click “Integrate manually“
 7. In your Shopify Admin, add the integration to your layout:
     1. Create a snippet:
-
         * Go to **Online Store** → **Themes**
         * Click **Actions** ("..." button) → **Edit code**
         * Go to **Snippets**
@@ -70,7 +67,6 @@ please follow the instructions below.
         * Click “Save”
 
     2. Render the snippet in the layout:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Layout**
         * Open `theme.liquid` file
         * Before closing `</head>` paste the following code:
@@ -82,9 +78,7 @@ please follow the instructions below.
         * Click “Save”
 
 8. In your Shopify Admin, create resources for referral share page:
-
     1. Create a share page section:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-campaign.liquid`
@@ -103,7 +97,6 @@ please follow the instructions below.
         * Click “Save”
 
     2. Create a share page template:
-
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `talkable` (`page.talkable.json`)
@@ -114,14 +107,10 @@ please follow the instructions below.
             :class: is-minimal
 
           .. important::
-            The name of the section should be the same as the one you used
-            in the previous step when naming your section file.
-
-          .. important::
-            If your main section is disabled, remove the row that does it.
+            - The name of the section should be the same as the one you used in the previous step when naming your section file.
+            - If your main section is disabled, remove the row that does it.
 
     3. Create a page:
-
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
         * Click “Add page“
@@ -130,9 +119,7 @@ please follow the instructions below.
         * Click “Save”
 
 9. In your Shopify Admin, create resources for referral dashboard page:
-
     1. Create a dashboard page section:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-dashboard.liquid`
@@ -152,7 +139,6 @@ please follow the instructions below.
         * Click “Save”
 
     2. Create a dashboard page template:
-
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `dashboard.talkable` (`page.dashboard.talkable.json`)
@@ -169,14 +155,10 @@ please follow the instructions below.
             }
 
           .. important::
-            The name of the section should be the same as the one you used
-            in the previous step when naming your section file.
-
-          .. important::
-            If your main section is disabled, remove the row that does it.
+            - The name of the section should be the same as the one you used in the previous step when naming your section file.
+            - If your main section is disabled, remove the row that does it.
 
     3. Create a page:
-
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
         * Click “Add page“
@@ -185,7 +167,6 @@ please follow the instructions below.
         * Click “Save” (Customer accounts must be enabled in **Settings** → **Checkout**)
 
 10. In your Shopify Admin, add a post-purchase script:
-
     * Go to **Settings** → **Checkout**
     * Scroll down to **Order status page**
     * Paste the following code into **Additional scripts** field:
@@ -212,7 +193,6 @@ please follow the instructions below.
 6. Click “Integrate manually“
 7. In your Shopify Admin, add the integration to your layout:
     1. Create a snippet:
-
         * Go to **Online Store** → **Themes**
         * Click **Actions** ("..." button) → **Edit code**
         * Go to **Snippets**
@@ -227,7 +207,6 @@ please follow the instructions below.
         * Click “Save”
 
     2. Render the snippet in the layout:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Layout**
         * Open `theme.liquid` file
         * Before closing `</head>` paste the following code:
@@ -239,9 +218,7 @@ please follow the instructions below.
         * Click “Save”
 
 8. In your Shopify Admin, create resources for referral share page:
-
     1. Create a share page template:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Templates**
         * Click “Add a new template“
         * Create a new Liquid template of type `page` called `talkable` (`page.talkable.liquid`)
@@ -254,7 +231,6 @@ please follow the instructions below.
         * Click “Save”
 
     2. Create a page:
-
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
         * Click “Add page“
@@ -263,9 +239,7 @@ please follow the instructions below.
         * Click “Save”
 
 9. In your Shopify Admin, create resources for referral dashboard page:
-
     1. Create a dashboard page template:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Templates**
         * Click “Add a new template“
         * Create a new Liquid template of type `page` called `dashboard.talkable` (`page.dashboard.talkable.liquid`)
@@ -293,7 +267,6 @@ please follow the instructions below.
         * Click “Save” (Customer accounts must be enabled in **Settings** → **Checkout**)
 
 10. In your Shopify Admin, add a post-purchase script:
-
     * Go to **Settings** → **Checkout**
     * Scroll down to **Order status page**
     * Paste the following code into **Additional scripts** field:
@@ -325,11 +298,8 @@ If you have previously integrated Talkable in your vintage Shopify theme and wan
 you need to do the following:
 
 1. Share page migration:
-
     1. If you have a `templates/page.talkable.liquid` file, store its content elsewhere and delete the file
-
     2. Create a share page section:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-campaign.liquid`
@@ -345,7 +315,6 @@ you need to do the following:
         * Click “Save”
 
     3. Create a share page template:
-
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `talkable` (`page.talkable.json`)
@@ -356,18 +325,12 @@ you need to do the following:
             :class: is-minimal
 
           .. important::
-            The name of the section should be the same as the one you used
-            in the previous step when naming your section file.
-
-          .. important::
-            If your main section is disabled, remove the row that does it.
+            - The name of the section should be the same as the one you used in the previous step when naming your section file.
+            - If your main section is disabled, remove the row that does it.
 
 2. Dashboard page migration:
-
     1. If you have a `templates/page.talkable-dashboard.liquid` file, store its content elsewhere and delete the file
-
     2. Create a dashboard page section:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-dashboard.liquid`
@@ -389,7 +352,6 @@ you need to do the following:
         * Click “Save”
 
     3. Create a dashboard page template:
-
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `dashboard.talkable` (`page.dashboard.talkable.json`)
@@ -406,11 +368,8 @@ you need to do the following:
             }
 
           .. important::
-            The name of the section should be the same as the one you used
-            in the previous step when naming your section file.
-
-          .. important::
-            If your main section is disabled, remove the row that does it.
+            - The name of the section should be the same as the one you used in the previous step when naming your section file.
+            - If your main section is disabled, remove the row that does it.
 
 **Contact us**
 
diff --git a/source/integration/loyalty.rst b/source/integration/loyalty.rst
index 52fb97d25..d49ac3f04 100644
--- a/source/integration/loyalty.rst
+++ b/source/integration/loyalty.rst
@@ -19,8 +19,7 @@ a few quick steps by adding the below scripts to your site.
    Add the :ref:`Talkable Initialization Script <integration/loyalty/integration_components/initialization_script>`
    to your header or any template spanning every page.
 
- .. note::
-
+.. note::
    Skip this step if you already have Talkable integrated on your site
 
 2. Add Loyalty Dashboard.
@@ -61,8 +60,7 @@ a few quick steps by adding the below scripts to your site.
    .. figure:: /_static/img/loyalty/redemption_batches.png
      :alt: Redemption batches
 
- .. note::
-
+.. note::
    All design and loyalty campaign setup is done inside the Talkable platform,
    then via iframe loyalty campaign content is injected into the site.
 
diff --git a/source/integration/loyalty/custom_app.rst b/source/integration/loyalty/custom_app.rst
index 2331eb4ae..b859274ff 100644
--- a/source/integration/loyalty/custom_app.rst
+++ b/source/integration/loyalty/custom_app.rst
@@ -37,7 +37,6 @@ To determine which loyalty action triggered the Custom App, use `{{ action.ident
 * when loyalty member exchanges points for a coupon, the Action Identifier is *"redeem"*;
 * when loyalty member gains or loses points due to a manual points adjustment, the Action Identifier is *"manual_adjustment"*;
 * when loyalty member earns points according to loyalty action configurations, the Action Identifier varies based on the action configuration type:
-
    * *"optin"* for "Loyalty join";
    * *"event"* for "Purchase points" and "Event points";
    * *"referral"* for "Refer a friend";
diff --git a/source/integration/loyalty/integration_components.rst b/source/integration/loyalty/integration_components.rst
index e409b797a..a05fe0eef 100644
--- a/source/integration/loyalty/integration_components.rst
+++ b/source/integration/loyalty/integration_components.rst
@@ -15,7 +15,6 @@ Talkable Loyalty is composed of the following components:
    that spans every page. All other integration components are dependent on the Init script.
 
    **Data Capture.** The Initialization Script should pass variables for logged in users:
-
     - Email
     - Phone Number
     - First Name
diff --git a/source/integration/loyalty/shopify_integration.rst b/source/integration/loyalty/shopify_integration.rst
index d23c4f523..4887026b0 100644
--- a/source/integration/loyalty/shopify_integration.rst
+++ b/source/integration/loyalty/shopify_integration.rst
@@ -28,9 +28,7 @@ Manual integration
 4. Click “Integrate manually“
 5. Set up Referral Integration :ref:`manually <integration/ecommerce_platforms/shopify/manual_integration>`
 6. In your Shopify Admin create resources for loyalty dashboard page:
-
     1. Create a loyalty dashboard page section:
-
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-loyalty-dashboard.liquid`
@@ -46,7 +44,6 @@ Manual integration
         * Click “Save”
 
     2. Create a loyalty dashboard page template:
-
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `loyalty_dashboard.talkable` (`page.loyalty_dashboard.talkable.json`)
@@ -70,7 +67,6 @@ Manual integration
             If your main section is disabled, remove the row that does it.
 
     3. Create a page:
-
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
         * Click “Add page“
@@ -95,7 +91,6 @@ you need to do the following:
 2. If you have a `templates/page.talkable-loyalty-dashboard.liquid` file, store its content elsewhere and delete the file
 
 3. Create a loyalty dashboard page section:
-
     * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
     * Click “Add a new section“
     * Create a new Liquid section called `talkable-loyalty-dashboard.liquid`
@@ -113,7 +108,6 @@ you need to do the following:
     * Click “Save”
 
 4. Create a loyalty dashboard page template:
-
     * Go to **Templates**
     * Click “Add a new template“
     * Create a new JSON template of type `page` called `loyalty_dashboard.talkable` (`page.loyalty_dashboard.talkable.json`)
@@ -130,8 +124,5 @@ you need to do the following:
         }
 
       .. important::
-        The name of the section should be the same as the one you used
-        in the previous step when naming your section file.
-
-      .. important::
-        If your main section is disabled, remove the row that does it.
+        - The name of the section should be the same as the one you used in the previous step when naming your section file.
+        - If your main section is disabled, remove the row that does it.
diff --git a/source/ios_sdk/advanced.rst b/source/ios_sdk/advanced.rst
index 64df00f7b..5a768e3ed 100644
--- a/source/ios_sdk/advanced.rst
+++ b/source/ios_sdk/advanced.rst
@@ -10,7 +10,7 @@ Specify a custom campaign tag
 By default if no campaign tag was specified, SDK uses `ios-invite` and `ios-post-purchase` tags for :ref:`Standalone <ios_sdk/integration/standalone>` and
 :ref:`Post Purchase <ios_sdk/integration/post_purchase>` campaigns. But you can explicitly specify your own tag in this way:
 
-  .. code-block:: objc
+.. code-block:: objc
 
     #import <TalkableSDK/Talkable.h>
     // ...
@@ -23,47 +23,47 @@ Implement TalkableDelegate
 
 1. Assign your `ViewController` or other object as Talkable delegate by using the following code:
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     [[Talkable manager] setDelegate: yourObjectConformsToTalkableDelegateProtocol];
 
 2. Take control of presenting offers to your users. Use the next two delegate methods to prevent
    or give an instruction as to where you want that offer to be displayed:
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     - (BOOL)shouldPresentTalkableOfferViewController:(UIViewController*)controller;
     - (UIViewController*)viewControllerForPresentingTalkableOfferViewController;
 
 3. Customize ViewContoller title by implementing the method below. By default, title of offer page is used.
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     - (NSString*)titleForTalkableOfferViewController:(UIViewController*)controller;
 
-  .. note::
+   .. note::
 
     You can modify page title on a Talkable Site during campaign development.
 
 4. Present offers to your users by yourself by handling request url or webView after origin was created.
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     - (void)didRegisterOrigin:(TKBLOriginType)type withURL:(NSURL*)url;
     - (void)didRegisterOrigin:(TKBLOriginType)type withWebView:(WKWebView*)webView;
 
-  .. note::
+   .. note::
 
     Talkable SDK assigns itself to WKWebView navigation delegate. Changing WKWebView navigation delegate
     may break some functionality so we strictly recommend not doing this.
 
 5. Manage cases where origin wasn't created or offer hasn't been presented.
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     - (void)registerOrigin:(TKBLOriginType)type didFailWithError:(NSError*)error;
 
-  .. note::
+   .. note::
 
     `userInfo` may contain detailed information about the error.
 
@@ -76,7 +76,7 @@ Implement TalkableDelegate
      - (void)showFacebookShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
      - (void)showTwitterShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
 
-   .. note::
+    .. note::
 
      See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
 
@@ -89,7 +89,7 @@ Subscribe to notifications that Talkable SDK publish and be aware of everything
 
 1. Receive the coupon given to your users:
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     #import <TalkableSDK/Talkable.h>
     // ...
@@ -101,7 +101,7 @@ Subscribe to notifications that Talkable SDK publish and be aware of everything
 
 2. Catch every message from presented offer:
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     #import <TalkableSDK/Talkable.h>
     // ...
@@ -113,11 +113,10 @@ Subscribe to notifications that Talkable SDK publish and be aware of everything
       }
     }
 
-  Available messages:
-
-  - TKBLMessageOfferLoaded
-  - TKBLMessageOfferClose
-  - TKBLMessageCouponIssued
+Available messages:
+   - TKBLMessageOfferLoaded
+   - TKBLMessageOfferClose
+   - TKBLMessageCouponIssued
 
 Contacts Import
 ---------------
@@ -128,7 +127,7 @@ The button at the Share page for contacts importing should have `class="js-impor
 Also, contacts usage description is required on iOS 10+ devices. It should be described under the `NSContactsUsageDescription` key
 in the `Info.plist` file of your app. This message will be shown when asking for contacts permissions.
 
-  .. code-block:: xml
+.. code-block:: xml
 
     <key>NSContactsUsageDescription</key>
     <string>Share the offer with your Friends from contacts</string>
@@ -143,7 +142,7 @@ Debugging
 
 See all debugging information in your console which can help you to understand what is going wrong:
 
-  .. code-block:: objc
+.. code-block:: objc
 
     #import <TalkableSDK/Talkable.h>
     // ...
diff --git a/source/ios_sdk/getting_started.rst b/source/ios_sdk/getting_started.rst
index 9bd51c546..593d9398c 100644
--- a/source/ios_sdk/getting_started.rst
+++ b/source/ios_sdk/getting_started.rst
@@ -25,7 +25,7 @@ Installing from Xcode:
 1. Add a package by selecting **File** → **Add Packages…** in Xcode’s menu bar.
 2. Search for the Talkable SDK using the repo's URL:
 
-  .. code-block:: bash
+   .. code-block:: bash
 
     https://github.com/talkable/ios-sdk.git
 
@@ -34,7 +34,7 @@ Installing from Xcode:
 
 Alternatively, you can add Talkable SDK directly to a `Package.swift` manifest:
 
-  .. code-block:: swift
+.. code-block:: swift
 
     dependencies: [
         .package(url: "https://github.com/talkable/ios-sdk.git", .upToNextMajor(from: "1.5.1"))
@@ -45,7 +45,7 @@ CocoaPods
 
 To integrate Talkable SDK into your Xcode project using CocoaPods, specify it in your `Podfile`_:
 
-  .. code-block:: ruby
+.. code-block:: ruby
 
     pod 'TalkableSDK', '~> 1.5.1'
 
@@ -67,13 +67,13 @@ Step 2: Configuration
 
 1. Initialize Talkable SDK in your `application:didFinishLaunchingWithOptions:` method, like so:
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     #import <TalkableSDK/Talkable.h>
     // ...
     [[Talkable manager] setApiKey:@"YOUR_TALKABLE_PUBLIC_API_KEY" andSiteId:@"YOUR_SITE_ID"];
 
-  .. note::
+   .. note::
 
     You can locate your credentials inside Talkable site:
 
@@ -83,9 +83,9 @@ Step 2: Configuration
 
 2. Register URL scheme for Talkable:
 
-  - Defines `tkbl-YOUR-SITE-ID` as URL Scheme in your Info.plist file:
+   - Defines `tkbl-YOUR-SITE-ID` as URL Scheme in your Info.plist file:
 
-    .. code-block:: xml
+     .. code-block:: xml
 
       <key>CFBundleURLTypes</key>
       <array>
@@ -97,10 +97,9 @@ Step 2: Configuration
         </dict>
       </array>
 
-  - Add `tkbl-YOUR-SITE-ID` scheme to the list of schemes that are queried within application.
-    Also add `fb-messenger`, `fbauth2`, `whatsapp` schemes if you are going to utilize these sharing channels:
+   - Add `tkbl-YOUR-SITE-ID` scheme to the list of schemes that are queried within application. Also add `fb-messenger`, `fbauth2`, `whatsapp` schemes if you are going to utilize these sharing channels:
 
-    .. code-block:: xml
+     .. code-block:: xml
 
       <key>LSApplicationQueriesSchemes</key>
       <array>
@@ -110,7 +109,7 @@ Step 2: Configuration
         <string>whatsapp</string>
       </array>
 
-  .. note::
+   .. note::
 
     Please replace `YOUR-SITE-ID` with your actual Site ID.
     Make sure to keep `tkbl-` prefix in the `<string>` value. For example,
@@ -118,7 +117,7 @@ Step 2: Configuration
 
 3. Add following lines to `application:openURL:options:`
 
-  .. code-block:: objc
+   .. code-block:: objc
 
     #import <TalkableSDK/Talkable.h>
     // ...
diff --git a/source/ios_sdk/social_sharing.rst b/source/ios_sdk/social_sharing.rst
index 09f3ca2a5..69615147b 100644
--- a/source/ios_sdk/social_sharing.rst
+++ b/source/ios_sdk/social_sharing.rst
@@ -31,9 +31,8 @@ showFacebookShareDialogWithParams:delegate:
 
 This method is called when the user clicks on the 'Facebook Share' button.
 The ``params`` dictionary contains information on the content being shared and will have the following keys:
-
-   * ``TKBLOfferClaimUrlKey`` - the link URL to share
-   * ``TKBLShareMessage`` - the message to share
+  -  ``TKBLOfferClaimUrlKey`` - the link URL to share
+  -  ``TKBLShareMessage`` - the message to share
 
 The ``delegate`` param is a delegate object that conforms to Facebook iOS SDK ``SharingDelegate`` protocol.
 Pass this object as a ``delegate:`` param when sharing the link using FBSDK to automatically notify the Talkable SDK
diff --git a/source/web_hooks/check_unsubscribe.rst b/source/web_hooks/check_unsubscribe.rst
index c35e63ce4..45c355c56 100644
--- a/source/web_hooks/check_unsubscribe.rst
+++ b/source/web_hooks/check_unsubscribe.rst
@@ -21,16 +21,15 @@ otherwise valid customer email, aimed at checking if the email is also valid on
 merchant side.
 
 .. important::
-
   If this Check Unsubscribe Webhook is used, the response JSON returned by
   merchant must contain the following fields:
 
-   .. code-block:: javascript
+  .. code-block:: javascript
 
-     { "result": { "unsubscribed": true } }
+    { "result": { "unsubscribed": true } }
 
-   The 'unsubscribed' field should have a boolean value,
-   representing unsubscribed status according to the merchant info.
+  The 'unsubscribed' field should have a boolean value,
+  representing unsubscribed status according to the merchant info.
 
 .. raw:: html
 
diff --git a/source/web_hooks/post_share.rst b/source/web_hooks/post_share.rst
index ff32240b6..1b1afea7e 100644
--- a/source/web_hooks/post_share.rst
+++ b/source/web_hooks/post_share.rst
@@ -7,24 +7,18 @@
 Post Share Webhook
 ==================
 
-Talkable Post Share Webhook provides notification of a share event performed
-within a referral campaign workflow. Use cases for the Post Share Webhook include:
-
-  * Sending automated 'Thank You' email to an Advocate for performing a share
-  * Any event that should be triggered when a user shares
-  * Data for Business Intelligence and analytics systems
+Talkable Post Share Webhook provides notification of a share event performed within a referral campaign workflow. Use cases for the Post Share Webhook include:
+  - Sending automated 'Thank You' email to an Advocate for performing a share
+  - Any event that should be triggered when a user shares
+  - Data for Business Intelligence and analytics systems
 
 .. raw:: html
 
   <h2>When does Talkable call the Post Share Webhook?</h2>
 
-Talkable Post Share Webhook is triggered any time an |advocate| (referrer)
-shares offer details with a |friend| (referee) via the corresponding form
-provided by campaign workflow. Which includes any time:
-
-  * An advocate shares with a Friend via Email or any other channel from inside
-    a referral campaign workflow
-  * An Advocate copies a share link from a referral campaign workflow share screen
+Talkable Post Share Webhook is triggered any time an |advocate| (referrer) shares offer details with a |friend| (referee) via the corresponding form provided by campaign workflow. Which includes any time:
+  - An advocate shares with a Friend via Email or any other channel from inside a referral campaign workflow
+  - An Advocate copies a share link from a referral campaign workflow share screen
 
 Note: the Post Share Webhook triggers every time a share occurs. For example,
 if an Advocate shares with a Friend via email (or any channel), then shares with

From b61f205c254bc551cf8a2e43ac2f1ce6b03a30fe Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 19:43:40 +0300
Subject: [PATCH 48/62] add "docs" to the name of nginx container

---
 docker-compose.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 4c4f50605..47dabf33f 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -17,7 +17,7 @@ services:
 
   nginx:
     image: nginx:1.27-alpine3.20
-    container_name: nginx-${ENVIRONMENT}
+    container_name: docs-nginx-${ENVIRONMENT}
     volumes:
       - docs_build:/var/www/html
       - ./nginx/conf.d:/etc/nginx/conf.d

From 2069c6a14e609f766813c26e87e76b07f98a5c34 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Tue, 28 Jan 2025 21:23:56 +0300
Subject: [PATCH 49/62] cicrleci errors fix

---
 .../klaviyo.rst                               |  5 +-
 .../ecommerce_platforms/magento/magento2.rst  | 53 +++++++++++--------
 source/ios_sdk/advanced.rst                   | 16 +++---
 source/ios_sdk/social_sharing.rst             |  5 +-
 4 files changed, 44 insertions(+), 35 deletions(-)

diff --git a/source/email_marketing_and_automation/klaviyo.rst b/source/email_marketing_and_automation/klaviyo.rst
index b72f7dabd..866ad0197 100644
--- a/source/email_marketing_and_automation/klaviyo.rst
+++ b/source/email_marketing_and_automation/klaviyo.rst
@@ -10,6 +10,7 @@ Klaviyo
 With ESP apps clients can synchronize emails that Talkable acquires with their ESP. Here are the conditions when Talkable acquires emails:
 
 1. Advocate signs up and opts in for Talkable marketing emails:
+
   .. image:: /_static/img/email_marketing_and_automation/subscribe.png
     :alt: Subscribe
 
@@ -24,8 +25,8 @@ Each ESP application allows custom attributes to be included with each request.
 2. ``{{ ip }}`` – a data object from which IP address either a signup or email gating occurred.
 3. ``{{ campaign }}`` – a data object with details about the campaign within which the email was captured.
 
-.. image:: /_static/img/email_marketing_and_automation/variables.png
-  :alt: Variables
+  .. image:: /_static/img/email_marketing_and_automation/variables.png
+    :alt: Variables
 
 Each variable is described in the “Available variables” sidebar and can be expanded to see all nested properties.
 
diff --git a/source/integration/ecommerce_platforms/magento/magento2.rst b/source/integration/ecommerce_platforms/magento/magento2.rst
index 7b420312e..2ea300035 100644
--- a/source/integration/ecommerce_platforms/magento/magento2.rst
+++ b/source/integration/ecommerce_platforms/magento/magento2.rst
@@ -35,36 +35,41 @@ Installation
    This guide shows example outputs for Terminal, but these steps can be modified for any command line tool of your choice.
 
 3. Run the following command to access the latest version of the Talkable extension.
-    .. code-block:: bash
+    
+.. code-block:: bash
 
-      composer require talkable/magento2-integration
+  composer require talkable/magento2-integration
 
 4. Run the following command to enable the Talkable extension you just downloaded:
-    .. code-block:: bash
 
-      php bin/magento module:enable Talkable_Integration --clear-static-content
+.. code-block:: bash
 
-   You should see the following output:
-    .. code-block::
+  php bin/magento module:enable Talkable_Integration --clear-static-content
 
-      The following modules have been enabled:
-      - Talkable_Integration
+You should see the following output:
+  
+.. code-block::
 
-      To make sure that the enabled modules are properly registered, run 'setup:upgrade'.
-      Cache cleared successfully.
-      Generated classes cleared successfully.
-      Please run the 'setup:di:compile' command to generate classes.
-      Generated static view files cleared successfully.
+  The following modules have been enabled:
+  - Talkable_Integration
+
+  To make sure that the enabled modules are properly registered, run 'setup:upgrade'.
+  Cache cleared successfully.
+  Generated classes cleared successfully.
+  Please run the 'setup:di:compile' command to generate classes.
+  Generated static view files cleared successfully.
 
 5. As displayed in the sample output, you must now enable any additional modules. Run the following command to enable them:
-    .. code-block:: bash
 
-      php bin/magento setup:upgrade
+.. code-block:: bash
+
+  php bin/magento setup:upgrade
 
 6. To ensure that the CSS and JS on your Magento 2 store continues to work properly, you’ll need to run a static content deploy command.
-    .. code-block:: bash
 
-      php bin/magento setup:static-content:deploy -f
+.. code-block:: bash
+
+  php bin/magento setup:static-content:deploy -f
 
 7. Installation via Composer is complete! You can now return to the Magento admin dashboard from your browser.
 
@@ -76,12 +81,12 @@ Accessing Talkable Configuration
 1. To access Talkable extension settings, navigate to **Stores** → **Configuration** in
    your Magento admin panel.
 
-   .. image:: /_static/img/magento2/access1.jpg
+.. image:: /_static/img/magento2/access1.jpg
 
 2. Then select **Talkable** → **Talkable Configuration** from the list of available configurations.
    If you have multiple stores, select the desired Store View you want to change the settings for.
 
-   .. image:: /_static/img/magento2/access2.jpg
+.. image:: /_static/img/magento2/access2.jpg
 
 |page_break|
 
@@ -89,7 +94,8 @@ Configuring Talkable Extension
 ------------------------------
 
 The extension configuration screen consists of three sections: Integration_, Campaigns_ and `Page URLs`_.
-   .. image:: /_static/img/magento2/configure1.jpg
+   
+.. image:: /_static/img/magento2/configure1.jpg
 
 |page_break|
 
@@ -98,7 +104,8 @@ Integration
 
 The Integration section allows you to change the Talkable Site ID, which is used to connect your store
 to your Talkable account.
-   .. image:: /_static/img/magento2/configure2.jpg
+   
+.. image:: /_static/img/magento2/configure2.jpg
 
 .. warning::
 
@@ -108,13 +115,13 @@ to your Talkable account.
   Changing the Site ID will invalidate the full page cache. Magento will display a warning message with
   a link to the Cache Management page. Please follow this link and refresh the invalidated cache types.
 
-  .. image:: /_static/img/magento2/cache.jpg
+.. image:: /_static/img/magento2/cache.jpg
 
 .. note::
 
   You need to paste the Site ID from your Talkable Site Dashboard into this field.
 
-  .. image:: /_static/img/magento2/configure3.jpg
+.. image:: /_static/img/magento2/configure3.jpg
 
 |page_break|
 
diff --git a/source/ios_sdk/advanced.rst b/source/ios_sdk/advanced.rst
index 5a768e3ed..b22eeeb02 100644
--- a/source/ios_sdk/advanced.rst
+++ b/source/ios_sdk/advanced.rst
@@ -76,9 +76,9 @@ Implement TalkableDelegate
      - (void)showFacebookShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
      - (void)showTwitterShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
 
-    .. note::
+   .. note::
 
-     See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
+    See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
 
 .. _ios_sdk/advanced/notifications:
 
@@ -114,18 +114,18 @@ Subscribe to notifications that Talkable SDK publish and be aware of everything
     }
 
 Available messages:
-   - TKBLMessageOfferLoaded
-   - TKBLMessageOfferClose
-   - TKBLMessageCouponIssued
+  - TKBLMessageOfferLoaded
+  - TKBLMessageOfferClose
+  - TKBLMessageCouponIssued
 
 Contacts Import
 ---------------
 
 It is possible to import contacts from a device with the SDK, so they will be accessible at the Share page with JavaScript.
-The button at the Share page for contacts importing should have `class="js-import-contacts"` property.
+The button at the Share page for contacts importing should have ``class="js-import-contacts"`` property.
 
-Also, contacts usage description is required on iOS 10+ devices. It should be described under the `NSContactsUsageDescription` key
-in the `Info.plist` file of your app. This message will be shown when asking for contacts permissions.
+Also, contacts usage description is required on iOS 10+ devices. It should be described under the ``NSContactsUsageDescription`` key
+in the ``Info.plist`` file of your app. This message will be shown when asking for contacts permissions.
 
 .. code-block:: xml
 
diff --git a/source/ios_sdk/social_sharing.rst b/source/ios_sdk/social_sharing.rst
index 69615147b..4f1e9be34 100644
--- a/source/ios_sdk/social_sharing.rst
+++ b/source/ios_sdk/social_sharing.rst
@@ -31,8 +31,9 @@ showFacebookShareDialogWithParams:delegate:
 
 This method is called when the user clicks on the 'Facebook Share' button.
 The ``params`` dictionary contains information on the content being shared and will have the following keys:
-  -  ``TKBLOfferClaimUrlKey`` - the link URL to share
-  -  ``TKBLShareMessage`` - the message to share
+  
+-  ``TKBLOfferClaimUrlKey`` - the link URL to share
+-  ``TKBLShareMessage`` - the message to share
 
 The ``delegate`` param is a delegate object that conforms to Facebook iOS SDK ``SharingDelegate`` protocol.
 Pass this object as a ``delegate:`` param when sharing the link using FBSDK to automatically notify the Talkable SDK

From cca4d449279d6b87b5bfb56e4d8f6c1964a6389d Mon Sep 17 00:00:00 2001
From: Vitalii Oliinyk <ilovepinkpony1@gmail.com>
Date: Tue, 28 Jan 2025 20:36:59 +0200
Subject: [PATCH 50/62] [PR-23724]: updated indentation

---
 source/_static/talkable.css | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/source/_static/talkable.css b/source/_static/talkable.css
index 887465952..396ab24e7 100644
--- a/source/_static/talkable.css
+++ b/source/_static/talkable.css
@@ -37,3 +37,7 @@ body[data-theme="light"] .highlight button.copybtn.success:after {
 .hidden {
   display: none;
 }
+
+dd {
+  margin-inline-start: 20px;
+}

From d431719dd1f597ba94ca92039d11701c484ca14a Mon Sep 17 00:00:00 2001
From: Enver <enver.ablyaev@gmail.com>
Date: Wed, 29 Jan 2025 11:45:42 +0300
Subject: [PATCH 51/62] Update README-maintainer.md

Co-authored-by: Bohdan Zhuravel <bohdan@zhuravel.bz>
---
 README-maintainer.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/README-maintainer.md b/README-maintainer.md
index c53e39e09..24c729d26 100644
--- a/README-maintainer.md
+++ b/README-maintainer.md
@@ -31,8 +31,7 @@ The maintenance routine includes the following tasks:
 2. Create a new branch from `master`.
 
     ```bash
-    git branch new-branch
-    git checkout new-branch
+    git checkout -b new-branch
     ```
 
 3. Generate a `.env` file from the `.env.template`.

From cec050cec4edce4c3f6e1a8b0f258c93f2b3b7cb Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Wed, 29 Jan 2025 11:53:15 +0300
Subject: [PATCH 52/62] gitignore refactoring

---
 .gitignore | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 65a67ae36..68fe5082d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -103,7 +103,7 @@ fabric.properties
 
 .idea/*
 
-!.idea/codeStyles
-!.idea/runConfigurations
+# !.idea/codeStyles
+# !.idea/runConfigurations
 
 # End of https://www.toptal.com/developers/gitignore/api/intellij+all

From 746556ac2d593f0f2c4548e9f953eadf01580396 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Wed, 29 Jan 2025 11:52:14 +0200
Subject: [PATCH 53/62] deploy jenkins

---
 deploy/Jenkinsfile |  16 +++---
 deploy/deploy.sh   | 132 +++++++++++++++++++++++++++++++++++++++++++++
 docker-compose.yml |  14 ++++-
 3 files changed, 150 insertions(+), 12 deletions(-)

diff --git a/deploy/Jenkinsfile b/deploy/Jenkinsfile
index b3c807eba..4f1656ad7 100644
--- a/deploy/Jenkinsfile
+++ b/deploy/Jenkinsfile
@@ -1,14 +1,5 @@
 #!/usr/bin/env groovy
 
-// Upgrades or installs nginx containers for WordPress.
-def dockerContainerUpdate(String hostEnv) {
-    sh """ssh -o StrictHostKeyChecking=no -i $SSH_KEY $SSH_USER@${hostEnv} 'cd talkable-docs/ && \
-        git checkout ${BRANCH_NAME} && git branch -a && git pull origin && \
-        docker-compose ls && docker ps && \
-        docker-compose down && docker-compose up -d --remove-orphans && \
-        docker-compose ls && docker ps' """
-}
-
 pipeline {
     agent {
         label "staging"
@@ -21,6 +12,11 @@ pipeline {
     triggers {
         pollSCM('* * * * *') // Polls SCM every minute
     }
+    parameters {
+        choice(name: "DEPLOY_COMMAND",
+                choices: ["deploy", "ci_status"],
+                description: "DEPLOY - Start the default deployment\nCI_STATUS - Check the GitHub commit status on CircleCI")
+    }
     options {
         buildDiscarder(logRotator(numToKeepStr: '15', daysToKeepStr: '14'))
         disableConcurrentBuilds()
@@ -57,7 +53,7 @@ pipeline {
             steps {
                 script {
                     withCredentials([sshUserPrivateKey(credentialsId: "${JENKINS_CRED_ID}", keyFileVariable: 'SSH_KEY', usernameVariable: 'SSH_USER')]) {
-                        dockerContainerUpdate('$HOST_ENV')
+                        sh "$WORKSPACE/deploy/deploy.sh ${DEPLOY_COMMAND}"
                     }
                 }
             }
diff --git a/deploy/deploy.sh b/deploy/deploy.sh
index e69de29bb..360d13f38 100755
--- a/deploy/deploy.sh
+++ b/deploy/deploy.sh
@@ -0,0 +1,132 @@
+#!/usr/bin/env bash
+set -ex
+echo $SECONDS
+
+echo "=== Environment Variables ==="
+printenv | sort
+
+TIMEFRAME_SECONDS=240
+PROJECT_ROOT="talkable-docs"
+CIRCLE_CI_API_URL="https://api.github.com/repos/talkable/${PROJECT_ROOT}/commits/${GIT_COMMIT}/status"
+CIRCLE_CI_URL="https://app.circleci.com/pipelines/github/talkable/${PROJECT_ROOT}?branch="
+TASK=$1
+
+#FUNCTIONS
+print_help() {
+  clear
+  echo 'Available Commands:'
+  echo '   deploy           - deploy current version of talkable'
+  echo '   ci | cistatus | status   - status on CircleCI'
+  echo 'Example:'
+  echo '         deploy.sh deploy'
+  echo '         deploy.sh cistatus'
+  exit 0
+}
+
+ci_status() {
+  show_status() {
+    curl -s -u "$GITHUB_ACC_USR":"$GITHUB_ACC_PSW" "$CIRCLE_CI_API_URL" | jq -r '.statuses[]' | jq '.context, .state' | grep ci/circleci -A1
+  }
+
+  while true; do
+    local tests_status
+    tests_status=$(curl -s -u "$GITHUB_ACC_USR":"$GITHUB_ACC_PSW" "$CIRCLE_CI_API_URL" |
+      jq -e -r '
+      [.statuses[].state] as $states |
+      if ($states | length) == 0 then
+        "no_tests"
+      elif $states | all(. == "success") then
+        "success"
+      elif $states | any(. == "failure" or . == "error") then
+        "failure"
+      elif $states | any(. == "pending") then
+        "pending"
+      else
+        "unknown"
+      end
+    ')
+
+    if [[ -z $tests_status ]]; then
+      echo "Error: Could not retrieve tests statuses. Check API response or credentials."
+      exit 1
+    fi
+
+    if [[ $tests_status == "success" ]]; then
+      show_status
+      echo "The sphinx build has succeeded!"
+      break
+    elif [[ $tests_status == "failure" ]]; then
+      show_status
+      echo -e "The Sphinx build failed on CircleCI.\nCheck the CircleCI results here: $CIRCLE_CI_URL$BRANCH_NAME"
+      exit 1
+    elif [[ $tests_status == "no_tests" ]]; then
+      show_status
+      echo -e "There is no sphinx build on CircleCI for the commit.\nCheck the CircleCI results here: $CIRCLE_CI_URL$ENV_BRANCH"
+      exit 1
+    elif [[ $tests_status == "pending" ]]; then
+      echo "Tests is pending or queued. Waiting for sphinx build ..."
+    fi
+
+    if [[ $SECONDS -gt $TIMEFRAME_SECONDS ]]; then
+      show_status
+      echo -e "The build is marked as FAILURE by timeout.\nCheck the CircleCI results here: $CIRCLE_CI_URL$ENV_BRANCH"
+      echo "Total elapsed time: $((SECONDS / 60)) minutes"
+      exit 228
+    fi
+
+    echo "Waiting for all tests to succeed. Next check in 8 seconds..."
+    echo "Elapsed time: $((SECONDS / 60)) minutes. Timeout at $((TIMEFRAME_SECONDS / 60)) minutes."
+    sleep 8
+  done
+
+  echo "CI checks completed successfully."
+  echo "Total elapsed time: $((SECONDS / 60)) minutes"
+}
+
+remote_ssh_exec() {
+  ssh -o StrictHostKeyChecking=no -i "$SSH_KEY" "$SSH_USER@$HOST_ENV" "$@"
+}
+
+deploy_docs() {
+  remote_ssh_exec <<EOF
+    set -e
+    cd ${PROJECT_ROOT}/
+    git checkout ${BRANCH_NAME}
+    git branch -a
+    git pull origin
+    docker-compose ls
+    docker ps | grep docs
+    docker-compose down
+    docker-compose up -d --remove-orphans
+EOF
+}
+
+deploy_check() {
+  remote_ssh_exec <<EOF
+    set -e
+    cd ${PROJECT_ROOT}/
+    docker-compose ls
+    docker ps | grep docs
+EOF
+}
+
+case $TASK in
+ci | ci_status | ci_only | status)
+  ci_status
+  deploy_check
+  ;;
+deploy)
+  echo "Starting deployment..."
+  ci_status
+  deploy_docs
+  deploy_check
+  ;;
+help|--help|-h)
+  print_help
+  ;;
+*)
+  echo "Unknown command: $TASK"
+  echo "Use '$0 --help' for usage."
+  exit 1
+  ;;
+esac
diff --git a/docker-compose.yml b/docker-compose.yml
index 47dabf33f..b23023ec0 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,10 +1,12 @@
 services:
+
   sphinx:
     build:
       context: .
       dockerfile: Dockerfile
     container_name: docs-sphinx-${ENVIRONMENT}
-    restart: unless-stopped
+    networks:
+      - docs-nginx
     volumes:
       - ./source:/docs/source
       - docs_build:/docs/_build
@@ -16,8 +18,10 @@ services:
       - DEVELOPMENT_HOST=${DEVELOPMENT_HOST}
 
   nginx:
-    image: nginx:1.27-alpine3.20
+    image: nginx:1.27.3-alpine3.20
     container_name: docs-nginx-${ENVIRONMENT}
+    networks:
+      - docs-nginx
     volumes:
       - docs_build:/var/www/html
       - ./nginx/conf.d:/etc/nginx/conf.d
@@ -29,3 +33,9 @@ services:
 
 volumes:
   docs_build:
+    driver: local
+
+networks:
+  docs-nginx:
+    name: docs-nginx
+    driver: bridge

From ce396cf8f40ffc6641822306024f06928ee1a99c Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Wed, 29 Jan 2025 15:30:51 +0300
Subject: [PATCH 54/62] remove idea detailed ignores, keep only '.idea' which
 covers everything

---
 .gitignore | 92 +-----------------------------------------------------
 1 file changed, 1 insertion(+), 91 deletions(-)

diff --git a/.gitignore b/.gitignore
index 68fe5082d..a89d2a3d7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -16,94 +16,4 @@ __pycache__
 # Ruby
 /build
 /.bundle
-Gemfile.lock
-
-### Intellij+all ###
-# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm and Rider
-# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
-
-# User-specific stuff
-.idea/**/workspace.xml
-.idea/**/tasks.xml
-.idea/**/usage.statistics.xml
-.idea/**/dictionaries
-.idea/**/shelf
-
-# AWS User-specific
-.idea/**/aws.xml
-
-# Generated files
-.idea/**/contentModel.xml
-
-# Sensitive or high-churn files
-.idea/**/dataSources/
-.idea/**/dataSources.ids
-.idea/**/dataSources.local.xml
-.idea/**/sqlDataSources.xml
-.idea/**/dynamic.xml
-.idea/**/uiDesigner.xml
-.idea/**/dbnavigator.xml
-
-# Gradle
-.idea/**/gradle.xml
-.idea/**/libraries
-
-# Gradle and Maven with auto-import
-# When using Gradle or Maven with auto-import, you should exclude module files,
-# since they will be recreated, and may cause churn.  Uncomment if using
-# auto-import.
-# .idea/artifacts
-# .idea/compiler.xml
-# .idea/jarRepositories.xml
-# .idea/modules.xml
-# .idea/*.iml
-# .idea/modules
-# *.iml
-# *.ipr
-
-# CMake
-cmake-build-*/
-
-# Mongo Explorer plugin
-.idea/**/mongoSettings.xml
-
-# File-based project format
-*.iws
-
-# IntelliJ
-out/
-
-# mpeltonen/sbt-idea plugin
-.idea_modules/
-
-# JIRA plugin
-atlassian-ide-plugin.xml
-
-# Cursive Clojure plugin
-.idea/replstate.xml
-
-# SonarLint plugin
-.idea/sonarlint/
-
-# Crashlytics plugin (for Android Studio and IntelliJ)
-com_crashlytics_export_strings.xml
-crashlytics.properties
-crashlytics-build.properties
-fabric.properties
-
-# Editor-based Rest Client
-.idea/httpRequests
-
-# Android studio 3.1+ serialized cache file
-.idea/caches/build_file_checksums.ser
-
-### Intellij+all Patch ###
-# Ignore everything but code style settings and run configurations
-# that are supposed to be shared within teams.
-
-.idea/*
-
-# !.idea/codeStyles
-# !.idea/runConfigurations
-
-# End of https://www.toptal.com/developers/gitignore/api/intellij+all
+Gemfile.lock
\ No newline at end of file

From e9b4931b9eed4fc8c4e7a3c3014f49e5f2858a7d Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Wed, 29 Jan 2025 15:41:21 +0300
Subject: [PATCH 55/62] formatting refactoring

---
 source/campaigns.rst | 22 +++++++++-------------
 1 file changed, 9 insertions(+), 13 deletions(-)

diff --git a/source/campaigns.rst b/source/campaigns.rst
index 8b4a15446..718a373e6 100644
--- a/source/campaigns.rst
+++ b/source/campaigns.rst
@@ -12,7 +12,7 @@ Talkable Campaign is based on interaction between ``Advocate`` and ``Friend``:
 - Advocate: person, who shares an offer with their Friend(s)
 - Friend: person, who is invited to participate in Campaign by Advocate
 
-.. image:: /_static/img/basics/sharing-process.png
+.. figure:: /_static/img/basics/sharing-process.png
   :alt: Sharing process
 
 Each step of this interaction has its own ``View`` so developer can easily
@@ -26,9 +26,8 @@ familiar with Liquid templating in Shopify.
 
 To start editing Views simply visit ``Editor`` page from the Campaign dashboard.
 
-.. raw:: html
-
-  <h2>Campaign Types and Placements</h2>
+Campaign Types and Placements
+=============================
 
 +-------------------------------+---------------------------------+
 | .. toctree::                  | .. toctree::                    |
@@ -37,9 +36,8 @@ To start editing Views simply visit ``Editor`` page from the Campaign dashboard.
 |   campaigns/campaign_types    |   campaigns/campaign_placements |
 +-------------------------------+---------------------------------+
 
-.. raw:: html
-
-  <h2>Campaign Structure</h2>
+Campaign Structure
+==================
 
 +-------------------------------+
 | .. toctree::                  |
@@ -48,9 +46,8 @@ To start editing Views simply visit ``Editor`` page from the Campaign dashboard.
 |   campaigns/views             |
 +-------------------------------+
 
-.. raw:: html
-
-  <h2>Campaign Setup & Tutorials</h2>
+Campaign Setup & tutorials
+==========================
 
 +-------------------------------+-----------------------------+
 | .. toctree::                  | .. toctree::                |
@@ -61,9 +58,8 @@ To start editing Views simply visit ``Editor`` page from the Campaign dashboard.
 |   campaigns/localization      |                             |
 +-------------------------------+-----------------------------+
 
-.. raw:: html
-
-  <h2>Designer Guide</h2>
+Designer Guide
+==============
 
 +-------------------------------+
 | .. toctree::                  |

From 9f72e7ccdd2b7261100f3a6090e7bf04bd11cdef Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Wed, 29 Jan 2025 16:58:43 +0200
Subject: [PATCH 56/62] add subproject variable

---
 deploy/deploy.sh | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/deploy/deploy.sh b/deploy/deploy.sh
index 360d13f38..bb2e9899b 100755
--- a/deploy/deploy.sh
+++ b/deploy/deploy.sh
@@ -7,6 +7,7 @@ printenv | sort
 
 TIMEFRAME_SECONDS=240
 PROJECT_ROOT="talkable-docs"
+SUBPROJECT="docs"
 CIRCLE_CI_API_URL="https://api.github.com/repos/talkable/${PROJECT_ROOT}/commits/${GIT_COMMIT}/status"
 CIRCLE_CI_URL="https://app.circleci.com/pipelines/github/talkable/${PROJECT_ROOT}?branch="
 TASK=$1
@@ -95,7 +96,7 @@ deploy_docs() {
     git branch -a
     git pull origin
     docker-compose ls
-    docker ps | grep docs
+    docker ps
     docker-compose down
     docker-compose up -d --remove-orphans
 EOF
@@ -105,8 +106,8 @@ deploy_check() {
   remote_ssh_exec <<EOF
     set -e
     cd ${PROJECT_ROOT}/
-    docker-compose ls
-    docker ps | grep docs
+    docker-compose ls | grep ${SUBPROJECT}
+    docker ps | grep ${SUBPROJECT}
 EOF
 }
 

From 12c44281317eb80cd094382434f338ac0f7d8290 Mon Sep 17 00:00:00 2001
From: en-ver <enver.ablyaev@gmail.com>
Date: Wed, 29 Jan 2025 19:34:57 +0300
Subject: [PATCH 57/62] readme for maintainer and gitignore refactoring

---
 .gitignore           |  5 ++---
 README-maintainer.md | 29 +++++++++++------------------
 2 files changed, 13 insertions(+), 21 deletions(-)

diff --git a/.gitignore b/.gitignore
index a89d2a3d7..867edcc1c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -8,12 +8,11 @@
 
 # Sphinx
 _build
+build
 
 # Python
 .venv
 __pycache__
-
 # Ruby
-/build
-/.bundle
+.bundle
 Gemfile.lock
\ No newline at end of file
diff --git a/README-maintainer.md b/README-maintainer.md
index 24c729d26..36ac89f19 100644
--- a/README-maintainer.md
+++ b/README-maintainer.md
@@ -4,8 +4,7 @@ This documentation provides instructions for maintaining the Sphinx Builder **fr
 
 It outlines the routine for maintaining the framework and associated workflows.
 
-> **Note**: 
-> 
+> [!NOTE]
 > This guide does not cover updating the documentation content. 
 > Refer to [README.md](README.md) for details on updating the Talkable documentation source, which is available at [https://docs.talkable.com/](https://docs.talkable.com/).
 
@@ -68,10 +67,6 @@ The goal is to update `requirements.txt` with the latest versions of dependencie
 
     Ensure everything works as expected locally. Once confirmed, update `requirements.txt` to include all installed dependencies with their versions.
 
-    > **Note:**
-    >
-    > In addition to the packages listed in [packages.txt](packages.txt), `requirements.txt` will include transitive dependencies.
-
     Save the dependencies with the following command:
 
     ```bash
@@ -146,26 +141,24 @@ docker compose up -d --build
 
 ### Installing Additional Packages
 
-1. Add the package to `requirements.txt`.
-
-    Append the package name to `requirements.txt` (version specification is optional at this stage).
+Add the package to `requirements.txt`.
 
-    > **Note:**
-    >
-    > Version pinning can be done later.
+Append the package name to `requirements.txt` (version specification is optional at this stage).
 
-2. Rebuild the container.
+> [!NOTE]
+>
+> Version pinning can be done later.
 
-    Rebuild the container after modifying `requirements.txt`:
+Rebuild the container after modifying `requirements.txt`:
 
-    ```bash
-    docker compose up -d --build
-    ```
+```bash
+docker compose up -d --build
+```
 
 ### Modifying Configuration Files
 
 Most changes involve editing the [./source/conf.py](./source/conf.py) file or other files in the [./source/](./source/) directory.
 
-> **Note:**
+> [!NOTE]
 >
 > Rebuilding the container is unnecessary for changes to [./source/conf.py](./source/conf.py) or [./source/](./source/). These changes are applied automatically within 1 second.

From 49a7e05d68075a7b33febe4d487d419260bacf59 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Thu, 30 Jan 2025 17:51:03 +0200
Subject: [PATCH 58/62] add link to Jenkins

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 1b4939068..217926c72 100644
--- a/README.md
+++ b/README.md
@@ -59,7 +59,7 @@ The repository consists of the following branches:
 
 You should not deploy it manually!
 
-The deployment is handled by Jenkins jobs.
+The deployment is handled by [Jenkins job](http://jenkins.production/view/Talkable-docs/).
 
 All you need to do is commit your changes to the corresponding branch to deploy them to the appropriate server:
 - Commit to the [staging](https://github.com/talkable/talkable-docs/tree/staging) branch => [docs.bastion.talkable.com](https://docs.bastion.talkable.com/).

From 742c0e7a2b24823a1431149df25404c8a70b7b1e Mon Sep 17 00:00:00 2001
From: Bohdan Zhuravel <bohdan@zhuravel.bz>
Date: Mon, 3 Feb 2025 20:39:00 +0200
Subject: [PATCH 59/62] [PR-23815]-Book-theme-for-Sphinx (#364)

Co-authored-by: en-ver <enver.ablyaev@gmail.com>
---
 nginx/conf.d/default.conf                     |  10 +-
 packages.txt                                  |   4 +-
 requirements.txt                              |   5 +
 source/_templates/layout.html                 |  53 +---
 .../converting_into_localization.rst          |  65 ++---
 source/advanced_features/coupons.rst          |  18 +-
 .../customer_service_portal/overview.rst      |   5 +-
 .../customer_service_portal/terminology.rst   |  32 +--
 .../customer_service_portal/use_case_1.rst    |   1 +
 .../customer_service_portal/use_case_2.rst    |   1 +
 .../customer_service_portal/use_case_3.rst    |  10 +-
 .../customer_service_portal/use_case_4.rst    |   1 +
 .../customer_service_portal/use_case_5.rst    |   5 +-
 .../customer_service_portal/use_case_6.rst    |   1 +
 .../facebook_login_share.rst                  |  10 +-
 source/advanced_features/file_encryption.rst  |  14 +-
 source/advanced_features/multi_currency.rst   |   8 +-
 .../advanced_features/passing_custom_data.rst |  24 +-
 .../personal_coupon_sharing.rst               |  11 +-
 source/advanced_features/reg_ex.rst           |   2 +-
 source/advanced_features/rybbon.rst           |   6 +-
 source/advanced_features/segments.rst         |  61 ++---
 .../shopify_coupons_auto_apply.rst            |  11 +-
 .../shopify_coupons_auto_sync.rst             |  18 +-
 .../shopify_purchase_syncing.rst              |   7 +-
 source/advanced_features/single_sign_on.rst   |  49 ++--
 .../subscribing_to_events.rst                 |  27 ++-
 source/advanced_features/tremendous.rst       |  34 +--
 source/advanced_features/url_parameters.rst   |   6 +-
 source/advanced_features/utm_tags.rst         |  15 +-
 source/advanced_features/white_labeling.rst   |   2 +-
 .../white_labeling/godaddy.rst                |  13 +-
 .../white_labeling/shopify.rst                |  10 +-
 source/android_sdk.rst                        |  39 ++-
 source/android_sdk/advanced.rst               | 131 +++++-----
 source/android_sdk/api.rst                    | 214 +++++++++--------
 source/android_sdk/deep_linking.rst           | 208 ++++++++--------
 source/android_sdk/getting_started.rst        | 158 ++++++------
 .../android_sdk/integration/post_purchase.rst |  74 +++---
 source/android_sdk/testing.rst                |  16 +-
 source/android_sdk/upgrade.rst                | 130 +++++-----
 source/api_v2.rst                             |  21 +-
 source/api_v2/flow.rst                        |   4 +-
 source/api_v2/origins.rst                     |  60 ++---
 source/api_v2/referrals.rst                   |  18 +-
 source/campaigns.rst                          |  76 ++++--
 source/campaigns/designer.rst                 |   4 +-
 source/campaigns/tutorials/global.rst         |   9 +-
 source/campaigns/tutorials/offers_claim.rst   |   6 +-
 source/campaigns/views.rst                    |  15 +-
 ...tifier_offers_share_via_email_reminder.rst |   8 +-
 source/conf.py                                |  42 ++--
 source/custom_integration.rst                 |   4 +-
 source/custom_integration/recharge.rst        |  18 +-
 source/email_marketing_and_automation.rst     |  78 +++---
 .../attentive.rst                             |  30 ++-
 .../custom_app.rst                            |  29 +--
 .../hubspot.rst                               |  18 +-
 .../klaviyo.rst                               |  28 +--
 .../mailchimp.rst                             |  34 +--
 .../oracle_bronto.rst                         |  34 +--
 .../sailthru.rst                              |  24 +-
 source/index.rst                              | 109 ++++-----
 .../custom/integration_components.rst         |   9 +-
 source/integration/custom/overview.rst        |  12 +-
 source/integration/custom/questions.rst       |  14 +-
 source/integration/custom_integration.rst     |  30 ++-
 source/integration/ecommerce_platforms.rst    |  23 +-
 .../ecommerce_platforms/magento/magento1.rst  |   7 +-
 .../ecommerce_platforms/magento/magento2.rst  |  70 +++---
 .../ecommerce_platforms/shopify.rst           | 226 ++++++++++--------
 source/integration/loyalty.rst                |  24 +-
 source/integration/loyalty/custom_app.rst     |   9 +-
 .../loyalty/integration_components.rst        |  13 +-
 .../loyalty/shopify_integration.rst           |  75 +++---
 source/ios_sdk.rst                            |  35 ++-
 source/ios_sdk/advanced.rst                   |   8 +-
 source/ios_sdk/api_integration.rst            |  83 ++++---
 source/ios_sdk/integration/post_purchase.rst  |  42 ++--
 .../campaign_placements_description.rst       |   7 +-
 source/web_hooks/check_unsubscribe.rst        |  20 +-
 source/web_hooks/claim_signup.rst             |  10 +-
 source/web_hooks/create_coupon.rst            |  22 +-
 source/web_hooks/event.rst                    |   6 +-
 source/web_hooks/offer_signup.rst             |  10 +-
 source/web_hooks/post_share.rst               |  34 +--
 source/web_hooks/referral.rst                 |  18 +-
 source/web_hooks/reward.rst                   |  36 +--
 source/web_hooks/unsubscribe.rst              |   6 +-
 89 files changed, 1588 insertions(+), 1439 deletions(-)

diff --git a/nginx/conf.d/default.conf b/nginx/conf.d/default.conf
index 5788ccada..6939578ac 100644
--- a/nginx/conf.d/default.conf
+++ b/nginx/conf.d/default.conf
@@ -57,11 +57,11 @@ server {
 
     # Redirect requests starting with /search/?q=& to /
     # Fix of the Furo theme bug described here https://talkable.atlassian.net/browse/PR-23789
-    location /search/ {
-        if ($arg_q = "") {
-            return 301 /;
-        }
-    }
+    # location /search/ {
+    #     if ($arg_q = "") {
+    #         return 301 /;
+    #     }
+    # }
 
     # Serve robots.txt from a specific file
     location = /robots.txt {
diff --git a/packages.txt b/packages.txt
index cca18c7b5..470254163 100644
--- a/packages.txt
+++ b/packages.txt
@@ -2,8 +2,8 @@
 # Used by the documentation maintainer
 # Add the package name here if you add some to the framework
 
-furo
 sphinx-copybutton
 sphinx-sitemap
 sphinx-autobuild
-sphinx-favicon
+sphinx-book-theme
+sphinx-design
diff --git a/requirements.txt b/requirements.txt
index 7b2f8fbf9..59857e703 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,3 +1,4 @@
+accessible-pygments==0.0.5
 alabaster==1.0.0
 anyio==4.8.0
 babel==2.16.0
@@ -14,6 +15,7 @@ imagesize==1.4.1
 Jinja2==3.1.5
 MarkupSafe==3.0.2
 packaging==24.2
+pydata-sphinx-theme==0.16.1
 Pygments==2.19.1
 requests==2.32.3
 sniffio==1.3.1
@@ -22,9 +24,11 @@ soupsieve==2.6
 Sphinx==8.1.3
 sphinx-autobuild==2024.10.3
 sphinx-basic-ng==1.0.0b2
+sphinx-book-theme==1.1.3
 sphinx-copybutton==0.5.2
 sphinx-favicon==1.0.1
 sphinx-sitemap==2.6.0
+sphinx_design==0.6.1
 sphinxcontrib-applehelp==2.0.0
 sphinxcontrib-devhelp==2.0.0
 sphinxcontrib-htmlhelp==2.1.0
@@ -32,6 +36,7 @@ sphinxcontrib-jsmath==1.0.1
 sphinxcontrib-qthelp==2.0.0
 sphinxcontrib-serializinghtml==2.0.0
 starlette==0.45.3
+typing_extensions==4.12.2
 urllib3==2.3.0
 uvicorn==0.34.0
 watchfiles==1.0.4
diff --git a/source/_templates/layout.html b/source/_templates/layout.html
index 781745852..4acdccc34 100644
--- a/source/_templates/layout.html
+++ b/source/_templates/layout.html
@@ -1,49 +1,16 @@
-{% extends "basic/layout.html" %}
-{% block relbar1 %}{% endblock %}
-{% block relbar2 %}{% endblock %}
-{% block sidebarlogo %}{% endblock %}
-{% block sidebar2 %}{% endblock %}
+{% extends "!layout.html" %}
 
-{%- block doctype -%}
-  <!DOCTYPE html>
-{%- endblock -%}
-
-{%- block extrahead -%}
-  <link href='https://fonts.googleapis.com/css?family=Source+Code+Pro' rel='stylesheet' type='text/css'>
-  <link href="{{ pathto("_static/pygments-github.css", 1) }}" rel="stylesheet">
-  <link href="{{ pathto("_static/img/favicon.ico", 1) }}" rel="shortcut icon" />
-{%- endblock -%}
-
-{# put the sidebar before the body #}
-{%- block sidebar1 %}
-  {% block rootrellink %}
-    <div class="header">
-      <a href="{{ pathto(master_doc) }}" class="header-logo">Talkable docs</a>
-      {%- block sidebarsearch %}
-        {%- if pagename != "search" and builder != "singlehtml" %}
-          <form class="search-form" action="{{ pathto('search') }}" method="get">
-            <input type="text" class="textfield search-form-field" name="q" placeholder="Search docs" />
-            <input type="submit" class="button search-form-button" value="Search" />
-            <input type="hidden" name="check_keywords" value="yes" />
-            <input type="hidden" name="area" value="default" />
-          </form>
-        {%- endif %}
-      {%- endblock %}
-      <div class="header-disclaimer">
-        Visit
-        <a href="https://www.talkable.com" target="_blank">www.talkable.com</a>
-      </div>
-    </div> <!-- /.header -->
-  {% endblock %}
-
-  <div class="content-container content clearfix">
-    {%- block sidebartoc %}
-      <div class="nav">
-        {{ toctree(maxdepth=3) }}
-      </div>
-    {%- endblock %}
+{# Set the title and sitename divider to '|' and hide 'no title' if the page has no title #}
+{% block htmltitle %}
+  {% if title == "&lt;no title&gt;" %}
+    <title>{{ docstitle|e }}</title>
+  {% else %}
+    <title>{{ title|striptags|e }} | {{ docstitle|e }}</title>
+  {% endif %}
 {% endblock %}
 
+{# Google Tag Manager injection #}
+
 {%- block footer %}
   </div> <!-- /.content-container -->
   <script>
diff --git a/source/advanced_features/converting_into_localization.rst b/source/advanced_features/converting_into_localization.rst
index d6de47f44..9547b2084 100644
--- a/source/advanced_features/converting_into_localization.rst
+++ b/source/advanced_features/converting_into_localization.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: This is a how-to guide to help you get the most out of Localizations.
+   :description: This is a how-to guide to help you get the most out of Localizations.
 
 Converting Into Localization
 ============================
@@ -10,53 +10,54 @@ Converting Into Localization
 If you don’t know what is Localization inside Talkable :ref:`read this article <campaigns/localization>`.
 
 Few benefits you get out of using Localizations:
-  1. It is extremely easy to set up an AB test if your copy is coded up as a Localization.
-  2. For non-technical people it is easier to change the copy inside Localization Editor because they are afraid to code.
+
+- It is extremely easy to set up an AB test if your copy is coded up as a Localization.
+- For non-technical people it is easier to change the copy inside Localization Editor because they are afraid to code.
 
 1. Visit Campaign Editor:
 
-.. image:: /_static/img/advanced_features/campaign_navigation.png
+   .. image:: /_static/img/advanced_features/campaign_navigation.png
 
 2. Swith to HTML & CSS editor:
 
-.. image:: /_static/img/advanced_features/campaign_navigation_html_css_editor.png
+   .. image:: /_static/img/advanced_features/campaign_navigation_html_css_editor.png
 
 3. Find a View you would like to convert a static copy at:
 
-.. image:: /_static/img/advanced_features/campaign_view_navigation.png
+   .. image:: /_static/img/advanced_features/campaign_view_navigation.png
 
 4. Find a copy that you’d like to convert into a Localization. You can hit `Cmd+F` (`Ctrl+F` on Windows) to search within HTML area.
 
-Static copy is basically a piece of text that sits inside HTML & CSS Editor and usually looks like this:
+   Static copy is basically a piece of text that sits inside HTML & CSS Editor and usually looks like this:
 
-.. code-block:: html
+   .. code-block:: html
 
-  <h1>
-    Get {{ advocate_incentive.description }}.
-  </h1>
+     <h1>
+       Get {{ advocate_incentive.description }}.
+     </h1>
 
-A piece that we are going to extract into Localizations is just a copy, without HTML tags. To do that, simply wrap the text into a variable notation like so:
+   A piece that we are going to extract into Localizations is just a copy, without HTML tags. To do that, simply wrap the text into a variable notation like so:
 
-.. code-block:: html
+   .. code-block:: html
 
-  <h1>
-    {{ "advocate_share_page_headline" | localize: "Get [[ advocate_incentive.description ]]." }}
-  </h1>
+     <h1>
+       {{ "advocate_share_page_headline" | localize: "Get [[ advocate_incentive.description ]]." }}
+     </h1>
 
 5. Go back to Editor to see newly created Localization:
 
-.. image:: /_static/img/advanced_features/campaign_localization_sidebar.png
+   .. image:: /_static/img/advanced_features/campaign_localization_sidebar.png
 
 .. raw:: html
 
   <h2>Few important things to remember</h2>
 
-1. Don’t forget to change `{{` into `[[` inside interpolation variables, otherwise variables will lose its function and become just a plain text.
-2. Keep in mind that `identifier` ("advocate_share_page_headline" in the example above) is a campaign-level Localization in fact, always remember to provide unique names for them, otherwise you will be overriding a value of one Localization.
+- Don’t forget to change `{{` into `[[` inside interpolation variables, otherwise variables will lose its function and become just a plain text.
+- Keep in mind that `identifier` ("advocate_share_page_headline" in the example above) is a campaign-level Localization in fact, always remember to provide unique names for them, otherwise you will be overriding a value of one Localization.
 
 .. warning::
 
-  Talkable does not allow coding up Localizations within CSS area. If you want to move some CSS property into localizations use inline <style> tag inside HTML area.
+   Talkable does not allow coding up Localizations within CSS area. If you want to move some CSS property into localizations use inline <style> tag inside HTML area.
 
 Moving Subject Line Into Localization
 -------------------------------------
@@ -73,7 +74,7 @@ Subject line is unique because its default value is set on the Advocate Signup/S
 
       <input name="email_subject" type="text" class="textfield" value="{{ 'friend_share_email_subject' | localize: 'Your friend [[ advocate_info.first_name ]] [[ advocate_info.last_name ]] gave you [[ friend_incentive.description ]]' | replace: '   ', ' ' | replace: '  ', ' ' }}" />
 
-  This code creates new Localization named "Friend share email subject" that you are able to change on the Advocate Signup/Share Page.
+   This code creates new Localization named "Friend share email subject" that you are able to change on the Advocate Signup/Share Page.
 
 2. Navigate to Friend Share email → Extra fields to see Email Subject field:
 
@@ -89,7 +90,7 @@ Subject line is unique because its default value is set on the Advocate Signup/S
         {{ custom_message_subject }}
       {% endif %}
 
-  The code snippet above checks if the Advocate provided any Subject at all. If not we take default Subject copy so Friend Share email does not come with a blank subject.
+   The code snippet above checks if the Advocate provided any Subject at all. If not we take default Subject copy so Friend Share email does not come with a blank subject.
 
 Color As Localization
 ---------------------
@@ -109,7 +110,7 @@ Another example would be localizing font color of a headline, all copy at once,
         border-color: {{ "advocate_share_page_button_color" | localize: "#f94d08", trait: "color" }};
       }
 
-    In the code example above we created new Color Localization with default HEX color `#f94d08` which is used for `background-color` and `border-color` CSS properties of `.button` selector. Whenever you set a new color inside Campaign Editor it will be changed across both places because we’re using the same Localization identifier in both places.
+   In the code example above we created new Color Localization with default HEX color `#f94d08` which is used for `background-color` and `border-color` CSS properties of `.button` selector. Whenever you set a new color inside Campaign Editor it will be changed across both places because we’re using the same Localization identifier in both places.
 
 3. New Color Localization appears under "Color" tab inside Campaign Editor:
 
@@ -132,7 +133,7 @@ Localizing Image asset can be handy if you want to AB test it. Here is how to do
         ...
       </div>
 
-    In the example above `share_page_background` is a name of an Image Localization. `share-page-background.jpg` is a name of an Asset (Files tab within HTML & CSS Editor).
+   In the example above `share_page_background` is a name of an Image Localization. `share-page-background.jpg` is a name of an Asset (Files tab within HTML & CSS Editor).
 
 3. Now we can see newly created Image Localization under "Images" tab:
 
@@ -145,13 +146,13 @@ In addition to localizing Images, Colors, and static copy Talkable allows you to
 
 An example can be to create an AB test for Equal Emphasis (all 3 sharing channels look visually equal) vs. Email Emphasis where email sharing form stands out:
 
-   .. image:: /_static/img/advanced_features/share_page_equal_emphasis.png
-      :height: 250 px
+.. image:: /_static/img/advanced_features/share_page_equal_emphasis.png
+  :height: 250 px
 
-   .. image:: /_static/img/advanced_features/share_page_email_emphasis.png
-      :height: 250 px
+.. image:: /_static/img/advanced_features/share_page_email_emphasis.png
+  :height: 250 px
 
-In order to chieve this AB test we need to
+In order to chieve this AB test we need to:
 
 1. Build two separate layouts using CSS cascades to style all nested children within a container block that holds all the content:
 
@@ -162,8 +163,8 @@ In order to chieve this AB test we need to
         ...
       </div>
 
-    The code above creates a local Liquid variable named `share_page_layout` and assigns `share_page_layout` Configuration Localization to it.
-    Then we optimize the variable value to be set as an HTML `class` attribute (downcase, replace spaces with hyphens) and set it as a part of a `class` attribute.
+   The code above creates a local Liquid variable named `share_page_layout` and assigns `share_page_layout` Configuration Localization to it.
+   Then we optimize the variable value to be set as an HTML `class` attribute (downcase, replace spaces with hyphens) and set it as a part of a `class` attribute.
 
 2. Now inside Campaign Editor we can see newly created Configuration Localization:
 
@@ -187,6 +188,6 @@ In order to chieve this AB test we need to
         }
       }
 
-    All other nested children can be styled following this pattern.
+   All other nested children can be styled following this pattern.
 
 4. Once you’re done with styling it is very easy to set up an AB test, just go back to Campaign Editor and click "Add A/B test variant" link. Once a Campaign goes Live it will start rotating both variants following AB test distribution rules (50:50 by default).
diff --git a/source/advanced_features/coupons.rst b/source/advanced_features/coupons.rst
index 5cadb3cbb..94833322d 100644
--- a/source/advanced_features/coupons.rst
+++ b/source/advanced_features/coupons.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: You can reward Advocate and their Friend with coupons. Talkable supports both one-time-use coupons as well as multi-use coupons.
+   :description: You can reward Advocate and their Friend with coupons. Talkable supports both one-time-use coupons as well as multi-use coupons.
 
 Coupons
 =======
@@ -35,7 +35,7 @@ There are several steps that need to be taken for this scenario:
 
 .. raw:: html
 
-  <h2>REST API to Create Coupons</h2>
+   <h2>REST API to Create Coupons</h2>
 
 Talkable can create coupons via a webhook using your REST API endpoint.
 Read :ref:`Create Coupon Webhook Documentation <web_hooks/create_coupon>` for implementation details.
@@ -55,18 +55,18 @@ Only the following characters are allowed in a coupon code:
 
 .. code-block:: text
 
-  A-Z 0-9 - _ / . % : * + @ & #
+   A-Z 0-9 - _ / . % : * + @ & #
 
 .. note::
-  Spaces are forbidden.
+   Spaces are forbidden.
 
 Try to avoid ambiguous characters. This simple solution generates a string of easily readable characters for activation codes.
 We do not want people confusing 8 with B, 1 with I, 0 with O, L with 1, etc.
 
 .. code-block:: ruby
 
-  # Generates a random string from a set of easily readable characters
-  def generate_activation_code(size = 6)
-    charset = ["2", "3", "4", "6", "7", "9", "A", "C", "D", "E", "F", "G", "H", "J", "K", "M", "N", "P", "Q", "R", "T", "V", "W", "X", "Y", "Z"]
-    (0...size).map { charset[rand(charset.size)] }.join
-  end
+   # Generates a random string from a set of easily readable characters
+   def generate_activation_code(size = 6)
+     charset = ["2", "3", "4", "6", "7", "9", "A", "C", "D", "E", "F", "G", "H", "J", "K", "M", "N", "P", "Q", "R", "T", "V", "W", "X", "Y", "Z"]
+     (0...size).map { charset[rand(charset.size)] }.join
+   end
diff --git a/source/advanced_features/customer_service_portal/overview.rst b/source/advanced_features/customer_service_portal/overview.rst
index 92927880d..e5c94b61e 100644
--- a/source/advanced_features/customer_service_portal/overview.rst
+++ b/source/advanced_features/customer_service_portal/overview.rst
@@ -21,12 +21,13 @@ The Customer Service Portal provides a simple search box that will allow you to
   If no county code is given, Talkable will try applying the USA and Canada codes and search with the resulting number.
 - **Order number**: the order number of a purchase.
 - **Coupon code**: the single-use coupon code issued as a reward to a referral program user.
-- **Personal coupon code**: the :ref:`personal coupon code <advanced_features/personal_coupon_sharing>`, shared by an Advocate.
+- **Personal coupon code**: the :ref:`personal coupon code <advanced_features/personal_coupon_sharing>`, shared by an Advocate
 
 The search query might produce multiple results. In such case, every matched user will be listed,
-showing some personal info (email and phone number) and, if present, other matched fields (i.e., order number and/or coupon code).
+showing some personal info (email and phone number) and, if present, other matched fields (i.e. order number and/or coupon code).
 To see more personal details, select a user from the list.
 
 Example of Customer Service Portal person lookup:
 
 .. image:: /_static/img/advanced_features/customer_service_portal/person_lookup.png
+
diff --git a/source/advanced_features/customer_service_portal/terminology.rst b/source/advanced_features/customer_service_portal/terminology.rst
index f17697a87..0366d90f8 100644
--- a/source/advanced_features/customer_service_portal/terminology.rst
+++ b/source/advanced_features/customer_service_portal/terminology.rst
@@ -15,30 +15,29 @@ Friend Email, and a Purchase made by a Referred Friend. Each referral is passed
 1. **In progress**: Talkable referral engine is processing the referral. Such action usually takes less than a second
    so it is highly unlikely that you will see this status. No rewards are issued at this point.
 
-2. **Pending**: a referral is pending approval. Talkable referral engine approves pending referrals
-   automatically with a delay set under fraud settings. A user can also approve a referral manually until
-   the auto-approval happens. Thus, if the referral fraud checks were passed successfully, each referral
-   will eventually become approved. No rewards are issued up until approval.
+2. **Pending**: a referral is pending approval. Talkable referral engine approves pending referrals automatically
+   with a delay set under fraud settings. A user can also approve a referral manually until the auto-approval happens.
+   Thus, if the referral fraud checks were passed successfully each referral will eventually become approved.
+   No rewards are issued up until approval.
 
 3. **Flagged**: due to having many different options to configure referral fraud checks,
-   it is not always possible to set up an automatic resolution for each referral. For such
-   cases, you may want to Flag referrals that are in a so-called grey area, where the
-   chance of fraud is around 50% and it is impossible to make the decision automatically.
+   it is not always possible to set up an automatic resolution for each referral.
+   For such cases, you may want to Flag referrals that are in a so-called grey area,
+   where the chance of fraud is around 50% and it is impossible to make the decision automatically.
    All flagged referrals are added to a queue and can be accessed inside CSP → Referrals.
    No rewards are issued at this point. All flagged referrals will be automatically resolved
    to either voided or approved status, depending on the fraud settings configuration.
-   It is recommended to void flagged referrals automatically so you can only approve valid
-   ones manually. As a result, this can save lots of time as most flagged referrals are
-   rather suspicious than valid.
+   It is recommended to void flagged referrals automatically so you can only approve valid ones manually.
+   As a result this can save lots of time as most flagged referrals are rather suspicious than valid.
 
 4. **Approved**: this is a valid referral status which either gets set by the Talkable referral engine
-   or by a user. Flagged referrals can also turn to approved. All rewards associated with
-   the referral are then passed to the next stage to verify if they can be issued.
+   or by a user. Flagged referrals can also turn to approved. All rewards associated
+   with the referral are then passed to the next stage to verify if they
+   can be issued.
 
-5. **Voided**: this status is set by a user manually if they decide a referral is invalid and there
-   should be no rewards issued as a result. Only pending and flagged referrals can be voided.
-   Talkable referral engine cannot set this status automatically. All rewards associated
-   with the referral are getting blocked as a result.
+5. **Voided**: this status is set by a user manually if they decide a referral is invalid and there should be no
+   rewards issued as a result. Only pending and flagged referrals can be voided. Talkable referral engine cannot set
+   this status automatically. All rewards associated with the referral are getting blocked as a result.
 
 6. **Blocked**: when some fraud checks are failed Talkable referral engine blocks the referral immediately. All rewards
    associated with the referral are getting blocked as a result.
@@ -60,3 +59,4 @@ This is what the person gets as a result of some action (incentive). Available r
 
 - **Blocked/No reward**: there was no reward created either because the associated referral was blocked according to
   Fraud Settings or because of other reasons: incentive criteria has blocked it, or the person was blocklisted.
+
diff --git a/source/advanced_features/customer_service_portal/use_case_1.rst b/source/advanced_features/customer_service_portal/use_case_1.rst
index 277d1e8b0..3ca745235 100644
--- a/source/advanced_features/customer_service_portal/use_case_1.rst
+++ b/source/advanced_features/customer_service_portal/use_case_1.rst
@@ -48,3 +48,4 @@ Let’s also expand fraud filters section to check the details:
 
 This looks like a valid referral. Let’s move on to
 :ref:`Use case #2 <advanced_features/customer_service_portal/use_case_2>`.
+
diff --git a/source/advanced_features/customer_service_portal/use_case_2.rst b/source/advanced_features/customer_service_portal/use_case_2.rst
index 218871358..583acd934 100644
--- a/source/advanced_features/customer_service_portal/use_case_2.rst
+++ b/source/advanced_features/customer_service_portal/use_case_2.rst
@@ -59,3 +59,4 @@ Here is what email statuses mean:
 - **Clicked**: Stephanie has clicked on the CTA inside the email.
 - **Scheduled**: the email will be sent on a specified date.
 - **Rejected**: the email was rejected by some reason.
+
diff --git a/source/advanced_features/customer_service_portal/use_case_3.rst b/source/advanced_features/customer_service_portal/use_case_3.rst
index c6153e03c..70a71f63d 100644
--- a/source/advanced_features/customer_service_portal/use_case_3.rst
+++ b/source/advanced_features/customer_service_portal/use_case_3.rst
@@ -69,12 +69,11 @@ Here is how to detect self-referrals in case you’ve got an email/call from a c
 1. Enter the customer’s email address in the Person Lookup.
 2. Review the “Referrals” tab and look for a “self-referral” alert:
 
-.. image:: /_static/img/advanced_features/customer_service_portal/self_referral.jpg
+   .. image:: /_static/img/advanced_features/customer_service_portal/self_referral.jpg
 
-3. Inspect the customer’s email address to see if it’s the same or similar to the Friends; you  can also inspect inside
-the referral details the IP address and cookie to see if they match:
+3. Inspect the customer’s email address to see if it’s the same or similar to the Friends; you  can also inspect inside the referral details the IP address and cookie to see if they match:
 
-.. image:: /_static/img/advanced_features/customer_service_portal/fraud_settings.jpg
+   .. image:: /_static/img/advanced_features/customer_service_portal/fraud_settings.jpg
 
 4. If it’s not obvious why the customer was flagged for self-referral (meaning that none of these three items matched),
    then you should click “Details” to dive deeper.
@@ -84,7 +83,7 @@ the referral details the IP address and cookie to see if they match:
    share as an Advocate and click on the share link as a Friend), and lastly, there’s a matching combination of IP address
    and user agent - meaning the Advocate and Friend were using the same device and IP address, in combination.
 
-.. image:: /_static/img/advanced_features/customer_service_portal/blocked_reasons.jpg
+   .. image:: /_static/img/advanced_features/customer_service_portal/blocked_reasons.jpg
 
 Cross referrals
 ---------------
@@ -94,3 +93,4 @@ occurs when an Advocate shares with a Friend who purchases and that same Friend
 in an attempt to get both the Advocate and Friend rewards.
 
 We identify this in the same way as described above.
+
diff --git a/source/advanced_features/customer_service_portal/use_case_4.rst b/source/advanced_features/customer_service_portal/use_case_4.rst
index b86418a3d..59e9f6e31 100644
--- a/source/advanced_features/customer_service_portal/use_case_4.rst
+++ b/source/advanced_features/customer_service_portal/use_case_4.rst
@@ -51,3 +51,4 @@ flagged/blocked ones. We see that the blocked reason in this case is “Matching
 “Similar email match”:
 
 .. image:: /_static/img/advanced_features/customer_service_portal/marked_as_fraud.jpg
+
diff --git a/source/advanced_features/customer_service_portal/use_case_5.rst b/source/advanced_features/customer_service_portal/use_case_5.rst
index 987887794..095513b51 100644
--- a/source/advanced_features/customer_service_portal/use_case_5.rst
+++ b/source/advanced_features/customer_service_portal/use_case_5.rst
@@ -11,13 +11,13 @@ on social media pages.
 To blocklist a user, first navigate to the “Blocklist” section of the Customer Service Portal:
 
 .. image:: /_static/img/advanced_features/customer_service_portal/blocklist.png
-  :width: 644 px
+   :width: 644 px
 
 Adding a user to the blocklist
 ------------------------------
 
 .. image:: /_static/img/advanced_features/customer_service_portal/adding_blocklist.png
-  :width: 436 px
+   :width: 436 px
 
 (We support adding users to a blocklist using two methods, by Email or by IP address. To add an email to the
 blocklist, just enter the email into the "Blocked emails” field and press “Save Changes”. Note that emails are
@@ -44,3 +44,4 @@ How do I UnBlocklist a user?
 If you realize that you made a mistake in Blocklisting a user who should actually be receiving rewards,
 all you have to do to take a user off the blocklist is to delete their email or IP from the list and then hit
 “Save Changes” again. It’s that easy.
+
diff --git a/source/advanced_features/customer_service_portal/use_case_6.rst b/source/advanced_features/customer_service_portal/use_case_6.rst
index 624f1b558..f8ed552c1 100644
--- a/source/advanced_features/customer_service_portal/use_case_6.rst
+++ b/source/advanced_features/customer_service_portal/use_case_6.rst
@@ -50,3 +50,4 @@ After creating the referral manually you will be taken to the newly created refe
 
 Advocate reward may be blocked due to incentive criteria, make sure to check the Advocate’s reward status as shown
 on the screenshot above.
+
diff --git a/source/advanced_features/facebook_login_share.rst b/source/advanced_features/facebook_login_share.rst
index a29154cb4..8f22fae50 100644
--- a/source/advanced_features/facebook_login_share.rst
+++ b/source/advanced_features/facebook_login_share.rst
@@ -20,8 +20,8 @@ Prerequisites
 
 Before you begin, ensure you have the following:
 
-   - Access to the Facebook Developer Console.
-   - A Facebook App ID.
+- Access to the Facebook Developer Console.
+- A Facebook App ID.
 
 Integration Steps
 -----------------
@@ -59,8 +59,10 @@ Creating a Facebook App ID
    - Go to the App Dashboard.
    - Click on "Create App" and select the appropriate permissions for your app.
    - Add Valid OAuth Redirect URIs, including:
-      - `https://www.talkable.com`
-      - Your custom domain, if applicable.
+
+     - `https://www.talkable.com`
+     - Your custom domain, if applicable.
+   
    - Save and copy the generated App ID.
 
 Error Handling
diff --git a/source/advanced_features/file_encryption.rst b/source/advanced_features/file_encryption.rst
index a6cdfca24..9a677ddc0 100644
--- a/source/advanced_features/file_encryption.rst
+++ b/source/advanced_features/file_encryption.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: This is a public key encryption program that has become the most popular standard for email encryption.
+   :description: This is a public key encryption program that has become the most popular standard for email encryption.
 
 File Encryption
 ===============
@@ -27,14 +27,14 @@ Here is a command to do it:
 
 .. code-block:: shell
 
-  curl https://d2jjzw81hqbuqv.cloudfront.net/integration/talkable_public_key.asc | gpg --import
+   curl https://d2jjzw81hqbuqv.cloudfront.net/integration/talkable_public_key.asc | gpg --import
 
 To check that the Talkable public key importing was done right, make sure that
 the next command is successful:
 
 .. code-block:: shell
 
-  gpg --list-keys dev@talkable.com
+   gpg --list-keys dev@talkable.com
 
 Encrypting
 ----------
@@ -43,7 +43,7 @@ To encrypt data, you can use the following syntax:
 
 .. code-block:: shell
 
-  gpg --encrypt --sign --armor -r dev@talkable.com name_of_file
+   gpg --encrypt --sign --armor -r dev@talkable.com name_of_file
 
 This encrypts data using the Talkable public key and signs it with your own
 private key to guarantee that it is coming from you. Encrypted files will have the
@@ -53,8 +53,8 @@ as well.
 
 .. note::
 
-  You should include a second ``"-r"`` recipient with your own email address if
-  you want to be able to read the encrypted message.
+   You should include a second ``"-r"`` recipient with your own email address if
+   you want to be able to read the encrypted message.
 
 Decrypting
 ----------
@@ -63,6 +63,6 @@ To decrypt a file simply call GPG on it:
 
 .. code-block:: shell
 
-  gpg file_name.asc
+   gpg file_name.asc
 
 .. _How To Use GPG to Encrypt and Sign Messages: https://www.digitalocean.com/community/tutorials/how-to-use-gpg-to-encrypt-and-sign-messages#set-up-gpg-keys
diff --git a/source/advanced_features/multi_currency.rst b/source/advanced_features/multi_currency.rst
index dc1dfa53b..a2ad2cbf5 100644
--- a/source/advanced_features/multi_currency.rst
+++ b/source/advanced_features/multi_currency.rst
@@ -67,9 +67,9 @@ with the currency pre-selected:
 Currency can also be provided directly in any of the following function calls,
 overriding the `authenticate_customer` data:
 
-  - `register_affiliate`
-  - `register_purchase`
-  - `register_event`
+- `register_affiliate`
+- `register_purchase`
+- `register_event`
 
 For example:
 
@@ -143,7 +143,7 @@ discounts in their familiar currency, enhancing transparency and trust during in
 
 For example:
 
-* A fixed discount of **$10 USD** will display as **€9 EUR** if the conversion rate at the time of checkout is 1 USD = 0.9 EUR.
+   A fixed discount of **$10 USD** will display as **€9 EUR** if the conversion rate at the time of checkout is 1 USD = 0.9 EUR.
 
 Shopify performs this conversion dynamically based on the customer's selected currency, simplifying the shopping
 experience for international buyers. For more details, refer to Shopify's guide on
diff --git a/source/advanced_features/passing_custom_data.rst b/source/advanced_features/passing_custom_data.rst
index aeb21a0ae..699c3c23b 100644
--- a/source/advanced_features/passing_custom_data.rst
+++ b/source/advanced_features/passing_custom_data.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: The custom properties variable allows you to transfer any custom data to Talkable as a collection of key-value pairs.
+   :description: The custom properties variable allows you to transfer any custom data to Talkable as a collection of key-value pairs.
 
 Pass Custom User Data
 =====================
@@ -17,7 +17,7 @@ across all Campaign Views.
 
 .. raw:: html
 
-  <h2>How to set</h2>
+   <h2>How to set</h2>
 
 **Initialization script**
 
@@ -57,29 +57,29 @@ The properties you add to the initialization script will be automatically passed
 
 .. note::
 
-  The values you pass in the ``custom_properties`` have to be JSON Key-Value pairs themselves,
-  meaning that complex nested data structures cannot be passed through.
-  Property names (e.g. ``eye_color``) can contain lowercase letters, numbers and ``_`` only and cannot begin with a number.
+    The values you pass in the ``custom_properties`` have to be JSON Key-Value pairs themselves,
+    meaning that complex nested data structures cannot be passed through.
+    Property names (e.g. ``eye_color``) can contain lowercase letters, numbers and ``_`` only and cannot begin with a number.
 
 .. raw:: html
 
-  <h2>How to use</h2>
+   <h2>How to use</h2>
 
 To access ``custom_properties`` in Talkable, use:
 
 .. code-block:: liquid
 
-  {{ advocate_custom_properties }}
-  {{ friend_custom_properties }}
-  {{ member_info.custom_properties }}
+   {{ advocate_custom_properties }}
+   {{ friend_custom_properties }}
+   {{ member_info.custom_properties }}
 
 Key-Value pairs can be referenced calling the desired data key, such as:
 
 .. code-block:: liquid
 
-  {{ advocate_custom_properties.eye_color }}
+   {{ advocate_custom_properties.eye_color }}
 
 .. note::
 
-  Any ``custom_properties`` data passed through is tied to the |advocate|, |friend|, or |loyalty_member|.
-  If Talkable receives a custom property that was previously defined for the user, the property gets overwritten with a new value.
+    Any ``custom_properties`` data passed through is tied to the |advocate|, |friend|, or |loyalty_member|.
+    If Talkable receives a custom property that was previously defined for the user, the property gets overwritten with a new value.
diff --git a/source/advanced_features/personal_coupon_sharing.rst b/source/advanced_features/personal_coupon_sharing.rst
index 5172b5b38..fdd8c3923 100644
--- a/source/advanced_features/personal_coupon_sharing.rst
+++ b/source/advanced_features/personal_coupon_sharing.rst
@@ -1,7 +1,7 @@
 .. _advanced_features/personal_coupon_sharing:
 
 .. meta::
-  :description: By clicking on the share link each Friend sees the discount on the Friend claim page.
+   :description: By clicking on the share link each Friend sees the discount on the Friend claim page.
 
 Advocate Personal Coupon Sharing
 ================================
@@ -119,9 +119,10 @@ As a result each Advocate may have multiple personal coupons associated with the
 **Q: What characters are allowed in the personal coupon?**
 
 A: Here is a list of validation rules that are defined globally for any coupons:
-  #. Coupon should be unique on a site level
-  #. Coupon value cannot be “SAMPLE-COUPON-CODE” (in any case)
-  #. All coupons are case insensitive, they are always normalized to uppercase and UTF8 encoding
-  #. Coupon length is between 3 and 255 characters
+  
+#. Coupon should be unique on a site level
+#. Coupon value cannot be “SAMPLE-COUPON-CODE” (in any case)
+#. All coupons are case insensitive, they are always normalized to uppercase and UTF8 encoding
+#. Coupon length is between 3 and 255 characters
 
 Any UTF8 characters are allowed (including spaces).
diff --git a/source/advanced_features/reg_ex.rst b/source/advanced_features/reg_ex.rst
index eb2e4b161..5c73de3cb 100644
--- a/source/advanced_features/reg_ex.rst
+++ b/source/advanced_features/reg_ex.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Talkable allows setting up of campaign placement “Shown on” / “Hidden on” criteria in two formats: relative match and regular expression.
+   :description: Talkable allows setting up of campaign placement “Shown on” / “Hidden on” criteria in two formats: relative match and regular expression.
 
 Setting up Campaign Placement criteria
 ======================================
diff --git a/source/advanced_features/rybbon.rst b/source/advanced_features/rybbon.rst
index f42109ef3..ed9715fa1 100644
--- a/source/advanced_features/rybbon.rst
+++ b/source/advanced_features/rybbon.rst
@@ -36,11 +36,11 @@ Example Usage
 
 2. **Custom Reward Amount for Rybbon Campaigns**
 
-Allows setting a custom reward amount for Rybbon campaigns with variable denomination. The minimum amount conforms to specific Rybbon gift card restrictions, and the maximum is 50.
+   Allows setting a custom reward amount for Rybbon campaigns with variable denomination. The minimum amount conforms to specific Rybbon gift card restrictions, and the maximum is 50.
 
-.. code-block:: liquid
+   .. code-block:: liquid
 
-   {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon: amount: 13.5 }}
+      {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon: amount: 13.5 }}
 
 Limitations
 -----------
diff --git a/source/advanced_features/segments.rst b/source/advanced_features/segments.rst
index f92fa7ca1..f5dc1857c 100644
--- a/source/advanced_features/segments.rst
+++ b/source/advanced_features/segments.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: While driving traffic to one of your campaigns, you can include a traffic source parameter as a URL query string. This will help to segment your reporting.
+   :description: While driving traffic to one of your campaigns, you can include a traffic source parameter as a URL query string. This will help to segment your reporting.
 
 Segments
 ========
@@ -20,32 +20,32 @@ criteria in there:
 
 .. code-block:: html
 
-  {% assign available_items = "sku1,sku2" | split: "," %}
-  {% assign user_items = advocate_origin.products | map: "product_id" %}
-  {% assign result = false %}
+   {% assign available_items = "sku1,sku2" | split: "," %}
+   {% assign user_items = advocate_origin.products | map: "product_id" %}
+   {% assign result = false %}
 
-  {% for available_item in available_items %}
-    {% for user_item in user_items %}
-      {% if user_item == available_item %}
-        {% assign result = true %}
-        {% break %}
-      {% endif %}
-    {% endfor %}
-  {% endfor %}
+   {% for available_item in available_items %}
+     {% for user_item in user_items %}
+       {% if user_item == available_item %}
+         {% assign result = true %}
+         {% break %}
+       {% endif %}
+     {% endfor %}
+   {% endfor %}
 
-  {{ result }}
+   {{ result }}
 
 Now only those customers who purchased a product with SKU of "SKU_GOES_HERE" will see a Campaign.
 The Campaign won’t show for any other product purchased.
 
 .. note::
 
-  In order to use this Campaign Join Criteria you need to make sure that the SKU numbers are passed
-  throught the integration first of all. To do that you need to go into Reports
-  (top header navigation) → Purchases → Click on "Details" link of any purchase and make sure there is "Product Id"
-  column with a valid "Product ID" value in place.
-  If there is no such column or it is blank you cannot use this feature unless you pass the following instructions
-  :ref:`Including Product Items <advanced_features/product_items>`.
+   In order to use this Campaign Join Criteria you need to make sure that the SKU numbers are passed
+   throught the integration first of all. To do that you need to go into Reports
+   (top header navigation) → Purchases → Click on "Details" link of any purchase and make sure there is "Product Id"
+   column with a valid "Product ID" value in place.
+   If there is no such column or it is blank you cannot use this feature unless you pass the following instructions
+   :ref:`Including Product Items <advanced_features/product_items>`.
 
 Please |contact_us| if you have any questions.
 
@@ -82,22 +82,23 @@ Example of usage with `register_purchase`:
 
 Example of usage with `authenticate_customer`:
 
-.. code-block:: javascript
+ .. code-block:: javascript
 
-  window._talkableq.push(['authenticate_customer', {
-    email: '', // Email of the customer. Example: 'customer@example.com'
-    first_name: '', // First name of the customer. Example: 'John'
-    last_name: '', // Last name of the customer. Example: 'Doe'
-    traffic_source: '', // The source of the traffic driven to the campaign. Example: 'facebook'
-    segment1: '', // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-    segment2: '', // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-    segment3: '' // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-  }]);
+       window._talkableq.push(['authenticate_customer', {
+         email: '', // Email of the customer. Example: 'customer@example.com'
+         first_name: '', // First name of the customer. Example: 'John'
+         last_name: '', // Last name of the customer. Example: 'Doe'
+         traffic_source: '', // The source of the traffic driven to the campaign. Example: 'facebook'
+         segment1: '', // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+         segment2: '', // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+         segment3: '' // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+       }]);
 
 In this example, `segment1`, `segment2`, and `segment3` attributes are passed through `authenticate_customer` to enable segmentation without requiring an Origin creation.
 
 .. note::
 
-  Segments can also be passed in `register_affiliate`, `register_purchase`, and `register_event`, providing flexibility for different integration scenarios.
+   Segments can also be passed in `register_affiliate`, `register_purchase`, and `register_event`, providing flexibility for different integration scenarios.
 
 This approach simplifies custom data handling for customers, allowing for unified data across various methods and optimizing segmentation management without additional calls.
+
diff --git a/source/advanced_features/shopify_coupons_auto_apply.rst b/source/advanced_features/shopify_coupons_auto_apply.rst
index 2c3ff501c..10190bc0e 100644
--- a/source/advanced_features/shopify_coupons_auto_apply.rst
+++ b/source/advanced_features/shopify_coupons_auto_apply.rst
@@ -44,11 +44,12 @@ This method involves including the discount code in the URL. This way, when a cu
       :class: is-minimal
 
    **Breakdown:**
-    - `{{ site_setup.url }}/discount/{{ coupon.code }}`: This applies the coupon code to the cart.
-    - `?redirect={{ site_setup.url }}`: This redirects the customer back to your store.
-    - `&utm_source=talkable&utm_medium={{ sharing_channel }}&utm_content={{ campaign_setup.name | encode_query_argument }}&utm_campaign={{ campaign_setup.id }}`: These are default UTM parameters used for tracking.
-    - `&tkbl_cvuuid={{ visitor_uuid }}&talkable_visitor_offer_id={{ friend_offer.id }}`: These parameters are specific to Talkable, to identify customer.
-    - `{% if coupon.code %}{% endif %}` - condition to check if we have coupon.
+
+   - `{{ site_setup.url }}/discount/{{ coupon.code }}`: This applies the coupon code to the cart.
+   - `?redirect={{ site_setup.url }}`: This redirects the customer back to your store.
+   - `&utm_source=talkable&utm_medium={{ sharing_channel }}&utm_content={{ campaign_setup.name | encode_query_argument }}&utm_campaign={{ campaign_setup.id }}`: These are default UTM parameters used for tracking.
+   - `&tkbl_cvuuid={{ visitor_uuid }}&talkable_visitor_offer_id={{ friend_offer.id }}`: These parameters are specific to Talkable, to identify customer.
+   - `{% if coupon.code %}{% endif %}` - condition to check if we have coupon.
 
 #. **Advocate destination URL:**
 
diff --git a/source/advanced_features/shopify_coupons_auto_sync.rst b/source/advanced_features/shopify_coupons_auto_sync.rst
index a4e7cf9c9..b677b1b23 100644
--- a/source/advanced_features/shopify_coupons_auto_sync.rst
+++ b/source/advanced_features/shopify_coupons_auto_sync.rst
@@ -113,12 +113,13 @@ Shopify Price Rule Changed Email Notification
 If you modify a Price Rules on Shopify, it could make them incompatible with the coupon lists they are attached to. In order to find out about such changes as early as possible, we have a daily monitoring job that checks that Price Rules have no critical differences from respective coupon lists.
 
 Attributes that are checked in this job are the following:
-  - `allocation_method` - must always be "across"
-  - `usage_limit` - must always be 1
-  - `value` - must correspond to coupon list amount
-  - `value_type` - must correspond to coupon list type
-  - `ends_at` - must be greater than or equal to coupon list expiration (and absent if coupon list has no expiration)
-  - `prerequisite_subtotal_range` - must match coupon list minimum subtotal
+  
+- `allocation_method` - must always be "across"
+- `usage_limit` - must always be 1
+- `value` - must correspond to coupon list amount
+- `value_type` - must correspond to coupon list type
+- `ends_at` - must be greater than or equal to coupon list expiration (and absent if coupon list has no expiration)
+- `prerequisite_subtotal_range` - must match coupon list minimum subtotal
 
 If any of these attributes differ from what they are expected to be and Talkable cannot fix that by updating a coupon list (see **Coupon list sync**), Talkable sends an email notification.
 
@@ -131,9 +132,8 @@ Talkable tries to keep up with the Price Rules assigned to coupon lists when/if
 
 As long as the Price Rule is otherwise valid for a coupon list, we update the coupon list’s:
 
-**expiration date** - only if Price Rule end date is further in the future (or absent)
-
-**minimum subtotal**
+- **expiration date** - only if Price Rule end date is further in the future (or absent)
+- **minimum subtotal**
 
 .. note::
   If there are any other changes in the Price Rule that make it not suitable for a certain coupon list, we won’t sync the coupon list. In this case, a Shopify Price Rule Changed Email Notification will be delivered and action will be required to fix the issue.
diff --git a/source/advanced_features/shopify_purchase_syncing.rst b/source/advanced_features/shopify_purchase_syncing.rst
index 0d32c5daf..3b8850905 100644
--- a/source/advanced_features/shopify_purchase_syncing.rst
+++ b/source/advanced_features/shopify_purchase_syncing.rst
@@ -63,8 +63,9 @@ In this setup Purchase Syncing is just ensuring that attributes passed with Java
 and notifies Talkable Integrations team in case it is not.
 
 Here is detailed explanation of this logic:
-   - Purchase Syncing tries to find Purchase in Talkable by Order Number (Shopify Purchase ID).
-   - If there is no such Purchase, the one will be registered with attributes described in `Shopify Webhook payload and Talkable Purchase attributes mapping`
-   - If such Purchase exists, Purchase Syncing compares **Email** and **Subtotal** with Shopify Webhook payload.
+   
+- Purchase Syncing tries to find Purchase in Talkable by Order Number (Shopify Purchase ID).
+- If there is no such Purchase, the one will be registered with attributes described in `Shopify Webhook payload and Talkable Purchase attributes mapping`
+- If such Purchase exists, Purchase Syncing compares **Email** and **Subtotal** with Shopify Webhook payload.
 
 In case these attributes differ, Talkable Integrations team will is notified. Otherwise, nothing happens and the existing Purchase data is kept unmodified.
diff --git a/source/advanced_features/single_sign_on.rst b/source/advanced_features/single_sign_on.rst
index 5f6ba27a8..0922ce48c 100644
--- a/source/advanced_features/single_sign_on.rst
+++ b/source/advanced_features/single_sign_on.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Talkable fully supports the SAML v2.0 standard, making it easy to add more security and convenience to your Talkable program.
+   :description: Talkable fully supports the SAML v2.0 standard, making it easy to add more security and convenience to your Talkable program.
 
 Single Sign-On (SSO)
 ====================
@@ -25,19 +25,19 @@ Here is some basic terminology to help you in this guide:
 
 .. container:: ptable
 
-  ======================== =========================================================================================
-  Parameter                Description
-  ======================== =========================================================================================
-  Identity Provider (IdP)  The software/service that verifies the identity of your users. For example, Okta, OneLogin,
-                           Active Directory, etc.
-  Service Provider (SP)    Talkable.
-  Metadata URL             URL for the provider’s metadata. Both the IdP and the SP should have a Metadata URL.
-  Issuer (Entity ID)       A unique string that identifies the provider issuing a SAML request. According to the SAML
-                           specification, the string should be a URL, though not all providers respect this.
-                           Not required by all providers.
-  Consumer URL             The Talkable (SP) URL that will receive SAML requests from your IdP.
-  IdP SSO Target URL       The IdP URL that will receive SAML requests from Talkable (the SP).
-  ======================== =========================================================================================
+   ======================== =========================================================================================
+   Parameter                Description
+   ======================== =========================================================================================
+   Identity Provider (IdP)  The software/service that verifies the identity of your users. For example, Okta, OneLogin,
+                            Active Directory, etc.
+   Service Provider (SP)    Talkable.
+   Metadata URL             URL for the provider’s metadata. Both the IdP and the SP should have a Metadata URL.
+   Issuer (Entity ID)       A unique string that identifies the provider issuing a SAML request. According to the SAML
+                            specification, the string should be a URL, though not all providers respect this.
+                            Not required by all providers.
+   Consumer URL             The Talkable (SP) URL that will receive SAML requests from your IdP.
+   IdP SSO Target URL       The IdP URL that will receive SAML requests from Talkable (the SP).
+   ======================== =========================================================================================
 
 Automatic Configuration
 -----------------------
@@ -60,15 +60,17 @@ If automatic configuration is not supported by your IdP, then try manual configu
 Manual Configuration
 --------------------
 
-Uncheck the box for “Automatically Configure from Metadata”.
+1. Uncheck the box for “Automatically Configure from Metadata”.
 
-Fill in the following fields:
-  * IdP Issuer (Entity ID)
-  * IdP SSO Target URL
-  * X.509 Certificate OR Certificate Fingerprint
-    (Talkable will automatically generate the fingerprint if the full X.509 certificate is provided)
+2. Fill in the following fields:
 
-Save the settings.
+   * IdP Issuer (Entity ID)
+   * IdP SSO Target URL
+   * X.509 Certificate OR Certificate Fingerprint
+     |br|
+     (Talkable will automatically generate the fingerprint if the full X.509 certificate is provided)
+
+3. Save the settings.
 
 Testing Single Sign-On
 ----------------------
@@ -77,7 +79,7 @@ Once you've configured SSO, you can test it as followed:
 
 .. raw:: html
 
-  <h4>IdP-initiated SSO</h4>
+   <h4>IdP-initiated SSO</h4>
 
 1. Log out of Talkable
 2. Log in to your IdP (e.g. Okta, OneLogin, etc.)
@@ -85,9 +87,10 @@ Once you've configured SSO, you can test it as followed:
 
 .. raw:: html
 
-  <h4>SP-initiated SSO</h4>
+   <h4>SP-initiated SSO</h4>
 
 1. Log out of Talkable
 2. Visit the SP-Initiated SSO URL (provided on the SSO configuration page in Talkable)
 
    .. image:: /_static/img/advanced_features/sso_sp_initiated_url.png
+
diff --git a/source/advanced_features/subscribing_to_events.rst b/source/advanced_features/subscribing_to_events.rst
index 61ed5a2c9..4c73c374c 100644
--- a/source/advanced_features/subscribing_to_events.rst
+++ b/source/advanced_features/subscribing_to_events.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Talkable JS integration script embeds Talkable campaign as an iframe.
+   :description: Talkable JS integration script embeds Talkable campaign as an iframe.
 
 Subscribing To Iframe Events
 ============================
@@ -31,8 +31,9 @@ Knowing the container `name` attribute of the iframe is `talkable-offer-iframe`
   });
 
 Notice two arguments passed in the callback:
-  - `data` object — the data passed by the iframe upon firing the event
-  - `iframe` object — iframe’s `HTML DOM reference`_
+
+- `data` object — the data passed by the iframe upon firing the event
+- `iframe` object — iframe’s `HTML DOM reference`_
 
 .. _HTML DOM reference: https://www.w3schools.com/jsref/dom_obj_frame.asp
 
@@ -40,12 +41,14 @@ Iframe Events List
 ------------------
 
 Talkable campaigns are equipped with the following set of events:
-  1. `offer_loaded` — Talkable iframe DOM ready event which is in fact the very first event that you can use to determine if the iframe is loaded.
-  2. `responsive_iframe_height` — fires every time iframe size gets changed. You can use it to detect changes in iframe size.
-     You can read more :ref:`here <responsive-views>`. Previously named as ``curebit_offer_iframe_broadcast``.
-  3. `offer_close` — fires when the close button is clicked. You can use this event to determine when user closes Talkable campaign, it then disappears from the screen.
-  4. `offer_triggered` — Talkable Trigger Widget iframe fires this event when user clicks on it. You can use this event to detect when the main offer iframe is about to show up.
-  5. `coupon_issued` — fires upon issuing coupon code as a reward for sharing. You can use it to determine when the user shares and receives their reward. `data.channel` tells which sharing channel was used and `data.coupon_code` stores the coupon code value.
-  6. `share_succeeded` — fires each time |advocate| shares. `data.channel` tells which sharing channel was used for the share.
-  7. `email_gating_passed` — fires when |friend| passes email gating on :ref:`Friend Claim Page <campaigns/views/offers_claim>`.
-  8. `email_gating_failed` — fires when |friend| fails to pass email gating on :ref:`Friend Claim Page <campaigns/views/offers_claim>`.
+
+1. `offer_loaded` — Talkable iframe DOM ready event which is in fact the very first event that you can use to determine if the iframe is loaded.
+2. `responsive_iframe_height` — fires every time iframe size gets changed. You can use it to detect changes in iframe size.
+   |br|
+   You can read more :ref:`here <responsive-views>`. Previously named as ``curebit_offer_iframe_broadcast``.
+3. `offer_close` — fires when the close button is clicked. You can use this event to determine when user closes Talkable campaign, it then disappears from the screen.
+4. `offer_triggered` — Talkable Trigger Widget iframe fires this event when user clicks on it. You can use this event to detect when the main offer iframe is about to show up.
+5. `coupon_issued` — fires upon issuing coupon code as a reward for sharing. You can use it to determine when the user shares and receives their reward. `data.channel` tells which sharing channel was used and `data.coupon_code` stores the coupon code value.
+6. `share_succeeded` — fires each time |advocate| shares. `data.channel` tells which sharing channel was used for the share.
+7. `email_gating_passed` — fires when |friend| passes email gating on :ref:`Friend Claim Page <campaigns/views/offers_claim>`.
+8. `email_gating_failed` — fires when |friend| fails to pass email gating on :ref:`Friend Claim Page <campaigns/views/offers_claim>`.
diff --git a/source/advanced_features/tremendous.rst b/source/advanced_features/tremendous.rst
index 1f1677f25..a3e794831 100644
--- a/source/advanced_features/tremendous.rst
+++ b/source/advanced_features/tremendous.rst
@@ -10,29 +10,31 @@ Tremendous Integration
 Reward advocates with gift cards from various retailers provided by Tremendous.
 
 Tremendous integration consists of several parts:
-  1. A campaign in Tremendous with the selected rewards for customers.
 
-  3. A "Tremendous" application installed from Talkable App Store. This application is responsible
-     for storing API tokens, enabling Talkable to request gift cards from Tremendous and insert the generated
-     claim links in the referral campaign theme.
+1. A campaign in Tremendous with the selected rewards for customers.
 
-  2. A referral campaign in Talkable having the following attributes:
+3. A "Tremendous" application installed from Talkable App Store. This application is responsible
+   for storing API tokens, enabling Talkable to request gift cards from Tremendous and insert the generated
+   claim links in the referral campaign theme.
 
-     - An Advocate Referral Incentive with "Tremendous" reward type
+2. A referral campaign in Talkable having the following attributes:
 
-       .. image:: /_static/img/advanced_features/tremendous_incentive.png
-          :width: 400
-          :alt: Creating a Tremendous Advocate Referral incentive
+   - An Advocate Referral Incentive with "Tremendous" reward type
 
-     - A :ref:`"tremendous" Liquid filter<tremendous_filter>` used in Reward Paid Email Page.
-       The filter generates a claim link within the specified Tremendous campaign.
+     .. image:: /_static/img/advanced_features/tremendous_incentive.png
+        :width: 400
+        :alt: Creating a Tremendous Advocate Referral incentive
 
-       .. code-block:: html
+   - A :ref:`"tremendous" Liquid filter<tremendous_filter>` used in Reward Paid Email Page.
+      
+     The filter generates a claim link within the specified Tremendous campaign.
 
-          <!-- An example of the claim link leading to Tremendous -->
-          <a href="{{ 'KBBYF5Q64BL4' | tremendous }}" target="_blank" title="{{ cta_text }}">
-            {{ cta_text }}
-          </a>
+     .. code-block:: html
+
+       <!-- An example of the claim link leading to Tremendous -->
+       <a href="{{ 'KBBYF5Q64BL4' | tremendous }}" target="_blank" title="{{ cta_text }}">
+       {{ cta_text }}
+       </a>
 
 **Contact us**
 
diff --git a/source/advanced_features/url_parameters.rst b/source/advanced_features/url_parameters.rst
index 6f54d4c58..9cfadfa2d 100644
--- a/source/advanced_features/url_parameters.rst
+++ b/source/advanced_features/url_parameters.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Talkable allows overriding some of the parameters right through URL query string.
+   :description: Talkable allows overriding some of the parameters right through URL query string.
 
 Using URL Parameters
 ====================
@@ -20,11 +20,11 @@ the page where Talkable campaign is integrated: http://example.com/share:
 
 .. code-block:: html
 
-  http://example.com/share?email=advocate%40example.com
+   http://example.com/share?email=advocate%40example.com
 
 Location parameters have higher priority than explicit parameters passed in the
 integration.
 
 .. note::
 
-  Don’t forget to escape URL parameters with URI parameter encoder.
+   Don’t forget to escape URL parameters with URI parameter encoder.
diff --git a/source/advanced_features/utm_tags.rst b/source/advanced_features/utm_tags.rst
index 4cceccb30..2834f8c92 100644
--- a/source/advanced_features/utm_tags.rst
+++ b/source/advanced_features/utm_tags.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: While driving traffic to one of your campaigns, you can include a UTM Tags parameters as a URL query string. This will help to segment your reporting.
+   :description: While driving traffic to one of your campaigns, you can include a UTM Tags parameters as a URL query string. This will help to segment your reporting.
 
 UTM Tags
 ========
@@ -12,14 +12,15 @@ channels. By correctly implementing UTM tags, marketers can gain valuable insigh
 the effectiveness of their campaigns and optimize their strategies accordingly.
 
 Components of UTM Tags:
-    - Source (utm_source): Identifies the specific source of the traffic, such as a search engine or newsletter.
-    - Medium (utm_medium): Specifies the marketing medium, such as email, social, or CPC (Cost Per Click).
-    - Campaign (utm_campaign): Specifies the name of the marketing campaign.
-    - Term (utm_term): Used for paid search keywords.
-    - Content (utm_content): Used to differentiate similar content, such as different versions of an ad.
+
+- Source (utm_source): Identifies the specific source of the traffic, such as a search engine or newsletter.
+- Medium (utm_medium): Specifies the marketing medium, such as email, social, or CPC (Cost Per Click).
+- Campaign (utm_campaign): Specifies the name of the marketing campaign.
+- Term (utm_term): Used for paid search keywords.
+- Content (utm_content): Used to differentiate similar content, such as different versions of an ad.
 
 Example of usage:
 
 .. code-block:: text
 
-  https://example1.com/friends?refer=friends&utm_source=example_source&utm_medium=example_medium
+   https://example1.com/friends?refer=friends&utm_source=example_source&utm_medium=example_medium
diff --git a/source/advanced_features/white_labeling.rst b/source/advanced_features/white_labeling.rst
index 7e639f28c..3ba9cb71b 100644
--- a/source/advanced_features/white_labeling.rst
+++ b/source/advanced_features/white_labeling.rst
@@ -45,7 +45,7 @@ Custom Email and Web domains can be configured in **Site Settings** → **Custom
    Click "Check DNS status" on Talkable custom domain settings to see the updated status of your domain
    (it could take up to 24 hours for the records to propagate).
 
-.. image:: /_static/img/advanced_features/custom_domain_missing_records.png
+   .. image:: /_static/img/advanced_features/custom_domain_missing_records.png
 
 .. _delegated-vs-self-managed:
 
diff --git a/source/advanced_features/white_labeling/godaddy.rst b/source/advanced_features/white_labeling/godaddy.rst
index c55ba215e..5f762650f 100644
--- a/source/advanced_features/white_labeling/godaddy.rst
+++ b/source/advanced_features/white_labeling/godaddy.rst
@@ -1,14 +1,21 @@
 .. _advanced_features/white_labeling/godaddy:
 
 .. meta::
-  :description: Learn how to add DNS records in GoDaddy to enable white-labeling.
+   :description: Learn how to add DNS records in GoDaddy to enable white-labeling.
 
 Adding DNS records in GoDaddy
 =============================
 
 .. note::
-  - The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain. `GoDaddy docs <https://www.godaddy.com/help/manage-dns-records-680>`_
-  - This instruction applies to domains that have GoDaddy name servers. If you purchased a GoDaddy domain, but use other service's name servers, you should add DNS records in the name server account.
+
+   The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
+
+`GoDaddy docs <https://www.godaddy.com/help/manage-dns-records-680>`_
+
+.. note::
+   This instruction applies to domains that have GoDaddy name servers.
+   If you purchased a GoDaddy domain, but use other service's name servers,
+   you should add DNS records in the name server account.
 
 #. Click **My Account** → **Domains**.
 
diff --git a/source/advanced_features/white_labeling/shopify.rst b/source/advanced_features/white_labeling/shopify.rst
index 5d2423f17..88b295cda 100644
--- a/source/advanced_features/white_labeling/shopify.rst
+++ b/source/advanced_features/white_labeling/shopify.rst
@@ -1,14 +1,18 @@
 .. _advanced_features/white_labeling/shopify:
 
 .. meta::
-  :description: Learn how to add DNS records in Shopify to enable white-labeling.
+   :description: Learn how to add DNS records in Shopify to enable white-labeling.
 
 Adding DNS records in Shopify
 =============================
 
 .. note::
-  - The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
-  - This instruction applies to domains that are transferred to Shopify or registered there in the first place. Third-party domains connected to Shopify should be managed in respective domain registries.
+   The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
+
+.. note::
+   This instruction applies to domains that are transferred to Shopify
+   or registered there in the first place.
+   Third-party domains connected to Shopify should be managed in respective domain registries.
 
 For delegated setup,
 
diff --git a/source/android_sdk.rst b/source/android_sdk.rst
index 018dba3af..ed93203c7 100644
--- a/source/android_sdk.rst
+++ b/source/android_sdk.rst
@@ -21,14 +21,31 @@ can use the following Talkable capabilities:
 
 - Track sales via the App and reward Advocate if a sale was driven through someone’s claim link
 
-Contents:
-
-.. toctree::
-
-   android_sdk/getting_started
-   android_sdk/integration
-   android_sdk/advanced
-   android_sdk/api
-   android_sdk/custom_deep_linking
-   android_sdk/testing
-   android_sdk/upgrade
+.. raw:: html
+
+   <h2 class="mts">Contents:</h2>
+
+.. grid:: 1 2 2 2
+
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 2 
+      
+         android_sdk/getting_started
+         android_sdk/integration
+         android_sdk/advanced
+    
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 2 
+        
+         android_sdk/api
+         android_sdk/custom_deep_linking
+         android_sdk/testing
+      
+      .. toctree::
+         :maxdepth: 1
+
+         android_sdk/upgrade
\ No newline at end of file
diff --git a/source/android_sdk/advanced.rst b/source/android_sdk/advanced.rst
index 7cfd102cd..7f0edf0a1 100644
--- a/source/android_sdk/advanced.rst
+++ b/source/android_sdk/advanced.rst
@@ -16,13 +16,10 @@ and ``error.getMessage()`` respectively.
 
 Here is a list of possible error codes from ``TalkableOfferLoadException`` with descriptions:
 
-   ``NETWORK_ERROR``: General network error
-
-   ``API_ERROR``: Talkable API unavailable
-
-   ``REQUEST_ERROR``: Bad request
-
-   ``CAMPAIGN_ERROR``: Campaign not found
+- ``NETWORK_ERROR``: General network error
+- ``API_ERROR``: Talkable API unavailable
+- ``REQUEST_ERROR``: Bad request
+- ``CAMPAIGN_ERROR``: Campaign not found
 
 Using multiple site slugs
 -------------------------
@@ -44,36 +41,36 @@ To use multiple site slugs (also known as IDs) in your application, follow these
 
    .. code-block:: xml
 
-     <application>
-         ...
-         <meta-data
-             android:name="tkbl-default-site-slug"
-             android:value="{{YOUR_DEFAULT_SITE_SLUG}}" />
-         ...
-     </application>
+      <application>
+          ...
+          <meta-data
+              android:name="tkbl-default-site-slug"
+              android:value="{{YOUR_DEFAULT_SITE_SLUG}}" />
+          ...
+      </application>
 
    or by passing it through ``Talkable.initialize`` in the ``Application``:
 
    .. code-block:: java
 
-     import com.talkable.sdk.Talkable;
-     import android.app.Application;
+      import com.talkable.sdk.Talkable;
+      import android.app.Application;
 
-     public class App extends Application {
-         @Override
-         public void onCreate() {
-             super.onCreate();
-             Talkable.initialize(this, "your-default-site-slug");
-         }
-     }
+      public class App extends Application {
+          @Override
+          public void onCreate() {
+              super.onCreate();
+              Talkable.initialize(this, "your-default-site-slug");
+          }
+      }
 
    .. note::
 
-     You can set the site slug at any time after initialization in the following way:
+      You can set the site slug at any time after initialization in the following way:
 
       .. code-block:: java
 
-        Talkable.setSiteSlug("some-site-slug");
+         Talkable.setSiteSlug("some-site-slug");
 
    Make sure to add the credentials for this site inside the manifest file.
    Otherwise, an exception will be raised.
@@ -92,28 +89,28 @@ Overriding default behaviour
 
    .. code-block:: java
 
-     import com.talkable.sdk.TalkableOfferFragment;
+      import com.talkable.sdk.TalkableOfferFragment;
 
-     public class OverriddenTalkableOfferFragment extends TalkableOfferFragment {
-         @Override
-         public void copyToClipboard(String string) {
-             super.copyToClipboard(string);
+      public class OverriddenTalkableOfferFragment extends TalkableOfferFragment {
+          @Override
+          public void copyToClipboard(String string) {
+              super.copyToClipboard(string);
 
-             Toast.makeText(getActivity(), "Text copied!", Toast.LENGTH_LONG).show();
-         }
-     }
+              Toast.makeText(getActivity(), "Text copied!", Toast.LENGTH_LONG).show();
+          }
+      }
 
 2. Pass Class of an activity you want to run a fragment in and the overriden fragment to
    `Talkable.showOffer` call:
 
    .. code-block:: java
 
-     Talkable.showOffer(activity, affiliateMember, OverridenTalkableOfferFragment.class, new TalkableErrorCallback<TalkableOfferLoadException>() {
-         @Override
-         public void onError(TalkableOfferLoadException error) {
-             // Error handling. Note that it runs on non UI thread
-         }
-     });
+      Talkable.showOffer(activity, affiliateMember, OverridenTalkableOfferFragment.class, new TalkableErrorCallback<TalkableOfferLoadException>() {
+          @Override
+          public void onError(TalkableOfferLoadException error) {
+              // Error handling. Note that it runs on non UI thread
+          }
+      });
 
 .. _fragment_listener:
 
@@ -122,16 +119,16 @@ If you want to implement custom offer closing handling you should implement
 
 .. code-block:: java
 
-  import com.talkable.sdk.TalkableOfferFragment.TalkableOfferFragmentListener;
+   import com.talkable.sdk.TalkableOfferFragment.TalkableOfferFragmentListener;
 
-  public class MyActivity implements TalkableOfferFragmentListener {
-      ...
-      @Override
-      public void onOfferClosed() {
-          finish();
-      }
-      ...
-  }
+   public class MyActivity implements TalkableOfferFragmentListener {
+       ...
+       @Override
+       public void onOfferClosed() {
+           finish();
+       }
+       ...
+   }
 
 .. _using_fragment_directly:
 
@@ -150,30 +147,30 @@ To use ``TalkableOfferFragment`` directly, follow these steps:
 
 .. code-block:: java
 
-  AffiliateMember affiliateMember = new AffiliateMember();
-  ...
+   AffiliateMember affiliateMember = new AffiliateMember();
+   ...
 
-  Talkable.loadOffer(affiliateMember, new TalkableCallback<String, TalkableOfferLoadException>() {
-      // Note that it runs on non UI thread
-      @Override
-      public void onSuccess(String offerCode) {
-          TalkableOfferFragment fragment = TalkableOfferFragment.newInstance(offerCode);
-          myMethodToDisplayTalkableOfferFragment(fragment);
-      }
+   Talkable.loadOffer(affiliateMember, new TalkableCallback<String, TalkableOfferLoadException>() {
+       // Note that it runs on non UI thread
+       @Override
+       public void onSuccess(String offerCode) {
+           TalkableOfferFragment fragment = TalkableOfferFragment.newInstance(offerCode);
+           myMethodToDisplayTalkableOfferFragment(fragment);
+       }
 
-      @Override
-      public void onError(TalkableOfferLoadException error) {
-          // Error handling
-      }
-   );
+       @Override
+       public void onError(TalkableOfferLoadException error) {
+           // Error handling
+       }
+    );
 
 .. note::
 
-  Make sure to `handle configuration changes`_, as ``TalkableOfferFragment``
-  is built on top of ``WebView`` and restoring its state is up to you. If you
-  need to reinitialize a fragment, you don't need to call ``loadOffer`` again.
-  Simply store the ``offerCode`` and use it to create a new ``TalkableOfferFragment``
-  instance.
+   Make sure to `handle configuration changes`_, as ``TalkableOfferFragment``
+   is built on top of ``WebView`` and restoring its state is up to you. If you
+   need to reinitialize a fragment, you don't need to call ``loadOffer`` again.
+   Simply store the ``offerCode`` and use it to create a new ``TalkableOfferFragment``
+   instance.
 
 Native integration via API
 --------------------------
diff --git a/source/android_sdk/api.rst b/source/android_sdk/api.rst
index e99f5d30e..c5d3cd9f3 100644
--- a/source/android_sdk/api.rst
+++ b/source/android_sdk/api.rst
@@ -39,10 +39,12 @@ You need to build `Origin` to create. There are three subclasses of this class.
 Hierarchy
 .........
 
-* `Origin` (Abstract)
-    * `AffiliateMember`
-    * `Event`
-        * `Purchase`
+*   `Origin` (Abstract)
+    
+    *   `AffiliateMember`
+    *   `Event`
+    
+        *   `Purchase`
 
 Building Origin
 ...............
@@ -51,45 +53,45 @@ You need to build `Origin` using one of examples below:
 
 .. code-block:: java
 
-  // Building customer, required for all types
-  String email = "advocate@example.com"; // Required
-  String idInYourApp = "a8db7683-0f7f-407e-8d12-af2d501035c8"; // Use unique identifier from your system, optional
-  String firstName = "John"; // Optional
-  String lastName = "Smith"; // Optional
-  Customer customer = new Customer(idInYourApp, firstName, lastName, email);
-
-  // Building AffiliateMember
-  AffiliateMember origin = new AffiliateMember();
-  origin.setCustomer(customer); // Required
-  origin.setCampaignTag("your-campaign-tag");
-
-  // Building Event
-  String eventNumber = "1"; // Required
-  String eventCategory = "event-category"; // Required
-  Double subtotal = 10.99; // Optional
-  String[] coupons = {"EXAMPLE-CODE"}; // Optional
-
-  Event origin = new Event(eventNumber, eventCategory, subtotal, coupons);
-  origin.setCustomer(customer); // Required
-  origin.setCampaignTag("your-campaign-tag");
-
-  // Build purchase
-  Double price = 10.99;
-  Integer quantity = 1;
-  String productId = "1";
-  Item item = new Item(subtotal, quantity, productId);
-  item.setTitle("Item Title"); // Optional
-  item.setUrl("https://site.com/product.html"); // Optional
-  item.setImageUrl("https://site.com/image.jpg"); // Optional
-
-  Double subtotal = price * quantity; // Required
-  String orderNumber = "123456"; // Required
-  String[] coupons = {"EXAMPLE-CODE-1", "EXAMPLE-CODE-2"}; // Optional
-
-  Purchase origin = new Purchase(subtotal, orderNumber, coupons);
-  origin.setCustomer(customer); // Required
-  origin.setCampaignTag("your-campaign-tag");
-  origin.addItem(item); // Optional
+    // Building customer, required for all types
+    String email = "advocate@example.com"; // Required
+    String idInYourApp = "a8db7683-0f7f-407e-8d12-af2d501035c8"; // Use unique identifier from your system, optional
+    String firstName = "John"; // Optional
+    String lastName = "Smith"; // Optional
+    Customer customer = new Customer(idInYourApp, firstName, lastName, email);
+
+    // Building AffiliateMember
+    AffiliateMember origin = new AffiliateMember();
+    origin.setCustomer(customer); // Required
+    origin.setCampaignTag("your-campaign-tag");
+
+    // Building Event
+    String eventNumber = "1"; // Required
+    String eventCategory = "event-category"; // Required
+    Double subtotal = 10.99; // Optional
+    String[] coupons = {"EXAMPLE-CODE"}; // Optional
+
+    Event origin = new Event(eventNumber, eventCategory, subtotal, coupons);
+    origin.setCustomer(customer); // Required
+    origin.setCampaignTag("your-campaign-tag");
+
+    // Build purchase
+    Double price = 10.99;
+    Integer quantity = 1;
+    String productId = "1";
+    Item item = new Item(subtotal, quantity, productId);
+    item.setTitle("Item Title"); // Optional
+    item.setUrl("https://site.com/product.html"); // Optional
+    item.setImageUrl("https://site.com/image.jpg"); // Optional
+
+    Double subtotal = price * quantity; // Required
+    String orderNumber = "123456"; // Required
+    String[] coupons = {"EXAMPLE-CODE-1", "EXAMPLE-CODE-2"}; // Optional
+
+    Purchase origin = new Purchase(subtotal, orderNumber, coupons);
+    origin.setCustomer(customer); // Required
+    origin.setCampaignTag("your-campaign-tag");
+    origin.addItem(item); // Optional
 
 API request
 ...........
@@ -99,17 +101,17 @@ If you have, you need call method like in the example below:
 
 .. code-block:: java
 
-  TalkableApi.createOrigin(origin, new Callback2<Origin, Offer>() {
-      @Override
-      public void onSuccess(Origin origin, Offer offer) {
-          // Process success
-      }
+    TalkableApi.createOrigin(origin, new Callback2<Origin, Offer>() {
+        @Override
+        public void onSuccess(Origin origin, Offer offer) {
+            // Process success
+        }
 
-      @Override
-      public void onError(ApiError error) {
-          // Process error
-      }
-  });
+        @Override
+        public void onError(ApiError error) {
+            // Process error
+        }
+    });
 
 .. _android-api-rewards:
 
@@ -120,37 +122,37 @@ This methods is used for retrieving rewards for user. Example:
 
 .. code-block:: java
 
-  TalkableApi.retrieveRewards(new Callback1<Reward[]>() {
-      @Override
-      public void onSuccess(Reward[] rewards) {
-          // Process success
-      }
+    TalkableApi.retrieveRewards(new Callback1<Reward[]>() {
+        @Override
+        public void onSuccess(Reward[] rewards) {
+            // Process success
+        }
 
-      @Override
-      public void onError(ApiError error) {
-          // Process error
-      }
-  });
+        @Override
+        public void onError(ApiError error) {
+            // Process error
+        }
+    });
 
 If you need get only rewards with some status or for other than user UUID,
 you need to pass this data to this method. Example:
 
 .. code-block:: java
 
-  Params params = new Params();
-  params.put("status", "Paid"); // Optional
-  params.put("visitor_uuid", "eb71e496-6567-41ec-a68c-49e96d101e0e"); // Some other uuid, optional
-  TalkableApi.retrieveRewards(params, new Callback1<Reward[]>() {
-      @Override
-      public void onSuccess(Reward[] rewards) {
-          // Process success
-      }
+    Params params = new Params();
+    params.put("status", "Paid"); // Optional
+    params.put("visitor_uuid", "eb71e496-6567-41ec-a68c-49e96d101e0e"); // Some other uuid, optional
+    TalkableApi.retrieveRewards(params, new Callback1<Reward[]>() {
+        @Override
+        public void onSuccess(Reward[] rewards) {
+            // Process success
+        }
 
-      @Override
-      public void onError(ApiError error) {
-          // Process error
-      }
-  });
+        @Override
+        public void onError(ApiError error) {
+            // Process error
+        }
+    });
 
 Retrieve offer
 --------------
@@ -159,18 +161,18 @@ This method is used to get offer details by it’s short code. Example:
 
 .. code-block:: java
 
-  String shortUrlCode = "ABCXYZ";
-  TalkableApi.retrieveOffer(shortUrlCode, new Callback1<Offer>() {
-      @Override
-      public void onSuccess(Offer newOffer) {
-          // Process success
-      }
+    String shortUrlCode = "ABCXYZ";
+    TalkableApi.retrieveOffer(shortUrlCode, new Callback1<Offer>() {
+        @Override
+        public void onSuccess(Offer newOffer) {
+            // Process success
+        }
 
-      @Override
-      public void onError(ApiError e) {
-          // Process error
-      }
-  });
+        @Override
+        public void onError(ApiError e) {
+            // Process error
+        }
+    });
 
 .. _android-api-sharing:
 
@@ -188,28 +190,28 @@ Use the ``createEmailShare`` method to share an offer via email.
 
 .. code-block:: java
 
-  String subject = "Email Subject"; // optional
-  String body = "Email custom message"; // optional
-  Boolean reminder = false; // whether Talkable should send a reminder email later; true by default; optional
-  ShareEmail email = new ShareEmail(subject, body, reminder); // optional
-
-  String recipients = "friend1@example.com,friend2@example.com"; // emails separated by commas; required
-  EmailOfferShare share = new EmailOfferShare(offer, recipients, email);
-  TalkableApi.createEmailShare(share, new Callback2<JsonElement, Reward>() {
-      @Override
-      public void onSuccess(JsonElement result, Reward reward) {
-          // Process success
-      }
-      @Override
-      public void onError(ApiError e) {
-          // Process error
-      }
-  });
+   String subject = "Email Subject"; // optional
+   String body = "Email custom message"; // optional
+   Boolean reminder = false; // whether Talkable should send a reminder email later; true by default; optional
+   ShareEmail email = new ShareEmail(subject, body, reminder); // optional
+
+   String recipients = "friend1@example.com,friend2@example.com"; // emails separated by commas; required
+   EmailOfferShare share = new EmailOfferShare(offer, recipients, email);
+   TalkableApi.createEmailShare(share, new Callback2<JsonElement, Reward>() {
+       @Override
+       public void onSuccess(JsonElement result, Reward reward) {
+           // Process success
+       }
+       @Override
+       public void onError(ApiError e) {
+           // Process error
+       }
+   });
 
 .. note::
 
-  ``JsonElement result`` from ``onSuccess(JsonElement result, Reward reward)``
-  contains data, described in |api_v2_share_via_email| under the ``result`` key
+   ``JsonElement result`` from ``onSuccess(JsonElement result, Reward reward)``
+   contains data, described in |api_v2_share_via_email| under the ``result`` key
 
 Social Share
 ............
diff --git a/source/android_sdk/deep_linking.rst b/source/android_sdk/deep_linking.rst
index 1291b14f4..218cc4149 100644
--- a/source/android_sdk/deep_linking.rst
+++ b/source/android_sdk/deep_linking.rst
@@ -12,10 +12,10 @@ your Android app.
 
 .. note::
 
-  Credentials, mentioned in this document (``YOUR_SITE_SLUG``, ``YOUR_TALKABLE_PUBLIC_API_KEY``,
-  ``YOUR_GETSOCIAL_APP_ID``, ``YOUR_LINK_DOMAIN_PREFIX``), will be provided
-  with the document. Make sure to replace corresponding placeholders
-  in examples with the providen values.
+   Credentials, mentioned in this document (``YOUR_SITE_SLUG``, ``YOUR_TALKABLE_PUBLIC_API_KEY``,
+   ``YOUR_GETSOCIAL_APP_ID``, ``YOUR_LINK_DOMAIN_PREFIX``), will be provided
+   with the document. Make sure to replace corresponding placeholders
+   in examples with the providen values.
 
 Application Attributes
 ----------------------
@@ -39,37 +39,37 @@ Talkable SDK is distributed as an Android Library in ``aar`` format.
 
    .. note::
 
-     To do this, open import popup using *File* → *New* → *New Module* → *Import .JAR/.AAR Package*
-     and add Talkable SDK as a module dependency to your main module
+      To do this, open import popup using *File* → *New* → *New Module* → *Import .JAR/.AAR Package*
+      and add Talkable SDK as a module dependency to your main module
 
 2. Add Talkable SDK dependencies to ``build.gradle``:
 
    .. code-block:: groovy
 
-     dependencies {
-         ...
-         implementation 'com.squareup.okhttp3:okhttp:3.2.0'
-         implementation 'com.facebook.android:facebook-android-sdk:[4,5)'
-         implementation 'im.getsocial:getsocial-core:[6,7)@aar'
-         implementation 'com.android.installreferrer:installreferrer:1.0'
-         implementation 'com.google.code.gson:gson:2.8.0'
-         implementation 'com.android.support:support-v4:27.1.1'
-         implementation project(':talkable-sdk')
-         ...
-     }
+      dependencies {
+          ...
+          implementation 'com.squareup.okhttp3:okhttp:3.2.0'
+          implementation 'com.facebook.android:facebook-android-sdk:[4,5)'
+          implementation 'im.getsocial:getsocial-core:[6,7)@aar'
+          implementation 'com.android.installreferrer:installreferrer:1.0'
+          implementation 'com.google.code.gson:gson:2.8.0'
+          implementation 'com.android.support:support-v4:27.1.1'
+          implementation project(':talkable-sdk')
+          ...
+      }
 
 3. Add GetSocial Maven Repository to the list of project dependency
    repositories inside your top-level ``build.gradle``:
 
    .. code-block:: groovy
 
-     allprojects {
-         repositories {
-             ...
-             maven { url 'http://maven.getsocial.im/' }
-             ...
-         }
-     }
+      allprojects {
+          repositories {
+              ...
+              maven { url 'http://maven.getsocial.im/' }
+              ...
+          }
+      }
 
 Configure Manifest
 ------------------
@@ -81,84 +81,84 @@ Open your ``AndroidManifest.xml`` file and configure it by following next steps:
 
    .. code-block:: xml
 
-     <application>
-         ...
-         <meta-data
-             android:name="tkbl-api-key-YOUR_SITE_SLUG"
-             android:value="YOUR_TALKABLE_PUBLIC_API_KEY" />
-         ...
-     </application>
+       <application>
+           ...
+           <meta-data
+               android:name="tkbl-api-key-YOUR_SITE_SLUG"
+               android:value="YOUR_TALKABLE_PUBLIC_API_KEY" />
+           ...
+       </application>
 
 2. Specify GetSocial App ID as a meta-data inside the ``<application>`` tag:
 
    .. code-block:: xml
 
-     <application>
-         ...
-         <meta-data
-             android:name="im.getsocial.sdk.AppId"
-             android:value="YOUR_GETSOCIAL_APP_ID" />
-         ...
-     </application>
+      <application>
+          ...
+          <meta-data
+              android:name="im.getsocial.sdk.AppId"
+              android:value="YOUR_GETSOCIAL_APP_ID" />
+          ...
+      </application>
 
 3. Add Content Provider for GetSocial SDK auto initialization inside the
    ``<application>`` tag:
 
    .. code-block:: xml
 
-     <application>
-         ...
-         <provider
-             android:authorities="YOUR_GETSOCIAL_APP_ID.AutoInitSdkContentProvider"
-             android:exported="false"
-             android:enabled="true"
-             android:name="im.getsocial.sdk.AutoInitSdkContentProvider" />
-         ...
-     </application>
+      <application>
+          ...
+          <provider
+              android:authorities="YOUR_GETSOCIAL_APP_ID.AutoInitSdkContentProvider"
+              android:exported="false"
+              android:enabled="true"
+              android:name="im.getsocial.sdk.AutoInitSdkContentProvider" />
+          ...
+      </application>
 
 4. Configure Install Referrer Receiver as the *first* receiver for ``INSTALL_REFERRER``
    inside the ``<application>`` tag:
 
    .. code-block:: xml
 
-     <application>
-         ...
-         <receiver android:name="im.getsocial.sdk.invites.MultipleInstallReferrerReceiver"  android:exported="true">
-             <intent-filter>
-                 <action android:name="com.android.vending.INSTALL_REFERRER"/>
-             </intent-filter>
-         </receiver>
-         ...
-     </application>
+      <application>
+          ...
+          <receiver android:name="im.getsocial.sdk.invites.MultipleInstallReferrerReceiver"  android:exported="true">
+              <intent-filter>
+                  <action android:name="com.android.vending.INSTALL_REFERRER"/>
+              </intent-filter>
+          </receiver>
+          ...
+      </application>
 
 5. Add the following intent filter to the activity, that should be opened from the
    deep link, inside the corresponding tag:
 
    .. code-block:: xml
 
-     <activity>
-         ...
-        <intent-filter>
-            <action android:name="android.intent.action.VIEW"/>
+      <activity>
+          ...
+         <intent-filter>
+             <action android:name="android.intent.action.VIEW"/>
 
-            <category android:name="android.intent.category.DEFAULT"/>
-            <category android:name="android.intent.category.BROWSABLE"/>
+             <category android:name="android.intent.category.DEFAULT"/>
+             <category android:name="android.intent.category.BROWSABLE"/>
 
-            <data
-                android:host="YOUR_GETSOCIAL_APP_ID"
-                android:scheme="getsocial"/>
-        </intent-filter>
+             <data
+                 android:host="YOUR_GETSOCIAL_APP_ID"
+                 android:scheme="getsocial"/>
+         </intent-filter>
 
-        <intent-filter>
-            <action android:name="android.intent.action.VIEW" />
+         <intent-filter>
+             <action android:name="android.intent.action.VIEW" />
 
-            <category android:name="android.intent.category.DEFAULT" />
-            <category android:name="android.intent.category.BROWSABLE" />
+             <category android:name="android.intent.category.DEFAULT" />
+             <category android:name="android.intent.category.BROWSABLE" />
 
-            <data android:scheme="tkbl-YOUR_SITE_SLUG" />
-        </intent-filter>
-        ...
-     </activity>
+             <data android:scheme="tkbl-YOUR_SITE_SLUG" />
+         </intent-filter>
+         ...
+      </activity>
 
 6. Setup App Links for Android 6+. App Links (supported on Android 6.0
    (API level 23) and higher) allow the user to be taken directly to the app
@@ -169,17 +169,17 @@ Open your ``AndroidManifest.xml`` file and configure it by following next steps:
 
    .. code-block:: xml
 
-     <activity>
+      <activity>
+          ...
+         <intent-filter android:autoVerify="true">
+             <action android:name="android.intent.action.VIEW" />
+             <category android:name="android.intent.category.DEFAULT" />
+             <category android:name="android.intent.category.BROWSABLE" />
+             <data android:scheme="https" android:host="YOUR_LINK_DOMAIN_PREFIX.gsc.im" />
+             <data android:scheme="https" android:host="YOUR_LINK_DOMAIN_PREFIX-gsalt.gsc.im" />
+         </intent-filter>
          ...
-        <intent-filter android:autoVerify="true">
-            <action android:name="android.intent.action.VIEW" />
-            <category android:name="android.intent.category.DEFAULT" />
-            <category android:name="android.intent.category.BROWSABLE" />
-            <data android:scheme="https" android:host="YOUR_LINK_DOMAIN_PREFIX.gsc.im" />
-            <data android:scheme="https" android:host="YOUR_LINK_DOMAIN_PREFIX-gsalt.gsc.im" />
-        </intent-filter>
-        ...
-     </activity>
+      </activity>
 
 SDK Initialization
 ------------------
@@ -188,34 +188,34 @@ SDK Initialization
 
    .. code-block:: java
 
-     import com.talkable.sdk.Talkable;
+      import com.talkable.sdk.Talkable;
 
-     public class App extends Application {
-         @Override
-         public void onCreate() {
-             super.onCreate();
-             Talkable.initialize(this);
-         }
-     }
+      public class App extends Application {
+          @Override
+          public void onCreate() {
+              super.onCreate();
+              Talkable.initialize(this);
+          }
+      }
 
    .. note::
 
-     Make sure to add your application class name as ``android:name`` parameter
-     of the ``<application>`` element in your manifest.
+      Make sure to add your application class name as ``android:name`` parameter
+      of the ``<application>`` element in your manifest.
 
 2. Call the ``Talkable.trackAppOpen`` method inside your main activity:
 
    .. code-block:: java
 
-     import com.talkable.sdk.Talkable;
+      import com.talkable.sdk.Talkable;
 
-     public class MainActivity extends Activity {
-         @Override
-         public void onCreate(Bundle savedInstanceState) {
-             super.onCreate();
-             Talkable.trackAppOpen(this);
-         }
-     }
+      public class MainActivity extends Activity {
+          @Override
+          public void onCreate(Bundle savedInstanceState) {
+              super.onCreate();
+              Talkable.trackAppOpen(this);
+          }
+      }
 
 Requirements
 ------------
@@ -225,3 +225,7 @@ The SDK supports Android 4.1 and later.
 .. _`GetSocial.im`: https://www.getsocial.im
 .. _`Android App Links docs`: https://developer.android.com/training/app-links/index.html
 .. _`Finding SHA256 fingerprint for Android signing keys`: https://docs.getsocial.im/knowledge-base/android-signing-key-sha256/
+
+.. container:: hidden
+
+   .. toctree::
diff --git a/source/android_sdk/getting_started.rst b/source/android_sdk/getting_started.rst
index 1e40be602..94d6f12c8 100644
--- a/source/android_sdk/getting_started.rst
+++ b/source/android_sdk/getting_started.rst
@@ -14,21 +14,21 @@ Installation
 
    .. code-block:: groovy
 
-     allprojects {
-       repositories {
-         ...
-         maven { url 'https://jitpack.io' }
-       }
-     }
+      allprojects {
+        repositories {
+          ...
+          maven { url 'https://jitpack.io' }
+        }
+      }
 
 2. Add TalkableSDK as a dependency to your module's *build.gradle* file.
 
    .. code-block:: groovy
 
-     dependencies {
-       ...
-       implementation 'com.github.talkable:android-sdk:0.5.12'
-     }
+      dependencies {
+        ...
+        implementation 'com.github.talkable:android-sdk:0.5.12'
+      }
 
 .. _setup_credentials:
 
@@ -37,21 +37,21 @@ Installation
 
    .. code-block:: xml
 
-     <application>
-         ...
-         <meta-data
-             android:name="tkbl-api-key-{{YOUR_SITE_ID}}"
-             android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
-         ...
-     </application>
+      <application>
+          ...
+          <meta-data
+              android:name="tkbl-api-key-{{YOUR_SITE_ID}}"
+              android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
+          ...
+      </application>
 
    .. note::
 
-     You can locate your credentials inside Talkable site:
+      You can locate your credentials inside Talkable site:
 
-     - Select site and go to **Dashboard** → **Settings** → **Site Settings** → **Integrations**.
-       Find **API integration** section and there you will see your API Keys and Site ID (also known as Site slug).
-       Use only the *Public API Key* in your production application.
+      - Select site and go to **Dashboard** → **Settings** → **Site Settings** → **Integrations**.
+        Find **API integration** section and there you will see your API Keys and Site ID (also known as Site slug).
+        Use only the *Public API Key* in your production application.
 
 .. _deep_linking_scheme:
 
@@ -60,17 +60,17 @@ Installation
 
    .. code-block:: xml
 
-     <activity>
-         ...
-         <intent-filter>
-             <action android:name="android.intent.action.VIEW" />
+      <activity>
+          ...
+          <intent-filter>
+              <action android:name="android.intent.action.VIEW" />
 
-             <category android:name="android.intent.category.DEFAULT" />
-             <category android:name="android.intent.category.BROWSABLE" />
+              <category android:name="android.intent.category.DEFAULT" />
+              <category android:name="android.intent.category.BROWSABLE" />
 
-             <data android:scheme="tkbl-{{YOUR_SITE_ID}}" />
-         </intent-filter>
-     </activity>
+              <data android:scheme="tkbl-{{YOUR_SITE_ID}}" />
+          </intent-filter>
+      </activity>
 
 .. _main_activity_setup:
 
@@ -78,80 +78,80 @@ Installation
 
    .. code-block:: java
 
-     import com.talkable.sdk.Talkable;
-     import android.app.Application;
+      import com.talkable.sdk.Talkable;
+      import android.app.Application;
 
-     public class App extends Application {
-         @Override
-         public void onCreate() {
-             super.onCreate();
-             Talkable.initialize(this);
-         }
-     }
+      public class App extends Application {
+          @Override
+          public void onCreate() {
+              super.onCreate();
+              Talkable.initialize(this);
+          }
+      }
 
    .. note::
 
-     Make sure to add your application class name as ``android:name`` parameter of
-     the ``<application>`` element in your manifest
+      Make sure to add your application class name as ``android:name`` parameter of
+      the ``<application>`` element in your manifest
 
 6. Call ``Talkable.trackAppOpen`` inside you main activity class, like this:
 
    .. code-block:: java
 
-     import com.talkable.sdk.Talkable;
-     import android.app.Activity;
+      import com.talkable.sdk.Talkable;
+      import android.app.Activity;
 
-     public class MainActivity extends Activity {
-         @Override
-         public void onCreate(Bundle savedInstanceState) {
-             ...
+      public class MainActivity extends Activity {
+          @Override
+          public void onCreate(Bundle savedInstanceState) {
+              ...
 
-             Talkable.trackAppOpen(this);
-         }
-     }
+              Talkable.trackAppOpen(this);
+          }
+      }
 
 Here is an example of ``AndroidManifest.xml`` file (with ``"demo-site"`` site
 ID) you should setup after steps above:
 
 .. code-block:: xml
 
-    <?xml version="1.0" encoding="utf-8"?>
-    <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-        package="com.talkable.demo">
+     <?xml version="1.0" encoding="utf-8"?>
+     <manifest xmlns:android="http://schemas.android.com/apk/res/android"
+         package="com.talkable.demo">
 
-        <application
-            android:allowBackup="true"
-            android:icon="@mipmap/ic_launcher"
-            android:label="@string/app_name"
-            android:supportsRtl="true"
-            android:theme="@style/AppTheme"
-            android:name=".App">
-            <activity android:name=".MainActivity">
-                <intent-filter>
-                    <action android:name="android.intent.action.MAIN" />
+         <application
+             android:allowBackup="true"
+             android:icon="@mipmap/ic_launcher"
+             android:label="@string/app_name"
+             android:supportsRtl="true"
+             android:theme="@style/AppTheme"
+             android:name=".App">
+             <activity android:name=".MainActivity">
+                 <intent-filter>
+                     <action android:name="android.intent.action.MAIN" />
 
-                    <category android:name="android.intent.category.LAUNCHER" />
-                </intent-filter>
+                     <category android:name="android.intent.category.LAUNCHER" />
+                 </intent-filter>
 
-                <intent-filter>
-                    <action android:name="android.intent.action.VIEW" />
+                 <intent-filter>
+                     <action android:name="android.intent.action.VIEW" />
 
-                    <category android:name="android.intent.category.DEFAULT" />
-                    <category android:name="android.intent.category.BROWSABLE" />
+                     <category android:name="android.intent.category.DEFAULT" />
+                     <category android:name="android.intent.category.BROWSABLE" />
 
-                    <data android:scheme="tkbl-demo-site" />
-                </intent-filter>
-            </activity>
+                     <data android:scheme="tkbl-demo-site" />
+                 </intent-filter>
+             </activity>
 
-            <!-- Talkable -->
+             <!-- Talkable -->
 
-            <meta-data
-                android:name="tkbl-api-key-demo-site"
-                android:value="nacsc9XseW4Kxne6AaJ" />
+             <meta-data
+                 android:name="tkbl-api-key-demo-site"
+                 android:value="nacsc9XseW4Kxne6AaJ" />
 
-            <!-- End Talkable -->
-        </application>
-    </manifest>
+             <!-- End Talkable -->
+         </application>
+     </manifest>
 
 Your environment is all set up! Now you need to
 :ref:`integrate <android_sdk/integration>` the Talkable campaign piece.
diff --git a/source/android_sdk/integration/post_purchase.rst b/source/android_sdk/integration/post_purchase.rst
index fbd28fb37..d58f58b73 100644
--- a/source/android_sdk/integration/post_purchase.rst
+++ b/source/android_sdk/integration/post_purchase.rst
@@ -18,43 +18,43 @@ Here is an example of a Purchase capturing, this action should be triggered on t
 
 .. code-block:: java
 
-  import com.talkable.sdk.Talkable;
-  ...
-  Double price = 10.99;
-  Integer quantity = 1;
-  String productId = "1";
-  Item item = new Item(subtotal, quantity, productId);
-  item.setTitle("Item Title"); // Optional
-  item.setUrl("https://site.com/product.html"); // Optional
-  item.setImageUrl("https://site.com/image.jpg"); // Optional
-
-  Double subtotal = price * quantity; // Required
-  String orderNumber = "123456"; // Required
-  String[] coupons = {"EXAMPLE-CODE-1", "EXAMPLE-CODE-2"}; // Optional
-
-  HashMap<String, String> customProperties = new HashMap<String, String>();
-  customProperties.put("property_key", "property_value");
-
-  Customer customer = new Customer(email);
-  customer.setCustomProperties(customProperties);
-
-  Purchase purchase = new Purchase(subtotal, orderNumber, coupons);
-  purchase.setCustomer(customer); // Required
-  purchase.addItem(item); // Optional
-
-  String campaignTag = "android-post-purchase";
-  purchase.setCampaignTag(campaignTag); // Optional
-
-  Activity activity = this;
-  Talkable.showOffer(activity, purchase, new TalkableErrorCallback<TalkableOfferLoadException>() {
-      @Override
-      public void onError(TalkableOfferLoadException error) {
-          // Error handling. Note that it runs on non UI thread
-      }
-  });
+   import com.talkable.sdk.Talkable;
+   ...
+   Double price = 10.99;
+   Integer quantity = 1;
+   String productId = "1";
+   Item item = new Item(subtotal, quantity, productId);
+   item.setTitle("Item Title"); // Optional
+   item.setUrl("https://site.com/product.html"); // Optional
+   item.setImageUrl("https://site.com/image.jpg"); // Optional
+
+   Double subtotal = price * quantity; // Required
+   String orderNumber = "123456"; // Required
+   String[] coupons = {"EXAMPLE-CODE-1", "EXAMPLE-CODE-2"}; // Optional
+
+   HashMap<String, String> customProperties = new HashMap<String, String>();
+   customProperties.put("property_key", "property_value");
+
+   Customer customer = new Customer(email);
+   customer.setCustomProperties(customProperties);
+
+   Purchase purchase = new Purchase(subtotal, orderNumber, coupons);
+   purchase.setCustomer(customer); // Required
+   purchase.addItem(item); // Optional
+
+   String campaignTag = "android-post-purchase";
+   purchase.setCampaignTag(campaignTag); // Optional
+
+   Activity activity = this;
+   Talkable.showOffer(activity, purchase, new TalkableErrorCallback<TalkableOfferLoadException>() {
+       @Override
+       public void onError(TalkableOfferLoadException error) {
+           // Error handling. Note that it runs on non UI thread
+       }
+   });
 
 .. note::
 
-  If Post Purchase campaign does not show up when testing make sure you have it Live
-  on the Campaigns listing with `android-post-purchase` tag or the tag you specified
-  in `setCampaignTag`.
+   If Post Purchase campaign does not show up when testing make sure you have it Live
+   on the Campaigns listing with `android-post-purchase` tag or the tag you specified
+   in `setCampaignTag`.
diff --git a/source/android_sdk/testing.rst b/source/android_sdk/testing.rst
index b6285b0a2..9be7f8167 100644
--- a/source/android_sdk/testing.rst
+++ b/source/android_sdk/testing.rst
@@ -16,10 +16,10 @@ the app is launched.
 
 .. code-block:: java
 
-  String initialSiteId = null; // pass null to use the Site ID specified in your manifest
-  boolean debug = true;
+   String initialSiteId = null; // pass null to use the Site ID specified in your manifest
+   boolean debug = true;
 
-  Talkable.initialize(this, initialSiteId, debug, null);
+   Talkable.initialize(this, initialSiteId, debug, null);
 
 You can use the last param to pass a custom device ID, allowing you to switch between user identities manually. This way
 you can use a single device to pose as an Advocate or Friend and easily replicate various scenarios. The custom device ID
@@ -27,12 +27,12 @@ will be applied only if debug is set to `true`.
 
 .. code-block:: java
 
-  String initialSiteId = null;
-  boolean debug = true;
-  String customDeviceId = "qa-advocate-007";
+   String initialSiteId = null;
+   boolean debug = true;
+   String customDeviceId = "qa-advocate-007";
 
-  Talkable.initialize(this, initialSiteId, debug, customDeviceId);
+   Talkable.initialize(this, initialSiteId, debug, customDeviceId);
 
 .. warning::
 
-  Debug mode must be turned off for release builds. Leaving it enabled will break the referral cycle and expose you to fraud.
+   Debug mode must be turned off for release builds. Leaving it enabled will break the referral cycle and expose you to fraud.
diff --git a/source/android_sdk/upgrade.rst b/source/android_sdk/upgrade.rst
index c5bdf57b5..a788012f7 100644
--- a/source/android_sdk/upgrade.rst
+++ b/source/android_sdk/upgrade.rst
@@ -88,38 +88,38 @@ To update from the previous version, please do following steps.
 
    .. code-block:: groovy
 
-     // From
-     compile 'com.google.code.gson:gson:2.7'
-     compile 'com.android.support:support-v4:25.3.1'
+      // From
+      compile 'com.google.code.gson:gson:2.7'
+      compile 'com.android.support:support-v4:25.3.1'
 
-     // To
-     compile 'com.google.code.gson:gson:2.8'
-     compile 'com.android.support:support-v4:26.1.0'
+      // To
+      compile 'com.google.code.gson:gson:2.8'
+      compile 'com.android.support:support-v4:26.1.0'
 
 2. Use ``showOffer`` functions with a callback parameter.
 
    .. code-block:: java
 
-     // From
-     showOffer(activity, origin);
+      // From
+      showOffer(activity, origin);
 
-     // To
-     showOffer(activity, origin, new TalkableErrorCallback<TalkableOfferLoadException>() {
-         @Override
-         public void onError(final TalkableOfferLoadException error) {
-             // Error handling. Note that it runs on non UI thread
-         }
-     });
+      // To
+      showOffer(activity, origin, new TalkableErrorCallback<TalkableOfferLoadException>() {
+          @Override
+          public void onError(final TalkableOfferLoadException error) {
+              // Error handling. Note that it runs on non UI thread
+          }
+      });
 
 3. Use ``Talkable.setSiteSlug`` functions without Context as a parameter.
 
    .. code-block:: java
 
-     // From
-     setSiteSlug(context, "site-slug");
+      // From
+      setSiteSlug(context, "site-slug");
 
-     // To
-     setSiteSlug("site-slug");
+      // To
+      setSiteSlug("site-slug");
 
 4. ``TalkableOfferFragmentListener`` interface implementation is optional now.
 
@@ -133,13 +133,13 @@ Read Contacts permission is optional from this version.
 In case you used ``import_contacts`` callback, you have to define ``READ_CONTACTS``
 permission inside the manifest:
 
-   .. code-block:: xml
+.. code-block:: xml
 
-     <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-       package="com.android.app.myapp" >
-       <uses-permission android:name="android.permission.READ_CONTACTS" />
-       ...
-     </manifest>
+    <manifest xmlns:android="http://schemas.android.com/apk/res/android"
+    package="com.android.app.myapp" >
+    <uses-permission android:name="android.permission.READ_CONTACTS" />
+    ...
+    </manifest>
 
 0.4.1
 -----
@@ -173,62 +173,62 @@ To update from the previous version, please do following steps.
 
    .. code-block:: xml
 
-     <!-- From -->
-     <application>
-         ...
-         <meta-data
-             android:name="TalkableApiKey"
-             android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
-         <meta-data
-             android:name="TalkableSiteSlug"
-             android:value="{{YOUR_SITE_SLUG}}" />
-         ...
-     </application>
-
-     <!-- To -->
-     <application>
-         ...
-         <meta-data
-             android:name="tkbl-api-key-{{YOUR_SITE_SLUG}}"
-             android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
-         ...
-     </application>
+      <!-- From -->
+      <application>
+          ...
+          <meta-data
+              android:name="TalkableApiKey"
+              android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
+          <meta-data
+              android:name="TalkableSiteSlug"
+              android:value="{{YOUR_SITE_SLUG}}" />
+          ...
+      </application>
+
+      <!-- To -->
+      <application>
+          ...
+          <meta-data
+              android:name="tkbl-api-key-{{YOUR_SITE_SLUG}}"
+              android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
+          ...
+      </application>
 
 3. Initialize Talkable in the ``Application``.
 
    .. code-block:: java
 
-     import com.talkable.sdk.Talkable;
-     import android.app.Application;
+      import com.talkable.sdk.Talkable;
+      import android.app.Application;
 
-     public class App extends Application {
-         @Override
-         public void onCreate() {
-             super.onCreate();
-             Talkable.initialize(this);
-         }
-     }
+      public class App extends Application {
+          @Override
+          public void onCreate() {
+              super.onCreate();
+              Talkable.initialize(this);
+          }
+      }
 
    .. note::
 
-     Make sure to add your application class name as ``android:name`` parameter of
-     the ``<application>`` element in your manifest
+      Make sure to add your application class name as ``android:name`` parameter of
+      the ``<application>`` element in your manifest
 
 4. Call ``Talkable.trackAppOpen`` inside you main activity class, like before.
 
    .. code-block:: java
 
-     import com.talkable.sdk.Talkable;
-     import android.app.Activity;
+      import com.talkable.sdk.Talkable;
+      import android.app.Activity;
 
-     public class MainActivity extends Activity {
-         @Override
-         public void onCreate(Bundle savedInstanceState) {
-             ...
+      public class MainActivity extends Activity {
+          @Override
+          public void onCreate(Bundle savedInstanceState) {
+              ...
 
-             Talkable.trackAppOpen(this);
-         }
-     }
+              Talkable.trackAppOpen(this);
+          }
+      }
 
 From this version defining of ``TalkableActivity`` and ``InstallReferrerReceiver``
 inside Android Manifest is not necessary.
diff --git a/source/api_v2.rst b/source/api_v2.rst
index 86d944b18..0d011454d 100644
--- a/source/api_v2.rst
+++ b/source/api_v2.rst
@@ -7,11 +7,20 @@
 API Reference
 #############
 
-Contents:
+.. grid:: 1 2 2 2
 
-.. toctree::
+   .. grid-item::
 
-   api_v2/intro
-   api_v2/flow
-   api_v2/origins
-   api_v2/referrals
+      .. toctree::
+         :maxdepth: 2 
+      
+         api_v2/intro
+    
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 2 
+        
+         api_v2/flow
+         api_v2/origins
+         api_v2/referrals
diff --git a/source/api_v2/flow.rst b/source/api_v2/flow.rst
index 2de54d831..64aba793b 100644
--- a/source/api_v2/flow.rst
+++ b/source/api_v2/flow.rst
@@ -50,9 +50,9 @@ This is the last step before |friend| proceeds to your site or app.
 - Edit your :ref:`Friend Claim Page <campaigns/views/offers_claim>` template or disable it for immediate redirect
 - Edit the Destination URL in *Extra* window
 
-**Important:**
+.. important::
 
-You need to pass the visitor `uuid` variable to your site via the destination URL GET parameter and store it somewhere in order to later pass it with |api_v2_origin|
+   You need to pass the visitor `uuid` variable to your site via the destination URL GET parameter and store it somewhere in order to later pass it with |api_v2_origin|
 
 Example destination URL: `http://merchant.com?tkbl_cvuuid={{visitor_uuid}}&utm_source=talkable&...`
 
diff --git a/source/api_v2/origins.rst b/source/api_v2/origins.rst
index 99c2079db..a9b208a8c 100644
--- a/source/api_v2/origins.rst
+++ b/source/api_v2/origins.rst
@@ -26,45 +26,45 @@ off-site transactions, or other off-site events.
 
 **Subscription:**
 
-* A company whose customers sign up for a monthly service by making an initial
-  ‘on-site’ payment, then are charged monthly on the backend for subsequent
-  subscription payments. This company would like to reward |advocate| users
-  (referrers) with a reward after their |friend| has been a member for three
-  billing cycles.
+A company whose customers sign up for a monthly service by making an initial
+‘on-site’ payment, then are charged monthly on the backend for subsequent
+subscription payments. This company would like to reward |advocate| users
+(referrers) with a reward after their |friend| has been a member for three
+billing cycles.
 
-  * Talkable’s :ref:`standard front-end <integration/custom/overview>`
-    integration captures the initial ‘on-site’ payment.
+* Talkable’s :ref:`standard front-end <integration/custom/overview>`
+  integration captures the initial ‘on-site’ payment.
 
-  * For Talkable to reward the |Advocate| after the third billing cycle of the
-    |friend| subscription, the Company must pass the subsequent subscription
-    data to Talkable’s |api_v2_origins| using ``"type": "Event"``.
+* For Talkable to reward the |Advocate| after the third billing cycle of the
+  |friend| subscription, the Company must pass the subsequent subscription
+  data to Talkable’s |api_v2_origins| using ``"type": "Event"``.
 
 **Off-Site Events:**
 
-* A company whose customers purchase product or perform events off-site. This
-  company would like to reward |advocate| users (referrers) with a reward after
-  their |friend| has purchased a product in the brick and mortar store, or
-  attended an in-person appointment.
+A company whose customers purchase product or perform events off-site. This
+company would like to reward |advocate| users (referrers) with a reward after
+their |friend| has purchased a product in the brick and mortar store, or
+attended an in-person appointment.
 
-  * Talkable’s :ref:`standard front-end <integration/custom/overview>`
-    integration captures an initial ‘on-site’ signup event if there is one.
+* Talkable’s :ref:`standard front-end <integration/custom/overview>`
+  integration captures an initial ‘on-site’ signup event if there is one.
 
-  * For Talkable to reward the |advocate| after the in-person |friend| store
-    purchase, or appointment attendance, the Company must pass the in-store
-    purchase, or appointment attendance data to Talkable’s |api_v2_origins| with
-    either ``"type": "Purchase"`` for a purchase or ``"type": "Event"`` for an
-    appointment attendance.
+* For Talkable to reward the |advocate| after the in-person |friend| store
+  purchase, or appointment attendance, the Company must pass the in-store
+  purchase, or appointment attendance data to Talkable’s |api_v2_origins| with
+  either ``"type": "Purchase"`` for a purchase or ``"type": "Event"`` for an
+  appointment attendance.
 
 **User Approval:**
 
-* User approval use cases start with customers who need to submit an application
-  by performing an initial ‘on-site’ sign-up event. This company would like to
-  reward |advocate| users (referrers) with a reward after their |friend|
-  application is approved.
+User approval use cases start with customers who need to submit an application
+by performing an initial ‘on-site’ sign-up event. This company would like to
+reward |advocate| users (referrers) with a reward after their |friend|
+application is approved.
 
-  * Talkable’s :ref:`standard front-end <integration/custom/overview>`
-    integration captures the initial ‘on-site’ application sign-up event.
+* Talkable’s :ref:`standard front-end <integration/custom/overview>`
+  integration captures the initial ‘on-site’ application sign-up event.
 
-  * In order for Talkable to reward the |advocate| after the |friend|
-    application approval, the Company must pass the approval data to Talkable’s
-    |api_v2_origins| using ``"type": "Event"``.
+* In order for Talkable to reward the |advocate| after the |friend|
+  application approval, the Company must pass the approval data to Talkable’s
+  |api_v2_origins| using ``"type": "Event"``.
diff --git a/source/api_v2/referrals.rst b/source/api_v2/referrals.rst
index 90e7c8ce6..e7fb8521c 100644
--- a/source/api_v2/referrals.rst
+++ b/source/api_v2/referrals.rst
@@ -15,18 +15,18 @@ The Talkable |api_v2_referrals| allows referrals to be approved or voided.
 
 **Voiding referrals after a purchase is returned or canceled:**
 
-* A company who wants to ensure an |advocate| does not receive referral Rewards
-  if the |friend| returns their purchase. To prevent the |advocate| from receiving
-  their referral reward, this company would call the Talkable |api_v2_referrals| with
-  ``{"status": "voided"}`` after the |friend| order is canceled.
+A company who wants to ensure an |advocate| does not receive referral Rewards
+if the |friend| returns their purchase. To prevent the |advocate| from receiving
+their referral reward, this company would call the Talkable |api_v2_referrals| with
+``{"status": "voided"}`` after the |friend| order is canceled.
 
 **Approving Referrals only after a specific CRM Event:**
 
-* A company who wants to approve referral rewards only after the |friend| order
-  has reached a certain state (ie, 'shipped’, or ‘no longer refundable’) can
-  control this Referral Approval with the Talkable |api_v2_referrals|. This company
-  would call the Talkable |api_v2_referrals| with ``{"status": "approved"}`` after
-  the |friend| order reaches the desired state.
+A company who wants to approve referral rewards only after the |friend| order
+has reached a certain state (ie, 'shipped’, or ‘no longer refundable’) can
+control this Referral Approval with the Talkable |api_v2_referrals|. This company
+would call the Talkable |api_v2_referrals| with ``{"status": "approved"}`` after
+the |friend| order reaches the desired state.
 
 .. note::
 
diff --git a/source/campaigns.rst b/source/campaigns.rst
index bf2016bce..567f372fb 100644
--- a/source/campaigns.rst
+++ b/source/campaigns.rst
@@ -29,41 +29,65 @@ To start editing Views simply visit ``Editor`` page from the Campaign dashboard.
 Campaign Types and Placements
 =============================
 
-+-------------------------------+---------------------------------+
-| .. toctree::                  | .. toctree::                    |
-|   :maxdepth: 2                |   :maxdepth: 2                  |
-|                               |                                 |
-|   campaigns/campaign_types    |   campaigns/campaign_placements |
-+-------------------------------+---------------------------------+
+.. grid:: 1 2 2 2
+
+    .. grid-item::
+
+        .. toctree::
+          :maxdepth: 2 
+        
+          campaigns/campaign_types
+        
+    .. grid-item::
+
+        
+        .. toctree::
+          :maxdepth: 2 
+        
+          campaigns/campaign_placements
 
 Campaign Structure
 ==================
 
-+-------------------------------+
-| .. toctree::                  |
-|   :maxdepth: 2                |
-|                               |
-|   campaigns/views             |
-+-------------------------------+
+.. grid:: 1 2 2 2
+
+    .. grid-item::
+
+        .. toctree::
+          :maxdepth: 2 
+        
+          campaigns/views
 
 Campaign Setup & tutorials
 ==========================
 
-+-------------------------------+-----------------------------+
-| .. toctree::                  | .. toctree::                |
-|   :maxdepth: 2                |   :maxdepth: 2              |
-|                               |                             |
-|   campaigns/tutorials         |   campaigns/editor          |
-|   campaigns/offers_expiration |                             |
-|   campaigns/localization      |                             |
-+-------------------------------+-----------------------------+
+.. grid:: 1 2 2 2
+
+    .. grid-item::
+
+        .. toctree::
+          :maxdepth: 2 
+        
+          campaigns/tutorials
+          campaigns/offers_expiration
+          campaigns/localization
+    
+    .. grid-item::
+
+        .. toctree::
+          :maxdepth: 2 
+        
+          campaigns/editor
 
 Designer Guide
 ==============
 
-+-------------------------------+
-| .. toctree::                  |
-|   :maxdepth: 2                |
-|                               |
-|   campaigns/designer          |
-+-------------------------------+
+.. grid:: 1 2 2 2
+
+    .. grid-item::
+
+        .. toctree::
+          :maxdepth: 2 
+        
+          campaigns/designer
+
diff --git a/source/campaigns/designer.rst b/source/campaigns/designer.rst
index a1c729e57..b43c7a52b 100644
--- a/source/campaigns/designer.rst
+++ b/source/campaigns/designer.rst
@@ -69,8 +69,8 @@ and solid ones:
 
 1. Purchase web-compatible font on https://www.myfonts.com
 
-.. image:: /_static/img/liquid/designer/image6.png
-   :alt: myfonts.com
+   .. image:: /_static/img/liquid/designer/image6.png
+      :alt: myfonts.com
 
 2. Purchase on https://fonts.adobe.com
 
diff --git a/source/campaigns/tutorials/global.rst b/source/campaigns/tutorials/global.rst
index 4601dc1ff..314d9d6a0 100644
--- a/source/campaigns/tutorials/global.rst
+++ b/source/campaigns/tutorials/global.rst
@@ -23,11 +23,14 @@ Allow showing coupon in the Friend Share Email and its reminder
 
 This option means that there could be only one visitor for each email share (one per email per offer). When this option is active such opportunities appear:
 
-**Show Coupon in the Friend Share Email and its reminder:**
+- **Show Coupon in the Friend Share Email and its reminder:**
+  
   Talkable allows you to control whether you want to generate a unique coupon code for each email share or all shares made by an Advocate should have an exact same coupon code associated with it. When using single-use coupons it is recommended to enable this option only if you want to show the coupon inside Friend Share email and its reminder(s).
 
-**{{ coupon_code_used }} interpolation:**
+- **{{ coupon_code_used }} interpolation:**
+  
   {{ coupon_code_used }} becomes available as an interpolation in Friend share email and its reminder(s). It allows you to check whether the coupon code has been used already at checkout.
 
-**Skip email gating:**
+- **Skip email gating:**
+  
   Allows you to make a smooth user experience for Friend where they can surpass email gating on the Friend Claim page when clicking from the Friend Share email and its reminder(s). This is done for Friend’s convenience.
diff --git a/source/campaigns/tutorials/offers_claim.rst b/source/campaigns/tutorials/offers_claim.rst
index d6550d991..bc5305abf 100644
--- a/source/campaigns/tutorials/offers_claim.rst
+++ b/source/campaigns/tutorials/offers_claim.rst
@@ -27,8 +27,8 @@ First of all, turn on email gating in Restricted settings:
 
 **Advanced Setup**
 
-1. 'Click to copy' functionality for coupon code
-2. 'Sign up for news' checkbox
-3. Email validation messages
+1. `Click to copy` functionality for coupon code
+2. `Sign up for news` checkbox
+3. `Email validation` messages
 
 .. include:: /samples/liquid/offers_claim/email_gating_advanced.rst
diff --git a/source/campaigns/views.rst b/source/campaigns/views.rst
index 28ee4721e..7f61226de 100644
--- a/source/campaigns/views.rst
+++ b/source/campaigns/views.rst
@@ -16,19 +16,14 @@ control appearance of each View by visiting Appearance:
 
 |br|
 |br|
-Understanding Page-Views is easy, just go through the glossary and learn who lands on
-what Page-View and where. Email-Views are more tricky in terms of understanding when
-they are sent. All Email-Views must go through a pre-validation step before they are
-sent:
+Understanding Page-Views is easy, just go through the glossary and learn who lands on what Page-View and where. Email-Views are more tricky in terms of understanding when they are sent. All Email-Views must go through a pre-validation step before they are sent:
 
-\1. Check if the Campaign View is in use (controlled inside Campaign Rules). Otherwise
-the email will never be sent.
+1. Check if the Campaign View is in use (controlled inside Campaign Rules). Otherwise the email will never be sent.
 
-.. image:: /_static/img/campaign/rules-views.png
+   .. image:: /_static/img/campaign/rules-views.png
 
-|br|
-2. Is the recipient email in a valid email format (i.e. Talkable mail servers can deliver an email to a real recipient)? If so, we move on to campaign specific rules
-to determine whether or not the email should be sent (see `Email sending conditions` section inside each Email-View).
+
+2. Is the recipient email in a valid email format (i.e. Talkable mail servers can deliver an email to a real recipient)? If so, we move on to campaign specific rules to determine whether or not the email should be sent (see `Email sending conditions` section inside each Email-View).
 
 After pre-validation Talkable campaign level validation kicks in:
 
diff --git a/source/campaigns/views/notifier_offers_share_via_email_reminder.rst b/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
index 693a99c8c..d5a96b414 100644
--- a/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
+++ b/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
@@ -31,8 +31,8 @@ particular email.
 
 By default the email is sent in 72 hours after the offer is shared.
 
-1. Main email sending criteria (unable to change):
+Main email sending criteria (unable to change):
 
-   1. If |friend| offer is active
-   2. Recipient (|friend|) was not referred by this offer yet
-   3. Current offer is the last one shared with the recipient (if were delayed few reminders Talkable sends the last one)
+-  If |friend| offer is active
+-  Recipient (|friend|) was not referred by this offer yet
+-  Current offer is the last one shared with the recipient (if were delayed few reminders Talkable sends the last one)
diff --git a/source/conf.py b/source/conf.py
index 296acbe88..9f421dc50 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -34,7 +34,7 @@
 extensions = [
     "sphinx_sitemap",
     "sphinx_copybutton",
-    "sphinx_favicon",
+    "sphinx_design",
 ]
 
 sitemap_url_scheme = "{link}"
@@ -108,8 +108,11 @@
 
 # The theme to use for HTML and HTML Help pages.  See the documentation for
 # a list of builtin themes.
-html_theme = "furo"
+# html_theme = "furo"
+# html_theme = "pydata_sphinx_theme"
+html_theme = "sphinx_book_theme"
 # html_style = 'talkable.css'
+html_css_files = ["talkable.css"]
 
 # Theme options are theme-specific and customize the look and feel of a theme
 # further.  For a list of options available for each theme, see the
@@ -123,42 +126,37 @@
 
 # The name for this set of Sphinx documents.  If None, it defaults to
 # "<project> v<release> documentation".
-html_title = ""
+html_title = "Talkable Documentation"
 
 # A shorter title for the navigation bar.  Default is the same as html_title.
 # html_short_title = None
 
 # The name of an image file (relative to this directory) to place at the top
 # of the sidebar.
-# html_logo = None
+html_logo = "_static/img/logo.svg"
 
 # The name of an image file (within the static path) to use as favicon of the
 # docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
 # pixels large.
-# html_favicon = None
-
-favicons = {
-    "rel": "icon",
-    "href": "img/favicon.ico",
-    "type": "image/vnd.microsoft.icon",
-}
+html_favicon = "_static/img/favicon.ico"
 
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
 html_static_path = ["_static"]
-html_css_files = [
-    "talkable.css",
-]
+# html_css_files = [
+#     "talkable.css",
+# ]
 html_theme_options = {
-    "light_logo": "img/logo.svg",
-    "dark_logo": "img/logo.svg",
-    "sidebar_hide_name": True,
-    "light_css_variables": {
-        "color-brand-primary": "#D36835",
-        "color-brand-content": "#D36835",
-        "color-brand-visited": "#D36835",
-    },
+    # "light_logo": "img/logo.svg",
+    # "dark_logo": "img/logo.svg",
+    # "sidebar_hide_name": True,
+    # "light_css_variables": {
+    #     "color-brand-primary": "#D36835",
+    #     "color-brand-content": "#D36835",
+    #     "color-brand-visited": "#D36835",
+    # },
+    "use_download_button": False,
 }
 
 # Add any extra paths that contain custom files (such as robots.txt or
diff --git a/source/custom_integration.rst b/source/custom_integration.rst
index 071391b2e..c84323c30 100644
--- a/source/custom_integration.rst
+++ b/source/custom_integration.rst
@@ -4,10 +4,8 @@
 Custom Integration
 ##################
 
-Contents:
-
 .. toctree::
-
+   
    custom_integration/crowdtwist
    custom_integration/chatgpt
    custom_integration/validity
diff --git a/source/custom_integration/recharge.rst b/source/custom_integration/recharge.rst
index 742f771cf..77868257e 100644
--- a/source/custom_integration/recharge.rst
+++ b/source/custom_integration/recharge.rst
@@ -21,21 +21,19 @@ Talkable integration with Recharge enables next use cases:
 2. Showing the Post Purchase campaign on subscription checkout with the ability to tweak it for Recharge flow specifically
 
 3. Coupon auto-sync.
-
-  Talkable will reward with coupons applicable on both Recharge and Shopify checkouts.
-
-  The offer should be equal for both Recharge and Shopify within the same campaign.
+   |br|
+   Talkable will reward with coupons applicable on both Recharge and Shopify checkouts.
+   The offer should be equal for both Recharge and Shopify within the same campaign.
 
 4. Coupon auto-apply.
-
-  Talkable will try to apply a coupon to the next charge of the customer’s subscription. This coupon will also be sent to the customer’s email in case they want to use it for Shopify instead.
-
-  **Version 2**  of the integration also allows for accrued discounts in case the customer refers multiple friends.
+   |br|
+   Talkable will try to apply a coupon to the next charge of the customer’s subscription. This coupon will also be sent to the customer’s email in case they want to use it for Shopify instead.
+   |br|
+   **Version 2**  of the integration also allows for accrued discounts in case the customer refers multiple friends.
 
 5. If the Gleam widget is enabled, it can behave differently depending on the customer’s actions (if it’s set up according to a non-default flow):
 
-  Once the Advocate receives a reward, they will be shown a Gleam widget that will be showing the coupon code as well as
-  a notice that the coupon would be automatically applied to the ongoing subscription if the advocate has the one. The discount is still available for use on regular Shopify flow, but once used it won’t be applied to the subscription of the customer.
+   Once the Advocate receives a reward, they will be shown a Gleam widget that will be showing the coupon code as well as a notice that the coupon would be automatically applied to the ongoing subscription if the advocate has the one. The discount is still available for use on regular Shopify flow, but once used it won’t be applied to the subscription of the customer.
 
 **Contact us**
 
diff --git a/source/email_marketing_and_automation.rst b/source/email_marketing_and_automation.rst
index 0f708c26e..84dc2a01f 100644
--- a/source/email_marketing_and_automation.rst
+++ b/source/email_marketing_and_automation.rst
@@ -9,32 +9,52 @@ Email Marketing & Automation
 
 With these tools, Talkable synchronizes all people who opt-in for Talkable marketing communication during signup. This way you will keep all your emails in one place in an automated way.
 
-Contents:
-
-.. toctree::
-
-   email_marketing_and_automation/bluecore
-   email_marketing_and_automation/braze
-   email_marketing_and_automation/cordial
-   email_marketing_and_automation/createsend
-   email_marketing_and_automation/cheetah
-   email_marketing_and_automation/klaviyo
-   email_marketing_and_automation/yotpo
-   email_marketing_and_automation/ometria
-   email_marketing_and_automation/oracle_bronto
-   email_marketing_and_automation/omnisend
-   email_marketing_and_automation/mailchimp
-   email_marketing_and_automation/sailthru
-   email_marketing_and_automation/sendgrid
-   email_marketing_and_automation/sfmc
-   email_marketing_and_automation/getresponse
-   email_marketing_and_automation/targetbay
-   email_marketing_and_automation/emarsys
-   email_marketing_and_automation/exponea
-   email_marketing_and_automation/hubspot
-   email_marketing_and_automation/iterable
-   email_marketing_and_automation/listrak
-   email_marketing_and_automation/attentive
-   email_marketing_and_automation/apsis
-   email_marketing_and_automation/what_counts_pro
-   email_marketing_and_automation/custom_app
+.. raw:: html
+
+   <h2 class="mts">Contents:</h2>
+
+.. grid:: 1 2 3 3
+
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 1
+      
+         email_marketing_and_automation/bluecore
+         email_marketing_and_automation/braze
+         email_marketing_and_automation/cordial
+         email_marketing_and_automation/createsend
+         email_marketing_and_automation/cheetah
+         email_marketing_and_automation/klaviyo
+         email_marketing_and_automation/yotpo
+         email_marketing_and_automation/ometria
+         
+    
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 1
+        
+         email_marketing_and_automation/oracle_bronto
+         email_marketing_and_automation/omnisend
+         email_marketing_and_automation/mailchimp
+         email_marketing_and_automation/sailthru
+         email_marketing_and_automation/sendgrid
+         email_marketing_and_automation/sfmc
+         email_marketing_and_automation/getresponse
+         email_marketing_and_automation/targetbay
+         email_marketing_and_automation/emarsys
+   
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 1
+
+         email_marketing_and_automation/exponea
+         email_marketing_and_automation/hubspot
+         email_marketing_and_automation/iterable
+         email_marketing_and_automation/listrak
+         email_marketing_and_automation/attentive
+         email_marketing_and_automation/apsis
+         email_marketing_and_automation/what_counts_pro
+         email_marketing_and_automation/custom_app
diff --git a/source/email_marketing_and_automation/attentive.rst b/source/email_marketing_and_automation/attentive.rst
index cd77a8862..ee85b20ce 100644
--- a/source/email_marketing_and_automation/attentive.rst
+++ b/source/email_marketing_and_automation/attentive.rst
@@ -7,10 +7,9 @@
 Attentive
 =========
 
-.. code-block:: text
+.. tip::
 
-   This is a custom integration that can be implemented with extra effort. If you wish to integrate this vendor,
-   please contact your Customer Success Manager to apply it to your campaigns.
+  This is a custom integration that can be implemented with extra effort. If you wish to integrate this vendor, please contact your Customer Success Manager to apply it to your campaigns.
 
 Talkable converts customers into brand advocates by enabling trusted, word-of-mouth referrals. Attentive connects with customers on the most engaging channel: SMS.
 
@@ -20,18 +19,18 @@ Together, Talkable and Attentive drive personalized brand engagement and the **a
 
 1. Capture phone numbers through Talkable to seamlessly grow your SMS subscriber list. The integration automatically passes these numbers to your Attentive messaging flow.
 
-  .. image:: /_static/img/email_marketing_and_automation/signup2.png
+   .. image:: /_static/img/email_marketing_and_automation/signup2.png
       :alt: Signup
 
 2. Promote refer-a-friend to your SMS list to facilitate increased sharing. Mobile messages have a 99% open rate.
 
-  **Sample SMS triggered post-purchase:**
+   **Sample SMS triggered post-purchase:**
 
-  Thanks for your recent purchase! A referral from you would mean a lot to us! Share ‘Brand name’ with friends & we’ll share $10 with you 😃
+     Thanks for your recent purchase! A referral from you would mean a lot to us! Share ‘Brand name’ with friends & we’ll share $10 with you 😃
 
 3. Trigger referral messages through SMS for increased engagement.
 
-  For example, send advocates their referral reward via text to increase redemptions and repeat shoppers.
+   For example, send advocates their referral reward via text to increase redemptions and repeat shoppers.
 
 App Store
 ---------
@@ -51,13 +50,13 @@ Here are the conditions when Talkable acquires phone numbers:
 
 1. Advocate signs up, provides phone number and opts in for Talkable marketing text messages:
 
-  .. image:: /_static/img/email_marketing_and_automation/phone_gating_ad.png
-    :alt: Subscribe
+   .. image:: /_static/img/email_marketing_and_automation/phone_gating_ad.png
+     :alt: Subscribe
 
 2. Friend passes phone gating and opts in for Talkable marketing text messages:
 
-  .. image:: /_static/img/email_marketing_and_automation/phone_gating_fr.png
-    :alt: Signup
+   .. image:: /_static/img/email_marketing_and_automation/phone_gating_fr.png
+     :alt: Signup
 
 Each ESP application allows custom attributes to be included with each request. The following interpolation variables are allowed:
 
@@ -79,22 +78,21 @@ Please use the following guide to start using an app you need:
 
 1. Navigate into the App store:
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_navigation.png
+   .. image:: /_static/img/email_marketing_and_automation/app_store_navigation.png
       :alt: App store navigation
 
 2. Choose an app you need by clicking “Install”
 
-3. Fill in all necessary fields. You can use tips on the right that
-instruct how to find all necessary credentials.
+3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 
 4. Complete installation and enable the app:
 
-  .. image:: /_static/img/email_marketing_and_automation/attentive_activate.png
+   .. image:: /_static/img/email_marketing_and_automation/attentive_activate.png
       :alt: Attentive
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
-  .. image:: /_static/img/email_marketing_and_automation/attentive_send_sample.png
+   .. image:: /_static/img/email_marketing_and_automation/attentive_send_sample.png
     :alt: Attentive send sample
 
 **Contact us**
diff --git a/source/email_marketing_and_automation/custom_app.rst b/source/email_marketing_and_automation/custom_app.rst
index e5e5551d5..9111db2a3 100644
--- a/source/email_marketing_and_automation/custom_app.rst
+++ b/source/email_marketing_and_automation/custom_app.rst
@@ -37,29 +37,30 @@ Talkable generates the signature using a `Base64 <https://en.wikipedia.org/wiki/
 
 To verify the signature, you should complete the following steps:
 
-**1. Prepare the** `payload_json` **string**
+1. Prepare the `payload_json` string
 
-  Create a JSON string from the payload of the request.
+   Create a JSON string from the payload of the request.
 
-**2. Determine the expected signature**
-  - Compute an hex encoded **HMAC** with the **SHA256** hash function. Use the **Webhook security key** as a key, and use the `payload_json` string as a message.
-  - Encode a computed hash with **Base64**
+2. Determine the expected signature
+  
+   - Compute an hex encoded **HMAC** with the **SHA256** hash function. Use the **Webhook security key** as a key, and use the `payload_json` string as a message.
+   - Encode a computed hash with **Base64**
 
-Your Talkable **Webhook security key** can be found in the Webhook set up page by navigating to **Menu** then **Webhooks**.
+   Your Talkable **Webhook security key** can be found in the Webhook set up page by navigating to **Menu** then **Webhooks**.
 
-.. image:: /_static/img/menu_webhooks_screenshot.png
-   :alt: Webhooks Menu Item
+   .. image:: /_static/img/menu_webhooks_screenshot.png
+      :alt: Webhooks Menu Item
 
-.. raw:: html
+   .. raw:: html
 
-   <hr>
+      <hr>
 
-.. image:: /_static/img/webhook_secret_key.png
-   :alt: Webhook Security Key
+   .. image:: /_static/img/webhook_secret_key.png
+      :alt: Webhook Security Key
 
-**3. Compare the signatures**
+3. Compare the signatures
 
-  Compare the signature from the header with your calculated signature.
+   Compare the signature from the header with your calculated signature.
 
 **Examples:**
 
diff --git a/source/email_marketing_and_automation/hubspot.rst b/source/email_marketing_and_automation/hubspot.rst
index 1157e8287..ada90af6a 100644
--- a/source/email_marketing_and_automation/hubspot.rst
+++ b/source/email_marketing_and_automation/hubspot.rst
@@ -11,13 +11,13 @@ With ESP apps clients can synchronize emails that Talkable acquires with their E
 
 1. Advocate signs up and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/subscribe.png
-    :alt: Subscribe
+   .. image:: /_static/img/email_marketing_and_automation/subscribe.png
+     :alt: Subscribe
 
 2. A friend passes email gating and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/signup.png
-    :alt: Signup
+   .. image:: /_static/img/email_marketing_and_automation/signup.png
+     :alt: Signup
 
 Each ESP application allows custom attributes to be included with each request. The following interpolation variables are allowed:
 
@@ -37,23 +37,23 @@ Please use the following guide to start using an app you need:
 
 1. Navigate into the App store:
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
+   .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
       :alt: App store step 1
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
+   .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
       :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
-  .. image:: /_static/img/email_marketing_and_automation/hubspot.jpg
+   .. image:: /_static/img/email_marketing_and_automation/hubspot.jpg
       :alt: hubspot
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
-  .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
-    :alt: Send sample payload
+   .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
+      :alt: Send sample payload
 
 **Contact us**
 
diff --git a/source/email_marketing_and_automation/klaviyo.rst b/source/email_marketing_and_automation/klaviyo.rst
index d980ef485..f7087bfcf 100644
--- a/source/email_marketing_and_automation/klaviyo.rst
+++ b/source/email_marketing_and_automation/klaviyo.rst
@@ -11,13 +11,13 @@ With ESP apps clients can synchronize emails that Talkable acquires with their E
 
 1. Advocate signs up and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/subscribe.png
-    :alt: Subscribe
+   .. image:: /_static/img/email_marketing_and_automation/subscribe.png
+     :alt: Subscribe
 
 2. A friend passes email gating and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/signup.png
-    :alt: Signup
+   .. image:: /_static/img/email_marketing_and_automation/signup.png
+     :alt: Signup
 
 Each ESP application allows custom attributes to be included with each request. The following interpolation variables are allowed:
 
@@ -25,8 +25,8 @@ Each ESP application allows custom attributes to be included with each request.
 2. ``{{ ip }}`` – a data object from which IP address either a signup or email gating occurred.
 3. ``{{ campaign }}`` – a data object with details about the campaign within which the email was captured.
 
-  .. image:: /_static/img/email_marketing_and_automation/variables.png
-    :alt: Variables
+   .. image:: /_static/img/email_marketing_and_automation/variables.png
+     :alt: Variables
 
 Each variable is described in the “Available variables” sidebar and can be expanded to see all nested properties.
 
@@ -37,23 +37,23 @@ Please use the following guide to start using an app you need:
 
 1. Navigate into the App store:
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-      :alt: App store step 1
+   .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
+     :alt: App store step 1
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+   .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
+     :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
-  .. image:: /_static/img/email_marketing_and_automation/klaviyo.png
-      :alt: klaviyo
+   .. image:: /_static/img/email_marketing_and_automation/klaviyo.png
+     :alt: klaviyo
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
-  .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
-    :alt: Send sample payload
+   .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
+     :alt: Send sample payload
 
 **Contact us**
 
diff --git a/source/email_marketing_and_automation/mailchimp.rst b/source/email_marketing_and_automation/mailchimp.rst
index 4513eddef..95e4ffc7b 100644
--- a/source/email_marketing_and_automation/mailchimp.rst
+++ b/source/email_marketing_and_automation/mailchimp.rst
@@ -9,15 +9,15 @@ Mailchimp
 
 With ESP apps clients can synchronize emails that Talkable acquires with their ESP. Here are the conditions when Talkable acquires emails:
 
-1. Advocate signs up and opts in for Talkable marketing emails:
+1.  Advocate signs up and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/subscribe.png
-    :alt: Subscribe
+    .. image:: /_static/img/email_marketing_and_automation/subscribe.png
+      :alt: Subscribe
 
-2. A friend passes email gating and opts in for Talkable marketing emails:
+2.  A friend passes email gating and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/signup.png
-    :alt: Signup
+    .. image:: /_static/img/email_marketing_and_automation/signup.png
+      :alt: Signup
 
 Each ESP application allows custom attributes to be included with each request. The following interpolation variables are allowed:
 
@@ -35,25 +35,25 @@ How to add a new app?
 
 Please use the following guide to start using an app you need:
 
-1. Navigate into the App store:
+1.  Navigate into the App store:
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-    :alt: App store step 1
+    .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
+      :alt: App store step 1
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+    .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
+        :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
-4. Complete installation and enable the app:
+4.  Complete installation and enable the app:
 
-  .. image:: /_static/img/email_marketing_and_automation/mailchimp.png
-      :alt: mailchimp
+    .. image:: /_static/img/email_marketing_and_automation/mailchimp.png
+        :alt: mailchimp
 
-5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
+5.  Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
-  .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
-    :alt: Send sample payload
+    .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
+      :alt: Send sample payload
 
 **Contact us**
 
diff --git a/source/email_marketing_and_automation/oracle_bronto.rst b/source/email_marketing_and_automation/oracle_bronto.rst
index 28388ab4c..7c24e4713 100644
--- a/source/email_marketing_and_automation/oracle_bronto.rst
+++ b/source/email_marketing_and_automation/oracle_bronto.rst
@@ -9,15 +9,15 @@ Oracle Bronto
 
 With ESP apps clients can synchronize emails that Talkable acquires with their ESP. Here are the conditions when Talkable acquires emails:
 
-1. Advocate signs up and opts in for Talkable marketing emails:
+1.  Advocate signs up and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/subscribe.png
-    :alt: Subscribe
+    .. image:: /_static/img/email_marketing_and_automation/subscribe.png
+      :alt: Subscribe
 
-2. A friend passes email gating and opts in for Talkable marketing emails:
+2.  A friend passes email gating and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/signup.png
-    :alt: Signup
+    .. image:: /_static/img/email_marketing_and_automation/signup.png
+      :alt: Signup
 
 Each ESP application allows custom attributes to be included with each request. The following interpolation variables are allowed:
 
@@ -35,25 +35,25 @@ How to add a new app?
 
 Please use the following guide to start using an app you need:
 
-1. Navigate into the App store:
+1.  Navigate into the App store:
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-      :alt: App store step 1
+    .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
+        :alt: App store step 1
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+    .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
+        :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
-4. Complete installation and enable the app:
+4.  Complete installation and enable the app:
 
-  .. image:: /_static/img/email_marketing_and_automation/oracle_bronto.jpg
-      :alt: Oracle Bronto
+    .. image:: /_static/img/email_marketing_and_automation/oracle_bronto.jpg
+        :alt: Oracle Bronto
 
-5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
+5.  Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
-  .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
-    :alt: Send sample payload
+    .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
+      :alt: Send sample payload
 
 **Contact us**
 
diff --git a/source/email_marketing_and_automation/sailthru.rst b/source/email_marketing_and_automation/sailthru.rst
index af8417e3f..d9171305f 100644
--- a/source/email_marketing_and_automation/sailthru.rst
+++ b/source/email_marketing_and_automation/sailthru.rst
@@ -11,13 +11,13 @@ With ESP apps clients can synchronize emails that Talkable acquires with their E
 
 1. Advocate signs up and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/subscribe.png
-    :alt: Subscribe
+   .. image:: /_static/img/email_marketing_and_automation/subscribe.png
+     :alt: Subscribe
 
 2. A friend passes email gating and opts in for Talkable marketing emails:
 
-  .. image:: /_static/img/email_marketing_and_automation/signup.png
-    :alt: Signup
+   .. image:: /_static/img/email_marketing_and_automation/signup.png
+     :alt: Signup
 
 Each ESP application allows custom attributes to be included with each request. The following interpolation variables are allowed:
 
@@ -37,23 +37,23 @@ Please use the following guide to start using an app you need:
 
 1. Navigate into the App store:
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-      :alt: App store step 1
+   .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
+       :alt: App store step 1
 
-  .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+   .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
+       :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
-  .. image:: /_static/img/email_marketing_and_automation/sailthru.jpg
-      :alt: Sailthru
+   .. image:: /_static/img/email_marketing_and_automation/sailthru.jpg
+       :alt: Sailthru
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
-  .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
-    :alt: Send sample payload
+   .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
+     :alt: Send sample payload
 
 **Contact us**
 
diff --git a/source/index.rst b/source/index.rst
index 614fecdab..a045235ab 100644
--- a/source/index.rst
+++ b/source/index.rst
@@ -8,82 +8,73 @@
 .. meta::
    :description: Talkable campaigns, features and integration docs for referral program launch and settings.
 
-Talkable Basics
-===============
+.. grid:: 1 2 2 2
 
-+------------------------------------+--------------------------------+
-| .. toctree::                       | .. toctree::                   |
-|   :maxdepth: 2                     |   :maxdepth: 2                 |
-|                                    |                                |
-|   campaigns                        |   advanced_features            |
-+------------------------------------+--------------------------------+
+    .. grid-item::
 
-|br|
+        .. raw:: html
 
-Talkable JS Integration
-=======================
+          <h3>Talkable Basics</h3>
 
-This section comes with full documentation for Talkable integration into E-Commerce store as well as into any SaaS product.
+        .. toctree::
+          :maxdepth: 2 
+        
+          campaigns
+          advanced_features
+        
+        .. raw:: html
 
-+------------------------------------+------------------------------------+
-| .. toctree::                       | .. toctree::                       |
-|   :maxdepth: 2                     |   :maxdepth: 2                     |
-|                                    |                                    |
-|   integration/custom_integration   |   integration/loyalty              |
-|                                    |                                    |
-|                                    |   integration/ecommerce_platforms  |
-+------------------------------------+------------------------------------+
+          <h3>Custom Integration</h3>
 
-.. raw:: html
+        .. toctree::
+          :maxdepth: 2 
+        
+          custom_integration
 
-  <p>&nbsp;</p>
+    .. grid-item::
 
-Email Marketing & Automation
-============================
+        .. raw:: html
 
-With these apps Talkable synchronizes all people who opt in for Talkable email marketing during signup. This way you will keep all your emails in one place in an automated way.
+          <h3>Email Marketing & Automation</h3>
 
-+-----------------------------------+
-| .. toctree::                      |
-|   :maxdepth: 2                    |
-|                                   |
-|   email_marketing_and_automation  |
-+-----------------------------------+
+        .. toctree::
+          :maxdepth: 2 
+        
+          email_marketing_and_automation
 
-Custom Integration
-==================
+        .. raw:: html
 
-+-----------------------+
-| .. toctree::          |
-|   :maxdepth: 2        |
-|                       |
-|   custom_integration  |
-+-----------------------+
+          <h3>JS Integration</h3>
 
-Talkable Back-end Integration
-=============================
+        .. toctree::
+          :maxdepth: 2 
+        
+          integration/custom_integration
+          integration/loyalty
+          integration/ecommerce_platforms 
+        
 
-Follow one of these sections in case you need to get or send data from/to Talkable.
+    .. grid-item::
 
-+--------------------+--------------------+
-| .. toctree::       | .. toctree::       |
-|   :maxdepth: 2     |   :maxdepth: 2     |
-|                    |                    |
-|   api_v2           |   web_hooks        |
-+--------------------+--------------------+
+        .. raw:: html
 
-.. raw:: html
+          <h3>Back-end Integration</h3>
 
-  <p>&nbsp;</p>
+        .. toctree::
+          :maxdepth: 2 
+        
+          api_v2
+          web_hooks
 
-Talkable For Mobile
-===================
+    .. grid-item::
 
-Follow our instructions on how to integrate Talkable into your native mobile app.
+        .. raw:: html
+
+          <h3>For Mobile</h3>
+
+        .. toctree::
+          :maxdepth: 2 
+        
+          ios_sdk
+          android_sdk
 
-+--------------------+--------------------+
-| .. toctree::       | .. toctree::       |
-|   :maxdepth: 2     |   :maxdepth: 2     |
-|                    |                    |
-|   ios_sdk          |   android_sdk      |
-+--------------------+--------------------+
diff --git a/source/integration/custom/integration_components.rst b/source/integration/custom/integration_components.rst
index 80657867b..281b04f44 100644
--- a/source/integration/custom/integration_components.rst
+++ b/source/integration/custom/integration_components.rst
@@ -15,10 +15,11 @@ Talkable is composed of the following components:
    that spans every page. All other integration components are dependent on the Init script.
 
    **Data Capture.** The Initialization Script should pass variables for logged in users:
-    - Email
-    - Phone Number
-    - First Name
-    - Last Name
+    
+   - Email
+   - Phone Number
+   - First Name
+   - Last Name
 
 2. :ref:`Post Purchase Script <integration/custom/integration_components/post_purchase_script>`
 
diff --git a/source/integration/custom/overview.rst b/source/integration/custom/overview.rst
index dba55aaf4..cf0607749 100644
--- a/source/integration/custom/overview.rst
+++ b/source/integration/custom/overview.rst
@@ -35,14 +35,14 @@ a few quick steps by adding the below scripts to your site.
    Surface purchase detail variables as described in more detail in
    :ref:`Integration Components <integration/custom/integration_components>`.
 
-.. note::
+   .. note::
 
-    If a business has both one-time purchases and subscription transactions, or
-    the business has a strictly subscription or SaaS model we recommend integrating
-    the ‘Post Purchase’ through Events. :ref:`Learn more <advanced_features/events>`.
+      If a business has both one-time purchases and subscription transactions, or
+      the business has a strictly subscription or SaaS model we recommend integrating
+      the ‘Post Purchase’ through Events. :ref:`Learn more <advanced_features/events>`.
 
-    Post Purchase step is the only step which changes for subscription business
-    model integration - other steps remain the same.
+      Post Purchase step is the only step which changes for subscription business
+      model integration - other steps remain the same.
 
 3. To host the Invite Standalone campaign, create a new HTML page with standard
    header/footer. Best practice is to create this page on ``www.your-site.com/share``
diff --git a/source/integration/custom/questions.rst b/source/integration/custom/questions.rst
index 7fe8e7be0..6f10065fd 100644
--- a/source/integration/custom/questions.rst
+++ b/source/integration/custom/questions.rst
@@ -24,7 +24,7 @@ F.A.Q.
 
 .. _integration/custom/questions/post_purchase_capture:
 
-**1.) Does the post purchase script need to capture all purchases or
+**1.  Does the post purchase script need to capture all purchases or
 just Talkable purchases?**
 
 The post purchase script needs to capture all purchases. This not only
@@ -37,7 +37,7 @@ along with other sales related metrics.
 
 .. _integration/custom/questions/how_does_referral_tracking_work:
 
-**2.) How does referral tracking work?**
+**2. How does referral tracking work?**
 
 Talkable automatically handles all referral tracking, so there’s nothing
 special you need to do as a developer. Talkable tracks referrals by at
@@ -49,7 +49,7 @@ referral.
 
 .. _integration/custom/questions/what_does_the_talkable_integration_do:
 
-**3.) What does the Talkable integration do?**
+**3. What does the Talkable integration do?**
 
 -  Displays Refer-A-Friend content inside a Talkable generated iframe
    either as an overlay or inline
@@ -69,7 +69,7 @@ referral.
 
 .. _integration/custom/questions/talkable_know_where_to_display_content:
 
-**4.) How does Talkable know where to display content?**
+**4. How does Talkable know where to display content?**
 
 -  "Placements" refer to areas of your website where referral content
    should display. These rules are defined inside of the Placements
@@ -102,7 +102,7 @@ referral.
 
 .. _integration/custom/questions/complete_integration:
 
-**5.) What work do I, as a developer, need to do to complete
+**5. What work do I, as a developer, need to do to complete
 integration?**
 
 -  Surface variables, plug into integration script, and copy into the
@@ -121,7 +121,7 @@ integration?**
 
 .. _integration/custom/questions/rewarding_process_work:
 
-**6.) How does the rewarding process work?**
+**6. How does the rewarding process work?**
 
 Referring Advocate Reward payout is configurable, it can be triggered
 automatically based on any grace period delay, through API call when
@@ -166,6 +166,6 @@ action.
 
 .. _integration/custom/questions/verify_success:
 
-**7.) How do I verify success?**
+**7. How do I verify success?**
 
 Refer to the section titled :ref:`Validating the Integration <integration/custom/validating_integration>`.
diff --git a/source/integration/custom_integration.rst b/source/integration/custom_integration.rst
index cdb868f43..953444a75 100644
--- a/source/integration/custom_integration.rst
+++ b/source/integration/custom_integration.rst
@@ -36,12 +36,28 @@ Standard Integration
 
      custom/overview
 
-Contents:
 
-.. toctree::
+.. raw:: html
+
+   <h2 class="mts">Contents:</h2>
+
+.. grid:: 1 2 2 2
+
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 2 
+      
+         custom/integration_components
+         verify
+    
+   .. grid-item::
 
-   custom/integration_components
-   custom/validating_integration
-   verify
-   custom/cookies
-   custom/questions
+      .. toctree::
+         :maxdepth: 2 
+        
+         custom/validating_integration
+         custom/cookies
+         custom/questions   
+   
+   
diff --git a/source/integration/ecommerce_platforms.rst b/source/integration/ecommerce_platforms.rst
index e9092dd78..7e52bf04a 100644
--- a/source/integration/ecommerce_platforms.rst
+++ b/source/integration/ecommerce_platforms.rst
@@ -7,10 +7,21 @@
 E-commerce Platforms
 ####################
 
-Contents:
+.. grid:: 1 2 2 2
 
-.. toctree::
-    ecommerce_platforms/bigcommerce
-    ecommerce_platforms/demandware
-    ecommerce_platforms/shopify
-    ecommerce_platforms/magento
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 2 
+      
+         ecommerce_platforms/demandware
+         ecommerce_platforms/shopify
+    
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 2 
+        
+         ecommerce_platforms/bigcommerce
+         ecommerce_platforms/magento
+         
\ No newline at end of file
diff --git a/source/integration/ecommerce_platforms/magento/magento1.rst b/source/integration/ecommerce_platforms/magento/magento1.rst
index 9f31e10e5..8e09c6f69 100644
--- a/source/integration/ecommerce_platforms/magento/magento1.rst
+++ b/source/integration/ecommerce_platforms/magento/magento1.rst
@@ -53,8 +53,9 @@ integration. The extension currently supports Magento versions 1.5+
    <h2>Troubleshooting</h2>
 
 In case you cannot find Talkable extension in the sidebar try clearing cache:
-   * In Admin Panel, go to **System** → **Cache Management**.
-   * Click **Flush Magento Cache**.
-   * Then click **Select All**, select action *"Refresh"* and click **Submit**.
+
+* In Admin Panel, go to **System** → **Cache Management**.
+* Click **Flush Magento Cache**.
+* Then click **Select All**, select action *"Refresh"* and click **Submit**.
 
 .. _Magento Talkable extension: https://github.com/talkable/talkable-magento/releases/latest
diff --git a/source/integration/ecommerce_platforms/magento/magento2.rst b/source/integration/ecommerce_platforms/magento/magento2.rst
index 2ea300035..16bbef3d9 100644
--- a/source/integration/ecommerce_platforms/magento/magento2.rst
+++ b/source/integration/ecommerce_platforms/magento/magento2.rst
@@ -2,17 +2,17 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: The Magento 2 Integration Extension is available to download in the Magento Marketplace. The extension supports all versions of Magento 2.0 or higher.
+   :description: The Magento 2 Integration Extension is available to download in the Magento Marketplace. The extension supports all versions of Magento 2.0 or higher.
 
 Magento 2.x Integration
 =======================
 
 .. note::
 
-  To get started, you must have an account created with Talkable, and a Magento Marketplace account.
-  If you do not have a Magento Marketplace account configured, follow
-  `these steps <https://docs.magento.com/user-guide/magento/magento-marketplace.html#marketplace-credentials>`_
-  to connect one to your Magento store.
+   To get started, you must have an account created with Talkable, and a Magento Marketplace account.
+   If you do not have a Magento Marketplace account configured, follow
+   `these steps <https://docs.magento.com/user-guide/magento/magento-marketplace.html#marketplace-credentials>`_
+   to connect one to your Magento store.
 
 The `Magento 2 Integration Extension`_ is available to download in the Magento Marketplace.
 The extension supports all versions of Magento 2.0 or higher.
@@ -24,8 +24,8 @@ Installation
 
 .. note::
 
-  Installation via Composer requires an IT administrator with SSH access to the server where Magento 2 is hosted.
-  To install the Talkable extension, you’ll need to execute four commands.
+   Installation via Composer requires an IT administrator with SSH access to the server where Magento 2 is hosted.
+   To install the Talkable extension, you’ll need to execute four commands.
 
 1. Visit the Magento Marketplace and get the `Talkable extension`_.
 
@@ -36,40 +36,38 @@ Installation
 
 3. Run the following command to access the latest version of the Talkable extension.
     
-.. code-block:: bash
+   .. code-block:: bash
 
-  composer require talkable/magento2-integration
+      composer require talkable/magento2-integration
 
 4. Run the following command to enable the Talkable extension you just downloaded:
 
-.. code-block:: bash
+   .. code-block:: bash
 
-  php bin/magento module:enable Talkable_Integration --clear-static-content
+      php bin/magento module:enable Talkable_Integration --clear-static-content
 
-You should see the following output:
-  
-.. code-block::
+   You should see the following output:
 
-  The following modules have been enabled:
-  - Talkable_Integration
+      The following modules have been enabled:
+      - Talkable_Integration
 
-  To make sure that the enabled modules are properly registered, run 'setup:upgrade'.
-  Cache cleared successfully.
-  Generated classes cleared successfully.
-  Please run the 'setup:di:compile' command to generate classes.
-  Generated static view files cleared successfully.
+      To make sure that the enabled modules are properly registered, run 'setup:upgrade'.
+      Cache cleared successfully.
+      Generated classes cleared successfully.
+      Please run the 'setup:di:compile' command to generate classes.
+      Generated static view files cleared successfully.
 
 5. As displayed in the sample output, you must now enable any additional modules. Run the following command to enable them:
 
-.. code-block:: bash
+   .. code-block:: bash
 
-  php bin/magento setup:upgrade
+      php bin/magento setup:upgrade
 
 6. To ensure that the CSS and JS on your Magento 2 store continues to work properly, you’ll need to run a static content deploy command.
 
-.. code-block:: bash
+   .. code-block:: bash
 
-  php bin/magento setup:static-content:deploy -f
+      php bin/magento setup:static-content:deploy -f
 
 7. Installation via Composer is complete! You can now return to the Magento admin dashboard from your browser.
 
@@ -81,12 +79,12 @@ Accessing Talkable Configuration
 1. To access Talkable extension settings, navigate to **Stores** → **Configuration** in
    your Magento admin panel.
 
-.. image:: /_static/img/magento2/access1.jpg
+   .. image:: /_static/img/magento2/access1.jpg
 
 2. Then select **Talkable** → **Talkable Configuration** from the list of available configurations.
    If you have multiple stores, select the desired Store View you want to change the settings for.
 
-.. image:: /_static/img/magento2/access2.jpg
+   .. image:: /_static/img/magento2/access2.jpg
 
 |page_break|
 
@@ -109,19 +107,19 @@ to your Talkable account.
 
 .. warning::
 
-  Only change this setting if you need to connect your store to a different site in the Talkable dashboard.
-  An incorrect value will prevent your campaigns from showing.
+   Only change this setting if you need to connect your store to a different site in the Talkable dashboard.
+   An incorrect value will prevent your campaigns from showing.
 
-  Changing the Site ID will invalidate the full page cache. Magento will display a warning message with
-  a link to the Cache Management page. Please follow this link and refresh the invalidated cache types.
+   Changing the Site ID will invalidate the full page cache. Magento will display a warning message with
+   a link to the Cache Management page. Please follow this link and refresh the invalidated cache types.
 
-.. image:: /_static/img/magento2/cache.jpg
+   .. image:: /_static/img/magento2/cache.jpg
 
 .. note::
 
-  You need to paste the Site ID from your Talkable Site Dashboard into this field.
+   You need to paste the Site ID from your Talkable Site Dashboard into this field.
 
-.. image:: /_static/img/magento2/configure3.jpg
+   .. image:: /_static/img/magento2/configure3.jpg
 
 |page_break|
 
@@ -147,8 +145,8 @@ Default values correspond to default placements in Talkable.
 
 .. warning::
 
-  Only change these settings if you have configured custom placements for these campaign types
-  in your Talkable dashboard. Incorrect values will prevent your Standalone or Dashboard campaign from showing.
+   Only change these settings if you have configured custom placements for these campaign types
+   in your Talkable dashboard. Incorrect values will prevent your Standalone or Dashboard campaign from showing.
 
 .. image:: /_static/img/magento2/configure6.jpg
 
diff --git a/source/integration/ecommerce_platforms/shopify.rst b/source/integration/ecommerce_platforms/shopify.rst
index e36b8f817..b9d98e0fb 100644
--- a/source/integration/ecommerce_platforms/shopify.rst
+++ b/source/integration/ecommerce_platforms/shopify.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Here’s how you can integrate Talkable Shopify app with your store.
+   :description: Here’s how you can integrate Talkable Shopify app with your store.
 
 Shopify Integration
 ===================
@@ -13,14 +13,15 @@ Automatic integration
 ---------------------
 
 .. note::
+
     If you have previously integrated with Talkable, make sure you remove the manual
     Talkable integration script located in the Additional Content & Scripts section before
     you start the Automatic integration process. See `Manual integration`_ for details.
 
 1. Contact sales@talkable.com to learn about our pricing and set up an account with Talkable
 
-|space_indent| - Provide a valid Shopify store URL. Example: |example_link|. |br|
-|space_indent| - Choose “Shopify” as your platform during registration process
+   - Provide a valid Shopify store URL. Example: `https://123test.myshopify.com`
+   - Choose “Shopify” as your platform during registration process
 
 2. Install the Shopify integration app via the link provided by Talkable team
 3. After the successful installation you will be redirected back to Talkable
@@ -28,7 +29,8 @@ Automatic integration
 5. Create, set up, and launch Campaigns (Invite, Advocate Dashboard, etc.)
 6. Verify your integration using :ref:`Verifying Integration instructions <integration/verify>`
 
-.. note::
+   .. note::
+
     Post Purchase campaign is located at the “Thank you” page after Checkout.
 
     To check how Standalone Campaign looks visit */pages/share* or */pages/invite* links of your store.
@@ -51,8 +53,10 @@ please follow the instructions below.
 4. You will be redirected to your Shopify store, log in and click the install button
 5. After successful installation you will be redirected back to Talkable
 6. Click “Integrate manually“
-7. In your Shopify Admin, add the integration to your layout:
-    1. Create a snippet:
+7.  In your Shopify Admin, add the integration to your layout:
+
+    1.  Create a snippet:
+        
         * Go to **Online Store** → **Themes**
         * Click **Actions** ("..." button) → **Edit code**
         * Go to **Snippets**
@@ -66,19 +70,22 @@ please follow the instructions below.
 
         * Click “Save”
 
-    2. Render the snippet in the layout:
+    2.  Render the snippet in the layout:
+        
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Layout**
         * Open `theme.liquid` file
         * Before closing `</head>` paste the following code:
 
           .. code-block:: liquid
 
-            {% render "talkable-partial" %}
+             {% render "talkable-partial" %}
 
         * Click “Save”
 
-8. In your Shopify Admin, create resources for referral share page:
-    1. Create a share page section:
+8.  In your Shopify Admin, create resources for referral share page:
+    
+    1.  Create a share page section:
+    
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-campaign.liquid`
@@ -86,31 +93,36 @@ please follow the instructions below.
 
           .. code-block:: html
 
-            <div id="talkable-offer"></div>
+             <div id="talkable-offer"></div>
 
         * Optionally, update the schema name to anything meaningful, for example, “Referral campaign“
 
           .. image:: /_static/img/shopify/editor_section.png
-            :alt: Shopify editor - talkable-campaign section
-            :class: is-minimal
+             :alt: Shopify editor - talkable-campaign section
+             :class: is-minimal
 
         * Click “Save”
 
-    2. Create a share page template:
+    2.  Create a share page template:
+        
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `talkable` (`page.talkable.json`)
         * Change the type of the main section to `talkable-campaign`
 
           .. image:: /_static/img/shopify/editor_template.png
-            :alt: Shopify editor - Talkable page section
-            :class: is-minimal
+             :alt: Shopify editor - Talkable page section
+             :class: is-minimal
 
           .. important::
-            - The name of the section should be the same as the one you used in the previous step when naming your section file.
-            - If your main section is disabled, remove the row that does it.
+             The name of the section should be the same as the one you used
+             in the previous step when naming your section file.
 
-    3. Create a page:
+          .. important::
+             If your main section is disabled, remove the row that does it.
+
+    3.  Create a page:
+        
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
         * Click “Add page“
@@ -118,8 +130,10 @@ please follow the instructions below.
         * Select theme template: `talkable`
         * Click “Save”
 
-9. In your Shopify Admin, create resources for referral dashboard page:
-    1. Create a dashboard page section:
+9.  In your Shopify Admin, create resources for referral dashboard page:
+    
+    1.  Create a dashboard page section:
+    
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-dashboard.liquid`
@@ -127,18 +141,19 @@ please follow the instructions below.
 
           .. code-block:: html
 
-            {% if shop.customer_accounts_enabled %}
-              {% if customer %}
-                <div id="talkable-offer"></div>
-              {% else %}
-                {{ 'Log in' | customer_login_link }}
-              {% endif %}
-            {% endif %}
+             {% if shop.customer_accounts_enabled %}
+               {% if customer %}
+                 <div id="talkable-offer"></div>
+               {% else %}
+                 {{ 'Log in' | customer_login_link }}
+               {% endif %}
+             {% endif %}
 
         * Optionally, update the schema name to anything meaningful, for example, “Referral dashboard“
         * Click “Save”
 
-    2. Create a dashboard page template:
+    2.  Create a dashboard page template:
+        
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `dashboard.talkable` (`page.dashboard.talkable.json`)
@@ -146,19 +161,23 @@ please follow the instructions below.
 
           .. code-block:: JSON
 
-            {
-              "sections": {
-                "main": {
-                  "type": "talkable-dashboard"
-                }
-              }
-            }
+             {
+               "sections": {
+                 "main": {
+                   "type": "talkable-dashboard"
+                 }
+               }
+             }
+
+          .. important::
+             The name of the section should be the same as the one you used
+             in the previous step when naming your section file.
 
           .. important::
-            - The name of the section should be the same as the one you used in the previous step when naming your section file.
-            - If your main section is disabled, remove the row that does it.
+             If your main section is disabled, remove the row that does it.
 
-    3. Create a page:
+    3.  Create a page:
+        
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
         * Click “Add page“
@@ -167,13 +186,14 @@ please follow the instructions below.
         * Click “Save” (Customer accounts must be enabled in **Settings** → **Checkout**)
 
 10. In your Shopify Admin, add a post-purchase script:
+    
     * Go to **Settings** → **Checkout**
     * Scroll down to **Order status page**
     * Paste the following code into **Additional scripts** field:
 
-    .. include:: /samples/ecommerce/platform/shopify.rst
+      .. include:: /samples/ecommerce/platform/shopify.rst
 
-    .. include:: /partials/note_sample_code.rst
+      .. include:: /partials/note_sample_code.rst
 
     * Click “Save”.
 
@@ -191,8 +211,10 @@ please follow the instructions below.
 4. You will be redirected to your Shopify store, log in and click the install button
 5. After successful installation you will be redirected back to Talkable
 6. Click “Integrate manually“
-7. In your Shopify Admin, add the integration to your layout:
-    1. Create a snippet:
+7.  In your Shopify Admin, add the integration to your layout:
+    
+    1.  Create a snippet:
+        
         * Go to **Online Store** → **Themes**
         * Click **Actions** ("..." button) → **Edit code**
         * Go to **Snippets**
@@ -206,19 +228,22 @@ please follow the instructions below.
 
         * Click “Save”
 
-    2. Render the snippet in the layout:
+    2.  Render the snippet in the layout:
+        
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Layout**
         * Open `theme.liquid` file
         * Before closing `</head>` paste the following code:
 
           .. code-block:: liquid
 
-            {% render "talkable-partial" %}
+             {% render "talkable-partial" %}
 
         * Click “Save”
 
-8. In your Shopify Admin, create resources for referral share page:
-    1. Create a share page template:
+8.  In your Shopify Admin, create resources for referral share page:
+    
+    1.  Create a share page template:
+        
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Templates**
         * Click “Add a new template“
         * Create a new Liquid template of type `page` called `talkable` (`page.talkable.liquid`)
@@ -226,11 +251,12 @@ please follow the instructions below.
 
           .. code-block:: html
 
-            <div id="talkable-offer"></div>
+             <div id="talkable-offer"></div>
 
         * Click “Save”
 
-    2. Create a page:
+    2.  Create a page:
+        
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
         * Click “Add page“
@@ -238,8 +264,10 @@ please follow the instructions below.
         * Select theme template: `talkable`
         * Click “Save”
 
-9. In your Shopify Admin, create resources for referral dashboard page:
-    1. Create a dashboard page template:
+9.  In your Shopify Admin, create resources for referral dashboard page:
+    
+    1.  Create a dashboard page template:
+    
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Templates**
         * Click “Add a new template“
         * Create a new Liquid template of type `page` called `dashboard.talkable` (`page.dashboard.talkable.liquid`)
@@ -247,17 +275,17 @@ please follow the instructions below.
 
           .. code-block:: html
 
-            {% if shop.customer_accounts_enabled %}
-              {% if customer %}
-                <div id="talkable-offer"></div>
-              {% else %}
-                {{ 'Log in' | customer_login_link }}
-              {% endif %}
-            {% endif %}
+             {% if shop.customer_accounts_enabled %}
+               {% if customer %}
+                 <div id="talkable-offer"></div>
+               {% else %}
+                 {{ 'Log in' | customer_login_link }}
+               {% endif %}
+             {% endif %}
 
         * Click “Save”
 
-    2. Create a page:
+    2.  Create a page:
 
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
@@ -267,27 +295,23 @@ please follow the instructions below.
         * Click “Save” (Customer accounts must be enabled in **Settings** → **Checkout**)
 
 10. In your Shopify Admin, add a post-purchase script:
+    
     * Go to **Settings** → **Checkout**
     * Scroll down to **Order status page**
     * Paste the following code into **Additional scripts** field:
 
-    .. include:: /samples/ecommerce/platform/shopify.rst
+      .. include:: /samples/ecommerce/platform/shopify.rst
 
-    .. include:: /partials/note_sample_code.rst
+      .. include:: /partials/note_sample_code.rst
 
     * Click “Save”.
 
 11. Verify your integration using :ref:`Verifying Integration instructions <integration/verify>`.
 
-.. |example_link| raw:: html
+    .. code:: html
 
-  <span class="a">https://123test.myshopify.com</span>
+      <span class="a">https://123test.myshopify.com</span>
 
-.. container:: hidden
-
-  .. toctree::
-
-    Verifying Integration instructions <../verify>
 
 .. _integration/ecommerce_platforms/shopify/manual_integration_theme_migration:
 
@@ -297,9 +321,11 @@ Manual migrating from a vintage theme to an Online store 2.0 theme
 If you have previously integrated Talkable in your vintage Shopify theme and want to migrate to a newer theme,
 you need to do the following:
 
-1. Share page migration:
+1.  Share page migration:
+
     1. If you have a `templates/page.talkable.liquid` file, store its content elsewhere and delete the file
-    2. Create a share page section:
+    2.  Create a share page section:
+        
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-campaign.liquid`
@@ -307,30 +333,36 @@ you need to do the following:
 
           .. code-block:: html
 
-            <div id="talkable-offer"></div>
+             <div id="talkable-offer"></div>
 
           If there were any customizations in the `templates/page.talkable.liquid`, add them as well
 
         * Optionally, update the schema name to anything meaningful, for example, “Referral campaign“
         * Click “Save”
 
-    3. Create a share page template:
+    3.  Create a share page template:
+        
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `talkable` (`page.talkable.json`)
         * Change the type of the main section to `talkable-campaign`
 
           .. image:: /_static/img/shopify/editor_template.png
-            :alt: Shopify editor - Talkable page section
-            :class: is-minimal
+             :alt: Shopify editor - Talkable page section
+             :class: is-minimal
 
           .. important::
-            - The name of the section should be the same as the one you used in the previous step when naming your section file.
-            - If your main section is disabled, remove the row that does it.
+             The name of the section should be the same as the one you used
+             in the previous step when naming your section file.
 
-2. Dashboard page migration:
+          .. important::
+             If your main section is disabled, remove the row that does it.
+
+2.  Dashboard page migration:
+    
     1. If you have a `templates/page.talkable-dashboard.liquid` file, store its content elsewhere and delete the file
-    2. Create a dashboard page section:
+    2.  Create a dashboard page section:
+        
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-dashboard.liquid`
@@ -338,20 +370,21 @@ you need to do the following:
 
           .. code-block:: html
 
-            {% if shop.customer_accounts_enabled %}
-              {% if customer %}
-                <div id="talkable-offer"></div>
-              {% else %}
-                {{ 'Log in' | customer_login_link }}
-              {% endif %}
-            {% endif %}
+             {% if shop.customer_accounts_enabled %}
+               {% if customer %}
+                 <div id="talkable-offer"></div>
+               {% else %}
+                 {{ 'Log in' | customer_login_link }}
+               {% endif %}
+             {% endif %}
 
           If there were any customizations in the `templates/page.talkable-dashboard.liquid`, add them as well
 
         * Optionally, update the schema name to anything meaningful, for example, “Referral dashboard“
         * Click “Save”
 
-    3. Create a dashboard page template:
+    3.  Create a dashboard page template:
+        
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `dashboard.talkable` (`page.dashboard.talkable.json`)
@@ -359,17 +392,20 @@ you need to do the following:
 
           .. code-block:: JSON
 
-            {
-              "sections": {
-                "main": {
-                  "type": "talkable-dashboard"
-                }
-              }
-            }
+             {
+               "sections": {
+                 "main": {
+                   "type": "talkable-dashboard"
+                 }
+               }
+             }
+
+          .. important::
+             The name of the section should be the same as the one you used
+             in the previous step when naming your section file.
 
           .. important::
-            - The name of the section should be the same as the one you used in the previous step when naming your section file.
-            - If your main section is disabled, remove the row that does it.
+             If your main section is disabled, remove the row that does it.
 
 **Contact us**
 
diff --git a/source/integration/loyalty.rst b/source/integration/loyalty.rst
index d49ac3f04..8a544a43a 100644
--- a/source/integration/loyalty.rst
+++ b/source/integration/loyalty.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: You can integrate Talkable Loyalty to e-commerce sites in a few quick steps.
+   :description: You can integrate Talkable Loyalty to e-commerce sites in a few quick steps.
 
 Loyalty Integration (beta)
 ==========================
@@ -12,7 +12,7 @@ a few quick steps by adding the below scripts to your site.
 
 .. raw:: html
 
-  <h2>Integration</h2>
+   <h2>Integration</h2>
 
 1. Initialize Talkable integration library.
 
@@ -20,6 +20,7 @@ a few quick steps by adding the below scripts to your site.
    to your header or any template spanning every page.
 
 .. note::
+
    Skip this step if you already have Talkable integrated on your site
 
 2. Add Loyalty Dashboard.
@@ -31,7 +32,7 @@ a few quick steps by adding the below scripts to your site.
 
    .. code-block:: html
 
-     <div id="talkable-loyalty"></div>
+      <div id="talkable-loyalty"></div>
 
 3. Add Redeem Widget.
 
@@ -40,12 +41,12 @@ a few quick steps by adding the below scripts to your site.
 
    .. code-block:: html
 
-     <div id="talkable-loyalty"></div>
+      <div id="talkable-loyalty"></div>
 
    It is recommended to add it above the discount field. Examples:
 
    .. figure:: /_static/img/loyalty/loyalty_checkout.png
-     :alt: Sample checkout
+      :alt: Sample checkout
 
 4. Define Loyalty points redemption batches.
 
@@ -58,15 +59,16 @@ a few quick steps by adding the below scripts to your site.
    It is recommended to upload 100,000 single-use coupons into every coupon list.
 
    .. figure:: /_static/img/loyalty/redemption_batches.png
-     :alt: Redemption batches
+      :alt: Redemption batches
 
 .. note::
+
    All design and loyalty campaign setup is done inside the Talkable platform,
    then via iframe loyalty campaign content is injected into the site.
 
 .. raw:: html
 
-  <h2>Requirements</h2>
+   <h2>Requirements</h2>
 
 1. User accounts. The website must support user accounts since the loyalty program is only available to logged in users.
 
@@ -80,7 +82,7 @@ a few quick steps by adding the below scripts to your site.
 
  .. toctree::
 
-   loyalty/integration_components
-   loyalty/custom_app
-   loyalty/auto_enrollment
-   loyalty/shopify_integration
+    loyalty/integration_components
+    loyalty/custom_app
+    loyalty/auto_enrollment
+    loyalty/shopify_integration
diff --git a/source/integration/loyalty/custom_app.rst b/source/integration/loyalty/custom_app.rst
index 09d9ef44e..226967dba 100644
--- a/source/integration/loyalty/custom_app.rst
+++ b/source/integration/loyalty/custom_app.rst
@@ -37,10 +37,11 @@ To determine which loyalty action triggered the Custom App, use `{{ action.ident
 * when loyalty member exchanges points for a coupon, the Action Identifier is *"redeem"*;
 * when loyalty member gains or loses points due to a manual points adjustment, the Action Identifier is *"manual_adjustment"*;
 * when loyalty member earns points according to loyalty action configurations, the Action Identifier varies based on the action configuration type:
-   * *"optin"* for "Loyalty join";
-   * *"event"* for "Purchase points" and "Event points";
-   * *"referral"* for "Refer a friend";
-   * for a custom type, the Identifier is taken straight from the action configuration "Identifier" field.
+
+  * *"optin"* for "Loyalty join";
+  * *"event"* for "Purchase points" and "Event points";
+  * *"referral"* for "Refer a friend";
+  * for a custom type, the Identifier is taken straight from the action configuration "Identifier" field.
 
 `{{ action.rule }}` contains details about the action configuration that is responsible for a particular points collection.
 
diff --git a/source/integration/loyalty/integration_components.rst b/source/integration/loyalty/integration_components.rst
index 1bc811c1a..6d9f58560 100644
--- a/source/integration/loyalty/integration_components.rst
+++ b/source/integration/loyalty/integration_components.rst
@@ -15,12 +15,13 @@ Talkable Loyalty is composed of the following components:
    that spans every page. All other integration components are dependent on the Init script.
 
    **Data Capture.** The Initialization Script should pass variables for logged in users:
-    - Email
-    - Phone Number
-    - First Name
-    - Last Name
-    - Custom Properties
-    - Customer ID
+    
+   - Email
+   - Phone Number
+   - First Name
+   - Last Name
+   - Custom Properties
+   - Customer ID
 
 2. :ref:`Talkable Container DIV`
 
diff --git a/source/integration/loyalty/shopify_integration.rst b/source/integration/loyalty/shopify_integration.rst
index 4887026b0..68a5a3998 100644
--- a/source/integration/loyalty/shopify_integration.rst
+++ b/source/integration/loyalty/shopify_integration.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Learn how to manually set up loyalty Shopify integration.
+   :description: Learn how to manually set up loyalty Shopify integration.
 
 Shopify Integration
 ===================
@@ -27,8 +27,10 @@ Manual integration
 3. After successful installation you will be redirected back to Talkable
 4. Click “Integrate manually“
 5. Set up Referral Integration :ref:`manually <integration/ecommerce_platforms/shopify/manual_integration>`
-6. In your Shopify Admin create resources for loyalty dashboard page:
-    1. Create a loyalty dashboard page section:
+6.  In your Shopify Admin create resources for loyalty dashboard page:
+
+    1.  Create a loyalty dashboard page section:
+    
         * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
         * Click “Add a new section“
         * Create a new Liquid section called `talkable-loyalty-dashboard.liquid`
@@ -36,14 +38,15 @@ Manual integration
 
           .. code-block:: html
 
-            {% if shop.customer_accounts_enabled %}
-              <div id="talkable-loyalty"></div>
-            {% endif %}
+             {% if shop.customer_accounts_enabled %}
+               <div id="talkable-loyalty"></div>
+             {% endif %}
 
         * Optionally, update the schema name to anything meaningful, for example, “Loyalty dashboard“
         * Click “Save”
 
-    2. Create a loyalty dashboard page template:
+    2.  Create a loyalty dashboard page template:
+        
         * Go to **Templates**
         * Click “Add a new template“
         * Create a new JSON template of type `page` called `loyalty_dashboard.talkable` (`page.loyalty_dashboard.talkable.json`)
@@ -51,22 +54,23 @@ Manual integration
 
           .. code-block:: JSON
 
-            {
-              "sections": {
-                "main": {
-                  "type": "talkable-loyalty-dashboard"
-                }
-              }
-            }
+             {
+               "sections": {
+                 "main": {
+                   "type": "talkable-loyalty-dashboard"
+                 }
+               }
+             }
 
           .. important::
-            The name of the section should be the same as the one you used
-            in the previous step when naming your section file.
+             The name of the section should be the same as the one you used
+             in the previous step when naming your section file.
 
           .. important::
-            If your main section is disabled, remove the row that does it.
+             If your main section is disabled, remove the row that does it.
 
-    3. Create a page:
+    3.  Create a page:
+        
         * Exit theme editor if it was opened
         * Go to **Online Store** → **Pages**
         * Click “Add page“
@@ -76,7 +80,7 @@ Manual integration
 
 .. raw:: html
 
-  <h2>Requirements</h2>
+   <h2>Requirements</h2>
 
 User accounts. The website must support user accounts since the loyalty program is only available to logged in users.
 
@@ -90,7 +94,8 @@ you need to do the following:
 
 2. If you have a `templates/page.talkable-loyalty-dashboard.liquid` file, store its content elsewhere and delete the file
 
-3. Create a loyalty dashboard page section:
+3.  Create a loyalty dashboard page section:
+    
     * In the theme code editor (**Online Store** → **Themes** → **Edit code**), go to **Sections**
     * Click “Add a new section“
     * Create a new Liquid section called `talkable-loyalty-dashboard.liquid`
@@ -98,16 +103,17 @@ you need to do the following:
 
       .. code-block:: html
 
-        {% if shop.customer_accounts_enabled %}
-          <div id="talkable-loyalty"></div>
-        {% endif %}
+         {% if shop.customer_accounts_enabled %}
+           <div id="talkable-loyalty"></div>
+         {% endif %}
 
       If there were any customizations in the `templates/page.talkable-loyalty-dashboard.liquid`, add them as well
 
     * Optionally, update the schema name to anything meaningful, for example, “Loyalty dashboard“
     * Click “Save”
 
-4. Create a loyalty dashboard page template:
+4.  Create a loyalty dashboard page template:
+    
     * Go to **Templates**
     * Click “Add a new template“
     * Create a new JSON template of type `page` called `loyalty_dashboard.talkable` (`page.loyalty_dashboard.talkable.json`)
@@ -115,14 +121,17 @@ you need to do the following:
 
       .. code-block:: JSON
 
-        {
-          "sections": {
-            "main": {
-              "type": "talkable-loyalty-dashboard"
-            }
-          }
-        }
+         {
+           "sections": {
+             "main": {
+               "type": "talkable-loyalty-dashboard"
+             }
+           }
+         }
+
+      .. important::
+         The name of the section should be the same as the one you used
+         in the previous step when naming your section file.
 
       .. important::
-        - The name of the section should be the same as the one you used in the previous step when naming your section file.
-        - If your main section is disabled, remove the row that does it.
+         If your main section is disabled, remove the row that does it.
diff --git a/source/ios_sdk.rst b/source/ios_sdk.rst
index 2b2044681..aa6736d7e 100644
--- a/source/ios_sdk.rst
+++ b/source/ios_sdk.rst
@@ -20,14 +20,31 @@ Talkable has an iOS framework enabling you to use Talkable in iOS Apps. Once int
 
 - Track sales via the App and reward Advocate if a sale was driven thourgh someone’s claim link
 
-Contents:
+.. raw:: html
 
-.. toctree::
+   <h2 class="mts">Contents:</h2>
 
-   ios_sdk/getting_started
-   ios_sdk/integration
-   ios_sdk/social_sharing
-   ios_sdk/api_integration
-   ios_sdk/advanced
-   ios_sdk/custom_deep_linking
-   ios_sdk/example
+.. grid:: 1 2 2 2
+
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 2 
+      
+         ios_sdk/getting_started
+         ios_sdk/integration
+         ios_sdk/social_sharing
+         ios_sdk/api_integration
+    
+   .. grid-item::
+
+      .. toctree::
+         :maxdepth: 2 
+        
+         ios_sdk/advanced
+         ios_sdk/custom_deep_linking
+         ios_sdk/example
+
+
+   
+   
diff --git a/source/ios_sdk/advanced.rst b/source/ios_sdk/advanced.rst
index b22eeeb02..2a6650aa4 100644
--- a/source/ios_sdk/advanced.rst
+++ b/source/ios_sdk/advanced.rst
@@ -72,13 +72,13 @@ Implement TalkableDelegate
 
    .. code-block:: objc
 
-     - (void)showFacebookShareDialogWithParams:(NSDictionary*)params delegate:(id)delegate;
-     - (void)showFacebookShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
-     - (void)showTwitterShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
+      - (void)showFacebookShareDialogWithParams:(NSDictionary*)params delegate:(id)delegate;
+      - (void)showFacebookShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
+      - (void)showTwitterShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
 
    .. note::
 
-    See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
+      See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
 
 .. _ios_sdk/advanced/notifications:
 
diff --git a/source/ios_sdk/api_integration.rst b/source/ios_sdk/api_integration.rst
index b384d5cb7..2ea0fb265 100644
--- a/source/ios_sdk/api_integration.rst
+++ b/source/ios_sdk/api_integration.rst
@@ -78,28 +78,28 @@ via |api_v2_share_via_social_channel|.
 
 .. code-block:: objc
 
-  MyFBSDKDelegateClass* delegate = [self myFBSDKDelegate];
-  delegate.shortUrlCode = shortUrlCode;
-  FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init];
-  content.contentURL = [NSURL URLWithString:[params objectForKey:[claimLinks objectForKey:TKBLShareChannelFacebook]]];
-  [FBSDKShareDialog showFromViewController:self
-                               withContent:content
-                                  delegate:delegate];
+   MyFBSDKDelegateClass* delegate = [self myFBSDKDelegate];
+   delegate.shortUrlCode = shortUrlCode;
+   FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init];
+   content.contentURL = [NSURL URLWithString:[params objectForKey:[claimLinks objectForKey:TKBLShareChannelFacebook]]];
+   [FBSDKShareDialog showFromViewController:self
+                                withContent:content
+                                   delegate:delegate];
 
-  // ...
+   // ...
 
-  @implementation MyFBSDKDelegateClass
+   @implementation MyFBSDKDelegateClass
 
-  @synthesize shortUrlCode;
+   @synthesize shortUrlCode;
 
-  - (void)sharer:(id)sharer didCompleteWithResults:(NSDictionary<NSString *, id> *)results {
-   if (_shortUrlCode != nil)
-      [[Talkable manager] createSocialShare:_shortUrlCode
-                                    channel:TKBLShareChannelFacebook
-                                withHandler:^(NSDictionary* response, NSError* error) {...}];
-  }
+   - (void)sharer:(id)sharer didCompleteWithResults:(NSDictionary<NSString *, id> *)results {
+    if (_shortUrlCode != nil)
+       [[Talkable manager] createSocialShare:_shortUrlCode
+                                     channel:TKBLShareChannelFacebook
+                                 withHandler:^(NSDictionary* response, NSError* error) {...}];
+   }
 
-  @end
+   @end
 
 .. raw:: html
 
@@ -107,15 +107,15 @@ via |api_v2_share_via_social_channel|.
 
 .. code-block:: objc
 
-  TWTRComposer *composer = [[TWTRComposer alloc] init];
-  [composer setText:[params objectForKey:TKBLShareMessage]];
-  [composer showFromViewController:self completion:^(TWTRComposerResult result) {
-    if (result == TWTRComposerResultDone) {
-      [[Talkable manager] createSocialShare:shortUrlCode
-                                    channel:TKBLShareChannelTwitter
-                                withHandler:^(NSDictionary* response, NSError* error) {...}];
-    }
-  }];
+   TWTRComposer *composer = [[TWTRComposer alloc] init];
+   [composer setText:[params objectForKey:TKBLShareMessage]];
+   [composer showFromViewController:self completion:^(TWTRComposerResult result) {
+     if (result == TWTRComposerResultDone) {
+       [[Talkable manager] createSocialShare:shortUrlCode
+                                     channel:TKBLShareChannelTwitter
+                                 withHandler:^(NSDictionary* response, NSError* error) {...}];
+     }
+   }];
 
 .. note::
 
@@ -124,27 +124,26 @@ via |api_v2_share_via_social_channel|.
 Legacy social sharing
 ~~~~~~~~~~~~~~~~~~~~~
 
-3. The legacy ``socialShare:`` method was used prior to v1.4.9 and is provided for backwards compatibility.
-   It will attempt to display a sharing dialog directly using the deprecated Social.framework.
-   Only the Facebook sharing channel is currently supported.
-
-   .. code-block:: objc
+The legacy ``socialShare:`` method was used prior to v1.4.9 and is provided for backwards compatibility.
+It will attempt to display a sharing dialog directly using the deprecated Social.framework.
+Only the Facebook sharing channel is currently supported.
 
-     SLComposeViewController* sheet = [[Talkable manager] socialShare:@{
-       TKBLShareChannel:TKBLShareChannelFacebook,
-       TKBLOfferClaimUrlKey:[claimLinks objectForKey:TKBLShareChannelFacebook],
-       TKBLShareMessage:@"Personalized message",
-       TKBLOfferShortUrlCodeKey:shortUrlCode
-     }];
+.. code-block:: objc
 
-     [self presentViewController:sheet animated:YES completion:^{}];
+  SLComposeViewController* sheet = [[Talkable manager] socialShare:@{
+    TKBLShareChannel:TKBLShareChannelFacebook,
+    TKBLOfferClaimUrlKey:[claimLinks objectForKey:TKBLShareChannelFacebook],
+    TKBLShareMessage:@"Personalized message",
+    TKBLOfferShortUrlCodeKey:shortUrlCode
+  }];
 
-   .. warning::
+  [self presentViewController:sheet animated:YES completion:^{}];
 
-     Starting with v1.4.9, this method is deprecated and offers only limited Facebook sharing support.
-     Native sharing or custom implementation based on Facebook/Twitter SDK should be used instead.
-     See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
+.. warning::
 
+  Starting with v1.4.9, this method is deprecated and offers only limited Facebook sharing support.
+  Native sharing or custom implementation based on Facebook/Twitter SDK should be used instead.
+  See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
 
 Email Share
 ~~~~~~~~~~~
diff --git a/source/ios_sdk/integration/post_purchase.rst b/source/ios_sdk/integration/post_purchase.rst
index 2d4c15d5e..0e2926c14 100644
--- a/source/ios_sdk/integration/post_purchase.rst
+++ b/source/ios_sdk/integration/post_purchase.rst
@@ -12,27 +12,27 @@ Here is an example of a Purchase capturing, this action should be triggered on t
 
 .. code-block:: objc
 
-  #import <TalkableSDK/Talkable.h>
-  // ...
-  NSDictionary* params = @{
-    TKBLPurchaseKey: @{
-      TKBLPurchaseOrderNumberKey: @"100130", // REQUIRED - Order number
-      TKBLPurchaseEmailKey: @"customer@example.com", // REQUIRED - Customer Email
-      TKBLPurchaseSubtotalKey: [NSNumber numberWithDouble:22.33], // REQUIRED - Purchase Subtotal
-      TKBLPurchaseCouponCodeKey: @"TEST25", // REQUIRED - Coupon code used at checkout, pass multiple as an array: @[@"SAVE20", @"FREE-SHIPPING"]. Pass @"" if there is no coupon code.
-      TKBLPurchaseOrderItemsKey:@[
-        @{
-          TKBLPurchaseOrderItemProductIDKey: @"sku3", // Item Product ID
-          TKBLPurchaseOrderItemPriceKey: [NSNumber numberWithDouble:4.99], // Item Unit Price
-          TKBLPurchaseOrderItemQuantityKey: [NSNumber numberWithUnsignedInt:5], // Item Quantity
-          TKBLPurchaseOrderItemTitleKey: @"Amazing Product 3", // Name of the product
-          TKBLPurchaseOrderItemUrlKey: @"http://www.store.com/product2", // URL of the product page
-          TKBLPurchaseOrderItemImageUrlKey: @"http://www.store.com/product2/image.jpg" // URL of the product image
-        }
-      ]
-    }
-  };
-  [[Talkable manager] registerOrigin:TKBLPurchase params:params];
+   #import <TalkableSDK/Talkable.h>
+   // ...
+   NSDictionary* params = @{
+     TKBLPurchaseKey: @{
+       TKBLPurchaseOrderNumberKey: @"100130", // REQUIRED - Order number
+       TKBLPurchaseEmailKey: @"customer@example.com", // REQUIRED - Customer Email
+       TKBLPurchaseSubtotalKey: [NSNumber numberWithDouble:22.33], // REQUIRED - Purchase Subtotal
+       TKBLPurchaseCouponCodeKey: @"TEST25", // REQUIRED - Coupon code used at checkout, pass multiple as an array: @[@"SAVE20", @"FREE-SHIPPING"]. Pass @"" if there is no coupon code.
+       TKBLPurchaseOrderItemsKey:@[
+         @{
+           TKBLPurchaseOrderItemProductIDKey: @"sku3", // Item Product ID
+           TKBLPurchaseOrderItemPriceKey: [NSNumber numberWithDouble:4.99], // Item Unit Price
+           TKBLPurchaseOrderItemQuantityKey: [NSNumber numberWithUnsignedInt:5], // Item Quantity
+           TKBLPurchaseOrderItemTitleKey: @"Amazing Product 3", // Name of the product
+           TKBLPurchaseOrderItemUrlKey: @"http://www.store.com/product2", // URL of the product page
+           TKBLPurchaseOrderItemImageUrlKey: @"http://www.store.com/product2/image.jpg" // URL of the product image
+         }
+       ]
+     }
+   };
+   [[Talkable manager] registerOrigin:TKBLPurchase params:params];
 
 .. note::
 
diff --git a/source/partials/campaign_placements_description.rst b/source/partials/campaign_placements_description.rst
index f4a790c0f..9895fb653 100644
--- a/source/partials/campaign_placements_description.rst
+++ b/source/partials/campaign_placements_description.rst
@@ -39,9 +39,10 @@ A Placement can have a set of criteria defined based on :ref:`custom properties
 If all of the criteria are met, the placement will show a campaign.
 
 The criteria can be defined using one of the following operators:
-  - `eq`
-  - `not_eq`
-  - `regex` (performs a case-insensitive match)
+
+- `eq`
+- `not_eq`
+- `regex` (performs a case-insensitive match)
 
 .. note::
   Custom Property Criteria require integration version 5.1.4 or higher to work.
diff --git a/source/web_hooks/check_unsubscribe.rst b/source/web_hooks/check_unsubscribe.rst
index 45c355c56..9e90e2ea7 100644
--- a/source/web_hooks/check_unsubscribe.rst
+++ b/source/web_hooks/check_unsubscribe.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Check Unsubscribe Webhook ensures that emails are not sent to unsubscribed users.
+   :description: Check Unsubscribe Webhook ensures that emails are not sent to unsubscribed users.
 
 Check Unsubscribe Webhook
 =========================
@@ -14,32 +14,26 @@ from Talkable referral related emails at any time from those emails directly.
 
 .. raw:: html
 
-  <h2>When does Talkable call the Check Unsubscribe Webhook?</h2>
+   <h2>When does Talkable call the Check Unsubscribe Webhook?</h2>
 
 Talkable Check Unsubscribe Webhook is triggered on every attempt to send an
 otherwise valid customer email, aimed at checking if the email is also valid on
 merchant side.
 
 .. important::
-  If this Check Unsubscribe Webhook is used, the response JSON returned by
-  merchant must contain the following fields:
-
-  .. code-block:: javascript
-
-    { "result": { "unsubscribed": true } }
-
-  The 'unsubscribed' field should have a boolean value,
-  representing unsubscribed status according to the merchant info.
+   
+   The 'unsubscribed' field should have a boolean value,
+   representing unsubscribed status according to the merchant info.
 
 .. raw:: html
 
-  <h2>Payload parameters provided</h2>
+   <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Check Unsubscribe Webhook is available here: `Check Unsubscribe Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Check%20Unsubscribe/post_your_api_check_unsubscribe_web_hook_path>`_.
 
 .. raw:: html
 
-  <h3>View categories</h3>
+   <h3>View categories</h3>
 
 View category can be one of the following:
 
diff --git a/source/web_hooks/claim_signup.rst b/source/web_hooks/claim_signup.rst
index f3ab6cc63..55ad8c28d 100644
--- a/source/web_hooks/claim_signup.rst
+++ b/source/web_hooks/claim_signup.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Friend Email Gating Webhook notifies your endpoint that Friend email gating form was submitted.
+   :description: Friend Email Gating Webhook notifies your endpoint that Friend email gating form was submitted.
 
 Friend Email Gating Webhook
 ===========================
@@ -20,7 +20,7 @@ Use cases for the Friend Email Gating Webhook include:
 
 .. raw:: html
 
-  <h2>When does Talkable call the Friend Email Gating Webhook?</h2>
+   <h2>When does Talkable call the Friend Email Gating Webhook?</h2>
 
 Talkable Friend Email Gating Webhook is triggered any time an Friend Email
 Gating form is submitted. This is the form a Friend completes after receiving
@@ -29,11 +29,11 @@ a share from an Advocate, and before receiving their discount code.
 Friend Email Gating form example:
 
 .. image:: /_static/img/friend_email_gating_form.png
-  :alt: Friend Email Gating Form
-  :class: is-minimal
+   :alt: Friend Email Gating Form
+   :class: is-minimal
 
 .. raw:: html
 
-  <h2>Payload parameters provided</h2>
+   <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Friend Email Gating Webhook is available here: `Friend Email Gating Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Friend%20Email%20Gating/post_your_api_claim_signup_web_hook_path>`_.
diff --git a/source/web_hooks/create_coupon.rst b/source/web_hooks/create_coupon.rst
index 1250cf10c..243e6e00e 100644
--- a/source/web_hooks/create_coupon.rst
+++ b/source/web_hooks/create_coupon.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Create Coupon Webhook enables automatic coupon creation. That means you are no longer need to upload coupon lists into the Talkable platform manually.
+   :description: Create Coupon Webhook enables automatic coupon creation. That means you are no longer need to upload coupon lists into the Talkable platform manually.
 
 Create Coupon Webhook
 =====================
@@ -19,7 +19,7 @@ on their platform.
 
 .. raw:: html
 
-  <h2>When does Talkable call the Create Coupon Webhook?</h2>
+   <h2>When does Talkable call the Create Coupon Webhook?</h2>
 
 Create Coupon Webhook is called when the quantity of available coupons drops
 below a Talkable threshold.
@@ -39,7 +39,7 @@ a successful response.
 
 .. raw:: html
 
-  <h2>Set Up</h2>
+   <h2>Set Up</h2>
 
 The Create Coupon Webhook will add coupons to a specific coupon list on Talkable’s
 backend. These coupon lists must be set up in the Talkable campaign editor before
@@ -51,9 +51,9 @@ coupon list for a campaign:
 2. Proceed to **Rules** then scroll down to **Incentives** section where
    incentives for both Advocate and Friend can be configured
 
-.. image:: /_static/img/advocate_referral_incentive.png
-  :alt: Edit Referral Incentives
-  :class: is-minimal
+   .. image:: /_static/img/advocate_referral_incentive.png
+      :alt: Edit Referral Incentives
+      :class: is-minimal
 
 3. Inside the Referral Incentive Editor choose the **Coupon code type: Single-use**
    then select an existing Coupon list or create a new coupon list by clicking
@@ -67,10 +67,10 @@ coupon list for a campaign:
 
 .. note::
 
-  Coupons created by the **Create Coupon Webhook** will be added to the coupon
-  list associated with the referral campaign. Multiple referral campaigns can
-  use the same or unique coupon lists. **Advocate** and **Friend** referral
-  incentives can also use the same or unique coupon lists.
+   Coupons created by the **Create Coupon Webhook** will be added to the coupon
+   list associated with the referral campaign. Multiple referral campaigns can
+   use the same or unique coupon lists. **Advocate** and **Friend** referral
+   incentives can also use the same or unique coupon lists.
 
 Once a single-use coupon code list is associated with a campaign, then the
 Create Coupon Webhook can now be set up.
@@ -78,6 +78,6 @@ Create Coupon Webhook can now be set up.
 
 .. raw:: html
 
-  <h2>Payload parameters provided by Create Coupon Webhook</h2>
+   <h2>Payload parameters provided by Create Coupon Webhook</h2>
 
 The sample payload with parameters for Create Coupon Webhook is available here: `Create Coupon Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Create%20Coupon/post_your_api_create_coupon_web_hook_path>`_.
diff --git a/source/web_hooks/event.rst b/source/web_hooks/event.rst
index 526d2d2fa..77f3bf667 100644
--- a/source/web_hooks/event.rst
+++ b/source/web_hooks/event.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Event Webhook lets you know when a purchase was made.
+   :description: Event Webhook lets you know when a purchase was made.
 
 Event Webhook
 =============
@@ -19,7 +19,7 @@ Use cases for the Event Webhook include:
 
 .. raw:: html
 
-  <h2>When does Talkable call the Event Webhook?</h2>
+   <h2>When does Talkable call the Event Webhook?</h2>
 
 Talkable calls the Event Webhook any time an Event or a Purchase
 is registered either via :ref:`the front-end Talkable integration <advanced_features/events>`
@@ -27,6 +27,6 @@ or using the :ref:`Talkable backend API <api_v2/origins>`.
 
 .. raw:: html
 
-  <h2>Payload parameters provided</h2>
+   <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Event Webhook is available here: `Event Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Event/post_your_api_event_web_hook_path>`_.
diff --git a/source/web_hooks/offer_signup.rst b/source/web_hooks/offer_signup.rst
index 80da5a174..011bb396c 100644
--- a/source/web_hooks/offer_signup.rst
+++ b/source/web_hooks/offer_signup.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Advocate Signup Webhook notifies your endpoint of an Advocate signup forms submission.
+   :description: Advocate Signup Webhook notifies your endpoint of an Advocate signup forms submission.
 
 Advocate Signup Webhook
 =======================
@@ -19,7 +19,7 @@ Use cases for the Advocate Signup Webhook include:
 
 .. raw:: html
 
-  <h2>When does Talkable call the Advocate Signup Webhook?</h2>
+   <h2>When does Talkable call the Advocate Signup Webhook?</h2>
 
 Talkable Signup Webhook is triggered any time an Advocate Signup Form is
 submitted. The Advocate Signup Form is the standard Name & Email (with optional
@@ -29,11 +29,11 @@ and sharing an offer with Friends.
 Advocate Signup Form example:
 
 .. image:: /_static/img/advocate_signup_form_webhook.png
-  :alt: Advocate Signup Form,
-  :class: is-minimal
+   :alt: Advocate Signup Form,
+   :class: is-minimal
 
 .. raw:: html
 
-  <h2>Payload parameters provided for Advocate Signup Webhook</h2>
+   <h2>Payload parameters provided for Advocate Signup Webhook</h2>
 
 The sample payload with parameters for Advocate Signup Webhook is available here: `Advocate Signup Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Advocate%20Signup/post_your_api_advocate_signup_web_hook_path>`_.
diff --git a/source/web_hooks/post_share.rst b/source/web_hooks/post_share.rst
index 1b1afea7e..8b7b49ea4 100644
--- a/source/web_hooks/post_share.rst
+++ b/source/web_hooks/post_share.rst
@@ -2,38 +2,40 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Post Share Webhook provides notification of share events performed within a referral campaign workflow.
+   :description: Post Share Webhook provides notification of share events performed within a referral campaign workflow.
 
 Post Share Webhook
 ==================
 
 Talkable Post Share Webhook provides notification of a share event performed within a referral campaign workflow. Use cases for the Post Share Webhook include:
-  - Sending automated 'Thank You' email to an Advocate for performing a share
-  - Any event that should be triggered when a user shares
-  - Data for Business Intelligence and analytics systems
+
+- Sending automated 'Thank You' email to an Advocate for performing a share
+- Any event that should be triggered when a user shares
+- Data for Business Intelligence and analytics systems
 
 .. raw:: html
 
-  <h2>When does Talkable call the Post Share Webhook?</h2>
+   <h2>When does Talkable call the Post Share Webhook?</h2>
 
 Talkable Post Share Webhook is triggered any time an |advocate| (referrer) shares offer details with a |friend| (referee) via the corresponding form provided by campaign workflow. Which includes any time:
-  - An advocate shares with a Friend via Email or any other channel from inside a referral campaign workflow
-  - An Advocate copies a share link from a referral campaign workflow share screen
+  
+- An advocate shares with a Friend via Email or any other channel from inside a referral campaign workflow
+- An Advocate copies a share link from a referral campaign workflow share screen
 
-Note: the Post Share Webhook triggers every time a share occurs. For example,
-if an Advocate shares with a Friend via email (or any channel), then shares with
-a second Friend via email (or any channel), the Post Share Webhook will be
-triggered twice.
+.. note:: 
+   
+   The Post Share Webhook triggers every time a share occurs. For example, if an Advocate shares with a Friend via email (or any channel), then shares with a second Friend via email (or any channel), the Post Share Webhook will be triggered twice.
 
 .. raw:: html
 
-  <h2>Payload parameters provided for Post Share Webhook</h2>
+   <h2>Payload parameters provided for Post Share Webhook</h2>
 
 The sample payload with parameters for Post Share Webhook is available here: `Post Share Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Post%20Share/post_your_api_post_share_web_hook_path>`_.
 
 .. note::
 
-  ``origin.email`` contains the email saved at the moment when the campaign is
-  first shown to the Advocate. It could be ``null``. For the most up-to-date
-  information about the Advocate, use ``sharer_info`` property which is updated
-  with the email address the Advocate has entered on the Advocate Signup/Share Page.
+   ``origin.email`` contains the email saved at the moment when the campaign is
+   first shown to the Advocate. It could be ``null``. For the most up-to-date
+   information about the Advocate, use ``sharer_info`` property which is updated
+   with the email address the Advocate has entered on the Advocate Signup/Share Page.
+
diff --git a/source/web_hooks/referral.rst b/source/web_hooks/referral.rst
index bfc191413..ccc44caee 100644
--- a/source/web_hooks/referral.rst
+++ b/source/web_hooks/referral.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Referral Webhook notifies your endpoint that your brand Advocate’s referral status has become “Approved”.
+   :description: Referral Webhook notifies your endpoint that your brand Advocate’s referral status has become “Approved”.
 
 Referral Webhook
 ================
@@ -25,7 +25,7 @@ Use cases for the Referral Webhook include:
 
 .. note::
 
-  “Approved” referral status does not guarantee that Advocate will receive a reward.
+   “Approved” referral status does not guarantee that Advocate will receive a reward.
 
 Things that can prevent Advocate or Friend from being rewarded:
 
@@ -37,25 +37,25 @@ Things that can prevent Advocate or Friend from being rewarded:
 
 .. important::
 
-  Referral Webhook keeps retrying until it gets 2xx HTTP status in response.
-  Only after that rewards associated with the referral can be paid.
+   Referral Webhook keeps retrying until it gets 2xx HTTP status in response.
+   Only after that rewards associated with the referral can be paid.
 
 .. raw:: html
 
-  <h2>When does Talkable call the Referral Webhook?</h2>
+   <h2>When does Talkable call the Referral Webhook?</h2>
 
 Talkable Referral Webhook is triggered any time an Advocate referral status has become
 “Approved” specifically for a Friend purchase or event.
 
 .. note::
 
-  Referral Webhook triggers only for Advocate rewards specifically from a Friend
-  Purchase or Friend Event (such as signup event or subscription purchase event).
-  To receive notification of both Advocate and Friend rewards use the Rewards Webhook.
+   Referral Webhook triggers only for Advocate rewards specifically from a Friend
+   Purchase or Friend Event (such as signup event or subscription purchase event).
+   To receive notification of both Advocate and Friend rewards use the Rewards Webhook.
 
 .. raw:: html
 
-  <h2>Payload parameters provided for Referral Webhook</h2>
+   <h2>Payload parameters provided for Referral Webhook</h2>
 
 The sample payload with parameters for Referral Webhook is available here: `Referral Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Referral/post_your_api_referral_web_hook_path>`_.
 
diff --git a/source/web_hooks/reward.rst b/source/web_hooks/reward.rst
index 04ef913bc..87d38da8b 100644
--- a/source/web_hooks/reward.rst
+++ b/source/web_hooks/reward.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Reward Webhook notifies your endpoint that a reward is ready to be given, or it has been already given.
+   :description: Reward Webhook notifies your endpoint that a reward is ready to be given, or it has been already given.
 
 Reward Webhook
 ==============
@@ -21,7 +21,7 @@ Use cases for the Reward Webhook include:
 
 .. raw:: html
 
-  <h2>When does Talkable call the Reward Webhook?</h2>
+   <h2>When does Talkable call the Reward Webhook?</h2>
 
 Talkable calls the Reward Webhook any time a reward is ready to be, or has been
 given to either an Advocate or a Friend according to the logic set-up in a
@@ -35,20 +35,20 @@ Possible events which will trigger the Reward Webhook are:
 
   .. note::
 
-    If campaign is setup without email gating form, Reward Webhook with
-    Reason = click will trigger when Friend clicks through to site.
+     If campaign is setup without email gating form, Reward Webhook with
+     Reason = click will trigger when Friend clicks through to site.
 
 * Friend makes eligible purchase (Reason = **referrer**)
 * Friend makes eligible purchase (Reason = **referred**)
 
   .. note::
 
-    Reason = referrer indicates a reward should be given to an Advocate.
-    Reason = referred indicates a reward should be given to a Friend.
+     Reason = referrer indicates a reward should be given to an Advocate.
+     Reason = referred indicates a reward should be given to a Friend.
 
 .. raw:: html
 
-  <h2>Set-Up</h2>
+   <h2>Set-Up</h2>
 
 Because the Reward Webhook will trigger at various events depending on the
 Incentive configuration for each referral campaign, to trigger the Reward
@@ -60,9 +60,9 @@ To configure incentives:
 2. Proceed to **Rules** then scroll down to **Incentives** section where
    incentives for both Advocates and Friends can be set-up
 
-.. image:: /_static/img/advocate_referral_incentive.png
-  :alt: Edit Referral Incentives,
-  :class: is-minimal
+   .. image:: /_static/img/advocate_referral_incentive.png
+      :alt: Edit Referral Incentives,
+      :class: is-minimal
 
 3. Configure the incentives as desired inside the Referral Incentive Editor.
    To configure Incentive types other than Coupon Codes, please contact your
@@ -71,12 +71,12 @@ To configure incentives:
 
 .. note::
 
-  If there is a delay configured into when the Advocate reward is approved then
-  the Reward Webhook trigger when the Advocate reward is ready to be, or has
-  been given. For example, if campaigns are set to send an Advocate their reward
-  three days after a Friend makes an eligible purchase, then the Reward Webhook
-  will be called three days after the Friend makes the eligible purchase. You
-  can select these delays under **Fraud Settings**, which is found under **Menu**.
+   If there is a delay configured into when the Advocate reward is approved then
+   the Reward Webhook trigger when the Advocate reward is ready to be, or has
+   been given. For example, if campaigns are set to send an Advocate their reward
+   three days after a Friend makes an eligible purchase, then the Reward Webhook
+   will be called three days after the Friend makes the eligible purchase. You
+   can select these delays under **Fraud Settings**, which is found under **Menu**.
 
 Once incentives are configured for a referral campaign, Talkable will then call
 the Reward Webhook any time either an Advocate or a Friend should receive a
@@ -85,13 +85,13 @@ Webhook Set Up Steps <web_hooks>`
 
 .. raw:: html
 
-  <h2>Payload parameters provided by Reward Webhook</h2>
+   <h2>Payload parameters provided by Reward Webhook</h2>
 
 The sample payload with parameters for Reward Webhook is available here: `Reward Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Reward/post_your_api_reward_web_hook_path>`_.
 
 .. raw:: html
 
-  <h2>Reasons</h2>
+   <h2>Reasons</h2>
 
 Reward reason can be of 5 following general types.
 
diff --git a/source/web_hooks/unsubscribe.rst b/source/web_hooks/unsubscribe.rst
index 523bd1520..7686cec00 100644
--- a/source/web_hooks/unsubscribe.rst
+++ b/source/web_hooks/unsubscribe.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-  :description: Unsubscribe Webhook notifies you that a user has unsubscribed from Talkable referral email.
+   :description: Unsubscribe Webhook notifies you that a user has unsubscribed from Talkable referral email.
 
 Unsubscribe Webhook
 ===================
@@ -19,13 +19,13 @@ Use cases for the Unsubscribe Webhook include:
 
 .. raw:: html
 
-  <h2>When does Talkable call the Unsubscribe Webhook?</h2>
+   <h2>When does Talkable call the Unsubscribe Webhook?</h2>
 
 Talkable Unsubscribe Webhook is called any time a user unsubscribes from a
 Talkable sent email.
 
 .. raw:: html
 
-  <h2>Payload parameters provided</h2>
+   <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Unsubscribe Webhook is available here: `Unsubscribe Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Unsubscribe/post_your_api_unsubscribe_web_hook_path>`_.

From 81f3502503a63a6bc4928534a1940f3f9a32ca3c Mon Sep 17 00:00:00 2001
From: Enver <enver.ablyaev@gmail.com>
Date: Mon, 3 Feb 2025 21:44:39 +0300
Subject: [PATCH 60/62] Apply suggestions from code review

Co-authored-by: Bohdan Zhuravel <bohdan@zhuravel.bz>
---
 README-maintainer.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/README-maintainer.md b/README-maintainer.md
index 36ac89f19..524c9e2bf 100644
--- a/README-maintainer.md
+++ b/README-maintainer.md
@@ -146,7 +146,6 @@ Add the package to `requirements.txt`.
 Append the package name to `requirements.txt` (version specification is optional at this stage).
 
 > [!NOTE]
->
 > Version pinning can be done later.
 
 Rebuild the container after modifying `requirements.txt`:
@@ -160,5 +159,4 @@ docker compose up -d --build
 Most changes involve editing the [./source/conf.py](./source/conf.py) file or other files in the [./source/](./source/) directory.
 
 > [!NOTE]
->
 > Rebuilding the container is unnecessary for changes to [./source/conf.py](./source/conf.py) or [./source/](./source/). These changes are applied automatically within 1 second.

From dba6f9306c51a517987257afafb0021ce40c001a Mon Sep 17 00:00:00 2001
From: Enver <enver.ablyaev@gmail.com>
Date: Mon, 3 Feb 2025 21:46:00 +0300
Subject: [PATCH 61/62] Update .gitignore

Co-authored-by: Bohdan Zhuravel <bohdan@zhuravel.bz>
---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 867edcc1c..9dd6b0384 100644
--- a/.gitignore
+++ b/.gitignore
@@ -13,6 +13,7 @@ build
 # Python
 .venv
 __pycache__
+
 # Ruby
 .bundle
 Gemfile.lock
\ No newline at end of file

From eb96b4aebb5c9ece08ea7eab3c61088cd1ae47b9 Mon Sep 17 00:00:00 2001
From: "sergii.kostiuk" <sergii.kostiuk@talkable.com>
Date: Tue, 4 Feb 2025 00:38:49 +0200
Subject: [PATCH 62/62] add build for sphinx

---
 deploy/deploy.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/deploy/deploy.sh b/deploy/deploy.sh
index bb2e9899b..659f94f00 100755
--- a/deploy/deploy.sh
+++ b/deploy/deploy.sh
@@ -97,8 +97,8 @@ deploy_docs() {
     git pull origin
     docker-compose ls
     docker ps
-    docker-compose down
-    docker-compose up -d --remove-orphans
+    docker-compose down -v
+    docker-compose up -d --build --remove-orphans
 EOF
 }