From 92ca2227518ff80df6f6725b1b7a33aeb340c098 Mon Sep 17 00:00:00 2001
From: Minh Nguyen <minhnc@younetco.com>
Date: Thu, 17 Mar 2022 17:13:25 +0700
Subject: [PATCH 01/14] Integration Contentful

---
 .env                                          |   2 +
 custom_theme/blog.html                        |  31 +-
 custom_theme/community.html                   |  74 +--
 custom_theme/home.html                        | 188 +------
 .../partials/contentful/blog-item.html        |  19 +
 custom_theme/partials/contentful/button.html  |   1 +
 .../partials/contentful/card-item.html        |  15 +
 custom_theme/partials/contentful/feature.html |  11 +
 .../partials/contentful/github-list-item.html |  19 +
 .../partials/contentful/github-list.html      |  15 +
 .../partials/contentful/grid-listing.html     |  18 +
 custom_theme/partials/contentful/hero.html    |   8 +
 .../partials/contentful/hubSpot-form.html     |  18 +
 .../partials/contentful/logo-list-item.html   |   9 +
 .../partials/contentful/logo-list.html        |  19 +
 .../partials/contentful/rich-text.html        |   6 +
 custom_theme/partials/contentful/section.html |  13 +
 main.py                                       | 114 +++-
 requirements.txt                              |   4 +-
 src/assets/stylesheets/extra.css              |  17 +
 .../index.md                                  |  30 --
 .../index.md                                  |  97 ----
 .../index.md                                  |  26 -
 .../index.md                                  |  53 --
 .../index.md                                  |  50 --
 .../index.md                                  | 179 -------
 .../index.md                                  |  70 ---
 .../index.md                                  |  86 ---
 .../axonis-enterprise-use-of-truffle/index.md |  91 ----
 .../index.md                                  |  41 --
 src/blog/blockchain-will-cure-cancer/index.md |  48 --
 src/blog/blog.html.jinja2                     |   7 +
 .../index.md                                  |  31 --
 .../index.md                                  |  32 --
 .../index.md                                  |  39 --
 .../index.md                                  |  80 ---
 src/blog/data.json                            | 506 ------------------
 .../index.md                                  |  61 ---
 .../index.md                                  | 122 -----
 src/blog/designing-the-ganache-logo/index.md  |  70 ---
 .../index.md                                  |  96 ----
 src/blog/drizzle-150-a-new-beginning/index.md |  69 ---
 .../index.md                                  |  57 --
 src/blog/drizzle-vue-a-truffle-story/index.md |  70 ---
 src/blog/ethereum-gas-exactimation/index.md   | 175 ------
 src/blog/first-ever-truffle-retreat/index.md  | 127 -----
 .../index.md                                  |  49 --
 src/blog/github-repository-moved/index.md     |  24 -
 .../index.md                                  |  76 ---
 .../index.md                                  |  99 ----
 .../index.md                                  |  62 ---
 .../index.md                                  |  74 ---
 src/blog/introducing-ganache-7/index.md       | 310 -----------
 .../introducing-truffle-dashboard/index.md    | 171 ------
 .../introducing-truffle-db-part-1/index.md    |  55 --
 .../introducing-truffle-db-part-2/index.md    | 110 ----
 .../index.md                                  |  87 ---
 .../index.md                                  |  30 --
 .../index.md                                  |  40 --
 .../index.md                                  | 100 ----
 .../index.md                                  |  41 --
 .../index.md                                  |  48 --
 .../stack-tracing-with-truffle-test/index.md  |  42 --
 src/blog/sunsetting-truffle-teams/index.md    |  46 --
 src/blog/take-a-dive-into-truffle-5/index.md  | 136 -----
 .../index.md                                  |  36 --
 src/blog/testrpc-is-now-ganache/index.md      |  37 --
 .../index.md                                  |  82 ---
 .../index.md                                  |  32 --
 .../index.md                                  |  33 --
 src/blog/token-taxonomy-framework/index.md    |  15 -
 src/blog/truffle-320-released/index.md        |  44 --
 .../index.md                                  |  50 --
 .../index.md                                  |  38 --
 .../index.md                                  |  39 --
 .../index.md                                  |  35 --
 .../index.md                                  |  38 --
 .../truffle-teams-gets-a-new-look/index.md    |  53 --
 .../index.md                                  |  37 --
 src/blog/truffle-v5-has-arrived/index.md      | 113 ----
 .../index.md                                  |  46 --
 .../index.md                                  |  44 --
 .../index.md                                  |  26 -
 src/blog/using-the-ens-integration/index.md   | 126 -----
 .../index.md                                  | 102 ----
 src/blog/why-i-love-trufflecon/index.md       |  31 --
 .../index.md                                  |  61 ---
 .../index.md                                  |  37 --
 .../index.md                                  |  45 --
 .../blog/introducing-ganache-7/example-1.png  | Bin
 .../blog/introducing-ganache-7/example-2.png  | Bin
 .../blog/introducing-ganache-7/ganache-v7.png | Bin
 .../secrets-oh-no.png                         | Bin
 .../truffle-dashboard-cli.png                 | Bin
 .../truffle-dashboard-confirm.png             | Bin
 .../truffle-dashboard-connect-wallet.png      | Bin
 .../truffle-dashboard-private-keys.png        | Bin
 .../truffle-dashboard-select-network.png      | Bin
 .../truffle-dashboard-sign.png                | Bin
 99 files changed, 334 insertions(+), 5380 deletions(-)
 create mode 100644 .env
 create mode 100644 custom_theme/partials/contentful/blog-item.html
 create mode 100644 custom_theme/partials/contentful/button.html
 create mode 100644 custom_theme/partials/contentful/card-item.html
 create mode 100644 custom_theme/partials/contentful/feature.html
 create mode 100644 custom_theme/partials/contentful/github-list-item.html
 create mode 100644 custom_theme/partials/contentful/github-list.html
 create mode 100644 custom_theme/partials/contentful/grid-listing.html
 create mode 100644 custom_theme/partials/contentful/hero.html
 create mode 100644 custom_theme/partials/contentful/hubSpot-form.html
 create mode 100644 custom_theme/partials/contentful/logo-list-item.html
 create mode 100644 custom_theme/partials/contentful/logo-list.html
 create mode 100644 custom_theme/partials/contentful/rich-text.html
 create mode 100644 custom_theme/partials/contentful/section.html
 delete mode 100644 src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
 delete mode 100644 src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
 delete mode 100644 src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
 delete mode 100644 src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
 delete mode 100644 src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
 delete mode 100644 src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
 delete mode 100644 src/blog/announcing-collaboration-with-filecoin/index.md
 delete mode 100644 src/blog/announcing-full-portable-solidity-debugger/index.md
 delete mode 100644 src/blog/axonis-enterprise-use-of-truffle/index.md
 delete mode 100644 src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
 delete mode 100644 src/blog/blockchain-will-cure-cancer/index.md
 create mode 100644 src/blog/blog.html.jinja2
 delete mode 100644 src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
 delete mode 100644 src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
 delete mode 100644 src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
 delete mode 100644 src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
 delete mode 100644 src/blog/data.json
 delete mode 100644 src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
 delete mode 100644 src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
 delete mode 100644 src/blog/designing-the-ganache-logo/index.md
 delete mode 100644 src/blog/develop-using-fluidity-truffle-box/index.md
 delete mode 100644 src/blog/drizzle-150-a-new-beginning/index.md
 delete mode 100644 src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
 delete mode 100644 src/blog/drizzle-vue-a-truffle-story/index.md
 delete mode 100644 src/blog/ethereum-gas-exactimation/index.md
 delete mode 100644 src/blog/first-ever-truffle-retreat/index.md
 delete mode 100644 src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
 delete mode 100644 src/blog/github-repository-moved/index.md
 delete mode 100644 src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
 delete mode 100644 src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
 delete mode 100644 src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
 delete mode 100644 src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
 delete mode 100644 src/blog/introducing-ganache-7/index.md
 delete mode 100644 src/blog/introducing-truffle-dashboard/index.md
 delete mode 100644 src/blog/introducing-truffle-db-part-1/index.md
 delete mode 100644 src/blog/introducing-truffle-db-part-2/index.md
 delete mode 100644 src/blog/iterate-faster-with-truffle-teams/index.md
 delete mode 100644 src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
 delete mode 100644 src/blog/one-hundred-documentation-pull-requests/index.md
 delete mode 100644 src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
 delete mode 100644 src/blog/removing-installation-issues-continued-testrpc/index.md
 delete mode 100644 src/blog/sandbox-forking-with-truffle-teams/index.md
 delete mode 100644 src/blog/stack-tracing-with-truffle-test/index.md
 delete mode 100644 src/blog/sunsetting-truffle-teams/index.md
 delete mode 100644 src/blog/take-a-dive-into-truffle-5/index.md
 delete mode 100644 src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
 delete mode 100644 src/blog/testrpc-is-now-ganache/index.md
 delete mode 100644 src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
 delete mode 100644 src/blog/the-best-ways-to-contribute-to-truffle/index.md
 delete mode 100644 src/blog/the-blockchain-problem-that-ens-solves/index.md
 delete mode 100644 src/blog/token-taxonomy-framework/index.md
 delete mode 100644 src/blog/truffle-320-released/index.md
 delete mode 100644 src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
 delete mode 100644 src/blog/truffle-and-infura-support-arbitrum/index.md
 delete mode 100644 src/blog/truffle-and-infura-support-optimism/index.md
 delete mode 100644 src/blog/truffle-and-infura-support-polygon/index.md
 delete mode 100644 src/blog/truffle-boxes-making-life-sweeter/index.md
 delete mode 100644 src/blog/truffle-teams-gets-a-new-look/index.md
 delete mode 100644 src/blog/truffle-teams-now-supports-private-repositories/index.md
 delete mode 100644 src/blog/truffle-v5-has-arrived/index.md
 delete mode 100644 src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
 delete mode 100644 src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
 delete mode 100644 src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
 delete mode 100644 src/blog/using-the-ens-integration/index.md
 delete mode 100644 src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
 delete mode 100644 src/blog/why-i-love-trufflecon/index.md
 delete mode 100644 src/blog/why-were-organizing-trufflecon-2018/index.md
 delete mode 100644 src/blog/you-can-now-make-your-own-truffle-box/index.md
 delete mode 100644 src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md
 rename src/{ => img}/blog/introducing-ganache-7/example-1.png (100%)
 rename src/{ => img}/blog/introducing-ganache-7/example-2.png (100%)
 rename src/{ => img}/blog/introducing-ganache-7/ganache-v7.png (100%)
 rename src/{ => img}/blog/introducing-truffle-dashboard/secrets-oh-no.png (100%)
 rename src/{ => img}/blog/introducing-truffle-dashboard/truffle-dashboard-cli.png (100%)
 rename src/{ => img}/blog/introducing-truffle-dashboard/truffle-dashboard-confirm.png (100%)
 rename src/{ => img}/blog/introducing-truffle-dashboard/truffle-dashboard-connect-wallet.png (100%)
 rename src/{ => img}/blog/introducing-truffle-dashboard/truffle-dashboard-private-keys.png (100%)
 rename src/{ => img}/blog/introducing-truffle-dashboard/truffle-dashboard-select-network.png (100%)
 rename src/{ => img}/blog/introducing-truffle-dashboard/truffle-dashboard-sign.png (100%)

diff --git a/.env b/.env
new file mode 100644
index 000000000..6438235e7
--- /dev/null
+++ b/.env
@@ -0,0 +1,2 @@
+CONTENTFUL_SPACE_ID = 'yfwlmanyz0dl'
+CONTENTFUL_TOKEN = 'avq84-sow2ZdZmBtpfkNvUL5RixZmEvshgPSLuNQ4PI'
\ No newline at end of file
diff --git a/custom_theme/blog.html b/custom_theme/blog.html
index 708757f76..3ee7fadbd 100644
--- a/custom_theme/blog.html
+++ b/custom_theme/blog.html
@@ -41,26 +41,17 @@
 
 <div class="container">
     <section class="p-5">
-        <h1>Truffle Blog</h1>
-        {% for post in config.extra.posts %}
-            <a href="{{ post.route }}">
-                <div class="row pt-3 pb-3">
-                    {% if post.image %}
-                    <div class="col-md-3">
-                        <img src="{{ post.image }}" class="rounded-circle img-fluid green" />
-                    </div>
-                    {% endif %}
-                    <div class="col-md-9">
-                        <h2>{{ post.title }}</h2>
-                        <p>{{ post.date }}&nbsp;&nbsp;&nbsp;<i class="far fa-user"></i> {{ post.author }}</p>
-                        {% if post.excerpt is not none %}
-                            <p>{{ post.excerpt }}</p>
-                        {% endif %}
-                        <span class="btn btn-secondary">READ MORE</span>
-                    </div>
-                </div>
-            </a>
-        {% endfor %}
+        <h1>{{config.extra.contentful_page.blog.title}}</h1>
+        {% with modules = config.extra.contentful_blogs %}
+          {% for module in modules %}
+            {% with %}
+              {% set props = module %}
+              <!-- {% set template = module.template %} -->
+              {% set template = config.extra.module_id_parse(module.sys['content_type'].id) %}
+              {% include 'partials/contentful/'+template+'.html' %}
+            {% endwith %}
+          {% endfor %}
+        {% endwith %}
     </section>
 </div>
 
diff --git a/custom_theme/community.html b/custom_theme/community.html
index 89a6416ab..70c97f392 100644
--- a/custom_theme/community.html
+++ b/custom_theme/community.html
@@ -40,70 +40,16 @@
     
   </style>
 
-<div class="container">
-  <section class="p-5">
-    <main role="main" class="container">
-      <div class="row align-items-center">
-        <div class="col-sm">
-          <h1><img class="support-heading" src="../img/support-header.svg" alt="Life Preserver" title="Support" /> COMMUNITY &amp; SUPPORT</h1>
-          <p class="mb-0"><strong>Help is close by!</strong> Truffle has a spectacular community of developers--the largest of any Ethereum development framework!</p>
-        </div>
-      </div>
-    </main>
-    
-    <main class="banner banner-light-cream pt-5 pb-5">
-      <div class="container">
-        <div class="row">
-          <div class="col">
-            <div class="card">
-              <div class="card-body card-zendesk">
-                <h2>Open a Support Ticket! <span class="badge rounded-pill bg-success">NEW</span></h2>
-                <p>The easiest way to track your conversation and contribute to our knowledge base! Open a support ticket to begin talking to our support staff. Common questions will be added to our knowledge base to assist future Trufflers!</p>
-                <a href="https://trufflesuite.zendesk.com/hc/en-us/requests/new" class="btn btn-sm btn-truffle text-uppercase">Open a Support Ticket</a>
-              </div>
-            </div>
-    
-            <h2 class="mt-5">A Little Help from Our Friends</h2>
-            <p>If you’re stuck trying to get something to work, have any questions, or suggestions, the fastest way to get help from the community. Truffle has the largest community of blockchain developers on Earth! Chat with hundreds of your fellow Trufflers on Gitter or Spectrum.</p>
-            <hr />
-          </div>
-        </div>
-    
-        <div class="row">
-          <div class="col-6">
-            <h3>Chat on Gitter</h3>
-            <p class="mb-0">For a chatroom, <a class="minty" href="http://gitter.im/ConsenSys/truffle">check out Gitter</a>. It's very active; the quickest response is generally here but it's difficult to track longer threads or search.</p>
-          </div>
-    
-          <div class="col-6">
-            <h3>Post on Spectrum</h3>
-            <p class="mb-0">For a forum, <a class="minty" href="https://spectrum.chat/trufflesuite?tab=posts">check out Spectrum</a>. Responses can be slower, but the post/response format lends itself to better tracking of your question and searchability of others.</p>
-          </div>
-        </div>
-    
-        <div class="row">
-          <div class="col">
-            <h2 class="mt-5"><i class="fab fa-github"></i> Find us on GitHub!</h2>
-            <p>Truffle not behaving as intended? Know your issue is a bug? Want to suggest an improvement? This is the place to do it!</p>
-            <hr />
-          </div>
-        </div>
-    
-        <div class="row">
-          <div class="col-6">
-            <h3>Submit an Issue on GitHub</h3>
-            <p>If something’s not working as expected, or you have an idea for a feature or change you’d like to see, please <a class="minty" href="https://github.com/trufflesuite/">open an issue</a> and start a discussion.</p>
-          </div>
-    
-          <div class="col-6">
-            <h3>Help Improve the Documentation</h3>
-            <p>We’re only human, and need all the help you can give us to improve the documentation. If you’d like to submit any feedback or suggestions, please create a pull request on <a class="minty" href="https://github.com/trufflesuite/trufflesuite.com/">our documentation repository</a>.</p>
-          </div>
-        </div>
-      </div>
-    </main>
-  </section>
-</div>
+{% with modules = config.extra.contentful_page.community.modules %}
+  {% for module in modules %}
+    {% with %}
+      {% set props = module %}
+      <!-- {% set template = module.template %} -->
+      {% set template = config.extra.module_id_parse(module.sys['content_type'].id) %}
+      {% include 'partials/contentful/'+template+'.html' %}
+    {% endwith %}
+  {% endfor %}
+{% endwith %}
 
 {% endblock %}
 
diff --git a/custom_theme/home.html b/custom_theme/home.html
index 2d2b7f297..f600698b9 100644
--- a/custom_theme/home.html
+++ b/custom_theme/home.html
@@ -32,182 +32,18 @@
       }
     </style>
 
-<!-- Hero for landing page -->
-<section class="pt-5">
-    <h1 class="text-center">Sweet Tools for Smart Contracts</h1>
-    <p class="text-center">The <strong>Truffle Suite</strong> gets developers from idea to dapp as comfortably as possible.</p>
-    <img class="img-fluid" src="img/homepage-hero-sept2021.svg" alt="Truffle Suite helps you iterate through the development lifecycle" />
-</section>
-
-<section class="bg-dark text-white">
-    <div class="container p-5">
-        <div class="row">
-            <div class="col">
-            <h2 class="text-truffle"><span class="narrow">T</span>RUFFLE
-                <div class="github-button-wrapper ml-0">
-                <a class="github-button" href="https://github.com/trufflesuite/truffle" data-size="large"  data-show-count="true" aria-label="Star trufflesuite/truffle on GitHub">Star</a>
-                </div>
-            </h2>
-            <h5 class="color-truffle">SMART CONTRACTS MADE SWEETER</h5>
-            <p>A world class development environment, testing framework and asset pipeline for blockchains using the Ethereum Virtual Machine (EVM), aiming to make life as a developer easier.</p>
-            <a href="truffle" class="btn btn-sm btn-truffle">LEARN MORE</a>
-            <a href="https://github.com/trufflesuite/truffle" class="btn btn-sm btn-truffle">GITHUB REPO</a>
-            <a href="docs/truffle" class="btn btn-sm btn-truffle">DOCS</a>
-        
-                <h2 class="text-ganache mt-5">Ganache
-                <div class="github-button-wrapper">
-                    <a class="github-button" href="https://github.com/trufflesuite/ganache" data-size="large"  data-show-count="true" aria-label="Star trufflesuite/ganache on GitHub">Star</a>
-                </div>
-                </h2>
-                <h5 class="color-ganache">ONE CLICK BLOCKCHAIN</h5> 
-                <p>A personal blockchain for Ethereum development you can use to deploy contracts, develop your applications, and run tests. It is available as both a desktop application as well as a command-line tool (formerly known as the TestRPC). Ganache is available for Windows, Mac, and Linux.</p>
-                <a href="ganache" class="btn btn-sm btn-ganache">LEARN MORE</a>
-                <a href="https://github.com/trufflesuite/ganache" class="btn btn-sm btn-ganache">GITHUB REPO</a>
-                <a href="docs/ganache" class="btn btn-sm btn-ganache">DOCS</a>
-        
-                <h2 class="text-drizzle mt-5">dri<span class="drizzle-z-skew-1">z</span><span class="drizzle-z-skew-2">z</span>le
-                <div class="github-button-wrapper">
-                    <a class="github-button" href="https://github.com/trufflesuite/drizzle" data-size="large"  data-show-count="true" aria-label="Star trufflesuite/drizzle on GitHub">Star</a>
-                </div>
-                </h2>
-                <h5 class="color-drizzle">FRESH CHAIN-DATA FOR FRONT-ENDS</h5>
-                <p>A collection of front-end libraries that make writing dapp front-ends easier and more predictable. The core of Drizzle is based on a Redux store, so you have access to the spectacular development tools around Redux. We take care of synchronizing your contract data, transaction data and more.</p>
-                <a href="drizzle" class="btn btn-sm btn-drizzle">LEARN MORE</a>
-                <a href="https://github.com/trufflesuite/drizzle" class="btn btn-sm btn-drizzle">GITHUB REPO</a>
-                <a href="docs/drizzle" class="btn btn-sm btn-drizzle">DOCS</a>
-            </div>
-        </div>
-    </div>
-</section>
-
-<section>
-    <div class="container p-5">
-      <div class="row">
-        <div class="col">
-          <h1>CASE STUDIES</h1>
-        </div>
-      </div>
-  
-      <div class="row align-items-center justify-content-center text-center mb-2">
-        <div class="col-8 col-sm-6 col-md-3 mt-5 mt-sm-3 mb-4 mb-sm-3">
-          <a href="case-studies/case-study-dish-network">
-            <img class="img-fluid" src="img/case-studies/case-study-dish-network/dish-logo.svg" alt="DISH Network" />
-          </a>
-        </div>
-        <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-          <a href="case-studies/case-study-microsoft-xbox">
-            <img class="img-fluid" src="img/case-studies/case-study-microsoft-xbox/xbox-logo.svg" alt="Microsoft Xbox" />
-          </a>
-        </div>
-        <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-          <a href="case-studies/case-study-starbucks">
-            <img class="img-fluid pl-5 pr-5" src="img/case-studies/case-study-starbucks/starbucks-logo.svg" alt="Starbucks" />
-          </a>
-        </div>
-        <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-          <a href="case-studies/case-study-microsoft-and-the-world-bank">
-            <img class="img-fluid" src="img/case-studies/case-study-microsoft-and-the-world-bank/msft-wb-logo.svg" alt="Microsoft & The World Bank" />
-          </a>
-        </div>
-      </div>
-    </div>
-</section>
-
-<section class="bg-dark text-white">
-    <div class="container p-5">
-        <div class="row">
-            <div class="col">
-                <h2>Awesome Companies Using Truffle</h2>
-            </div>
-        </div>
-
-        <div class="row align-items-center justify-content-center text-center mb-2">
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art02-consensys.svg" alt="ConsenSys" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/consensys-diligence-logo.svg" alt="ConsenSys Diligence" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-5 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art01-microsoft.svg" alt="Microsoft" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art03-ey.svg" alt="Ernst & Young" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art04-airbus.svg" alt="Airbus" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art05-gd.svg" alt="General Dynamics" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art06-amazon.svg" alt="Amazon" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art07-jpmorgan.svg" alt="J.P.Morgan" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid pl-4 pr-4 sepia" src="img/home/art08-vmware.svg" alt="VMWare" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art09-shapeshift.svg" alt="ShapeShift" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid sepia" src="img/home/art10-colony.svg" alt="Colony" />
-            </div>
-            <div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
-                <img class="img-fluid pl-4 pr-4 sepia" src="img/home/art11-amberdata.svg" alt="Amberdata" />
-            </div>
-        </div>
-    </div>
-</section>
-
-<section>
-    <div class="container p-5">
-      <div class="row text-center justify-content-center">
-        <div class="col-md-10 hs-form-inline">
-          <h1>SIGN UP FOR THE TRUFFLE MAILING LIST</h1>
-          <p>Sign up today to be a member of the Truffle mailing list. You'll be added to our low volume mailing list which we'll
-            use to communicate future changes, development ideas and allow you to shape Truffle's development.
-          </p>
-          <!--[if lte IE 8]>
-            <script charset="utf-8" type="text/javascript" src="/js.hsforms.net/forms/v2-legacy.js"></script>
-          <![endif]-->
-          <script charset="utf-8" type="text/javascript" src="//js.hsforms.net/forms/v2.js"></script>
-          <script>
-            hbspt.forms.create({
-              portalId: "4795067",
-              formId: "d18995c8-32bb-4b2d-bde9-3f49fb3d2837"
-            });
-          </script>
-        </div>
-      </div>
-    </div>
-</section>
-  
-  <section class="bg-dark text-white">
-    <div class="container p-5">
-      <div class="row align-items-center home-github-row">
-        <div class="col-md-8">
-          <h1>CONTRIBUTE TO THE TRUFFLE SUITE</h1>
-  
-          <p>We need your help! There are many ways you can help contribute to the Truffle project. Here are some ways that you
-            can contribute:</p>
-  
-          <ol>
-            <li>Open issues on our <a class="minty" href="https://github.com/trufflesuite">GitHub page</a>.</li>
-            <li>Submit Pull Requests to the GitHub project - but please open an issue to discuss the feature first!</li>
-            <li>Test out the Beta versions of Truffle to help us nail down issues and stomp bugs.</li>
-            <li>Participate in our <a class="minty" href="http://gitter.im/ConsenSys/truffle">community Gitter channel</a> helping out other users.</li>
-          </ol>
-        </div>
-  
-        <div class="col-md-4">
-          <img src="img/github-logo-gradient.svg" class="img-fluid" alt="GitHub Logo" title="GitHub Logo" />
-        </div>
-      </div>
-    </div>
-</section>
+<!-- Contentful modules render -->
+
+{% with modules = config.extra.contentful_page.home.modules %}
+  {% for module in modules %}
+    {% with %}
+      {% set props = module %}
+      <!-- {% set template = module.template %} -->
+      {% set template = config.extra.module_id_parse(module.sys['content_type'].id) %}
+      {% include 'partials/contentful/'+template+'.html' %}
+    {% endwith %}
+  {% endfor %}
+{% endwith %}
 
 <script async defer src="https://buttons.github.io/buttons.js"></script>
 
diff --git a/custom_theme/partials/contentful/blog-item.html b/custom_theme/partials/contentful/blog-item.html
new file mode 100644
index 000000000..a188b072d
--- /dev/null
+++ b/custom_theme/partials/contentful/blog-item.html
@@ -0,0 +1,19 @@
+<a href={{config.extra.parse_url(props.slug)}}>
+  <div class="row pt-3 pb-3">
+      {% if props.thumbnail %}
+      <div class="col-md-3">
+          <img alt={{props.thumbnail.title}} src={{config.extra.parse_asset_contentful(props.thumbnail)}} class="rounded-circle img-fluid green" />
+      </div>
+      {% endif %}
+      <div class="col-md-9">
+          <h2>{{ props.title }}</h2>
+          <p>{% if props.date %}{{ props.date.strftime('%Y-%m-%d') }}&nbsp;&nbsp;&nbsp;{% endif %}<i class="far fa-user"></i> {{ props.author }}</p>
+          {% if props.description %}
+              <p>{{ props.description }}</p>
+          {% endif %}
+          {% if props.cta_text %}
+          <span class="btn btn-secondary">{{props.cta_text}}</span>
+          {% endif %}
+      </div>
+  </div>
+</a>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/button.html b/custom_theme/partials/contentful/button.html
new file mode 100644
index 000000000..25054d22c
--- /dev/null
+++ b/custom_theme/partials/contentful/button.html
@@ -0,0 +1 @@
+<a href={{config.extra.parse_url(props.url)}} class="btn btn-sm btn-{{props.type}}">{{props.text}}</a>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/card-item.html b/custom_theme/partials/contentful/card-item.html
new file mode 100644
index 000000000..b1a0bafe6
--- /dev/null
+++ b/custom_theme/partials/contentful/card-item.html
@@ -0,0 +1,15 @@
+<div class="card mt-5">
+  <div class="card-body card-zendesk">
+    <h2>{{props.title}}</h2>
+    <p>{{props.description}}</p>
+    {% with buttons = props.buttons %}
+      {% for button in buttons %}
+        {% with %}
+          {% set props = button %}
+          {% set template = config.extra.module_id_parse(button.sys['content_type'].id) %}
+          {% include 'partials/contentful/'+template+'.html' %}
+        {% endwith %}
+      {% endfor %}
+    {% endwith %}
+  </div>
+</div>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/feature.html b/custom_theme/partials/contentful/feature.html
new file mode 100644
index 000000000..69da4b3f7
--- /dev/null
+++ b/custom_theme/partials/contentful/feature.html
@@ -0,0 +1,11 @@
+<div class="">
+  <div class="row align-items-center home-github-row">
+    <div class="col-md-8">
+      <h1>{{props.title}}</h1>
+      <p>{{props.description}}</p>
+    </div>
+    <div class="col-md-4">
+      <img class="img-fluid " src={{config.extra.parse_asset_contentful(props.image)}} alt={{props.image.title}} title={{props.image.title}} />
+    </div>
+  </div>
+</div>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/github-list-item.html b/custom_theme/partials/contentful/github-list-item.html
new file mode 100644
index 000000000..32434ef09
--- /dev/null
+++ b/custom_theme/partials/contentful/github-list-item.html
@@ -0,0 +1,19 @@
+<div class="github-item-row">
+  <h2 class="text-{{props.type}}">
+    <div>{{props.heading}}</div>
+    <div class="github-button-wrapper ml-0">
+    <a class="github-button" href="https://github.com/trufflesuite/{{props.type}}" data-size="large"  data-show-count="true" aria-label="Star trufflesuite/{{props.type}} on GitHub">Star</a>
+    </div>
+  </h2>
+  <h5 class="color-{{props.type}}">{{props.title}}</h5>
+  <p>{{props.description}}</p>
+  {% with buttons = props.buttons %}
+    {% for button in buttons %}
+      {% with %}
+        {% set props = button %}
+        {% set template = config.extra.module_id_parse(button.sys['content_type'].id) %}
+        {% include 'partials/contentful/'+template+'.html' %}
+      {% endwith %}
+    {% endfor %}
+  {% endwith %}
+</div>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/github-list.html b/custom_theme/partials/contentful/github-list.html
new file mode 100644
index 000000000..f70ad84d2
--- /dev/null
+++ b/custom_theme/partials/contentful/github-list.html
@@ -0,0 +1,15 @@
+<div class="">
+    <div class="row">
+        <div class="col">
+          {% with modules = props.modules %}
+            {% for module in modules %}
+              {% with %}
+                {% set props = module %}
+                {% set template = config.extra.module_id_parse(module.sys['content_type'].id) %}
+                {% include 'partials/contentful/'+template+'.html' %}
+              {% endwith %}
+            {% endfor %}
+          {% endwith %}
+        </div>
+    </div>
+</div>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/grid-listing.html b/custom_theme/partials/contentful/grid-listing.html
new file mode 100644
index 000000000..338083786
--- /dev/null
+++ b/custom_theme/partials/contentful/grid-listing.html
@@ -0,0 +1,18 @@
+<div class="mt-5">
+  <h2>{{props.title}}</h2>
+  <p>{{props.description}}</p>
+  <div class="row">
+    {% with listing = props.listing %}
+      {% for item in listing %}
+        {% with %}
+          {% set column = 12 // props.columns %}
+          {% set props = item %}
+          {% set template = config.extra.module_id_parse(item.sys['content_type'].id) %}
+          <div class="col-{{column}} col-xs-12">
+            {% include 'partials/contentful/'+template+'.html' %}
+          </div>
+        {% endwith %}
+      {% endfor %}
+    {% endwith %}
+  </div>
+</div>
diff --git a/custom_theme/partials/contentful/hero.html b/custom_theme/partials/contentful/hero.html
new file mode 100644
index 000000000..a8411f359
--- /dev/null
+++ b/custom_theme/partials/contentful/hero.html
@@ -0,0 +1,8 @@
+<section class="pt-5">
+  <h1 class="text-center">{{props.title}}</h1>
+  <p class="text-center">{{props.description}}</p>
+  {% if props.image is defined %}
+  <!-- <img class="img-fluid" src="{{props.image.file.url}}" alt={{props.image.title}} /> -->
+  <img class="img-fluid img-fullwidth" src={{config.extra.parse_asset_contentful(props.image)}} alt={{props.image.title}} />
+  {% endif %}
+</section>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/hubSpot-form.html b/custom_theme/partials/contentful/hubSpot-form.html
new file mode 100644
index 000000000..d24b4fbee
--- /dev/null
+++ b/custom_theme/partials/contentful/hubSpot-form.html
@@ -0,0 +1,18 @@
+<div class="">
+  <div class="row text-center justify-content-center">
+    <div class="col-md-10 hs-form-inline">
+      <h1>{{props.title}}</h1>
+      <p>{{props.description}}</p>
+      <!--[if lte IE 8]>
+        <script charset="utf-8" type="text/javascript" src="/js.hsforms.net/forms/v2-legacy.js"></script>
+      <![endif]-->
+      <script charset="utf-8" type="text/javascript" src="//js.hsforms.net/forms/v2.js"></script>
+      <script>
+        hbspt.forms.create({
+          portalId: "{{props.portal_id}}",
+          formId: "{{props.form_id}}"
+        });
+      </script>
+    </div>
+  </div>
+</div>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/logo-list-item.html b/custom_theme/partials/contentful/logo-list-item.html
new file mode 100644
index 000000000..204fa8f23
--- /dev/null
+++ b/custom_theme/partials/contentful/logo-list-item.html
@@ -0,0 +1,9 @@
+<div class="col-8 col-sm-6 col-md-3 mt-4 mt-sm-3 mb-4 mb-sm-3">
+  {% if props.url %}
+  <a href={{config.extra.parse_url(props.url)}}>
+    <img class="img-fluid {{props.image.theme}}" src={{config.extra.parse_asset_contentful(props.image)}} alt={{props.image.title}} />
+  </a>
+  {% else %}
+  <img class="img-fluid {{props.image.theme}}" src={{config.extra.parse_asset_contentful(props.image)}} alt={{props.image.title}} />
+  {% endif %}
+</div>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/logo-list.html b/custom_theme/partials/contentful/logo-list.html
new file mode 100644
index 000000000..640cb82d7
--- /dev/null
+++ b/custom_theme/partials/contentful/logo-list.html
@@ -0,0 +1,19 @@
+<div class="">
+    <div class="row">
+        <div class="col">
+            <h2>{{props.title}}</h2>
+        </div>
+    </div>
+
+    <div class="row align-items-center justify-content-center text-center mb-2 wrapper-bg-{{props.logo_theme}}">
+        {% with logos = props.logos %}
+          {% for logo in logos %}
+            {% with %}
+              {% set props = logo %}
+              {% set template = config.extra.module_id_parse(logo.sys['content_type'].id) %}
+              {% include 'partials/contentful/'+template+'.html' %}
+            {% endwith %}
+          {% endfor %}
+        {% endwith %}
+    </div>
+</div>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/rich-text.html b/custom_theme/partials/contentful/rich-text.html
new file mode 100644
index 000000000..bcaee07db
--- /dev/null
+++ b/custom_theme/partials/contentful/rich-text.html
@@ -0,0 +1,6 @@
+<div>
+  {{props.title}}
+  <div>
+    {{props.content}}
+  </div>
+</div>
\ No newline at end of file
diff --git a/custom_theme/partials/contentful/section.html b/custom_theme/partials/contentful/section.html
new file mode 100644
index 000000000..217418152
--- /dev/null
+++ b/custom_theme/partials/contentful/section.html
@@ -0,0 +1,13 @@
+<section class="{% if props.background %}bg-{{props.background}}{% endif %} {% if props.color %}text-{{props.color}}{% endif %}">
+  <div class="{% if props.is_container %}container p-5{% endif %}">
+    {% with modules = props.modules %}
+      {% for module in modules %}
+        {% with %}
+          {% set props = module %}
+          {% set template = config.extra.module_id_parse(module.sys['content_type'].id) %}
+          {% include 'partials/contentful/'+template+'.html' %}
+        {% endwith %}
+      {% endfor %}
+    {% endwith %}
+  </div>
+</section>
\ No newline at end of file
diff --git a/main.py b/main.py
index 9c7446a75..d26cddc73 100644
--- a/main.py
+++ b/main.py
@@ -4,15 +4,116 @@
 
 import json
 import mkdocs
+import contentful
 
 import requests
 from requests.auth import HTTPBasicAuth
 
 from jinja2 import Template
 
+from dotenv import load_dotenv
+
+load_dotenv()
+
+
+def nested_set(dic, keys, value):
+    for key in keys[:-1]:
+        dic = dic.setdefault(key, {})
+    dic[keys[-1]] = value
+
+def parse_url(path):
+    return os.path.join(path, '')
+
+def module_id_parse(id):
+    listMapping = {
+        'hero': 'hero',
+        'githubList': 'github-list',
+        'githubItem': 'github-list-item',
+        'button': 'button',
+        'logoList': 'logo-list',
+        'logoItem': 'logo-list-item',
+        'section': 'section',
+        'hubSpotForm': 'hubSpot-form',
+        'feature': 'feature',
+        'blog': 'blog-item',
+        'cardItem': 'card-item',
+        'richText': 'rich-text',
+        'gridListing': 'grid-listing',
+    }
+    return listMapping[id]
+
+def parse_asset_contentful(data, w = 1200):
+    if ("svg" in data.file['contentType']):
+        return data.url()
+    return data.url(w=w, fm='webp', q=100)
+
+def get_blogs_contentful(client, data):
+    blogs = client.entries({'limit': 500, 'content_type': 'blog', 'include': 10, 'order': '-fields.date,-sys.createdAt'})
+    data = data + blogs.items
+    size = len(data)
+    total = blogs.total
+    if(total > size):
+        return get_blogs_contentful(client, data)
+    return data
+
 def define_env(env):
     "Definition of the module"
 
+    contentful_space_id = os.getenv('CONTENTFUL_SPACE_ID')
+    contentful_token = os.getenv('CONTENTFUL_TOKEN')
+    env.conf['extra']['module_id_parse'] = module_id_parse;
+    env.conf['extra']['parse_asset_contentful'] = parse_asset_contentful;
+    env.conf['extra']['parse_url'] = parse_url;
+    client = contentful.Client(contentful_space_id, contentful_token)
+    site_dir = env.conf['docs_dir']
+
+    # Query all entry 'page'
+    entries = client.entries({'content_type': 'page', 'include': 10})
+    contentful_data = {}
+    # test = client.entry('1CgkzrVtPU7A4FbD6MfwwJ')
+    # from pprint import pprint
+    # pprint(test.date)
+    for entry in entries:
+        # dictModules = [{'template': module_id_parse(module.sys['content_type'].id), 'props': module} for module in entry.modules]
+        nested_set(contentful_data, [entry.slug], entry)
+        env.conf['extra']['contentful_page'] = contentful_data
+
+    #blog page
+    # contentful_entries_blogs = client.entries({'limit': 500, 'content_type': 'blog', 'include': 10, 'order': '-fields.date,-sys.createdAt'})
+    contentful_entries_blogs = get_blogs_contentful(client, [])
+    env.conf['extra']['contentful_blogs'] = contentful_entries_blogs
+
+    for blog in contentful_entries_blogs:
+        blog_dir = os.path.join(site_dir, 'blog', blog.slug)
+
+        if os.path.exists(blog_dir):
+            shutil.rmtree(blog_dir)
+            
+        os.makedirs(blog_dir)
+        file_path = os.path.join(blog_dir, 'index.md')
+
+        #content of blog detail
+        blog_detail = blog.detail
+
+        #heading detail and SEO title
+        blog_detail_title = blog.title
+        if hasattr(blog, 'detail_title'):
+            blog_detail_title = blog.detail_title
+
+        try:
+            markdown = blog_detail
+
+            with open('src/blog/blog.html.jinja2') as file_:
+                template = Template(file_.read())
+
+            outputText = template.render(blog=blog, content=markdown, title=blog_detail_title)
+
+            with open(file_path, 'w') as f:
+                f.write(outputText)
+
+        except Exception as ex:
+            print('error: ' + repr(ex))
+
     # boxes page
     data_file_object = open('src/boxes/data.json')
     boxes  = json.load(data_file_object)
@@ -39,7 +140,6 @@ def define_env(env):
     if os.environ.get("LOCAL_BUILD"):
         env.conf['extra']['boxes'] = env.conf['extra']['boxes'][:6] 
 
-    site_dir = env.conf['docs_dir']
     username = os.environ.get("TRUFFLESUITE_COM_GH_API_USERNAME")
     key = os.environ.get("TRUFFLESUITE_COM_GH_API_KEY")
     for box in env.conf['extra']['boxes']:
@@ -71,18 +171,6 @@ def define_env(env):
 def on_pre_page_macros(env):
     "Pre-page actions"
 
-    # blog posts page
-    blog_file_object = open('src/blog/data.json')
-    posts = json.load(blog_file_object)
-    publishedposts = []
-    for key in posts.keys():
-        if posts[key]['published']:
-            entry = posts[key]
-            entry['route'] = key
-            publishedposts.append(entry)
-
-    env.conf['extra']['posts'] = publishedposts
-
     # guide page
     guide_file_object = open('src/guides/data.json')
     guides = json.load(guide_file_object)
diff --git a/requirements.txt b/requirements.txt
index 8caf2dd63..93c4b001a 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -2,4 +2,6 @@ mkdocs-material==8.0.2
 mkdocs-awesome-pages-plugin==2.5.1
 mkdocs-macros-plugin==0.6.0
 requests==2.26.0
-mkdocs-minify-plugin==0.5.0
\ No newline at end of file
+mkdocs-minify-plugin==0.5.0
+contentful
+python-dotenv
\ No newline at end of file
diff --git a/src/assets/stylesheets/extra.css b/src/assets/stylesheets/extra.css
index 8ac9aba90..61485b565 100644
--- a/src/assets/stylesheets/extra.css
+++ b/src/assets/stylesheets/extra.css
@@ -183,6 +183,10 @@ pre {
   filter: invert(0.5) sepia(1);
 }
 
+.wrapper-bg-sepia img{
+  filter: invert(0.5) sepia(1);
+}
+
 .minty {
   color: var(--mint);
 }
@@ -426,3 +430,16 @@ footer .hs-form ul.hs-error-msgs {
   background-size: 80vh;
   border-top: 1px solid #e911bd;
 }
+
+.github-item-row:not(:first-child) {
+  margin-top: 3rem;
+}
+@media (max-width: 480px){
+  .col-xs-12 {
+    width: 100% !important;
+  }
+}
+
+.img-fullwidth {
+  width: 100%;
+}
\ No newline at end of file
diff --git a/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md b/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
deleted file mode 100644
index 9f4bc58ff..000000000
--- a/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: 10 Things We Don't Do That Make Working at Truffle Awesome
-hide:
-  - navigation
----
-
-![tapestry of Truffle team headshots](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-1.jpg)
-
-At Truffle we have an extremely tight-knit team. You'll see that at this year's TruffleCon, a conference for hundreds of attendees organized by only a handful of people. We often have more work than we can handle, yet we take it on because we love the work we're doing and we love the people we work with. In my history of hopping startups – I'm currently on number nine – I haven't seen this anywhere else, so I wanted to take the time to highlight some things that set Truffle apart from the rest. Here's a list of what we don't do that makes working at Truffle awesome:
-
-1. **We don't have an office.** This is the most important point, as it permeates the makeup and structure of our organization. We have members all over the US and Canada. I live in Yakima, WA, of all places, known more for apples and hops than for tech and blockchain. For communication efficiency we intentionally hired within US time zones, but we realize remote work means there's no office to clock into. We currently have team members working from China, Japan and Germany, following the path their family and personal lives have taken them, while still remaining valuable members of the team.
-1. **We don't clock in.** For most of our team, working remotely means working from home. Often our home life and work life are intertwined, and we know that on some days work wins (i.e., I'm writing this the morning of July 4th, a holiday in the United States), and on other days life wins. This means a flexible schedule is absolutely required. Often, I tell my team to add their life events to their work calendar, like taking their dog to the vet or their kids to school, to ensure work doesn't encroach on the needs of their home life.
-1. **We don't track vacation time.** Our vacation policy is unlimited: We take whatever time we need. This is important to our work/life balance, and it also ensures our team gets much-needed breaks. Over time we've perfected this policy by engaging work and life into a little quid pro quo: If you let your coworkers know about your time off in advance, and you ensure your work is completed and fully handed off to another team member while you're away, then the time is yours. (Emergencies, of course, aren't governed by this policy.) This has worked surprisingly well. Recently a coworker "sipped bevvies" in the Bahamas for a week and a half, and his team happily held their own while he was on vacation. We all recognize that we're working extremely hard, so we all want to step in when others need a break.
-![Liz Daldalian proudly displaying a fish she caught](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-2.jpg)
-1. **We don't let people burn out.** Burn out can be a huge you-know-what. It comes on quick, often sneaking in at the tail end of an intense work effort where life lost out one too many times. It also comes when a striking life event seeps into our work life. It's an energy killer, and a turnover monster out to eat up all our employees. We don't let it eat us. After our first burn out event caused one of our best developers to leave, we created a company policy called the Get Out of Burn Out Free Card. When played, it gives the team member two weeks of vacation starting immediately, no questions asked. It's up to the rest of the team to pick up the slack, and find creative solutions in the team member's absence. It's not a card that gets played often, but it's been played a few times since and we've saved valuable team members from throwing in the towel. Even if the card never gets played, it's reassuring to know other members of the team have our backs in times of need.
-1. **We don't wear business attire.** We work from home, which means we wear the attire we'd normally wear at home. I'm known for wearing pajamas, often brightly colored ones, even during business calls. At the very least, professionalism only matters to the eye of the webcam, and anything out of frame is totally fair game. And heck, we're working hard, so we want to be comfortable.
-![Truffle team meeting featuring funny hats and coats](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-3.jpg)
-1. **We don't stay remote.** Though video calls and Slack messages are our main source of communication, we know nothing builds a relationship better than real human connection. That's why we plan full company retreats three to four times a year, to exciting places that help us all become closer. Our most recent retreat took us to the snowy mountains of Breckinridge, CO. Yes, it was super cold outside and the air was hard to breathe, but it was a new experience for all of us and we came out with some interesting stories to tell. My most memorable moment was when I commandeered a sled and careened right off the side of a hill. Lucky for me it was a false slope and I had no injuries, though my team certainly got a good laugh.
-![Truffle team in Breckenridge](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-4.jpg)
-![Truffle team at TruffleCon 2018](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-5.jpg)
-1. **We don't try to be fully flat.** We love the egalitarian nature of flat organizations, but we also love the efficiency of explicit hierarchy. In our experience flat organizations push hierarchy under the surface, turning decision-making into a confusing game of personal politics and popularity contests. Instead, we take a hybrid approach. We accept that hierarchy exists in our organization, but we try to make it as flat as possible. We push decisions as far down in the hierarchy as they can go, so each team member feels empowered to do the best work possible, and we clearly define the decisions that each role can make. As the CEO of Truffle, I get to make decisions on money and resources, but I'm also the founder, which means I once touched every line of code. That's now Nick D'Andrea's job, our head of engineering, and the jobs of the engineers leading each of our individual engineering projects.
-![Tim Coulter photoshopped as Steve Jobs](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-6.jpg)
-1. **We don't leave people hanging.** Having a light hierarchy gives us the ability to appoint leads. Leads are sometimes a vehicle for accountability, like managers in traditional organizations, but most of the time they're there to serve the members of our team. Every team member gets a lead, and gets a weekly one-on-one that they can use any way they like. Often these one-on-ones are used as a regular place to vent: they help us catch issues early and provide team members a useful outlet so small issues don't turn into something bigger. Leads go to bat for their team members when the team member doesn't feel comfortable raising an issue themselves.
-1. **We don’t give in to perfect.** At least, not initially. In our organization, perfect is the enemy of the good. Had I not been writing this on Independence Day, I may have shot for ten items to round out the list instead of nine. Similarly, it’s the same reason we release a new version of Truffle weekly: We like to bring value to users as quickly as possible, and then strive towards perfection iteratively over time. This idea governs all the work that we do, from software to sales to even our VC pitch decks, because we realize the feedback we get from users far outweighs our initial ideas at perfection. If you have thoughts on how we can better improve our blog or this blog post, please send me an email at tim@trufflesuite.com.
-1. **See #9.**
-
-Working at Truffle has been an amazing journey. It's incredibly humbling to see a project I started from necessity turn into a company run by the heart and soul of a close, tight-knit group of professionals. Truffle would be nothing without this team, and without Truffle I'd likely not be excited to go to work every morning (I commute downstairs in my pajamas, but still). Thank you, Truffle team, for making this company awesome.
-
-![Truffle team members preparing for TruffleCon 2019](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-7.jpg)
-
diff --git a/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md b/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
deleted file mode 100644
index d1463276d..000000000
--- a/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: 2020 is Finally Over - A Year End Wrapup
-hide:
-  - navigation
----
-
-![Truffle End of Year Wrapup Banner](/img/blog/2020-is-finally-over-a-year-end-wrapup/blog-header.png)
-
-2020 has been a trying time for us all: COVID-19 is still ravaging the world, the United States mired through one of our most contentious elections yet; basically, it’s been a rough year.
-
-It’s not all bad though! Let’s take a look back at some positive things that came out of 2020, along with a little of what to look forward to in 2021.
-
-## A Look Back
-
-### ConsenSys Fold-in
-
-This year was a busy one for Truffle, but the biggest news squeaked in just in time for the end of the year: Truffle is now a part of ConsenSys! We’re excited to collaborate with Infura, MythX, MetaMask, and more!
-
-### Teams Enhancements
-
-It was also a big year for Truffle Teams. We’ve added new features and enhanced existing ones to complete the core workflow Truffle Teams offers (I summarize this in our final Dapp Lifecycle webinar episode here). Big highlights include the release of:
-
-* **Dashboard** ([Blog](/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard) | [Docs](/docs/teams/dashboard/dashboard-overview)): More incoming data begets a greater need to gain insights and properly segment that data to prevent overload. Truffle Teams new dashboard provides an overview of your application, along with ways to drill down and get further context on more narrow slices.
-* **Debugger** ([Blog](/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger) | [Docs](/docs/teams/debugger/debugger-overview)): This is a huge workflow enhancement--allowing us to debug transactions in the places we're already viewing--via the deployment details screen or while monitoring individual contracts.
-* **Early Access** ([Blog](/blog/try-new-features-first-with-truffle-teams-early-access)): Truffle Teams is constantly evolving. Between adding new features, polishing, and refining the app there's so much we'd love to share with the world in a faster way. Wouldn't it be nice to take those new enhancements and features for a test drive? Now you can with early access!
-* **Deployment and Monitoring Improvements** ([Blog](/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager) | [Docs](/docs/teams/deployments/deployments-overview)): We’ve added a table view and a deployment details page. We're also offering more insight into each deployment, by providing the cost and console output.
-
-Before the end of this year, we’ll be releasing the Contract Manager to Early Access, completing the workflow and allowing teams to build, deploy, monitor, and debug conveniently in one place.
-
-### Truffle’s Unstoppable Release Schedule
-
-Going on 2 years now, Truffle has released on a weekly basis. We’re so proud of our team for their hard work and commitment to improving the lives of other developers. We don’t have any plans to stop this cadence--full steam ahead for the Truffle train!
-
-### Debugger and Test Enhancements
-
-2020 saw great improvements to Truffle, including debugging verified contracts with `truffle debug --fetch-external` ([Blog](/blog/debugging-verified-external-contracts-with-truffle-debugger)), support for stacktraces in tests with `truffle test --stacktrace` ([Blog](/blog/stack-tracing-with-truffle-test)), and even freshly-added support for stepping through Vyper contracts!
-
-### Forking in Ganache – much improved!
-
-Since the summer of 2020 saw DeFi reach a whole new level of usage, more and more people have been looking to test their code against live smart contracts on-chain. Ganache has always had its `--fork` option, but thanks to members of the community, we’ve fixed more than half a dozen critical bugs that inhibited certain use cases. Forking is more reliable than ever!
-
-### Collaborations
-
-2020 was a year of partnerships for Truffle, seeing us make good on the vision to become a multi-blockchain toolset.
-
-* **Tezos** ([Blog](/blog/branching-out-announcing-tezos-support-in-truffle) | [Docs](/docs/tezos/truffle/quickstart)): Tezos is supported in Truffle! Many of the commands you’re used to are still here: compile, deploy, test, and console!
-* **Corda** ([Blog](/blog/branching-out-phase-2-of-corda-flavored-ganache) | [Docs](/docs/ganache/corda/working-with-corda)): Ganache UI supports creating Corda networks! Easily create and introspect into a local Corada development network with a familiar UI.
-* **Filecoin** ([Blog](/blog/announcing-collaboration-with-filecoin)): Truffle Preserve allows you to easily preserve files on IPFS and/or Filecoin.
-
-## A Look Forward
-
-### Continued Maturation of Truffle Teams
-
-Truffle Teams will continue to be enhanced throughout 2021, with useful additions such as:
-
-* **Monitoring enhancements**: receive alerts when we observe contract anomalies, such as a sudden spike in failed transactions or a drop in balance. Set up your own custom triggers for things like an event firing or a certain address interacting with your contracts.
-* **Debugging public transactions**: The debugger only works for sandboxes currently, but we want to bring it to feature parity with the CLI debugger by also supporting public networks.
-* **Custom Network Support**: Deploy via your own infrastructure by supplying the RPC URL. Put your DappNode to good use!
-* **Continuous (Automated) Deployment**: You can already deploy manually via Truffle Team’s deployment wizard, but there may be times you know you’ll be continuously deploying your changes. For example iterating on a new feature in a sandbox.
-* **Better Dashboard**: The dashboard today provides a good overview of your deployment, but we’re going to expand it to provide better drill down functionality and greater context.
-
-### Advanced Analysis
-
-Truffle’s been around for over 5 years now. In that time, we’ve been thinking about how smart contract systems grow and change over time. Be on the lookout for tools to better examine your contract’s deployment history, track contracts across forks, and more!
-
-### Ganache Rewrite
-
-Ganache is getting a tune-up! This means faster execution of your test suites--**4x faster** in the case of SushiSwap’s test suite. Also lookout for ways to test pending transactions, implementation of EIP-1193, the ability to set the account nonce (`evm_setAccountNonce`), and support for running Ganache in the browser. We’ll also begin publishing auto-generated API documentation so you always have a reference close at hand.
-
-### The Return of the Frontend
-
-2020 didn’t see much movement in our set of frontend libraries, [Drizzle](https://github.com/trufflesuite/drizzle). In 2021 we’ll be giving some love to the frontend in the form of easier state management, more granular tooling, and more.
-
-### More Collaborations
-
-As mentioned above, now that we’re a part of ConsenSys Software Inc, Truffle's going to have many opportunities to collaborate with other groups. We’d love to hear what this sparks in you! Check out our Slack group below and let us know your thoughts. Here are some links to CSI’s groups so you know what they’re about:
-
-* [Infura](https://infura.io/)
-* [MythX](https://mythx.io/)
-* [ConsenSys Diligence](https://consensys.net/diligence/)
-* [MetaMask](https://metamask.io/)
-* [CodeFi](https://codefi.consensys.net/)
-* [ConsenSys Quorum](https://consensys.net/quorum/)
-
-## Catch us on Slack
-
-We want Truffle the best developer tool suite in the blockchain space for new and seasoned devs alike. Let us know what you think about our plans, or if you/your team have other needs we haven't met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Product Lead & The Whole Team at Truffle_
diff --git a/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md b/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
deleted file mode 100644
index d0fc6ab0f..000000000
--- a/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: 3 Ways Enterprises Are Addressing Blockchain Privacy Concerns
-hide:
-  - navigation
----
-
-[Blockchain has been touted as the great connector to integrate businesses under consortium networks](https://www.forbes.com/sites/andrewarnold/2019/02/21/why-2019-may-become-the-year-of-enterprise-blockchain/#66c9e516427e). It’s ability to verify data using smart contracts and provide transparency across network participants through immutable shared data has people talking about a technical revolution. However, this benefit has been a double-edged sword because the enterprise world is skeptical about sharing sensitive data on a ledger where the information cannot be deleted. The good news is, this year has seen numerous announcements of single and multi-party blockchain pilots by the Fortune 500 such as… [Starbucks](https://news.microsoft.com/transform/starbucks-turns-to-technology-to-brew-up-a-more-personal-connection-with-its-customers/) and [MetLife](https://www.forbes.com/sites/stevenehrlich/2019/06/19/metlife-plans-to-disrupt-2-7-trillion-life-insurance-industry-using-ethereum-blockchain/#3e9a87277022). Data privacy issues haven’t stopped them and the enterprise blockchain world has taken these steps to shift their thinking.
-
-## 1. Store references to data on the blockchain
-The simplest way to circumvent this data privacy issue is to not put the data on the chain. A popular approach is to share anonymous IDs on the blockchain and use that to get data from another system. For example, [MediLedger](https://www.mediledger.com/) is a supply chain pilot in the heavily regulated pharmaceutical industry that uses a blockchain to trace a drug’s exchange of hands and then uses another private peer-to-peer application to transfer details about the medication. What is passed around on the chain is just an anonymous identifier to the medication. This keeps transactions light, allows enterprises to regulate data access, and uses proven methods to secure sensitive data. MediLedger actually takes this a step further and anonymizes the transaction details with zero knowledge proofs — which I’ll cover later.
-
-## 2. Use blockchains to verify instead of share
-Blockchain’s real power is in its ability to verify data. Instead of putting actual information on the chain, a solution could combine unique elements of data and share a hash of it on the blockchain. Hashing is a cryptographic method that generates a random, unique value from a fed input. In this scenario, the resulting hash itself doesn’t reveal any information, but it can verify an on-hand document by checking if it generates the same hash when fed into the function. The data inputs could also be selected in a way that no critical information is sampled to create the hash so that compliance regulations can be withheld. Businesses have reliable methods to exchange data, but the verification is long and expensive. By using blockchain as a verifier and not the store of the data, we can ease the pain point and maintain a higher level of privacy than open sharing.
-
-## 3. Anonymize transactions with zero knowledge proofs
-Building off the two previous trends, blockchain pilots have taken an extra step in securing data and replaced hashed transaction details with zero knowledge proofs (ZKP). [ZKPs allow for verification of a transaction without exposing transaction details](https://hackernoon.com/wtf-is-zero-knowledge-proof-be5b49735f27). Now two businesses can communicate on a public network and be completely anonymous. This is because what is placed on the chain is a proof that is cryptographically verified by the receiver, not the data that goes into the transaction. This shift in data validation methods addresses data privacy concerns and supports industry consortiums.
-
-## Blockchain is just one piece of the puzzle
-
-Finally, with all the hype on blockchain’s potential in the last years, we have to remember that this is just another tool in the technology box when solving a problem. Enterprises have gotten smarter in finding ways to use blockchain to solve unique problems that are more expensive or less reliable with other technologies. What we have seen is that distributed ledgers can’t do everything, but when paired with multiple other technologies that help fill gaps, the solution as a whole is optimized. A better perspective is to not think of future solutions as blockchain applications, but rather applications that leverage the unique advantages of blockchain.
-
-## About West Monroe Partners
-
-West Monroe is a national business and technology consulting firm that partners with dynamic organizations to reimagine, build, and operate their businesses at peak performance. Our team of more than 1,400 professionals across nine offices is comprised of an uncommon blend of business consultants and deep technologists. I am one of those consultants and I am one of the leaders of our blockchain center of excellence. I’ll be presenting on Sunday morning (8/4) about one of our blockchain projects that looks to [incentivize electric vehicle owners to charge with cleaner energy](https://trufflecon2019.sched.com/event/RHIR/driving-renewable-energy-usage-with-blockchain-and-electric-vehicles). Check us out at our [website](https://www.westmonroepartners.com/) and read more about our [blockchain perspectives](https://blog.westmonroepartners.com/?s=blockchain) on our blog!
-
-Danny Pan is a consultant with West Monroe Partner’s Seattle Technology Practice. He focuses on providing value in adopting blockchain, distributed technologies, and robust SDLC practices. Contact Danny at [dpan@wmp.com](mailto:dpan@wmp.com)
diff --git a/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md b/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
deleted file mode 100644
index df6e65cb9..000000000
--- a/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 5 Trends Impacting the Blockchain Developer Experience
-hide:
-  - navigation
----
-
-In this article we explore 5 trends impacting the developer-experience (or DX) when it comes to building blockchain-based solutions. Specifically, applications and services that leverage a blockchain or distributed ledger or as part of their overall architecture.
-
-This is, of course, is by no means a definitive list. As with everything in the industry, change is happening fast and as such, this is more of a selection of trends that are on the team’s radar. If there’s anything we’ve missed or should know about, we’d love to hear from you (or speak in person at [TruffleCon 2019](/trufflecon2019)).
-
-## #1 Development tooling release velocity is on fire
-
-Obviously we’re a little biased, but in this case, we’re talking about tools and utilities that are not [chocolate-themed](/truffle). It’s literally every day we collectively come across something new that makes our lives as developers (or users, auditors, admins, etc) easier.
-
-This is a big deal for the long-term success of the wider ecosystem because happy and productive developers obviously strongly correlates with increased experimentation, the volume of shipped products and services, and expedites the process of on-boarding new people (developers or otherwise) into the blockchain space.
-
-At Truffle, we’re also pushing harder than ever to make the DX as sweet as possible. Like, raspberry truffle sweet. This includes new features and enhancements to the existing suite (such as integration with [Hyperledger Fabric's chaincode EVM](https://github.com/trufflesuite/truffle/releases/tag/v5.0.27)), as well as the upcoming [Truffle DB](/blog/introducing-truffle-db-part-1) and [Truffle Teams](/docs/teams/overview).
-
-## #2 Managed Blockchain Services are here
-
-Managed Blockchain Services (MBS) are evolving rapidly. In the first half of 2019 alone we’ve seen the launch of new services from heavyweights such as [Microsoft](https://azure.microsoft.com/en-us/services/blockchain-service/) and [Amazon](https://aws.amazon.com/managed-blockchain/), and players such as [Kaleido](https://kaleido.io/) evolving their stack with dizzying speed.
-
-These services, of course, do all the heavy lifting when it comes to spinning up private or consortium networks, something that was historically cumbersome from a DevOps perspective. Excitingly, the maturation of these services is coinciding with an increased understanding of the use-cases for permissioned ledgers and accordingly, we’re seeing major projects and initiatives begin to roll out.
-
-The managed nature of these services has allowed the teams behind them to really focus on streamlining the developer experience Which leads us to the next trend...
-
-## #3 We’re seeing glimpses of the DX of the future
-
-In the words of William Gibson: *“The future is already here - it's just not very evenly distributed”* and with the blockchain DX it’s no different.
-
-Our favorite example of a DX from the future is [Kaleido’s Marketplace](https://marketplace.kaleido.io/) where within a few clicks you can add a [token swap service](https://marketplace.kaleido.io/service/token-swap), store data on [IPFS](https://marketplace.kaleido.io/service/ipfs-file-store), or [pin a state proof](https://marketplace.kaleido.io/service/public-ethereum-tether/) to a public network.
-
-![Example A](/img/blog/5-trends-impacting-the-blockchain-developer-experience/example-1a.png)
-
-It’s almost too easy. Seriously though, this evolution of developer experiences paves the way for how “delightful” things might one-day be when building equivalent services for public networks.
-
-## #4 Major corporations are pushing some seriously awesome open-source software
-
-While veteran projects like [OpenZeppelin](https://openzeppelin.org/) continue to blossom, one interesting trend we’ve seen is larger organizations’ increasing embrace of open-source with the recent release of some exciting new projects.
-
-Some great examples of this include Ernst & Young’s [Nightfall](https://github.com/EYBlockchain/nightfall), Samsung’s [Blockchain SDK](https://developer.samsung.com/blockchain), Microsoft’s [Confidential Consortium Framework](https://github.com/microsoft/CCF), and the continued evolution of the JPMorgan-backed [Quorum](https://github.com/jpmorganchase/quorum). We’re equally pumped by the launch of Cloudflare’s [Ethereum gateway](https://blog.cloudflare.com/cloudflare-ethereum-gateway/) too!
-
-It’s exciting to see companies of all shapes and sizes embracing the paradigm in ways that we can all benefit.
-
-## #5 Industries are becoming increasingly programmable, led by DeFi
-
-While companies like [Stripe](https://stripe.com/) have turned programming against “centralized” finance into an art form, they are inherently bound by the rules and regulations imposed by the industry itself. Decentralized Finance (or DeFi) on the other hand has no such intrinsic limitations. Want to open a Collateralized Debt Position? MakerDAO has a [JavaScript library](https://makerdao.com/documentation/#dai-js) for that. DeFi is only limited by the imagination (and programming ability) of individual developers.
-
-We’re rapidly seeing the decentralized equivalent of swaths of traditional financial services emerge, all of which are open and programmable in ways that the existing industry can only dream of.
-
-And of course it goes far beyond finance. Everything from supply chains to in-game assets are steadily turning Ethereum into the “[global platform for every asset](https://twitter.com/MuteDialog/status/1149047398532075526)”.
-
-**It’s never been a better time to building on Ethereum. From tooling to infrastructure to a world-class open-source ecosystem, the developer-experience continues to blossom.**
diff --git a/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md b/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
deleted file mode 100644
index d70676f22..000000000
--- a/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: A Sweet Upgradeable Contract Experience with OpenZeppelin and Truffle
-hide:
-  - navigation
----
-
-![Truffle + OpenZeppelin Banner](/img/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/blog-header.png)
-
-Immutability is a cornerstone of blockchain technology. This is great for many reasons, but presents a problem when it’s time to upgrade our smart contracts. There are a few different upgrade patterns, but one that’s proven to be robust is the proxy pattern. This pattern has, until now, involved some additional overhead for development teams. Thanks to OpenZeppelin though, you can now deploy upgradeable contract systems with ease using the familiar Truffle tool suite!
-
-## The Proxy Pattern
-
-At a high level, the proxy upgrade pattern involves deploying a proxy contract that delegates function calls to your logic and storage contracts. The proxy is storing addresses of the logic contracts and these addresses can be changed. This allows you to deploy a new version of the logic contract and point the proxy to that new version.
-
-<figure>
-  <img class="mb-4 w-100" src="/img/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/proxy-contract.png" alt="Proxy contract upgrade diagram">
-  <figcaption class="text-center font-italic">The proxy contract can point to any number of different logic contracts.</figcaption>
-</figure>
-
-There are many concerns around this pattern you’ll need to keep in mind, such as making sure your old contracts cannot be used maliciously. For more information on proxy patterns, [check out OpenZeppelin’s proxy pattern guide](https://docs.openzeppelin.com/upgrades/2.8/proxies).
-
-## Using the Plugin
-
-First, install the package:
-
-```bash
-npm install --save-dev @openzeppelin/truffle-upgrades
-```
-
-<p class="alert alert-info m-t-2">
-<i class="fas fa-info-circle"></i> <strong>Note</strong>: This package requires Truffle version 5.1.35 or greater.
-</p>
-
-Then, in your migration script, use the new deployProxy and upgradeProxy functions:
-
-```javascript
-const { deployProxy, upgradeProxy } = require('@openzeppelin/truffle-upgrades');
-
-const Box = artifacts.require('Box');
-const BoxV2 = artifacts.require('BoxV2');
-
-module.exports = async function (deployer) {
-  const instance = await deployProxy(Box, [42], { deployer });
-  const upgraded = await upgradeProxy(instance.address, BoxV2, { deployer });
-}
-```
-
-Now your contract systems can be much more flexible while still leveraging all of the benefits of a blockchain network. For more information on the truffle-upgrades plugin, check out [OpenZeppelin’s Truffle documentation](https://github.com/OpenZeppelin/openzeppelin-upgrades/blob/master/packages/plugin-truffle/README.md).
-
-We’re very excited about this plugin and would love to hear more about how you’re using it and how we can make the experience even better! Please let us know how you feel in [the Truffler Slack community](https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA) or on [OpenZeppelin’s forum](https://forum.openzeppelin.com/)!
\ No newline at end of file
diff --git a/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md b/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
deleted file mode 100644
index 3bcd89b70..000000000
--- a/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
-title: An Easier Way to Deploy Your Smart Contracts
-hide:
-  - navigation
----
-
-**TL;DR** - Deploying your smart contracts shouldn't be difficult, and the process should be flexible. I give a sneak peek at the next feature we're building: an **easy to use interface to deploy your Truffle projects with [Truffle Teams](/docs/teams/overview)**! It's going to be awesome, and **you can be the first to use it**! I'll be giving a **hands-on workshop from 9AM-12PM on Friday, August 2nd, at [TruffleCon 2019](/trufflecon2019)** that will walk you through through the entire Truffle Teams lifecycle, including the **never-before-used Deployments interface**! See you there!
-
----
-
-So! You've finished implementing your dApp, you've tested it on [Ganache](/ganache), and you're ready to push it to a testnet or Mainnet! Congratula—oh wait.
-
-![One Does Not Simply Deploy to Mainnet](/img/blog/an-easier-way-to-deploy-your-smart-contracts/got-deploy-mainnet.jpg)
-
-It's not that easy.
-
-There are a handful of solutions, and none have _really_ made it painlessly easy. Even our own `truffle migrate` (aka `truffle deploy`) has left much to be desired.
-
-Well it's about to get a whole lot easier with Truffle Teams. [Skip to the good stuff.](#truffle-teams)
-
-## The Not-So-Easy Ways to Deploy Your Smart Contracts
-
-So what's wrong with what's already made? Why make _yet another_ tool? I hear you. Let's take a look at what **is** available, and if you're still meh, I'd love to talk to you at [TruffleCon](/trufflecon2019)!
-
-<h3 class="link-markdown">
-  <a href="#remix" name="remix">
-    <i class="fas fa-link">
-    </i>
-  </a>
-  <div>
-    <span>Remix</span>
-    <img style="margin: 0 !important; display: inline-block !important;" src="/img/blog/an-easier-way-to-deploy-your-smart-contracts/remix-logo.svg"  width="40px" title="Remix" alt="Remix">
-  </div>
-</h3>
-
-![Remix IDE](/img/blog/an-easier-way-to-deploy-your-smart-contracts/remix.png)
-
-Oh [Remix](https://remix.ethereum.org), we all have fond memories of you. And many people still use Remix for all sorts of use cases! Remix gives you an in-browser Ethereum IDE, letting you develop, compile, test, debug, and deploy smart contracts for Ethereum. And it's probably the least amount of work needed to throw a single smart contract onto a testnet or Mainnet (i.e. when deploying a single `.sol` file).
-
-Remix, as of version `0.7.7`, gives you a simple `Deploy` button. This will send a transaction to the `web3` provider of your choice (many use [MetaMask](https://metamask.io)), and you're off to the races!
-
-Great, right?
-
-Well, Remix gets harder to use as you add more contracts, import 3rd party contracts, work as a whole team, etc. It's definitely flexible and able to handle these use cases (though not without legwork and configuration), but it's not my personal preference for developing large, complex dApps.
-
-<h3 class="link-markdown">
-  <a href="#truffle-cli" name="truffle-cli">
-    <i class="fas fa-link">
-    </i>
-  </a>
-  <div>
-    <span>Truffle CLI</span>
-    <img style="margin: 0 !important; display: inline-block !important;" src="/img/truffle-logo-light.svg"  width="50px" title="Truffle" alt="Truffle">
-  </div>
-</h3>
-
-Enter [Truffle](/truffle).
-
-It's a fantastic framework (not to toot our own horns) that lets you develop your dApp in a flexible and extensible way. It provides structure to keep you sane in this chaotic world of Web 3.0.
-
-It even gives you a mechanism to define what deploying (aka: "migrating") means for your application. You can specify what contracts get deployed in which order with whatever arguments you require. For instance, your smart contracts may depend on the deployment of a past contract, which you can easily code in migration scripts.
-
-**And it's as easy as running `truffle migrate`!**
-
-...and if you were deploying directly to [Ganache](/ganache), that'd be entirely true.
-
-![Running `truffle migrate`](/img/blog/an-easier-way-to-deploy-your-smart-contracts/truffle.png)
-
-But that's not the case when we start talking about testnets or Mainnet.
-
-The **easiest** way to deploy to an external network is by using [Truffle's HD Wallet Provider](/docs/truffle/reference/configuration#providers). However, this requires you to somehow get your mnemonic or private key into the `truffle-config.js` config file, **without committing it to your provider source control provider (PLEASE don't do this - you'll get your Ether stolen).** To use an account you created with MetaMask, you'd need to export your private key from MetaMask (or your mnemonic, if you're feeling lucky 😱) and create the boilerplate code to read in the key from an environment variable (to prevent committing it to your repository and sharing it publicly).
-
-In all truthfulness, this isn't too bad, but it's also a bit too much config for me. I'd much rather use MetaMask directly to authenticate transactions during deployments.
-
-### Custom Management Web Interface
-
-Some devs will create a small front-end web interface which uses [web3.js](https://github.com/ethereum/web3.js) to deploy their smart contracts. I have done this personally in my [Game of Thrones Death Pool](https://seesemichaelj.github.io/game-of-thrones-death-pool) project, and I chalked it up to "well I can put this on a website and others can deploy their own versions."
-
-![Custom Management Web Interface for GoT Death Pool](/img/blog/an-easier-way-to-deploy-your-smart-contracts/got-death-pool.png)
-
-Sometimes this is necessary, but it's more work if it's not absolutely needed for your application.
-
-## My Version of an Ideal Deployment Interface
-
-In an ideal world, I'd like these features in a deployment interface:
-
-<ul>
-  <li>Lets me use MetaMask directly for signing transactions
-    <ul>
-      <li style="margin-bottom: 0 !important;">Remix ✔️ | Truffle CLI ❌ | Custom Webapp ✔️</li>
-      <li>A bonus win here is support for Ledger and Trezor wallets!</li>
-    </ul>
-  </li>
-  <li>I can use a framework/toolset/etc. that lets me build complex apps and supports complex deployment processes
-    <ul>
-      <li>Remix ❌ | Truffle CLI ✔️ | Custom Webapp ✔️</li>
-    </ul>
-  </li>
-  <li>I don't need to do a lot of work to go from finishing development to deploying
-    <ul>
-      <li>Remix ✔️ | Truffle CLI ✔️ | Custom Webapp ❌</li>
-    </ul>
-  </li>
-</ul>
-
-<h3 class="link-markdown">
-  <a href="#truffle-teams" name="truffle-teams">
-    <i class="fas fa-link">
-    </i>
-  </a>
-  <div>
-    <span>Introducing: Truffle Teams Deployments</span>
-    <img style="margin: 0 !important; display: inline-block !important;" src="/img/tt-logomark.svg"  width="50px" title="Truffle Teams" alt="Truffle Teams">
-  </div>
-</h3>
-
-If you haven't heard about our latest tool, [Truffle Teams](/docs/teams/overview), you really should check it out. Truffle Teams gives you zero-config Continuous Integration (CI) for your Truffle projects, and it also lets you monitor what's happening with your deployed contracts. Truffle Teams meshes the full Truffle Suite into a cohesive application that enables better collaboration within development teams (even teams of 1!).
-
-![Truffle Teams Builds](/img/blog/an-easier-way-to-deploy-your-smart-contracts/teams-build.png)
-
-The next big feature we're working on is Deployments. We already compile your contracts from your Truffle project for you when you make a commit to GitHub; why can't we migrate/deploy them as well? Further, Truffle Teams is a web application, allowing for easy integration with [MetaMask](https://metamask.io).
-
-We're looking at this from a [DevOps](https://en.wikipedia.org/wiki/DevOps) perspective, and we're trying to create an extensible system that will support projects and teams of **any size**.
-
-### Connect Your GitHub Repository to Truffle Teams
-
-To get started with Truffle Teams, you must first connect your GitHub repository. This is a simple step, and we have instructions on how to do this [here](/docs/teams/quickstart).
-
-### Setup Your Migrations Scripts
-
-If you haven't built a Truffle project, you should really give it a try; the [Pet Shop Tutorial](/tutorial) is a great place to start as it gives a good survey of the different facets of Truffle, including the `migration` scripts. These scripts let you define the behavior of deploying your smart contracts using a language you're already familiar with. In the tutorial, you deploy a single contract, but it has the flexibility to do so much more (i.e. you can deploy one contract, get its address, and use that in the constructor when deploying another contract).
-
-Setting up these scripts is part of the development lifecycle of creating a Truffle project, so I won't cover that here. But that's great! You should already be done with this step!!
-
-### Commit to GitHub
-
-Welp. That was easy. 😅
-
-### Monitor the Status of Your Build
-
-Head over to https://my.truffleteams.com and click on the `BUILDS` tab if you're not there already. You can see a build has been queued or has started to process. You can click on the repository name in the card to see more details. You can also get to this page by clicking on the yellow dot in GitHub next to your commit and pressing `Details`.
-
-![Teams Builds More Details](/img/docs/teams/starting-builds-comp.png)
-
-### All Your Tests Pass, Let's Deploy! (but only to a testnet just to be sure)
-
-> NOTE: This is just a sneak peek of features to come! You won't be able to follow along (yet, but [stay tuned](https://share.hsforms.com/1OaTglVhGTdWk7spR6nE_AA34pbp)!).
-
-Great! Your builds are passing, and you're ready to deploy to a testnet (i.e. Ropsten) to see if everything works.
-
-Now head over to the `DEPLOYMENTS` tab and select your repository.
-
-You'll now see a screen that shows a list of builds for your commits on the left.
-
-![Deployments Empty](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployments-empty.png)
-
-Deploying a build is as simple as hovering over the commit, pressing a button, and selecting which network you'd like to deploy to.
-
-![Deployment Wizard Select](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployment-wizard-select.png)
-
-Truffle Teams will then start the migration/deployment process. Each transaction is sent to the web application and MetaMask will prompt you to confirm transactions. By leveraging MetaMask, we can give you **[Ledger](https://www.ledger.com) and [Trezor](https://trezor.io) hardware wallet support too! 🔒**
-
-![MetaMask Transaction](/img/blog/an-easier-way-to-deploy-your-smart-contracts/metamask-tx.png)
-
-### Happy With a Released Version? Promote it to Production (aka deploy to Mainnet)
-
-But we're not done yet! You've finished your testing on Ropsten, and you're now ready to deploy to Mainnet. With the upcoming version of Teams, you can select that deployment and promote it to production (aka Mainnet) with just a couple of clicks.
-
-![Deployments Complete](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployments-complete.png)
-
-## And that's it! Pretty easy if you ask me.
-
-![Fry, Easy or Too Easy](/img/blog/an-easier-way-to-deploy-your-smart-contracts/fry-easy.jpg)
-
-## 🎉 Don't Believe Me? Be The First to Try it at My TruffleCon 2019 Workshop! 🎉
-
-I really hope you're going to TruffleCon; it's going to be awesome. Even more so because you can **be the first to try Truffle Teams Deployments in my workshop!** In my `Push It! Push It Real Good: Truffle Teams Intro & Deployments` (9AM-12PM on Friday, Aug, 2nd) workshop, we'll cover this entire lifecycle: hooking up your repository, getting your first build to pass, deploying to Ropsten, and finally monitoring transactions made against your contracts (we didn't talk about this here; check out the [docs](/docs/teams/deployments/contract-monitoring) for more details on contract monitoring).
-
-Hopefully there will be time for me to answer any questions you have, and maybe even help get your own Truffle project hooked up with Truffle Teams! If not, I will be available during the office hours at 5PM on Friday! I'm also always happy to chat anytime throughout the conference!
diff --git a/src/blog/announcing-collaboration-with-filecoin/index.md b/src/blog/announcing-collaboration-with-filecoin/index.md
deleted file mode 100644
index a9eb30004..000000000
--- a/src/blog/announcing-collaboration-with-filecoin/index.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Announcing Collaboration with Filecoin - Big Integrations Coming
-hide:
-  - navigation
----
-
-![Filecoin Collab Banner](/img/blog/announcing-collaboration-with-filecoin/blog-header.png)
-
-Today we're announcing an exciting new collaboration, aimed at helping developers across the globe create and deploy fully decentralized applications. We've teamed up with Filecoin to add support for the Filecoin network into our world class suite of tools. In typical Truffle fashion, we'll beef up the Truffle command line tool to give you everything you need to deploy directly to Filecoin; and then we'll add new features to Ganache so that you can easily simulate the Filecoin network during development and testing.
-
-### The Decentralized Ideal
-
-Since Truffle's inception, we've long wanted to integrate with decentralized storage networks so we can help developers build fully decentralized applications. For the most part, this has been a waiting game: Decentralized storage networks have been in heavy development, and it's clear these technologies needed time to mature. With Filecoin's month-long hackathon starting [this week](https://hackfs.com/), and the launch of their main network ("mainnet") coming later this summer, we thought now was the right time to give developers access to this amazing new technology.
-
-We're excited about Filecoin because it allows developers to build applications with 100% uptime. For instance, if an application uses only fully-dentralized technologies like Etheruem and Filecoin, the built-in incentivizations of those technologies will ensure miners around the world will keep that application running. With anti-censorship properties, as well as support for large amounts of data, Filecoin support could bring in a new age of Web3. 
-
-There's a lot we have to do before we reach this ideal, but I'd love to tell you about our roadmap for the next six months. 
-
-### Truffle Preserve: Save Your App Data (available today!)
-
-![Truffle Preserve](/img/blog/announcing-collaboration-with-filecoin/truffle-preserve.gif)
-
-In thinking about our support for Filecoin, the idea of *preservation* came quickly to mind. We envisioned that preserving application data like Javascript frontends and static assets would be a normal part of the deployment process. So we ran with that idea and added a new command to the Truffle command line tool: `truffle preserve`.
-
-Like preserving fruit, Truffle follows a "recipe" to preserve your files. In the gif above, Truffle is using the `filecoin` recipe, which will ship standard with our new version of Truffle. 
-
-**You can use `truffle preserve` today!** You'll need to download a special release we created so you can start testing, shown below. Note that our Filecoin integration is very alpha, but we wanted to support all the amazing devs hacking on Filecoin this month during [HackFS](https://hackfs.com/). 
-
-```
-$ npm install -g truffle@preserves
-```
-
-To use `truffle preserve`, simply specify the files you want to preserve on the command line, and choose between the `--filecoin` or `--ipfs` recipes. The `filecoin` recipe uses the `ipfs` recipe under the hood. You can choose only the `ipfs` recipe if you have a different set up!  
-
-```javascript
-// Preserve to Filecoin:
-$ truffle preserve ./path/to/directory --filecoin
-
-// Preserve to IPFS only:
-$ truffle preserve ./path/to/directory --ipfs 
-```
-
-By default, `truffle preserve` comes configured to work with the [Powergate localnet](https://docs.textile.io/powergate/localnet/), though you can change the IPFS and Filecoin connection information by adding the following to your `truffle-config.js` file: 
-
-```javascript 
-  // ...,
-  environments: {
-    development: {
-      "ipfs": {
-        address: "http://localhost:5001"
-      },
-      "filecoin": {
-        address: "ws://localhost:7777"
-      }
-    }
-  },
-```
-
-Note that this configuration adds a new top-level `environments` object. We'll be using this new configuration object as we upgrade to Truffle 6 in the future.
-
-### Filecoin-flavored Ganache: Simulate Filecoin (Summer/Fall/Winter)
-
-Ganache was built as the sister application to Truffle, to speed up development and testing Ethereum applications. Now that we've added support to Truffle, it's only natural we provide the same highly-modular simulator for Filecoin. Over this summer and into Fall, we plan to create a Filecoin simulation library, as part of [`ganache-core`](https://github.com/trufflesuite/ganache-core). Then later on this Fall/Winter, we'll follow that up with support in our graphical version of Ganache, below! 
-
-
-![Filecoin-flavored Ganache](/img/blog/announcing-collaboration-with-filecoin/filecoin-flavored-ganache.png)
-
-### Get involved / Reach out!
-
-We're extremely excited to be working with the Filecoin team and adding support for Filecoin into Truffle's tooling. If you have questions about our Filecoin integration or our plan for the future, <a href="https://trfl.co/become-a-truffler" target="_blank">join our slack community</a> and get your questions answered. Whether you're a new dev or a [HackFS hacker](https://hackfs.com/), we're happy to help. 
diff --git a/src/blog/announcing-full-portable-solidity-debugger/index.md b/src/blog/announcing-full-portable-solidity-debugger/index.md
deleted file mode 100644
index 120316ea9..000000000
--- a/src/blog/announcing-full-portable-solidity-debugger/index.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Announcing our Fully Featured, Portable Solidity Debugger
-hide:
-  - navigation
----
-
-Every one at Truffle is giddy right now. 
-
-----------------
-
-Since Truffle's inception, it's been our mission to build outstanding development tools for the Ethereum community. The analogy we always used was one of history: Ethereum development practices are years behind the rest of the industry, and it's our job to build tools that modernize our craft. Well today, Truffle's come one step closer to that goal. We're happy to announce the release of our fully featured, fully portable Solidity [debugger](https://github.com/trufflesuite/truffle/releases) and [debugging libraries](https://github.com/trufflesuite/truffle/tree/master/packages/debugger).
-
-![Debugger in Action](https://i.imgur.com/7y80aF3.gif)
-
-### What We've Built
-
-If you've followed Truffle development, you're familiar with the `truffle debug` command. This was the first incarnation of a "debugger" built into Truffle, though it wasn't much more than a code tracer. Our new debugger comes with everything you expect :
-
-* Code stepping (over, into, out, next, instruction, etc.)
-* Current code location, including the address of the running contract
-* Breakpoints
-* Watch expressions
-* Variable inspection (stack, memory _and_ storage)
-* Custom expression evaluation using Solidity variables
-
-On top of that, our new debugger is fully portable, built to integrate with any Javascript project or editor, like Visual Studio Code. Lastly, we built it to work with **any Ethereum client**, so you could debug transactions against the main Ethereum network if you so desired. 
-
-### How it Works
-
-To debug your Solidity code, you first need to make a transaction. Ethereum is a world computer with a history of all execution, so we can pull all the information we need from past transactions. After obtaining the transaction hash, simply run the following to kick off your debugging experience:
-
-```shell
-$ truffle debug <tx hash>
-```
-
-This will open up the debugging console which you can use to your heart's content! 
-
-![Debugger user interface](https://i.imgur.com/0NUTSlM.png)
-
-The above user interface gives you access to the debugger features you need to step through your contracts' code, set breakpoints, evaluate expressions and inspect Solidity variables, providing you a better sense of what your code is doing. Under the hood, our debugger is interacting with your Ethereum client to gather all the data necessary to provide this information to you in a suitable manner. For developers reading this, the debugging library stores all this data in Redux, making the data easy to manage and making the library super portable. 
-
-Most of the work done by the debugger results in some type of mapping. The debugger gathers tons of disparate data, like the bytecode of your contracts, abstract representations of your code, instructions run during your transaction, etc., and combines them to produce information useful to the contract developer. Perhaps the debugger's most valuable property is variable inspection: Using all the data gathered, the debugger can determine which variables exist within your contract, which apply to each section of the code, and what their values are at any point in time. It can even show the values of complex data types, like structs with nested arrays. We're still filling out a few data types, but expect those in the next couple weeks.
-
-If you plan on using the `debug` command _today_, we recommend using [Using Truffle Develop and the Console](/docs/truffle/getting-started/using-truffle-develop-and-the-console). Truffle Develop comes with everything you need "baked in" to fully debug your contracts. Ganache and `ganache-cli` will need to be updated, so stay tuned for that in the coming days. 
-
-### Where to Next
-
-The debugger we built unlocks tons of value for all Ethereum developers both new and advanced, but what you're seeing here is the tip of the iceberg of where this technology will go. The interface above is just **one** interface, meant to show off the debugger's capability. As mentioned, the libraries we built are super portable, so they'll end up making their way into all of the following:
-
-* Integrated Development Environments (IDEs) like Visual Studio Code
-* [Ganache](/ganache), including a full debugging UI
-* [Drizzle](/docs/drizzle/quickstart), for automatic variable change detection after a transaction
-* Browser plugins so you can debug transactions on the fly within your application
-* Ethereum provider libraries that let you debug your code anywhere, without a plugin
-
-We encourage the Ethereum community to help build these tools. Our code is open source, and you can find all of it [on Github](https://github.com/trufflesuite/).
-
-### How to Get It
-
-If you already have Truffle installed, simply run the following to get you to the latest version:
-
-```shell
-$ npm uninstall -g truffle
-$ npm install -g truffle
-```
-
-If you're new to Truffle, you can try it out using:
-
-```shell
-$ npm install -g truffle
-```
-
-You may have to use `sudo` with the above commands if you're running Linux.
-
-More information about how to use Truffle can be found in [our documentation](/docs), and feel free to reach out on our [community Gitter channel](https://gitter.im/consensys/truffle), where hundreds of your fellow Trufflers congregate to answer your question.
-
-### A Quick Thank You
-
-I'd like to personally thank the whole Truffle team for this effort, and particularly [Nick D'Andrea](https://github.com/gnidan) for turning some initial research work into a fully portable, fully featured debugger. The engineering under the hood is amazing, [I urge you to take a look](https://github.com/trufflesuite/truffle/tree/master/packages/debugger). I'd also like to thank the community at large: It's a pleasure building the tools that make your lives easier, and your consistent feedback makes the whole endeavor worthwhile.
-
-Thanks,
-<br/>-- Tim 
-
-
-
-
diff --git a/src/blog/axonis-enterprise-use-of-truffle/index.md b/src/blog/axonis-enterprise-use-of-truffle/index.md
deleted file mode 100644
index c6836f688..000000000
--- a/src/blog/axonis-enterprise-use-of-truffle/index.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Axoni's Enterprise Use of Truffle
-hide:
-  - navigation
----
-
-![Truffle + Axoni](/img/blog/axonis-enterprise-use-of-truffle/truffle-axoni.png)
-
-## Axoni Background
-
-At Axoni, our mission is to make shared information more trusted and reliable. We do this through distributed technology that we call "Ethereum-inspired", which has both a broad and a specific meaning. In the broad sense, the core technology plays a role for its users analogous to the public blockchain, presenting a powerful and extensible capacity to side-step undesired intermediaries (yes, these exist for banks too...). In a more precise technical sense, our platform borrows certain concepts from Ethereum (e.g. accounts, contracts, gas...) and, importantly, we make efforts to comply with Ethereum-world interfaces (e.g. evm bytecode, web3 JSON-rpc).
-
-Of course, an up-shot of the last is the ability to take part in all the innovation taking place in the broader Ethereum ecosystem, including client-side libraries that enable a "tastier" application development process. To this end, within the last year we have worked to leverage the Truffle suite and ecosystem to great effect. In fact, as [reported](https://www.forbes.com/sites/michaeldelcastillo/2019/04/29/consensys-spins-off-ethereum-startup-truffle-to-take-blockchain-to-big-business/#1e84a5622e21), it is fair to say that Truffle serves by and large as the main toolset for on-chain application development at Axoni.
-
-## Using Truffle at Axoni
-
-It was a delight for us to find that, given our compliance with the web3 JSON-RPC spec, truffle basically works "out-of-the-box" with no extensive customization required for many very useful stages in the application lifecycle: develop, build, test....
-
-One notable exception: we found the native `truffle migrate` functionality not extensible to our use case. In part, this is due to the fact that our smart contract applications implement something [similar to the proxy pattern](https://blog.zeppelinos.org/the-transparent-proxy-pattern/), which runs counter to the "migration" paradigm. On the other hand, and for reasons beyond the scope of this post, tools such as `zoslib` designed to handle upgradeable smart contract application deployments, generate smart contract implementations incompatible with our use case. At a high level, our smart contract framework is optimized for high-throughput and highly complex Solidity applications which enables the ability to make automatic upgrades based on semantic versioning. [ Note: I plan to speak more about our particular use cases and smart contract topologies at Trufflecon on August 3rd]
-
-In any case, especially due to the often very high levels of complexity entailed by our use cases– combined with the noted [application-level gotcha's of upgrade design patterns in solidity itself](https://blog.trailofbits.com/2018/09/05/contract-upgrade-anti-patterns/)–we are biased towards a simple and opinionated declarative format that application and production engineers can easily understand and (when needed) manipulate.
-
-This raises the question -- why use truffle for this? It seems there are at least three reasons:
-
-1. `truffle-config.js` / `truffle.js` serves as an already existing central source of shared information about various network providers relevant for a particular application developer. It only makes sense to extend this format for use in production-like environments as well.
-1. Truffle code artifacts, a battle-tested standard for smart contracts and solidity code, in particular, provide a common interface for a toolchain. By virtue of using truffle, there is no need to re-create this format. For a non-development deployment, a `contracts_build_directory` parameter is supplied, which results in a pull from a remote artifacts repository.
-1. Obviously `@truffle/contract` itself provides a nice object oriented interface for deploying and performing operations on contracts within this script, thus avoiding any reinventing the wheel within the deployment library itself.
-
-Thus, we ventured to build a package on top of truffle that manages configuration-driven smart contract deployments and upgrades.
-
-## Building a Truffle-Based Deployment Tool
-
-The first question is what the configuration file should look like? We determined the "Straw Man" to be, simply, a two-dimensional list of job types and associated contracts specified for deployment. Starting with this, we found another concept we needed to add ("custom-partition") that is specific to Axcore, relating to the way the node software provisions data across network partitions; certain contracts are provisioned differently from others. In addition to this, we found that the only other concept we needed was a parameter specifying dependencies ("deps") that linearizes to a certain order to deployment (which may be necessary, for instance, if a given storage address stores reference to another). For concision, we added limited regex support. In the end, we arrived at a yaml-based file looking very much like the below:
-
-``` yaml
-version: 0.0.1
-setup:
-    partitions:
-        - custom-partition: *
-        - custom-partition: ^public-common
-    contracts:
-        - name: MagmaRegistryFooStorage
-        - name: MagmaRegistryBarStorage
-          deps:
-            - MagmaRegistryFooStorage
-upgrade:
-    partitions:
-        - custom-partition: "*"
-    contracts:
-        - name: MagmaRegistryFoo
-        - name: MagmaRegistryBar
-```
-
-In terms of implementation, a truffle exec script reads this configuration file, and for each contract, a) deploys the contract b) performs some basic API configuration and c) installs it in the application through invoking a basic `initialization` method. The basic top-level run (truffle exec) script looks very much like the below:
-
-``` javascript
-const run = async (done) => {
-    let jobParams = args;
-
-        // Configure specific variables for a PROD-like environment:
-    if (process.env.ENV === 'PROD') {
-        jobParams = Object.assign(args, handleProd());
-    }
-
-       //hoisting injected vars to global scope:
-    global.web3 = web3;
-    global.artifacts = artifacts;
-
-        // Create instance of job based on type
-    const jobInstance = new Job(jobParams.job, jobParams);
-
-        //Run job by deploying and invoking an initialization method on each contract
-    await jobInstance.run().catch(e => done(e));
-    done();
-};
-```
-
-A command-line client can specify a given job to run, such as the "upgrade" job specified above. Given the above configuration, the below command would deploy (if necessary) and initialize "MagmaRegistryFooStorage", followed by "MagmaRegistryBarStorage" from a given artifacts repository:
-
-``` bash
-etna --job upgrade --contracts_build_directory /path/to/artifacts
-```
-
-## Future Plans and an Announcement
-
-I am pleased to announce that we plan to open-source our core Solidity smart contract library, which provides an alternative version of the Proxy pattern, along with this aforementioned deployment tool. We believe both could be useful both for private and public applications and the Axoni team is excited to see what the community builds with these tools.
-
-
-In the meantime, we hope the above at least provides a high-level example of an approach to building lightweight extensions within truffle, and as a simplifying approach to the smart contract deployment process, especially for Proxy Pattern topologies.
-
-The Axoni team and I look forward to discussing this topic and much more (such as [Axlang, our Scala-based Solidity-alternative](https://axoni.com/axlang/)) at Trufflecon.
diff --git a/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md b/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
deleted file mode 100644
index 8e9f1a8aa..000000000
--- a/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: The Best Methods to Understand Blockchain Technology if You’re Not A Developer
-hide:
-  - navigation
----
-
-As a non-technical person, it feels like it takes 1.21 gigawatts to keep up with the speed of technology - even Doc Brown himself couldn't have predicted all of the technological advancements with his flux capacitor. Not only are we trying to keep up with technologies like blockchain, machine learning, and AI, but we have an overwhelming amount of information on the web all at the click of a mouse. It's overwhelming to the point that it's difficult to even know where to begin. However, online blockchain educational materials have started to ramp up. As I write this, I'm confident I'll start seeing “ Blockchain for dummies” online course advertisements on my browser (Opt-in, of course, because I'm using Brave). Mind-blowing! Let me help you begin by slowing down in order to speed up effectively.
-
-So you're someone who's not technical that wants to learn blockchain - great! Whether you're technical or non-technical isn't necessarily contingent on understanding an emerging technology like blockchain. Rather it's how you position yourself in the marketplace where you'll start to see the fruits of your labor.
-
-## Human to human chit chatting
-
-First things first, human to human interaction is where you want to start and it's awesome! Yes, [YouTube](https://www.youtube.com/watch?v=YGC9ECnot0k) will always be there for you - or at least until your battery dies, but dialoguing with another person and in this case, someone well-versed in blockchain will lay a strong foundation to springboard yourself into understanding this industry. I hate to use the phrase “trust me,” but trust me, as someone who's not that technical and has a background in Kinesiology, I can assure you that learning from the great minds of my Truffle developers has helped me grasp the concepts of blockchain technology. I'll say, most folks that are experts in their field generally have no problem chatting with a hungry and curious mind. If anything, it's flattering when I get approached to explain blockchain to someone who desires to understand it. We're gifted with the ability to use analogies and other practical ways of explanations that can make light of things that often feel dark and hard to see. Check out this great analogy on [sharding](https://youtu.be/5bOO7P-tZ3U?t=166)!
-
-Guess what? Developers don't mind talking to non-technical people who are trying to understand a particular technology like blockchain. It's a ridiculous stereotype to think devs only like to chat with other devs. If that were the case, how could a business be run successfully? In fact, oftentimes the best explanations come from the top experts. Developers don't like jargon or complexity either. We even gave the term developer operations a cute little nickname like DevOps. Seek out the developer in the blockchain space and ask away...better yet, reach out to one of us at Truffle–we love our community!
-
-## Meet-ups
-
-Go to your local blockchain meetups. There's probably more than a few that are available for you to attend. Meetups can be two-fold, namely, one to obtain knowledge and the other for networking, which can sometimes lead to a job. I can't tell you how many times I've hired someone that I initially met at a meetup. It sure beats throwing your resume on a job board hoping that it will stick. Relationships become the most valuable asset you can have to aid in your next employment opportunity. Moreover, everyone at a meetup shares one common trait. A passion for blockchain.
-
-## Social Media
-
-Maybe you're a little shy and don't want to network (although I highly recommend it!). There's a myriad of resources available online to learn the underpinnings of blockchain technology. You can visit our [Truffle University](/university) page for more information taking our courses. If you like to learn through watching other people's conversations, [Twitter is the place to go](https://media.consensys.net/i-read-crypto-twitter-for-hours-everyday-here-are-40-accounts-that-really-matter-cfecc681379d). You can make your way over to Quora if you have specific questions about blockchain. Don't want people to know who you are, Reddit has phenomenal ELI5 (explain it like I'm 5) explanations.
-
-## Read a Book
-
-Some people enjoy a nice old fashion book. By far the best book to understand blockchain is Mastering Bitcoin and [Mastering Ethereum](https://github.com/ethereumbook/ethereumbook) by Andreas Antonopoulos.
-
-## Podcast
-
-Listening to a [Podcast](https://player.fm/podcasts/Blockchain) is great. Especially when you're on the go. It's a way to redeem your commute to work, get through a workout session, or just something to pass the time. Often times, podcast hosts will have [guest](https://povcryptopod.libsyn.com/making-eth-sweet-with-tim-coulter) in the blockchain space to give an objective perspective on what the challenges and successes are with the technology.
-
-<h3 class="link-markdown">
-  <a href="#trufflecon" name="trufflecon">
-    <i class="fas fa-link">
-    </i>
-  </a>
-  ![TruffleCon](/img/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/trufflecon.png)
-</h3>
-
-Finally, and I may be a little bias, but if you really want to increase the pace at which you can comprehend blockchain then go to TruffleCon! Come say hi to all of us at Truffle. Come say hello to all of the speakers and blockchain company representatives. Ask us questions. Let us help you understand blockchain better. Let's network. Let's have a relationship that will enable amicability. Or better yet, let's interop with each other to leverage the power of blockchain for careers, security, and better transparency in an ever-growing technological world, one node at a time.
diff --git a/src/blog/blockchain-will-cure-cancer/index.md b/src/blog/blockchain-will-cure-cancer/index.md
deleted file mode 100644
index b35b6c055..000000000
--- a/src/blog/blockchain-will-cure-cancer/index.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Blockchain Will Cure Cancer
-hide:
-  - navigation
----
-
-<p style="width: 40%; float: left; margin-right: 1rem;">
-  <img style="margin-top: 0.3rem; margin-bottom: 0;" class="img-fluid" src="/img/blog/blockchain-will-cure-cancer/laptop.jpg" title="Laptop" alt="Laptop">
-</p>
-
-Physicians and scientists will be the actual agents behind a cure for cancer. But in their potential to disrupt the very nature of medical research and treatment, blockchain-based solutions are extremely likely to light the way. It is important when examining any new technology to consider the ways in which it may change the world. Join me here as we briefly look at how blockchain can help lead us to a world without cancer.
-
-Cancer is a significant public health issue in the United States and around the world. In the United States alone, an estimated [1.7 million new cancer cases](https://www.cancer.gov/about-cancer/understanding/statistics) were diagnosed in 2018. This number is expected to increase drastically as time goes on.
-
-Several barriers exist to finding a cure for cancer. Key among them are data challenges, difficulty quickly assessing the effectiveness of new treatments, and the financing required to fund research and treatment. Fortunately, blockchain technology is already providing avenues for addressing these barriers and bringing us closer to a cure for cancer.
-
-## It’s in the Data
-
-At its core, the path to curing cancer lies in accessing and evaluating as much data about the disease as possible. Blockchain solutions for medical data are [already being proposed and tested](https://www.healthcareitnews.com/news/blockchain-use-case-electronic-health-records). The primary benefits of using blockchain technology for storing and processing medical data lie in the portability and patient ownership of that data. On their own, these benefits are as helpful to cancer patients as they are to other medical patients.
-
-The particular usefulness of blockchain for cancer data lies in the ability of patients to volunteer their medical records to be used in research. This data will need to be anonymized and, of course, regulatory hurdles are likely to exist, but aggregating medical data from potentially millions of patients around the world will allow physicians and researchers access to unprecedented levels of information about the disease they seek to cure.
-
-[BreastWeCan.org](https://BreastWeCan.org) is one fledgling organization seeking to increase the base of data upon which further cancer research can be built. By encouraging women to upload their mammogram scans and other breast cancer images onto a blockchain, the company hopes to allow an AI to then study these images and share what it learns.
-
-## Better knowledge sharing means more effective treatments
-
-<p style="width: 40%; float: right; margin-left: 1rem;">
-  <img style="margin-top: 0.3rem; margin-bottom: 0;" class="img-fluid" src="/img/blog/blockchain-will-cure-cancer/petri.jpg" title="Petri Dish" alt="Petri Dish">
-</p>
-
-Information about cancer treatment and the results thereof is essential to finding a cure. From clinical trials to variation in responses to existing treatments among patients, information is the key. Blockchain technology can help in this respect by encouraging patients to share their treatment experiences and encouraging physicians to collaborate in their treatment attempts.
-
-One U.S. company has piloted a blockchain-based system for evaluating patient responses to cancer treatment. Encouraging patients and oncologists to provide information with an “Onco” coin, [OncoPower](https://pharmaphorum.com/news/blockchain-firm-witty-health-launches-digital-cancer-decision-tool/) will allow oncologists access to “de-identified … details like co-morbidity, specific cancer type, lines of therapy, and actual drugs used for treatment.”
-
-OncoPower’s promise lies in the ability to anonymize medical data, put it on a blockchain, and make it accessible to the medical community. This will encourage collaboration and knowledge-sharing amongst health care practitioners and researchers, increasing the visibility of various health outcomes and leading to faster iteration when it comes to experimental treatments.
-
-Another exciting treatment approach by [Hypertrust Patient Data Care](https://www.hypertrust-patient.com/) in Germany focuses on the immutable and verifiable aspects of blockchain to ensure that the supply chain for very sensitive immunotherapy treatments can be made as reliable as possible. Hypertrust tracks medication from “needle to needle” and leverages the transparency of a blockchain to improve patient outcomes.
-
-## Targeted Financing
-
-One thing that blockchain technology does incredibly well is to provide opportunities for decentralized governance and transparency. In the case of financing cancer research, blockchain could prove to be the silver bullet needed to ensure that funding goes where it will be most useful.
-
-While it does not appear that cancer fundraising has made its way onto a blockchain just yet, the ability of donors to contribute to cancer research in a tangible and trackable way is likely to increase donations and empower engagement within the scientific community. Putting cancer funding on a blockchain and encouraging the scientific community to engage in that blockchain’s governance could provide a catalyst for encouraging efficient, transparent, and collaborative research efforts.
-
-## Looking Ahead
-
-Blockchain technology is still in early stages, and it may be too soon to know precisely in which ways it may change our world. Developments in the medical applications of blockchain technology are very encouraging. Cancer has evaded a cure for many years, and the advent of new ways for scientists and physicians to learn, collaborate, and experiment may be just what the medical community needs.
-
diff --git a/src/blog/blog.html.jinja2 b/src/blog/blog.html.jinja2
new file mode 100644
index 000000000..48c2fd68f
--- /dev/null
+++ b/src/blog/blog.html.jinja2
@@ -0,0 +1,7 @@
+---
+title: {{title}}
+hide:
+  - navigation
+---
+
+{{ content }}
\ No newline at end of file
diff --git a/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md b/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
deleted file mode 100644
index fd9201f0e..000000000
--- a/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Branching Out - Announcing Tezos Support in Truffle
-hide:
-  - navigation
----
-
-![Announcing Truffle Integration](/img/blog/branching-out-announcing-tezos-support-in-truffle/chameleon-t3-truffle-blog-header.png)
-
-If you've been following Truffle's development, you'll notice that our tools already support a handful of exciting platforms: [Ethereum](https://ethereum.org/), [Quorum](https://www.goquorum.com/), [Axoni](https://axoni.com/technology/), Hyperledger [Fabric-EVM](https://github.com/hyperledger/fabric-chaincode-evm), Hyperledger [Sawtooth](https://www.hyperledger.org/projects/sawtooth), and Hyperledger [Burrow](https://www.hyperledger.org/projects/hyperledger-burrow). What's common amongst these chains is that they all use the Ethereum Virtual Machine under the hood. Ethereum is very near and dear to our hearts -- it's where we got our start, and where we are the most competent. But we're branching out, in large part due to market demand. In December we released a beta [Corda-flavored Ganache](/blog/unwrap-the-corda-flavored-ganache-beta) as part of our initial support for the [Corda platform](https://www.r3.com/corda-platform/). And today, we branch out even further.
-
-**I'm excited to announce Tezos integration into the Truffle command line tool.**
-
-Right now, at this very moment, you can [download a Tezos-specific version of Truffle](/docs/tezos/truffle/quickstart) and start building smart contracts on Tezos networks using the time-tested tooling you know and love. And if you're a Tezos native who got your start building on top of the Tezos platform, then this means professional-grade tooling has finally arrived.
-
-We chose Tezos as our first non-EVM chain because of its blossoming developer community. In our position as tool builders, we go where the market takes us: If enough people ask for Tezos support, we listen. This market demand was coupled with an active and interested group of core developers, and a blockchain architecture that's similar to Ethereum. Ultimately, Tezos is "EVM-like". This makes it a great candidate for integration, fitting into Truffle like a glove.
-
-Are you a developer who wants to build on top of Tezos using Truffle? [Check out our documentation](/docs/tezos/truffle/quickstart) and our [quick start guide](/docs/tezos/truffle/quickstart).
-
-It's important to note that our integration with Tezos is experimental. As of now you'll need to download a special version of Truffle to start building on Tezos. This is by design: Integrating a new blockchain into a common workflow takes some work, and we want to ensure we keep the same level of quality for our existing chains while we work out the kinks. You can be extremely helpful here! If you run into an issue using the Tezos version of Truffle, let us know! You can file an issue at our [issue tracker](https://github.com/trufflesuite/truffle/issues), or reach out to us on [Spectrum](https://spectrum.chat/trufflesuite).
-
-Our plan over the coming months is to harden our Tezos integration and ultimately release it under the mainline version of Truffle. We’ve also expanded our commitment to the Tezos project by finalizing plans for further integrations: 1) a Tezos-flavored [Ganache](/ganache); and 2) full support for the [SmartPy](https://smartpy.io/) programming language.
-
-Though this is our first foray into supporting non-EVM blockchains, I'd like to take this moment to reaffirm our support and interest in Ethereum and Ethereum-based blockchains. You'll see many more announcements in 2020 about how we're planning to make development on both Ethereum 1.0 and Ethereum 2.0 better. Stay tuned.
-
-I'd like to thank some standout developers in the Tezos community for making this integration a reality. First, are the developers from [Stove Labs](https://stove-labs.com/), Matej Šima & Istvan Deak. They helped significantly in stress testing our integration and providing continuous feedback during development. I'd also like to thank [Taquito](https://tezostaquito.io/) developers Jev Björsell and Simon B.Robert for creating an easy to use library for communicating with and interacting with the Tezos blockchain (for Ethereum developers, this is the Web3.js equivalent). Last but not least, a big shout out to the developers of the [LIGO](https://ligolang.org/) programming language, Gabriel Alfour and the rest of the LIGO development team, for making LIGO compiler integration easy on us. Cheers to you!
-
-We're excited to announce Tezos support as one of many integrations to come in 2020. Thank you for your continued support of our work, and the opportunity to make your development life easier. Happy coding!
-
-Tim
-
--- Founder & CEO, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md b/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
deleted file mode 100644
index cc3d131ab..000000000
--- a/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Branching Out - Phase 2 of Corda-flavored Ganache
-hide:
-  - navigation
----
-
-![Branching out to Corda-flavored Ganache](/img/blog/branching-out-phase-2-of-corda-flavored-ganache/chameleon-corda-truffle-blog-header.png)
-
-April has been a big month for Truffle Suite! Earlier this month we branched out and announced Tezos integration into the Truffle command line tool. If you remember, back in December we released a beta [Corda-flavored Ganache](/blog/unwrap-the-corda-flavored-ganache-beta) as part of our initial support for the Corda platform. Today, we are excited to share [Phase 2 of Corda-flavored Ganache, v2.4.0](https://github.com/trufflesuite/ganache/releases) with you! Phase 2 includes more robust features for Corda including Corda CRaSH Shell, network map visualization, and a version picker.
-
-We're thrilled to release Phase 2 of Ganache for Corda, an open source blockchain platform built for business applications, as this continues to lower the barrier to entry for Corda developers. These updates enable developers to easily set up a local network on their machines, letting them inspect the state of that network across various nodes and giving them visibility into transactions normally hidden by a live Corda network's privacy protections.
-
-Features Include:
-
-* One-click Corda network configuration and initialization, so you can focus on what matters most: your application.
-* Multiple workspaces for all of your Corda projects including a Corda network map, notaries, nodes, transactions, accounts, and ledgers.
-* Simple testing for interoperability with the Version Picker node.
-* Easy access to all your application's data, including network map, notaries, nodes, transactions, and states.
-* Visualizations of node connections with the Corda network map graph
-* Embedded Corda CRaSH Shell to provide control over your nodes and project data
-
-As always, this release is compatible with the latest versions of Windows ⊞, Mac OS 🍎, and Linux 🐧. You can now run and interact with a Corda network without installing prerequisites like Java, PostgreSQL, Corda binaries, docker, etc!
-
-If you are a Corda developer who wants to use Ganache with your CorDapp [check out our documentation and our quick start guide](/docs/ganache/corda/working-with-corda). We are also hosting a [joint webinar with R3](https://www.crowdcast.io/e/corda-ganache) on May 6th to demonstrate these features along with how this fits into existing Corda developer’s’ workflow.
-
-In closing, I’d like to thank our partners at R3, Todd McDonald, Lisa Chiong, Tiffany Sarmiento, Chris Chabot, and Nick Rogers for their collaboration, vision, and teamwork. I’d also like to thank [David Murdoch and Nick Paterno](/staff) from the Truffle team for their tireless efforts to make Corda Flavored Ganache a reality.
-
-Thank you for your continued support and the opportunity to make your development life easier. Happy coding!
-
-Tim
-
--- Founder & CEO, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md b/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
deleted file mode 100644
index dc158cce0..000000000
--- a/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Bring Your Own CI (BYOCI) with Truffle Teams
-hide:
-  - navigation
----
-
-Truffle Teams has always offered an internal continuous integration (CI) service. This service is great for getting up and running quickly since it requires no configuration to run your Truffle tests.
-
-We also want to support teams who have established CI setups outside of Truffle Teams. Thanks to the fantastic work by [Erin Shaben](https://github.com/eshaben), **you can now leverage your existing GitHub-integrated build services**!
-
-## Using an Existing CI Service
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/bring-your-own-ci-byoci-with-truffle-teams/figure-1.png" alt="Builds settings screen" style="width:100%">
-  <figcaption class="text-center font-italic">The BUILDS settings screen</figcaption>
-</figure>
-
-Enabling external CI for a repository only requires a single checkbox! Navigate to your user or organization’s settings page by clicking the user/org icon in the navbar. From there, click the BUILDS tab, then check the checkbox next to the repository of your choice!
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/bring-your-own-ci-byoci-with-truffle-teams/figure-2.png" alt="Build with external CI enabled" style="width:100%">
-  <figcaption class="text-center font-italic">Build with external CI enabled</figcaption>
-</figure>
-
-Now, when you navigate to the builds page for that repository, any new builds will show a list of your GitHub-integrated build services, along with their respective statuses.
-
-For more detailed information on the external CI service, [check out our documentation here](/docs/teams/builds/external-ci).
-
-For more detailed information on adding services to GitHub via their Marketplace, [check out the GitHub Marketplace docs here](https://help.github.com/en/github/customizing-your-github-workflow/about-github-marketplace).
-
-## Future Integration
-
-We want Truffle Teams to be the most effective devops tool in the blockchain space for both new and existing teams. Let us know what you think about this integration solution, and if your team has other needs we haven’t met yet.
-
-Thanks!
-
-Josh Quintal
-
--- Head of Product & Marketing, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md b/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
deleted file mode 100644
index 8fca48191..000000000
--- a/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Crytic - Continuous Assurance for Smart Contracts
-hide:
-  - navigation
----
-
-We are proud to announce our new Smart contract security product: [https://crytic.io/](https://crytic.io/). Crytic provides continuous assurance for smart contracts. The platform reports build status on every commit and runs a suite of security analyses for immediate feedback.
-
-The beta access will be open soon. Follow us [on twitter](https://twitter.com/CryticCI) to be notified and benefit from the service as soon as possible! The first three months are free.
-
-## How Crytic will secure your smart contracts
-
-Once connected to your GitHub repository, Crytic will:
-
-* Run our static analyzer [Slither](https://github.com/crytic/slither/), which detects the most common smart contracts vulnerabilities and will save you from critical mistakes.
-* Run your Truffle tests continuously to ensure that no bug is added while developing your project.
-
-Slither will analyze your codebase for more than 60 security flaws, including reentrancy, integer overflows, race conditions, and many others. Half of these flaw-detectors are private and were not available to the public. They can detect flaws for which public knowledge is limited and that no other tool can find. The recent [GridLock bug](https://blog.trailofbits.com/2019/07/03/avoiding-smart-contract-gridlock-with-slither/) would have been detected ahead of time using Crytic!
-
-We built this platform for developers, so we integrated it with GitHub. It will watch every commit and branch to ensure that bugs are not added during development. In addition, Crytic will run the checks on every PR to facilitate your code review.
-
-For every security issue found, Crytic will:
-
-* Show you a detailed report on the bug, including source-code highlighting.
-* Allow you to create a GitHub issue to keep track of the fixes easily.
-* Let you triage the results, so you can decide what needs to be fixed.
-
-## Quick Walkthrough
-
-Adding Crytic to your system is straightforward: you just need to connect to your GitHub repository. We have first-class support for Truffle; it works out of the box! We also support most of the other smart contract platforms, including Embark, Dapp, and Etherlime. After adding your repository, the dashboard (Figure 1) will show you a summary of the project, like this [crytic-demo](https://github.com/crytic/crytic-demo):
-
-<figure>
-  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-1.png" alt="Crytic Dashboard" style="width:100%">
-  <figcaption class="text-center font-italic">Figure 1: Crytic Dashboard</figcaption>
-</figure>
-
-From now on, you will benefit from continuous security analyses.
-
-### Issue reports
-
-Finding an issue is only the first part. Crytic will provide you with detailed information you need about the bug to fix it:
-
-<figure>
-  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-2.png" alt="Crytic Report" style="width:100%">
-  <figcaption class="text-center font-italic">Figure 2: Report</figcaption>
-</figure>
-
-A careful reader will notice the vulnerability here: `function constuctor` creates a public function (with a typo!) that is callable by anyone instead of being run only at initialization. Crytic will detect these types of critical mistakes instantaneously.
-
-### Triaging issues
-
-Once a bug has been found, the user can decide to:
-
-* create a GitHub issue, to easily keep track of the fix, or
-* discard the issue.
-
-<figure>
-  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-3.png" alt="GitHub Issue Generated" style="width:100%">
-  <figcaption class="text-center font-italic">Figure 3: GitHub Issue Generated</figcaption>
-</figure>
-
-Crytic follows the modifications to your code and reports only new bugs that are introduced.  Each new PR will be analyzed automatically:
-
-<figure>
-  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-4.png" alt="Pull Request Integration" style="width:100%">
-  <figcaption class="text-center font-italic">Figure 4: Pull Request Integration</figcaption>
-</figure>
-
-## What’s next for Crytic
-
-We are constantly improving Crytic. Expect to see new bug detectors and new features in the future. We are planning to add:
-
-* [Echidna](https://github.com/crytic/echidna) and [Manticore](https://github.com/trailofbits/manticore) integration: to ensure your code is checked for custom security properties.
-* Automatic bug repair: Crytic will propose patches to fix the issues it finds.
-* [Slither printer integration](https://github.com/crytic/slither/wiki/Printer-documentation): to help visualize the underlying details of your code.
-* Delegatecall proxy [checker](https://github.com/crytic/slither/wiki/Upgradeability-Checks): to prevent you from making critical—and all too common—mistakes in your [upgradeability process](https://blog.trailofbits.com/2018/09/05/contract-upgrade-anti-patterns/).
-
-Questions? Bring them to TruffleCon, and pose them to us at our booth or at our Friday workshop [on automated vulnerability detection tools](https://trufflecon2019.sched.com/event/RFQL/how-to-build-secure-smart-contracts-a-deep-dive-into-automated-tools?iframe=no&w=100%&sidebar=yes&bg=no)!
-
-Whether or not you can make it to TruffleCon, join our [slack channel](https://empireslacking.herokuapp.com/) (#crytic) for support, and watch [@CryticCI](https://twitter.com/CryticCI) to find out as soon as our beta is open.
diff --git a/src/blog/data.json b/src/blog/data.json
deleted file mode 100644
index 0652b64fe..000000000
--- a/src/blog/data.json
+++ /dev/null
@@ -1,506 +0,0 @@
-{
-  "introducing-truffle-dashboard": {
-    "title": "Introducing Truffle Dashboard",
-    "date": "2022-02-19",
-    "author": "Kingsley Arinze",
-    "published": true,
-    "excerpt": "Truffle Dashboard is a tool that completely removes the need to manually interact with your wallet's mnemonic phrase or private keys throughout the development lifecycle...",
-    "image": "/img/blog/thumbnails/truffle-dashboard-key.png"
-  },
-  "introducing-ganache-7": {
-    "title": "Introducing Ganache 7",
-    "date": "2022-01-20",
-    "author": "Kingsley Arinze, Mei Chan, & David Murdoch",
-    "published": true,
-    "excerpt": "Ganache is a pioneer in the Ethereum development space, aiding DApp developers and enthusiasts to build, test, and explore blockchain since 2016. We are excited to announce the wide release of the latest version of Ganache today...",
-    "image": "/img/blog/thumbnails/ganache-for-blog.jpg"
-  },
-  "truffle-and-infura-support-arbitrum": {
-    "title": "Truffle and Infura Now Support Arbitrum",
-    "date": "2021-07-07",
-    "author": "Faina Shalts",
-    "published": true,
-    "excerpt": "The Truffle team is thrilled to announce the launch of the Arbitrum Truffle Box. The usability and efficiency of Ethereum depends on scalability, and Arbitrum’s Layer 2 solution blends security and higher throughput to help make scalable Ethereum a reality.",
-    "image": "/img/blog/truffle-and-infura-support-arbitrum/blog-thumbnail.png"
-  },
-  "truffle-and-infura-support-optimism": {
-    "title": "Truffle and Infura Now Support Optimism",
-    "date": "2021-06-23",
-    "author": "Faina Shalts",
-    "published": true,
-    "excerpt": "The Truffle team is delighted to support Optimistic Ethereum in helping developers build for this ecosystem. Today we are announcing the launch of the new Truffle Optimism Box.",
-    "image": "/img/blog/truffle-and-infura-support-optimism/blog-thumbnail.jpg"
-  },
-  "sunsetting-truffle-teams": {
-    "title": "Sunsetting Truffle Teams",
-    "date": "2021-06-11",
-    "author": "The Truffle Suite Team",
-    "published": true,
-    "excerpt": "After a 2 year long road, we're sunsetting Truffle Teams. Truffle Teams will be shutting down in 30 days. Parts of Truffle Teams will be making their way into our open-source tools!",
-    "image": "/img/blog/sunsetting-truffle-teams/blog-thumbnail.png"
-  },
-  "truffle-and-infura-support-polygon": {
-    "title": "Truffle and Infura Now Support Polygon",
-    "date": "2021-05-11",
-    "author": "Faina Shalts & Michael Godsey",
-    "published": true,
-    "excerpt": "The developer demand for scaling solutions that work directly with Ethereum is here and growing, so today we are very excited to launch our all new Polygon Truffle Box.",
-    "image": "/img/blog/truffle-and-infura-support-polygon/blog-thumbnail.png"
-  },
-  "take-a-dive-into-truffle-5": {
-    "title": "Take a Dive into Truffle 5",
-    "date": "2021-4-20",
-    "author": "Harry Altman, Josh Quintal, Tyler Feickert",
-    "published": true,
-    "excerpt": "Dive into all the new features in Truffle's recent 5.x releases: Filecoin support, Solidity version detection, better Vyper compatibility and more!",
-    "image": "/img/blog/take-a-dive-into-truffle-5/blog-thumbnail.png"
-  },
-  "truffle-and-ganache-now-come-in-filecoin-flavor": {
-    "title": "Truffle and Ganache now come in Filecoin Flavor",
-    "date": "2021-3-31",
-    "author": "The Truffle Team",
-    "published": true,
-    "excerpt": "Today we are introducing two new integrations that support Filecoin and IPFS capabilities within Truffle and Ganache to build fully decentralized applications.",
-    "image": "/img/blog/truffle-and-ganache-now-come-in-filecoin-flavor/blog-thumbnail.png"
-  },
-  "iterate-faster-with-truffle-teams": {
-    "title": "Iterate Faster with Truffle Teams",
-    "date": "2021-2-10",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Consider the amount of context switching required to develop a dapp: you’re writing Solidity one minute, writing tests another, debugging those results--it’s easy to get lost! I’m happy to inform you Truffle Teams can help reduce context switching and help you or your team iterate faster.",
-    "image": "/img/blog/iterate-faster-with-truffle-teams/blog-thumbnail.png"
-  },
-  "2020-is-finally-over-a-year-end-wrapup": {
-    "title": "2020 is Finally Over: A Year End Wrapup",
-    "date": "2020-12-22",
-    "author": "Josh Quintal & The Truffle Team",
-    "published": true,
-    "excerpt": "2020 has been a trying time for us all: COVID-19 is still ravaging the world, the United States mired through one of our most contentious elections yet; basically, it’s been a rough year. Let’s take a look back at some positive things that came out of 2020, along with a little of what to look forward to in 2021.",
-    "image": "/img/blog/2020-is-finally-over-a-year-end-wrapup/blog-thumbnail.png"
-  },
-  "debug-quickly-and-in-context-with-truffle-teams-new-debugger": {
-    "title": "Debug Quickly and in Context with Truffle Teams New Debugger",
-    "date": "2020-11-12",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "If you’ve used Truffle’s debugger, you know it’s best-in-class. Until now though, it’s been confined to the command line. Today the debugger breaks out of the console to a GUI within Truffle Teams!",
-    "image": "/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/blog-thumbnail.png"
-  },
-  "try-new-features-first-with-truffle-teams-early-access": {
-    "title": "Try New Features First with Truffle Teams Early Access",
-    "date": "2020-11-12",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Wouldn’t it be nice to take Truffle Teams' new enhancements and features for a test drive? Now you can with early access!",
-    "image": "/img/blog/try-new-features-first-with-truffle-teams-early-access/blog-thumbnail.png"
-  },
-  "you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager": {
-    "title": "You Decide: Pipeline or Table View in Truffle Teams' Refreshed Deployments Manager",
-    "date": "2020-10-8",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Truffle Teams new deployments manager now has a table view, deployment cost, and console output.",
-    "image": "/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/blog-thumbnail.png"
-  },
-  "a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle": {
-    "title": "A Sweet Upgradeable Contract Experience with OpenZeppelin and Truffle",
-    "date": "2020-8-18",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Check out OpenZeppelin's new plugin to make it easier to deploy and upgrade proxy contracts.",
-    "image": "/img/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/blog-thumbnail.png"
-  },
-  "get-a-birds-eye-view-with-truffle-teams-new-dashboard": {
-    "title": "Get a Bird's Eye View with Truffle Teams' New Dashboard",
-    "date": "2020-8-11",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Truffle Teams new dashboard provides an overview of your application, along with ways to drill down and get further context on more narrow slices.",
-    "image": "/img/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/blog-thumbnail.jpg"
-  },
-  "announcing-collaboration-with-filecoin": {
-    "title": "Announcing Collaboration with Filecoin - Big Integrations Coming",
-    "date": "2020-7-7",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "Truffle and Filecoin have teamed up to help you build fully decentralized applications.",
-    "image": "/img/blog/announcing-collaboration-with-filecoin/blog-thumbnail.png"
-  },
-  "debugging-verified-external-contracts-with-truffle-debugger": {
-    "title": "Debugging verified external contracts with Truffle Debugger",
-    "date": "2020-6-18",
-    "author": "Harry Altman",
-    "published": true,
-    "excerpt": "Use Truffle Debugger and Truffle Teams to debug any Etherscan verified contract!",
-    "image": "/img/blog/debugging-verified-external-contracts-with-truffle-debugger/blog-thumbnail.png"
-  },
-  "sandbox-forking-with-truffle-teams": {
-    "title": "Simulate Live Networks with Forked Sandboxes",
-    "date": "2020-6-5",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Sandboxes are the easiest way to share a Ganache instance across an entire team. Our newest sandbox feature unlocks the power to run a simulated Mainnet (and other live networks).",
-    "image": "/img/blog/sandbox-forking-with-truffle-teams/sandbox-forking-thumb.png"
-  },
-  "stack-tracing-with-truffle-test": {
-    "title": "Stack Tracing with Truffle Test",
-    "date": "2020-5-8",
-    "author": "Harry Altman",
-    "published": true,
-    "excerpt": "Truffle Test can now provide stacktraces when your transactions revert!",
-    "image": "/img/blog/stack-tracing-with-truffle-test/blog-thumbnail-stacktraces.png"
-  },
-  "bring-your-own-ci-byoci-with-truffle-teams": {
-    "title": "Bring Your Own CI (BYOCI) with Truffle Teams",
-    "date": "2020-4-30",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "If you remember, back in December we released a beta Corda-flavored Ganache as part of our initial support for the Corda platform. Today, we are excited to share Phase 2 of Corda-flavored Ganache, v2.4.0 with you!",
-    "image": "/img/blog/thumbnails/byoci.png"
-  },
-  "branching-out-phase-2-of-corda-flavored-ganache": {
-    "title": "Branching Out: Phase 2 of Corda-flavored Ganache",
-    "date": "2020-4-28",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "If you remember, back in December we released a beta Corda-flavored Ganache as part of our initial support for the Corda platform. Today, we are excited to share Phase 2 of Corda-flavored Ganache, v2.4.0 with you!",
-    "image": "/img/blog/thumbnails/chameleon-corda-circle.png"
-  },
-  "branching-out-announcing-tezos-support-in-truffle": {
-    "title": "Branching Out: Announcing Tezos Support in Truffle",
-    "date": "2020-4-15",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "We're branching out with a new integration: Tezos! We've teamed up with the Tezos Foundation to provide Truffle's time-tested developer tools to the Tezos community.",
-    "image": "/img/blog/thumbnails/chameleon-t3-circle2.png"
-  },
-  "truffle-teams-gets-a-new-look": {
-    "title": "Truffle Teams Gets a New Look!",
-    "date": "2020-03-04",
-    "author": "Mike Seese",
-    "published": true,
-    "excerpt": "The Theobromine design efforts Josh presented at TruffleCon are coming alive in the latest release of Truffle Teams! The application now has a lighter, cleaner feal. We also changed the navigation a little to make your experience smoother.",
-    "image": "/img/blog/thumbnails/truffle-teams-gets-a-new-look.png"
-  },
-  "unwrap-the-corda-flavored-ganache-beta": {
-    "title": "Unwrap the Corda Flavored Ganache Beta",
-    "date": "2019-12-23",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Earlier this year at TruffleCon we announced our partnership with Corda to develop a Corda Flavored Ganache. Then, at CordaCon in London we shared more details around the integration. Today, we are proud to share with you the Beta release is live!",
-    "image": "/img/blog/thumbnails/corda-ganache-beta-blog-thumb.png"
-  },
-  "take-control-of-your-deployments-with-truffle-teams": {
-    "title": "Take Control of Your Deployments with Truffle Teams",
-    "date": "2019-12-18",
-    "author": "Mike Seese",
-    "published": true,
-    "excerpt": "Truffle Teams now gives you a dead-simple deployment experience. You push a couple of buttons, send transactions with MetaMask, and badabing, your contracts are on a public Ethereum network.",
-    "image": "/img/blog/thumbnails/truffle-teams-deployments.png"
-  },
-  "using-the-ens-integration": {
-    "title": "Using Truffle's ENS Integration",
-    "date": "2019-11-21",
-    "author": "Tyler Feickert",
-    "published": true,
-    "excerpt": "Truffle's ENS integration allows you to use ENS names in your migrations! You can also set addresses for ENS names that you own."
-  },
-  "truffle-teams-now-supports-private-repositories": {
-    "title": "Truffle Teams Now Supports Private Repositories",
-    "date": "2019-10-16",
-    "author": "Josh Quintal and Mike Seese",
-    "published": true,
-    "excerpt": "We're excited to announce that you can now integrate private repositories with Truffle Teams! This will eventually be a premium feature, but we're releasing it for free while the product is still in beta.",
-    "image": "/img/blog/thumbnails/truffle-teams-private.png"
-  },
-  "drizzle-150-a-new-beginning": {
-    "title": "Drizzle 1.5.0: A new beginning",
-    "date": "2019-9-10",
-    "author": "Adrian Li",
-    "published": true,
-    "excerpt": "Drizzle gets migrated to a monorepo with a focus on regular releases and a better contributor experience."
-  },
-  "using-truffle-to-interact-with-chainlink-smart-contracts": {
-    "title": "Using Truffle to interact with Chainlink Smart Contracts",
-    "date": "2019-8-20",
-    "author": "Chainlink, Guest Blogger",
-    "published": true,
-    "excerpt": "Chainlink is one of the leading blockchain projects building the very first decentralized oracle network that provides external data to smart contracts. Truffle helps smart contract developers by providing a powerful framework to create, test, and deploy smart contracts.",
-    "image": "/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/chainlink-az-circle.jpg"
-  },
-  "3-ways-enterprises-are-addressing-blockchain-privacy-concerns": {
-    "title": "3 Ways Enterprises Are Addressing Blockchain Privacy Concerns",
-    "date": "2019-7-31",
-    "author": "Danny Pan, Guest Blogger, West Monroe Partners",
-    "published": true,
-    "excerpt": "This year has seen numerous announcements of single and multi-party blockchain pilots by the Fortune 500 such as… Starbucks and MetLife. Data privacy issues haven’t stopped them and the enterprise blockchain world has taken these steps to shift their thinking."
-  },
-  "crytic-continuous-assurance-for-smart-contracts": {
-    "title": "Crytic: Continuous Assurance for Smart Contracts",
-    "date": "2019-7-30",
-    "author": "Josselin Feist, Guest Blogger, Senior Security Engineer from Trail of Bits",
-    "published": true,
-    "excerpt": "We at Trail of Bits are proud to announce our new Smart contract security product: https://crytic.io/. Crytic provides continuous assurance for smart contracts. The platform reports build status on every commit and runs a suite of security analyses for immediate feedback."
-  },
-  "upcoming-improvements-to-encoding-and-decoding": {
-    "title": "Upcoming improvements to encoding and decoding",
-    "date": "2019-7-29",
-    "author": "Harry Altman",
-    "published": true,
-    "excerpt": "When you’re writing, running, or debugging your smart contract, you don’t want to have to deal with raw binary data. Truffle––and Ganache and Drizzle––already contain a number of encoding and decoding features to help you interact with your contract and understand what you’re seeing. But luckily, encoding and decoding are about to become even more robust, informative, and usable."
-  },
-  "token-taxonomy-framework": {
-    "title": "Token Taxonomy Framework",
-    "date": "2019-7-26",
-    "author": "Marley Gray, Guest Blogger, Microsoft, Principal Architect - Azure Blockchain",
-    "published": true,
-    "excerpt": "To some, the sudden rise of Tokens in the blockchain dialog comes as a surprise. However, tokens have always been the bedrock of the blockchain movement. The introduction of SmartContract by Ethereum quickly overshadowed them, particularly in enterprise contexts. The capabilities of Smart Contracts and the broad acceptance of them, thanks to companies like Truffle, blazed a trail forward and we all went along. It wasn’t until we got halfway up the trail that someone turned around and asked, “did we pack any trail mix?”"
-  },
-  "axonis-enterprise-use-of-truffle": {
-    "title": "Axoni's Enterprise Use of Truffle",
-    "date": "2019-7-25",
-    "author": "Jonathan Leslie, Guest Blogger, a Lead Software Engineer from Axoni",
-    "published": true,
-    "excerpt": "At Axoni, our mission is to make shared information more trusted and reliable. We do this through distributed technology that we call \"Ethereum-inspired\"...given our compliance with the web3 JSON-RPC spec, Truffle basically works \"out-of-the-box\". However `truffle migrate` was less extensible, so we built a Truffle-based deployment tool.",
-    "image": "/img/blog/thumbnails/truffle-axoni.png"
-  },
-  "open-call-for-contributions-truffle-pegasys-eea-private-transactions": {
-    "title": "Open call for contributions by Truffle + PegaSys: EEA private transactions",
-    "date": "2019-7-24",
-    "author": "Felipe Faraggi, Guest Blogger, Developer Evangelist from PegaSys",
-    "published": true,
-    "excerpt": "In its current state, Truffle doesn't support EEA private transactions. Support for the web3js-eea library is needed for this to work and PegaSys has recently made an implementation of the v4.0 EEA specification. PegaSys and Truffle have teamed up to make a single open call for contributions. Help out and get some 😎 PegaSys swag and personally thanked on stage at TruffleCon!"
-  },
-  "best-methods-to-understand-blockchain-if-youre-not-a-developer": {
-    "title": "The Best Methods to Understand Blockchain Technology if You’re Not A Developer",
-    "date": "2019-7-24",
-    "author": "Scott Olson",
-    "published": true,
-    "excerpt": "As a non-technical person, it feels like it takes 1.21 gigawatts to keep up with the speed of technology - even Doc Brown himself couldn’t have predicted all of the technological advancements with his flux capacitor. Not only are we trying to keep up with technologies like blockchain, machine learning, and AI, but we have an overwhelming amount of information on the web all at the click of a mouse."
-  },
-  "blockchain-will-cure-cancer": {
-    "title": "Blockchain Will Cure Cancer",
-    "date": "2019-7-23",
-    "author": "Faina Shalts",
-    "published": true,
-    "excerpt": "Physicians and scientists will be the actual agents behind a cure for cancer. But in their potential to disrupt the very nature of medical research and treatment, blockchain-based solutions are extremely likely to light the way. It is important when examining any new technology to consider the ways in which it may change the world. Join me here as we briefly look at how blockchain can help lead us to a world without cancer."
-  },
-  "drizzle-vue-a-truffle-story": {
-    "title": "Drizzle Vue: A Truffle Story",
-    "date": "2019-7-22",
-    "author": "Amal Sudama",
-    "published": true,
-    "excerpt": "I felt this was an important problem to solve in order to improve the dapp developer experience.  It was important to get Drizzle working for Vue. Unfortunately, I knew nothing about Vue. In previous organizations I was a part of, I would have shied away from pursuing this project. However, at Truffle I felt comfortable and empowered to champion the idea.",
-    "image": "/img/blog/thumbnails/drizzle-vue.png"
-  },
-  "an-easier-way-to-deploy-your-smart-contracts": {
-    "title": "An Easier Way to Deploy Your Smart Contracts",
-    "date": "2019-7-19",
-    "author": "Mike Seese",
-    "published": true,
-    "excerpt": "Deploying your smart contracts shouldn't be difficult, and the process should be flexible. I give a sneak peek at the next feature we're building: an easy to use interface to deploy your Truffle projects with Truffle Teams! Be the first to use it at my TruffleCon 2019 workshop!",
-    "image": "/img/blog/thumbnails/truffle-teams.png"
-  },
-  "why-i-love-trufflecon": {
-    "title": "Why I love TruffleCon",
-    "date": "2019-7-18",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "TruffleCon is a conference, sure, but it's more than that: it's the feeling of excitement when learning a new technology; the eureka we felt when first discovering this new frontier. It's connections made in minutes that can last a lifetime."
-  },
-  "how-the-arrival-of-web-3-0-is-transforming-traditional-business-models": {
-    "title": "How the Arrival of Web 3.0 is Transforming Traditional Business Models",
-    "date": "2019-7-17",
-    "author": "Kevin Owocki, Guest Blogger, Founder at GitCoin",
-    "published": true,
-    "excerpt": "Although the Internet continues to drive digital transformation, the technology operates far beyond its original parameters. Since its inception over two decades ago, the web has been subject to increasing levels of centralization and mass surveillance. See how web 3.0 is transforming us today."
-  },
-  "how-ethical-advertising-will-transform-the-blockchain-industry": {
-    "title": "How Ethical Advertising Will Transform the Blockchain Industry",
-    "date": "2019-7-16",
-    "author": "Eric Berry, Guest Blogger, Founder at CodeFund",
-    "published": true,
-    "excerpt": "Introducing CodeFund for Blockchain"
-  },
-  "5-trends-impacting-the-blockchain-developer-experience": {
-    "title": "5 Trends Impacting the Blockchain Developer Experience",
-    "date": "2019-7-15",
-    "author": "Kevin Bluer",
-    "published": true,
-    "excerpt": "In this article we explore 5 trends impacting the developer-experience (or DX) when it comes to building blockchain-based solutions. Specifically, applications and services that leverage a blockchain or distributed ledger or as part of their overall architecture."
-  },
-  "develop-using-fluidity-truffle-box": {
-    "title": "Develop using Fluidity Truffle Box",
-    "date": "2019-7-12",
-    "author": "Deepa Sathaye, Guest Blogger from Fluidity",
-    "published": true,
-    "excerpt": "Fluidity has a pretty awesome truffle-box with lots of goodies to build secure, well-tested smart contracts. With two simple commands, you’ll be set up for development using these testing and security tools preconfigured."
-  },
-  "introducing-truffle-db-part-2": {
-    "title": "Introducing Truffle DB, part 2: 'Weight and Switch'",
-    "date": "2019-7-11",
-    "author": "gnidan (Nick D'Andrea) and Faina Shalts",
-    "published": true,
-    "excerpt": "In the second of this two-part blog post, we go over Truffle DB's data model, interface, and our roadmap to release."
-  },
-  "introducing-truffle-db-part-1": {
-    "title": "Introducing Truffle DB, Part 1: Artifact archeology",
-    "date": "2019-7-10",
-    "author": "gnidan (Nick D'Andrea)",
-    "published": true,
-    "excerpt": "In the first of this two-part blog post, learn about how Truffle manages to make sense of your project and some of the current limitations we hope to solve with our upcoming Truffle DB."
-  },
-  "the-blockchain-problem-that-ens-solves": {
-    "title": "The Blockchain UI Problem that ENS Solves",
-    "date": "2019-7-9",
-    "author": "Brantly Millegan, guest blogger from Ethereum Name Service",
-    "published": true,
-    "excerpt": "The blockchain world has a UI problem. The computer-generated address system works great for computers but isn’t user-friendly. That’s where the Ethereum Name Service (ENS) comes in. ENS provides the same basic functionality of DNS (look up the records for “example.tld,” retrieve information), but replaces the hierarchical DNS server system with a few smart contracts on Ethereum."
-  },
-  "the-best-ways-to-contribute-to-truffle": {
-    "title": "The Best Ways to Contribute to Truffle",
-    "date": "2019-7-8",
-    "author": "Tyler Feickert",
-    "published": true,
-    "excerpt": "Truffle is the amazing framework it is today because of developers like you. Find out how you can make Truffle even better!"
-  },
-  "10-things-we-dont-do-that-make-working-at-truffle-awesome": {
-    "title": "10 Things We Don't Do That Make Working at Truffle Awesome",
-    "date": "2019-7-5",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "At Truffle we have an extremely tight-knit team. You'll see that at this year's TruffleCon, a conference for hundreds of attendees organized by only a handful of people. We often have more work than we can handle, yet we take it on because we love the work we're doing and we love the people we work with."
-  },
-  "the-best-things-to-do-in-seattle-during-trufflecon": {
-    "title": "The Best Things to do in Seattle During TruffleCon",
-    "date": "2019-7-3",
-    "author": "Liz Daldalian",
-    "published": true,
-    "excerpt": "TruffleCon 2019 is happening August 2-4, 2019 at Microsoft’s Redmond campus on the Eastside of Seattle. Five Trufflers call the Seattle area home and we compiled a list of our favorite things to do in the area!"
-  },
-  "ethereum-gas-exactimation": {
-    "title": "Ethereum Gas Exactimation",
-    "date": "2019-6-21",
-    "author": "Nicholas Paterno & Cruz Molina",
-    "published": true,
-    "excerpt": "At Truffle, we decided such an approach was an unnecessarily CPU-intensive solution to the problem and set out to find a (theoretically) more performant and perfectly accurate way of estimating gas. The result? Gas exactimation."
-  },
-  "how-to-get-your-boss-to-send-you-to-trufflecon": {
-    "title": "How to get your boss to send you to TruffleCon",
-    "date": "2019-5-6",
-    "author": "Liz Daldalian",
-    "published": true,
-    "excerpt": "Last year Truffle Suite launched TruffleCon, an event designed for the Truffle community and those interested in building world-changing applications powered by decentralized technologies. The event was received with an overwhelmingly positive response."
-  },
-  "truffle-v5-has-arrived": {
-    "title": "Truffle v5 has arrived!",
-    "date": "2018-12-18",
-    "author": "Brittany Alexander",
-    "published": true,
-    "excerpt": "We have released the most awaited version of Truffle just in time for the holidays! There are SO many exciting things to mention that will make your Truffle experience a rich one."
-  },
-  "why-were-organizing-trufflecon-2018": {
-    "title": "Why We're Organizing TruffleCon 2018",
-    "date": "2018-07-16",
-    "author": "Mike Pumphrey",
-    "published": true,
-    "excerpt": "As you have hopefully heard by now, TruffleCon, Truffle's first-ever user conference, will be on October 5-7, 2018 in Portland, Oregon, U.S.A."
-  },
-  "announcing-full-portable-solidity-debugger": {
-    "title": "Announcing our Fully Featured, Portable Solidity Debugger",
-    "date": "2018-2-26",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "Since Truffle's inception, it's been our mission to build outstanding development tools for the Ethereum community. The analogy we always used was one of history: Ethereum development practices are years behind the rest of the industry, and it's our job to build tools that modernize our craft. Well today, Truffle's come one step closer to that goal. We're happy to announce the release of our fully featured, fully portable Solidity debugger and debugging libraries."
-  },
-  "drizzle-reactive-ethereum-data-for-front-ends": {
-    "title": "Drizzle: Reactive Ethereum Data for Front-ends",
-    "date": "2018-2-20",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Today we're proud to announce the addition of a new product to the Truffle Suite: Drizzle. Drizzle is a collection of front-end libraries that make writing dapp front-ends easier and more predictable.",
-    "image": "/img/blog/thumbnails/drizzle-some-chaindata-on-your-ui.jpg"
-  },
-  "testrpc-is-now-ganache": {
-    "title": "TestRPC is now Ganache",
-    "date": "2017-12-26",
-    "author": "Mike Pumphrey",
-    "published": true,
-    "excerpt": "Have you been looking for the TestRPC recently and haven't been able to find it? Don't worry, it's still here! It's just now known as Ganache. Ganache comes in two flavors: a fully-interactive development blockchain with a graphical interface, and the more familiar command-line version."
-  },
-  "first-ever-truffle-retreat": {
-    "title": "Our First Ever Truffle Retreat",
-    "date": "2017-11-29",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "We recently released Truffle 3.0 in February to much fanfare. As part of that release we separated our codebase into multiple different modules to make integrating with Truffle easier. Those modules now live in the github repository http://github.com/trufflesuite, which hints at our broader mission of providing a comprehensive suite of tools for Ethereum development.",
-    "image": "/img/blog/thumbnails/first-ever-truffle-retreat.jpg"
-  },
-  "designing-the-ganache-logo": {
-    "title": "Designing the Ganache Logo",
-    "date": "2017-11-21",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Last week we released Ganache, a personal blockchain for Ethereum development. Many of you commented on the design of the landing page and logo, but just how did the gooey cube come to be? Let's take a trip through the 30+ iterations that led to our newest confection.",
-    "image": "/img/blog/thumbnails/designing-the-ganache-logo.jpg"
-  },
-  "one-hundred-documentation-pull-requests": {
-    "title": "One hundred documentation pull requests? Yes please.",
-    "date": "2017-10-23",
-    "author": "Mike Pumphrey",
-    "published": true,
-    "excerpt": "Greetings! The Truffle team has been growing over the course of the last year. From a single developer, we are now a team of five (soon to be even more), which means that we can spread the work around. As a new full-time member of the team, I've first taken to looking at our existing materials to ensure that everything is up-to-date and working well. For example, our website, a public GitHub repository, had been receiving pull requests (PRs) for the better part of a year, and they had been languishing for want of someone to go through them.",
-    "image": "/img/blog/thumbnails/one-hundred-documentation-pull-requests.jpg"
-  },
-  "you-can-now-make-your-own-truffle-box": {
-    "title": "You Can Now Make Your Own Truffle Box",
-    "date": "2017-9-26",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Two months ago we unveiled official integration with Truffle Boxes, example Ethereum applications and/or boilerplates that put complimentary tools and libraries into sweet, easily-downloadable packages. In addition to rolling out some official boxes, Status.im released the first community-supported box. Today we're happy to announce anyone can now make their very own Truffle Box!"
-  },
-  "learn-ethereum-the-fun-way-with-our-pet-shop-tutorial": {
-    "title": "Learn Ethereum The Fun Way with our Pet Shop Tutorial",
-    "date": "2017-7-12",
-    "author": "Josh Quintal",
-    "published": true,
-    "excerpt": "Here at Truffle we want to make Ethereum development accessible to developers of all stripes. To that end, today we're releasing a new tutorial called Pet Shop. It covers the entire local development process, start to finish. For added fun, we've tied the whole thing together within the narrative of creating a pet adoption dapp for a local pet shop owner.",
-    "image": "/img/blog/thumbnails/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial.jpg"
-  },
-  "truffle-boxes-making-life-sweeter": {
-    "title": "Truffle Boxes: Making Life Sweeter",
-    "date": "2017-7-6",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "When users begin developing on Ethereum, the first question they ask is, \"Where do I start?\". In the past, there hasn't been an easy answer: the answer generally consisted of many flavors of \"it depends\", and usually led to an investigation of what the user was trying to build, a general overview of their development skills, their knowledge of Ethereum, and the libraries and tools they're already most comfortable with. When determining how the Truffle team can help in this process, it quickly became apparent that what our users needed were examples. Many of them. So, being the upstanding community members we are, we set out to create those example, and today, we're happy to show you what we've accomplished."
-  },
-  "removing-installation-issues-continued-testrpc": {
-    "title": "Removing installation issues, con't: TestRPC",
-    "date": "2017-6-13",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "Update: Since this blog post was published, we have released Ganache a personal blockchain and a replacement to the TestRPC. We have left this post unaltered, but we highly recommend checking out our Working with Ganache page."
-  },
-  "how-were-making-installation-issues-a-thing-of-the-past": {
-    "title": "How we're making installation issues a thing of the past",
-    "date": "2017-6-5",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "Update: Since this blog post was published, we have released Ganache a personal blockchain and a replacement to the TestRPC. We have left this post unaltered, but we highly recommend checking out our Working with Ganache page."
-  },
-  "truffle-320-released": {
-    "title": "Truffle 3.2.0 released 🎉",
-    "date": "2017-3-22",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "Hi all. Great news today. Following your feedback from the Truffle 3.0 release, we've just released Truffle 3.2.0! This release includes a number of great new features and bug fixes, but we're most excited about the following. I've bolded the good stuff for ya."
-  },
-  "github-repository-moved": {
-    "title": "We've moved our github repo!",
-    "date": "2017-3-17",
-    "author": "Tim Coulter",
-    "published": true,
-    "excerpt": "We recently released Truffle 3.0 in February to much fanfare. As part of that release we separated our codebase into multiple different modules to make integrating with Truffle easier. Those modules now live in the github repository http://github.com/trufflesuite, which hints at our broader mission of providing a comprehensive suite of tools for Ethereum development."
-  }
-}
diff --git a/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md b/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
deleted file mode 100644
index 3a9571084..000000000
--- a/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Debug Quickly and in Context with Truffle Teams New Debugger
-hide:
-  - navigation
----
-
-![Truffle Teams Debugger Banner](/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/blog-header.png)
-
-If you've used Truffle's debugger, you know it's best-in-class. Until now though, it's been confined to the command line. Today the debugger breaks out of the console to a GUI within Truffle Teams! This is a huge workflow enhancement--allowing us to debug transactions in the places we're already viewing--via the deployment details screen or while monitoring individual contracts. Let's take a look!
-
-<p class="alert alert-info">
-  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the debugger right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
-</p>
-
-## Launching the Debugger
-
-To launch the debugger, we just need to find a transaction. Head over to the Deployments screen and select a deployment. From there select the transactions tab or click the monitoring button for a contract. You'll notice there's a debug button on each transaction card; clicking it will open the Truffle Teams debugger.
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/teams-debugger-1.png" alt="All transaction cards now have a debug button">
-  <figcaption class="text-center font-italic">Debugging is only a click away!</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-## Navigating the UI
-
-Starting at the top, you'll see the transaction hash along with an icon noting its status and, if applicable, the accompanying error message (1). Below that we have our functions, from left to right: Step Next, Step Over, Step In, Step Out, and Reset (2). Next we have some tabs showing the contracts included in this transaction (3). Finally we have two panes, one showing our Solidity with the current step highlighted in yellow (4). The second with our variables (5).
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 figure-shadow" src="/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/teams-debugger-2.png" alt="The debugger in action on a failed transaction">
-  <figcaption class="text-center font-italic">Debugging a failed transaction.</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-At the moment some other enhancements, including breakpoints and syntax highlighting, are coming soon. We wanted to get this powerful feature in your hands as quickly as possible, so we're releasing it now via Early Access. For more information on what to expect from early access, check out [the Truffle Teams Early Access blog post](/blog/try-new-features-first-with-truffle-teams-early-access).
-
-For more information, check out [the Truffle Teams Debugger docs](/docs/teams/debugger/debugging-a-transaction) or for general information about Truffle's debugger, check out [the Truffle Debugger docs](/docs/truffle/getting-started/debugging-your-contracts).
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE TRUFFLE TEAMS DEBUGGER</a>
-</div>
-
-## Continue the Conversation
-
-We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven't met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md b/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
deleted file mode 100644
index a68a6d549..000000000
--- a/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: Debugging verified external contracts with Truffle Debugger
-hide:
-  - navigation
----
-
-![Truffle Teams Redesign Banner](/img/blog/debugging-verified-external-contracts-with-truffle-debugger/blog-header.png)
-
-Let's say you're crafting a clever flashloan transaction that interacts with
-five different DeFi dapps -- but on trying it, it doesn't work as expected.  You
-open the transaction in Truffle Debugger to get a closer look at what went
-wrong.  But how will you debug a transaction that the debugger doesn't have the
-source code for?
-
-Well, new in Truffle release v5.1.29 is the debugger's `--fetch-external` flag!
-This new flag tells the debugger to search [Etherscan's repository of verified
-contracts](https://etherscan.io/contractsVerified) and automatically
-download and compile those sources.  As long as all the contracts you're
-interacting with are verified on Etherscan, you're good to go!
-
-This means you'll be able to debug Mainnet / Görli / Ropsten / etc. transactions
-that interact with external contracts _without the need to have external
-contract source code available locally_!
-
-Now, before you get too excited, some caveats apply:
-- This only works with Solidity contracts, since @truffle/debugger only supports
-  Solidity at this time.
-- While using this feature, you won't be able to load and unload transactions
-  in the debugger like normal; you'll have to quit and restart to change
-  transactions.
-- In order to be able to use the debugger and have it find the right source to
-  download for your network, you'll need to connect to an archive node that
-  offers the `debug_traceTransaction` JSON RPC method. (See Geth's [Management
-  APIs](https://github.com/ethereum/go-ethereum/wiki/Management-APIs)).
-
-That last one is a pretty big caveat, but **there's good news here**! Our
-sibling SaaS project, [Truffle Teams](/docs/teams/overview), now
-lets you [simulate live
-networks](/blog/sandbox-forking-with-truffle-teams)
-via the free Sandbox feature. This works without requiring you to run your own
-node or to pay for someone else to run their own node, since Truffle Teams
-offers 1 free sandbox per GitHub organization!
-
-Of course, you're free to use the debugger with whatever compatible Ethereum
-node you like, including command-line Ganache; but here's how to use Truffle
-Teams, which offers so much more, for this feature.
-
-### Example: Debug ENS in a [mostly] empty Truffle project!
-<a href="/img/blog/debugging-verified-external-contracts-with-truffle-debugger/debug-example1.png" target="_blank"><img width="100%" alt="Click to enlarge" src="/img/blog/debugging-verified-external-contracts-with-truffle-debugger/debug-example1.png">Click to enlarge</a>
-
-This screenshot shows `truffle debug` stepping through a Görli transaction to the ENS registry. Once you upgrade to Truffle v5.1.29, you can recreate this by doing the following:
-
-1. Find the [Görli ENS contract page on
-Etherscan](https://goerli.etherscan.io/address/0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e).
-
-2. Find a recent transaction hash. (See [example from
-screenshot](https://goerli.etherscan.io/tx/0x79381a69eb828558f2728900615109eb7bdeb6d216af130142341da15cc6fecd).)
-
-3. [Sign up / login to Truffle Teams](https://my.truffleteams.com/) and make a
-free Sandbox that forks off Görli. **Note**: At the moment, you'll have to make
-sure that you manually specify that the Sandbox should use the same network ID
-as the chain it's forked from (in this case, 5).  In the future, however, this
-step will be handled automatically.  You can read more about Sandboxes in [our
-earlier blog post on the
-subject](/blog/sandbox-forking-with-truffle-teams).
-
-4. Copy your sandbox JSON RPC url to the clipboard.
-
-5. Run `truffle init` and add this to your new `truffle-config.js` (replacing `"<paste RPC url>"` with your clipboard contents from step 4):
-  ```javascript
-  module.exports = {
-    /* ... rest of truffle-config.js ... */
-    networks: {
-      /* ... rest of networks ... */
-      sandbox: {
-        url: "<paste RPC url>",
-        network_id: 5
-      }
-    }
-  }
-  ```
-5a. _Optional_. If you have an [Etherscan API key](https://etherscan.io/apis) or
-feel like making one, you can specify that as well in your `truffle-config.js`
-to speed up downloads:
-  ```javascript
-  module.exports = {
-    /* ... rest of truffle-config.js ... */
-    etherscan: {
-      // replace this with your API key
-      apiKey: "0123456789abcdef0123456789abcdef"
-    }
-  }
-  ```
-  
-6. Copy the transaction hash from step 2 and run the following (replacing
-`<transaction hash>` with the `0x`-prefixed transaction hash):
-  ```
-  truffle debug <transaction hash> --network sandbox --fetch-external
-  ```
-
-And that's it!  You're now debugging an ENS transaction in an empty Truffle
-project.  You can step through and set breakpoints; inspect both decoded
-variables and the raw binary state; and get return values, revert messages, and
-stacktraces just like normal.
-
-Now this example is a minimal one just to show how things work.  But it will
-work just as well in your existing projects on transactions that feature your
-contracts in your project interacting with external verified contracts deployed
-on live networks.
-
-Right now "verified contracts" just means contracts verified on Etherscan, but
-we're also looking at supporting the new
-[Sourcify](https://github.com/ethereum/sourcify) project, which provides a more
-decentralized alternative to Etherscan's repository. We plan to add this in an
-upcoming release.  But as of right now, you can use this feature with
-Etherscan's large library of verified contracts!
-
-**Update**: As of Truffle v5.1.32, [Sourcify](https://github.com/ethereum/sourcify) is now supported!  Truffle
-Debugger will now check both [Etherscan](https://etherscan.io/) and [Sourcify](https://github.com/ethereum/sourcify) for verified
-contract sources!
-
-Hope you find this as exciting as we do! Thanks for using Truffle!
diff --git a/src/blog/designing-the-ganache-logo/index.md b/src/blog/designing-the-ganache-logo/index.md
deleted file mode 100644
index 2e80b01bb..000000000
--- a/src/blog/designing-the-ganache-logo/index.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Designing the Ganache Logo
-hide:
-  - navigation
----
-
-Last week we released [Ganache](/ganache), a personal blockchain for Ethereum development. Many of you commented on the design of the landing page and logo, but just how did the gooey cube come to be? Let's take a trip through the 30+ iterations that led to our newest confection.
-
-<div class="row"><div class="col-xs-10 col-xs-push-1 col-sm-6 col-sm-push-3 m-b-2">
-![Final Ganache Logomark](/img/blog/designing-the-ganache-logo/final-logomark.png)
-</div></div>
-
-Before setting out on our design journey, we started with some loose guidelines:
-
-* The new logo should be round and have some dimensionality to keep it consistent with the Truffle logo.
-* The colors should consist of chocolate, an accent color and white.
-
-The concepts we explored can be roughly broken down into 4 categories: Core Cutaways, Toppings, Gooey Cores and Soft Blocks.
-
-## Core Cutaways
-
-The first set of core cutaways was an attempt to convey that Ganache, as a local development blockchain, was the "core" of your development workflow. They also depict a ganache filled truffle candy of varying viscosities.
-
-It was toward the end of this stage we qualified one of our initial guidelines. The logo's dimensionality should be represented purely by shape--no gradients!
-
-**Fun fact**: We considered one of the third row, second and third column concepts as a final candidate, but scrapped it when Tim's wife said it looks like a banana slug floating in space. My baby, a slug?! A great reminder to not get too attached before getting feedback!
-
-</div><div class="text-center container">
-  ![Ganache Logo Concepts - Core Cutaways](/img/blog/designing-the-ganache-logo/core-cutaways.png)
-</div><div class="container container-narrow">
-
-## Toppings
-
-Questions about the ability of the core cutaways to translate to flat color, as well as being dimensionally mismatched with the Truffle logo caused us to consider a simpler approach; a spherical candy with ganache on the outside. Overall these failed to look interesting and had the opposite problem in that they weren't dimensional enough.
-
-</div><div class="text-center container">
-  ![Ganache Logo Concepts - Toppings](/img/blog/designing-the-ganache-logo/toppings.png)
-</div><div class="container container-narrow">
-
-## Gooey Cores
-
-Not satisfied with the topping options we pressed on and attempted the core concept again, this time with some fancier cutaways. While they stood on their own, they were too wide a departure from the Truffle logo. This lack of cohesion lead to a realization that would be our design breakthrough.
-
-</div><div class="text-center container">
-  ![Ganache Logo Concepts - Gooey Cores](/img/blog/designing-the-ganache-logo/gooey-cores.png)
-</div><div class="container container-narrow">
-
-## Soft Blocks
-
-Letting go of our assumption that the shape should be round unlocked a series of designs that eventually led to our final logo. To achieve a more interesting drip pattern, we traced and combined different stages of glaze dripping down a cake. It became apparent that this approach was interesting, but made an overly detailed drip pattern which we later simplified for the final. We also tried a few different treatments of the candy's reflection. Check out that longhorn steer in the lower-left!
-
-</div><div class="text-center container">
-  ![Ganache Logo Concepts - Soft Blocks](/img/blog/designing-the-ganache-logo/soft-blocks.png)
-</div><div class="container container-narrow">
-
-## The Final Logo
-
-Success! After reconsidering some assumptions and solidifying others, we arrived at our final design. The final logo has both a compelling design and the following qualities that made it a winner:
-
-* The colors consist of chocolate, an accent color and white; a guideline we'll keep going forward.
-* It's metaphorically grounded in the product it represents--it's a block, after all!
-* The gooey consistency and soft, rounded corners represent the intimidating technical concept of a blockchain in a friendly and approachable way.
-
-<div class="row"><div class="col-xs-10 col-xs-push-1 col-sm-6 col-sm-push-3 m-b-2">
-![Final Ganache Logo](/img/blog/designing-the-ganache-logo/final-logomark.png)
-</div></div>
-
-We had a blast iterating this logo and Ganache itself. We hoped you learned from our experience and maybe picked up some of your own inspiration along the way. **Happy illustrating!**
-
--- Josh & the Truffle Team
diff --git a/src/blog/develop-using-fluidity-truffle-box/index.md b/src/blog/develop-using-fluidity-truffle-box/index.md
deleted file mode 100644
index a3b155a1e..000000000
--- a/src/blog/develop-using-fluidity-truffle-box/index.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Develop using Fluidity Truffle Box
-hide:
-  - navigation
----
-
-**TLDR;** Fluidity has a pretty awesome truffle-box with lots of goodies to build secure, well-tested smart contracts. With two simple commands, you’ll be set up for development using these testing and security tools preconfigured.
-
-To use:
-
-```shell
-npm install -g truffle
-truffle unbox fluidity/fluidity-truffle-box
-```
-
-## Develop using Fluidity Truffle Box
-
-Today, I’d like to share Fluidity’s Truffle Box. It contains a combination of tools we use to develop, test, and analyze our smart contracts. As our team has created several products and proof-of-concepts, we’ve developed a set of standards for creating smart contract repos and having a truffle-box makes this easier. We’ve tried and tested different tools and this box contains our favorite tools for efficient development.
-
-The Fluidity Truffle Box allows us to bootstrap our smart contract projects. This box focuses primarily on building safe and secure smart contracts that can be easily audited. We’re able to consolidate many of the new tools, as well as ensure that any projects we start always use up to date versions. Prior to starting new projects, we double check that the packages and tools within truffle-box are up to date. We acknowledge this truffle-box is not a kitchen sink of all the tools. It has been curated based upon what we consistently use. The box doesn’t have a UI component and mostly contains configurations and tools that aid in testing.
-
-## Core Tools
-
-At Fluidity we write smart contracts with Solidity using the latest fixed version, currently 0.5.10, and we use Ganache as our primary test chain. We use Open-Zeppelin as the base for many of our contracts’ systems. In addition, there’s a linter for both the smart contracts and tests using [solhint](https://www.npmjs.com/package/solhint) and [standard](https://www.npmjs.com/package/standard). A linter analyzes code and tests and then either recommends or updates the code for potential syntax errors and style recommendations. Solhint’s configuration is present in fluidity-truffle-box and tries to closely align with the Solidity documentation. We use standard because it’s opinionated and keeps the codebase consistent with minimal fuss. Thus, standard doesn’t have any custom configurations.
-
-## How we handle testing and code coverage
-
-### Gnosis Mock Contract
-Gnosis-Mock is a comprehensive mocking smart contract that allows us to perform unit-testing of our smart contracts. For those not familiar, mocking means creating dummy objects to simulate the behavior of real objects. Mocking allows one to isolate the behavior of the testable object from any other dependencies. As an example, certain behavior in smart contract designs, such as closing a token sale, may require dependencies on several state variables and contracts to already be triggered to allow it to burn tokens. To close a token sale, let’s say you need to have started the sale, sold some threshold of tokens, reached a certain future block, and given close sale privileges to another user. Any one of these requirements, outside of just calling close sale, would need to be run if mocking were not used. By simulating these states with dummy smart contract, it narrows down exactly what needs to be tested. We heavily use the Gnosis mock library which allows us to test contracts independently before running any integration tests.
-
-### Truffle Assertions
-Truffle assertions has streamlined how we test events and states of smart contracts. The packages works inside Truffle tests and provides more assertions to call about smart contract states. It supports revert reason strings so we can be confident that exact cases are hit on revert. In addition, it provides more granular ways to test for function failures.
-
-### Eth-gas-reporter
-Eth gas reporter shows us the gas usage per unit tests in a nice report after running your test suite. We’ve tried many other tools before as well as trying to write custom gas usage with web3. This has been a recent find for us and has made gas analysis much easier.
-
-### Solidity-coverage
-We use solidity-coverage to determine what percentage of the codebase is covered by unit tests. We use a forked version by **leapdao** because this version supports many of the breaking changes with Solidity 0.5.0+. Code coverages give a helpful metric to ensure we’re testing as we code and that all branch paths are tested. It has also served for us to remove redundant code paths that we’ve found were not accessible. In addition, we have incorporated code-coverage with our CI process, meaning it is automatically executed on every pull request we make, allowing us to easily check PRs for code coverage. The configuration is stored in `<project_rool>/.solcover.js`, and can be personalised for your project.
-
-### Slither and Mythril
-Both slither and mythril are python packages that we’ve included in our truffle-box. They are security tools by [Trail of Bits](https://www.trailofbits.com/) that allow us to better self-audit our code and evaluate many of our invariants and assumptions internally. Instructions to run each of these packages are stored in the README.md file of the fluidity-truffle-box.
-
-Slither is a static code analyzer by Trail of Bits. It runs across the contracts directory fairly quickly (< 1 min) and picks up potentially vulnerable Solidity code. Mythril is a security analysis tool for EVM bytecode from ConsenSys. The program takes much longer to run, and while it’s in the truffle-box, we’ll usually run this tool on AWS or another cloud environment and analyze those results. While there is some overlap of errors that are picked up by truffle-compile, slither, and mythril, each focuses on different types of error. We therefore find it helpful to use all 3 on our contracts.
-
-### Circle CI Template
-At Fluidity we use circle-ci for our continuous integration. By having sample templates in the repo, it’s more convenient to making sure we enable it whenever we create new repositories. The new repos therefore constantly have to build successfully and migrate via Ganache, and test coverage is apparent to all members on the team. With the template in place, it’s quick for us to add additional commands such as linting or gas reporting dependent on where we are in the development process.
-
-## Unique features
-### Using allowUnlimitedContractSize
-We allow our initial contract designs not to be limited by any contract size constraints with the use of the flag *allowUnlimitedContractSize*. Ganache has a default gas limit of 6,721,975 which does not reflect the actual gas limit of public testnet and mainnets, being 7,000,000 and 8,000,000 respectively. While our team does want to reduce the gas footprint while developing and iterating through different token designs/debugging, it’s been helpful not to be limited by a strict gas price or gas limit with testing. For example, we use longer descriptive messages in revert reasons when developing, but reduce them to be more succinct for final code versions. Reducing the string lengths saved us 3,000,000 gas.
-
-
-Run each line in a different terminal window
-
-```shell
-yarn ganache-unlimited
-yarn truffle truffle-unlimited
-```
-
-After settling on a design, we’ll start iterating to reduce gas usage. As mentioned above, we use eth-gas-reporter to do this. Thus, with 100% test coverage and integration tests, eth-gas-reporter gives a pretty comprehensive understanding of gas usage throughout.
-
-## Custom Migration and Test Utilities
-
-There are two custom utilities files that we have created and keep available for the right circumstance of contracts. First, we have a custom migration utilities script. Truffle has deployed contract management but only stores a single address for each contract deploy per network id; each deployed contract is treated as a singleton. However, there have been cases where we’ve deployed multiple instances of the same contract and have needed to save each of the deployed contract addresses. Our solution was to create a custom migration_utils.js that stored the contract addresses per migration in  a JSON file. From there, integration tests and accessory scripts use the contract addresses while still relying on the build directory for ABIs.
-
-The second script is related to testing time sensitive smart contracts. We’ve written a post about it called [Standing the Time of Test](https://medium.com/fluidity/standing-the-time-of-test-b906fcc374a9) and we’ve used this script and features in Ganache to run both idempotent tests as well as run simulations.
-
-Running the command for a specific date
-
-```shell
-yarn ganache-unlimited --time '2019-02-15T15:53:00+00:00'
-```
-
-## Anything else
-
-Most of the features are in the [README](https://github.com/airswap/fluidity-truffle-box) in the directory and I’d love to take any questions or issues using this repository. Linking all these tools allows for a solid, sane development process for our team. They’re always at our fingertips with fluidity-truffle-box. Hopefully, you’ll be able to use the Fluidity Truffle Box to enhance your own smart contract development process!
-
-## Github repos
-* Fluidity Truffle Box: [https://github.com/fluidity/fluidity-truffle-box](https://github.com/fluidity/fluidity-truffle-box)
-* Gnosis-Mock: [https://github.com/gnosis/mock-contract](https://github.com/gnosis/mock-contract)
-* Truffle Assertions: [https://github.com/rkalis/truffle-assertions](https://github.com/rkalis/truffle-assertions)
-* Eth gas reporter: [https://github.com/cgewecke/eth-gas-reporter](https://github.com/cgewecke/eth-gas-reporter)
-* Leapdao Solidity-Coverage: [https://github.com/leapdao/solidity-coverage](https://github.com/leapdao/solidity-coverage)
-* Original Solidity-Coverage: [https://github.com/sc-forks/solidity-coverage](https://github.com/sc-forks/solidity-coverage)
-* Slither: [https://github.com/crytic/slither](https://github.com/crytic/slither)
-* Mythril: [https://github.com/ConsenSys/mythril](https://github.com/ConsenSys/mythril)
-
-## Fluidity Resources:
-* Website: [https://fluidity.io](https://fluidity.io)
-* Twitter: [https://twitter.com/fluidityio](https://twitter.com/fluidityio)
-* Facebook: [https://facebook.com/fluidityio/](https://facebook.com/fluidityio/)
-* LinkedIn: [https://linkedin.com/company/fluidityio/](https://linkedin.com/company/fluidityio/)
-* YouTube: [https://youtube.com/c/fluidityio](https://youtube.com/c/fluidityio)
-* Blog: [https://medium.com/fluidity](https://medium.com/fluidity)
-
-
diff --git a/src/blog/drizzle-150-a-new-beginning/index.md b/src/blog/drizzle-150-a-new-beginning/index.md
deleted file mode 100644
index af77107ca..000000000
--- a/src/blog/drizzle-150-a-new-beginning/index.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Drizzle 1.5.0 - A new beginning
-hide:
-  - navigation
----
-
-<figure>
-  <img src="/img/blog/drizzle-150-a-new-beginning/sunrise.jpg" alt="Sunrise landscape" style="width:100%">
-  <figcaption style="text-align: center;">_The dawn of a new era for regular releases and a better contributor experience_</figcaption>
-</figure>
-
-Since the beginning, our goal here at Truffle has been to make dapp development as easy as it can be. To this end Josh Quintal created [Drizzle](https://github.com/trufflesuite/drizzle), a managed Redux store to make interfacing with the blockchain just a little bit easier.
-
-## From many to one
-
-Today, we are announcing that we are moving to a monorepo. From now on, a single PR can be used to update code and documentation that used to span multiple repos.
-
-Over the last two years, we’ve developed libraries on top of Drizzle such as `drizzle-react` and `drizzle-react-components`. Since these libraries depend so heavily on each other, it only makes sense for us to move all of these packages to a monorepo to streamline any updates.
-
-In addition, we now also have an experimental Vue.js plugin that fits naturally into the monorepo architecture. It is very likely that going forward we will develop new packages to aid the Drizzle ecosystem in this manner.
-
-## Scoped package names
-
-Another big change we are making is towards scoped package names on NPM. This means that instead of:
-
-```
-drizzle
-drizzle-react
-drizzle-react-components
-drizzle-vue-plugin
-```
-
-We will now have:
-
-```
-@drizzle/store
-@drizzle/react-plugin
-@drizzle/react-components
-@drizzle/vue-plugin
-```
-
-From an organizational standpoint, this makes it a lot more intuitive to manage your dapp development.
-
-## Testing
-
-Prior to the monorepo, testing our libraries together was a slow, error-prone and painful experience. Our maintainers had to build custom dapps to isolate changes and manually link packages together as well as coordinate with ganache for each front end.
-
-The monorepo allows us to have dedicated front end apps that automatically build against the latest libraries and we can conveniently orchestrate them with a single ganache instance in just a couple commands. In other words, you can easily spin up three apps to test various aspects of the monorepo [in seconds](https://github.com/trufflesuite/drizzle/blob/develop/README.md#testing-and-debugging-with-ganache).
-
-<figure>
-  <img src="/img/blog/drizzle-150-a-new-beginning/test-ui.png" alt="Test UI instances" style="width:100%">
-  <figcaption style="text-align: center;">_Easily spin up real front ends to test that dapps can work with the current code_</figcaption>
-</figure>
-
-## Better release strategy
-
-Perhaps the biggest thing that the changes above allow us to do is more frequent releases.
-
-In the past year, we often had to deal with delaying the publishing of a new change because it required testing and updating other repos. Our publishing process was essentially being blocked by having to synchronize changes amongst multiple repos.
-
-With a monorepo, that all changes, which means that you can look forward to more regular releases and a faster turnaround time for getting issues fixed. Better changelogs are also coming as we move toward adopting [conventional commits](https://www.conventionalcommits.org) for each PR that gets merged.
-
-## Going forward
-
-It’s important to note that Drizzle wouldn’t be what it is without the open source community. A big part of why we are making all these changes is because we need you to help us make Web3 a reality together.
-
-Here at Truffle, every member on the team is passionate about improving the developer experience of building on Web3. In the upcoming weeks, we will be doing more regular blog posts targeting the front end space so keep an eye out!
-
-I would also like to specifically thank Amal Sudama for his work on making this transition. It certainly couldn’t have happened without him.
diff --git a/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md b/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
deleted file mode 100644
index 0dffda153..000000000
--- a/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Drizzle - Reactive Ethereum Data for Front-ends
-hide:
-  - navigation
----
-
-Today we're proud to announce the addition of a new product to the Truffle Suite: Drizzle. Drizzle is a collection of front-end libraries that make writing dapp front-ends easier and more predictable.
-
-The core is based on a Redux store. We take care of synchronizing your contract data, transaction data and more. Things stay fast because you declare what to keep in sync. Importantly, this means you have access to the spectacular development tools around Redux. **Want to time travel through your recent transactions? You can do that with a slider.**
-
-  <video width="640" height="480" controls>
-    <source src="/img/blog/drizzle-some-chaindata-on-your-ui/drizzle-time-travel.mp4" type="video/mp4">
-    Your browser does not support the video tag.
-  </video>
-
-Drizzle's architecture is completely modular. This means you never lose access to the underlying web3 functionality you already know--drizzle as much or as little as you like. We've created two packages for use with React, but the core functionality is contained in the base `drizzle` module itself. If you're familiar with Redux, it's not a stretch to create an Angular library or use it for something other than a webapp.
-
-  ![Drizzle Modules](/img/blog/drizzle-some-chaindata-on-your-ui/drizzle-modules.png)
-
-Want to dive in right away? `truffle unbox drizzle` and you've got a full example dapp. Need more info? Read on!
-
-## The Libraries
-
-### Drizzle
-
-The core library responsible for web3, account and contract instantiation; wiring up the necessary synchronizations and providing additional contract functionality.
-
-[GitHub Repo](https://github.com/trufflesuite/drizzle)
-
-### Drizzle React
-
-Provides a DrizzleProvider component and drizzleConnect helper method to make it easier to connect Drizzle with your React app.
-
-[GitHub Repo](https://github.com/trufflesuite/drizzle-react)
-
-### Drizzle React Components
-
-A library of useful components for common dapp functions. Currently includes:
-*   `LoadingContainer`: Wraps your app, ensuring it waits for web3 and contract instantiation and displays relevant feedback if something goes wrong.
-*   `ContractData`: Displays contract call output.
-*   `ContractForm`: Automatically generates a form for contract transactions.
-
-[GitHub Repo](https://github.com/trufflesuite/drizzle-react-components)
-
-## The Box
-
-Shown in the video above, this box makes use of all of Drizzle's libraries in a finished example dapp.
-
-[GitHub Repo](https://github.com/truffle-box/drizzle-box)
-
-**Help us grow this baby!** What do you want to see from Drizzle? More components? More options? To put it another way: what are you sick of doing on the front-end?
-
-![Drizzle Baby](/img/blog/drizzle-some-chaindata-on-your-ui/baby.jpg)
-
-We're excited to hear your feedback and can't wait to see what you'll build! 
-
--- Josh & the Truffle Team
diff --git a/src/blog/drizzle-vue-a-truffle-story/index.md b/src/blog/drizzle-vue-a-truffle-story/index.md
deleted file mode 100644
index e81676840..000000000
--- a/src/blog/drizzle-vue-a-truffle-story/index.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Drizzle Vue - A Truffle Story
-hide:
-  - navigation
----
-
-![Drizzle + Vue = <3](/img/blog/drizzle-vue-a-truffle-story/title-image.png)
-
-Truffle is an organization that maintains a balance of transparency, mentorship, encouragement, inclusivity and humor that I'm thankful for everyday. While much could be written about Truffle's management culture, I want to share my experience of working on a side project here.
-
-Our remote work setup and the openness of our team contributes to a healthy and productive environment. The ability to schedule zoom sessions to brainstorm and discuss ideas fits well with our schedule. Every member contributes to this culture being generous with their time and knowledge. I'm happy and inspired to see team members grow as developers through the subtle mentorship as a result of our culture.
-
-For most of my career, I dreaded mandatory soul draining review type meetings, but at Truffle, I look forward to the incredibly productive and creative weekly one-on-ones I have with Joshua Quintal, our Product Lead. Josh originally developed Drizzle and we often discuss its role in the dapp ecosystem, issues and roadmap during our meetings.
-
-## About Drizzle
-
-Drizzle is a Smart Contract Store with a subscription and mutation API that abstracts away the boilerplate for reading and writing smart contract state as well as listening for contract events.
-
-Drizzle originated as a helper library for a React project Josh was developing. However he came to realize that the Smart Contract Store was an important piece needed in dapp development as applications start to scale. In Web 2.0 the need to manage and reason about state at scale has led to libraries like [1] [Redux](https://redux.js.org/introduction/prior-art). Similarly, we want to give web 3.0 dapp developers these best practices to leverage as their applications grow in complexity.
-
-## Drizzle's Unintended Front End Frameworks Exclusion
-
-Unfortunately, this is not how Drizzle is understood by developers we interviewed formally and informally. The most common misunderstanding is that Drizzle is coupled with React, the most popular JavaScript front end framework. We can't blame our community as most of our documentation focuses on implementing Dapps using React.
-
-Drizzle was initially released with bindings only for React which created this misperception that excluded developers from utilizing other front end frameworks such as Vue and Angular.
-
-The problem is that we didn't offer an easy solution for Vue or Angular and our documentation doesn't offer guidance. We want to change this! We want to support all the frameworks!
-
-## A Vue Plugin Side Project
-
-I felt this was an important problem to solve in order to improve the dapp developer experience.  It was important to get Drizzle working for Vue. Unfortunately, I knew nothing about Vue. In previous organizations I was a part of, I would have shied away from pursuing this project. However, at Truffle I felt comfortable and empowered to champion the idea. Josh encouraged me to spend the time needed to study Vue and experiment with the concepts.
-
-The basic plan was to:
-- Use Vuex, Vue's popular State management plugin
-- Transform Drizzle's redux store to be consumed by Vuex
-  - A redux store as an [2] [Observable](https://redux.js.org/api/store#subscribe) which would allow us to transform/map drizzle state to a more state pieces that Vuex could consume.
-  - This would allow us to have more efficient UI renders by using RxJS techniques like `distinctUntilChanged`
-- Create basic Vue components mimicking drizzle-react-components
-  - Vue's architecture allows us to use the adaptor as a datasource as well as provide basic support for Components that can render the data. This gives Vue developers to use our basic Components to make quick proof of concepts, and the flexibility to create richer Components when they need to.
-
-A [3] [basic proof of concept](https://github.com/trufflesuite/drizzle-vue-plugin) eventually surfaced and I was happy with the outcome as it showed a path forward to Angular using this approach with RxJS and can't wait to test it out!
-
-## Collaboration And Improvements
-
-Another aspect of Truffle's culture is to promote collaboration and exchange ideas with our community, and meet like minded developers and advocates working on similar problems. We're encouraged to go to meetups and be advocates for this incredible space.
-
-I reached out to Julien Klepatch on reddit after seeing his impressive [4] [Drizzle overview video](https://www.youtube.com/watch?v=QH_yLPYQEs4&feature=youtu.be) and asked for his feedback on the Vue Plugin. His participation, code contribution, code review and feedback clarified the project's direction and generally improved the codebase. Furthermore, he created 3 videos to explain the new plugin.
-- [5] [Drizzle Vue Plugin: overview](https://www.youtube.com/watch?v=XaVEZ1ucxac)
-- [6] [Drizzle Vue Plugin: Custom Components](https://www.youtube.com/watch?v=ApJwXfWKl7Q)
-- [7] [Drizzle Vue Plugin: Events](https://www.youtube.com/watch?v=xyoztqeYd6U)
-
-We also run a range of educational programs as part of Truffle University, that amongst other things, teaches developers how to use our full suite of tools. As part of the experience, students are mentored by the team and are encouraged to contribute to open-source projects, such as the Truffle Suite itself. James Kehoe, a developer in our first cohort, uses Vue on a daily basis and took an interest in the plugin. He took the initial design of the Contract Event Logic and turned it into idiomatic Vue. James also improved the documentation and introduced testing to the project. I learned a lot about Vue pairing with James, and look forward to future sessions with him.
-
-## Take A Preview
-
-You can preview the [3] [Plugin](https://github.com/trufflesuite/drizzle-vue-plugin) before we officially release it. Be sure to check out Julien's videos for an excellent walkthrough: [5] [Drizzle Vue Plugin: overview](https://www.youtube.com/watch?v=XaVEZ1ucxac), [6] [Drizzle Vue Plugin: Custom Components](https://www.youtube.com/watch?v=ApJwXfWKl7Q) and [7] [Drizzle Vue Plugin: Events](https://www.youtube.com/watch?v=xyoztqeYd6U)
-
-This project happened because of Truffle's enabling and supportive culture. Truffle is cool like that!  Also, co-MVPs James and Julien's improved the Vue Plugin and made it a viable tool. In fact, I consider them to be original contributors and am happy to see their continued involvement in the project.
-
-Come meet the team and learn about our tools at TruffleCon. We're looking forward to meeting you all!
-
-
-## References
-1. https://redux.js.org/
-1. https://redux.js.org/api/store#subscribe
-1. https://github.com/trufflesuite/drizzle-vue-plugin
-1. https://www.youtube.com/watch?v=QH_yLPYQEs4
-1. https://www.youtube.com/watch?v=XaVEZ1ucxac
-1. https://www.youtube.com/watch?v=ApJwXfWKl7Q
-1. https://www.youtube.com/watch?v=xyoztqeYd6U
diff --git a/src/blog/ethereum-gas-exactimation/index.md b/src/blog/ethereum-gas-exactimation/index.md
deleted file mode 100644
index 87288056f..000000000
--- a/src/blog/ethereum-gas-exactimation/index.md
+++ /dev/null
@@ -1,175 +0,0 @@
----
-title: Ethereum Gas Exactimation
-hide:
-  - navigation
----
-
-In Ethereum, estimating gas for a given transaction is a tricky problem to solve (especially when attempting to maintain [EIP-114](https://github.com/ethereum/EIPs/issues/114) compliance). Most of the well-known Ethereum implementations like Geth<sup>¹</sup> and Parity<sup>²</sup> use interval halving (binary search) to estimate gas by running transactions through the EVM until an approximate estimation converges.
-
-![Ganache Logo](/img/ganache-logo-h-dark.svg)
-
-At [Truffle](/), we decided such an approach was an unnecessarily CPU-intensive solution to the problem and set out to find a (theoretically) more performant and perfectly accurate way of estimating gas. The result? [Gas exactimation](https://github.com/trufflesuite/ganache-cli/releases/tag/v6.4.2). In this tutorial, we’ll go over gas exactimation at a high level in order to demonstrate its precision.
-
-**Complete example available at [the following repo](https://github.com/trufflesuite/gas-exactimation-tutorial).**
-
-**_Prerequisites: You should be familiar with Truffle, Ganache, and Solidity. If you need an introduction please consult the following resources:_**
-
-* [Truffle Quickstart](/docs/truffle/quickstart)
-* [Ganache Quickstart](/docs/ganache/quickstart)
-* [Solidity Documentation](https://solidity.readthedocs.io/en/v0.5.9/index.html)
-
-## EIP-114, or the “1/64ths rule”
-
-[EIP-114](https://github.com/ethereum/EIPs/issues/114) mandates that certain stackdepth-creating opcodes _withhold_ 1/64th of remaining gas from the stack they create. In practice this means:
-
-1. The gas required for a successful transaction can be greater than the actual gas spent (similar to how gas refunds behave).
-2. The extra gas required for a successful transaction varies depending on the transaction’s initial `gas` amount.
-
-A long-standing issue with [Ganache](/ganache) has been the fact that we haven’t returned EIP-114 compliant gas estimations. This has caused our gas estimates to be too low in cases where a transaction executed certain opcodes. **Gas exactimation** addresses this by considering how the gas withheld at any nested stack depth/frame affects the gas needed outside of its execution context.
-
-Let’s see it in action.
-
-## Create a New Truffle Project
-
-We will use `truffle init` to create a new Truffle project and then wire up an example [Solidity](https://solidity.readthedocs.io/en/v0.5.9/index.html) smart contract and test script.
-
-```shell
-// In a new project directory...
-$ truffle init
-```
-
-## Setup an Example Smart Contract
-
-With our new project initialized, we will create an example file: `ContractFactory.sol`.
-
-```shell
-$ touch ./contracts/ContractFactory.sol
-```
-
-Our file will have two contracts, `Contract` and `ContractFactory`. `ContractFactory` will have the method `createInstance` that we will use to create a new empty `Contract`.
-
-```
-// ./contracts/ContractFactory.sol
-pragma solidity ^0.5.0;
-
-contract ContractFactory {
-  function createInstance() public {
-    new Contract();
-  }
-}
-
-contract Contract {
-  constructor() public {}
-}
-```
-
-Note the `new` keyword being used to create a new `Contract`. A valid statement containing the `new` keyword gets compiled to bytecode containing the `CREATE` opcode which is subject to the [EIP-114](https://github.com/ethereum/EIPs/issues/114#issue-160782694) 1/64th gas withholding.
-
-## Write a Test Case
-
-Next, we will write a `ContractFactory` test case.
-
-```shell
-$ touch ./test/ContractFactory.js
-```
-
-This test case will deploy `ContractFactory` to a Ganache test network and use a gas estimate provided by Ganache to create a new `Contract`.
-
-```
-// ./test/ContractFactory.js
-const ContractFactory = artifacts.require("ContractFactory");
-
-contract("ContractFactory", () => {
-  it("...should deploy and successfully call createInstance using the method's provided gas estimate", async () => {
-    const contractFactoryInstance = await ContractFactory.new();
-
-    const gasEstimate = await contractFactoryInstance.createInstance.estimateGas();
-
-    const tx = await contractFactoryInstance.createInstance({
-      gas: gasEstimate
-    });
-    assert(tx);
-  });
-});
-```
-
-## A Quick Check
-
-Before we run our test, we’ll download the most recent version of Truffle that uses Ganache _before_ gas exactimation.
-
-```shell
-// In the project directory...
-$ npm i truffle@5.0.13
-```
-
-And we’ll make sure we have the latest version of Truffle installed globally that uses Ganache _with_ gas exactimation.
-
-```shell
-$ npm i -g truffle
-```
-
-## Testing Before and After
-
-```shell
-$ npx truffle test
-...
-...
-Error: Returned error: VM Exception while processing transaction: revert
-```
-
-And when we use gas exactimation...
-
-```shell
-$ truffle test
-...
-...
-Contract: ContractFactory
-
-✓ ...should deploy and successfully call createInstance using the method's provided gas estimate (130ms)
-
-1 passing (143ms)
-```
-
-!!!!
-
-## Testing Exactimation
-
-But is gas exactimation actually _exact_? 🤔
-
-We’ll open our test file and subtract exactly a single unit of gas from the `gasEstimate` before sending our test transaction.
-
-```shell
-// ./test/ContractFactory.js
-const ContractFactory = artifacts.require("ContractFactory");
-
-contract("ContractFactory", () => {
-  it("...should deploy and successfully call createInstance using the method's provided gas estimate", async () => {
-    const contractFactoryInstance = await ContractFactory.new();
-
-const gasEstimate = await contractFactoryInstance.createInstance.estimateGas();
-
-const tx = await contractFactoryInstance.createInstance({
-      gas: gasEstimate - 1
-    });
-    assert(tx);
-  });
-});
-```
-
-Running our test again against Ganache with gas exactimation...
-
-```shell
-$ truffle test
-...
-...
-Error: Returned error: VM Exception while processing transaction: revert
-```
-
-Exactimation confirmed 🚀.
-
-
-Note: Since the initial release of gas exactimation, an even more performant iteration of the algorithm is currently in review here.
-
-[1]: [https://github.com/ethereum/go-ethereum/blob/master/accounts/abi/bind/backends/simulated.go#L267](https://github.com/ethereum/go-ethereum/blob/master/accounts/abi/bind/backends/simulated.go#L267)
-
-[2]: [https://github.com/paritytech/parity-ethereum/blob/master/ethcore/src/client/client.rs#L1658](https://github.com/paritytech/parity-ethereum/blob/master/ethcore/src/client/client.rs#L1658)
diff --git a/src/blog/first-ever-truffle-retreat/index.md b/src/blog/first-ever-truffle-retreat/index.md
deleted file mode 100644
index 4dbe4d958..000000000
--- a/src/blog/first-ever-truffle-retreat/index.md
+++ /dev/null
@@ -1,127 +0,0 @@
----
-title: Our First Ever Truffle Retreat
-hide:
-  - navigation
----
-
-![Truffle](/img/blog/first-ever-truffle-retreat/medium-truffle-retreat.jpg)
-
-This past summer, the Truffle team got together to together to define our roles, our mission statement, and our product roadmap - and had some fun in the process.  
-
-----------
-
-The Truffle team is fully remote. This has a lot of advantages in that it allows for a wide range of people available to work on your project; but it can also make it difficult to get to know your coworkers. 
-
-I started Truffle in early 2015 as the sole developer, and it stayed that way for nearly a year and half. John McDowell joined in late 2016, and by the time of the retreat we happily brought Nick D’Andrea and Josh Quintal on board. All interviews happened over Skype.
-
-I live in Yakima, Washington. John lives in Victoria, British Columbia. Nick lives in Philadelphia, and Josh lives in Detroit. That’s a lot of distance between us. 
-
-![Truffle employees in September](/img/blog/first-ever-truffle-retreat/truffle-map-01.jpg)
-
-When we brought Nick and Josh onto the team, it became obvious that we needed to meet up in person to solidify our roles, define responsibilities, and establish our own culture before growing the team even larger. 
-
-And we wanted to hang out in the woods, at the top of a mountain, and get to know each other. 
-
-## The Location
-
-![View from the house](/img/blog/first-ever-truffle-retreat/location.jpg)
-
-We had our retreat near Victoria, BC where John lives. Nick, Josh and I traveled all day through a series of planes, ferries and car rides to finally arrive at the house around 7 pm. The house sits atop a large hill in Braemer Heights overlooking all of Victoria, and on a good day has a beautiful view of Mt. Baker in the States. 
-
-The house was the definition of excess for a team of four, especially with only three of us sleeping there. It had five bedrooms and four bathrooms; a deck with a grill; three stories, the topmost containing only an office with 360-degree windows; and loads of wildlife. Unexpectedly, it was only ten minutes away from a Costco, which helped immensely. Even more unexpectedly, this mansion cost us less than three hotel rooms and a coworking space.  
-
-![Another view](/img/blog/first-ever-truffle-retreat/mountain.jpg)
-
-## The Work
-
-I had a few specific goals for our retreat: to define everyone’s roles and responsibilities within our team, to define our product roadmap for the next six months, and to create a mission statement for Truffle that our whole team could rally behind. 
-
-### Retrospective
-
-We started with a retro. We wanted to evaluate where we were as a team before deciding where we wanted to go in the future.
-
-So on Tuesday morning, we sat down and gave praise for what we’ve done well and identified areas where we could improve. I brought a list of business areas that are important for Truffle -- things like development, technical leadership, branding, marketing, etc. -- and we graded ourselves on each of them. 
-
-This turned out to be an interesting exercise. As the leader of the team you want to say “we’re doing great”, and not diminish anyone’s efforts -- because, it’s true, we’ve come far for a small team. However, we need to know where we can improve and how different areas of our company, teamwork and products stack up to the rest. In general, we all seemed to agree on the results: Branding and growth have been stellar (e.g., we have a good product that people like to use), but more external communication -- like our technical leadership, our relationship with the Ethereum Foundation, and relationships with some of our VIP users -- could use some improvement. Though these results were mostly subjective judgements, the conversations that resulted helped inform discussions about our roles and future roadmap. 
-
-### Roles & Responsibilities
-
-The Truffle team had already doubled in size in 2017, and right before the retreat two new team members -- Ben Burns and Mike Pumphrey -- had accepted offers (welcome!). So we knew we had some work to do regarding defining our roles and how we work together as a team.
-
-Before the retreat, I had met separately with Nick, Josh, and John to evaluate how they felt about their current roles at Truffle. We each talked about what they wanted to do both within the team and professionally, and how I could help them get there. Then we used this time at the retreat to reorganize the work so that it aligns with each team member’s personal goals as well as the group’s goals. We created a new org chart and chain of command, including the new team members we knew were coming on. 
-
-We decided that Josh and John would share design responsibilities for our website, logo design and general aesthetics for all of our products. Ben, who started in October, would take on the internals of the TestRPC (now [Ganache](/ganache/)) and related products ensuring we stay up to date with the Ethereum ecosystem. And Mike would be coming on board to wrangle all of our documentation and learning content, eventually molding it into tailored courses we’d offer to individuals and businesses. 
-
-That just left Nick and I. Though we both knew Nick would work on the internals of Truffle when he was hired, we didn’t know the extent of the work required; in addition to improving Truffle, Nick would be burdened with the arduous task of softly and lovingly ripping my baby from my arms. That is, Truffle’s my baby, and I’ve been nurturing it from day one. In order to build a more functional and growing team, it became clear I’d have to let go of the internal implementation details and focus more on our business and our product, leaving Nick to explore the tool’s technical way forward.
-
-This transition has been a great growing experience already, both professionally and personally. We’ll continue to evaluate this structure over the next six months to see how it works out. 
-
-### Mission Statement
-
-The next step was to determine why we’re here. The big three questions were: Why are you here? What do you value? And what do you stand for? The point was to elicit each team member’s value systems to get a big picture of what it is we really care about. 
-
-My original plan for this session was to put each person on the spot and ask them those questions directly. As it turns out, this interrogation technique was not the best way to get meaningful, genuine answers from the team. 
-
-Luckily, John came up with a better plan. He suggested we have each member of the team write their values on six index cards, and then have the whole team talk about each other’s values, create a big list, and vote on them to determine our company values. 
-
-![Our values](/img/blog/first-ever-truffle-retreat/mission.jpg)
-
-The conversation helped us all understand how different we were, and how much our values varied. We expressed everything from receiving good pay to building the distributed ecosystem. 
-
-In the end, we all agreed why we’re here. Our new mission statement: 
-
-> _Truffle builds useful tools for the next generation of blockchain technologies. We enable the growth of the Ethereum and open source communities, help to improve the role of decentralization in society, and empower developers to achieve their goals._
-
-### Product Roadmap
-
-On Thursday, we got into the details of what we’ve been working on at Truffle and where we’re going. This included presentations for new products [SPOILER ALERT!] and discussions about specific features. We’ve been hard at work since we drafted this post, so some you may have heard of already: 
-
-* [Truffle 4.0!](https://github.com/trufflesuite/truffle/releases) - with a debugger, improved development and testing experience, and more! 
-* [Ganache](/ganache) - a personal blockchain for developers. 
-* Drizzle - a frontend framework for React and Angular to easily connect Truffle-based projects.
-* Project Hotcakes - a full stack suite for web applications.
-* Live - a browser-based, interactive Truffle IDE.
-
-We also talked about revamping our development processes, which included not only how we work together as well as beefing up our continuous integration systems and making it very easy for users to contribute to Truffle projects. Stay tuned for more info!
-
-## The Fun
-
-In the middle of all of this work we wanted to get some bonding time in too. And if you haven’t been to Victoria, it really is gorgeous, and we couldn’t let this trip go to waste.
-
-So on Wednesday we got in John’s Honda Element and drove for two hours to Port Renfrew. The hike on paper: beach hike, sun, potentially bears, great outdoorsy time. The hike in reality: 
-
-![Rainy hike](/img/blog/first-ever-truffle-retreat/hike.jpg)
-
-We didn’t see any bears, and we got completely rained out of the hike. But, we also took our first Truffle team selfie: 
-
-![hashtag selfie](/img/blog/first-ever-truffle-retreat/team-pic.jpg)
-
-And eventually when the rain cleared got this cloudy-but-serene view from the dock at Port Renfrew.
-
-![A nice dock](/img/blog/first-ever-truffle-retreat/dock.jpg)
-
-
-And when we got back to the house, we made dinner, played board games, and drank a bunch of wine. 
-
-![Fooooood](/img/blog/first-ever-truffle-retreat/food-1.jpg)
-![Josh cooks](/img/blog/first-ever-truffle-retreat/food-2.jpg)
-
-
-So overall, we had some successful bonding time. 
-
-## Going Home 
-
-Being able to all be in the same room for the first time ever was extremely rewarding. It gave us a great foundation for the future of our working relationships and of Truffle as a whole, and increased our personal relationships in a way you don’t get when working 100% remotely. We’ll definitely be making retreats a recurring part of working at Truffle. 
-
-Now that we’re all back to work as usual, we’ve already taken the results of the retreat to heart. We’ve implemented our new development processes (info to come soon); revamped our products and offerings to be more in line with each other; have been settling into our new roles amazingly, and with little conflict; and overall we’ve been having a great time.
-
-There are a few things I want to make sure I remember coming out of this retreat: 
-
-**You can build more of a relationship with someone in 10 minutes in person than you can in 3 months on Slack.** I want to maintain this momentum and rapport. We’ve found that video calls are the closest you can get on a 100% remote team. Going forward, we’re now having one-on-one meetings every week to make sure we can keep up our rapport and ensure we’re giving each other consistent, useful feedback.   
-
-**The right processes and structures are the basis for responsibility, autonomy, and trust between teammates.**  During the retreat we collectively decided on rules and structure that would help us work better together. These rules were meant to increase responsibility and autonomy and provide a basis of trust in decision-making where each of us are responsible for our own individual specialties. I want to increase this trust and know that each team member can make the right decisions when needed.
-
-**Building rapport with your teammates is worth the effort.** In a remote team you don’t often get the chance to invite your coworker over for dinner or go to a local event. Bridging this gap is hard, and requires conscious effort, but has so many benefits including happiness, morale and general enthusiasm toward coming into work every day. I want to continue to bridge this gap and foster a culture where even if we’re a thousand miles away, we can still feel close enough to have each other over for dinner.
-
-Final thought: I’d eat Nick’s caprese salad and Josh’s sirloin medallions any day of the week.
-
diff --git a/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md b/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
deleted file mode 100644
index 954d59301..000000000
--- a/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Get a Bird's Eye View with Truffle Teams' New Dashboard
-hide:
-  - navigation
----
-
-<figure>
-  <img class="mb-4" src="/img/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/blog-header.jpg" alt="Truffle Teams Dashboard" style="width:100%">
-</figure>
-
-As the operational needs of your dapp grow in complexity, it helps to be able to choose an area of focus. More incoming data begets a greater need to gain insights and properly segment that data to prevent overload. Wouldn’t it be nice to see an overview of a particular deployed instance of your application with the ability to drill down into the parts you need to see in more detail? This is where the dashboard comes in!
-
-<p class="alert alert-warning">💬 The Dashboard feature could expand in many different directions and we need your help to prioritize what matters most for your dapps. In that spirit we’ve released this first version quickly to get the conversation started. Please comment in the <a href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA">Truffler Slack workspace</a>, <a href="mailto:info@trufflesuite.com">email us</a>, reach out any way you can--we’re excited to hear from you.</p>
-
-We first asked ourselves “what is a dashboard”? and surprisingly, got many different answers! We arrived at this definition: **A dashboard is a place to see an overview of your application, along with ways to drill down and get further context on more narrow slices.**
-
-The first release focuses mostly on the high-level, but we plan to increase the drilldown capabilities as the feature evolves.
-
-## A Bird’s Eye View
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/truffle-teams-dashboard.png" alt="Truffle Teams Dashboard" style="width:100%">
-  <figcaption class="text-center font-italic">The dashboard page with a deployment selected</figcaption>
-</figure>
-
-In this first version of the dashboard, you can pin a deployment for quick insights and visualization. Some of this information we haven’t surfaced before, such as the deployment’s cost and the number of unique addresses interacting with a deployment’s contracts.
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE NEW DASHBOARD</a>
-</div>
-
-## Looking Ahead
-
-Here’s a bit of a teaser for you to get an idea of where this is going:
-
-* A filter option to specify exactly which contracts are being displayed in the transaction graph
-* A list of contracts providing the ability to hop into monitoring a specific contract instance or...
-* Quickly interact with those contracts via our upcoming Contract Manager
-
-We strive for Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about this integration solution, and if your team has other needs we haven’t met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3 mb-4" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLE SLACK COMMUNITY</a>
-</div>
-
-Thanks!
-_Josh Quintal, Head of Product & Marketing_
\ No newline at end of file
diff --git a/src/blog/github-repository-moved/index.md b/src/blog/github-repository-moved/index.md
deleted file mode 100644
index 0cb7e7d8e..000000000
--- a/src/blog/github-repository-moved/index.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: We've moved our github repo!
-hide:
-  - navigation
----
-
-We recently released [Truffle 3.0](https://github.com/trufflesuite/truffle/releases/tag/v3.0.2) in February to [much fanfare](/dashboard). As part of that release we separated our codebase into multiple different modules to make integrating with Truffle easier. Those modules now live in the github repository [https://github.com/trufflesuite](https://github.com/trufflesuite), which hints at our broader mission of providing a comprehensive suite of tools for Ethereum development.
-
-## But something was missing...
-
-We forgot Truffle! The main Truffle repository -- including the Truffle command line tool -- remained at it's old [Consensys](https://github.com/consensys) location while its modules hung out at their new digs. We thought to ourselves: That just wouldn't do. So, as matter of announcement, Truffle has officially moved. It's new home is [https://github.com/trufflesuite](https://github.com/trufflesuite).
-
-
-## Wait, there's more.
-
-The [Truffle Suite](https://github.com/trufflesuite) repository will soon be filling up with more open-source tools to make your Ethereum development life easier. We're not ready to announce what those are yet, but stay tuned for some awesome announcements in the coming weeks.
-
-## While you're here.
-
-While we're announcing things, we should let you know we have a new Twitter account: [@trufflesuite](https://twitter.com/trufflesuite). Feel free to reach out to use there for all your Truffle needs.
-
-Au revoir for now!
-
--- Tim
diff --git a/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md b/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
deleted file mode 100644
index eba5df74e..000000000
--- a/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: How Ethical Advertising Will Transform the Blockchain Industry
-hide:
-  - navigation
----
-
-![GitCoin](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/pasted image 0-5.png)
-
-*CodeFund is an ethical ad platform that funds contributors to the open source ecosystem. Visit [CodeFund](https://codefund.io/) to learn more and apply.*
-
-### The Conflicting Relationship Between Blockchain and Marketing
-In the initial years following Bitcoin’s inception, most blockchain companies didn’t need paid advertising. The early adopters were a community of cypherpunks, libertarians, developers, miners, and hobbyists, that truly believed in the power of decentralized networks. To them, adoption was inevitable, and rather than putting paid ads in front of the general public, resources were better spent building wallets, development tools, infrastructure, and scalability solutions.
-
-Additionally, almost all early blockchain users and entrepreneurs were extremely privacy-conscious. Pseudonymity is a key component to cryptocurrencies, they wouldn’t work in a permissionless manner without it. The Adtech industry, on the other hand, is run by monolithic centralized powerhouses that gather and store immense amounts of personal data for precise targeting. For the first 5 years of Bitcoin, **the blockchain community ethos was quite literally the polar opposite of the advertising industry**.
-
-That’s not to say that in the early days exchanges, wallets, and other blockchain services were unable to run successful marketing campaigns. However, the community was generally so niche that most users had a good sense of what they were looking for. The famous cliche, “If you build it, they will come” is frequently repeated in this space. While it was arguably true for Bitcoin, the internet, and certain decentralized protocols, the data shows that marketing is often crucial for launching a business or community built on top of these networks.
-
-
-
-![Blockchain thought leaders Anthony Pompliano and Ryan Selkis share differing views on marketing](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-1.jpg "Blockchain thought leaders Anthony Pompliano and Ryan Selkis share differing views on marketing")
-
-Following the launch of Ethereum, the rise of smart contracts, and the ICO mania, things changed. All of a sudden it was relatively easy for startups to launch their own token and rake in millions with a whitepaper. As a result, marketing budgets began to skyrocket and paid campaigns were everywhere due to the (seemingly) huge potential for capital accumulation.
-
-While some genuinely revolutionary ideas were started and funded during this time, the vast majority were subpar projects and outright fraudulent scams preying on naive users. At one point [Coinmarketcap](https://coinmarketcap.com/), a fairly well-regarded website in the crypto space, was showing ads for [Bitconnect](https://en.wikipedia.org/wiki/Bitconnect), a known Ponzi scheme.
-
-![Example 2](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-2.jpg)
-
-As a result, most mainstream ad providers like Google and Facebook banned all ads pertaining to crypto. Some people in the blockchain industry thought this was unfair, but it was for good reason. Scammy projects were ruining the public perception of blockchain technology. However, reputable companies were also caught in the crossfire, finding it increasingly difficult to advertise their projects. Notably, Mailchimp’s blockchain ban impacted a project I was working on along with plenty of other startups. I remember when [Evan Van Ness](https://twitter.com/evan_van_ness)’ twitter and [Week in Ethereum](https://www.weekinethereum.com/) newsletter (my favorite Ethereum educational resource) were shut down [multiple times](https://cointelegraph.com/news/breaking-mailchimp-reportedly-shuts-down-accounts-related-to-crypto-prices-drop).
-
-![GetCoin image 3](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-3.jpg)
-
-So, what’s the solution? Fortunately, the majority of mainstream advertising services have relaxed their bans on blockchain advertising in the face of a maturing ecosystem. This is especially interesting when considering that both [Google](https://www.bloomberg.com/news/articles/2018-03-21/google-is-said-to-work-on-its-own-blockchain-related-technology) and [Facebook](https://libra.org) have announced their foray into the industry.
-
-### Existing Blockchain Advertising Obstacles
-
-We recently released a [blog post](https://codefund.io/blog/how-to-advertise-your-startup-blockchain-project) covering a variety of different free and paid channels to advertise your blockchain startup. And although there are more options than ever, there are still several obstacles to overcome. As we appear to be approaching the next bull market, scams will undoubtedly come back (I’ve already seen a huge uptick in the “free crypto” scams on twitter). Further, the crypto ecosystem hasn’t addressed the problems of mass data collection and rampant user profiling in the Adtech world. Most of us believe blockchain will be the catalyst for a revolution of privacy and self-sovereign identity, hopefully breaking up the big data monopolies of web2. Yet **the entrepreneurs and thought leaders pushing this narrative of individual autonomy and privacy in the digital age are still using advertising services that track, profile, and collect mass amounts of data from their target markets.** Marketing is inevitable - startups need to reach their desired audience and grow a user base. But can this be done in a more ethical way, in line with the ethos of this technology we love and support?
-
-### Enter: CodeFund
-
-While all of this craziness was happening in the blockchain world, [Eric Berry](https://twitter.com/coderberry) was focused on tackling a different problem: [The Open Source Conundrum](https://codefund.io/blog/the-open-source-conundrum-how-do-we-keep-the-lights-on). Open source software lays the foundation for the Internet as we know it and supports so much of our global business processes, yet comparatively receives very little support and funding. **How can we help open source projects and maintainers get consistent financial support?**
-
-Eric founded Code Sponsor [2 years ago](https://changelog.com/founderstalk/56), allowing companies to place small text-based sponsored messages on GitHub project READMEs to support open source software. Since then he’s been threatened with legal action, shut down, started again, rebranded to CodeFund, and eventually joined the [Gitcoin](https://gitcoin.co/) team at [ConsenSys](https://consensys.net/), who share the same mission: **get developers paid**.
-
-At [CodeFund](https://codefund.io/), we pride ourselves on showing ethical ads on developer websites, acknowledging and respecting individual privacy. This means that our ads do not track, use cookies, nor collect any data except for IP addresses and browser agents. We feel ads that track our browsing history and know our personal information are an invasion of privacy, and from our research, the majority of our user base feels the same way. So while we can't profile and target specific demographics and individuals, we can help you tailor your ads to the desired audience and display them on sites that your audience frequents with geotargeting. Users will see ads that they actually want to see without compromising their data, browsing history, or personal information.
-
-CodeFund is 100% [open source](https://github.com/gitcoinco/code_fund_ads) (feel free to contribute! 😄) and was built by developers for developers, so we understand the motivations of our users. We keep our content relevant by only showing high-quality ads from companies that are of interest to the audience. We diligently vet all advertisers and publishers to make sure they are a good fit for the network. By understanding the community and showing them ads relevant to their interests, you build trust between your advertisers, publishers, and most importantly, users.
-
-The CodeFund model is a bit unorthodox in the Adtech world. However, we find it to be extremely successful in our niche (and growing) open source community. Developers are typically [much more likely](https://www.stackoverflowbusiness.com/engagement/resources/the-state-of-developer-engagement-2018) to use ad blockers compared to typical Internet users. Developers are also known to be more concerned about privacy and data collection. For these reasons, they can often be hard to reach with advertising. To get your message seen, you need reputable publishers who are trusted by their audience. CodeFund is bound by the standards set by [acceptable ads](https://acceptableads.com/en/about/criteria), which means many ad blockers do not block us. We work with our users to allow our ads and make sure they are relevant to the audience, ensuring all parties involved are benefiting.
-
-![CodeFund growth by impressions, YTD](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-4.jpg "CodeFund growth by impressions, YTD")
-
-We believe the future of the web will be a **privacy-focused, user-driven evolution**. More scandals are emerging from large corporations revealing data mismanagement, leaks, and hacks of sensitive information. Digital advertising will never go away, but the average internet user is becoming more security and privacy conscious, and we think this will lead to an increased demand for ethical advertising products. That's why we built a platform to allow advertisers to get their message to the right audience without compromising user integrity.
-
-### Ethical Ads for Blockchain - Why Target Crypto Users?
-
-Initially CodeFund was not focused on the blockchain space, however, since [joining Gitcoin](https://medium.com/codefund/code-sponsor-joins-gitcoin-b7d35966b93d), we’ve been [expanding](https://medium.com/gitcoin/codefund-ads-on-etherscan-fae1a3d35b51) our offerings. We realized that ethical advertising is going to play a crucial role in Web3, blockchain, open source, and the future of the Internet - and that's something we want to support.
-
-Blockchain technology was undeniably born out of the open source ecosystem. While the two communities are not exactly the same, they share many morals and have significant overlap. By nature, blockchain and cryptocurrencies would be useless if they were not open source. A key feature of *decentralized* cryptocurrencies is that there is no need to trust an intermediary and no barriers to entry. For it to work, anyone must be able to run, review, and contribute to the code. Today's leading blockchains are a cumulation of hundreds, if not thousands of individuals contributing to open source code bases.
-
-Just like most developers, blockchain users and enthusiasts tend to be much more privacy conscious than a typical Internet user. As a result, CodeFund's ethical ad model is a great fit, not only for blockchain developers but also for blockchain users.
-
-CodeFund ensures that the blockchain projects we work with are building applications and tools for open source blockchains, primarily for Ethereum. We don’t work with projects pumping their own token sales, instead, we partner with blockchain companies that are **adding value to society and the open source ecosystem**.
-
-### CodeFund’s Blockchain Offerings
-
-For the next few months, CodeFund will be actively building out our blockchain publisher and advertiser networks. We are currently publishing ads on [Etherscan](https://etherscan.io/), [State of the Dapps](https://www.stateofthedapps.com/), [Etherchain](https://www.etherchain.org/), [Decrypt Media](https://decrypt.co/), [Coingecko](https://www.coingecko.com/), and a handful of other high-quality blockchain websites - with even more in the pipeline. Decrypt just release a great [piece](https://wp.me/p9ZACC-1Vv) on the problems with crypto “news” sites, and their motivations for advertising ethically. Our advertisers like [Truffle](/truffle) are happy with their results so far and have seen high conversion rates from their campaigns, without sacrificing the privacy and integrity of their audience.
-
-![Decrypt’s ethical ad integration](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-5.jpg "Decrypt’s ethical ad integration")
-
-Crypto markets are beginning to turn around, more startups are shipping products, and the global blockchain community is growing. We expect this trend to continue, driving the demand for blockchain advertising as a result. Many blockchain websites publishing ads see it as a necessary evil – they need to keep the lights on to continue providing their services, but feel their choices are limited.
-
-The first option is working with companies to run direct advertising campaigns. However, this approach consumes time and resources and can be risky if advertisers pull out. The second option, and perhaps the easiest, is to use Google Ads or another incumbent service. Using this approach, many feel they’re compromising users’ privacy and trust. Moreover, outsourcing to huge Adtech giants is part of the problem that made ICO scams so rampant in 2018-2019. These companies simply have far too much traffic and lack the specialized skill set required to manually vet every single advertiser and identify blockchain scams. The last thing publishers want on their website is an ad that loses your users' money or promotes the purchasing of unregistered securities.
-
-At Gitcoin and CodeFund, we are a small team that has been in the blockchain world for years. We view every publisher and advertiser as a partner, diligently vet them, and hold them to the highest standards. **We’d like to see ethical advertising become the new standard in the blockchain space, and eventually on the Internet as a whole.**
-
-If your blockchain company is interested in advertising to a high-quality audience, or you would like to earn passive income showing relevant ads on your website without sacrificing your community’s privacy, CodeFund is for you! Apply now on the [CodeFund](https://codefund.io/) landing page and we’ll be in touch, or reach out to [connor@codefund.io](mailto:connor@codefund.io) for more information.
diff --git a/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md b/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
deleted file mode 100644
index 8b8072b09..000000000
--- a/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: How the Arrival of Web 3.0 is Transforming Traditional Business Models
-hide:
-  - navigation
----
-
-Although the Internet continues to drive digital transformation, the technology operates far beyond its original parameters. Since its inception over two decades ago, the web has been subject to increasing levels of centralization and mass surveillance. As a result, large corporations, governments, and media outlets remain the primary beneficiaries of an infrastructure meant to serve all of humanity. Herein lies the problem with the current Internet ecosystem, also known as Web 2.0.
-
-In the current online environment, users continually function as commodities, generating value along with their data. And while large entities should not shoulder the blame for their role in our everyday lives, their control over our personal information is cause for concern. As Internet founder Tim Berners-Lee [once said](https://www.vanityfair.com/news/2018/07/the-man-who-created-the-world-wide-web-has-some-regrets), "for people who want to make sure the Web serves humanity, we have to concern ourselves with what people are building on top of it."
-
-It is precisely this sentiment that drives the Web 3.0 movement. And although blockchain technology may be the foundation of this movement, the initiative is much broader. Web 3.0 is about building a decentralized infrastructure that protects individual property and privacy. But what exactly does this look like and what are the potential implications? In this article, we'll explore the evolution of Internet infrastructure and how the arrival of Web 3.0 is impacting existing business models.
-
-## The Evolution of Web Infrastructure
-
-The Internet debuted employing simplistic "read-only" technology, meaning users were only able to search for information and read it. This Web 1.0 environment was primarily intended for advertising purposes, acting as an extension of physical storefronts. With the arrival of "read-write" functionality, users of Web 2.0 are able to create their content and interact with the Internet in a far deeper capacity. By facilitating the prolific growth of social media platforms, blogs, and online reviews, this infrastructure continues to guide global business models.
-
-However, as mentioned, this era of robust growth has not come without consequences. Consumer protections continue to rank behind corporate interests as web surveillance fuels lucrative data collection. Continued [data breaches](https://www.nytimes.com/2018/08/01/technology/data-breaches.html) effectively highlight the downside of this arrangement. In response to these challenges, Web 3.0 initiatives aim to put power back into the hands of users. But before exploring how this will occur, it's crucial to understand the specific Web 3.0 characteristics that will facilitate this process.
-
-![Example 1](/img/blog/how-the-arrival-of-web3/web3-example1.jpg)
-
-## Characteristics of Web 3.0
-
-Although Web 3.0 is difficult to define in exact terms, it can be effectively broken down into unique components.
-
-### Semantic Web
-
-The [semantic web](https://www.w3.org/standards/semanticweb/) improves upon existing web infrastructure by generating, sharing, and connecting content based on an understanding of words. Rather than relying on keywords and numbers, search and analysis utilize context.
-
-
-![Source: The Semantic Web Stack
-Connectivity](/img/blog/how-the-arrival-of-web3/web3-example2.jpg)
-*Source: [The Semantic Web Stack
-Connectivity](https://devopedia.org/semantic-web)*
-
-Thanks to semantic metadata, Web 3.0 achieves greater connectivity. By leveraging all available information, the user experience dramatically improves.
-
-### Artificial Intelligence
-
-Web 3.0 technology can process information in a way similar to humans. As a result, platforms can better satisfy user needs through continuous learning.
-
-### 3D Capabilities
-
-Three-dimensional design is already in use on many Web 3.0 platforms. Computer games, e-commerce applications, and mapping software represent only a few potential use cases.
-
-### Ubiquitous
-
-In the decentralized Web 3.0 environment, all content is accessible by multiple applications, every device connects to the web, and the associated services are available everywhere.
-
-## Web 3.0 and Existing Business Models
-
-Although we have only just begun to explore the potential of Web 3.0 applications, their ability to upset the status-quo is undeniable. Of particular interest to many is how decentralized projects, operating in traditional industries, will up-end conventional revenue models. Through utilizing distributed, peer-to-peer platforms, some industries have begun to consider other funding options.
-
-![Example 3](/img/blog/how-the-arrival-of-web3/web3-example3.jpg)
-
-Although there is a vast array of revenue models to consider, we’ll explore some of the most prominent options here. To see the full list, check out the [Github repository](https://github.com/FEMBusinessModelsRing/web3_revenue_primitives/#revenue-share).
-
-### Revenue Share
-
-The revenue share model uses profits to enable separate actors to develop efficiencies or innovate in mutually beneficial ways, such as splitting earnings.
-
-#### Percentage Fee
-
-This model is where you take a percentage of each transaction executed on your platform. It remains a popular model with exchanges and marketplaces. The seller usually pays for the fee since they're the one that benefits from completing a sale on the platform.
-
-#### Income Share
-
-Using this model, users share earnings from another entity. An offline example would be a restaurant where the cashier shares the tips with everyone. In the context of Web 3.0, you could give a one-dollar tip in a coffee shop and split it with every actor in the coffee value chain with minimal transaction costs.
-
-### ICO’s
-
-Conducting an ICO is the process of selling project tokens all at once, or over some time. There are several ICO models and token variations that companies can use to raise funds.
-
-### Continuous Funding Models
-
-Continuous Funding Models are business models that sell ERC-20 tokens over time, rather than all at once.
-
-#### Curved Bonding
-
-Curved Bonding is a method of continuous funding that incentivizes early investment. In contrast to conventional ERC-20 token sales and ICO's, which feature each token being sold for the same price (no matter the time of purchase), such models hardcode buy prices according to an algorithmic curve. By purchasing early, investors get more tokens for the same price than if they are buying later. Ultimately, using Curved Bonding incentivizes early adopters to invest in a token.
-
-#### Continuous Organizations
-
-A continuous organization is one that sets up a Decentralized Autonomous Trust (DAT). This trust is an immutable smart-contract that implements curve bonding to automatically mint, burn, and distribute security tokens called FAIR securities. Organizations provide value to the trust by diverting part or all of their cash flow to it.
-
-### Streaming Money
-
-#### Side Channels
-
-A sidechain is a separate blockchain that is attached to its parent blockchain using a two-way peg. Using this model, you can move assets to the sidechain and then back to the parent chain. However, sidechains also need their miners. These miners receive an incentive through 'merged mining,' whereby two separate cryptocurrencies, based on the same algorithm, are mined simultaneously.
-
-#### State Channels
-
-State channels are mostly two-way pathways open between two users that want to communicate with each other in the form of transactions. Here, only the outcome needs to be included in the form of a single transaction on the main chain. Other transactions occur on off-chain.
-
-### The Future of Internet Infrastructure
-
-As the development of Web 3.0 technology persists, blockchain technology will remain a vital component of online infrastructure. Although the world continues to benefit from the transformative power of the web, user empowerment remains a priority among a growing segment of society. In a time when centralized institutions and governments exert control over personal data, many have begun to challenge the status quo.
-
-Those exploring this emerging subset of the web are well-positioned to benefit from growing momentum. By leveraging Web 3.0 technologies, companies also have the ability to enact new, potentially lucrative business models. Regardless of the industry, the new web presents an opportunity to pivot from traditional revenue streams in search of more optimal solutions. In the midst of ongoing innovation, it’s important to note that all new technology requires refinement - and Web 3.0 is only just beginning.
diff --git a/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md b/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
deleted file mode 100644
index 4cb75b39b..000000000
--- a/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: How to get your boss to send you to TruffleCon
-hide:
-  - navigation
----
-
-Last year [Truffle Suite](/) launched [TruffleCon](/trufflecon2019), an event designed for the Truffle community and those interested in building world-changing applications powered by decentralized technologies. The event was received with an overwhelmingly positive response. TruffleCon attracted 250 attendees, 53 speakers, and 2 locations. After such a successful inaugural event, the team immediately started planning an even bigger and better Trufflecon for 2019.
-
-Join us this year on August 2-4 at the Microsoft Campus in Redmond, WA for the second annual event for the Truffle community: those who actively build using Truffle’s framework for development on Ethereum. Programming will include speakers from the blockchain ecosystem, along with hands-on workshops geared toward novice users and expert builders alike. There’s truly something for developers of all experience levels!
-
-TruffleCon places focus on the developer by exploring the many ways in which the Truffle tools can enhance the development process by increasing efficiency and enabling high-quality dapp production.
-
-We know that attending a blockchain conference often comes down to ROI for your organization. With so many learning and growth opportunities, here are a few things to remind your boss about when asking to send you to the 2nd Annual [TruffleCon](/trufflecon2019).
-
-## Truffle is widely considered the most popular tool for blockchain application development
-
-Truffle is widely considered the most popular tool for blockchain application development with over 1.5 million lifetime downloads. Truffle supports developers across the full lifecycle of their projects, whether they are looking to build on Ethereum, Hyperledger, Quorum, or one of an ever-growing list of other supported platforms. Paired with Ganache, a personal blockchain, and Drizzle, a front-end dapp development kit, the full Truffle suite of tools promises to be an end-to-end dapp development platform.
-
-## Truffle is being used by the largest and most prominent firms
-
-If your company want to implement blockchain solutions, you’ll need to learn how to interact with Truffle suite of products. Truffle is used by many fortune 500 firms and will be the first company to integrate with AxCore, a proprietary blockchain created by Goldman Sachs and JPMorgan-backed Axoni, which is scheduled to start processing $10 trillion worth of transactions annually for the DTCC’s Trade Information Warehouse later this year.
-
-Here are some of the amazing companies using or integrating Truffle:
-* Microsoft, ConsenSys, Amazon, VMWare Airbus, General Dynamics, J.P. Morgan and more!
-* Soon to be your company too!
-
-## Build dapps hands on and learn to deploy smart contracts 
-
-TrufflCon will have something for everyone from the novice and crypto curious to the advanced blockchain developers and everyone in between. Truffle’s world-class developers and trainers will be there to support you along your developer journey. You’ll learn hands-on how to build dapps and deploy smart contracts during our workshops.
-
-## Meet and learn from the creators of Truffle Suite: the ones closest to Truffle’s development
-
-#### Tim Coulter
-Tim Coulter is the Founder and CEO of Truffle. Before blockchain, Tim built a career specializing in software testing and developer support, which became extremely valuable in the early days of blockchain development. He's now surrounded by an amazing team building the next generation of blockchain development tools, and can't wait to tell you about what's to come.
-
-#### Mike Seese
-Mike Seese is a Core Developer on the Enterprise Products team. In addition to integrating the Truffle Suite to other ledgers and frameworks, he strives to bring the modern development experience to the blockchain community.
-
-#### Josh Quintal 
-Josh is passionate about where the user meets the tech; this led to the creation of two products, Truffle Boxes and Drizzle. He also created "Pet Shop", one of Ethereum's most used beginner tutorials. Besides his obvious technical prowess,Josh is also the most stylish member of the Truffle team.
-
-#### G. Nicholas D’Andrea
-Ever since 2016, he has been obsessed with the decentralized future and working towards building core software components for the blockchain ecosystem. Besides his work on Truffle, he is a core contributor to the EthPM package management system and author of EIP-1123.
-
-#### Kevin Bluer
-He’s building our world-class program at Truffle University from the ground up which trains existing software developers to become Truffle-certified blockchain engineers. Outside of his work with Truffle, he has trained and mentored developers in cities around the globe including New York, Austin, London, Hong Kong, Shenzhen, and Kuala Lumpur.
-
-TruffleCon is a place to meet our developers and work with them, ask questions, and get feedback on your work.
-
-## TruffleCon is for developers by developers
-
-While there is no shortage of conferences in the blockchain space, TruffleCon is uniquely created for developers, by developers. Tim Coulter, Truffle’s Founder & CEO, explained, "Developers attach their identity to the tools they're using. People are congregating around Truffle and want to learn from and collaborate with the people who are using the tools. We aim to host a conference where people can engage with their peers and share insights on how best to use these tools. We hope attendees will leave inspired and that the knowledge shared will transform how people build."
-
-## There will be lots of chocolate
-
-If your boss is still not convinced, most importantly, there will be A LOT of chocolate.
-
-Now, send this to your boss so they can send you to TruffleCon!
-
-[Secure Your Spot for TruffleCon 2019 in Redmond, WA August 2-4, 2019.](/trufflecon2019)
-
-More 2019 announcements are on the way — [Subscribe to the Truffle newsletter](https://truffleframework.us11.list-manage.com/subscribe/post?u=947c9b18fc27e0b00fc2ad055&id=97cfd4251b) and [join the conversation on Telegram in the TruffleCon Channel](https://t.me/TruffleCon).
\ No newline at end of file
diff --git a/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md b/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
deleted file mode 100644
index 840c7388c..000000000
--- a/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: How we're making installation issues a thing of the past
-hide:
-  - navigation
----
-
-<p class="alert alert-info">
-**Update**: Since this blog post was published, we have released [Ganache](/ganache) a personal blockchain and a replacement to the TestRPC. We have left this post unaltered, but we highly recommend checking out our [Ganache Quickstart](/docs/ganache/quickstart) page.
-</p>
-
-It doesn't matter what operating system you're on -- if you've used Truffle in any capacity, you've likely run into an install issue in some form or another. This is especially true for Windows, as Windows doesn't generally ship with the necessary tools to install all of Truffle's important dependencies. And for most users, this sucks: getting hung up on installation is incredibly frustrating when you're usually just one error message or two away from creating your first Ethereum-enabled application. Well, I've got good news. As of the latest Truffle beta release, I'm happy to tell you that this is an issue no longer.
-
-That's right: No matter what platform you're on, your install issues should be over. This is big.
-
-In order to completely sidestep most if not all of the most common installation issues, we had to overcome some technical difficulties as well as rethink how we ship our code. In this post, I'm going to tell you about what we did and how that made installation incredibly simpler, on every platform, for everyone.
-
-## So what was the problem?
-
-Since Truffle is a Javascript-based application, we (naturally) ship our code using the [Node Package Manager](https://www.npmjs.com/) (NPM for short). NPM hosts thousands if not millions of code packages, and it's the service that makes modern Javascript programming possible. Without NPM, not only would programming Truffle be nearly impossible, but programming _anything_ complex in Javascript would be impossible: NPM lets developers separate and bundle code into its own individual chunks, called "packages", that any of those other chunks (packages) can then rely on.
-
-Because of NPM, Truffle is standing on the shoulders of giants. Truffle relies on the code of so many other people that if you looked at the full list you'd be hard pressed to give us credit for the codebase. And that's the beauty of it: packages like hashing functions and cryptographic libraries -- hard libraries to write (and get right!) -- we don't have to write ourselves.
-
-Though using dependencies on NPM has significant upsides, it also comes with significant drawbacks. Those same hashing functions -- functions used throughout Ethereum -- are written to be extremely performant, and so are written in C. In order to install those packages, NPM has to be able to compile them on the fly during installation, which means every Truffle user needs to have a C compiler installed. Additionally, NPM (for some reason) uses Python during the compilation process, which means Truffle users _also_ need to have Python installed.
-
-Bottom line: In order to install a Javascript project, Truffle users need both C and Python. [This is madness.](https://s-media-cache-ak0.pinimg.com/originals/ec/5a/0a/ec5a0a5e4990668ca3f41ed50ca273d3.gif)
-
-## So what can we do?
-
-Most of the issues people were seeing stem from the compilation process mentioned: Either they didn't have the right compilers/interpreters installed for C and Python, or C and Python _itself_ required some dependency that wasn't properly installed. We've had a [tutorial](/guides/how-to-install-truffle-and-testrpc-on-windows-for-blockchain-development) written for awhile that shows Windows users how to correctly set up their environment and get everything installed, but this required considerable effort from novice users and didn't take into account the many landmines hiding around every corner, waiting to explode at any moment. So we can't "instruct" our way around this problem. The only way to fix it, then, is to sidestep it completely.
-
-Sidestepping the compilation process means completely excising any compilation out of the installation process. The way we chose to tackle this is two ways:
-
-- Remove any unnecessary dependencies that rely on compilation.
-- Replace dependencies that need compilation with versions 100% written in Javascript.
-
-In theory this sounds easy: i.e., "just use the Javascript versions or don't use the C versions as all". In practice, this is much harder. Often, we don't directly control the dependencies our application relies on, because _dependencies of dependencies_ (of dependencies of dependencies) might rely on a package that requires compilation. Since the bad apples are the packages that power the code we rely on (i.e., they're "indirect dependencies"), we have to surgically remove them and replace them with versions that install and function more easily. This is no small matter.
-
-Thankfully, a tool exists that makes this surgical replacement possible. It's called [Webpack](https://webpack.js.org/). Webpack bills itself as a Javascript bundler, aiming to mash together all your project's dependencies into a single blob of code, i.e., a "bundle". Webpack finds most of its uses in browser applications, as browsers need to download all code first before a website can be displayed, and it's more performant for the browser to download that code in a single request. However, for console applications like Truffle, Webpack can still be immensely valuable. By creating a bundle with Webpack, we can control exactly which dependencies get included in it.
-
-Take [js-scrypt](https://github.com/tonyg/js-scrypt) for instance. This library provides hashing functions required by Ethereum, is 100% written in Javascript, and is API-compatible with the C-compiled [node-scrypt](https://github.com/barrysteyn/node-scrypt) library. With Webpack, we can simply remove `scrypt` and replace it with `js-scrypt` like nothing happened.
-
-How about another example: Let's do IPFS. Truffle relies on the [ethpm-js](https://github.com/ethpm/ethpm-js) package to provide EthPM support, which itself relies on the [ipfs](https://github.com/ipfs/js-ipfs) package to communicate with IPFS servers. Somewhere deep down in `ipfs`'s dependency tree, some code needs the [execSync](https://www.npmjs.com/package/execSync) package, a package that causes installation issues for some users. Using Webpack, when creating our bundle, we can just _not include it_. Since that code only matters for parts of IPFS that Truffle doesn't use, that code doesn't need to be in our bundle. Ex-nay, [gone-yay](https://www.technobuffalo.com/wp-content/uploads/2016/03/kanye-west-1280x640.jpg). Zip, zilch, completely gone.
-
-Creating a bundle for our releases instead of letting NPM manage dependencies has other benefits as well. To keep code modular and maintainable, Truffle relies on almost 2000 packages! (This includes the dependencies of dependencies we mentioned before). Bundling ahead of time creates a single file users have to download during installation instead of requiring NPM to make requests for all 2000 dependencies. So not only do we get to sidestep all of the installation issues, but we make installation nearly instant as well.
-
-Yep. Feel free to party. We did. 🎉
-
-## So how can you get it?
-
-Bundling Truffle's dependencies means releasing a version of the code where certain dependencies have been either replaced or removed. This not only means releasing structurally new code, but it means releasing code that has differing testability characteristics which change our ability to ensure its of the quality you've come to expect. We need to build infrastructure to help us do that, so in the meantime **we've released the new version of the code in beta.**
-
-To get the beta version of Truffle, first uninstall the version you currently have (they'll conflict):
-
-```shell
-$ npm uninstall -g truffle
-```
-
-And now install the beta version:
-
-```shell
-$ npm install -g truffle@beta
-```
-
-You'll notice that the beta version installs almost instantly, and no compilation is required. Hot-dog.
-
-## So what's next?
-
-As we gain responses from the community about this new version we'll likely make changes to ensure we've sidestepped all the installation issues that have plagued users in the past. Once that's finished we'll make an official release. As well, we'll be performing this same work for the TestRPC in the coming weeks to ensure the TestRPC has the same hassle-free, instant installation that you'll soon come to expect from Truffle.
-
-If you run into issues with the beta version, don't hesitate to [write up an issue](https://github.com/trufflesuite/truffle/issues) in our issue tracker or reach out on the [community Gitter channel](https://gitter.im/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions.
-
-Cheers, and we appreciate your ongoing support and feedback.
-
--- Tim & the Truffle Team
diff --git a/src/blog/introducing-ganache-7/index.md b/src/blog/introducing-ganache-7/index.md
deleted file mode 100644
index 9681ee1ee..000000000
--- a/src/blog/introducing-ganache-7/index.md
+++ /dev/null
@@ -1,310 +0,0 @@
----
-title: Ganache 7 Ethereum Simulator - Building on Web3 is now easier and faster than ever before
-hide:
-  - navigation
----
-
-![ganache v7 banner](./ganache-v7.png)
-
-**By Kingsley Arinze, Mei Chan and David Murdoch**
-
-Ganache is a pioneer in the Ethereum development space, aiding DApp developers and enthusiasts to build, test, and explore blockchain since 2016. We are excited to announce the wide release of the latest version of Ganache today, with 30 times faster forking performance and an Infura integration that allows you to replay historical transactions with free access to archive data.
-
-For the uninitiated, Ganache is a local development blockchain used to develop decentralized applications on the Ethereum blockchain. It simulates the Ethereum network, and you can see how your DApp will perform before you release it to production.
-
-Typically, to start developing distributed applications on the Ethereum network, you will need to set up an Ethereum client such as Geth or OpenEthereum to provide you access to an [Ethereum Virtual Machine (EVM)](https://ethereum.org/en/developers/docs/evm/).
-
-Although that is a great way to develop distributed applications on Ethereum, it is not the most efficient and user-friendly approach, as you need to configure these clients manually and keep them running. Maintaining a self-hosted node can be expensive and time-consuming, you don’t want to spend valuable time troubleshooting a failed node during development.
-
-With Ganache, all you need to do is start the application and you have a preconfigured Ethereum client with 10 pre-funded and unlocked accounts ready for use. This allows you to quickly test your DApp throughout your development cycle.
-
-## Ganache 7: 30x faster forking and operations
-
-Many Web3 developers building on Ethereum already use Ganache to fork and test smart contracts in their local environments for confidence before deployment. Armed with the knowledge gained from previous iterations, we rewrote Ganache from the ground up with the mission to make the blockchain simulator tool even more flexible, faster, and more stable. 
-
-We heard your feedback that Ganache v6 was slow to install, slow to run, and leaked memory. It also didn’t use the modern language features and paradigms developers use today, like TypeScript types and the Promise abstraction. Ganache v6’s architecture made testing, fixing bugs, and adding features difficult and time-consuming.
-
-How is Ganache v7 better?
-
-- With advanced caching capabilities on the latest version, Ganache's forking feature is up to 30 times faster than v6.
-- Zero-config Mainnet forking! Ganache v7 has a [native integration with Infura](https://blog.infura.io/fork-ethereum-replay-historical-transactions-with-ganache-7-archive-support/) which enables free access to historical data
-- You can run Ganache indefinitely without running into crashes due to memory issues
-- Common operations are about 3 times faster than v6.
-
-## Installing and Setting up Ganache 7
-
-Ganache can be used in many ways, including as a command-line tool, programmatically via Node.js, or in the browser. See the instructions below for installing and using Ganache 7 for all these use cases.
-
-### A. Using Ganache 7 On the command line
-
-To run Ganache 7 on the command line, you must have Node.js >= v12.0.0 and NPM >= 6.4.1 installed on your computer. See [here](https://nodejs.org/en/download/) to download the latest version for your operating system, or use nvm to manage your Node installation for [Unix](https://github.com/nvm-sh/nvm) or [Windows](https://github.com/coreybutler/nvm-windows).
-
-With Node.js and NPM installed, you can install Ganache 7 globally by running `npm install ganache --global`. Once installed, you can run `ganache` from anywhere in your command line. 
-
-Your terminal should look like this:
-
-![screenshot-1](./example-1.png)
-
-By default, Ganache provides 10 test accounts, each with 1000 (fake) Ether along with the corresponding private keys and the mnemonic phrase used to generate them. You can use this phrase to import the accounts into wallets like [MetaMask](https://metamask.io/) during development.
-
-We can override all defaults by specifying options when starting Ganache 7; for example, we can have more control over account creation by providing a mapping of private keys to account balances like so:
-
-```
-ganache --wallet.accounts "0xfd485338e322f5930f7cf475f385341ec88bfc4f8a0a16f30b2fb417d1bb5427, 1000000000000000000000" "0x05bba0b9f7a251080aa23feee4eab3f75a1abee905c0271008c93e5d2e2e7541, 10000000000000000000000"
-```
-
-We can also specify a mnemonic phrase to derive all initial accounts from,  a miner gas price, and the block gas limit. For example:
-
-```
-ganache --miner.defaultGasPrice 200 --miner.blockGasLimit 90071 --miner.callGasLimit 898989 --wallet.mnemonic "alarm cause brave super lab glide awake hunt rose win sugar idea"
-```
-
-Run the command `ganache --help` for a list of all the available options you can pass to Ganache.
-
-We can also install ganache into a local Node.js project using  `npm install ganache` without the `--global` flag, then add it to your project’s package.json `scripts`, e.g., `"scripts": {"ganache": "ganache --mnemonic <12 words mnemonic>"}`.
-
-### B. Using Ganache 7 programmatically
-
-Ganache 7 can be used programmatically in your Node.js project as:
-
-- A standalone EIP-1193 provider,
-- A JSON-RPC server and EIP-1193 provider, 
-- A web3.js provider and
-- An ethers.js provider. 
-
-See code samples for these different use cases below.
-
-To begin, install Ganache 7 as  npm package in your Node.js project
-
-```console
-$ npm install ganache
-```
-
-As a standalone EIP-1193 provider
-
-```javascript
-const ganache = require("ganache");
-
-const options = {};
-const provider = ganache.provider(options);
-const accounts = await provider.request({ method: "eth_accounts", params: [] });
-...
-```
-
-As a JSON-RPC web server and an EIP-1193 provider 
-
-```javascript
-const ganache = require("ganache");
-
-const options = {};
-const server = ganache.server(options);
-const PORT = 8545;
-server.listen(PORT, err => {
-  if (err) throw err;
-
-  console.log(`ganache listening on port ${PORT}...`);
-  const provider = server.provider;
-  const accounts = await provider.request({ method: "eth_accounts", params:[] });
-});
-...
-```
-
-As a Web3.js provider
-
-```javascript
-const Web3 = require("web3");
-const ganache = require("ganache");
-
-const web3 = new Web3(ganache.provider());
-...
-```
-
-As an Ethers.js provider
-
-```javascript
-const ganache = require("ganache");
-
-const provider = new ethers.providers.Web3Provider(ganache.provider());
-```
-
-### C. Using Ganache 7 in the browser.
-
-You can use Ganache 7 in the browser by adding the following script tag to your HTML code:
-
-```javascript
-<script src="https://cdn.jsdelivr.net/npm/ganache@7.0.0/dist/web/ganache.min.js"></script>
-```
-
-By doing that, Ganache 7 is automatically available in your browser for use:
-
-```javascript
-const options = {};
-const provider = Ganache.provider(options);
-```
-
-Again, see [here](https://github.com/trufflesuite/ganache#readme) for a list of available options you can pass in.
-
-## New Ganache 7 Features
-
-### 1. Zero-config mainnet forking
-
-Ganache supports mainnet forking out of the box without any configuration, allowing you to simulate having the same state as the Ethereum mainnet, but on your local machine. 
-
-This opens up many possibilities; for example, you can interact with a real-world protocol/contract locally during development, step through, and debug main net transactions locally (using [`truffle debug`](https://trufflesuite.com/docs/truffle/getting-started/using-the-truffle-debugger)), allowing visibility to details about your contract.
-
-[Here's](https://www.reddit.com/r/ethereum/comments/4yd1o4/testrpc_teaser_instantaneous_forking_coming_soon/) a 2016 demo of the Ganache team using the Mainnet forking feature to exploit the [DAO hack](https://www.gemini.com/cryptopedia/the-dao-hack-makerdao).
-
-To use this feature, start Ganache 7 using the `ganache --fork` command. Ganache uses [Infura](https://infura.io/docs) as its provider under the hood by default, but you can also specify a provider by passing a URL; for example, you can use your own Infura URL by running this command:
-
-```console
-$ ganache --fork.url wss://mainnet.infura.io/ws/v3/<PROJECT ID>
-```
-
-Ganache fetches five blocks back from the latest by default to avoid missing blocks due to reordering.
-
-This is a configurable behavior; you can either specify the exact block you want to fork from using `--fork.blockNumber <BLOCK NUMBER>` or by setting `--fork.preLatestConfirmations 0`.
-
-### 2. Fork any Ethereum test network without waiting for sync time
-
-In addition to being able to fork the Ethereum main network with zero configuration, Ganache also allows you to fork from any Ethereum test network, including Ropsten, Kovan, Rinkeby, and Görli. 
-
-You can do that by running the fork command with the network option: `ganache -- fork.network <NETWORK NAME>`. Cool, yeah? Here's what forking from the Rinkeby testnet looks like:
-
-![screenshot-2](./example-2.png)
-
-### 3. Support for massive transaction traces (over 10GB+)
-
-Ganache supports massive transaction tracing using the `debug_traceTransaction` RPC method.
-
-To use this feature, start Ganache by forking off of Mainnet (or any test network) at a block number greater than that of the transaction you're trying to trace; for example, if you want to trace a transaction inside block 13,886,877, you will need to start Ganache at block number 13,886,878: 
-
-```console
-$ ganache --fork.network mainnet --fork.blockNumber <blockNumber>
-```
-
-Then send a curl request using the debug_traceTransaction method specifying the transaction hash like so: 
-
-```console
-$ curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "debug_traceTransaction", "params": [ "<TRANSACTION HASH>" ] }' http://localhost:8545
-```
-
-This would return the aggregated summary of this transaction for post-processing.
-
-Try it with a large transaction like `0x8bb8dc5c7c830bac85fa48acad2505e9300a91c3ff239c9517d0cae33b595090` (Warp Finance hack):
-
-First, start ganache (with lots of extra memory):
-```console
-$ NODE_OPTIONS=--max-old-space-size=16384 ganache --fork --fork.blockNumber 14037983
-```
-
-then execute `debug_traceTransaction` and send the output to trace.json: 
-```console
-$ curl -H 'Content-Type: application/json'   --data '{"jsonrpc":"2.0", "id": 1, "method": "debug_traceTransaction", "params": [ "0x8bb8dc5c7c830bac85fa48acad2505e9300a91c3ff239c9517d0cae33b595090" ] }' http://localhost:8545 -o trace.json
-```
-
-If you really want to test the limits of what's possible (and have a lot of time - about 1-2 hours) try out the 10GB+ Cream Finance hack transaction, `0x0fe2542079644e107cbf13690eb9c2c65963ccb79089ff96bfaf8dced2331c92`!
-
-### 4. Snapshot and Revert state
-
-In blockchain terms, a snapshot refers to the act of capturing and recording the state of a blockchain at a particular block number. A snapshot is the complete view of the blockchain in that specific block and includes all existing addresses and their associated data, including transactions, fees, balance, metadata, etc.
-
-In Ganache, you can take a snapshot of your development blockchain (or even a fork of Mainnet) using the `evm_snapshot` RPC method; it takes no parameters and returns an ID of the snapshot that it creates. 
-
-Ganache also supports reverting state to a previously taken snapshot using the `evm_revert` RPC method, although once a revert is invoked and succeeds, you can no longer use the snapshot with the corresponding ID as you can only revert a snapshot once. 
-
-You should consider creating a new snapshot after every evm_revert if you need to revert to the same point multiple times; here's a demo of taking a snapshot and reverting state in Ganache:
-
-```javascript
-const provider = ganache.provider();
-const [from, to] = await provider.send("eth_accounts");
-const startingBalance = BigInt(await provider.send("eth_getBalance", [from] ));
- 
-// take a snapshot
-const snapshotId = await provider.send("evm_snapshot");
- 
-// send value to another account (over-simplified example)
-await provider.send("eth_subscribe", ["newHeads"] );
-await provider.send("eth_sendTransaction", [{from, to, value: "0xffff"}] );
-await provider.once("message"); // Note: `await provider.once` is non-standard
- 
-// ensure balance has updated
-const newBalance = await provider.send("eth_getBalance", [from] );
-assert(BigInt(newBalance) < startingBalance);
- 
-// revert the snapshot
-const isReverted = await provider.send("evm_revert", [snapshotId] );
-assert(isReverted);
- 
-// ensure balance has reverted
-const endingBalance = await provider.send("eth_getBalance", [from] );
-const isBalanceReverted = assert.strictEqual(BigInt(endingBalance), startingBalance);
-console.log({isBalanceReverted: isBalanceReverted});
-```
-
-### 5. Mine blocks instantly, at interval, or on demand
-
-Ganache allows you to configure how you want blocks to be mined during development; by default, blocks will be mined immediately upon receiving a transaction, but you can choose between the following options:
-
-- **At interval**: You can specify the time in seconds Ganache should wait before mining the next transaction by passing the `--miner.blockTime <TIME IN SECONDS>` option. A block time of 0 means Ganache should mine new transactions instantly.
-- **On demand**: Ganache also exposes an `evm_mine` RPC method which forces a single block to be mined whether mining is running or stopped. This will mine an empty block if no transaction exists in the mempool. See code sample below:
-
-```javascript
-console.log("start", await provider.send("eth_blockNumber"));
-await provider.send("evm_mine", [{blocks: 5}] ); // mines 5 blocks
-console.log("end", await provider.send("eth_blockNumber"));
-```
-
-### 6. Fast forward time
-
-Ganache exposes two RPC methods for manipulating time on your development blockchain. 
-
-A typical use case would be a smart contract that requires that a specific time passes before users can take certain actions; if the set time isn't something you want to wait for, you can use the `evm_increaseTime` to increase the blockchain current timestamp by the specified amount of time in seconds (passed in as hexadecimal).
-
-```
-curl -H 'Content-Type: application/json' --data' {"jsonrpc": "2.0", "id": 1, "method": "evm_increaseTime", "params": ["0x15180"] }' http://localhost:8545
-```
-
-This returns the total time adjusted in milliseconds. Furthermore, you can use the `evm_setTime` to set it to a specific timestamp; it accepts a JavaScript timestamp (Unix epoch) with millisecond precision and returns the number of seconds between the given timestamp and the current time. 
-
-```
-curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "evm_increaseTime", "params": ["0x15180"] }' http://localhost:8545
-```
-
-You should use this method cautiously as it allows you to move backwards in time, which may cause new blocks to appear to be mined before older blocks, thereby invalidating the blockchain state.
-
-### 7. Impersonate any account
-
-Ganache allows you to impersonate another account during development. This is more interesting when used with the fork feature; you can fork Mainnet and impersonate any account. 
-
-Here's an example of how you can fork Mainnet, impersonate an account, and send some tokens to another account. 
-
-- Start Ganache by forking Mainnet and impersonating (unlocking) a random account: 
-`ganache --fork --wallet.unlockedAccounts <Account Address Here>`
-- Get the balance of the unlocked account: 
-`curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "eth_getBalance", "params": ["<Account Address Here>"] }' http://localhost:8545`. This returns the balance in WEI encoded as a hex number.
-- Send some ether from the unlocked account to another account:
-`curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "eth_sendTransaction", "params": [{"from": "UNLOCKED ACCOUNT", "to": "RECEIVING ACCOUNT", "value": "AMOUNT TO SEND"}] }' http://localhost:8545`
-
-Now verify that the unlocked account's balance has been reduced by the number of Ether sent out.
-
-Sending Ether to another account isn't the only use case as you can impersonate an account to call certain owner-only functions in a smart contract as we did in the convex benchmark contract we saw earlier.
-
-### 8. Pending transactions
-
-In Ethereum, every transaction has a nonce. The nonce is the number of transactions sent from a given address to date, and anytime you send a transaction, the nonce increases by 1. 
-
-For a transaction to be mined, it has to have a nonce greater than that of the previous transaction by 1. In earlier versions of Ganache, if you send a transaction with a nonce greater than the last nonce by more than 1, Ganache would error, and the transaction would be rejected.
-
-With Ganache 7, if the nonce of the previous transaction is 1, and you send a transaction with the nonce set to 3 for whatever reason, this transaction with nonce 3 will sit in the transaction pool until a transaction with nonce 2 is sent, at which time both transactions will be mined and added to the blockchain state.
-
----
-
-Start using Ganache 7 today by simply running `npm install ganache --global && ganache --help`, or view the [v7 Release Notes](https://github.com/trufflesuite/ganache/releases/tag/v7.0.0).
-
----
-
-This release has been years in the making and we're really proud of the work we've done. We hope you love it as much as we do.
-
-Thank you to everyone who has been a part of making this release happen — contributors, mentors, reviewers, issue reporters, and community participators have all been instrumental in making Ganache v7. We are immensely thankful to you all.
-
-<p align="center">💖 The Truffle Team</p>
diff --git a/src/blog/introducing-truffle-dashboard/index.md b/src/blog/introducing-truffle-dashboard/index.md
deleted file mode 100644
index 8c70ffdc2..000000000
--- a/src/blog/introducing-truffle-dashboard/index.md
+++ /dev/null
@@ -1,171 +0,0 @@
----
-title: Introducing Truffle Dashboard - Stop copy + pasting your private keys!
-hide:
-  - navigation
----
-
-![truffle dashboard - banner](./truffle-dashboard-private-keys.png)
-
-**By [Kingsley Arinze](https://twitter.com/heydamali)**
-
-## Don't get rekt 🙀
-
-One of our core missions at Truffle is to provide tooling that aids in the complete Web3 dapp development lifecycle, while maintaining rigorous security practices throughout. **As a smart contract developer, you require your development tools to keep your sensitive information secret and safe.** At Truffle, we're always looking for ways to make your experience more secure.
-
-If you’ve ever deployed a smart contract, chances are you’ve had to think twice about sharing your private keys with Truffle or other development tools. Maybe you've had to be vigilant not to accidentally share those keys on GitHub. To deploy to an Ethereum network, you've needed to copy your wallet credentials and store them in an insecure location to share with a tool like HDWalletProvider. **This has been necessary because your mnemonic or private key gives Truffle the permissions it needs to sign transactions on your behalf.**
-
-<figure markdown>
-  <img
-    src="./secrets-oh-no.png"
-    alt="Screenshot of an example truffle-config.js using HDWalletProvider with hardcoded mnemonic and Infura key."
-    style="margin: 0 auto;"
-    width="75%"
-    />
-  <figcaption>Have you ever had to do something like this?</figcaption>
-</figure>
-
-
-**Storing your mnemonic seed phrase or private keys in regular files poses a considerable security concern.** Your seed phrase can easily be hijacked by JavaScript code, accidentally committed to Git, or targeted by bad actors.
-
-## Enter Truffle Dashboard 🔥 🚀
-
-Truffle Dashboard completely removes the need to manually interact with your wallet's mnemonic phrase or private keys throughout the development lifecycle.  **You can now safely deploy your smart contracts to your network of choice without Truffle ever needing to know what your keys look like.** Truffle seamlessly connects to your MetaMask wallet without any configuration, using the currently selected account and network for Truffle's deployment configuration.
-
-_But that's not all!_ For your convenience, **you can use Truffle Dashboard with any development tool.** For example, if you use Hardhat or Foundry to develop your smart contracts, you can also integrate with Truffle Dashboard for this improved security workflow. See the [Using Truffle Dashboard with other development tools](/docs/truffle/getting-started/using-the-truffle-dashboard) section of our docs to learn how.
-
-## How does Truffle Dashboard Work? ⚙️🔧
-
-If you're new to Truffle, ensure you have Node.js then install the latest version of Truffle with the following command:
-
-```console
-npm install -g truffle
-```
-
-If you already have Truffle installed, you want to first uninstall your existing instance of Truffle globally:
-
-```console
-npm uninstall -g truffle
-npm install -g truffle
-```
-
-
-### Running Truffle Dashboard 🚀
-
-With the latest version of Truffle, in addition to all previously existing `truffle <...>` commands, you will see a new `truffle dashboard` command.
-
-Running `truffle init` walks you through the process of setting up a new truffle project.
-
-Running `truffle dashboard` in a separate terminal window starts Truffle Dashboard at `http://localhost:24012` and automatically opens a new tab in your existing browser session.
-
-![truffle dashboard - start from the cli](./truffle-dashboard-cli.png)
-
-You can also configure the port and host to run Truffle Dashboard in one of two ways:
-
-  - On the command line:
-
-    ```console
-    truffle dashboard --port <Port of choice> --host <Host of choice>`
-    ```
-
-  - In your Truffle configuration (truffle-config.js) file:
-
-    ```javascript
-    module.exports = {
-      /* ... rest of truffle-config.js ... */
-
-      dashboard: {
-        port: 25012,
-        host: "localhost"
-      }
-    }
-    ```
-
-See the [Truffle Commands](/docs/truffle/reference/truffle-commands.html) and/or the [Configuration](/docs/truffle/reference/configuration.html) reference documentation to learn more.
-
-### Connecting your wallet 🤝
-
-Truffle Dashboard requires you to connect your wallet to get started. Click the "Connect Wallet" button and connect Truffle Dashboard to your wallet the same way you would for any other dapp.
-
-![truffle dashboard - connect wallet](./truffle-dashboard-connect-wallet.png)
-
-Next, Truffle Dashboard prompts you to confirm that you are connected to the correct network, since it uses the wallet's default active network. Make sure you switch to the desired network before confirming. Every transaction you process will be sent to the confirmed network.
-
-![truffle dashboard - confirm](./truffle-dashboard-confirm.png)
-
-During development, a typical workflow is first to deploy and test out your smart contract code on a development blockchain like [Ganache](https://trufflesuite.com/ganache) before deploying to your favorite test network.
-
-You can still maintain this workflow with Truffle Dashboard by simply importing Ganache’s local blockchain network into your MetaMask wallet as usual and pointing Truffle Dashboard to use it as your confirmed network.
-
-![truffle dashboard - select network](./truffle-dashboard-select-network.png)
-
-### Using Truffle Dashboard in your Truffle project 🎉
-
-Before Truffle Dashboard was available, if you wanted to connect to a network like Rinkeby or Mainnet from your Truffle project, you had to specify some configuration variables in the network section of the truffle-config.js file.
-
-```javascript
-module.exports = {
-  /* ... rest of truffle-config.js ... */
-
-  networks: {
-    development: {
-      host: "localhost",
-      port: 8545,
-      network_id: "*"
-    },
-
-    ropsten: {
-      // ...
-    },
-
-    mainnet: {
-      // ...
-    }
-  }
-};
-```
-
-With Truffle Dashboard, you do not need any of that, as Truffle now exposes a built-in network named `"dashboard"` which runs on whatever port and host your Truffle Dashboard is running on (`http://localhost:24012` by default). With Truffle Dashboard running and connected to MetaMask, you can simply supply the `dashboard` keyword to any Truffle command that requires you to specify a network. For example:
-
-```console
-truffle migrate --network dashboard
-truffle console --network dashboard
-```
-
-When you run the above commands (or any RPC request), Truffle forwards your request from the command-line to the browser, where you can inspect it and choose to process or reject with MetaMask.
-
-![truffle dashboard - process transaction](./truffle-dashboard-sign.png)
-
-As with every zero-configuration feature, you are allowed to override the default configuration by adding a network called `dashboard` to your Truffle configuration file and specifying its options as you would for other networks. See the [`networks` configuration](/docs/truffle/reference/configuration.html#networks) reference documentation for more information.
-
-### Using Truffle Dashboard with other development tools 👪
-
-Although we developed Truffle Dashboard intending to improve the development experience for those who choose to build with Truffle, we made sure to make it tool-agnostic. So if Truffle isn't your development tool of choice for developing smart contracts (why on earth should it not be? C'mon, now let's talk!), but you'd like to integrate the Dashboard into your workflow, we've got you covered.
-
-You can use Truffle Dashboard with other development tools. For example, use it with Hardhat by simply starting Truffle Dashboard in a separate terminal window and add a network configuration option that points to Truffle Dashboard's RPC URL in your Hardhat config file:
-
-```js
-module.exports = {
-  // ...
-
-  networks: {
-    // ...
-
-    "truffle-dashboard": {
-      url: "http://localhost:24012/rpc"
-    }
-  },
-};
-```
-
-With this setup, when you run the command `hardhat deploy --network truffle-dashboard`, the request is forwarded to Truffle Dashboard, where you can inspect and process them.
-
-## Conclusion ❤️️
-
-**With Truffle Dashboard, you no longer have to worry about giving your private keys to someone else's JavaScript code.** You can now relax and leave it up to MetaMask to keep your private keys safe and sign transactions on your behalf.
-
-
-To get started, download the latest version of Truffle and start using Truffle Dashboard today by running the command `npm uninstall -g truffle && npm install -g truffle`.  Please refer to the [Truffle Dashboard](/docs/truffle/getting-started/using-the-truffle-dashboard.html) feature documentation for more.
-
-Truffle Dashboard was borne out of our years of experience working on developer tools for the Ethereum ecosystem and receiving valuable feedback from our users. We are extremely excited to release this feature. We hope you're excited to try it out.
-
-With ❤️️ from the Truffle team. Questions/comments/concerns? Please shoot us a tweet [@trufflesuite](https://twitter.com/trufflesuite)!
diff --git a/src/blog/introducing-truffle-db-part-1/index.md b/src/blog/introducing-truffle-db-part-1/index.md
deleted file mode 100644
index 977300e4d..000000000
--- a/src/blog/introducing-truffle-db-part-1/index.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Introducing Truffle DB, Part 1 - Artifact archeology
-hide:
-  - navigation
----
-
-## Introducing Truffle DB, part 1: Artifact archeology
-Truffle is not a small utility: it compiles your contracts, deploys them to multiple networks, runs your automated tests, provides an interactive debugger for when things go wrong, offers a library for interacting with your contracts on the frontend, … (*the list goes on.*) With just over 20,000 lines of code and close to thirty discrete software packages, Truffle has a lot going on.
-
-Truffle is “not small” on purpose. The tool oversees the development lifecycle in human developer terms. It keeps track of familiar concepts and hides unnecessary, low-level specifics. That’s a big goal.
-
-So how does this work? Well, Truffle tries to be smart about it. It stores information about your contracts so that it can refer to it later. It tracks compilation results alongside the source code you wrote, maintaining a steady mapping between *data for the blockchain* and *data for developers’ brains*.
-
-Right now, this system of record-keeping is served through Truffle’s **contract artifacts**: the large JSON files that get saved in your *build/contracts/* directory. Truffle saves your artifacts when you compile and updates your artifacts with address information when you migrate. Pretty much whenever you use any part of Truffle, these artifacts are read from disk and processed, enabling Truffle to paint itself (and you) a picture of what’s happening in human terms.
-
-Truffle’s artifacts have been enormously useful: the tool simply couldn’t exist without this kind of first-class data capturing. Beyond that, though, being able to count on this data has enabled an ecosystem of other tools and utilities that build on top of Truffle’s functionality using Truffle’s artifacts format. Truffle’s artifacts have served as a common language for representing smart contract development concepts.
-
-Unfortunately, Truffle’s artifacts format has a number of core limitations that prevent Truffle from offering ideal behavior in several key situations. This post describes a few of these limitations. In this post’s follow-up, we’ll share information about a new system to manage this record-keeping, which we’re calling **Truffle DB**.
-
-## So what’s the problem now?
-For starters: artifact files are huge! Too huge! In addition to Truffle reading your contract artifacts, your dapp’s frontend code may read and use your artifacts to let users connect to any deployed network, etc. Problem is—there’s a ton of JSON. It’s a mess, and it’s in your face too much.
-
-<figure>
-  <img src="/img/blog/introducing-truffle-db/example-truffle-db.png" alt="Example of Truffle DB" style="width:100%">
-  <figcaption>**For example:** Truffle stores the same abstract syntax tree* (AST) in two different formats, in every single artifact! Most applications do not need this.
-
-  *for the curious: the AST is the reason your code works whether you wrote it all on a single line or not. Source gets parsed, and the AST is the result. Truffle and other tools rely on the AST for things like debugging, code coverage, and linting.</figcaption>
-</figure>
-
-By the byte, almost all of the information in each contract artifact is for internal use or for some specific purpose. **Only a small subset of the data in each artifact is necessary for your frontend or for you to think about directly.** Thus far, users who have struggled with these large files needed to use a tool like [jq](https://stedolan.github.io/jq/) or write a custom solution.
-
-In addition to these files being too large, the information is grouped purely by the idea of “contract name”. What if you want to have two contracts with the same name? You can’t. What if you want to debug an old version of your contract, deployed to a testnet? I hope you backed up your old artifacts directory somehow.
-
-Although we’ve implemented plenty of workarounds to deal with these limitations, the problems do not go unnoticed. See some long-outstanding open GitHub issues, for example:
-* [Truffle contract artifacts are too big and contain too much sensitive detail to actually deploy on the web (#1269)](https://github.com/trufflesuite/truffle/issues/1269)
-* [Artifact is overwritten if there are two contracts with the same name (#1087)](https://github.com/trufflesuite/truffle/issues/1087)
-* [Source map indexes are missing in artifacts (#1236)](https://github.com/trufflesuite/truffle/issues/1236)
-* [Allow persistency of artifacts remotely (#1790)](https://github.com/trufflesuite/truffle/issues/1790)
-
-Unfortunately, these issues are blocked by the fundamental design of the contract artifacts.
-
-The root of the problem is that Truffle’s artifacts try to serve two conflicting purposes: they try to serve the developer, but they also try to serve the tool itself.
-
-## “Stop talking about data formats”, you say.
-
-Right? Ideally, Truffle should silently keep complete records of everything you will ever need, and nothing more. And you, the developer, should only ever come face-to-face with the information you need at any given moment.
-
-So, for some time, we have been working on a plan to improve the state of affairs of Truffle’s record-keeping.
-
-We’ll get into it more in the next post, but Truffle DB aims to provide two things:
-* a data model: a set of terms that collectively represent various, high-level concepts associated with smart contract development
-* a flexible interface: a way to query and update your Truffle project’s records
-
-In doing this, we’re taking a data-first approach, organizing your project’s information through immutable records and a clean separation of concerns. Stay tuned for the next post, where we’ll talk about this more and outline our release plan for Truffle DB: what we’ll be releasing first, what work still needs to be done, and how we plan to handle backwards compatibility over time.
-
diff --git a/src/blog/introducing-truffle-db-part-2/index.md b/src/blog/introducing-truffle-db-part-2/index.md
deleted file mode 100644
index c5d738bb6..000000000
--- a/src/blog/introducing-truffle-db-part-2/index.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Introducing Truffle DB, part 2 - 'Weight and Switch'
-hide:
-  - navigation
----
-
-Welcome back! If you missed the [first part](/blog/introducing-truffle-db-part-1) of this post, you may want to read it to learn more about Truffle’s contract artifacts, their current limitations, and why we seek to build a better solution.
-
-Or, just to catch up:
-* Truffle currently stores information about your smart contracts in files that we call “contract artifacts” (or just “artifacts” for short.)
-* Truffle uses these artifacts for pretty much everything.
-* Plenty of other tools use artifacts too, and rely on their behavior.
-* Unfortunately, the artifacts file format has several design flaws, forcing dozens of workarounds and even preventing certain use cases entirely.
-* Addressing these flaws head-on risks severe negative impact on other projects.
-* We’re excited to share a project we’ve been working on, to offer a deprecation plan and to encourage community involvement.
-
-So why should you care?
-* If you are a tools developer, or rely on Truffle artifacts directly in any way: there will be breaking changes!
-* If you use Truffle for smart contract development: the developer experience using Truffle will have fewer roadblocks (“[software warts](https://www.catb.org/jargon/html/W/wart.html)”). This will not break existing Truffle projects.
-* No matter who you are: better data means better tools.
-
-Great! I’m convinced. 😁 Now, where were we?
-
-## What is Truffle DB?
-
-Truffle DB comprises two key ideas, currently at different stages of development. These are:
-
-1. A data model for organizing your project’s smart contracts: how to keep track of all the different pieces of information, from your contract source files to where they are deployed.
-1. A flexible JSON data access interface: how to read exactly the data you need and how to update the DB with the data you have.
-
-### Data model
-
-<figure>
-  <img src="/img/blog/introducing-truffle-db/truffle-db-data-model.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>**Data model excerpt**: how contracts, sources, compilers, and compilations all relate. ([Text-accessible version](https://github.com/trufflesuite/artifact-updates/blob/master/docs/uml/macros.iuml) available via diagram source)</figcaption>
-</figure>
-
-What is a smart contract? What is your contract’s bytecode, what is its source code, and how do they relate? By looking at how Truffle expects these relationships in practice, and considering how these concepts are commonly understood, we hope to make life easy by creating a shared vocabulary for interacting with the smart contract domain.
-
-Diagrams are worth more than words here, so please check out our data model docs to get a broader sense for what this represents.
-
-**Current status**: Implemented as minimally viable, designed to be extended.
-
-### Flexible interface
-
-<figure>
-  <img src="/img/blog/introducing-truffle-db/concept-query.png" alt="Example of Truffle DB" style="width:100%">
-  <figcaption>**Concept image**: Example query to fetch specific project contract info. ([See gist for image text](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-concept-query-graphql))</figcaption>
-</figure>
-
-Truffle DB uses [GraphQL](https://graphql.org) for its primary interface. GraphQL affords flexibility and a data-first design methodology that suits our goals well. This interface is intended for use in tools to build on top of Truffle; as a normal user you won’t have to touch this. (Of course, we hope this will encourage you to find new ways to solve problems by building and sharing tools of your own!)
-
-Truffle DB is still in development, but we would like to share what we’ve got so far and to talk about where we’re looking to go. Although it’s early, we want to increase awareness about future breaking changes, and we hope to paint a picture of some new foundations that we’re excited will help the smart contract development tools ecosystem.
-
-**Current status**: Internal infrastructure in place, prototyping for public review to begin soon.
-
-## What we’re releasing first
-
-We’re gearing up for a minor release (Truffle v5.1), and we plan to make a first version of Truffle DB available as an experimental implementation. This means building blocks to start: key pieces of infrastructure to paint a picture of Truffle DB for review and iteration.
-
-Day 1, this means you will get:
-* The ability to convert your artifacts and load them into Truffle DB
-* A mechanism to persist Truffle DB data side-by-side with your artifacts
-* Improvements to Truffle that take advantage of this data when it exists
-* A bundled GraphQL playground for hands-on exploration
-* The ability to easily explore the schema to better understand our system design
-
-<figure>
-  <img src="/img/blog/introducing-truffle-db/graphql-playground.png" alt="Example of Truffle DB" style="width:100%">
-  <figcaption>**Interact with Truffle DB**: Apollo’s [GraphQL Playground](https://www.apollographql.com/docs/apollo-server/features/graphql-playground/) provides a handy way to work with GraphQL interfaces. We’re bundling a Playground instance into Truffle DB to make it easier to learn about.
-(For text-accessible version, see [query source](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-graphql), [query variables](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-result-json), and the [query result](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-result-json))</figcaption>
-</figure>
-
-## What’s left to be done (soon)
-
-Since we’ve started by building infrastructure, the work remains to connect the dots into a final design that we can validate for quality and usefulness.
-
-This includes:
-* Documentation, of course! See our current [Truffle DB – Proposal](https://trufflesuite.github.io/artifact-updates/index.html) working docs, which include the data model diagrams. Expect us to convert these docs into proper documentation for release.
-* Better persistence. Our initial implementation will save JSON files to disk, but we intend to support more robust data storage options, including relational databases and native support in [Truffle Teams](/docs/teams/overview).
-* Schema design updates, including support for pagination and proper data filtering.
-* A prototype candidate for Truffle DB’s external interface.
-
-## The long-term plan
-
-We’re going to introduce Truffle DB gradually, deprecating the old artifacts format and introducing Truffle DB more and more as it’s validated.
-
-We expect to follow these steps:
-1. Release initial Truffle DB features as opt-in and experimental.
-1. Gather feedback and support to build a cohesive Truffle DB release candidate (for broad community use).
-1. Turn Truffle DB on by default, but continue to use artifacts as the primary data store.
-1. Convert the rest of Truffle to use Truffle DB as its primary data store, but continue to maintain artifacts alongside it for compatibility.
-1. Continue to maintain both data stores, and switch to using Truffle DB to manage artifacts (instead of existing artifacts management code).
-1. Turn off artifacts by default, but maintain legacy support through configuration.
-1. Eventually, remove artifacts altogether.
-
-We expect this process, start to finish, to span at least two major (breaking change) releases. We plan to maintain legacy support for artifacts for at least 18 months after we release a Truffle DB release candidate.
-
-<figure>
-  <div style="width:100%;height:0;padding-bottom:43%;position:relative;"><iframe src="https://giphy.com/embed/26tPcRGbvMEcKmrRe" width="100%" height="100%" style="position:absolute" frameBorder="0" class="giphy-embed" allowFullScreen></iframe></div><p><a href="https://giphy.com/gifs/film-cinemagraph-26tPcRGbvMEcKmrRe">via GIPHY</a></p>
-  <figcaption>[Weight and Switch](https://tvtropes.org/pmwiki/pmwiki.php/Main/WeightAndSwitch): Dr. Jones demonstrating proper technique for delicate data migration procedures</figcaption>
-</figure>
-
-## What do you think?
-
-Please reach out with questions/thoughts/use case ideas/implementation strategies, or even just to say hello. Your feedback will help us provide the most value and make sure we do so with enough clarity!
-
-We’re tracking overall progress in this [GitHub issue (trufflesuite/truffle#1718)](https://github.com/trufflesuite/truffle/issues/1718). Expect to see this filled out more in the coming weeks, so please follow along there if you’re interested.
-
-Thanks for reading! Hope to see you at TruffleCon!
diff --git a/src/blog/iterate-faster-with-truffle-teams/index.md b/src/blog/iterate-faster-with-truffle-teams/index.md
deleted file mode 100644
index 800f61d5e..000000000
--- a/src/blog/iterate-faster-with-truffle-teams/index.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Iterate Faster with Truffle Teams
-hide:
-  - navigation
----
-
-Consider the amount of context switching required to develop a dapp: you’re writing Solidity one minute, writing tests another, debugging those results--it’s easy to get lost! These switches carry a cognitive load and when errors equal a loss of ETH we need all the help we can get. I’m happy to inform you Truffle Teams can help reduce context switching and help you or your team iterate faster.
-
-Truffle Teams has reached a very important stage in its life: it now provides a complete workflow including building, testing, managing, monitoring, and debugging. This means you’re getting a huge boost in productivity. This amounts to a more robust workflow for you and/or your team and contributes to the application lifecycle generally by tightening the feedback loop between deployment, operation, and debugging all within a flexible development network.
-
-<figure>
-  <img class="mb-4 w-100" src="/img/blog/iterate-faster-with-truffle-teams/dev-lifecycle.png" alt="The development lifecycle: plan, code, build, test, release, deploy, operate, and monitor.">
-  <figcaption class="text-center font-italic">The development lifecycle.</figcaption>
-</figure>
-
-Up to this point, Truffle Teams has already offered a builds system, deployment manager, blockchain sandboxes, and monitoring. Recently we released a visual debugger into early access. With that, we’d like to highlight two features that completed this cycle: the Debugger and the Contract Manager.
-
-For a great video example, check out our demo from TruffleCon 2020. We briefly touch all the phases talked about above using a rock, paper, scissors game. For something more long-form, check out our 5-part webinar series walking you through using the Truffle suite to create an NFT and trade it on a decentralized marketplace.
-
-<figure>
-  <a href="https://www.youtube.com/watch?v=LsQ2Iwd5VMc" target="_blank">
-    <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/teams-demo-tcon-2020.jpg" alt="The video thumbnail for Josh Quintal and Mike Seeses demo of Truffle Teams at TruffleCon 2020.">
-    <figcaption class="text-center font-italic">Mike Seese and Josh Quintal go over the entire development lifecycle using Truffle Teams for a decentralized rock, paper, scissors dapp.</figcaption>
-  </a>
-</figure>
-
-## Debugger Enhancements
-
-<p class="alert alert-info">
-  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the debugger right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
-</p>
-
-Truffle offers a sophisticated forensic transaction debugger and allows you to extract the most information and context possible from your transactions. We released a graphical version of our command line debugger into Truffle Teams Early Access in December. Since then we’ve added syntax highlighting and breakpoints for an improved developer experience. Readability increases and you control where execution stops, providing a precision debugging experience. Check out the Truffle Teams debugger docs to learn more about breakpoints. Currently the debugger in Truffle Teams only works for sandbox environments, but we plan on supporting public networks next!
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/debugger.png" alt="The Truffle Teams debugger working on an NFT-based badge contract">
-  <figcaption class="text-center font-italic">The Truffle Teams Debugger--now with syntax highlighting and breakpoints!</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-## The Contract Manager
-
-<p class="alert alert-info">
-  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the contract manager right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
-</p>
-
-Truffle Teams’ Contract Manager generates a UI for interacting with all the functions of your smart contracts, as well as a live state tree so you can quickly see the changes propagated by those functions. If you’re familiar with Remix, you’ll feel right at home here.
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/contract-manager.png" alt="The Truffle Teams Contract Manager using an NFT-based badge contract">
-  <figcaption class="text-center font-italic">The Contract Manager; shown here using an NFT badge.</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-The Contract Manager is great for quick demos, integration tests, and a faster, all-GUI debugging workflow. For example, you can deploy to a sandbox via the deployment wizard, hop over to the contract manager to fire off a few transactions, and finally debug these transactions from the monitoring screen.
-
-## Dapp Topography
-
-Going forward, we’ll be helping you understand your dapp on an even deeper level, offering forensic-level analysis of your transactions. Not only that, but it will be able to diagram contract interaction to allow different stakeholders to participate in the debugging process. For example a product manager, or other domain expert can participate in the forensic analysis. These diagrams and other assets can be shareable media that can fit into existing communication channels.
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 w-md-70" src="/img/blog/iterate-faster-with-truffle-teams/ens-plant-uml.png" alt="Plant UML diagram of an ENS transaction">
-  <figcaption class="text-center font-italic">A test in which a user who isn't the owner of an ENS name attempt to change the resolver. Note the "X" shoing the revert.</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-## Get Started with Truffle Teams
-
-We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Check out Truffle Teams today and let us know what you think about the new deployment views and contract manager, or if your team has other needs we haven’t met yet.
-
-<div class="mt-3 mb-4 text-center">
-  <a class="btn btn-truffle" href="https://my.truffleteams.com">SIGN UP FOR THE TRUFFLE TEAMS</a>
-  <a class="btn btn-truffle" href="/docs/teams/quickstart">TRUFFLE TEAMS QUICKSTART</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md b/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
deleted file mode 100644
index 047487be5..000000000
--- a/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Learn Ethereum The Fun Way with our Pet Shop Tutorial
-hide:
-  - navigation
----
-
-Here at Truffle we want to make Ethereum development accessible to developers of all stripes. To that end, today we're releasing a new tutorial called [Pet Shop](/tutorial). It covers the entire local development process, start to finish. For added fun, we've tied the whole thing together within the narrative of creating a pet adoption dapp for a local pet shop owner.
-
-Here's a preview of what's covered:
-
-* Setting up The Development Environment
-* Creating a Truffle Project using a Truffle Box
-* Writing and Testing a Smart Contract
-* Creating a UI to Interact with our Smart Contract
-
-By then end of the tutorial you'll have a shiny new dapp with which you can reserve pets for adoption.
-
-![The Completed Pet Shop Dapp](/img/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/pet-shop-preview.jpeg "The completed dapp.")
-
-In the future we'll be building on this tutorial with others such as deploying to live testnets and additional, more advanced functionality. We hope you enjoy and thank everyone for your support!
-
-Got stuck? The fastest way to get help is from our [community Gitter channel](https://github.com/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions.
-
-Love it? Send us your feedback on [Twitter](https://twitter.com/trufflesuite).
-
-Found a problem? Let us know by raise a [GitHub issue](https://github.com/trufflesuite/trufflesuite.com/issues) if there's something you think we can improve! Pull requests are always welcome!
-
-Cheers!
-
--- Josh & the Truffle Team
diff --git a/src/blog/one-hundred-documentation-pull-requests/index.md b/src/blog/one-hundred-documentation-pull-requests/index.md
deleted file mode 100644
index 347a0cbdb..000000000
--- a/src/blog/one-hundred-documentation-pull-requests/index.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: One hundred documentation pull requests? Yes please.
-hide:
-  - navigation
----
-
-Greetings! The Truffle team has been growing over the course of the last year. From a single developer, we are now a team of five (soon to be even more), which means that we can spread the work around.
-
-As a new full-time member of the team, I've first taken to looking at our existing materials to ensure that everything is up-to-date and working well.
-
-For example, our website, a public GitHub repository, had been receiving pull requests (PRs) for the better part of a year, and they had been languishing for want of someone to go through them.
-
-We're not talking a few or even a dozen. We're talking **almost 100 PRs**.
-
-All I can say is: **wow**.
-
-I've been working in the open source software world for about a decade, and I've never seen so many people freely offering suggestions to documentation. As we all ruefully know, documentation can be first to go out of date and last to be updated, so knowing that our community is keeping such an eagle eye on even minute details says a lot.
-
-And I do mean *minute details*. When one of our tutorials wrote "tag a stab" instead of "take a stab", not less than [ten of you took the time to submit pull requests](https://github.com/trufflesuite/trufflesuite.github.io/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aclosed%20tag%20take) telling us so.
-
-</div><div class="text-center container">
-  ![Take a stab, indeed](/img/blog/one-hundred-documentation-pull-requests/take-a-stab.png)
-  <p class="caption">Take a stab indeed</p></br></br>
-</div><div class="container container-narrow">
-
-Make no mistake: this is good thing. I believe in the [Broken Windows theory](https://en.wikipedia.org/wiki/Broken_windows_theory) as it applies to documentation. **We want to fix up the small things now so we can maintain the larger things more easily in the future.**
-
-We have big plans for our content here, just like we have big plans for Truffle. (Check out the new features coming in Truffle 4 (<https://github.com/trufflesuite/truffle/releases/tag/v4.0.0-beta.0>)!) And note that [we have since separated out the website source code to its own repository](https://github.com/trufflesuite/trufflesuite.com) to make submissions easier for the community.
-
-I'm happy to be part of a community that cares about what we're doing, reducing the bar to developing Ethereum dapps, and making them delicious.
-
-As for your suggestions on how we can serve you even better? Please keep them coming. Submit a pull request to our documentation, reach out on [Twitter](https://twitter.com/trufflesuite), or let us know if there's something we can improve by raising a [GitHub issue](https://github.com/trufflesuite/trufflesuite.com/issues).
-
-Need help with something? Reach out on our [community Gitter channel](https://github.com/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions. 
-
--- Mike & the Truffle team
-
------
-
-*Mike Pumphrey is an Enterprise Trainer at ConsenSys working on the Truffle team. With over a dozen years of experience in documentation, support, and training, Mike is passionate about making technical concepts understandable to a wider audience. He believes that great software can only be great when people know how to use it, and is excited to be bringing clarity to a field as exciting and new as blockchain.*
diff --git a/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md b/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
deleted file mode 100644
index 394411332..000000000
--- a/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: Open call for contributions by Truffle + PegaSys - EEA private transactions
-hide:
-  - navigation
----
-
-# Open call for contributions by Truffle + PegaSys: EEA private transactions
-![Pegasys Truffle Open Call For Contributions](https://i.imgur.com/GLw8iok.jpg)
-
-## What's missing?
-
-In its current state, Truffle doesn't support EEA private transactions. Support for the web3js-eea library is needed for this to work and PegaSys has recently made an implementation of the v4.0 EEA specification.
-
-## Why did this happen?
-
-The `interface-adapter` in Truffle’s codebase doesn’t provide an adapter for the  EEA 4.0 client spec, therefore private transactions aren’t working.
-
-The EEA client specification is a developing specification and  Truffle has not yet implemented the EEA client specification around private transactions.  PegaSys is providing an implementation of the specification for private transactions.  Pegasys and Truffle are teaming up to ensure that Truffle supports the EEA JSON RPC API methods.
-
-## What's the solution?
-PegaSys and Truffle have teamed up to make a single open call for contributions. This guest blog post is made by the PegaSys team and is to be posted on the Truffle blog and promoted by both teams in order to add code to Truffle codebase to add support for them.
-
-The solution involves using a Delegation pattern to help make that work.
-
-The location of the files to be modified can be found here:
-[truffle/packages/interface-adapter/lib](https://github.com/trufflesuite/truffle/tree/develop/packages/interface-adapter/lib)
-
-In short, when Truffle receives a transaction, it should determine if its a `privateFor` transaction. If so, it would delegate the rest of the business logic to the EEA library. If not, it should just continue processing the transaction with the original web3 methods.
-
-Also, it would be very useful to make sure this plays nicely with the getTransactionReceipt methods later in the chain of events.
-
-## What to do Exactly?
-
-The initial process involves adding an EEA definition to the shim file. The `web3-shim.ts` file currently contains the overloads for the different interface definitions and their mappings.
-
-``` typescript
-import { EthereumDefinition } from "./ethereum-overloads";
-import { QuorumDefinition } from "./quorum-overloads";
-import { FabricEvmDefinition } from "./fabric-evm-overloads";
-
-const initInterface = async(web3Shim: Web3Shim) => {
-
-    const networkTypes: NetworkTypesConfig = new Map(Object.entries({
-      "ethereum": EthereumDefinition,
-      "quorum": QuorumDefinition,
-      "fabric-evm": FabricEvmDefinition
-    }));
-
-    networkTypes.get(web3Shim.networkType).initNetworkType(web3Shim);
-  }
-```
-
-The initial import and mapping has been done [in this fork](https://github.com/faraggi/truffle).
-
-``` typescript
-import { EthereumDefinition } from "./ethereum-overloads";
-import { EEADefinition } from "./EEA-overloads";
-import { QuorumDefinition } from "./quorum-overloads";
-import { FabricEvmDefinition } from "./fabric-evm-overloads";
-
-const initInterface = async(web3Shim: Web3Shim) => {
-
-    const networkTypes: NetworkTypesConfig = new Map(Object.entries({
-      "ethereum": EthereumDefinition,
-      "EEA": EEADefinition,
-      "quorum": QuorumDefinition,
-      "fabric-evm": FabricEvmDefinition
-    }));
-
-    networkTypes.get(web3Shim.networkType).initNetworkType(web3Shim);
-  }
-```
-
-
-The [rest of the owl](https://i.imgur.com/4fVoQoQ.png) is to add the needed logic in the `eea-overloads.ts` file and the `overrides` variable for it to interact with the [web3eeajs library](https://www.npmjs.com/package/web3-eea).
-
-![PegaSys owl](https://i.imgur.com/4fVoQoQ.png)
-
-
-## Who can do this?
-
-Anyone who'd like to try can very much do so we will gladly support any developer who wants to help out.
-But here are some recommended prerequisites:
-
-The Truffle codebase is mainly written in `javascript`, and this particular interface-adapter library we'll be looking at is written in `typescript`.
-So knowing some javascript is a must.
-
-It will definitely help if you've had some exposure and usage of the Truffle library. Nothing fancy, just using it for compiling and deploying contracts for example.
-Likewise, having some previous knowledge of the web3js library is going to prove quite helpful.
-
-All of the above somewhat describes a general dapp developer- so in other words; if you've already written a dapp before using Truffle, this contribution could be done by you.
-
-So what's in it for you?
-Two things:
-- You'll receive some 😎 PegaSys Swag!
-- We'll personally thank and credit you on stage at [Trufflecon at my Permissioning  Talk](https://twitter.com/trufflesuite/status/1150929297647034374)
-
-
-For more information or help on this contribution, contact [Felipe](mailto:felipe.faraggi@consensys.net) from [PegaSys](https://pegasys.tech),  or write us on [our gitter channel](https://gitter.im/PegaSysEng/pantheon).
-
diff --git a/src/blog/removing-installation-issues-continued-testrpc/index.md b/src/blog/removing-installation-issues-continued-testrpc/index.md
deleted file mode 100644
index 52429e4a9..000000000
--- a/src/blog/removing-installation-issues-continued-testrpc/index.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Removing installation issues, con't - TestRPC
-hide:
-  - navigation
----
-
-<p class="alert alert-info">
-**Update**: Since this blog post was published, we have released [Ganache](/ganache) a personal blockchain and a replacement to the TestRPC. We have left this post unaltered, but we highly recommend checking out our [Ganache Quickstart](/docs/ganache/quickstart) page.
-</p>
-
-If you've been following along, you'll know that we recently [removed most if not all installation issues from Truffle](/blog/how-were-making-installation-issues-a-thing-of-the-past). For us it was a pretty big deal: Installation issues were, by far, the number one issue plaguing new users on any platform. We thought our solution was novel, so we blogged about it, and the biggest reaction we received from users was, "This is awesome, thank you! But can you do it for the TestRPC too?" Well you asked, and today we delivered.
-
-The [TestRPC](https://github.com/ethereumjs/testrpc) has always been the sister application to Truffle, and for good reason. The TestRPC gives users a personal blockchain with which to develop, drastically lowering the barrier to entry of Ethereum development and removing the need for mining or dealing with real Ether. Developing on the TestRPC is an integral part of every Ethereum project, and it's usually the first blockchain deployed to in a professional Ethereum developer's workflow. We'll be blogging about the ideal Truffle workflow a bit later, but instead of waiting, you can just let [Chris Hitchcott from Digix Global show you how it's done](https://youtu.be/SFW6W-DIdIo?t=1079). (Thank you Chris, this was a great presentation.)
-
-Fixing installation issues on the TestRPC required the [very same solution](/blog/how-were-making-installation-issues-a-thing-of-the-past) as fixing them on Truffle, so we won't go into detail here. However, I will say the solution worked _even better for the TestRPC_ than it did for Truffle. This is because the bundle we were able to create didn't require any external dependencies, making the package that you install just a single download. When compared to the old installation, the experience is night and day.
-
-## Getting the new version
-
-Like Truffle, we need you to put this version through its paces before we can release it as an official version, so we've **released it in beta**.
-
-To get the beta version, first uninstall the version of the TestRPC you currently have (because they'll conflict):
-
-```shell
-$ npm uninstall -g ethereumjs-testrpc
-```
-
-And now install the beta version:
-
-```shell
-$ npm install -g ethereumjs-testrpc@beta
-```
-
-(If you're on a Unix-based system, you may have to prefix the above commands with `sudo`.)
-
-You'll notice that the beta version installs instantly, quicker than you can say, "Holy crap, this is awesome."
-
-## So what's next?
-
-We have a lot of things planned for the TestRPC. We're not ready to officially announce everything just yet, but know that solving these installation issues is a stepping stone to providing you the best Ethereum development experience possible. Like creamy ganache filling is to a chocolate truffle, so is the TestRPC to the core of your workflow. So stay tuned. It's gonna be sweet.
-
--- Tim & the Truffle Team
diff --git a/src/blog/sandbox-forking-with-truffle-teams/index.md b/src/blog/sandbox-forking-with-truffle-teams/index.md
deleted file mode 100644
index bbf226122..000000000
--- a/src/blog/sandbox-forking-with-truffle-teams/index.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Simulate Live Networks with Forked Sandboxes
-hide:
-  - navigation
----
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/sandbox-forking-with-truffle-teams/sandbox-forking-blog.png" alt="Sandbox Forking" style="width:100%">
-</figure>
-
-Sandboxes in Truffle Teams are the easiest way to setup a shared Ganache instance for the entire team. They integrate seamlessly with our deployments manager, and work locally as expected too: insert the mnemonic and RPC URL into your Truffle config or browser wallet and starting sending ether, deploying contracts, interacting via the console and more! We’re not stopping there though. Today we’re proud to introduce live network simulation via sandbox forking!
-
-## Introducing Forking
-
-Forking allows a sandbox to act as a live network from a given block number. We take for granted in web2 that we can get test credentials and interact with an API that will map to our production environment, but in web3 this hasn’t been so easy. With a forked sandbox you can transact, deploy, test, and debug against Mainnet without spending real Ether!
-
-Forking has been available since 2017 ([see this older tutorial](/guides/chain-forking-exploiting-the-dao)), but the requirement of a full archival node was a barrier for many. By adding this ability to Truffle Teams, you no longer need to worry about anything--just select a network and go. Here are some more specific examples:
-
-* **DeFi**: Some DeFi protocols have testnet deployments that differ from their Mainnet counterparts for a variety of reasons. For dapp developers, this inconsistency presents a problem. You want to develop against the “real” protocol, but developing in production is terrible, especially when real ETH is at stake! With forking, you’re free to simply fork Mainnet and deploy your dapp to an environment that translates to the live network.
-
-* **Testing**: Ensuring your dapp integrates with another used to require getting those contracts, deploying them to your local test network or a live testnet (assuming there’s no comparable testnet deployment already), then finally running your tests. With a forked sandbox your target dapp is already there, with its state. Want to test your CryptoKitty item? You can do it with your actual kitty!
-
-* **Security Analysis**: Dynamic analysis, the process of executing code and data in real-time with the hope of finding issues during execution, has never been easier. With the ability to take control of any account on the given network and travel through time by selecting an older block, you can run attacks live and see exactly what went wrong.
-
-## How to Create a Forked Sandbox
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/sandbox-forking-with-truffle-teams/forking-details-for-blog.png" alt="--stacktrace-extra" style="width:100%">
-  <figcaption class="text-center font-italic">A forked Mainnet sandbox.</figcaption>
-</figure>
-
-To fork a network, create a new sandbox and check the forking checkbox. From there, select a network and optionally provide a block number. Clicking CONFIRM will spin up a new Ganache instance forked from the given network and block. For more details, <a href="/docs/teams/sandboxes/sandbox-forking" target="_blank">see our sandboxes documentation.</a>
-
-You can now interact with this sandbox as you would the forked network. Using Ethereum 
-Mainnet as an example: you can call out to Mainnet contracts, and send ETH to Mainnet addresses.
-<div class="mt-12 text-center">
-    <a class="btn btn-truffle mt-3" href="/docs/teams/getting-started/creating-an-account" target="_blank">START TESTING AGAINST PRODUCTION NETWORKS TODAY!</a>
-  </div>
-
-## How Will you Use Forking?
-We’re very proud of this feature and think it’s going to be a game-changer for the community. We’re curious: how will you use forking?
-
-We want Truffle Teams to be the most effective devops tool in the blockchain space for both new and existing teams. <a href="https://trfl.co/become-a-truffler" target="_blank">Join our slack community</a> and let us know what you think about this feature, and if your team has other needs we haven’t met yet.
-
-**Thank you!**
-
-Josh Quintal, Head of Product & Marketing
-
diff --git a/src/blog/stack-tracing-with-truffle-test/index.md b/src/blog/stack-tracing-with-truffle-test/index.md
deleted file mode 100644
index c442e5083..000000000
--- a/src/blog/stack-tracing-with-truffle-test/index.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Stack Tracing with Truffle Test
-hide:
-  - navigation
----
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog-header-stacktraces.png" alt="--stacktrace-extra" style="width:100%">
-</figure>
-
-Truffle Test can now provide stacktraces when your transactions revert! This is still a little experimental, and it requires `truffle test` to recompile all your contracts, so you’ll have to enable it with `truffle test --stacktrace`. 
-Here’s what the result looks like:
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog1.png" alt="truffle test --stacktrace" style="width:100%">
-  <figcaption class="text-center font-italic">truffle test --stacktrace</figcaption>
-</figure>
-
-The stacktrace continues seamlessly from the Javascript test into the Solidity contracts. It begins in the Javscript where the transaction was sent, continues through the contract that initially received the transaction, and finally ends in the contract where the revert occurred.
-
-These Solidity stacktraces will be printed both for reverted transactions sent during tests and for reverted deployments made during tests with `Contract.new()`. Stacktraces are not currently available for calls or gas estimates. Note that stacktraces are a Truffle Contract feature, and will not be available if transactions are sent by other means.
-
-What if we want a little more? Looking at the above example again, one of our stacktraces helpfully included a revert message, but the other did not. Wouldn’t it be nice if it had one too? Let’s try this again, but this time with `--stacktrace-extra`:
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog2.png" alt="--stacktrace-extra" style="width:100%">
-  <figcaption class="text-center font-italic">--stacktrace-extra</figcaption>
-</figure>
-
-There we go! The `--stacktrace-extra` option, in addition to turning on stacktraces, additionally compiles your contracts with Solidity’s debug mode, so you get more information about just why the transaction reverted.
-
-Of course, for more detailed analysis, you may want to use Truffle Debugger! But stacktraces in tests can give a good first view of why your transaction reverted.
-
-These testing options are still a little experimental, so it’s possible some things may not work with them. But, in most cases, they should provide a quick helpful view into why your test transaction reverted!
-
-Thanks,
-
-Harry Altman
-
---Debugger Engineer, Truffle Suite
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-6" href="https://github.com/trufflesuite/truffle/releases/tag/v5.1.24">Click here for the release notes on GitHub</a>
-</div>
diff --git a/src/blog/sunsetting-truffle-teams/index.md b/src/blog/sunsetting-truffle-teams/index.md
deleted file mode 100644
index ad9334a34..000000000
--- a/src/blog/sunsetting-truffle-teams/index.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Sunsetting Truffle Teams
-hide:
-  - navigation
----
-
-![Sunsetting Truffle Teams Banner](/img/blog/sunsetting-truffle-teams/blog-header.png)
-
-<p class="alert alert-warning">
-<i class="far fa-info-circle"></i> <strong>N.B</strong>: we published an earlier version of this blogpost with an incorrect timeline. Truffle Teams will be sunset on September 10, 2021.</a>
-</p>
-
-After a 2 year long road, we're sunsetting Truffle Teams (effective September 10th, 2021). 
-
-The journey began when Truffle was an independent company. It extended our reach from dapp development into dapp maintenance. We've gained valuable insights about the state of blockchain devops, the most desirable parts of our tools, and a new clarity around our core competencies.
-
-As an independent company, Truffle Teams was integral to building a business for the long-term, but it came with some costly tradeoffs. Over time the resources required to develop and maintain it were too great, taking time away from development of our open-source tools and eventually taking time away from supporting tasks like ecosystem engagement and development. This was unsustainable.
-
-Another important factor made this sunsetting possible: The acquisition of Truffle Suite by ConsenSys Software granted us greater supporting resources and freed us from monetary metrics. Which leads us to some good news! We are reaffirming our commitment to having the best-in-class open-source blockchain developer tools.
-
-## What about paid subscribers?
-
-All active Pro and Enterprise tier users will receive a refund of 1 month and recurring billings will cease. If you don't see a refund within 5 days (Paddle's processing time), email us at [truffle-teams@trufflesuite.com](mailto:truffle-teams@trufflesuite.com).
-
-## What about my data?
-
-All user data will be deleted 30 days following the date of shut down (September 10th 2021). Be sure to request your data before this time, otherwise we'll be unable to guarantee recovery. If you would like a dump of your data, email us at [truffle-teams@trufflesuite.com](mailto:truffle-teams@trufflesuite.com).
-
-**All user data will be deleted on September 10th, 2021.** Make sure to request your data before this time, otherwise we'll be unable to recover it.
-
-## The afterlife is open-source
-
-Parts of Truffle Teams will be making their way into our open-source tools! We're happy to share one right now--repackaging the visual debugger as a plugin that allows you to launch an instance from within Truffle. Truffle Teams provided greater context around your dapps activity thanks to its GUI. Being able to pull up a list of transactions from a Ganache instance, filter by failures, and clicking a debug button was one of the better workflows that we're proud to integrate with our open-source suite.
-
-These repurposed bits will all be open-source, so you can [check out the `truffle-plugin-debugger` repository here.](https://github.com/trufflesuite/truffle-plugin-debugger)
-
-<figure>
-  <img class="mb-4 w-100" src="/img/blog/sunsetting-truffle-teams/visual-debugger.png" alt="the Truffle Teams visual debugger--coming to Truffle!">
-  <figcaption class="text-center font-italic">The Truffle Teams visual debugger--coming to Truffle!</figcaption>
-</figure>
-
-If there are other features you'd like to see again, for example the deployments screen or contract manager, let us know!
-
-Sincerely,
-
-_The Truffle Suite Team_
diff --git a/src/blog/take-a-dive-into-truffle-5/index.md b/src/blog/take-a-dive-into-truffle-5/index.md
deleted file mode 100644
index 065a9d89d..000000000
--- a/src/blog/take-a-dive-into-truffle-5/index.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: Take a Dive into Truffle 5
-hide:
-  - navigation
----
-
-![Take a Dive into Truffle 5 Banner](/img/blog/take-a-dive-into-truffle-5/blog-header.png)
-
-Truffle 5 has had some exciting releases in the flexibilty they provide to your workflow. 🌊 Truffle now offers the ability to detect the version of Solidity in your contracts at compile time and allows for compilation from ABI files. Because of this, wrangling a project whose contracts use multiple version of Solidity is much easier going forward. We've also enhanced our testing capabilities with Solidity strack traces and better event decoding, making it much easier to get to the source of an error and get richer information from events. When our projects integrate with existing protocols, it's a pain to have to deal with those external contracts. Now Truffle makes this easy with the ability to fetch external contracts verified on Etherscan! Vyper support continues to improve with experimental debugging for Vyper contracts, as well as improved import handling for Vyper.
-
-Did I mention support for **decentralized file storage**?
-
-## What's New in 5.2 and 5.3
-
-### IPFS, Filecoin, and Textile Bucket support via `truffle preserve`
-
-Tests have ran, bugs are squashed, your smart contracts have been deployed successfully to mainnet; life is good. It's time to make your dapp accessible to the masses! So you... go to a centralized host and spin up the frontend? Something's definitely off here.
-
-Enter `truffle preserve`: You can now use Truffle to upload your static assets to [IPFS](https://ipfs.io/), [Filecoin](https://filecoin.io/), and/or [Textile Buckets](https://docs.textile.io/buckets/) for a fully decentralized application across the entire stack!
-
-Here are some companion pieces to help you get started:
-- The [Filecoin Truffle Box](https://github.com/truffle-box/filecoin-box) includes a decentralized art gallery to get you started with a fully working project!
-- [The original Filecoin + Truffle & Ganache Blog Post](/blog/truffle-and-ganache-now-come-in-filecoin-flavor)
-- [`truffle preserve` Documentation](/docs/truffle/getting-started/preserving-files-and-content-to-storage-platforms)
-
-<figure>
-  <img class="mb-4 w-100" src="https://github.com/truffle-box/filecoin-box/raw/master/screenshots/sample-ui.png?raw=true" alt="the Filecoin Trufflebox provides you with a Filecoin powred art gallery">
-  <figcaption class="text-center font-italic">Unbox a decentralized art gallery with the Filecoin Truffle Box.</figcaption>
-</figure>
-
-### Pragma compilation
-
-As of version 5.2.0, Truffle now ships with a fun, experimental setting for compilation: the “pragma” setting. This feature analyzes your Solidity source files for their pragma expressions. It then uses these expressions to figure out which version of the Solidity compiler is required for each given source. This allows your project to compile when it contains multiple Solidity files, each requiring a different version of the Solidity compiler!
-
-To use this feature, set the Solidity compiler version field in your `truffle-config.js` as follows:
-
-```javascript
-module.exports = {
-  compilers: {
-    solc: {
-      version: “pragma”
-    }
-  },
-  // … the rest of your config goes here
-};
-```
-
-Now you can run `truffle compile` and your project will compile!
-
-To illustrate this feature and the ones below, we have created a [Truffle box for Truffle 5.2](https://github.com/truffle-box/v5.2-example-box).
-
-In this box you can see how the `truffle-config.js` is set up to use this new experimental feature. Notice that `contracts/MetaCoin.sol` requires `^0.7.0` and how `contracts/Conversion.sol` requires `^0.6.0`. When running `truffle compile` on this example project you should get a printout of all the versions of the Solidity compiler used during compilation. Namely, you should see that both version `0.6.12` and `0.7.6` are listed.
-
-When you use this feature, Truffle will analyze each of your Solidity sources one by one to find the appropriate version of the Solidity compiler for each source. Do note, however, that each source file and all of its imports must be compiled with one version of Solidity; this means there must be a version of the compiler that satisfies all of their pragma expressions.
-
-## Things you may have missed in Truffle 5.1
-
-We’ve added a fair bit over the course of Truffle 5.1 as well, and there’s a good chance you didn’t catch all of it!  We thought this would be a good time to review some of that as well!
-
-### Compilation of abi.json files
-
-Another exciting addition to Truffle is the ability to compile from a contract’s ABI. When you create a JSON source file in your “contracts” directory that contains a contract’s ABI, Truffle will take it, use it to create an interface, and compile it. This might come in handy, for example, when you want to import and use a library that requires a different version of the Solidity compiler than the importing file. You can then simply compile the library and create a new JSON file containing the ABI of the imported library. Under the hood Truffle will compile the ABI into a Solidity interface and create an artifact for it. You will then be able to import the interface into your contract!
-
-In the v5.2-example-box, consider the `contracts/MetaCoin.sol` and `contracts/Conversion.sol`. We would like to import Conversion into the MetaCoin contract to use it but cannot since they require different versions of the Solidity compiler.  To work around this, we have created `contracts/IConversion.abi.json` which contains the ABI from the compiled Conversion. In this way we can now import the interface into `contracts/MetaCoin.sol` (see line 4 in the MetaCoin contract) to use it!
-
-### Solidity stacktraces in Truffle Test
-
-Try running your tests with the `--stacktrace` option (or `-t` for short) and get combined Solidity-Javascript stacktraces!  This feature does have some limitations and is still somewhat experimental, but we expect you’ll find it quite useful.  In the future we may add support for Vyper stacktraces as well!  
-
-And speaking of Vyper...
-
-### Experimental Vyper debugging
-
-You can now use Truffle Debugger with Vyper!  Support for this is still in its early stages; you won’t be able to inspect variables, I’m afraid.  But you can step through a Vyper transaction, and there will likely be more in the future!
-
-But perhaps the biggest improvement to the debugger is...
-
-### Debugging verified external contracts
-
-Use the `--fetch-external` (or `-x` for short) option with Truffle Debugger and it will automatically download sources for any verified contracts and allow you to step through them!  Contracts can be verified on either Etherscan or Sourcify.  You no longer need to download these yourself and add them to your Truffle project!  You can see [this](/blog/debugging-verified-external-contracts-with-truffle-debugger) earlier post for more information.
-
-###Improved import handling in Vyper
-
-Here’s another one for our Vyper users; you can now do imports from other projects (via NPM or EthPM) just like in Solidity!
-
-For instance, suppose `examplepackage` is an NPM package which is structured as a Truffle project, and you want to import a Vyper contract, `VyperContract`, from it.  You can now do
-
-```python
-from examplepackage.contracts import VyperContract
-```
-
-or
-
-```python
-import examplepackage.contracts.VyperContract as VyperContract
-```
-
-to import it, much like you could do in Solidity!
-
-Note that if your own project uses such “absolute” imports as a way to import its own files from the project root -- e.g., if you have a file `contracts/subdirectory/Contract1.vy` which imports `contracts/Contract2.vy` via
-
-```python
-import Contract2 as Contract2
-```
-
-then this will work within your own project, but won’t work if other people try to import your `Contract1`.  We suggest that if you want other people to import contracts from your project, you use explicitly relative imports instead:
-
-```python
-from .. import Contract2
-```
-
-But such imports are now possible.  We hope you’ll find all sorts of uses for this!
-
-### Enumeration values in Truffle Contract objects
-
-When sending a transaction that takes an `enum`, it’s inconvenient to have to look up the numeric constants that the `enum` uses.  Well, now, each Truffle Contract constructor object contains enumeration constants, so you don’t need to do that.  Just do
-
-```javascript
-contractInstance.exampleMethod(Contract.ExampleEnum.EnumValue);
-```
-
-and don’t worry about the particular numeric value of `EnumValue`.  You can also do `Contract.enums.ExampleEnum.EnumValue`, if you want to be extra-certain.
-
-Note that it’s not currently possible to access enums declared outside of a contract this way, but we have plans in the future to make using those easier, too!
-
-### Even more!
-
-Other things you might have missed include: Improved event decoding in `truffle test`; being able to use the debugger to step through Yul (assembly) sources generated by Solidity for its own internal subroutines (try the `g` command!); being able to inspect assembly variables in the debugger; `truffle test --bail`; `truffle create all`; and the debugger providing more information upon transaction reversion.
-
-### What's Next? Want to Help us Build it?
-
-How will you use the new enhancements in Truffle? Let us know what you think about these features on Twitter, and if you have other needs we haven’t met yet.
-
-<p class="alert alert-info m-t-2">
-<i class="fas fa-info-circle"></i> <strong>WE'RE HIRING!</strong> Why stop at feature requests--cut out the middleman and work with us directly! There are many exciting problems to solve like layer 2 support, mapping decoding, and a revamped deployment system, to name a few. We'd love your help and perspective. <strong><a href="https://consensys.net/open-roles/3004215/">Apply here on ConsenSys' website!</a></strong>
-</p>
diff --git a/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md b/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
deleted file mode 100644
index 93b4b1f9f..000000000
--- a/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Take Control of Your Deployments with Truffle Teams
-hide:
-  - navigation
----
-
-![Truffle Teams Deployments Banner](/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/truffle-teams-deployments-banner.png)
-
-If you read our [blog post back in July](/blog/an-easier-way-to-deploy-your-smart-contracts), attended my TruffleCon workshop **Push It! Push It Real Good: Truffle Teams Intro & Deployments** back in August, or tuned in last week to our **Truffle Teams Overview** webinar, you've known something awesome has been in the works for Truffle Teams.
-
-Well it's finally here! On behalf of the whole team, I'm excited to announce Deployments within Truffle Teams!
-
-<a target="_blank" href="/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/deployments.png">![Deployments](/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/deployments.png)</a>
-
-## Bridging the Gap Between Local Ganache Testing and Public Testnet/Mainnet Deployments
-
-The interaction between Truffle and Ganache provides an awesome way to iteratively test and fix contracts on a personal Ethereum blockchain. However, it can be a little tricky when you're ready to publish your application to the rest of the world. That's where Truffle Teams Deployments comes in: we give you a **dead-simple deployment experience** which links with MetaMask so you never need to export your private keys.
-
-## Benefits of Deploying with Truffle Teams
-
-- **Easily deploy to public Ethereum networks** (Mainnet, Ropsten, Görli, Rinkeby, and Kovan are supported)
-- **Works with the existing migration scripts** in your Truffle project; Truffle Teams uses `truffle migrate` under the hood
-- **No need to export/import private keys** — use [MetaMask](https://metamask.io/) to deploy like you would with any other dapp
-- **Deploy with [Ledger](https://www.ledger.com/) or [Trezor](https://trezor.io/) hardware wallets** within MetaMask
-
-## Learn More in Our Tutorial or Try It Now!
-
-We put together a step-by-step [tutorial](/guides/learn-how-to-deploy-with-truffle-teams) to guide you through your first Truffle Teams deployment. While we recommend that you follow the tutorial (as it answers some FAQs), the deployment experience is simple enough for you to just give it a shot! 👇
-
-<div class="post-trufflecon-box mt-5 text-center">
-  Get started with Truffle Teams, and see deployments for yourself!
-
-  <div class="mt-3">
-    <a class="btn btn-truffle" href="/docs/teams/getting-started/creating-an-account">Try Truffle Teams</a>
-  </div>
-</div>
\ No newline at end of file
diff --git a/src/blog/testrpc-is-now-ganache/index.md b/src/blog/testrpc-is-now-ganache/index.md
deleted file mode 100644
index 6166510a0..000000000
--- a/src/blog/testrpc-is-now-ganache/index.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: TestRPC is now Ganache
-hide:
-  - navigation
----
-
-Have you been looking for the TestRPC recently and haven't been able to find it?
-
-Don't worry, it's still here! It's just now known as **Ganache**.
-
-Ganache comes in two flavors: a fully-interactive development blockchain with a graphical interface, and the more familiar command-line version.
-
-* [Get the graphical version here](/ganache).
-
-* For the command-line version (known as **Ganache CLI**):
-
-  ```shell
-  npm install -g ganache-cli
-  ```
-
-## A little history
-
-Prior to the existence of the TestRPC, you would have to deploy to private internal test networks to see how your contract code operated (as public test networks like Ropsten didn't yet exist!).
-
-While initially under the auspices of the [EthereumJS project](https://github.com/ethereumjs/), it was originally created by the Truffle team, and today we remain its primary maintainers. So simply for maintainability sake, it just made sense to bring the TestRPC under Truffle's wing.
-
-Additionally, we realized over time that the TestRPC was a poor name. The TestRPC quickly became more powerful than simply a blockchain environment used for testing. To stay with the sweet Truffle brand, we decided to rename it Ganache, as Ganache is (often) the core of your favorite chocolate truffle. It's a much catchier name (and a much tastier one too).
-
-## Multiple ways to enjoy
-
-With this name change, we also released [a fully-interactive, graphical version of Ganache](/ganache).
-
-The command-line utility is still available via NPM; the [command line flags](https://github.com/trufflesuite/ganache-cli/blob/master/README.md) are the same too. All that's changed is the name of the command.
-
-Ganache is also available as a library for your applications. See the [README](https://github.com/trufflesuite/ganache-cli/blob/master/README.md) for more details.
-
-So now you have multiple ways to create a personal blockchain. If you're looking for a blockchain with a graphical environment that's perfect for beginners, check out [Ganache](/ganache). And if you want the familiar command-line interface, install Ganache CLI. Happy developing!
diff --git a/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md b/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
deleted file mode 100644
index 75b120766..000000000
--- a/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: The Best Things to do in Seattle During TruffleCon
-hide:
-  - navigation
----
-
-![river view at Marymoor Park](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-1.jpg)
-
-## [Marymoor Park](https://www.kingcounty.gov/services/parks-recreation/parks/parks-and-natural-lands/popular-parks/marymoor.aspx)
-
-Marymoor Park, located on the north end of Lake Sammamish in Redmond, Washington, is King County's largest, oldest, and most popular park, with more than 3 million annual visitors coming to roam its 640 acres. Marymoor is famous for its [outdoor concert series](https://www.marymoorconcerts.com/events) during the summer. You can catch concerts on Aug 2 and Aug 4 after the day festivities at TruffleCon!
-
-## [Sammamish River Trail](https://www.alltrails.com/trail/us/washington/sammamish-river)
-
-The Sammamish River Trail is a beautiful 19-mile bike path and recreational trail in King County, Washington that runs along the Sammamish River from Blythe Park in Bothell to Marymoor Park in Redmond. There are several places along the trail you can enter. It's perfect for biking, running, or just enjoying a nice walk in the beautiful outdoors!
-
-## [Idylwood Beach Park](https://experienceredmond.com/activities-and-attractions/idylwood-beach-park/)
-
-August can reach temperatures of up to 80 degrees, which is quite hot for Seattleites. Idylwood Beach Park is one of the best places to cool off. It's a waterfront park on Lake Sammamish with a beach, boat ramp, playground & canoe rentals.
-
-## [Microsoft Visitor Center](https://experienceredmond.com/activities-and-attractions/microsoft-visitors-center/)
-
-The Microsoft Visitor Center is open during the weekdays. Walk through the doors of the Microsoft Visitor Center and unlock your potential—experience everything from the latest Microsoft Research innovations to the very first personal computer. Microsoft offers self-guided tour information to explore hands-on exhibits featuring some of the company's most exciting technologies for home and business.
-
-![entrance to Microsoft Visitor Center](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-2.jpg)
-
-## [Woodinville Wine Country](https://woodinvillewinecountry.com/)
-
-Nestled in the beautiful Sammamish River Valley just 30 minutes northeast of Seattle, Woodinville Wine Country is home to over 100 wineries and tasting rooms representing every appellation in Washington.
-
-From the historic and beautiful grounds of Chateau Ste. Michelle to the quaint boutique wineries where you are likely to have the winemaker themselves pour you a glass of his or her finest blend, a wonderful variety of wine tasting experiences awaits you!
-
-![winery building in the Sammamish River Valley](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-3.jpg)
-
-## [Black Raven Brewing Company](https://www.blackravenbrewing.com/)
-
-Black Raven is a neighborhood brewery with a friendly retail taproom, The Raven's Nest, with locations in both Redmond and Woodinville. The Raven's Nest is not a traditional brewpub; it's more like our brewery's living room. Open 7 days a week and a seating capacity of about 100, it's home to local beer lovers who want to be a part of a community that enjoy great beer and great friends.
-
-## [Mac & Jack's Brewing](https://www.macandjacks.com/)
-
-Mac and Jack's brewing offer a tasting room, retail store, beer garden, and tours at their brewery in Redmond, WA. Mac & Jack's started out of Jack's garage in 1993, with nothing but a passion for exceptional beer. Lots of hops and 26 years later they are still producing one of Seattle's favorite beverages.
-
-## [Flee Escape Room](https://www.fleeescape.com/)
-
-Flee Escape Game is one of the largest Seattle and Redmond Real Life Escape Rooms. So grab your team, new friends you just met, or organize a party to see if you can all make your great escape.
-
-![egyptian themed escape room](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-4.jpg)
-
-## [Paragliding](https://www.tigermountainparagliding.com/fly-tandem/)
-
-Come paraglide tandem with us, and experience free flight in its purest form! After running down a moderately steep hill you'll find yourself airborne, sitting comfortably in a reclined harness, your feet dangling above the trees, no one in front of you (pilot rides in back) and no cockpit surrounding you.
-
-Depending on conditions you'll have views of Mt. Rainier, Mt. Si, Lake Sammamish, Bellevue, Seattle, the Puget Sound and so much more. Bald eagles and other predators leave their nests to ride the same thermals allowing you to literally fly with birds.
-
-![couple having fun paragliding](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-5.jpg)
-
-## [Salish Lodge/Snoqualmie Falls](https://www.salishlodge.com/)
-
-Overlooking Snoqualmie Falls, just 30 minutes east of Seattle and Bellevue, Salish Lodge & Spa is a Washington State resort getaway, perfect for those seeking an authentic and memorable escape from the everyday. Dine on mouthwatering [Northwest cuisine](https://www.salishlodge.com/dining.php) hand-crafted from seasonal ingredients, savor the serenity of [The Spa](https://www.salishlodge.com/spa.php), then drift off to sleep in front of your cozy fireplace in one of our newly renovated guestrooms. We invite you to experience the iconic Salish Lodge.
-
-![aerial view of snoqualmie falls](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-6.jpg)
-
-## [DirtFish Rally Driving School](https://www.dirtfish.com/)
-
-Nestled in the foothills of the Cascade Mountain Range in the scenic town of Snoqualmie, WA, DirtFish Rally School was established in 2010 with the idea that the exciting sport of rally should be accessible to everyone. Armed with an immaculate fleet of turbocharged, all-wheel-drive cars, right from the beginning DirtFish was equipped to share with anyone the excitement of what a real rally car can do on a loose surface. In the fall of 2014, DirtFish embellished their offerings with the launch of rear-wheel drive programs. Similar in nature to the all-wheel drive programs, the precise and very sideways action the classes offer provides an entirely different challenge for drivers of every background. Ever since, DirtFish has become the most prestigious rally school in North America, providing the highest level of instruction, top level cars and gorgeous facilities all year round.
-
-![rally car driving on dirt road](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-7.jpg)
-
-## [Hiking](https://www.wta.org/)
-
-Hiking in nature has a positive impact on people's hearts, minds and bodies. It is vital for everyone to have the opportunity to access the outdoors, and the WTA is committed to reducing barriers to hiking trails and lands. We strive to inspire people to go outside—giving them the skills and knowledge they need to recreate safely and sustainably.
-
-People will protect the places they love to hike. WTA rallies hikers to raise our collective voice to protect the places we love. Our voice is amplified by the support of our members and sweat equity of every volunteer who helps to build and maintain trails.
-
-![beautful views of the mountains on the hiking trail](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-8.jpg)
-
-## [Mountain Biking](https://seattlemountainbiketours.com/)
-
-Your all-inclusive mountain biking tour in Seattle includes pickup from Downtown Seattle or Bellevue and shuttle transportation to our favorite trails for intermediate and experienced cyclists. At the trailhead, you get your high-quality mountain bike, a helmet, gloves, and any other safety gear needed for our ride. Don't worry, we have plenty of water and snacks for our mountain biking adventure!
-
-![mountain biker rounding the bend in Seattle](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-9.jpg)
-
diff --git a/src/blog/the-best-ways-to-contribute-to-truffle/index.md b/src/blog/the-best-ways-to-contribute-to-truffle/index.md
deleted file mode 100644
index 4dc4c0718..000000000
--- a/src/blog/the-best-ways-to-contribute-to-truffle/index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: The Best Ways to Contribute to Truffle
-hide:
-  - navigation
----
-
-Have you ever thought about contributing to Truffle? All of us at Truffle really enjoy producing free and open source software, and it is especially fun when many of you in the community contribute. User contributions make life easier for us, make our work more enjoyable by showing that you’re engaged, and often give us a chance to learn from those that offer code to the project. We’d absolutely love any and all developers to contribute to our project. The following are a few ways that you can get involved.
-
-## Read the contributor guidelines.
-
-The first step anyone should take before contributing to Truffle is to hop on over to our Github page and [read our contributing guidelines](https://github.com/trufflesuite/truffle/blob/develop/CONTRIBUTING.md). Our contributing guidelines will give you a baseline understanding of how Truffle is built, which tools to use during development, and other useful information to get you started. Make sure to read those guidelines before continuing on in this post.
-
-## Follow the command flow.
-
-You’ll see that the contributing guidelines focus on the command flow. This is because at its core, Truffle is a command line tool that processes and runs specific commands on behalf of a user. If you can figure out where a command starts, you can follow its execution to get a better understanding of what Truffle is doing. We recommend choosing your favorite command and following its path through the code. We’d also recommend performing your own local experiments by changing the behavior of a specific command and seeing how it behaves. Don’t forget to read the contributing guidelines above, as it tells you where to get started for each command.
-
-## Change callbacks to Promises.
-
-Given the lifetime of the project -- over four years! -- Truffle has its share of legacy code. Before Promises became widespread in the Node world, callbacks were used to control the flow of asynchronous code within Truffle. The code was written in a style where a callback function was passed from one method to the next, intended to be executed after everything else had finished running or when an error occurred. Nowadays, many people find this style of code to be abstruse, and hard to understand, and now favor Promises over callbacks. We do too. One of our major tasks over the coming year is to rework our code to favor a Promise-based coding style instead of a callback-based one. We are always interested in receiving PRs that clean up our callbacks and make the code easier to understand for everyone (we love you async/await).
-
-
-## Start small, and chat with us for larger tasks.
-
-It can be very overwhelming to begin contributing to Truffle with a big feature. Instead, we recommend going after a smaller, more bite-sized change that will not only make you feel more successful, but can also help you get a better understanding of the underlying code. If you find something trivial, like a documentation error, go ahead and fork the repository, make your changes, and submit a pull request. For something bigger, we like to have a discussion first as our tools support many different use cases and platforms. If you have a great idea for a change that will require significant effort, we recommend filing a GitHub issue with a proposal or contacting us using the channels below. We can layout specs, bounce ideas around, and agree on what’s needed before you dive in.
-
-## Tackle an issue.
-
-Many of our users submit issues for things that need to be fixed. Sometimes these issues are small bugs that have been able to hide in the cracks. Other times they can be large changes or feature requests that require significant effort to fix. Regardless of your appetite, our [issues list](https://github.com/trufflesuite/truffle/issues) is often a great place to start for people to contribute. Due to the nature of software, you’re bound to find an issue that’s right for you. And even if you don’t think you can fix an issue, confirming that issues exist and giving us extra information can be extremely helpful. Often the biggest factor keeping a sneaky bug alive is information, so validating an issue exists and providing more data can help us squash that bug even faster.
-
-## Contact us.
-
-As always, we’d love to hear your feedback and concerns, as well as answer any questions you have when contributing to Truffle. Feel free to reach out to us on our [Spectrum](https://spectrum.chat/trufflesuite) page, or file an issue on [Github](https://github.com/trufflesuite/truffle/issues). We'd love to hear from you. Happy Truffling!
diff --git a/src/blog/the-blockchain-problem-that-ens-solves/index.md b/src/blog/the-blockchain-problem-that-ens-solves/index.md
deleted file mode 100644
index 9ea02cef3..000000000
--- a/src/blog/the-blockchain-problem-that-ens-solves/index.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: The Blockchain UI Problem that ENS Solves
-hide:
-  - navigation
----
-
-The blockchain world has a UI problem. This is what an Ethereum receiving address looks like:
-
-**0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359**
-
-Bitcoin and other cryptocurrencies have the same problem, as do related decentralized projects like IPFS. The computer-generated address system works great for computers but isn’t user-friendly.
-
-This isn’t a new problem. The nascent Internet had a similar issue with IP addresses. For the Internet to eventually be used by millions and now billions of regular users, it needed a way to mask the machine-readable identifiers. So, in 1985, the “phone book of the Internet,” the Domain Name System (DNS), was born. While the DNS is used by many protocols, the World Wide Web really took the DNS mainstream. Can you imagine the web if users had to type in “72.125.224.72” rather than “google.com”?
-
-The blockchain world needs the same thing. We could use the existing DNS, but it’s a relatively centralized server architecture which makes it unattractive for blockchain applications.
-
-That’s where the Ethereum Name Service (ENS) comes in. ENS provides the same basic functionality of DNS (look up the records for “example.tld,” retrieve information), but replaces the hierarchical DNS server system with a few smart contracts on Ethereum.
-
-ENS is the naming service of the new decentralized Internet - with less infrastructure, better security, and of course less centralized control.
-
-ENS launched in 2017 with the native TLD.ETH, but we’ve been experimenting with allowing owners of DNS domains to use their domains on ENS and have successfully done this with .XYZ and .LUXE domains. We plan on rolling out this capability to most other TLDs later this year.
-
-We want to make it as easy as possible for dapp developers to take advantage of the big UI gains that ENS provides, which is why we’re working with Truffle. We are excited to be announcing several useful ENS integrations built into TruffleSuite at TruffleCon, so stay tuned!
-
-[Register your domain name](https://ens.domains/) using ENS today!
-
-Helpful Links:
-* Website: [https://ens.domains/](https://ens.domains/)
-* Manager: [https://manager.ens.domains/](https://manager.ens.domains/)
-* Docs: [https://docs.ens.domains/](https://docs.ens.domains/)
-* Gitter: [https://gitter.im/ethereum/go-ethereum/name-registry](https://gitter.im/ethereum/go-ethereum/name-registry)
-* Forum: [https://discuss.ens.domains/](https://discuss.ens.domains/)
-
diff --git a/src/blog/token-taxonomy-framework/index.md b/src/blog/token-taxonomy-framework/index.md
deleted file mode 100644
index b8059a4c0..000000000
--- a/src/blog/token-taxonomy-framework/index.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Token Taxonomy Framework
-hide:
-  - navigation
----
-
-To some, the sudden rise of Tokens in the blockchain dialog comes as a surprise. However, tokens have always been the bedrock of the blockchain movement. The introduction of SmartContract by Ethereum quickly overshadowed them, particularly in enterprise contexts. The capabilities of Smart Contracts and the broad acceptance of them, thanks to companies like Truffle, blazed a trail forward and we all went along. It wasn’t until we got halfway up the trail that someone turned around and asked, “did we pack any trail mix?”
-
-Sure, we had Ether, but one cannot persist on Ether alone. Focus shifted back to our roots. Developers who had steeped in SmartContracts turned their attention to tokens. However, they also brought a bit of baggage. You can do a lot in a Token using SmartContract concepts. We started to see the blurring of lines between what a contract was and what was a token, leading to a good bit of confusion all around.
-
-Back in April, [the Token Taxonomy Initiative (TTI)](https://tokentaxonomy.org/) was launched with very strong backing and a cross blockchain and platform set of founders including the EEA, ConsenSys, IBM, R3 and Digital Asset in an effort to provide clarity and purpose for tokens moving forward as the way we define value and how it can be used between parties across networks and platforms. The major deliverable from the TTI is the Token Taxonomy Framework (TTF), which is a platform neutral framework for defining and token that can eventually be certified and start to address critical issues like interoperability.
-
-![Token Taxonomy Framework](/img/blog/token-taxonomy-framework/framework.png)
-
-I’ll be presenting an [Introduction to the TTF](https://trufflecon2019.sched.com/event/RneW/token-taxonomy-framework) at TruffleCon on August 4th here in Redmond, WA. Swing by to hear how you can use the TTF to communicate with customers and partners, use the same terms and get solid requirements from the business, legal and regulatory communities.
diff --git a/src/blog/truffle-320-released/index.md b/src/blog/truffle-320-released/index.md
deleted file mode 100644
index 68219d4ba..000000000
--- a/src/blog/truffle-320-released/index.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Truffle 3.2.0 released
-hide:
-  - navigation
----
-
-<p class="alert alert-info" style="margin-top: -2rem; margin-bottom: 3rem;">
-  <strong>UPDATE</strong>: We made another minor release after this blog post was written <a href="https://github.com/trufflesuite/truffle/releases/tag/v3.2.1">upgrading web3 to 0.18.2</a> due to request of our users. <a href="https://github.com/trufflesuite/truffle/releases/tag/v3.2.1">Truffle v3.2.1</a> is now the latest release, but it still includes all the awesome stuff below.
-</p>
-
-Hi all. Great news today.
-
-Following your feedback from the Truffle 3.0 release, we've just released Truffle 3.2.0! This release includes a [number of great new features and bug fixes](https://github.com/trufflesuite/truffle/releases/tag/3.2.0), but we're most excited about the following. I've bolded the good stuff for ya.
-
-1. **We've built infrastructure for providing you boilerplates on demand!** Now with `truffle init` comes `truffle init webpack`, which gives you a boilerplate web application combining the web development capabilities of Webpack with the power of Truffle. More boilerplates to come to make your life easier, so stay tuned!
-
-1. **We've added huge speed improvements to the Truffle command line tool.** Now your commands trigger in milliseconds! Go ahead, try it out. `truffle version`
-
-1. **Solidity tests can now be given default balances** so you can use those tests to exercise sending Ether to your contracts. Big win for Solidity tests, and your sanity in general. [Documentation](/docs/truffle/testing/writing-tests-in-solidity.html#testing-ether-transactions)
-
-1. Similarly, **Javascript abstractions got an upgrade** making it easier to send Ether directly to your contracts as well as trigger your contracts' fallback functions. You can use this feature within your tests as well as within your application. [More on that here](/docs/truffle/getting-started/interacting-with-your-contracts.html#sending-ether-to-a-contract). Also, they now use web3 0.18.2.
-
-1. **Migrations got an extra scout badge (function parameter)**, [allowing you to view available accounts directly within your migration](/docs/truffle/getting-started/running-migrations.html#available-accounts)
-
-1. Oh, and **there's no more naming restriction on contract names!** 🎉🎉🎉 You can now have a file called `ImABigDeal.sol` and have it define contracts under a completely different name. Woot!
-
-1. Along with the above, **there's a new way of requiring contract artifacts within your migrations and tests**. The old way still works if your contract names match your Solidity file names, but even if they don't you can simply require the contract by name:
-
-```javascript
-// Assume `ImABigDeal.sol` defines `contract MyContract { ... }`
-var MyContract = artifacts.require("MyContract");
-```
-
-There's been a lot of bug fixes too. Check out the [release notes on Github](https://github.com/trufflesuite/truffle/releases/tag/3.2.0) for a full list of changes, upgrades and fixes.
-
-### Big thanks!
-
-As always, we have to give you all a big thanks for being a part of the community and making Truffle better. This release would not be possible without your continued feedback, bug fixes and pull requests.
-
-If you run into trouble with any of the above, reach out on our [community Gitter channel](https://gitter.im/ConsenSys/truffle) where hundreds of your fellow Trufflers congregate to answer your questions. As well, check us out [on Twitter](https://twitter.com/trufflesuite) and send us a tweet.
-
-Cheers, and happy coding!
-
--- Tim
diff --git a/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md b/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
deleted file mode 100644
index 000544e6c..000000000
--- a/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Truffle and Ganache now come in Filecoin Flavor
-hide:
-  - navigation
----
-
-![Filecoin Collab Banner with Ganache](/img/blog/truffle-and-ganache-now-come-in-filecoin-flavor/blog-header.png)
-
-[Filecoin](https://filecoin.io) was created by [Protocol Labs](https://protocol.ai), the same organization who created and maintains [IPFS](https://ipfs.io). Filecoin extends the IPFS vision by creating an open-source decentralized storage network that provides incentives to keep data stored and pinned on IPFS. Filecoin is powerful because it provides a decentralized storage solution without having to rely on larger centralized solutions. Additionally when it comes to building dapps on other decentralized networks, like Ethereum, it provides the groundwork for a much needed storage and authenticity solution to full decentralization.
-
-## Truffle Preserve to Buckets
-
-[Back in July](/blog/announcing-collaboration-with-filecoin), we announced a first look at using the `truffle preserve` command in an experimental release. Today, we are releasing `truffle preserve` as part of the main, stable version of Truffle! To use `truffle preserve`, simply specify the files you want to preserve on the command line, and choose between the `--filecoin`, `--ipfs`, or `--buckets` recipes. The `filecoin` recipe uses the `ipfs` recipe under the hood, but if you need to, you can choose to use the `ipfs` recipe without `filecoin`. You can learn more about `truffle preserve` in this [blog post](/blog/announcing-collaboration-with-filecoin).
-
-In addition, we’re also introducing a new recipe for `truffle preserve` which allows developers to save data to [Textile Buckets](https://docs.textile.io/buckets/): `truffle preserve --buckets`.
-
-![`truffle preserve --buckets` Example](/img/blog/truffle-and-ganache-now-come-in-filecoin-flavor/preserve-buckets.gif)
-
-Try out any of these three recipes today by [downloading the latest version of Truffle](/docs/truffle/getting-started/installation)!
-
-## Filecoin-flavored Ganache
-
-Ganache has helped many developers create Ethereum dapps by providing a "one-click" experience; Ganache automates the difficult parts of running a decentralized network to give the developer a personal environment to tinker with and develop applications. It speeds up development by not having to wait for decentralized test networks to confirm transactions, and it provides a controlled, configurable environment to reproduce different test scenarios.
-
-Prior to Ganache, if you wanted to run a development network for Filecoin you would need to run the [lotus-devnet](https://github.com/textileio/lotus-devnet), which requires compiling native resources or running a public Docker image. This is still a great resource to emulate the Filecoin network as close as possible as it includes a real [Lotus](https://docs.filecoin.io/get-started/lotus/) node, but Ganache now provides a lightweight alternative for getting started with Filecoin app development.
-
-With the Filecoin flavor, Ganache now provides you both an IPFS server (used to store files) as well as a Lotus simulator (used to maintain file storage, simulate a storage provider, and availability) to add the necessary Filecoin methods to get started with Filecoin development. Like the Ethereum flavor of Ganache, we've made the process as simple as possible for you to get started with Filecoin quickly.
-
-## What can I do with Filecoin-flavored Ganache?
-
-With Filecoin-flavored Ganache, you can do most of the development tasks for building a Filecoin application:
-- Store and retrieve files from a personal IPFS node that Ganache starts for you
-- Create a storage deal and see it progress through different states
-- Test how your application handles storage deal expiration
-- Transfer Filecoin's token FIL between accounts
-- Interact with the various Filecoin wallet methods
-
-You can find a full list of supported RPC methods on [GitHub](https://github.com/trufflesuite/ganache-core/tree/develop/src/chains/filecoin/filecoin#supported-rpc-methods).
-
-## How do I get started?
-
-If you’re looking to get started with Ganache, head over to the [documentation](/docs/filecoin/ganache/overview) to see Get Started guides whether you're using the NodeJS library, CLI, or graphical UI version.
-
-Need an example on how to build a Filecoin application? Check out the [Filecoin Truffle Box](https://github.com/truffle-box/filecoin-box) to see an example to mint NFTs and provide a decentralized art gallery application.
-
-We’re finalizing the Truffle documentation in the coming days, so stay tuned for those! When they’re live, you’ll be able to find them at our [main documentation page](/docs) and click on the Filecoin link.
-
-## Where can I get help?
-
-We're extremely excited to be working with the Filecoin community to add support for Filecoin into Truffle Suite's tooling. If you have questions about our Filecoin integration or our plan for the future, join [Truffle’s Discord community](https://trfl.co/truffle-community) & the [Filecoin community Slack](https://filecoin.io/slack) to get your questions answered. We're happy to help!
diff --git a/src/blog/truffle-and-infura-support-arbitrum/index.md b/src/blog/truffle-and-infura-support-arbitrum/index.md
deleted file mode 100644
index 607b9031c..000000000
--- a/src/blog/truffle-and-infura-support-arbitrum/index.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Truffle and Infura Now Support Arbitrum
-hide:
-  - navigation
----
-
-![Truffle, Arbitrum Collab Image](/img/blog/truffle-and-infura-support-arbitrum/blog-header.png)
-
-In our continuing efforts to help build the emerging multi-network Ethereum ecosystem, the Truffle team is thrilled to announce the launch of the Arbitrum Truffle Box. The usability and efficiency of Ethereum depends on scalability, and Arbitrum’s Layer 2 solution blends security and higher throughput to help make scalable Ethereum a reality.
-
-## Arbitrum
-
-Arbitrum is a Layer 2 scaling solution for Ethereum that uses optimistic rollups with interactive proving to make smart contracts scalable, fast, and private. It tracks closely to Ethereum, so that Ethereum developers can easily cross-compile their contracts to deploy on Arbitrum. Arbitrum offers its developers a variety of benefits: trustless security, compatibility with Ethereum, scalability, and cost efficiency.
-
-The Arbitrum rollup chain is built on top of and secured by Ethereum. From the developer perspective, interacting with Arbitrum is nearly identical to interacting with Ethereum. Arbitrum supports the same RPC interface as Ethereum, supports all EVM languages, and natively supports all Ethereum tooling without any special adapters. The main difference users and developers will notice is that transactions on Arbitrum cost a fraction of what they would if run natively on Ethereum.
-
-It is important to understand the mechanics of withdrawing funds from the Arbitrum chain. When withdrawing to Ethereum through an Arbitrum bridge, there is a delay to ensure that the transactions being rolled up are confirmed. Information about this finality delay and potential methods to avoid it can be found in Arbitrum's documentation [here](https://developer.offchainlabs.com/docs/withdrawals).
-
-For more details on Arbitrum’s protocol, see their [complete documentation](https://developer.offchainlabs.com/docs/inside_arbitrum).
-
-## Introducing The Arbitrum Truffle Box
-
-The [Truffle Arbitrum Box](https://github.com/truffle-box/arbitrum-box) provides developers with the boilerplate structure necessary to start coding for Arbitrum’s Ethereum Layer 2 solution.
-
-We provide the initial building blocks to get started working on Arbitrum without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Arbitrum Networks.
-
-Arbitrum’s Layer 2 solution is almost fully compatible with the EVM. The main difference between the EVM and the Arbitrum chain that developers will notice is that some opcodes are different and concepts such as time and gas are handled a little differently. Developers can use their regular Solidity compiler to compile contracts for Arbitrum. You can see the complete list of differences between the Arbitrum L2 chain and Ethereum [here](https://developer.offchainlabs.com/docs/differences_overview).
-
-## Integration With Infura
-
-Our colleagues at Infura are also adding full API support for the Arbitrum network. Infura users can now add the free Arbitrum add-on directly in their Infura dashboard. The Arbitrum network API largely uses the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Arbitrum network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/).
-
-Infura endpoints for the Arbitrum chain are included in the configuration of the Arbitrum Truffle Box, to aid developers in getting fully acquainted with their options when developing for Arbitrum.
-
-## Where To Get Help
-
-You can find all of the documentation for the Truffle Arbitrum Box [here](https://github.com/truffle-box/arbitrum-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
-We are thrilled to add Arbitrum to the Truffle development suite and can’t wait to see the universe of applications built on Layer 2. Stay tuned as we continue to add more networks, features, and tools that accelerate and simplify development on a secure and scalable Ethereum.
diff --git a/src/blog/truffle-and-infura-support-optimism/index.md b/src/blog/truffle-and-infura-support-optimism/index.md
deleted file mode 100644
index 783de64ce..000000000
--- a/src/blog/truffle-and-infura-support-optimism/index.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Truffle and Infura Now Support Optimism
-hide:
-  - navigation
----
-
-![Truffle, Optimism Collab Image](/img/blog/truffle-and-infura-support-optimism/blog-header.png)
-
-Developer demand for scalable Ethereum application development tooling continues to grow. The multi-network Ethereum ecosystem is here, and Layer 2 solutions such as Optimistic Ethereum are leading the way. The Truffle team is delighted to support Optimistic Ethereum in helping developers build for this ecosystem. Today we are announcing the launch of the new Truffle Optimism Box.
-
-## Optimistic Ethereum
-
-Optimistic Ethereum is a Layer 2 scaling protocol for Ethereum applications. It is an application inside of Ethereum that executes transactions more efficiently than Ethereum itself, based on the concept of an [Optimistic Rollup](https://medium.com/plasma-group/ethereum-smart-contracts-in-l2-optimistic-rollup-2c1cef2ec537). The Optimistic Ethereum security model is backed by a system of “fraud proofs” that allow users to identify bad transaction results to support the accuracy of the data that is eventually rolled up and published to the main Ethereum chain. Transactions on Optimistic Ethereum are handled similarly to those on the Ethereum mainnet, and bridging between Optimistic Ethereum and mainnet Ethereum allows users to conduct gas-intensive operations on Optimistic Ethereum for a fraction of the cost.
-
-Optimistic Ethereum tracks closely to the structure and operation of the Ethereum mainnet, preserving security guarantees while increasing throughput and decreasing transaction costs. Important to note, this protocol requires a delay for bridging funds from Optimism back to Ethereum, and you can find more information about that [here](https://community.optimism.io/docs/developers/bridging.html#understanding-the-fraud-proof-window).
-
-Existing Solidity smart contracts can run on Optimistic Ethereum with minimal differences. Off-chain code such as user interfaces and wallets will need to update their RPC endpoints to interact with Optimistic Ethereum, and will largely just work once the update is made.
-
-For detailed documentation on the Optimistic Ethereum protocol, see [here](https://community.optimism.io/docs/protocol/protocol.html#introduction) and [here](https://community.optimism.io/docs/developers/integration.html).
-
-## Introducing the Truffle Optimism Box
-
-The [Truffle Optimism Box](https://github.com/truffle-box/optimism-box) provides developers with the boilerplate structure necessary to start coding for Optimism’s Ethereum Layer 2 solution.
-
-We provide the initial building blocks to get to work on Optimistic Ethereum without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Optimistic Ethereum networks.
-
-Optimism’s Layer 2 solution is almost fully compatible with the EVM, though it uses an “optimistic” EVM called the OVM. The main difference between the EVM and the OVM that developers will notice is that some opcodes are not available for contracts that are deployed to the OVM. The Truffle Optimism Box is complete with the Optimistic `solc` compiler already referenced in the `truffle-config.ovm.js` file. You can see a complete list of differences between Optimism’s fork of the `solc` compiler and the original [here](https://github.com/ethereum-optimism/solidity/compare/27d51765c0623c9f6aef7c00214e9fe705c331b1...develop-0.6).
-
-## Integration With Infura
-
-Our colleagues at Infura are also adding full API support for the Optimistic Ethereum network. Infura users can now add the free Optimism add-on directly in their Infura dashboard. The Optimism network API largely uses the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Optimistic Ethereum network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/).
-
-Infura endpoints for the Optimistic Ethereum chain are included in the configuration of the Optimism Truffle Box, to aid developers in getting fully acquainted with their options when developing for the Optimistic Ethereum chain.
-
-## Where to Get Help
-
-You can find all of the documentation for the Truffle Optimism Box [here](https://github.com/truffle-box/optimism-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
-
-We are thrilled to add Optimistic Ethereum to the Truffle development suite and can’t wait to see the universe of applications built on Layer 2. Stay tuned as we continue to add more networks, features, and tools that accelerate and simplify development on a secure and scalable Ethereum.
diff --git a/src/blog/truffle-and-infura-support-polygon/index.md b/src/blog/truffle-and-infura-support-polygon/index.md
deleted file mode 100644
index c77371d2a..000000000
--- a/src/blog/truffle-and-infura-support-polygon/index.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Truffle and Infura Now Support Polygon
-hide:
-  - navigation
----
-
-![Truffle, Infura, and Polygon Collab Image](/img/blog/truffle-and-infura-support-polygon/blog-header.png)
-
-The developer demand for scaling solutions that work directly with Ethereum is here and growing, so today we are very excited to launch the new Polygon Truffle Box. Ethereum-based dapp development is rapidly entering a new phase wherein a multi-network future is certain and Layer 2 solutions like Polygon's are leading the charge into this uncharted territory. Layer 2 scaling is essential to the health of the Ethereum ecosystem, and the Truffle team is delighted to support the Polygon PoS chain in helping developers build toward this future.
-
-## Polygon PoS Chain
-
-Polygon PoS is a hybrid Plasma Proof-of-Stake sidechain to the Ethereum mainnet which consists of a Tendermint consensus validator layer and a Plasma sidechain for block production. This configuration allows for higher transaction throughput, lower gas fees, and through Polygon's established bridges, easy connection back to the Ethereum mainnet.
-
-## Introducing the Polygon Truffle Box
-
-The core component of this new tooling is the [Truffle Polygon Box](https://github.com/truffle-box/polygon-box). This new Truffle box provides you with the boilerplate structure necessary to start coding for Polygon's Ethereum L2 solution, the Polygon PoS chain (previously the Matic PoS chain). For detailed information on how the Polygon PoS chain works, please see their documentation [here](https://docs.matic.network/docs/develop/getting-started).
-
-We provide the initial building blocks needed to get to work on Polygon PoS without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Polygon PoS networks.
-
-Polygon's L2 solution is fully compatible with the EVM. This means you will not need a new compiler to deploy Solidity contracts, and should be able to add your own Solidity contracts to this project. The main difference developers will encounter is in accessing and interacting with the Polygon PoS network. Additionally, Polygon offers multiple ways for dapp developers to implement communication between Ethereum ("Layer 1") and the Polygon PoS chain. Further information about how to enable Ethereum-Polygon communication can be found in the Polygon documentation [here](https://docs.matic.network/docs/develop/ethereum-matic/getting-started).
-
-_A quick note about naming: The Polygon ecosystem was previously called Matic Network. The chain to which we'll be deploying in the Polygon Truffle Box is now called the Polygon PoS chain. We have named this box the Polygon Box because we expect to include the ability to deploy to future Polygon chains in addition to what is presented in the initial Polygon Box, and developers using this Box may find themselves incorporating additional aspects of the Polygon ecosystem in their work._
-
-## Integration With Infura
-
-Our colleagues at Infura are also adding full API support for the Polygon network. Infura users can now add the free Polygon Network add-on directly in their Infura dashboard. The Polygon network API largely utilizes the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Polygon network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/Polygon-PoS?&utm_source=infurablog&utm_medium=referral&utm_campaign=announcement&utm_content=polygon-launch).
-
-Infura endpoints for the Polygon PoS chain are included in the configuration of the Polygon Truffle Box, to aid developers in getting fully acquainted with their options when developing for the Polygon PoS chain.
-
-## Where to Get Help
-
-You can find all of the documentation for the Truffle Polygon box [here](https://github.com/truffle-box/polygon-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
-
-We are very excited to add Polygon PoS to our development suite and we can't wait to see all of the amazing applications built with these tools. Stay tuned as we continue to add more networks, features, and products that accelerate and simplify development on this exciting new technology.
diff --git a/src/blog/truffle-boxes-making-life-sweeter/index.md b/src/blog/truffle-boxes-making-life-sweeter/index.md
deleted file mode 100644
index 4a89c1293..000000000
--- a/src/blog/truffle-boxes-making-life-sweeter/index.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Truffle Boxes - Making Life Sweeter
-hide:
-  - navigation
----
-
-When users begin developing on Ethereum, the first question they ask is, "Where do I start?". In the past, there hasn't been an easy answer: the answer generally consisted of many flavors of "it depends", and usually led to an investigation of what the user was trying to build, a general overview of their development skills, their knowledge of Ethereum, and the libraries and tools they're already most comfortable with. When determining how the Truffle team can help in this process, it quickly became apparent that what our users needed were examples. _Many of them._ So, being the upstanding community members we are, we set out to create those example, and today, we're happy to show you what we've accomplished.
-
-## Introducing Truffle Boxes!
-
-A Truffle box is an example Ethereum application and/or boilerplate that puts complimentary tools and libraries into a single, sweet, easily-downloadable package. Every Truffle box comes with libraries and tools already preinstalled, code that uses those libraries and tools, external scripts (if necessary), as well as helpful README's and documentation. All Truffle boxes are directly integrated into the Truffle command line, and you need only type `truffle unbox <box name>` to download and prepare your box of choice.
-
-**[Click here for a list of all available boxes.](/boxes)** Ensure you've installed the latest version of Truffle before opening your first box.
-
------------------
-
-Today's release comes with three officially-supported boxes, as well as one community-supported box. Our officially-supported boxes are:
-
-* [react](/boxes/react): A box that pairs Truffle with React in an easy to understand structure, meant for a web-based Ethereum application.
-* [react-auth](/boxes/react-auth): Our `react` box with extra goodies for authentication powered by smart contracts.
-* [react-uport](/boxes/react-uport): Like `react-auth`, but authentication is powered by Uport.
-
-Perhaps the most exciting part of this release -- our _pièce de résistance_ -- is the [Status Truffle box](/boxes/status), our first community-supported box. This box was created by the Status team, and instantly links Truffle and Status together with an example application and all the tools and libraries you need to build your own Status dapp.
-
-
-## Get Involved: Make Your Own Box
-
-We've released four boxes out of the gate to get you started, but this isn't just our candy store. **We want you to contribute** to the boxes on our site. If you have boilerplate code, an example dapp, a helpful integration or an exciting dapp stack (say, an Ethereum-enabled iOS app built with Truffle), send us an email at [boxes@trufflesuite.com](mailto:boxes@trufflesuite.com?subject=Truffle%20box%20review) and we'll look it over. If it's awesome, we'll list it on our site with your name front and center. If it's better than awesome, we'll help contribute and maintain it and make it an officially-supported Truffle box. With Truffle, you can share your code with others and help build the community, one box at a time.
-
-## One More thing...
-
-There's always one more thing. Fair warning, this one's techy. Right now, all the boxes you're seeing are static pages showing off what we and the Status team have built. Soon, however, we'll be taking on the ultimate challenge and will be creating a Truffle box registry, built on top of Ethereum, to help market and promote our community-supported boxes. Of course we'll be using Truffle, which adds a whole new layer of sweetness. Stay tuned for more details about the registry and how you can use the Ethereum blockchain to become a Truffle contributor.
-
-As always, we thank everyone for your support, and would love to hear from you. Don't hesitate to reach out on our [community Gitter channel](https://gitter.im/ConsenSys/truffle) where hundreds of your fellow Trufflers congregate to answer your questions.
-
-Cheers!
-
--- Tim & the Truffle Team
diff --git a/src/blog/truffle-teams-gets-a-new-look/index.md b/src/blog/truffle-teams-gets-a-new-look/index.md
deleted file mode 100644
index 04b209ab6..000000000
--- a/src/blog/truffle-teams-gets-a-new-look/index.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Truffle Teams Gets a New Look!
-hide:
-  - navigation
----
-
-![Truffle Teams Redesign Banner](/img/blog/truffle-teams-gets-a-new-look/banner.png)
-
-Thanks to [Josh Quintal](https://github.com/DiscRiskandBisque) and [Heyse Li](https://github.com/honestbonsai), the redesign of Truffle Teams is complete! Josh presented the [Theobromine design system at TruffleCon 2019](https://www.youtube.com/watch?v=aoU710h38xE&t=1m47s), and this release is the first step towards this vision! In addition to the stylistic upgrade, we've redesigned the app navigation to help you focus on a single repository at a time.
-
-Read more below about the most recent changes, or [go check them out for yourself](https://my.truffleteams.com)!
-
-## Redesign
-
-The Theobromine Design System uplifts the entire Truffle Teams application. This lighter theme makes the application feel more welcoming and presents itself more as a professional productivity tool.
-
-![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-builds.png)
-
-We also added support to collapse the left navbar to give you some more screen real estate. This is super helpful for those with small or vertical screens; it’s also instrumental for multitaskers that use Truffle Teams in a split-screen setup.
-
-![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-build-detail.png)
-
-## Navigation Updates
-
-The previous iteration of Truffle Teams utilized a "feature first" navigation where you would select the feature you'd like to see (Builds, Deployments, Monitoring [formally known as Data]) and then select the repository you'd want to drill into. We found this to be a jarring and tedious experience, so we changed things to be "repository first".
-
-When you login, you'll now see a home page with a list of your repositories. You can quickly search for a repository or keep your favorites at the top of the list by pinning them.
-
-![Teams Redesign - Home Page](/img/blog/truffle-teams-gets-a-new-look/teams-home.png)
-
-After clicking on a repository you'll be presented with the details of that repository. On the Builds page you'll now see a history of your builds rather than seeing the list of your repositories. The Deployments and Monitoring pages will look familiar as they haven't changed much other than not having to select the repository again.
-
-![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-builds.png)
-
-Want to focus on a different repository? You can quickly switch between them using the breadcrumb dropdown at the top of each page.
-
-![Teams Redesign - Breadcrumb Dropdown](/img/blog/truffle-teams-gets-a-new-look/teams-repo-breadcrumb.png)
-
-You can also click the Truffle Teams logo in the top left to go back to the home page with the search bar and pinned repositories.
-
-![Teams Redesign - Logo in Top Left](/img/blog/truffle-teams-gets-a-new-look/teams-logo-to-home.png)
-
-## Got Feedback or Questions?
-
-If you aren't aware of our official support channel, head over to [the Truffle Teams channel in Spectrum.chat](https://spectrum.chat/trufflesuite/truffle-teams). Posting a thread there will ping us in our internal Slack workspace and we'll answer you ASAP. You can also submit Truffle Teams feature requests and issues [on GitHub](https://github.com/trufflesuite/truffle-teams/issues).
-
-<div class="post-trufflecon-box mt-5 text-center">
-  Get started with Truffle Teams, and see the redesign for yourself!
-
-  <div class="mt-3">
-    <a class="btn btn-truffle" href="/docs/teams/getting-started/creating-an-account">Try Truffle Teams</a>
-  </div>
-</div>
diff --git a/src/blog/truffle-teams-now-supports-private-repositories/index.md b/src/blog/truffle-teams-now-supports-private-repositories/index.md
deleted file mode 100644
index 04589a051..000000000
--- a/src/blog/truffle-teams-now-supports-private-repositories/index.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Truffle Teams Now Supports Private Repositories
-hide:
-  - navigation
----
-
-Thanks to the awesome work of [@nicholasjpaterno](https://github.com/nicholasjpaterno), you can now integrate private repositories with Truffle Teams! This will eventually be a premium feature, but we're releasing it for free while the product is still in beta.
-
-## Using Private Repos
-
-<figure>
-  <img src="/img/blog/truffle-teams-now-supports-private-repositories/tt-private-repo-badge.png" alt="Example of Truffle DB" style="width:100%; box-shadow: 0px 3px 5px 0px rgba(0,0,0,0.25);">
-  <figcaption>Here we see the lock icon denoting a private repository and an indication of this being a future premium feature.</figcaption>
-</figure>
-
-There are no extra steps to use your private repositories with Truffle Teams! Simply [add your repo](https://github.com/apps/truffle-teams), and automatic builds should start working! Private repos will have a lock icon next to their name indicating their private status. Otherwise, they have the same functionality as public repos.
-
-You'll see that we're very loud about which features will be premium. We'll continue this practice for future premium features so that we stay transparent about what's to come.
-
-## Next Up: Deployments!
-
-Here's a teaser of our next upcoming feature: Graduated Deployments.
-
-<figure>
-  <img src="/img/blog/truffle-teams-now-supports-private-repositories/tt-deployments.png" alt="Example of Truffle DB" style="width:100%; box-shadow: 0px 3px 5px 0px rgba(0,0,0,0.25);">
-  <figcaption>The main deployments screen showing successful testnet and mainnet deployments.</figcaption>
-</figure>
-
-You'll be able to deploy any commit with a successful build to Ropsten, Rinkeby, and Mainnet Ethereum networks (with more to come soon!). You'll get some useful contextual information for your deployments: the status of the deployment, when it took place, who on your team deployed it, the contracts deployed, the ability to download your Truffle Artifacts, and more.
-
-Deploy to the Staging environment (Ropsten and Rinkeby currently) to make sure everything works out. Once you're ready, you can easily graduate a deployment in Staging to Production (Mainnet currently). We're using `truffle migrate` under the hood, so your existing migration scripts will work just fine.
-
-We've distilled the deployment process into an informative and helpful wizard to guide you through the deployment process. With this wizard and leveraging [MetaMask](https://metamask.io) for signing transactions, we are finally giving you an interface that makes it easier to deploy for seasoned and new devs alike!
-
-We'll release a full article with all the details about using Truffle Teams' deployment features once it's ready for release.
-
-Thank you and happy truffling!
\ No newline at end of file
diff --git a/src/blog/truffle-v5-has-arrived/index.md b/src/blog/truffle-v5-has-arrived/index.md
deleted file mode 100644
index d99e291d3..000000000
--- a/src/blog/truffle-v5-has-arrived/index.md
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: Truffle v5 has arrived!
-hide:
-  - navigation
----
-
-We have just released the most awaited version of Truffle just in time for the
-holidays! There are SO many exciting things that we would like to mention that
-will make your Truffle experience a rich one. Highlighted below are the new
-exciting things Truffle has to offer.
-
-👯    [Download Truffle v5](/truffle) or check out the
-full [Release Notes](https://github.com/trufflesuite/truffle/releases/tag/v5.0.0).    👯
-
-- **Bring your own compiler!** You can now choose any solc-js version
-  available at solc-bin. Just tell Truffle which version you want to use and it
-  will automatically fetch it for you! This feature also includes the ability to
-  use Docker and native binaries in an advanced way.
-
-- **Web3 1.0** - The truffle-contract package is now using Web3.js 1.0! This
-  will greatly improve error handling!
-
-- **New migrations command** - In v5, the `migrate` command has been completely
-  rewritten. We have included better error messages: e.g., when a deployment fails
-  Truffle will notify you and give you an idea of possible fixes. Truffle will
-  now also give you more information about what is going on when you deploy a
-  contract. This includes cost summaries and real time status updates about the
-  amount of time a transaction has been pending.
-
-  Dry run simulations also now run automatically if you are deploying to a known
-  public network and using the `--interactive` flag on the command line will give
-  you a prompt between dry runs and real deployments.
-
-  Another improvement is the ability to configure the amount of block confirmations
-  in between deployments. This allows the user to specify the number of blocks to
-  wait before transactions time out.
-
-- **Usage analytics** - Usage analytics have been added and users can opt-in by
-  running `truffle config --enable-analytics`. We think this feature will be a
-  vital tool that will help us to make informed decisions about the future of Truffle
-  and to determine what is most valuable to our users. When enabled, Truffle will
-  collect information about your version number, the commands you run, and
-  whether commands succeed or fail. And of course, it will do so in an anonymous
-  fashion.
-
-- **`truffle run <command>`** -  Truffle now gives users the ability to create
-  custom command plugins. This feature is still in its infancy so let us know
-  what you think!
-
-- **Vyper support** - Another added feature is that Truffle will now compile
-  `*.vy` contracts. We have published a Truffle Box to help you get started
-  with Vyper. You can access it by running:
-
-  ```shell
-  $ truffle unbox vyper-example
-  ```
-
-  (Make sure you have [Vyper](https://vyper.readthedocs.io/en/latest/installing-vyper.html) installed.)
-
-- **Solidity v0.5.0** - Truffle also now ships with Solidity v0.5.0 by default.
-  Solidity v0.4.xx is still supported and can be used by specifying the version
-  you wish to use in your Truffle config.
-
--  **Structured function parameters** - Truffle has been upgraded to use
-   Web3.js v1.0. This has allowed us to include support for passing/returning
-   ‘struct’s in Solidity functions. To use this ability, you need to specify the
-   following at the top of your contracts:
-
-  ```solidity
-  pragma experimental ABIEncoderV2
-  ```
-
-  This feature allows you to use complex function arguments and have the values
-  returned so that they can interact with other contracts via truffle-contract’s
-  JS interface.
-
-- **Help system** - Now access Truffle’s built in help system by running:
-  ```shell
-  $ truffle help <command>
-  ```
-
-  This allows you to see all the available options for the command as well as a
-  description of what it does.
-
-- **Unique `truffle develop` mnemonics** - Truffle will now generate random mnemonics
-  that will persist only for you. Use caution with crypto security when working
-  with mnemonics and private keys!
-
-- **Debugger improvements** - v5 includes debugger breakpoints! Add breakpoints
-  using the ’b’ command and remove them using the ‘B’ command. Additionally we
-  have added mapping support for the debugger!
-
-- **`truffle init` / `truffle unbox`** - These commands have been improved and
-  you are now asked if you want to overwrite files in the case of name conflicts
-  in the target directory. A force option (--force) has also been added in the
-  case where you wish to overwrite the files automatically and avoid the
-  prompt.
-
-- **`async`/`await`** - Support for async/await syntax in the Truffle console
-  is also now available!
-
-Looking towards the future we intend to add third-party plugins and
-hope through our fancy, improved analaytics to provide features the community
-needs most!
-
-![V5 Breaking Changes](/img/blog/truffle-v5-blog-media/breaking-changes-photo-v5.png)
-
-**Thank you to all who have helped make this release of Truffle possible! We
-hope you enjoy this new Truffle release and ask that you let us know if you have
-any suggestions or problems on our community Gitter channel or on our GitHub
-page!**
-
-[Get started with Truffle v5 today!](/truffle)
diff --git a/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md b/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
deleted file mode 100644
index af065564b..000000000
--- a/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Try New Features First with Truffle Teams Early Access
-hide:
-  - navigation
----
-
-![Truffle Teams Early Access Banner](/img/blog/try-new-features-first-with-truffle-teams-early-access/blog-header.png)
-
-Truffle Teams is constantly evolving. Between adding new features, polishing, and refining the app there's so much we'd love to share with the world in a faster way. Wouldn't it be nice to take those new enhancements and features for a test drive? Now you can with early access!
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 figure-shadow" src="/img/blog/try-new-features-first-with-truffle-teams-early-access/early-access-1.png" alt="Enabling Early Access from the settings screen">
-  <figcaption class="text-center font-italic">Enable early access with just one click!</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-## How Early Access Works
-
-To join early access, select the Early Access option in the Advanced tab via the account Settings Page. This account will now have access to new features and enhancements we're cooking up. First up is a hotly anticipated feature--the debugger, [which you can learn more about here](/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger).
-
-We'll provide a helpful reminder as to where you can provide feedback and request support. Your feedback is one of the most important parts of this process, and we're excited to hear from you in the earlier phases of development!
-
-Want to switch back to the stable track? You can disable Early Access at any time, but anything that requires data storage will be erased.
-
-We hope you enjoy getting a taste of what's to come!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT TRUFFLE TEAMS EARLY ACCESS</a>
-</div>
-
-## Continue the Conversation
-
-We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven't met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md b/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
deleted file mode 100644
index 47cf621d7..000000000
--- a/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Unwrap the Corda Flavored Ganache Beta
-hide:
-  - navigation
----
-
-![Truffle Teams Deployments Banner](/img/blog/unwrap-the-corda-flavored-ganache-beta/corda-ganache-beta-blog-banner.png)
-
-Earlier this year at TruffleCon [we announced our partnership with Corda to develop a Corda Flavored Ganache](https://youtu.be/MtOaXVt1yOE?t=697). Then, at CordaCon in London [we shared more details around the integration](https://www.r3.com/videos/truffle-and-corda/).
-
-**Today, we are proud to share with you [the beta release is live](https://github.com/trufflesuite/ganache/releases/tag/v2.3.0-beta.1)!**
-
-As a quick refresher: Ganache is Truffle's "one click blockchain" that allows you to run a test network for local development. You don't need an internet connection and because it's all on the same machine, Ganache allows users to see the status of the network in greater detail than on a live network.
-
-<figure>
-  <img src="/img/blog/unwrap-the-corda-flavored-ganache-beta/corda-ganache-beta-screenshot.png" alt="Corda Flavored Ganache startup screen" style="width:100%">
-  <figcaption class="text-center">The workspace selection screen--now with Corda!</figcaption>
-</figure>
-
-We're thrilled to release Ganache for the Corda Blockchain, as this lowers the barrier of entry for Corda developers by allowing them to easily set up a local network on their machines, giving introspection into the state of that network across various nodes and visibility to transactions normally hidden by a live Corda network's privacy protections.
-
-With the Beta version, Corda Flavored Ganache brings you:
-
-* **One-click** Corda network configuration and initialization, so you can focus on what matters most: your application.
-* **Easy access** to all your application's data, including network map, notaries, nodes, transactions, and states.
-* **Multiple workspaces** for all of your Corda projects; workspaces contain configurations of a Corda network map, notaries, nodes, transactions, accounts, and ledgers.
-
-As always, Truffle's tools come standard on Windows, macOS, and Linux.
-
-We are excited to share this with the Corda community and **we also need to your help!** Since this is a Beta release, we know it's not perfect. If you find a bug, do us a favor and file an issue [here](https://github.com/trufflesuite/ganache/issues/new).
-
-<a href="https://share.hsforms.com/1jbMAfLzGSj6HWx_-na9Bew34pbp">✉️ Sign up for the Corda Flavored Ganache mailing list here</a> to get the latest updates on all things Ganache + Corda.
-
-If you don't hear from us immediately, know that our team is taking some much needed time off starting today. We'll be back January 6th, 2020 ready to dive into your feedback! 
-
-If you see them around the net, make sure to give a _**HUGE thank you**_ to [David Murdoch and Nick Paterno](/staff). Their hard work made this all possible and we're a very fortunate organization to have them aboard! 💖
-
-<div class="post-trufflecon-box mt-5 text-center">
-  Try the Corda Flavored Ganache beta and let us know what you think!
-
-  <div class="mt-3">
-    <a class="btn btn-truffle" href="https://github.com/trufflesuite/ganache/releases/tag/v2.3.0-beta.1">Download Corda Flavored Ganache</a>
-  </div>
-</div>
\ No newline at end of file
diff --git a/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md b/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
deleted file mode 100644
index 6a78ecf8c..000000000
--- a/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Upcoming improvements to encoding and decoding
-hide:
-  - navigation
----
-
-When you’re writing, running, or debugging your smart contract, you don’t want to have to deal with raw binary data. Truffle––and Ganache and Drizzle––already contain a number of encoding and decoding features to help you interact with your contract and understand what you’re seeing. But luckily, encoding and decoding are about to become even more robust, informative, and usable.
-
-Not all of these features will be immediately available in Truffle 5.1, but some will, so let’s start with one that will be ready! Allow me to illustrate:
-
-![Syntax Highlighting](/img/blog/upcoming-improvements-to-encoding-and-decoding/syntax-highlighting.png)
-
-Yes, debugging displays are about to become quite a bit more colorful! And though it’s not related to decoding, yes that is `syntax highlighting` in the debugger! Of course, it’s not just a matter of color. Previously, many data types displayed inappropriately as strings, and enums displayed as objects. Now, each data type will be displayed in a form (and color) that makes sense, making them recognizable at a glance. No longer will a function be confused for a string!
-
-![Contracts and External Functions](/img/blog/upcoming-improvements-to-encoding-and-decoding/contracts-and-external-functions.png)
-
-Of course, this wouldn’t be possible without our new, more machine-readable, decoder output format. This one’s a little technical, and it’s not something you’re likely to find yourself dealing with directly -- you probably aren’t using Truffle Decoder directly. But Ganache and Drizzle both make use of it, and as they update to incorporate the new format, you’ll be able to get a better view of the state of your contracts with them.
-
-But that’s not all; we’re also intending to eventually integrate these encoding and decoding features into Truffle Contract. This will allow you to send transactions and decode events that you currently can’t!
-
-For instance, Vyper contracts support decimal fractions as a datatype, but our current encoder and decoder, and the ethers library, do not support these. If you want to send a transaction (or if your contract emits an event) that takes a decimal fraction as input, you are going to run into trouble. With our upcoming encoding and decoding improvements, this should no longer be a problem. (Or, for something of more concern to our Solidity users, the same applies to external function pointers.)
-
-Finally, I’d like to discuss decoding of events. Currently, when you check what events your contract may have emitted recently, you may have trouble decoding events emitted by libraries. Our new decoder, though, will be able to handle these just fine. It will even handle anonymous events! That may seem impossible, but hey, that hasn’t deterred us.
-
-We’re hoping Truffle’s new encoder and decoder will make staring at raw binary data a thing of the past! Unless you like to, of course. But for those of you who’d prefer to take a higher-level view and deal directly with what that binary data actually means… well, that’s what Truffle’s for, isn’t it?
-
diff --git a/src/blog/using-the-ens-integration/index.md b/src/blog/using-the-ens-integration/index.md
deleted file mode 100644
index 7622ce13d..000000000
--- a/src/blog/using-the-ens-integration/index.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: Using Truffle's ENS Integration
-hide:
-  - navigation
----
-
-**By Tyler Feickert, Blockchain Tools Engineer at Truffle**
-
-Among the new features released with Truffle 5.1 is support for Ethereum Name Service
-(ENS) name resolution and setting the resolver address for owned names!
-
-ENS is a system that allows for the resolution of Ethereum addresses using
-human-readable names. Like DNS, ENS aims to simplify working with addresses and
-allowing us to work with names like "truffle.eth" in place of things that cumbersomely
-resemble something like `"0x1234567890123456789012345678901234567890"`. Are you
-sure you copied that address correctly? Ready to send your Ether there?
-
-In ENS, a contract called a registry is deployed to a network. The ENS team has
-deployed a registry contract to Mainnet and several test networks. These are the
-registries that Truffle connects to by default if no registry address is set
-in the Truffle config.
-
-An ENS registry contract contains a list of names and who owns them. Each name
-also points to a resolver contract if one is set. Addresses own ENS names and
-have the ability to set the resolver that a given name points to. The resolver
-is the contract responsible for returning an address for resolution. The
-idea is that the owner will have the ability to set the resolver contract
-to return the desired address.
-
-For more detailed information on ENS, check out the [ENS website](https://ens.domains/).
-
-So we at Truffle think this project is pretty awesome and, as mentioned above,
-built an integration with it. Previously in your migrations, for example, you
-needed to manually deal with addresses. So maybe you wanted to send some
-tokens from your contract to another address. In your Truffle migration you
-might have the following code:
-
-```javascript
-await myTokenContract.sendTokens(
-  999,
-  "0x1234567890123456789012345678901234567890",
-  { from: "0x0987654321098765432109876543210987654321" }
-);
-```
-
-It is difficult and tiring to deal with raw addresses like this.
-
-Now in Truffle, if you turn on the ENS name resolution and you have a
-resolver set to your address of choice, you can do something like the
-following in place of the above:
-
-```javascript
-await myTokenContract.sendTokens(
-  999,
-  "truffle.eth",
-  { from: "my.account" }
-);
-```
-
-Well, that seems much easier to read. Under the hood during the migrations,
-Truffle will connect to the on-chain registry and automatically resolve the
-addresses for both "truffle.eth" and "my.account". You now can use
-valid ENS names in place of addresses in your migrations! In other
-words, any place that an address is expected for an argument to a
-function call, you can instead provide the ENS name.
-
-One other big piece of functionality for this ENS integration is the ability to set
-the resolution address for owned ENS addresses. You can do this using
-`deployer.ens.setAddress` in your migrations.
-
-Suppose I control an address that owns the name "arnold.hagenchop.eth" and I
-want to set the address to "0x1234123412123412341212341234121234123412". In
-this case I would write something like the following in my migration:
-
-```javascript
-const myAddress = "0x1234123412123412341212341234121234123412";
-await deployer.ens.setAddress(
-  "arnold.hagenchop.eth",
-  myAddress,
-  { from: "0x8888888888888888888888888888888888888888" }
-)
-```
-
-Now let's take a step back and look at what we did. So you can see that the
-`setAddress` method has three arguments. The first one is the name that we'd
-like to set the resolver for. As stated above we want to set the resolver
-address for "arnold.hagenchop.eth". The second argument is the address to set
-for the given name's ENS resolution. The last one is an object that resembles
-a transaction parameter object. The important thing about this object is
-that it must have a `from` property with the address that controls the name
-given as the first argument. This is important or the transaction will fail!
-
-You can find some more information about registering ENS names from the
-[ENS website](https://ens.domains/).
-
-One other useful convenience with this method is that you can also provide
-a Truffle contract object that has a deployed address as the second argument
-if you'd like. So the above code might look like the following instead:
-
-```javascript
-const MyContract = artifacts.require("MyContract");
-const myContract = await MyContract.deployed();
-await deployer.ens.setAddress(
-  "arnold.hagenchop.eth",
-  myContract,
-  { from: "0x8888888888888888888888888888888888888888" }
-)
-```
-
-In that case, "arnold.hagenchop.eth" will be set to the address at which
-`myContract` is deployed!
-
-This new integration should just be the start of a much more robust system that
-allows Truffle projects to interact with ENS! In the future, we also hope
-to add other features such as reverse resolution (resolving a name from an
-address) and automatic name registration where possible. We think this will
-be a big step forward in making the Ethereum ecosystem more accessible as well
-as convenient to work with!
-
-For more thorough information about this integration, see the
-[Truffle docs](/docs/truffle/advanced/ethereum-name-service).
-We have also created an
-[example Truffle box](https://github.com/truffle-box/v5.1-example-box#v51-example-box)
-that has some examples of using this new ENS integration alongside other new
-Truffle v5.1 features. We hope you find this feature as useful as we think
-it is! Happy Truffling!
diff --git a/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md b/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
deleted file mode 100644
index 88d7a6c2e..000000000
--- a/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
+++ /dev/null
@@ -1,102 +0,0 @@
----
-title: Using Truffle to interact with Chainlink Smart Contracts
-hide:
-  - navigation
----
-
-![Truffle + Chainlink](/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/chainlink-az.png)
-
-Chainlink is one of the leading blockchain projects building the very first decentralized oracle network that provides external data to smart contracts. Truffle helps smart contract developers by providing a powerful framework to create, test, and deploy smart contracts. In Chainlink’s blog [post](https://blog.chain.link/how-to-use-chainlink-with-truffle-2/), their [Chainlink Truffle Box](https://github.com/smartcontractkit/chainlink/tree/master/evm/box) has gotten some significant upgrades! If you were fortunate enough to attend Trufflecon 2019, then you have already seen these improvements in action, thanks to Chainlink’s presentation by Thomas Hodges. To start developing your very own Chainlink smart contracts, you can grab Chainlink’s Truffle Box by following the guide [here](https://blog.chain.link/how-to-use-chainlink-with-truffle-2/).
-
-This article will showcase these brand new additions, starting with [Truffle Scripts](/docs/truffle/getting-started/writing-external-scripts). Scripts create a much easier approach to interact with our contracts, allowing us to fund a contract with LINK, request data from it, and read the contract’s data with only three commands. To demonstrate this functionality, we will first need to set up our environment variables: MNEMONIC and RPC_URL.
-
-Working with blockchain technology requires a wallet, with one of the most popular choices being [MetaMask](https://metamask.io/). Within minutes, you can have your very own Ethereum wallet that allows you to easily interact with various dApps. During account generation, you will be shown your **_secret_** 12-word seed phrase, known as your mnemonic. (Do not share this with anyone; if someone knows your _mnemonic_ they WILL have access to your addresses and private keys). Be sure to store this mnemonic somewhere safe, as you will need it later to work with our example.
-
-Furthermore, you will also need to fund your MetaMask wallet with [test LINK](https://ropsten.chain.link/) and [test ETH](https://faucet.ropsten.be/), in order to power transactions on the Ropsten Ethereum Testnet.
-
-_Note: When funding your account from a test faucet, make sure you switch from the default Main Ethereum Network to the Ropsten Test Network, to properly see your funds. You can follow any transactions made on the Ropsten Testnet via Etherscan._
-
-Our second environment variable will require an RPC URL. Some popular RPC connectivity services include [Infura](/guides/using-infura-custom-provider), [LinkPool](https://www.linkpool.io/), and [Fiews](https://fiews.io/free-rpc). After establishing a valid RPC connection and the funded address, you can start deploying smart contracts to public networks.
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/01.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>_Shown above are the environment variables needed to link your MetaMask wallet to Truffle, found in truffle-config.js._</figcaption>
-</figure>
-
-Once you have all the data you need, you can set your environment variables via the terminal commands:
-
-```shell
-export RPC_URL=your_url_here
-export MNEMONIC=’your 12 words here’
-```
-
-## Migration
-
-We are now ready to deploy our smart contract on a public network. To begin, run the command:
-
-```shell
-npm run migrate:live
-```
-
-This will compile all of your smart contracts, and then start deploying (migrating) them.
-
-_Note: you may encounter some compilation warnings with the Chainlink contracts. This is simply because the LINK token was originally deployed with an older version of Solidity. Given that this contract is only being deployed when you run tests, these can be ignored._
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/02.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>_Console output of one of our contracts deploying. This particular transaction can be found [here](https://ropsten.etherscan.io/tx/0x4c8125f0e074ce3f65b08f67f9685a0d00c2985c6ebd372507016d78c344d25b)._</figcaption>
-</figure>
- 
-Deploying our `Migrations` and `MyContract` cost us Ethereum, hence why we needed the faucet from earlier. Now that our contract is deployed, we can utilize the three helper scripts to fund `MyContract` with LINK (which we got from the Chainlink faucet), create requests, and read the state.
-
-There are 3 helper scripts provided to interact with our contract, located in the scripts directory:
-
-* `fund-contract.js`
-* `request-data.js`
-* `read-contract.js`
-
-They can be used by calling them from `npx truffle exec`. First, we must fund our contract with LINK, which can be done by running the following command:
-
-```shell
-npx truffle exec scripts/fund-contract.js --network live
-```
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/03.png" alt="Truffle DB data model" style="width:100%">
-</figure>
-
-Following deployment, the output displays our contract address as well as the transaction address. We can also look this up on the ropsten [explorer](https://ropsten.etherscan.io/tx/0x39e48b6d8170060affdb57baf8b794424f83296aa9e105163113fea08d300504).
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/04.png" alt="Truffle DB data model" style="width:100%">
-</figure>
-
-Notice that upon completion, a payment of 1 LINK was sent during the transaction, clearly indicating that our contract has properly been funded. Next, we can now `request data` from the contract by running:
-
-```shell
-npx truffle exec scripts/request-data.js --network live
-```
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/05.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>_In the Chainlink explorer for the network that you made the request (in our example we use Ropsten, but it would work similarly for Rinkeby, Kovan, and Mainnet). As you can see the Chainlink node that we were requesting data from picked up our request and waited for 3 block confirmations before executing the job. We are now ready to read the contract’s state with the written answer from the Chainlink node, indicated by the fulfillment transaction (highlighted in red)._</figcaption>
-</figure>
-
-And finally, for reading the data we run our read-contract script. In particular, this will run faster because we’re not creating a transaction, we are simply reading the current state of the smart contract.
-
-```shell
-npx truffle exec scripts/read-contract.js --network live
-```
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/06.png" alt="Truffle DB data model">
-</figure>
-
-Notice for our output when reading the data, we get a number displaying the current price of LINK in USD * 100 (as of writing, 22094). This is due to the value of times specified in our smart contract request-data.js.
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/07.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>_Request-data.js. TRUFFLE_CL_BOX_TIMES is an environment variable which is used to override the default value of 100. This value is used for the precision of the endpoint’s response (in this case, for the price of ETH in USD), and also because Solidity cannot handle decimals. Any of these values can be changed for your project._</figcaption>
-</figure>
-
-Thanks to the power of Truffle, it has never been easier to work with smart contract development. We hope you enjoyed working with our Chainlink Truffle Box, allowing you to fully test, deploy, and interact with contracts on the network. Thanks for reading, and stay tuned for future updates at [https://blog.chain.link/](https://blog.chain.link/).
\ No newline at end of file
diff --git a/src/blog/why-i-love-trufflecon/index.md b/src/blog/why-i-love-trufflecon/index.md
deleted file mode 100644
index 581371614..000000000
--- a/src/blog/why-i-love-trufflecon/index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Why I love TruffleCon
-hide:
-  - navigation
----
-
-**By Josh Quintal, Head of Product & Marketing**
-
-The blockchain space is hitting a plateau.
-
-It’s not a bad thing: new technologies encounter a series of plateaus and this one's no different. It’s a good time to reflect and mature the ecosystem without the noise brought by rapid growth. We're in a crucible period not seen since the tech boom of the 90s. The early adopters are all here forging the blockchain-enabled world, readying for the next influx of users and companies.
-
-Remember when your friends and family raised eyebrows about this chainblock (or whatever) or thought Bitcoin was some kind of scam? Isn't that used to buy drugs? 😳 Now blockchain technology is becoming more efficient, more ubiquitous, and more accessible with each passing day. Now we hear things like "blockchain is the future" coming from outside our community.
-
-Almost two years ago when Truffle reached 4 people and that future seemed less sure, we were on our second retreat at a little place in Yakima. We mused about putting on a blockchain developer conference. Would people actually go? Who's going to speak? Can we get enough content? A few months later we decided to give it a try. Wow, people showed up--and not just that--they loved it! So many great conversations, so much valuable knowledge! Talks about smart contract upgrades, novel uses of merkle proofs, and data storage with IPFS just to name a few. A quietly skeptical Dave Burela (Blockchain Dev, MSFT and TruffleCon 2018 speaker) noted afterwards "You actually pulled it off". 🙂
-
-This year we have over 60 speakers across 60 sessions including: Thomas Hodges on Decentralized Oracles: Reliably Triggering Smart Contracts using Decentralized Computation using Truffle, Alejandro Banzas on RSK Integration with Ganache, and Greg Kapka on Developing Data-Rich Smart Contracts via Provable (Oraclize 2.0).
-
-TruffleCon is a conference, sure, but it's more than that: it's the feeling of excitement when learning a new technology; the eureka we felt when first discovering this new frontier. It's connections made in minutes that can last a lifetime.
-
-It's the culmination of everything we've worked for since the founding of this company.
-
-I hope to not only see you there but to have a chat about what we do well and how we can improve (you'll also get a hat). Together we're building the community that will take us from this plateau onward to the next meteoric growth spurt.
-
-Sincerely,
-
-<p>
-  <img style="margin-left: 0 !important; margin-bottom: 0 !important;" src="/img/blog/why-i-love-trufflecon/josh-signature.png" title="Josh Quintal Signature" alt="Josh Quintal Signature" width="150px">
-</p>
-
-Josh Quintal
diff --git a/src/blog/why-were-organizing-trufflecon-2018/index.md b/src/blog/why-were-organizing-trufflecon-2018/index.md
deleted file mode 100644
index 95388f553..000000000
--- a/src/blog/why-were-organizing-trufflecon-2018/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Why We're Organizing TruffleCon 2018
-hide:
-  - navigation
----
-
-![TruffleCon 2018](/img/blog/why-were-organizing-trufflecon-2018/trufflecon2018header.jpg)
-
-As you have hopefully heard by now, [TruffleCon](/trufflecon2018), Truffle's first-ever user conference, will be on [October 5-7, 2018 in Portland, Oregon, U.S.A](/trufflecon2018).
-
-<p class="m-b-2">
-  <a href="https://trufflecon2018.eventbrite.com" class="btn btn-eventbrite m-t-1" target="_blank">Buy Tickets!</a>
-</p>
-
-## Why TruffleCon?
-
-There is certainly no shortage of conferences related to Ethereum. [Ethereal](https://etherealsummit.com) recently wrapped up in New York City, and [Devcon4](https://devcon4.ethereum.org) is ramping up in Prague later on this year. There's also [EDCON](https://edcon.io), [EthCC](https://ethcc.io), and plenty more, especially when you count those that intersect with the larger blockchain space.
-
-And yet, these events usually have a focus on the larger ecosystem. What about the people who are deep in the trenches, building the dapps and deploying the contracts?
-
-**We want TruffleCon to be the place for people who are doing the building.**
-
-Also, many developers are working in silos, connected to other teams only by GitHub, Gitter, StackExchange, Reddit, or other "[weak ties](https://en.wikipedia.org/wiki/Interpersonal_ties)". **We want to strengthen those connections to bring people together**.
-
-We want people to share their ideas, and talk about their successes and challenges. We want people to promote their projects, of course, and professional networking is always a part of these events, but more than anything else, **we want people to be heard**.
-
-
-## Why now?
-
-We've noticed a shift over the past year or so in the usage of Truffle.
-
-Whereas many of the comments and requests in [our Gitter channel](https://gitter.im/ConsenSys/truffle) and GitHub issues were originally regarding local tests, and in sandboxes, we noticed more and more people deploying their contracts to the public test networks and even the mainnet. While this, of course, was always the intention, it shows that **confidence in our tools and the Ethereum ecosystem is growing**.
-
-**We want to help people "go live".** And so we believe that there has never been a better time than now.
-
-
-## Why Portland?
-
-Portland is a vibrant city full of world-class food and drink, unmatched outdoor opportunities, and an excellent transportation system for getting where you need to go. And early October is typically a sweet spot where the days are still warm and dry, while the fall colors are starting to come into view.
-
-If you've never been, you're missing out. And why not stay awhile once you're here?
-![TruffleCon 2018](/img/blog/why-were-organizing-trufflecon-2018/portlandskyline.jpg)
-*Photo courtesy of Flickr/sama093. [Large version here](https://flic.kr/p/qg3nwJ).* 
-
-## See you in October!
-
-From Truffle founder Tim Coulter:
-
-<blockquote><em>"The best conference we could put on is one where there's a ton of active engagement. I want people to feel like they are surrounded by other people who can help them. And I want them to leave feeling like they learned something and that the Truffle community is better off because they were there.<br/><br/>
-
-If we do it right, people will go home inspired, and will change how they do their development."</em></blockquote>
-
-We can't wait to see you there. If you have questions, feel free to tweet us at [@trufflesuite](https://twitter.com/trufflesuite). And please use the hashtag [#TruffleCon](https://twitter.com/search?l=&q=%23TruffleCon&src=typd).
-
-<p class="m-b-2">
-  <a href="https://trufflecon2018.eventbrite.com" class="btn btn-eventbrite m-t-1" target="_blank">Buy Tickets!</a>
-</p>
-
------
-
-*Mike Pumphrey is an Enterprise Trainer at ConsenSys working on the Truffle team. With over a dozen years of experience in documentation, support, and training, Mike is passionate about making technical concepts understandable to a wider audience. Mike is also the lead organizer for TruffleCon 2018.*
diff --git a/src/blog/you-can-now-make-your-own-truffle-box/index.md b/src/blog/you-can-now-make-your-own-truffle-box/index.md
deleted file mode 100644
index dcff42890..000000000
--- a/src/blog/you-can-now-make-your-own-truffle-box/index.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: You Can Now Make Your Own Truffle Box
-hide:
-  - navigation
----
-
-Two months ago we unveiled official integration with **Truffle Boxes**, example Ethereum applications and/or boilerplates that put complimentary tools and libraries into sweet, easily-downloadable packages. In addition to rolling out some official boxes, [Status.im](https://status.im/) released [the first community-supported box](/boxes/status).
-
-Today we're happy to announce anyone can now make their very own Truffle Box!
-
-## Making a Box
-
-To get started making a box, we've added a page to [our documentation](/docs/truffle/advanced/creating-a-truffle-box). For those starting a new box from scratch, we've also created a [blueprint Truffle Box](/boxes/blueprint) to get you started quickly.
-
-## The First Wave
-
-We included a call for pre-screening in the community section of our first box rollout and some trailblazers answered the call!
-
-Here are the first community boxes:
-
-**[Quintor/angular-truffle-box](/boxes/angular-truffle-box)**<br/>
-This Truffle Box provides a base for working with the Truffle Suite and Angular. It provides a basic working example of the MetaCoin contracts with Angular components. This project is generated with Angular CLI.
-
-**[hackingbeauty/react-dapp-material-ui](/boxes/react-dapp-material-ui)**<br/>
-In addition to Webpack and React, this box adds: React-Router, Redux and Material-UI for easy skinning of a Dapp.
-
-**[antony/svelte-box](/boxes/svelte-box)**<br/>
-A Truffle box using SvelteJS and Rollup. This box contains everything you need to start building a smart-contract app.
-
-**[kierenh/vue-dark-chocolate](/boxes/vue-dark-chocolate)**<br/>
-A truffle box that comes with everything you need to start using smart contracts from a Vue App with Bootstrap styling and components. Supporting frameworks include Vuex, Vue-Router & Bootstrap 4 (via Bootstrap-Vue) and webpack. The sample uses webpack-dev-server for hot-reloading or you can build and serve from express.
-
-Check out [the full list of boxes here](/boxes).
-
-A huge thank you to our entire community! We're humbled by your dedication and excited to see what's in store for the future.
-
--- Josh & the Truffle Team
diff --git a/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md b/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md
deleted file mode 100644
index 203aa8c58..000000000
--- a/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: You Decide - Pipeline or Table View in Truffle Teams' Refreshed Deployments Manager
-hide:
-  - navigation
----
-
-![Truffle Teams Deployments Refresh Banner](/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/blog-header.png)
-
-With Truffle Teams, you can manage multiple deployed instances of your smart contracts across different networks. We’ve heard mixed feedback about this workflow and are updating it accordingly: adding a table view and a deployment details page. We're also offering more insight into each deployment, by providing the cost and console output.
-
-## What’s New with Deployments?
-
-Our first iteration of Visual Deployments revolved around a pipeline view, with your commits on the left hand side and a production network on the right. While some do use and appreciate this type of workflow, many have only   a single production instance, and having an entire column just for this doesn’t make sense for those use cases. With that in mind, we’re offering a new table view, so you can see all of your deployed instances even more quickly and in an uncluttered way. In the future, you’ll also be able to sort and filter this table for even easier access.
-
-<figure>
-  <img class="mb-4 w-100 figure-shadow" src="/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/deployments-refresh-1.png" alt="The new deployments table view">
-  <figcaption class="text-center font-italic">The new deployments table view--you can still access the card view via the toggle switch in the upper-right.</figcaption>
-</figure> 
-
-You’ll also notice that clicking the name of a deployment now goes to a new deployment details screen. This contains the current status of the deployment along with its console output (an oft-requested addition)!
-
-<figure>
-  <img class="mb-4 w-100 figure-shadow" src="/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/deployments-refresh-2.png" alt="The deployment details screen">
-  <figcaption class="text-center font-italic">The deployment details screen. Notice you can now access the console output!</figcaption>
-</figure>
-
-For more information on the new deployments screen, check out the [Truffle Teams Deployments docs](/docs/teams/deployments/deployment-details).
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE DEPLOYMENTS MANAGER</a>
-</div>
-
-## Thoughts?
-
-We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven’t met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/introducing-ganache-7/example-1.png b/src/img/blog/introducing-ganache-7/example-1.png
similarity index 100%
rename from src/blog/introducing-ganache-7/example-1.png
rename to src/img/blog/introducing-ganache-7/example-1.png
diff --git a/src/blog/introducing-ganache-7/example-2.png b/src/img/blog/introducing-ganache-7/example-2.png
similarity index 100%
rename from src/blog/introducing-ganache-7/example-2.png
rename to src/img/blog/introducing-ganache-7/example-2.png
diff --git a/src/blog/introducing-ganache-7/ganache-v7.png b/src/img/blog/introducing-ganache-7/ganache-v7.png
similarity index 100%
rename from src/blog/introducing-ganache-7/ganache-v7.png
rename to src/img/blog/introducing-ganache-7/ganache-v7.png
diff --git a/src/blog/introducing-truffle-dashboard/secrets-oh-no.png b/src/img/blog/introducing-truffle-dashboard/secrets-oh-no.png
similarity index 100%
rename from src/blog/introducing-truffle-dashboard/secrets-oh-no.png
rename to src/img/blog/introducing-truffle-dashboard/secrets-oh-no.png
diff --git a/src/blog/introducing-truffle-dashboard/truffle-dashboard-cli.png b/src/img/blog/introducing-truffle-dashboard/truffle-dashboard-cli.png
similarity index 100%
rename from src/blog/introducing-truffle-dashboard/truffle-dashboard-cli.png
rename to src/img/blog/introducing-truffle-dashboard/truffle-dashboard-cli.png
diff --git a/src/blog/introducing-truffle-dashboard/truffle-dashboard-confirm.png b/src/img/blog/introducing-truffle-dashboard/truffle-dashboard-confirm.png
similarity index 100%
rename from src/blog/introducing-truffle-dashboard/truffle-dashboard-confirm.png
rename to src/img/blog/introducing-truffle-dashboard/truffle-dashboard-confirm.png
diff --git a/src/blog/introducing-truffle-dashboard/truffle-dashboard-connect-wallet.png b/src/img/blog/introducing-truffle-dashboard/truffle-dashboard-connect-wallet.png
similarity index 100%
rename from src/blog/introducing-truffle-dashboard/truffle-dashboard-connect-wallet.png
rename to src/img/blog/introducing-truffle-dashboard/truffle-dashboard-connect-wallet.png
diff --git a/src/blog/introducing-truffle-dashboard/truffle-dashboard-private-keys.png b/src/img/blog/introducing-truffle-dashboard/truffle-dashboard-private-keys.png
similarity index 100%
rename from src/blog/introducing-truffle-dashboard/truffle-dashboard-private-keys.png
rename to src/img/blog/introducing-truffle-dashboard/truffle-dashboard-private-keys.png
diff --git a/src/blog/introducing-truffle-dashboard/truffle-dashboard-select-network.png b/src/img/blog/introducing-truffle-dashboard/truffle-dashboard-select-network.png
similarity index 100%
rename from src/blog/introducing-truffle-dashboard/truffle-dashboard-select-network.png
rename to src/img/blog/introducing-truffle-dashboard/truffle-dashboard-select-network.png
diff --git a/src/blog/introducing-truffle-dashboard/truffle-dashboard-sign.png b/src/img/blog/introducing-truffle-dashboard/truffle-dashboard-sign.png
similarity index 100%
rename from src/blog/introducing-truffle-dashboard/truffle-dashboard-sign.png
rename to src/img/blog/introducing-truffle-dashboard/truffle-dashboard-sign.png

From 0703187df0ebb10b7084ec3e3e54568ae6a8394b Mon Sep 17 00:00:00 2001
From: Minh Nguyen <minhnc@younetco.com>
Date: Mon, 21 Mar 2022 11:01:49 +0700
Subject: [PATCH 02/14] Update content blog and some url

---
 custom_theme/main.html                        |  18 +
 src/.pages                                    |  14 +-
 .../index.md                                  |  29 ++
 .../index.md                                  |  97 ++++++
 .../index.md                                  |  26 ++
 .../index.md                                  |  53 +++
 .../index.md                                  |  50 +++
 .../index.md                                  | 179 ++++++++++
 .../index.md                                  |  69 ++++
 .../index.md                                  |  82 +++++
 .../axonis-enterprise-use-of-truffle/index.md |  90 +++++
 .../index.md                                  |  41 +++
 src/blog/blockchain-will-cure-cancer/index.md |  47 +++
 .../index.md                                  |  31 ++
 .../index.md                                  |  32 ++
 .../index.md                                  |  39 +++
 .../index.md                                  |  80 +++++
 .../index.md                                  |  62 ++++
 .../index.md                                  | 122 +++++++
 src/blog/designing-the-ganache-logo/index.md  |  70 ++++
 .../index.md                                  |  93 ++++++
 src/blog/drizzle-150-a-new-beginning/index.md |  69 ++++
 .../index.md                                  |  57 ++++
 src/blog/drizzle-vue-a-truffle-story/index.md |  69 ++++
 src/blog/ethereum-gas-exactimation/index.md   | 174 ++++++++++
 src/blog/first-ever-truffle-retreat/index.md  | 124 +++++++
 .../index.md                                  |  49 +++
 src/blog/github-repository-moved/index.md     |  23 ++
 .../index.md                                  |  74 +++++
 .../index.md                                  |  98 ++++++
 .../index.md                                  |  62 ++++
 .../index.md                                  |  74 +++++
 src/blog/introducing-ganache-7/index.md       | 310 ++++++++++++++++++
 .../introducing-truffle-dashboard/index.md    | 162 +++++++++
 .../introducing-truffle-db-part-1/index.md    |  54 +++
 .../introducing-truffle-db-part-2/index.md    | 110 +++++++
 .../index.md                                  |  87 +++++
 .../index.md                                  |  30 ++
 .../index.md                                  |  40 +++
 .../index.md                                  |  96 ++++++
 .../index.md                                  |  41 +++
 .../index.md                                  |  47 +++
 .../stack-tracing-with-truffle-test/index.md  |  42 +++
 src/blog/sunsetting-truffle-teams/index.md    |  46 +++
 src/blog/take-a-dive-into-truffle-5/index.md  | 136 ++++++++
 .../index.md                                  |  36 ++
 src/blog/testrpc-is-now-ganache/index.md      |  37 +++
 .../index.md                                  |  81 +++++
 .../index.md                                  |  31 ++
 .../index.md                                  |  32 ++
 src/blog/token-taxonomy-framework/index.md    |  15 +
 src/blog/truffle-320-released/index.md        |  44 +++
 .../index.md                                  |  50 +++
 .../index.md                                  |  38 +++
 .../index.md                                  |  39 +++
 .../index.md                                  |  35 ++
 .../index.md                                  |  37 +++
 .../truffle-teams-gets-a-new-look/index.md    |  53 +++
 .../index.md                                  |  37 +++
 src/blog/truffle-v5-has-arrived/index.md      | 113 +++++++
 .../index.md                                  |  46 +++
 .../index.md                                  |  44 +++
 .../index.md                                  |  25 ++
 src/blog/using-the-ens-integration/index.md   | 126 +++++++
 .../index.md                                  | 102 ++++++
 src/blog/why-i-love-trufflecon/index.md       |  31 ++
 .../index.md                                  |  59 ++++
 .../index.md                                  |  37 +++
 .../index.md                                  |  45 +++
 69 files changed, 4584 insertions(+), 7 deletions(-)
 create mode 100644 src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
 create mode 100644 src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
 create mode 100644 src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
 create mode 100644 src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
 create mode 100644 src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
 create mode 100644 src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
 create mode 100644 src/blog/announcing-collaboration-with-filecoin/index.md
 create mode 100644 src/blog/announcing-full-portable-solidity-debugger/index.md
 create mode 100644 src/blog/axonis-enterprise-use-of-truffle/index.md
 create mode 100644 src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
 create mode 100644 src/blog/blockchain-will-cure-cancer/index.md
 create mode 100644 src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
 create mode 100644 src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
 create mode 100644 src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
 create mode 100644 src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
 create mode 100644 src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
 create mode 100644 src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
 create mode 100644 src/blog/designing-the-ganache-logo/index.md
 create mode 100644 src/blog/develop-using-fluidity-truffle-box/index.md
 create mode 100644 src/blog/drizzle-150-a-new-beginning/index.md
 create mode 100644 src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
 create mode 100644 src/blog/drizzle-vue-a-truffle-story/index.md
 create mode 100644 src/blog/ethereum-gas-exactimation/index.md
 create mode 100644 src/blog/first-ever-truffle-retreat/index.md
 create mode 100644 src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
 create mode 100644 src/blog/github-repository-moved/index.md
 create mode 100644 src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
 create mode 100644 src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
 create mode 100644 src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
 create mode 100644 src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
 create mode 100644 src/blog/introducing-ganache-7/index.md
 create mode 100644 src/blog/introducing-truffle-dashboard/index.md
 create mode 100644 src/blog/introducing-truffle-db-part-1/index.md
 create mode 100644 src/blog/introducing-truffle-db-part-2/index.md
 create mode 100644 src/blog/iterate-faster-with-truffle-teams/index.md
 create mode 100644 src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
 create mode 100644 src/blog/one-hundred-documentation-pull-requests/index.md
 create mode 100644 src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
 create mode 100644 src/blog/removing-installation-issues-continued-testrpc/index.md
 create mode 100644 src/blog/sandbox-forking-with-truffle-teams/index.md
 create mode 100644 src/blog/stack-tracing-with-truffle-test/index.md
 create mode 100644 src/blog/sunsetting-truffle-teams/index.md
 create mode 100644 src/blog/take-a-dive-into-truffle-5/index.md
 create mode 100644 src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
 create mode 100644 src/blog/testrpc-is-now-ganache/index.md
 create mode 100644 src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
 create mode 100644 src/blog/the-best-ways-to-contribute-to-truffle/index.md
 create mode 100644 src/blog/the-blockchain-problem-that-ens-solves/index.md
 create mode 100644 src/blog/token-taxonomy-framework/index.md
 create mode 100644 src/blog/truffle-320-released/index.md
 create mode 100644 src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
 create mode 100644 src/blog/truffle-and-infura-support-arbitrum/index.md
 create mode 100644 src/blog/truffle-and-infura-support-optimism/index.md
 create mode 100644 src/blog/truffle-and-infura-support-polygon/index.md
 create mode 100644 src/blog/truffle-boxes-making-life-sweeter/index.md
 create mode 100644 src/blog/truffle-teams-gets-a-new-look/index.md
 create mode 100644 src/blog/truffle-teams-now-supports-private-repositories/index.md
 create mode 100644 src/blog/truffle-v5-has-arrived/index.md
 create mode 100644 src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
 create mode 100644 src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
 create mode 100644 src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
 create mode 100644 src/blog/using-the-ens-integration/index.md
 create mode 100644 src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
 create mode 100644 src/blog/why-i-love-trufflecon/index.md
 create mode 100644 src/blog/why-were-organizing-trufflecon-2018/index.md
 create mode 100644 src/blog/you-can-now-make-your-own-truffle-box/index.md
 create mode 100644 src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md

diff --git a/custom_theme/main.html b/custom_theme/main.html
index 749c0a947..6765022f1 100644
--- a/custom_theme/main.html
+++ b/custom_theme/main.html
@@ -12,6 +12,24 @@
 
 {% endblock %}
 
+{% block extrahead %}
+    {{ super() }}
+    <!-- Redirect -->
+    <script>(function(){
+      var path = location.pathname;
+      var slug = path.slice(1);
+      var ext = slug.split('.').pop();
+      var regex = /index\.html\/?$/;
+      if(path.match(regex)) {
+        location.href = path.replace(regex,'')
+      } else if(ext !== slug && ext === 'html') {
+        location.href = path.substr(0, path.lastIndexOf(".")) + '/';
+      } 
+    })()</script>
+    <!-- End redirect -->
+
+{% endblock %}
+
 <!-- Announcement bar -->
 {% block announce %}
   <!-- Google Tag Manager (noscript) -->
diff --git a/src/.pages b/src/.pages
index 31a31633d..31f2ed896 100644
--- a/src/.pages
+++ b/src/.pages
@@ -1,8 +1,8 @@
 nav:
-    - Home: index.md
-    - Documentation: docs
-    - guides
-    - tutorial
-    - boxes
-    - blog
-    - community
\ No newline at end of file
+    - Home: /
+    - Documentation: docs/
+    - guides: guides/
+    - tutorial: tutorial/
+    - boxes: boxes/
+    - blog: blog/
+    - community: community/
\ No newline at end of file
diff --git a/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md b/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
new file mode 100644
index 000000000..f0aa0f02c
--- /dev/null
+++ b/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
@@ -0,0 +1,29 @@
+---
+title: 10 Things We Don't Do That Make Working at Truffle Awesome
+hide:
+  - navigation
+---
+
+![tapestry of Truffle team headshots](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-1.jpg)
+
+At Truffle we have an extremely tight-knit team. You'll see that at this year's TruffleCon, a conference for hundreds of attendees organized by only a handful of people. We often have more work than we can handle, yet we take it on because we love the work we're doing and we love the people we work with. In my history of hopping startups – I'm currently on number nine – I haven't seen this anywhere else, so I wanted to take the time to highlight some things that set Truffle apart from the rest. Here's a list of what we don't do that makes working at Truffle awesome:
+
+1. **We don't have an office.** This is the most important point, as it permeates the makeup and structure of our organization. We have members all over the US and Canada. I live in Yakima, WA, of all places, known more for apples and hops than for tech and blockchain. For communication efficiency we intentionally hired within US time zones, but we realize remote work means there's no office to clock into. We currently have team members working from China, Japan and Germany, following the path their family and personal lives have taken them, while still remaining valuable members of the team.
+1. **We don't clock in.** For most of our team, working remotely means working from home. Often our home life and work life are intertwined, and we know that on some days work wins (i.e., I'm writing this the morning of July 4th, a holiday in the United States), and on other days life wins. This means a flexible schedule is absolutely required. Often, I tell my team to add their life events to their work calendar, like taking their dog to the vet or their kids to school, to ensure work doesn't encroach on the needs of their home life.
+1. **We don't track vacation time.** Our vacation policy is unlimited: We take whatever time we need. This is important to our work/life balance, and it also ensures our team gets much-needed breaks. Over time we've perfected this policy by engaging work and life into a little quid pro quo: If you let your coworkers know about your time off in advance, and you ensure your work is completed and fully handed off to another team member while you're away, then the time is yours. (Emergencies, of course, aren't governed by this policy.) This has worked surprisingly well. Recently a coworker "sipped bevvies" in the Bahamas for a week and a half, and his team happily held their own while he was on vacation. We all recognize that we're working extremely hard, so we all want to step in when others need a break.
+![Liz Daldalian proudly displaying a fish she caught](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-2.jpg)
+1. **We don't let people burn out.** Burn out can be a huge you-know-what. It comes on quick, often sneaking in at the tail end of an intense work effort where life lost out one too many times. It also comes when a striking life event seeps into our work life. It's an energy killer, and a turnover monster out to eat up all our employees. We don't let it eat us. After our first burn out event caused one of our best developers to leave, we created a company policy called the Get Out of Burn Out Free Card. When played, it gives the team member two weeks of vacation starting immediately, no questions asked. It's up to the rest of the team to pick up the slack, and find creative solutions in the team member's absence. It's not a card that gets played often, but it's been played a few times since and we've saved valuable team members from throwing in the towel. Even if the card never gets played, it's reassuring to know other members of the team have our backs in times of need.
+1. **We don't wear business attire.** We work from home, which means we wear the attire we'd normally wear at home. I'm known for wearing pajamas, often brightly colored ones, even during business calls. At the very least, professionalism only matters to the eye of the webcam, and anything out of frame is totally fair game. And heck, we're working hard, so we want to be comfortable.
+![Truffle team meeting featuring funny hats and coats](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-3.jpg)
+1. **We don't stay remote.** Though video calls and Slack messages are our main source of communication, we know nothing builds a relationship better than real human connection. That's why we plan full company retreats three to four times a year, to exciting places that help us all become closer. Our most recent retreat took us to the snowy mountains of Breckinridge, CO. Yes, it was super cold outside and the air was hard to breathe, but it was a new experience for all of us and we came out with some interesting stories to tell. My most memorable moment was when I commandeered a sled and careened right off the side of a hill. Lucky for me it was a false slope and I had no injuries, though my team certainly got a good laugh.
+![Truffle team in Breckenridge](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-4.jpg)
+![Truffle team at TruffleCon 2018](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-5.jpg)
+1. **We don't try to be fully flat.** We love the egalitarian nature of flat organizations, but we also love the efficiency of explicit hierarchy. In our experience flat organizations push hierarchy under the surface, turning decision-making into a confusing game of personal politics and popularity contests. Instead, we take a hybrid approach. We accept that hierarchy exists in our organization, but we try to make it as flat as possible. We push decisions as far down in the hierarchy as they can go, so each team member feels empowered to do the best work possible, and we clearly define the decisions that each role can make. As the CEO of Truffle, I get to make decisions on money and resources, but I'm also the founder, which means I once touched every line of code. That's now Nick D'Andrea's job, our head of engineering, and the jobs of the engineers leading each of our individual engineering projects.
+![Tim Coulter photoshopped as Steve Jobs](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-6.jpg)
+1. **We don't leave people hanging.** Having a light hierarchy gives us the ability to appoint leads. Leads are sometimes a vehicle for accountability, like managers in traditional organizations, but most of the time they're there to serve the members of our team. Every team member gets a lead, and gets a weekly one-on-one that they can use any way they like. Often these one-on-ones are used as a regular place to vent: they help us catch issues early and provide team members a useful outlet so small issues don't turn into something bigger. Leads go to bat for their team members when the team member doesn't feel comfortable raising an issue themselves.
+1. **We don’t give in to perfect.** At least, not initially. In our organization, perfect is the enemy of the good. Had I not been writing this on Independence Day, I may have shot for ten items to round out the list instead of nine. Similarly, it’s the same reason we release a new version of Truffle weekly: We like to bring value to users as quickly as possible, and then strive towards perfection iteratively over time. This idea governs all the work that we do, from software to sales to even our VC pitch decks, because we realize the feedback we get from users far outweighs our initial ideas at perfection. If you have thoughts on how we can better improve our blog or this blog post, please send me an email at tim@trufflesuite.com.
+1. **See #9.**
+
+Working at Truffle has been an amazing journey. It's incredibly humbling to see a project I started from necessity turn into a company run by the heart and soul of a close, tight-knit group of professionals. Truffle would be nothing without this team, and without Truffle I'd likely not be excited to go to work every morning (I commute downstairs in my pajamas, but still). Thank you, Truffle team, for making this company awesome.
+
+![Truffle team members preparing for TruffleCon 2019](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-7.jpg)
diff --git a/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md b/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
new file mode 100644
index 000000000..d1463276d
--- /dev/null
+++ b/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
@@ -0,0 +1,97 @@
+---
+title: 2020 is Finally Over - A Year End Wrapup
+hide:
+  - navigation
+---
+
+![Truffle End of Year Wrapup Banner](/img/blog/2020-is-finally-over-a-year-end-wrapup/blog-header.png)
+
+2020 has been a trying time for us all: COVID-19 is still ravaging the world, the United States mired through one of our most contentious elections yet; basically, it’s been a rough year.
+
+It’s not all bad though! Let’s take a look back at some positive things that came out of 2020, along with a little of what to look forward to in 2021.
+
+## A Look Back
+
+### ConsenSys Fold-in
+
+This year was a busy one for Truffle, but the biggest news squeaked in just in time for the end of the year: Truffle is now a part of ConsenSys! We’re excited to collaborate with Infura, MythX, MetaMask, and more!
+
+### Teams Enhancements
+
+It was also a big year for Truffle Teams. We’ve added new features and enhanced existing ones to complete the core workflow Truffle Teams offers (I summarize this in our final Dapp Lifecycle webinar episode here). Big highlights include the release of:
+
+* **Dashboard** ([Blog](/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard) | [Docs](/docs/teams/dashboard/dashboard-overview)): More incoming data begets a greater need to gain insights and properly segment that data to prevent overload. Truffle Teams new dashboard provides an overview of your application, along with ways to drill down and get further context on more narrow slices.
+* **Debugger** ([Blog](/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger) | [Docs](/docs/teams/debugger/debugger-overview)): This is a huge workflow enhancement--allowing us to debug transactions in the places we're already viewing--via the deployment details screen or while monitoring individual contracts.
+* **Early Access** ([Blog](/blog/try-new-features-first-with-truffle-teams-early-access)): Truffle Teams is constantly evolving. Between adding new features, polishing, and refining the app there's so much we'd love to share with the world in a faster way. Wouldn't it be nice to take those new enhancements and features for a test drive? Now you can with early access!
+* **Deployment and Monitoring Improvements** ([Blog](/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager) | [Docs](/docs/teams/deployments/deployments-overview)): We’ve added a table view and a deployment details page. We're also offering more insight into each deployment, by providing the cost and console output.
+
+Before the end of this year, we’ll be releasing the Contract Manager to Early Access, completing the workflow and allowing teams to build, deploy, monitor, and debug conveniently in one place.
+
+### Truffle’s Unstoppable Release Schedule
+
+Going on 2 years now, Truffle has released on a weekly basis. We’re so proud of our team for their hard work and commitment to improving the lives of other developers. We don’t have any plans to stop this cadence--full steam ahead for the Truffle train!
+
+### Debugger and Test Enhancements
+
+2020 saw great improvements to Truffle, including debugging verified contracts with `truffle debug --fetch-external` ([Blog](/blog/debugging-verified-external-contracts-with-truffle-debugger)), support for stacktraces in tests with `truffle test --stacktrace` ([Blog](/blog/stack-tracing-with-truffle-test)), and even freshly-added support for stepping through Vyper contracts!
+
+### Forking in Ganache – much improved!
+
+Since the summer of 2020 saw DeFi reach a whole new level of usage, more and more people have been looking to test their code against live smart contracts on-chain. Ganache has always had its `--fork` option, but thanks to members of the community, we’ve fixed more than half a dozen critical bugs that inhibited certain use cases. Forking is more reliable than ever!
+
+### Collaborations
+
+2020 was a year of partnerships for Truffle, seeing us make good on the vision to become a multi-blockchain toolset.
+
+* **Tezos** ([Blog](/blog/branching-out-announcing-tezos-support-in-truffle) | [Docs](/docs/tezos/truffle/quickstart)): Tezos is supported in Truffle! Many of the commands you’re used to are still here: compile, deploy, test, and console!
+* **Corda** ([Blog](/blog/branching-out-phase-2-of-corda-flavored-ganache) | [Docs](/docs/ganache/corda/working-with-corda)): Ganache UI supports creating Corda networks! Easily create and introspect into a local Corada development network with a familiar UI.
+* **Filecoin** ([Blog](/blog/announcing-collaboration-with-filecoin)): Truffle Preserve allows you to easily preserve files on IPFS and/or Filecoin.
+
+## A Look Forward
+
+### Continued Maturation of Truffle Teams
+
+Truffle Teams will continue to be enhanced throughout 2021, with useful additions such as:
+
+* **Monitoring enhancements**: receive alerts when we observe contract anomalies, such as a sudden spike in failed transactions or a drop in balance. Set up your own custom triggers for things like an event firing or a certain address interacting with your contracts.
+* **Debugging public transactions**: The debugger only works for sandboxes currently, but we want to bring it to feature parity with the CLI debugger by also supporting public networks.
+* **Custom Network Support**: Deploy via your own infrastructure by supplying the RPC URL. Put your DappNode to good use!
+* **Continuous (Automated) Deployment**: You can already deploy manually via Truffle Team’s deployment wizard, but there may be times you know you’ll be continuously deploying your changes. For example iterating on a new feature in a sandbox.
+* **Better Dashboard**: The dashboard today provides a good overview of your deployment, but we’re going to expand it to provide better drill down functionality and greater context.
+
+### Advanced Analysis
+
+Truffle’s been around for over 5 years now. In that time, we’ve been thinking about how smart contract systems grow and change over time. Be on the lookout for tools to better examine your contract’s deployment history, track contracts across forks, and more!
+
+### Ganache Rewrite
+
+Ganache is getting a tune-up! This means faster execution of your test suites--**4x faster** in the case of SushiSwap’s test suite. Also lookout for ways to test pending transactions, implementation of EIP-1193, the ability to set the account nonce (`evm_setAccountNonce`), and support for running Ganache in the browser. We’ll also begin publishing auto-generated API documentation so you always have a reference close at hand.
+
+### The Return of the Frontend
+
+2020 didn’t see much movement in our set of frontend libraries, [Drizzle](https://github.com/trufflesuite/drizzle). In 2021 we’ll be giving some love to the frontend in the form of easier state management, more granular tooling, and more.
+
+### More Collaborations
+
+As mentioned above, now that we’re a part of ConsenSys Software Inc, Truffle's going to have many opportunities to collaborate with other groups. We’d love to hear what this sparks in you! Check out our Slack group below and let us know your thoughts. Here are some links to CSI’s groups so you know what they’re about:
+
+* [Infura](https://infura.io/)
+* [MythX](https://mythx.io/)
+* [ConsenSys Diligence](https://consensys.net/diligence/)
+* [MetaMask](https://metamask.io/)
+* [CodeFi](https://codefi.consensys.net/)
+* [ConsenSys Quorum](https://consensys.net/quorum/)
+
+## Catch us on Slack
+
+We want Truffle the best developer tool suite in the blockchain space for new and seasoned devs alike. Let us know what you think about our plans, or if you/your team have other needs we haven't met yet.
+
+Continue the conversation with your fellow Trufflers in our Slack community!
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
+</div>
+
+Thanks!
+
+_Josh Quintal, Product Lead & The Whole Team at Truffle_
diff --git a/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md b/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
new file mode 100644
index 000000000..d0fc6ab0f
--- /dev/null
+++ b/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
@@ -0,0 +1,26 @@
+---
+title: 3 Ways Enterprises Are Addressing Blockchain Privacy Concerns
+hide:
+  - navigation
+---
+
+[Blockchain has been touted as the great connector to integrate businesses under consortium networks](https://www.forbes.com/sites/andrewarnold/2019/02/21/why-2019-may-become-the-year-of-enterprise-blockchain/#66c9e516427e). It’s ability to verify data using smart contracts and provide transparency across network participants through immutable shared data has people talking about a technical revolution. However, this benefit has been a double-edged sword because the enterprise world is skeptical about sharing sensitive data on a ledger where the information cannot be deleted. The good news is, this year has seen numerous announcements of single and multi-party blockchain pilots by the Fortune 500 such as… [Starbucks](https://news.microsoft.com/transform/starbucks-turns-to-technology-to-brew-up-a-more-personal-connection-with-its-customers/) and [MetLife](https://www.forbes.com/sites/stevenehrlich/2019/06/19/metlife-plans-to-disrupt-2-7-trillion-life-insurance-industry-using-ethereum-blockchain/#3e9a87277022). Data privacy issues haven’t stopped them and the enterprise blockchain world has taken these steps to shift their thinking.
+
+## 1. Store references to data on the blockchain
+The simplest way to circumvent this data privacy issue is to not put the data on the chain. A popular approach is to share anonymous IDs on the blockchain and use that to get data from another system. For example, [MediLedger](https://www.mediledger.com/) is a supply chain pilot in the heavily regulated pharmaceutical industry that uses a blockchain to trace a drug’s exchange of hands and then uses another private peer-to-peer application to transfer details about the medication. What is passed around on the chain is just an anonymous identifier to the medication. This keeps transactions light, allows enterprises to regulate data access, and uses proven methods to secure sensitive data. MediLedger actually takes this a step further and anonymizes the transaction details with zero knowledge proofs — which I’ll cover later.
+
+## 2. Use blockchains to verify instead of share
+Blockchain’s real power is in its ability to verify data. Instead of putting actual information on the chain, a solution could combine unique elements of data and share a hash of it on the blockchain. Hashing is a cryptographic method that generates a random, unique value from a fed input. In this scenario, the resulting hash itself doesn’t reveal any information, but it can verify an on-hand document by checking if it generates the same hash when fed into the function. The data inputs could also be selected in a way that no critical information is sampled to create the hash so that compliance regulations can be withheld. Businesses have reliable methods to exchange data, but the verification is long and expensive. By using blockchain as a verifier and not the store of the data, we can ease the pain point and maintain a higher level of privacy than open sharing.
+
+## 3. Anonymize transactions with zero knowledge proofs
+Building off the two previous trends, blockchain pilots have taken an extra step in securing data and replaced hashed transaction details with zero knowledge proofs (ZKP). [ZKPs allow for verification of a transaction without exposing transaction details](https://hackernoon.com/wtf-is-zero-knowledge-proof-be5b49735f27). Now two businesses can communicate on a public network and be completely anonymous. This is because what is placed on the chain is a proof that is cryptographically verified by the receiver, not the data that goes into the transaction. This shift in data validation methods addresses data privacy concerns and supports industry consortiums.
+
+## Blockchain is just one piece of the puzzle
+
+Finally, with all the hype on blockchain’s potential in the last years, we have to remember that this is just another tool in the technology box when solving a problem. Enterprises have gotten smarter in finding ways to use blockchain to solve unique problems that are more expensive or less reliable with other technologies. What we have seen is that distributed ledgers can’t do everything, but when paired with multiple other technologies that help fill gaps, the solution as a whole is optimized. A better perspective is to not think of future solutions as blockchain applications, but rather applications that leverage the unique advantages of blockchain.
+
+## About West Monroe Partners
+
+West Monroe is a national business and technology consulting firm that partners with dynamic organizations to reimagine, build, and operate their businesses at peak performance. Our team of more than 1,400 professionals across nine offices is comprised of an uncommon blend of business consultants and deep technologists. I am one of those consultants and I am one of the leaders of our blockchain center of excellence. I’ll be presenting on Sunday morning (8/4) about one of our blockchain projects that looks to [incentivize electric vehicle owners to charge with cleaner energy](https://trufflecon2019.sched.com/event/RHIR/driving-renewable-energy-usage-with-blockchain-and-electric-vehicles). Check us out at our [website](https://www.westmonroepartners.com/) and read more about our [blockchain perspectives](https://blog.westmonroepartners.com/?s=blockchain) on our blog!
+
+Danny Pan is a consultant with West Monroe Partner’s Seattle Technology Practice. He focuses on providing value in adopting blockchain, distributed technologies, and robust SDLC practices. Contact Danny at [dpan@wmp.com](mailto:dpan@wmp.com)
diff --git a/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md b/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
new file mode 100644
index 000000000..df6e65cb9
--- /dev/null
+++ b/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
@@ -0,0 +1,53 @@
+---
+title: 5 Trends Impacting the Blockchain Developer Experience
+hide:
+  - navigation
+---
+
+In this article we explore 5 trends impacting the developer-experience (or DX) when it comes to building blockchain-based solutions. Specifically, applications and services that leverage a blockchain or distributed ledger or as part of their overall architecture.
+
+This is, of course, is by no means a definitive list. As with everything in the industry, change is happening fast and as such, this is more of a selection of trends that are on the team’s radar. If there’s anything we’ve missed or should know about, we’d love to hear from you (or speak in person at [TruffleCon 2019](/trufflecon2019)).
+
+## #1 Development tooling release velocity is on fire
+
+Obviously we’re a little biased, but in this case, we’re talking about tools and utilities that are not [chocolate-themed](/truffle). It’s literally every day we collectively come across something new that makes our lives as developers (or users, auditors, admins, etc) easier.
+
+This is a big deal for the long-term success of the wider ecosystem because happy and productive developers obviously strongly correlates with increased experimentation, the volume of shipped products and services, and expedites the process of on-boarding new people (developers or otherwise) into the blockchain space.
+
+At Truffle, we’re also pushing harder than ever to make the DX as sweet as possible. Like, raspberry truffle sweet. This includes new features and enhancements to the existing suite (such as integration with [Hyperledger Fabric's chaincode EVM](https://github.com/trufflesuite/truffle/releases/tag/v5.0.27)), as well as the upcoming [Truffle DB](/blog/introducing-truffle-db-part-1) and [Truffle Teams](/docs/teams/overview).
+
+## #2 Managed Blockchain Services are here
+
+Managed Blockchain Services (MBS) are evolving rapidly. In the first half of 2019 alone we’ve seen the launch of new services from heavyweights such as [Microsoft](https://azure.microsoft.com/en-us/services/blockchain-service/) and [Amazon](https://aws.amazon.com/managed-blockchain/), and players such as [Kaleido](https://kaleido.io/) evolving their stack with dizzying speed.
+
+These services, of course, do all the heavy lifting when it comes to spinning up private or consortium networks, something that was historically cumbersome from a DevOps perspective. Excitingly, the maturation of these services is coinciding with an increased understanding of the use-cases for permissioned ledgers and accordingly, we’re seeing major projects and initiatives begin to roll out.
+
+The managed nature of these services has allowed the teams behind them to really focus on streamlining the developer experience Which leads us to the next trend...
+
+## #3 We’re seeing glimpses of the DX of the future
+
+In the words of William Gibson: *“The future is already here - it's just not very evenly distributed”* and with the blockchain DX it’s no different.
+
+Our favorite example of a DX from the future is [Kaleido’s Marketplace](https://marketplace.kaleido.io/) where within a few clicks you can add a [token swap service](https://marketplace.kaleido.io/service/token-swap), store data on [IPFS](https://marketplace.kaleido.io/service/ipfs-file-store), or [pin a state proof](https://marketplace.kaleido.io/service/public-ethereum-tether/) to a public network.
+
+![Example A](/img/blog/5-trends-impacting-the-blockchain-developer-experience/example-1a.png)
+
+It’s almost too easy. Seriously though, this evolution of developer experiences paves the way for how “delightful” things might one-day be when building equivalent services for public networks.
+
+## #4 Major corporations are pushing some seriously awesome open-source software
+
+While veteran projects like [OpenZeppelin](https://openzeppelin.org/) continue to blossom, one interesting trend we’ve seen is larger organizations’ increasing embrace of open-source with the recent release of some exciting new projects.
+
+Some great examples of this include Ernst & Young’s [Nightfall](https://github.com/EYBlockchain/nightfall), Samsung’s [Blockchain SDK](https://developer.samsung.com/blockchain), Microsoft’s [Confidential Consortium Framework](https://github.com/microsoft/CCF), and the continued evolution of the JPMorgan-backed [Quorum](https://github.com/jpmorganchase/quorum). We’re equally pumped by the launch of Cloudflare’s [Ethereum gateway](https://blog.cloudflare.com/cloudflare-ethereum-gateway/) too!
+
+It’s exciting to see companies of all shapes and sizes embracing the paradigm in ways that we can all benefit.
+
+## #5 Industries are becoming increasingly programmable, led by DeFi
+
+While companies like [Stripe](https://stripe.com/) have turned programming against “centralized” finance into an art form, they are inherently bound by the rules and regulations imposed by the industry itself. Decentralized Finance (or DeFi) on the other hand has no such intrinsic limitations. Want to open a Collateralized Debt Position? MakerDAO has a [JavaScript library](https://makerdao.com/documentation/#dai-js) for that. DeFi is only limited by the imagination (and programming ability) of individual developers.
+
+We’re rapidly seeing the decentralized equivalent of swaths of traditional financial services emerge, all of which are open and programmable in ways that the existing industry can only dream of.
+
+And of course it goes far beyond finance. Everything from supply chains to in-game assets are steadily turning Ethereum into the “[global platform for every asset](https://twitter.com/MuteDialog/status/1149047398532075526)”.
+
+**It’s never been a better time to building on Ethereum. From tooling to infrastructure to a world-class open-source ecosystem, the developer-experience continues to blossom.**
diff --git a/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md b/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
new file mode 100644
index 000000000..d70676f22
--- /dev/null
+++ b/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
@@ -0,0 +1,50 @@
+---
+title: A Sweet Upgradeable Contract Experience with OpenZeppelin and Truffle
+hide:
+  - navigation
+---
+
+![Truffle + OpenZeppelin Banner](/img/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/blog-header.png)
+
+Immutability is a cornerstone of blockchain technology. This is great for many reasons, but presents a problem when it’s time to upgrade our smart contracts. There are a few different upgrade patterns, but one that’s proven to be robust is the proxy pattern. This pattern has, until now, involved some additional overhead for development teams. Thanks to OpenZeppelin though, you can now deploy upgradeable contract systems with ease using the familiar Truffle tool suite!
+
+## The Proxy Pattern
+
+At a high level, the proxy upgrade pattern involves deploying a proxy contract that delegates function calls to your logic and storage contracts. The proxy is storing addresses of the logic contracts and these addresses can be changed. This allows you to deploy a new version of the logic contract and point the proxy to that new version.
+
+<figure>
+  <img class="mb-4 w-100" src="/img/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/proxy-contract.png" alt="Proxy contract upgrade diagram">
+  <figcaption class="text-center font-italic">The proxy contract can point to any number of different logic contracts.</figcaption>
+</figure>
+
+There are many concerns around this pattern you’ll need to keep in mind, such as making sure your old contracts cannot be used maliciously. For more information on proxy patterns, [check out OpenZeppelin’s proxy pattern guide](https://docs.openzeppelin.com/upgrades/2.8/proxies).
+
+## Using the Plugin
+
+First, install the package:
+
+```bash
+npm install --save-dev @openzeppelin/truffle-upgrades
+```
+
+<p class="alert alert-info m-t-2">
+<i class="fas fa-info-circle"></i> <strong>Note</strong>: This package requires Truffle version 5.1.35 or greater.
+</p>
+
+Then, in your migration script, use the new deployProxy and upgradeProxy functions:
+
+```javascript
+const { deployProxy, upgradeProxy } = require('@openzeppelin/truffle-upgrades');
+
+const Box = artifacts.require('Box');
+const BoxV2 = artifacts.require('BoxV2');
+
+module.exports = async function (deployer) {
+  const instance = await deployProxy(Box, [42], { deployer });
+  const upgraded = await upgradeProxy(instance.address, BoxV2, { deployer });
+}
+```
+
+Now your contract systems can be much more flexible while still leveraging all of the benefits of a blockchain network. For more information on the truffle-upgrades plugin, check out [OpenZeppelin’s Truffle documentation](https://github.com/OpenZeppelin/openzeppelin-upgrades/blob/master/packages/plugin-truffle/README.md).
+
+We’re very excited about this plugin and would love to hear more about how you’re using it and how we can make the experience even better! Please let us know how you feel in [the Truffler Slack community](https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA) or on [OpenZeppelin’s forum](https://forum.openzeppelin.com/)!
\ No newline at end of file
diff --git a/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md b/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
new file mode 100644
index 000000000..3bcd89b70
--- /dev/null
+++ b/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
@@ -0,0 +1,179 @@
+---
+title: An Easier Way to Deploy Your Smart Contracts
+hide:
+  - navigation
+---
+
+**TL;DR** - Deploying your smart contracts shouldn't be difficult, and the process should be flexible. I give a sneak peek at the next feature we're building: an **easy to use interface to deploy your Truffle projects with [Truffle Teams](/docs/teams/overview)**! It's going to be awesome, and **you can be the first to use it**! I'll be giving a **hands-on workshop from 9AM-12PM on Friday, August 2nd, at [TruffleCon 2019](/trufflecon2019)** that will walk you through through the entire Truffle Teams lifecycle, including the **never-before-used Deployments interface**! See you there!
+
+---
+
+So! You've finished implementing your dApp, you've tested it on [Ganache](/ganache), and you're ready to push it to a testnet or Mainnet! Congratula—oh wait.
+
+![One Does Not Simply Deploy to Mainnet](/img/blog/an-easier-way-to-deploy-your-smart-contracts/got-deploy-mainnet.jpg)
+
+It's not that easy.
+
+There are a handful of solutions, and none have _really_ made it painlessly easy. Even our own `truffle migrate` (aka `truffle deploy`) has left much to be desired.
+
+Well it's about to get a whole lot easier with Truffle Teams. [Skip to the good stuff.](#truffle-teams)
+
+## The Not-So-Easy Ways to Deploy Your Smart Contracts
+
+So what's wrong with what's already made? Why make _yet another_ tool? I hear you. Let's take a look at what **is** available, and if you're still meh, I'd love to talk to you at [TruffleCon](/trufflecon2019)!
+
+<h3 class="link-markdown">
+  <a href="#remix" name="remix">
+    <i class="fas fa-link">
+    </i>
+  </a>
+  <div>
+    <span>Remix</span>
+    <img style="margin: 0 !important; display: inline-block !important;" src="/img/blog/an-easier-way-to-deploy-your-smart-contracts/remix-logo.svg"  width="40px" title="Remix" alt="Remix">
+  </div>
+</h3>
+
+![Remix IDE](/img/blog/an-easier-way-to-deploy-your-smart-contracts/remix.png)
+
+Oh [Remix](https://remix.ethereum.org), we all have fond memories of you. And many people still use Remix for all sorts of use cases! Remix gives you an in-browser Ethereum IDE, letting you develop, compile, test, debug, and deploy smart contracts for Ethereum. And it's probably the least amount of work needed to throw a single smart contract onto a testnet or Mainnet (i.e. when deploying a single `.sol` file).
+
+Remix, as of version `0.7.7`, gives you a simple `Deploy` button. This will send a transaction to the `web3` provider of your choice (many use [MetaMask](https://metamask.io)), and you're off to the races!
+
+Great, right?
+
+Well, Remix gets harder to use as you add more contracts, import 3rd party contracts, work as a whole team, etc. It's definitely flexible and able to handle these use cases (though not without legwork and configuration), but it's not my personal preference for developing large, complex dApps.
+
+<h3 class="link-markdown">
+  <a href="#truffle-cli" name="truffle-cli">
+    <i class="fas fa-link">
+    </i>
+  </a>
+  <div>
+    <span>Truffle CLI</span>
+    <img style="margin: 0 !important; display: inline-block !important;" src="/img/truffle-logo-light.svg"  width="50px" title="Truffle" alt="Truffle">
+  </div>
+</h3>
+
+Enter [Truffle](/truffle).
+
+It's a fantastic framework (not to toot our own horns) that lets you develop your dApp in a flexible and extensible way. It provides structure to keep you sane in this chaotic world of Web 3.0.
+
+It even gives you a mechanism to define what deploying (aka: "migrating") means for your application. You can specify what contracts get deployed in which order with whatever arguments you require. For instance, your smart contracts may depend on the deployment of a past contract, which you can easily code in migration scripts.
+
+**And it's as easy as running `truffle migrate`!**
+
+...and if you were deploying directly to [Ganache](/ganache), that'd be entirely true.
+
+![Running `truffle migrate`](/img/blog/an-easier-way-to-deploy-your-smart-contracts/truffle.png)
+
+But that's not the case when we start talking about testnets or Mainnet.
+
+The **easiest** way to deploy to an external network is by using [Truffle's HD Wallet Provider](/docs/truffle/reference/configuration#providers). However, this requires you to somehow get your mnemonic or private key into the `truffle-config.js` config file, **without committing it to your provider source control provider (PLEASE don't do this - you'll get your Ether stolen).** To use an account you created with MetaMask, you'd need to export your private key from MetaMask (or your mnemonic, if you're feeling lucky 😱) and create the boilerplate code to read in the key from an environment variable (to prevent committing it to your repository and sharing it publicly).
+
+In all truthfulness, this isn't too bad, but it's also a bit too much config for me. I'd much rather use MetaMask directly to authenticate transactions during deployments.
+
+### Custom Management Web Interface
+
+Some devs will create a small front-end web interface which uses [web3.js](https://github.com/ethereum/web3.js) to deploy their smart contracts. I have done this personally in my [Game of Thrones Death Pool](https://seesemichaelj.github.io/game-of-thrones-death-pool) project, and I chalked it up to "well I can put this on a website and others can deploy their own versions."
+
+![Custom Management Web Interface for GoT Death Pool](/img/blog/an-easier-way-to-deploy-your-smart-contracts/got-death-pool.png)
+
+Sometimes this is necessary, but it's more work if it's not absolutely needed for your application.
+
+## My Version of an Ideal Deployment Interface
+
+In an ideal world, I'd like these features in a deployment interface:
+
+<ul>
+  <li>Lets me use MetaMask directly for signing transactions
+    <ul>
+      <li style="margin-bottom: 0 !important;">Remix ✔️ | Truffle CLI ❌ | Custom Webapp ✔️</li>
+      <li>A bonus win here is support for Ledger and Trezor wallets!</li>
+    </ul>
+  </li>
+  <li>I can use a framework/toolset/etc. that lets me build complex apps and supports complex deployment processes
+    <ul>
+      <li>Remix ❌ | Truffle CLI ✔️ | Custom Webapp ✔️</li>
+    </ul>
+  </li>
+  <li>I don't need to do a lot of work to go from finishing development to deploying
+    <ul>
+      <li>Remix ✔️ | Truffle CLI ✔️ | Custom Webapp ❌</li>
+    </ul>
+  </li>
+</ul>
+
+<h3 class="link-markdown">
+  <a href="#truffle-teams" name="truffle-teams">
+    <i class="fas fa-link">
+    </i>
+  </a>
+  <div>
+    <span>Introducing: Truffle Teams Deployments</span>
+    <img style="margin: 0 !important; display: inline-block !important;" src="/img/tt-logomark.svg"  width="50px" title="Truffle Teams" alt="Truffle Teams">
+  </div>
+</h3>
+
+If you haven't heard about our latest tool, [Truffle Teams](/docs/teams/overview), you really should check it out. Truffle Teams gives you zero-config Continuous Integration (CI) for your Truffle projects, and it also lets you monitor what's happening with your deployed contracts. Truffle Teams meshes the full Truffle Suite into a cohesive application that enables better collaboration within development teams (even teams of 1!).
+
+![Truffle Teams Builds](/img/blog/an-easier-way-to-deploy-your-smart-contracts/teams-build.png)
+
+The next big feature we're working on is Deployments. We already compile your contracts from your Truffle project for you when you make a commit to GitHub; why can't we migrate/deploy them as well? Further, Truffle Teams is a web application, allowing for easy integration with [MetaMask](https://metamask.io).
+
+We're looking at this from a [DevOps](https://en.wikipedia.org/wiki/DevOps) perspective, and we're trying to create an extensible system that will support projects and teams of **any size**.
+
+### Connect Your GitHub Repository to Truffle Teams
+
+To get started with Truffle Teams, you must first connect your GitHub repository. This is a simple step, and we have instructions on how to do this [here](/docs/teams/quickstart).
+
+### Setup Your Migrations Scripts
+
+If you haven't built a Truffle project, you should really give it a try; the [Pet Shop Tutorial](/tutorial) is a great place to start as it gives a good survey of the different facets of Truffle, including the `migration` scripts. These scripts let you define the behavior of deploying your smart contracts using a language you're already familiar with. In the tutorial, you deploy a single contract, but it has the flexibility to do so much more (i.e. you can deploy one contract, get its address, and use that in the constructor when deploying another contract).
+
+Setting up these scripts is part of the development lifecycle of creating a Truffle project, so I won't cover that here. But that's great! You should already be done with this step!!
+
+### Commit to GitHub
+
+Welp. That was easy. 😅
+
+### Monitor the Status of Your Build
+
+Head over to https://my.truffleteams.com and click on the `BUILDS` tab if you're not there already. You can see a build has been queued or has started to process. You can click on the repository name in the card to see more details. You can also get to this page by clicking on the yellow dot in GitHub next to your commit and pressing `Details`.
+
+![Teams Builds More Details](/img/docs/teams/starting-builds-comp.png)
+
+### All Your Tests Pass, Let's Deploy! (but only to a testnet just to be sure)
+
+> NOTE: This is just a sneak peek of features to come! You won't be able to follow along (yet, but [stay tuned](https://share.hsforms.com/1OaTglVhGTdWk7spR6nE_AA34pbp)!).
+
+Great! Your builds are passing, and you're ready to deploy to a testnet (i.e. Ropsten) to see if everything works.
+
+Now head over to the `DEPLOYMENTS` tab and select your repository.
+
+You'll now see a screen that shows a list of builds for your commits on the left.
+
+![Deployments Empty](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployments-empty.png)
+
+Deploying a build is as simple as hovering over the commit, pressing a button, and selecting which network you'd like to deploy to.
+
+![Deployment Wizard Select](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployment-wizard-select.png)
+
+Truffle Teams will then start the migration/deployment process. Each transaction is sent to the web application and MetaMask will prompt you to confirm transactions. By leveraging MetaMask, we can give you **[Ledger](https://www.ledger.com) and [Trezor](https://trezor.io) hardware wallet support too! 🔒**
+
+![MetaMask Transaction](/img/blog/an-easier-way-to-deploy-your-smart-contracts/metamask-tx.png)
+
+### Happy With a Released Version? Promote it to Production (aka deploy to Mainnet)
+
+But we're not done yet! You've finished your testing on Ropsten, and you're now ready to deploy to Mainnet. With the upcoming version of Teams, you can select that deployment and promote it to production (aka Mainnet) with just a couple of clicks.
+
+![Deployments Complete](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployments-complete.png)
+
+## And that's it! Pretty easy if you ask me.
+
+![Fry, Easy or Too Easy](/img/blog/an-easier-way-to-deploy-your-smart-contracts/fry-easy.jpg)
+
+## 🎉 Don't Believe Me? Be The First to Try it at My TruffleCon 2019 Workshop! 🎉
+
+I really hope you're going to TruffleCon; it's going to be awesome. Even more so because you can **be the first to try Truffle Teams Deployments in my workshop!** In my `Push It! Push It Real Good: Truffle Teams Intro & Deployments` (9AM-12PM on Friday, Aug, 2nd) workshop, we'll cover this entire lifecycle: hooking up your repository, getting your first build to pass, deploying to Ropsten, and finally monitoring transactions made against your contracts (we didn't talk about this here; check out the [docs](/docs/teams/deployments/contract-monitoring) for more details on contract monitoring).
+
+Hopefully there will be time for me to answer any questions you have, and maybe even help get your own Truffle project hooked up with Truffle Teams! If not, I will be available during the office hours at 5PM on Friday! I'm also always happy to chat anytime throughout the conference!
diff --git a/src/blog/announcing-collaboration-with-filecoin/index.md b/src/blog/announcing-collaboration-with-filecoin/index.md
new file mode 100644
index 000000000..a4ad9a98e
--- /dev/null
+++ b/src/blog/announcing-collaboration-with-filecoin/index.md
@@ -0,0 +1,69 @@
+---
+title: Announcing Collaboration with Filecoin - Big Integrations Coming
+hide:
+  - navigation
+---
+
+![Filecoin Collab Banner](/img/blog/announcing-collaboration-with-filecoin/blog-header.png)
+
+Today we're announcing an exciting new collaboration, aimed at helping developers across the globe create and deploy fully decentralized applications. We've teamed up with Filecoin to add support for the Filecoin network into our world class suite of tools. In typical Truffle fashion, we'll beef up the Truffle command line tool to give you everything you need to deploy directly to Filecoin; and then we'll add new features to Ganache so that you can easily simulate the Filecoin network during development and testing.
+
+### The Decentralized Ideal
+
+Since Truffle's inception, we've long wanted to integrate with decentralized storage networks so we can help developers build fully decentralized applications. For the most part, this has been a waiting game: Decentralized storage networks have been in heavy development, and it's clear these technologies needed time to mature. With Filecoin's month-long hackathon starting [this week](https://hackfs.com/), and the launch of their main network ("mainnet") coming later this summer, we thought now was the right time to give developers access to this amazing new technology.
+
+We're excited about Filecoin because it allows developers to build applications with 100% uptime. For instance, if an application uses only fully-dentralized technologies like Etheruem and Filecoin, the built-in incentivizations of those technologies will ensure miners around the world will keep that application running. With anti-censorship properties, as well as support for large amounts of data, Filecoin support could bring in a new age of Web3. 
+
+There's a lot we have to do before we reach this ideal, but I'd love to tell you about our roadmap for the next six months. 
+
+### Truffle Preserve: Save Your App Data (available today!)
+
+![Truffle Preserve](/img/blog/announcing-collaboration-with-filecoin/truffle-preserve.gif)
+
+In thinking about our support for Filecoin, the idea of *preservation* came quickly to mind. We envisioned that preserving application data like Javascript frontends and static assets would be a normal part of the deployment process. So we ran with that idea and added a new command to the Truffle command line tool: `truffle preserve`.
+
+Like preserving fruit, Truffle follows a "recipe" to preserve your files. In the gif above, Truffle is using the `filecoin` recipe, which will ship standard with our new version of Truffle. 
+
+**You can use `truffle preserve` today!** You'll need to download a special release we created so you can start testing, shown below. Note that our Filecoin integration is very alpha, but we wanted to support all the amazing devs hacking on Filecoin this month during [HackFS](https://hackfs.com/). 
+
+```
+$ npm install -g truffle@preserves
+```
+
+To use `truffle preserve`, simply specify the files you want to preserve on the command line, and choose between the `--filecoin` or `--ipfs` recipes. The `filecoin` recipe uses the `ipfs` recipe under the hood. You can choose only the `ipfs` recipe if you have a different set up!  
+
+```javascript
+// Preserve to Filecoin:
+$ truffle preserve ./path/to/directory --filecoin
+
+// Preserve to IPFS only:
+$ truffle preserve ./path/to/directory --ipfs 
+```
+
+By default, `truffle preserve` comes configured to work with the [Powergate localnet](https://docs.textile.io/powergate/localnet/), though you can change the IPFS and Filecoin connection information by adding the following to your `truffle-config.js` file: 
+
+```javascript 
+  // ...,
+  environments: {
+    development: {
+      "ipfs": {
+        address: "http://localhost:5001"
+      },
+      "filecoin": {
+        address: "ws://localhost:7777"
+      }
+    }
+  },
+```
+
+Note that this configuration adds a new top-level `environments` object. We'll be using this new configuration object as we upgrade to Truffle 6 in the future.
+
+### Filecoin-flavored Ganache: Simulate Filecoin (Summer/Fall/Winter)
+
+Ganache was built as the sister application to Truffle, to speed up development and testing Ethereum applications. Now that we've added support to Truffle, it's only natural we provide the same highly-modular simulator for Filecoin. Over this summer and into Fall, we plan to create a Filecoin simulation library, as part of [`ganache-core`](https://github.com/trufflesuite/ganache-core). Then later on this Fall/Winter, we'll follow that up with support in our graphical version of Ganache, below! 
+
+![Filecoin-flavored Ganache](/img/blog/announcing-collaboration-with-filecoin/filecoin-flavored-ganache.png)
+
+### Get involved / Reach out!
+
+We're extremely excited to be working with the Filecoin team and adding support for Filecoin into Truffle's tooling. If you have questions about our Filecoin integration or our plan for the future, <a href="https://trfl.co/become-a-truffler" target="_blank">join our slack community</a> and get your questions answered. Whether you're a new dev or a [HackFS hacker](https://hackfs.com/), we're happy to help. 
diff --git a/src/blog/announcing-full-portable-solidity-debugger/index.md b/src/blog/announcing-full-portable-solidity-debugger/index.md
new file mode 100644
index 000000000..5ed2f032b
--- /dev/null
+++ b/src/blog/announcing-full-portable-solidity-debugger/index.md
@@ -0,0 +1,82 @@
+---
+title: Announcing our Fully Featured, Portable Solidity Debugger
+hide:
+  - navigation
+---
+
+Every one at Truffle is giddy right now. 
+
+----------------
+
+Since Truffle's inception, it's been our mission to build outstanding development tools for the Ethereum community. The analogy we always used was one of history: Ethereum development practices are years behind the rest of the industry, and it's our job to build tools that modernize our craft. Well today, Truffle's come one step closer to that goal. We're happy to announce the release of our fully featured, fully portable Solidity [debugger](https://github.com/trufflesuite/truffle/releases) and [debugging libraries](https://github.com/trufflesuite/truffle/tree/master/packages/debugger).
+
+![Debugger in Action](https://i.imgur.com/7y80aF3.gif)
+
+### What We've Built
+
+If you've followed Truffle development, you're familiar with the `truffle debug` command. This was the first incarnation of a "debugger" built into Truffle, though it wasn't much more than a code tracer. Our new debugger comes with everything you expect :
+
+* Code stepping (over, into, out, next, instruction, etc.)
+* Current code location, including the address of the running contract
+* Breakpoints
+* Watch expressions
+* Variable inspection (stack, memory _and_ storage)
+* Custom expression evaluation using Solidity variables
+
+On top of that, our new debugger is fully portable, built to integrate with any Javascript project or editor, like Visual Studio Code. Lastly, we built it to work with **any Ethereum client**, so you could debug transactions against the main Ethereum network if you so desired. 
+
+### How it Works
+
+To debug your Solidity code, you first need to make a transaction. Ethereum is a world computer with a history of all execution, so we can pull all the information we need from past transactions. After obtaining the transaction hash, simply run the following to kick off your debugging experience:
+
+```shell
+$ truffle debug <tx hash>
+```
+
+This will open up the debugging console which you can use to your heart's content! 
+
+![Debugger user interface](https://i.imgur.com/0NUTSlM.png)
+
+The above user interface gives you access to the debugger features you need to step through your contracts' code, set breakpoints, evaluate expressions and inspect Solidity variables, providing you a better sense of what your code is doing. Under the hood, our debugger is interacting with your Ethereum client to gather all the data necessary to provide this information to you in a suitable manner. For developers reading this, the debugging library stores all this data in Redux, making the data easy to manage and making the library super portable. 
+
+Most of the work done by the debugger results in some type of mapping. The debugger gathers tons of disparate data, like the bytecode of your contracts, abstract representations of your code, instructions run during your transaction, etc., and combines them to produce information useful to the contract developer. Perhaps the debugger's most valuable property is variable inspection: Using all the data gathered, the debugger can determine which variables exist within your contract, which apply to each section of the code, and what their values are at any point in time. It can even show the values of complex data types, like structs with nested arrays. We're still filling out a few data types, but expect those in the next couple weeks.
+
+If you plan on using the `debug` command _today_, we recommend using [Using Truffle Develop and the Console](/docs/truffle/getting-started/using-truffle-develop-and-the-console). Truffle Develop comes with everything you need "baked in" to fully debug your contracts. Ganache and `ganache-cli` will need to be updated, so stay tuned for that in the coming days. 
+
+### Where to Next
+
+The debugger we built unlocks tons of value for all Ethereum developers both new and advanced, but what you're seeing here is the tip of the iceberg of where this technology will go. The interface above is just **one** interface, meant to show off the debugger's capability. As mentioned, the libraries we built are super portable, so they'll end up making their way into all of the following:
+
+* Integrated Development Environments (IDEs) like Visual Studio Code
+* [Ganache](/ganache), including a full debugging UI
+* [Drizzle](/docs/drizzle/quickstart), for automatic variable change detection after a transaction
+* Browser plugins so you can debug transactions on the fly within your application
+* Ethereum provider libraries that let you debug your code anywhere, without a plugin
+
+We encourage the Ethereum community to help build these tools. Our code is open source, and you can find all of it [on Github](https://github.com/trufflesuite/).
+
+### How to Get It
+
+If you already have Truffle installed, simply run the following to get you to the latest version:
+
+```shell
+$ npm uninstall -g truffle
+$ npm install -g truffle
+```
+
+If you're new to Truffle, you can try it out using:
+
+```shell
+$ npm install -g truffle
+```
+
+You may have to use `sudo` with the above commands if you're running Linux.
+
+More information about how to use Truffle can be found in [our documentation](/docs), and feel free to reach out on our [community Gitter channel](https://gitter.im/consensys/truffle), where hundreds of your fellow Trufflers congregate to answer your question.
+
+### A Quick Thank You
+
+I'd like to personally thank the whole Truffle team for this effort, and particularly [Nick D'Andrea](https://github.com/gnidan) for turning some initial research work into a fully portable, fully featured debugger. The engineering under the hood is amazing, [I urge you to take a look](https://github.com/trufflesuite/truffle/tree/master/packages/debugger). I'd also like to thank the community at large: It's a pleasure building the tools that make your lives easier, and your consistent feedback makes the whole endeavor worthwhile.
+
+Thanks,
+<br/>-- Tim 
diff --git a/src/blog/axonis-enterprise-use-of-truffle/index.md b/src/blog/axonis-enterprise-use-of-truffle/index.md
new file mode 100644
index 000000000..cca7183a6
--- /dev/null
+++ b/src/blog/axonis-enterprise-use-of-truffle/index.md
@@ -0,0 +1,90 @@
+---
+title: Axoni's Enterprise Use of Truffle
+hide:
+  - navigation
+---
+
+![Truffle + Axoni](/img/blog/axonis-enterprise-use-of-truffle/truffle-axoni.png)
+
+## Axoni Background
+
+At Axoni, our mission is to make shared information more trusted and reliable. We do this through distributed technology that we call "Ethereum-inspired", which has both a broad and a specific meaning. In the broad sense, the core technology plays a role for its users analogous to the public blockchain, presenting a powerful and extensible capacity to side-step undesired intermediaries (yes, these exist for banks too...). In a more precise technical sense, our platform borrows certain concepts from Ethereum (e.g. accounts, contracts, gas...) and, importantly, we make efforts to comply with Ethereum-world interfaces (e.g. evm bytecode, web3 JSON-rpc).
+
+Of course, an up-shot of the last is the ability to take part in all the innovation taking place in the broader Ethereum ecosystem, including client-side libraries that enable a "tastier" application development process. To this end, within the last year we have worked to leverage the Truffle suite and ecosystem to great effect. In fact, as [reported](https://www.forbes.com/sites/michaeldelcastillo/2019/04/29/consensys-spins-off-ethereum-startup-truffle-to-take-blockchain-to-big-business/#1e84a5622e21), it is fair to say that Truffle serves by and large as the main toolset for on-chain application development at Axoni.
+
+## Using Truffle at Axoni
+
+It was a delight for us to find that, given our compliance with the web3 JSON-RPC spec, truffle basically works "out-of-the-box" with no extensive customization required for many very useful stages in the application lifecycle: develop, build, test....
+
+One notable exception: we found the native `truffle migrate` functionality not extensible to our use case. In part, this is due to the fact that our smart contract applications implement something [similar to the proxy pattern](https://blog.zeppelinos.org/the-transparent-proxy-pattern/), which runs counter to the "migration" paradigm. On the other hand, and for reasons beyond the scope of this post, tools such as `zoslib` designed to handle upgradeable smart contract application deployments, generate smart contract implementations incompatible with our use case. At a high level, our smart contract framework is optimized for high-throughput and highly complex Solidity applications which enables the ability to make automatic upgrades based on semantic versioning. [ Note: I plan to speak more about our particular use cases and smart contract topologies at Trufflecon on August 3rd]
+
+In any case, especially due to the often very high levels of complexity entailed by our use cases– combined with the noted [application-level gotcha's of upgrade design patterns in solidity itself](https://blog.trailofbits.com/2018/09/05/contract-upgrade-anti-patterns/)–we are biased towards a simple and opinionated declarative format that application and production engineers can easily understand and (when needed) manipulate.
+
+This raises the question -- why use truffle for this? It seems there are at least three reasons:
+
+1. `truffle-config.js` / `truffle.js` serves as an already existing central source of shared information about various network providers relevant for a particular application developer. It only makes sense to extend this format for use in production-like environments as well.
+1. Truffle code artifacts, a battle-tested standard for smart contracts and solidity code, in particular, provide a common interface for a toolchain. By virtue of using truffle, there is no need to re-create this format. For a non-development deployment, a `contracts_build_directory` parameter is supplied, which results in a pull from a remote artifacts repository.
+1. Obviously `@truffle/contract` itself provides a nice object oriented interface for deploying and performing operations on contracts within this script, thus avoiding any reinventing the wheel within the deployment library itself.
+
+Thus, we ventured to build a package on top of truffle that manages configuration-driven smart contract deployments and upgrades.
+
+## Building a Truffle-Based Deployment Tool
+
+The first question is what the configuration file should look like? We determined the "Straw Man" to be, simply, a two-dimensional list of job types and associated contracts specified for deployment. Starting with this, we found another concept we needed to add ("custom-partition") that is specific to Axcore, relating to the way the node software provisions data across network partitions; certain contracts are provisioned differently from others. In addition to this, we found that the only other concept we needed was a parameter specifying dependencies ("deps") that linearizes to a certain order to deployment (which may be necessary, for instance, if a given storage address stores reference to another). For concision, we added limited regex support. In the end, we arrived at a yaml-based file looking very much like the below:
+
+``` yaml
+version: 0.0.1
+setup:
+    partitions:
+        - custom-partition: *
+        - custom-partition: ^public-common
+    contracts:
+        - name: MagmaRegistryFooStorage
+        - name: MagmaRegistryBarStorage
+          deps:
+            - MagmaRegistryFooStorage
+upgrade:
+    partitions:
+        - custom-partition: "*"
+    contracts:
+        - name: MagmaRegistryFoo
+        - name: MagmaRegistryBar
+```
+
+In terms of implementation, a truffle exec script reads this configuration file, and for each contract, a) deploys the contract b) performs some basic API configuration and c) installs it in the application through invoking a basic `initialization` method. The basic top-level run (truffle exec) script looks very much like the below:
+
+``` javascript
+const run = async (done) => {
+    let jobParams = args;
+
+        // Configure specific variables for a PROD-like environment:
+    if (process.env.ENV === 'PROD') {
+        jobParams = Object.assign(args, handleProd());
+    }
+
+       //hoisting injected vars to global scope:
+    global.web3 = web3;
+    global.artifacts = artifacts;
+
+        // Create instance of job based on type
+    const jobInstance = new Job(jobParams.job, jobParams);
+
+        //Run job by deploying and invoking an initialization method on each contract
+    await jobInstance.run().catch(e => done(e));
+    done();
+};
+```
+
+A command-line client can specify a given job to run, such as the "upgrade" job specified above. Given the above configuration, the below command would deploy (if necessary) and initialize "MagmaRegistryFooStorage", followed by "MagmaRegistryBarStorage" from a given artifacts repository:
+
+``` bash
+etna --job upgrade --contracts_build_directory /path/to/artifacts
+```
+
+## Future Plans and an Announcement
+
+I am pleased to announce that we plan to open-source our core Solidity smart contract library, which provides an alternative version of the Proxy pattern, along with this aforementioned deployment tool. We believe both could be useful both for private and public applications and the Axoni team is excited to see what the community builds with these tools.
+
+In the meantime, we hope the above at least provides a high-level example of an approach to building lightweight extensions within truffle, and as a simplifying approach to the smart contract deployment process, especially for Proxy Pattern topologies.
+
+The Axoni team and I look forward to discussing this topic and much more (such as [Axlang, our Scala-based Solidity-alternative](https://axoni.com/axlang/)) at Trufflecon.
diff --git a/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md b/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
new file mode 100644
index 000000000..8e9f1a8aa
--- /dev/null
+++ b/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
@@ -0,0 +1,41 @@
+---
+title: The Best Methods to Understand Blockchain Technology if You’re Not A Developer
+hide:
+  - navigation
+---
+
+As a non-technical person, it feels like it takes 1.21 gigawatts to keep up with the speed of technology - even Doc Brown himself couldn't have predicted all of the technological advancements with his flux capacitor. Not only are we trying to keep up with technologies like blockchain, machine learning, and AI, but we have an overwhelming amount of information on the web all at the click of a mouse. It's overwhelming to the point that it's difficult to even know where to begin. However, online blockchain educational materials have started to ramp up. As I write this, I'm confident I'll start seeing “ Blockchain for dummies” online course advertisements on my browser (Opt-in, of course, because I'm using Brave). Mind-blowing! Let me help you begin by slowing down in order to speed up effectively.
+
+So you're someone who's not technical that wants to learn blockchain - great! Whether you're technical or non-technical isn't necessarily contingent on understanding an emerging technology like blockchain. Rather it's how you position yourself in the marketplace where you'll start to see the fruits of your labor.
+
+## Human to human chit chatting
+
+First things first, human to human interaction is where you want to start and it's awesome! Yes, [YouTube](https://www.youtube.com/watch?v=YGC9ECnot0k) will always be there for you - or at least until your battery dies, but dialoguing with another person and in this case, someone well-versed in blockchain will lay a strong foundation to springboard yourself into understanding this industry. I hate to use the phrase “trust me,” but trust me, as someone who's not that technical and has a background in Kinesiology, I can assure you that learning from the great minds of my Truffle developers has helped me grasp the concepts of blockchain technology. I'll say, most folks that are experts in their field generally have no problem chatting with a hungry and curious mind. If anything, it's flattering when I get approached to explain blockchain to someone who desires to understand it. We're gifted with the ability to use analogies and other practical ways of explanations that can make light of things that often feel dark and hard to see. Check out this great analogy on [sharding](https://youtu.be/5bOO7P-tZ3U?t=166)!
+
+Guess what? Developers don't mind talking to non-technical people who are trying to understand a particular technology like blockchain. It's a ridiculous stereotype to think devs only like to chat with other devs. If that were the case, how could a business be run successfully? In fact, oftentimes the best explanations come from the top experts. Developers don't like jargon or complexity either. We even gave the term developer operations a cute little nickname like DevOps. Seek out the developer in the blockchain space and ask away...better yet, reach out to one of us at Truffle–we love our community!
+
+## Meet-ups
+
+Go to your local blockchain meetups. There's probably more than a few that are available for you to attend. Meetups can be two-fold, namely, one to obtain knowledge and the other for networking, which can sometimes lead to a job. I can't tell you how many times I've hired someone that I initially met at a meetup. It sure beats throwing your resume on a job board hoping that it will stick. Relationships become the most valuable asset you can have to aid in your next employment opportunity. Moreover, everyone at a meetup shares one common trait. A passion for blockchain.
+
+## Social Media
+
+Maybe you're a little shy and don't want to network (although I highly recommend it!). There's a myriad of resources available online to learn the underpinnings of blockchain technology. You can visit our [Truffle University](/university) page for more information taking our courses. If you like to learn through watching other people's conversations, [Twitter is the place to go](https://media.consensys.net/i-read-crypto-twitter-for-hours-everyday-here-are-40-accounts-that-really-matter-cfecc681379d). You can make your way over to Quora if you have specific questions about blockchain. Don't want people to know who you are, Reddit has phenomenal ELI5 (explain it like I'm 5) explanations.
+
+## Read a Book
+
+Some people enjoy a nice old fashion book. By far the best book to understand blockchain is Mastering Bitcoin and [Mastering Ethereum](https://github.com/ethereumbook/ethereumbook) by Andreas Antonopoulos.
+
+## Podcast
+
+Listening to a [Podcast](https://player.fm/podcasts/Blockchain) is great. Especially when you're on the go. It's a way to redeem your commute to work, get through a workout session, or just something to pass the time. Often times, podcast hosts will have [guest](https://povcryptopod.libsyn.com/making-eth-sweet-with-tim-coulter) in the blockchain space to give an objective perspective on what the challenges and successes are with the technology.
+
+<h3 class="link-markdown">
+  <a href="#trufflecon" name="trufflecon">
+    <i class="fas fa-link">
+    </i>
+  </a>
+  ![TruffleCon](/img/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/trufflecon.png)
+</h3>
+
+Finally, and I may be a little bias, but if you really want to increase the pace at which you can comprehend blockchain then go to TruffleCon! Come say hi to all of us at Truffle. Come say hello to all of the speakers and blockchain company representatives. Ask us questions. Let us help you understand blockchain better. Let's network. Let's have a relationship that will enable amicability. Or better yet, let's interop with each other to leverage the power of blockchain for careers, security, and better transparency in an ever-growing technological world, one node at a time.
diff --git a/src/blog/blockchain-will-cure-cancer/index.md b/src/blog/blockchain-will-cure-cancer/index.md
new file mode 100644
index 000000000..dde1c563a
--- /dev/null
+++ b/src/blog/blockchain-will-cure-cancer/index.md
@@ -0,0 +1,47 @@
+---
+title: Blockchain Will Cure Cancer
+hide:
+  - navigation
+---
+
+<p style="width: 40%; float: left; margin-right: 1rem;">
+  <img style="margin-top: 0.3rem; margin-bottom: 0;" class="img-fluid" src="/img/blog/blockchain-will-cure-cancer/laptop.jpg" title="Laptop" alt="Laptop">
+</p>
+
+Physicians and scientists will be the actual agents behind a cure for cancer. But in their potential to disrupt the very nature of medical research and treatment, blockchain-based solutions are extremely likely to light the way. It is important when examining any new technology to consider the ways in which it may change the world. Join me here as we briefly look at how blockchain can help lead us to a world without cancer.
+
+Cancer is a significant public health issue in the United States and around the world. In the United States alone, an estimated [1.7 million new cancer cases](https://www.cancer.gov/about-cancer/understanding/statistics) were diagnosed in 2018. This number is expected to increase drastically as time goes on.
+
+Several barriers exist to finding a cure for cancer. Key among them are data challenges, difficulty quickly assessing the effectiveness of new treatments, and the financing required to fund research and treatment. Fortunately, blockchain technology is already providing avenues for addressing these barriers and bringing us closer to a cure for cancer.
+
+## It’s in the Data
+
+At its core, the path to curing cancer lies in accessing and evaluating as much data about the disease as possible. Blockchain solutions for medical data are [already being proposed and tested](https://www.healthcareitnews.com/news/blockchain-use-case-electronic-health-records). The primary benefits of using blockchain technology for storing and processing medical data lie in the portability and patient ownership of that data. On their own, these benefits are as helpful to cancer patients as they are to other medical patients.
+
+The particular usefulness of blockchain for cancer data lies in the ability of patients to volunteer their medical records to be used in research. This data will need to be anonymized and, of course, regulatory hurdles are likely to exist, but aggregating medical data from potentially millions of patients around the world will allow physicians and researchers access to unprecedented levels of information about the disease they seek to cure.
+
+[BreastWeCan.org](https://BreastWeCan.org) is one fledgling organization seeking to increase the base of data upon which further cancer research can be built. By encouraging women to upload their mammogram scans and other breast cancer images onto a blockchain, the company hopes to allow an AI to then study these images and share what it learns.
+
+## Better knowledge sharing means more effective treatments
+
+<p style="width: 40%; float: right; margin-left: 1rem;">
+  <img style="margin-top: 0.3rem; margin-bottom: 0;" class="img-fluid" src="/img/blog/blockchain-will-cure-cancer/petri.jpg" title="Petri Dish" alt="Petri Dish">
+</p>
+
+Information about cancer treatment and the results thereof is essential to finding a cure. From clinical trials to variation in responses to existing treatments among patients, information is the key. Blockchain technology can help in this respect by encouraging patients to share their treatment experiences and encouraging physicians to collaborate in their treatment attempts.
+
+One U.S. company has piloted a blockchain-based system for evaluating patient responses to cancer treatment. Encouraging patients and oncologists to provide information with an “Onco” coin, [OncoPower](https://pharmaphorum.com/news/blockchain-firm-witty-health-launches-digital-cancer-decision-tool/) will allow oncologists access to “de-identified … details like co-morbidity, specific cancer type, lines of therapy, and actual drugs used for treatment.”
+
+OncoPower’s promise lies in the ability to anonymize medical data, put it on a blockchain, and make it accessible to the medical community. This will encourage collaboration and knowledge-sharing amongst health care practitioners and researchers, increasing the visibility of various health outcomes and leading to faster iteration when it comes to experimental treatments.
+
+Another exciting treatment approach by [Hypertrust Patient Data Care](https://www.hypertrust-patient.com/) in Germany focuses on the immutable and verifiable aspects of blockchain to ensure that the supply chain for very sensitive immunotherapy treatments can be made as reliable as possible. Hypertrust tracks medication from “needle to needle” and leverages the transparency of a blockchain to improve patient outcomes.
+
+## Targeted Financing
+
+One thing that blockchain technology does incredibly well is to provide opportunities for decentralized governance and transparency. In the case of financing cancer research, blockchain could prove to be the silver bullet needed to ensure that funding goes where it will be most useful.
+
+While it does not appear that cancer fundraising has made its way onto a blockchain just yet, the ability of donors to contribute to cancer research in a tangible and trackable way is likely to increase donations and empower engagement within the scientific community. Putting cancer funding on a blockchain and encouraging the scientific community to engage in that blockchain’s governance could provide a catalyst for encouraging efficient, transparent, and collaborative research efforts.
+
+## Looking Ahead
+
+Blockchain technology is still in early stages, and it may be too soon to know precisely in which ways it may change our world. Developments in the medical applications of blockchain technology are very encouraging. Cancer has evaded a cure for many years, and the advent of new ways for scientists and physicians to learn, collaborate, and experiment may be just what the medical community needs.
diff --git a/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md b/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
new file mode 100644
index 000000000..fd9201f0e
--- /dev/null
+++ b/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
@@ -0,0 +1,31 @@
+---
+title: Branching Out - Announcing Tezos Support in Truffle
+hide:
+  - navigation
+---
+
+![Announcing Truffle Integration](/img/blog/branching-out-announcing-tezos-support-in-truffle/chameleon-t3-truffle-blog-header.png)
+
+If you've been following Truffle's development, you'll notice that our tools already support a handful of exciting platforms: [Ethereum](https://ethereum.org/), [Quorum](https://www.goquorum.com/), [Axoni](https://axoni.com/technology/), Hyperledger [Fabric-EVM](https://github.com/hyperledger/fabric-chaincode-evm), Hyperledger [Sawtooth](https://www.hyperledger.org/projects/sawtooth), and Hyperledger [Burrow](https://www.hyperledger.org/projects/hyperledger-burrow). What's common amongst these chains is that they all use the Ethereum Virtual Machine under the hood. Ethereum is very near and dear to our hearts -- it's where we got our start, and where we are the most competent. But we're branching out, in large part due to market demand. In December we released a beta [Corda-flavored Ganache](/blog/unwrap-the-corda-flavored-ganache-beta) as part of our initial support for the [Corda platform](https://www.r3.com/corda-platform/). And today, we branch out even further.
+
+**I'm excited to announce Tezos integration into the Truffle command line tool.**
+
+Right now, at this very moment, you can [download a Tezos-specific version of Truffle](/docs/tezos/truffle/quickstart) and start building smart contracts on Tezos networks using the time-tested tooling you know and love. And if you're a Tezos native who got your start building on top of the Tezos platform, then this means professional-grade tooling has finally arrived.
+
+We chose Tezos as our first non-EVM chain because of its blossoming developer community. In our position as tool builders, we go where the market takes us: If enough people ask for Tezos support, we listen. This market demand was coupled with an active and interested group of core developers, and a blockchain architecture that's similar to Ethereum. Ultimately, Tezos is "EVM-like". This makes it a great candidate for integration, fitting into Truffle like a glove.
+
+Are you a developer who wants to build on top of Tezos using Truffle? [Check out our documentation](/docs/tezos/truffle/quickstart) and our [quick start guide](/docs/tezos/truffle/quickstart).
+
+It's important to note that our integration with Tezos is experimental. As of now you'll need to download a special version of Truffle to start building on Tezos. This is by design: Integrating a new blockchain into a common workflow takes some work, and we want to ensure we keep the same level of quality for our existing chains while we work out the kinks. You can be extremely helpful here! If you run into an issue using the Tezos version of Truffle, let us know! You can file an issue at our [issue tracker](https://github.com/trufflesuite/truffle/issues), or reach out to us on [Spectrum](https://spectrum.chat/trufflesuite).
+
+Our plan over the coming months is to harden our Tezos integration and ultimately release it under the mainline version of Truffle. We’ve also expanded our commitment to the Tezos project by finalizing plans for further integrations: 1) a Tezos-flavored [Ganache](/ganache); and 2) full support for the [SmartPy](https://smartpy.io/) programming language.
+
+Though this is our first foray into supporting non-EVM blockchains, I'd like to take this moment to reaffirm our support and interest in Ethereum and Ethereum-based blockchains. You'll see many more announcements in 2020 about how we're planning to make development on both Ethereum 1.0 and Ethereum 2.0 better. Stay tuned.
+
+I'd like to thank some standout developers in the Tezos community for making this integration a reality. First, are the developers from [Stove Labs](https://stove-labs.com/), Matej Šima & Istvan Deak. They helped significantly in stress testing our integration and providing continuous feedback during development. I'd also like to thank [Taquito](https://tezostaquito.io/) developers Jev Björsell and Simon B.Robert for creating an easy to use library for communicating with and interacting with the Tezos blockchain (for Ethereum developers, this is the Web3.js equivalent). Last but not least, a big shout out to the developers of the [LIGO](https://ligolang.org/) programming language, Gabriel Alfour and the rest of the LIGO development team, for making LIGO compiler integration easy on us. Cheers to you!
+
+We're excited to announce Tezos support as one of many integrations to come in 2020. Thank you for your continued support of our work, and the opportunity to make your development life easier. Happy coding!
+
+Tim
+
+-- Founder & CEO, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md b/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
new file mode 100644
index 000000000..cc3d131ab
--- /dev/null
+++ b/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
@@ -0,0 +1,32 @@
+---
+title: Branching Out - Phase 2 of Corda-flavored Ganache
+hide:
+  - navigation
+---
+
+![Branching out to Corda-flavored Ganache](/img/blog/branching-out-phase-2-of-corda-flavored-ganache/chameleon-corda-truffle-blog-header.png)
+
+April has been a big month for Truffle Suite! Earlier this month we branched out and announced Tezos integration into the Truffle command line tool. If you remember, back in December we released a beta [Corda-flavored Ganache](/blog/unwrap-the-corda-flavored-ganache-beta) as part of our initial support for the Corda platform. Today, we are excited to share [Phase 2 of Corda-flavored Ganache, v2.4.0](https://github.com/trufflesuite/ganache/releases) with you! Phase 2 includes more robust features for Corda including Corda CRaSH Shell, network map visualization, and a version picker.
+
+We're thrilled to release Phase 2 of Ganache for Corda, an open source blockchain platform built for business applications, as this continues to lower the barrier to entry for Corda developers. These updates enable developers to easily set up a local network on their machines, letting them inspect the state of that network across various nodes and giving them visibility into transactions normally hidden by a live Corda network's privacy protections.
+
+Features Include:
+
+* One-click Corda network configuration and initialization, so you can focus on what matters most: your application.
+* Multiple workspaces for all of your Corda projects including a Corda network map, notaries, nodes, transactions, accounts, and ledgers.
+* Simple testing for interoperability with the Version Picker node.
+* Easy access to all your application's data, including network map, notaries, nodes, transactions, and states.
+* Visualizations of node connections with the Corda network map graph
+* Embedded Corda CRaSH Shell to provide control over your nodes and project data
+
+As always, this release is compatible with the latest versions of Windows ⊞, Mac OS 🍎, and Linux 🐧. You can now run and interact with a Corda network without installing prerequisites like Java, PostgreSQL, Corda binaries, docker, etc!
+
+If you are a Corda developer who wants to use Ganache with your CorDapp [check out our documentation and our quick start guide](/docs/ganache/corda/working-with-corda). We are also hosting a [joint webinar with R3](https://www.crowdcast.io/e/corda-ganache) on May 6th to demonstrate these features along with how this fits into existing Corda developer’s’ workflow.
+
+In closing, I’d like to thank our partners at R3, Todd McDonald, Lisa Chiong, Tiffany Sarmiento, Chris Chabot, and Nick Rogers for their collaboration, vision, and teamwork. I’d also like to thank [David Murdoch and Nick Paterno](/staff) from the Truffle team for their tireless efforts to make Corda Flavored Ganache a reality.
+
+Thank you for your continued support and the opportunity to make your development life easier. Happy coding!
+
+Tim
+
+-- Founder & CEO, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md b/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
new file mode 100644
index 000000000..dc158cce0
--- /dev/null
+++ b/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
@@ -0,0 +1,39 @@
+---
+title: Bring Your Own CI (BYOCI) with Truffle Teams
+hide:
+  - navigation
+---
+
+Truffle Teams has always offered an internal continuous integration (CI) service. This service is great for getting up and running quickly since it requires no configuration to run your Truffle tests.
+
+We also want to support teams who have established CI setups outside of Truffle Teams. Thanks to the fantastic work by [Erin Shaben](https://github.com/eshaben), **you can now leverage your existing GitHub-integrated build services**!
+
+## Using an Existing CI Service
+
+<figure>
+  <img class="mb-4 figure-shadow" src="/img/blog/bring-your-own-ci-byoci-with-truffle-teams/figure-1.png" alt="Builds settings screen" style="width:100%">
+  <figcaption class="text-center font-italic">The BUILDS settings screen</figcaption>
+</figure>
+
+Enabling external CI for a repository only requires a single checkbox! Navigate to your user or organization’s settings page by clicking the user/org icon in the navbar. From there, click the BUILDS tab, then check the checkbox next to the repository of your choice!
+
+<figure>
+  <img class="mb-4 figure-shadow" src="/img/blog/bring-your-own-ci-byoci-with-truffle-teams/figure-2.png" alt="Build with external CI enabled" style="width:100%">
+  <figcaption class="text-center font-italic">Build with external CI enabled</figcaption>
+</figure>
+
+Now, when you navigate to the builds page for that repository, any new builds will show a list of your GitHub-integrated build services, along with their respective statuses.
+
+For more detailed information on the external CI service, [check out our documentation here](/docs/teams/builds/external-ci).
+
+For more detailed information on adding services to GitHub via their Marketplace, [check out the GitHub Marketplace docs here](https://help.github.com/en/github/customizing-your-github-workflow/about-github-marketplace).
+
+## Future Integration
+
+We want Truffle Teams to be the most effective devops tool in the blockchain space for both new and existing teams. Let us know what you think about this integration solution, and if your team has other needs we haven’t met yet.
+
+Thanks!
+
+Josh Quintal
+
+-- Head of Product & Marketing, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md b/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
new file mode 100644
index 000000000..8fca48191
--- /dev/null
+++ b/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
@@ -0,0 +1,80 @@
+---
+title: Crytic - Continuous Assurance for Smart Contracts
+hide:
+  - navigation
+---
+
+We are proud to announce our new Smart contract security product: [https://crytic.io/](https://crytic.io/). Crytic provides continuous assurance for smart contracts. The platform reports build status on every commit and runs a suite of security analyses for immediate feedback.
+
+The beta access will be open soon. Follow us [on twitter](https://twitter.com/CryticCI) to be notified and benefit from the service as soon as possible! The first three months are free.
+
+## How Crytic will secure your smart contracts
+
+Once connected to your GitHub repository, Crytic will:
+
+* Run our static analyzer [Slither](https://github.com/crytic/slither/), which detects the most common smart contracts vulnerabilities and will save you from critical mistakes.
+* Run your Truffle tests continuously to ensure that no bug is added while developing your project.
+
+Slither will analyze your codebase for more than 60 security flaws, including reentrancy, integer overflows, race conditions, and many others. Half of these flaw-detectors are private and were not available to the public. They can detect flaws for which public knowledge is limited and that no other tool can find. The recent [GridLock bug](https://blog.trailofbits.com/2019/07/03/avoiding-smart-contract-gridlock-with-slither/) would have been detected ahead of time using Crytic!
+
+We built this platform for developers, so we integrated it with GitHub. It will watch every commit and branch to ensure that bugs are not added during development. In addition, Crytic will run the checks on every PR to facilitate your code review.
+
+For every security issue found, Crytic will:
+
+* Show you a detailed report on the bug, including source-code highlighting.
+* Allow you to create a GitHub issue to keep track of the fixes easily.
+* Let you triage the results, so you can decide what needs to be fixed.
+
+## Quick Walkthrough
+
+Adding Crytic to your system is straightforward: you just need to connect to your GitHub repository. We have first-class support for Truffle; it works out of the box! We also support most of the other smart contract platforms, including Embark, Dapp, and Etherlime. After adding your repository, the dashboard (Figure 1) will show you a summary of the project, like this [crytic-demo](https://github.com/crytic/crytic-demo):
+
+<figure>
+  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-1.png" alt="Crytic Dashboard" style="width:100%">
+  <figcaption class="text-center font-italic">Figure 1: Crytic Dashboard</figcaption>
+</figure>
+
+From now on, you will benefit from continuous security analyses.
+
+### Issue reports
+
+Finding an issue is only the first part. Crytic will provide you with detailed information you need about the bug to fix it:
+
+<figure>
+  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-2.png" alt="Crytic Report" style="width:100%">
+  <figcaption class="text-center font-italic">Figure 2: Report</figcaption>
+</figure>
+
+A careful reader will notice the vulnerability here: `function constuctor` creates a public function (with a typo!) that is callable by anyone instead of being run only at initialization. Crytic will detect these types of critical mistakes instantaneously.
+
+### Triaging issues
+
+Once a bug has been found, the user can decide to:
+
+* create a GitHub issue, to easily keep track of the fix, or
+* discard the issue.
+
+<figure>
+  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-3.png" alt="GitHub Issue Generated" style="width:100%">
+  <figcaption class="text-center font-italic">Figure 3: GitHub Issue Generated</figcaption>
+</figure>
+
+Crytic follows the modifications to your code and reports only new bugs that are introduced.  Each new PR will be analyzed automatically:
+
+<figure>
+  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-4.png" alt="Pull Request Integration" style="width:100%">
+  <figcaption class="text-center font-italic">Figure 4: Pull Request Integration</figcaption>
+</figure>
+
+## What’s next for Crytic
+
+We are constantly improving Crytic. Expect to see new bug detectors and new features in the future. We are planning to add:
+
+* [Echidna](https://github.com/crytic/echidna) and [Manticore](https://github.com/trailofbits/manticore) integration: to ensure your code is checked for custom security properties.
+* Automatic bug repair: Crytic will propose patches to fix the issues it finds.
+* [Slither printer integration](https://github.com/crytic/slither/wiki/Printer-documentation): to help visualize the underlying details of your code.
+* Delegatecall proxy [checker](https://github.com/crytic/slither/wiki/Upgradeability-Checks): to prevent you from making critical—and all too common—mistakes in your [upgradeability process](https://blog.trailofbits.com/2018/09/05/contract-upgrade-anti-patterns/).
+
+Questions? Bring them to TruffleCon, and pose them to us at our booth or at our Friday workshop [on automated vulnerability detection tools](https://trufflecon2019.sched.com/event/RFQL/how-to-build-secure-smart-contracts-a-deep-dive-into-automated-tools?iframe=no&w=100%&sidebar=yes&bg=no)!
+
+Whether or not you can make it to TruffleCon, join our [slack channel](https://empireslacking.herokuapp.com/) (#crytic) for support, and watch [@CryticCI](https://twitter.com/CryticCI) to find out as soon as our beta is open.
diff --git a/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md b/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
new file mode 100644
index 000000000..ecc2231f7
--- /dev/null
+++ b/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
@@ -0,0 +1,62 @@
+---
+title: Debug Quickly and in Context with Truffle Teams New Debugger
+hide:
+  - navigation
+---
+
+
+![Truffle Teams Debugger Banner](/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/blog-header.png)
+
+If you've used Truffle's debugger, you know it's best-in-class. Until now though, it's been confined to the command line. Today the debugger breaks out of the console to a GUI within Truffle Teams! This is a huge workflow enhancement--allowing us to debug transactions in the places we're already viewing--via the deployment details screen or while monitoring individual contracts. Let's take a look!
+
+<p class="alert alert-info">
+  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the debugger right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
+</p>
+
+## Launching the Debugger
+
+To launch the debugger, we just need to find a transaction. Head over to the Deployments screen and select a deployment. From there select the transactions tab or click the monitoring button for a contract. You'll notice there's a debug button on each transaction card; clicking it will open the Truffle Teams debugger.
+
+</div></div></div>
+
+<figure class="breakout">
+  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/teams-debugger-1.png" alt="All transaction cards now have a debug button">
+  <figcaption class="text-center font-italic">Debugging is only a click away!</figcaption>
+</figure>
+
+<div class="container container-post"><div class="row justify-content-center"><div class="col">
+
+## Navigating the UI
+
+Starting at the top, you'll see the transaction hash along with an icon noting its status and, if applicable, the accompanying error message (1). Below that we have our functions, from left to right: Step Next, Step Over, Step In, Step Out, and Reset (2). Next we have some tabs showing the contracts included in this transaction (3). Finally we have two panes, one showing our Solidity with the current step highlighted in yellow (4). The second with our variables (5).
+
+</div></div></div>
+
+<figure class="breakout">
+  <img class="mb-4 w-100 figure-shadow" src="/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/teams-debugger-2.png" alt="The debugger in action on a failed transaction">
+  <figcaption class="text-center font-italic">Debugging a failed transaction.</figcaption>
+</figure>
+
+<div class="container container-post"><div class="row justify-content-center"><div class="col">
+
+At the moment some other enhancements, including breakpoints and syntax highlighting, are coming soon. We wanted to get this powerful feature in your hands as quickly as possible, so we're releasing it now via Early Access. For more information on what to expect from early access, check out [the Truffle Teams Early Access blog post](/blog/try-new-features-first-with-truffle-teams-early-access).
+
+For more information, check out [the Truffle Teams Debugger docs](/docs/teams/debugger/debugging-a-transaction) or for general information about Truffle's debugger, check out [the Truffle Debugger docs](/docs/truffle/getting-started/debugging-your-contracts).
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE TRUFFLE TEAMS DEBUGGER</a>
+</div>
+
+## Continue the Conversation
+
+We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven't met yet.
+
+Continue the conversation with your fellow Trufflers in our Slack community!
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
+</div>
+
+Thanks!
+
+_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md b/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
new file mode 100644
index 000000000..2fdcbef08
--- /dev/null
+++ b/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
@@ -0,0 +1,122 @@
+---
+title: Debugging verified external contracts with Truffle Debugger
+hide:
+  - navigation
+---
+
+![Truffle Teams Redesign Banner](/img/blog/debugging-verified-external-contracts-with-truffle-debugger/blog-header.png)
+
+Let's say you're crafting a clever flashloan transaction that interacts with
+five different DeFi dapps -- but on trying it, it doesn't work as expected.  You
+open the transaction in Truffle Debugger to get a closer look at what went
+wrong.  But how will you debug a transaction that the debugger doesn't have the
+source code for?
+
+Well, new in Truffle release v5.1.29 is the debugger's `--fetch-external` flag!
+This new flag tells the debugger to search [Etherscan's repository of verified
+contracts](https://etherscan.io/contractsVerified) and automatically
+download and compile those sources.  As long as all the contracts you're
+interacting with are verified on Etherscan, you're good to go!
+
+This means you'll be able to debug Mainnet / Görli / Ropsten / etc. transactions
+that interact with external contracts _without the need to have external
+contract source code available locally_!
+
+Now, before you get too excited, some caveats apply:
+- This only works with Solidity contracts, since @truffle/debugger only supports
+  Solidity at this time.
+- While using this feature, you won't be able to load and unload transactions
+  in the debugger like normal; you'll have to quit and restart to change
+  transactions.
+- In order to be able to use the debugger and have it find the right source to
+  download for your network, you'll need to connect to an archive node that
+  offers the `debug_traceTransaction` JSON RPC method. (See Geth's [Management
+  APIs](https://github.com/ethereum/go-ethereum/wiki/Management-APIs)).
+
+That last one is a pretty big caveat, but **there's good news here**! Our
+sibling SaaS project, [Truffle Teams](/docs/teams/overview), now
+lets you [simulate live
+networks](/blog/sandbox-forking-with-truffle-teams)
+via the free Sandbox feature. This works without requiring you to run your own
+node or to pay for someone else to run their own node, since Truffle Teams
+offers 1 free sandbox per GitHub organization!
+
+Of course, you're free to use the debugger with whatever compatible Ethereum
+node you like, including command-line Ganache; but here's how to use Truffle
+Teams, which offers so much more, for this feature.
+
+### Example: Debug ENS in a [mostly] empty Truffle project!
+<a href="/img/blog/debugging-verified-external-contracts-with-truffle-debugger/debug-example1.png" target="_blank"><img width="100%" alt="Click to enlarge" src="/img/blog/debugging-verified-external-contracts-with-truffle-debugger/debug-example1.png">Click to enlarge</a>
+
+This screenshot shows `truffle debug` stepping through a Görli transaction to the ENS registry. Once you upgrade to Truffle v5.1.29, you can recreate this by doing the following:
+
+1. Find the [Görli ENS contract page on
+Etherscan](https://goerli.etherscan.io/address/0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e).
+
+2. Find a recent transaction hash. (See [example from
+screenshot](https://goerli.etherscan.io/tx/0x79381a69eb828558f2728900615109eb7bdeb6d216af130142341da15cc6fecd).)
+
+3. [Sign up / login to Truffle Teams](https://my.truffleteams.com/) and make a
+free Sandbox that forks off Görli. **Note**: At the moment, you'll have to make
+sure that you manually specify that the Sandbox should use the same network ID
+as the chain it's forked from (in this case, 5).  In the future, however, this
+step will be handled automatically.  You can read more about Sandboxes in [our
+earlier blog post on the
+subject](/blog/sandbox-forking-with-truffle-teams).
+
+4. Copy your sandbox JSON RPC url to the clipboard.
+
+5. Run `truffle init` and add this to your new `truffle-config.js` (replacing `"<paste RPC url>"` with your clipboard contents from step 4):
+  ```javascript
+  module.exports = {
+    /* ... rest of truffle-config.js ... */
+    networks: {
+      /* ... rest of networks ... */
+      sandbox: {
+        url: "<paste RPC url>",
+        network_id: 5
+      }
+    }
+  }
+  ```
+5a. _Optional_. If you have an [Etherscan API key](https://etherscan.io/apis) or
+feel like making one, you can specify that as well in your `truffle-config.js`
+to speed up downloads:
+  ```javascript
+  module.exports = {
+    /* ... rest of truffle-config.js ... */
+    etherscan: {
+      // replace this with your API key
+      apiKey: "0123456789abcdef0123456789abcdef"
+    }
+  }
+  ```
+
+6. Copy the transaction hash from step 2 and run the following (replacing
+`<transaction hash>` with the `0x`-prefixed transaction hash):
+  ```
+  truffle debug <transaction hash> --network sandbox --fetch-external
+  ```
+
+And that's it!  You're now debugging an ENS transaction in an empty Truffle
+project.  You can step through and set breakpoints; inspect both decoded
+variables and the raw binary state; and get return values, revert messages, and
+stacktraces just like normal.
+
+Now this example is a minimal one just to show how things work.  But it will
+work just as well in your existing projects on transactions that feature your
+contracts in your project interacting with external verified contracts deployed
+on live networks.
+
+Right now "verified contracts" just means contracts verified on Etherscan, but
+we're also looking at supporting the new
+[Sourcify](https://github.com/ethereum/sourcify) project, which provides a more
+decentralized alternative to Etherscan's repository. We plan to add this in an
+upcoming release.  But as of right now, you can use this feature with
+Etherscan's large library of verified contracts!
+
+**Update**: As of Truffle v5.1.32, [Sourcify](https://github.com/ethereum/sourcify) is now supported!  Truffle
+Debugger will now check both [Etherscan](https://etherscan.io/) and [Sourcify](https://github.com/ethereum/sourcify) for verified
+contract sources!
+
+Hope you find this as exciting as we do! Thanks for using Truffle!
diff --git a/src/blog/designing-the-ganache-logo/index.md b/src/blog/designing-the-ganache-logo/index.md
new file mode 100644
index 000000000..2e80b01bb
--- /dev/null
+++ b/src/blog/designing-the-ganache-logo/index.md
@@ -0,0 +1,70 @@
+---
+title: Designing the Ganache Logo
+hide:
+  - navigation
+---
+
+Last week we released [Ganache](/ganache), a personal blockchain for Ethereum development. Many of you commented on the design of the landing page and logo, but just how did the gooey cube come to be? Let's take a trip through the 30+ iterations that led to our newest confection.
+
+<div class="row"><div class="col-xs-10 col-xs-push-1 col-sm-6 col-sm-push-3 m-b-2">
+![Final Ganache Logomark](/img/blog/designing-the-ganache-logo/final-logomark.png)
+</div></div>
+
+Before setting out on our design journey, we started with some loose guidelines:
+
+* The new logo should be round and have some dimensionality to keep it consistent with the Truffle logo.
+* The colors should consist of chocolate, an accent color and white.
+
+The concepts we explored can be roughly broken down into 4 categories: Core Cutaways, Toppings, Gooey Cores and Soft Blocks.
+
+## Core Cutaways
+
+The first set of core cutaways was an attempt to convey that Ganache, as a local development blockchain, was the "core" of your development workflow. They also depict a ganache filled truffle candy of varying viscosities.
+
+It was toward the end of this stage we qualified one of our initial guidelines. The logo's dimensionality should be represented purely by shape--no gradients!
+
+**Fun fact**: We considered one of the third row, second and third column concepts as a final candidate, but scrapped it when Tim's wife said it looks like a banana slug floating in space. My baby, a slug?! A great reminder to not get too attached before getting feedback!
+
+</div><div class="text-center container">
+  ![Ganache Logo Concepts - Core Cutaways](/img/blog/designing-the-ganache-logo/core-cutaways.png)
+</div><div class="container container-narrow">
+
+## Toppings
+
+Questions about the ability of the core cutaways to translate to flat color, as well as being dimensionally mismatched with the Truffle logo caused us to consider a simpler approach; a spherical candy with ganache on the outside. Overall these failed to look interesting and had the opposite problem in that they weren't dimensional enough.
+
+</div><div class="text-center container">
+  ![Ganache Logo Concepts - Toppings](/img/blog/designing-the-ganache-logo/toppings.png)
+</div><div class="container container-narrow">
+
+## Gooey Cores
+
+Not satisfied with the topping options we pressed on and attempted the core concept again, this time with some fancier cutaways. While they stood on their own, they were too wide a departure from the Truffle logo. This lack of cohesion lead to a realization that would be our design breakthrough.
+
+</div><div class="text-center container">
+  ![Ganache Logo Concepts - Gooey Cores](/img/blog/designing-the-ganache-logo/gooey-cores.png)
+</div><div class="container container-narrow">
+
+## Soft Blocks
+
+Letting go of our assumption that the shape should be round unlocked a series of designs that eventually led to our final logo. To achieve a more interesting drip pattern, we traced and combined different stages of glaze dripping down a cake. It became apparent that this approach was interesting, but made an overly detailed drip pattern which we later simplified for the final. We also tried a few different treatments of the candy's reflection. Check out that longhorn steer in the lower-left!
+
+</div><div class="text-center container">
+  ![Ganache Logo Concepts - Soft Blocks](/img/blog/designing-the-ganache-logo/soft-blocks.png)
+</div><div class="container container-narrow">
+
+## The Final Logo
+
+Success! After reconsidering some assumptions and solidifying others, we arrived at our final design. The final logo has both a compelling design and the following qualities that made it a winner:
+
+* The colors consist of chocolate, an accent color and white; a guideline we'll keep going forward.
+* It's metaphorically grounded in the product it represents--it's a block, after all!
+* The gooey consistency and soft, rounded corners represent the intimidating technical concept of a blockchain in a friendly and approachable way.
+
+<div class="row"><div class="col-xs-10 col-xs-push-1 col-sm-6 col-sm-push-3 m-b-2">
+![Final Ganache Logo](/img/blog/designing-the-ganache-logo/final-logomark.png)
+</div></div>
+
+We had a blast iterating this logo and Ganache itself. We hoped you learned from our experience and maybe picked up some of your own inspiration along the way. **Happy illustrating!**
+
+-- Josh & the Truffle Team
diff --git a/src/blog/develop-using-fluidity-truffle-box/index.md b/src/blog/develop-using-fluidity-truffle-box/index.md
new file mode 100644
index 000000000..60307490c
--- /dev/null
+++ b/src/blog/develop-using-fluidity-truffle-box/index.md
@@ -0,0 +1,93 @@
+---
+title: Develop using Fluidity Truffle Box
+hide:
+  - navigation
+---
+
+**TLDR;** Fluidity has a pretty awesome truffle-box with lots of goodies to build secure, well-tested smart contracts. With two simple commands, you’ll be set up for development using these testing and security tools preconfigured.
+
+To use:
+
+```shell
+npm install -g truffle
+truffle unbox fluidity/fluidity-truffle-box
+```
+
+## Develop using Fluidity Truffle Box
+
+Today, I’d like to share Fluidity’s Truffle Box. It contains a combination of tools we use to develop, test, and analyze our smart contracts. As our team has created several products and proof-of-concepts, we’ve developed a set of standards for creating smart contract repos and having a truffle-box makes this easier. We’ve tried and tested different tools and this box contains our favorite tools for efficient development.
+
+The Fluidity Truffle Box allows us to bootstrap our smart contract projects. This box focuses primarily on building safe and secure smart contracts that can be easily audited. We’re able to consolidate many of the new tools, as well as ensure that any projects we start always use up to date versions. Prior to starting new projects, we double check that the packages and tools within truffle-box are up to date. We acknowledge this truffle-box is not a kitchen sink of all the tools. It has been curated based upon what we consistently use. The box doesn’t have a UI component and mostly contains configurations and tools that aid in testing.
+
+## Core Tools
+
+At Fluidity we write smart contracts with Solidity using the latest fixed version, currently 0.5.10, and we use Ganache as our primary test chain. We use Open-Zeppelin as the base for many of our contracts’ systems. In addition, there’s a linter for both the smart contracts and tests using [solhint](https://www.npmjs.com/package/solhint) and [standard](https://www.npmjs.com/package/standard). A linter analyzes code and tests and then either recommends or updates the code for potential syntax errors and style recommendations. Solhint’s configuration is present in fluidity-truffle-box and tries to closely align with the Solidity documentation. We use standard because it’s opinionated and keeps the codebase consistent with minimal fuss. Thus, standard doesn’t have any custom configurations.
+
+## How we handle testing and code coverage
+
+### Gnosis Mock Contract
+Gnosis-Mock is a comprehensive mocking smart contract that allows us to perform unit-testing of our smart contracts. For those not familiar, mocking means creating dummy objects to simulate the behavior of real objects. Mocking allows one to isolate the behavior of the testable object from any other dependencies. As an example, certain behavior in smart contract designs, such as closing a token sale, may require dependencies on several state variables and contracts to already be triggered to allow it to burn tokens. To close a token sale, let’s say you need to have started the sale, sold some threshold of tokens, reached a certain future block, and given close sale privileges to another user. Any one of these requirements, outside of just calling close sale, would need to be run if mocking were not used. By simulating these states with dummy smart contract, it narrows down exactly what needs to be tested. We heavily use the Gnosis mock library which allows us to test contracts independently before running any integration tests.
+
+### Truffle Assertions
+Truffle assertions has streamlined how we test events and states of smart contracts. The packages works inside Truffle tests and provides more assertions to call about smart contract states. It supports revert reason strings so we can be confident that exact cases are hit on revert. In addition, it provides more granular ways to test for function failures.
+
+### Eth-gas-reporter
+Eth gas reporter shows us the gas usage per unit tests in a nice report after running your test suite. We’ve tried many other tools before as well as trying to write custom gas usage with web3. This has been a recent find for us and has made gas analysis much easier.
+
+### Solidity-coverage
+We use solidity-coverage to determine what percentage of the codebase is covered by unit tests. We use a forked version by **leapdao** because this version supports many of the breaking changes with Solidity 0.5.0+. Code coverages give a helpful metric to ensure we’re testing as we code and that all branch paths are tested. It has also served for us to remove redundant code paths that we’ve found were not accessible. In addition, we have incorporated code-coverage with our CI process, meaning it is automatically executed on every pull request we make, allowing us to easily check PRs for code coverage. The configuration is stored in `<project_rool>/.solcover.js`, and can be personalised for your project.
+
+### Slither and Mythril
+Both slither and mythril are python packages that we’ve included in our truffle-box. They are security tools by [Trail of Bits](https://www.trailofbits.com/) that allow us to better self-audit our code and evaluate many of our invariants and assumptions internally. Instructions to run each of these packages are stored in the README.md file of the fluidity-truffle-box.
+
+Slither is a static code analyzer by Trail of Bits. It runs across the contracts directory fairly quickly (< 1 min) and picks up potentially vulnerable Solidity code. Mythril is a security analysis tool for EVM bytecode from ConsenSys. The program takes much longer to run, and while it’s in the truffle-box, we’ll usually run this tool on AWS or another cloud environment and analyze those results. While there is some overlap of errors that are picked up by truffle-compile, slither, and mythril, each focuses on different types of error. We therefore find it helpful to use all 3 on our contracts.
+
+### Circle CI Template
+At Fluidity we use circle-ci for our continuous integration. By having sample templates in the repo, it’s more convenient to making sure we enable it whenever we create new repositories. The new repos therefore constantly have to build successfully and migrate via Ganache, and test coverage is apparent to all members on the team. With the template in place, it’s quick for us to add additional commands such as linting or gas reporting dependent on where we are in the development process.
+
+## Unique features
+### Using allowUnlimitedContractSize
+We allow our initial contract designs not to be limited by any contract size constraints with the use of the flag *allowUnlimitedContractSize*. Ganache has a default gas limit of 6,721,975 which does not reflect the actual gas limit of public testnet and mainnets, being 7,000,000 and 8,000,000 respectively. While our team does want to reduce the gas footprint while developing and iterating through different token designs/debugging, it’s been helpful not to be limited by a strict gas price or gas limit with testing. For example, we use longer descriptive messages in revert reasons when developing, but reduce them to be more succinct for final code versions. Reducing the string lengths saved us 3,000,000 gas.
+
+Run each line in a different terminal window
+
+```shell
+yarn ganache-unlimited
+yarn truffle truffle-unlimited
+```
+
+After settling on a design, we’ll start iterating to reduce gas usage. As mentioned above, we use eth-gas-reporter to do this. Thus, with 100% test coverage and integration tests, eth-gas-reporter gives a pretty comprehensive understanding of gas usage throughout.
+
+## Custom Migration and Test Utilities
+
+There are two custom utilities files that we have created and keep available for the right circumstance of contracts. First, we have a custom migration utilities script. Truffle has deployed contract management but only stores a single address for each contract deploy per network id; each deployed contract is treated as a singleton. However, there have been cases where we’ve deployed multiple instances of the same contract and have needed to save each of the deployed contract addresses. Our solution was to create a custom migration_utils.js that stored the contract addresses per migration in  a JSON file. From there, integration tests and accessory scripts use the contract addresses while still relying on the build directory for ABIs.
+
+The second script is related to testing time sensitive smart contracts. We’ve written a post about it called [Standing the Time of Test](https://medium.com/fluidity/standing-the-time-of-test-b906fcc374a9) and we’ve used this script and features in Ganache to run both idempotent tests as well as run simulations.
+
+Running the command for a specific date
+
+```shell
+yarn ganache-unlimited --time '2019-02-15T15:53:00+00:00'
+```
+
+## Anything else
+
+Most of the features are in the [README](https://github.com/airswap/fluidity-truffle-box) in the directory and I’d love to take any questions or issues using this repository. Linking all these tools allows for a solid, sane development process for our team. They’re always at our fingertips with fluidity-truffle-box. Hopefully, you’ll be able to use the Fluidity Truffle Box to enhance your own smart contract development process!
+
+## Github repos
+* Fluidity Truffle Box: [https://github.com/fluidity/fluidity-truffle-box](https://github.com/fluidity/fluidity-truffle-box)
+* Gnosis-Mock: [https://github.com/gnosis/mock-contract](https://github.com/gnosis/mock-contract)
+* Truffle Assertions: [https://github.com/rkalis/truffle-assertions](https://github.com/rkalis/truffle-assertions)
+* Eth gas reporter: [https://github.com/cgewecke/eth-gas-reporter](https://github.com/cgewecke/eth-gas-reporter)
+* Leapdao Solidity-Coverage: [https://github.com/leapdao/solidity-coverage](https://github.com/leapdao/solidity-coverage)
+* Original Solidity-Coverage: [https://github.com/sc-forks/solidity-coverage](https://github.com/sc-forks/solidity-coverage)
+* Slither: [https://github.com/crytic/slither](https://github.com/crytic/slither)
+* Mythril: [https://github.com/ConsenSys/mythril](https://github.com/ConsenSys/mythril)
+
+## Fluidity Resources:
+* Website: [https://fluidity.io](https://fluidity.io)
+* Twitter: [https://twitter.com/fluidityio](https://twitter.com/fluidityio)
+* Facebook: [https://facebook.com/fluidityio/](https://facebook.com/fluidityio/)
+* LinkedIn: [https://linkedin.com/company/fluidityio/](https://linkedin.com/company/fluidityio/)
+* YouTube: [https://youtube.com/c/fluidityio](https://youtube.com/c/fluidityio)
+* Blog: [https://medium.com/fluidity](https://medium.com/fluidity)
diff --git a/src/blog/drizzle-150-a-new-beginning/index.md b/src/blog/drizzle-150-a-new-beginning/index.md
new file mode 100644
index 000000000..af77107ca
--- /dev/null
+++ b/src/blog/drizzle-150-a-new-beginning/index.md
@@ -0,0 +1,69 @@
+---
+title: Drizzle 1.5.0 - A new beginning
+hide:
+  - navigation
+---
+
+<figure>
+  <img src="/img/blog/drizzle-150-a-new-beginning/sunrise.jpg" alt="Sunrise landscape" style="width:100%">
+  <figcaption style="text-align: center;">_The dawn of a new era for regular releases and a better contributor experience_</figcaption>
+</figure>
+
+Since the beginning, our goal here at Truffle has been to make dapp development as easy as it can be. To this end Josh Quintal created [Drizzle](https://github.com/trufflesuite/drizzle), a managed Redux store to make interfacing with the blockchain just a little bit easier.
+
+## From many to one
+
+Today, we are announcing that we are moving to a monorepo. From now on, a single PR can be used to update code and documentation that used to span multiple repos.
+
+Over the last two years, we’ve developed libraries on top of Drizzle such as `drizzle-react` and `drizzle-react-components`. Since these libraries depend so heavily on each other, it only makes sense for us to move all of these packages to a monorepo to streamline any updates.
+
+In addition, we now also have an experimental Vue.js plugin that fits naturally into the monorepo architecture. It is very likely that going forward we will develop new packages to aid the Drizzle ecosystem in this manner.
+
+## Scoped package names
+
+Another big change we are making is towards scoped package names on NPM. This means that instead of:
+
+```
+drizzle
+drizzle-react
+drizzle-react-components
+drizzle-vue-plugin
+```
+
+We will now have:
+
+```
+@drizzle/store
+@drizzle/react-plugin
+@drizzle/react-components
+@drizzle/vue-plugin
+```
+
+From an organizational standpoint, this makes it a lot more intuitive to manage your dapp development.
+
+## Testing
+
+Prior to the monorepo, testing our libraries together was a slow, error-prone and painful experience. Our maintainers had to build custom dapps to isolate changes and manually link packages together as well as coordinate with ganache for each front end.
+
+The monorepo allows us to have dedicated front end apps that automatically build against the latest libraries and we can conveniently orchestrate them with a single ganache instance in just a couple commands. In other words, you can easily spin up three apps to test various aspects of the monorepo [in seconds](https://github.com/trufflesuite/drizzle/blob/develop/README.md#testing-and-debugging-with-ganache).
+
+<figure>
+  <img src="/img/blog/drizzle-150-a-new-beginning/test-ui.png" alt="Test UI instances" style="width:100%">
+  <figcaption style="text-align: center;">_Easily spin up real front ends to test that dapps can work with the current code_</figcaption>
+</figure>
+
+## Better release strategy
+
+Perhaps the biggest thing that the changes above allow us to do is more frequent releases.
+
+In the past year, we often had to deal with delaying the publishing of a new change because it required testing and updating other repos. Our publishing process was essentially being blocked by having to synchronize changes amongst multiple repos.
+
+With a monorepo, that all changes, which means that you can look forward to more regular releases and a faster turnaround time for getting issues fixed. Better changelogs are also coming as we move toward adopting [conventional commits](https://www.conventionalcommits.org) for each PR that gets merged.
+
+## Going forward
+
+It’s important to note that Drizzle wouldn’t be what it is without the open source community. A big part of why we are making all these changes is because we need you to help us make Web3 a reality together.
+
+Here at Truffle, every member on the team is passionate about improving the developer experience of building on Web3. In the upcoming weeks, we will be doing more regular blog posts targeting the front end space so keep an eye out!
+
+I would also like to specifically thank Amal Sudama for his work on making this transition. It certainly couldn’t have happened without him.
diff --git a/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md b/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
new file mode 100644
index 000000000..0dffda153
--- /dev/null
+++ b/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
@@ -0,0 +1,57 @@
+---
+title: Drizzle - Reactive Ethereum Data for Front-ends
+hide:
+  - navigation
+---
+
+Today we're proud to announce the addition of a new product to the Truffle Suite: Drizzle. Drizzle is a collection of front-end libraries that make writing dapp front-ends easier and more predictable.
+
+The core is based on a Redux store. We take care of synchronizing your contract data, transaction data and more. Things stay fast because you declare what to keep in sync. Importantly, this means you have access to the spectacular development tools around Redux. **Want to time travel through your recent transactions? You can do that with a slider.**
+
+  <video width="640" height="480" controls>
+    <source src="/img/blog/drizzle-some-chaindata-on-your-ui/drizzle-time-travel.mp4" type="video/mp4">
+    Your browser does not support the video tag.
+  </video>
+
+Drizzle's architecture is completely modular. This means you never lose access to the underlying web3 functionality you already know--drizzle as much or as little as you like. We've created two packages for use with React, but the core functionality is contained in the base `drizzle` module itself. If you're familiar with Redux, it's not a stretch to create an Angular library or use it for something other than a webapp.
+
+  ![Drizzle Modules](/img/blog/drizzle-some-chaindata-on-your-ui/drizzle-modules.png)
+
+Want to dive in right away? `truffle unbox drizzle` and you've got a full example dapp. Need more info? Read on!
+
+## The Libraries
+
+### Drizzle
+
+The core library responsible for web3, account and contract instantiation; wiring up the necessary synchronizations and providing additional contract functionality.
+
+[GitHub Repo](https://github.com/trufflesuite/drizzle)
+
+### Drizzle React
+
+Provides a DrizzleProvider component and drizzleConnect helper method to make it easier to connect Drizzle with your React app.
+
+[GitHub Repo](https://github.com/trufflesuite/drizzle-react)
+
+### Drizzle React Components
+
+A library of useful components for common dapp functions. Currently includes:
+*   `LoadingContainer`: Wraps your app, ensuring it waits for web3 and contract instantiation and displays relevant feedback if something goes wrong.
+*   `ContractData`: Displays contract call output.
+*   `ContractForm`: Automatically generates a form for contract transactions.
+
+[GitHub Repo](https://github.com/trufflesuite/drizzle-react-components)
+
+## The Box
+
+Shown in the video above, this box makes use of all of Drizzle's libraries in a finished example dapp.
+
+[GitHub Repo](https://github.com/truffle-box/drizzle-box)
+
+**Help us grow this baby!** What do you want to see from Drizzle? More components? More options? To put it another way: what are you sick of doing on the front-end?
+
+![Drizzle Baby](/img/blog/drizzle-some-chaindata-on-your-ui/baby.jpg)
+
+We're excited to hear your feedback and can't wait to see what you'll build! 
+
+-- Josh & the Truffle Team
diff --git a/src/blog/drizzle-vue-a-truffle-story/index.md b/src/blog/drizzle-vue-a-truffle-story/index.md
new file mode 100644
index 000000000..3a7ada19e
--- /dev/null
+++ b/src/blog/drizzle-vue-a-truffle-story/index.md
@@ -0,0 +1,69 @@
+---
+title: Drizzle Vue - A Truffle Story
+hide:
+  - navigation
+---
+
+![Drizzle + Vue = <3](/img/blog/drizzle-vue-a-truffle-story/title-image.png)
+
+Truffle is an organization that maintains a balance of transparency, mentorship, encouragement, inclusivity and humor that I'm thankful for everyday. While much could be written about Truffle's management culture, I want to share my experience of working on a side project here.
+
+Our remote work setup and the openness of our team contributes to a healthy and productive environment. The ability to schedule zoom sessions to brainstorm and discuss ideas fits well with our schedule. Every member contributes to this culture being generous with their time and knowledge. I'm happy and inspired to see team members grow as developers through the subtle mentorship as a result of our culture.
+
+For most of my career, I dreaded mandatory soul draining review type meetings, but at Truffle, I look forward to the incredibly productive and creative weekly one-on-ones I have with Joshua Quintal, our Product Lead. Josh originally developed Drizzle and we often discuss its role in the dapp ecosystem, issues and roadmap during our meetings.
+
+## About Drizzle
+
+Drizzle is a Smart Contract Store with a subscription and mutation API that abstracts away the boilerplate for reading and writing smart contract state as well as listening for contract events.
+
+Drizzle originated as a helper library for a React project Josh was developing. However he came to realize that the Smart Contract Store was an important piece needed in dapp development as applications start to scale. In Web 2.0 the need to manage and reason about state at scale has led to libraries like [1] [Redux](https://redux.js.org/introduction/prior-art). Similarly, we want to give web 3.0 dapp developers these best practices to leverage as their applications grow in complexity.
+
+## Drizzle's Unintended Front End Frameworks Exclusion
+
+Unfortunately, this is not how Drizzle is understood by developers we interviewed formally and informally. The most common misunderstanding is that Drizzle is coupled with React, the most popular JavaScript front end framework. We can't blame our community as most of our documentation focuses on implementing Dapps using React.
+
+Drizzle was initially released with bindings only for React which created this misperception that excluded developers from utilizing other front end frameworks such as Vue and Angular.
+
+The problem is that we didn't offer an easy solution for Vue or Angular and our documentation doesn't offer guidance. We want to change this! We want to support all the frameworks!
+
+## A Vue Plugin Side Project
+
+I felt this was an important problem to solve in order to improve the dapp developer experience.  It was important to get Drizzle working for Vue. Unfortunately, I knew nothing about Vue. In previous organizations I was a part of, I would have shied away from pursuing this project. However, at Truffle I felt comfortable and empowered to champion the idea. Josh encouraged me to spend the time needed to study Vue and experiment with the concepts.
+
+The basic plan was to:
+- Use Vuex, Vue's popular State management plugin
+- Transform Drizzle's redux store to be consumed by Vuex
+  - A redux store as an [2] [Observable](https://redux.js.org/api/store#subscribe) which would allow us to transform/map drizzle state to a more state pieces that Vuex could consume.
+  - This would allow us to have more efficient UI renders by using RxJS techniques like `distinctUntilChanged`
+- Create basic Vue components mimicking drizzle-react-components
+  - Vue's architecture allows us to use the adaptor as a datasource as well as provide basic support for Components that can render the data. This gives Vue developers to use our basic Components to make quick proof of concepts, and the flexibility to create richer Components when they need to.
+
+A [3] [basic proof of concept](https://github.com/trufflesuite/drizzle-vue-plugin) eventually surfaced and I was happy with the outcome as it showed a path forward to Angular using this approach with RxJS and can't wait to test it out!
+
+## Collaboration And Improvements
+
+Another aspect of Truffle's culture is to promote collaboration and exchange ideas with our community, and meet like minded developers and advocates working on similar problems. We're encouraged to go to meetups and be advocates for this incredible space.
+
+I reached out to Julien Klepatch on reddit after seeing his impressive [4] [Drizzle overview video](https://www.youtube.com/watch?v=QH_yLPYQEs4&feature=youtu.be) and asked for his feedback on the Vue Plugin. His participation, code contribution, code review and feedback clarified the project's direction and generally improved the codebase. Furthermore, he created 3 videos to explain the new plugin.
+- [5] [Drizzle Vue Plugin: overview](https://www.youtube.com/watch?v=XaVEZ1ucxac)
+- [6] [Drizzle Vue Plugin: Custom Components](https://www.youtube.com/watch?v=ApJwXfWKl7Q)
+- [7] [Drizzle Vue Plugin: Events](https://www.youtube.com/watch?v=xyoztqeYd6U)
+
+We also run a range of educational programs as part of Truffle University, that amongst other things, teaches developers how to use our full suite of tools. As part of the experience, students are mentored by the team and are encouraged to contribute to open-source projects, such as the Truffle Suite itself. James Kehoe, a developer in our first cohort, uses Vue on a daily basis and took an interest in the plugin. He took the initial design of the Contract Event Logic and turned it into idiomatic Vue. James also improved the documentation and introduced testing to the project. I learned a lot about Vue pairing with James, and look forward to future sessions with him.
+
+## Take A Preview
+
+You can preview the [3] [Plugin](https://github.com/trufflesuite/drizzle-vue-plugin) before we officially release it. Be sure to check out Julien's videos for an excellent walkthrough: [5] [Drizzle Vue Plugin: overview](https://www.youtube.com/watch?v=XaVEZ1ucxac), [6] [Drizzle Vue Plugin: Custom Components](https://www.youtube.com/watch?v=ApJwXfWKl7Q) and [7] [Drizzle Vue Plugin: Events](https://www.youtube.com/watch?v=xyoztqeYd6U)
+
+This project happened because of Truffle's enabling and supportive culture. Truffle is cool like that!  Also, co-MVPs James and Julien's improved the Vue Plugin and made it a viable tool. In fact, I consider them to be original contributors and am happy to see their continued involvement in the project.
+
+Come meet the team and learn about our tools at TruffleCon. We're looking forward to meeting you all!
+
+## References
+1. https://redux.js.org/
+1. https://redux.js.org/api/store#subscribe
+1. https://github.com/trufflesuite/drizzle-vue-plugin
+1. https://www.youtube.com/watch?v=QH_yLPYQEs4
+1. https://www.youtube.com/watch?v=XaVEZ1ucxac
+1. https://www.youtube.com/watch?v=ApJwXfWKl7Q
+1. https://www.youtube.com/watch?v=xyoztqeYd6U
diff --git a/src/blog/ethereum-gas-exactimation/index.md b/src/blog/ethereum-gas-exactimation/index.md
new file mode 100644
index 000000000..6b21130bc
--- /dev/null
+++ b/src/blog/ethereum-gas-exactimation/index.md
@@ -0,0 +1,174 @@
+---
+title: Ethereum Gas Exactimation
+hide:
+  - navigation
+---
+
+In Ethereum, estimating gas for a given transaction is a tricky problem to solve (especially when attempting to maintain [EIP-114](https://github.com/ethereum/EIPs/issues/114) compliance). Most of the well-known Ethereum implementations like Geth<sup>¹</sup> and Parity<sup>²</sup> use interval halving (binary search) to estimate gas by running transactions through the EVM until an approximate estimation converges.
+
+![Ganache Logo](/img/ganache-logo-h-dark.svg)
+
+At [Truffle](/), we decided such an approach was an unnecessarily CPU-intensive solution to the problem and set out to find a (theoretically) more performant and perfectly accurate way of estimating gas. The result? [Gas exactimation](https://github.com/trufflesuite/ganache-cli/releases/tag/v6.4.2). In this tutorial, we’ll go over gas exactimation at a high level in order to demonstrate its precision.
+
+**Complete example available at [the following repo](https://github.com/trufflesuite/gas-exactimation-tutorial).**
+
+**_Prerequisites: You should be familiar with Truffle, Ganache, and Solidity. If you need an introduction please consult the following resources:_**
+
+* [Truffle Quickstart](/docs/truffle/quickstart)
+* [Ganache Quickstart](/docs/ganache/quickstart)
+* [Solidity Documentation](https://solidity.readthedocs.io/en/v0.5.9/index.html)
+
+## EIP-114, or the “1/64ths rule”
+
+[EIP-114](https://github.com/ethereum/EIPs/issues/114) mandates that certain stackdepth-creating opcodes _withhold_ 1/64th of remaining gas from the stack they create. In practice this means:
+
+1. The gas required for a successful transaction can be greater than the actual gas spent (similar to how gas refunds behave).
+2. The extra gas required for a successful transaction varies depending on the transaction’s initial `gas` amount.
+
+A long-standing issue with [Ganache](/ganache) has been the fact that we haven’t returned EIP-114 compliant gas estimations. This has caused our gas estimates to be too low in cases where a transaction executed certain opcodes. **Gas exactimation** addresses this by considering how the gas withheld at any nested stack depth/frame affects the gas needed outside of its execution context.
+
+Let’s see it in action.
+
+## Create a New Truffle Project
+
+We will use `truffle init` to create a new Truffle project and then wire up an example [Solidity](https://solidity.readthedocs.io/en/v0.5.9/index.html) smart contract and test script.
+
+```shell
+// In a new project directory...
+$ truffle init
+```
+
+## Setup an Example Smart Contract
+
+With our new project initialized, we will create an example file: `ContractFactory.sol`.
+
+```shell
+$ touch ./contracts/ContractFactory.sol
+```
+
+Our file will have two contracts, `Contract` and `ContractFactory`. `ContractFactory` will have the method `createInstance` that we will use to create a new empty `Contract`.
+
+```
+// ./contracts/ContractFactory.sol
+pragma solidity ^0.5.0;
+
+contract ContractFactory {
+  function createInstance() public {
+    new Contract();
+  }
+}
+
+contract Contract {
+  constructor() public {}
+}
+```
+
+Note the `new` keyword being used to create a new `Contract`. A valid statement containing the `new` keyword gets compiled to bytecode containing the `CREATE` opcode which is subject to the [EIP-114](https://github.com/ethereum/EIPs/issues/114#issue-160782694) 1/64th gas withholding.
+
+## Write a Test Case
+
+Next, we will write a `ContractFactory` test case.
+
+```shell
+$ touch ./test/ContractFactory.js
+```
+
+This test case will deploy `ContractFactory` to a Ganache test network and use a gas estimate provided by Ganache to create a new `Contract`.
+
+```
+// ./test/ContractFactory.js
+const ContractFactory = artifacts.require("ContractFactory");
+
+contract("ContractFactory", () => {
+  it("...should deploy and successfully call createInstance using the method's provided gas estimate", async () => {
+    const contractFactoryInstance = await ContractFactory.new();
+
+    const gasEstimate = await contractFactoryInstance.createInstance.estimateGas();
+
+    const tx = await contractFactoryInstance.createInstance({
+      gas: gasEstimate
+    });
+    assert(tx);
+  });
+});
+```
+
+## A Quick Check
+
+Before we run our test, we’ll download the most recent version of Truffle that uses Ganache _before_ gas exactimation.
+
+```shell
+// In the project directory...
+$ npm i truffle@5.0.13
+```
+
+And we’ll make sure we have the latest version of Truffle installed globally that uses Ganache _with_ gas exactimation.
+
+```shell
+$ npm i -g truffle
+```
+
+## Testing Before and After
+
+```shell
+$ npx truffle test
+...
+...
+Error: Returned error: VM Exception while processing transaction: revert
+```
+
+And when we use gas exactimation...
+
+```shell
+$ truffle test
+...
+...
+Contract: ContractFactory
+
+✓ ...should deploy and successfully call createInstance using the method's provided gas estimate (130ms)
+
+1 passing (143ms)
+```
+
+!!!!
+
+## Testing Exactimation
+
+But is gas exactimation actually _exact_? 🤔
+
+We’ll open our test file and subtract exactly a single unit of gas from the `gasEstimate` before sending our test transaction.
+
+```shell
+// ./test/ContractFactory.js
+const ContractFactory = artifacts.require("ContractFactory");
+
+contract("ContractFactory", () => {
+  it("...should deploy and successfully call createInstance using the method's provided gas estimate", async () => {
+    const contractFactoryInstance = await ContractFactory.new();
+
+const gasEstimate = await contractFactoryInstance.createInstance.estimateGas();
+
+const tx = await contractFactoryInstance.createInstance({
+      gas: gasEstimate - 1
+    });
+    assert(tx);
+  });
+});
+```
+
+Running our test again against Ganache with gas exactimation...
+
+```shell
+$ truffle test
+...
+...
+Error: Returned error: VM Exception while processing transaction: revert
+```
+
+Exactimation confirmed 🚀.
+
+Note: Since the initial release of gas exactimation, an even more performant iteration of the algorithm is currently in review here.
+
+[1]: [https://github.com/ethereum/go-ethereum/blob/master/accounts/abi/bind/backends/simulated.go#L267](https://github.com/ethereum/go-ethereum/blob/master/accounts/abi/bind/backends/simulated.go#L267)
+
+[2]: [https://github.com/paritytech/parity-ethereum/blob/master/ethcore/src/client/client.rs#L1658](https://github.com/paritytech/parity-ethereum/blob/master/ethcore/src/client/client.rs#L1658)
diff --git a/src/blog/first-ever-truffle-retreat/index.md b/src/blog/first-ever-truffle-retreat/index.md
new file mode 100644
index 000000000..b7a3a22ba
--- /dev/null
+++ b/src/blog/first-ever-truffle-retreat/index.md
@@ -0,0 +1,124 @@
+---
+title: Our First Ever Truffle Retreat
+hide:
+  - navigation
+---
+
+![Truffle](/img/blog/first-ever-truffle-retreat/medium-truffle-retreat.jpg)
+
+This past summer, the Truffle team got together to together to define our roles, our mission statement, and our product roadmap - and had some fun in the process.  
+
+----------
+
+The Truffle team is fully remote. This has a lot of advantages in that it allows for a wide range of people available to work on your project; but it can also make it difficult to get to know your coworkers. 
+
+I started Truffle in early 2015 as the sole developer, and it stayed that way for nearly a year and half. John McDowell joined in late 2016, and by the time of the retreat we happily brought Nick D’Andrea and Josh Quintal on board. All interviews happened over Skype.
+
+I live in Yakima, Washington. John lives in Victoria, British Columbia. Nick lives in Philadelphia, and Josh lives in Detroit. That’s a lot of distance between us. 
+
+![Truffle employees in September](/img/blog/first-ever-truffle-retreat/truffle-map-01.jpg)
+
+When we brought Nick and Josh onto the team, it became obvious that we needed to meet up in person to solidify our roles, define responsibilities, and establish our own culture before growing the team even larger. 
+
+And we wanted to hang out in the woods, at the top of a mountain, and get to know each other. 
+
+## The Location
+
+![View from the house](/img/blog/first-ever-truffle-retreat/location.jpg)
+
+We had our retreat near Victoria, BC where John lives. Nick, Josh and I traveled all day through a series of planes, ferries and car rides to finally arrive at the house around 7 pm. The house sits atop a large hill in Braemer Heights overlooking all of Victoria, and on a good day has a beautiful view of Mt. Baker in the States. 
+
+The house was the definition of excess for a team of four, especially with only three of us sleeping there. It had five bedrooms and four bathrooms; a deck with a grill; three stories, the topmost containing only an office with 360-degree windows; and loads of wildlife. Unexpectedly, it was only ten minutes away from a Costco, which helped immensely. Even more unexpectedly, this mansion cost us less than three hotel rooms and a coworking space.  
+
+![Another view](/img/blog/first-ever-truffle-retreat/mountain.jpg)
+
+## The Work
+
+I had a few specific goals for our retreat: to define everyone’s roles and responsibilities within our team, to define our product roadmap for the next six months, and to create a mission statement for Truffle that our whole team could rally behind. 
+
+### Retrospective
+
+We started with a retro. We wanted to evaluate where we were as a team before deciding where we wanted to go in the future.
+
+So on Tuesday morning, we sat down and gave praise for what we’ve done well and identified areas where we could improve. I brought a list of business areas that are important for Truffle -- things like development, technical leadership, branding, marketing, etc. -- and we graded ourselves on each of them. 
+
+This turned out to be an interesting exercise. As the leader of the team you want to say “we’re doing great”, and not diminish anyone’s efforts -- because, it’s true, we’ve come far for a small team. However, we need to know where we can improve and how different areas of our company, teamwork and products stack up to the rest. In general, we all seemed to agree on the results: Branding and growth have been stellar (e.g., we have a good product that people like to use), but more external communication -- like our technical leadership, our relationship with the Ethereum Foundation, and relationships with some of our VIP users -- could use some improvement. Though these results were mostly subjective judgements, the conversations that resulted helped inform discussions about our roles and future roadmap. 
+
+### Roles & Responsibilities
+
+The Truffle team had already doubled in size in 2017, and right before the retreat two new team members -- Ben Burns and Mike Pumphrey -- had accepted offers (welcome!). So we knew we had some work to do regarding defining our roles and how we work together as a team.
+
+Before the retreat, I had met separately with Nick, Josh, and John to evaluate how they felt about their current roles at Truffle. We each talked about what they wanted to do both within the team and professionally, and how I could help them get there. Then we used this time at the retreat to reorganize the work so that it aligns with each team member’s personal goals as well as the group’s goals. We created a new org chart and chain of command, including the new team members we knew were coming on. 
+
+We decided that Josh and John would share design responsibilities for our website, logo design and general aesthetics for all of our products. Ben, who started in October, would take on the internals of the TestRPC (now [Ganache](/ganache/)) and related products ensuring we stay up to date with the Ethereum ecosystem. And Mike would be coming on board to wrangle all of our documentation and learning content, eventually molding it into tailored courses we’d offer to individuals and businesses. 
+
+That just left Nick and I. Though we both knew Nick would work on the internals of Truffle when he was hired, we didn’t know the extent of the work required; in addition to improving Truffle, Nick would be burdened with the arduous task of softly and lovingly ripping my baby from my arms. That is, Truffle’s my baby, and I’ve been nurturing it from day one. In order to build a more functional and growing team, it became clear I’d have to let go of the internal implementation details and focus more on our business and our product, leaving Nick to explore the tool’s technical way forward.
+
+This transition has been a great growing experience already, both professionally and personally. We’ll continue to evaluate this structure over the next six months to see how it works out. 
+
+### Mission Statement
+
+The next step was to determine why we’re here. The big three questions were: Why are you here? What do you value? And what do you stand for? The point was to elicit each team member’s value systems to get a big picture of what it is we really care about. 
+
+My original plan for this session was to put each person on the spot and ask them those questions directly. As it turns out, this interrogation technique was not the best way to get meaningful, genuine answers from the team. 
+
+Luckily, John came up with a better plan. He suggested we have each member of the team write their values on six index cards, and then have the whole team talk about each other’s values, create a big list, and vote on them to determine our company values. 
+
+![Our values](/img/blog/first-ever-truffle-retreat/mission.jpg)
+
+The conversation helped us all understand how different we were, and how much our values varied. We expressed everything from receiving good pay to building the distributed ecosystem. 
+
+In the end, we all agreed why we’re here. Our new mission statement: 
+
+> _Truffle builds useful tools for the next generation of blockchain technologies. We enable the growth of the Ethereum and open source communities, help to improve the role of decentralization in society, and empower developers to achieve their goals._
+
+### Product Roadmap
+
+On Thursday, we got into the details of what we’ve been working on at Truffle and where we’re going. This included presentations for new products [SPOILER ALERT!] and discussions about specific features. We’ve been hard at work since we drafted this post, so some you may have heard of already: 
+
+* [Truffle 4.0!](https://github.com/trufflesuite/truffle/releases) - with a debugger, improved development and testing experience, and more! 
+* [Ganache](/ganache) - a personal blockchain for developers. 
+* Drizzle - a frontend framework for React and Angular to easily connect Truffle-based projects.
+* Project Hotcakes - a full stack suite for web applications.
+* Live - a browser-based, interactive Truffle IDE.
+
+We also talked about revamping our development processes, which included not only how we work together as well as beefing up our continuous integration systems and making it very easy for users to contribute to Truffle projects. Stay tuned for more info!
+
+## The Fun
+
+In the middle of all of this work we wanted to get some bonding time in too. And if you haven’t been to Victoria, it really is gorgeous, and we couldn’t let this trip go to waste.
+
+So on Wednesday we got in John’s Honda Element and drove for two hours to Port Renfrew. The hike on paper: beach hike, sun, potentially bears, great outdoorsy time. The hike in reality: 
+
+![Rainy hike](/img/blog/first-ever-truffle-retreat/hike.jpg)
+
+We didn’t see any bears, and we got completely rained out of the hike. But, we also took our first Truffle team selfie: 
+
+![hashtag selfie](/img/blog/first-ever-truffle-retreat/team-pic.jpg)
+
+And eventually when the rain cleared got this cloudy-but-serene view from the dock at Port Renfrew.
+
+![A nice dock](/img/blog/first-ever-truffle-retreat/dock.jpg)
+
+And when we got back to the house, we made dinner, played board games, and drank a bunch of wine. 
+
+![Fooooood](/img/blog/first-ever-truffle-retreat/food-1.jpg)
+![Josh cooks](/img/blog/first-ever-truffle-retreat/food-2.jpg)
+
+So overall, we had some successful bonding time. 
+
+## Going Home 
+
+Being able to all be in the same room for the first time ever was extremely rewarding. It gave us a great foundation for the future of our working relationships and of Truffle as a whole, and increased our personal relationships in a way you don’t get when working 100% remotely. We’ll definitely be making retreats a recurring part of working at Truffle. 
+
+Now that we’re all back to work as usual, we’ve already taken the results of the retreat to heart. We’ve implemented our new development processes (info to come soon); revamped our products and offerings to be more in line with each other; have been settling into our new roles amazingly, and with little conflict; and overall we’ve been having a great time.
+
+There are a few things I want to make sure I remember coming out of this retreat: 
+
+**You can build more of a relationship with someone in 10 minutes in person than you can in 3 months on Slack.** I want to maintain this momentum and rapport. We’ve found that video calls are the closest you can get on a 100% remote team. Going forward, we’re now having one-on-one meetings every week to make sure we can keep up our rapport and ensure we’re giving each other consistent, useful feedback.   
+
+**The right processes and structures are the basis for responsibility, autonomy, and trust between teammates.**  During the retreat we collectively decided on rules and structure that would help us work better together. These rules were meant to increase responsibility and autonomy and provide a basis of trust in decision-making where each of us are responsible for our own individual specialties. I want to increase this trust and know that each team member can make the right decisions when needed.
+
+**Building rapport with your teammates is worth the effort.** In a remote team you don’t often get the chance to invite your coworker over for dinner or go to a local event. Bridging this gap is hard, and requires conscious effort, but has so many benefits including happiness, morale and general enthusiasm toward coming into work every day. I want to continue to bridge this gap and foster a culture where even if we’re a thousand miles away, we can still feel close enough to have each other over for dinner.
+
+Final thought: I’d eat Nick’s caprese salad and Josh’s sirloin medallions any day of the week.
diff --git a/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md b/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
new file mode 100644
index 000000000..954d59301
--- /dev/null
+++ b/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
@@ -0,0 +1,49 @@
+---
+title: Get a Bird's Eye View with Truffle Teams' New Dashboard
+hide:
+  - navigation
+---
+
+<figure>
+  <img class="mb-4" src="/img/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/blog-header.jpg" alt="Truffle Teams Dashboard" style="width:100%">
+</figure>
+
+As the operational needs of your dapp grow in complexity, it helps to be able to choose an area of focus. More incoming data begets a greater need to gain insights and properly segment that data to prevent overload. Wouldn’t it be nice to see an overview of a particular deployed instance of your application with the ability to drill down into the parts you need to see in more detail? This is where the dashboard comes in!
+
+<p class="alert alert-warning">💬 The Dashboard feature could expand in many different directions and we need your help to prioritize what matters most for your dapps. In that spirit we’ve released this first version quickly to get the conversation started. Please comment in the <a href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA">Truffler Slack workspace</a>, <a href="mailto:info@trufflesuite.com">email us</a>, reach out any way you can--we’re excited to hear from you.</p>
+
+We first asked ourselves “what is a dashboard”? and surprisingly, got many different answers! We arrived at this definition: **A dashboard is a place to see an overview of your application, along with ways to drill down and get further context on more narrow slices.**
+
+The first release focuses mostly on the high-level, but we plan to increase the drilldown capabilities as the feature evolves.
+
+## A Bird’s Eye View
+
+<figure>
+  <img class="mb-4 figure-shadow" src="/img/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/truffle-teams-dashboard.png" alt="Truffle Teams Dashboard" style="width:100%">
+  <figcaption class="text-center font-italic">The dashboard page with a deployment selected</figcaption>
+</figure>
+
+In this first version of the dashboard, you can pin a deployment for quick insights and visualization. Some of this information we haven’t surfaced before, such as the deployment’s cost and the number of unique addresses interacting with a deployment’s contracts.
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE NEW DASHBOARD</a>
+</div>
+
+## Looking Ahead
+
+Here’s a bit of a teaser for you to get an idea of where this is going:
+
+* A filter option to specify exactly which contracts are being displayed in the transaction graph
+* A list of contracts providing the ability to hop into monitoring a specific contract instance or...
+* Quickly interact with those contracts via our upcoming Contract Manager
+
+We strive for Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about this integration solution, and if your team has other needs we haven’t met yet.
+
+Continue the conversation with your fellow Trufflers in our Slack community!
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3 mb-4" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLE SLACK COMMUNITY</a>
+</div>
+
+Thanks!
+_Josh Quintal, Head of Product & Marketing_
\ No newline at end of file
diff --git a/src/blog/github-repository-moved/index.md b/src/blog/github-repository-moved/index.md
new file mode 100644
index 000000000..a48f5d8ad
--- /dev/null
+++ b/src/blog/github-repository-moved/index.md
@@ -0,0 +1,23 @@
+---
+title: We've moved our github repo!
+hide:
+  - navigation
+---
+
+We recently released [Truffle 3.0](https://github.com/trufflesuite/truffle/releases/tag/v3.0.2) in February to [much fanfare](/dashboard). As part of that release we separated our codebase into multiple different modules to make integrating with Truffle easier. Those modules now live in the github repository [https://github.com/trufflesuite](https://github.com/trufflesuite), which hints at our broader mission of providing a comprehensive suite of tools for Ethereum development.
+
+## But something was missing...
+
+We forgot Truffle! The main Truffle repository -- including the Truffle command line tool -- remained at it's old [Consensys](https://github.com/consensys) location while its modules hung out at their new digs. We thought to ourselves: That just wouldn't do. So, as matter of announcement, Truffle has officially moved. It's new home is [https://github.com/trufflesuite](https://github.com/trufflesuite).
+
+## Wait, there's more.
+
+The [Truffle Suite](https://github.com/trufflesuite) repository will soon be filling up with more open-source tools to make your Ethereum development life easier. We're not ready to announce what those are yet, but stay tuned for some awesome announcements in the coming weeks.
+
+## While you're here.
+
+While we're announcing things, we should let you know we have a new Twitter account: [@trufflesuite](https://twitter.com/trufflesuite). Feel free to reach out to use there for all your Truffle needs.
+
+Au revoir for now!
+
+-- Tim
diff --git a/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md b/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
new file mode 100644
index 000000000..b14a5d918
--- /dev/null
+++ b/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
@@ -0,0 +1,74 @@
+---
+title: How Ethical Advertising Will Transform the Blockchain Industry
+hide:
+  - navigation
+---
+
+![GitCoin](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/pasted image 0-5.png)
+
+*CodeFund is an ethical ad platform that funds contributors to the open source ecosystem. Visit [CodeFund](https://codefund.io/) to learn more and apply.*
+
+### The Conflicting Relationship Between Blockchain and Marketing
+In the initial years following Bitcoin’s inception, most blockchain companies didn’t need paid advertising. The early adopters were a community of cypherpunks, libertarians, developers, miners, and hobbyists, that truly believed in the power of decentralized networks. To them, adoption was inevitable, and rather than putting paid ads in front of the general public, resources were better spent building wallets, development tools, infrastructure, and scalability solutions.
+
+Additionally, almost all early blockchain users and entrepreneurs were extremely privacy-conscious. Pseudonymity is a key component to cryptocurrencies, they wouldn’t work in a permissionless manner without it. The Adtech industry, on the other hand, is run by monolithic centralized powerhouses that gather and store immense amounts of personal data for precise targeting. For the first 5 years of Bitcoin, **the blockchain community ethos was quite literally the polar opposite of the advertising industry**.
+
+That’s not to say that in the early days exchanges, wallets, and other blockchain services were unable to run successful marketing campaigns. However, the community was generally so niche that most users had a good sense of what they were looking for. The famous cliche, “If you build it, they will come” is frequently repeated in this space. While it was arguably true for Bitcoin, the internet, and certain decentralized protocols, the data shows that marketing is often crucial for launching a business or community built on top of these networks.
+
+![Blockchain thought leaders Anthony Pompliano and Ryan Selkis share differing views on marketing](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-1.jpg "Blockchain thought leaders Anthony Pompliano and Ryan Selkis share differing views on marketing")
+
+Following the launch of Ethereum, the rise of smart contracts, and the ICO mania, things changed. All of a sudden it was relatively easy for startups to launch their own token and rake in millions with a whitepaper. As a result, marketing budgets began to skyrocket and paid campaigns were everywhere due to the (seemingly) huge potential for capital accumulation.
+
+While some genuinely revolutionary ideas were started and funded during this time, the vast majority were subpar projects and outright fraudulent scams preying on naive users. At one point [Coinmarketcap](https://coinmarketcap.com/), a fairly well-regarded website in the crypto space, was showing ads for [Bitconnect](https://en.wikipedia.org/wiki/Bitconnect), a known Ponzi scheme.
+
+![Example 2](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-2.jpg)
+
+As a result, most mainstream ad providers like Google and Facebook banned all ads pertaining to crypto. Some people in the blockchain industry thought this was unfair, but it was for good reason. Scammy projects were ruining the public perception of blockchain technology. However, reputable companies were also caught in the crossfire, finding it increasingly difficult to advertise their projects. Notably, Mailchimp’s blockchain ban impacted a project I was working on along with plenty of other startups. I remember when [Evan Van Ness](https://twitter.com/evan_van_ness)’ twitter and [Week in Ethereum](https://www.weekinethereum.com/) newsletter (my favorite Ethereum educational resource) were shut down [multiple times](https://cointelegraph.com/news/breaking-mailchimp-reportedly-shuts-down-accounts-related-to-crypto-prices-drop).
+
+![GetCoin image 3](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-3.jpg)
+
+So, what’s the solution? Fortunately, the majority of mainstream advertising services have relaxed their bans on blockchain advertising in the face of a maturing ecosystem. This is especially interesting when considering that both [Google](https://www.bloomberg.com/news/articles/2018-03-21/google-is-said-to-work-on-its-own-blockchain-related-technology) and [Facebook](https://libra.org) have announced their foray into the industry.
+
+### Existing Blockchain Advertising Obstacles
+
+We recently released a [blog post](https://codefund.io/blog/how-to-advertise-your-startup-blockchain-project) covering a variety of different free and paid channels to advertise your blockchain startup. And although there are more options than ever, there are still several obstacles to overcome. As we appear to be approaching the next bull market, scams will undoubtedly come back (I’ve already seen a huge uptick in the “free crypto” scams on twitter). Further, the crypto ecosystem hasn’t addressed the problems of mass data collection and rampant user profiling in the Adtech world. Most of us believe blockchain will be the catalyst for a revolution of privacy and self-sovereign identity, hopefully breaking up the big data monopolies of web2. Yet **the entrepreneurs and thought leaders pushing this narrative of individual autonomy and privacy in the digital age are still using advertising services that track, profile, and collect mass amounts of data from their target markets.** Marketing is inevitable - startups need to reach their desired audience and grow a user base. But can this be done in a more ethical way, in line with the ethos of this technology we love and support?
+
+### Enter: CodeFund
+
+While all of this craziness was happening in the blockchain world, [Eric Berry](https://twitter.com/coderberry) was focused on tackling a different problem: [The Open Source Conundrum](https://codefund.io/blog/the-open-source-conundrum-how-do-we-keep-the-lights-on). Open source software lays the foundation for the Internet as we know it and supports so much of our global business processes, yet comparatively receives very little support and funding. **How can we help open source projects and maintainers get consistent financial support?**
+
+Eric founded Code Sponsor [2 years ago](https://changelog.com/founderstalk/56), allowing companies to place small text-based sponsored messages on GitHub project READMEs to support open source software. Since then he’s been threatened with legal action, shut down, started again, rebranded to CodeFund, and eventually joined the [Gitcoin](https://gitcoin.co/) team at [ConsenSys](https://consensys.net/), who share the same mission: **get developers paid**.
+
+At [CodeFund](https://codefund.io/), we pride ourselves on showing ethical ads on developer websites, acknowledging and respecting individual privacy. This means that our ads do not track, use cookies, nor collect any data except for IP addresses and browser agents. We feel ads that track our browsing history and know our personal information are an invasion of privacy, and from our research, the majority of our user base feels the same way. So while we can't profile and target specific demographics and individuals, we can help you tailor your ads to the desired audience and display them on sites that your audience frequents with geotargeting. Users will see ads that they actually want to see without compromising their data, browsing history, or personal information.
+
+CodeFund is 100% [open source](https://github.com/gitcoinco/code_fund_ads) (feel free to contribute! 😄) and was built by developers for developers, so we understand the motivations of our users. We keep our content relevant by only showing high-quality ads from companies that are of interest to the audience. We diligently vet all advertisers and publishers to make sure they are a good fit for the network. By understanding the community and showing them ads relevant to their interests, you build trust between your advertisers, publishers, and most importantly, users.
+
+The CodeFund model is a bit unorthodox in the Adtech world. However, we find it to be extremely successful in our niche (and growing) open source community. Developers are typically [much more likely](https://www.stackoverflowbusiness.com/engagement/resources/the-state-of-developer-engagement-2018) to use ad blockers compared to typical Internet users. Developers are also known to be more concerned about privacy and data collection. For these reasons, they can often be hard to reach with advertising. To get your message seen, you need reputable publishers who are trusted by their audience. CodeFund is bound by the standards set by [acceptable ads](https://acceptableads.com/en/about/criteria), which means many ad blockers do not block us. We work with our users to allow our ads and make sure they are relevant to the audience, ensuring all parties involved are benefiting.
+
+![CodeFund growth by impressions, YTD](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-4.jpg "CodeFund growth by impressions, YTD")
+
+We believe the future of the web will be a **privacy-focused, user-driven evolution**. More scandals are emerging from large corporations revealing data mismanagement, leaks, and hacks of sensitive information. Digital advertising will never go away, but the average internet user is becoming more security and privacy conscious, and we think this will lead to an increased demand for ethical advertising products. That's why we built a platform to allow advertisers to get their message to the right audience without compromising user integrity.
+
+### Ethical Ads for Blockchain - Why Target Crypto Users?
+
+Initially CodeFund was not focused on the blockchain space, however, since [joining Gitcoin](https://medium.com/codefund/code-sponsor-joins-gitcoin-b7d35966b93d), we’ve been [expanding](https://medium.com/gitcoin/codefund-ads-on-etherscan-fae1a3d35b51) our offerings. We realized that ethical advertising is going to play a crucial role in Web3, blockchain, open source, and the future of the Internet - and that's something we want to support.
+
+Blockchain technology was undeniably born out of the open source ecosystem. While the two communities are not exactly the same, they share many morals and have significant overlap. By nature, blockchain and cryptocurrencies would be useless if they were not open source. A key feature of *decentralized* cryptocurrencies is that there is no need to trust an intermediary and no barriers to entry. For it to work, anyone must be able to run, review, and contribute to the code. Today's leading blockchains are a cumulation of hundreds, if not thousands of individuals contributing to open source code bases.
+
+Just like most developers, blockchain users and enthusiasts tend to be much more privacy conscious than a typical Internet user. As a result, CodeFund's ethical ad model is a great fit, not only for blockchain developers but also for blockchain users.
+
+CodeFund ensures that the blockchain projects we work with are building applications and tools for open source blockchains, primarily for Ethereum. We don’t work with projects pumping their own token sales, instead, we partner with blockchain companies that are **adding value to society and the open source ecosystem**.
+
+### CodeFund’s Blockchain Offerings
+
+For the next few months, CodeFund will be actively building out our blockchain publisher and advertiser networks. We are currently publishing ads on [Etherscan](https://etherscan.io/), [State of the Dapps](https://www.stateofthedapps.com/), [Etherchain](https://www.etherchain.org/), [Decrypt Media](https://decrypt.co/), [Coingecko](https://www.coingecko.com/), and a handful of other high-quality blockchain websites - with even more in the pipeline. Decrypt just release a great [piece](https://wp.me/p9ZACC-1Vv) on the problems with crypto “news” sites, and their motivations for advertising ethically. Our advertisers like [Truffle](/truffle) are happy with their results so far and have seen high conversion rates from their campaigns, without sacrificing the privacy and integrity of their audience.
+
+![Decrypt’s ethical ad integration](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-5.jpg "Decrypt’s ethical ad integration")
+
+Crypto markets are beginning to turn around, more startups are shipping products, and the global blockchain community is growing. We expect this trend to continue, driving the demand for blockchain advertising as a result. Many blockchain websites publishing ads see it as a necessary evil – they need to keep the lights on to continue providing their services, but feel their choices are limited.
+
+The first option is working with companies to run direct advertising campaigns. However, this approach consumes time and resources and can be risky if advertisers pull out. The second option, and perhaps the easiest, is to use Google Ads or another incumbent service. Using this approach, many feel they’re compromising users’ privacy and trust. Moreover, outsourcing to huge Adtech giants is part of the problem that made ICO scams so rampant in 2018-2019. These companies simply have far too much traffic and lack the specialized skill set required to manually vet every single advertiser and identify blockchain scams. The last thing publishers want on their website is an ad that loses your users' money or promotes the purchasing of unregistered securities.
+
+At Gitcoin and CodeFund, we are a small team that has been in the blockchain world for years. We view every publisher and advertiser as a partner, diligently vet them, and hold them to the highest standards. **We’d like to see ethical advertising become the new standard in the blockchain space, and eventually on the Internet as a whole.**
+
+If your blockchain company is interested in advertising to a high-quality audience, or you would like to earn passive income showing relevant ads on your website without sacrificing your community’s privacy, CodeFund is for you! Apply now on the [CodeFund](https://codefund.io/) landing page and we’ll be in touch, or reach out to [connor@codefund.io](mailto:connor@codefund.io) for more information.
diff --git a/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md b/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
new file mode 100644
index 000000000..9de4546d4
--- /dev/null
+++ b/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
@@ -0,0 +1,98 @@
+---
+title: How the Arrival of Web 3.0 is Transforming Traditional Business Models
+hide:
+  - navigation
+---
+
+Although the Internet continues to drive digital transformation, the technology operates far beyond its original parameters. Since its inception over two decades ago, the web has been subject to increasing levels of centralization and mass surveillance. As a result, large corporations, governments, and media outlets remain the primary beneficiaries of an infrastructure meant to serve all of humanity. Herein lies the problem with the current Internet ecosystem, also known as Web 2.0.
+
+In the current online environment, users continually function as commodities, generating value along with their data. And while large entities should not shoulder the blame for their role in our everyday lives, their control over our personal information is cause for concern. As Internet founder Tim Berners-Lee [once said](https://www.vanityfair.com/news/2018/07/the-man-who-created-the-world-wide-web-has-some-regrets), "for people who want to make sure the Web serves humanity, we have to concern ourselves with what people are building on top of it."
+
+It is precisely this sentiment that drives the Web 3.0 movement. And although blockchain technology may be the foundation of this movement, the initiative is much broader. Web 3.0 is about building a decentralized infrastructure that protects individual property and privacy. But what exactly does this look like and what are the potential implications? In this article, we'll explore the evolution of Internet infrastructure and how the arrival of Web 3.0 is impacting existing business models.
+
+## The Evolution of Web Infrastructure
+
+The Internet debuted employing simplistic "read-only" technology, meaning users were only able to search for information and read it. This Web 1.0 environment was primarily intended for advertising purposes, acting as an extension of physical storefronts. With the arrival of "read-write" functionality, users of Web 2.0 are able to create their content and interact with the Internet in a far deeper capacity. By facilitating the prolific growth of social media platforms, blogs, and online reviews, this infrastructure continues to guide global business models.
+
+However, as mentioned, this era of robust growth has not come without consequences. Consumer protections continue to rank behind corporate interests as web surveillance fuels lucrative data collection. Continued [data breaches](https://www.nytimes.com/2018/08/01/technology/data-breaches.html) effectively highlight the downside of this arrangement. In response to these challenges, Web 3.0 initiatives aim to put power back into the hands of users. But before exploring how this will occur, it's crucial to understand the specific Web 3.0 characteristics that will facilitate this process.
+
+![Example 1](/img/blog/how-the-arrival-of-web3/web3-example1.jpg)
+
+## Characteristics of Web 3.0
+
+Although Web 3.0 is difficult to define in exact terms, it can be effectively broken down into unique components.
+
+### Semantic Web
+
+The [semantic web](https://www.w3.org/standards/semanticweb/) improves upon existing web infrastructure by generating, sharing, and connecting content based on an understanding of words. Rather than relying on keywords and numbers, search and analysis utilize context.
+
+![Source: The Semantic Web Stack
+Connectivity](/img/blog/how-the-arrival-of-web3/web3-example2.jpg)
+*Source: [The Semantic Web Stack
+Connectivity](https://devopedia.org/semantic-web)*
+
+Thanks to semantic metadata, Web 3.0 achieves greater connectivity. By leveraging all available information, the user experience dramatically improves.
+
+### Artificial Intelligence
+
+Web 3.0 technology can process information in a way similar to humans. As a result, platforms can better satisfy user needs through continuous learning.
+
+### 3D Capabilities
+
+Three-dimensional design is already in use on many Web 3.0 platforms. Computer games, e-commerce applications, and mapping software represent only a few potential use cases.
+
+### Ubiquitous
+
+In the decentralized Web 3.0 environment, all content is accessible by multiple applications, every device connects to the web, and the associated services are available everywhere.
+
+## Web 3.0 and Existing Business Models
+
+Although we have only just begun to explore the potential of Web 3.0 applications, their ability to upset the status-quo is undeniable. Of particular interest to many is how decentralized projects, operating in traditional industries, will up-end conventional revenue models. Through utilizing distributed, peer-to-peer platforms, some industries have begun to consider other funding options.
+
+![Example 3](/img/blog/how-the-arrival-of-web3/web3-example3.jpg)
+
+Although there is a vast array of revenue models to consider, we’ll explore some of the most prominent options here. To see the full list, check out the [Github repository](https://github.com/FEMBusinessModelsRing/web3_revenue_primitives/#revenue-share).
+
+### Revenue Share
+
+The revenue share model uses profits to enable separate actors to develop efficiencies or innovate in mutually beneficial ways, such as splitting earnings.
+
+#### Percentage Fee
+
+This model is where you take a percentage of each transaction executed on your platform. It remains a popular model with exchanges and marketplaces. The seller usually pays for the fee since they're the one that benefits from completing a sale on the platform.
+
+#### Income Share
+
+Using this model, users share earnings from another entity. An offline example would be a restaurant where the cashier shares the tips with everyone. In the context of Web 3.0, you could give a one-dollar tip in a coffee shop and split it with every actor in the coffee value chain with minimal transaction costs.
+
+### ICO’s
+
+Conducting an ICO is the process of selling project tokens all at once, or over some time. There are several ICO models and token variations that companies can use to raise funds.
+
+### Continuous Funding Models
+
+Continuous Funding Models are business models that sell ERC-20 tokens over time, rather than all at once.
+
+#### Curved Bonding
+
+Curved Bonding is a method of continuous funding that incentivizes early investment. In contrast to conventional ERC-20 token sales and ICO's, which feature each token being sold for the same price (no matter the time of purchase), such models hardcode buy prices according to an algorithmic curve. By purchasing early, investors get more tokens for the same price than if they are buying later. Ultimately, using Curved Bonding incentivizes early adopters to invest in a token.
+
+#### Continuous Organizations
+
+A continuous organization is one that sets up a Decentralized Autonomous Trust (DAT). This trust is an immutable smart-contract that implements curve bonding to automatically mint, burn, and distribute security tokens called FAIR securities. Organizations provide value to the trust by diverting part or all of their cash flow to it.
+
+### Streaming Money
+
+#### Side Channels
+
+A sidechain is a separate blockchain that is attached to its parent blockchain using a two-way peg. Using this model, you can move assets to the sidechain and then back to the parent chain. However, sidechains also need their miners. These miners receive an incentive through 'merged mining,' whereby two separate cryptocurrencies, based on the same algorithm, are mined simultaneously.
+
+#### State Channels
+
+State channels are mostly two-way pathways open between two users that want to communicate with each other in the form of transactions. Here, only the outcome needs to be included in the form of a single transaction on the main chain. Other transactions occur on off-chain.
+
+### The Future of Internet Infrastructure
+
+As the development of Web 3.0 technology persists, blockchain technology will remain a vital component of online infrastructure. Although the world continues to benefit from the transformative power of the web, user empowerment remains a priority among a growing segment of society. In a time when centralized institutions and governments exert control over personal data, many have begun to challenge the status quo.
+
+Those exploring this emerging subset of the web are well-positioned to benefit from growing momentum. By leveraging Web 3.0 technologies, companies also have the ability to enact new, potentially lucrative business models. Regardless of the industry, the new web presents an opportunity to pivot from traditional revenue streams in search of more optimal solutions. In the midst of ongoing innovation, it’s important to note that all new technology requires refinement - and Web 3.0 is only just beginning.
diff --git a/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md b/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
new file mode 100644
index 000000000..4cb75b39b
--- /dev/null
+++ b/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
@@ -0,0 +1,62 @@
+---
+title: How to get your boss to send you to TruffleCon
+hide:
+  - navigation
+---
+
+Last year [Truffle Suite](/) launched [TruffleCon](/trufflecon2019), an event designed for the Truffle community and those interested in building world-changing applications powered by decentralized technologies. The event was received with an overwhelmingly positive response. TruffleCon attracted 250 attendees, 53 speakers, and 2 locations. After such a successful inaugural event, the team immediately started planning an even bigger and better Trufflecon for 2019.
+
+Join us this year on August 2-4 at the Microsoft Campus in Redmond, WA for the second annual event for the Truffle community: those who actively build using Truffle’s framework for development on Ethereum. Programming will include speakers from the blockchain ecosystem, along with hands-on workshops geared toward novice users and expert builders alike. There’s truly something for developers of all experience levels!
+
+TruffleCon places focus on the developer by exploring the many ways in which the Truffle tools can enhance the development process by increasing efficiency and enabling high-quality dapp production.
+
+We know that attending a blockchain conference often comes down to ROI for your organization. With so many learning and growth opportunities, here are a few things to remind your boss about when asking to send you to the 2nd Annual [TruffleCon](/trufflecon2019).
+
+## Truffle is widely considered the most popular tool for blockchain application development
+
+Truffle is widely considered the most popular tool for blockchain application development with over 1.5 million lifetime downloads. Truffle supports developers across the full lifecycle of their projects, whether they are looking to build on Ethereum, Hyperledger, Quorum, or one of an ever-growing list of other supported platforms. Paired with Ganache, a personal blockchain, and Drizzle, a front-end dapp development kit, the full Truffle suite of tools promises to be an end-to-end dapp development platform.
+
+## Truffle is being used by the largest and most prominent firms
+
+If your company want to implement blockchain solutions, you’ll need to learn how to interact with Truffle suite of products. Truffle is used by many fortune 500 firms and will be the first company to integrate with AxCore, a proprietary blockchain created by Goldman Sachs and JPMorgan-backed Axoni, which is scheduled to start processing $10 trillion worth of transactions annually for the DTCC’s Trade Information Warehouse later this year.
+
+Here are some of the amazing companies using or integrating Truffle:
+* Microsoft, ConsenSys, Amazon, VMWare Airbus, General Dynamics, J.P. Morgan and more!
+* Soon to be your company too!
+
+## Build dapps hands on and learn to deploy smart contracts 
+
+TrufflCon will have something for everyone from the novice and crypto curious to the advanced blockchain developers and everyone in between. Truffle’s world-class developers and trainers will be there to support you along your developer journey. You’ll learn hands-on how to build dapps and deploy smart contracts during our workshops.
+
+## Meet and learn from the creators of Truffle Suite: the ones closest to Truffle’s development
+
+#### Tim Coulter
+Tim Coulter is the Founder and CEO of Truffle. Before blockchain, Tim built a career specializing in software testing and developer support, which became extremely valuable in the early days of blockchain development. He's now surrounded by an amazing team building the next generation of blockchain development tools, and can't wait to tell you about what's to come.
+
+#### Mike Seese
+Mike Seese is a Core Developer on the Enterprise Products team. In addition to integrating the Truffle Suite to other ledgers and frameworks, he strives to bring the modern development experience to the blockchain community.
+
+#### Josh Quintal 
+Josh is passionate about where the user meets the tech; this led to the creation of two products, Truffle Boxes and Drizzle. He also created "Pet Shop", one of Ethereum's most used beginner tutorials. Besides his obvious technical prowess,Josh is also the most stylish member of the Truffle team.
+
+#### G. Nicholas D’Andrea
+Ever since 2016, he has been obsessed with the decentralized future and working towards building core software components for the blockchain ecosystem. Besides his work on Truffle, he is a core contributor to the EthPM package management system and author of EIP-1123.
+
+#### Kevin Bluer
+He’s building our world-class program at Truffle University from the ground up which trains existing software developers to become Truffle-certified blockchain engineers. Outside of his work with Truffle, he has trained and mentored developers in cities around the globe including New York, Austin, London, Hong Kong, Shenzhen, and Kuala Lumpur.
+
+TruffleCon is a place to meet our developers and work with them, ask questions, and get feedback on your work.
+
+## TruffleCon is for developers by developers
+
+While there is no shortage of conferences in the blockchain space, TruffleCon is uniquely created for developers, by developers. Tim Coulter, Truffle’s Founder & CEO, explained, "Developers attach their identity to the tools they're using. People are congregating around Truffle and want to learn from and collaborate with the people who are using the tools. We aim to host a conference where people can engage with their peers and share insights on how best to use these tools. We hope attendees will leave inspired and that the knowledge shared will transform how people build."
+
+## There will be lots of chocolate
+
+If your boss is still not convinced, most importantly, there will be A LOT of chocolate.
+
+Now, send this to your boss so they can send you to TruffleCon!
+
+[Secure Your Spot for TruffleCon 2019 in Redmond, WA August 2-4, 2019.](/trufflecon2019)
+
+More 2019 announcements are on the way — [Subscribe to the Truffle newsletter](https://truffleframework.us11.list-manage.com/subscribe/post?u=947c9b18fc27e0b00fc2ad055&id=97cfd4251b) and [join the conversation on Telegram in the TruffleCon Channel](https://t.me/TruffleCon).
\ No newline at end of file
diff --git a/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md b/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
new file mode 100644
index 000000000..840c7388c
--- /dev/null
+++ b/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
@@ -0,0 +1,74 @@
+---
+title: How we're making installation issues a thing of the past
+hide:
+  - navigation
+---
+
+<p class="alert alert-info">
+**Update**: Since this blog post was published, we have released [Ganache](/ganache) a personal blockchain and a replacement to the TestRPC. We have left this post unaltered, but we highly recommend checking out our [Ganache Quickstart](/docs/ganache/quickstart) page.
+</p>
+
+It doesn't matter what operating system you're on -- if you've used Truffle in any capacity, you've likely run into an install issue in some form or another. This is especially true for Windows, as Windows doesn't generally ship with the necessary tools to install all of Truffle's important dependencies. And for most users, this sucks: getting hung up on installation is incredibly frustrating when you're usually just one error message or two away from creating your first Ethereum-enabled application. Well, I've got good news. As of the latest Truffle beta release, I'm happy to tell you that this is an issue no longer.
+
+That's right: No matter what platform you're on, your install issues should be over. This is big.
+
+In order to completely sidestep most if not all of the most common installation issues, we had to overcome some technical difficulties as well as rethink how we ship our code. In this post, I'm going to tell you about what we did and how that made installation incredibly simpler, on every platform, for everyone.
+
+## So what was the problem?
+
+Since Truffle is a Javascript-based application, we (naturally) ship our code using the [Node Package Manager](https://www.npmjs.com/) (NPM for short). NPM hosts thousands if not millions of code packages, and it's the service that makes modern Javascript programming possible. Without NPM, not only would programming Truffle be nearly impossible, but programming _anything_ complex in Javascript would be impossible: NPM lets developers separate and bundle code into its own individual chunks, called "packages", that any of those other chunks (packages) can then rely on.
+
+Because of NPM, Truffle is standing on the shoulders of giants. Truffle relies on the code of so many other people that if you looked at the full list you'd be hard pressed to give us credit for the codebase. And that's the beauty of it: packages like hashing functions and cryptographic libraries -- hard libraries to write (and get right!) -- we don't have to write ourselves.
+
+Though using dependencies on NPM has significant upsides, it also comes with significant drawbacks. Those same hashing functions -- functions used throughout Ethereum -- are written to be extremely performant, and so are written in C. In order to install those packages, NPM has to be able to compile them on the fly during installation, which means every Truffle user needs to have a C compiler installed. Additionally, NPM (for some reason) uses Python during the compilation process, which means Truffle users _also_ need to have Python installed.
+
+Bottom line: In order to install a Javascript project, Truffle users need both C and Python. [This is madness.](https://s-media-cache-ak0.pinimg.com/originals/ec/5a/0a/ec5a0a5e4990668ca3f41ed50ca273d3.gif)
+
+## So what can we do?
+
+Most of the issues people were seeing stem from the compilation process mentioned: Either they didn't have the right compilers/interpreters installed for C and Python, or C and Python _itself_ required some dependency that wasn't properly installed. We've had a [tutorial](/guides/how-to-install-truffle-and-testrpc-on-windows-for-blockchain-development) written for awhile that shows Windows users how to correctly set up their environment and get everything installed, but this required considerable effort from novice users and didn't take into account the many landmines hiding around every corner, waiting to explode at any moment. So we can't "instruct" our way around this problem. The only way to fix it, then, is to sidestep it completely.
+
+Sidestepping the compilation process means completely excising any compilation out of the installation process. The way we chose to tackle this is two ways:
+
+- Remove any unnecessary dependencies that rely on compilation.
+- Replace dependencies that need compilation with versions 100% written in Javascript.
+
+In theory this sounds easy: i.e., "just use the Javascript versions or don't use the C versions as all". In practice, this is much harder. Often, we don't directly control the dependencies our application relies on, because _dependencies of dependencies_ (of dependencies of dependencies) might rely on a package that requires compilation. Since the bad apples are the packages that power the code we rely on (i.e., they're "indirect dependencies"), we have to surgically remove them and replace them with versions that install and function more easily. This is no small matter.
+
+Thankfully, a tool exists that makes this surgical replacement possible. It's called [Webpack](https://webpack.js.org/). Webpack bills itself as a Javascript bundler, aiming to mash together all your project's dependencies into a single blob of code, i.e., a "bundle". Webpack finds most of its uses in browser applications, as browsers need to download all code first before a website can be displayed, and it's more performant for the browser to download that code in a single request. However, for console applications like Truffle, Webpack can still be immensely valuable. By creating a bundle with Webpack, we can control exactly which dependencies get included in it.
+
+Take [js-scrypt](https://github.com/tonyg/js-scrypt) for instance. This library provides hashing functions required by Ethereum, is 100% written in Javascript, and is API-compatible with the C-compiled [node-scrypt](https://github.com/barrysteyn/node-scrypt) library. With Webpack, we can simply remove `scrypt` and replace it with `js-scrypt` like nothing happened.
+
+How about another example: Let's do IPFS. Truffle relies on the [ethpm-js](https://github.com/ethpm/ethpm-js) package to provide EthPM support, which itself relies on the [ipfs](https://github.com/ipfs/js-ipfs) package to communicate with IPFS servers. Somewhere deep down in `ipfs`'s dependency tree, some code needs the [execSync](https://www.npmjs.com/package/execSync) package, a package that causes installation issues for some users. Using Webpack, when creating our bundle, we can just _not include it_. Since that code only matters for parts of IPFS that Truffle doesn't use, that code doesn't need to be in our bundle. Ex-nay, [gone-yay](https://www.technobuffalo.com/wp-content/uploads/2016/03/kanye-west-1280x640.jpg). Zip, zilch, completely gone.
+
+Creating a bundle for our releases instead of letting NPM manage dependencies has other benefits as well. To keep code modular and maintainable, Truffle relies on almost 2000 packages! (This includes the dependencies of dependencies we mentioned before). Bundling ahead of time creates a single file users have to download during installation instead of requiring NPM to make requests for all 2000 dependencies. So not only do we get to sidestep all of the installation issues, but we make installation nearly instant as well.
+
+Yep. Feel free to party. We did. 🎉
+
+## So how can you get it?
+
+Bundling Truffle's dependencies means releasing a version of the code where certain dependencies have been either replaced or removed. This not only means releasing structurally new code, but it means releasing code that has differing testability characteristics which change our ability to ensure its of the quality you've come to expect. We need to build infrastructure to help us do that, so in the meantime **we've released the new version of the code in beta.**
+
+To get the beta version of Truffle, first uninstall the version you currently have (they'll conflict):
+
+```shell
+$ npm uninstall -g truffle
+```
+
+And now install the beta version:
+
+```shell
+$ npm install -g truffle@beta
+```
+
+You'll notice that the beta version installs almost instantly, and no compilation is required. Hot-dog.
+
+## So what's next?
+
+As we gain responses from the community about this new version we'll likely make changes to ensure we've sidestepped all the installation issues that have plagued users in the past. Once that's finished we'll make an official release. As well, we'll be performing this same work for the TestRPC in the coming weeks to ensure the TestRPC has the same hassle-free, instant installation that you'll soon come to expect from Truffle.
+
+If you run into issues with the beta version, don't hesitate to [write up an issue](https://github.com/trufflesuite/truffle/issues) in our issue tracker or reach out on the [community Gitter channel](https://gitter.im/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions.
+
+Cheers, and we appreciate your ongoing support and feedback.
+
+-- Tim & the Truffle Team
diff --git a/src/blog/introducing-ganache-7/index.md b/src/blog/introducing-ganache-7/index.md
new file mode 100644
index 000000000..f4a7a54af
--- /dev/null
+++ b/src/blog/introducing-ganache-7/index.md
@@ -0,0 +1,310 @@
+---
+title: Ganache 7 Ethereum Simulator - Building on Web3 is now easier and faster than ever before
+hide:
+  - navigation
+---
+
+![ganache v7 banner](/img/blog/introducing-ganache-7/ganache-v7.png)
+
+**By Kingsley Arinze, Mei Chan and David Murdoch**
+
+Ganache is a pioneer in the Ethereum development space, aiding DApp developers and enthusiasts to build, test, and explore blockchain since 2016. We are excited to announce the wide release of the latest version of Ganache today, with 30 times faster forking performance and an Infura integration that allows you to replay historical transactions with free access to archive data.
+
+For the uninitiated, Ganache is a local development blockchain used to develop decentralized applications on the Ethereum blockchain. It simulates the Ethereum network, and you can see how your DApp will perform before you release it to production.
+
+Typically, to start developing distributed applications on the Ethereum network, you will need to set up an Ethereum client such as Geth or OpenEthereum to provide you access to an [Ethereum Virtual Machine (EVM)](https://ethereum.org/en/developers/docs/evm/).
+
+Although that is a great way to develop distributed applications on Ethereum, it is not the most efficient and user-friendly approach, as you need to configure these clients manually and keep them running. Maintaining a self-hosted node can be expensive and time-consuming, you don’t want to spend valuable time troubleshooting a failed node during development.
+
+With Ganache, all you need to do is start the application and you have a preconfigured Ethereum client with 10 pre-funded and unlocked accounts ready for use. This allows you to quickly test your DApp throughout your development cycle.
+
+## Ganache 7: 30x faster forking and operations
+
+Many Web3 developers building on Ethereum already use Ganache to fork and test smart contracts in their local environments for confidence before deployment. Armed with the knowledge gained from previous iterations, we rewrote Ganache from the ground up with the mission to make the blockchain simulator tool even more flexible, faster, and more stable. 
+
+We heard your feedback that Ganache v6 was slow to install, slow to run, and leaked memory. It also didn’t use the modern language features and paradigms developers use today, like TypeScript types and the Promise abstraction. Ganache v6’s architecture made testing, fixing bugs, and adding features difficult and time-consuming.
+
+How is Ganache v7 better?
+
+- With advanced caching capabilities on the latest version, Ganache's forking feature is up to 30 times faster than v6.
+- Zero-config Mainnet forking! Ganache v7 has a [native integration with Infura](https://blog.infura.io/fork-ethereum-replay-historical-transactions-with-ganache-7-archive-support/) which enables free access to historical data
+- You can run Ganache indefinitely without running into crashes due to memory issues
+- Common operations are about 3 times faster than v6.
+
+## Installing and Setting up Ganache 7
+
+Ganache can be used in many ways, including as a command-line tool, programmatically via Node.js, or in the browser. See the instructions below for installing and using Ganache 7 for all these use cases.
+
+### A. Using Ganache 7 On the command line
+
+To run Ganache 7 on the command line, you must have Node.js >= v12.0.0 and NPM >= 6.4.1 installed on your computer. See [here](https://nodejs.org/en/download/) to download the latest version for your operating system, or use nvm to manage your Node installation for [Unix](https://github.com/nvm-sh/nvm) or [Windows](https://github.com/coreybutler/nvm-windows).
+
+With Node.js and NPM installed, you can install Ganache 7 globally by running `npm install ganache --global`. Once installed, you can run `ganache` from anywhere in your command line. 
+
+Your terminal should look like this:
+
+![screenshot-1](/img/blog/introducing-ganache-7/example-1.png)
+
+By default, Ganache provides 10 test accounts, each with 1000 (fake) Ether along with the corresponding private keys and the mnemonic phrase used to generate them. You can use this phrase to import the accounts into wallets like [MetaMask](https://metamask.io/) during development.
+
+We can override all defaults by specifying options when starting Ganache 7; for example, we can have more control over account creation by providing a mapping of private keys to account balances like so:
+
+```
+ganache --wallet.accounts "0xfd485338e322f5930f7cf475f385341ec88bfc4f8a0a16f30b2fb417d1bb5427, 1000000000000000000000" "0x05bba0b9f7a251080aa23feee4eab3f75a1abee905c0271008c93e5d2e2e7541, 10000000000000000000000"
+```
+
+We can also specify a mnemonic phrase to derive all initial accounts from,  a miner gas price, and the block gas limit. For example:
+
+```
+ganache --miner.defaultGasPrice 200 --miner.blockGasLimit 90071 --miner.callGasLimit 898989 --wallet.mnemonic "alarm cause brave super lab glide awake hunt rose win sugar idea"
+```
+
+Run the command `ganache --help` for a list of all the available options you can pass to Ganache.
+
+We can also install ganache into a local Node.js project using  `npm install ganache` without the `--global` flag, then add it to your project’s package.json `scripts`, e.g., `"scripts": {"ganache": "ganache --mnemonic <12 words mnemonic>"}`.
+
+### B. Using Ganache 7 programmatically
+
+Ganache 7 can be used programmatically in your Node.js project as:
+
+- A standalone EIP-1193 provider,
+- A JSON-RPC server and EIP-1193 provider, 
+- A web3.js provider and
+- An ethers.js provider. 
+
+See code samples for these different use cases below.
+
+To begin, install Ganache 7 as  npm package in your Node.js project
+
+```console
+$ npm install ganache
+```
+
+As a standalone EIP-1193 provider
+
+```javascript
+const ganache = require("ganache");
+
+const options = {};
+const provider = ganache.provider(options);
+const accounts = await provider.request({ method: "eth_accounts", params: [] });
+...
+```
+
+As a JSON-RPC web server and an EIP-1193 provider 
+
+```javascript
+const ganache = require("ganache");
+
+const options = {};
+const server = ganache.server(options);
+const PORT = 8545;
+server.listen(PORT, err => {
+  if (err) throw err;
+
+  console.log(`ganache listening on port ${PORT}...`);
+  const provider = server.provider;
+  const accounts = await provider.request({ method: "eth_accounts", params:[] });
+});
+...
+```
+
+As a Web3.js provider
+
+```javascript
+const Web3 = require("web3");
+const ganache = require("ganache");
+
+const web3 = new Web3(ganache.provider());
+...
+```
+
+As an Ethers.js provider
+
+```javascript
+const ganache = require("ganache");
+
+const provider = new ethers.providers.Web3Provider(ganache.provider());
+```
+
+### C. Using Ganache 7 in the browser.
+
+You can use Ganache 7 in the browser by adding the following script tag to your HTML code:
+
+```javascript
+<script src="https://cdn.jsdelivr.net/npm/ganache@7.0.0/dist/web/ganache.min.js"></script>
+```
+
+By doing that, Ganache 7 is automatically available in your browser for use:
+
+```javascript
+const options = {};
+const provider = Ganache.provider(options);
+```
+
+Again, see [here](https://github.com/trufflesuite/ganache#readme) for a list of available options you can pass in.
+
+## New Ganache 7 Features
+
+### 1. Zero-config mainnet forking
+
+Ganache supports mainnet forking out of the box without any configuration, allowing you to simulate having the same state as the Ethereum mainnet, but on your local machine. 
+
+This opens up many possibilities; for example, you can interact with a real-world protocol/contract locally during development, step through, and debug main net transactions locally (using [`truffle debug`](https://trufflesuite.com/docs/truffle/getting-started/using-the-truffle-debugger)), allowing visibility to details about your contract.
+
+[Here's](https://www.reddit.com/r/ethereum/comments/4yd1o4/testrpc_teaser_instantaneous_forking_coming_soon/) a 2016 demo of the Ganache team using the Mainnet forking feature to exploit the [DAO hack](https://www.gemini.com/cryptopedia/the-dao-hack-makerdao).
+
+To use this feature, start Ganache 7 using the `ganache --fork` command. Ganache uses [Infura](https://infura.io/docs) as its provider under the hood by default, but you can also specify a provider by passing a URL; for example, you can use your own Infura URL by running this command:
+
+```console
+$ ganache --fork.url wss://mainnet.infura.io/ws/v3/<PROJECT ID>
+```
+
+Ganache fetches five blocks back from the latest by default to avoid missing blocks due to reordering.
+
+This is a configurable behavior; you can either specify the exact block you want to fork from using `--fork.blockNumber <BLOCK NUMBER>` or by setting `--fork.preLatestConfirmations 0`.
+
+### 2. Fork any Ethereum test network without waiting for sync time
+
+In addition to being able to fork the Ethereum main network with zero configuration, Ganache also allows you to fork from any Ethereum test network, including Ropsten, Kovan, Rinkeby, and Görli. 
+
+You can do that by running the fork command with the network option: `ganache -- fork.network <NETWORK NAME>`. Cool, yeah? Here's what forking from the Rinkeby testnet looks like:
+
+![screenshot-2](/img/blog/introducing-ganache-7/example-2.png)
+
+### 3. Support for massive transaction traces (over 10GB+)
+
+Ganache supports massive transaction tracing using the `debug_traceTransaction` RPC method.
+
+To use this feature, start Ganache by forking off of Mainnet (or any test network) at a block number greater than that of the transaction you're trying to trace; for example, if you want to trace a transaction inside block 13,886,877, you will need to start Ganache at block number 13,886,878: 
+
+```console
+$ ganache --fork.network mainnet --fork.blockNumber <blockNumber>
+```
+
+Then send a curl request using the debug_traceTransaction method specifying the transaction hash like so: 
+
+```console
+$ curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "debug_traceTransaction", "params": [ "<TRANSACTION HASH>" ] }' http://localhost:8545
+```
+
+This would return the aggregated summary of this transaction for post-processing.
+
+Try it with a large transaction like `0x8bb8dc5c7c830bac85fa48acad2505e9300a91c3ff239c9517d0cae33b595090` (Warp Finance hack):
+
+First, start ganache (with lots of extra memory):
+```console
+$ NODE_OPTIONS=--max-old-space-size=16384 ganache --fork --fork.blockNumber 14037983
+```
+
+then execute `debug_traceTransaction` and send the output to trace.json: 
+```console
+$ curl -H 'Content-Type: application/json'   --data '{"jsonrpc":"2.0", "id": 1, "method": "debug_traceTransaction", "params": [ "0x8bb8dc5c7c830bac85fa48acad2505e9300a91c3ff239c9517d0cae33b595090" ] }' http://localhost:8545 -o trace.json
+```
+
+If you really want to test the limits of what's possible (and have a lot of time - about 1-2 hours) try out the 10GB+ Cream Finance hack transaction, `0x0fe2542079644e107cbf13690eb9c2c65963ccb79089ff96bfaf8dced2331c92`!
+
+### 4. Snapshot and Revert state
+
+In blockchain terms, a snapshot refers to the act of capturing and recording the state of a blockchain at a particular block number. A snapshot is the complete view of the blockchain in that specific block and includes all existing addresses and their associated data, including transactions, fees, balance, metadata, etc.
+
+In Ganache, you can take a snapshot of your development blockchain (or even a fork of Mainnet) using the `evm_snapshot` RPC method; it takes no parameters and returns an ID of the snapshot that it creates. 
+
+Ganache also supports reverting state to a previously taken snapshot using the `evm_revert` RPC method, although once a revert is invoked and succeeds, you can no longer use the snapshot with the corresponding ID as you can only revert a snapshot once. 
+
+You should consider creating a new snapshot after every evm_revert if you need to revert to the same point multiple times; here's a demo of taking a snapshot and reverting state in Ganache:
+
+```javascript
+const provider = ganache.provider();
+const [from, to] = await provider.send("eth_accounts");
+const startingBalance = BigInt(await provider.send("eth_getBalance", [from] ));
+
+// take a snapshot
+const snapshotId = await provider.send("evm_snapshot");
+
+// send value to another account (over-simplified example)
+await provider.send("eth_subscribe", ["newHeads"] );
+await provider.send("eth_sendTransaction", [{from, to, value: "0xffff"}] );
+await provider.once("message"); // Note: `await provider.once` is non-standard
+
+// ensure balance has updated
+const newBalance = await provider.send("eth_getBalance", [from] );
+assert(BigInt(newBalance) < startingBalance);
+
+// revert the snapshot
+const isReverted = await provider.send("evm_revert", [snapshotId] );
+assert(isReverted);
+
+// ensure balance has reverted
+const endingBalance = await provider.send("eth_getBalance", [from] );
+const isBalanceReverted = assert.strictEqual(BigInt(endingBalance), startingBalance);
+console.log({isBalanceReverted: isBalanceReverted});
+```
+
+### 5. Mine blocks instantly, at interval, or on demand
+
+Ganache allows you to configure how you want blocks to be mined during development; by default, blocks will be mined immediately upon receiving a transaction, but you can choose between the following options:
+
+- **At interval**: You can specify the time in seconds Ganache should wait before mining the next transaction by passing the `--miner.blockTime <TIME IN SECONDS>` option. A block time of 0 means Ganache should mine new transactions instantly.
+- **On demand**: Ganache also exposes an `evm_mine` RPC method which forces a single block to be mined whether mining is running or stopped. This will mine an empty block if no transaction exists in the mempool. See code sample below:
+
+```javascript
+console.log("start", await provider.send("eth_blockNumber"));
+await provider.send("evm_mine", [{blocks: 5}] ); // mines 5 blocks
+console.log("end", await provider.send("eth_blockNumber"));
+```
+
+### 6. Fast forward time
+
+Ganache exposes two RPC methods for manipulating time on your development blockchain. 
+
+A typical use case would be a smart contract that requires that a specific time passes before users can take certain actions; if the set time isn't something you want to wait for, you can use the `evm_increaseTime` to increase the blockchain current timestamp by the specified amount of time in seconds (passed in as hexadecimal).
+
+```
+curl -H 'Content-Type: application/json' --data' {"jsonrpc": "2.0", "id": 1, "method": "evm_increaseTime", "params": ["0x15180"] }' http://localhost:8545
+```
+
+This returns the total time adjusted in milliseconds. Furthermore, you can use the `evm_setTime` to set it to a specific timestamp; it accepts a JavaScript timestamp (Unix epoch) with millisecond precision and returns the number of seconds between the given timestamp and the current time. 
+
+```
+curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "evm_increaseTime", "params": ["0x15180"] }' http://localhost:8545
+```
+
+You should use this method cautiously as it allows you to move backwards in time, which may cause new blocks to appear to be mined before older blocks, thereby invalidating the blockchain state.
+
+### 7. Impersonate any account
+
+Ganache allows you to impersonate another account during development. This is more interesting when used with the fork feature; you can fork Mainnet and impersonate any account. 
+
+Here's an example of how you can fork Mainnet, impersonate an account, and send some tokens to another account. 
+
+- Start Ganache by forking Mainnet and impersonating (unlocking) a random account: 
+`ganache --fork --wallet.unlockedAccounts <Account Address Here>`
+- Get the balance of the unlocked account: 
+`curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "eth_getBalance", "params": ["<Account Address Here>"] }' http://localhost:8545`. This returns the balance in WEI encoded as a hex number.
+- Send some ether from the unlocked account to another account:
+`curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "eth_sendTransaction", "params": [{"from": "UNLOCKED ACCOUNT", "to": "RECEIVING ACCOUNT", "value": "AMOUNT TO SEND"}] }' http://localhost:8545`
+
+Now verify that the unlocked account's balance has been reduced by the number of Ether sent out.
+
+Sending Ether to another account isn't the only use case as you can impersonate an account to call certain owner-only functions in a smart contract as we did in the convex benchmark contract we saw earlier.
+
+### 8. Pending transactions
+
+In Ethereum, every transaction has a nonce. The nonce is the number of transactions sent from a given address to date, and anytime you send a transaction, the nonce increases by 1. 
+
+For a transaction to be mined, it has to have a nonce greater than that of the previous transaction by 1. In earlier versions of Ganache, if you send a transaction with a nonce greater than the last nonce by more than 1, Ganache would error, and the transaction would be rejected.
+
+With Ganache 7, if the nonce of the previous transaction is 1, and you send a transaction with the nonce set to 3 for whatever reason, this transaction with nonce 3 will sit in the transaction pool until a transaction with nonce 2 is sent, at which time both transactions will be mined and added to the blockchain state.
+
+---
+
+Start using Ganache 7 today by simply running `npm install ganache --global && ganache --help`, or view the [v7 Release Notes](https://github.com/trufflesuite/ganache/releases/tag/v7.0.0).
+
+---
+
+This release has been years in the making and we're really proud of the work we've done. We hope you love it as much as we do.
+
+Thank you to everyone who has been a part of making this release happen — contributors, mentors, reviewers, issue reporters, and community participators have all been instrumental in making Ganache v7. We are immensely thankful to you all.
+
+<p align="center">💖 The Truffle Team</p>
diff --git a/src/blog/introducing-truffle-dashboard/index.md b/src/blog/introducing-truffle-dashboard/index.md
new file mode 100644
index 000000000..1e66e584e
--- /dev/null
+++ b/src/blog/introducing-truffle-dashboard/index.md
@@ -0,0 +1,162 @@
+---
+title: Introducing Truffle Dashboard - Stop copy + pasting your private keys!
+hide:
+  - navigation
+---
+
+![truffle dashboard - banner](//images.ctfassets.net/yfwlmanyz0dl/5NZQV67wUnXWjgNCxmCc9P/56d02491458a533e7eda3db250a33b6e/truffle-dashboard-private-keys.png)
+
+**By [Kingsley Arinze](https://twitter.com/heydamali)**
+
+## Don't get rekt 🙀
+
+One of our core missions at Truffle is to provide tooling that aids in the complete Web3 dapp development lifecycle, while maintaining rigorous security practices throughout. **As a smart contract developer, you require your development tools to keep your sensitive information secret and safe.** At Truffle, we're always looking for ways to make your experience more secure.
+
+If you’ve ever deployed a smart contract, chances are you’ve had to think twice about sharing your private keys with Truffle or other development tools. Maybe you've had to be vigilant not to accidentally share those keys on GitHub. To deploy to an Ethereum network, you've needed to copy your wallet credentials and store them in an insecure location to share with a tool like HDWalletProvider. **This has been necessary because your mnemonic or private key gives Truffle the permissions it needs to sign transactions on your behalf.**
+
+<figure markdown>![Screenshot of an example truffle-config.js using HDWalletProvider with hardcoded mnemonic and Infura key.](/img/blog/introducing-truffle-dashboard/secrets-oh-no.png)
+  <figcaption>Have you ever had to do something like this?</figcaption>
+</figure>
+
+**Storing your mnemonic seed phrase or private keys in regular files poses a considerable security concern.** Your seed phrase can easily be hijacked by JavaScript code, accidentally committed to Git, or targeted by bad actors.
+
+## Enter Truffle Dashboard 🔥 🚀
+
+Truffle Dashboard completely removes the need to manually interact with your wallet's mnemonic phrase or private keys throughout the development lifecycle.  **You can now safely deploy your smart contracts to your network of choice without Truffle ever needing to know what your keys look like.** Truffle seamlessly connects to your MetaMask wallet without any configuration, using the currently selected account and network for Truffle's deployment configuration.
+
+_But that's not all!_ For your convenience, **you can use Truffle Dashboard with any development tool.** For example, if you use Hardhat or Foundry to develop your smart contracts, you can also integrate with Truffle Dashboard for this improved security workflow. See the [Using Truffle Dashboard with other development tools](/docs/truffle/getting-started/using-the-truffle-dashboard) section of our docs to learn how.
+
+## How does Truffle Dashboard Work? ⚙️🔧
+
+If you're new to Truffle, ensure you have Node.js then install the latest version of Truffle with the following command:
+
+```console
+npm install -g truffle
+```
+
+If you already have Truffle installed, you want to first uninstall your existing instance of Truffle globally:
+
+```console
+npm uninstall -g truffle
+npm install -g truffle
+```
+
+### Running Truffle Dashboard 🚀
+
+With the latest version of Truffle, in addition to all previously existing `truffle <...>` commands, you will see a new `truffle dashboard` command.
+
+Running `truffle init` walks you through the process of setting up a new truffle project.
+
+Running `truffle dashboard` in a separate terminal window starts Truffle Dashboard at `http://localhost:24012` and automatically opens a new tab in your existing browser session.
+
+![truffle dashboard - start from the cli](/img/blog/introducing-truffle-dashboard/truffle-dashboard-cli.png)
+
+You can also configure the port and host to run Truffle Dashboard in one of two ways:
+
+  - On the command line:
+
+    ```console
+    truffle dashboard --port <Port of choice> --host <Host of choice>`
+    ```
+
+  - In your Truffle configuration (truffle-config.js) file:
+
+    ```javascript
+    module.exports = {
+      /* ... rest of truffle-config.js ... */
+
+      dashboard: {
+        port: 25012,
+        host: "localhost"
+      }
+    }
+    ```
+
+See the [Truffle Commands](/docs/truffle/reference/truffle-commands.html) and/or the [Configuration](/docs/truffle/reference/configuration.html) reference documentation to learn more.
+
+### Connecting your wallet 🤝
+
+Truffle Dashboard requires you to connect your wallet to get started. Click the "Connect Wallet" button and connect Truffle Dashboard to your wallet the same way you would for any other dapp.
+
+![truffle dashboard - connect wallet](/img/blog/introducing-truffle-dashboard/truffle-dashboard-connect-wallet.png)
+
+Next, Truffle Dashboard prompts you to confirm that you are connected to the correct network, since it uses the wallet's default active network. Make sure you switch to the desired network before confirming. Every transaction you process will be sent to the confirmed network.
+
+![truffle dashboard - confirm](/img/blog/introducing-truffle-dashboard/truffle-dashboard-confirm.png)
+
+During development, a typical workflow is first to deploy and test out your smart contract code on a development blockchain like [Ganache](https://trufflesuite.com/ganache) before deploying to your favorite test network.
+
+You can still maintain this workflow with Truffle Dashboard by simply importing Ganache’s local blockchain network into your MetaMask wallet as usual and pointing Truffle Dashboard to use it as your confirmed network.
+
+![truffle dashboard - select network](/img/blog/introducing-truffle-dashboard/truffle-dashboard-select-network.png)
+
+### Using Truffle Dashboard in your Truffle project 🎉
+
+Before Truffle Dashboard was available, if you wanted to connect to a network like Rinkeby or Mainnet from your Truffle project, you had to specify some configuration variables in the network section of the truffle-config.js file.
+
+```javascript
+module.exports = {
+  /* ... rest of truffle-config.js ... */
+
+  networks: {
+    development: {
+      host: "localhost",
+      port: 8545,
+      network_id: "*"
+    },
+
+    ropsten: {
+      // ...
+    },
+
+    mainnet: {
+      // ...
+    }
+  }
+};
+```
+
+With Truffle Dashboard, you do not need any of that, as Truffle now exposes a built-in network named `"dashboard"` which runs on whatever port and host your Truffle Dashboard is running on (`http://localhost:24012` by default). With Truffle Dashboard running and connected to MetaMask, you can simply supply the `dashboard` keyword to any Truffle command that requires you to specify a network. For example:
+
+```console
+truffle migrate --network dashboard
+truffle console --network dashboard
+```
+
+When you run the above commands (or any RPC request), Truffle forwards your request from the command-line to the browser, where you can inspect it and choose to process or reject with MetaMask.
+
+![truffle dashboard - process transaction](/img/blog/introducing-truffle-dashboard/truffle-dashboard-sign.png)
+
+As with every zero-configuration feature, you are allowed to override the default configuration by adding a network called `dashboard` to your Truffle configuration file and specifying its options as you would for other networks. See the [`networks` configuration](/docs/truffle/reference/configuration.html#networks) reference documentation for more information.
+
+### Using Truffle Dashboard with other development tools 👪
+
+Although we developed Truffle Dashboard intending to improve the development experience for those who choose to build with Truffle, we made sure to make it tool-agnostic. So if Truffle isn't your development tool of choice for developing smart contracts (why on earth should it not be? C'mon, now let's talk!), but you'd like to integrate the Dashboard into your workflow, we've got you covered.
+
+You can use Truffle Dashboard with other development tools. For example, use it with Hardhat by simply starting Truffle Dashboard in a separate terminal window and add a network configuration option that points to Truffle Dashboard's RPC URL in your Hardhat config file:
+
+```js
+module.exports = {
+  // ...
+
+  networks: {
+    // ...
+
+    "truffle-dashboard": {
+      url: "http://localhost:24012/rpc"
+    }
+  },
+};
+```
+
+With this setup, when you run the command `hardhat deploy --network truffle-dashboard`, the request is forwarded to Truffle Dashboard, where you can inspect and process them.
+
+## Conclusion ❤️️
+
+**With Truffle Dashboard, you no longer have to worry about giving your private keys to someone else's JavaScript code.** You can now relax and leave it up to MetaMask to keep your private keys safe and sign transactions on your behalf.
+
+To get started, download the latest version of Truffle and start using Truffle Dashboard today by running the command `npm uninstall -g truffle && npm install -g truffle`.  Please refer to the [Truffle Dashboard](/docs/truffle/getting-started/using-the-truffle-dashboard.html) feature documentation for more.
+
+Truffle Dashboard was borne out of our years of experience working on developer tools for the Ethereum ecosystem and receiving valuable feedback from our users. We are extremely excited to release this feature. We hope you're excited to try it out.
+
+With ❤️️ from the Truffle team. Questions/comments/concerns? Please shoot us a tweet [@trufflesuite](https://twitter.com/trufflesuite)!
diff --git a/src/blog/introducing-truffle-db-part-1/index.md b/src/blog/introducing-truffle-db-part-1/index.md
new file mode 100644
index 000000000..5f51819bb
--- /dev/null
+++ b/src/blog/introducing-truffle-db-part-1/index.md
@@ -0,0 +1,54 @@
+---
+title: Introducing Truffle DB, Part 1 - Artifact archeology
+hide:
+  - navigation
+---
+
+## Introducing Truffle DB, part 1: Artifact archeology
+Truffle is not a small utility: it compiles your contracts, deploys them to multiple networks, runs your automated tests, provides an interactive debugger for when things go wrong, offers a library for interacting with your contracts on the frontend, … (*the list goes on.*) With just over 20,000 lines of code and close to thirty discrete software packages, Truffle has a lot going on.
+
+Truffle is “not small” on purpose. The tool oversees the development lifecycle in human developer terms. It keeps track of familiar concepts and hides unnecessary, low-level specifics. That’s a big goal.
+
+So how does this work? Well, Truffle tries to be smart about it. It stores information about your contracts so that it can refer to it later. It tracks compilation results alongside the source code you wrote, maintaining a steady mapping between *data for the blockchain* and *data for developers’ brains*.
+
+Right now, this system of record-keeping is served through Truffle’s **contract artifacts**: the large JSON files that get saved in your *build/contracts/* directory. Truffle saves your artifacts when you compile and updates your artifacts with address information when you migrate. Pretty much whenever you use any part of Truffle, these artifacts are read from disk and processed, enabling Truffle to paint itself (and you) a picture of what’s happening in human terms.
+
+Truffle’s artifacts have been enormously useful: the tool simply couldn’t exist without this kind of first-class data capturing. Beyond that, though, being able to count on this data has enabled an ecosystem of other tools and utilities that build on top of Truffle’s functionality using Truffle’s artifacts format. Truffle’s artifacts have served as a common language for representing smart contract development concepts.
+
+Unfortunately, Truffle’s artifacts format has a number of core limitations that prevent Truffle from offering ideal behavior in several key situations. This post describes a few of these limitations. In this post’s follow-up, we’ll share information about a new system to manage this record-keeping, which we’re calling **Truffle DB**.
+
+## So what’s the problem now?
+For starters: artifact files are huge! Too huge! In addition to Truffle reading your contract artifacts, your dapp’s frontend code may read and use your artifacts to let users connect to any deployed network, etc. Problem is—there’s a ton of JSON. It’s a mess, and it’s in your face too much.
+
+<figure>
+  <img src="/img/blog/introducing-truffle-db/example-truffle-db.png" alt="Example of Truffle DB" style="width:100%">
+  <figcaption>**For example:** Truffle stores the same abstract syntax tree* (AST) in two different formats, in every single artifact! Most applications do not need this.
+
+  *for the curious: the AST is the reason your code works whether you wrote it all on a single line or not. Source gets parsed, and the AST is the result. Truffle and other tools rely on the AST for things like debugging, code coverage, and linting.</figcaption>
+</figure>
+
+By the byte, almost all of the information in each contract artifact is for internal use or for some specific purpose. **Only a small subset of the data in each artifact is necessary for your frontend or for you to think about directly.** Thus far, users who have struggled with these large files needed to use a tool like [jq](https://stedolan.github.io/jq/) or write a custom solution.
+
+In addition to these files being too large, the information is grouped purely by the idea of “contract name”. What if you want to have two contracts with the same name? You can’t. What if you want to debug an old version of your contract, deployed to a testnet? I hope you backed up your old artifacts directory somehow.
+
+Although we’ve implemented plenty of workarounds to deal with these limitations, the problems do not go unnoticed. See some long-outstanding open GitHub issues, for example:
+* [Truffle contract artifacts are too big and contain too much sensitive detail to actually deploy on the web (#1269)](https://github.com/trufflesuite/truffle/issues/1269)
+* [Artifact is overwritten if there are two contracts with the same name (#1087)](https://github.com/trufflesuite/truffle/issues/1087)
+* [Source map indexes are missing in artifacts (#1236)](https://github.com/trufflesuite/truffle/issues/1236)
+* [Allow persistency of artifacts remotely (#1790)](https://github.com/trufflesuite/truffle/issues/1790)
+
+Unfortunately, these issues are blocked by the fundamental design of the contract artifacts.
+
+The root of the problem is that Truffle’s artifacts try to serve two conflicting purposes: they try to serve the developer, but they also try to serve the tool itself.
+
+## “Stop talking about data formats”, you say.
+
+Right? Ideally, Truffle should silently keep complete records of everything you will ever need, and nothing more. And you, the developer, should only ever come face-to-face with the information you need at any given moment.
+
+So, for some time, we have been working on a plan to improve the state of affairs of Truffle’s record-keeping.
+
+We’ll get into it more in the next post, but Truffle DB aims to provide two things:
+* a data model: a set of terms that collectively represent various, high-level concepts associated with smart contract development
+* a flexible interface: a way to query and update your Truffle project’s records
+
+In doing this, we’re taking a data-first approach, organizing your project’s information through immutable records and a clean separation of concerns. Stay tuned for the next post, where we’ll talk about this more and outline our release plan for Truffle DB: what we’ll be releasing first, what work still needs to be done, and how we plan to handle backwards compatibility over time.
diff --git a/src/blog/introducing-truffle-db-part-2/index.md b/src/blog/introducing-truffle-db-part-2/index.md
new file mode 100644
index 000000000..c5d738bb6
--- /dev/null
+++ b/src/blog/introducing-truffle-db-part-2/index.md
@@ -0,0 +1,110 @@
+---
+title: Introducing Truffle DB, part 2 - 'Weight and Switch'
+hide:
+  - navigation
+---
+
+Welcome back! If you missed the [first part](/blog/introducing-truffle-db-part-1) of this post, you may want to read it to learn more about Truffle’s contract artifacts, their current limitations, and why we seek to build a better solution.
+
+Or, just to catch up:
+* Truffle currently stores information about your smart contracts in files that we call “contract artifacts” (or just “artifacts” for short.)
+* Truffle uses these artifacts for pretty much everything.
+* Plenty of other tools use artifacts too, and rely on their behavior.
+* Unfortunately, the artifacts file format has several design flaws, forcing dozens of workarounds and even preventing certain use cases entirely.
+* Addressing these flaws head-on risks severe negative impact on other projects.
+* We’re excited to share a project we’ve been working on, to offer a deprecation plan and to encourage community involvement.
+
+So why should you care?
+* If you are a tools developer, or rely on Truffle artifacts directly in any way: there will be breaking changes!
+* If you use Truffle for smart contract development: the developer experience using Truffle will have fewer roadblocks (“[software warts](https://www.catb.org/jargon/html/W/wart.html)”). This will not break existing Truffle projects.
+* No matter who you are: better data means better tools.
+
+Great! I’m convinced. 😁 Now, where were we?
+
+## What is Truffle DB?
+
+Truffle DB comprises two key ideas, currently at different stages of development. These are:
+
+1. A data model for organizing your project’s smart contracts: how to keep track of all the different pieces of information, from your contract source files to where they are deployed.
+1. A flexible JSON data access interface: how to read exactly the data you need and how to update the DB with the data you have.
+
+### Data model
+
+<figure>
+  <img src="/img/blog/introducing-truffle-db/truffle-db-data-model.png" alt="Truffle DB data model" style="width:100%">
+  <figcaption>**Data model excerpt**: how contracts, sources, compilers, and compilations all relate. ([Text-accessible version](https://github.com/trufflesuite/artifact-updates/blob/master/docs/uml/macros.iuml) available via diagram source)</figcaption>
+</figure>
+
+What is a smart contract? What is your contract’s bytecode, what is its source code, and how do they relate? By looking at how Truffle expects these relationships in practice, and considering how these concepts are commonly understood, we hope to make life easy by creating a shared vocabulary for interacting with the smart contract domain.
+
+Diagrams are worth more than words here, so please check out our data model docs to get a broader sense for what this represents.
+
+**Current status**: Implemented as minimally viable, designed to be extended.
+
+### Flexible interface
+
+<figure>
+  <img src="/img/blog/introducing-truffle-db/concept-query.png" alt="Example of Truffle DB" style="width:100%">
+  <figcaption>**Concept image**: Example query to fetch specific project contract info. ([See gist for image text](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-concept-query-graphql))</figcaption>
+</figure>
+
+Truffle DB uses [GraphQL](https://graphql.org) for its primary interface. GraphQL affords flexibility and a data-first design methodology that suits our goals well. This interface is intended for use in tools to build on top of Truffle; as a normal user you won’t have to touch this. (Of course, we hope this will encourage you to find new ways to solve problems by building and sharing tools of your own!)
+
+Truffle DB is still in development, but we would like to share what we’ve got so far and to talk about where we’re looking to go. Although it’s early, we want to increase awareness about future breaking changes, and we hope to paint a picture of some new foundations that we’re excited will help the smart contract development tools ecosystem.
+
+**Current status**: Internal infrastructure in place, prototyping for public review to begin soon.
+
+## What we’re releasing first
+
+We’re gearing up for a minor release (Truffle v5.1), and we plan to make a first version of Truffle DB available as an experimental implementation. This means building blocks to start: key pieces of infrastructure to paint a picture of Truffle DB for review and iteration.
+
+Day 1, this means you will get:
+* The ability to convert your artifacts and load them into Truffle DB
+* A mechanism to persist Truffle DB data side-by-side with your artifacts
+* Improvements to Truffle that take advantage of this data when it exists
+* A bundled GraphQL playground for hands-on exploration
+* The ability to easily explore the schema to better understand our system design
+
+<figure>
+  <img src="/img/blog/introducing-truffle-db/graphql-playground.png" alt="Example of Truffle DB" style="width:100%">
+  <figcaption>**Interact with Truffle DB**: Apollo’s [GraphQL Playground](https://www.apollographql.com/docs/apollo-server/features/graphql-playground/) provides a handy way to work with GraphQL interfaces. We’re bundling a Playground instance into Truffle DB to make it easier to learn about.
+(For text-accessible version, see [query source](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-graphql), [query variables](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-result-json), and the [query result](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-result-json))</figcaption>
+</figure>
+
+## What’s left to be done (soon)
+
+Since we’ve started by building infrastructure, the work remains to connect the dots into a final design that we can validate for quality and usefulness.
+
+This includes:
+* Documentation, of course! See our current [Truffle DB – Proposal](https://trufflesuite.github.io/artifact-updates/index.html) working docs, which include the data model diagrams. Expect us to convert these docs into proper documentation for release.
+* Better persistence. Our initial implementation will save JSON files to disk, but we intend to support more robust data storage options, including relational databases and native support in [Truffle Teams](/docs/teams/overview).
+* Schema design updates, including support for pagination and proper data filtering.
+* A prototype candidate for Truffle DB’s external interface.
+
+## The long-term plan
+
+We’re going to introduce Truffle DB gradually, deprecating the old artifacts format and introducing Truffle DB more and more as it’s validated.
+
+We expect to follow these steps:
+1. Release initial Truffle DB features as opt-in and experimental.
+1. Gather feedback and support to build a cohesive Truffle DB release candidate (for broad community use).
+1. Turn Truffle DB on by default, but continue to use artifacts as the primary data store.
+1. Convert the rest of Truffle to use Truffle DB as its primary data store, but continue to maintain artifacts alongside it for compatibility.
+1. Continue to maintain both data stores, and switch to using Truffle DB to manage artifacts (instead of existing artifacts management code).
+1. Turn off artifacts by default, but maintain legacy support through configuration.
+1. Eventually, remove artifacts altogether.
+
+We expect this process, start to finish, to span at least two major (breaking change) releases. We plan to maintain legacy support for artifacts for at least 18 months after we release a Truffle DB release candidate.
+
+<figure>
+  <div style="width:100%;height:0;padding-bottom:43%;position:relative;"><iframe src="https://giphy.com/embed/26tPcRGbvMEcKmrRe" width="100%" height="100%" style="position:absolute" frameBorder="0" class="giphy-embed" allowFullScreen></iframe></div><p><a href="https://giphy.com/gifs/film-cinemagraph-26tPcRGbvMEcKmrRe">via GIPHY</a></p>
+  <figcaption>[Weight and Switch](https://tvtropes.org/pmwiki/pmwiki.php/Main/WeightAndSwitch): Dr. Jones demonstrating proper technique for delicate data migration procedures</figcaption>
+</figure>
+
+## What do you think?
+
+Please reach out with questions/thoughts/use case ideas/implementation strategies, or even just to say hello. Your feedback will help us provide the most value and make sure we do so with enough clarity!
+
+We’re tracking overall progress in this [GitHub issue (trufflesuite/truffle#1718)](https://github.com/trufflesuite/truffle/issues/1718). Expect to see this filled out more in the coming weeks, so please follow along there if you’re interested.
+
+Thanks for reading! Hope to see you at TruffleCon!
diff --git a/src/blog/iterate-faster-with-truffle-teams/index.md b/src/blog/iterate-faster-with-truffle-teams/index.md
new file mode 100644
index 000000000..800f61d5e
--- /dev/null
+++ b/src/blog/iterate-faster-with-truffle-teams/index.md
@@ -0,0 +1,87 @@
+---
+title: Iterate Faster with Truffle Teams
+hide:
+  - navigation
+---
+
+Consider the amount of context switching required to develop a dapp: you’re writing Solidity one minute, writing tests another, debugging those results--it’s easy to get lost! These switches carry a cognitive load and when errors equal a loss of ETH we need all the help we can get. I’m happy to inform you Truffle Teams can help reduce context switching and help you or your team iterate faster.
+
+Truffle Teams has reached a very important stage in its life: it now provides a complete workflow including building, testing, managing, monitoring, and debugging. This means you’re getting a huge boost in productivity. This amounts to a more robust workflow for you and/or your team and contributes to the application lifecycle generally by tightening the feedback loop between deployment, operation, and debugging all within a flexible development network.
+
+<figure>
+  <img class="mb-4 w-100" src="/img/blog/iterate-faster-with-truffle-teams/dev-lifecycle.png" alt="The development lifecycle: plan, code, build, test, release, deploy, operate, and monitor.">
+  <figcaption class="text-center font-italic">The development lifecycle.</figcaption>
+</figure>
+
+Up to this point, Truffle Teams has already offered a builds system, deployment manager, blockchain sandboxes, and monitoring. Recently we released a visual debugger into early access. With that, we’d like to highlight two features that completed this cycle: the Debugger and the Contract Manager.
+
+For a great video example, check out our demo from TruffleCon 2020. We briefly touch all the phases talked about above using a rock, paper, scissors game. For something more long-form, check out our 5-part webinar series walking you through using the Truffle suite to create an NFT and trade it on a decentralized marketplace.
+
+<figure>
+  <a href="https://www.youtube.com/watch?v=LsQ2Iwd5VMc" target="_blank">
+    <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/teams-demo-tcon-2020.jpg" alt="The video thumbnail for Josh Quintal and Mike Seeses demo of Truffle Teams at TruffleCon 2020.">
+    <figcaption class="text-center font-italic">Mike Seese and Josh Quintal go over the entire development lifecycle using Truffle Teams for a decentralized rock, paper, scissors dapp.</figcaption>
+  </a>
+</figure>
+
+## Debugger Enhancements
+
+<p class="alert alert-info">
+  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the debugger right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
+</p>
+
+Truffle offers a sophisticated forensic transaction debugger and allows you to extract the most information and context possible from your transactions. We released a graphical version of our command line debugger into Truffle Teams Early Access in December. Since then we’ve added syntax highlighting and breakpoints for an improved developer experience. Readability increases and you control where execution stops, providing a precision debugging experience. Check out the Truffle Teams debugger docs to learn more about breakpoints. Currently the debugger in Truffle Teams only works for sandbox environments, but we plan on supporting public networks next!
+
+</div></div></div>
+
+<figure class="breakout">
+  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/debugger.png" alt="The Truffle Teams debugger working on an NFT-based badge contract">
+  <figcaption class="text-center font-italic">The Truffle Teams Debugger--now with syntax highlighting and breakpoints!</figcaption>
+</figure>
+
+<div class="container container-post"><div class="row justify-content-center"><div class="col">
+
+## The Contract Manager
+
+<p class="alert alert-info">
+  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the contract manager right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
+</p>
+
+Truffle Teams’ Contract Manager generates a UI for interacting with all the functions of your smart contracts, as well as a live state tree so you can quickly see the changes propagated by those functions. If you’re familiar with Remix, you’ll feel right at home here.
+
+</div></div></div>
+
+<figure class="breakout">
+  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/contract-manager.png" alt="The Truffle Teams Contract Manager using an NFT-based badge contract">
+  <figcaption class="text-center font-italic">The Contract Manager; shown here using an NFT badge.</figcaption>
+</figure>
+
+<div class="container container-post"><div class="row justify-content-center"><div class="col">
+
+The Contract Manager is great for quick demos, integration tests, and a faster, all-GUI debugging workflow. For example, you can deploy to a sandbox via the deployment wizard, hop over to the contract manager to fire off a few transactions, and finally debug these transactions from the monitoring screen.
+
+## Dapp Topography
+
+Going forward, we’ll be helping you understand your dapp on an even deeper level, offering forensic-level analysis of your transactions. Not only that, but it will be able to diagram contract interaction to allow different stakeholders to participate in the debugging process. For example a product manager, or other domain expert can participate in the forensic analysis. These diagrams and other assets can be shareable media that can fit into existing communication channels.
+
+</div></div></div>
+
+<figure class="breakout">
+  <img class="mb-4 w-100 w-md-70" src="/img/blog/iterate-faster-with-truffle-teams/ens-plant-uml.png" alt="Plant UML diagram of an ENS transaction">
+  <figcaption class="text-center font-italic">A test in which a user who isn't the owner of an ENS name attempt to change the resolver. Note the "X" shoing the revert.</figcaption>
+</figure>
+
+<div class="container container-post"><div class="row justify-content-center"><div class="col">
+
+## Get Started with Truffle Teams
+
+We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Check out Truffle Teams today and let us know what you think about the new deployment views and contract manager, or if your team has other needs we haven’t met yet.
+
+<div class="mt-3 mb-4 text-center">
+  <a class="btn btn-truffle" href="https://my.truffleteams.com">SIGN UP FOR THE TRUFFLE TEAMS</a>
+  <a class="btn btn-truffle" href="/docs/teams/quickstart">TRUFFLE TEAMS QUICKSTART</a>
+</div>
+
+Thanks!
+
+_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md b/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
new file mode 100644
index 000000000..047487be5
--- /dev/null
+++ b/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
@@ -0,0 +1,30 @@
+---
+title: Learn Ethereum The Fun Way with our Pet Shop Tutorial
+hide:
+  - navigation
+---
+
+Here at Truffle we want to make Ethereum development accessible to developers of all stripes. To that end, today we're releasing a new tutorial called [Pet Shop](/tutorial). It covers the entire local development process, start to finish. For added fun, we've tied the whole thing together within the narrative of creating a pet adoption dapp for a local pet shop owner.
+
+Here's a preview of what's covered:
+
+* Setting up The Development Environment
+* Creating a Truffle Project using a Truffle Box
+* Writing and Testing a Smart Contract
+* Creating a UI to Interact with our Smart Contract
+
+By then end of the tutorial you'll have a shiny new dapp with which you can reserve pets for adoption.
+
+![The Completed Pet Shop Dapp](/img/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/pet-shop-preview.jpeg "The completed dapp.")
+
+In the future we'll be building on this tutorial with others such as deploying to live testnets and additional, more advanced functionality. We hope you enjoy and thank everyone for your support!
+
+Got stuck? The fastest way to get help is from our [community Gitter channel](https://github.com/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions.
+
+Love it? Send us your feedback on [Twitter](https://twitter.com/trufflesuite).
+
+Found a problem? Let us know by raise a [GitHub issue](https://github.com/trufflesuite/trufflesuite.com/issues) if there's something you think we can improve! Pull requests are always welcome!
+
+Cheers!
+
+-- Josh & the Truffle Team
diff --git a/src/blog/one-hundred-documentation-pull-requests/index.md b/src/blog/one-hundred-documentation-pull-requests/index.md
new file mode 100644
index 000000000..347a0cbdb
--- /dev/null
+++ b/src/blog/one-hundred-documentation-pull-requests/index.md
@@ -0,0 +1,40 @@
+---
+title: One hundred documentation pull requests? Yes please.
+hide:
+  - navigation
+---
+
+Greetings! The Truffle team has been growing over the course of the last year. From a single developer, we are now a team of five (soon to be even more), which means that we can spread the work around.
+
+As a new full-time member of the team, I've first taken to looking at our existing materials to ensure that everything is up-to-date and working well.
+
+For example, our website, a public GitHub repository, had been receiving pull requests (PRs) for the better part of a year, and they had been languishing for want of someone to go through them.
+
+We're not talking a few or even a dozen. We're talking **almost 100 PRs**.
+
+All I can say is: **wow**.
+
+I've been working in the open source software world for about a decade, and I've never seen so many people freely offering suggestions to documentation. As we all ruefully know, documentation can be first to go out of date and last to be updated, so knowing that our community is keeping such an eagle eye on even minute details says a lot.
+
+And I do mean *minute details*. When one of our tutorials wrote "tag a stab" instead of "take a stab", not less than [ten of you took the time to submit pull requests](https://github.com/trufflesuite/trufflesuite.github.io/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aclosed%20tag%20take) telling us so.
+
+</div><div class="text-center container">
+  ![Take a stab, indeed](/img/blog/one-hundred-documentation-pull-requests/take-a-stab.png)
+  <p class="caption">Take a stab indeed</p></br></br>
+</div><div class="container container-narrow">
+
+Make no mistake: this is good thing. I believe in the [Broken Windows theory](https://en.wikipedia.org/wiki/Broken_windows_theory) as it applies to documentation. **We want to fix up the small things now so we can maintain the larger things more easily in the future.**
+
+We have big plans for our content here, just like we have big plans for Truffle. (Check out the new features coming in Truffle 4 (<https://github.com/trufflesuite/truffle/releases/tag/v4.0.0-beta.0>)!) And note that [we have since separated out the website source code to its own repository](https://github.com/trufflesuite/trufflesuite.com) to make submissions easier for the community.
+
+I'm happy to be part of a community that cares about what we're doing, reducing the bar to developing Ethereum dapps, and making them delicious.
+
+As for your suggestions on how we can serve you even better? Please keep them coming. Submit a pull request to our documentation, reach out on [Twitter](https://twitter.com/trufflesuite), or let us know if there's something we can improve by raising a [GitHub issue](https://github.com/trufflesuite/trufflesuite.com/issues).
+
+Need help with something? Reach out on our [community Gitter channel](https://github.com/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions. 
+
+-- Mike & the Truffle team
+
+-----
+
+*Mike Pumphrey is an Enterprise Trainer at ConsenSys working on the Truffle team. With over a dozen years of experience in documentation, support, and training, Mike is passionate about making technical concepts understandable to a wider audience. He believes that great software can only be great when people know how to use it, and is excited to be bringing clarity to a field as exciting and new as blockchain.*
diff --git a/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md b/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
new file mode 100644
index 000000000..9f271eacd
--- /dev/null
+++ b/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
@@ -0,0 +1,96 @@
+---
+title: Open call for contributions by Truffle + PegaSys - EEA private transactions
+hide:
+  - navigation
+---
+
+# Open call for contributions by Truffle + PegaSys: EEA private transactions
+![Pegasys Truffle Open Call For Contributions](https://i.imgur.com/GLw8iok.jpg)
+
+## What's missing?
+
+In its current state, Truffle doesn't support EEA private transactions. Support for the web3js-eea library is needed for this to work and PegaSys has recently made an implementation of the v4.0 EEA specification.
+
+## Why did this happen?
+
+The `interface-adapter` in Truffle’s codebase doesn’t provide an adapter for the  EEA 4.0 client spec, therefore private transactions aren’t working.
+
+The EEA client specification is a developing specification and  Truffle has not yet implemented the EEA client specification around private transactions.  PegaSys is providing an implementation of the specification for private transactions.  Pegasys and Truffle are teaming up to ensure that Truffle supports the EEA JSON RPC API methods.
+
+## What's the solution?
+PegaSys and Truffle have teamed up to make a single open call for contributions. This guest blog post is made by the PegaSys team and is to be posted on the Truffle blog and promoted by both teams in order to add code to Truffle codebase to add support for them.
+
+The solution involves using a Delegation pattern to help make that work.
+
+The location of the files to be modified can be found here:
+[truffle/packages/interface-adapter/lib](https://github.com/trufflesuite/truffle/tree/develop/packages/interface-adapter/lib)
+
+In short, when Truffle receives a transaction, it should determine if its a `privateFor` transaction. If so, it would delegate the rest of the business logic to the EEA library. If not, it should just continue processing the transaction with the original web3 methods.
+
+Also, it would be very useful to make sure this plays nicely with the getTransactionReceipt methods later in the chain of events.
+
+## What to do Exactly?
+
+The initial process involves adding an EEA definition to the shim file. The `web3-shim.ts` file currently contains the overloads for the different interface definitions and their mappings.
+
+``` typescript
+import { EthereumDefinition } from "./ethereum-overloads";
+import { QuorumDefinition } from "./quorum-overloads";
+import { FabricEvmDefinition } from "./fabric-evm-overloads";
+
+const initInterface = async(web3Shim: Web3Shim) => {
+
+    const networkTypes: NetworkTypesConfig = new Map(Object.entries({
+      "ethereum": EthereumDefinition,
+      "quorum": QuorumDefinition,
+      "fabric-evm": FabricEvmDefinition
+    }));
+
+    networkTypes.get(web3Shim.networkType).initNetworkType(web3Shim);
+  }
+```
+
+The initial import and mapping has been done [in this fork](https://github.com/faraggi/truffle).
+
+``` typescript
+import { EthereumDefinition } from "./ethereum-overloads";
+import { EEADefinition } from "./EEA-overloads";
+import { QuorumDefinition } from "./quorum-overloads";
+import { FabricEvmDefinition } from "./fabric-evm-overloads";
+
+const initInterface = async(web3Shim: Web3Shim) => {
+
+    const networkTypes: NetworkTypesConfig = new Map(Object.entries({
+      "ethereum": EthereumDefinition,
+      "EEA": EEADefinition,
+      "quorum": QuorumDefinition,
+      "fabric-evm": FabricEvmDefinition
+    }));
+
+    networkTypes.get(web3Shim.networkType).initNetworkType(web3Shim);
+  }
+```
+
+The [rest of the owl](https://i.imgur.com/4fVoQoQ.png) is to add the needed logic in the `eea-overloads.ts` file and the `overrides` variable for it to interact with the [web3eeajs library](https://www.npmjs.com/package/web3-eea).
+
+![PegaSys owl](https://i.imgur.com/4fVoQoQ.png)
+
+## Who can do this?
+
+Anyone who'd like to try can very much do so we will gladly support any developer who wants to help out.
+But here are some recommended prerequisites:
+
+The Truffle codebase is mainly written in `javascript`, and this particular interface-adapter library we'll be looking at is written in `typescript`.
+So knowing some javascript is a must.
+
+It will definitely help if you've had some exposure and usage of the Truffle library. Nothing fancy, just using it for compiling and deploying contracts for example.
+Likewise, having some previous knowledge of the web3js library is going to prove quite helpful.
+
+All of the above somewhat describes a general dapp developer- so in other words; if you've already written a dapp before using Truffle, this contribution could be done by you.
+
+So what's in it for you?
+Two things:
+- You'll receive some 😎 PegaSys Swag!
+- We'll personally thank and credit you on stage at [Trufflecon at my Permissioning  Talk](https://twitter.com/trufflesuite/status/1150929297647034374)
+
+For more information or help on this contribution, contact [Felipe](mailto:felipe.faraggi@consensys.net) from [PegaSys](https://pegasys.tech),  or write us on [our gitter channel](https://gitter.im/PegaSysEng/pantheon).
diff --git a/src/blog/removing-installation-issues-continued-testrpc/index.md b/src/blog/removing-installation-issues-continued-testrpc/index.md
new file mode 100644
index 000000000..52429e4a9
--- /dev/null
+++ b/src/blog/removing-installation-issues-continued-testrpc/index.md
@@ -0,0 +1,41 @@
+---
+title: Removing installation issues, con't - TestRPC
+hide:
+  - navigation
+---
+
+<p class="alert alert-info">
+**Update**: Since this blog post was published, we have released [Ganache](/ganache) a personal blockchain and a replacement to the TestRPC. We have left this post unaltered, but we highly recommend checking out our [Ganache Quickstart](/docs/ganache/quickstart) page.
+</p>
+
+If you've been following along, you'll know that we recently [removed most if not all installation issues from Truffle](/blog/how-were-making-installation-issues-a-thing-of-the-past). For us it was a pretty big deal: Installation issues were, by far, the number one issue plaguing new users on any platform. We thought our solution was novel, so we blogged about it, and the biggest reaction we received from users was, "This is awesome, thank you! But can you do it for the TestRPC too?" Well you asked, and today we delivered.
+
+The [TestRPC](https://github.com/ethereumjs/testrpc) has always been the sister application to Truffle, and for good reason. The TestRPC gives users a personal blockchain with which to develop, drastically lowering the barrier to entry of Ethereum development and removing the need for mining or dealing with real Ether. Developing on the TestRPC is an integral part of every Ethereum project, and it's usually the first blockchain deployed to in a professional Ethereum developer's workflow. We'll be blogging about the ideal Truffle workflow a bit later, but instead of waiting, you can just let [Chris Hitchcott from Digix Global show you how it's done](https://youtu.be/SFW6W-DIdIo?t=1079). (Thank you Chris, this was a great presentation.)
+
+Fixing installation issues on the TestRPC required the [very same solution](/blog/how-were-making-installation-issues-a-thing-of-the-past) as fixing them on Truffle, so we won't go into detail here. However, I will say the solution worked _even better for the TestRPC_ than it did for Truffle. This is because the bundle we were able to create didn't require any external dependencies, making the package that you install just a single download. When compared to the old installation, the experience is night and day.
+
+## Getting the new version
+
+Like Truffle, we need you to put this version through its paces before we can release it as an official version, so we've **released it in beta**.
+
+To get the beta version, first uninstall the version of the TestRPC you currently have (because they'll conflict):
+
+```shell
+$ npm uninstall -g ethereumjs-testrpc
+```
+
+And now install the beta version:
+
+```shell
+$ npm install -g ethereumjs-testrpc@beta
+```
+
+(If you're on a Unix-based system, you may have to prefix the above commands with `sudo`.)
+
+You'll notice that the beta version installs instantly, quicker than you can say, "Holy crap, this is awesome."
+
+## So what's next?
+
+We have a lot of things planned for the TestRPC. We're not ready to officially announce everything just yet, but know that solving these installation issues is a stepping stone to providing you the best Ethereum development experience possible. Like creamy ganache filling is to a chocolate truffle, so is the TestRPC to the core of your workflow. So stay tuned. It's gonna be sweet.
+
+-- Tim & the Truffle Team
diff --git a/src/blog/sandbox-forking-with-truffle-teams/index.md b/src/blog/sandbox-forking-with-truffle-teams/index.md
new file mode 100644
index 000000000..7f5709e8b
--- /dev/null
+++ b/src/blog/sandbox-forking-with-truffle-teams/index.md
@@ -0,0 +1,47 @@
+---
+title: Simulate Live Networks with Forked Sandboxes
+hide:
+  - navigation
+---
+
+<figure>
+  <img class="mb-4 figure-shadow" src="/img/blog/sandbox-forking-with-truffle-teams/sandbox-forking-blog.png" alt="Sandbox Forking" style="width:100%">
+</figure>
+
+Sandboxes in Truffle Teams are the easiest way to setup a shared Ganache instance for the entire team. They integrate seamlessly with our deployments manager, and work locally as expected too: insert the mnemonic and RPC URL into your Truffle config or browser wallet and starting sending ether, deploying contracts, interacting via the console and more! We’re not stopping there though. Today we’re proud to introduce live network simulation via sandbox forking!
+
+## Introducing Forking
+
+Forking allows a sandbox to act as a live network from a given block number. We take for granted in web2 that we can get test credentials and interact with an API that will map to our production environment, but in web3 this hasn’t been so easy. With a forked sandbox you can transact, deploy, test, and debug against Mainnet without spending real Ether!
+
+Forking has been available since 2017 ([see this older tutorial](/guides/chain-forking-exploiting-the-dao)), but the requirement of a full archival node was a barrier for many. By adding this ability to Truffle Teams, you no longer need to worry about anything--just select a network and go. Here are some more specific examples:
+
+* **DeFi**: Some DeFi protocols have testnet deployments that differ from their Mainnet counterparts for a variety of reasons. For dapp developers, this inconsistency presents a problem. You want to develop against the “real” protocol, but developing in production is terrible, especially when real ETH is at stake! With forking, you’re free to simply fork Mainnet and deploy your dapp to an environment that translates to the live network.
+
+* **Testing**: Ensuring your dapp integrates with another used to require getting those contracts, deploying them to your local test network or a live testnet (assuming there’s no comparable testnet deployment already), then finally running your tests. With a forked sandbox your target dapp is already there, with its state. Want to test your CryptoKitty item? You can do it with your actual kitty!
+
+* **Security Analysis**: Dynamic analysis, the process of executing code and data in real-time with the hope of finding issues during execution, has never been easier. With the ability to take control of any account on the given network and travel through time by selecting an older block, you can run attacks live and see exactly what went wrong.
+
+## How to Create a Forked Sandbox
+
+<figure>
+  <img class="mb-4 figure-shadow" src="/img/blog/sandbox-forking-with-truffle-teams/forking-details-for-blog.png" alt="--stacktrace-extra" style="width:100%">
+  <figcaption class="text-center font-italic">A forked Mainnet sandbox.</figcaption>
+</figure>
+
+To fork a network, create a new sandbox and check the forking checkbox. From there, select a network and optionally provide a block number. Clicking CONFIRM will spin up a new Ganache instance forked from the given network and block. For more details, <a href="/docs/teams/sandboxes/sandbox-forking" target="_blank">see our sandboxes documentation.</a>
+
+You can now interact with this sandbox as you would the forked network. Using Ethereum 
+Mainnet as an example: you can call out to Mainnet contracts, and send ETH to Mainnet addresses.
+<div class="mt-12 text-center">
+    <a class="btn btn-truffle mt-3" href="/docs/teams/getting-started/creating-an-account" target="_blank">START TESTING AGAINST PRODUCTION NETWORKS TODAY!</a>
+  </div>
+
+## How Will you Use Forking?
+We’re very proud of this feature and think it’s going to be a game-changer for the community. We’re curious: how will you use forking?
+
+We want Truffle Teams to be the most effective devops tool in the blockchain space for both new and existing teams. <a href="https://trfl.co/become-a-truffler" target="_blank">Join our slack community</a> and let us know what you think about this feature, and if your team has other needs we haven’t met yet.
+
+**Thank you!**
+
+Josh Quintal, Head of Product & Marketing
diff --git a/src/blog/stack-tracing-with-truffle-test/index.md b/src/blog/stack-tracing-with-truffle-test/index.md
new file mode 100644
index 000000000..c442e5083
--- /dev/null
+++ b/src/blog/stack-tracing-with-truffle-test/index.md
@@ -0,0 +1,42 @@
+---
+title: Stack Tracing with Truffle Test
+hide:
+  - navigation
+---
+
+<figure>
+  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog-header-stacktraces.png" alt="--stacktrace-extra" style="width:100%">
+</figure>
+
+Truffle Test can now provide stacktraces when your transactions revert! This is still a little experimental, and it requires `truffle test` to recompile all your contracts, so you’ll have to enable it with `truffle test --stacktrace`. 
+Here’s what the result looks like:
+<figure>
+  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog1.png" alt="truffle test --stacktrace" style="width:100%">
+  <figcaption class="text-center font-italic">truffle test --stacktrace</figcaption>
+</figure>
+
+The stacktrace continues seamlessly from the Javascript test into the Solidity contracts. It begins in the Javscript where the transaction was sent, continues through the contract that initially received the transaction, and finally ends in the contract where the revert occurred.
+
+These Solidity stacktraces will be printed both for reverted transactions sent during tests and for reverted deployments made during tests with `Contract.new()`. Stacktraces are not currently available for calls or gas estimates. Note that stacktraces are a Truffle Contract feature, and will not be available if transactions are sent by other means.
+
+What if we want a little more? Looking at the above example again, one of our stacktraces helpfully included a revert message, but the other did not. Wouldn’t it be nice if it had one too? Let’s try this again, but this time with `--stacktrace-extra`:
+<figure>
+  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog2.png" alt="--stacktrace-extra" style="width:100%">
+  <figcaption class="text-center font-italic">--stacktrace-extra</figcaption>
+</figure>
+
+There we go! The `--stacktrace-extra` option, in addition to turning on stacktraces, additionally compiles your contracts with Solidity’s debug mode, so you get more information about just why the transaction reverted.
+
+Of course, for more detailed analysis, you may want to use Truffle Debugger! But stacktraces in tests can give a good first view of why your transaction reverted.
+
+These testing options are still a little experimental, so it’s possible some things may not work with them. But, in most cases, they should provide a quick helpful view into why your test transaction reverted!
+
+Thanks,
+
+Harry Altman
+
+--Debugger Engineer, Truffle Suite
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-6" href="https://github.com/trufflesuite/truffle/releases/tag/v5.1.24">Click here for the release notes on GitHub</a>
+</div>
diff --git a/src/blog/sunsetting-truffle-teams/index.md b/src/blog/sunsetting-truffle-teams/index.md
new file mode 100644
index 000000000..ad9334a34
--- /dev/null
+++ b/src/blog/sunsetting-truffle-teams/index.md
@@ -0,0 +1,46 @@
+---
+title: Sunsetting Truffle Teams
+hide:
+  - navigation
+---
+
+![Sunsetting Truffle Teams Banner](/img/blog/sunsetting-truffle-teams/blog-header.png)
+
+<p class="alert alert-warning">
+<i class="far fa-info-circle"></i> <strong>N.B</strong>: we published an earlier version of this blogpost with an incorrect timeline. Truffle Teams will be sunset on September 10, 2021.</a>
+</p>
+
+After a 2 year long road, we're sunsetting Truffle Teams (effective September 10th, 2021). 
+
+The journey began when Truffle was an independent company. It extended our reach from dapp development into dapp maintenance. We've gained valuable insights about the state of blockchain devops, the most desirable parts of our tools, and a new clarity around our core competencies.
+
+As an independent company, Truffle Teams was integral to building a business for the long-term, but it came with some costly tradeoffs. Over time the resources required to develop and maintain it were too great, taking time away from development of our open-source tools and eventually taking time away from supporting tasks like ecosystem engagement and development. This was unsustainable.
+
+Another important factor made this sunsetting possible: The acquisition of Truffle Suite by ConsenSys Software granted us greater supporting resources and freed us from monetary metrics. Which leads us to some good news! We are reaffirming our commitment to having the best-in-class open-source blockchain developer tools.
+
+## What about paid subscribers?
+
+All active Pro and Enterprise tier users will receive a refund of 1 month and recurring billings will cease. If you don't see a refund within 5 days (Paddle's processing time), email us at [truffle-teams@trufflesuite.com](mailto:truffle-teams@trufflesuite.com).
+
+## What about my data?
+
+All user data will be deleted 30 days following the date of shut down (September 10th 2021). Be sure to request your data before this time, otherwise we'll be unable to guarantee recovery. If you would like a dump of your data, email us at [truffle-teams@trufflesuite.com](mailto:truffle-teams@trufflesuite.com).
+
+**All user data will be deleted on September 10th, 2021.** Make sure to request your data before this time, otherwise we'll be unable to recover it.
+
+## The afterlife is open-source
+
+Parts of Truffle Teams will be making their way into our open-source tools! We're happy to share one right now--repackaging the visual debugger as a plugin that allows you to launch an instance from within Truffle. Truffle Teams provided greater context around your dapps activity thanks to its GUI. Being able to pull up a list of transactions from a Ganache instance, filter by failures, and clicking a debug button was one of the better workflows that we're proud to integrate with our open-source suite.
+
+These repurposed bits will all be open-source, so you can [check out the `truffle-plugin-debugger` repository here.](https://github.com/trufflesuite/truffle-plugin-debugger)
+
+<figure>
+  <img class="mb-4 w-100" src="/img/blog/sunsetting-truffle-teams/visual-debugger.png" alt="the Truffle Teams visual debugger--coming to Truffle!">
+  <figcaption class="text-center font-italic">The Truffle Teams visual debugger--coming to Truffle!</figcaption>
+</figure>
+
+If there are other features you'd like to see again, for example the deployments screen or contract manager, let us know!
+
+Sincerely,
+
+_The Truffle Suite Team_
diff --git a/src/blog/take-a-dive-into-truffle-5/index.md b/src/blog/take-a-dive-into-truffle-5/index.md
new file mode 100644
index 000000000..065a9d89d
--- /dev/null
+++ b/src/blog/take-a-dive-into-truffle-5/index.md
@@ -0,0 +1,136 @@
+---
+title: Take a Dive into Truffle 5
+hide:
+  - navigation
+---
+
+![Take a Dive into Truffle 5 Banner](/img/blog/take-a-dive-into-truffle-5/blog-header.png)
+
+Truffle 5 has had some exciting releases in the flexibilty they provide to your workflow. 🌊 Truffle now offers the ability to detect the version of Solidity in your contracts at compile time and allows for compilation from ABI files. Because of this, wrangling a project whose contracts use multiple version of Solidity is much easier going forward. We've also enhanced our testing capabilities with Solidity strack traces and better event decoding, making it much easier to get to the source of an error and get richer information from events. When our projects integrate with existing protocols, it's a pain to have to deal with those external contracts. Now Truffle makes this easy with the ability to fetch external contracts verified on Etherscan! Vyper support continues to improve with experimental debugging for Vyper contracts, as well as improved import handling for Vyper.
+
+Did I mention support for **decentralized file storage**?
+
+## What's New in 5.2 and 5.3
+
+### IPFS, Filecoin, and Textile Bucket support via `truffle preserve`
+
+Tests have ran, bugs are squashed, your smart contracts have been deployed successfully to mainnet; life is good. It's time to make your dapp accessible to the masses! So you... go to a centralized host and spin up the frontend? Something's definitely off here.
+
+Enter `truffle preserve`: You can now use Truffle to upload your static assets to [IPFS](https://ipfs.io/), [Filecoin](https://filecoin.io/), and/or [Textile Buckets](https://docs.textile.io/buckets/) for a fully decentralized application across the entire stack!
+
+Here are some companion pieces to help you get started:
+- The [Filecoin Truffle Box](https://github.com/truffle-box/filecoin-box) includes a decentralized art gallery to get you started with a fully working project!
+- [The original Filecoin + Truffle & Ganache Blog Post](/blog/truffle-and-ganache-now-come-in-filecoin-flavor)
+- [`truffle preserve` Documentation](/docs/truffle/getting-started/preserving-files-and-content-to-storage-platforms)
+
+<figure>
+  <img class="mb-4 w-100" src="https://github.com/truffle-box/filecoin-box/raw/master/screenshots/sample-ui.png?raw=true" alt="the Filecoin Trufflebox provides you with a Filecoin powred art gallery">
+  <figcaption class="text-center font-italic">Unbox a decentralized art gallery with the Filecoin Truffle Box.</figcaption>
+</figure>
+
+### Pragma compilation
+
+As of version 5.2.0, Truffle now ships with a fun, experimental setting for compilation: the “pragma” setting. This feature analyzes your Solidity source files for their pragma expressions. It then uses these expressions to figure out which version of the Solidity compiler is required for each given source. This allows your project to compile when it contains multiple Solidity files, each requiring a different version of the Solidity compiler!
+
+To use this feature, set the Solidity compiler version field in your `truffle-config.js` as follows:
+
+```javascript
+module.exports = {
+  compilers: {
+    solc: {
+      version: “pragma”
+    }
+  },
+  // … the rest of your config goes here
+};
+```
+
+Now you can run `truffle compile` and your project will compile!
+
+To illustrate this feature and the ones below, we have created a [Truffle box for Truffle 5.2](https://github.com/truffle-box/v5.2-example-box).
+
+In this box you can see how the `truffle-config.js` is set up to use this new experimental feature. Notice that `contracts/MetaCoin.sol` requires `^0.7.0` and how `contracts/Conversion.sol` requires `^0.6.0`. When running `truffle compile` on this example project you should get a printout of all the versions of the Solidity compiler used during compilation. Namely, you should see that both version `0.6.12` and `0.7.6` are listed.
+
+When you use this feature, Truffle will analyze each of your Solidity sources one by one to find the appropriate version of the Solidity compiler for each source. Do note, however, that each source file and all of its imports must be compiled with one version of Solidity; this means there must be a version of the compiler that satisfies all of their pragma expressions.
+
+## Things you may have missed in Truffle 5.1
+
+We’ve added a fair bit over the course of Truffle 5.1 as well, and there’s a good chance you didn’t catch all of it!  We thought this would be a good time to review some of that as well!
+
+### Compilation of abi.json files
+
+Another exciting addition to Truffle is the ability to compile from a contract’s ABI. When you create a JSON source file in your “contracts” directory that contains a contract’s ABI, Truffle will take it, use it to create an interface, and compile it. This might come in handy, for example, when you want to import and use a library that requires a different version of the Solidity compiler than the importing file. You can then simply compile the library and create a new JSON file containing the ABI of the imported library. Under the hood Truffle will compile the ABI into a Solidity interface and create an artifact for it. You will then be able to import the interface into your contract!
+
+In the v5.2-example-box, consider the `contracts/MetaCoin.sol` and `contracts/Conversion.sol`. We would like to import Conversion into the MetaCoin contract to use it but cannot since they require different versions of the Solidity compiler.  To work around this, we have created `contracts/IConversion.abi.json` which contains the ABI from the compiled Conversion. In this way we can now import the interface into `contracts/MetaCoin.sol` (see line 4 in the MetaCoin contract) to use it!
+
+### Solidity stacktraces in Truffle Test
+
+Try running your tests with the `--stacktrace` option (or `-t` for short) and get combined Solidity-Javascript stacktraces!  This feature does have some limitations and is still somewhat experimental, but we expect you’ll find it quite useful.  In the future we may add support for Vyper stacktraces as well!  
+
+And speaking of Vyper...
+
+### Experimental Vyper debugging
+
+You can now use Truffle Debugger with Vyper!  Support for this is still in its early stages; you won’t be able to inspect variables, I’m afraid.  But you can step through a Vyper transaction, and there will likely be more in the future!
+
+But perhaps the biggest improvement to the debugger is...
+
+### Debugging verified external contracts
+
+Use the `--fetch-external` (or `-x` for short) option with Truffle Debugger and it will automatically download sources for any verified contracts and allow you to step through them!  Contracts can be verified on either Etherscan or Sourcify.  You no longer need to download these yourself and add them to your Truffle project!  You can see [this](/blog/debugging-verified-external-contracts-with-truffle-debugger) earlier post for more information.
+
+###Improved import handling in Vyper
+
+Here’s another one for our Vyper users; you can now do imports from other projects (via NPM or EthPM) just like in Solidity!
+
+For instance, suppose `examplepackage` is an NPM package which is structured as a Truffle project, and you want to import a Vyper contract, `VyperContract`, from it.  You can now do
+
+```python
+from examplepackage.contracts import VyperContract
+```
+
+or
+
+```python
+import examplepackage.contracts.VyperContract as VyperContract
+```
+
+to import it, much like you could do in Solidity!
+
+Note that if your own project uses such “absolute” imports as a way to import its own files from the project root -- e.g., if you have a file `contracts/subdirectory/Contract1.vy` which imports `contracts/Contract2.vy` via
+
+```python
+import Contract2 as Contract2
+```
+
+then this will work within your own project, but won’t work if other people try to import your `Contract1`.  We suggest that if you want other people to import contracts from your project, you use explicitly relative imports instead:
+
+```python
+from .. import Contract2
+```
+
+But such imports are now possible.  We hope you’ll find all sorts of uses for this!
+
+### Enumeration values in Truffle Contract objects
+
+When sending a transaction that takes an `enum`, it’s inconvenient to have to look up the numeric constants that the `enum` uses.  Well, now, each Truffle Contract constructor object contains enumeration constants, so you don’t need to do that.  Just do
+
+```javascript
+contractInstance.exampleMethod(Contract.ExampleEnum.EnumValue);
+```
+
+and don’t worry about the particular numeric value of `EnumValue`.  You can also do `Contract.enums.ExampleEnum.EnumValue`, if you want to be extra-certain.
+
+Note that it’s not currently possible to access enums declared outside of a contract this way, but we have plans in the future to make using those easier, too!
+
+### Even more!
+
+Other things you might have missed include: Improved event decoding in `truffle test`; being able to use the debugger to step through Yul (assembly) sources generated by Solidity for its own internal subroutines (try the `g` command!); being able to inspect assembly variables in the debugger; `truffle test --bail`; `truffle create all`; and the debugger providing more information upon transaction reversion.
+
+### What's Next? Want to Help us Build it?
+
+How will you use the new enhancements in Truffle? Let us know what you think about these features on Twitter, and if you have other needs we haven’t met yet.
+
+<p class="alert alert-info m-t-2">
+<i class="fas fa-info-circle"></i> <strong>WE'RE HIRING!</strong> Why stop at feature requests--cut out the middleman and work with us directly! There are many exciting problems to solve like layer 2 support, mapping decoding, and a revamped deployment system, to name a few. We'd love your help and perspective. <strong><a href="https://consensys.net/open-roles/3004215/">Apply here on ConsenSys' website!</a></strong>
+</p>
diff --git a/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md b/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
new file mode 100644
index 000000000..93b4b1f9f
--- /dev/null
+++ b/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
@@ -0,0 +1,36 @@
+---
+title: Take Control of Your Deployments with Truffle Teams
+hide:
+  - navigation
+---
+
+![Truffle Teams Deployments Banner](/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/truffle-teams-deployments-banner.png)
+
+If you read our [blog post back in July](/blog/an-easier-way-to-deploy-your-smart-contracts), attended my TruffleCon workshop **Push It! Push It Real Good: Truffle Teams Intro & Deployments** back in August, or tuned in last week to our **Truffle Teams Overview** webinar, you've known something awesome has been in the works for Truffle Teams.
+
+Well it's finally here! On behalf of the whole team, I'm excited to announce Deployments within Truffle Teams!
+
+<a target="_blank" href="/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/deployments.png">![Deployments](/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/deployments.png)</a>
+
+## Bridging the Gap Between Local Ganache Testing and Public Testnet/Mainnet Deployments
+
+The interaction between Truffle and Ganache provides an awesome way to iteratively test and fix contracts on a personal Ethereum blockchain. However, it can be a little tricky when you're ready to publish your application to the rest of the world. That's where Truffle Teams Deployments comes in: we give you a **dead-simple deployment experience** which links with MetaMask so you never need to export your private keys.
+
+## Benefits of Deploying with Truffle Teams
+
+- **Easily deploy to public Ethereum networks** (Mainnet, Ropsten, Görli, Rinkeby, and Kovan are supported)
+- **Works with the existing migration scripts** in your Truffle project; Truffle Teams uses `truffle migrate` under the hood
+- **No need to export/import private keys** — use [MetaMask](https://metamask.io/) to deploy like you would with any other dapp
+- **Deploy with [Ledger](https://www.ledger.com/) or [Trezor](https://trezor.io/) hardware wallets** within MetaMask
+
+## Learn More in Our Tutorial or Try It Now!
+
+We put together a step-by-step [tutorial](/guides/learn-how-to-deploy-with-truffle-teams) to guide you through your first Truffle Teams deployment. While we recommend that you follow the tutorial (as it answers some FAQs), the deployment experience is simple enough for you to just give it a shot! 👇
+
+<div class="post-trufflecon-box mt-5 text-center">
+  Get started with Truffle Teams, and see deployments for yourself!
+
+  <div class="mt-3">
+    <a class="btn btn-truffle" href="/docs/teams/getting-started/creating-an-account">Try Truffle Teams</a>
+  </div>
+</div>
\ No newline at end of file
diff --git a/src/blog/testrpc-is-now-ganache/index.md b/src/blog/testrpc-is-now-ganache/index.md
new file mode 100644
index 000000000..6166510a0
--- /dev/null
+++ b/src/blog/testrpc-is-now-ganache/index.md
@@ -0,0 +1,37 @@
+---
+title: TestRPC is now Ganache
+hide:
+  - navigation
+---
+
+Have you been looking for the TestRPC recently and haven't been able to find it?
+
+Don't worry, it's still here! It's just now known as **Ganache**.
+
+Ganache comes in two flavors: a fully-interactive development blockchain with a graphical interface, and the more familiar command-line version.
+
+* [Get the graphical version here](/ganache).
+
+* For the command-line version (known as **Ganache CLI**):
+
+  ```shell
+  npm install -g ganache-cli
+  ```
+
+## A little history
+
+Prior to the existence of the TestRPC, you would have to deploy to private internal test networks to see how your contract code operated (as public test networks like Ropsten didn't yet exist!).
+
+While initially under the auspices of the [EthereumJS project](https://github.com/ethereumjs/), it was originally created by the Truffle team, and today we remain its primary maintainers. So simply for maintainability sake, it just made sense to bring the TestRPC under Truffle's wing.
+
+Additionally, we realized over time that the TestRPC was a poor name. The TestRPC quickly became more powerful than simply a blockchain environment used for testing. To stay with the sweet Truffle brand, we decided to rename it Ganache, as Ganache is (often) the core of your favorite chocolate truffle. It's a much catchier name (and a much tastier one too).
+
+## Multiple ways to enjoy
+
+With this name change, we also released [a fully-interactive, graphical version of Ganache](/ganache).
+
+The command-line utility is still available via NPM; the [command line flags](https://github.com/trufflesuite/ganache-cli/blob/master/README.md) are the same too. All that's changed is the name of the command.
+
+Ganache is also available as a library for your applications. See the [README](https://github.com/trufflesuite/ganache-cli/blob/master/README.md) for more details.
+
+So now you have multiple ways to create a personal blockchain. If you're looking for a blockchain with a graphical environment that's perfect for beginners, check out [Ganache](/ganache). And if you want the familiar command-line interface, install Ganache CLI. Happy developing!
diff --git a/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md b/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
new file mode 100644
index 000000000..fa7f61224
--- /dev/null
+++ b/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
@@ -0,0 +1,81 @@
+---
+title: The Best Things to do in Seattle During TruffleCon
+hide:
+  - navigation
+---
+
+![river view at Marymoor Park](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-1.jpg)
+
+## [Marymoor Park](https://www.kingcounty.gov/services/parks-recreation/parks/parks-and-natural-lands/popular-parks/marymoor.aspx)
+
+Marymoor Park, located on the north end of Lake Sammamish in Redmond, Washington, is King County's largest, oldest, and most popular park, with more than 3 million annual visitors coming to roam its 640 acres. Marymoor is famous for its [outdoor concert series](https://www.marymoorconcerts.com/events) during the summer. You can catch concerts on Aug 2 and Aug 4 after the day festivities at TruffleCon!
+
+## [Sammamish River Trail](https://www.alltrails.com/trail/us/washington/sammamish-river)
+
+The Sammamish River Trail is a beautiful 19-mile bike path and recreational trail in King County, Washington that runs along the Sammamish River from Blythe Park in Bothell to Marymoor Park in Redmond. There are several places along the trail you can enter. It's perfect for biking, running, or just enjoying a nice walk in the beautiful outdoors!
+
+## [Idylwood Beach Park](https://experienceredmond.com/activities-and-attractions/idylwood-beach-park/)
+
+August can reach temperatures of up to 80 degrees, which is quite hot for Seattleites. Idylwood Beach Park is one of the best places to cool off. It's a waterfront park on Lake Sammamish with a beach, boat ramp, playground & canoe rentals.
+
+## [Microsoft Visitor Center](https://experienceredmond.com/activities-and-attractions/microsoft-visitors-center/)
+
+The Microsoft Visitor Center is open during the weekdays. Walk through the doors of the Microsoft Visitor Center and unlock your potential—experience everything from the latest Microsoft Research innovations to the very first personal computer. Microsoft offers self-guided tour information to explore hands-on exhibits featuring some of the company's most exciting technologies for home and business.
+
+![entrance to Microsoft Visitor Center](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-2.jpg)
+
+## [Woodinville Wine Country](https://woodinvillewinecountry.com/)
+
+Nestled in the beautiful Sammamish River Valley just 30 minutes northeast of Seattle, Woodinville Wine Country is home to over 100 wineries and tasting rooms representing every appellation in Washington.
+
+From the historic and beautiful grounds of Chateau Ste. Michelle to the quaint boutique wineries where you are likely to have the winemaker themselves pour you a glass of his or her finest blend, a wonderful variety of wine tasting experiences awaits you!
+
+![winery building in the Sammamish River Valley](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-3.jpg)
+
+## [Black Raven Brewing Company](https://www.blackravenbrewing.com/)
+
+Black Raven is a neighborhood brewery with a friendly retail taproom, The Raven's Nest, with locations in both Redmond and Woodinville. The Raven's Nest is not a traditional brewpub; it's more like our brewery's living room. Open 7 days a week and a seating capacity of about 100, it's home to local beer lovers who want to be a part of a community that enjoy great beer and great friends.
+
+## [Mac & Jack's Brewing](https://www.macandjacks.com/)
+
+Mac and Jack's brewing offer a tasting room, retail store, beer garden, and tours at their brewery in Redmond, WA. Mac & Jack's started out of Jack's garage in 1993, with nothing but a passion for exceptional beer. Lots of hops and 26 years later they are still producing one of Seattle's favorite beverages.
+
+## [Flee Escape Room](https://www.fleeescape.com/)
+
+Flee Escape Game is one of the largest Seattle and Redmond Real Life Escape Rooms. So grab your team, new friends you just met, or organize a party to see if you can all make your great escape.
+
+![egyptian themed escape room](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-4.jpg)
+
+## [Paragliding](https://www.tigermountainparagliding.com/fly-tandem/)
+
+Come paraglide tandem with us, and experience free flight in its purest form! After running down a moderately steep hill you'll find yourself airborne, sitting comfortably in a reclined harness, your feet dangling above the trees, no one in front of you (pilot rides in back) and no cockpit surrounding you.
+
+Depending on conditions you'll have views of Mt. Rainier, Mt. Si, Lake Sammamish, Bellevue, Seattle, the Puget Sound and so much more. Bald eagles and other predators leave their nests to ride the same thermals allowing you to literally fly with birds.
+
+![couple having fun paragliding](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-5.jpg)
+
+## [Salish Lodge/Snoqualmie Falls](https://www.salishlodge.com/)
+
+Overlooking Snoqualmie Falls, just 30 minutes east of Seattle and Bellevue, Salish Lodge & Spa is a Washington State resort getaway, perfect for those seeking an authentic and memorable escape from the everyday. Dine on mouthwatering [Northwest cuisine](https://www.salishlodge.com/dining.php) hand-crafted from seasonal ingredients, savor the serenity of [The Spa](https://www.salishlodge.com/spa.php), then drift off to sleep in front of your cozy fireplace in one of our newly renovated guestrooms. We invite you to experience the iconic Salish Lodge.
+
+![aerial view of snoqualmie falls](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-6.jpg)
+
+## [DirtFish Rally Driving School](https://www.dirtfish.com/)
+
+Nestled in the foothills of the Cascade Mountain Range in the scenic town of Snoqualmie, WA, DirtFish Rally School was established in 2010 with the idea that the exciting sport of rally should be accessible to everyone. Armed with an immaculate fleet of turbocharged, all-wheel-drive cars, right from the beginning DirtFish was equipped to share with anyone the excitement of what a real rally car can do on a loose surface. In the fall of 2014, DirtFish embellished their offerings with the launch of rear-wheel drive programs. Similar in nature to the all-wheel drive programs, the precise and very sideways action the classes offer provides an entirely different challenge for drivers of every background. Ever since, DirtFish has become the most prestigious rally school in North America, providing the highest level of instruction, top level cars and gorgeous facilities all year round.
+
+![rally car driving on dirt road](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-7.jpg)
+
+## [Hiking](https://www.wta.org/)
+
+Hiking in nature has a positive impact on people's hearts, minds and bodies. It is vital for everyone to have the opportunity to access the outdoors, and the WTA is committed to reducing barriers to hiking trails and lands. We strive to inspire people to go outside—giving them the skills and knowledge they need to recreate safely and sustainably.
+
+People will protect the places they love to hike. WTA rallies hikers to raise our collective voice to protect the places we love. Our voice is amplified by the support of our members and sweat equity of every volunteer who helps to build and maintain trails.
+
+![beautful views of the mountains on the hiking trail](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-8.jpg)
+
+## [Mountain Biking](https://seattlemountainbiketours.com/)
+
+Your all-inclusive mountain biking tour in Seattle includes pickup from Downtown Seattle or Bellevue and shuttle transportation to our favorite trails for intermediate and experienced cyclists. At the trailhead, you get your high-quality mountain bike, a helmet, gloves, and any other safety gear needed for our ride. Don't worry, we have plenty of water and snacks for our mountain biking adventure!
+
+![mountain biker rounding the bend in Seattle](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-9.jpg)
diff --git a/src/blog/the-best-ways-to-contribute-to-truffle/index.md b/src/blog/the-best-ways-to-contribute-to-truffle/index.md
new file mode 100644
index 000000000..ea5121adb
--- /dev/null
+++ b/src/blog/the-best-ways-to-contribute-to-truffle/index.md
@@ -0,0 +1,31 @@
+---
+title: The Best Ways to Contribute to Truffle
+hide:
+  - navigation
+---
+
+Have you ever thought about contributing to Truffle? All of us at Truffle really enjoy producing free and open source software, and it is especially fun when many of you in the community contribute. User contributions make life easier for us, make our work more enjoyable by showing that you’re engaged, and often give us a chance to learn from those that offer code to the project. We’d absolutely love any and all developers to contribute to our project. The following are a few ways that you can get involved.
+
+## Read the contributor guidelines.
+
+The first step anyone should take before contributing to Truffle is to hop on over to our Github page and [read our contributing guidelines](https://github.com/trufflesuite/truffle/blob/develop/CONTRIBUTING.md). Our contributing guidelines will give you a baseline understanding of how Truffle is built, which tools to use during development, and other useful information to get you started. Make sure to read those guidelines before continuing on in this post.
+
+## Follow the command flow.
+
+You’ll see that the contributing guidelines focus on the command flow. This is because at its core, Truffle is a command line tool that processes and runs specific commands on behalf of a user. If you can figure out where a command starts, you can follow its execution to get a better understanding of what Truffle is doing. We recommend choosing your favorite command and following its path through the code. We’d also recommend performing your own local experiments by changing the behavior of a specific command and seeing how it behaves. Don’t forget to read the contributing guidelines above, as it tells you where to get started for each command.
+
+## Change callbacks to Promises.
+
+Given the lifetime of the project -- over four years! -- Truffle has its share of legacy code. Before Promises became widespread in the Node world, callbacks were used to control the flow of asynchronous code within Truffle. The code was written in a style where a callback function was passed from one method to the next, intended to be executed after everything else had finished running or when an error occurred. Nowadays, many people find this style of code to be abstruse, and hard to understand, and now favor Promises over callbacks. We do too. One of our major tasks over the coming year is to rework our code to favor a Promise-based coding style instead of a callback-based one. We are always interested in receiving PRs that clean up our callbacks and make the code easier to understand for everyone (we love you async/await).
+
+## Start small, and chat with us for larger tasks.
+
+It can be very overwhelming to begin contributing to Truffle with a big feature. Instead, we recommend going after a smaller, more bite-sized change that will not only make you feel more successful, but can also help you get a better understanding of the underlying code. If you find something trivial, like a documentation error, go ahead and fork the repository, make your changes, and submit a pull request. For something bigger, we like to have a discussion first as our tools support many different use cases and platforms. If you have a great idea for a change that will require significant effort, we recommend filing a GitHub issue with a proposal or contacting us using the channels below. We can layout specs, bounce ideas around, and agree on what’s needed before you dive in.
+
+## Tackle an issue.
+
+Many of our users submit issues for things that need to be fixed. Sometimes these issues are small bugs that have been able to hide in the cracks. Other times they can be large changes or feature requests that require significant effort to fix. Regardless of your appetite, our [issues list](https://github.com/trufflesuite/truffle/issues) is often a great place to start for people to contribute. Due to the nature of software, you’re bound to find an issue that’s right for you. And even if you don’t think you can fix an issue, confirming that issues exist and giving us extra information can be extremely helpful. Often the biggest factor keeping a sneaky bug alive is information, so validating an issue exists and providing more data can help us squash that bug even faster.
+
+## Contact us.
+
+As always, we’d love to hear your feedback and concerns, as well as answer any questions you have when contributing to Truffle. Feel free to reach out to us on our [Spectrum](https://spectrum.chat/trufflesuite) page, or file an issue on [Github](https://github.com/trufflesuite/truffle/issues). We'd love to hear from you. Happy Truffling!
diff --git a/src/blog/the-blockchain-problem-that-ens-solves/index.md b/src/blog/the-blockchain-problem-that-ens-solves/index.md
new file mode 100644
index 000000000..d4916ab4a
--- /dev/null
+++ b/src/blog/the-blockchain-problem-that-ens-solves/index.md
@@ -0,0 +1,32 @@
+---
+title: The Blockchain UI Problem that ENS Solves
+hide:
+  - navigation
+---
+
+The blockchain world has a UI problem. This is what an Ethereum receiving address looks like:
+
+**0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359**
+
+Bitcoin and other cryptocurrencies have the same problem, as do related decentralized projects like IPFS. The computer-generated address system works great for computers but isn’t user-friendly.
+
+This isn’t a new problem. The nascent Internet had a similar issue with IP addresses. For the Internet to eventually be used by millions and now billions of regular users, it needed a way to mask the machine-readable identifiers. So, in 1985, the “phone book of the Internet,” the Domain Name System (DNS), was born. While the DNS is used by many protocols, the World Wide Web really took the DNS mainstream. Can you imagine the web if users had to type in “72.125.224.72” rather than “google.com”?
+
+The blockchain world needs the same thing. We could use the existing DNS, but it’s a relatively centralized server architecture which makes it unattractive for blockchain applications.
+
+That’s where the Ethereum Name Service (ENS) comes in. ENS provides the same basic functionality of DNS (look up the records for “example.tld,” retrieve information), but replaces the hierarchical DNS server system with a few smart contracts on Ethereum.
+
+ENS is the naming service of the new decentralized Internet - with less infrastructure, better security, and of course less centralized control.
+
+ENS launched in 2017 with the native TLD.ETH, but we’ve been experimenting with allowing owners of DNS domains to use their domains on ENS and have successfully done this with .XYZ and .LUXE domains. We plan on rolling out this capability to most other TLDs later this year.
+
+We want to make it as easy as possible for dapp developers to take advantage of the big UI gains that ENS provides, which is why we’re working with Truffle. We are excited to be announcing several useful ENS integrations built into TruffleSuite at TruffleCon, so stay tuned!
+
+[Register your domain name](https://ens.domains/) using ENS today!
+
+Helpful Links:
+* Website: [https://ens.domains/](https://ens.domains/)
+* Manager: [https://manager.ens.domains/](https://manager.ens.domains/)
+* Docs: [https://docs.ens.domains/](https://docs.ens.domains/)
+* Gitter: [https://gitter.im/ethereum/go-ethereum/name-registry](https://gitter.im/ethereum/go-ethereum/name-registry)
+* Forum: [https://discuss.ens.domains/](https://discuss.ens.domains/)
diff --git a/src/blog/token-taxonomy-framework/index.md b/src/blog/token-taxonomy-framework/index.md
new file mode 100644
index 000000000..b8059a4c0
--- /dev/null
+++ b/src/blog/token-taxonomy-framework/index.md
@@ -0,0 +1,15 @@
+---
+title: Token Taxonomy Framework
+hide:
+  - navigation
+---
+
+To some, the sudden rise of Tokens in the blockchain dialog comes as a surprise. However, tokens have always been the bedrock of the blockchain movement. The introduction of SmartContract by Ethereum quickly overshadowed them, particularly in enterprise contexts. The capabilities of Smart Contracts and the broad acceptance of them, thanks to companies like Truffle, blazed a trail forward and we all went along. It wasn’t until we got halfway up the trail that someone turned around and asked, “did we pack any trail mix?”
+
+Sure, we had Ether, but one cannot persist on Ether alone. Focus shifted back to our roots. Developers who had steeped in SmartContracts turned their attention to tokens. However, they also brought a bit of baggage. You can do a lot in a Token using SmartContract concepts. We started to see the blurring of lines between what a contract was and what was a token, leading to a good bit of confusion all around.
+
+Back in April, [the Token Taxonomy Initiative (TTI)](https://tokentaxonomy.org/) was launched with very strong backing and a cross blockchain and platform set of founders including the EEA, ConsenSys, IBM, R3 and Digital Asset in an effort to provide clarity and purpose for tokens moving forward as the way we define value and how it can be used between parties across networks and platforms. The major deliverable from the TTI is the Token Taxonomy Framework (TTF), which is a platform neutral framework for defining and token that can eventually be certified and start to address critical issues like interoperability.
+
+![Token Taxonomy Framework](/img/blog/token-taxonomy-framework/framework.png)
+
+I’ll be presenting an [Introduction to the TTF](https://trufflecon2019.sched.com/event/RneW/token-taxonomy-framework) at TruffleCon on August 4th here in Redmond, WA. Swing by to hear how you can use the TTF to communicate with customers and partners, use the same terms and get solid requirements from the business, legal and regulatory communities.
diff --git a/src/blog/truffle-320-released/index.md b/src/blog/truffle-320-released/index.md
new file mode 100644
index 000000000..68219d4ba
--- /dev/null
+++ b/src/blog/truffle-320-released/index.md
@@ -0,0 +1,44 @@
+---
+title: Truffle 3.2.0 released
+hide:
+  - navigation
+---
+
+<p class="alert alert-info" style="margin-top: -2rem; margin-bottom: 3rem;">
+  <strong>UPDATE</strong>: We made another minor release after this blog post was written <a href="https://github.com/trufflesuite/truffle/releases/tag/v3.2.1">upgrading web3 to 0.18.2</a> due to request of our users. <a href="https://github.com/trufflesuite/truffle/releases/tag/v3.2.1">Truffle v3.2.1</a> is now the latest release, but it still includes all the awesome stuff below.
+</p>
+
+Hi all. Great news today.
+
+Following your feedback from the Truffle 3.0 release, we've just released Truffle 3.2.0! This release includes a [number of great new features and bug fixes](https://github.com/trufflesuite/truffle/releases/tag/3.2.0), but we're most excited about the following. I've bolded the good stuff for ya.
+
+1. **We've built infrastructure for providing you boilerplates on demand!** Now with `truffle init` comes `truffle init webpack`, which gives you a boilerplate web application combining the web development capabilities of Webpack with the power of Truffle. More boilerplates to come to make your life easier, so stay tuned!
+
+1. **We've added huge speed improvements to the Truffle command line tool.** Now your commands trigger in milliseconds! Go ahead, try it out. `truffle version`
+
+1. **Solidity tests can now be given default balances** so you can use those tests to exercise sending Ether to your contracts. Big win for Solidity tests, and your sanity in general. [Documentation](/docs/truffle/testing/writing-tests-in-solidity.html#testing-ether-transactions)
+
+1. Similarly, **Javascript abstractions got an upgrade** making it easier to send Ether directly to your contracts as well as trigger your contracts' fallback functions. You can use this feature within your tests as well as within your application. [More on that here](/docs/truffle/getting-started/interacting-with-your-contracts.html#sending-ether-to-a-contract). Also, they now use web3 0.18.2.
+
+1. **Migrations got an extra scout badge (function parameter)**, [allowing you to view available accounts directly within your migration](/docs/truffle/getting-started/running-migrations.html#available-accounts)
+
+1. Oh, and **there's no more naming restriction on contract names!** 🎉🎉🎉 You can now have a file called `ImABigDeal.sol` and have it define contracts under a completely different name. Woot!
+
+1. Along with the above, **there's a new way of requiring contract artifacts within your migrations and tests**. The old way still works if your contract names match your Solidity file names, but even if they don't you can simply require the contract by name:
+
+```javascript
+// Assume `ImABigDeal.sol` defines `contract MyContract { ... }`
+var MyContract = artifacts.require("MyContract");
+```
+
+There's been a lot of bug fixes too. Check out the [release notes on Github](https://github.com/trufflesuite/truffle/releases/tag/3.2.0) for a full list of changes, upgrades and fixes.
+
+### Big thanks!
+
+As always, we have to give you all a big thanks for being a part of the community and making Truffle better. This release would not be possible without your continued feedback, bug fixes and pull requests.
+
+If you run into trouble with any of the above, reach out on our [community Gitter channel](https://gitter.im/ConsenSys/truffle) where hundreds of your fellow Trufflers congregate to answer your questions. As well, check us out [on Twitter](https://twitter.com/trufflesuite) and send us a tweet.
+
+Cheers, and happy coding!
+
+-- Tim
diff --git a/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md b/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
new file mode 100644
index 000000000..000544e6c
--- /dev/null
+++ b/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
@@ -0,0 +1,50 @@
+---
+title: Truffle and Ganache now come in Filecoin Flavor
+hide:
+  - navigation
+---
+
+![Filecoin Collab Banner with Ganache](/img/blog/truffle-and-ganache-now-come-in-filecoin-flavor/blog-header.png)
+
+[Filecoin](https://filecoin.io) was created by [Protocol Labs](https://protocol.ai), the same organization who created and maintains [IPFS](https://ipfs.io). Filecoin extends the IPFS vision by creating an open-source decentralized storage network that provides incentives to keep data stored and pinned on IPFS. Filecoin is powerful because it provides a decentralized storage solution without having to rely on larger centralized solutions. Additionally when it comes to building dapps on other decentralized networks, like Ethereum, it provides the groundwork for a much needed storage and authenticity solution to full decentralization.
+
+## Truffle Preserve to Buckets
+
+[Back in July](/blog/announcing-collaboration-with-filecoin), we announced a first look at using the `truffle preserve` command in an experimental release. Today, we are releasing `truffle preserve` as part of the main, stable version of Truffle! To use `truffle preserve`, simply specify the files you want to preserve on the command line, and choose between the `--filecoin`, `--ipfs`, or `--buckets` recipes. The `filecoin` recipe uses the `ipfs` recipe under the hood, but if you need to, you can choose to use the `ipfs` recipe without `filecoin`. You can learn more about `truffle preserve` in this [blog post](/blog/announcing-collaboration-with-filecoin).
+
+In addition, we’re also introducing a new recipe for `truffle preserve` which allows developers to save data to [Textile Buckets](https://docs.textile.io/buckets/): `truffle preserve --buckets`.
+
+![`truffle preserve --buckets` Example](/img/blog/truffle-and-ganache-now-come-in-filecoin-flavor/preserve-buckets.gif)
+
+Try out any of these three recipes today by [downloading the latest version of Truffle](/docs/truffle/getting-started/installation)!
+
+## Filecoin-flavored Ganache
+
+Ganache has helped many developers create Ethereum dapps by providing a "one-click" experience; Ganache automates the difficult parts of running a decentralized network to give the developer a personal environment to tinker with and develop applications. It speeds up development by not having to wait for decentralized test networks to confirm transactions, and it provides a controlled, configurable environment to reproduce different test scenarios.
+
+Prior to Ganache, if you wanted to run a development network for Filecoin you would need to run the [lotus-devnet](https://github.com/textileio/lotus-devnet), which requires compiling native resources or running a public Docker image. This is still a great resource to emulate the Filecoin network as close as possible as it includes a real [Lotus](https://docs.filecoin.io/get-started/lotus/) node, but Ganache now provides a lightweight alternative for getting started with Filecoin app development.
+
+With the Filecoin flavor, Ganache now provides you both an IPFS server (used to store files) as well as a Lotus simulator (used to maintain file storage, simulate a storage provider, and availability) to add the necessary Filecoin methods to get started with Filecoin development. Like the Ethereum flavor of Ganache, we've made the process as simple as possible for you to get started with Filecoin quickly.
+
+## What can I do with Filecoin-flavored Ganache?
+
+With Filecoin-flavored Ganache, you can do most of the development tasks for building a Filecoin application:
+- Store and retrieve files from a personal IPFS node that Ganache starts for you
+- Create a storage deal and see it progress through different states
+- Test how your application handles storage deal expiration
+- Transfer Filecoin's token FIL between accounts
+- Interact with the various Filecoin wallet methods
+
+You can find a full list of supported RPC methods on [GitHub](https://github.com/trufflesuite/ganache-core/tree/develop/src/chains/filecoin/filecoin#supported-rpc-methods).
+
+## How do I get started?
+
+If you’re looking to get started with Ganache, head over to the [documentation](/docs/filecoin/ganache/overview) to see Get Started guides whether you're using the NodeJS library, CLI, or graphical UI version.
+
+Need an example on how to build a Filecoin application? Check out the [Filecoin Truffle Box](https://github.com/truffle-box/filecoin-box) to see an example to mint NFTs and provide a decentralized art gallery application.
+
+We’re finalizing the Truffle documentation in the coming days, so stay tuned for those! When they’re live, you’ll be able to find them at our [main documentation page](/docs) and click on the Filecoin link.
+
+## Where can I get help?
+
+We're extremely excited to be working with the Filecoin community to add support for Filecoin into Truffle Suite's tooling. If you have questions about our Filecoin integration or our plan for the future, join [Truffle’s Discord community](https://trfl.co/truffle-community) & the [Filecoin community Slack](https://filecoin.io/slack) to get your questions answered. We're happy to help!
diff --git a/src/blog/truffle-and-infura-support-arbitrum/index.md b/src/blog/truffle-and-infura-support-arbitrum/index.md
new file mode 100644
index 000000000..607b9031c
--- /dev/null
+++ b/src/blog/truffle-and-infura-support-arbitrum/index.md
@@ -0,0 +1,38 @@
+---
+title: Truffle and Infura Now Support Arbitrum
+hide:
+  - navigation
+---
+
+![Truffle, Arbitrum Collab Image](/img/blog/truffle-and-infura-support-arbitrum/blog-header.png)
+
+In our continuing efforts to help build the emerging multi-network Ethereum ecosystem, the Truffle team is thrilled to announce the launch of the Arbitrum Truffle Box. The usability and efficiency of Ethereum depends on scalability, and Arbitrum’s Layer 2 solution blends security and higher throughput to help make scalable Ethereum a reality.
+
+## Arbitrum
+
+Arbitrum is a Layer 2 scaling solution for Ethereum that uses optimistic rollups with interactive proving to make smart contracts scalable, fast, and private. It tracks closely to Ethereum, so that Ethereum developers can easily cross-compile their contracts to deploy on Arbitrum. Arbitrum offers its developers a variety of benefits: trustless security, compatibility with Ethereum, scalability, and cost efficiency.
+
+The Arbitrum rollup chain is built on top of and secured by Ethereum. From the developer perspective, interacting with Arbitrum is nearly identical to interacting with Ethereum. Arbitrum supports the same RPC interface as Ethereum, supports all EVM languages, and natively supports all Ethereum tooling without any special adapters. The main difference users and developers will notice is that transactions on Arbitrum cost a fraction of what they would if run natively on Ethereum.
+
+It is important to understand the mechanics of withdrawing funds from the Arbitrum chain. When withdrawing to Ethereum through an Arbitrum bridge, there is a delay to ensure that the transactions being rolled up are confirmed. Information about this finality delay and potential methods to avoid it can be found in Arbitrum's documentation [here](https://developer.offchainlabs.com/docs/withdrawals).
+
+For more details on Arbitrum’s protocol, see their [complete documentation](https://developer.offchainlabs.com/docs/inside_arbitrum).
+
+## Introducing The Arbitrum Truffle Box
+
+The [Truffle Arbitrum Box](https://github.com/truffle-box/arbitrum-box) provides developers with the boilerplate structure necessary to start coding for Arbitrum’s Ethereum Layer 2 solution.
+
+We provide the initial building blocks to get started working on Arbitrum without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Arbitrum Networks.
+
+Arbitrum’s Layer 2 solution is almost fully compatible with the EVM. The main difference between the EVM and the Arbitrum chain that developers will notice is that some opcodes are different and concepts such as time and gas are handled a little differently. Developers can use their regular Solidity compiler to compile contracts for Arbitrum. You can see the complete list of differences between the Arbitrum L2 chain and Ethereum [here](https://developer.offchainlabs.com/docs/differences_overview).
+
+## Integration With Infura
+
+Our colleagues at Infura are also adding full API support for the Arbitrum network. Infura users can now add the free Arbitrum add-on directly in their Infura dashboard. The Arbitrum network API largely uses the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Arbitrum network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/).
+
+Infura endpoints for the Arbitrum chain are included in the configuration of the Arbitrum Truffle Box, to aid developers in getting fully acquainted with their options when developing for Arbitrum.
+
+## Where To Get Help
+
+You can find all of the documentation for the Truffle Arbitrum Box [here](https://github.com/truffle-box/arbitrum-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
+We are thrilled to add Arbitrum to the Truffle development suite and can’t wait to see the universe of applications built on Layer 2. Stay tuned as we continue to add more networks, features, and tools that accelerate and simplify development on a secure and scalable Ethereum.
diff --git a/src/blog/truffle-and-infura-support-optimism/index.md b/src/blog/truffle-and-infura-support-optimism/index.md
new file mode 100644
index 000000000..783de64ce
--- /dev/null
+++ b/src/blog/truffle-and-infura-support-optimism/index.md
@@ -0,0 +1,39 @@
+---
+title: Truffle and Infura Now Support Optimism
+hide:
+  - navigation
+---
+
+![Truffle, Optimism Collab Image](/img/blog/truffle-and-infura-support-optimism/blog-header.png)
+
+Developer demand for scalable Ethereum application development tooling continues to grow. The multi-network Ethereum ecosystem is here, and Layer 2 solutions such as Optimistic Ethereum are leading the way. The Truffle team is delighted to support Optimistic Ethereum in helping developers build for this ecosystem. Today we are announcing the launch of the new Truffle Optimism Box.
+
+## Optimistic Ethereum
+
+Optimistic Ethereum is a Layer 2 scaling protocol for Ethereum applications. It is an application inside of Ethereum that executes transactions more efficiently than Ethereum itself, based on the concept of an [Optimistic Rollup](https://medium.com/plasma-group/ethereum-smart-contracts-in-l2-optimistic-rollup-2c1cef2ec537). The Optimistic Ethereum security model is backed by a system of “fraud proofs” that allow users to identify bad transaction results to support the accuracy of the data that is eventually rolled up and published to the main Ethereum chain. Transactions on Optimistic Ethereum are handled similarly to those on the Ethereum mainnet, and bridging between Optimistic Ethereum and mainnet Ethereum allows users to conduct gas-intensive operations on Optimistic Ethereum for a fraction of the cost.
+
+Optimistic Ethereum tracks closely to the structure and operation of the Ethereum mainnet, preserving security guarantees while increasing throughput and decreasing transaction costs. Important to note, this protocol requires a delay for bridging funds from Optimism back to Ethereum, and you can find more information about that [here](https://community.optimism.io/docs/developers/bridging.html#understanding-the-fraud-proof-window).
+
+Existing Solidity smart contracts can run on Optimistic Ethereum with minimal differences. Off-chain code such as user interfaces and wallets will need to update their RPC endpoints to interact with Optimistic Ethereum, and will largely just work once the update is made.
+
+For detailed documentation on the Optimistic Ethereum protocol, see [here](https://community.optimism.io/docs/protocol/protocol.html#introduction) and [here](https://community.optimism.io/docs/developers/integration.html).
+
+## Introducing the Truffle Optimism Box
+
+The [Truffle Optimism Box](https://github.com/truffle-box/optimism-box) provides developers with the boilerplate structure necessary to start coding for Optimism’s Ethereum Layer 2 solution.
+
+We provide the initial building blocks to get to work on Optimistic Ethereum without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Optimistic Ethereum networks.
+
+Optimism’s Layer 2 solution is almost fully compatible with the EVM, though it uses an “optimistic” EVM called the OVM. The main difference between the EVM and the OVM that developers will notice is that some opcodes are not available for contracts that are deployed to the OVM. The Truffle Optimism Box is complete with the Optimistic `solc` compiler already referenced in the `truffle-config.ovm.js` file. You can see a complete list of differences between Optimism’s fork of the `solc` compiler and the original [here](https://github.com/ethereum-optimism/solidity/compare/27d51765c0623c9f6aef7c00214e9fe705c331b1...develop-0.6).
+
+## Integration With Infura
+
+Our colleagues at Infura are also adding full API support for the Optimistic Ethereum network. Infura users can now add the free Optimism add-on directly in their Infura dashboard. The Optimism network API largely uses the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Optimistic Ethereum network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/).
+
+Infura endpoints for the Optimistic Ethereum chain are included in the configuration of the Optimism Truffle Box, to aid developers in getting fully acquainted with their options when developing for the Optimistic Ethereum chain.
+
+## Where to Get Help
+
+You can find all of the documentation for the Truffle Optimism Box [here](https://github.com/truffle-box/optimism-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
+
+We are thrilled to add Optimistic Ethereum to the Truffle development suite and can’t wait to see the universe of applications built on Layer 2. Stay tuned as we continue to add more networks, features, and tools that accelerate and simplify development on a secure and scalable Ethereum.
diff --git a/src/blog/truffle-and-infura-support-polygon/index.md b/src/blog/truffle-and-infura-support-polygon/index.md
new file mode 100644
index 000000000..c77371d2a
--- /dev/null
+++ b/src/blog/truffle-and-infura-support-polygon/index.md
@@ -0,0 +1,35 @@
+---
+title: Truffle and Infura Now Support Polygon
+hide:
+  - navigation
+---
+
+![Truffle, Infura, and Polygon Collab Image](/img/blog/truffle-and-infura-support-polygon/blog-header.png)
+
+The developer demand for scaling solutions that work directly with Ethereum is here and growing, so today we are very excited to launch the new Polygon Truffle Box. Ethereum-based dapp development is rapidly entering a new phase wherein a multi-network future is certain and Layer 2 solutions like Polygon's are leading the charge into this uncharted territory. Layer 2 scaling is essential to the health of the Ethereum ecosystem, and the Truffle team is delighted to support the Polygon PoS chain in helping developers build toward this future.
+
+## Polygon PoS Chain
+
+Polygon PoS is a hybrid Plasma Proof-of-Stake sidechain to the Ethereum mainnet which consists of a Tendermint consensus validator layer and a Plasma sidechain for block production. This configuration allows for higher transaction throughput, lower gas fees, and through Polygon's established bridges, easy connection back to the Ethereum mainnet.
+
+## Introducing the Polygon Truffle Box
+
+The core component of this new tooling is the [Truffle Polygon Box](https://github.com/truffle-box/polygon-box). This new Truffle box provides you with the boilerplate structure necessary to start coding for Polygon's Ethereum L2 solution, the Polygon PoS chain (previously the Matic PoS chain). For detailed information on how the Polygon PoS chain works, please see their documentation [here](https://docs.matic.network/docs/develop/getting-started).
+
+We provide the initial building blocks needed to get to work on Polygon PoS without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Polygon PoS networks.
+
+Polygon's L2 solution is fully compatible with the EVM. This means you will not need a new compiler to deploy Solidity contracts, and should be able to add your own Solidity contracts to this project. The main difference developers will encounter is in accessing and interacting with the Polygon PoS network. Additionally, Polygon offers multiple ways for dapp developers to implement communication between Ethereum ("Layer 1") and the Polygon PoS chain. Further information about how to enable Ethereum-Polygon communication can be found in the Polygon documentation [here](https://docs.matic.network/docs/develop/ethereum-matic/getting-started).
+
+_A quick note about naming: The Polygon ecosystem was previously called Matic Network. The chain to which we'll be deploying in the Polygon Truffle Box is now called the Polygon PoS chain. We have named this box the Polygon Box because we expect to include the ability to deploy to future Polygon chains in addition to what is presented in the initial Polygon Box, and developers using this Box may find themselves incorporating additional aspects of the Polygon ecosystem in their work._
+
+## Integration With Infura
+
+Our colleagues at Infura are also adding full API support for the Polygon network. Infura users can now add the free Polygon Network add-on directly in their Infura dashboard. The Polygon network API largely utilizes the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Polygon network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/Polygon-PoS?&utm_source=infurablog&utm_medium=referral&utm_campaign=announcement&utm_content=polygon-launch).
+
+Infura endpoints for the Polygon PoS chain are included in the configuration of the Polygon Truffle Box, to aid developers in getting fully acquainted with their options when developing for the Polygon PoS chain.
+
+## Where to Get Help
+
+You can find all of the documentation for the Truffle Polygon box [here](https://github.com/truffle-box/polygon-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
+
+We are very excited to add Polygon PoS to our development suite and we can't wait to see all of the amazing applications built with these tools. Stay tuned as we continue to add more networks, features, and products that accelerate and simplify development on this exciting new technology.
diff --git a/src/blog/truffle-boxes-making-life-sweeter/index.md b/src/blog/truffle-boxes-making-life-sweeter/index.md
new file mode 100644
index 000000000..e498526e9
--- /dev/null
+++ b/src/blog/truffle-boxes-making-life-sweeter/index.md
@@ -0,0 +1,37 @@
+---
+title: Truffle Boxes - Making Life Sweeter
+hide:
+  - navigation
+---
+
+When users begin developing on Ethereum, the first question they ask is, "Where do I start?". In the past, there hasn't been an easy answer: the answer generally consisted of many flavors of "it depends", and usually led to an investigation of what the user was trying to build, a general overview of their development skills, their knowledge of Ethereum, and the libraries and tools they're already most comfortable with. When determining how the Truffle team can help in this process, it quickly became apparent that what our users needed were examples. _Many of them._ So, being the upstanding community members we are, we set out to create those example, and today, we're happy to show you what we've accomplished.
+
+## Introducing Truffle Boxes!
+
+A Truffle box is an example Ethereum application and/or boilerplate that puts complimentary tools and libraries into a single, sweet, easily-downloadable package. Every Truffle box comes with libraries and tools already preinstalled, code that uses those libraries and tools, external scripts (if necessary), as well as helpful README's and documentation. All Truffle boxes are directly integrated into the Truffle command line, and you need only type `truffle unbox <box name>` to download and prepare your box of choice.
+
+**[Click here for a list of all available boxes.](/boxes)** Ensure you've installed the latest version of Truffle before opening your first box.
+
+-----------------
+
+Today's release comes with three officially-supported boxes, as well as one community-supported box. Our officially-supported boxes are:
+
+* [react](/boxes/react): A box that pairs Truffle with React in an easy to understand structure, meant for a web-based Ethereum application.
+* [react-auth](/boxes/react-auth): Our `react` box with extra goodies for authentication powered by smart contracts.
+* [react-uport](/boxes/react-uport): Like `react-auth`, but authentication is powered by Uport.
+
+Perhaps the most exciting part of this release -- our _pièce de résistance_ -- is the [Status Truffle box](/boxes/status), our first community-supported box. This box was created by the Status team, and instantly links Truffle and Status together with an example application and all the tools and libraries you need to build your own Status dapp.
+
+## Get Involved: Make Your Own Box
+
+We've released four boxes out of the gate to get you started, but this isn't just our candy store. **We want you to contribute** to the boxes on our site. If you have boilerplate code, an example dapp, a helpful integration or an exciting dapp stack (say, an Ethereum-enabled iOS app built with Truffle), send us an email at [boxes@trufflesuite.com](mailto:boxes@trufflesuite.com?subject=Truffle%20box%20review) and we'll look it over. If it's awesome, we'll list it on our site with your name front and center. If it's better than awesome, we'll help contribute and maintain it and make it an officially-supported Truffle box. With Truffle, you can share your code with others and help build the community, one box at a time.
+
+## One More thing...
+
+There's always one more thing. Fair warning, this one's techy. Right now, all the boxes you're seeing are static pages showing off what we and the Status team have built. Soon, however, we'll be taking on the ultimate challenge and will be creating a Truffle box registry, built on top of Ethereum, to help market and promote our community-supported boxes. Of course we'll be using Truffle, which adds a whole new layer of sweetness. Stay tuned for more details about the registry and how you can use the Ethereum blockchain to become a Truffle contributor.
+
+As always, we thank everyone for your support, and would love to hear from you. Don't hesitate to reach out on our [community Gitter channel](https://gitter.im/ConsenSys/truffle) where hundreds of your fellow Trufflers congregate to answer your questions.
+
+Cheers!
+
+-- Tim & the Truffle Team
diff --git a/src/blog/truffle-teams-gets-a-new-look/index.md b/src/blog/truffle-teams-gets-a-new-look/index.md
new file mode 100644
index 000000000..04b209ab6
--- /dev/null
+++ b/src/blog/truffle-teams-gets-a-new-look/index.md
@@ -0,0 +1,53 @@
+---
+title: Truffle Teams Gets a New Look!
+hide:
+  - navigation
+---
+
+![Truffle Teams Redesign Banner](/img/blog/truffle-teams-gets-a-new-look/banner.png)
+
+Thanks to [Josh Quintal](https://github.com/DiscRiskandBisque) and [Heyse Li](https://github.com/honestbonsai), the redesign of Truffle Teams is complete! Josh presented the [Theobromine design system at TruffleCon 2019](https://www.youtube.com/watch?v=aoU710h38xE&t=1m47s), and this release is the first step towards this vision! In addition to the stylistic upgrade, we've redesigned the app navigation to help you focus on a single repository at a time.
+
+Read more below about the most recent changes, or [go check them out for yourself](https://my.truffleteams.com)!
+
+## Redesign
+
+The Theobromine Design System uplifts the entire Truffle Teams application. This lighter theme makes the application feel more welcoming and presents itself more as a professional productivity tool.
+
+![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-builds.png)
+
+We also added support to collapse the left navbar to give you some more screen real estate. This is super helpful for those with small or vertical screens; it’s also instrumental for multitaskers that use Truffle Teams in a split-screen setup.
+
+![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-build-detail.png)
+
+## Navigation Updates
+
+The previous iteration of Truffle Teams utilized a "feature first" navigation where you would select the feature you'd like to see (Builds, Deployments, Monitoring [formally known as Data]) and then select the repository you'd want to drill into. We found this to be a jarring and tedious experience, so we changed things to be "repository first".
+
+When you login, you'll now see a home page with a list of your repositories. You can quickly search for a repository or keep your favorites at the top of the list by pinning them.
+
+![Teams Redesign - Home Page](/img/blog/truffle-teams-gets-a-new-look/teams-home.png)
+
+After clicking on a repository you'll be presented with the details of that repository. On the Builds page you'll now see a history of your builds rather than seeing the list of your repositories. The Deployments and Monitoring pages will look familiar as they haven't changed much other than not having to select the repository again.
+
+![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-builds.png)
+
+Want to focus on a different repository? You can quickly switch between them using the breadcrumb dropdown at the top of each page.
+
+![Teams Redesign - Breadcrumb Dropdown](/img/blog/truffle-teams-gets-a-new-look/teams-repo-breadcrumb.png)
+
+You can also click the Truffle Teams logo in the top left to go back to the home page with the search bar and pinned repositories.
+
+![Teams Redesign - Logo in Top Left](/img/blog/truffle-teams-gets-a-new-look/teams-logo-to-home.png)
+
+## Got Feedback or Questions?
+
+If you aren't aware of our official support channel, head over to [the Truffle Teams channel in Spectrum.chat](https://spectrum.chat/trufflesuite/truffle-teams). Posting a thread there will ping us in our internal Slack workspace and we'll answer you ASAP. You can also submit Truffle Teams feature requests and issues [on GitHub](https://github.com/trufflesuite/truffle-teams/issues).
+
+<div class="post-trufflecon-box mt-5 text-center">
+  Get started with Truffle Teams, and see the redesign for yourself!
+
+  <div class="mt-3">
+    <a class="btn btn-truffle" href="/docs/teams/getting-started/creating-an-account">Try Truffle Teams</a>
+  </div>
+</div>
diff --git a/src/blog/truffle-teams-now-supports-private-repositories/index.md b/src/blog/truffle-teams-now-supports-private-repositories/index.md
new file mode 100644
index 000000000..04589a051
--- /dev/null
+++ b/src/blog/truffle-teams-now-supports-private-repositories/index.md
@@ -0,0 +1,37 @@
+---
+title: Truffle Teams Now Supports Private Repositories
+hide:
+  - navigation
+---
+
+Thanks to the awesome work of [@nicholasjpaterno](https://github.com/nicholasjpaterno), you can now integrate private repositories with Truffle Teams! This will eventually be a premium feature, but we're releasing it for free while the product is still in beta.
+
+## Using Private Repos
+
+<figure>
+  <img src="/img/blog/truffle-teams-now-supports-private-repositories/tt-private-repo-badge.png" alt="Example of Truffle DB" style="width:100%; box-shadow: 0px 3px 5px 0px rgba(0,0,0,0.25);">
+  <figcaption>Here we see the lock icon denoting a private repository and an indication of this being a future premium feature.</figcaption>
+</figure>
+
+There are no extra steps to use your private repositories with Truffle Teams! Simply [add your repo](https://github.com/apps/truffle-teams), and automatic builds should start working! Private repos will have a lock icon next to their name indicating their private status. Otherwise, they have the same functionality as public repos.
+
+You'll see that we're very loud about which features will be premium. We'll continue this practice for future premium features so that we stay transparent about what's to come.
+
+## Next Up: Deployments!
+
+Here's a teaser of our next upcoming feature: Graduated Deployments.
+
+<figure>
+  <img src="/img/blog/truffle-teams-now-supports-private-repositories/tt-deployments.png" alt="Example of Truffle DB" style="width:100%; box-shadow: 0px 3px 5px 0px rgba(0,0,0,0.25);">
+  <figcaption>The main deployments screen showing successful testnet and mainnet deployments.</figcaption>
+</figure>
+
+You'll be able to deploy any commit with a successful build to Ropsten, Rinkeby, and Mainnet Ethereum networks (with more to come soon!). You'll get some useful contextual information for your deployments: the status of the deployment, when it took place, who on your team deployed it, the contracts deployed, the ability to download your Truffle Artifacts, and more.
+
+Deploy to the Staging environment (Ropsten and Rinkeby currently) to make sure everything works out. Once you're ready, you can easily graduate a deployment in Staging to Production (Mainnet currently). We're using `truffle migrate` under the hood, so your existing migration scripts will work just fine.
+
+We've distilled the deployment process into an informative and helpful wizard to guide you through the deployment process. With this wizard and leveraging [MetaMask](https://metamask.io) for signing transactions, we are finally giving you an interface that makes it easier to deploy for seasoned and new devs alike!
+
+We'll release a full article with all the details about using Truffle Teams' deployment features once it's ready for release.
+
+Thank you and happy truffling!
\ No newline at end of file
diff --git a/src/blog/truffle-v5-has-arrived/index.md b/src/blog/truffle-v5-has-arrived/index.md
new file mode 100644
index 000000000..d99e291d3
--- /dev/null
+++ b/src/blog/truffle-v5-has-arrived/index.md
@@ -0,0 +1,113 @@
+---
+title: Truffle v5 has arrived!
+hide:
+  - navigation
+---
+
+We have just released the most awaited version of Truffle just in time for the
+holidays! There are SO many exciting things that we would like to mention that
+will make your Truffle experience a rich one. Highlighted below are the new
+exciting things Truffle has to offer.
+
+👯    [Download Truffle v5](/truffle) or check out the
+full [Release Notes](https://github.com/trufflesuite/truffle/releases/tag/v5.0.0).    👯
+
+- **Bring your own compiler!** You can now choose any solc-js version
+  available at solc-bin. Just tell Truffle which version you want to use and it
+  will automatically fetch it for you! This feature also includes the ability to
+  use Docker and native binaries in an advanced way.
+
+- **Web3 1.0** - The truffle-contract package is now using Web3.js 1.0! This
+  will greatly improve error handling!
+
+- **New migrations command** - In v5, the `migrate` command has been completely
+  rewritten. We have included better error messages: e.g., when a deployment fails
+  Truffle will notify you and give you an idea of possible fixes. Truffle will
+  now also give you more information about what is going on when you deploy a
+  contract. This includes cost summaries and real time status updates about the
+  amount of time a transaction has been pending.
+
+  Dry run simulations also now run automatically if you are deploying to a known
+  public network and using the `--interactive` flag on the command line will give
+  you a prompt between dry runs and real deployments.
+
+  Another improvement is the ability to configure the amount of block confirmations
+  in between deployments. This allows the user to specify the number of blocks to
+  wait before transactions time out.
+
+- **Usage analytics** - Usage analytics have been added and users can opt-in by
+  running `truffle config --enable-analytics`. We think this feature will be a
+  vital tool that will help us to make informed decisions about the future of Truffle
+  and to determine what is most valuable to our users. When enabled, Truffle will
+  collect information about your version number, the commands you run, and
+  whether commands succeed or fail. And of course, it will do so in an anonymous
+  fashion.
+
+- **`truffle run <command>`** -  Truffle now gives users the ability to create
+  custom command plugins. This feature is still in its infancy so let us know
+  what you think!
+
+- **Vyper support** - Another added feature is that Truffle will now compile
+  `*.vy` contracts. We have published a Truffle Box to help you get started
+  with Vyper. You can access it by running:
+
+  ```shell
+  $ truffle unbox vyper-example
+  ```
+
+  (Make sure you have [Vyper](https://vyper.readthedocs.io/en/latest/installing-vyper.html) installed.)
+
+- **Solidity v0.5.0** - Truffle also now ships with Solidity v0.5.0 by default.
+  Solidity v0.4.xx is still supported and can be used by specifying the version
+  you wish to use in your Truffle config.
+
+-  **Structured function parameters** - Truffle has been upgraded to use
+   Web3.js v1.0. This has allowed us to include support for passing/returning
+   ‘struct’s in Solidity functions. To use this ability, you need to specify the
+   following at the top of your contracts:
+
+  ```solidity
+  pragma experimental ABIEncoderV2
+  ```
+
+  This feature allows you to use complex function arguments and have the values
+  returned so that they can interact with other contracts via truffle-contract’s
+  JS interface.
+
+- **Help system** - Now access Truffle’s built in help system by running:
+  ```shell
+  $ truffle help <command>
+  ```
+
+  This allows you to see all the available options for the command as well as a
+  description of what it does.
+
+- **Unique `truffle develop` mnemonics** - Truffle will now generate random mnemonics
+  that will persist only for you. Use caution with crypto security when working
+  with mnemonics and private keys!
+
+- **Debugger improvements** - v5 includes debugger breakpoints! Add breakpoints
+  using the ’b’ command and remove them using the ‘B’ command. Additionally we
+  have added mapping support for the debugger!
+
+- **`truffle init` / `truffle unbox`** - These commands have been improved and
+  you are now asked if you want to overwrite files in the case of name conflicts
+  in the target directory. A force option (--force) has also been added in the
+  case where you wish to overwrite the files automatically and avoid the
+  prompt.
+
+- **`async`/`await`** - Support for async/await syntax in the Truffle console
+  is also now available!
+
+Looking towards the future we intend to add third-party plugins and
+hope through our fancy, improved analaytics to provide features the community
+needs most!
+
+![V5 Breaking Changes](/img/blog/truffle-v5-blog-media/breaking-changes-photo-v5.png)
+
+**Thank you to all who have helped make this release of Truffle possible! We
+hope you enjoy this new Truffle release and ask that you let us know if you have
+any suggestions or problems on our community Gitter channel or on our GitHub
+page!**
+
+[Get started with Truffle v5 today!](/truffle)
diff --git a/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md b/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
new file mode 100644
index 000000000..af065564b
--- /dev/null
+++ b/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
@@ -0,0 +1,46 @@
+---
+title: Try New Features First with Truffle Teams Early Access
+hide:
+  - navigation
+---
+
+![Truffle Teams Early Access Banner](/img/blog/try-new-features-first-with-truffle-teams-early-access/blog-header.png)
+
+Truffle Teams is constantly evolving. Between adding new features, polishing, and refining the app there's so much we'd love to share with the world in a faster way. Wouldn't it be nice to take those new enhancements and features for a test drive? Now you can with early access!
+
+</div></div></div>
+
+<figure class="breakout">
+  <img class="mb-4 w-100 figure-shadow" src="/img/blog/try-new-features-first-with-truffle-teams-early-access/early-access-1.png" alt="Enabling Early Access from the settings screen">
+  <figcaption class="text-center font-italic">Enable early access with just one click!</figcaption>
+</figure>
+
+<div class="container container-post"><div class="row justify-content-center"><div class="col">
+
+## How Early Access Works
+
+To join early access, select the Early Access option in the Advanced tab via the account Settings Page. This account will now have access to new features and enhancements we're cooking up. First up is a hotly anticipated feature--the debugger, [which you can learn more about here](/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger).
+
+We'll provide a helpful reminder as to where you can provide feedback and request support. Your feedback is one of the most important parts of this process, and we're excited to hear from you in the earlier phases of development!
+
+Want to switch back to the stable track? You can disable Early Access at any time, but anything that requires data storage will be erased.
+
+We hope you enjoy getting a taste of what's to come!
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT TRUFFLE TEAMS EARLY ACCESS</a>
+</div>
+
+## Continue the Conversation
+
+We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven't met yet.
+
+Continue the conversation with your fellow Trufflers in our Slack community!
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
+</div>
+
+Thanks!
+
+_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md b/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
new file mode 100644
index 000000000..47cf621d7
--- /dev/null
+++ b/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
@@ -0,0 +1,44 @@
+---
+title: Unwrap the Corda Flavored Ganache Beta
+hide:
+  - navigation
+---
+
+![Truffle Teams Deployments Banner](/img/blog/unwrap-the-corda-flavored-ganache-beta/corda-ganache-beta-blog-banner.png)
+
+Earlier this year at TruffleCon [we announced our partnership with Corda to develop a Corda Flavored Ganache](https://youtu.be/MtOaXVt1yOE?t=697). Then, at CordaCon in London [we shared more details around the integration](https://www.r3.com/videos/truffle-and-corda/).
+
+**Today, we are proud to share with you [the beta release is live](https://github.com/trufflesuite/ganache/releases/tag/v2.3.0-beta.1)!**
+
+As a quick refresher: Ganache is Truffle's "one click blockchain" that allows you to run a test network for local development. You don't need an internet connection and because it's all on the same machine, Ganache allows users to see the status of the network in greater detail than on a live network.
+
+<figure>
+  <img src="/img/blog/unwrap-the-corda-flavored-ganache-beta/corda-ganache-beta-screenshot.png" alt="Corda Flavored Ganache startup screen" style="width:100%">
+  <figcaption class="text-center">The workspace selection screen--now with Corda!</figcaption>
+</figure>
+
+We're thrilled to release Ganache for the Corda Blockchain, as this lowers the barrier of entry for Corda developers by allowing them to easily set up a local network on their machines, giving introspection into the state of that network across various nodes and visibility to transactions normally hidden by a live Corda network's privacy protections.
+
+With the Beta version, Corda Flavored Ganache brings you:
+
+* **One-click** Corda network configuration and initialization, so you can focus on what matters most: your application.
+* **Easy access** to all your application's data, including network map, notaries, nodes, transactions, and states.
+* **Multiple workspaces** for all of your Corda projects; workspaces contain configurations of a Corda network map, notaries, nodes, transactions, accounts, and ledgers.
+
+As always, Truffle's tools come standard on Windows, macOS, and Linux.
+
+We are excited to share this with the Corda community and **we also need to your help!** Since this is a Beta release, we know it's not perfect. If you find a bug, do us a favor and file an issue [here](https://github.com/trufflesuite/ganache/issues/new).
+
+<a href="https://share.hsforms.com/1jbMAfLzGSj6HWx_-na9Bew34pbp">✉️ Sign up for the Corda Flavored Ganache mailing list here</a> to get the latest updates on all things Ganache + Corda.
+
+If you don't hear from us immediately, know that our team is taking some much needed time off starting today. We'll be back January 6th, 2020 ready to dive into your feedback! 
+
+If you see them around the net, make sure to give a _**HUGE thank you**_ to [David Murdoch and Nick Paterno](/staff). Their hard work made this all possible and we're a very fortunate organization to have them aboard! 💖
+
+<div class="post-trufflecon-box mt-5 text-center">
+  Try the Corda Flavored Ganache beta and let us know what you think!
+
+  <div class="mt-3">
+    <a class="btn btn-truffle" href="https://github.com/trufflesuite/ganache/releases/tag/v2.3.0-beta.1">Download Corda Flavored Ganache</a>
+  </div>
+</div>
\ No newline at end of file
diff --git a/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md b/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
new file mode 100644
index 000000000..ab0f471f0
--- /dev/null
+++ b/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
@@ -0,0 +1,25 @@
+---
+title: Upcoming improvements to encoding and decoding
+hide:
+  - navigation
+---
+
+When you’re writing, running, or debugging your smart contract, you don’t want to have to deal with raw binary data. Truffle––and Ganache and Drizzle––already contain a number of encoding and decoding features to help you interact with your contract and understand what you’re seeing. But luckily, encoding and decoding are about to become even more robust, informative, and usable.
+
+Not all of these features will be immediately available in Truffle 5.1, but some will, so let’s start with one that will be ready! Allow me to illustrate:
+
+![Syntax Highlighting](/img/blog/upcoming-improvements-to-encoding-and-decoding/syntax-highlighting.png)
+
+Yes, debugging displays are about to become quite a bit more colorful! And though it’s not related to decoding, yes that is `syntax highlighting` in the debugger! Of course, it’s not just a matter of color. Previously, many data types displayed inappropriately as strings, and enums displayed as objects. Now, each data type will be displayed in a form (and color) that makes sense, making them recognizable at a glance. No longer will a function be confused for a string!
+
+![Contracts and External Functions](/img/blog/upcoming-improvements-to-encoding-and-decoding/contracts-and-external-functions.png)
+
+Of course, this wouldn’t be possible without our new, more machine-readable, decoder output format. This one’s a little technical, and it’s not something you’re likely to find yourself dealing with directly -- you probably aren’t using Truffle Decoder directly. But Ganache and Drizzle both make use of it, and as they update to incorporate the new format, you’ll be able to get a better view of the state of your contracts with them.
+
+But that’s not all; we’re also intending to eventually integrate these encoding and decoding features into Truffle Contract. This will allow you to send transactions and decode events that you currently can’t!
+
+For instance, Vyper contracts support decimal fractions as a datatype, but our current encoder and decoder, and the ethers library, do not support these. If you want to send a transaction (or if your contract emits an event) that takes a decimal fraction as input, you are going to run into trouble. With our upcoming encoding and decoding improvements, this should no longer be a problem. (Or, for something of more concern to our Solidity users, the same applies to external function pointers.)
+
+Finally, I’d like to discuss decoding of events. Currently, when you check what events your contract may have emitted recently, you may have trouble decoding events emitted by libraries. Our new decoder, though, will be able to handle these just fine. It will even handle anonymous events! That may seem impossible, but hey, that hasn’t deterred us.
+
+We’re hoping Truffle’s new encoder and decoder will make staring at raw binary data a thing of the past! Unless you like to, of course. But for those of you who’d prefer to take a higher-level view and deal directly with what that binary data actually means… well, that’s what Truffle’s for, isn’t it?
diff --git a/src/blog/using-the-ens-integration/index.md b/src/blog/using-the-ens-integration/index.md
new file mode 100644
index 000000000..7622ce13d
--- /dev/null
+++ b/src/blog/using-the-ens-integration/index.md
@@ -0,0 +1,126 @@
+---
+title: Using Truffle's ENS Integration
+hide:
+  - navigation
+---
+
+**By Tyler Feickert, Blockchain Tools Engineer at Truffle**
+
+Among the new features released with Truffle 5.1 is support for Ethereum Name Service
+(ENS) name resolution and setting the resolver address for owned names!
+
+ENS is a system that allows for the resolution of Ethereum addresses using
+human-readable names. Like DNS, ENS aims to simplify working with addresses and
+allowing us to work with names like "truffle.eth" in place of things that cumbersomely
+resemble something like `"0x1234567890123456789012345678901234567890"`. Are you
+sure you copied that address correctly? Ready to send your Ether there?
+
+In ENS, a contract called a registry is deployed to a network. The ENS team has
+deployed a registry contract to Mainnet and several test networks. These are the
+registries that Truffle connects to by default if no registry address is set
+in the Truffle config.
+
+An ENS registry contract contains a list of names and who owns them. Each name
+also points to a resolver contract if one is set. Addresses own ENS names and
+have the ability to set the resolver that a given name points to. The resolver
+is the contract responsible for returning an address for resolution. The
+idea is that the owner will have the ability to set the resolver contract
+to return the desired address.
+
+For more detailed information on ENS, check out the [ENS website](https://ens.domains/).
+
+So we at Truffle think this project is pretty awesome and, as mentioned above,
+built an integration with it. Previously in your migrations, for example, you
+needed to manually deal with addresses. So maybe you wanted to send some
+tokens from your contract to another address. In your Truffle migration you
+might have the following code:
+
+```javascript
+await myTokenContract.sendTokens(
+  999,
+  "0x1234567890123456789012345678901234567890",
+  { from: "0x0987654321098765432109876543210987654321" }
+);
+```
+
+It is difficult and tiring to deal with raw addresses like this.
+
+Now in Truffle, if you turn on the ENS name resolution and you have a
+resolver set to your address of choice, you can do something like the
+following in place of the above:
+
+```javascript
+await myTokenContract.sendTokens(
+  999,
+  "truffle.eth",
+  { from: "my.account" }
+);
+```
+
+Well, that seems much easier to read. Under the hood during the migrations,
+Truffle will connect to the on-chain registry and automatically resolve the
+addresses for both "truffle.eth" and "my.account". You now can use
+valid ENS names in place of addresses in your migrations! In other
+words, any place that an address is expected for an argument to a
+function call, you can instead provide the ENS name.
+
+One other big piece of functionality for this ENS integration is the ability to set
+the resolution address for owned ENS addresses. You can do this using
+`deployer.ens.setAddress` in your migrations.
+
+Suppose I control an address that owns the name "arnold.hagenchop.eth" and I
+want to set the address to "0x1234123412123412341212341234121234123412". In
+this case I would write something like the following in my migration:
+
+```javascript
+const myAddress = "0x1234123412123412341212341234121234123412";
+await deployer.ens.setAddress(
+  "arnold.hagenchop.eth",
+  myAddress,
+  { from: "0x8888888888888888888888888888888888888888" }
+)
+```
+
+Now let's take a step back and look at what we did. So you can see that the
+`setAddress` method has three arguments. The first one is the name that we'd
+like to set the resolver for. As stated above we want to set the resolver
+address for "arnold.hagenchop.eth". The second argument is the address to set
+for the given name's ENS resolution. The last one is an object that resembles
+a transaction parameter object. The important thing about this object is
+that it must have a `from` property with the address that controls the name
+given as the first argument. This is important or the transaction will fail!
+
+You can find some more information about registering ENS names from the
+[ENS website](https://ens.domains/).
+
+One other useful convenience with this method is that you can also provide
+a Truffle contract object that has a deployed address as the second argument
+if you'd like. So the above code might look like the following instead:
+
+```javascript
+const MyContract = artifacts.require("MyContract");
+const myContract = await MyContract.deployed();
+await deployer.ens.setAddress(
+  "arnold.hagenchop.eth",
+  myContract,
+  { from: "0x8888888888888888888888888888888888888888" }
+)
+```
+
+In that case, "arnold.hagenchop.eth" will be set to the address at which
+`myContract` is deployed!
+
+This new integration should just be the start of a much more robust system that
+allows Truffle projects to interact with ENS! In the future, we also hope
+to add other features such as reverse resolution (resolving a name from an
+address) and automatic name registration where possible. We think this will
+be a big step forward in making the Ethereum ecosystem more accessible as well
+as convenient to work with!
+
+For more thorough information about this integration, see the
+[Truffle docs](/docs/truffle/advanced/ethereum-name-service).
+We have also created an
+[example Truffle box](https://github.com/truffle-box/v5.1-example-box#v51-example-box)
+that has some examples of using this new ENS integration alongside other new
+Truffle v5.1 features. We hope you find this feature as useful as we think
+it is! Happy Truffling!
diff --git a/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md b/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
new file mode 100644
index 000000000..2d4ad069e
--- /dev/null
+++ b/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
@@ -0,0 +1,102 @@
+---
+title: Using Truffle to interact with Chainlink Smart Contracts
+hide:
+  - navigation
+---
+
+![Truffle + Chainlink](/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/chainlink-az.png)
+
+Chainlink is one of the leading blockchain projects building the very first decentralized oracle network that provides external data to smart contracts. Truffle helps smart contract developers by providing a powerful framework to create, test, and deploy smart contracts. In Chainlink’s blog [post](https://blog.chain.link/how-to-use-chainlink-with-truffle-2/), their [Chainlink Truffle Box](https://github.com/smartcontractkit/chainlink/tree/master/evm/box) has gotten some significant upgrades! If you were fortunate enough to attend Trufflecon 2019, then you have already seen these improvements in action, thanks to Chainlink’s presentation by Thomas Hodges. To start developing your very own Chainlink smart contracts, you can grab Chainlink’s Truffle Box by following the guide [here](https://blog.chain.link/how-to-use-chainlink-with-truffle-2/).
+
+This article will showcase these brand new additions, starting with [Truffle Scripts](/docs/truffle/getting-started/writing-external-scripts). Scripts create a much easier approach to interact with our contracts, allowing us to fund a contract with LINK, request data from it, and read the contract’s data with only three commands. To demonstrate this functionality, we will first need to set up our environment variables: MNEMONIC and RPC_URL.
+
+Working with blockchain technology requires a wallet, with one of the most popular choices being [MetaMask](https://metamask.io/). Within minutes, you can have your very own Ethereum wallet that allows you to easily interact with various dApps. During account generation, you will be shown your **_secret_** 12-word seed phrase, known as your mnemonic. (Do not share this with anyone; if someone knows your _mnemonic_ they WILL have access to your addresses and private keys). Be sure to store this mnemonic somewhere safe, as you will need it later to work with our example.
+
+Furthermore, you will also need to fund your MetaMask wallet with [test LINK](https://ropsten.chain.link/) and [test ETH](https://faucet.ropsten.be/), in order to power transactions on the Ropsten Ethereum Testnet.
+
+_Note: When funding your account from a test faucet, make sure you switch from the default Main Ethereum Network to the Ropsten Test Network, to properly see your funds. You can follow any transactions made on the Ropsten Testnet via Etherscan._
+
+Our second environment variable will require an RPC URL. Some popular RPC connectivity services include [Infura](/guides/using-infura-custom-provider), [LinkPool](https://www.linkpool.io/), and [Fiews](https://fiews.io/free-rpc). After establishing a valid RPC connection and the funded address, you can start deploying smart contracts to public networks.
+
+<figure>
+  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/01.png" alt="Truffle DB data model" style="width:100%">
+  <figcaption>_Shown above are the environment variables needed to link your MetaMask wallet to Truffle, found in truffle-config.js._</figcaption>
+</figure>
+
+Once you have all the data you need, you can set your environment variables via the terminal commands:
+
+```shell
+export RPC_URL=your_url_here
+export MNEMONIC=’your 12 words here’
+```
+
+## Migration
+
+We are now ready to deploy our smart contract on a public network. To begin, run the command:
+
+```shell
+npm run migrate:live
+```
+
+This will compile all of your smart contracts, and then start deploying (migrating) them.
+
+_Note: you may encounter some compilation warnings with the Chainlink contracts. This is simply because the LINK token was originally deployed with an older version of Solidity. Given that this contract is only being deployed when you run tests, these can be ignored._
+
+<figure>
+  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/02.png" alt="Truffle DB data model" style="width:100%">
+  <figcaption>_Console output of one of our contracts deploying. This particular transaction can be found [here](https://ropsten.etherscan.io/tx/0x4c8125f0e074ce3f65b08f67f9685a0d00c2985c6ebd372507016d78c344d25b)._</figcaption>
+</figure>
+
+Deploying our `Migrations` and `MyContract` cost us Ethereum, hence why we needed the faucet from earlier. Now that our contract is deployed, we can utilize the three helper scripts to fund `MyContract` with LINK (which we got from the Chainlink faucet), create requests, and read the state.
+
+There are 3 helper scripts provided to interact with our contract, located in the scripts directory:
+
+* `fund-contract.js`
+* `request-data.js`
+* `read-contract.js`
+
+They can be used by calling them from `npx truffle exec`. First, we must fund our contract with LINK, which can be done by running the following command:
+
+```shell
+npx truffle exec scripts/fund-contract.js --network live
+```
+
+<figure>
+  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/03.png" alt="Truffle DB data model" style="width:100%">
+</figure>
+
+Following deployment, the output displays our contract address as well as the transaction address. We can also look this up on the ropsten [explorer](https://ropsten.etherscan.io/tx/0x39e48b6d8170060affdb57baf8b794424f83296aa9e105163113fea08d300504).
+
+<figure>
+  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/04.png" alt="Truffle DB data model" style="width:100%">
+</figure>
+
+Notice that upon completion, a payment of 1 LINK was sent during the transaction, clearly indicating that our contract has properly been funded. Next, we can now `request data` from the contract by running:
+
+```shell
+npx truffle exec scripts/request-data.js --network live
+```
+
+<figure>
+  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/05.png" alt="Truffle DB data model" style="width:100%">
+  <figcaption>_In the Chainlink explorer for the network that you made the request (in our example we use Ropsten, but it would work similarly for Rinkeby, Kovan, and Mainnet). As you can see the Chainlink node that we were requesting data from picked up our request and waited for 3 block confirmations before executing the job. We are now ready to read the contract’s state with the written answer from the Chainlink node, indicated by the fulfillment transaction (highlighted in red)._</figcaption>
+</figure>
+
+And finally, for reading the data we run our read-contract script. In particular, this will run faster because we’re not creating a transaction, we are simply reading the current state of the smart contract.
+
+```shell
+npx truffle exec scripts/read-contract.js --network live
+```
+
+<figure>
+  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/06.png" alt="Truffle DB data model">
+</figure>
+
+Notice for our output when reading the data, we get a number displaying the current price of LINK in USD * 100 (as of writing, 22094). This is due to the value of times specified in our smart contract request-data.js.
+
+<figure>
+  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/07.png" alt="Truffle DB data model" style="width:100%">
+  <figcaption>_Request-data.js. TRUFFLE_CL_BOX_TIMES is an environment variable which is used to override the default value of 100. This value is used for the precision of the endpoint’s response (in this case, for the price of ETH in USD), and also because Solidity cannot handle decimals. Any of these values can be changed for your project._</figcaption>
+</figure>
+
+Thanks to the power of Truffle, it has never been easier to work with smart contract development. We hope you enjoyed working with our Chainlink Truffle Box, allowing you to fully test, deploy, and interact with contracts on the network. Thanks for reading, and stay tuned for future updates at [https://blog.chain.link/](https://blog.chain.link/).
\ No newline at end of file
diff --git a/src/blog/why-i-love-trufflecon/index.md b/src/blog/why-i-love-trufflecon/index.md
new file mode 100644
index 000000000..581371614
--- /dev/null
+++ b/src/blog/why-i-love-trufflecon/index.md
@@ -0,0 +1,31 @@
+---
+title: Why I love TruffleCon
+hide:
+  - navigation
+---
+
+**By Josh Quintal, Head of Product & Marketing**
+
+The blockchain space is hitting a plateau.
+
+It’s not a bad thing: new technologies encounter a series of plateaus and this one's no different. It’s a good time to reflect and mature the ecosystem without the noise brought by rapid growth. We're in a crucible period not seen since the tech boom of the 90s. The early adopters are all here forging the blockchain-enabled world, readying for the next influx of users and companies.
+
+Remember when your friends and family raised eyebrows about this chainblock (or whatever) or thought Bitcoin was some kind of scam? Isn't that used to buy drugs? 😳 Now blockchain technology is becoming more efficient, more ubiquitous, and more accessible with each passing day. Now we hear things like "blockchain is the future" coming from outside our community.
+
+Almost two years ago when Truffle reached 4 people and that future seemed less sure, we were on our second retreat at a little place in Yakima. We mused about putting on a blockchain developer conference. Would people actually go? Who's going to speak? Can we get enough content? A few months later we decided to give it a try. Wow, people showed up--and not just that--they loved it! So many great conversations, so much valuable knowledge! Talks about smart contract upgrades, novel uses of merkle proofs, and data storage with IPFS just to name a few. A quietly skeptical Dave Burela (Blockchain Dev, MSFT and TruffleCon 2018 speaker) noted afterwards "You actually pulled it off". 🙂
+
+This year we have over 60 speakers across 60 sessions including: Thomas Hodges on Decentralized Oracles: Reliably Triggering Smart Contracts using Decentralized Computation using Truffle, Alejandro Banzas on RSK Integration with Ganache, and Greg Kapka on Developing Data-Rich Smart Contracts via Provable (Oraclize 2.0).
+
+TruffleCon is a conference, sure, but it's more than that: it's the feeling of excitement when learning a new technology; the eureka we felt when first discovering this new frontier. It's connections made in minutes that can last a lifetime.
+
+It's the culmination of everything we've worked for since the founding of this company.
+
+I hope to not only see you there but to have a chat about what we do well and how we can improve (you'll also get a hat). Together we're building the community that will take us from this plateau onward to the next meteoric growth spurt.
+
+Sincerely,
+
+<p>
+  <img style="margin-left: 0 !important; margin-bottom: 0 !important;" src="/img/blog/why-i-love-trufflecon/josh-signature.png" title="Josh Quintal Signature" alt="Josh Quintal Signature" width="150px">
+</p>
+
+Josh Quintal
diff --git a/src/blog/why-were-organizing-trufflecon-2018/index.md b/src/blog/why-were-organizing-trufflecon-2018/index.md
new file mode 100644
index 000000000..3e366cf80
--- /dev/null
+++ b/src/blog/why-were-organizing-trufflecon-2018/index.md
@@ -0,0 +1,59 @@
+---
+title: Why We're Organizing TruffleCon 2018
+hide:
+  - navigation
+---
+
+![TruffleCon 2018](/img/blog/why-were-organizing-trufflecon-2018/trufflecon2018header.jpg)
+
+As you have hopefully heard by now, [TruffleCon](/trufflecon2018), Truffle's first-ever user conference, will be on [October 5-7, 2018 in Portland, Oregon, U.S.A](/trufflecon2018).
+
+<p class="m-b-2">
+  <a href="https://trufflecon2018.eventbrite.com" class="btn btn-eventbrite m-t-1" target="_blank">Buy Tickets!</a>
+</p>
+
+## Why TruffleCon?
+
+There is certainly no shortage of conferences related to Ethereum. [Ethereal](https://etherealsummit.com) recently wrapped up in New York City, and [Devcon4](https://devcon4.ethereum.org) is ramping up in Prague later on this year. There's also [EDCON](https://edcon.io), [EthCC](https://ethcc.io), and plenty more, especially when you count those that intersect with the larger blockchain space.
+
+And yet, these events usually have a focus on the larger ecosystem. What about the people who are deep in the trenches, building the dapps and deploying the contracts?
+
+**We want TruffleCon to be the place for people who are doing the building.**
+
+Also, many developers are working in silos, connected to other teams only by GitHub, Gitter, StackExchange, Reddit, or other "[weak ties](https://en.wikipedia.org/wiki/Interpersonal_ties)". **We want to strengthen those connections to bring people together**.
+
+We want people to share their ideas, and talk about their successes and challenges. We want people to promote their projects, of course, and professional networking is always a part of these events, but more than anything else, **we want people to be heard**.
+
+## Why now?
+
+We've noticed a shift over the past year or so in the usage of Truffle.
+
+Whereas many of the comments and requests in [our Gitter channel](https://gitter.im/ConsenSys/truffle) and GitHub issues were originally regarding local tests, and in sandboxes, we noticed more and more people deploying their contracts to the public test networks and even the mainnet. While this, of course, was always the intention, it shows that **confidence in our tools and the Ethereum ecosystem is growing**.
+
+**We want to help people "go live".** And so we believe that there has never been a better time than now.
+
+## Why Portland?
+
+Portland is a vibrant city full of world-class food and drink, unmatched outdoor opportunities, and an excellent transportation system for getting where you need to go. And early October is typically a sweet spot where the days are still warm and dry, while the fall colors are starting to come into view.
+
+If you've never been, you're missing out. And why not stay awhile once you're here?
+![TruffleCon 2018](/img/blog/why-were-organizing-trufflecon-2018/portlandskyline.jpg)
+*Photo courtesy of Flickr/sama093. [Large version here](https://flic.kr/p/qg3nwJ).* 
+
+## See you in October!
+
+From Truffle founder Tim Coulter:
+
+<blockquote><em>"The best conference we could put on is one where there's a ton of active engagement. I want people to feel like they are surrounded by other people who can help them. And I want them to leave feeling like they learned something and that the Truffle community is better off because they were there.<br/><br/>
+
+If we do it right, people will go home inspired, and will change how they do their development."</em></blockquote>
+
+We can't wait to see you there. If you have questions, feel free to tweet us at [@trufflesuite](https://twitter.com/trufflesuite). And please use the hashtag [#TruffleCon](https://twitter.com/search?l=&q=%23TruffleCon&src=typd).
+
+<p class="m-b-2">
+  <a href="https://trufflecon2018.eventbrite.com" class="btn btn-eventbrite m-t-1" target="_blank">Buy Tickets!</a>
+</p>
+
+-----
+
+*Mike Pumphrey is an Enterprise Trainer at ConsenSys working on the Truffle team. With over a dozen years of experience in documentation, support, and training, Mike is passionate about making technical concepts understandable to a wider audience. Mike is also the lead organizer for TruffleCon 2018.*
diff --git a/src/blog/you-can-now-make-your-own-truffle-box/index.md b/src/blog/you-can-now-make-your-own-truffle-box/index.md
new file mode 100644
index 000000000..dcff42890
--- /dev/null
+++ b/src/blog/you-can-now-make-your-own-truffle-box/index.md
@@ -0,0 +1,37 @@
+---
+title: You Can Now Make Your Own Truffle Box
+hide:
+  - navigation
+---
+
+Two months ago we unveiled official integration with **Truffle Boxes**, example Ethereum applications and/or boilerplates that put complimentary tools and libraries into sweet, easily-downloadable packages. In addition to rolling out some official boxes, [Status.im](https://status.im/) released [the first community-supported box](/boxes/status).
+
+Today we're happy to announce anyone can now make their very own Truffle Box!
+
+## Making a Box
+
+To get started making a box, we've added a page to [our documentation](/docs/truffle/advanced/creating-a-truffle-box). For those starting a new box from scratch, we've also created a [blueprint Truffle Box](/boxes/blueprint) to get you started quickly.
+
+## The First Wave
+
+We included a call for pre-screening in the community section of our first box rollout and some trailblazers answered the call!
+
+Here are the first community boxes:
+
+**[Quintor/angular-truffle-box](/boxes/angular-truffle-box)**<br/>
+This Truffle Box provides a base for working with the Truffle Suite and Angular. It provides a basic working example of the MetaCoin contracts with Angular components. This project is generated with Angular CLI.
+
+**[hackingbeauty/react-dapp-material-ui](/boxes/react-dapp-material-ui)**<br/>
+In addition to Webpack and React, this box adds: React-Router, Redux and Material-UI for easy skinning of a Dapp.
+
+**[antony/svelte-box](/boxes/svelte-box)**<br/>
+A Truffle box using SvelteJS and Rollup. This box contains everything you need to start building a smart-contract app.
+
+**[kierenh/vue-dark-chocolate](/boxes/vue-dark-chocolate)**<br/>
+A truffle box that comes with everything you need to start using smart contracts from a Vue App with Bootstrap styling and components. Supporting frameworks include Vuex, Vue-Router & Bootstrap 4 (via Bootstrap-Vue) and webpack. The sample uses webpack-dev-server for hot-reloading or you can build and serve from express.
+
+Check out [the full list of boxes here](/boxes).
+
+A huge thank you to our entire community! We're humbled by your dedication and excited to see what's in store for the future.
+
+-- Josh & the Truffle Team
diff --git a/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md b/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md
new file mode 100644
index 000000000..203aa8c58
--- /dev/null
+++ b/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md
@@ -0,0 +1,45 @@
+---
+title: You Decide - Pipeline or Table View in Truffle Teams' Refreshed Deployments Manager
+hide:
+  - navigation
+---
+
+![Truffle Teams Deployments Refresh Banner](/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/blog-header.png)
+
+With Truffle Teams, you can manage multiple deployed instances of your smart contracts across different networks. We’ve heard mixed feedback about this workflow and are updating it accordingly: adding a table view and a deployment details page. We're also offering more insight into each deployment, by providing the cost and console output.
+
+## What’s New with Deployments?
+
+Our first iteration of Visual Deployments revolved around a pipeline view, with your commits on the left hand side and a production network on the right. While some do use and appreciate this type of workflow, many have only   a single production instance, and having an entire column just for this doesn’t make sense for those use cases. With that in mind, we’re offering a new table view, so you can see all of your deployed instances even more quickly and in an uncluttered way. In the future, you’ll also be able to sort and filter this table for even easier access.
+
+<figure>
+  <img class="mb-4 w-100 figure-shadow" src="/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/deployments-refresh-1.png" alt="The new deployments table view">
+  <figcaption class="text-center font-italic">The new deployments table view--you can still access the card view via the toggle switch in the upper-right.</figcaption>
+</figure> 
+
+You’ll also notice that clicking the name of a deployment now goes to a new deployment details screen. This contains the current status of the deployment along with its console output (an oft-requested addition)!
+
+<figure>
+  <img class="mb-4 w-100 figure-shadow" src="/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/deployments-refresh-2.png" alt="The deployment details screen">
+  <figcaption class="text-center font-italic">The deployment details screen. Notice you can now access the console output!</figcaption>
+</figure>
+
+For more information on the new deployments screen, check out the [Truffle Teams Deployments docs](/docs/teams/deployments/deployment-details).
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE DEPLOYMENTS MANAGER</a>
+</div>
+
+## Thoughts?
+
+We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven’t met yet.
+
+Continue the conversation with your fellow Trufflers in our Slack community!
+
+<div class="mt-12 text-center">
+  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
+</div>
+
+Thanks!
+
+_Josh Quintal, Head of Product & Marketing_

From b7878c33e405523f0d3123d254c313ab9a32df73 Mon Sep 17 00:00:00 2001
From: David Nguyen <minhnc@younetco.com>
Date: Mon, 21 Mar 2022 11:19:12 +0700
Subject: [PATCH 03/14] Remove not used

---
 .../index.md                                  |  29 --
 .../index.md                                  |  97 ------
 .../index.md                                  |  26 --
 .../index.md                                  |  53 ---
 .../index.md                                  |  50 ---
 .../index.md                                  | 179 ----------
 .../index.md                                  |  69 ----
 .../index.md                                  |  82 -----
 .../axonis-enterprise-use-of-truffle/index.md |  90 -----
 .../index.md                                  |  41 ---
 src/blog/blockchain-will-cure-cancer/index.md |  47 ---
 .../index.md                                  |  31 --
 .../index.md                                  |  32 --
 .../index.md                                  |  39 ---
 .../index.md                                  |  80 -----
 .../index.md                                  |  62 ----
 .../index.md                                  | 122 -------
 src/blog/designing-the-ganache-logo/index.md  |  70 ----
 .../index.md                                  |  93 ------
 src/blog/drizzle-150-a-new-beginning/index.md |  69 ----
 .../index.md                                  |  57 ----
 src/blog/drizzle-vue-a-truffle-story/index.md |  69 ----
 src/blog/ethereum-gas-exactimation/index.md   | 174 ----------
 src/blog/first-ever-truffle-retreat/index.md  | 124 -------
 .../index.md                                  |  49 ---
 src/blog/github-repository-moved/index.md     |  23 --
 .../index.md                                  |  74 -----
 .../index.md                                  |  98 ------
 .../index.md                                  |  62 ----
 .../index.md                                  |  74 -----
 src/blog/introducing-ganache-7/index.md       | 310 ------------------
 .../introducing-truffle-dashboard/index.md    | 162 ---------
 .../introducing-truffle-db-part-1/index.md    |  54 ---
 .../introducing-truffle-db-part-2/index.md    | 110 -------
 .../index.md                                  |  87 -----
 .../index.md                                  |  30 --
 .../index.md                                  |  40 ---
 .../index.md                                  |  96 ------
 .../index.md                                  |  41 ---
 .../index.md                                  |  47 ---
 .../stack-tracing-with-truffle-test/index.md  |  42 ---
 src/blog/sunsetting-truffle-teams/index.md    |  46 ---
 src/blog/take-a-dive-into-truffle-5/index.md  | 136 --------
 .../index.md                                  |  36 --
 src/blog/testrpc-is-now-ganache/index.md      |  37 ---
 .../index.md                                  |  81 -----
 .../index.md                                  |  31 --
 .../index.md                                  |  32 --
 src/blog/token-taxonomy-framework/index.md    |  15 -
 src/blog/truffle-320-released/index.md        |  44 ---
 .../index.md                                  |  50 ---
 .../index.md                                  |  38 ---
 .../index.md                                  |  39 ---
 .../index.md                                  |  35 --
 .../index.md                                  |  37 ---
 .../truffle-teams-gets-a-new-look/index.md    |  53 ---
 .../index.md                                  |  37 ---
 src/blog/truffle-v5-has-arrived/index.md      | 113 -------
 .../index.md                                  |  46 ---
 .../index.md                                  |  44 ---
 .../index.md                                  |  25 --
 src/blog/using-the-ens-integration/index.md   | 126 -------
 .../index.md                                  | 102 ------
 src/blog/why-i-love-trufflecon/index.md       |  31 --
 .../index.md                                  |  59 ----
 .../index.md                                  |  37 ---
 .../index.md                                  |  45 ---
 src/community/index.md                        |   1 -
 src/index.md                                  |   1 -
 69 files changed, 4561 deletions(-)
 delete mode 100644 src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
 delete mode 100644 src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
 delete mode 100644 src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
 delete mode 100644 src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
 delete mode 100644 src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
 delete mode 100644 src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
 delete mode 100644 src/blog/announcing-collaboration-with-filecoin/index.md
 delete mode 100644 src/blog/announcing-full-portable-solidity-debugger/index.md
 delete mode 100644 src/blog/axonis-enterprise-use-of-truffle/index.md
 delete mode 100644 src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
 delete mode 100644 src/blog/blockchain-will-cure-cancer/index.md
 delete mode 100644 src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
 delete mode 100644 src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
 delete mode 100644 src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
 delete mode 100644 src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
 delete mode 100644 src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
 delete mode 100644 src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
 delete mode 100644 src/blog/designing-the-ganache-logo/index.md
 delete mode 100644 src/blog/develop-using-fluidity-truffle-box/index.md
 delete mode 100644 src/blog/drizzle-150-a-new-beginning/index.md
 delete mode 100644 src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
 delete mode 100644 src/blog/drizzle-vue-a-truffle-story/index.md
 delete mode 100644 src/blog/ethereum-gas-exactimation/index.md
 delete mode 100644 src/blog/first-ever-truffle-retreat/index.md
 delete mode 100644 src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
 delete mode 100644 src/blog/github-repository-moved/index.md
 delete mode 100644 src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
 delete mode 100644 src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
 delete mode 100644 src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
 delete mode 100644 src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
 delete mode 100644 src/blog/introducing-ganache-7/index.md
 delete mode 100644 src/blog/introducing-truffle-dashboard/index.md
 delete mode 100644 src/blog/introducing-truffle-db-part-1/index.md
 delete mode 100644 src/blog/introducing-truffle-db-part-2/index.md
 delete mode 100644 src/blog/iterate-faster-with-truffle-teams/index.md
 delete mode 100644 src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
 delete mode 100644 src/blog/one-hundred-documentation-pull-requests/index.md
 delete mode 100644 src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
 delete mode 100644 src/blog/removing-installation-issues-continued-testrpc/index.md
 delete mode 100644 src/blog/sandbox-forking-with-truffle-teams/index.md
 delete mode 100644 src/blog/stack-tracing-with-truffle-test/index.md
 delete mode 100644 src/blog/sunsetting-truffle-teams/index.md
 delete mode 100644 src/blog/take-a-dive-into-truffle-5/index.md
 delete mode 100644 src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
 delete mode 100644 src/blog/testrpc-is-now-ganache/index.md
 delete mode 100644 src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
 delete mode 100644 src/blog/the-best-ways-to-contribute-to-truffle/index.md
 delete mode 100644 src/blog/the-blockchain-problem-that-ens-solves/index.md
 delete mode 100644 src/blog/token-taxonomy-framework/index.md
 delete mode 100644 src/blog/truffle-320-released/index.md
 delete mode 100644 src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
 delete mode 100644 src/blog/truffle-and-infura-support-arbitrum/index.md
 delete mode 100644 src/blog/truffle-and-infura-support-optimism/index.md
 delete mode 100644 src/blog/truffle-and-infura-support-polygon/index.md
 delete mode 100644 src/blog/truffle-boxes-making-life-sweeter/index.md
 delete mode 100644 src/blog/truffle-teams-gets-a-new-look/index.md
 delete mode 100644 src/blog/truffle-teams-now-supports-private-repositories/index.md
 delete mode 100644 src/blog/truffle-v5-has-arrived/index.md
 delete mode 100644 src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
 delete mode 100644 src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
 delete mode 100644 src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
 delete mode 100644 src/blog/using-the-ens-integration/index.md
 delete mode 100644 src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
 delete mode 100644 src/blog/why-i-love-trufflecon/index.md
 delete mode 100644 src/blog/why-were-organizing-trufflecon-2018/index.md
 delete mode 100644 src/blog/you-can-now-make-your-own-truffle-box/index.md
 delete mode 100644 src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md

diff --git a/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md b/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
deleted file mode 100644
index f0aa0f02c..000000000
--- a/src/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/index.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: 10 Things We Don't Do That Make Working at Truffle Awesome
-hide:
-  - navigation
----
-
-![tapestry of Truffle team headshots](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-1.jpg)
-
-At Truffle we have an extremely tight-knit team. You'll see that at this year's TruffleCon, a conference for hundreds of attendees organized by only a handful of people. We often have more work than we can handle, yet we take it on because we love the work we're doing and we love the people we work with. In my history of hopping startups – I'm currently on number nine – I haven't seen this anywhere else, so I wanted to take the time to highlight some things that set Truffle apart from the rest. Here's a list of what we don't do that makes working at Truffle awesome:
-
-1. **We don't have an office.** This is the most important point, as it permeates the makeup and structure of our organization. We have members all over the US and Canada. I live in Yakima, WA, of all places, known more for apples and hops than for tech and blockchain. For communication efficiency we intentionally hired within US time zones, but we realize remote work means there's no office to clock into. We currently have team members working from China, Japan and Germany, following the path their family and personal lives have taken them, while still remaining valuable members of the team.
-1. **We don't clock in.** For most of our team, working remotely means working from home. Often our home life and work life are intertwined, and we know that on some days work wins (i.e., I'm writing this the morning of July 4th, a holiday in the United States), and on other days life wins. This means a flexible schedule is absolutely required. Often, I tell my team to add their life events to their work calendar, like taking their dog to the vet or their kids to school, to ensure work doesn't encroach on the needs of their home life.
-1. **We don't track vacation time.** Our vacation policy is unlimited: We take whatever time we need. This is important to our work/life balance, and it also ensures our team gets much-needed breaks. Over time we've perfected this policy by engaging work and life into a little quid pro quo: If you let your coworkers know about your time off in advance, and you ensure your work is completed and fully handed off to another team member while you're away, then the time is yours. (Emergencies, of course, aren't governed by this policy.) This has worked surprisingly well. Recently a coworker "sipped bevvies" in the Bahamas for a week and a half, and his team happily held their own while he was on vacation. We all recognize that we're working extremely hard, so we all want to step in when others need a break.
-![Liz Daldalian proudly displaying a fish she caught](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-2.jpg)
-1. **We don't let people burn out.** Burn out can be a huge you-know-what. It comes on quick, often sneaking in at the tail end of an intense work effort where life lost out one too many times. It also comes when a striking life event seeps into our work life. It's an energy killer, and a turnover monster out to eat up all our employees. We don't let it eat us. After our first burn out event caused one of our best developers to leave, we created a company policy called the Get Out of Burn Out Free Card. When played, it gives the team member two weeks of vacation starting immediately, no questions asked. It's up to the rest of the team to pick up the slack, and find creative solutions in the team member's absence. It's not a card that gets played often, but it's been played a few times since and we've saved valuable team members from throwing in the towel. Even if the card never gets played, it's reassuring to know other members of the team have our backs in times of need.
-1. **We don't wear business attire.** We work from home, which means we wear the attire we'd normally wear at home. I'm known for wearing pajamas, often brightly colored ones, even during business calls. At the very least, professionalism only matters to the eye of the webcam, and anything out of frame is totally fair game. And heck, we're working hard, so we want to be comfortable.
-![Truffle team meeting featuring funny hats and coats](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-3.jpg)
-1. **We don't stay remote.** Though video calls and Slack messages are our main source of communication, we know nothing builds a relationship better than real human connection. That's why we plan full company retreats three to four times a year, to exciting places that help us all become closer. Our most recent retreat took us to the snowy mountains of Breckinridge, CO. Yes, it was super cold outside and the air was hard to breathe, but it was a new experience for all of us and we came out with some interesting stories to tell. My most memorable moment was when I commandeered a sled and careened right off the side of a hill. Lucky for me it was a false slope and I had no injuries, though my team certainly got a good laugh.
-![Truffle team in Breckenridge](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-4.jpg)
-![Truffle team at TruffleCon 2018](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-5.jpg)
-1. **We don't try to be fully flat.** We love the egalitarian nature of flat organizations, but we also love the efficiency of explicit hierarchy. In our experience flat organizations push hierarchy under the surface, turning decision-making into a confusing game of personal politics and popularity contests. Instead, we take a hybrid approach. We accept that hierarchy exists in our organization, but we try to make it as flat as possible. We push decisions as far down in the hierarchy as they can go, so each team member feels empowered to do the best work possible, and we clearly define the decisions that each role can make. As the CEO of Truffle, I get to make decisions on money and resources, but I'm also the founder, which means I once touched every line of code. That's now Nick D'Andrea's job, our head of engineering, and the jobs of the engineers leading each of our individual engineering projects.
-![Tim Coulter photoshopped as Steve Jobs](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-6.jpg)
-1. **We don't leave people hanging.** Having a light hierarchy gives us the ability to appoint leads. Leads are sometimes a vehicle for accountability, like managers in traditional organizations, but most of the time they're there to serve the members of our team. Every team member gets a lead, and gets a weekly one-on-one that they can use any way they like. Often these one-on-ones are used as a regular place to vent: they help us catch issues early and provide team members a useful outlet so small issues don't turn into something bigger. Leads go to bat for their team members when the team member doesn't feel comfortable raising an issue themselves.
-1. **We don’t give in to perfect.** At least, not initially. In our organization, perfect is the enemy of the good. Had I not been writing this on Independence Day, I may have shot for ten items to round out the list instead of nine. Similarly, it’s the same reason we release a new version of Truffle weekly: We like to bring value to users as quickly as possible, and then strive towards perfection iteratively over time. This idea governs all the work that we do, from software to sales to even our VC pitch decks, because we realize the feedback we get from users far outweighs our initial ideas at perfection. If you have thoughts on how we can better improve our blog or this blog post, please send me an email at tim@trufflesuite.com.
-1. **See #9.**
-
-Working at Truffle has been an amazing journey. It's incredibly humbling to see a project I started from necessity turn into a company run by the heart and soul of a close, tight-knit group of professionals. Truffle would be nothing without this team, and without Truffle I'd likely not be excited to go to work every morning (I commute downstairs in my pajamas, but still). Thank you, Truffle team, for making this company awesome.
-
-![Truffle team members preparing for TruffleCon 2019](/img/blog/10-things-we-dont-do-that-make-working-at-truffle-awesome/layer-7.jpg)
diff --git a/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md b/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
deleted file mode 100644
index d1463276d..000000000
--- a/src/blog/2020-is-finally-over-a-year-end-wrapup/index.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: 2020 is Finally Over - A Year End Wrapup
-hide:
-  - navigation
----
-
-![Truffle End of Year Wrapup Banner](/img/blog/2020-is-finally-over-a-year-end-wrapup/blog-header.png)
-
-2020 has been a trying time for us all: COVID-19 is still ravaging the world, the United States mired through one of our most contentious elections yet; basically, it’s been a rough year.
-
-It’s not all bad though! Let’s take a look back at some positive things that came out of 2020, along with a little of what to look forward to in 2021.
-
-## A Look Back
-
-### ConsenSys Fold-in
-
-This year was a busy one for Truffle, but the biggest news squeaked in just in time for the end of the year: Truffle is now a part of ConsenSys! We’re excited to collaborate with Infura, MythX, MetaMask, and more!
-
-### Teams Enhancements
-
-It was also a big year for Truffle Teams. We’ve added new features and enhanced existing ones to complete the core workflow Truffle Teams offers (I summarize this in our final Dapp Lifecycle webinar episode here). Big highlights include the release of:
-
-* **Dashboard** ([Blog](/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard) | [Docs](/docs/teams/dashboard/dashboard-overview)): More incoming data begets a greater need to gain insights and properly segment that data to prevent overload. Truffle Teams new dashboard provides an overview of your application, along with ways to drill down and get further context on more narrow slices.
-* **Debugger** ([Blog](/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger) | [Docs](/docs/teams/debugger/debugger-overview)): This is a huge workflow enhancement--allowing us to debug transactions in the places we're already viewing--via the deployment details screen or while monitoring individual contracts.
-* **Early Access** ([Blog](/blog/try-new-features-first-with-truffle-teams-early-access)): Truffle Teams is constantly evolving. Between adding new features, polishing, and refining the app there's so much we'd love to share with the world in a faster way. Wouldn't it be nice to take those new enhancements and features for a test drive? Now you can with early access!
-* **Deployment and Monitoring Improvements** ([Blog](/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager) | [Docs](/docs/teams/deployments/deployments-overview)): We’ve added a table view and a deployment details page. We're also offering more insight into each deployment, by providing the cost and console output.
-
-Before the end of this year, we’ll be releasing the Contract Manager to Early Access, completing the workflow and allowing teams to build, deploy, monitor, and debug conveniently in one place.
-
-### Truffle’s Unstoppable Release Schedule
-
-Going on 2 years now, Truffle has released on a weekly basis. We’re so proud of our team for their hard work and commitment to improving the lives of other developers. We don’t have any plans to stop this cadence--full steam ahead for the Truffle train!
-
-### Debugger and Test Enhancements
-
-2020 saw great improvements to Truffle, including debugging verified contracts with `truffle debug --fetch-external` ([Blog](/blog/debugging-verified-external-contracts-with-truffle-debugger)), support for stacktraces in tests with `truffle test --stacktrace` ([Blog](/blog/stack-tracing-with-truffle-test)), and even freshly-added support for stepping through Vyper contracts!
-
-### Forking in Ganache – much improved!
-
-Since the summer of 2020 saw DeFi reach a whole new level of usage, more and more people have been looking to test their code against live smart contracts on-chain. Ganache has always had its `--fork` option, but thanks to members of the community, we’ve fixed more than half a dozen critical bugs that inhibited certain use cases. Forking is more reliable than ever!
-
-### Collaborations
-
-2020 was a year of partnerships for Truffle, seeing us make good on the vision to become a multi-blockchain toolset.
-
-* **Tezos** ([Blog](/blog/branching-out-announcing-tezos-support-in-truffle) | [Docs](/docs/tezos/truffle/quickstart)): Tezos is supported in Truffle! Many of the commands you’re used to are still here: compile, deploy, test, and console!
-* **Corda** ([Blog](/blog/branching-out-phase-2-of-corda-flavored-ganache) | [Docs](/docs/ganache/corda/working-with-corda)): Ganache UI supports creating Corda networks! Easily create and introspect into a local Corada development network with a familiar UI.
-* **Filecoin** ([Blog](/blog/announcing-collaboration-with-filecoin)): Truffle Preserve allows you to easily preserve files on IPFS and/or Filecoin.
-
-## A Look Forward
-
-### Continued Maturation of Truffle Teams
-
-Truffle Teams will continue to be enhanced throughout 2021, with useful additions such as:
-
-* **Monitoring enhancements**: receive alerts when we observe contract anomalies, such as a sudden spike in failed transactions or a drop in balance. Set up your own custom triggers for things like an event firing or a certain address interacting with your contracts.
-* **Debugging public transactions**: The debugger only works for sandboxes currently, but we want to bring it to feature parity with the CLI debugger by also supporting public networks.
-* **Custom Network Support**: Deploy via your own infrastructure by supplying the RPC URL. Put your DappNode to good use!
-* **Continuous (Automated) Deployment**: You can already deploy manually via Truffle Team’s deployment wizard, but there may be times you know you’ll be continuously deploying your changes. For example iterating on a new feature in a sandbox.
-* **Better Dashboard**: The dashboard today provides a good overview of your deployment, but we’re going to expand it to provide better drill down functionality and greater context.
-
-### Advanced Analysis
-
-Truffle’s been around for over 5 years now. In that time, we’ve been thinking about how smart contract systems grow and change over time. Be on the lookout for tools to better examine your contract’s deployment history, track contracts across forks, and more!
-
-### Ganache Rewrite
-
-Ganache is getting a tune-up! This means faster execution of your test suites--**4x faster** in the case of SushiSwap’s test suite. Also lookout for ways to test pending transactions, implementation of EIP-1193, the ability to set the account nonce (`evm_setAccountNonce`), and support for running Ganache in the browser. We’ll also begin publishing auto-generated API documentation so you always have a reference close at hand.
-
-### The Return of the Frontend
-
-2020 didn’t see much movement in our set of frontend libraries, [Drizzle](https://github.com/trufflesuite/drizzle). In 2021 we’ll be giving some love to the frontend in the form of easier state management, more granular tooling, and more.
-
-### More Collaborations
-
-As mentioned above, now that we’re a part of ConsenSys Software Inc, Truffle's going to have many opportunities to collaborate with other groups. We’d love to hear what this sparks in you! Check out our Slack group below and let us know your thoughts. Here are some links to CSI’s groups so you know what they’re about:
-
-* [Infura](https://infura.io/)
-* [MythX](https://mythx.io/)
-* [ConsenSys Diligence](https://consensys.net/diligence/)
-* [MetaMask](https://metamask.io/)
-* [CodeFi](https://codefi.consensys.net/)
-* [ConsenSys Quorum](https://consensys.net/quorum/)
-
-## Catch us on Slack
-
-We want Truffle the best developer tool suite in the blockchain space for new and seasoned devs alike. Let us know what you think about our plans, or if you/your team have other needs we haven't met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Product Lead & The Whole Team at Truffle_
diff --git a/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md b/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
deleted file mode 100644
index d0fc6ab0f..000000000
--- a/src/blog/3-ways-enterprises-are-addressing-blockchain-privacy-concerns/index.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: 3 Ways Enterprises Are Addressing Blockchain Privacy Concerns
-hide:
-  - navigation
----
-
-[Blockchain has been touted as the great connector to integrate businesses under consortium networks](https://www.forbes.com/sites/andrewarnold/2019/02/21/why-2019-may-become-the-year-of-enterprise-blockchain/#66c9e516427e). It’s ability to verify data using smart contracts and provide transparency across network participants through immutable shared data has people talking about a technical revolution. However, this benefit has been a double-edged sword because the enterprise world is skeptical about sharing sensitive data on a ledger where the information cannot be deleted. The good news is, this year has seen numerous announcements of single and multi-party blockchain pilots by the Fortune 500 such as… [Starbucks](https://news.microsoft.com/transform/starbucks-turns-to-technology-to-brew-up-a-more-personal-connection-with-its-customers/) and [MetLife](https://www.forbes.com/sites/stevenehrlich/2019/06/19/metlife-plans-to-disrupt-2-7-trillion-life-insurance-industry-using-ethereum-blockchain/#3e9a87277022). Data privacy issues haven’t stopped them and the enterprise blockchain world has taken these steps to shift their thinking.
-
-## 1. Store references to data on the blockchain
-The simplest way to circumvent this data privacy issue is to not put the data on the chain. A popular approach is to share anonymous IDs on the blockchain and use that to get data from another system. For example, [MediLedger](https://www.mediledger.com/) is a supply chain pilot in the heavily regulated pharmaceutical industry that uses a blockchain to trace a drug’s exchange of hands and then uses another private peer-to-peer application to transfer details about the medication. What is passed around on the chain is just an anonymous identifier to the medication. This keeps transactions light, allows enterprises to regulate data access, and uses proven methods to secure sensitive data. MediLedger actually takes this a step further and anonymizes the transaction details with zero knowledge proofs — which I’ll cover later.
-
-## 2. Use blockchains to verify instead of share
-Blockchain’s real power is in its ability to verify data. Instead of putting actual information on the chain, a solution could combine unique elements of data and share a hash of it on the blockchain. Hashing is a cryptographic method that generates a random, unique value from a fed input. In this scenario, the resulting hash itself doesn’t reveal any information, but it can verify an on-hand document by checking if it generates the same hash when fed into the function. The data inputs could also be selected in a way that no critical information is sampled to create the hash so that compliance regulations can be withheld. Businesses have reliable methods to exchange data, but the verification is long and expensive. By using blockchain as a verifier and not the store of the data, we can ease the pain point and maintain a higher level of privacy than open sharing.
-
-## 3. Anonymize transactions with zero knowledge proofs
-Building off the two previous trends, blockchain pilots have taken an extra step in securing data and replaced hashed transaction details with zero knowledge proofs (ZKP). [ZKPs allow for verification of a transaction without exposing transaction details](https://hackernoon.com/wtf-is-zero-knowledge-proof-be5b49735f27). Now two businesses can communicate on a public network and be completely anonymous. This is because what is placed on the chain is a proof that is cryptographically verified by the receiver, not the data that goes into the transaction. This shift in data validation methods addresses data privacy concerns and supports industry consortiums.
-
-## Blockchain is just one piece of the puzzle
-
-Finally, with all the hype on blockchain’s potential in the last years, we have to remember that this is just another tool in the technology box when solving a problem. Enterprises have gotten smarter in finding ways to use blockchain to solve unique problems that are more expensive or less reliable with other technologies. What we have seen is that distributed ledgers can’t do everything, but when paired with multiple other technologies that help fill gaps, the solution as a whole is optimized. A better perspective is to not think of future solutions as blockchain applications, but rather applications that leverage the unique advantages of blockchain.
-
-## About West Monroe Partners
-
-West Monroe is a national business and technology consulting firm that partners with dynamic organizations to reimagine, build, and operate their businesses at peak performance. Our team of more than 1,400 professionals across nine offices is comprised of an uncommon blend of business consultants and deep technologists. I am one of those consultants and I am one of the leaders of our blockchain center of excellence. I’ll be presenting on Sunday morning (8/4) about one of our blockchain projects that looks to [incentivize electric vehicle owners to charge with cleaner energy](https://trufflecon2019.sched.com/event/RHIR/driving-renewable-energy-usage-with-blockchain-and-electric-vehicles). Check us out at our [website](https://www.westmonroepartners.com/) and read more about our [blockchain perspectives](https://blog.westmonroepartners.com/?s=blockchain) on our blog!
-
-Danny Pan is a consultant with West Monroe Partner’s Seattle Technology Practice. He focuses on providing value in adopting blockchain, distributed technologies, and robust SDLC practices. Contact Danny at [dpan@wmp.com](mailto:dpan@wmp.com)
diff --git a/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md b/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
deleted file mode 100644
index df6e65cb9..000000000
--- a/src/blog/5-trends-impacting-the-blockchain-developer-experience/index.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 5 Trends Impacting the Blockchain Developer Experience
-hide:
-  - navigation
----
-
-In this article we explore 5 trends impacting the developer-experience (or DX) when it comes to building blockchain-based solutions. Specifically, applications and services that leverage a blockchain or distributed ledger or as part of their overall architecture.
-
-This is, of course, is by no means a definitive list. As with everything in the industry, change is happening fast and as such, this is more of a selection of trends that are on the team’s radar. If there’s anything we’ve missed or should know about, we’d love to hear from you (or speak in person at [TruffleCon 2019](/trufflecon2019)).
-
-## #1 Development tooling release velocity is on fire
-
-Obviously we’re a little biased, but in this case, we’re talking about tools and utilities that are not [chocolate-themed](/truffle). It’s literally every day we collectively come across something new that makes our lives as developers (or users, auditors, admins, etc) easier.
-
-This is a big deal for the long-term success of the wider ecosystem because happy and productive developers obviously strongly correlates with increased experimentation, the volume of shipped products and services, and expedites the process of on-boarding new people (developers or otherwise) into the blockchain space.
-
-At Truffle, we’re also pushing harder than ever to make the DX as sweet as possible. Like, raspberry truffle sweet. This includes new features and enhancements to the existing suite (such as integration with [Hyperledger Fabric's chaincode EVM](https://github.com/trufflesuite/truffle/releases/tag/v5.0.27)), as well as the upcoming [Truffle DB](/blog/introducing-truffle-db-part-1) and [Truffle Teams](/docs/teams/overview).
-
-## #2 Managed Blockchain Services are here
-
-Managed Blockchain Services (MBS) are evolving rapidly. In the first half of 2019 alone we’ve seen the launch of new services from heavyweights such as [Microsoft](https://azure.microsoft.com/en-us/services/blockchain-service/) and [Amazon](https://aws.amazon.com/managed-blockchain/), and players such as [Kaleido](https://kaleido.io/) evolving their stack with dizzying speed.
-
-These services, of course, do all the heavy lifting when it comes to spinning up private or consortium networks, something that was historically cumbersome from a DevOps perspective. Excitingly, the maturation of these services is coinciding with an increased understanding of the use-cases for permissioned ledgers and accordingly, we’re seeing major projects and initiatives begin to roll out.
-
-The managed nature of these services has allowed the teams behind them to really focus on streamlining the developer experience Which leads us to the next trend...
-
-## #3 We’re seeing glimpses of the DX of the future
-
-In the words of William Gibson: *“The future is already here - it's just not very evenly distributed”* and with the blockchain DX it’s no different.
-
-Our favorite example of a DX from the future is [Kaleido’s Marketplace](https://marketplace.kaleido.io/) where within a few clicks you can add a [token swap service](https://marketplace.kaleido.io/service/token-swap), store data on [IPFS](https://marketplace.kaleido.io/service/ipfs-file-store), or [pin a state proof](https://marketplace.kaleido.io/service/public-ethereum-tether/) to a public network.
-
-![Example A](/img/blog/5-trends-impacting-the-blockchain-developer-experience/example-1a.png)
-
-It’s almost too easy. Seriously though, this evolution of developer experiences paves the way for how “delightful” things might one-day be when building equivalent services for public networks.
-
-## #4 Major corporations are pushing some seriously awesome open-source software
-
-While veteran projects like [OpenZeppelin](https://openzeppelin.org/) continue to blossom, one interesting trend we’ve seen is larger organizations’ increasing embrace of open-source with the recent release of some exciting new projects.
-
-Some great examples of this include Ernst & Young’s [Nightfall](https://github.com/EYBlockchain/nightfall), Samsung’s [Blockchain SDK](https://developer.samsung.com/blockchain), Microsoft’s [Confidential Consortium Framework](https://github.com/microsoft/CCF), and the continued evolution of the JPMorgan-backed [Quorum](https://github.com/jpmorganchase/quorum). We’re equally pumped by the launch of Cloudflare’s [Ethereum gateway](https://blog.cloudflare.com/cloudflare-ethereum-gateway/) too!
-
-It’s exciting to see companies of all shapes and sizes embracing the paradigm in ways that we can all benefit.
-
-## #5 Industries are becoming increasingly programmable, led by DeFi
-
-While companies like [Stripe](https://stripe.com/) have turned programming against “centralized” finance into an art form, they are inherently bound by the rules and regulations imposed by the industry itself. Decentralized Finance (or DeFi) on the other hand has no such intrinsic limitations. Want to open a Collateralized Debt Position? MakerDAO has a [JavaScript library](https://makerdao.com/documentation/#dai-js) for that. DeFi is only limited by the imagination (and programming ability) of individual developers.
-
-We’re rapidly seeing the decentralized equivalent of swaths of traditional financial services emerge, all of which are open and programmable in ways that the existing industry can only dream of.
-
-And of course it goes far beyond finance. Everything from supply chains to in-game assets are steadily turning Ethereum into the “[global platform for every asset](https://twitter.com/MuteDialog/status/1149047398532075526)”.
-
-**It’s never been a better time to building on Ethereum. From tooling to infrastructure to a world-class open-source ecosystem, the developer-experience continues to blossom.**
diff --git a/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md b/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
deleted file mode 100644
index d70676f22..000000000
--- a/src/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/index.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: A Sweet Upgradeable Contract Experience with OpenZeppelin and Truffle
-hide:
-  - navigation
----
-
-![Truffle + OpenZeppelin Banner](/img/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/blog-header.png)
-
-Immutability is a cornerstone of blockchain technology. This is great for many reasons, but presents a problem when it’s time to upgrade our smart contracts. There are a few different upgrade patterns, but one that’s proven to be robust is the proxy pattern. This pattern has, until now, involved some additional overhead for development teams. Thanks to OpenZeppelin though, you can now deploy upgradeable contract systems with ease using the familiar Truffle tool suite!
-
-## The Proxy Pattern
-
-At a high level, the proxy upgrade pattern involves deploying a proxy contract that delegates function calls to your logic and storage contracts. The proxy is storing addresses of the logic contracts and these addresses can be changed. This allows you to deploy a new version of the logic contract and point the proxy to that new version.
-
-<figure>
-  <img class="mb-4 w-100" src="/img/blog/a-sweet-upgradeable-contract-experience-with-openzeppelin-and-truffle/proxy-contract.png" alt="Proxy contract upgrade diagram">
-  <figcaption class="text-center font-italic">The proxy contract can point to any number of different logic contracts.</figcaption>
-</figure>
-
-There are many concerns around this pattern you’ll need to keep in mind, such as making sure your old contracts cannot be used maliciously. For more information on proxy patterns, [check out OpenZeppelin’s proxy pattern guide](https://docs.openzeppelin.com/upgrades/2.8/proxies).
-
-## Using the Plugin
-
-First, install the package:
-
-```bash
-npm install --save-dev @openzeppelin/truffle-upgrades
-```
-
-<p class="alert alert-info m-t-2">
-<i class="fas fa-info-circle"></i> <strong>Note</strong>: This package requires Truffle version 5.1.35 or greater.
-</p>
-
-Then, in your migration script, use the new deployProxy and upgradeProxy functions:
-
-```javascript
-const { deployProxy, upgradeProxy } = require('@openzeppelin/truffle-upgrades');
-
-const Box = artifacts.require('Box');
-const BoxV2 = artifacts.require('BoxV2');
-
-module.exports = async function (deployer) {
-  const instance = await deployProxy(Box, [42], { deployer });
-  const upgraded = await upgradeProxy(instance.address, BoxV2, { deployer });
-}
-```
-
-Now your contract systems can be much more flexible while still leveraging all of the benefits of a blockchain network. For more information on the truffle-upgrades plugin, check out [OpenZeppelin’s Truffle documentation](https://github.com/OpenZeppelin/openzeppelin-upgrades/blob/master/packages/plugin-truffle/README.md).
-
-We’re very excited about this plugin and would love to hear more about how you’re using it and how we can make the experience even better! Please let us know how you feel in [the Truffler Slack community](https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA) or on [OpenZeppelin’s forum](https://forum.openzeppelin.com/)!
\ No newline at end of file
diff --git a/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md b/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
deleted file mode 100644
index 3bcd89b70..000000000
--- a/src/blog/an-easier-way-to-deploy-your-smart-contracts/index.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
-title: An Easier Way to Deploy Your Smart Contracts
-hide:
-  - navigation
----
-
-**TL;DR** - Deploying your smart contracts shouldn't be difficult, and the process should be flexible. I give a sneak peek at the next feature we're building: an **easy to use interface to deploy your Truffle projects with [Truffle Teams](/docs/teams/overview)**! It's going to be awesome, and **you can be the first to use it**! I'll be giving a **hands-on workshop from 9AM-12PM on Friday, August 2nd, at [TruffleCon 2019](/trufflecon2019)** that will walk you through through the entire Truffle Teams lifecycle, including the **never-before-used Deployments interface**! See you there!
-
----
-
-So! You've finished implementing your dApp, you've tested it on [Ganache](/ganache), and you're ready to push it to a testnet or Mainnet! Congratula—oh wait.
-
-![One Does Not Simply Deploy to Mainnet](/img/blog/an-easier-way-to-deploy-your-smart-contracts/got-deploy-mainnet.jpg)
-
-It's not that easy.
-
-There are a handful of solutions, and none have _really_ made it painlessly easy. Even our own `truffle migrate` (aka `truffle deploy`) has left much to be desired.
-
-Well it's about to get a whole lot easier with Truffle Teams. [Skip to the good stuff.](#truffle-teams)
-
-## The Not-So-Easy Ways to Deploy Your Smart Contracts
-
-So what's wrong with what's already made? Why make _yet another_ tool? I hear you. Let's take a look at what **is** available, and if you're still meh, I'd love to talk to you at [TruffleCon](/trufflecon2019)!
-
-<h3 class="link-markdown">
-  <a href="#remix" name="remix">
-    <i class="fas fa-link">
-    </i>
-  </a>
-  <div>
-    <span>Remix</span>
-    <img style="margin: 0 !important; display: inline-block !important;" src="/img/blog/an-easier-way-to-deploy-your-smart-contracts/remix-logo.svg"  width="40px" title="Remix" alt="Remix">
-  </div>
-</h3>
-
-![Remix IDE](/img/blog/an-easier-way-to-deploy-your-smart-contracts/remix.png)
-
-Oh [Remix](https://remix.ethereum.org), we all have fond memories of you. And many people still use Remix for all sorts of use cases! Remix gives you an in-browser Ethereum IDE, letting you develop, compile, test, debug, and deploy smart contracts for Ethereum. And it's probably the least amount of work needed to throw a single smart contract onto a testnet or Mainnet (i.e. when deploying a single `.sol` file).
-
-Remix, as of version `0.7.7`, gives you a simple `Deploy` button. This will send a transaction to the `web3` provider of your choice (many use [MetaMask](https://metamask.io)), and you're off to the races!
-
-Great, right?
-
-Well, Remix gets harder to use as you add more contracts, import 3rd party contracts, work as a whole team, etc. It's definitely flexible and able to handle these use cases (though not without legwork and configuration), but it's not my personal preference for developing large, complex dApps.
-
-<h3 class="link-markdown">
-  <a href="#truffle-cli" name="truffle-cli">
-    <i class="fas fa-link">
-    </i>
-  </a>
-  <div>
-    <span>Truffle CLI</span>
-    <img style="margin: 0 !important; display: inline-block !important;" src="/img/truffle-logo-light.svg"  width="50px" title="Truffle" alt="Truffle">
-  </div>
-</h3>
-
-Enter [Truffle](/truffle).
-
-It's a fantastic framework (not to toot our own horns) that lets you develop your dApp in a flexible and extensible way. It provides structure to keep you sane in this chaotic world of Web 3.0.
-
-It even gives you a mechanism to define what deploying (aka: "migrating") means for your application. You can specify what contracts get deployed in which order with whatever arguments you require. For instance, your smart contracts may depend on the deployment of a past contract, which you can easily code in migration scripts.
-
-**And it's as easy as running `truffle migrate`!**
-
-...and if you were deploying directly to [Ganache](/ganache), that'd be entirely true.
-
-![Running `truffle migrate`](/img/blog/an-easier-way-to-deploy-your-smart-contracts/truffle.png)
-
-But that's not the case when we start talking about testnets or Mainnet.
-
-The **easiest** way to deploy to an external network is by using [Truffle's HD Wallet Provider](/docs/truffle/reference/configuration#providers). However, this requires you to somehow get your mnemonic or private key into the `truffle-config.js` config file, **without committing it to your provider source control provider (PLEASE don't do this - you'll get your Ether stolen).** To use an account you created with MetaMask, you'd need to export your private key from MetaMask (or your mnemonic, if you're feeling lucky 😱) and create the boilerplate code to read in the key from an environment variable (to prevent committing it to your repository and sharing it publicly).
-
-In all truthfulness, this isn't too bad, but it's also a bit too much config for me. I'd much rather use MetaMask directly to authenticate transactions during deployments.
-
-### Custom Management Web Interface
-
-Some devs will create a small front-end web interface which uses [web3.js](https://github.com/ethereum/web3.js) to deploy their smart contracts. I have done this personally in my [Game of Thrones Death Pool](https://seesemichaelj.github.io/game-of-thrones-death-pool) project, and I chalked it up to "well I can put this on a website and others can deploy their own versions."
-
-![Custom Management Web Interface for GoT Death Pool](/img/blog/an-easier-way-to-deploy-your-smart-contracts/got-death-pool.png)
-
-Sometimes this is necessary, but it's more work if it's not absolutely needed for your application.
-
-## My Version of an Ideal Deployment Interface
-
-In an ideal world, I'd like these features in a deployment interface:
-
-<ul>
-  <li>Lets me use MetaMask directly for signing transactions
-    <ul>
-      <li style="margin-bottom: 0 !important;">Remix ✔️ | Truffle CLI ❌ | Custom Webapp ✔️</li>
-      <li>A bonus win here is support for Ledger and Trezor wallets!</li>
-    </ul>
-  </li>
-  <li>I can use a framework/toolset/etc. that lets me build complex apps and supports complex deployment processes
-    <ul>
-      <li>Remix ❌ | Truffle CLI ✔️ | Custom Webapp ✔️</li>
-    </ul>
-  </li>
-  <li>I don't need to do a lot of work to go from finishing development to deploying
-    <ul>
-      <li>Remix ✔️ | Truffle CLI ✔️ | Custom Webapp ❌</li>
-    </ul>
-  </li>
-</ul>
-
-<h3 class="link-markdown">
-  <a href="#truffle-teams" name="truffle-teams">
-    <i class="fas fa-link">
-    </i>
-  </a>
-  <div>
-    <span>Introducing: Truffle Teams Deployments</span>
-    <img style="margin: 0 !important; display: inline-block !important;" src="/img/tt-logomark.svg"  width="50px" title="Truffle Teams" alt="Truffle Teams">
-  </div>
-</h3>
-
-If you haven't heard about our latest tool, [Truffle Teams](/docs/teams/overview), you really should check it out. Truffle Teams gives you zero-config Continuous Integration (CI) for your Truffle projects, and it also lets you monitor what's happening with your deployed contracts. Truffle Teams meshes the full Truffle Suite into a cohesive application that enables better collaboration within development teams (even teams of 1!).
-
-![Truffle Teams Builds](/img/blog/an-easier-way-to-deploy-your-smart-contracts/teams-build.png)
-
-The next big feature we're working on is Deployments. We already compile your contracts from your Truffle project for you when you make a commit to GitHub; why can't we migrate/deploy them as well? Further, Truffle Teams is a web application, allowing for easy integration with [MetaMask](https://metamask.io).
-
-We're looking at this from a [DevOps](https://en.wikipedia.org/wiki/DevOps) perspective, and we're trying to create an extensible system that will support projects and teams of **any size**.
-
-### Connect Your GitHub Repository to Truffle Teams
-
-To get started with Truffle Teams, you must first connect your GitHub repository. This is a simple step, and we have instructions on how to do this [here](/docs/teams/quickstart).
-
-### Setup Your Migrations Scripts
-
-If you haven't built a Truffle project, you should really give it a try; the [Pet Shop Tutorial](/tutorial) is a great place to start as it gives a good survey of the different facets of Truffle, including the `migration` scripts. These scripts let you define the behavior of deploying your smart contracts using a language you're already familiar with. In the tutorial, you deploy a single contract, but it has the flexibility to do so much more (i.e. you can deploy one contract, get its address, and use that in the constructor when deploying another contract).
-
-Setting up these scripts is part of the development lifecycle of creating a Truffle project, so I won't cover that here. But that's great! You should already be done with this step!!
-
-### Commit to GitHub
-
-Welp. That was easy. 😅
-
-### Monitor the Status of Your Build
-
-Head over to https://my.truffleteams.com and click on the `BUILDS` tab if you're not there already. You can see a build has been queued or has started to process. You can click on the repository name in the card to see more details. You can also get to this page by clicking on the yellow dot in GitHub next to your commit and pressing `Details`.
-
-![Teams Builds More Details](/img/docs/teams/starting-builds-comp.png)
-
-### All Your Tests Pass, Let's Deploy! (but only to a testnet just to be sure)
-
-> NOTE: This is just a sneak peek of features to come! You won't be able to follow along (yet, but [stay tuned](https://share.hsforms.com/1OaTglVhGTdWk7spR6nE_AA34pbp)!).
-
-Great! Your builds are passing, and you're ready to deploy to a testnet (i.e. Ropsten) to see if everything works.
-
-Now head over to the `DEPLOYMENTS` tab and select your repository.
-
-You'll now see a screen that shows a list of builds for your commits on the left.
-
-![Deployments Empty](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployments-empty.png)
-
-Deploying a build is as simple as hovering over the commit, pressing a button, and selecting which network you'd like to deploy to.
-
-![Deployment Wizard Select](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployment-wizard-select.png)
-
-Truffle Teams will then start the migration/deployment process. Each transaction is sent to the web application and MetaMask will prompt you to confirm transactions. By leveraging MetaMask, we can give you **[Ledger](https://www.ledger.com) and [Trezor](https://trezor.io) hardware wallet support too! 🔒**
-
-![MetaMask Transaction](/img/blog/an-easier-way-to-deploy-your-smart-contracts/metamask-tx.png)
-
-### Happy With a Released Version? Promote it to Production (aka deploy to Mainnet)
-
-But we're not done yet! You've finished your testing on Ropsten, and you're now ready to deploy to Mainnet. With the upcoming version of Teams, you can select that deployment and promote it to production (aka Mainnet) with just a couple of clicks.
-
-![Deployments Complete](/img/blog/an-easier-way-to-deploy-your-smart-contracts/deployments-complete.png)
-
-## And that's it! Pretty easy if you ask me.
-
-![Fry, Easy or Too Easy](/img/blog/an-easier-way-to-deploy-your-smart-contracts/fry-easy.jpg)
-
-## 🎉 Don't Believe Me? Be The First to Try it at My TruffleCon 2019 Workshop! 🎉
-
-I really hope you're going to TruffleCon; it's going to be awesome. Even more so because you can **be the first to try Truffle Teams Deployments in my workshop!** In my `Push It! Push It Real Good: Truffle Teams Intro & Deployments` (9AM-12PM on Friday, Aug, 2nd) workshop, we'll cover this entire lifecycle: hooking up your repository, getting your first build to pass, deploying to Ropsten, and finally monitoring transactions made against your contracts (we didn't talk about this here; check out the [docs](/docs/teams/deployments/contract-monitoring) for more details on contract monitoring).
-
-Hopefully there will be time for me to answer any questions you have, and maybe even help get your own Truffle project hooked up with Truffle Teams! If not, I will be available during the office hours at 5PM on Friday! I'm also always happy to chat anytime throughout the conference!
diff --git a/src/blog/announcing-collaboration-with-filecoin/index.md b/src/blog/announcing-collaboration-with-filecoin/index.md
deleted file mode 100644
index a4ad9a98e..000000000
--- a/src/blog/announcing-collaboration-with-filecoin/index.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Announcing Collaboration with Filecoin - Big Integrations Coming
-hide:
-  - navigation
----
-
-![Filecoin Collab Banner](/img/blog/announcing-collaboration-with-filecoin/blog-header.png)
-
-Today we're announcing an exciting new collaboration, aimed at helping developers across the globe create and deploy fully decentralized applications. We've teamed up with Filecoin to add support for the Filecoin network into our world class suite of tools. In typical Truffle fashion, we'll beef up the Truffle command line tool to give you everything you need to deploy directly to Filecoin; and then we'll add new features to Ganache so that you can easily simulate the Filecoin network during development and testing.
-
-### The Decentralized Ideal
-
-Since Truffle's inception, we've long wanted to integrate with decentralized storage networks so we can help developers build fully decentralized applications. For the most part, this has been a waiting game: Decentralized storage networks have been in heavy development, and it's clear these technologies needed time to mature. With Filecoin's month-long hackathon starting [this week](https://hackfs.com/), and the launch of their main network ("mainnet") coming later this summer, we thought now was the right time to give developers access to this amazing new technology.
-
-We're excited about Filecoin because it allows developers to build applications with 100% uptime. For instance, if an application uses only fully-dentralized technologies like Etheruem and Filecoin, the built-in incentivizations of those technologies will ensure miners around the world will keep that application running. With anti-censorship properties, as well as support for large amounts of data, Filecoin support could bring in a new age of Web3. 
-
-There's a lot we have to do before we reach this ideal, but I'd love to tell you about our roadmap for the next six months. 
-
-### Truffle Preserve: Save Your App Data (available today!)
-
-![Truffle Preserve](/img/blog/announcing-collaboration-with-filecoin/truffle-preserve.gif)
-
-In thinking about our support for Filecoin, the idea of *preservation* came quickly to mind. We envisioned that preserving application data like Javascript frontends and static assets would be a normal part of the deployment process. So we ran with that idea and added a new command to the Truffle command line tool: `truffle preserve`.
-
-Like preserving fruit, Truffle follows a "recipe" to preserve your files. In the gif above, Truffle is using the `filecoin` recipe, which will ship standard with our new version of Truffle. 
-
-**You can use `truffle preserve` today!** You'll need to download a special release we created so you can start testing, shown below. Note that our Filecoin integration is very alpha, but we wanted to support all the amazing devs hacking on Filecoin this month during [HackFS](https://hackfs.com/). 
-
-```
-$ npm install -g truffle@preserves
-```
-
-To use `truffle preserve`, simply specify the files you want to preserve on the command line, and choose between the `--filecoin` or `--ipfs` recipes. The `filecoin` recipe uses the `ipfs` recipe under the hood. You can choose only the `ipfs` recipe if you have a different set up!  
-
-```javascript
-// Preserve to Filecoin:
-$ truffle preserve ./path/to/directory --filecoin
-
-// Preserve to IPFS only:
-$ truffle preserve ./path/to/directory --ipfs 
-```
-
-By default, `truffle preserve` comes configured to work with the [Powergate localnet](https://docs.textile.io/powergate/localnet/), though you can change the IPFS and Filecoin connection information by adding the following to your `truffle-config.js` file: 
-
-```javascript 
-  // ...,
-  environments: {
-    development: {
-      "ipfs": {
-        address: "http://localhost:5001"
-      },
-      "filecoin": {
-        address: "ws://localhost:7777"
-      }
-    }
-  },
-```
-
-Note that this configuration adds a new top-level `environments` object. We'll be using this new configuration object as we upgrade to Truffle 6 in the future.
-
-### Filecoin-flavored Ganache: Simulate Filecoin (Summer/Fall/Winter)
-
-Ganache was built as the sister application to Truffle, to speed up development and testing Ethereum applications. Now that we've added support to Truffle, it's only natural we provide the same highly-modular simulator for Filecoin. Over this summer and into Fall, we plan to create a Filecoin simulation library, as part of [`ganache-core`](https://github.com/trufflesuite/ganache-core). Then later on this Fall/Winter, we'll follow that up with support in our graphical version of Ganache, below! 
-
-![Filecoin-flavored Ganache](/img/blog/announcing-collaboration-with-filecoin/filecoin-flavored-ganache.png)
-
-### Get involved / Reach out!
-
-We're extremely excited to be working with the Filecoin team and adding support for Filecoin into Truffle's tooling. If you have questions about our Filecoin integration or our plan for the future, <a href="https://trfl.co/become-a-truffler" target="_blank">join our slack community</a> and get your questions answered. Whether you're a new dev or a [HackFS hacker](https://hackfs.com/), we're happy to help. 
diff --git a/src/blog/announcing-full-portable-solidity-debugger/index.md b/src/blog/announcing-full-portable-solidity-debugger/index.md
deleted file mode 100644
index 5ed2f032b..000000000
--- a/src/blog/announcing-full-portable-solidity-debugger/index.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: Announcing our Fully Featured, Portable Solidity Debugger
-hide:
-  - navigation
----
-
-Every one at Truffle is giddy right now. 
-
-----------------
-
-Since Truffle's inception, it's been our mission to build outstanding development tools for the Ethereum community. The analogy we always used was one of history: Ethereum development practices are years behind the rest of the industry, and it's our job to build tools that modernize our craft. Well today, Truffle's come one step closer to that goal. We're happy to announce the release of our fully featured, fully portable Solidity [debugger](https://github.com/trufflesuite/truffle/releases) and [debugging libraries](https://github.com/trufflesuite/truffle/tree/master/packages/debugger).
-
-![Debugger in Action](https://i.imgur.com/7y80aF3.gif)
-
-### What We've Built
-
-If you've followed Truffle development, you're familiar with the `truffle debug` command. This was the first incarnation of a "debugger" built into Truffle, though it wasn't much more than a code tracer. Our new debugger comes with everything you expect :
-
-* Code stepping (over, into, out, next, instruction, etc.)
-* Current code location, including the address of the running contract
-* Breakpoints
-* Watch expressions
-* Variable inspection (stack, memory _and_ storage)
-* Custom expression evaluation using Solidity variables
-
-On top of that, our new debugger is fully portable, built to integrate with any Javascript project or editor, like Visual Studio Code. Lastly, we built it to work with **any Ethereum client**, so you could debug transactions against the main Ethereum network if you so desired. 
-
-### How it Works
-
-To debug your Solidity code, you first need to make a transaction. Ethereum is a world computer with a history of all execution, so we can pull all the information we need from past transactions. After obtaining the transaction hash, simply run the following to kick off your debugging experience:
-
-```shell
-$ truffle debug <tx hash>
-```
-
-This will open up the debugging console which you can use to your heart's content! 
-
-![Debugger user interface](https://i.imgur.com/0NUTSlM.png)
-
-The above user interface gives you access to the debugger features you need to step through your contracts' code, set breakpoints, evaluate expressions and inspect Solidity variables, providing you a better sense of what your code is doing. Under the hood, our debugger is interacting with your Ethereum client to gather all the data necessary to provide this information to you in a suitable manner. For developers reading this, the debugging library stores all this data in Redux, making the data easy to manage and making the library super portable. 
-
-Most of the work done by the debugger results in some type of mapping. The debugger gathers tons of disparate data, like the bytecode of your contracts, abstract representations of your code, instructions run during your transaction, etc., and combines them to produce information useful to the contract developer. Perhaps the debugger's most valuable property is variable inspection: Using all the data gathered, the debugger can determine which variables exist within your contract, which apply to each section of the code, and what their values are at any point in time. It can even show the values of complex data types, like structs with nested arrays. We're still filling out a few data types, but expect those in the next couple weeks.
-
-If you plan on using the `debug` command _today_, we recommend using [Using Truffle Develop and the Console](/docs/truffle/getting-started/using-truffle-develop-and-the-console). Truffle Develop comes with everything you need "baked in" to fully debug your contracts. Ganache and `ganache-cli` will need to be updated, so stay tuned for that in the coming days. 
-
-### Where to Next
-
-The debugger we built unlocks tons of value for all Ethereum developers both new and advanced, but what you're seeing here is the tip of the iceberg of where this technology will go. The interface above is just **one** interface, meant to show off the debugger's capability. As mentioned, the libraries we built are super portable, so they'll end up making their way into all of the following:
-
-* Integrated Development Environments (IDEs) like Visual Studio Code
-* [Ganache](/ganache), including a full debugging UI
-* [Drizzle](/docs/drizzle/quickstart), for automatic variable change detection after a transaction
-* Browser plugins so you can debug transactions on the fly within your application
-* Ethereum provider libraries that let you debug your code anywhere, without a plugin
-
-We encourage the Ethereum community to help build these tools. Our code is open source, and you can find all of it [on Github](https://github.com/trufflesuite/).
-
-### How to Get It
-
-If you already have Truffle installed, simply run the following to get you to the latest version:
-
-```shell
-$ npm uninstall -g truffle
-$ npm install -g truffle
-```
-
-If you're new to Truffle, you can try it out using:
-
-```shell
-$ npm install -g truffle
-```
-
-You may have to use `sudo` with the above commands if you're running Linux.
-
-More information about how to use Truffle can be found in [our documentation](/docs), and feel free to reach out on our [community Gitter channel](https://gitter.im/consensys/truffle), where hundreds of your fellow Trufflers congregate to answer your question.
-
-### A Quick Thank You
-
-I'd like to personally thank the whole Truffle team for this effort, and particularly [Nick D'Andrea](https://github.com/gnidan) for turning some initial research work into a fully portable, fully featured debugger. The engineering under the hood is amazing, [I urge you to take a look](https://github.com/trufflesuite/truffle/tree/master/packages/debugger). I'd also like to thank the community at large: It's a pleasure building the tools that make your lives easier, and your consistent feedback makes the whole endeavor worthwhile.
-
-Thanks,
-<br/>-- Tim 
diff --git a/src/blog/axonis-enterprise-use-of-truffle/index.md b/src/blog/axonis-enterprise-use-of-truffle/index.md
deleted file mode 100644
index cca7183a6..000000000
--- a/src/blog/axonis-enterprise-use-of-truffle/index.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Axoni's Enterprise Use of Truffle
-hide:
-  - navigation
----
-
-![Truffle + Axoni](/img/blog/axonis-enterprise-use-of-truffle/truffle-axoni.png)
-
-## Axoni Background
-
-At Axoni, our mission is to make shared information more trusted and reliable. We do this through distributed technology that we call "Ethereum-inspired", which has both a broad and a specific meaning. In the broad sense, the core technology plays a role for its users analogous to the public blockchain, presenting a powerful and extensible capacity to side-step undesired intermediaries (yes, these exist for banks too...). In a more precise technical sense, our platform borrows certain concepts from Ethereum (e.g. accounts, contracts, gas...) and, importantly, we make efforts to comply with Ethereum-world interfaces (e.g. evm bytecode, web3 JSON-rpc).
-
-Of course, an up-shot of the last is the ability to take part in all the innovation taking place in the broader Ethereum ecosystem, including client-side libraries that enable a "tastier" application development process. To this end, within the last year we have worked to leverage the Truffle suite and ecosystem to great effect. In fact, as [reported](https://www.forbes.com/sites/michaeldelcastillo/2019/04/29/consensys-spins-off-ethereum-startup-truffle-to-take-blockchain-to-big-business/#1e84a5622e21), it is fair to say that Truffle serves by and large as the main toolset for on-chain application development at Axoni.
-
-## Using Truffle at Axoni
-
-It was a delight for us to find that, given our compliance with the web3 JSON-RPC spec, truffle basically works "out-of-the-box" with no extensive customization required for many very useful stages in the application lifecycle: develop, build, test....
-
-One notable exception: we found the native `truffle migrate` functionality not extensible to our use case. In part, this is due to the fact that our smart contract applications implement something [similar to the proxy pattern](https://blog.zeppelinos.org/the-transparent-proxy-pattern/), which runs counter to the "migration" paradigm. On the other hand, and for reasons beyond the scope of this post, tools such as `zoslib` designed to handle upgradeable smart contract application deployments, generate smart contract implementations incompatible with our use case. At a high level, our smart contract framework is optimized for high-throughput and highly complex Solidity applications which enables the ability to make automatic upgrades based on semantic versioning. [ Note: I plan to speak more about our particular use cases and smart contract topologies at Trufflecon on August 3rd]
-
-In any case, especially due to the often very high levels of complexity entailed by our use cases– combined with the noted [application-level gotcha's of upgrade design patterns in solidity itself](https://blog.trailofbits.com/2018/09/05/contract-upgrade-anti-patterns/)–we are biased towards a simple and opinionated declarative format that application and production engineers can easily understand and (when needed) manipulate.
-
-This raises the question -- why use truffle for this? It seems there are at least three reasons:
-
-1. `truffle-config.js` / `truffle.js` serves as an already existing central source of shared information about various network providers relevant for a particular application developer. It only makes sense to extend this format for use in production-like environments as well.
-1. Truffle code artifacts, a battle-tested standard for smart contracts and solidity code, in particular, provide a common interface for a toolchain. By virtue of using truffle, there is no need to re-create this format. For a non-development deployment, a `contracts_build_directory` parameter is supplied, which results in a pull from a remote artifacts repository.
-1. Obviously `@truffle/contract` itself provides a nice object oriented interface for deploying and performing operations on contracts within this script, thus avoiding any reinventing the wheel within the deployment library itself.
-
-Thus, we ventured to build a package on top of truffle that manages configuration-driven smart contract deployments and upgrades.
-
-## Building a Truffle-Based Deployment Tool
-
-The first question is what the configuration file should look like? We determined the "Straw Man" to be, simply, a two-dimensional list of job types and associated contracts specified for deployment. Starting with this, we found another concept we needed to add ("custom-partition") that is specific to Axcore, relating to the way the node software provisions data across network partitions; certain contracts are provisioned differently from others. In addition to this, we found that the only other concept we needed was a parameter specifying dependencies ("deps") that linearizes to a certain order to deployment (which may be necessary, for instance, if a given storage address stores reference to another). For concision, we added limited regex support. In the end, we arrived at a yaml-based file looking very much like the below:
-
-``` yaml
-version: 0.0.1
-setup:
-    partitions:
-        - custom-partition: *
-        - custom-partition: ^public-common
-    contracts:
-        - name: MagmaRegistryFooStorage
-        - name: MagmaRegistryBarStorage
-          deps:
-            - MagmaRegistryFooStorage
-upgrade:
-    partitions:
-        - custom-partition: "*"
-    contracts:
-        - name: MagmaRegistryFoo
-        - name: MagmaRegistryBar
-```
-
-In terms of implementation, a truffle exec script reads this configuration file, and for each contract, a) deploys the contract b) performs some basic API configuration and c) installs it in the application through invoking a basic `initialization` method. The basic top-level run (truffle exec) script looks very much like the below:
-
-``` javascript
-const run = async (done) => {
-    let jobParams = args;
-
-        // Configure specific variables for a PROD-like environment:
-    if (process.env.ENV === 'PROD') {
-        jobParams = Object.assign(args, handleProd());
-    }
-
-       //hoisting injected vars to global scope:
-    global.web3 = web3;
-    global.artifacts = artifacts;
-
-        // Create instance of job based on type
-    const jobInstance = new Job(jobParams.job, jobParams);
-
-        //Run job by deploying and invoking an initialization method on each contract
-    await jobInstance.run().catch(e => done(e));
-    done();
-};
-```
-
-A command-line client can specify a given job to run, such as the "upgrade" job specified above. Given the above configuration, the below command would deploy (if necessary) and initialize "MagmaRegistryFooStorage", followed by "MagmaRegistryBarStorage" from a given artifacts repository:
-
-``` bash
-etna --job upgrade --contracts_build_directory /path/to/artifacts
-```
-
-## Future Plans and an Announcement
-
-I am pleased to announce that we plan to open-source our core Solidity smart contract library, which provides an alternative version of the Proxy pattern, along with this aforementioned deployment tool. We believe both could be useful both for private and public applications and the Axoni team is excited to see what the community builds with these tools.
-
-In the meantime, we hope the above at least provides a high-level example of an approach to building lightweight extensions within truffle, and as a simplifying approach to the smart contract deployment process, especially for Proxy Pattern topologies.
-
-The Axoni team and I look forward to discussing this topic and much more (such as [Axlang, our Scala-based Solidity-alternative](https://axoni.com/axlang/)) at Trufflecon.
diff --git a/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md b/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
deleted file mode 100644
index 8e9f1a8aa..000000000
--- a/src/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/index.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: The Best Methods to Understand Blockchain Technology if You’re Not A Developer
-hide:
-  - navigation
----
-
-As a non-technical person, it feels like it takes 1.21 gigawatts to keep up with the speed of technology - even Doc Brown himself couldn't have predicted all of the technological advancements with his flux capacitor. Not only are we trying to keep up with technologies like blockchain, machine learning, and AI, but we have an overwhelming amount of information on the web all at the click of a mouse. It's overwhelming to the point that it's difficult to even know where to begin. However, online blockchain educational materials have started to ramp up. As I write this, I'm confident I'll start seeing “ Blockchain for dummies” online course advertisements on my browser (Opt-in, of course, because I'm using Brave). Mind-blowing! Let me help you begin by slowing down in order to speed up effectively.
-
-So you're someone who's not technical that wants to learn blockchain - great! Whether you're technical or non-technical isn't necessarily contingent on understanding an emerging technology like blockchain. Rather it's how you position yourself in the marketplace where you'll start to see the fruits of your labor.
-
-## Human to human chit chatting
-
-First things first, human to human interaction is where you want to start and it's awesome! Yes, [YouTube](https://www.youtube.com/watch?v=YGC9ECnot0k) will always be there for you - or at least until your battery dies, but dialoguing with another person and in this case, someone well-versed in blockchain will lay a strong foundation to springboard yourself into understanding this industry. I hate to use the phrase “trust me,” but trust me, as someone who's not that technical and has a background in Kinesiology, I can assure you that learning from the great minds of my Truffle developers has helped me grasp the concepts of blockchain technology. I'll say, most folks that are experts in their field generally have no problem chatting with a hungry and curious mind. If anything, it's flattering when I get approached to explain blockchain to someone who desires to understand it. We're gifted with the ability to use analogies and other practical ways of explanations that can make light of things that often feel dark and hard to see. Check out this great analogy on [sharding](https://youtu.be/5bOO7P-tZ3U?t=166)!
-
-Guess what? Developers don't mind talking to non-technical people who are trying to understand a particular technology like blockchain. It's a ridiculous stereotype to think devs only like to chat with other devs. If that were the case, how could a business be run successfully? In fact, oftentimes the best explanations come from the top experts. Developers don't like jargon or complexity either. We even gave the term developer operations a cute little nickname like DevOps. Seek out the developer in the blockchain space and ask away...better yet, reach out to one of us at Truffle–we love our community!
-
-## Meet-ups
-
-Go to your local blockchain meetups. There's probably more than a few that are available for you to attend. Meetups can be two-fold, namely, one to obtain knowledge and the other for networking, which can sometimes lead to a job. I can't tell you how many times I've hired someone that I initially met at a meetup. It sure beats throwing your resume on a job board hoping that it will stick. Relationships become the most valuable asset you can have to aid in your next employment opportunity. Moreover, everyone at a meetup shares one common trait. A passion for blockchain.
-
-## Social Media
-
-Maybe you're a little shy and don't want to network (although I highly recommend it!). There's a myriad of resources available online to learn the underpinnings of blockchain technology. You can visit our [Truffle University](/university) page for more information taking our courses. If you like to learn through watching other people's conversations, [Twitter is the place to go](https://media.consensys.net/i-read-crypto-twitter-for-hours-everyday-here-are-40-accounts-that-really-matter-cfecc681379d). You can make your way over to Quora if you have specific questions about blockchain. Don't want people to know who you are, Reddit has phenomenal ELI5 (explain it like I'm 5) explanations.
-
-## Read a Book
-
-Some people enjoy a nice old fashion book. By far the best book to understand blockchain is Mastering Bitcoin and [Mastering Ethereum](https://github.com/ethereumbook/ethereumbook) by Andreas Antonopoulos.
-
-## Podcast
-
-Listening to a [Podcast](https://player.fm/podcasts/Blockchain) is great. Especially when you're on the go. It's a way to redeem your commute to work, get through a workout session, or just something to pass the time. Often times, podcast hosts will have [guest](https://povcryptopod.libsyn.com/making-eth-sweet-with-tim-coulter) in the blockchain space to give an objective perspective on what the challenges and successes are with the technology.
-
-<h3 class="link-markdown">
-  <a href="#trufflecon" name="trufflecon">
-    <i class="fas fa-link">
-    </i>
-  </a>
-  ![TruffleCon](/img/blog/best-methods-to-understand-blockchain-if-youre-not-a-developer/trufflecon.png)
-</h3>
-
-Finally, and I may be a little bias, but if you really want to increase the pace at which you can comprehend blockchain then go to TruffleCon! Come say hi to all of us at Truffle. Come say hello to all of the speakers and blockchain company representatives. Ask us questions. Let us help you understand blockchain better. Let's network. Let's have a relationship that will enable amicability. Or better yet, let's interop with each other to leverage the power of blockchain for careers, security, and better transparency in an ever-growing technological world, one node at a time.
diff --git a/src/blog/blockchain-will-cure-cancer/index.md b/src/blog/blockchain-will-cure-cancer/index.md
deleted file mode 100644
index dde1c563a..000000000
--- a/src/blog/blockchain-will-cure-cancer/index.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Blockchain Will Cure Cancer
-hide:
-  - navigation
----
-
-<p style="width: 40%; float: left; margin-right: 1rem;">
-  <img style="margin-top: 0.3rem; margin-bottom: 0;" class="img-fluid" src="/img/blog/blockchain-will-cure-cancer/laptop.jpg" title="Laptop" alt="Laptop">
-</p>
-
-Physicians and scientists will be the actual agents behind a cure for cancer. But in their potential to disrupt the very nature of medical research and treatment, blockchain-based solutions are extremely likely to light the way. It is important when examining any new technology to consider the ways in which it may change the world. Join me here as we briefly look at how blockchain can help lead us to a world without cancer.
-
-Cancer is a significant public health issue in the United States and around the world. In the United States alone, an estimated [1.7 million new cancer cases](https://www.cancer.gov/about-cancer/understanding/statistics) were diagnosed in 2018. This number is expected to increase drastically as time goes on.
-
-Several barriers exist to finding a cure for cancer. Key among them are data challenges, difficulty quickly assessing the effectiveness of new treatments, and the financing required to fund research and treatment. Fortunately, blockchain technology is already providing avenues for addressing these barriers and bringing us closer to a cure for cancer.
-
-## It’s in the Data
-
-At its core, the path to curing cancer lies in accessing and evaluating as much data about the disease as possible. Blockchain solutions for medical data are [already being proposed and tested](https://www.healthcareitnews.com/news/blockchain-use-case-electronic-health-records). The primary benefits of using blockchain technology for storing and processing medical data lie in the portability and patient ownership of that data. On their own, these benefits are as helpful to cancer patients as they are to other medical patients.
-
-The particular usefulness of blockchain for cancer data lies in the ability of patients to volunteer their medical records to be used in research. This data will need to be anonymized and, of course, regulatory hurdles are likely to exist, but aggregating medical data from potentially millions of patients around the world will allow physicians and researchers access to unprecedented levels of information about the disease they seek to cure.
-
-[BreastWeCan.org](https://BreastWeCan.org) is one fledgling organization seeking to increase the base of data upon which further cancer research can be built. By encouraging women to upload their mammogram scans and other breast cancer images onto a blockchain, the company hopes to allow an AI to then study these images and share what it learns.
-
-## Better knowledge sharing means more effective treatments
-
-<p style="width: 40%; float: right; margin-left: 1rem;">
-  <img style="margin-top: 0.3rem; margin-bottom: 0;" class="img-fluid" src="/img/blog/blockchain-will-cure-cancer/petri.jpg" title="Petri Dish" alt="Petri Dish">
-</p>
-
-Information about cancer treatment and the results thereof is essential to finding a cure. From clinical trials to variation in responses to existing treatments among patients, information is the key. Blockchain technology can help in this respect by encouraging patients to share their treatment experiences and encouraging physicians to collaborate in their treatment attempts.
-
-One U.S. company has piloted a blockchain-based system for evaluating patient responses to cancer treatment. Encouraging patients and oncologists to provide information with an “Onco” coin, [OncoPower](https://pharmaphorum.com/news/blockchain-firm-witty-health-launches-digital-cancer-decision-tool/) will allow oncologists access to “de-identified … details like co-morbidity, specific cancer type, lines of therapy, and actual drugs used for treatment.”
-
-OncoPower’s promise lies in the ability to anonymize medical data, put it on a blockchain, and make it accessible to the medical community. This will encourage collaboration and knowledge-sharing amongst health care practitioners and researchers, increasing the visibility of various health outcomes and leading to faster iteration when it comes to experimental treatments.
-
-Another exciting treatment approach by [Hypertrust Patient Data Care](https://www.hypertrust-patient.com/) in Germany focuses on the immutable and verifiable aspects of blockchain to ensure that the supply chain for very sensitive immunotherapy treatments can be made as reliable as possible. Hypertrust tracks medication from “needle to needle” and leverages the transparency of a blockchain to improve patient outcomes.
-
-## Targeted Financing
-
-One thing that blockchain technology does incredibly well is to provide opportunities for decentralized governance and transparency. In the case of financing cancer research, blockchain could prove to be the silver bullet needed to ensure that funding goes where it will be most useful.
-
-While it does not appear that cancer fundraising has made its way onto a blockchain just yet, the ability of donors to contribute to cancer research in a tangible and trackable way is likely to increase donations and empower engagement within the scientific community. Putting cancer funding on a blockchain and encouraging the scientific community to engage in that blockchain’s governance could provide a catalyst for encouraging efficient, transparent, and collaborative research efforts.
-
-## Looking Ahead
-
-Blockchain technology is still in early stages, and it may be too soon to know precisely in which ways it may change our world. Developments in the medical applications of blockchain technology are very encouraging. Cancer has evaded a cure for many years, and the advent of new ways for scientists and physicians to learn, collaborate, and experiment may be just what the medical community needs.
diff --git a/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md b/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
deleted file mode 100644
index fd9201f0e..000000000
--- a/src/blog/branching-out-announcing-tezos-support-in-truffle/index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Branching Out - Announcing Tezos Support in Truffle
-hide:
-  - navigation
----
-
-![Announcing Truffle Integration](/img/blog/branching-out-announcing-tezos-support-in-truffle/chameleon-t3-truffle-blog-header.png)
-
-If you've been following Truffle's development, you'll notice that our tools already support a handful of exciting platforms: [Ethereum](https://ethereum.org/), [Quorum](https://www.goquorum.com/), [Axoni](https://axoni.com/technology/), Hyperledger [Fabric-EVM](https://github.com/hyperledger/fabric-chaincode-evm), Hyperledger [Sawtooth](https://www.hyperledger.org/projects/sawtooth), and Hyperledger [Burrow](https://www.hyperledger.org/projects/hyperledger-burrow). What's common amongst these chains is that they all use the Ethereum Virtual Machine under the hood. Ethereum is very near and dear to our hearts -- it's where we got our start, and where we are the most competent. But we're branching out, in large part due to market demand. In December we released a beta [Corda-flavored Ganache](/blog/unwrap-the-corda-flavored-ganache-beta) as part of our initial support for the [Corda platform](https://www.r3.com/corda-platform/). And today, we branch out even further.
-
-**I'm excited to announce Tezos integration into the Truffle command line tool.**
-
-Right now, at this very moment, you can [download a Tezos-specific version of Truffle](/docs/tezos/truffle/quickstart) and start building smart contracts on Tezos networks using the time-tested tooling you know and love. And if you're a Tezos native who got your start building on top of the Tezos platform, then this means professional-grade tooling has finally arrived.
-
-We chose Tezos as our first non-EVM chain because of its blossoming developer community. In our position as tool builders, we go where the market takes us: If enough people ask for Tezos support, we listen. This market demand was coupled with an active and interested group of core developers, and a blockchain architecture that's similar to Ethereum. Ultimately, Tezos is "EVM-like". This makes it a great candidate for integration, fitting into Truffle like a glove.
-
-Are you a developer who wants to build on top of Tezos using Truffle? [Check out our documentation](/docs/tezos/truffle/quickstart) and our [quick start guide](/docs/tezos/truffle/quickstart).
-
-It's important to note that our integration with Tezos is experimental. As of now you'll need to download a special version of Truffle to start building on Tezos. This is by design: Integrating a new blockchain into a common workflow takes some work, and we want to ensure we keep the same level of quality for our existing chains while we work out the kinks. You can be extremely helpful here! If you run into an issue using the Tezos version of Truffle, let us know! You can file an issue at our [issue tracker](https://github.com/trufflesuite/truffle/issues), or reach out to us on [Spectrum](https://spectrum.chat/trufflesuite).
-
-Our plan over the coming months is to harden our Tezos integration and ultimately release it under the mainline version of Truffle. We’ve also expanded our commitment to the Tezos project by finalizing plans for further integrations: 1) a Tezos-flavored [Ganache](/ganache); and 2) full support for the [SmartPy](https://smartpy.io/) programming language.
-
-Though this is our first foray into supporting non-EVM blockchains, I'd like to take this moment to reaffirm our support and interest in Ethereum and Ethereum-based blockchains. You'll see many more announcements in 2020 about how we're planning to make development on both Ethereum 1.0 and Ethereum 2.0 better. Stay tuned.
-
-I'd like to thank some standout developers in the Tezos community for making this integration a reality. First, are the developers from [Stove Labs](https://stove-labs.com/), Matej Šima & Istvan Deak. They helped significantly in stress testing our integration and providing continuous feedback during development. I'd also like to thank [Taquito](https://tezostaquito.io/) developers Jev Björsell and Simon B.Robert for creating an easy to use library for communicating with and interacting with the Tezos blockchain (for Ethereum developers, this is the Web3.js equivalent). Last but not least, a big shout out to the developers of the [LIGO](https://ligolang.org/) programming language, Gabriel Alfour and the rest of the LIGO development team, for making LIGO compiler integration easy on us. Cheers to you!
-
-We're excited to announce Tezos support as one of many integrations to come in 2020. Thank you for your continued support of our work, and the opportunity to make your development life easier. Happy coding!
-
-Tim
-
--- Founder & CEO, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md b/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
deleted file mode 100644
index cc3d131ab..000000000
--- a/src/blog/branching-out-phase-2-of-corda-flavored-ganache/index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Branching Out - Phase 2 of Corda-flavored Ganache
-hide:
-  - navigation
----
-
-![Branching out to Corda-flavored Ganache](/img/blog/branching-out-phase-2-of-corda-flavored-ganache/chameleon-corda-truffle-blog-header.png)
-
-April has been a big month for Truffle Suite! Earlier this month we branched out and announced Tezos integration into the Truffle command line tool. If you remember, back in December we released a beta [Corda-flavored Ganache](/blog/unwrap-the-corda-flavored-ganache-beta) as part of our initial support for the Corda platform. Today, we are excited to share [Phase 2 of Corda-flavored Ganache, v2.4.0](https://github.com/trufflesuite/ganache/releases) with you! Phase 2 includes more robust features for Corda including Corda CRaSH Shell, network map visualization, and a version picker.
-
-We're thrilled to release Phase 2 of Ganache for Corda, an open source blockchain platform built for business applications, as this continues to lower the barrier to entry for Corda developers. These updates enable developers to easily set up a local network on their machines, letting them inspect the state of that network across various nodes and giving them visibility into transactions normally hidden by a live Corda network's privacy protections.
-
-Features Include:
-
-* One-click Corda network configuration and initialization, so you can focus on what matters most: your application.
-* Multiple workspaces for all of your Corda projects including a Corda network map, notaries, nodes, transactions, accounts, and ledgers.
-* Simple testing for interoperability with the Version Picker node.
-* Easy access to all your application's data, including network map, notaries, nodes, transactions, and states.
-* Visualizations of node connections with the Corda network map graph
-* Embedded Corda CRaSH Shell to provide control over your nodes and project data
-
-As always, this release is compatible with the latest versions of Windows ⊞, Mac OS 🍎, and Linux 🐧. You can now run and interact with a Corda network without installing prerequisites like Java, PostgreSQL, Corda binaries, docker, etc!
-
-If you are a Corda developer who wants to use Ganache with your CorDapp [check out our documentation and our quick start guide](/docs/ganache/corda/working-with-corda). We are also hosting a [joint webinar with R3](https://www.crowdcast.io/e/corda-ganache) on May 6th to demonstrate these features along with how this fits into existing Corda developer’s’ workflow.
-
-In closing, I’d like to thank our partners at R3, Todd McDonald, Lisa Chiong, Tiffany Sarmiento, Chris Chabot, and Nick Rogers for their collaboration, vision, and teamwork. I’d also like to thank [David Murdoch and Nick Paterno](/staff) from the Truffle team for their tireless efforts to make Corda Flavored Ganache a reality.
-
-Thank you for your continued support and the opportunity to make your development life easier. Happy coding!
-
-Tim
-
--- Founder & CEO, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md b/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
deleted file mode 100644
index dc158cce0..000000000
--- a/src/blog/bring-your-own-ci-byoci-with-truffle-teams/index.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Bring Your Own CI (BYOCI) with Truffle Teams
-hide:
-  - navigation
----
-
-Truffle Teams has always offered an internal continuous integration (CI) service. This service is great for getting up and running quickly since it requires no configuration to run your Truffle tests.
-
-We also want to support teams who have established CI setups outside of Truffle Teams. Thanks to the fantastic work by [Erin Shaben](https://github.com/eshaben), **you can now leverage your existing GitHub-integrated build services**!
-
-## Using an Existing CI Service
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/bring-your-own-ci-byoci-with-truffle-teams/figure-1.png" alt="Builds settings screen" style="width:100%">
-  <figcaption class="text-center font-italic">The BUILDS settings screen</figcaption>
-</figure>
-
-Enabling external CI for a repository only requires a single checkbox! Navigate to your user or organization’s settings page by clicking the user/org icon in the navbar. From there, click the BUILDS tab, then check the checkbox next to the repository of your choice!
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/bring-your-own-ci-byoci-with-truffle-teams/figure-2.png" alt="Build with external CI enabled" style="width:100%">
-  <figcaption class="text-center font-italic">Build with external CI enabled</figcaption>
-</figure>
-
-Now, when you navigate to the builds page for that repository, any new builds will show a list of your GitHub-integrated build services, along with their respective statuses.
-
-For more detailed information on the external CI service, [check out our documentation here](/docs/teams/builds/external-ci).
-
-For more detailed information on adding services to GitHub via their Marketplace, [check out the GitHub Marketplace docs here](https://help.github.com/en/github/customizing-your-github-workflow/about-github-marketplace).
-
-## Future Integration
-
-We want Truffle Teams to be the most effective devops tool in the blockchain space for both new and existing teams. Let us know what you think about this integration solution, and if your team has other needs we haven’t met yet.
-
-Thanks!
-
-Josh Quintal
-
--- Head of Product & Marketing, Truffle Suite
\ No newline at end of file
diff --git a/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md b/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
deleted file mode 100644
index 8fca48191..000000000
--- a/src/blog/crytic-continuous-assurance-for-smart-contracts/index.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Crytic - Continuous Assurance for Smart Contracts
-hide:
-  - navigation
----
-
-We are proud to announce our new Smart contract security product: [https://crytic.io/](https://crytic.io/). Crytic provides continuous assurance for smart contracts. The platform reports build status on every commit and runs a suite of security analyses for immediate feedback.
-
-The beta access will be open soon. Follow us [on twitter](https://twitter.com/CryticCI) to be notified and benefit from the service as soon as possible! The first three months are free.
-
-## How Crytic will secure your smart contracts
-
-Once connected to your GitHub repository, Crytic will:
-
-* Run our static analyzer [Slither](https://github.com/crytic/slither/), which detects the most common smart contracts vulnerabilities and will save you from critical mistakes.
-* Run your Truffle tests continuously to ensure that no bug is added while developing your project.
-
-Slither will analyze your codebase for more than 60 security flaws, including reentrancy, integer overflows, race conditions, and many others. Half of these flaw-detectors are private and were not available to the public. They can detect flaws for which public knowledge is limited and that no other tool can find. The recent [GridLock bug](https://blog.trailofbits.com/2019/07/03/avoiding-smart-contract-gridlock-with-slither/) would have been detected ahead of time using Crytic!
-
-We built this platform for developers, so we integrated it with GitHub. It will watch every commit and branch to ensure that bugs are not added during development. In addition, Crytic will run the checks on every PR to facilitate your code review.
-
-For every security issue found, Crytic will:
-
-* Show you a detailed report on the bug, including source-code highlighting.
-* Allow you to create a GitHub issue to keep track of the fixes easily.
-* Let you triage the results, so you can decide what needs to be fixed.
-
-## Quick Walkthrough
-
-Adding Crytic to your system is straightforward: you just need to connect to your GitHub repository. We have first-class support for Truffle; it works out of the box! We also support most of the other smart contract platforms, including Embark, Dapp, and Etherlime. After adding your repository, the dashboard (Figure 1) will show you a summary of the project, like this [crytic-demo](https://github.com/crytic/crytic-demo):
-
-<figure>
-  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-1.png" alt="Crytic Dashboard" style="width:100%">
-  <figcaption class="text-center font-italic">Figure 1: Crytic Dashboard</figcaption>
-</figure>
-
-From now on, you will benefit from continuous security analyses.
-
-### Issue reports
-
-Finding an issue is only the first part. Crytic will provide you with detailed information you need about the bug to fix it:
-
-<figure>
-  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-2.png" alt="Crytic Report" style="width:100%">
-  <figcaption class="text-center font-italic">Figure 2: Report</figcaption>
-</figure>
-
-A careful reader will notice the vulnerability here: `function constuctor` creates a public function (with a typo!) that is callable by anyone instead of being run only at initialization. Crytic will detect these types of critical mistakes instantaneously.
-
-### Triaging issues
-
-Once a bug has been found, the user can decide to:
-
-* create a GitHub issue, to easily keep track of the fix, or
-* discard the issue.
-
-<figure>
-  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-3.png" alt="GitHub Issue Generated" style="width:100%">
-  <figcaption class="text-center font-italic">Figure 3: GitHub Issue Generated</figcaption>
-</figure>
-
-Crytic follows the modifications to your code and reports only new bugs that are introduced.  Each new PR will be analyzed automatically:
-
-<figure>
-  <img class="mb-2" src="/img/blog/crytic-continuous-assurance-for-smart-contracts/figure-4.png" alt="Pull Request Integration" style="width:100%">
-  <figcaption class="text-center font-italic">Figure 4: Pull Request Integration</figcaption>
-</figure>
-
-## What’s next for Crytic
-
-We are constantly improving Crytic. Expect to see new bug detectors and new features in the future. We are planning to add:
-
-* [Echidna](https://github.com/crytic/echidna) and [Manticore](https://github.com/trailofbits/manticore) integration: to ensure your code is checked for custom security properties.
-* Automatic bug repair: Crytic will propose patches to fix the issues it finds.
-* [Slither printer integration](https://github.com/crytic/slither/wiki/Printer-documentation): to help visualize the underlying details of your code.
-* Delegatecall proxy [checker](https://github.com/crytic/slither/wiki/Upgradeability-Checks): to prevent you from making critical—and all too common—mistakes in your [upgradeability process](https://blog.trailofbits.com/2018/09/05/contract-upgrade-anti-patterns/).
-
-Questions? Bring them to TruffleCon, and pose them to us at our booth or at our Friday workshop [on automated vulnerability detection tools](https://trufflecon2019.sched.com/event/RFQL/how-to-build-secure-smart-contracts-a-deep-dive-into-automated-tools?iframe=no&w=100%&sidebar=yes&bg=no)!
-
-Whether or not you can make it to TruffleCon, join our [slack channel](https://empireslacking.herokuapp.com/) (#crytic) for support, and watch [@CryticCI](https://twitter.com/CryticCI) to find out as soon as our beta is open.
diff --git a/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md b/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
deleted file mode 100644
index ecc2231f7..000000000
--- a/src/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/index.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Debug Quickly and in Context with Truffle Teams New Debugger
-hide:
-  - navigation
----
-
-
-![Truffle Teams Debugger Banner](/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/blog-header.png)
-
-If you've used Truffle's debugger, you know it's best-in-class. Until now though, it's been confined to the command line. Today the debugger breaks out of the console to a GUI within Truffle Teams! This is a huge workflow enhancement--allowing us to debug transactions in the places we're already viewing--via the deployment details screen or while monitoring individual contracts. Let's take a look!
-
-<p class="alert alert-info">
-  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the debugger right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
-</p>
-
-## Launching the Debugger
-
-To launch the debugger, we just need to find a transaction. Head over to the Deployments screen and select a deployment. From there select the transactions tab or click the monitoring button for a contract. You'll notice there's a debug button on each transaction card; clicking it will open the Truffle Teams debugger.
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/teams-debugger-1.png" alt="All transaction cards now have a debug button">
-  <figcaption class="text-center font-italic">Debugging is only a click away!</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-## Navigating the UI
-
-Starting at the top, you'll see the transaction hash along with an icon noting its status and, if applicable, the accompanying error message (1). Below that we have our functions, from left to right: Step Next, Step Over, Step In, Step Out, and Reset (2). Next we have some tabs showing the contracts included in this transaction (3). Finally we have two panes, one showing our Solidity with the current step highlighted in yellow (4). The second with our variables (5).
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 figure-shadow" src="/img/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger/teams-debugger-2.png" alt="The debugger in action on a failed transaction">
-  <figcaption class="text-center font-italic">Debugging a failed transaction.</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-At the moment some other enhancements, including breakpoints and syntax highlighting, are coming soon. We wanted to get this powerful feature in your hands as quickly as possible, so we're releasing it now via Early Access. For more information on what to expect from early access, check out [the Truffle Teams Early Access blog post](/blog/try-new-features-first-with-truffle-teams-early-access).
-
-For more information, check out [the Truffle Teams Debugger docs](/docs/teams/debugger/debugging-a-transaction) or for general information about Truffle's debugger, check out [the Truffle Debugger docs](/docs/truffle/getting-started/debugging-your-contracts).
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE TRUFFLE TEAMS DEBUGGER</a>
-</div>
-
-## Continue the Conversation
-
-We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven't met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md b/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
deleted file mode 100644
index 2fdcbef08..000000000
--- a/src/blog/debugging-verified-external-contracts-with-truffle-debugger/index.md
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: Debugging verified external contracts with Truffle Debugger
-hide:
-  - navigation
----
-
-![Truffle Teams Redesign Banner](/img/blog/debugging-verified-external-contracts-with-truffle-debugger/blog-header.png)
-
-Let's say you're crafting a clever flashloan transaction that interacts with
-five different DeFi dapps -- but on trying it, it doesn't work as expected.  You
-open the transaction in Truffle Debugger to get a closer look at what went
-wrong.  But how will you debug a transaction that the debugger doesn't have the
-source code for?
-
-Well, new in Truffle release v5.1.29 is the debugger's `--fetch-external` flag!
-This new flag tells the debugger to search [Etherscan's repository of verified
-contracts](https://etherscan.io/contractsVerified) and automatically
-download and compile those sources.  As long as all the contracts you're
-interacting with are verified on Etherscan, you're good to go!
-
-This means you'll be able to debug Mainnet / Görli / Ropsten / etc. transactions
-that interact with external contracts _without the need to have external
-contract source code available locally_!
-
-Now, before you get too excited, some caveats apply:
-- This only works with Solidity contracts, since @truffle/debugger only supports
-  Solidity at this time.
-- While using this feature, you won't be able to load and unload transactions
-  in the debugger like normal; you'll have to quit and restart to change
-  transactions.
-- In order to be able to use the debugger and have it find the right source to
-  download for your network, you'll need to connect to an archive node that
-  offers the `debug_traceTransaction` JSON RPC method. (See Geth's [Management
-  APIs](https://github.com/ethereum/go-ethereum/wiki/Management-APIs)).
-
-That last one is a pretty big caveat, but **there's good news here**! Our
-sibling SaaS project, [Truffle Teams](/docs/teams/overview), now
-lets you [simulate live
-networks](/blog/sandbox-forking-with-truffle-teams)
-via the free Sandbox feature. This works without requiring you to run your own
-node or to pay for someone else to run their own node, since Truffle Teams
-offers 1 free sandbox per GitHub organization!
-
-Of course, you're free to use the debugger with whatever compatible Ethereum
-node you like, including command-line Ganache; but here's how to use Truffle
-Teams, which offers so much more, for this feature.
-
-### Example: Debug ENS in a [mostly] empty Truffle project!
-<a href="/img/blog/debugging-verified-external-contracts-with-truffle-debugger/debug-example1.png" target="_blank"><img width="100%" alt="Click to enlarge" src="/img/blog/debugging-verified-external-contracts-with-truffle-debugger/debug-example1.png">Click to enlarge</a>
-
-This screenshot shows `truffle debug` stepping through a Görli transaction to the ENS registry. Once you upgrade to Truffle v5.1.29, you can recreate this by doing the following:
-
-1. Find the [Görli ENS contract page on
-Etherscan](https://goerli.etherscan.io/address/0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e).
-
-2. Find a recent transaction hash. (See [example from
-screenshot](https://goerli.etherscan.io/tx/0x79381a69eb828558f2728900615109eb7bdeb6d216af130142341da15cc6fecd).)
-
-3. [Sign up / login to Truffle Teams](https://my.truffleteams.com/) and make a
-free Sandbox that forks off Görli. **Note**: At the moment, you'll have to make
-sure that you manually specify that the Sandbox should use the same network ID
-as the chain it's forked from (in this case, 5).  In the future, however, this
-step will be handled automatically.  You can read more about Sandboxes in [our
-earlier blog post on the
-subject](/blog/sandbox-forking-with-truffle-teams).
-
-4. Copy your sandbox JSON RPC url to the clipboard.
-
-5. Run `truffle init` and add this to your new `truffle-config.js` (replacing `"<paste RPC url>"` with your clipboard contents from step 4):
-  ```javascript
-  module.exports = {
-    /* ... rest of truffle-config.js ... */
-    networks: {
-      /* ... rest of networks ... */
-      sandbox: {
-        url: "<paste RPC url>",
-        network_id: 5
-      }
-    }
-  }
-  ```
-5a. _Optional_. If you have an [Etherscan API key](https://etherscan.io/apis) or
-feel like making one, you can specify that as well in your `truffle-config.js`
-to speed up downloads:
-  ```javascript
-  module.exports = {
-    /* ... rest of truffle-config.js ... */
-    etherscan: {
-      // replace this with your API key
-      apiKey: "0123456789abcdef0123456789abcdef"
-    }
-  }
-  ```
-
-6. Copy the transaction hash from step 2 and run the following (replacing
-`<transaction hash>` with the `0x`-prefixed transaction hash):
-  ```
-  truffle debug <transaction hash> --network sandbox --fetch-external
-  ```
-
-And that's it!  You're now debugging an ENS transaction in an empty Truffle
-project.  You can step through and set breakpoints; inspect both decoded
-variables and the raw binary state; and get return values, revert messages, and
-stacktraces just like normal.
-
-Now this example is a minimal one just to show how things work.  But it will
-work just as well in your existing projects on transactions that feature your
-contracts in your project interacting with external verified contracts deployed
-on live networks.
-
-Right now "verified contracts" just means contracts verified on Etherscan, but
-we're also looking at supporting the new
-[Sourcify](https://github.com/ethereum/sourcify) project, which provides a more
-decentralized alternative to Etherscan's repository. We plan to add this in an
-upcoming release.  But as of right now, you can use this feature with
-Etherscan's large library of verified contracts!
-
-**Update**: As of Truffle v5.1.32, [Sourcify](https://github.com/ethereum/sourcify) is now supported!  Truffle
-Debugger will now check both [Etherscan](https://etherscan.io/) and [Sourcify](https://github.com/ethereum/sourcify) for verified
-contract sources!
-
-Hope you find this as exciting as we do! Thanks for using Truffle!
diff --git a/src/blog/designing-the-ganache-logo/index.md b/src/blog/designing-the-ganache-logo/index.md
deleted file mode 100644
index 2e80b01bb..000000000
--- a/src/blog/designing-the-ganache-logo/index.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Designing the Ganache Logo
-hide:
-  - navigation
----
-
-Last week we released [Ganache](/ganache), a personal blockchain for Ethereum development. Many of you commented on the design of the landing page and logo, but just how did the gooey cube come to be? Let's take a trip through the 30+ iterations that led to our newest confection.
-
-<div class="row"><div class="col-xs-10 col-xs-push-1 col-sm-6 col-sm-push-3 m-b-2">
-![Final Ganache Logomark](/img/blog/designing-the-ganache-logo/final-logomark.png)
-</div></div>
-
-Before setting out on our design journey, we started with some loose guidelines:
-
-* The new logo should be round and have some dimensionality to keep it consistent with the Truffle logo.
-* The colors should consist of chocolate, an accent color and white.
-
-The concepts we explored can be roughly broken down into 4 categories: Core Cutaways, Toppings, Gooey Cores and Soft Blocks.
-
-## Core Cutaways
-
-The first set of core cutaways was an attempt to convey that Ganache, as a local development blockchain, was the "core" of your development workflow. They also depict a ganache filled truffle candy of varying viscosities.
-
-It was toward the end of this stage we qualified one of our initial guidelines. The logo's dimensionality should be represented purely by shape--no gradients!
-
-**Fun fact**: We considered one of the third row, second and third column concepts as a final candidate, but scrapped it when Tim's wife said it looks like a banana slug floating in space. My baby, a slug?! A great reminder to not get too attached before getting feedback!
-
-</div><div class="text-center container">
-  ![Ganache Logo Concepts - Core Cutaways](/img/blog/designing-the-ganache-logo/core-cutaways.png)
-</div><div class="container container-narrow">
-
-## Toppings
-
-Questions about the ability of the core cutaways to translate to flat color, as well as being dimensionally mismatched with the Truffle logo caused us to consider a simpler approach; a spherical candy with ganache on the outside. Overall these failed to look interesting and had the opposite problem in that they weren't dimensional enough.
-
-</div><div class="text-center container">
-  ![Ganache Logo Concepts - Toppings](/img/blog/designing-the-ganache-logo/toppings.png)
-</div><div class="container container-narrow">
-
-## Gooey Cores
-
-Not satisfied with the topping options we pressed on and attempted the core concept again, this time with some fancier cutaways. While they stood on their own, they were too wide a departure from the Truffle logo. This lack of cohesion lead to a realization that would be our design breakthrough.
-
-</div><div class="text-center container">
-  ![Ganache Logo Concepts - Gooey Cores](/img/blog/designing-the-ganache-logo/gooey-cores.png)
-</div><div class="container container-narrow">
-
-## Soft Blocks
-
-Letting go of our assumption that the shape should be round unlocked a series of designs that eventually led to our final logo. To achieve a more interesting drip pattern, we traced and combined different stages of glaze dripping down a cake. It became apparent that this approach was interesting, but made an overly detailed drip pattern which we later simplified for the final. We also tried a few different treatments of the candy's reflection. Check out that longhorn steer in the lower-left!
-
-</div><div class="text-center container">
-  ![Ganache Logo Concepts - Soft Blocks](/img/blog/designing-the-ganache-logo/soft-blocks.png)
-</div><div class="container container-narrow">
-
-## The Final Logo
-
-Success! After reconsidering some assumptions and solidifying others, we arrived at our final design. The final logo has both a compelling design and the following qualities that made it a winner:
-
-* The colors consist of chocolate, an accent color and white; a guideline we'll keep going forward.
-* It's metaphorically grounded in the product it represents--it's a block, after all!
-* The gooey consistency and soft, rounded corners represent the intimidating technical concept of a blockchain in a friendly and approachable way.
-
-<div class="row"><div class="col-xs-10 col-xs-push-1 col-sm-6 col-sm-push-3 m-b-2">
-![Final Ganache Logo](/img/blog/designing-the-ganache-logo/final-logomark.png)
-</div></div>
-
-We had a blast iterating this logo and Ganache itself. We hoped you learned from our experience and maybe picked up some of your own inspiration along the way. **Happy illustrating!**
-
--- Josh & the Truffle Team
diff --git a/src/blog/develop-using-fluidity-truffle-box/index.md b/src/blog/develop-using-fluidity-truffle-box/index.md
deleted file mode 100644
index 60307490c..000000000
--- a/src/blog/develop-using-fluidity-truffle-box/index.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Develop using Fluidity Truffle Box
-hide:
-  - navigation
----
-
-**TLDR;** Fluidity has a pretty awesome truffle-box with lots of goodies to build secure, well-tested smart contracts. With two simple commands, you’ll be set up for development using these testing and security tools preconfigured.
-
-To use:
-
-```shell
-npm install -g truffle
-truffle unbox fluidity/fluidity-truffle-box
-```
-
-## Develop using Fluidity Truffle Box
-
-Today, I’d like to share Fluidity’s Truffle Box. It contains a combination of tools we use to develop, test, and analyze our smart contracts. As our team has created several products and proof-of-concepts, we’ve developed a set of standards for creating smart contract repos and having a truffle-box makes this easier. We’ve tried and tested different tools and this box contains our favorite tools for efficient development.
-
-The Fluidity Truffle Box allows us to bootstrap our smart contract projects. This box focuses primarily on building safe and secure smart contracts that can be easily audited. We’re able to consolidate many of the new tools, as well as ensure that any projects we start always use up to date versions. Prior to starting new projects, we double check that the packages and tools within truffle-box are up to date. We acknowledge this truffle-box is not a kitchen sink of all the tools. It has been curated based upon what we consistently use. The box doesn’t have a UI component and mostly contains configurations and tools that aid in testing.
-
-## Core Tools
-
-At Fluidity we write smart contracts with Solidity using the latest fixed version, currently 0.5.10, and we use Ganache as our primary test chain. We use Open-Zeppelin as the base for many of our contracts’ systems. In addition, there’s a linter for both the smart contracts and tests using [solhint](https://www.npmjs.com/package/solhint) and [standard](https://www.npmjs.com/package/standard). A linter analyzes code and tests and then either recommends or updates the code for potential syntax errors and style recommendations. Solhint’s configuration is present in fluidity-truffle-box and tries to closely align with the Solidity documentation. We use standard because it’s opinionated and keeps the codebase consistent with minimal fuss. Thus, standard doesn’t have any custom configurations.
-
-## How we handle testing and code coverage
-
-### Gnosis Mock Contract
-Gnosis-Mock is a comprehensive mocking smart contract that allows us to perform unit-testing of our smart contracts. For those not familiar, mocking means creating dummy objects to simulate the behavior of real objects. Mocking allows one to isolate the behavior of the testable object from any other dependencies. As an example, certain behavior in smart contract designs, such as closing a token sale, may require dependencies on several state variables and contracts to already be triggered to allow it to burn tokens. To close a token sale, let’s say you need to have started the sale, sold some threshold of tokens, reached a certain future block, and given close sale privileges to another user. Any one of these requirements, outside of just calling close sale, would need to be run if mocking were not used. By simulating these states with dummy smart contract, it narrows down exactly what needs to be tested. We heavily use the Gnosis mock library which allows us to test contracts independently before running any integration tests.
-
-### Truffle Assertions
-Truffle assertions has streamlined how we test events and states of smart contracts. The packages works inside Truffle tests and provides more assertions to call about smart contract states. It supports revert reason strings so we can be confident that exact cases are hit on revert. In addition, it provides more granular ways to test for function failures.
-
-### Eth-gas-reporter
-Eth gas reporter shows us the gas usage per unit tests in a nice report after running your test suite. We’ve tried many other tools before as well as trying to write custom gas usage with web3. This has been a recent find for us and has made gas analysis much easier.
-
-### Solidity-coverage
-We use solidity-coverage to determine what percentage of the codebase is covered by unit tests. We use a forked version by **leapdao** because this version supports many of the breaking changes with Solidity 0.5.0+. Code coverages give a helpful metric to ensure we’re testing as we code and that all branch paths are tested. It has also served for us to remove redundant code paths that we’ve found were not accessible. In addition, we have incorporated code-coverage with our CI process, meaning it is automatically executed on every pull request we make, allowing us to easily check PRs for code coverage. The configuration is stored in `<project_rool>/.solcover.js`, and can be personalised for your project.
-
-### Slither and Mythril
-Both slither and mythril are python packages that we’ve included in our truffle-box. They are security tools by [Trail of Bits](https://www.trailofbits.com/) that allow us to better self-audit our code and evaluate many of our invariants and assumptions internally. Instructions to run each of these packages are stored in the README.md file of the fluidity-truffle-box.
-
-Slither is a static code analyzer by Trail of Bits. It runs across the contracts directory fairly quickly (< 1 min) and picks up potentially vulnerable Solidity code. Mythril is a security analysis tool for EVM bytecode from ConsenSys. The program takes much longer to run, and while it’s in the truffle-box, we’ll usually run this tool on AWS or another cloud environment and analyze those results. While there is some overlap of errors that are picked up by truffle-compile, slither, and mythril, each focuses on different types of error. We therefore find it helpful to use all 3 on our contracts.
-
-### Circle CI Template
-At Fluidity we use circle-ci for our continuous integration. By having sample templates in the repo, it’s more convenient to making sure we enable it whenever we create new repositories. The new repos therefore constantly have to build successfully and migrate via Ganache, and test coverage is apparent to all members on the team. With the template in place, it’s quick for us to add additional commands such as linting or gas reporting dependent on where we are in the development process.
-
-## Unique features
-### Using allowUnlimitedContractSize
-We allow our initial contract designs not to be limited by any contract size constraints with the use of the flag *allowUnlimitedContractSize*. Ganache has a default gas limit of 6,721,975 which does not reflect the actual gas limit of public testnet and mainnets, being 7,000,000 and 8,000,000 respectively. While our team does want to reduce the gas footprint while developing and iterating through different token designs/debugging, it’s been helpful not to be limited by a strict gas price or gas limit with testing. For example, we use longer descriptive messages in revert reasons when developing, but reduce them to be more succinct for final code versions. Reducing the string lengths saved us 3,000,000 gas.
-
-Run each line in a different terminal window
-
-```shell
-yarn ganache-unlimited
-yarn truffle truffle-unlimited
-```
-
-After settling on a design, we’ll start iterating to reduce gas usage. As mentioned above, we use eth-gas-reporter to do this. Thus, with 100% test coverage and integration tests, eth-gas-reporter gives a pretty comprehensive understanding of gas usage throughout.
-
-## Custom Migration and Test Utilities
-
-There are two custom utilities files that we have created and keep available for the right circumstance of contracts. First, we have a custom migration utilities script. Truffle has deployed contract management but only stores a single address for each contract deploy per network id; each deployed contract is treated as a singleton. However, there have been cases where we’ve deployed multiple instances of the same contract and have needed to save each of the deployed contract addresses. Our solution was to create a custom migration_utils.js that stored the contract addresses per migration in  a JSON file. From there, integration tests and accessory scripts use the contract addresses while still relying on the build directory for ABIs.
-
-The second script is related to testing time sensitive smart contracts. We’ve written a post about it called [Standing the Time of Test](https://medium.com/fluidity/standing-the-time-of-test-b906fcc374a9) and we’ve used this script and features in Ganache to run both idempotent tests as well as run simulations.
-
-Running the command for a specific date
-
-```shell
-yarn ganache-unlimited --time '2019-02-15T15:53:00+00:00'
-```
-
-## Anything else
-
-Most of the features are in the [README](https://github.com/airswap/fluidity-truffle-box) in the directory and I’d love to take any questions or issues using this repository. Linking all these tools allows for a solid, sane development process for our team. They’re always at our fingertips with fluidity-truffle-box. Hopefully, you’ll be able to use the Fluidity Truffle Box to enhance your own smart contract development process!
-
-## Github repos
-* Fluidity Truffle Box: [https://github.com/fluidity/fluidity-truffle-box](https://github.com/fluidity/fluidity-truffle-box)
-* Gnosis-Mock: [https://github.com/gnosis/mock-contract](https://github.com/gnosis/mock-contract)
-* Truffle Assertions: [https://github.com/rkalis/truffle-assertions](https://github.com/rkalis/truffle-assertions)
-* Eth gas reporter: [https://github.com/cgewecke/eth-gas-reporter](https://github.com/cgewecke/eth-gas-reporter)
-* Leapdao Solidity-Coverage: [https://github.com/leapdao/solidity-coverage](https://github.com/leapdao/solidity-coverage)
-* Original Solidity-Coverage: [https://github.com/sc-forks/solidity-coverage](https://github.com/sc-forks/solidity-coverage)
-* Slither: [https://github.com/crytic/slither](https://github.com/crytic/slither)
-* Mythril: [https://github.com/ConsenSys/mythril](https://github.com/ConsenSys/mythril)
-
-## Fluidity Resources:
-* Website: [https://fluidity.io](https://fluidity.io)
-* Twitter: [https://twitter.com/fluidityio](https://twitter.com/fluidityio)
-* Facebook: [https://facebook.com/fluidityio/](https://facebook.com/fluidityio/)
-* LinkedIn: [https://linkedin.com/company/fluidityio/](https://linkedin.com/company/fluidityio/)
-* YouTube: [https://youtube.com/c/fluidityio](https://youtube.com/c/fluidityio)
-* Blog: [https://medium.com/fluidity](https://medium.com/fluidity)
diff --git a/src/blog/drizzle-150-a-new-beginning/index.md b/src/blog/drizzle-150-a-new-beginning/index.md
deleted file mode 100644
index af77107ca..000000000
--- a/src/blog/drizzle-150-a-new-beginning/index.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Drizzle 1.5.0 - A new beginning
-hide:
-  - navigation
----
-
-<figure>
-  <img src="/img/blog/drizzle-150-a-new-beginning/sunrise.jpg" alt="Sunrise landscape" style="width:100%">
-  <figcaption style="text-align: center;">_The dawn of a new era for regular releases and a better contributor experience_</figcaption>
-</figure>
-
-Since the beginning, our goal here at Truffle has been to make dapp development as easy as it can be. To this end Josh Quintal created [Drizzle](https://github.com/trufflesuite/drizzle), a managed Redux store to make interfacing with the blockchain just a little bit easier.
-
-## From many to one
-
-Today, we are announcing that we are moving to a monorepo. From now on, a single PR can be used to update code and documentation that used to span multiple repos.
-
-Over the last two years, we’ve developed libraries on top of Drizzle such as `drizzle-react` and `drizzle-react-components`. Since these libraries depend so heavily on each other, it only makes sense for us to move all of these packages to a monorepo to streamline any updates.
-
-In addition, we now also have an experimental Vue.js plugin that fits naturally into the monorepo architecture. It is very likely that going forward we will develop new packages to aid the Drizzle ecosystem in this manner.
-
-## Scoped package names
-
-Another big change we are making is towards scoped package names on NPM. This means that instead of:
-
-```
-drizzle
-drizzle-react
-drizzle-react-components
-drizzle-vue-plugin
-```
-
-We will now have:
-
-```
-@drizzle/store
-@drizzle/react-plugin
-@drizzle/react-components
-@drizzle/vue-plugin
-```
-
-From an organizational standpoint, this makes it a lot more intuitive to manage your dapp development.
-
-## Testing
-
-Prior to the monorepo, testing our libraries together was a slow, error-prone and painful experience. Our maintainers had to build custom dapps to isolate changes and manually link packages together as well as coordinate with ganache for each front end.
-
-The monorepo allows us to have dedicated front end apps that automatically build against the latest libraries and we can conveniently orchestrate them with a single ganache instance in just a couple commands. In other words, you can easily spin up three apps to test various aspects of the monorepo [in seconds](https://github.com/trufflesuite/drizzle/blob/develop/README.md#testing-and-debugging-with-ganache).
-
-<figure>
-  <img src="/img/blog/drizzle-150-a-new-beginning/test-ui.png" alt="Test UI instances" style="width:100%">
-  <figcaption style="text-align: center;">_Easily spin up real front ends to test that dapps can work with the current code_</figcaption>
-</figure>
-
-## Better release strategy
-
-Perhaps the biggest thing that the changes above allow us to do is more frequent releases.
-
-In the past year, we often had to deal with delaying the publishing of a new change because it required testing and updating other repos. Our publishing process was essentially being blocked by having to synchronize changes amongst multiple repos.
-
-With a monorepo, that all changes, which means that you can look forward to more regular releases and a faster turnaround time for getting issues fixed. Better changelogs are also coming as we move toward adopting [conventional commits](https://www.conventionalcommits.org) for each PR that gets merged.
-
-## Going forward
-
-It’s important to note that Drizzle wouldn’t be what it is without the open source community. A big part of why we are making all these changes is because we need you to help us make Web3 a reality together.
-
-Here at Truffle, every member on the team is passionate about improving the developer experience of building on Web3. In the upcoming weeks, we will be doing more regular blog posts targeting the front end space so keep an eye out!
-
-I would also like to specifically thank Amal Sudama for his work on making this transition. It certainly couldn’t have happened without him.
diff --git a/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md b/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
deleted file mode 100644
index 0dffda153..000000000
--- a/src/blog/drizzle-reactive-ethereum-data-for-front-ends/index.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Drizzle - Reactive Ethereum Data for Front-ends
-hide:
-  - navigation
----
-
-Today we're proud to announce the addition of a new product to the Truffle Suite: Drizzle. Drizzle is a collection of front-end libraries that make writing dapp front-ends easier and more predictable.
-
-The core is based on a Redux store. We take care of synchronizing your contract data, transaction data and more. Things stay fast because you declare what to keep in sync. Importantly, this means you have access to the spectacular development tools around Redux. **Want to time travel through your recent transactions? You can do that with a slider.**
-
-  <video width="640" height="480" controls>
-    <source src="/img/blog/drizzle-some-chaindata-on-your-ui/drizzle-time-travel.mp4" type="video/mp4">
-    Your browser does not support the video tag.
-  </video>
-
-Drizzle's architecture is completely modular. This means you never lose access to the underlying web3 functionality you already know--drizzle as much or as little as you like. We've created two packages for use with React, but the core functionality is contained in the base `drizzle` module itself. If you're familiar with Redux, it's not a stretch to create an Angular library or use it for something other than a webapp.
-
-  ![Drizzle Modules](/img/blog/drizzle-some-chaindata-on-your-ui/drizzle-modules.png)
-
-Want to dive in right away? `truffle unbox drizzle` and you've got a full example dapp. Need more info? Read on!
-
-## The Libraries
-
-### Drizzle
-
-The core library responsible for web3, account and contract instantiation; wiring up the necessary synchronizations and providing additional contract functionality.
-
-[GitHub Repo](https://github.com/trufflesuite/drizzle)
-
-### Drizzle React
-
-Provides a DrizzleProvider component and drizzleConnect helper method to make it easier to connect Drizzle with your React app.
-
-[GitHub Repo](https://github.com/trufflesuite/drizzle-react)
-
-### Drizzle React Components
-
-A library of useful components for common dapp functions. Currently includes:
-*   `LoadingContainer`: Wraps your app, ensuring it waits for web3 and contract instantiation and displays relevant feedback if something goes wrong.
-*   `ContractData`: Displays contract call output.
-*   `ContractForm`: Automatically generates a form for contract transactions.
-
-[GitHub Repo](https://github.com/trufflesuite/drizzle-react-components)
-
-## The Box
-
-Shown in the video above, this box makes use of all of Drizzle's libraries in a finished example dapp.
-
-[GitHub Repo](https://github.com/truffle-box/drizzle-box)
-
-**Help us grow this baby!** What do you want to see from Drizzle? More components? More options? To put it another way: what are you sick of doing on the front-end?
-
-![Drizzle Baby](/img/blog/drizzle-some-chaindata-on-your-ui/baby.jpg)
-
-We're excited to hear your feedback and can't wait to see what you'll build! 
-
--- Josh & the Truffle Team
diff --git a/src/blog/drizzle-vue-a-truffle-story/index.md b/src/blog/drizzle-vue-a-truffle-story/index.md
deleted file mode 100644
index 3a7ada19e..000000000
--- a/src/blog/drizzle-vue-a-truffle-story/index.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Drizzle Vue - A Truffle Story
-hide:
-  - navigation
----
-
-![Drizzle + Vue = <3](/img/blog/drizzle-vue-a-truffle-story/title-image.png)
-
-Truffle is an organization that maintains a balance of transparency, mentorship, encouragement, inclusivity and humor that I'm thankful for everyday. While much could be written about Truffle's management culture, I want to share my experience of working on a side project here.
-
-Our remote work setup and the openness of our team contributes to a healthy and productive environment. The ability to schedule zoom sessions to brainstorm and discuss ideas fits well with our schedule. Every member contributes to this culture being generous with their time and knowledge. I'm happy and inspired to see team members grow as developers through the subtle mentorship as a result of our culture.
-
-For most of my career, I dreaded mandatory soul draining review type meetings, but at Truffle, I look forward to the incredibly productive and creative weekly one-on-ones I have with Joshua Quintal, our Product Lead. Josh originally developed Drizzle and we often discuss its role in the dapp ecosystem, issues and roadmap during our meetings.
-
-## About Drizzle
-
-Drizzle is a Smart Contract Store with a subscription and mutation API that abstracts away the boilerplate for reading and writing smart contract state as well as listening for contract events.
-
-Drizzle originated as a helper library for a React project Josh was developing. However he came to realize that the Smart Contract Store was an important piece needed in dapp development as applications start to scale. In Web 2.0 the need to manage and reason about state at scale has led to libraries like [1] [Redux](https://redux.js.org/introduction/prior-art). Similarly, we want to give web 3.0 dapp developers these best practices to leverage as their applications grow in complexity.
-
-## Drizzle's Unintended Front End Frameworks Exclusion
-
-Unfortunately, this is not how Drizzle is understood by developers we interviewed formally and informally. The most common misunderstanding is that Drizzle is coupled with React, the most popular JavaScript front end framework. We can't blame our community as most of our documentation focuses on implementing Dapps using React.
-
-Drizzle was initially released with bindings only for React which created this misperception that excluded developers from utilizing other front end frameworks such as Vue and Angular.
-
-The problem is that we didn't offer an easy solution for Vue or Angular and our documentation doesn't offer guidance. We want to change this! We want to support all the frameworks!
-
-## A Vue Plugin Side Project
-
-I felt this was an important problem to solve in order to improve the dapp developer experience.  It was important to get Drizzle working for Vue. Unfortunately, I knew nothing about Vue. In previous organizations I was a part of, I would have shied away from pursuing this project. However, at Truffle I felt comfortable and empowered to champion the idea. Josh encouraged me to spend the time needed to study Vue and experiment with the concepts.
-
-The basic plan was to:
-- Use Vuex, Vue's popular State management plugin
-- Transform Drizzle's redux store to be consumed by Vuex
-  - A redux store as an [2] [Observable](https://redux.js.org/api/store#subscribe) which would allow us to transform/map drizzle state to a more state pieces that Vuex could consume.
-  - This would allow us to have more efficient UI renders by using RxJS techniques like `distinctUntilChanged`
-- Create basic Vue components mimicking drizzle-react-components
-  - Vue's architecture allows us to use the adaptor as a datasource as well as provide basic support for Components that can render the data. This gives Vue developers to use our basic Components to make quick proof of concepts, and the flexibility to create richer Components when they need to.
-
-A [3] [basic proof of concept](https://github.com/trufflesuite/drizzle-vue-plugin) eventually surfaced and I was happy with the outcome as it showed a path forward to Angular using this approach with RxJS and can't wait to test it out!
-
-## Collaboration And Improvements
-
-Another aspect of Truffle's culture is to promote collaboration and exchange ideas with our community, and meet like minded developers and advocates working on similar problems. We're encouraged to go to meetups and be advocates for this incredible space.
-
-I reached out to Julien Klepatch on reddit after seeing his impressive [4] [Drizzle overview video](https://www.youtube.com/watch?v=QH_yLPYQEs4&feature=youtu.be) and asked for his feedback on the Vue Plugin. His participation, code contribution, code review and feedback clarified the project's direction and generally improved the codebase. Furthermore, he created 3 videos to explain the new plugin.
-- [5] [Drizzle Vue Plugin: overview](https://www.youtube.com/watch?v=XaVEZ1ucxac)
-- [6] [Drizzle Vue Plugin: Custom Components](https://www.youtube.com/watch?v=ApJwXfWKl7Q)
-- [7] [Drizzle Vue Plugin: Events](https://www.youtube.com/watch?v=xyoztqeYd6U)
-
-We also run a range of educational programs as part of Truffle University, that amongst other things, teaches developers how to use our full suite of tools. As part of the experience, students are mentored by the team and are encouraged to contribute to open-source projects, such as the Truffle Suite itself. James Kehoe, a developer in our first cohort, uses Vue on a daily basis and took an interest in the plugin. He took the initial design of the Contract Event Logic and turned it into idiomatic Vue. James also improved the documentation and introduced testing to the project. I learned a lot about Vue pairing with James, and look forward to future sessions with him.
-
-## Take A Preview
-
-You can preview the [3] [Plugin](https://github.com/trufflesuite/drizzle-vue-plugin) before we officially release it. Be sure to check out Julien's videos for an excellent walkthrough: [5] [Drizzle Vue Plugin: overview](https://www.youtube.com/watch?v=XaVEZ1ucxac), [6] [Drizzle Vue Plugin: Custom Components](https://www.youtube.com/watch?v=ApJwXfWKl7Q) and [7] [Drizzle Vue Plugin: Events](https://www.youtube.com/watch?v=xyoztqeYd6U)
-
-This project happened because of Truffle's enabling and supportive culture. Truffle is cool like that!  Also, co-MVPs James and Julien's improved the Vue Plugin and made it a viable tool. In fact, I consider them to be original contributors and am happy to see their continued involvement in the project.
-
-Come meet the team and learn about our tools at TruffleCon. We're looking forward to meeting you all!
-
-## References
-1. https://redux.js.org/
-1. https://redux.js.org/api/store#subscribe
-1. https://github.com/trufflesuite/drizzle-vue-plugin
-1. https://www.youtube.com/watch?v=QH_yLPYQEs4
-1. https://www.youtube.com/watch?v=XaVEZ1ucxac
-1. https://www.youtube.com/watch?v=ApJwXfWKl7Q
-1. https://www.youtube.com/watch?v=xyoztqeYd6U
diff --git a/src/blog/ethereum-gas-exactimation/index.md b/src/blog/ethereum-gas-exactimation/index.md
deleted file mode 100644
index 6b21130bc..000000000
--- a/src/blog/ethereum-gas-exactimation/index.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: Ethereum Gas Exactimation
-hide:
-  - navigation
----
-
-In Ethereum, estimating gas for a given transaction is a tricky problem to solve (especially when attempting to maintain [EIP-114](https://github.com/ethereum/EIPs/issues/114) compliance). Most of the well-known Ethereum implementations like Geth<sup>¹</sup> and Parity<sup>²</sup> use interval halving (binary search) to estimate gas by running transactions through the EVM until an approximate estimation converges.
-
-![Ganache Logo](/img/ganache-logo-h-dark.svg)
-
-At [Truffle](/), we decided such an approach was an unnecessarily CPU-intensive solution to the problem and set out to find a (theoretically) more performant and perfectly accurate way of estimating gas. The result? [Gas exactimation](https://github.com/trufflesuite/ganache-cli/releases/tag/v6.4.2). In this tutorial, we’ll go over gas exactimation at a high level in order to demonstrate its precision.
-
-**Complete example available at [the following repo](https://github.com/trufflesuite/gas-exactimation-tutorial).**
-
-**_Prerequisites: You should be familiar with Truffle, Ganache, and Solidity. If you need an introduction please consult the following resources:_**
-
-* [Truffle Quickstart](/docs/truffle/quickstart)
-* [Ganache Quickstart](/docs/ganache/quickstart)
-* [Solidity Documentation](https://solidity.readthedocs.io/en/v0.5.9/index.html)
-
-## EIP-114, or the “1/64ths rule”
-
-[EIP-114](https://github.com/ethereum/EIPs/issues/114) mandates that certain stackdepth-creating opcodes _withhold_ 1/64th of remaining gas from the stack they create. In practice this means:
-
-1. The gas required for a successful transaction can be greater than the actual gas spent (similar to how gas refunds behave).
-2. The extra gas required for a successful transaction varies depending on the transaction’s initial `gas` amount.
-
-A long-standing issue with [Ganache](/ganache) has been the fact that we haven’t returned EIP-114 compliant gas estimations. This has caused our gas estimates to be too low in cases where a transaction executed certain opcodes. **Gas exactimation** addresses this by considering how the gas withheld at any nested stack depth/frame affects the gas needed outside of its execution context.
-
-Let’s see it in action.
-
-## Create a New Truffle Project
-
-We will use `truffle init` to create a new Truffle project and then wire up an example [Solidity](https://solidity.readthedocs.io/en/v0.5.9/index.html) smart contract and test script.
-
-```shell
-// In a new project directory...
-$ truffle init
-```
-
-## Setup an Example Smart Contract
-
-With our new project initialized, we will create an example file: `ContractFactory.sol`.
-
-```shell
-$ touch ./contracts/ContractFactory.sol
-```
-
-Our file will have two contracts, `Contract` and `ContractFactory`. `ContractFactory` will have the method `createInstance` that we will use to create a new empty `Contract`.
-
-```
-// ./contracts/ContractFactory.sol
-pragma solidity ^0.5.0;
-
-contract ContractFactory {
-  function createInstance() public {
-    new Contract();
-  }
-}
-
-contract Contract {
-  constructor() public {}
-}
-```
-
-Note the `new` keyword being used to create a new `Contract`. A valid statement containing the `new` keyword gets compiled to bytecode containing the `CREATE` opcode which is subject to the [EIP-114](https://github.com/ethereum/EIPs/issues/114#issue-160782694) 1/64th gas withholding.
-
-## Write a Test Case
-
-Next, we will write a `ContractFactory` test case.
-
-```shell
-$ touch ./test/ContractFactory.js
-```
-
-This test case will deploy `ContractFactory` to a Ganache test network and use a gas estimate provided by Ganache to create a new `Contract`.
-
-```
-// ./test/ContractFactory.js
-const ContractFactory = artifacts.require("ContractFactory");
-
-contract("ContractFactory", () => {
-  it("...should deploy and successfully call createInstance using the method's provided gas estimate", async () => {
-    const contractFactoryInstance = await ContractFactory.new();
-
-    const gasEstimate = await contractFactoryInstance.createInstance.estimateGas();
-
-    const tx = await contractFactoryInstance.createInstance({
-      gas: gasEstimate
-    });
-    assert(tx);
-  });
-});
-```
-
-## A Quick Check
-
-Before we run our test, we’ll download the most recent version of Truffle that uses Ganache _before_ gas exactimation.
-
-```shell
-// In the project directory...
-$ npm i truffle@5.0.13
-```
-
-And we’ll make sure we have the latest version of Truffle installed globally that uses Ganache _with_ gas exactimation.
-
-```shell
-$ npm i -g truffle
-```
-
-## Testing Before and After
-
-```shell
-$ npx truffle test
-...
-...
-Error: Returned error: VM Exception while processing transaction: revert
-```
-
-And when we use gas exactimation...
-
-```shell
-$ truffle test
-...
-...
-Contract: ContractFactory
-
-✓ ...should deploy and successfully call createInstance using the method's provided gas estimate (130ms)
-
-1 passing (143ms)
-```
-
-!!!!
-
-## Testing Exactimation
-
-But is gas exactimation actually _exact_? 🤔
-
-We’ll open our test file and subtract exactly a single unit of gas from the `gasEstimate` before sending our test transaction.
-
-```shell
-// ./test/ContractFactory.js
-const ContractFactory = artifacts.require("ContractFactory");
-
-contract("ContractFactory", () => {
-  it("...should deploy and successfully call createInstance using the method's provided gas estimate", async () => {
-    const contractFactoryInstance = await ContractFactory.new();
-
-const gasEstimate = await contractFactoryInstance.createInstance.estimateGas();
-
-const tx = await contractFactoryInstance.createInstance({
-      gas: gasEstimate - 1
-    });
-    assert(tx);
-  });
-});
-```
-
-Running our test again against Ganache with gas exactimation...
-
-```shell
-$ truffle test
-...
-...
-Error: Returned error: VM Exception while processing transaction: revert
-```
-
-Exactimation confirmed 🚀.
-
-Note: Since the initial release of gas exactimation, an even more performant iteration of the algorithm is currently in review here.
-
-[1]: [https://github.com/ethereum/go-ethereum/blob/master/accounts/abi/bind/backends/simulated.go#L267](https://github.com/ethereum/go-ethereum/blob/master/accounts/abi/bind/backends/simulated.go#L267)
-
-[2]: [https://github.com/paritytech/parity-ethereum/blob/master/ethcore/src/client/client.rs#L1658](https://github.com/paritytech/parity-ethereum/blob/master/ethcore/src/client/client.rs#L1658)
diff --git a/src/blog/first-ever-truffle-retreat/index.md b/src/blog/first-ever-truffle-retreat/index.md
deleted file mode 100644
index b7a3a22ba..000000000
--- a/src/blog/first-ever-truffle-retreat/index.md
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: Our First Ever Truffle Retreat
-hide:
-  - navigation
----
-
-![Truffle](/img/blog/first-ever-truffle-retreat/medium-truffle-retreat.jpg)
-
-This past summer, the Truffle team got together to together to define our roles, our mission statement, and our product roadmap - and had some fun in the process.  
-
-----------
-
-The Truffle team is fully remote. This has a lot of advantages in that it allows for a wide range of people available to work on your project; but it can also make it difficult to get to know your coworkers. 
-
-I started Truffle in early 2015 as the sole developer, and it stayed that way for nearly a year and half. John McDowell joined in late 2016, and by the time of the retreat we happily brought Nick D’Andrea and Josh Quintal on board. All interviews happened over Skype.
-
-I live in Yakima, Washington. John lives in Victoria, British Columbia. Nick lives in Philadelphia, and Josh lives in Detroit. That’s a lot of distance between us. 
-
-![Truffle employees in September](/img/blog/first-ever-truffle-retreat/truffle-map-01.jpg)
-
-When we brought Nick and Josh onto the team, it became obvious that we needed to meet up in person to solidify our roles, define responsibilities, and establish our own culture before growing the team even larger. 
-
-And we wanted to hang out in the woods, at the top of a mountain, and get to know each other. 
-
-## The Location
-
-![View from the house](/img/blog/first-ever-truffle-retreat/location.jpg)
-
-We had our retreat near Victoria, BC where John lives. Nick, Josh and I traveled all day through a series of planes, ferries and car rides to finally arrive at the house around 7 pm. The house sits atop a large hill in Braemer Heights overlooking all of Victoria, and on a good day has a beautiful view of Mt. Baker in the States. 
-
-The house was the definition of excess for a team of four, especially with only three of us sleeping there. It had five bedrooms and four bathrooms; a deck with a grill; three stories, the topmost containing only an office with 360-degree windows; and loads of wildlife. Unexpectedly, it was only ten minutes away from a Costco, which helped immensely. Even more unexpectedly, this mansion cost us less than three hotel rooms and a coworking space.  
-
-![Another view](/img/blog/first-ever-truffle-retreat/mountain.jpg)
-
-## The Work
-
-I had a few specific goals for our retreat: to define everyone’s roles and responsibilities within our team, to define our product roadmap for the next six months, and to create a mission statement for Truffle that our whole team could rally behind. 
-
-### Retrospective
-
-We started with a retro. We wanted to evaluate where we were as a team before deciding where we wanted to go in the future.
-
-So on Tuesday morning, we sat down and gave praise for what we’ve done well and identified areas where we could improve. I brought a list of business areas that are important for Truffle -- things like development, technical leadership, branding, marketing, etc. -- and we graded ourselves on each of them. 
-
-This turned out to be an interesting exercise. As the leader of the team you want to say “we’re doing great”, and not diminish anyone’s efforts -- because, it’s true, we’ve come far for a small team. However, we need to know where we can improve and how different areas of our company, teamwork and products stack up to the rest. In general, we all seemed to agree on the results: Branding and growth have been stellar (e.g., we have a good product that people like to use), but more external communication -- like our technical leadership, our relationship with the Ethereum Foundation, and relationships with some of our VIP users -- could use some improvement. Though these results were mostly subjective judgements, the conversations that resulted helped inform discussions about our roles and future roadmap. 
-
-### Roles & Responsibilities
-
-The Truffle team had already doubled in size in 2017, and right before the retreat two new team members -- Ben Burns and Mike Pumphrey -- had accepted offers (welcome!). So we knew we had some work to do regarding defining our roles and how we work together as a team.
-
-Before the retreat, I had met separately with Nick, Josh, and John to evaluate how they felt about their current roles at Truffle. We each talked about what they wanted to do both within the team and professionally, and how I could help them get there. Then we used this time at the retreat to reorganize the work so that it aligns with each team member’s personal goals as well as the group’s goals. We created a new org chart and chain of command, including the new team members we knew were coming on. 
-
-We decided that Josh and John would share design responsibilities for our website, logo design and general aesthetics for all of our products. Ben, who started in October, would take on the internals of the TestRPC (now [Ganache](/ganache/)) and related products ensuring we stay up to date with the Ethereum ecosystem. And Mike would be coming on board to wrangle all of our documentation and learning content, eventually molding it into tailored courses we’d offer to individuals and businesses. 
-
-That just left Nick and I. Though we both knew Nick would work on the internals of Truffle when he was hired, we didn’t know the extent of the work required; in addition to improving Truffle, Nick would be burdened with the arduous task of softly and lovingly ripping my baby from my arms. That is, Truffle’s my baby, and I’ve been nurturing it from day one. In order to build a more functional and growing team, it became clear I’d have to let go of the internal implementation details and focus more on our business and our product, leaving Nick to explore the tool’s technical way forward.
-
-This transition has been a great growing experience already, both professionally and personally. We’ll continue to evaluate this structure over the next six months to see how it works out. 
-
-### Mission Statement
-
-The next step was to determine why we’re here. The big three questions were: Why are you here? What do you value? And what do you stand for? The point was to elicit each team member’s value systems to get a big picture of what it is we really care about. 
-
-My original plan for this session was to put each person on the spot and ask them those questions directly. As it turns out, this interrogation technique was not the best way to get meaningful, genuine answers from the team. 
-
-Luckily, John came up with a better plan. He suggested we have each member of the team write their values on six index cards, and then have the whole team talk about each other’s values, create a big list, and vote on them to determine our company values. 
-
-![Our values](/img/blog/first-ever-truffle-retreat/mission.jpg)
-
-The conversation helped us all understand how different we were, and how much our values varied. We expressed everything from receiving good pay to building the distributed ecosystem. 
-
-In the end, we all agreed why we’re here. Our new mission statement: 
-
-> _Truffle builds useful tools for the next generation of blockchain technologies. We enable the growth of the Ethereum and open source communities, help to improve the role of decentralization in society, and empower developers to achieve their goals._
-
-### Product Roadmap
-
-On Thursday, we got into the details of what we’ve been working on at Truffle and where we’re going. This included presentations for new products [SPOILER ALERT!] and discussions about specific features. We’ve been hard at work since we drafted this post, so some you may have heard of already: 
-
-* [Truffle 4.0!](https://github.com/trufflesuite/truffle/releases) - with a debugger, improved development and testing experience, and more! 
-* [Ganache](/ganache) - a personal blockchain for developers. 
-* Drizzle - a frontend framework for React and Angular to easily connect Truffle-based projects.
-* Project Hotcakes - a full stack suite for web applications.
-* Live - a browser-based, interactive Truffle IDE.
-
-We also talked about revamping our development processes, which included not only how we work together as well as beefing up our continuous integration systems and making it very easy for users to contribute to Truffle projects. Stay tuned for more info!
-
-## The Fun
-
-In the middle of all of this work we wanted to get some bonding time in too. And if you haven’t been to Victoria, it really is gorgeous, and we couldn’t let this trip go to waste.
-
-So on Wednesday we got in John’s Honda Element and drove for two hours to Port Renfrew. The hike on paper: beach hike, sun, potentially bears, great outdoorsy time. The hike in reality: 
-
-![Rainy hike](/img/blog/first-ever-truffle-retreat/hike.jpg)
-
-We didn’t see any bears, and we got completely rained out of the hike. But, we also took our first Truffle team selfie: 
-
-![hashtag selfie](/img/blog/first-ever-truffle-retreat/team-pic.jpg)
-
-And eventually when the rain cleared got this cloudy-but-serene view from the dock at Port Renfrew.
-
-![A nice dock](/img/blog/first-ever-truffle-retreat/dock.jpg)
-
-And when we got back to the house, we made dinner, played board games, and drank a bunch of wine. 
-
-![Fooooood](/img/blog/first-ever-truffle-retreat/food-1.jpg)
-![Josh cooks](/img/blog/first-ever-truffle-retreat/food-2.jpg)
-
-So overall, we had some successful bonding time. 
-
-## Going Home 
-
-Being able to all be in the same room for the first time ever was extremely rewarding. It gave us a great foundation for the future of our working relationships and of Truffle as a whole, and increased our personal relationships in a way you don’t get when working 100% remotely. We’ll definitely be making retreats a recurring part of working at Truffle. 
-
-Now that we’re all back to work as usual, we’ve already taken the results of the retreat to heart. We’ve implemented our new development processes (info to come soon); revamped our products and offerings to be more in line with each other; have been settling into our new roles amazingly, and with little conflict; and overall we’ve been having a great time.
-
-There are a few things I want to make sure I remember coming out of this retreat: 
-
-**You can build more of a relationship with someone in 10 minutes in person than you can in 3 months on Slack.** I want to maintain this momentum and rapport. We’ve found that video calls are the closest you can get on a 100% remote team. Going forward, we’re now having one-on-one meetings every week to make sure we can keep up our rapport and ensure we’re giving each other consistent, useful feedback.   
-
-**The right processes and structures are the basis for responsibility, autonomy, and trust between teammates.**  During the retreat we collectively decided on rules and structure that would help us work better together. These rules were meant to increase responsibility and autonomy and provide a basis of trust in decision-making where each of us are responsible for our own individual specialties. I want to increase this trust and know that each team member can make the right decisions when needed.
-
-**Building rapport with your teammates is worth the effort.** In a remote team you don’t often get the chance to invite your coworker over for dinner or go to a local event. Bridging this gap is hard, and requires conscious effort, but has so many benefits including happiness, morale and general enthusiasm toward coming into work every day. I want to continue to bridge this gap and foster a culture where even if we’re a thousand miles away, we can still feel close enough to have each other over for dinner.
-
-Final thought: I’d eat Nick’s caprese salad and Josh’s sirloin medallions any day of the week.
diff --git a/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md b/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
deleted file mode 100644
index 954d59301..000000000
--- a/src/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/index.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Get a Bird's Eye View with Truffle Teams' New Dashboard
-hide:
-  - navigation
----
-
-<figure>
-  <img class="mb-4" src="/img/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/blog-header.jpg" alt="Truffle Teams Dashboard" style="width:100%">
-</figure>
-
-As the operational needs of your dapp grow in complexity, it helps to be able to choose an area of focus. More incoming data begets a greater need to gain insights and properly segment that data to prevent overload. Wouldn’t it be nice to see an overview of a particular deployed instance of your application with the ability to drill down into the parts you need to see in more detail? This is where the dashboard comes in!
-
-<p class="alert alert-warning">💬 The Dashboard feature could expand in many different directions and we need your help to prioritize what matters most for your dapps. In that spirit we’ve released this first version quickly to get the conversation started. Please comment in the <a href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA">Truffler Slack workspace</a>, <a href="mailto:info@trufflesuite.com">email us</a>, reach out any way you can--we’re excited to hear from you.</p>
-
-We first asked ourselves “what is a dashboard”? and surprisingly, got many different answers! We arrived at this definition: **A dashboard is a place to see an overview of your application, along with ways to drill down and get further context on more narrow slices.**
-
-The first release focuses mostly on the high-level, but we plan to increase the drilldown capabilities as the feature evolves.
-
-## A Bird’s Eye View
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/get-a-birds-eye-view-with-truffle-teams-new-dashboard/truffle-teams-dashboard.png" alt="Truffle Teams Dashboard" style="width:100%">
-  <figcaption class="text-center font-italic">The dashboard page with a deployment selected</figcaption>
-</figure>
-
-In this first version of the dashboard, you can pin a deployment for quick insights and visualization. Some of this information we haven’t surfaced before, such as the deployment’s cost and the number of unique addresses interacting with a deployment’s contracts.
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE NEW DASHBOARD</a>
-</div>
-
-## Looking Ahead
-
-Here’s a bit of a teaser for you to get an idea of where this is going:
-
-* A filter option to specify exactly which contracts are being displayed in the transaction graph
-* A list of contracts providing the ability to hop into monitoring a specific contract instance or...
-* Quickly interact with those contracts via our upcoming Contract Manager
-
-We strive for Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about this integration solution, and if your team has other needs we haven’t met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3 mb-4" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLE SLACK COMMUNITY</a>
-</div>
-
-Thanks!
-_Josh Quintal, Head of Product & Marketing_
\ No newline at end of file
diff --git a/src/blog/github-repository-moved/index.md b/src/blog/github-repository-moved/index.md
deleted file mode 100644
index a48f5d8ad..000000000
--- a/src/blog/github-repository-moved/index.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: We've moved our github repo!
-hide:
-  - navigation
----
-
-We recently released [Truffle 3.0](https://github.com/trufflesuite/truffle/releases/tag/v3.0.2) in February to [much fanfare](/dashboard). As part of that release we separated our codebase into multiple different modules to make integrating with Truffle easier. Those modules now live in the github repository [https://github.com/trufflesuite](https://github.com/trufflesuite), which hints at our broader mission of providing a comprehensive suite of tools for Ethereum development.
-
-## But something was missing...
-
-We forgot Truffle! The main Truffle repository -- including the Truffle command line tool -- remained at it's old [Consensys](https://github.com/consensys) location while its modules hung out at their new digs. We thought to ourselves: That just wouldn't do. So, as matter of announcement, Truffle has officially moved. It's new home is [https://github.com/trufflesuite](https://github.com/trufflesuite).
-
-## Wait, there's more.
-
-The [Truffle Suite](https://github.com/trufflesuite) repository will soon be filling up with more open-source tools to make your Ethereum development life easier. We're not ready to announce what those are yet, but stay tuned for some awesome announcements in the coming weeks.
-
-## While you're here.
-
-While we're announcing things, we should let you know we have a new Twitter account: [@trufflesuite](https://twitter.com/trufflesuite). Feel free to reach out to use there for all your Truffle needs.
-
-Au revoir for now!
-
--- Tim
diff --git a/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md b/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
deleted file mode 100644
index b14a5d918..000000000
--- a/src/blog/how-ethical-advertising-will-transform-the-blockchain-industry/index.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: How Ethical Advertising Will Transform the Blockchain Industry
-hide:
-  - navigation
----
-
-![GitCoin](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/pasted image 0-5.png)
-
-*CodeFund is an ethical ad platform that funds contributors to the open source ecosystem. Visit [CodeFund](https://codefund.io/) to learn more and apply.*
-
-### The Conflicting Relationship Between Blockchain and Marketing
-In the initial years following Bitcoin’s inception, most blockchain companies didn’t need paid advertising. The early adopters were a community of cypherpunks, libertarians, developers, miners, and hobbyists, that truly believed in the power of decentralized networks. To them, adoption was inevitable, and rather than putting paid ads in front of the general public, resources were better spent building wallets, development tools, infrastructure, and scalability solutions.
-
-Additionally, almost all early blockchain users and entrepreneurs were extremely privacy-conscious. Pseudonymity is a key component to cryptocurrencies, they wouldn’t work in a permissionless manner without it. The Adtech industry, on the other hand, is run by monolithic centralized powerhouses that gather and store immense amounts of personal data for precise targeting. For the first 5 years of Bitcoin, **the blockchain community ethos was quite literally the polar opposite of the advertising industry**.
-
-That’s not to say that in the early days exchanges, wallets, and other blockchain services were unable to run successful marketing campaigns. However, the community was generally so niche that most users had a good sense of what they were looking for. The famous cliche, “If you build it, they will come” is frequently repeated in this space. While it was arguably true for Bitcoin, the internet, and certain decentralized protocols, the data shows that marketing is often crucial for launching a business or community built on top of these networks.
-
-![Blockchain thought leaders Anthony Pompliano and Ryan Selkis share differing views on marketing](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-1.jpg "Blockchain thought leaders Anthony Pompliano and Ryan Selkis share differing views on marketing")
-
-Following the launch of Ethereum, the rise of smart contracts, and the ICO mania, things changed. All of a sudden it was relatively easy for startups to launch their own token and rake in millions with a whitepaper. As a result, marketing budgets began to skyrocket and paid campaigns were everywhere due to the (seemingly) huge potential for capital accumulation.
-
-While some genuinely revolutionary ideas were started and funded during this time, the vast majority were subpar projects and outright fraudulent scams preying on naive users. At one point [Coinmarketcap](https://coinmarketcap.com/), a fairly well-regarded website in the crypto space, was showing ads for [Bitconnect](https://en.wikipedia.org/wiki/Bitconnect), a known Ponzi scheme.
-
-![Example 2](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-2.jpg)
-
-As a result, most mainstream ad providers like Google and Facebook banned all ads pertaining to crypto. Some people in the blockchain industry thought this was unfair, but it was for good reason. Scammy projects were ruining the public perception of blockchain technology. However, reputable companies were also caught in the crossfire, finding it increasingly difficult to advertise their projects. Notably, Mailchimp’s blockchain ban impacted a project I was working on along with plenty of other startups. I remember when [Evan Van Ness](https://twitter.com/evan_van_ness)’ twitter and [Week in Ethereum](https://www.weekinethereum.com/) newsletter (my favorite Ethereum educational resource) were shut down [multiple times](https://cointelegraph.com/news/breaking-mailchimp-reportedly-shuts-down-accounts-related-to-crypto-prices-drop).
-
-![GetCoin image 3](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-3.jpg)
-
-So, what’s the solution? Fortunately, the majority of mainstream advertising services have relaxed their bans on blockchain advertising in the face of a maturing ecosystem. This is especially interesting when considering that both [Google](https://www.bloomberg.com/news/articles/2018-03-21/google-is-said-to-work-on-its-own-blockchain-related-technology) and [Facebook](https://libra.org) have announced their foray into the industry.
-
-### Existing Blockchain Advertising Obstacles
-
-We recently released a [blog post](https://codefund.io/blog/how-to-advertise-your-startup-blockchain-project) covering a variety of different free and paid channels to advertise your blockchain startup. And although there are more options than ever, there are still several obstacles to overcome. As we appear to be approaching the next bull market, scams will undoubtedly come back (I’ve already seen a huge uptick in the “free crypto” scams on twitter). Further, the crypto ecosystem hasn’t addressed the problems of mass data collection and rampant user profiling in the Adtech world. Most of us believe blockchain will be the catalyst for a revolution of privacy and self-sovereign identity, hopefully breaking up the big data monopolies of web2. Yet **the entrepreneurs and thought leaders pushing this narrative of individual autonomy and privacy in the digital age are still using advertising services that track, profile, and collect mass amounts of data from their target markets.** Marketing is inevitable - startups need to reach their desired audience and grow a user base. But can this be done in a more ethical way, in line with the ethos of this technology we love and support?
-
-### Enter: CodeFund
-
-While all of this craziness was happening in the blockchain world, [Eric Berry](https://twitter.com/coderberry) was focused on tackling a different problem: [The Open Source Conundrum](https://codefund.io/blog/the-open-source-conundrum-how-do-we-keep-the-lights-on). Open source software lays the foundation for the Internet as we know it and supports so much of our global business processes, yet comparatively receives very little support and funding. **How can we help open source projects and maintainers get consistent financial support?**
-
-Eric founded Code Sponsor [2 years ago](https://changelog.com/founderstalk/56), allowing companies to place small text-based sponsored messages on GitHub project READMEs to support open source software. Since then he’s been threatened with legal action, shut down, started again, rebranded to CodeFund, and eventually joined the [Gitcoin](https://gitcoin.co/) team at [ConsenSys](https://consensys.net/), who share the same mission: **get developers paid**.
-
-At [CodeFund](https://codefund.io/), we pride ourselves on showing ethical ads on developer websites, acknowledging and respecting individual privacy. This means that our ads do not track, use cookies, nor collect any data except for IP addresses and browser agents. We feel ads that track our browsing history and know our personal information are an invasion of privacy, and from our research, the majority of our user base feels the same way. So while we can't profile and target specific demographics and individuals, we can help you tailor your ads to the desired audience and display them on sites that your audience frequents with geotargeting. Users will see ads that they actually want to see without compromising their data, browsing history, or personal information.
-
-CodeFund is 100% [open source](https://github.com/gitcoinco/code_fund_ads) (feel free to contribute! 😄) and was built by developers for developers, so we understand the motivations of our users. We keep our content relevant by only showing high-quality ads from companies that are of interest to the audience. We diligently vet all advertisers and publishers to make sure they are a good fit for the network. By understanding the community and showing them ads relevant to their interests, you build trust between your advertisers, publishers, and most importantly, users.
-
-The CodeFund model is a bit unorthodox in the Adtech world. However, we find it to be extremely successful in our niche (and growing) open source community. Developers are typically [much more likely](https://www.stackoverflowbusiness.com/engagement/resources/the-state-of-developer-engagement-2018) to use ad blockers compared to typical Internet users. Developers are also known to be more concerned about privacy and data collection. For these reasons, they can often be hard to reach with advertising. To get your message seen, you need reputable publishers who are trusted by their audience. CodeFund is bound by the standards set by [acceptable ads](https://acceptableads.com/en/about/criteria), which means many ad blockers do not block us. We work with our users to allow our ads and make sure they are relevant to the audience, ensuring all parties involved are benefiting.
-
-![CodeFund growth by impressions, YTD](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-4.jpg "CodeFund growth by impressions, YTD")
-
-We believe the future of the web will be a **privacy-focused, user-driven evolution**. More scandals are emerging from large corporations revealing data mismanagement, leaks, and hacks of sensitive information. Digital advertising will never go away, but the average internet user is becoming more security and privacy conscious, and we think this will lead to an increased demand for ethical advertising products. That's why we built a platform to allow advertisers to get their message to the right audience without compromising user integrity.
-
-### Ethical Ads for Blockchain - Why Target Crypto Users?
-
-Initially CodeFund was not focused on the blockchain space, however, since [joining Gitcoin](https://medium.com/codefund/code-sponsor-joins-gitcoin-b7d35966b93d), we’ve been [expanding](https://medium.com/gitcoin/codefund-ads-on-etherscan-fae1a3d35b51) our offerings. We realized that ethical advertising is going to play a crucial role in Web3, blockchain, open source, and the future of the Internet - and that's something we want to support.
-
-Blockchain technology was undeniably born out of the open source ecosystem. While the two communities are not exactly the same, they share many morals and have significant overlap. By nature, blockchain and cryptocurrencies would be useless if they were not open source. A key feature of *decentralized* cryptocurrencies is that there is no need to trust an intermediary and no barriers to entry. For it to work, anyone must be able to run, review, and contribute to the code. Today's leading blockchains are a cumulation of hundreds, if not thousands of individuals contributing to open source code bases.
-
-Just like most developers, blockchain users and enthusiasts tend to be much more privacy conscious than a typical Internet user. As a result, CodeFund's ethical ad model is a great fit, not only for blockchain developers but also for blockchain users.
-
-CodeFund ensures that the blockchain projects we work with are building applications and tools for open source blockchains, primarily for Ethereum. We don’t work with projects pumping their own token sales, instead, we partner with blockchain companies that are **adding value to society and the open source ecosystem**.
-
-### CodeFund’s Blockchain Offerings
-
-For the next few months, CodeFund will be actively building out our blockchain publisher and advertiser networks. We are currently publishing ads on [Etherscan](https://etherscan.io/), [State of the Dapps](https://www.stateofthedapps.com/), [Etherchain](https://www.etherchain.org/), [Decrypt Media](https://decrypt.co/), [Coingecko](https://www.coingecko.com/), and a handful of other high-quality blockchain websites - with even more in the pipeline. Decrypt just release a great [piece](https://wp.me/p9ZACC-1Vv) on the problems with crypto “news” sites, and their motivations for advertising ethically. Our advertisers like [Truffle](/truffle) are happy with their results so far and have seen high conversion rates from their campaigns, without sacrificing the privacy and integrity of their audience.
-
-![Decrypt’s ethical ad integration](/img/blog/how-ethical-advertising-will-transform-the-blockchain-industry/getcoin-image-5.jpg "Decrypt’s ethical ad integration")
-
-Crypto markets are beginning to turn around, more startups are shipping products, and the global blockchain community is growing. We expect this trend to continue, driving the demand for blockchain advertising as a result. Many blockchain websites publishing ads see it as a necessary evil – they need to keep the lights on to continue providing their services, but feel their choices are limited.
-
-The first option is working with companies to run direct advertising campaigns. However, this approach consumes time and resources and can be risky if advertisers pull out. The second option, and perhaps the easiest, is to use Google Ads or another incumbent service. Using this approach, many feel they’re compromising users’ privacy and trust. Moreover, outsourcing to huge Adtech giants is part of the problem that made ICO scams so rampant in 2018-2019. These companies simply have far too much traffic and lack the specialized skill set required to manually vet every single advertiser and identify blockchain scams. The last thing publishers want on their website is an ad that loses your users' money or promotes the purchasing of unregistered securities.
-
-At Gitcoin and CodeFund, we are a small team that has been in the blockchain world for years. We view every publisher and advertiser as a partner, diligently vet them, and hold them to the highest standards. **We’d like to see ethical advertising become the new standard in the blockchain space, and eventually on the Internet as a whole.**
-
-If your blockchain company is interested in advertising to a high-quality audience, or you would like to earn passive income showing relevant ads on your website without sacrificing your community’s privacy, CodeFund is for you! Apply now on the [CodeFund](https://codefund.io/) landing page and we’ll be in touch, or reach out to [connor@codefund.io](mailto:connor@codefund.io) for more information.
diff --git a/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md b/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
deleted file mode 100644
index 9de4546d4..000000000
--- a/src/blog/how-the-arrival-of-web-3-0-is-transforming-traditional-business-models/index.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: How the Arrival of Web 3.0 is Transforming Traditional Business Models
-hide:
-  - navigation
----
-
-Although the Internet continues to drive digital transformation, the technology operates far beyond its original parameters. Since its inception over two decades ago, the web has been subject to increasing levels of centralization and mass surveillance. As a result, large corporations, governments, and media outlets remain the primary beneficiaries of an infrastructure meant to serve all of humanity. Herein lies the problem with the current Internet ecosystem, also known as Web 2.0.
-
-In the current online environment, users continually function as commodities, generating value along with their data. And while large entities should not shoulder the blame for their role in our everyday lives, their control over our personal information is cause for concern. As Internet founder Tim Berners-Lee [once said](https://www.vanityfair.com/news/2018/07/the-man-who-created-the-world-wide-web-has-some-regrets), "for people who want to make sure the Web serves humanity, we have to concern ourselves with what people are building on top of it."
-
-It is precisely this sentiment that drives the Web 3.0 movement. And although blockchain technology may be the foundation of this movement, the initiative is much broader. Web 3.0 is about building a decentralized infrastructure that protects individual property and privacy. But what exactly does this look like and what are the potential implications? In this article, we'll explore the evolution of Internet infrastructure and how the arrival of Web 3.0 is impacting existing business models.
-
-## The Evolution of Web Infrastructure
-
-The Internet debuted employing simplistic "read-only" technology, meaning users were only able to search for information and read it. This Web 1.0 environment was primarily intended for advertising purposes, acting as an extension of physical storefronts. With the arrival of "read-write" functionality, users of Web 2.0 are able to create their content and interact with the Internet in a far deeper capacity. By facilitating the prolific growth of social media platforms, blogs, and online reviews, this infrastructure continues to guide global business models.
-
-However, as mentioned, this era of robust growth has not come without consequences. Consumer protections continue to rank behind corporate interests as web surveillance fuels lucrative data collection. Continued [data breaches](https://www.nytimes.com/2018/08/01/technology/data-breaches.html) effectively highlight the downside of this arrangement. In response to these challenges, Web 3.0 initiatives aim to put power back into the hands of users. But before exploring how this will occur, it's crucial to understand the specific Web 3.0 characteristics that will facilitate this process.
-
-![Example 1](/img/blog/how-the-arrival-of-web3/web3-example1.jpg)
-
-## Characteristics of Web 3.0
-
-Although Web 3.0 is difficult to define in exact terms, it can be effectively broken down into unique components.
-
-### Semantic Web
-
-The [semantic web](https://www.w3.org/standards/semanticweb/) improves upon existing web infrastructure by generating, sharing, and connecting content based on an understanding of words. Rather than relying on keywords and numbers, search and analysis utilize context.
-
-![Source: The Semantic Web Stack
-Connectivity](/img/blog/how-the-arrival-of-web3/web3-example2.jpg)
-*Source: [The Semantic Web Stack
-Connectivity](https://devopedia.org/semantic-web)*
-
-Thanks to semantic metadata, Web 3.0 achieves greater connectivity. By leveraging all available information, the user experience dramatically improves.
-
-### Artificial Intelligence
-
-Web 3.0 technology can process information in a way similar to humans. As a result, platforms can better satisfy user needs through continuous learning.
-
-### 3D Capabilities
-
-Three-dimensional design is already in use on many Web 3.0 platforms. Computer games, e-commerce applications, and mapping software represent only a few potential use cases.
-
-### Ubiquitous
-
-In the decentralized Web 3.0 environment, all content is accessible by multiple applications, every device connects to the web, and the associated services are available everywhere.
-
-## Web 3.0 and Existing Business Models
-
-Although we have only just begun to explore the potential of Web 3.0 applications, their ability to upset the status-quo is undeniable. Of particular interest to many is how decentralized projects, operating in traditional industries, will up-end conventional revenue models. Through utilizing distributed, peer-to-peer platforms, some industries have begun to consider other funding options.
-
-![Example 3](/img/blog/how-the-arrival-of-web3/web3-example3.jpg)
-
-Although there is a vast array of revenue models to consider, we’ll explore some of the most prominent options here. To see the full list, check out the [Github repository](https://github.com/FEMBusinessModelsRing/web3_revenue_primitives/#revenue-share).
-
-### Revenue Share
-
-The revenue share model uses profits to enable separate actors to develop efficiencies or innovate in mutually beneficial ways, such as splitting earnings.
-
-#### Percentage Fee
-
-This model is where you take a percentage of each transaction executed on your platform. It remains a popular model with exchanges and marketplaces. The seller usually pays for the fee since they're the one that benefits from completing a sale on the platform.
-
-#### Income Share
-
-Using this model, users share earnings from another entity. An offline example would be a restaurant where the cashier shares the tips with everyone. In the context of Web 3.0, you could give a one-dollar tip in a coffee shop and split it with every actor in the coffee value chain with minimal transaction costs.
-
-### ICO’s
-
-Conducting an ICO is the process of selling project tokens all at once, or over some time. There are several ICO models and token variations that companies can use to raise funds.
-
-### Continuous Funding Models
-
-Continuous Funding Models are business models that sell ERC-20 tokens over time, rather than all at once.
-
-#### Curved Bonding
-
-Curved Bonding is a method of continuous funding that incentivizes early investment. In contrast to conventional ERC-20 token sales and ICO's, which feature each token being sold for the same price (no matter the time of purchase), such models hardcode buy prices according to an algorithmic curve. By purchasing early, investors get more tokens for the same price than if they are buying later. Ultimately, using Curved Bonding incentivizes early adopters to invest in a token.
-
-#### Continuous Organizations
-
-A continuous organization is one that sets up a Decentralized Autonomous Trust (DAT). This trust is an immutable smart-contract that implements curve bonding to automatically mint, burn, and distribute security tokens called FAIR securities. Organizations provide value to the trust by diverting part or all of their cash flow to it.
-
-### Streaming Money
-
-#### Side Channels
-
-A sidechain is a separate blockchain that is attached to its parent blockchain using a two-way peg. Using this model, you can move assets to the sidechain and then back to the parent chain. However, sidechains also need their miners. These miners receive an incentive through 'merged mining,' whereby two separate cryptocurrencies, based on the same algorithm, are mined simultaneously.
-
-#### State Channels
-
-State channels are mostly two-way pathways open between two users that want to communicate with each other in the form of transactions. Here, only the outcome needs to be included in the form of a single transaction on the main chain. Other transactions occur on off-chain.
-
-### The Future of Internet Infrastructure
-
-As the development of Web 3.0 technology persists, blockchain technology will remain a vital component of online infrastructure. Although the world continues to benefit from the transformative power of the web, user empowerment remains a priority among a growing segment of society. In a time when centralized institutions and governments exert control over personal data, many have begun to challenge the status quo.
-
-Those exploring this emerging subset of the web are well-positioned to benefit from growing momentum. By leveraging Web 3.0 technologies, companies also have the ability to enact new, potentially lucrative business models. Regardless of the industry, the new web presents an opportunity to pivot from traditional revenue streams in search of more optimal solutions. In the midst of ongoing innovation, it’s important to note that all new technology requires refinement - and Web 3.0 is only just beginning.
diff --git a/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md b/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
deleted file mode 100644
index 4cb75b39b..000000000
--- a/src/blog/how-to-get-your-boss-to-send-you-to-trufflecon/index.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: How to get your boss to send you to TruffleCon
-hide:
-  - navigation
----
-
-Last year [Truffle Suite](/) launched [TruffleCon](/trufflecon2019), an event designed for the Truffle community and those interested in building world-changing applications powered by decentralized technologies. The event was received with an overwhelmingly positive response. TruffleCon attracted 250 attendees, 53 speakers, and 2 locations. After such a successful inaugural event, the team immediately started planning an even bigger and better Trufflecon for 2019.
-
-Join us this year on August 2-4 at the Microsoft Campus in Redmond, WA for the second annual event for the Truffle community: those who actively build using Truffle’s framework for development on Ethereum. Programming will include speakers from the blockchain ecosystem, along with hands-on workshops geared toward novice users and expert builders alike. There’s truly something for developers of all experience levels!
-
-TruffleCon places focus on the developer by exploring the many ways in which the Truffle tools can enhance the development process by increasing efficiency and enabling high-quality dapp production.
-
-We know that attending a blockchain conference often comes down to ROI for your organization. With so many learning and growth opportunities, here are a few things to remind your boss about when asking to send you to the 2nd Annual [TruffleCon](/trufflecon2019).
-
-## Truffle is widely considered the most popular tool for blockchain application development
-
-Truffle is widely considered the most popular tool for blockchain application development with over 1.5 million lifetime downloads. Truffle supports developers across the full lifecycle of their projects, whether they are looking to build on Ethereum, Hyperledger, Quorum, or one of an ever-growing list of other supported platforms. Paired with Ganache, a personal blockchain, and Drizzle, a front-end dapp development kit, the full Truffle suite of tools promises to be an end-to-end dapp development platform.
-
-## Truffle is being used by the largest and most prominent firms
-
-If your company want to implement blockchain solutions, you’ll need to learn how to interact with Truffle suite of products. Truffle is used by many fortune 500 firms and will be the first company to integrate with AxCore, a proprietary blockchain created by Goldman Sachs and JPMorgan-backed Axoni, which is scheduled to start processing $10 trillion worth of transactions annually for the DTCC’s Trade Information Warehouse later this year.
-
-Here are some of the amazing companies using or integrating Truffle:
-* Microsoft, ConsenSys, Amazon, VMWare Airbus, General Dynamics, J.P. Morgan and more!
-* Soon to be your company too!
-
-## Build dapps hands on and learn to deploy smart contracts 
-
-TrufflCon will have something for everyone from the novice and crypto curious to the advanced blockchain developers and everyone in between. Truffle’s world-class developers and trainers will be there to support you along your developer journey. You’ll learn hands-on how to build dapps and deploy smart contracts during our workshops.
-
-## Meet and learn from the creators of Truffle Suite: the ones closest to Truffle’s development
-
-#### Tim Coulter
-Tim Coulter is the Founder and CEO of Truffle. Before blockchain, Tim built a career specializing in software testing and developer support, which became extremely valuable in the early days of blockchain development. He's now surrounded by an amazing team building the next generation of blockchain development tools, and can't wait to tell you about what's to come.
-
-#### Mike Seese
-Mike Seese is a Core Developer on the Enterprise Products team. In addition to integrating the Truffle Suite to other ledgers and frameworks, he strives to bring the modern development experience to the blockchain community.
-
-#### Josh Quintal 
-Josh is passionate about where the user meets the tech; this led to the creation of two products, Truffle Boxes and Drizzle. He also created "Pet Shop", one of Ethereum's most used beginner tutorials. Besides his obvious technical prowess,Josh is also the most stylish member of the Truffle team.
-
-#### G. Nicholas D’Andrea
-Ever since 2016, he has been obsessed with the decentralized future and working towards building core software components for the blockchain ecosystem. Besides his work on Truffle, he is a core contributor to the EthPM package management system and author of EIP-1123.
-
-#### Kevin Bluer
-He’s building our world-class program at Truffle University from the ground up which trains existing software developers to become Truffle-certified blockchain engineers. Outside of his work with Truffle, he has trained and mentored developers in cities around the globe including New York, Austin, London, Hong Kong, Shenzhen, and Kuala Lumpur.
-
-TruffleCon is a place to meet our developers and work with them, ask questions, and get feedback on your work.
-
-## TruffleCon is for developers by developers
-
-While there is no shortage of conferences in the blockchain space, TruffleCon is uniquely created for developers, by developers. Tim Coulter, Truffle’s Founder & CEO, explained, "Developers attach their identity to the tools they're using. People are congregating around Truffle and want to learn from and collaborate with the people who are using the tools. We aim to host a conference where people can engage with their peers and share insights on how best to use these tools. We hope attendees will leave inspired and that the knowledge shared will transform how people build."
-
-## There will be lots of chocolate
-
-If your boss is still not convinced, most importantly, there will be A LOT of chocolate.
-
-Now, send this to your boss so they can send you to TruffleCon!
-
-[Secure Your Spot for TruffleCon 2019 in Redmond, WA August 2-4, 2019.](/trufflecon2019)
-
-More 2019 announcements are on the way — [Subscribe to the Truffle newsletter](https://truffleframework.us11.list-manage.com/subscribe/post?u=947c9b18fc27e0b00fc2ad055&id=97cfd4251b) and [join the conversation on Telegram in the TruffleCon Channel](https://t.me/TruffleCon).
\ No newline at end of file
diff --git a/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md b/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
deleted file mode 100644
index 840c7388c..000000000
--- a/src/blog/how-were-making-installation-issues-a-thing-of-the-past/index.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: How we're making installation issues a thing of the past
-hide:
-  - navigation
----
-
-<p class="alert alert-info">
-**Update**: Since this blog post was published, we have released [Ganache](/ganache) a personal blockchain and a replacement to the TestRPC. We have left this post unaltered, but we highly recommend checking out our [Ganache Quickstart](/docs/ganache/quickstart) page.
-</p>
-
-It doesn't matter what operating system you're on -- if you've used Truffle in any capacity, you've likely run into an install issue in some form or another. This is especially true for Windows, as Windows doesn't generally ship with the necessary tools to install all of Truffle's important dependencies. And for most users, this sucks: getting hung up on installation is incredibly frustrating when you're usually just one error message or two away from creating your first Ethereum-enabled application. Well, I've got good news. As of the latest Truffle beta release, I'm happy to tell you that this is an issue no longer.
-
-That's right: No matter what platform you're on, your install issues should be over. This is big.
-
-In order to completely sidestep most if not all of the most common installation issues, we had to overcome some technical difficulties as well as rethink how we ship our code. In this post, I'm going to tell you about what we did and how that made installation incredibly simpler, on every platform, for everyone.
-
-## So what was the problem?
-
-Since Truffle is a Javascript-based application, we (naturally) ship our code using the [Node Package Manager](https://www.npmjs.com/) (NPM for short). NPM hosts thousands if not millions of code packages, and it's the service that makes modern Javascript programming possible. Without NPM, not only would programming Truffle be nearly impossible, but programming _anything_ complex in Javascript would be impossible: NPM lets developers separate and bundle code into its own individual chunks, called "packages", that any of those other chunks (packages) can then rely on.
-
-Because of NPM, Truffle is standing on the shoulders of giants. Truffle relies on the code of so many other people that if you looked at the full list you'd be hard pressed to give us credit for the codebase. And that's the beauty of it: packages like hashing functions and cryptographic libraries -- hard libraries to write (and get right!) -- we don't have to write ourselves.
-
-Though using dependencies on NPM has significant upsides, it also comes with significant drawbacks. Those same hashing functions -- functions used throughout Ethereum -- are written to be extremely performant, and so are written in C. In order to install those packages, NPM has to be able to compile them on the fly during installation, which means every Truffle user needs to have a C compiler installed. Additionally, NPM (for some reason) uses Python during the compilation process, which means Truffle users _also_ need to have Python installed.
-
-Bottom line: In order to install a Javascript project, Truffle users need both C and Python. [This is madness.](https://s-media-cache-ak0.pinimg.com/originals/ec/5a/0a/ec5a0a5e4990668ca3f41ed50ca273d3.gif)
-
-## So what can we do?
-
-Most of the issues people were seeing stem from the compilation process mentioned: Either they didn't have the right compilers/interpreters installed for C and Python, or C and Python _itself_ required some dependency that wasn't properly installed. We've had a [tutorial](/guides/how-to-install-truffle-and-testrpc-on-windows-for-blockchain-development) written for awhile that shows Windows users how to correctly set up their environment and get everything installed, but this required considerable effort from novice users and didn't take into account the many landmines hiding around every corner, waiting to explode at any moment. So we can't "instruct" our way around this problem. The only way to fix it, then, is to sidestep it completely.
-
-Sidestepping the compilation process means completely excising any compilation out of the installation process. The way we chose to tackle this is two ways:
-
-- Remove any unnecessary dependencies that rely on compilation.
-- Replace dependencies that need compilation with versions 100% written in Javascript.
-
-In theory this sounds easy: i.e., "just use the Javascript versions or don't use the C versions as all". In practice, this is much harder. Often, we don't directly control the dependencies our application relies on, because _dependencies of dependencies_ (of dependencies of dependencies) might rely on a package that requires compilation. Since the bad apples are the packages that power the code we rely on (i.e., they're "indirect dependencies"), we have to surgically remove them and replace them with versions that install and function more easily. This is no small matter.
-
-Thankfully, a tool exists that makes this surgical replacement possible. It's called [Webpack](https://webpack.js.org/). Webpack bills itself as a Javascript bundler, aiming to mash together all your project's dependencies into a single blob of code, i.e., a "bundle". Webpack finds most of its uses in browser applications, as browsers need to download all code first before a website can be displayed, and it's more performant for the browser to download that code in a single request. However, for console applications like Truffle, Webpack can still be immensely valuable. By creating a bundle with Webpack, we can control exactly which dependencies get included in it.
-
-Take [js-scrypt](https://github.com/tonyg/js-scrypt) for instance. This library provides hashing functions required by Ethereum, is 100% written in Javascript, and is API-compatible with the C-compiled [node-scrypt](https://github.com/barrysteyn/node-scrypt) library. With Webpack, we can simply remove `scrypt` and replace it with `js-scrypt` like nothing happened.
-
-How about another example: Let's do IPFS. Truffle relies on the [ethpm-js](https://github.com/ethpm/ethpm-js) package to provide EthPM support, which itself relies on the [ipfs](https://github.com/ipfs/js-ipfs) package to communicate with IPFS servers. Somewhere deep down in `ipfs`'s dependency tree, some code needs the [execSync](https://www.npmjs.com/package/execSync) package, a package that causes installation issues for some users. Using Webpack, when creating our bundle, we can just _not include it_. Since that code only matters for parts of IPFS that Truffle doesn't use, that code doesn't need to be in our bundle. Ex-nay, [gone-yay](https://www.technobuffalo.com/wp-content/uploads/2016/03/kanye-west-1280x640.jpg). Zip, zilch, completely gone.
-
-Creating a bundle for our releases instead of letting NPM manage dependencies has other benefits as well. To keep code modular and maintainable, Truffle relies on almost 2000 packages! (This includes the dependencies of dependencies we mentioned before). Bundling ahead of time creates a single file users have to download during installation instead of requiring NPM to make requests for all 2000 dependencies. So not only do we get to sidestep all of the installation issues, but we make installation nearly instant as well.
-
-Yep. Feel free to party. We did. 🎉
-
-## So how can you get it?
-
-Bundling Truffle's dependencies means releasing a version of the code where certain dependencies have been either replaced or removed. This not only means releasing structurally new code, but it means releasing code that has differing testability characteristics which change our ability to ensure its of the quality you've come to expect. We need to build infrastructure to help us do that, so in the meantime **we've released the new version of the code in beta.**
-
-To get the beta version of Truffle, first uninstall the version you currently have (they'll conflict):
-
-```shell
-$ npm uninstall -g truffle
-```
-
-And now install the beta version:
-
-```shell
-$ npm install -g truffle@beta
-```
-
-You'll notice that the beta version installs almost instantly, and no compilation is required. Hot-dog.
-
-## So what's next?
-
-As we gain responses from the community about this new version we'll likely make changes to ensure we've sidestepped all the installation issues that have plagued users in the past. Once that's finished we'll make an official release. As well, we'll be performing this same work for the TestRPC in the coming weeks to ensure the TestRPC has the same hassle-free, instant installation that you'll soon come to expect from Truffle.
-
-If you run into issues with the beta version, don't hesitate to [write up an issue](https://github.com/trufflesuite/truffle/issues) in our issue tracker or reach out on the [community Gitter channel](https://gitter.im/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions.
-
-Cheers, and we appreciate your ongoing support and feedback.
-
--- Tim & the Truffle Team
diff --git a/src/blog/introducing-ganache-7/index.md b/src/blog/introducing-ganache-7/index.md
deleted file mode 100644
index f4a7a54af..000000000
--- a/src/blog/introducing-ganache-7/index.md
+++ /dev/null
@@ -1,310 +0,0 @@
----
-title: Ganache 7 Ethereum Simulator - Building on Web3 is now easier and faster than ever before
-hide:
-  - navigation
----
-
-![ganache v7 banner](/img/blog/introducing-ganache-7/ganache-v7.png)
-
-**By Kingsley Arinze, Mei Chan and David Murdoch**
-
-Ganache is a pioneer in the Ethereum development space, aiding DApp developers and enthusiasts to build, test, and explore blockchain since 2016. We are excited to announce the wide release of the latest version of Ganache today, with 30 times faster forking performance and an Infura integration that allows you to replay historical transactions with free access to archive data.
-
-For the uninitiated, Ganache is a local development blockchain used to develop decentralized applications on the Ethereum blockchain. It simulates the Ethereum network, and you can see how your DApp will perform before you release it to production.
-
-Typically, to start developing distributed applications on the Ethereum network, you will need to set up an Ethereum client such as Geth or OpenEthereum to provide you access to an [Ethereum Virtual Machine (EVM)](https://ethereum.org/en/developers/docs/evm/).
-
-Although that is a great way to develop distributed applications on Ethereum, it is not the most efficient and user-friendly approach, as you need to configure these clients manually and keep them running. Maintaining a self-hosted node can be expensive and time-consuming, you don’t want to spend valuable time troubleshooting a failed node during development.
-
-With Ganache, all you need to do is start the application and you have a preconfigured Ethereum client with 10 pre-funded and unlocked accounts ready for use. This allows you to quickly test your DApp throughout your development cycle.
-
-## Ganache 7: 30x faster forking and operations
-
-Many Web3 developers building on Ethereum already use Ganache to fork and test smart contracts in their local environments for confidence before deployment. Armed with the knowledge gained from previous iterations, we rewrote Ganache from the ground up with the mission to make the blockchain simulator tool even more flexible, faster, and more stable. 
-
-We heard your feedback that Ganache v6 was slow to install, slow to run, and leaked memory. It also didn’t use the modern language features and paradigms developers use today, like TypeScript types and the Promise abstraction. Ganache v6’s architecture made testing, fixing bugs, and adding features difficult and time-consuming.
-
-How is Ganache v7 better?
-
-- With advanced caching capabilities on the latest version, Ganache's forking feature is up to 30 times faster than v6.
-- Zero-config Mainnet forking! Ganache v7 has a [native integration with Infura](https://blog.infura.io/fork-ethereum-replay-historical-transactions-with-ganache-7-archive-support/) which enables free access to historical data
-- You can run Ganache indefinitely without running into crashes due to memory issues
-- Common operations are about 3 times faster than v6.
-
-## Installing and Setting up Ganache 7
-
-Ganache can be used in many ways, including as a command-line tool, programmatically via Node.js, or in the browser. See the instructions below for installing and using Ganache 7 for all these use cases.
-
-### A. Using Ganache 7 On the command line
-
-To run Ganache 7 on the command line, you must have Node.js >= v12.0.0 and NPM >= 6.4.1 installed on your computer. See [here](https://nodejs.org/en/download/) to download the latest version for your operating system, or use nvm to manage your Node installation for [Unix](https://github.com/nvm-sh/nvm) or [Windows](https://github.com/coreybutler/nvm-windows).
-
-With Node.js and NPM installed, you can install Ganache 7 globally by running `npm install ganache --global`. Once installed, you can run `ganache` from anywhere in your command line. 
-
-Your terminal should look like this:
-
-![screenshot-1](/img/blog/introducing-ganache-7/example-1.png)
-
-By default, Ganache provides 10 test accounts, each with 1000 (fake) Ether along with the corresponding private keys and the mnemonic phrase used to generate them. You can use this phrase to import the accounts into wallets like [MetaMask](https://metamask.io/) during development.
-
-We can override all defaults by specifying options when starting Ganache 7; for example, we can have more control over account creation by providing a mapping of private keys to account balances like so:
-
-```
-ganache --wallet.accounts "0xfd485338e322f5930f7cf475f385341ec88bfc4f8a0a16f30b2fb417d1bb5427, 1000000000000000000000" "0x05bba0b9f7a251080aa23feee4eab3f75a1abee905c0271008c93e5d2e2e7541, 10000000000000000000000"
-```
-
-We can also specify a mnemonic phrase to derive all initial accounts from,  a miner gas price, and the block gas limit. For example:
-
-```
-ganache --miner.defaultGasPrice 200 --miner.blockGasLimit 90071 --miner.callGasLimit 898989 --wallet.mnemonic "alarm cause brave super lab glide awake hunt rose win sugar idea"
-```
-
-Run the command `ganache --help` for a list of all the available options you can pass to Ganache.
-
-We can also install ganache into a local Node.js project using  `npm install ganache` without the `--global` flag, then add it to your project’s package.json `scripts`, e.g., `"scripts": {"ganache": "ganache --mnemonic <12 words mnemonic>"}`.
-
-### B. Using Ganache 7 programmatically
-
-Ganache 7 can be used programmatically in your Node.js project as:
-
-- A standalone EIP-1193 provider,
-- A JSON-RPC server and EIP-1193 provider, 
-- A web3.js provider and
-- An ethers.js provider. 
-
-See code samples for these different use cases below.
-
-To begin, install Ganache 7 as  npm package in your Node.js project
-
-```console
-$ npm install ganache
-```
-
-As a standalone EIP-1193 provider
-
-```javascript
-const ganache = require("ganache");
-
-const options = {};
-const provider = ganache.provider(options);
-const accounts = await provider.request({ method: "eth_accounts", params: [] });
-...
-```
-
-As a JSON-RPC web server and an EIP-1193 provider 
-
-```javascript
-const ganache = require("ganache");
-
-const options = {};
-const server = ganache.server(options);
-const PORT = 8545;
-server.listen(PORT, err => {
-  if (err) throw err;
-
-  console.log(`ganache listening on port ${PORT}...`);
-  const provider = server.provider;
-  const accounts = await provider.request({ method: "eth_accounts", params:[] });
-});
-...
-```
-
-As a Web3.js provider
-
-```javascript
-const Web3 = require("web3");
-const ganache = require("ganache");
-
-const web3 = new Web3(ganache.provider());
-...
-```
-
-As an Ethers.js provider
-
-```javascript
-const ganache = require("ganache");
-
-const provider = new ethers.providers.Web3Provider(ganache.provider());
-```
-
-### C. Using Ganache 7 in the browser.
-
-You can use Ganache 7 in the browser by adding the following script tag to your HTML code:
-
-```javascript
-<script src="https://cdn.jsdelivr.net/npm/ganache@7.0.0/dist/web/ganache.min.js"></script>
-```
-
-By doing that, Ganache 7 is automatically available in your browser for use:
-
-```javascript
-const options = {};
-const provider = Ganache.provider(options);
-```
-
-Again, see [here](https://github.com/trufflesuite/ganache#readme) for a list of available options you can pass in.
-
-## New Ganache 7 Features
-
-### 1. Zero-config mainnet forking
-
-Ganache supports mainnet forking out of the box without any configuration, allowing you to simulate having the same state as the Ethereum mainnet, but on your local machine. 
-
-This opens up many possibilities; for example, you can interact with a real-world protocol/contract locally during development, step through, and debug main net transactions locally (using [`truffle debug`](https://trufflesuite.com/docs/truffle/getting-started/using-the-truffle-debugger)), allowing visibility to details about your contract.
-
-[Here's](https://www.reddit.com/r/ethereum/comments/4yd1o4/testrpc_teaser_instantaneous_forking_coming_soon/) a 2016 demo of the Ganache team using the Mainnet forking feature to exploit the [DAO hack](https://www.gemini.com/cryptopedia/the-dao-hack-makerdao).
-
-To use this feature, start Ganache 7 using the `ganache --fork` command. Ganache uses [Infura](https://infura.io/docs) as its provider under the hood by default, but you can also specify a provider by passing a URL; for example, you can use your own Infura URL by running this command:
-
-```console
-$ ganache --fork.url wss://mainnet.infura.io/ws/v3/<PROJECT ID>
-```
-
-Ganache fetches five blocks back from the latest by default to avoid missing blocks due to reordering.
-
-This is a configurable behavior; you can either specify the exact block you want to fork from using `--fork.blockNumber <BLOCK NUMBER>` or by setting `--fork.preLatestConfirmations 0`.
-
-### 2. Fork any Ethereum test network without waiting for sync time
-
-In addition to being able to fork the Ethereum main network with zero configuration, Ganache also allows you to fork from any Ethereum test network, including Ropsten, Kovan, Rinkeby, and Görli. 
-
-You can do that by running the fork command with the network option: `ganache -- fork.network <NETWORK NAME>`. Cool, yeah? Here's what forking from the Rinkeby testnet looks like:
-
-![screenshot-2](/img/blog/introducing-ganache-7/example-2.png)
-
-### 3. Support for massive transaction traces (over 10GB+)
-
-Ganache supports massive transaction tracing using the `debug_traceTransaction` RPC method.
-
-To use this feature, start Ganache by forking off of Mainnet (or any test network) at a block number greater than that of the transaction you're trying to trace; for example, if you want to trace a transaction inside block 13,886,877, you will need to start Ganache at block number 13,886,878: 
-
-```console
-$ ganache --fork.network mainnet --fork.blockNumber <blockNumber>
-```
-
-Then send a curl request using the debug_traceTransaction method specifying the transaction hash like so: 
-
-```console
-$ curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "debug_traceTransaction", "params": [ "<TRANSACTION HASH>" ] }' http://localhost:8545
-```
-
-This would return the aggregated summary of this transaction for post-processing.
-
-Try it with a large transaction like `0x8bb8dc5c7c830bac85fa48acad2505e9300a91c3ff239c9517d0cae33b595090` (Warp Finance hack):
-
-First, start ganache (with lots of extra memory):
-```console
-$ NODE_OPTIONS=--max-old-space-size=16384 ganache --fork --fork.blockNumber 14037983
-```
-
-then execute `debug_traceTransaction` and send the output to trace.json: 
-```console
-$ curl -H 'Content-Type: application/json'   --data '{"jsonrpc":"2.0", "id": 1, "method": "debug_traceTransaction", "params": [ "0x8bb8dc5c7c830bac85fa48acad2505e9300a91c3ff239c9517d0cae33b595090" ] }' http://localhost:8545 -o trace.json
-```
-
-If you really want to test the limits of what's possible (and have a lot of time - about 1-2 hours) try out the 10GB+ Cream Finance hack transaction, `0x0fe2542079644e107cbf13690eb9c2c65963ccb79089ff96bfaf8dced2331c92`!
-
-### 4. Snapshot and Revert state
-
-In blockchain terms, a snapshot refers to the act of capturing and recording the state of a blockchain at a particular block number. A snapshot is the complete view of the blockchain in that specific block and includes all existing addresses and their associated data, including transactions, fees, balance, metadata, etc.
-
-In Ganache, you can take a snapshot of your development blockchain (or even a fork of Mainnet) using the `evm_snapshot` RPC method; it takes no parameters and returns an ID of the snapshot that it creates. 
-
-Ganache also supports reverting state to a previously taken snapshot using the `evm_revert` RPC method, although once a revert is invoked and succeeds, you can no longer use the snapshot with the corresponding ID as you can only revert a snapshot once. 
-
-You should consider creating a new snapshot after every evm_revert if you need to revert to the same point multiple times; here's a demo of taking a snapshot and reverting state in Ganache:
-
-```javascript
-const provider = ganache.provider();
-const [from, to] = await provider.send("eth_accounts");
-const startingBalance = BigInt(await provider.send("eth_getBalance", [from] ));
-
-// take a snapshot
-const snapshotId = await provider.send("evm_snapshot");
-
-// send value to another account (over-simplified example)
-await provider.send("eth_subscribe", ["newHeads"] );
-await provider.send("eth_sendTransaction", [{from, to, value: "0xffff"}] );
-await provider.once("message"); // Note: `await provider.once` is non-standard
-
-// ensure balance has updated
-const newBalance = await provider.send("eth_getBalance", [from] );
-assert(BigInt(newBalance) < startingBalance);
-
-// revert the snapshot
-const isReverted = await provider.send("evm_revert", [snapshotId] );
-assert(isReverted);
-
-// ensure balance has reverted
-const endingBalance = await provider.send("eth_getBalance", [from] );
-const isBalanceReverted = assert.strictEqual(BigInt(endingBalance), startingBalance);
-console.log({isBalanceReverted: isBalanceReverted});
-```
-
-### 5. Mine blocks instantly, at interval, or on demand
-
-Ganache allows you to configure how you want blocks to be mined during development; by default, blocks will be mined immediately upon receiving a transaction, but you can choose between the following options:
-
-- **At interval**: You can specify the time in seconds Ganache should wait before mining the next transaction by passing the `--miner.blockTime <TIME IN SECONDS>` option. A block time of 0 means Ganache should mine new transactions instantly.
-- **On demand**: Ganache also exposes an `evm_mine` RPC method which forces a single block to be mined whether mining is running or stopped. This will mine an empty block if no transaction exists in the mempool. See code sample below:
-
-```javascript
-console.log("start", await provider.send("eth_blockNumber"));
-await provider.send("evm_mine", [{blocks: 5}] ); // mines 5 blocks
-console.log("end", await provider.send("eth_blockNumber"));
-```
-
-### 6. Fast forward time
-
-Ganache exposes two RPC methods for manipulating time on your development blockchain. 
-
-A typical use case would be a smart contract that requires that a specific time passes before users can take certain actions; if the set time isn't something you want to wait for, you can use the `evm_increaseTime` to increase the blockchain current timestamp by the specified amount of time in seconds (passed in as hexadecimal).
-
-```
-curl -H 'Content-Type: application/json' --data' {"jsonrpc": "2.0", "id": 1, "method": "evm_increaseTime", "params": ["0x15180"] }' http://localhost:8545
-```
-
-This returns the total time adjusted in milliseconds. Furthermore, you can use the `evm_setTime` to set it to a specific timestamp; it accepts a JavaScript timestamp (Unix epoch) with millisecond precision and returns the number of seconds between the given timestamp and the current time. 
-
-```
-curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "evm_increaseTime", "params": ["0x15180"] }' http://localhost:8545
-```
-
-You should use this method cautiously as it allows you to move backwards in time, which may cause new blocks to appear to be mined before older blocks, thereby invalidating the blockchain state.
-
-### 7. Impersonate any account
-
-Ganache allows you to impersonate another account during development. This is more interesting when used with the fork feature; you can fork Mainnet and impersonate any account. 
-
-Here's an example of how you can fork Mainnet, impersonate an account, and send some tokens to another account. 
-
-- Start Ganache by forking Mainnet and impersonating (unlocking) a random account: 
-`ganache --fork --wallet.unlockedAccounts <Account Address Here>`
-- Get the balance of the unlocked account: 
-`curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "eth_getBalance", "params": ["<Account Address Here>"] }' http://localhost:8545`. This returns the balance in WEI encoded as a hex number.
-- Send some ether from the unlocked account to another account:
-`curl -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0", "id": 1, "method": "eth_sendTransaction", "params": [{"from": "UNLOCKED ACCOUNT", "to": "RECEIVING ACCOUNT", "value": "AMOUNT TO SEND"}] }' http://localhost:8545`
-
-Now verify that the unlocked account's balance has been reduced by the number of Ether sent out.
-
-Sending Ether to another account isn't the only use case as you can impersonate an account to call certain owner-only functions in a smart contract as we did in the convex benchmark contract we saw earlier.
-
-### 8. Pending transactions
-
-In Ethereum, every transaction has a nonce. The nonce is the number of transactions sent from a given address to date, and anytime you send a transaction, the nonce increases by 1. 
-
-For a transaction to be mined, it has to have a nonce greater than that of the previous transaction by 1. In earlier versions of Ganache, if you send a transaction with a nonce greater than the last nonce by more than 1, Ganache would error, and the transaction would be rejected.
-
-With Ganache 7, if the nonce of the previous transaction is 1, and you send a transaction with the nonce set to 3 for whatever reason, this transaction with nonce 3 will sit in the transaction pool until a transaction with nonce 2 is sent, at which time both transactions will be mined and added to the blockchain state.
-
----
-
-Start using Ganache 7 today by simply running `npm install ganache --global && ganache --help`, or view the [v7 Release Notes](https://github.com/trufflesuite/ganache/releases/tag/v7.0.0).
-
----
-
-This release has been years in the making and we're really proud of the work we've done. We hope you love it as much as we do.
-
-Thank you to everyone who has been a part of making this release happen — contributors, mentors, reviewers, issue reporters, and community participators have all been instrumental in making Ganache v7. We are immensely thankful to you all.
-
-<p align="center">💖 The Truffle Team</p>
diff --git a/src/blog/introducing-truffle-dashboard/index.md b/src/blog/introducing-truffle-dashboard/index.md
deleted file mode 100644
index 1e66e584e..000000000
--- a/src/blog/introducing-truffle-dashboard/index.md
+++ /dev/null
@@ -1,162 +0,0 @@
----
-title: Introducing Truffle Dashboard - Stop copy + pasting your private keys!
-hide:
-  - navigation
----
-
-![truffle dashboard - banner](//images.ctfassets.net/yfwlmanyz0dl/5NZQV67wUnXWjgNCxmCc9P/56d02491458a533e7eda3db250a33b6e/truffle-dashboard-private-keys.png)
-
-**By [Kingsley Arinze](https://twitter.com/heydamali)**
-
-## Don't get rekt 🙀
-
-One of our core missions at Truffle is to provide tooling that aids in the complete Web3 dapp development lifecycle, while maintaining rigorous security practices throughout. **As a smart contract developer, you require your development tools to keep your sensitive information secret and safe.** At Truffle, we're always looking for ways to make your experience more secure.
-
-If you’ve ever deployed a smart contract, chances are you’ve had to think twice about sharing your private keys with Truffle or other development tools. Maybe you've had to be vigilant not to accidentally share those keys on GitHub. To deploy to an Ethereum network, you've needed to copy your wallet credentials and store them in an insecure location to share with a tool like HDWalletProvider. **This has been necessary because your mnemonic or private key gives Truffle the permissions it needs to sign transactions on your behalf.**
-
-<figure markdown>![Screenshot of an example truffle-config.js using HDWalletProvider with hardcoded mnemonic and Infura key.](/img/blog/introducing-truffle-dashboard/secrets-oh-no.png)
-  <figcaption>Have you ever had to do something like this?</figcaption>
-</figure>
-
-**Storing your mnemonic seed phrase or private keys in regular files poses a considerable security concern.** Your seed phrase can easily be hijacked by JavaScript code, accidentally committed to Git, or targeted by bad actors.
-
-## Enter Truffle Dashboard 🔥 🚀
-
-Truffle Dashboard completely removes the need to manually interact with your wallet's mnemonic phrase or private keys throughout the development lifecycle.  **You can now safely deploy your smart contracts to your network of choice without Truffle ever needing to know what your keys look like.** Truffle seamlessly connects to your MetaMask wallet without any configuration, using the currently selected account and network for Truffle's deployment configuration.
-
-_But that's not all!_ For your convenience, **you can use Truffle Dashboard with any development tool.** For example, if you use Hardhat or Foundry to develop your smart contracts, you can also integrate with Truffle Dashboard for this improved security workflow. See the [Using Truffle Dashboard with other development tools](/docs/truffle/getting-started/using-the-truffle-dashboard) section of our docs to learn how.
-
-## How does Truffle Dashboard Work? ⚙️🔧
-
-If you're new to Truffle, ensure you have Node.js then install the latest version of Truffle with the following command:
-
-```console
-npm install -g truffle
-```
-
-If you already have Truffle installed, you want to first uninstall your existing instance of Truffle globally:
-
-```console
-npm uninstall -g truffle
-npm install -g truffle
-```
-
-### Running Truffle Dashboard 🚀
-
-With the latest version of Truffle, in addition to all previously existing `truffle <...>` commands, you will see a new `truffle dashboard` command.
-
-Running `truffle init` walks you through the process of setting up a new truffle project.
-
-Running `truffle dashboard` in a separate terminal window starts Truffle Dashboard at `http://localhost:24012` and automatically opens a new tab in your existing browser session.
-
-![truffle dashboard - start from the cli](/img/blog/introducing-truffle-dashboard/truffle-dashboard-cli.png)
-
-You can also configure the port and host to run Truffle Dashboard in one of two ways:
-
-  - On the command line:
-
-    ```console
-    truffle dashboard --port <Port of choice> --host <Host of choice>`
-    ```
-
-  - In your Truffle configuration (truffle-config.js) file:
-
-    ```javascript
-    module.exports = {
-      /* ... rest of truffle-config.js ... */
-
-      dashboard: {
-        port: 25012,
-        host: "localhost"
-      }
-    }
-    ```
-
-See the [Truffle Commands](/docs/truffle/reference/truffle-commands.html) and/or the [Configuration](/docs/truffle/reference/configuration.html) reference documentation to learn more.
-
-### Connecting your wallet 🤝
-
-Truffle Dashboard requires you to connect your wallet to get started. Click the "Connect Wallet" button and connect Truffle Dashboard to your wallet the same way you would for any other dapp.
-
-![truffle dashboard - connect wallet](/img/blog/introducing-truffle-dashboard/truffle-dashboard-connect-wallet.png)
-
-Next, Truffle Dashboard prompts you to confirm that you are connected to the correct network, since it uses the wallet's default active network. Make sure you switch to the desired network before confirming. Every transaction you process will be sent to the confirmed network.
-
-![truffle dashboard - confirm](/img/blog/introducing-truffle-dashboard/truffle-dashboard-confirm.png)
-
-During development, a typical workflow is first to deploy and test out your smart contract code on a development blockchain like [Ganache](https://trufflesuite.com/ganache) before deploying to your favorite test network.
-
-You can still maintain this workflow with Truffle Dashboard by simply importing Ganache’s local blockchain network into your MetaMask wallet as usual and pointing Truffle Dashboard to use it as your confirmed network.
-
-![truffle dashboard - select network](/img/blog/introducing-truffle-dashboard/truffle-dashboard-select-network.png)
-
-### Using Truffle Dashboard in your Truffle project 🎉
-
-Before Truffle Dashboard was available, if you wanted to connect to a network like Rinkeby or Mainnet from your Truffle project, you had to specify some configuration variables in the network section of the truffle-config.js file.
-
-```javascript
-module.exports = {
-  /* ... rest of truffle-config.js ... */
-
-  networks: {
-    development: {
-      host: "localhost",
-      port: 8545,
-      network_id: "*"
-    },
-
-    ropsten: {
-      // ...
-    },
-
-    mainnet: {
-      // ...
-    }
-  }
-};
-```
-
-With Truffle Dashboard, you do not need any of that, as Truffle now exposes a built-in network named `"dashboard"` which runs on whatever port and host your Truffle Dashboard is running on (`http://localhost:24012` by default). With Truffle Dashboard running and connected to MetaMask, you can simply supply the `dashboard` keyword to any Truffle command that requires you to specify a network. For example:
-
-```console
-truffle migrate --network dashboard
-truffle console --network dashboard
-```
-
-When you run the above commands (or any RPC request), Truffle forwards your request from the command-line to the browser, where you can inspect it and choose to process or reject with MetaMask.
-
-![truffle dashboard - process transaction](/img/blog/introducing-truffle-dashboard/truffle-dashboard-sign.png)
-
-As with every zero-configuration feature, you are allowed to override the default configuration by adding a network called `dashboard` to your Truffle configuration file and specifying its options as you would for other networks. See the [`networks` configuration](/docs/truffle/reference/configuration.html#networks) reference documentation for more information.
-
-### Using Truffle Dashboard with other development tools 👪
-
-Although we developed Truffle Dashboard intending to improve the development experience for those who choose to build with Truffle, we made sure to make it tool-agnostic. So if Truffle isn't your development tool of choice for developing smart contracts (why on earth should it not be? C'mon, now let's talk!), but you'd like to integrate the Dashboard into your workflow, we've got you covered.
-
-You can use Truffle Dashboard with other development tools. For example, use it with Hardhat by simply starting Truffle Dashboard in a separate terminal window and add a network configuration option that points to Truffle Dashboard's RPC URL in your Hardhat config file:
-
-```js
-module.exports = {
-  // ...
-
-  networks: {
-    // ...
-
-    "truffle-dashboard": {
-      url: "http://localhost:24012/rpc"
-    }
-  },
-};
-```
-
-With this setup, when you run the command `hardhat deploy --network truffle-dashboard`, the request is forwarded to Truffle Dashboard, where you can inspect and process them.
-
-## Conclusion ❤️️
-
-**With Truffle Dashboard, you no longer have to worry about giving your private keys to someone else's JavaScript code.** You can now relax and leave it up to MetaMask to keep your private keys safe and sign transactions on your behalf.
-
-To get started, download the latest version of Truffle and start using Truffle Dashboard today by running the command `npm uninstall -g truffle && npm install -g truffle`.  Please refer to the [Truffle Dashboard](/docs/truffle/getting-started/using-the-truffle-dashboard.html) feature documentation for more.
-
-Truffle Dashboard was borne out of our years of experience working on developer tools for the Ethereum ecosystem and receiving valuable feedback from our users. We are extremely excited to release this feature. We hope you're excited to try it out.
-
-With ❤️️ from the Truffle team. Questions/comments/concerns? Please shoot us a tweet [@trufflesuite](https://twitter.com/trufflesuite)!
diff --git a/src/blog/introducing-truffle-db-part-1/index.md b/src/blog/introducing-truffle-db-part-1/index.md
deleted file mode 100644
index 5f51819bb..000000000
--- a/src/blog/introducing-truffle-db-part-1/index.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Introducing Truffle DB, Part 1 - Artifact archeology
-hide:
-  - navigation
----
-
-## Introducing Truffle DB, part 1: Artifact archeology
-Truffle is not a small utility: it compiles your contracts, deploys them to multiple networks, runs your automated tests, provides an interactive debugger for when things go wrong, offers a library for interacting with your contracts on the frontend, … (*the list goes on.*) With just over 20,000 lines of code and close to thirty discrete software packages, Truffle has a lot going on.
-
-Truffle is “not small” on purpose. The tool oversees the development lifecycle in human developer terms. It keeps track of familiar concepts and hides unnecessary, low-level specifics. That’s a big goal.
-
-So how does this work? Well, Truffle tries to be smart about it. It stores information about your contracts so that it can refer to it later. It tracks compilation results alongside the source code you wrote, maintaining a steady mapping between *data for the blockchain* and *data for developers’ brains*.
-
-Right now, this system of record-keeping is served through Truffle’s **contract artifacts**: the large JSON files that get saved in your *build/contracts/* directory. Truffle saves your artifacts when you compile and updates your artifacts with address information when you migrate. Pretty much whenever you use any part of Truffle, these artifacts are read from disk and processed, enabling Truffle to paint itself (and you) a picture of what’s happening in human terms.
-
-Truffle’s artifacts have been enormously useful: the tool simply couldn’t exist without this kind of first-class data capturing. Beyond that, though, being able to count on this data has enabled an ecosystem of other tools and utilities that build on top of Truffle’s functionality using Truffle’s artifacts format. Truffle’s artifacts have served as a common language for representing smart contract development concepts.
-
-Unfortunately, Truffle’s artifacts format has a number of core limitations that prevent Truffle from offering ideal behavior in several key situations. This post describes a few of these limitations. In this post’s follow-up, we’ll share information about a new system to manage this record-keeping, which we’re calling **Truffle DB**.
-
-## So what’s the problem now?
-For starters: artifact files are huge! Too huge! In addition to Truffle reading your contract artifacts, your dapp’s frontend code may read and use your artifacts to let users connect to any deployed network, etc. Problem is—there’s a ton of JSON. It’s a mess, and it’s in your face too much.
-
-<figure>
-  <img src="/img/blog/introducing-truffle-db/example-truffle-db.png" alt="Example of Truffle DB" style="width:100%">
-  <figcaption>**For example:** Truffle stores the same abstract syntax tree* (AST) in two different formats, in every single artifact! Most applications do not need this.
-
-  *for the curious: the AST is the reason your code works whether you wrote it all on a single line or not. Source gets parsed, and the AST is the result. Truffle and other tools rely on the AST for things like debugging, code coverage, and linting.</figcaption>
-</figure>
-
-By the byte, almost all of the information in each contract artifact is for internal use or for some specific purpose. **Only a small subset of the data in each artifact is necessary for your frontend or for you to think about directly.** Thus far, users who have struggled with these large files needed to use a tool like [jq](https://stedolan.github.io/jq/) or write a custom solution.
-
-In addition to these files being too large, the information is grouped purely by the idea of “contract name”. What if you want to have two contracts with the same name? You can’t. What if you want to debug an old version of your contract, deployed to a testnet? I hope you backed up your old artifacts directory somehow.
-
-Although we’ve implemented plenty of workarounds to deal with these limitations, the problems do not go unnoticed. See some long-outstanding open GitHub issues, for example:
-* [Truffle contract artifacts are too big and contain too much sensitive detail to actually deploy on the web (#1269)](https://github.com/trufflesuite/truffle/issues/1269)
-* [Artifact is overwritten if there are two contracts with the same name (#1087)](https://github.com/trufflesuite/truffle/issues/1087)
-* [Source map indexes are missing in artifacts (#1236)](https://github.com/trufflesuite/truffle/issues/1236)
-* [Allow persistency of artifacts remotely (#1790)](https://github.com/trufflesuite/truffle/issues/1790)
-
-Unfortunately, these issues are blocked by the fundamental design of the contract artifacts.
-
-The root of the problem is that Truffle’s artifacts try to serve two conflicting purposes: they try to serve the developer, but they also try to serve the tool itself.
-
-## “Stop talking about data formats”, you say.
-
-Right? Ideally, Truffle should silently keep complete records of everything you will ever need, and nothing more. And you, the developer, should only ever come face-to-face with the information you need at any given moment.
-
-So, for some time, we have been working on a plan to improve the state of affairs of Truffle’s record-keeping.
-
-We’ll get into it more in the next post, but Truffle DB aims to provide two things:
-* a data model: a set of terms that collectively represent various, high-level concepts associated with smart contract development
-* a flexible interface: a way to query and update your Truffle project’s records
-
-In doing this, we’re taking a data-first approach, organizing your project’s information through immutable records and a clean separation of concerns. Stay tuned for the next post, where we’ll talk about this more and outline our release plan for Truffle DB: what we’ll be releasing first, what work still needs to be done, and how we plan to handle backwards compatibility over time.
diff --git a/src/blog/introducing-truffle-db-part-2/index.md b/src/blog/introducing-truffle-db-part-2/index.md
deleted file mode 100644
index c5d738bb6..000000000
--- a/src/blog/introducing-truffle-db-part-2/index.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Introducing Truffle DB, part 2 - 'Weight and Switch'
-hide:
-  - navigation
----
-
-Welcome back! If you missed the [first part](/blog/introducing-truffle-db-part-1) of this post, you may want to read it to learn more about Truffle’s contract artifacts, their current limitations, and why we seek to build a better solution.
-
-Or, just to catch up:
-* Truffle currently stores information about your smart contracts in files that we call “contract artifacts” (or just “artifacts” for short.)
-* Truffle uses these artifacts for pretty much everything.
-* Plenty of other tools use artifacts too, and rely on their behavior.
-* Unfortunately, the artifacts file format has several design flaws, forcing dozens of workarounds and even preventing certain use cases entirely.
-* Addressing these flaws head-on risks severe negative impact on other projects.
-* We’re excited to share a project we’ve been working on, to offer a deprecation plan and to encourage community involvement.
-
-So why should you care?
-* If you are a tools developer, or rely on Truffle artifacts directly in any way: there will be breaking changes!
-* If you use Truffle for smart contract development: the developer experience using Truffle will have fewer roadblocks (“[software warts](https://www.catb.org/jargon/html/W/wart.html)”). This will not break existing Truffle projects.
-* No matter who you are: better data means better tools.
-
-Great! I’m convinced. 😁 Now, where were we?
-
-## What is Truffle DB?
-
-Truffle DB comprises two key ideas, currently at different stages of development. These are:
-
-1. A data model for organizing your project’s smart contracts: how to keep track of all the different pieces of information, from your contract source files to where they are deployed.
-1. A flexible JSON data access interface: how to read exactly the data you need and how to update the DB with the data you have.
-
-### Data model
-
-<figure>
-  <img src="/img/blog/introducing-truffle-db/truffle-db-data-model.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>**Data model excerpt**: how contracts, sources, compilers, and compilations all relate. ([Text-accessible version](https://github.com/trufflesuite/artifact-updates/blob/master/docs/uml/macros.iuml) available via diagram source)</figcaption>
-</figure>
-
-What is a smart contract? What is your contract’s bytecode, what is its source code, and how do they relate? By looking at how Truffle expects these relationships in practice, and considering how these concepts are commonly understood, we hope to make life easy by creating a shared vocabulary for interacting with the smart contract domain.
-
-Diagrams are worth more than words here, so please check out our data model docs to get a broader sense for what this represents.
-
-**Current status**: Implemented as minimally viable, designed to be extended.
-
-### Flexible interface
-
-<figure>
-  <img src="/img/blog/introducing-truffle-db/concept-query.png" alt="Example of Truffle DB" style="width:100%">
-  <figcaption>**Concept image**: Example query to fetch specific project contract info. ([See gist for image text](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-concept-query-graphql))</figcaption>
-</figure>
-
-Truffle DB uses [GraphQL](https://graphql.org) for its primary interface. GraphQL affords flexibility and a data-first design methodology that suits our goals well. This interface is intended for use in tools to build on top of Truffle; as a normal user you won’t have to touch this. (Of course, we hope this will encourage you to find new ways to solve problems by building and sharing tools of your own!)
-
-Truffle DB is still in development, but we would like to share what we’ve got so far and to talk about where we’re looking to go. Although it’s early, we want to increase awareness about future breaking changes, and we hope to paint a picture of some new foundations that we’re excited will help the smart contract development tools ecosystem.
-
-**Current status**: Internal infrastructure in place, prototyping for public review to begin soon.
-
-## What we’re releasing first
-
-We’re gearing up for a minor release (Truffle v5.1), and we plan to make a first version of Truffle DB available as an experimental implementation. This means building blocks to start: key pieces of infrastructure to paint a picture of Truffle DB for review and iteration.
-
-Day 1, this means you will get:
-* The ability to convert your artifacts and load them into Truffle DB
-* A mechanism to persist Truffle DB data side-by-side with your artifacts
-* Improvements to Truffle that take advantage of this data when it exists
-* A bundled GraphQL playground for hands-on exploration
-* The ability to easily explore the schema to better understand our system design
-
-<figure>
-  <img src="/img/blog/introducing-truffle-db/graphql-playground.png" alt="Example of Truffle DB" style="width:100%">
-  <figcaption>**Interact with Truffle DB**: Apollo’s [GraphQL Playground](https://www.apollographql.com/docs/apollo-server/features/graphql-playground/) provides a handy way to work with GraphQL interfaces. We’re bundling a Playground instance into Truffle DB to make it easier to learn about.
-(For text-accessible version, see [query source](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-graphql), [query variables](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-result-json), and the [query result](https://gist.github.com/gnidan/c653c57a69adf50f5d60b7d0c1d3c6a2#file-playground-query-result-json))</figcaption>
-</figure>
-
-## What’s left to be done (soon)
-
-Since we’ve started by building infrastructure, the work remains to connect the dots into a final design that we can validate for quality and usefulness.
-
-This includes:
-* Documentation, of course! See our current [Truffle DB – Proposal](https://trufflesuite.github.io/artifact-updates/index.html) working docs, which include the data model diagrams. Expect us to convert these docs into proper documentation for release.
-* Better persistence. Our initial implementation will save JSON files to disk, but we intend to support more robust data storage options, including relational databases and native support in [Truffle Teams](/docs/teams/overview).
-* Schema design updates, including support for pagination and proper data filtering.
-* A prototype candidate for Truffle DB’s external interface.
-
-## The long-term plan
-
-We’re going to introduce Truffle DB gradually, deprecating the old artifacts format and introducing Truffle DB more and more as it’s validated.
-
-We expect to follow these steps:
-1. Release initial Truffle DB features as opt-in and experimental.
-1. Gather feedback and support to build a cohesive Truffle DB release candidate (for broad community use).
-1. Turn Truffle DB on by default, but continue to use artifacts as the primary data store.
-1. Convert the rest of Truffle to use Truffle DB as its primary data store, but continue to maintain artifacts alongside it for compatibility.
-1. Continue to maintain both data stores, and switch to using Truffle DB to manage artifacts (instead of existing artifacts management code).
-1. Turn off artifacts by default, but maintain legacy support through configuration.
-1. Eventually, remove artifacts altogether.
-
-We expect this process, start to finish, to span at least two major (breaking change) releases. We plan to maintain legacy support for artifacts for at least 18 months after we release a Truffle DB release candidate.
-
-<figure>
-  <div style="width:100%;height:0;padding-bottom:43%;position:relative;"><iframe src="https://giphy.com/embed/26tPcRGbvMEcKmrRe" width="100%" height="100%" style="position:absolute" frameBorder="0" class="giphy-embed" allowFullScreen></iframe></div><p><a href="https://giphy.com/gifs/film-cinemagraph-26tPcRGbvMEcKmrRe">via GIPHY</a></p>
-  <figcaption>[Weight and Switch](https://tvtropes.org/pmwiki/pmwiki.php/Main/WeightAndSwitch): Dr. Jones demonstrating proper technique for delicate data migration procedures</figcaption>
-</figure>
-
-## What do you think?
-
-Please reach out with questions/thoughts/use case ideas/implementation strategies, or even just to say hello. Your feedback will help us provide the most value and make sure we do so with enough clarity!
-
-We’re tracking overall progress in this [GitHub issue (trufflesuite/truffle#1718)](https://github.com/trufflesuite/truffle/issues/1718). Expect to see this filled out more in the coming weeks, so please follow along there if you’re interested.
-
-Thanks for reading! Hope to see you at TruffleCon!
diff --git a/src/blog/iterate-faster-with-truffle-teams/index.md b/src/blog/iterate-faster-with-truffle-teams/index.md
deleted file mode 100644
index 800f61d5e..000000000
--- a/src/blog/iterate-faster-with-truffle-teams/index.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Iterate Faster with Truffle Teams
-hide:
-  - navigation
----
-
-Consider the amount of context switching required to develop a dapp: you’re writing Solidity one minute, writing tests another, debugging those results--it’s easy to get lost! These switches carry a cognitive load and when errors equal a loss of ETH we need all the help we can get. I’m happy to inform you Truffle Teams can help reduce context switching and help you or your team iterate faster.
-
-Truffle Teams has reached a very important stage in its life: it now provides a complete workflow including building, testing, managing, monitoring, and debugging. This means you’re getting a huge boost in productivity. This amounts to a more robust workflow for you and/or your team and contributes to the application lifecycle generally by tightening the feedback loop between deployment, operation, and debugging all within a flexible development network.
-
-<figure>
-  <img class="mb-4 w-100" src="/img/blog/iterate-faster-with-truffle-teams/dev-lifecycle.png" alt="The development lifecycle: plan, code, build, test, release, deploy, operate, and monitor.">
-  <figcaption class="text-center font-italic">The development lifecycle.</figcaption>
-</figure>
-
-Up to this point, Truffle Teams has already offered a builds system, deployment manager, blockchain sandboxes, and monitoring. Recently we released a visual debugger into early access. With that, we’d like to highlight two features that completed this cycle: the Debugger and the Contract Manager.
-
-For a great video example, check out our demo from TruffleCon 2020. We briefly touch all the phases talked about above using a rock, paper, scissors game. For something more long-form, check out our 5-part webinar series walking you through using the Truffle suite to create an NFT and trade it on a decentralized marketplace.
-
-<figure>
-  <a href="https://www.youtube.com/watch?v=LsQ2Iwd5VMc" target="_blank">
-    <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/teams-demo-tcon-2020.jpg" alt="The video thumbnail for Josh Quintal and Mike Seeses demo of Truffle Teams at TruffleCon 2020.">
-    <figcaption class="text-center font-italic">Mike Seese and Josh Quintal go over the entire development lifecycle using Truffle Teams for a decentralized rock, paper, scissors dapp.</figcaption>
-  </a>
-</figure>
-
-## Debugger Enhancements
-
-<p class="alert alert-info">
-  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the debugger right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
-</p>
-
-Truffle offers a sophisticated forensic transaction debugger and allows you to extract the most information and context possible from your transactions. We released a graphical version of our command line debugger into Truffle Teams Early Access in December. Since then we’ve added syntax highlighting and breakpoints for an improved developer experience. Readability increases and you control where execution stops, providing a precision debugging experience. Check out the Truffle Teams debugger docs to learn more about breakpoints. Currently the debugger in Truffle Teams only works for sandbox environments, but we plan on supporting public networks next!
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/debugger.png" alt="The Truffle Teams debugger working on an NFT-based badge contract">
-  <figcaption class="text-center font-italic">The Truffle Teams Debugger--now with syntax highlighting and breakpoints!</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-## The Contract Manager
-
-<p class="alert alert-info">
-  <i class="fas fa-info-circle"></i> <strong>Note</strong>: To use the contract manager right away, you'll need to opt-in to <a href="/blog/try-new-features-first-with-truffle-teams-early-access">Truffle Teams Early Access</a>.
-</p>
-
-Truffle Teams’ Contract Manager generates a UI for interacting with all the functions of your smart contracts, as well as a live state tree so you can quickly see the changes propagated by those functions. If you’re familiar with Remix, you’ll feel right at home here.
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 w-md-70 figure-shadow" src="/img/blog/iterate-faster-with-truffle-teams/contract-manager.png" alt="The Truffle Teams Contract Manager using an NFT-based badge contract">
-  <figcaption class="text-center font-italic">The Contract Manager; shown here using an NFT badge.</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-The Contract Manager is great for quick demos, integration tests, and a faster, all-GUI debugging workflow. For example, you can deploy to a sandbox via the deployment wizard, hop over to the contract manager to fire off a few transactions, and finally debug these transactions from the monitoring screen.
-
-## Dapp Topography
-
-Going forward, we’ll be helping you understand your dapp on an even deeper level, offering forensic-level analysis of your transactions. Not only that, but it will be able to diagram contract interaction to allow different stakeholders to participate in the debugging process. For example a product manager, or other domain expert can participate in the forensic analysis. These diagrams and other assets can be shareable media that can fit into existing communication channels.
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 w-md-70" src="/img/blog/iterate-faster-with-truffle-teams/ens-plant-uml.png" alt="Plant UML diagram of an ENS transaction">
-  <figcaption class="text-center font-italic">A test in which a user who isn't the owner of an ENS name attempt to change the resolver. Note the "X" shoing the revert.</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-## Get Started with Truffle Teams
-
-We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Check out Truffle Teams today and let us know what you think about the new deployment views and contract manager, or if your team has other needs we haven’t met yet.
-
-<div class="mt-3 mb-4 text-center">
-  <a class="btn btn-truffle" href="https://my.truffleteams.com">SIGN UP FOR THE TRUFFLE TEAMS</a>
-  <a class="btn btn-truffle" href="/docs/teams/quickstart">TRUFFLE TEAMS QUICKSTART</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md b/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
deleted file mode 100644
index 047487be5..000000000
--- a/src/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/index.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Learn Ethereum The Fun Way with our Pet Shop Tutorial
-hide:
-  - navigation
----
-
-Here at Truffle we want to make Ethereum development accessible to developers of all stripes. To that end, today we're releasing a new tutorial called [Pet Shop](/tutorial). It covers the entire local development process, start to finish. For added fun, we've tied the whole thing together within the narrative of creating a pet adoption dapp for a local pet shop owner.
-
-Here's a preview of what's covered:
-
-* Setting up The Development Environment
-* Creating a Truffle Project using a Truffle Box
-* Writing and Testing a Smart Contract
-* Creating a UI to Interact with our Smart Contract
-
-By then end of the tutorial you'll have a shiny new dapp with which you can reserve pets for adoption.
-
-![The Completed Pet Shop Dapp](/img/blog/learn-ethereum-the-fun-way-with-our-pet-shop-tutorial/pet-shop-preview.jpeg "The completed dapp.")
-
-In the future we'll be building on this tutorial with others such as deploying to live testnets and additional, more advanced functionality. We hope you enjoy and thank everyone for your support!
-
-Got stuck? The fastest way to get help is from our [community Gitter channel](https://github.com/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions.
-
-Love it? Send us your feedback on [Twitter](https://twitter.com/trufflesuite).
-
-Found a problem? Let us know by raise a [GitHub issue](https://github.com/trufflesuite/trufflesuite.com/issues) if there's something you think we can improve! Pull requests are always welcome!
-
-Cheers!
-
--- Josh & the Truffle Team
diff --git a/src/blog/one-hundred-documentation-pull-requests/index.md b/src/blog/one-hundred-documentation-pull-requests/index.md
deleted file mode 100644
index 347a0cbdb..000000000
--- a/src/blog/one-hundred-documentation-pull-requests/index.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: One hundred documentation pull requests? Yes please.
-hide:
-  - navigation
----
-
-Greetings! The Truffle team has been growing over the course of the last year. From a single developer, we are now a team of five (soon to be even more), which means that we can spread the work around.
-
-As a new full-time member of the team, I've first taken to looking at our existing materials to ensure that everything is up-to-date and working well.
-
-For example, our website, a public GitHub repository, had been receiving pull requests (PRs) for the better part of a year, and they had been languishing for want of someone to go through them.
-
-We're not talking a few or even a dozen. We're talking **almost 100 PRs**.
-
-All I can say is: **wow**.
-
-I've been working in the open source software world for about a decade, and I've never seen so many people freely offering suggestions to documentation. As we all ruefully know, documentation can be first to go out of date and last to be updated, so knowing that our community is keeping such an eagle eye on even minute details says a lot.
-
-And I do mean *minute details*. When one of our tutorials wrote "tag a stab" instead of "take a stab", not less than [ten of you took the time to submit pull requests](https://github.com/trufflesuite/trufflesuite.github.io/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aclosed%20tag%20take) telling us so.
-
-</div><div class="text-center container">
-  ![Take a stab, indeed](/img/blog/one-hundred-documentation-pull-requests/take-a-stab.png)
-  <p class="caption">Take a stab indeed</p></br></br>
-</div><div class="container container-narrow">
-
-Make no mistake: this is good thing. I believe in the [Broken Windows theory](https://en.wikipedia.org/wiki/Broken_windows_theory) as it applies to documentation. **We want to fix up the small things now so we can maintain the larger things more easily in the future.**
-
-We have big plans for our content here, just like we have big plans for Truffle. (Check out the new features coming in Truffle 4 (<https://github.com/trufflesuite/truffle/releases/tag/v4.0.0-beta.0>)!) And note that [we have since separated out the website source code to its own repository](https://github.com/trufflesuite/trufflesuite.com) to make submissions easier for the community.
-
-I'm happy to be part of a community that cares about what we're doing, reducing the bar to developing Ethereum dapps, and making them delicious.
-
-As for your suggestions on how we can serve you even better? Please keep them coming. Submit a pull request to our documentation, reach out on [Twitter](https://twitter.com/trufflesuite), or let us know if there's something we can improve by raising a [GitHub issue](https://github.com/trufflesuite/trufflesuite.com/issues).
-
-Need help with something? Reach out on our [community Gitter channel](https://github.com/ConsenSys/truffle), where hundreds of your fellow Trufflers congregate to answer your questions. 
-
--- Mike & the Truffle team
-
------
-
-*Mike Pumphrey is an Enterprise Trainer at ConsenSys working on the Truffle team. With over a dozen years of experience in documentation, support, and training, Mike is passionate about making technical concepts understandable to a wider audience. He believes that great software can only be great when people know how to use it, and is excited to be bringing clarity to a field as exciting and new as blockchain.*
diff --git a/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md b/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
deleted file mode 100644
index 9f271eacd..000000000
--- a/src/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions/index.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Open call for contributions by Truffle + PegaSys - EEA private transactions
-hide:
-  - navigation
----
-
-# Open call for contributions by Truffle + PegaSys: EEA private transactions
-![Pegasys Truffle Open Call For Contributions](https://i.imgur.com/GLw8iok.jpg)
-
-## What's missing?
-
-In its current state, Truffle doesn't support EEA private transactions. Support for the web3js-eea library is needed for this to work and PegaSys has recently made an implementation of the v4.0 EEA specification.
-
-## Why did this happen?
-
-The `interface-adapter` in Truffle’s codebase doesn’t provide an adapter for the  EEA 4.0 client spec, therefore private transactions aren’t working.
-
-The EEA client specification is a developing specification and  Truffle has not yet implemented the EEA client specification around private transactions.  PegaSys is providing an implementation of the specification for private transactions.  Pegasys and Truffle are teaming up to ensure that Truffle supports the EEA JSON RPC API methods.
-
-## What's the solution?
-PegaSys and Truffle have teamed up to make a single open call for contributions. This guest blog post is made by the PegaSys team and is to be posted on the Truffle blog and promoted by both teams in order to add code to Truffle codebase to add support for them.
-
-The solution involves using a Delegation pattern to help make that work.
-
-The location of the files to be modified can be found here:
-[truffle/packages/interface-adapter/lib](https://github.com/trufflesuite/truffle/tree/develop/packages/interface-adapter/lib)
-
-In short, when Truffle receives a transaction, it should determine if its a `privateFor` transaction. If so, it would delegate the rest of the business logic to the EEA library. If not, it should just continue processing the transaction with the original web3 methods.
-
-Also, it would be very useful to make sure this plays nicely with the getTransactionReceipt methods later in the chain of events.
-
-## What to do Exactly?
-
-The initial process involves adding an EEA definition to the shim file. The `web3-shim.ts` file currently contains the overloads for the different interface definitions and their mappings.
-
-``` typescript
-import { EthereumDefinition } from "./ethereum-overloads";
-import { QuorumDefinition } from "./quorum-overloads";
-import { FabricEvmDefinition } from "./fabric-evm-overloads";
-
-const initInterface = async(web3Shim: Web3Shim) => {
-
-    const networkTypes: NetworkTypesConfig = new Map(Object.entries({
-      "ethereum": EthereumDefinition,
-      "quorum": QuorumDefinition,
-      "fabric-evm": FabricEvmDefinition
-    }));
-
-    networkTypes.get(web3Shim.networkType).initNetworkType(web3Shim);
-  }
-```
-
-The initial import and mapping has been done [in this fork](https://github.com/faraggi/truffle).
-
-``` typescript
-import { EthereumDefinition } from "./ethereum-overloads";
-import { EEADefinition } from "./EEA-overloads";
-import { QuorumDefinition } from "./quorum-overloads";
-import { FabricEvmDefinition } from "./fabric-evm-overloads";
-
-const initInterface = async(web3Shim: Web3Shim) => {
-
-    const networkTypes: NetworkTypesConfig = new Map(Object.entries({
-      "ethereum": EthereumDefinition,
-      "EEA": EEADefinition,
-      "quorum": QuorumDefinition,
-      "fabric-evm": FabricEvmDefinition
-    }));
-
-    networkTypes.get(web3Shim.networkType).initNetworkType(web3Shim);
-  }
-```
-
-The [rest of the owl](https://i.imgur.com/4fVoQoQ.png) is to add the needed logic in the `eea-overloads.ts` file and the `overrides` variable for it to interact with the [web3eeajs library](https://www.npmjs.com/package/web3-eea).
-
-![PegaSys owl](https://i.imgur.com/4fVoQoQ.png)
-
-## Who can do this?
-
-Anyone who'd like to try can very much do so we will gladly support any developer who wants to help out.
-But here are some recommended prerequisites:
-
-The Truffle codebase is mainly written in `javascript`, and this particular interface-adapter library we'll be looking at is written in `typescript`.
-So knowing some javascript is a must.
-
-It will definitely help if you've had some exposure and usage of the Truffle library. Nothing fancy, just using it for compiling and deploying contracts for example.
-Likewise, having some previous knowledge of the web3js library is going to prove quite helpful.
-
-All of the above somewhat describes a general dapp developer- so in other words; if you've already written a dapp before using Truffle, this contribution could be done by you.
-
-So what's in it for you?
-Two things:
-- You'll receive some 😎 PegaSys Swag!
-- We'll personally thank and credit you on stage at [Trufflecon at my Permissioning  Talk](https://twitter.com/trufflesuite/status/1150929297647034374)
-
-For more information or help on this contribution, contact [Felipe](mailto:felipe.faraggi@consensys.net) from [PegaSys](https://pegasys.tech),  or write us on [our gitter channel](https://gitter.im/PegaSysEng/pantheon).
diff --git a/src/blog/removing-installation-issues-continued-testrpc/index.md b/src/blog/removing-installation-issues-continued-testrpc/index.md
deleted file mode 100644
index 52429e4a9..000000000
--- a/src/blog/removing-installation-issues-continued-testrpc/index.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Removing installation issues, con't - TestRPC
-hide:
-  - navigation
----
-
-<p class="alert alert-info">
-**Update**: Since this blog post was published, we have released [Ganache](/ganache) a personal blockchain and a replacement to the TestRPC. We have left this post unaltered, but we highly recommend checking out our [Ganache Quickstart](/docs/ganache/quickstart) page.
-</p>
-
-If you've been following along, you'll know that we recently [removed most if not all installation issues from Truffle](/blog/how-were-making-installation-issues-a-thing-of-the-past). For us it was a pretty big deal: Installation issues were, by far, the number one issue plaguing new users on any platform. We thought our solution was novel, so we blogged about it, and the biggest reaction we received from users was, "This is awesome, thank you! But can you do it for the TestRPC too?" Well you asked, and today we delivered.
-
-The [TestRPC](https://github.com/ethereumjs/testrpc) has always been the sister application to Truffle, and for good reason. The TestRPC gives users a personal blockchain with which to develop, drastically lowering the barrier to entry of Ethereum development and removing the need for mining or dealing with real Ether. Developing on the TestRPC is an integral part of every Ethereum project, and it's usually the first blockchain deployed to in a professional Ethereum developer's workflow. We'll be blogging about the ideal Truffle workflow a bit later, but instead of waiting, you can just let [Chris Hitchcott from Digix Global show you how it's done](https://youtu.be/SFW6W-DIdIo?t=1079). (Thank you Chris, this was a great presentation.)
-
-Fixing installation issues on the TestRPC required the [very same solution](/blog/how-were-making-installation-issues-a-thing-of-the-past) as fixing them on Truffle, so we won't go into detail here. However, I will say the solution worked _even better for the TestRPC_ than it did for Truffle. This is because the bundle we were able to create didn't require any external dependencies, making the package that you install just a single download. When compared to the old installation, the experience is night and day.
-
-## Getting the new version
-
-Like Truffle, we need you to put this version through its paces before we can release it as an official version, so we've **released it in beta**.
-
-To get the beta version, first uninstall the version of the TestRPC you currently have (because they'll conflict):
-
-```shell
-$ npm uninstall -g ethereumjs-testrpc
-```
-
-And now install the beta version:
-
-```shell
-$ npm install -g ethereumjs-testrpc@beta
-```
-
-(If you're on a Unix-based system, you may have to prefix the above commands with `sudo`.)
-
-You'll notice that the beta version installs instantly, quicker than you can say, "Holy crap, this is awesome."
-
-## So what's next?
-
-We have a lot of things planned for the TestRPC. We're not ready to officially announce everything just yet, but know that solving these installation issues is a stepping stone to providing you the best Ethereum development experience possible. Like creamy ganache filling is to a chocolate truffle, so is the TestRPC to the core of your workflow. So stay tuned. It's gonna be sweet.
-
--- Tim & the Truffle Team
diff --git a/src/blog/sandbox-forking-with-truffle-teams/index.md b/src/blog/sandbox-forking-with-truffle-teams/index.md
deleted file mode 100644
index 7f5709e8b..000000000
--- a/src/blog/sandbox-forking-with-truffle-teams/index.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Simulate Live Networks with Forked Sandboxes
-hide:
-  - navigation
----
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/sandbox-forking-with-truffle-teams/sandbox-forking-blog.png" alt="Sandbox Forking" style="width:100%">
-</figure>
-
-Sandboxes in Truffle Teams are the easiest way to setup a shared Ganache instance for the entire team. They integrate seamlessly with our deployments manager, and work locally as expected too: insert the mnemonic and RPC URL into your Truffle config or browser wallet and starting sending ether, deploying contracts, interacting via the console and more! We’re not stopping there though. Today we’re proud to introduce live network simulation via sandbox forking!
-
-## Introducing Forking
-
-Forking allows a sandbox to act as a live network from a given block number. We take for granted in web2 that we can get test credentials and interact with an API that will map to our production environment, but in web3 this hasn’t been so easy. With a forked sandbox you can transact, deploy, test, and debug against Mainnet without spending real Ether!
-
-Forking has been available since 2017 ([see this older tutorial](/guides/chain-forking-exploiting-the-dao)), but the requirement of a full archival node was a barrier for many. By adding this ability to Truffle Teams, you no longer need to worry about anything--just select a network and go. Here are some more specific examples:
-
-* **DeFi**: Some DeFi protocols have testnet deployments that differ from their Mainnet counterparts for a variety of reasons. For dapp developers, this inconsistency presents a problem. You want to develop against the “real” protocol, but developing in production is terrible, especially when real ETH is at stake! With forking, you’re free to simply fork Mainnet and deploy your dapp to an environment that translates to the live network.
-
-* **Testing**: Ensuring your dapp integrates with another used to require getting those contracts, deploying them to your local test network or a live testnet (assuming there’s no comparable testnet deployment already), then finally running your tests. With a forked sandbox your target dapp is already there, with its state. Want to test your CryptoKitty item? You can do it with your actual kitty!
-
-* **Security Analysis**: Dynamic analysis, the process of executing code and data in real-time with the hope of finding issues during execution, has never been easier. With the ability to take control of any account on the given network and travel through time by selecting an older block, you can run attacks live and see exactly what went wrong.
-
-## How to Create a Forked Sandbox
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/sandbox-forking-with-truffle-teams/forking-details-for-blog.png" alt="--stacktrace-extra" style="width:100%">
-  <figcaption class="text-center font-italic">A forked Mainnet sandbox.</figcaption>
-</figure>
-
-To fork a network, create a new sandbox and check the forking checkbox. From there, select a network and optionally provide a block number. Clicking CONFIRM will spin up a new Ganache instance forked from the given network and block. For more details, <a href="/docs/teams/sandboxes/sandbox-forking" target="_blank">see our sandboxes documentation.</a>
-
-You can now interact with this sandbox as you would the forked network. Using Ethereum 
-Mainnet as an example: you can call out to Mainnet contracts, and send ETH to Mainnet addresses.
-<div class="mt-12 text-center">
-    <a class="btn btn-truffle mt-3" href="/docs/teams/getting-started/creating-an-account" target="_blank">START TESTING AGAINST PRODUCTION NETWORKS TODAY!</a>
-  </div>
-
-## How Will you Use Forking?
-We’re very proud of this feature and think it’s going to be a game-changer for the community. We’re curious: how will you use forking?
-
-We want Truffle Teams to be the most effective devops tool in the blockchain space for both new and existing teams. <a href="https://trfl.co/become-a-truffler" target="_blank">Join our slack community</a> and let us know what you think about this feature, and if your team has other needs we haven’t met yet.
-
-**Thank you!**
-
-Josh Quintal, Head of Product & Marketing
diff --git a/src/blog/stack-tracing-with-truffle-test/index.md b/src/blog/stack-tracing-with-truffle-test/index.md
deleted file mode 100644
index c442e5083..000000000
--- a/src/blog/stack-tracing-with-truffle-test/index.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Stack Tracing with Truffle Test
-hide:
-  - navigation
----
-
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog-header-stacktraces.png" alt="--stacktrace-extra" style="width:100%">
-</figure>
-
-Truffle Test can now provide stacktraces when your transactions revert! This is still a little experimental, and it requires `truffle test` to recompile all your contracts, so you’ll have to enable it with `truffle test --stacktrace`. 
-Here’s what the result looks like:
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog1.png" alt="truffle test --stacktrace" style="width:100%">
-  <figcaption class="text-center font-italic">truffle test --stacktrace</figcaption>
-</figure>
-
-The stacktrace continues seamlessly from the Javascript test into the Solidity contracts. It begins in the Javscript where the transaction was sent, continues through the contract that initially received the transaction, and finally ends in the contract where the revert occurred.
-
-These Solidity stacktraces will be printed both for reverted transactions sent during tests and for reverted deployments made during tests with `Contract.new()`. Stacktraces are not currently available for calls or gas estimates. Note that stacktraces are a Truffle Contract feature, and will not be available if transactions are sent by other means.
-
-What if we want a little more? Looking at the above example again, one of our stacktraces helpfully included a revert message, but the other did not. Wouldn’t it be nice if it had one too? Let’s try this again, but this time with `--stacktrace-extra`:
-<figure>
-  <img class="mb-4 figure-shadow" src="/img/blog/stack-tracing-with-truffle-test/blog2.png" alt="--stacktrace-extra" style="width:100%">
-  <figcaption class="text-center font-italic">--stacktrace-extra</figcaption>
-</figure>
-
-There we go! The `--stacktrace-extra` option, in addition to turning on stacktraces, additionally compiles your contracts with Solidity’s debug mode, so you get more information about just why the transaction reverted.
-
-Of course, for more detailed analysis, you may want to use Truffle Debugger! But stacktraces in tests can give a good first view of why your transaction reverted.
-
-These testing options are still a little experimental, so it’s possible some things may not work with them. But, in most cases, they should provide a quick helpful view into why your test transaction reverted!
-
-Thanks,
-
-Harry Altman
-
---Debugger Engineer, Truffle Suite
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-6" href="https://github.com/trufflesuite/truffle/releases/tag/v5.1.24">Click here for the release notes on GitHub</a>
-</div>
diff --git a/src/blog/sunsetting-truffle-teams/index.md b/src/blog/sunsetting-truffle-teams/index.md
deleted file mode 100644
index ad9334a34..000000000
--- a/src/blog/sunsetting-truffle-teams/index.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Sunsetting Truffle Teams
-hide:
-  - navigation
----
-
-![Sunsetting Truffle Teams Banner](/img/blog/sunsetting-truffle-teams/blog-header.png)
-
-<p class="alert alert-warning">
-<i class="far fa-info-circle"></i> <strong>N.B</strong>: we published an earlier version of this blogpost with an incorrect timeline. Truffle Teams will be sunset on September 10, 2021.</a>
-</p>
-
-After a 2 year long road, we're sunsetting Truffle Teams (effective September 10th, 2021). 
-
-The journey began when Truffle was an independent company. It extended our reach from dapp development into dapp maintenance. We've gained valuable insights about the state of blockchain devops, the most desirable parts of our tools, and a new clarity around our core competencies.
-
-As an independent company, Truffle Teams was integral to building a business for the long-term, but it came with some costly tradeoffs. Over time the resources required to develop and maintain it were too great, taking time away from development of our open-source tools and eventually taking time away from supporting tasks like ecosystem engagement and development. This was unsustainable.
-
-Another important factor made this sunsetting possible: The acquisition of Truffle Suite by ConsenSys Software granted us greater supporting resources and freed us from monetary metrics. Which leads us to some good news! We are reaffirming our commitment to having the best-in-class open-source blockchain developer tools.
-
-## What about paid subscribers?
-
-All active Pro and Enterprise tier users will receive a refund of 1 month and recurring billings will cease. If you don't see a refund within 5 days (Paddle's processing time), email us at [truffle-teams@trufflesuite.com](mailto:truffle-teams@trufflesuite.com).
-
-## What about my data?
-
-All user data will be deleted 30 days following the date of shut down (September 10th 2021). Be sure to request your data before this time, otherwise we'll be unable to guarantee recovery. If you would like a dump of your data, email us at [truffle-teams@trufflesuite.com](mailto:truffle-teams@trufflesuite.com).
-
-**All user data will be deleted on September 10th, 2021.** Make sure to request your data before this time, otherwise we'll be unable to recover it.
-
-## The afterlife is open-source
-
-Parts of Truffle Teams will be making their way into our open-source tools! We're happy to share one right now--repackaging the visual debugger as a plugin that allows you to launch an instance from within Truffle. Truffle Teams provided greater context around your dapps activity thanks to its GUI. Being able to pull up a list of transactions from a Ganache instance, filter by failures, and clicking a debug button was one of the better workflows that we're proud to integrate with our open-source suite.
-
-These repurposed bits will all be open-source, so you can [check out the `truffle-plugin-debugger` repository here.](https://github.com/trufflesuite/truffle-plugin-debugger)
-
-<figure>
-  <img class="mb-4 w-100" src="/img/blog/sunsetting-truffle-teams/visual-debugger.png" alt="the Truffle Teams visual debugger--coming to Truffle!">
-  <figcaption class="text-center font-italic">The Truffle Teams visual debugger--coming to Truffle!</figcaption>
-</figure>
-
-If there are other features you'd like to see again, for example the deployments screen or contract manager, let us know!
-
-Sincerely,
-
-_The Truffle Suite Team_
diff --git a/src/blog/take-a-dive-into-truffle-5/index.md b/src/blog/take-a-dive-into-truffle-5/index.md
deleted file mode 100644
index 065a9d89d..000000000
--- a/src/blog/take-a-dive-into-truffle-5/index.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: Take a Dive into Truffle 5
-hide:
-  - navigation
----
-
-![Take a Dive into Truffle 5 Banner](/img/blog/take-a-dive-into-truffle-5/blog-header.png)
-
-Truffle 5 has had some exciting releases in the flexibilty they provide to your workflow. 🌊 Truffle now offers the ability to detect the version of Solidity in your contracts at compile time and allows for compilation from ABI files. Because of this, wrangling a project whose contracts use multiple version of Solidity is much easier going forward. We've also enhanced our testing capabilities with Solidity strack traces and better event decoding, making it much easier to get to the source of an error and get richer information from events. When our projects integrate with existing protocols, it's a pain to have to deal with those external contracts. Now Truffle makes this easy with the ability to fetch external contracts verified on Etherscan! Vyper support continues to improve with experimental debugging for Vyper contracts, as well as improved import handling for Vyper.
-
-Did I mention support for **decentralized file storage**?
-
-## What's New in 5.2 and 5.3
-
-### IPFS, Filecoin, and Textile Bucket support via `truffle preserve`
-
-Tests have ran, bugs are squashed, your smart contracts have been deployed successfully to mainnet; life is good. It's time to make your dapp accessible to the masses! So you... go to a centralized host and spin up the frontend? Something's definitely off here.
-
-Enter `truffle preserve`: You can now use Truffle to upload your static assets to [IPFS](https://ipfs.io/), [Filecoin](https://filecoin.io/), and/or [Textile Buckets](https://docs.textile.io/buckets/) for a fully decentralized application across the entire stack!
-
-Here are some companion pieces to help you get started:
-- The [Filecoin Truffle Box](https://github.com/truffle-box/filecoin-box) includes a decentralized art gallery to get you started with a fully working project!
-- [The original Filecoin + Truffle & Ganache Blog Post](/blog/truffle-and-ganache-now-come-in-filecoin-flavor)
-- [`truffle preserve` Documentation](/docs/truffle/getting-started/preserving-files-and-content-to-storage-platforms)
-
-<figure>
-  <img class="mb-4 w-100" src="https://github.com/truffle-box/filecoin-box/raw/master/screenshots/sample-ui.png?raw=true" alt="the Filecoin Trufflebox provides you with a Filecoin powred art gallery">
-  <figcaption class="text-center font-italic">Unbox a decentralized art gallery with the Filecoin Truffle Box.</figcaption>
-</figure>
-
-### Pragma compilation
-
-As of version 5.2.0, Truffle now ships with a fun, experimental setting for compilation: the “pragma” setting. This feature analyzes your Solidity source files for their pragma expressions. It then uses these expressions to figure out which version of the Solidity compiler is required for each given source. This allows your project to compile when it contains multiple Solidity files, each requiring a different version of the Solidity compiler!
-
-To use this feature, set the Solidity compiler version field in your `truffle-config.js` as follows:
-
-```javascript
-module.exports = {
-  compilers: {
-    solc: {
-      version: “pragma”
-    }
-  },
-  // … the rest of your config goes here
-};
-```
-
-Now you can run `truffle compile` and your project will compile!
-
-To illustrate this feature and the ones below, we have created a [Truffle box for Truffle 5.2](https://github.com/truffle-box/v5.2-example-box).
-
-In this box you can see how the `truffle-config.js` is set up to use this new experimental feature. Notice that `contracts/MetaCoin.sol` requires `^0.7.0` and how `contracts/Conversion.sol` requires `^0.6.0`. When running `truffle compile` on this example project you should get a printout of all the versions of the Solidity compiler used during compilation. Namely, you should see that both version `0.6.12` and `0.7.6` are listed.
-
-When you use this feature, Truffle will analyze each of your Solidity sources one by one to find the appropriate version of the Solidity compiler for each source. Do note, however, that each source file and all of its imports must be compiled with one version of Solidity; this means there must be a version of the compiler that satisfies all of their pragma expressions.
-
-## Things you may have missed in Truffle 5.1
-
-We’ve added a fair bit over the course of Truffle 5.1 as well, and there’s a good chance you didn’t catch all of it!  We thought this would be a good time to review some of that as well!
-
-### Compilation of abi.json files
-
-Another exciting addition to Truffle is the ability to compile from a contract’s ABI. When you create a JSON source file in your “contracts” directory that contains a contract’s ABI, Truffle will take it, use it to create an interface, and compile it. This might come in handy, for example, when you want to import and use a library that requires a different version of the Solidity compiler than the importing file. You can then simply compile the library and create a new JSON file containing the ABI of the imported library. Under the hood Truffle will compile the ABI into a Solidity interface and create an artifact for it. You will then be able to import the interface into your contract!
-
-In the v5.2-example-box, consider the `contracts/MetaCoin.sol` and `contracts/Conversion.sol`. We would like to import Conversion into the MetaCoin contract to use it but cannot since they require different versions of the Solidity compiler.  To work around this, we have created `contracts/IConversion.abi.json` which contains the ABI from the compiled Conversion. In this way we can now import the interface into `contracts/MetaCoin.sol` (see line 4 in the MetaCoin contract) to use it!
-
-### Solidity stacktraces in Truffle Test
-
-Try running your tests with the `--stacktrace` option (or `-t` for short) and get combined Solidity-Javascript stacktraces!  This feature does have some limitations and is still somewhat experimental, but we expect you’ll find it quite useful.  In the future we may add support for Vyper stacktraces as well!  
-
-And speaking of Vyper...
-
-### Experimental Vyper debugging
-
-You can now use Truffle Debugger with Vyper!  Support for this is still in its early stages; you won’t be able to inspect variables, I’m afraid.  But you can step through a Vyper transaction, and there will likely be more in the future!
-
-But perhaps the biggest improvement to the debugger is...
-
-### Debugging verified external contracts
-
-Use the `--fetch-external` (or `-x` for short) option with Truffle Debugger and it will automatically download sources for any verified contracts and allow you to step through them!  Contracts can be verified on either Etherscan or Sourcify.  You no longer need to download these yourself and add them to your Truffle project!  You can see [this](/blog/debugging-verified-external-contracts-with-truffle-debugger) earlier post for more information.
-
-###Improved import handling in Vyper
-
-Here’s another one for our Vyper users; you can now do imports from other projects (via NPM or EthPM) just like in Solidity!
-
-For instance, suppose `examplepackage` is an NPM package which is structured as a Truffle project, and you want to import a Vyper contract, `VyperContract`, from it.  You can now do
-
-```python
-from examplepackage.contracts import VyperContract
-```
-
-or
-
-```python
-import examplepackage.contracts.VyperContract as VyperContract
-```
-
-to import it, much like you could do in Solidity!
-
-Note that if your own project uses such “absolute” imports as a way to import its own files from the project root -- e.g., if you have a file `contracts/subdirectory/Contract1.vy` which imports `contracts/Contract2.vy` via
-
-```python
-import Contract2 as Contract2
-```
-
-then this will work within your own project, but won’t work if other people try to import your `Contract1`.  We suggest that if you want other people to import contracts from your project, you use explicitly relative imports instead:
-
-```python
-from .. import Contract2
-```
-
-But such imports are now possible.  We hope you’ll find all sorts of uses for this!
-
-### Enumeration values in Truffle Contract objects
-
-When sending a transaction that takes an `enum`, it’s inconvenient to have to look up the numeric constants that the `enum` uses.  Well, now, each Truffle Contract constructor object contains enumeration constants, so you don’t need to do that.  Just do
-
-```javascript
-contractInstance.exampleMethod(Contract.ExampleEnum.EnumValue);
-```
-
-and don’t worry about the particular numeric value of `EnumValue`.  You can also do `Contract.enums.ExampleEnum.EnumValue`, if you want to be extra-certain.
-
-Note that it’s not currently possible to access enums declared outside of a contract this way, but we have plans in the future to make using those easier, too!
-
-### Even more!
-
-Other things you might have missed include: Improved event decoding in `truffle test`; being able to use the debugger to step through Yul (assembly) sources generated by Solidity for its own internal subroutines (try the `g` command!); being able to inspect assembly variables in the debugger; `truffle test --bail`; `truffle create all`; and the debugger providing more information upon transaction reversion.
-
-### What's Next? Want to Help us Build it?
-
-How will you use the new enhancements in Truffle? Let us know what you think about these features on Twitter, and if you have other needs we haven’t met yet.
-
-<p class="alert alert-info m-t-2">
-<i class="fas fa-info-circle"></i> <strong>WE'RE HIRING!</strong> Why stop at feature requests--cut out the middleman and work with us directly! There are many exciting problems to solve like layer 2 support, mapping decoding, and a revamped deployment system, to name a few. We'd love your help and perspective. <strong><a href="https://consensys.net/open-roles/3004215/">Apply here on ConsenSys' website!</a></strong>
-</p>
diff --git a/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md b/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
deleted file mode 100644
index 93b4b1f9f..000000000
--- a/src/blog/take-control-of-your-deployments-with-truffle-teams/index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Take Control of Your Deployments with Truffle Teams
-hide:
-  - navigation
----
-
-![Truffle Teams Deployments Banner](/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/truffle-teams-deployments-banner.png)
-
-If you read our [blog post back in July](/blog/an-easier-way-to-deploy-your-smart-contracts), attended my TruffleCon workshop **Push It! Push It Real Good: Truffle Teams Intro & Deployments** back in August, or tuned in last week to our **Truffle Teams Overview** webinar, you've known something awesome has been in the works for Truffle Teams.
-
-Well it's finally here! On behalf of the whole team, I'm excited to announce Deployments within Truffle Teams!
-
-<a target="_blank" href="/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/deployments.png">![Deployments](/img/blog/easily-deploy-your-smart-contracts-with-truffle-teams/deployments.png)</a>
-
-## Bridging the Gap Between Local Ganache Testing and Public Testnet/Mainnet Deployments
-
-The interaction between Truffle and Ganache provides an awesome way to iteratively test and fix contracts on a personal Ethereum blockchain. However, it can be a little tricky when you're ready to publish your application to the rest of the world. That's where Truffle Teams Deployments comes in: we give you a **dead-simple deployment experience** which links with MetaMask so you never need to export your private keys.
-
-## Benefits of Deploying with Truffle Teams
-
-- **Easily deploy to public Ethereum networks** (Mainnet, Ropsten, Görli, Rinkeby, and Kovan are supported)
-- **Works with the existing migration scripts** in your Truffle project; Truffle Teams uses `truffle migrate` under the hood
-- **No need to export/import private keys** — use [MetaMask](https://metamask.io/) to deploy like you would with any other dapp
-- **Deploy with [Ledger](https://www.ledger.com/) or [Trezor](https://trezor.io/) hardware wallets** within MetaMask
-
-## Learn More in Our Tutorial or Try It Now!
-
-We put together a step-by-step [tutorial](/guides/learn-how-to-deploy-with-truffle-teams) to guide you through your first Truffle Teams deployment. While we recommend that you follow the tutorial (as it answers some FAQs), the deployment experience is simple enough for you to just give it a shot! 👇
-
-<div class="post-trufflecon-box mt-5 text-center">
-  Get started with Truffle Teams, and see deployments for yourself!
-
-  <div class="mt-3">
-    <a class="btn btn-truffle" href="/docs/teams/getting-started/creating-an-account">Try Truffle Teams</a>
-  </div>
-</div>
\ No newline at end of file
diff --git a/src/blog/testrpc-is-now-ganache/index.md b/src/blog/testrpc-is-now-ganache/index.md
deleted file mode 100644
index 6166510a0..000000000
--- a/src/blog/testrpc-is-now-ganache/index.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: TestRPC is now Ganache
-hide:
-  - navigation
----
-
-Have you been looking for the TestRPC recently and haven't been able to find it?
-
-Don't worry, it's still here! It's just now known as **Ganache**.
-
-Ganache comes in two flavors: a fully-interactive development blockchain with a graphical interface, and the more familiar command-line version.
-
-* [Get the graphical version here](/ganache).
-
-* For the command-line version (known as **Ganache CLI**):
-
-  ```shell
-  npm install -g ganache-cli
-  ```
-
-## A little history
-
-Prior to the existence of the TestRPC, you would have to deploy to private internal test networks to see how your contract code operated (as public test networks like Ropsten didn't yet exist!).
-
-While initially under the auspices of the [EthereumJS project](https://github.com/ethereumjs/), it was originally created by the Truffle team, and today we remain its primary maintainers. So simply for maintainability sake, it just made sense to bring the TestRPC under Truffle's wing.
-
-Additionally, we realized over time that the TestRPC was a poor name. The TestRPC quickly became more powerful than simply a blockchain environment used for testing. To stay with the sweet Truffle brand, we decided to rename it Ganache, as Ganache is (often) the core of your favorite chocolate truffle. It's a much catchier name (and a much tastier one too).
-
-## Multiple ways to enjoy
-
-With this name change, we also released [a fully-interactive, graphical version of Ganache](/ganache).
-
-The command-line utility is still available via NPM; the [command line flags](https://github.com/trufflesuite/ganache-cli/blob/master/README.md) are the same too. All that's changed is the name of the command.
-
-Ganache is also available as a library for your applications. See the [README](https://github.com/trufflesuite/ganache-cli/blob/master/README.md) for more details.
-
-So now you have multiple ways to create a personal blockchain. If you're looking for a blockchain with a graphical environment that's perfect for beginners, check out [Ganache](/ganache). And if you want the familiar command-line interface, install Ganache CLI. Happy developing!
diff --git a/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md b/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
deleted file mode 100644
index fa7f61224..000000000
--- a/src/blog/the-best-things-to-do-in-seattle-during-trufflecon/index.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: The Best Things to do in Seattle During TruffleCon
-hide:
-  - navigation
----
-
-![river view at Marymoor Park](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-1.jpg)
-
-## [Marymoor Park](https://www.kingcounty.gov/services/parks-recreation/parks/parks-and-natural-lands/popular-parks/marymoor.aspx)
-
-Marymoor Park, located on the north end of Lake Sammamish in Redmond, Washington, is King County's largest, oldest, and most popular park, with more than 3 million annual visitors coming to roam its 640 acres. Marymoor is famous for its [outdoor concert series](https://www.marymoorconcerts.com/events) during the summer. You can catch concerts on Aug 2 and Aug 4 after the day festivities at TruffleCon!
-
-## [Sammamish River Trail](https://www.alltrails.com/trail/us/washington/sammamish-river)
-
-The Sammamish River Trail is a beautiful 19-mile bike path and recreational trail in King County, Washington that runs along the Sammamish River from Blythe Park in Bothell to Marymoor Park in Redmond. There are several places along the trail you can enter. It's perfect for biking, running, or just enjoying a nice walk in the beautiful outdoors!
-
-## [Idylwood Beach Park](https://experienceredmond.com/activities-and-attractions/idylwood-beach-park/)
-
-August can reach temperatures of up to 80 degrees, which is quite hot for Seattleites. Idylwood Beach Park is one of the best places to cool off. It's a waterfront park on Lake Sammamish with a beach, boat ramp, playground & canoe rentals.
-
-## [Microsoft Visitor Center](https://experienceredmond.com/activities-and-attractions/microsoft-visitors-center/)
-
-The Microsoft Visitor Center is open during the weekdays. Walk through the doors of the Microsoft Visitor Center and unlock your potential—experience everything from the latest Microsoft Research innovations to the very first personal computer. Microsoft offers self-guided tour information to explore hands-on exhibits featuring some of the company's most exciting technologies for home and business.
-
-![entrance to Microsoft Visitor Center](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-2.jpg)
-
-## [Woodinville Wine Country](https://woodinvillewinecountry.com/)
-
-Nestled in the beautiful Sammamish River Valley just 30 minutes northeast of Seattle, Woodinville Wine Country is home to over 100 wineries and tasting rooms representing every appellation in Washington.
-
-From the historic and beautiful grounds of Chateau Ste. Michelle to the quaint boutique wineries where you are likely to have the winemaker themselves pour you a glass of his or her finest blend, a wonderful variety of wine tasting experiences awaits you!
-
-![winery building in the Sammamish River Valley](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-3.jpg)
-
-## [Black Raven Brewing Company](https://www.blackravenbrewing.com/)
-
-Black Raven is a neighborhood brewery with a friendly retail taproom, The Raven's Nest, with locations in both Redmond and Woodinville. The Raven's Nest is not a traditional brewpub; it's more like our brewery's living room. Open 7 days a week and a seating capacity of about 100, it's home to local beer lovers who want to be a part of a community that enjoy great beer and great friends.
-
-## [Mac & Jack's Brewing](https://www.macandjacks.com/)
-
-Mac and Jack's brewing offer a tasting room, retail store, beer garden, and tours at their brewery in Redmond, WA. Mac & Jack's started out of Jack's garage in 1993, with nothing but a passion for exceptional beer. Lots of hops and 26 years later they are still producing one of Seattle's favorite beverages.
-
-## [Flee Escape Room](https://www.fleeescape.com/)
-
-Flee Escape Game is one of the largest Seattle and Redmond Real Life Escape Rooms. So grab your team, new friends you just met, or organize a party to see if you can all make your great escape.
-
-![egyptian themed escape room](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-4.jpg)
-
-## [Paragliding](https://www.tigermountainparagliding.com/fly-tandem/)
-
-Come paraglide tandem with us, and experience free flight in its purest form! After running down a moderately steep hill you'll find yourself airborne, sitting comfortably in a reclined harness, your feet dangling above the trees, no one in front of you (pilot rides in back) and no cockpit surrounding you.
-
-Depending on conditions you'll have views of Mt. Rainier, Mt. Si, Lake Sammamish, Bellevue, Seattle, the Puget Sound and so much more. Bald eagles and other predators leave their nests to ride the same thermals allowing you to literally fly with birds.
-
-![couple having fun paragliding](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-5.jpg)
-
-## [Salish Lodge/Snoqualmie Falls](https://www.salishlodge.com/)
-
-Overlooking Snoqualmie Falls, just 30 minutes east of Seattle and Bellevue, Salish Lodge & Spa is a Washington State resort getaway, perfect for those seeking an authentic and memorable escape from the everyday. Dine on mouthwatering [Northwest cuisine](https://www.salishlodge.com/dining.php) hand-crafted from seasonal ingredients, savor the serenity of [The Spa](https://www.salishlodge.com/spa.php), then drift off to sleep in front of your cozy fireplace in one of our newly renovated guestrooms. We invite you to experience the iconic Salish Lodge.
-
-![aerial view of snoqualmie falls](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-6.jpg)
-
-## [DirtFish Rally Driving School](https://www.dirtfish.com/)
-
-Nestled in the foothills of the Cascade Mountain Range in the scenic town of Snoqualmie, WA, DirtFish Rally School was established in 2010 with the idea that the exciting sport of rally should be accessible to everyone. Armed with an immaculate fleet of turbocharged, all-wheel-drive cars, right from the beginning DirtFish was equipped to share with anyone the excitement of what a real rally car can do on a loose surface. In the fall of 2014, DirtFish embellished their offerings with the launch of rear-wheel drive programs. Similar in nature to the all-wheel drive programs, the precise and very sideways action the classes offer provides an entirely different challenge for drivers of every background. Ever since, DirtFish has become the most prestigious rally school in North America, providing the highest level of instruction, top level cars and gorgeous facilities all year round.
-
-![rally car driving on dirt road](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-7.jpg)
-
-## [Hiking](https://www.wta.org/)
-
-Hiking in nature has a positive impact on people's hearts, minds and bodies. It is vital for everyone to have the opportunity to access the outdoors, and the WTA is committed to reducing barriers to hiking trails and lands. We strive to inspire people to go outside—giving them the skills and knowledge they need to recreate safely and sustainably.
-
-People will protect the places they love to hike. WTA rallies hikers to raise our collective voice to protect the places we love. Our voice is amplified by the support of our members and sweat equity of every volunteer who helps to build and maintain trails.
-
-![beautful views of the mountains on the hiking trail](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-8.jpg)
-
-## [Mountain Biking](https://seattlemountainbiketours.com/)
-
-Your all-inclusive mountain biking tour in Seattle includes pickup from Downtown Seattle or Bellevue and shuttle transportation to our favorite trails for intermediate and experienced cyclists. At the trailhead, you get your high-quality mountain bike, a helmet, gloves, and any other safety gear needed for our ride. Don't worry, we have plenty of water and snacks for our mountain biking adventure!
-
-![mountain biker rounding the bend in Seattle](/img/blog/the-best-things-to-do-in-seattle-during-trufflecon/layer-9.jpg)
diff --git a/src/blog/the-best-ways-to-contribute-to-truffle/index.md b/src/blog/the-best-ways-to-contribute-to-truffle/index.md
deleted file mode 100644
index ea5121adb..000000000
--- a/src/blog/the-best-ways-to-contribute-to-truffle/index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: The Best Ways to Contribute to Truffle
-hide:
-  - navigation
----
-
-Have you ever thought about contributing to Truffle? All of us at Truffle really enjoy producing free and open source software, and it is especially fun when many of you in the community contribute. User contributions make life easier for us, make our work more enjoyable by showing that you’re engaged, and often give us a chance to learn from those that offer code to the project. We’d absolutely love any and all developers to contribute to our project. The following are a few ways that you can get involved.
-
-## Read the contributor guidelines.
-
-The first step anyone should take before contributing to Truffle is to hop on over to our Github page and [read our contributing guidelines](https://github.com/trufflesuite/truffle/blob/develop/CONTRIBUTING.md). Our contributing guidelines will give you a baseline understanding of how Truffle is built, which tools to use during development, and other useful information to get you started. Make sure to read those guidelines before continuing on in this post.
-
-## Follow the command flow.
-
-You’ll see that the contributing guidelines focus on the command flow. This is because at its core, Truffle is a command line tool that processes and runs specific commands on behalf of a user. If you can figure out where a command starts, you can follow its execution to get a better understanding of what Truffle is doing. We recommend choosing your favorite command and following its path through the code. We’d also recommend performing your own local experiments by changing the behavior of a specific command and seeing how it behaves. Don’t forget to read the contributing guidelines above, as it tells you where to get started for each command.
-
-## Change callbacks to Promises.
-
-Given the lifetime of the project -- over four years! -- Truffle has its share of legacy code. Before Promises became widespread in the Node world, callbacks were used to control the flow of asynchronous code within Truffle. The code was written in a style where a callback function was passed from one method to the next, intended to be executed after everything else had finished running or when an error occurred. Nowadays, many people find this style of code to be abstruse, and hard to understand, and now favor Promises over callbacks. We do too. One of our major tasks over the coming year is to rework our code to favor a Promise-based coding style instead of a callback-based one. We are always interested in receiving PRs that clean up our callbacks and make the code easier to understand for everyone (we love you async/await).
-
-## Start small, and chat with us for larger tasks.
-
-It can be very overwhelming to begin contributing to Truffle with a big feature. Instead, we recommend going after a smaller, more bite-sized change that will not only make you feel more successful, but can also help you get a better understanding of the underlying code. If you find something trivial, like a documentation error, go ahead and fork the repository, make your changes, and submit a pull request. For something bigger, we like to have a discussion first as our tools support many different use cases and platforms. If you have a great idea for a change that will require significant effort, we recommend filing a GitHub issue with a proposal or contacting us using the channels below. We can layout specs, bounce ideas around, and agree on what’s needed before you dive in.
-
-## Tackle an issue.
-
-Many of our users submit issues for things that need to be fixed. Sometimes these issues are small bugs that have been able to hide in the cracks. Other times they can be large changes or feature requests that require significant effort to fix. Regardless of your appetite, our [issues list](https://github.com/trufflesuite/truffle/issues) is often a great place to start for people to contribute. Due to the nature of software, you’re bound to find an issue that’s right for you. And even if you don’t think you can fix an issue, confirming that issues exist and giving us extra information can be extremely helpful. Often the biggest factor keeping a sneaky bug alive is information, so validating an issue exists and providing more data can help us squash that bug even faster.
-
-## Contact us.
-
-As always, we’d love to hear your feedback and concerns, as well as answer any questions you have when contributing to Truffle. Feel free to reach out to us on our [Spectrum](https://spectrum.chat/trufflesuite) page, or file an issue on [Github](https://github.com/trufflesuite/truffle/issues). We'd love to hear from you. Happy Truffling!
diff --git a/src/blog/the-blockchain-problem-that-ens-solves/index.md b/src/blog/the-blockchain-problem-that-ens-solves/index.md
deleted file mode 100644
index d4916ab4a..000000000
--- a/src/blog/the-blockchain-problem-that-ens-solves/index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: The Blockchain UI Problem that ENS Solves
-hide:
-  - navigation
----
-
-The blockchain world has a UI problem. This is what an Ethereum receiving address looks like:
-
-**0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359**
-
-Bitcoin and other cryptocurrencies have the same problem, as do related decentralized projects like IPFS. The computer-generated address system works great for computers but isn’t user-friendly.
-
-This isn’t a new problem. The nascent Internet had a similar issue with IP addresses. For the Internet to eventually be used by millions and now billions of regular users, it needed a way to mask the machine-readable identifiers. So, in 1985, the “phone book of the Internet,” the Domain Name System (DNS), was born. While the DNS is used by many protocols, the World Wide Web really took the DNS mainstream. Can you imagine the web if users had to type in “72.125.224.72” rather than “google.com”?
-
-The blockchain world needs the same thing. We could use the existing DNS, but it’s a relatively centralized server architecture which makes it unattractive for blockchain applications.
-
-That’s where the Ethereum Name Service (ENS) comes in. ENS provides the same basic functionality of DNS (look up the records for “example.tld,” retrieve information), but replaces the hierarchical DNS server system with a few smart contracts on Ethereum.
-
-ENS is the naming service of the new decentralized Internet - with less infrastructure, better security, and of course less centralized control.
-
-ENS launched in 2017 with the native TLD.ETH, but we’ve been experimenting with allowing owners of DNS domains to use their domains on ENS and have successfully done this with .XYZ and .LUXE domains. We plan on rolling out this capability to most other TLDs later this year.
-
-We want to make it as easy as possible for dapp developers to take advantage of the big UI gains that ENS provides, which is why we’re working with Truffle. We are excited to be announcing several useful ENS integrations built into TruffleSuite at TruffleCon, so stay tuned!
-
-[Register your domain name](https://ens.domains/) using ENS today!
-
-Helpful Links:
-* Website: [https://ens.domains/](https://ens.domains/)
-* Manager: [https://manager.ens.domains/](https://manager.ens.domains/)
-* Docs: [https://docs.ens.domains/](https://docs.ens.domains/)
-* Gitter: [https://gitter.im/ethereum/go-ethereum/name-registry](https://gitter.im/ethereum/go-ethereum/name-registry)
-* Forum: [https://discuss.ens.domains/](https://discuss.ens.domains/)
diff --git a/src/blog/token-taxonomy-framework/index.md b/src/blog/token-taxonomy-framework/index.md
deleted file mode 100644
index b8059a4c0..000000000
--- a/src/blog/token-taxonomy-framework/index.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Token Taxonomy Framework
-hide:
-  - navigation
----
-
-To some, the sudden rise of Tokens in the blockchain dialog comes as a surprise. However, tokens have always been the bedrock of the blockchain movement. The introduction of SmartContract by Ethereum quickly overshadowed them, particularly in enterprise contexts. The capabilities of Smart Contracts and the broad acceptance of them, thanks to companies like Truffle, blazed a trail forward and we all went along. It wasn’t until we got halfway up the trail that someone turned around and asked, “did we pack any trail mix?”
-
-Sure, we had Ether, but one cannot persist on Ether alone. Focus shifted back to our roots. Developers who had steeped in SmartContracts turned their attention to tokens. However, they also brought a bit of baggage. You can do a lot in a Token using SmartContract concepts. We started to see the blurring of lines between what a contract was and what was a token, leading to a good bit of confusion all around.
-
-Back in April, [the Token Taxonomy Initiative (TTI)](https://tokentaxonomy.org/) was launched with very strong backing and a cross blockchain and platform set of founders including the EEA, ConsenSys, IBM, R3 and Digital Asset in an effort to provide clarity and purpose for tokens moving forward as the way we define value and how it can be used between parties across networks and platforms. The major deliverable from the TTI is the Token Taxonomy Framework (TTF), which is a platform neutral framework for defining and token that can eventually be certified and start to address critical issues like interoperability.
-
-![Token Taxonomy Framework](/img/blog/token-taxonomy-framework/framework.png)
-
-I’ll be presenting an [Introduction to the TTF](https://trufflecon2019.sched.com/event/RneW/token-taxonomy-framework) at TruffleCon on August 4th here in Redmond, WA. Swing by to hear how you can use the TTF to communicate with customers and partners, use the same terms and get solid requirements from the business, legal and regulatory communities.
diff --git a/src/blog/truffle-320-released/index.md b/src/blog/truffle-320-released/index.md
deleted file mode 100644
index 68219d4ba..000000000
--- a/src/blog/truffle-320-released/index.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Truffle 3.2.0 released
-hide:
-  - navigation
----
-
-<p class="alert alert-info" style="margin-top: -2rem; margin-bottom: 3rem;">
-  <strong>UPDATE</strong>: We made another minor release after this blog post was written <a href="https://github.com/trufflesuite/truffle/releases/tag/v3.2.1">upgrading web3 to 0.18.2</a> due to request of our users. <a href="https://github.com/trufflesuite/truffle/releases/tag/v3.2.1">Truffle v3.2.1</a> is now the latest release, but it still includes all the awesome stuff below.
-</p>
-
-Hi all. Great news today.
-
-Following your feedback from the Truffle 3.0 release, we've just released Truffle 3.2.0! This release includes a [number of great new features and bug fixes](https://github.com/trufflesuite/truffle/releases/tag/3.2.0), but we're most excited about the following. I've bolded the good stuff for ya.
-
-1. **We've built infrastructure for providing you boilerplates on demand!** Now with `truffle init` comes `truffle init webpack`, which gives you a boilerplate web application combining the web development capabilities of Webpack with the power of Truffle. More boilerplates to come to make your life easier, so stay tuned!
-
-1. **We've added huge speed improvements to the Truffle command line tool.** Now your commands trigger in milliseconds! Go ahead, try it out. `truffle version`
-
-1. **Solidity tests can now be given default balances** so you can use those tests to exercise sending Ether to your contracts. Big win for Solidity tests, and your sanity in general. [Documentation](/docs/truffle/testing/writing-tests-in-solidity.html#testing-ether-transactions)
-
-1. Similarly, **Javascript abstractions got an upgrade** making it easier to send Ether directly to your contracts as well as trigger your contracts' fallback functions. You can use this feature within your tests as well as within your application. [More on that here](/docs/truffle/getting-started/interacting-with-your-contracts.html#sending-ether-to-a-contract). Also, they now use web3 0.18.2.
-
-1. **Migrations got an extra scout badge (function parameter)**, [allowing you to view available accounts directly within your migration](/docs/truffle/getting-started/running-migrations.html#available-accounts)
-
-1. Oh, and **there's no more naming restriction on contract names!** 🎉🎉🎉 You can now have a file called `ImABigDeal.sol` and have it define contracts under a completely different name. Woot!
-
-1. Along with the above, **there's a new way of requiring contract artifacts within your migrations and tests**. The old way still works if your contract names match your Solidity file names, but even if they don't you can simply require the contract by name:
-
-```javascript
-// Assume `ImABigDeal.sol` defines `contract MyContract { ... }`
-var MyContract = artifacts.require("MyContract");
-```
-
-There's been a lot of bug fixes too. Check out the [release notes on Github](https://github.com/trufflesuite/truffle/releases/tag/3.2.0) for a full list of changes, upgrades and fixes.
-
-### Big thanks!
-
-As always, we have to give you all a big thanks for being a part of the community and making Truffle better. This release would not be possible without your continued feedback, bug fixes and pull requests.
-
-If you run into trouble with any of the above, reach out on our [community Gitter channel](https://gitter.im/ConsenSys/truffle) where hundreds of your fellow Trufflers congregate to answer your questions. As well, check us out [on Twitter](https://twitter.com/trufflesuite) and send us a tweet.
-
-Cheers, and happy coding!
-
--- Tim
diff --git a/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md b/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
deleted file mode 100644
index 000544e6c..000000000
--- a/src/blog/truffle-and-ganache-now-come-in-filecoin-flavor/index.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Truffle and Ganache now come in Filecoin Flavor
-hide:
-  - navigation
----
-
-![Filecoin Collab Banner with Ganache](/img/blog/truffle-and-ganache-now-come-in-filecoin-flavor/blog-header.png)
-
-[Filecoin](https://filecoin.io) was created by [Protocol Labs](https://protocol.ai), the same organization who created and maintains [IPFS](https://ipfs.io). Filecoin extends the IPFS vision by creating an open-source decentralized storage network that provides incentives to keep data stored and pinned on IPFS. Filecoin is powerful because it provides a decentralized storage solution without having to rely on larger centralized solutions. Additionally when it comes to building dapps on other decentralized networks, like Ethereum, it provides the groundwork for a much needed storage and authenticity solution to full decentralization.
-
-## Truffle Preserve to Buckets
-
-[Back in July](/blog/announcing-collaboration-with-filecoin), we announced a first look at using the `truffle preserve` command in an experimental release. Today, we are releasing `truffle preserve` as part of the main, stable version of Truffle! To use `truffle preserve`, simply specify the files you want to preserve on the command line, and choose between the `--filecoin`, `--ipfs`, or `--buckets` recipes. The `filecoin` recipe uses the `ipfs` recipe under the hood, but if you need to, you can choose to use the `ipfs` recipe without `filecoin`. You can learn more about `truffle preserve` in this [blog post](/blog/announcing-collaboration-with-filecoin).
-
-In addition, we’re also introducing a new recipe for `truffle preserve` which allows developers to save data to [Textile Buckets](https://docs.textile.io/buckets/): `truffle preserve --buckets`.
-
-![`truffle preserve --buckets` Example](/img/blog/truffle-and-ganache-now-come-in-filecoin-flavor/preserve-buckets.gif)
-
-Try out any of these three recipes today by [downloading the latest version of Truffle](/docs/truffle/getting-started/installation)!
-
-## Filecoin-flavored Ganache
-
-Ganache has helped many developers create Ethereum dapps by providing a "one-click" experience; Ganache automates the difficult parts of running a decentralized network to give the developer a personal environment to tinker with and develop applications. It speeds up development by not having to wait for decentralized test networks to confirm transactions, and it provides a controlled, configurable environment to reproduce different test scenarios.
-
-Prior to Ganache, if you wanted to run a development network for Filecoin you would need to run the [lotus-devnet](https://github.com/textileio/lotus-devnet), which requires compiling native resources or running a public Docker image. This is still a great resource to emulate the Filecoin network as close as possible as it includes a real [Lotus](https://docs.filecoin.io/get-started/lotus/) node, but Ganache now provides a lightweight alternative for getting started with Filecoin app development.
-
-With the Filecoin flavor, Ganache now provides you both an IPFS server (used to store files) as well as a Lotus simulator (used to maintain file storage, simulate a storage provider, and availability) to add the necessary Filecoin methods to get started with Filecoin development. Like the Ethereum flavor of Ganache, we've made the process as simple as possible for you to get started with Filecoin quickly.
-
-## What can I do with Filecoin-flavored Ganache?
-
-With Filecoin-flavored Ganache, you can do most of the development tasks for building a Filecoin application:
-- Store and retrieve files from a personal IPFS node that Ganache starts for you
-- Create a storage deal and see it progress through different states
-- Test how your application handles storage deal expiration
-- Transfer Filecoin's token FIL between accounts
-- Interact with the various Filecoin wallet methods
-
-You can find a full list of supported RPC methods on [GitHub](https://github.com/trufflesuite/ganache-core/tree/develop/src/chains/filecoin/filecoin#supported-rpc-methods).
-
-## How do I get started?
-
-If you’re looking to get started with Ganache, head over to the [documentation](/docs/filecoin/ganache/overview) to see Get Started guides whether you're using the NodeJS library, CLI, or graphical UI version.
-
-Need an example on how to build a Filecoin application? Check out the [Filecoin Truffle Box](https://github.com/truffle-box/filecoin-box) to see an example to mint NFTs and provide a decentralized art gallery application.
-
-We’re finalizing the Truffle documentation in the coming days, so stay tuned for those! When they’re live, you’ll be able to find them at our [main documentation page](/docs) and click on the Filecoin link.
-
-## Where can I get help?
-
-We're extremely excited to be working with the Filecoin community to add support for Filecoin into Truffle Suite's tooling. If you have questions about our Filecoin integration or our plan for the future, join [Truffle’s Discord community](https://trfl.co/truffle-community) & the [Filecoin community Slack](https://filecoin.io/slack) to get your questions answered. We're happy to help!
diff --git a/src/blog/truffle-and-infura-support-arbitrum/index.md b/src/blog/truffle-and-infura-support-arbitrum/index.md
deleted file mode 100644
index 607b9031c..000000000
--- a/src/blog/truffle-and-infura-support-arbitrum/index.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Truffle and Infura Now Support Arbitrum
-hide:
-  - navigation
----
-
-![Truffle, Arbitrum Collab Image](/img/blog/truffle-and-infura-support-arbitrum/blog-header.png)
-
-In our continuing efforts to help build the emerging multi-network Ethereum ecosystem, the Truffle team is thrilled to announce the launch of the Arbitrum Truffle Box. The usability and efficiency of Ethereum depends on scalability, and Arbitrum’s Layer 2 solution blends security and higher throughput to help make scalable Ethereum a reality.
-
-## Arbitrum
-
-Arbitrum is a Layer 2 scaling solution for Ethereum that uses optimistic rollups with interactive proving to make smart contracts scalable, fast, and private. It tracks closely to Ethereum, so that Ethereum developers can easily cross-compile their contracts to deploy on Arbitrum. Arbitrum offers its developers a variety of benefits: trustless security, compatibility with Ethereum, scalability, and cost efficiency.
-
-The Arbitrum rollup chain is built on top of and secured by Ethereum. From the developer perspective, interacting with Arbitrum is nearly identical to interacting with Ethereum. Arbitrum supports the same RPC interface as Ethereum, supports all EVM languages, and natively supports all Ethereum tooling without any special adapters. The main difference users and developers will notice is that transactions on Arbitrum cost a fraction of what they would if run natively on Ethereum.
-
-It is important to understand the mechanics of withdrawing funds from the Arbitrum chain. When withdrawing to Ethereum through an Arbitrum bridge, there is a delay to ensure that the transactions being rolled up are confirmed. Information about this finality delay and potential methods to avoid it can be found in Arbitrum's documentation [here](https://developer.offchainlabs.com/docs/withdrawals).
-
-For more details on Arbitrum’s protocol, see their [complete documentation](https://developer.offchainlabs.com/docs/inside_arbitrum).
-
-## Introducing The Arbitrum Truffle Box
-
-The [Truffle Arbitrum Box](https://github.com/truffle-box/arbitrum-box) provides developers with the boilerplate structure necessary to start coding for Arbitrum’s Ethereum Layer 2 solution.
-
-We provide the initial building blocks to get started working on Arbitrum without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Arbitrum Networks.
-
-Arbitrum’s Layer 2 solution is almost fully compatible with the EVM. The main difference between the EVM and the Arbitrum chain that developers will notice is that some opcodes are different and concepts such as time and gas are handled a little differently. Developers can use their regular Solidity compiler to compile contracts for Arbitrum. You can see the complete list of differences between the Arbitrum L2 chain and Ethereum [here](https://developer.offchainlabs.com/docs/differences_overview).
-
-## Integration With Infura
-
-Our colleagues at Infura are also adding full API support for the Arbitrum network. Infura users can now add the free Arbitrum add-on directly in their Infura dashboard. The Arbitrum network API largely uses the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Arbitrum network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/).
-
-Infura endpoints for the Arbitrum chain are included in the configuration of the Arbitrum Truffle Box, to aid developers in getting fully acquainted with their options when developing for Arbitrum.
-
-## Where To Get Help
-
-You can find all of the documentation for the Truffle Arbitrum Box [here](https://github.com/truffle-box/arbitrum-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
-We are thrilled to add Arbitrum to the Truffle development suite and can’t wait to see the universe of applications built on Layer 2. Stay tuned as we continue to add more networks, features, and tools that accelerate and simplify development on a secure and scalable Ethereum.
diff --git a/src/blog/truffle-and-infura-support-optimism/index.md b/src/blog/truffle-and-infura-support-optimism/index.md
deleted file mode 100644
index 783de64ce..000000000
--- a/src/blog/truffle-and-infura-support-optimism/index.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Truffle and Infura Now Support Optimism
-hide:
-  - navigation
----
-
-![Truffle, Optimism Collab Image](/img/blog/truffle-and-infura-support-optimism/blog-header.png)
-
-Developer demand for scalable Ethereum application development tooling continues to grow. The multi-network Ethereum ecosystem is here, and Layer 2 solutions such as Optimistic Ethereum are leading the way. The Truffle team is delighted to support Optimistic Ethereum in helping developers build for this ecosystem. Today we are announcing the launch of the new Truffle Optimism Box.
-
-## Optimistic Ethereum
-
-Optimistic Ethereum is a Layer 2 scaling protocol for Ethereum applications. It is an application inside of Ethereum that executes transactions more efficiently than Ethereum itself, based on the concept of an [Optimistic Rollup](https://medium.com/plasma-group/ethereum-smart-contracts-in-l2-optimistic-rollup-2c1cef2ec537). The Optimistic Ethereum security model is backed by a system of “fraud proofs” that allow users to identify bad transaction results to support the accuracy of the data that is eventually rolled up and published to the main Ethereum chain. Transactions on Optimistic Ethereum are handled similarly to those on the Ethereum mainnet, and bridging between Optimistic Ethereum and mainnet Ethereum allows users to conduct gas-intensive operations on Optimistic Ethereum for a fraction of the cost.
-
-Optimistic Ethereum tracks closely to the structure and operation of the Ethereum mainnet, preserving security guarantees while increasing throughput and decreasing transaction costs. Important to note, this protocol requires a delay for bridging funds from Optimism back to Ethereum, and you can find more information about that [here](https://community.optimism.io/docs/developers/bridging.html#understanding-the-fraud-proof-window).
-
-Existing Solidity smart contracts can run on Optimistic Ethereum with minimal differences. Off-chain code such as user interfaces and wallets will need to update their RPC endpoints to interact with Optimistic Ethereum, and will largely just work once the update is made.
-
-For detailed documentation on the Optimistic Ethereum protocol, see [here](https://community.optimism.io/docs/protocol/protocol.html#introduction) and [here](https://community.optimism.io/docs/developers/integration.html).
-
-## Introducing the Truffle Optimism Box
-
-The [Truffle Optimism Box](https://github.com/truffle-box/optimism-box) provides developers with the boilerplate structure necessary to start coding for Optimism’s Ethereum Layer 2 solution.
-
-We provide the initial building blocks to get to work on Optimistic Ethereum without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Optimistic Ethereum networks.
-
-Optimism’s Layer 2 solution is almost fully compatible with the EVM, though it uses an “optimistic” EVM called the OVM. The main difference between the EVM and the OVM that developers will notice is that some opcodes are not available for contracts that are deployed to the OVM. The Truffle Optimism Box is complete with the Optimistic `solc` compiler already referenced in the `truffle-config.ovm.js` file. You can see a complete list of differences between Optimism’s fork of the `solc` compiler and the original [here](https://github.com/ethereum-optimism/solidity/compare/27d51765c0623c9f6aef7c00214e9fe705c331b1...develop-0.6).
-
-## Integration With Infura
-
-Our colleagues at Infura are also adding full API support for the Optimistic Ethereum network. Infura users can now add the free Optimism add-on directly in their Infura dashboard. The Optimism network API largely uses the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Optimistic Ethereum network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/).
-
-Infura endpoints for the Optimistic Ethereum chain are included in the configuration of the Optimism Truffle Box, to aid developers in getting fully acquainted with their options when developing for the Optimistic Ethereum chain.
-
-## Where to Get Help
-
-You can find all of the documentation for the Truffle Optimism Box [here](https://github.com/truffle-box/optimism-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
-
-We are thrilled to add Optimistic Ethereum to the Truffle development suite and can’t wait to see the universe of applications built on Layer 2. Stay tuned as we continue to add more networks, features, and tools that accelerate and simplify development on a secure and scalable Ethereum.
diff --git a/src/blog/truffle-and-infura-support-polygon/index.md b/src/blog/truffle-and-infura-support-polygon/index.md
deleted file mode 100644
index c77371d2a..000000000
--- a/src/blog/truffle-and-infura-support-polygon/index.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Truffle and Infura Now Support Polygon
-hide:
-  - navigation
----
-
-![Truffle, Infura, and Polygon Collab Image](/img/blog/truffle-and-infura-support-polygon/blog-header.png)
-
-The developer demand for scaling solutions that work directly with Ethereum is here and growing, so today we are very excited to launch the new Polygon Truffle Box. Ethereum-based dapp development is rapidly entering a new phase wherein a multi-network future is certain and Layer 2 solutions like Polygon's are leading the charge into this uncharted territory. Layer 2 scaling is essential to the health of the Ethereum ecosystem, and the Truffle team is delighted to support the Polygon PoS chain in helping developers build toward this future.
-
-## Polygon PoS Chain
-
-Polygon PoS is a hybrid Plasma Proof-of-Stake sidechain to the Ethereum mainnet which consists of a Tendermint consensus validator layer and a Plasma sidechain for block production. This configuration allows for higher transaction throughput, lower gas fees, and through Polygon's established bridges, easy connection back to the Ethereum mainnet.
-
-## Introducing the Polygon Truffle Box
-
-The core component of this new tooling is the [Truffle Polygon Box](https://github.com/truffle-box/polygon-box). This new Truffle box provides you with the boilerplate structure necessary to start coding for Polygon's Ethereum L2 solution, the Polygon PoS chain (previously the Matic PoS chain). For detailed information on how the Polygon PoS chain works, please see their documentation [here](https://docs.matic.network/docs/develop/getting-started).
-
-We provide the initial building blocks needed to get to work on Polygon PoS without pushing developers to write any particular sort of application. With this box, you will be able to compile, migrate, and test Solidity code against several instances of Polygon PoS networks.
-
-Polygon's L2 solution is fully compatible with the EVM. This means you will not need a new compiler to deploy Solidity contracts, and should be able to add your own Solidity contracts to this project. The main difference developers will encounter is in accessing and interacting with the Polygon PoS network. Additionally, Polygon offers multiple ways for dapp developers to implement communication between Ethereum ("Layer 1") and the Polygon PoS chain. Further information about how to enable Ethereum-Polygon communication can be found in the Polygon documentation [here](https://docs.matic.network/docs/develop/ethereum-matic/getting-started).
-
-_A quick note about naming: The Polygon ecosystem was previously called Matic Network. The chain to which we'll be deploying in the Polygon Truffle Box is now called the Polygon PoS chain. We have named this box the Polygon Box because we expect to include the ability to deploy to future Polygon chains in addition to what is presented in the initial Polygon Box, and developers using this Box may find themselves incorporating additional aspects of the Polygon ecosystem in their work._
-
-## Integration With Infura
-
-Our colleagues at Infura are also adding full API support for the Polygon network. Infura users can now add the free Polygon Network add-on directly in their Infura dashboard. The Polygon network API largely utilizes the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Polygon network. For more information on the full support check out the [complete documentation](https://infura.io/docs/ethereum#section/Network-Add-Ons/Polygon-PoS?&utm_source=infurablog&utm_medium=referral&utm_campaign=announcement&utm_content=polygon-launch).
-
-Infura endpoints for the Polygon PoS chain are included in the configuration of the Polygon Truffle Box, to aid developers in getting fully acquainted with their options when developing for the Polygon PoS chain.
-
-## Where to Get Help
-
-You can find all of the documentation for the Truffle Polygon box [here](https://github.com/truffle-box/polygon-box). If you have any questions, feedback, or just want to chat, reach out to us through the resources on our [community page](/community).
-
-We are very excited to add Polygon PoS to our development suite and we can't wait to see all of the amazing applications built with these tools. Stay tuned as we continue to add more networks, features, and products that accelerate and simplify development on this exciting new technology.
diff --git a/src/blog/truffle-boxes-making-life-sweeter/index.md b/src/blog/truffle-boxes-making-life-sweeter/index.md
deleted file mode 100644
index e498526e9..000000000
--- a/src/blog/truffle-boxes-making-life-sweeter/index.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Truffle Boxes - Making Life Sweeter
-hide:
-  - navigation
----
-
-When users begin developing on Ethereum, the first question they ask is, "Where do I start?". In the past, there hasn't been an easy answer: the answer generally consisted of many flavors of "it depends", and usually led to an investigation of what the user was trying to build, a general overview of their development skills, their knowledge of Ethereum, and the libraries and tools they're already most comfortable with. When determining how the Truffle team can help in this process, it quickly became apparent that what our users needed were examples. _Many of them._ So, being the upstanding community members we are, we set out to create those example, and today, we're happy to show you what we've accomplished.
-
-## Introducing Truffle Boxes!
-
-A Truffle box is an example Ethereum application and/or boilerplate that puts complimentary tools and libraries into a single, sweet, easily-downloadable package. Every Truffle box comes with libraries and tools already preinstalled, code that uses those libraries and tools, external scripts (if necessary), as well as helpful README's and documentation. All Truffle boxes are directly integrated into the Truffle command line, and you need only type `truffle unbox <box name>` to download and prepare your box of choice.
-
-**[Click here for a list of all available boxes.](/boxes)** Ensure you've installed the latest version of Truffle before opening your first box.
-
------------------
-
-Today's release comes with three officially-supported boxes, as well as one community-supported box. Our officially-supported boxes are:
-
-* [react](/boxes/react): A box that pairs Truffle with React in an easy to understand structure, meant for a web-based Ethereum application.
-* [react-auth](/boxes/react-auth): Our `react` box with extra goodies for authentication powered by smart contracts.
-* [react-uport](/boxes/react-uport): Like `react-auth`, but authentication is powered by Uport.
-
-Perhaps the most exciting part of this release -- our _pièce de résistance_ -- is the [Status Truffle box](/boxes/status), our first community-supported box. This box was created by the Status team, and instantly links Truffle and Status together with an example application and all the tools and libraries you need to build your own Status dapp.
-
-## Get Involved: Make Your Own Box
-
-We've released four boxes out of the gate to get you started, but this isn't just our candy store. **We want you to contribute** to the boxes on our site. If you have boilerplate code, an example dapp, a helpful integration or an exciting dapp stack (say, an Ethereum-enabled iOS app built with Truffle), send us an email at [boxes@trufflesuite.com](mailto:boxes@trufflesuite.com?subject=Truffle%20box%20review) and we'll look it over. If it's awesome, we'll list it on our site with your name front and center. If it's better than awesome, we'll help contribute and maintain it and make it an officially-supported Truffle box. With Truffle, you can share your code with others and help build the community, one box at a time.
-
-## One More thing...
-
-There's always one more thing. Fair warning, this one's techy. Right now, all the boxes you're seeing are static pages showing off what we and the Status team have built. Soon, however, we'll be taking on the ultimate challenge and will be creating a Truffle box registry, built on top of Ethereum, to help market and promote our community-supported boxes. Of course we'll be using Truffle, which adds a whole new layer of sweetness. Stay tuned for more details about the registry and how you can use the Ethereum blockchain to become a Truffle contributor.
-
-As always, we thank everyone for your support, and would love to hear from you. Don't hesitate to reach out on our [community Gitter channel](https://gitter.im/ConsenSys/truffle) where hundreds of your fellow Trufflers congregate to answer your questions.
-
-Cheers!
-
--- Tim & the Truffle Team
diff --git a/src/blog/truffle-teams-gets-a-new-look/index.md b/src/blog/truffle-teams-gets-a-new-look/index.md
deleted file mode 100644
index 04b209ab6..000000000
--- a/src/blog/truffle-teams-gets-a-new-look/index.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Truffle Teams Gets a New Look!
-hide:
-  - navigation
----
-
-![Truffle Teams Redesign Banner](/img/blog/truffle-teams-gets-a-new-look/banner.png)
-
-Thanks to [Josh Quintal](https://github.com/DiscRiskandBisque) and [Heyse Li](https://github.com/honestbonsai), the redesign of Truffle Teams is complete! Josh presented the [Theobromine design system at TruffleCon 2019](https://www.youtube.com/watch?v=aoU710h38xE&t=1m47s), and this release is the first step towards this vision! In addition to the stylistic upgrade, we've redesigned the app navigation to help you focus on a single repository at a time.
-
-Read more below about the most recent changes, or [go check them out for yourself](https://my.truffleteams.com)!
-
-## Redesign
-
-The Theobromine Design System uplifts the entire Truffle Teams application. This lighter theme makes the application feel more welcoming and presents itself more as a professional productivity tool.
-
-![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-builds.png)
-
-We also added support to collapse the left navbar to give you some more screen real estate. This is super helpful for those with small or vertical screens; it’s also instrumental for multitaskers that use Truffle Teams in a split-screen setup.
-
-![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-build-detail.png)
-
-## Navigation Updates
-
-The previous iteration of Truffle Teams utilized a "feature first" navigation where you would select the feature you'd like to see (Builds, Deployments, Monitoring [formally known as Data]) and then select the repository you'd want to drill into. We found this to be a jarring and tedious experience, so we changed things to be "repository first".
-
-When you login, you'll now see a home page with a list of your repositories. You can quickly search for a repository or keep your favorites at the top of the list by pinning them.
-
-![Teams Redesign - Home Page](/img/blog/truffle-teams-gets-a-new-look/teams-home.png)
-
-After clicking on a repository you'll be presented with the details of that repository. On the Builds page you'll now see a history of your builds rather than seeing the list of your repositories. The Deployments and Monitoring pages will look familiar as they haven't changed much other than not having to select the repository again.
-
-![Teams Redesign - Builds Page](/img/blog/truffle-teams-gets-a-new-look/teams-redesign-builds.png)
-
-Want to focus on a different repository? You can quickly switch between them using the breadcrumb dropdown at the top of each page.
-
-![Teams Redesign - Breadcrumb Dropdown](/img/blog/truffle-teams-gets-a-new-look/teams-repo-breadcrumb.png)
-
-You can also click the Truffle Teams logo in the top left to go back to the home page with the search bar and pinned repositories.
-
-![Teams Redesign - Logo in Top Left](/img/blog/truffle-teams-gets-a-new-look/teams-logo-to-home.png)
-
-## Got Feedback or Questions?
-
-If you aren't aware of our official support channel, head over to [the Truffle Teams channel in Spectrum.chat](https://spectrum.chat/trufflesuite/truffle-teams). Posting a thread there will ping us in our internal Slack workspace and we'll answer you ASAP. You can also submit Truffle Teams feature requests and issues [on GitHub](https://github.com/trufflesuite/truffle-teams/issues).
-
-<div class="post-trufflecon-box mt-5 text-center">
-  Get started with Truffle Teams, and see the redesign for yourself!
-
-  <div class="mt-3">
-    <a class="btn btn-truffle" href="/docs/teams/getting-started/creating-an-account">Try Truffle Teams</a>
-  </div>
-</div>
diff --git a/src/blog/truffle-teams-now-supports-private-repositories/index.md b/src/blog/truffle-teams-now-supports-private-repositories/index.md
deleted file mode 100644
index 04589a051..000000000
--- a/src/blog/truffle-teams-now-supports-private-repositories/index.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Truffle Teams Now Supports Private Repositories
-hide:
-  - navigation
----
-
-Thanks to the awesome work of [@nicholasjpaterno](https://github.com/nicholasjpaterno), you can now integrate private repositories with Truffle Teams! This will eventually be a premium feature, but we're releasing it for free while the product is still in beta.
-
-## Using Private Repos
-
-<figure>
-  <img src="/img/blog/truffle-teams-now-supports-private-repositories/tt-private-repo-badge.png" alt="Example of Truffle DB" style="width:100%; box-shadow: 0px 3px 5px 0px rgba(0,0,0,0.25);">
-  <figcaption>Here we see the lock icon denoting a private repository and an indication of this being a future premium feature.</figcaption>
-</figure>
-
-There are no extra steps to use your private repositories with Truffle Teams! Simply [add your repo](https://github.com/apps/truffle-teams), and automatic builds should start working! Private repos will have a lock icon next to their name indicating their private status. Otherwise, they have the same functionality as public repos.
-
-You'll see that we're very loud about which features will be premium. We'll continue this practice for future premium features so that we stay transparent about what's to come.
-
-## Next Up: Deployments!
-
-Here's a teaser of our next upcoming feature: Graduated Deployments.
-
-<figure>
-  <img src="/img/blog/truffle-teams-now-supports-private-repositories/tt-deployments.png" alt="Example of Truffle DB" style="width:100%; box-shadow: 0px 3px 5px 0px rgba(0,0,0,0.25);">
-  <figcaption>The main deployments screen showing successful testnet and mainnet deployments.</figcaption>
-</figure>
-
-You'll be able to deploy any commit with a successful build to Ropsten, Rinkeby, and Mainnet Ethereum networks (with more to come soon!). You'll get some useful contextual information for your deployments: the status of the deployment, when it took place, who on your team deployed it, the contracts deployed, the ability to download your Truffle Artifacts, and more.
-
-Deploy to the Staging environment (Ropsten and Rinkeby currently) to make sure everything works out. Once you're ready, you can easily graduate a deployment in Staging to Production (Mainnet currently). We're using `truffle migrate` under the hood, so your existing migration scripts will work just fine.
-
-We've distilled the deployment process into an informative and helpful wizard to guide you through the deployment process. With this wizard and leveraging [MetaMask](https://metamask.io) for signing transactions, we are finally giving you an interface that makes it easier to deploy for seasoned and new devs alike!
-
-We'll release a full article with all the details about using Truffle Teams' deployment features once it's ready for release.
-
-Thank you and happy truffling!
\ No newline at end of file
diff --git a/src/blog/truffle-v5-has-arrived/index.md b/src/blog/truffle-v5-has-arrived/index.md
deleted file mode 100644
index d99e291d3..000000000
--- a/src/blog/truffle-v5-has-arrived/index.md
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: Truffle v5 has arrived!
-hide:
-  - navigation
----
-
-We have just released the most awaited version of Truffle just in time for the
-holidays! There are SO many exciting things that we would like to mention that
-will make your Truffle experience a rich one. Highlighted below are the new
-exciting things Truffle has to offer.
-
-👯    [Download Truffle v5](/truffle) or check out the
-full [Release Notes](https://github.com/trufflesuite/truffle/releases/tag/v5.0.0).    👯
-
-- **Bring your own compiler!** You can now choose any solc-js version
-  available at solc-bin. Just tell Truffle which version you want to use and it
-  will automatically fetch it for you! This feature also includes the ability to
-  use Docker and native binaries in an advanced way.
-
-- **Web3 1.0** - The truffle-contract package is now using Web3.js 1.0! This
-  will greatly improve error handling!
-
-- **New migrations command** - In v5, the `migrate` command has been completely
-  rewritten. We have included better error messages: e.g., when a deployment fails
-  Truffle will notify you and give you an idea of possible fixes. Truffle will
-  now also give you more information about what is going on when you deploy a
-  contract. This includes cost summaries and real time status updates about the
-  amount of time a transaction has been pending.
-
-  Dry run simulations also now run automatically if you are deploying to a known
-  public network and using the `--interactive` flag on the command line will give
-  you a prompt between dry runs and real deployments.
-
-  Another improvement is the ability to configure the amount of block confirmations
-  in between deployments. This allows the user to specify the number of blocks to
-  wait before transactions time out.
-
-- **Usage analytics** - Usage analytics have been added and users can opt-in by
-  running `truffle config --enable-analytics`. We think this feature will be a
-  vital tool that will help us to make informed decisions about the future of Truffle
-  and to determine what is most valuable to our users. When enabled, Truffle will
-  collect information about your version number, the commands you run, and
-  whether commands succeed or fail. And of course, it will do so in an anonymous
-  fashion.
-
-- **`truffle run <command>`** -  Truffle now gives users the ability to create
-  custom command plugins. This feature is still in its infancy so let us know
-  what you think!
-
-- **Vyper support** - Another added feature is that Truffle will now compile
-  `*.vy` contracts. We have published a Truffle Box to help you get started
-  with Vyper. You can access it by running:
-
-  ```shell
-  $ truffle unbox vyper-example
-  ```
-
-  (Make sure you have [Vyper](https://vyper.readthedocs.io/en/latest/installing-vyper.html) installed.)
-
-- **Solidity v0.5.0** - Truffle also now ships with Solidity v0.5.0 by default.
-  Solidity v0.4.xx is still supported and can be used by specifying the version
-  you wish to use in your Truffle config.
-
--  **Structured function parameters** - Truffle has been upgraded to use
-   Web3.js v1.0. This has allowed us to include support for passing/returning
-   ‘struct’s in Solidity functions. To use this ability, you need to specify the
-   following at the top of your contracts:
-
-  ```solidity
-  pragma experimental ABIEncoderV2
-  ```
-
-  This feature allows you to use complex function arguments and have the values
-  returned so that they can interact with other contracts via truffle-contract’s
-  JS interface.
-
-- **Help system** - Now access Truffle’s built in help system by running:
-  ```shell
-  $ truffle help <command>
-  ```
-
-  This allows you to see all the available options for the command as well as a
-  description of what it does.
-
-- **Unique `truffle develop` mnemonics** - Truffle will now generate random mnemonics
-  that will persist only for you. Use caution with crypto security when working
-  with mnemonics and private keys!
-
-- **Debugger improvements** - v5 includes debugger breakpoints! Add breakpoints
-  using the ’b’ command and remove them using the ‘B’ command. Additionally we
-  have added mapping support for the debugger!
-
-- **`truffle init` / `truffle unbox`** - These commands have been improved and
-  you are now asked if you want to overwrite files in the case of name conflicts
-  in the target directory. A force option (--force) has also been added in the
-  case where you wish to overwrite the files automatically and avoid the
-  prompt.
-
-- **`async`/`await`** - Support for async/await syntax in the Truffle console
-  is also now available!
-
-Looking towards the future we intend to add third-party plugins and
-hope through our fancy, improved analaytics to provide features the community
-needs most!
-
-![V5 Breaking Changes](/img/blog/truffle-v5-blog-media/breaking-changes-photo-v5.png)
-
-**Thank you to all who have helped make this release of Truffle possible! We
-hope you enjoy this new Truffle release and ask that you let us know if you have
-any suggestions or problems on our community Gitter channel or on our GitHub
-page!**
-
-[Get started with Truffle v5 today!](/truffle)
diff --git a/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md b/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
deleted file mode 100644
index af065564b..000000000
--- a/src/blog/try-new-features-first-with-truffle-teams-early-access/index.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Try New Features First with Truffle Teams Early Access
-hide:
-  - navigation
----
-
-![Truffle Teams Early Access Banner](/img/blog/try-new-features-first-with-truffle-teams-early-access/blog-header.png)
-
-Truffle Teams is constantly evolving. Between adding new features, polishing, and refining the app there's so much we'd love to share with the world in a faster way. Wouldn't it be nice to take those new enhancements and features for a test drive? Now you can with early access!
-
-</div></div></div>
-
-<figure class="breakout">
-  <img class="mb-4 w-100 figure-shadow" src="/img/blog/try-new-features-first-with-truffle-teams-early-access/early-access-1.png" alt="Enabling Early Access from the settings screen">
-  <figcaption class="text-center font-italic">Enable early access with just one click!</figcaption>
-</figure>
-
-<div class="container container-post"><div class="row justify-content-center"><div class="col">
-
-## How Early Access Works
-
-To join early access, select the Early Access option in the Advanced tab via the account Settings Page. This account will now have access to new features and enhancements we're cooking up. First up is a hotly anticipated feature--the debugger, [which you can learn more about here](/blog/debug-quickly-and-in-context-with-truffle-teams-new-debugger).
-
-We'll provide a helpful reminder as to where you can provide feedback and request support. Your feedback is one of the most important parts of this process, and we're excited to hear from you in the earlier phases of development!
-
-Want to switch back to the stable track? You can disable Early Access at any time, but anything that requires data storage will be erased.
-
-We hope you enjoy getting a taste of what's to come!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT TRUFFLE TEAMS EARLY ACCESS</a>
-</div>
-
-## Continue the Conversation
-
-We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven't met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Head of Product & Marketing_
diff --git a/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md b/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
deleted file mode 100644
index 47cf621d7..000000000
--- a/src/blog/unwrap-the-corda-flavored-ganache-beta/index.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Unwrap the Corda Flavored Ganache Beta
-hide:
-  - navigation
----
-
-![Truffle Teams Deployments Banner](/img/blog/unwrap-the-corda-flavored-ganache-beta/corda-ganache-beta-blog-banner.png)
-
-Earlier this year at TruffleCon [we announced our partnership with Corda to develop a Corda Flavored Ganache](https://youtu.be/MtOaXVt1yOE?t=697). Then, at CordaCon in London [we shared more details around the integration](https://www.r3.com/videos/truffle-and-corda/).
-
-**Today, we are proud to share with you [the beta release is live](https://github.com/trufflesuite/ganache/releases/tag/v2.3.0-beta.1)!**
-
-As a quick refresher: Ganache is Truffle's "one click blockchain" that allows you to run a test network for local development. You don't need an internet connection and because it's all on the same machine, Ganache allows users to see the status of the network in greater detail than on a live network.
-
-<figure>
-  <img src="/img/blog/unwrap-the-corda-flavored-ganache-beta/corda-ganache-beta-screenshot.png" alt="Corda Flavored Ganache startup screen" style="width:100%">
-  <figcaption class="text-center">The workspace selection screen--now with Corda!</figcaption>
-</figure>
-
-We're thrilled to release Ganache for the Corda Blockchain, as this lowers the barrier of entry for Corda developers by allowing them to easily set up a local network on their machines, giving introspection into the state of that network across various nodes and visibility to transactions normally hidden by a live Corda network's privacy protections.
-
-With the Beta version, Corda Flavored Ganache brings you:
-
-* **One-click** Corda network configuration and initialization, so you can focus on what matters most: your application.
-* **Easy access** to all your application's data, including network map, notaries, nodes, transactions, and states.
-* **Multiple workspaces** for all of your Corda projects; workspaces contain configurations of a Corda network map, notaries, nodes, transactions, accounts, and ledgers.
-
-As always, Truffle's tools come standard on Windows, macOS, and Linux.
-
-We are excited to share this with the Corda community and **we also need to your help!** Since this is a Beta release, we know it's not perfect. If you find a bug, do us a favor and file an issue [here](https://github.com/trufflesuite/ganache/issues/new).
-
-<a href="https://share.hsforms.com/1jbMAfLzGSj6HWx_-na9Bew34pbp">✉️ Sign up for the Corda Flavored Ganache mailing list here</a> to get the latest updates on all things Ganache + Corda.
-
-If you don't hear from us immediately, know that our team is taking some much needed time off starting today. We'll be back January 6th, 2020 ready to dive into your feedback! 
-
-If you see them around the net, make sure to give a _**HUGE thank you**_ to [David Murdoch and Nick Paterno](/staff). Their hard work made this all possible and we're a very fortunate organization to have them aboard! 💖
-
-<div class="post-trufflecon-box mt-5 text-center">
-  Try the Corda Flavored Ganache beta and let us know what you think!
-
-  <div class="mt-3">
-    <a class="btn btn-truffle" href="https://github.com/trufflesuite/ganache/releases/tag/v2.3.0-beta.1">Download Corda Flavored Ganache</a>
-  </div>
-</div>
\ No newline at end of file
diff --git a/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md b/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
deleted file mode 100644
index ab0f471f0..000000000
--- a/src/blog/upcoming-improvements-to-encoding-and-decoding/index.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Upcoming improvements to encoding and decoding
-hide:
-  - navigation
----
-
-When you’re writing, running, or debugging your smart contract, you don’t want to have to deal with raw binary data. Truffle––and Ganache and Drizzle––already contain a number of encoding and decoding features to help you interact with your contract and understand what you’re seeing. But luckily, encoding and decoding are about to become even more robust, informative, and usable.
-
-Not all of these features will be immediately available in Truffle 5.1, but some will, so let’s start with one that will be ready! Allow me to illustrate:
-
-![Syntax Highlighting](/img/blog/upcoming-improvements-to-encoding-and-decoding/syntax-highlighting.png)
-
-Yes, debugging displays are about to become quite a bit more colorful! And though it’s not related to decoding, yes that is `syntax highlighting` in the debugger! Of course, it’s not just a matter of color. Previously, many data types displayed inappropriately as strings, and enums displayed as objects. Now, each data type will be displayed in a form (and color) that makes sense, making them recognizable at a glance. No longer will a function be confused for a string!
-
-![Contracts and External Functions](/img/blog/upcoming-improvements-to-encoding-and-decoding/contracts-and-external-functions.png)
-
-Of course, this wouldn’t be possible without our new, more machine-readable, decoder output format. This one’s a little technical, and it’s not something you’re likely to find yourself dealing with directly -- you probably aren’t using Truffle Decoder directly. But Ganache and Drizzle both make use of it, and as they update to incorporate the new format, you’ll be able to get a better view of the state of your contracts with them.
-
-But that’s not all; we’re also intending to eventually integrate these encoding and decoding features into Truffle Contract. This will allow you to send transactions and decode events that you currently can’t!
-
-For instance, Vyper contracts support decimal fractions as a datatype, but our current encoder and decoder, and the ethers library, do not support these. If you want to send a transaction (or if your contract emits an event) that takes a decimal fraction as input, you are going to run into trouble. With our upcoming encoding and decoding improvements, this should no longer be a problem. (Or, for something of more concern to our Solidity users, the same applies to external function pointers.)
-
-Finally, I’d like to discuss decoding of events. Currently, when you check what events your contract may have emitted recently, you may have trouble decoding events emitted by libraries. Our new decoder, though, will be able to handle these just fine. It will even handle anonymous events! That may seem impossible, but hey, that hasn’t deterred us.
-
-We’re hoping Truffle’s new encoder and decoder will make staring at raw binary data a thing of the past! Unless you like to, of course. But for those of you who’d prefer to take a higher-level view and deal directly with what that binary data actually means… well, that’s what Truffle’s for, isn’t it?
diff --git a/src/blog/using-the-ens-integration/index.md b/src/blog/using-the-ens-integration/index.md
deleted file mode 100644
index 7622ce13d..000000000
--- a/src/blog/using-the-ens-integration/index.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: Using Truffle's ENS Integration
-hide:
-  - navigation
----
-
-**By Tyler Feickert, Blockchain Tools Engineer at Truffle**
-
-Among the new features released with Truffle 5.1 is support for Ethereum Name Service
-(ENS) name resolution and setting the resolver address for owned names!
-
-ENS is a system that allows for the resolution of Ethereum addresses using
-human-readable names. Like DNS, ENS aims to simplify working with addresses and
-allowing us to work with names like "truffle.eth" in place of things that cumbersomely
-resemble something like `"0x1234567890123456789012345678901234567890"`. Are you
-sure you copied that address correctly? Ready to send your Ether there?
-
-In ENS, a contract called a registry is deployed to a network. The ENS team has
-deployed a registry contract to Mainnet and several test networks. These are the
-registries that Truffle connects to by default if no registry address is set
-in the Truffle config.
-
-An ENS registry contract contains a list of names and who owns them. Each name
-also points to a resolver contract if one is set. Addresses own ENS names and
-have the ability to set the resolver that a given name points to. The resolver
-is the contract responsible for returning an address for resolution. The
-idea is that the owner will have the ability to set the resolver contract
-to return the desired address.
-
-For more detailed information on ENS, check out the [ENS website](https://ens.domains/).
-
-So we at Truffle think this project is pretty awesome and, as mentioned above,
-built an integration with it. Previously in your migrations, for example, you
-needed to manually deal with addresses. So maybe you wanted to send some
-tokens from your contract to another address. In your Truffle migration you
-might have the following code:
-
-```javascript
-await myTokenContract.sendTokens(
-  999,
-  "0x1234567890123456789012345678901234567890",
-  { from: "0x0987654321098765432109876543210987654321" }
-);
-```
-
-It is difficult and tiring to deal with raw addresses like this.
-
-Now in Truffle, if you turn on the ENS name resolution and you have a
-resolver set to your address of choice, you can do something like the
-following in place of the above:
-
-```javascript
-await myTokenContract.sendTokens(
-  999,
-  "truffle.eth",
-  { from: "my.account" }
-);
-```
-
-Well, that seems much easier to read. Under the hood during the migrations,
-Truffle will connect to the on-chain registry and automatically resolve the
-addresses for both "truffle.eth" and "my.account". You now can use
-valid ENS names in place of addresses in your migrations! In other
-words, any place that an address is expected for an argument to a
-function call, you can instead provide the ENS name.
-
-One other big piece of functionality for this ENS integration is the ability to set
-the resolution address for owned ENS addresses. You can do this using
-`deployer.ens.setAddress` in your migrations.
-
-Suppose I control an address that owns the name "arnold.hagenchop.eth" and I
-want to set the address to "0x1234123412123412341212341234121234123412". In
-this case I would write something like the following in my migration:
-
-```javascript
-const myAddress = "0x1234123412123412341212341234121234123412";
-await deployer.ens.setAddress(
-  "arnold.hagenchop.eth",
-  myAddress,
-  { from: "0x8888888888888888888888888888888888888888" }
-)
-```
-
-Now let's take a step back and look at what we did. So you can see that the
-`setAddress` method has three arguments. The first one is the name that we'd
-like to set the resolver for. As stated above we want to set the resolver
-address for "arnold.hagenchop.eth". The second argument is the address to set
-for the given name's ENS resolution. The last one is an object that resembles
-a transaction parameter object. The important thing about this object is
-that it must have a `from` property with the address that controls the name
-given as the first argument. This is important or the transaction will fail!
-
-You can find some more information about registering ENS names from the
-[ENS website](https://ens.domains/).
-
-One other useful convenience with this method is that you can also provide
-a Truffle contract object that has a deployed address as the second argument
-if you'd like. So the above code might look like the following instead:
-
-```javascript
-const MyContract = artifacts.require("MyContract");
-const myContract = await MyContract.deployed();
-await deployer.ens.setAddress(
-  "arnold.hagenchop.eth",
-  myContract,
-  { from: "0x8888888888888888888888888888888888888888" }
-)
-```
-
-In that case, "arnold.hagenchop.eth" will be set to the address at which
-`myContract` is deployed!
-
-This new integration should just be the start of a much more robust system that
-allows Truffle projects to interact with ENS! In the future, we also hope
-to add other features such as reverse resolution (resolving a name from an
-address) and automatic name registration where possible. We think this will
-be a big step forward in making the Ethereum ecosystem more accessible as well
-as convenient to work with!
-
-For more thorough information about this integration, see the
-[Truffle docs](/docs/truffle/advanced/ethereum-name-service).
-We have also created an
-[example Truffle box](https://github.com/truffle-box/v5.1-example-box#v51-example-box)
-that has some examples of using this new ENS integration alongside other new
-Truffle v5.1 features. We hope you find this feature as useful as we think
-it is! Happy Truffling!
diff --git a/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md b/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
deleted file mode 100644
index 2d4ad069e..000000000
--- a/src/blog/using-truffle-to-interact-with-chainlink-smart-contracts/index.md
+++ /dev/null
@@ -1,102 +0,0 @@
----
-title: Using Truffle to interact with Chainlink Smart Contracts
-hide:
-  - navigation
----
-
-![Truffle + Chainlink](/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/chainlink-az.png)
-
-Chainlink is one of the leading blockchain projects building the very first decentralized oracle network that provides external data to smart contracts. Truffle helps smart contract developers by providing a powerful framework to create, test, and deploy smart contracts. In Chainlink’s blog [post](https://blog.chain.link/how-to-use-chainlink-with-truffle-2/), their [Chainlink Truffle Box](https://github.com/smartcontractkit/chainlink/tree/master/evm/box) has gotten some significant upgrades! If you were fortunate enough to attend Trufflecon 2019, then you have already seen these improvements in action, thanks to Chainlink’s presentation by Thomas Hodges. To start developing your very own Chainlink smart contracts, you can grab Chainlink’s Truffle Box by following the guide [here](https://blog.chain.link/how-to-use-chainlink-with-truffle-2/).
-
-This article will showcase these brand new additions, starting with [Truffle Scripts](/docs/truffle/getting-started/writing-external-scripts). Scripts create a much easier approach to interact with our contracts, allowing us to fund a contract with LINK, request data from it, and read the contract’s data with only three commands. To demonstrate this functionality, we will first need to set up our environment variables: MNEMONIC and RPC_URL.
-
-Working with blockchain technology requires a wallet, with one of the most popular choices being [MetaMask](https://metamask.io/). Within minutes, you can have your very own Ethereum wallet that allows you to easily interact with various dApps. During account generation, you will be shown your **_secret_** 12-word seed phrase, known as your mnemonic. (Do not share this with anyone; if someone knows your _mnemonic_ they WILL have access to your addresses and private keys). Be sure to store this mnemonic somewhere safe, as you will need it later to work with our example.
-
-Furthermore, you will also need to fund your MetaMask wallet with [test LINK](https://ropsten.chain.link/) and [test ETH](https://faucet.ropsten.be/), in order to power transactions on the Ropsten Ethereum Testnet.
-
-_Note: When funding your account from a test faucet, make sure you switch from the default Main Ethereum Network to the Ropsten Test Network, to properly see your funds. You can follow any transactions made on the Ropsten Testnet via Etherscan._
-
-Our second environment variable will require an RPC URL. Some popular RPC connectivity services include [Infura](/guides/using-infura-custom-provider), [LinkPool](https://www.linkpool.io/), and [Fiews](https://fiews.io/free-rpc). After establishing a valid RPC connection and the funded address, you can start deploying smart contracts to public networks.
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/01.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>_Shown above are the environment variables needed to link your MetaMask wallet to Truffle, found in truffle-config.js._</figcaption>
-</figure>
-
-Once you have all the data you need, you can set your environment variables via the terminal commands:
-
-```shell
-export RPC_URL=your_url_here
-export MNEMONIC=’your 12 words here’
-```
-
-## Migration
-
-We are now ready to deploy our smart contract on a public network. To begin, run the command:
-
-```shell
-npm run migrate:live
-```
-
-This will compile all of your smart contracts, and then start deploying (migrating) them.
-
-_Note: you may encounter some compilation warnings with the Chainlink contracts. This is simply because the LINK token was originally deployed with an older version of Solidity. Given that this contract is only being deployed when you run tests, these can be ignored._
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/02.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>_Console output of one of our contracts deploying. This particular transaction can be found [here](https://ropsten.etherscan.io/tx/0x4c8125f0e074ce3f65b08f67f9685a0d00c2985c6ebd372507016d78c344d25b)._</figcaption>
-</figure>
-
-Deploying our `Migrations` and `MyContract` cost us Ethereum, hence why we needed the faucet from earlier. Now that our contract is deployed, we can utilize the three helper scripts to fund `MyContract` with LINK (which we got from the Chainlink faucet), create requests, and read the state.
-
-There are 3 helper scripts provided to interact with our contract, located in the scripts directory:
-
-* `fund-contract.js`
-* `request-data.js`
-* `read-contract.js`
-
-They can be used by calling them from `npx truffle exec`. First, we must fund our contract with LINK, which can be done by running the following command:
-
-```shell
-npx truffle exec scripts/fund-contract.js --network live
-```
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/03.png" alt="Truffle DB data model" style="width:100%">
-</figure>
-
-Following deployment, the output displays our contract address as well as the transaction address. We can also look this up on the ropsten [explorer](https://ropsten.etherscan.io/tx/0x39e48b6d8170060affdb57baf8b794424f83296aa9e105163113fea08d300504).
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/04.png" alt="Truffle DB data model" style="width:100%">
-</figure>
-
-Notice that upon completion, a payment of 1 LINK was sent during the transaction, clearly indicating that our contract has properly been funded. Next, we can now `request data` from the contract by running:
-
-```shell
-npx truffle exec scripts/request-data.js --network live
-```
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/05.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>_In the Chainlink explorer for the network that you made the request (in our example we use Ropsten, but it would work similarly for Rinkeby, Kovan, and Mainnet). As you can see the Chainlink node that we were requesting data from picked up our request and waited for 3 block confirmations before executing the job. We are now ready to read the contract’s state with the written answer from the Chainlink node, indicated by the fulfillment transaction (highlighted in red)._</figcaption>
-</figure>
-
-And finally, for reading the data we run our read-contract script. In particular, this will run faster because we’re not creating a transaction, we are simply reading the current state of the smart contract.
-
-```shell
-npx truffle exec scripts/read-contract.js --network live
-```
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/06.png" alt="Truffle DB data model">
-</figure>
-
-Notice for our output when reading the data, we get a number displaying the current price of LINK in USD * 100 (as of writing, 22094). This is due to the value of times specified in our smart contract request-data.js.
-
-<figure>
-  <img src="/img/blog/using-truffle-to-interact-with-chainlink-smart-contracts/07.png" alt="Truffle DB data model" style="width:100%">
-  <figcaption>_Request-data.js. TRUFFLE_CL_BOX_TIMES is an environment variable which is used to override the default value of 100. This value is used for the precision of the endpoint’s response (in this case, for the price of ETH in USD), and also because Solidity cannot handle decimals. Any of these values can be changed for your project._</figcaption>
-</figure>
-
-Thanks to the power of Truffle, it has never been easier to work with smart contract development. We hope you enjoyed working with our Chainlink Truffle Box, allowing you to fully test, deploy, and interact with contracts on the network. Thanks for reading, and stay tuned for future updates at [https://blog.chain.link/](https://blog.chain.link/).
\ No newline at end of file
diff --git a/src/blog/why-i-love-trufflecon/index.md b/src/blog/why-i-love-trufflecon/index.md
deleted file mode 100644
index 581371614..000000000
--- a/src/blog/why-i-love-trufflecon/index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Why I love TruffleCon
-hide:
-  - navigation
----
-
-**By Josh Quintal, Head of Product & Marketing**
-
-The blockchain space is hitting a plateau.
-
-It’s not a bad thing: new technologies encounter a series of plateaus and this one's no different. It’s a good time to reflect and mature the ecosystem without the noise brought by rapid growth. We're in a crucible period not seen since the tech boom of the 90s. The early adopters are all here forging the blockchain-enabled world, readying for the next influx of users and companies.
-
-Remember when your friends and family raised eyebrows about this chainblock (or whatever) or thought Bitcoin was some kind of scam? Isn't that used to buy drugs? 😳 Now blockchain technology is becoming more efficient, more ubiquitous, and more accessible with each passing day. Now we hear things like "blockchain is the future" coming from outside our community.
-
-Almost two years ago when Truffle reached 4 people and that future seemed less sure, we were on our second retreat at a little place in Yakima. We mused about putting on a blockchain developer conference. Would people actually go? Who's going to speak? Can we get enough content? A few months later we decided to give it a try. Wow, people showed up--and not just that--they loved it! So many great conversations, so much valuable knowledge! Talks about smart contract upgrades, novel uses of merkle proofs, and data storage with IPFS just to name a few. A quietly skeptical Dave Burela (Blockchain Dev, MSFT and TruffleCon 2018 speaker) noted afterwards "You actually pulled it off". 🙂
-
-This year we have over 60 speakers across 60 sessions including: Thomas Hodges on Decentralized Oracles: Reliably Triggering Smart Contracts using Decentralized Computation using Truffle, Alejandro Banzas on RSK Integration with Ganache, and Greg Kapka on Developing Data-Rich Smart Contracts via Provable (Oraclize 2.0).
-
-TruffleCon is a conference, sure, but it's more than that: it's the feeling of excitement when learning a new technology; the eureka we felt when first discovering this new frontier. It's connections made in minutes that can last a lifetime.
-
-It's the culmination of everything we've worked for since the founding of this company.
-
-I hope to not only see you there but to have a chat about what we do well and how we can improve (you'll also get a hat). Together we're building the community that will take us from this plateau onward to the next meteoric growth spurt.
-
-Sincerely,
-
-<p>
-  <img style="margin-left: 0 !important; margin-bottom: 0 !important;" src="/img/blog/why-i-love-trufflecon/josh-signature.png" title="Josh Quintal Signature" alt="Josh Quintal Signature" width="150px">
-</p>
-
-Josh Quintal
diff --git a/src/blog/why-were-organizing-trufflecon-2018/index.md b/src/blog/why-were-organizing-trufflecon-2018/index.md
deleted file mode 100644
index 3e366cf80..000000000
--- a/src/blog/why-were-organizing-trufflecon-2018/index.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Why We're Organizing TruffleCon 2018
-hide:
-  - navigation
----
-
-![TruffleCon 2018](/img/blog/why-were-organizing-trufflecon-2018/trufflecon2018header.jpg)
-
-As you have hopefully heard by now, [TruffleCon](/trufflecon2018), Truffle's first-ever user conference, will be on [October 5-7, 2018 in Portland, Oregon, U.S.A](/trufflecon2018).
-
-<p class="m-b-2">
-  <a href="https://trufflecon2018.eventbrite.com" class="btn btn-eventbrite m-t-1" target="_blank">Buy Tickets!</a>
-</p>
-
-## Why TruffleCon?
-
-There is certainly no shortage of conferences related to Ethereum. [Ethereal](https://etherealsummit.com) recently wrapped up in New York City, and [Devcon4](https://devcon4.ethereum.org) is ramping up in Prague later on this year. There's also [EDCON](https://edcon.io), [EthCC](https://ethcc.io), and plenty more, especially when you count those that intersect with the larger blockchain space.
-
-And yet, these events usually have a focus on the larger ecosystem. What about the people who are deep in the trenches, building the dapps and deploying the contracts?
-
-**We want TruffleCon to be the place for people who are doing the building.**
-
-Also, many developers are working in silos, connected to other teams only by GitHub, Gitter, StackExchange, Reddit, or other "[weak ties](https://en.wikipedia.org/wiki/Interpersonal_ties)". **We want to strengthen those connections to bring people together**.
-
-We want people to share their ideas, and talk about their successes and challenges. We want people to promote their projects, of course, and professional networking is always a part of these events, but more than anything else, **we want people to be heard**.
-
-## Why now?
-
-We've noticed a shift over the past year or so in the usage of Truffle.
-
-Whereas many of the comments and requests in [our Gitter channel](https://gitter.im/ConsenSys/truffle) and GitHub issues were originally regarding local tests, and in sandboxes, we noticed more and more people deploying their contracts to the public test networks and even the mainnet. While this, of course, was always the intention, it shows that **confidence in our tools and the Ethereum ecosystem is growing**.
-
-**We want to help people "go live".** And so we believe that there has never been a better time than now.
-
-## Why Portland?
-
-Portland is a vibrant city full of world-class food and drink, unmatched outdoor opportunities, and an excellent transportation system for getting where you need to go. And early October is typically a sweet spot where the days are still warm and dry, while the fall colors are starting to come into view.
-
-If you've never been, you're missing out. And why not stay awhile once you're here?
-![TruffleCon 2018](/img/blog/why-were-organizing-trufflecon-2018/portlandskyline.jpg)
-*Photo courtesy of Flickr/sama093. [Large version here](https://flic.kr/p/qg3nwJ).* 
-
-## See you in October!
-
-From Truffle founder Tim Coulter:
-
-<blockquote><em>"The best conference we could put on is one where there's a ton of active engagement. I want people to feel like they are surrounded by other people who can help them. And I want them to leave feeling like they learned something and that the Truffle community is better off because they were there.<br/><br/>
-
-If we do it right, people will go home inspired, and will change how they do their development."</em></blockquote>
-
-We can't wait to see you there. If you have questions, feel free to tweet us at [@trufflesuite](https://twitter.com/trufflesuite). And please use the hashtag [#TruffleCon](https://twitter.com/search?l=&q=%23TruffleCon&src=typd).
-
-<p class="m-b-2">
-  <a href="https://trufflecon2018.eventbrite.com" class="btn btn-eventbrite m-t-1" target="_blank">Buy Tickets!</a>
-</p>
-
------
-
-*Mike Pumphrey is an Enterprise Trainer at ConsenSys working on the Truffle team. With over a dozen years of experience in documentation, support, and training, Mike is passionate about making technical concepts understandable to a wider audience. Mike is also the lead organizer for TruffleCon 2018.*
diff --git a/src/blog/you-can-now-make-your-own-truffle-box/index.md b/src/blog/you-can-now-make-your-own-truffle-box/index.md
deleted file mode 100644
index dcff42890..000000000
--- a/src/blog/you-can-now-make-your-own-truffle-box/index.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: You Can Now Make Your Own Truffle Box
-hide:
-  - navigation
----
-
-Two months ago we unveiled official integration with **Truffle Boxes**, example Ethereum applications and/or boilerplates that put complimentary tools and libraries into sweet, easily-downloadable packages. In addition to rolling out some official boxes, [Status.im](https://status.im/) released [the first community-supported box](/boxes/status).
-
-Today we're happy to announce anyone can now make their very own Truffle Box!
-
-## Making a Box
-
-To get started making a box, we've added a page to [our documentation](/docs/truffle/advanced/creating-a-truffle-box). For those starting a new box from scratch, we've also created a [blueprint Truffle Box](/boxes/blueprint) to get you started quickly.
-
-## The First Wave
-
-We included a call for pre-screening in the community section of our first box rollout and some trailblazers answered the call!
-
-Here are the first community boxes:
-
-**[Quintor/angular-truffle-box](/boxes/angular-truffle-box)**<br/>
-This Truffle Box provides a base for working with the Truffle Suite and Angular. It provides a basic working example of the MetaCoin contracts with Angular components. This project is generated with Angular CLI.
-
-**[hackingbeauty/react-dapp-material-ui](/boxes/react-dapp-material-ui)**<br/>
-In addition to Webpack and React, this box adds: React-Router, Redux and Material-UI for easy skinning of a Dapp.
-
-**[antony/svelte-box](/boxes/svelte-box)**<br/>
-A Truffle box using SvelteJS and Rollup. This box contains everything you need to start building a smart-contract app.
-
-**[kierenh/vue-dark-chocolate](/boxes/vue-dark-chocolate)**<br/>
-A truffle box that comes with everything you need to start using smart contracts from a Vue App with Bootstrap styling and components. Supporting frameworks include Vuex, Vue-Router & Bootstrap 4 (via Bootstrap-Vue) and webpack. The sample uses webpack-dev-server for hot-reloading or you can build and serve from express.
-
-Check out [the full list of boxes here](/boxes).
-
-A huge thank you to our entire community! We're humbled by your dedication and excited to see what's in store for the future.
-
--- Josh & the Truffle Team
diff --git a/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md b/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md
deleted file mode 100644
index 203aa8c58..000000000
--- a/src/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/index.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: You Decide - Pipeline or Table View in Truffle Teams' Refreshed Deployments Manager
-hide:
-  - navigation
----
-
-![Truffle Teams Deployments Refresh Banner](/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/blog-header.png)
-
-With Truffle Teams, you can manage multiple deployed instances of your smart contracts across different networks. We’ve heard mixed feedback about this workflow and are updating it accordingly: adding a table view and a deployment details page. We're also offering more insight into each deployment, by providing the cost and console output.
-
-## What’s New with Deployments?
-
-Our first iteration of Visual Deployments revolved around a pipeline view, with your commits on the left hand side and a production network on the right. While some do use and appreciate this type of workflow, many have only   a single production instance, and having an entire column just for this doesn’t make sense for those use cases. With that in mind, we’re offering a new table view, so you can see all of your deployed instances even more quickly and in an uncluttered way. In the future, you’ll also be able to sort and filter this table for even easier access.
-
-<figure>
-  <img class="mb-4 w-100 figure-shadow" src="/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/deployments-refresh-1.png" alt="The new deployments table view">
-  <figcaption class="text-center font-italic">The new deployments table view--you can still access the card view via the toggle switch in the upper-right.</figcaption>
-</figure> 
-
-You’ll also notice that clicking the name of a deployment now goes to a new deployment details screen. This contains the current status of the deployment along with its console output (an oft-requested addition)!
-
-<figure>
-  <img class="mb-4 w-100 figure-shadow" src="/img/blog/you-decide-pipeline-or-table-view-in-truffle-teams-deployments-manager/deployments-refresh-2.png" alt="The deployment details screen">
-  <figcaption class="text-center font-italic">The deployment details screen. Notice you can now access the console output!</figcaption>
-</figure>
-
-For more information on the new deployments screen, check out the [Truffle Teams Deployments docs](/docs/teams/deployments/deployment-details).
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://my.truffleteams.com/" target="_blank">CHECK OUT THE DEPLOYMENTS MANAGER</a>
-</div>
-
-## Thoughts?
-
-We want Truffle Teams to be the most effective DevOps tool in the blockchain space for both new and existing teams. Let us know what you think about the new deployment views, or if your team has other needs we haven’t met yet.
-
-Continue the conversation with your fellow Trufflers in our Slack community!
-
-<div class="mt-12 text-center">
-  <a class="btn btn-truffle mt-3" href="https://join.slack.com/t/truffle-community/shared_invite/zt-8wab0bnl-KcugRAqsY9yeNJYcnanfLA" target="_blank">SIGN UP FOR THE TRUFFLER SLACK</a>
-</div>
-
-Thanks!
-
-_Josh Quintal, Head of Product & Marketing_
diff --git a/src/community/index.md b/src/community/index.md
index 1bb032639..45c541d10 100644
--- a/src/community/index.md
+++ b/src/community/index.md
@@ -1,4 +1,3 @@
 ---
 template: community.html
-title: Truffle Suite
 ---
diff --git a/src/index.md b/src/index.md
index 4573c2d26..a572d90d6 100644
--- a/src/index.md
+++ b/src/index.md
@@ -1,4 +1,3 @@
 ---
 template: home.html
-title: Truffle Suite
 ---

From 2e28bfcf03ac84b7b59d8de25d16838aaad69e6c Mon Sep 17 00:00:00 2001
From: David Nguyen <57245545+davidnguyen88@users.noreply.github.com>
Date: Mon, 21 Mar 2022 17:07:19 +0700
Subject: [PATCH 04/14] Delete .env

---
 .env | 2 --
 1 file changed, 2 deletions(-)
 delete mode 100644 .env

diff --git a/.env b/.env
deleted file mode 100644
index 6438235e7..000000000
--- a/.env
+++ /dev/null
@@ -1,2 +0,0 @@
-CONTENTFUL_SPACE_ID = 'yfwlmanyz0dl'
-CONTENTFUL_TOKEN = 'avq84-sow2ZdZmBtpfkNvUL5RixZmEvshgPSLuNQ4PI'
\ No newline at end of file

From 8d7013585d61ac3115cd91cc4476a0ae9412579a Mon Sep 17 00:00:00 2001
From: David Nguyen <minhnc@younetco.com>
Date: Mon, 21 Mar 2022 17:26:22 +0700
Subject: [PATCH 05/14] Update workflows

---
 .github/workflows/main.yml | 9 +++++++++
 .gitignore                 | 3 ++-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index c02228436..273836cc9 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -4,6 +4,8 @@ on:
     branches:
       - main
 
+  workflow_dispatch:
+
 jobs:
   build:
     name: Deploy docs
@@ -12,6 +14,13 @@ jobs:
       - name: Checkout master
         uses: actions/checkout@v1
 
+      - name: Create env file
+        run: |
+          touch .env
+          echo CONTENTFUL_SPACE_ID=${{ secrets.CONTENTFUL_SPACE_ID }} >> .env
+          echo CONTENTFUL_ENVIRONMENT=${{ secrets.CONTENTFUL_ENVIRONMENT }} >> .env
+          echo CONTENTFUL_TOKEN=${{ secrets.CONTENTFUL_TOKEN }} >> .env
+
       - name: Deploy docs
         uses: mhausenblas/mkdocs-deploy-gh-pages@1.20
         env:
diff --git a/.gitignore b/.gitignore
index 18afbdb03..6d2d0c448 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,5 @@
 site
 src/boxes/*/
 __pycache__
-.DS_Store
\ No newline at end of file
+.DS_Store
+.env

From 7862c2c354e3f45ca68e0bd08897370be04592ad Mon Sep 17 00:00:00 2001
From: David Nguyen <minhnc@younetco.com>
Date: Mon, 21 Mar 2022 17:36:40 +0700
Subject: [PATCH 06/14] Update Env

---
 .github/workflows/main.yml | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 273836cc9..be676d4a9 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -14,16 +14,12 @@ jobs:
       - name: Checkout master
         uses: actions/checkout@v1
 
-      - name: Create env file
-        run: |
-          touch .env
-          echo CONTENTFUL_SPACE_ID=${{ secrets.CONTENTFUL_SPACE_ID }} >> .env
-          echo CONTENTFUL_ENVIRONMENT=${{ secrets.CONTENTFUL_ENVIRONMENT }} >> .env
-          echo CONTENTFUL_TOKEN=${{ secrets.CONTENTFUL_TOKEN }} >> .env
-
       - name: Deploy docs
         uses: mhausenblas/mkdocs-deploy-gh-pages@1.20
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           TRUFFLESUITE_COM_GH_API_USERNAME: ${{ secrets.TRUFFLESUITE_COM_GH_API_USERNAME }}
           TRUFFLESUITE_COM_GH_API_KEY: ${{ secrets.TRUFFLESUITE_COM_GH_API_KEY }}
+          CONTENTFUL_SPACE_ID: ${{ secrets.CONTENTFUL_SPACE_ID }}
+          CONTENTFUL_ENVIRONMENT: ${{ secrets.CONTENTFUL_ENVIRONMENT }}
+          CONTENTFUL_TOKEN: ${{ secrets.CONTENTFUL_TOKEN }}

From 1b523cebefaaaf85b196569c0836c7fb920ee841 Mon Sep 17 00:00:00 2001
From: Minh Nguyen <minhnc@younetco.com>
Date: Mon, 21 Mar 2022 17:37:19 +0700
Subject: [PATCH 07/14] update environment contenful

---
 main.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/main.py b/main.py
index d26cddc73..6f284b4cd 100644
--- a/main.py
+++ b/main.py
@@ -61,10 +61,11 @@ def define_env(env):
 
     contentful_space_id = os.getenv('CONTENTFUL_SPACE_ID')
     contentful_token = os.getenv('CONTENTFUL_TOKEN')
+    contentful_environment = os.getenv('CONTENTFUL_ENVIRONMENT')
     env.conf['extra']['module_id_parse'] = module_id_parse;
     env.conf['extra']['parse_asset_contentful'] = parse_asset_contentful;
     env.conf['extra']['parse_url'] = parse_url;
-    client = contentful.Client(contentful_space_id, contentful_token)
+    client = contentful.Client(contentful_space_id, contentful_token, environment=contentful_environment)
     site_dir = env.conf['docs_dir']
 
     # Query all entry 'page'

From 13e60dc1aa90e48f180c919af7e67b946029c168 Mon Sep 17 00:00:00 2001
From: David Nguyen <minhnc@younetco.com>
Date: Mon, 21 Mar 2022 18:03:17 +0700
Subject: [PATCH 08/14] Update Env

---
 .gitignore |  3 +++
 main.py    | 18 +++++++++---------
 2 files changed, 12 insertions(+), 9 deletions(-)

diff --git a/.gitignore b/.gitignore
index 6d2d0c448..711f85195 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,6 @@ src/boxes/*/
 __pycache__
 .DS_Store
 .env
+src/blog
+!src/blog/index.md
+!src/blog/blog.html.jinja2
diff --git a/main.py b/main.py
index 6f284b4cd..347565b2f 100644
--- a/main.py
+++ b/main.py
@@ -59,12 +59,12 @@ def get_blogs_contentful(client, data):
 def define_env(env):
     "Definition of the module"
 
-    contentful_space_id = os.getenv('CONTENTFUL_SPACE_ID')
-    contentful_token = os.getenv('CONTENTFUL_TOKEN')
-    contentful_environment = os.getenv('CONTENTFUL_ENVIRONMENT')
-    env.conf['extra']['module_id_parse'] = module_id_parse;
-    env.conf['extra']['parse_asset_contentful'] = parse_asset_contentful;
-    env.conf['extra']['parse_url'] = parse_url;
+    contentful_space_id = os.getenv('CONTENTFUL_SPACE_ID') or os.environ.get('CONTENTFUL_SPACE_ID')
+    contentful_token = os.getenv('CONTENTFUL_TOKEN') or os.environ.get('CONTENTFUL_TOKEN')
+    contentful_environment = os.getenv('CONTENTFUL_ENVIRONMENT') or os.environ.get('CONTENTFUL_ENVIRONMENT')
+    env.conf['extra']['module_id_parse'] = module_id_parse
+    env.conf['extra']['parse_asset_contentful'] = parse_asset_contentful
+    env.conf['extra']['parse_url'] = parse_url
     client = contentful.Client(contentful_space_id, contentful_token, environment=contentful_environment)
     site_dir = env.conf['docs_dir']
 
@@ -89,7 +89,7 @@ def define_env(env):
 
         if os.path.exists(blog_dir):
             shutil.rmtree(blog_dir)
-            
+
         os.makedirs(blog_dir)
         file_path = os.path.join(blog_dir, 'index.md')
 
@@ -121,7 +121,7 @@ def define_env(env):
 
     # dict: repoName -> box
     dicBox = dict(zip(
-        [box['repoName'] for box in boxes], 
+        [box['repoName'] for box in boxes],
         boxes
     ))
 
@@ -139,7 +139,7 @@ def define_env(env):
     env.conf['extra']['boxes'] = list(dicBox.values())
 
     if os.environ.get("LOCAL_BUILD"):
-        env.conf['extra']['boxes'] = env.conf['extra']['boxes'][:6] 
+        env.conf['extra']['boxes'] = env.conf['extra']['boxes'][:6]
 
     username = os.environ.get("TRUFFLESUITE_COM_GH_API_USERNAME")
     key = os.environ.get("TRUFFLESUITE_COM_GH_API_KEY")

From 25d0e0d9126e023b08924ca13730723d0d7c6c39 Mon Sep 17 00:00:00 2001
From: Minh Nguyen <minhnc@younetco.com>
Date: Tue, 22 Mar 2022 10:11:10 +0700
Subject: [PATCH 09/14] update environment secrets

---
 .github/workflows/main.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index be676d4a9..c4304bd63 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -10,6 +10,7 @@ jobs:
   build:
     name: Deploy docs
     runs-on: ubuntu-latest
+    environment: github-pages
     steps:
       - name: Checkout master
         uses: actions/checkout@v1

From 957069d3b3e12b33335e5999c179d0b92285d760 Mon Sep 17 00:00:00 2001
From: Minh Nguyen <minhnc@younetco.com>
Date: Tue, 22 Mar 2022 10:25:07 +0700
Subject: [PATCH 10/14] merge newest code

---
 main.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/main.py b/main.py
index 347565b2f..4048959e5 100644
--- a/main.py
+++ b/main.py
@@ -59,9 +59,9 @@ def get_blogs_contentful(client, data):
 def define_env(env):
     "Definition of the module"
 
-    contentful_space_id = os.getenv('CONTENTFUL_SPACE_ID') or os.environ.get('CONTENTFUL_SPACE_ID')
-    contentful_token = os.getenv('CONTENTFUL_TOKEN') or os.environ.get('CONTENTFUL_TOKEN')
-    contentful_environment = os.getenv('CONTENTFUL_ENVIRONMENT') or os.environ.get('CONTENTFUL_ENVIRONMENT')
+    contentful_space_id = os.environ.get('CONTENTFUL_SPACE_ID')
+    contentful_token = os.environ.get('CONTENTFUL_TOKEN')
+    contentful_environment = os.environ.get('CONTENTFUL_ENVIRONMENT')
     env.conf['extra']['module_id_parse'] = module_id_parse
     env.conf['extra']['parse_asset_contentful'] = parse_asset_contentful
     env.conf['extra']['parse_url'] = parse_url

From cac220f5a977632d7e2cd22061cec0110869c563 Mon Sep 17 00:00:00 2001
From: Minh Nguyen <minhnc@younetco.com>
Date: Tue, 22 Mar 2022 17:20:04 +0700
Subject: [PATCH 11/14] Merge newest code

---
 custom_theme/blog.html      |  4 +++
 custom_theme/community.html |  3 ++
 custom_theme/home.html      |  3 ++
 main.py                     | 56 +++++++++++++++++++++----------------
 4 files changed, 42 insertions(+), 24 deletions(-)

diff --git a/custom_theme/blog.html b/custom_theme/blog.html
index 3ee7fadbd..aa0b5b5d1 100644
--- a/custom_theme/blog.html
+++ b/custom_theme/blog.html
@@ -1,6 +1,10 @@
 
 {% extends "main.html" %}
 
+{% block htmltitle %}
+<title>{{config.extra.contentful_page.blog.seo.page_title}}</title>
+{% endblock %}
+
 <!-- Render hero under tabs -->
 {% block tabs %}
   {{ super() }}
diff --git a/custom_theme/community.html b/custom_theme/community.html
index 70c97f392..da8939cb7 100644
--- a/custom_theme/community.html
+++ b/custom_theme/community.html
@@ -1,5 +1,8 @@
 {% extends "main.html" %}
 
+{% block htmltitle %}
+<title>{{config.extra.contentful_page.community.seo.page_title}}</title>
+{% endblock %}
 <!-- Render hero under tabs -->
 {% block tabs %}
   {{ super() }}
diff --git a/custom_theme/home.html b/custom_theme/home.html
index f600698b9..08a52efa6 100644
--- a/custom_theme/home.html
+++ b/custom_theme/home.html
@@ -1,5 +1,8 @@
 {% extends "main.html" %}
 
+{% block htmltitle %}
+<title>{{config.extra.contentful_page.home.seo.page_title}}</title>
+{% endblock %}
 <!-- Render hero under tabs -->
 {% block tabs %}
   {{ super() }}
diff --git a/main.py b/main.py
index 4048959e5..bb7e8baea 100644
--- a/main.py
+++ b/main.py
@@ -84,14 +84,20 @@ def define_env(env):
     contentful_entries_blogs = get_blogs_contentful(client, [])
     env.conf['extra']['contentful_blogs'] = contentful_entries_blogs
 
-    for blog in contentful_entries_blogs:
-        blog_dir = os.path.join(site_dir, 'blog', blog.slug)
+    #clear all data old blog
+    blog_dir = os.path.join(site_dir, 'blog')
+    for f in os.listdir(blog_dir):
+        if(os.path.isdir(os.path.join(blog_dir, f))):
+            shutil.rmtree(os.path.join(blog_dir, f))
 
-        if os.path.exists(blog_dir):
-            shutil.rmtree(blog_dir)
+    for blog in contentful_entries_blogs:
+        blog_detail_dir = os.path.join(site_dir, 'blog', blog.slug)
 
-        os.makedirs(blog_dir)
-        file_path = os.path.join(blog_dir, 'index.md')
+        if os.path.exists(blog_detail_dir):
+            shutil.rmtree(blog_detail_dir)
+            
+        os.makedirs(blog_detail_dir)
+        file_path = os.path.join(blog_detail_dir, 'index.md')
 
         #content of blog detail
         blog_detail = blog.detail
@@ -143,31 +149,33 @@ def define_env(env):
 
     username = os.environ.get("TRUFFLESUITE_COM_GH_API_USERNAME")
     key = os.environ.get("TRUFFLESUITE_COM_GH_API_KEY")
-    for box in env.conf['extra']['boxes']:
-        print(box['repoName'])
+    if key:
+        for box in env.conf['extra']['boxes']:
+            print(box['repoName'])
 
-        box_dir = os.path.join(site_dir, 'boxes', box['displayName'])
-        if os.path.exists(box_dir):
-            shutil.rmtree(box_dir)
-        os.makedirs(box_dir)
-        file_path = os.path.join(box_dir, 'index.md')
+            box_dir = os.path.join(site_dir, 'boxes', box['displayName'])
+            if os.path.exists(box_dir):
+                shutil.rmtree(box_dir)
+            os.makedirs(box_dir)
+            file_path = os.path.join(box_dir, 'index.md')
 
-        response = requests.get("https://api.github.com/repos/" + box['userOrg'] + "/" + box['repoName'] + "/readme", auth=HTTPBasicAuth(username, key))
-        json_response = response.json()
+            response = requests.get("https://api.github.com/repos/" + box['userOrg'] + "/" + box['repoName'] + "/readme", auth=HTTPBasicAuth(username, key))
+            json_response = response.json()
 
-        try:
-            markdown = base64.b64decode(json_response['content'])
+            try:
+                if hasattr(json_response, 'content'):
+                    markdown = base64.b64decode(json_response['content'])
 
-            with open('src/boxes/box.html.jinja2') as file_:
-                template = Template(file_.read())
+                    with open('src/boxes/box.html.jinja2') as file_:
+                        template = Template(file_.read())
 
-            outputText = template.render(box=box, readme=markdown.decode('utf-8'))
+                    outputText = template.render(box=box, readme=markdown.decode('utf-8'))
 
-            with open(file_path, 'w') as f:
-                f.write(outputText)
+                    with open(file_path, 'w') as f:
+                        f.write(outputText)
 
-        except Exception as ex:
-            print('error: ' + repr(ex))
+            except Exception as ex:
+                print('error: ' + repr(ex))
 
 def on_pre_page_macros(env):
     "Pre-page actions"

From fd36db567a2121406e32b3939463c8249f82b437 Mon Sep 17 00:00:00 2001
From: David Nguyen <minhnc@younetco.com>
Date: Wed, 23 Mar 2022 18:01:25 +0700
Subject: [PATCH 12/14] Support SEO

---
 custom_theme/blog.html            | 22 ++++++++++++++++++----
 custom_theme/community.html       | 21 ++++++++++++++++++---
 custom_theme/home.html            | 26 +++++++++++++++++++++-----
 custom_theme/main.html            | 31 ++++++++++++++++++++-----------
 custom_theme/partials/footer.html |  8 ++++----
 main.py                           | 31 ++++++++++++++++---------------
 mkdocs.yml                        |  1 +
 src/blog/blog.html.jinja2         |  4 +++-
 8 files changed, 101 insertions(+), 43 deletions(-)

diff --git a/custom_theme/blog.html b/custom_theme/blog.html
index aa0b5b5d1..ce7281388 100644
--- a/custom_theme/blog.html
+++ b/custom_theme/blog.html
@@ -1,8 +1,22 @@
-
 {% extends "main.html" %}
 
 {% block htmltitle %}
-<title>{{config.extra.contentful_page.blog.seo.page_title}}</title>
+    {% if config.extra.contentful_page.blog and config.extra.contentful_page.blog.seo %}
+        <title>{{config.extra.contentful_page.blog.seo.page_title}}</title>
+        <meta name="description" content="{{config.extra.contentful_page.blog.seo.page_description}}">
+        <meta property="og:site_name" content="{{config.site_name}}">
+        <meta property="og:url" content="{{ page.canonical_url }}">
+        <meta property="og:type" content="page">
+        <meta property="og:title" content="{{config.extra.contentful_page.blog.seo.page_title}}">
+        <meta property="og:description" content="{{config.extra.contentful_page.blog.seo.page_description}}">
+        <meta property="og:image" content="{{config.extra.contentful_page.blog.seo.featured_image.url()}}">
+        <meta name="twitter:url" content="{{ page.canonical_url }}">
+        <meta name="twitter:title" content="{{config.extra.contentful_page.blog.seo.page_title}}">
+        <meta name="twitter:description" content="{{config.extra.contentful_page.blog.seo.page_description}}">
+        <meta name="twitter:image" content="{{config.extra.contentful_page.blog.seo.featured_image.url()}}">
+    {% else %}
+        {{ super() }}
+    {% endif %}
 {% endblock %}
 
 <!-- Render hero under tabs -->
@@ -59,7 +73,7 @@ <h1>{{config.extra.contentful_page.blog.title}}</h1>
     </section>
 </div>
 
-  {% endblock %}
+{% endblock %}
 
 
 <!-- Content -->
@@ -69,4 +83,4 @@ <h1>{{config.extra.contentful_page.blog.title}}</h1>
 
 {% block footer %}
     {% include "partials/footer.html" %}
-{% endblock %}
\ No newline at end of file
+{% endblock %}
diff --git a/custom_theme/community.html b/custom_theme/community.html
index da8939cb7..6479a63ea 100644
--- a/custom_theme/community.html
+++ b/custom_theme/community.html
@@ -1,7 +1,22 @@
 {% extends "main.html" %}
 
 {% block htmltitle %}
-<title>{{config.extra.contentful_page.community.seo.page_title}}</title>
+  {% if config.extra.contentful_page.community and config.extra.contentful_page.community.seo %}
+    <title>{{config.extra.contentful_page.community.seo.page_title}}</title>
+    <meta name="description" content="{{config.extra.contentful_page.community.seo.page_description}}">
+    <meta property="og:site_name" content="{{config.site_name}}">
+    <meta property="og:url" content="{{ page.canonical_url }}">
+    <meta property="og:type" content="page">
+    <meta property="og:title" content="{{config.extra.contentful_page.community.seo.page_title}}">
+    <meta property="og:description" content="{{config.extra.contentful_page.community.seo.page_description}}">
+    <meta property="og:image" content="{{config.extra.contentful_page.community.seo.featured_image.url()}}">
+    <meta name="twitter:url" content="{{ page.canonical_url }}">
+    <meta name="twitter:title" content="{{config.extra.contentful_page.community.seo.page_title}}">
+    <meta name="twitter:description" content="{{config.extra.contentful_page.community.seo.page_description}}">
+    <meta name="twitter:image" content="{{config.extra.contentful_page.community.seo.featured_image.url()}}">
+  {% else %}
+    {{ super() }}
+  {% endif %}
 {% endblock %}
 <!-- Render hero under tabs -->
 {% block tabs %}
@@ -40,7 +55,7 @@
       width: 2.5rem;
       max-height: 2.5rem;
     }
-    
+
   </style>
 
 {% with modules = config.extra.contentful_page.community.modules %}
@@ -63,4 +78,4 @@
 
 {% block footer %}
     {% include "partials/footer.html" %}
-{% endblock %}
\ No newline at end of file
+{% endblock %}
diff --git a/custom_theme/home.html b/custom_theme/home.html
index 08a52efa6..6cb91e24d 100644
--- a/custom_theme/home.html
+++ b/custom_theme/home.html
@@ -1,8 +1,24 @@
 {% extends "main.html" %}
 
 {% block htmltitle %}
-<title>{{config.extra.contentful_page.home.seo.page_title}}</title>
+  {% if config.extra.contentful_page.home and config.extra.contentful_page.home.seo %}
+    <title>{{config.extra.contentful_page.home.seo.page_title}}</title>
+    <meta name="description" content="{{config.extra.contentful_page.home.seo.page_description}}">
+    <meta property="og:site_name" content="{{config.site_name}}">
+    <meta property="og:url" content="{{ page.canonical_url }}">
+    <meta property="og:type" content="page">
+    <meta property="og:title" content="{{config.extra.contentful_page.home.seo.page_title}}">
+    <meta property="og:description" content="{{config.extra.contentful_page.home.seo.page_description}}">
+    <meta property="og:image" content="{{config.extra.contentful_page.home.seo.featured_image.url()}}">
+    <meta name="twitter:url" content="{{ page.canonical_url }}">
+    <meta name="twitter:title" content="{{config.extra.contentful_page.home.seo.page_title}}">
+    <meta name="twitter:description" content="{{config.extra.contentful_page.home.seo.page_description}}">
+    <meta name="twitter:image" content="{{config.extra.contentful_page.home.seo.featured_image.url()}}">
+  {% else %}
+    {{ super() }}
+  {% endif %}
 {% endblock %}
+
 <!-- Render hero under tabs -->
 {% block tabs %}
   {{ super() }}
@@ -14,19 +30,19 @@
       .md-main__inner {
         margin: 0;
       }
-  
+
       /* Hide main content for now */
       .md-content {
         display: none;
       }
-  
+
       /* Hide table of contents */
       @media screen and (min-width: 60em) {
         .md-sidebar--secondary {
           display: none;
         }
       }
-  
+
       /* Hide navigation */
       @media screen and (min-width: 76.25em) {
         .md-sidebar--primary {
@@ -59,4 +75,4 @@
 
 {% block footer %}
     {% include "partials/footer.html" %}
-{% endblock %}
\ No newline at end of file
+{% endblock %}
diff --git a/custom_theme/main.html b/custom_theme/main.html
index 6765022f1..e65d19566 100644
--- a/custom_theme/main.html
+++ b/custom_theme/main.html
@@ -1,20 +1,30 @@
 {% extends "base.html" %}
 
-{% block site_meta %}
+{% block htmltitle %}
+    {{ super() }}
+    <meta property="og:url" content="{{ page.canonical_url }}">
+    <meta property="og:site_name" content="{{config.site_name}}">
+    <meta property="og:type" content="article">
+    <meta property="og:title" content="{{page.title}} - {{config.site_name}}">
+    {% if page and page.meta and page.meta.description %}<meta property="og:description" content="{{page.meta.description}}">{% endif %}
+    {% if page and page.meta and page.meta.featured %}<meta property="og:image" content="{{page.meta.featured}}">{% endif %}
+    <meta name="twitter:url" content="{{ page.canonical_url }}">
+    <meta name="twitter:title" content="{{page.title}} - {{config.site_name}}">
+    {% if page and page.meta and page.meta.description %}<meta name="twitter:description" content="{{page.meta.description}}">{% endif %}
+    {% if page and page.meta and page.meta.featured %}<meta name="twitter:image" content="{{page.meta.featured}}">{% endif %}
+{% endblock %}
+
+{% block extrahead %}
     {{ super() }}
     <!-- Google Tag Manager -->
     <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
-      new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
+        new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
       j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
       'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
-      })(window,document,'script','dataLayer','GTM-PPB7LNV');</script>
-      <!-- End Google Tag Manager -->
+    })(window,document,'script','dataLayer','GTM-PPB7LNV');</script>
+    <!-- End Google Tag Manager -->
 
-{% endblock %}
-
-{% block extrahead %}
-    {{ super() }}
-    <!-- Redirect -->
+<!-- Redirect -->
     <script>(function(){
       var path = location.pathname;
       var slug = path.slice(1);
@@ -24,10 +34,9 @@
         location.href = path.replace(regex,'')
       } else if(ext !== slug && ext === 'html') {
         location.href = path.substr(0, path.lastIndexOf(".")) + '/';
-      } 
+      }
     })()</script>
     <!-- End redirect -->
-
 {% endblock %}
 
 <!-- Announcement bar -->
diff --git a/custom_theme/partials/footer.html b/custom_theme/partials/footer.html
index 04565dc8e..3b2e98e20 100644
--- a/custom_theme/partials/footer.html
+++ b/custom_theme/partials/footer.html
@@ -19,10 +19,10 @@
             <div class="col-8">
               <ul class="footer-naviation">
                 <li><a class="text-uppercase" href="mailto:inquiry@trufflesuite.com">Contact Us</a></li>
-                <li><a class="text-uppercase" href="/policy">Privacy Policy</a></li>
-                <li><a class="text-uppercase" href="/staff">Staff</a></li>
+                <li><a class="text-uppercase" href="/policy/">Privacy Policy</a></li>
+                <li><a class="text-uppercase" href="/staff/">Staff</a></li>
                 <li><a class="text-uppercase" href="https://github.com/trufflesuite">Github</a></li>
-                <li><a class="text-uppercase" href="/trufflecon2020">TruffleCon 2020</a></li>
+                <li><a class="text-uppercase" href="/trufflecon2020/">TruffleCon 2020</a></li>
               </ul>
             </div>
             <div class="col-2">
@@ -49,4 +49,4 @@
 
 <!-- Start of HubSpot Embed Code -->
 <script type="text/javascript" id="hs-script-loader" async defer src="//js.hs-scripts.com/4795067.js"></script>
-<!-- End of HubSpot Embed Code -->
\ No newline at end of file
+<!-- End of HubSpot Embed Code -->
diff --git a/main.py b/main.py
index bb7e8baea..648e46ed1 100644
--- a/main.py
+++ b/main.py
@@ -68,23 +68,18 @@ def define_env(env):
     client = contentful.Client(contentful_space_id, contentful_token, environment=contentful_environment)
     site_dir = env.conf['docs_dir']
 
-    # Query all entry 'page'
+    # query all entry 'page'
     entries = client.entries({'content_type': 'page', 'include': 10})
     contentful_data = {}
-    # test = client.entry('1CgkzrVtPU7A4FbD6MfwwJ')
-    # from pprint import pprint
-    # pprint(test.date)
     for entry in entries:
-        # dictModules = [{'template': module_id_parse(module.sys['content_type'].id), 'props': module} for module in entry.modules]
         nested_set(contentful_data, [entry.slug], entry)
         env.conf['extra']['contentful_page'] = contentful_data
 
-    #blog page
-    # contentful_entries_blogs = client.entries({'limit': 500, 'content_type': 'blog', 'include': 10, 'order': '-fields.date,-sys.createdAt'})
+    # blog page
     contentful_entries_blogs = get_blogs_contentful(client, [])
     env.conf['extra']['contentful_blogs'] = contentful_entries_blogs
 
-    #clear all data old blog
+    # get blog content from contentful
     blog_dir = os.path.join(site_dir, 'blog')
     for f in os.listdir(blog_dir):
         if(os.path.isdir(os.path.join(blog_dir, f))):
@@ -95,26 +90,32 @@ def define_env(env):
 
         if os.path.exists(blog_detail_dir):
             shutil.rmtree(blog_detail_dir)
-            
+
         os.makedirs(blog_detail_dir)
         file_path = os.path.join(blog_detail_dir, 'index.md')
 
         #content of blog detail
         blog_detail = blog.detail
 
-        #heading detail and SEO title
+        #heading detail title
         blog_detail_title = blog.title
-        if hasattr(blog, 'detail_title'):
+        blog_detail_description = blog.description
+
+        blog_detail_featured = 'https://trufflesuite.com/img/home-hero.png'
+        if hasattr(blog, 'detail_title') and blog.detail_title:
             blog_detail_title = blog.detail_title
 
+        if hasattr(blog, 'thumbnail') and blog.thumbnail.url():
+            blog_detail_featured = blog.thumbnail.url()
+
+        if hasattr(blog, 'featured') and blog.featured.url():
+            blog_detail_featured = blog.featured.url()
+
         try:
             markdown = blog_detail
-
             with open('src/blog/blog.html.jinja2') as file_:
                 template = Template(file_.read())
-
-            outputText = template.render(blog=blog, content=markdown, title=blog_detail_title)
-
+            outputText = template.render(blog=blog, content=markdown, title=blog_detail_title, description=blog_detail_description, featured=blog_detail_featured)
             with open(file_path, 'w') as f:
                 f.write(outputText)
 
diff --git a/mkdocs.yml b/mkdocs.yml
index 19e5bdf05..042125528 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -51,6 +51,7 @@ markdown_extensions:
   - markdown.extensions.md_in_html
   - toc:
       permalink: true
+  - meta
 use_directory_urls: false
 plugins:
   - search
diff --git a/src/blog/blog.html.jinja2 b/src/blog/blog.html.jinja2
index 48c2fd68f..0e91a6cfc 100644
--- a/src/blog/blog.html.jinja2
+++ b/src/blog/blog.html.jinja2
@@ -1,7 +1,9 @@
 ---
 title: {{title}}
+description: {{description}}
+featured: {{featured}}
 hide:
   - navigation
 ---
 
-{{ content }}
\ No newline at end of file
+{{ content }}

From 163c5d7ddee0ce4cf3cd2efc6602e4b839a457b6 Mon Sep 17 00:00:00 2001
From: Minh Nguyen <minhnc@younetco.com>
Date: Thu, 24 Mar 2022 09:04:40 +0700
Subject: [PATCH 13/14] Merge newest code

---
 src/blog/blog.html.jinja2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/blog/blog.html.jinja2 b/src/blog/blog.html.jinja2
index 0e91a6cfc..4c2b6cef9 100644
--- a/src/blog/blog.html.jinja2
+++ b/src/blog/blog.html.jinja2
@@ -1,6 +1,6 @@
 ---
-title: {{title}}
-description: {{description}}
+title: "{{title}}"
+description: "{{description}}"
 featured: {{featured}}
 hide:
   - navigation

From cff676c390eb7ae5dac8fda8f90f801115573132 Mon Sep 17 00:00:00 2001
From: Minh Nguyen <minhnc@younetco.com>
Date: Thu, 24 Mar 2022 11:23:59 +0700
Subject: [PATCH 14/14] Merge newest code

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

diff --git a/mkdocs.yml b/mkdocs.yml
index 042125528..5810df711 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -52,7 +52,7 @@ markdown_extensions:
   - toc:
       permalink: true
   - meta
-use_directory_urls: false
+use_directory_urls: true
 plugins:
   - search
   - awesome-pages