diff --git a/_HowToContribute/intro.md b/_HowToContribute/intro.md
deleted file mode 100644
index 550dcde8..00000000
--- a/_HowToContribute/intro.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: "DIDecentral: Contributors Intro"
-description: "Getting started contributing to DIDecentral via Twitter, Discord Chat, and GitHub."
-excerpt: >
- A variety of ways to contribute to DIDecentral with a minimal barriar to entry. Starting from Twitter, Discord Chat, and GitHub.
-header:
- caption: "Quickstart for [GitHub](https://github.com/didecentral), [Twitter](https://twitter.com/didecentral)."
-tags:
- - Discord
- - Archives
- - GitHub
- - Twitter
- - How-To
-toc_sticky: true
-date: 2019-07-06
-author_profile: false
-authors:
- - "Infominer"
- - "JuanSC"
-published: false
-last_modified_at: 2019-07-14
----
-
-
-We welcome issues or pull requests for question, comments, or contributions of every type. While some may feel intimidated to get started with GitHub, we assure you it's just like any other social platform with user profiles, content, text fields and buttons.
-
-If you have questions, other people probably want to know the answer also. Its not easy to remember and document every sticky point of working with github pages, discord, and associated digital tools.
-
-However, over time, through the process of collaborative editing, crowdsourcing ideas, and learning together, to discover and extract value from various datasets.
-
-
-{% include figure image_path="https://imgur.com/WJVcyXT.png" alt="github.com/didecentral" caption="[github.com/didecentral](https://github.com/didecentral)" %}
-
-### DIDecentral - Repositories
-
-A number of repositories which will be good sources for content creation have been forked into this organization for reference. The following are the primary repositories under our care.
-
-* [DIDecentral](https://github.com/DIDecentral)
- * [didecentral/decentralized-id.com](https://github.com/didecentral/decentralized-id.com) - Decentralized Identity
-
-Besides these, @infominer33 commonly forks repositories into the organization that seem like good sources for future collaboration and\or content creation.
-
-## GitHub Issues
-
-* [didecentral/community-website/issues](https://github.com/didecentral/community-website/issues)
-* [didecentral/decentralized-id.com/issues](https://github.com/didecentral/decentralized-id.com/issues)
-* [didecentral/rwot-dir/issues](https://github.com/didecentral/rwot-dir/issues)
-
-Generally speaking, this is a good place if you have a link or two to contribute, a question, ideas, want to point out a broken feature, or even just to say Hello :D
-
-Github issues are just like the comments feature, except it lets you note where exactly in the source there is a problem, or you have a suggestion. We're open to feedback and collaboration in whichever venue you prefer.
-
-## Pull-Requests
-
-* [didecentral/community-website/pulls](https://github.com/didecentral/community-website/pulls)
-* [didecentral/decentralized-id.com/pulls](https://github.com/didecentral/decentralized-id.com/pulls)
-* [didecentral/rwot-dir/pulls](https://github.com/didecentral/rwot-dir/pulls)
-
-
-These are good if you'd like to correct something, or suggest some changes to any aspect of the site. Also, a pull-request is the official pipeline for introducing changes to a repository.
-
-Over time we will introduce more fine grained guides on how to do this in a way so that your contribution is easily accepted and recorded in the git history.
-
-### "Edit This Page"
-
-
-
-Nearly every page has a section like this, where you can share socially, or edit\view on GitHub.
-
-Clicking that button takes you to the unformatted version of the page on GitHub. When you are logged in to GitHub, that puts you one click away from editing this page: look for the pencil icon on the right side, just above where the line-numbered raw file begins.
-
-
-
-Clicking it will reload an take you to an editable version of the page, which proposes an update through github. The monitor icon will open an editable change-proposal of the file. This allows you to contribute through a familiar interface (your web-browser), without having to understand anything about GitHub.
-
-Whether it's an actual improvement, fully functioning with proper markup, or simply a note, it will be read and appreciated! Even if your change isn't perfect: We'll try to accept it and include your "commits", which are Git's way of recording contributions that GitHub has built a web-interface over.
-
-None of us are necessarily professional or experts with git or web-publishing. However, we do wish to learn and grow our digital skillset.
-
-## Thanks for Visiting!
-
-Feel free to visit [Web-work.tools](https://web-work.tools) for an array of entry-level web-work how-tools.
\ No newline at end of file
diff --git a/_HowToContribute/quickstart.md b/_HowToContribute/quickstart.md
deleted file mode 100644
index 3953e6fb..00000000
--- a/_HowToContribute/quickstart.md
+++ /dev/null
@@ -1,314 +0,0 @@
----
-title: "Contributors Quickstart (A Gentle Introduction to GitHub)"
-excerpt: "Learn how to revise/add content to a page, or submit your first blog-post via web-browser."
-tags: ["Quickstart","Tools", "GitHub Pages", "Minimal Mistakes"]
-author: Infominer
-published: false
-author_profile: false
-toc_sticky: true
-date: 2019-07-13
-last_modified_at: 2019-07-14
----
-
-So far, we've covered quite a lot of ground in our contributors guides!
-
-* [Welcome DIDecentral](https://didecentral.com/welcome/) - A high level overview of the projects we're working on.
-* [Intro](https://didecentral.com/contributors-guide/intro/) - The easiest ways to participate with DIDecentral.
-* [Quickstart](https://didecentral.com/contributors-guide/quickstart/)
- * [Infobot Hello](https://didecentral.com/test/infobot-hello/) - Teplate for your first community blogpost.
-* [Site Setup and Configuration](https://didecentral.com/contributors-guide/site-config/) - 'Everything' about how this site is configured.
-* [Social Curation Archive](https://didecentral.com/contributors-guide/discord-archive-howto/) - How to export discord history and integrate with Minimal Mistakes Jekyll.
-
-What is needed is a quickstart guide, so that you don't have to read all of that to revise \ add a few links to a page, or even submit your first blog-post.
-
-
-All that's required to follow this guide is a web-browser and a GitHub account. If you don't already have one, go ahead and [sign up](https://github.com/join) so you can follow along.
-{: .notice--primary}
-
-
-If you've been following along with these posts from the beginning, you'll want to go back and review, since I forgot to wrap any liquid templating that I was showing in codesnippets with "raw tags" (see source for details). As a result, a significant portion of the value was lost to any early readers.
-{: .notice--warning}
-
-
-## Edit This Page
-
-Feel free to submit test pull-requests while following along or exploring on GitHub.
-
-
-
-Besides using social media, such as [twitter](https://didecentral.com/contributors-intro/#twitter--mention-and-hash-tags) or [discord](https://didecentral.com/contributors-intro/#contributing-via-discord), the simplest way to contribute to these web-sites is by clicking "Edit this page", which should be found at the bottom of every page run by DIDecentral.
-
-If everything is properly set up on our side of things, you will find yourself transported from our website to that pages source file on GitHub.
-
-
-
-If you click the little pencil icon (red circle in above image), you will find a basic text editor and the pages source. If you don't have commit access to the repository, a patch copy of that file will be created in your github account where you can edit, and propose changes.
-
-
-
-
-## Front Matter
-
-This is where configuration on the page level happens.
-
-```markdown
-{% raw %}
----
-title: "Welcome to DIDecentral Community Site and Social Archive"
-description: "DIDecentral is a collaborative curation initiative aiming to create quality educational content related to Decentralized Identity: Principles, Specs, Code and Initiatives."
-
-# the excerpt is what supplies preview text on the post-index.
-
-excerpt: >
- A high-level overview of our organization, its projects, and their general state of development.
-header:
- image: /assets/images/didecentral-community-header.png
- teaser: /assets/images/didecentral-community-teaser.png
- caption: ""
-tags:
- - "Decentralized Identity"
- - "Web of Trust"
- - "Self Sovereign Identity"
- - Archive
- - How-To
-categories: ["DIDecentral", "Welcome"]
-author: Infominer
-
-#If you are making some revisions to existing content you can use the following example that will add a contributors section at the bottom of the page near tags and categories (be sure to uncomment and edit those lines to fit the situation of whatever page you are on).
-authors:
- - #"Infominer"
- - #"JuanSC"
-
-#If you want to change a permalink, you must add the current permalink to the `redirect_from` list, or create one if it does not already exist.
-permalink: welcome/
-redirect_from:
- - welcome-didecentral/
- - welcome
- - welcome-didecentral
-toc_sticky: true
-published: true
-last_modified_at: 2019-07-10
-#Be sure to change the modified date. I create my own custom made-up time, with the actual date. You can simply ignore the time, and update the date, or use whatever you'd like for the time. Later, the most recently modified content will be featured.
----
-{% endraw %}
-```
-
-In yaml documents, and the yaml front-matter of posts, the #hashtag is used for comments. Hopefully with the commented front-matter above, it's reasonably clear how the configuration of a page works. There are other page settings, but this covers all the essentials.
-
-
-## Saving your changes
-
-Once you've completed any edits, whether you've added a link or corrected a spelling error, leave a simple comment explaining what type of change you're proposing.
-
-
-
-Once you've submitted a change, GitHub compares the original with your proposed changes and asks if you'd like to create a pull-request.
-
-
-
-Assuming you're happy with the changes (in green at the bottom) go ahead and create a pull-request.
-
-
-
-Leave a comment explaining your changes. There is plenty of room to be as descriptive as you want in the pull-request comments, compared to the commit comment which is typically short.
-
-## Checking on your Pull-Request
-
-You should get an e-mail notifying you of any updates related to your pull-request. However, you can always see updates related to your open issues and pull-requests by clicking the GitHub logo at the top of any page on GitHub.
-
-
-
-
-That feed also includes notifications for any individuals you follow or repositories you watch.
-
-
-
-Since the account I used to create this guide doesn't follow anyone or have any activity, here's an example of an active feed:
-
-
-
-If you don't have time to get into GitHub, don't feel obliged to read any further. Above should be plenty to begin making simple contributions, as you browse, without getting too technical.
-{: .notice--primary}
-
-## Fork didecentral.github.io
-
-One advantage of forking the repository is that you can make as many changes as you like, and take as long as you want in your local repository. Then submit a pull-request when you're satisfied.
-
-
-
-Now you'll have a copy of the repository in your account.
-
-
-
-## Write a Blog Post
-
-Since you have full permissions to this repository, you can upload files or create them right in your browser!
-
-This site is for the community. Anyone is welcome to sumbit a post. This should be a low-stakes environment where anyone could learn to use GitHub and GitHub Pages for the first time.
-
-Even if you just want to write about what brings you to DIDecentral, share what project you are working on. If you aren't currently working on anything identity related, that's fine, share what you'd like, use your imagination.
-
-The idea is to be as welcoming as possible, and encourage people to try it out. Editing text files on GitHub is a gateway to digital transformation.
-
-You don't have to be very technical to get started. If you start with the simple things, after a while, you'll find that you're getting to know the lay of the land. It's possible to build from there to learn any number of technical skills, as @infominer33 has been discovering.
-
-## authors.yml
-
-If you're submitting a new post, or planning to make any contributions, why not add yourself to the [authors.yml](https://github.com/didecentral/community-website/edit/master/_data/authors.yml)?
-
-This way an "author profile" will be shown next to your posts. Later, we can modify the author profile template to include info about all of your contributions to the site, and eventually each author will have their own page made with user-generated Jekyll data.
-
-
-
-
-```yaml
-
-Infobot:
- name : "Info-bot"
- bio : "Digital Helper"
- avatar : "https://imgur.com/LPDefso.png"
- links:
- - label: "Email"
- icon: "fas fa-fw fa-envelope-square"
- url: "mailto:infominer@protonmail.com"
- - label: "Website"
- icon: "fas fa-fw fa-link"
- url: "https://infominer.id"
- - label: "GitHub"
- icon: "fab fa-fw fa-github"
- url: "https://github.com/info-bot/"
- - label: "Twitter"
- icon: "fab fa-fw fa-twitter-square"
- url: "https://twitter.com/infominer33"
- - label: "Discord"
- icon: "fab fa-fw fa-discord"
- url: "https://discord.gg/29mZwPQ"
- - label: "Telegram"
- icon: "fab fa-fw fa-telegram"
- url: "https://t.me/InfoMiner33"
-
-```
-
-Simply copy-paste this example, removing any social networks you don't use, and if you don't see your preferred social networks listed, go to [fontawesome.com](https://fontawesome.com/icons/telegram?style=brands) to see how your favorite social site is labeled (mostly you can just use it's name and copy the format shown above).
-
-Save your addition to `authors.yml`, and we'll cover pull-requests after submitting our post.
-
-## Create New File
-
-Now that you've added your info into the author data file, you are ready to create your first blog-post with DIDecentral.
-
-
-
-
-Click "Create new file" where the hand pointer is in the illustration, above the file listing, below the "watch" icon.
-
-Name your post starting with the date, and then the title, with `-` dashes instead of spaces.
-
-`YEAR-MONTH-DAY-title.md`
-
-
-```html
-{% raw %}
-
----
-title: "Hi I'm info-bot!"
-author: Infobot
-permalink: test/
----
-
-
-**Hello world**, this is my first Jekyll blog post.
-
-I hope you like it!
-
-I'm an account that @infominer33 uses for experimenting with various features.
-
-This post was written during the creation of our [Contributors Quickstart](/contributors-quickstart/) guide.
-
-{% endraw %}
-
-```
-
-
-
-For now we'll just commit to the master branch, and submit a pull-request. However, in the future, we'll detail how to create (and merge back in) a new working branch, to leave the master branch in sync with its source while you work (especially helpful for bigger changes that might take a while).
-
-## Submit a Pull Request
-
-Now that we've saved the file in our personal copy of the repository, lets create a pull-request and get it published.
-
-**Click the "Pull-Requests" tab on the upper left below your repository name:**
-
-
-
-**Then click the "New Pull Request" Button**
-
-
-
-Any time you are creating a pull-request, remember, the `base repository` is wherever you're trying to send the suggested changes, and the `head repository` is wherever you've made the changes.
-
-[](https://imgur.com/PqpNCuR.png)
-
-Once you're sure that you've included only changes you intended, and that you are making changes where you meant to, go ahead and "Create pull-request"
-
-
-
-Enter some comment and click "Create a pull-request" on this page:
-
-
-
-Now the project collaborators will recieve a notice that a pull-request has been submitted, and within a day or so (hopefully sooner) you're pull-request will have been accepted, or at least commented on.
-
-Should it take longer than you'd expect, visit [DIDecentral Discord Chat](https://discord.gg/eYm2XvZ) and check to see if anyone has seen your pull-request.
-
-## Changes After Request is Submitted
-
-After you submit a pull-request, you can continue to change the branch or repository where your pull-request originated, and any additional updates will be included in the request.
-{ .notice}
-
-Head over to [didecentral/community-website/pulls](https://github.com/didecentral/community-website/pulls) and you can see the active pull-requests.
-
-Whether you were working from a personal copy of the site, or a patch automatically created by GitHub after clicking the "edit this page" button, you can get there from this page:
-
-
-
-Clicking [info-bot:patch-2](https://github.com/info-bot/didecentral.github.io/tree/patch-2) leads me to the patch that was created and I can edit to my hearts content, here, if I'd like those edits to be included in the same pull-request.
-
-## Site Structure:
-
-```
-/_application
-/_blockchain
-/_multi-media
-/_organizations
-/_private-sector
-/_public-sector
-/_tech
-/_resources # This line and above are "categories" as explained in discord archive post
-/_data # Data files including authors.yml, and navigation.yml
-/assets # images javascript and css live here.
-/bookmark-donations # Upload your bookmarks export file here.
-/example-site # Find example posts here.
-/_includes # Partials used to inject modularized html blocks into pages
-/_layouts # These are large partials defining the layout of different page types
-/_pages # These don't require a dated filename, or get added to the blog feed.
-/_posts # This is where you'll be submitting a blog post
-/_sass
-/_site # This is the latest local build of the site, not the live version.
-/_config.yml # Site Configuration
-/Gemfile # Local Site Configuration
-/CNAME # Site url
-/index.html
-/favicon.ico
-/README.md
-```
-
-## That's all for now
-
-**Let us know in the comments if you have any questions!**
-
-### More Info
-
-* [jekyllrb.com/docs/posts](https://jekyllrb.com/docs/posts/)
-* [What is the JAMstack?](https://jamstack.org/)
- >You may have already seen or worked on a JAMstack site! They do not have to include all attributes of JavaScript, APIs, and Markup. They might be built using by hand, or with Jekyll, Hugo, Nuxt, Next, Gatsby, or another static site generator...
\ No newline at end of file
diff --git a/_HowToContribute/website-config-minimal-mistakes.md b/_HowToContribute/website-config-minimal-mistakes.md
deleted file mode 100644
index 166d021d..00000000
--- a/_HowToContribute/website-config-minimal-mistakes.md
+++ /dev/null
@@ -1,642 +0,0 @@
----
-title: "Minimal-Mistakes-Jekyll - Setup and Configuration"
-description: "Contributing to the websites of DIDecentral via GitHub, Jekyll and Minimal Mistakes."
-excerpt: >
- This is to help anyone to understand how we're using Minimal Mistakes to publish this and other web-sites. For contributors, or your own use, outside of this organization.
-header:
- caption: "Minimal Mistakes Setup and [Quick-Start](https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/)."
-date: 2019-07-04
-authors:
- - "Infominer"
- - "JuanSC"
-published: true
-last_modified_at: 2020-01-05
-redirect_to: https://web-work.tools/minimal-mistakes/contributors-guide/site-config/
-canonical_url: https://web-work.tools/minimal-mistakes/contributors-guide/site-config/
----
-
-This guide should make it easier for contributors to understand how this site works. It should also be useful as a way to learn the basics of using Jekyll with the Minimal Mistakes theme, to publish a website via GitHub pages.
-
-Granted, you don't *need* to know all of this to simply add content to a page.
-
-I'm just sharing this here, for anyone who is interested.
-
-## Why Minimal Mistakes?
-
-Generally speaking, I like to use and learn a variety of [static site generators](https://web-work.tools/static-site-generators/) and their themes.
-
-However, I've used Minimal Mistakes to publish large websites and small web-sites. It really works. It works well. Even before you know how to use all of it's features, its a really reliable framework.
-
-It supports an incredible variety of functions that simply work. So for building public-domain educational resources, it makes sense for me to stick with what's tried and true. I've tried to find other themes that offer a comprable feature set, and it's not easy.
-
-Much respect to [Michael Rose](https://mademistakes.com/)!!
-
-I've used a few of his themes; they are well put together, often ported to other SSGs besides Jekyll, and really a class of their own when it comes to Jekyll themes.
-
-## Getting Started
-
-* [Minimal-Mistakes Quick-Start Guide](https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/)
-* [GitHub Pages Starter Pack](https://web-work.tools/github-pages-starter-pack)
-
-You shouldn't need the above for our imediate purposes, but will likely find them useful at some point.
-
-* [mmistakes/minimal-mistakes](https://github.com/mmistakes/minimal-mistakes/)
-* [didecentral/decentralized-id.com](https://github.com/didecentral/decentralized-id.com)
-* [didecentral/community-website](https://github.com/didecenral/didecentral.github.io)
-
-
-### Pre-requisites
-
-You must have installed [Git](https://web-work.tools/command-line-git-ssh/),` and the [Ruby Bundler](https://bundler.io/).
-
-I'll also recommend using [VSCode](https://web-work.tools/content-creation/), because it's fully integrated with `git`, so that you don't have to worrying about learning git commands.
-
-Also, I usually create a new repository on github, first. Then I clone it locally, again, avoiding the terminal. Meaning we can learn git in more depth, at our leisure.
-
-### [Site Structure](https://mmistakes.github.io/minimal-mistakes/docs/structure/)
-
-Before we get started, here is a high-level view of the site-structure.
-
-* [minimal-mistakes](https://github.com/mmistakes/minimal-mistakes/)
-
-```
-minimal-mistakes
-├── _data # data files for customizing the theme
-| ├── navigation.yml # main navigation links
-| └── ui-text.yml # text used throughout the theme's UI
-├── _includes
-| ├── analytics-providers # snippets for analytics (Google and custom)
-| ├── comments-providers # snippets for comments
-| ├── footer # custom snippets to add to site footer
-| ├── head # custom snippets to add to site head
-| ├── feature_row # feature row helper
-| ├── gallery # image gallery helper
-| ├── group-by-array # group by array helper for archives
-| ├── nav_list # navigation list helper
-| ├── toc # table of contents helper
-| └── ...
-├── _layouts
-| ├── archive-taxonomy.html # tag/category archive for Jekyll Archives plugin
-| ├── archive.html # archive base
-| ├── categories.html # archive listing posts grouped by category
-| ├── category.html # archive listing posts grouped by specific category
-| ├── collection.html # archive listing documents in a specific collection
-| ├── compress.html # compresses HTML in pure Liquid
-| ├── default.html # base for all other layouts
-| ├── home.html # home page
-| ├── posts.html # archive listing posts grouped by year
-| ├── search.html # search page
-| ├── single.html # single document (post/page/etc)
-| ├── tag.html # archive listing posts grouped by specific tag
-| ├── tags.html # archive listing posts grouped by tags
-| └── splash.html # splash page
-├── _sass # SCSS partials
-├── assets
-| ├── css
-| | └── main.scss # main stylesheet, loads SCSS partials from _sass
-| ├── images # image assets for posts/pages/collections/etc.
-| ├── js
-| | ├── plugins # jQuery plugins
-| | ├── vendor # vendor scripts
-| | ├── _main.js # plugin settings and other scripts to load after jQuery
-| | └── main.min.js # optimized and concatenated script file loaded before
-├── _config.yml # site configuration
-├── Gemfile # gem file dependencies
-├── index.html # paginated home page showing recent posts
-└── package.json # NPM build scripts
-```
-
-
-### CSS - Stylesheets
-
-At the moment, I'm quite CSS agnostic. One thing at a time.. However, if you wanted to add a little style to the page, the community might appreciate that.
-
-* [mmistakes.github.io/minimal-mistakes/docs/stylesheets/](https://mmistakes.github.io/minimal-mistakes/docs/stylesheets/)
-
-The theme’s assets/css/main.css file is built from several SCSS partials located in _sass/ and is structured as follows:
-
-```
-minimal-mistakes
-├── _sass
-| └── minimal-mistakes
-| ├── vendor # vendor SCSS partials
-| | ├── breakpoint # media query mixins
-| | ├── magnific-popup # Magnific Popup lightbox
-| | └── susy # Susy grid system
-| ├── _animations.scss # animations
-| ├── _archive.scss # archives (list, grid, feature views)
-| ├── _base.scss # base HTML elements
-| ├── _buttons.scss # buttons
-| ├── _footer.scss # footer
-| ├── _masthead.scss # masthead
-| ├── _mixins.scss # mixins (em function, clearfix)
-| ├── _navigation.scss # nav links (breadcrumb, priority+, toc, pagination, etc.)
-| ├── _notices.scss # notices
-| ├── _page.scss # pages
-| ├── _print.scss # print styles
-| ├── _reset.scss # reset
-| ├── _sidebar.scss # sidebar
-| ├── _syntax.scss # syntax highlighting
-| ├── _tables.scss # tables
-| ├── _utilities.scss # utility classes (text/image alignment)
-| └── _variables.scss # theme defaults (fonts, colors, etc.)
-├── assets
-| ├── css
-| | └── main.scss # main stylesheet, loads SCSS partials in _sass
-
-
-```
-
->To make basic tweaks to theme’s style Sass variables can be overridden by adding to `