diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 0000000000000..262d6bd7b8616
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1,16 @@
+# Set default behavior to automatically normalize line endings.
+* text=auto
+
+# Force bash scripts to always use LF line endings so that if a repo is accessed
+# in Unix via a file share from Windows, the scripts will work.
+*.sh text eol=lf
+
+# Force batch scripts to always use CRLF line endings so that if a repo is accessed
+# in Windows via a file share from Linux, the scripts will work.
+*.{cmd,[cC][mM][dD]} text eol=crlf
+*.{bat,[bB][aA][tT]} text eol=crlf
+
+# Denote all files that are truly binary and should not be modified.
+*.png binary
+*.jpg binary
+*.ico binary
diff --git a/.github/workflows/pages-deploy.yml b/.github/workflows/pages-deploy.yml
new file mode 100644
index 0000000000000..8a3a42c9a1a7f
--- /dev/null
+++ b/.github/workflows/pages-deploy.yml
@@ -0,0 +1,83 @@
+name: "Build and deploy"
+on:
+ push:
+ branches:
+ - main
+ - master
+ paths-ignore:
+ - .gitignore
+ - README.md
+ - LICENSE
+
+ # Allows you to run this workflow manually from the Actions tab
+ workflow_dispatch:
+
+permissions:
+ contents: read
+ pages: write
+ id-token: write
+
+# Allow one concurrent deployment
+concurrency:
+ group: "pages"
+ cancel-in-progress: true
+
+jobs:
+ build:
+ runs-on: ubuntu-latest
+ environment:
+ name: github-pages
+
+ steps:
+ - name: Checkout
+ uses: actions/checkout@v3
+ with:
+ fetch-depth: 0
+ # submodules: true
+ # If using the 'assets' git submodule from Chirpy Starter, uncomment above
+ # (See: https://github.com/cotes2020/chirpy-starter/tree/main/assets)
+
+ - name: Setup Pages
+ id: pages
+ uses: actions/configure-pages@v1
+
+ - name: Setup Ruby
+ uses: ruby/setup-ruby@v1
+ with:
+ ruby-version: 3 # reads from a '.ruby-version' or '.tools-version' file if 'ruby-version' is omitted
+ bundler-cache: true
+
+ - name: NPM Install
+ run: npm ci
+
+ - name: Build TinaCMS
+ env:
+ TINA_PUBLIC_CLIENT_ID: ${{ secrets.TINA_PUBLIC_CLIENT_ID }}
+ TINA_TOKEN: ${{ secrets.TINA_TOKEN }}
+ run: npx tinacms build
+
+ - name: Build site
+ run: bundle exec jekyll b -d "_site${{ steps.pages.outputs.base_path }}"
+ env:
+ JEKYLL_ENV: "production"
+
+ - name: Test site
+ run: |
+ bundle exec htmlproofer _site --disable-external --allow_hash_href --no-enforce-https --allow-missing-href --ignore-files "_site/admin/index.html"
+
+ - name: Upload site artifact
+ uses: actions/upload-pages-artifact@v1
+ with:
+ path: "_site${{ steps.pages.outputs.base_path }}"
+
+ deploy:
+ name: "Deploy site"
+ environment:
+ name: github-pages
+ url: ${{ steps.deployment.outputs.page_url }}
+ runs-on: ubuntu-latest
+ needs: build
+ steps:
+ - name: Deploy to GitHub Pages
+ id: deployment
+ uses: actions/deploy-pages@v1
diff --git a/.gitignore b/.gitignore
index 62bf7251e6d5b..6765518e987a0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,10 +1,22 @@
+# hidden files
+.*
+!.git*
+!.editorconfig
+!.nojekyll
+!.travis.yml
+!.husky
+!.commitlintrc.json
+!.versionrc.json
+
+# bundler cache
_site
-.DS_Store
-.jekyll
-.jekyll-metadata
-.bundle
-.sass-cache
-Gemfile
-Gemfile.lock
+vendor
+
+# rubygem
+*.gem
+
+# npm dependencies
node_modules
-package.json
+
+admin/
+tina/env.bat
diff --git a/.gitmodules b/.gitmodules
new file mode 100644
index 0000000000000..58062c54bd367
--- /dev/null
+++ b/.gitmodules
@@ -0,0 +1,3 @@
+[submodule "assets/lib"]
+ path = assets/lib
+ url = https://github.com/cotes2020/chirpy-static-assets.git
diff --git a/.nojekyll b/.nojekyll
new file mode 100644
index 0000000000000..8b137891791fe
--- /dev/null
+++ b/.nojekyll
@@ -0,0 +1 @@
+
diff --git a/404.md b/404.md
deleted file mode 100644
index c2d3903feda33..0000000000000
--- a/404.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-layout: page
-title: 404 - Page not found
-permalink: /404.html
----
-
-Sorry, we can't find that page that you're looking for. You can try again by going [back to the homepage]({{ site.baseurl }}/).
-
-[]({{ site.baseurl }}/)
diff --git a/CNAME b/CNAME
index 8b137891791fe..4b6e08d90863f 100644
--- a/CNAME
+++ b/CNAME
@@ -1 +1 @@
-
+www.dowen.me.uk
diff --git a/Gemfile b/Gemfile
new file mode 100644
index 0000000000000..ba2fe4aede03f
--- /dev/null
+++ b/Gemfile
@@ -0,0 +1,28 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gem "jekyll-theme-chirpy", "~> 6.0", ">= 6.0.1"
+
+group :test do
+ gem "html-proofer", "~> 5.0.7"
+end
+
+# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
+# and associated library.
+platforms :mingw, :x64_mingw, :mswin, :jruby do
+ gem "tzinfo", ">= 1", "< 3"
+ gem "tzinfo-data"
+end
+
+# Performance-booster for watching directories on Windows
+gem 'wdm', '~> 0.1.1', :install_if => Gem.win_platform?
+
+# Jekyll <= 4.2.0 compatibility with Ruby 3.0
+gem 'nokogiri', '~> 1.15', '>= 1.15.2'
+
+gem "webrick", "~> 1.7"
+
+gem 'jekyll-redirect-from'
+
+gem 'jekyll-compose', group: [:jekyll_plugins]
diff --git a/Gemfile.lock b/Gemfile.lock
new file mode 100644
index 0000000000000..d5c16db47547a
--- /dev/null
+++ b/Gemfile.lock
@@ -0,0 +1,164 @@
+GEM
+ remote: https://rubygems.org/
+ specs:
+ Ascii85 (1.1.1)
+ addressable (2.8.6)
+ public_suffix (>= 2.0.2, < 6.0)
+ afm (0.2.2)
+ async (2.12.0)
+ console (~> 1.25, >= 1.25.2)
+ fiber-annotation
+ io-event (~> 1.6)
+ bigdecimal (3.1.8)
+ colorator (1.1.0)
+ concurrent-ruby (1.3.3)
+ console (1.25.2)
+ fiber-annotation
+ fiber-local (~> 1.1)
+ json
+ em-websocket (0.5.3)
+ eventmachine (>= 0.12.9)
+ http_parser.rb (~> 0)
+ ethon (0.16.0)
+ ffi (>= 1.15.0)
+ eventmachine (1.2.7)
+ ffi (1.17.0-x64-mingw-ucrt)
+ ffi (1.17.0-x86_64-linux-gnu)
+ fiber-annotation (0.2.0)
+ fiber-local (1.1.0)
+ fiber-storage
+ fiber-storage (0.1.2)
+ forwardable-extended (2.6.0)
+ google-protobuf (4.27.1-x64-mingw-ucrt)
+ bigdecimal
+ rake (>= 13)
+ google-protobuf (4.27.1-x86_64-linux)
+ bigdecimal
+ rake (>= 13)
+ hashery (2.1.2)
+ html-proofer (5.0.9)
+ addressable (~> 2.3)
+ async (~> 2.1)
+ nokogiri (~> 1.13)
+ pdf-reader (~> 2.11)
+ rainbow (~> 3.0)
+ typhoeus (~> 1.3)
+ yell (~> 2.0)
+ zeitwerk (~> 2.5)
+ http_parser.rb (0.8.0)
+ i18n (1.14.5)
+ concurrent-ruby (~> 1.0)
+ io-event (1.6.4)
+ jekyll (4.3.3)
+ addressable (~> 2.4)
+ colorator (~> 1.0)
+ em-websocket (~> 0.5)
+ i18n (~> 1.0)
+ jekyll-sass-converter (>= 2.0, < 4.0)
+ jekyll-watch (~> 2.0)
+ kramdown (~> 2.3, >= 2.3.1)
+ kramdown-parser-gfm (~> 1.0)
+ liquid (~> 4.0)
+ mercenary (>= 0.3.6, < 0.5)
+ pathutil (~> 0.9)
+ rouge (>= 3.0, < 5.0)
+ safe_yaml (~> 1.0)
+ terminal-table (>= 1.8, < 4.0)
+ webrick (~> 1.7)
+ jekyll-archives (2.2.1)
+ jekyll (>= 3.6, < 5.0)
+ jekyll-compose (0.12.0)
+ jekyll (>= 3.7, < 5.0)
+ jekyll-include-cache (0.2.1)
+ jekyll (>= 3.7, < 5.0)
+ jekyll-paginate (1.1.0)
+ jekyll-redirect-from (0.16.0)
+ jekyll (>= 3.3, < 5.0)
+ jekyll-sass-converter (3.0.0)
+ sass-embedded (~> 1.54)
+ jekyll-seo-tag (2.8.0)
+ jekyll (>= 3.8, < 5.0)
+ jekyll-sitemap (1.4.0)
+ jekyll (>= 3.7, < 5.0)
+ jekyll-theme-chirpy (6.5.5)
+ jekyll (~> 4.3)
+ jekyll-archives (~> 2.2)
+ jekyll-include-cache (~> 0.2)
+ jekyll-paginate (~> 1.1)
+ jekyll-redirect-from (~> 0.16)
+ jekyll-seo-tag (~> 2.8)
+ jekyll-sitemap (~> 1.4)
+ jekyll-watch (2.2.1)
+ listen (~> 3.0)
+ json (2.7.2)
+ kramdown (2.4.0)
+ rexml
+ kramdown-parser-gfm (1.1.0)
+ kramdown (~> 2.0)
+ liquid (4.0.4)
+ listen (3.9.0)
+ rb-fsevent (~> 0.10, >= 0.10.3)
+ rb-inotify (~> 0.9, >= 0.9.10)
+ mercenary (0.4.0)
+ nokogiri (1.16.6-x64-mingw-ucrt)
+ racc (~> 1.4)
+ nokogiri (1.16.6-x86_64-linux)
+ racc (~> 1.4)
+ pathutil (0.16.2)
+ forwardable-extended (~> 2.6)
+ pdf-reader (2.12.0)
+ Ascii85 (~> 1.0)
+ afm (~> 0.2.1)
+ hashery (~> 2.0)
+ ruby-rc4
+ ttfunk
+ public_suffix (5.1.1)
+ racc (1.8.0)
+ rainbow (3.1.1)
+ rake (13.2.1)
+ rb-fsevent (0.11.2)
+ rb-inotify (0.11.1)
+ ffi (~> 1.0)
+ rexml (3.3.0)
+ strscan
+ rouge (4.3.0)
+ ruby-rc4 (0.1.5)
+ safe_yaml (1.0.5)
+ sass-embedded (1.77.5-x64-mingw-ucrt)
+ google-protobuf (>= 3.25, < 5.0)
+ sass-embedded (1.77.5-x86_64-linux-gnu)
+ google-protobuf (>= 3.25, < 5.0)
+ strscan (3.1.0)
+ terminal-table (3.0.2)
+ unicode-display_width (>= 1.1.1, < 3)
+ ttfunk (1.8.0)
+ bigdecimal (~> 3.1)
+ typhoeus (1.4.1)
+ ethon (>= 0.9.0)
+ tzinfo (2.0.6)
+ concurrent-ruby (~> 1.0)
+ tzinfo-data (1.2024.1)
+ tzinfo (>= 1.0.0)
+ unicode-display_width (2.5.0)
+ wdm (0.1.1)
+ webrick (1.8.1)
+ yell (2.2.2)
+ zeitwerk (2.6.16)
+
+PLATFORMS
+ x64-mingw-ucrt
+ x86_64-linux
+
+DEPENDENCIES
+ html-proofer (~> 5.0.7)
+ jekyll-compose
+ jekyll-redirect-from
+ jekyll-theme-chirpy (~> 6.0, >= 6.0.1)
+ nokogiri (~> 1.15, >= 1.15.2)
+ tzinfo (>= 1, < 3)
+ tzinfo-data
+ wdm (~> 0.1.1)
+ webrick (~> 1.7)
+
+BUNDLED WITH
+ 2.4.13
diff --git a/LICENSE b/LICENSE
index 40e6030143cb3..a6f6c9fed8620 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,20 +1,21 @@
-The MIT License (MIT)
+MIT License
-Copyright (c) 2015 Barry Clark
+Copyright (c) 2021 Cotes Chung
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
\ No newline at end of file
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
index 45c202063a374..c1b0375c34f23 100644
--- a/README.md
+++ b/README.md
@@ -1,120 +1,46 @@
-> March, 2016: If you're on an old version of Jekyll Now and run into a) build warnings or b) syntax highlighting issues caused by [Jekyll 3 and GitHub Pages updates](https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0), just :sparkles:[update your _config.yml](https://github.com/barryclark/jekyll-now/pull/445/files):sparkles: and you'll be set!
+# Chirpy Starter [](https://rubygems.org/gems/jekyll-theme-chirpy) [][mit]
-# Jekyll Now
+When installing the [**Chirpy**][chirpy] theme through [RubyGems.org][gem], Jekyll can only read files in the folders `_includes`, `_layout`, `_sass` and `assets`, as well as a small part of options of the `_config.yml` file from the theme's gem. If you have ever installed this theme gem, you can use the command `bundle info --path jekyll-theme-chirpy` to locate these files.
-**Jekyll** is a static site generator that's perfect for GitHub hosted blogs ([Jekyll Repository](https://github.com/jekyll/jekyll))
+The Jekyll organization claims that this is to leave the ball in the user’s court, but this also results in users not being able to enjoy the out-of-the-box experience when using feature-rich themes.
-**Jekyll Now** makes it easier to create your Jekyll blog, by eliminating a lot of the up front setup.
+To fully use all the features of **Chirpy**, you need to copy the other critical files from the theme's gem to your Jekyll site. The following is a list of targets:
-- You don't need to touch the command line
-- You don't need to install/configure ruby, rvm/rbenv, ruby gems :relaxed:
-- You don't need to install runtime dependencies like markdown processors, Pygments, etc
-- If you're on Windows, this will make setting up Jekyll a lot easier
-- It's easy to try out, you can just delete your forked repository if you don't like it
+```shell
+.
+├── _config.yml
+├── _data
+├── _plugins
+├── _tabs
+└── index.html
+```
-In a few minutes you'll be set up with a minimal, responsive blog like the one below giving you more time to spend on writing epic blog posts!
+In order to save your time, and to prevent you from missing some files when copying, we extract those files/configurations of the latest version of the **Chirpy** theme and the [CD][CD] workflow to here, so that you can start writing in minutes.
-
+## Prerequisites
-## Quick Start
+Follow the instructions in the [Jekyll Docs](https://jekyllrb.com/docs/installation/) to complete the installation of `Ruby`, `RubyGems`, `Jekyll` and `Bundler`.
-### Step 1) Fork Jekyll Now to your User Repository
+## Installation
-Fork this repo, then rename the repository to yourgithubusername.github.io.
+[**Use this template**][use-template] to generate a brand new repository and name it `.github.io`, where `GH_USERNAME` represents your GitHub username.
-Your Jekyll blog will often be viewable immediately at (if it's not, you can often force it to build by completing step 2)
+Then clone it to your local machine and run:
-
+```
+$ bundle
+```
-### Step 2) Customize and view your site
+## Usage
-Enter your site name, description, avatar and many other options by editing the _config.yml file. You can easily turn on Google Analytics tracking, Disqus commenting and social icons here too.
+Please see the [theme's docs](https://github.com/cotes2020/jekyll-theme-chirpy#documentation).
-Making a change to _config.yml (or any file in your repository) will force GitHub Pages to rebuild your site with jekyll. Your rebuilt site will be viewable a few seconds later at - if not, give it ten minutes as GitHub suggests and it'll appear soon
+## License
-> There are 3 different ways that you can make changes to your blog's files:
+This work is published under [MIT][mit] License.
-> 1. Edit files within your new username.github.io repository in the browser at GitHub.com (shown below).
-> 2. Use a third party GitHub content editor, like [Prose by Development Seed](http://prose.io). It's optimized for use with Jekyll making markdown editing, writing drafts, and uploading images really easy.
-> 3. Clone down your repository and make updates locally, then push them to your GitHub repository.
-
-
-
-### Step 3) Publish your first blog post
-
-Edit `/_posts/2014-3-3-Hello-World.md` to publish your first blog post. This [Markdown Cheatsheet](http://www.jekyllnow.com/Markdown-Style-Guide/) might come in handy.
-
-
-
-> You can add additional posts in the browser on GitHub.com too! Just hit the + icon in `/_posts/` to create new content. Just make sure to include the [front-matter](http://jekyllrb.com/docs/frontmatter/) block at the top of each new blog post and make sure the post's filename is in this format: year-month-day-title.md
-
-## Local Development
-
-1. Install Jekyll and plug-ins in one fell swoop. `gem install github-pages` This mirrors the plug-ins used by GitHub Pages on your local machine including Jekyll, Sass, etc.
-2. Clone down your fork `git clone https://github.com/yourusername/yourusername.github.io.git`
-3. Serve the site and watch for markup/sass changes `jekyll serve`
-4. View your website at http://127.0.0.1:4000/
-5. Commit any changes and push everything to the master branch of your GitHub user repository. GitHub Pages will then rebuild and serve your website.
-
-## Moar!
-
-I've created a more detailed walkthrough, [**Build A Blog With Jekyll And GitHub Pages**](http://www.smashingmagazine.com/2014/08/01/build-blog-jekyll-github-pages/) over at the Smashing Magazine website. Check it out if you'd like a more detailed walkthrough and some background on Jekyll. :metal:
-
-It covers:
-
-- A more detailed walkthrough of setting up your Jekyll blog
-- Common issues that you might encounter while using Jekyll
-- Importing from Wordpress, using your own domain name, and blogging in your favorite editor
-- Theming in Jekyll, with Liquid templating examples
-- A quick look at Jekyll 2.0’s new features, including Sass/Coffeescript support and Collections
-
-## Jekyll Now Features
-
-✓ Command-line free _fork-first workflow_, using GitHub.com to create, customize and post to your blog
-✓ Fully responsive and mobile optimized base theme (**[Theme Demo](http://jekyllnow.com)**)
-✓ Sass/Coffeescript support using Jekyll 2.0
-✓ Free hosting on your GitHub Pages user site
-✓ Markdown blogging
-✓ Syntax highlighting
-✓ Disqus commenting
-✓ Google Analytics integration
-✓ SVG social icons for your footer
-✓ 3 http requests, including your avatar
-
-✘ No installing dependencies
-✘ No need to set up local development
-✘ No configuring plugins
-✘ No need to spend time on theming
-✘ More time to code other things ... wait ✓!
-
-## Questions?
-
-[Open an Issue](https://github.com/barryclark/jekyll-now/issues/new) and let's chat!
-
-## Other forkable themes
-
-You can use the [Quick Start](https://github.com/barryclark/jekyll-now#quick-start) workflow with other themes that are set up to be forked too! Here are some of my favorites:
-
-- [Hyde](https://github.com/poole/hyde) by MDO
-- [Lanyon](https://github.com/poole/lanyon) by MDO
-- [mojombo.github.io](https://github.com/mojombo/mojombo.github.io) by Tom Preston-Werner
-- [Left](https://github.com/holman/left) by Zach Holman
-- [Minimal Mistakes](https://github.com/mmistakes/minimal-mistakes) by Michael Rose
-- [Skinny Bones](https://github.com/mmistakes/skinny-bones-jekyll) by Michael Rose
-
-## Credits
-
-- [Jekyll](https://github.com/jekyll/jekyll) - Thanks to its creators, contributors and maintainers.
-- [SVG icons](https://github.com/neilorangepeel/Free-Social-Icons) - Thanks, Neil Orange Peel. They're beautiful.
-- [Solarized Light Pygments](https://gist.github.com/edwardhotchkiss/2005058) - Thanks, Edward.
-- [Joel Glovier](http://joelglovier.com/writing/) - Great Jekyll articles. I used Joel's feed.xml in this repository.
-- [David Furnes](https://github.com/dfurnes), [Jon Uy](https://github.com/jonuy), [Luke Patton](https://github.com/lkpttn) - Thanks for the design/code reviews.
-- [Bart Kiers](https://github.com/bkiers), [Florian Simon](https://github.com/vermluh), [Henry Stanley](https://github.com/henryaj), [Hun Jae Lee](https://github.com/hunjaelee), [Javier Cejudo](https://github.com/javiercejudo), [Peter Etelej](https://github.com/etelej), [Ben Abbott](https://github.com/jaminscript), [Ray Nicholus](https://github.com/rnicholus), [Erin Grand](https://github.com/eringrand), [Léo Colombaro](https://github.com/LeoColomb), [Dean Attali](https://github.com/daattali), [Clayton Errington](https://github.com/cjerrington), [Colton Fitzgerald](https://github.com/coltonfitzgerald), [Trace Mayer](https://github.com/sunnankar) - Thanks for your [fantastic contributions](https://github.com/barryclark/jekyll-now/commits/master) to the project!
-
-## Contributing
-
-Issues and Pull Requests are greatly appreciated. If you've never contributed to an open source project before I'm more than happy to walk you through how to create a pull request.
-
-You can start by [opening an issue](https://github.com/barryclark/jekyll-now/issues/new) describing the problem that you're looking to resolve and we'll go from there.
-
-I want to keep Jekyll Now as minimal as possible. Every line of code should be one that's useful to 90% of the people using it. Please bear that in mind when submitting feature requests. If it's not something that most people will use, it probably won't get merged. :guardsman:
+[gem]: https://rubygems.org/gems/jekyll-theme-chirpy
+[chirpy]: https://github.com/cotes2020/jekyll-theme-chirpy/
+[use-template]: https://github.com/cotes2020/chirpy-starter/generate
+[CD]: https://en.wikipedia.org/wiki/Continuous_deployment
+[mit]: https://github.com/cotes2020/chirpy-starter/blob/master/LICENSE
diff --git a/_config.yml b/_config.yml
index d4916414195c9..655d36149b5b7 100644
--- a/_config.yml
+++ b/_config.yml
@@ -1,86 +1,220 @@
-#
-# This file contains configuration flags to customize your site
-#
+# The Site Configuration
-# Name of your site (displayed in the header)
-name: Your Name
+# Import the theme
+theme: jekyll-theme-chirpy
-# Short bio or description (displayed in the header)
-description: Web Developer from Somewhere
+# Change the following value to '/PROJECT_NAME' ONLY IF your site type is GitHub Pages Project sites
+# and doesn't have a custom domain.
+baseurl: ''
-# URL of your avatar or profile pic (you could use your GitHub profile pic)
-avatar: https://raw.githubusercontent.com/barryclark/jekyll-now/master/images/jekyll-logo.png
+# The language of the webpage › http://www.lingoes.net/en/translator/langcode.htm
+# If it has the same name as one of the files in folder `_data/locales`, the layout language will also be changed,
+# otherwise, the layout language will use the default value of 'en'.
+lang: en
-#
-# Flags below are optional
-#
+# Additional parameters for datetime localization, optional. › https://github.com/iamkun/dayjs/tree/dev/src/locale
+prefer_datetime_locale: en-gb
-# Includes an icon in the footer for each username you enter
-footer-links:
- dribbble:
- email:
- facebook:
- flickr:
- github: barryclark/jekyll-now
- instagram:
- linkedin:
- pinterest:
- rss: # just type anything here for a working RSS icon
- twitter: jekyllrb
- stackoverflow: # your stackoverflow profile, e.g. "users/50476/bart-kiers"
- youtube: # channel/ or user/
- googleplus: # anything in your profile username that comes after plus.google.com/
-
-
-# Enter your Disqus shortname (not your username) to enable commenting on posts
-# You can find your shortname on the Settings page of your Disqus account
-disqus:
-
-# Enter your Google Analytics web tracking code (e.g. UA-2110908-2) to activate tracking
-google_analytics:
+# Change to your timezone › http://www.timezoneconverter.com/cgi-bin/findzone/findzone
+timezone: Europe/London
+
+# jekyll-seo-tag settings › https://github.com/jekyll/jekyll-seo-tag/blob/master/docs/usage.md
+# ↓ --------------------------
+
+title: Ben Dowen # the main title
+
+tagline: Software Adventurer, Quality Explorer, Testing Advocate # it will display as the sub-title
+
+description: >- # used by seo meta and the atom feed
+ Ben Dowen, the Full Snack Tester, blogs about Software Testing, Quality and Agile Software Development.
+
+# fill in the protocol & hostname for your site, e.g., 'https://username.github.io'
+url: 'https://www.dowen.me.uk'
+
+github:
+ username: dowenb # change to your github username
-# Your website URL (e.g. http://barryclark.github.io or http://www.barryclark.co)
-# Used for Sitemap.xml and your RSS feed
-url:
+twitter:
+ username: FullSnackTester # change to your twitter username
-# If you're hosting your site at a Project repository on GitHub pages
-# (http://yourusername.github.io/repository-name)
-# and NOT your User repository (http://yourusername.github.io)
-# then add in the baseurl here, like this: "/repository-name"
-baseurl: ""
+social:
+ # Change to your full name.
+ # It will be displayed as the default author of the posts and the copyright owner in the Footer
+ name: Ben Dowen
+ email: ben@dowen.me.uk # change to your email address
+ links:
+ # The first element serves as the copyright owner's link
+ - https://twitter.com/fullsnacktester # change to your twitter homepage
+ - https://github.com/dowenb # change to your github homepage
+ # Uncomment below to add more social links
+ # - https://www.facebook.com/username
+ - https://www.linkedin.com/in/dowenb
+google_site_verification: # fill in to your verification string
+
+# ↑ --------------------------
+# The end of `jekyll-seo-tag` settings
+
+google_analytics:
+ id: # fill in your Google Analytics ID
+ # Google Analytics pageviews report settings
+ pv:
+ proxy_endpoint: # fill in the Google Analytics superProxy endpoint of Google App Engine
+ cache_path: # the local PV cache data, friendly to visitors from GFW region
+
+# Prefer color scheme setting.
#
-# !! You don't need to change any of the configuration flags below !!
+# Note: Keep empty will follow the system prefer color by default,
+# and there will be a toggle to switch the theme between dark and light
+# on the bottom left of the sidebar.
#
+# Available options:
+#
+# light - Use the light color scheme
+# dark - Use the dark color scheme
+#
+theme_mode: # [light|dark]
-permalink: /:title/
-
-# The release of Jekyll Now that you're using
-version: v1.2.0
+# The CDN endpoint for images.
+# Notice that once it is assigned, the CDN url
+# will be added to all image (site avatar & posts' images) paths starting with '/'
+#
+# e.g. 'https://cdn.com'
+img_cdn:
+
+# the avatar on sidebar, support local or CORS resources
+avatar: /uploads/avatar.png
+
+# boolean type, the global switch for ToC in posts.
+toc: true
+
+comments:
+ active: # The global switch for posts comments, e.g., 'disqus'. Keep it empty means disable
+ # The active options are as follows:
+ disqus:
+ shortname: # fill with the Disqus shortname. › https://help.disqus.com/en/articles/1717111-what-s-a-shortname
+ # utterances settings › https://utteranc.es/
+ utterances:
+ repo: # /
+ issue_term: # < url | pathname | title | ...>
+ # Giscus options › https://giscus.app
+ giscus:
+ repo: # /
+ repo_id:
+ category:
+ category_id:
+ mapping: # optional, default to 'pathname'
+ input_position: # optional, default to 'bottom'
+ lang: # optional, default to the value of `site.lang`
+
+# Self-hosted static assets, optional › https://github.com/cotes2020/chirpy-static-assets
+assets:
+ self_host:
+ enabled: # boolean, keep empty means false
+ # specify the Jekyll environment, empty means both
+ # only works if `assets.self_host.enabled` is 'true'
+ env: # [development|production]
+
+pwa:
+ enabled: true # the option for PWA feature
+
+paginate: 10
+
+# ------------ The following options are not recommended to be modified ------------------
-# Jekyll 3 now only supports Kramdown for Markdown
kramdown:
- # Use GitHub flavored markdown, including triple backtick fenced code blocks
- input: GFM
- # Jekyll 3 and GitHub Pages now only support rouge for syntax highlighting
syntax_highlighter: rouge
- syntax_highlighter_opts:
- # Use existing pygments syntax highlighting css
- css_class: 'highlight'
+ syntax_highlighter_opts: # Rouge Options › https://github.com/jneen/rouge#full-options
+ css_class: highlight
+ # default_lang: console
+ span:
+ line_numbers: false
+ block:
+ line_numbers: true
+ start_line: 1
+
+collections:
+ tabs:
+ output: true
+ sort_by: order
+
+defaults:
+ - scope:
+ path: '' # An empty string here means all files in the project
+ type: posts
+ values:
+ layout: post
+ comments: true # Enable comments in posts.
+ toc: true # Display TOC column in posts.
+ # DO NOT modify the following parameter unless you are confident enough
+ # to update the code of all other post links in this project.
+ permalink: /posts/:title/
+ - scope:
+ path: _drafts
+ values:
+ comments: false
+ - scope:
+ path: ''
+ type: tabs # see `site.collections`
+ values:
+ layout: page
+ permalink: /:title/
+ - scope:
+ path: assets/img/favicons
+ values:
+ swcache: true
+ - scope:
+ path: assets/js/dist
+ values:
+ swcache: true
-# Set the Sass partials directory, as we're using @imports
sass:
- style: :expanded # You might prefer to minify using :compressed
+ style: compressed
-# Use the following plug-ins
-gems:
- - jekyll-sitemap # Create a sitemap using the official Jekyll sitemap gem
- - jekyll-feed # Create an Atom feed using the official Jekyll feed gem
+compress_html:
+ clippings: all
+ comments: all
+ endings: all
+ profile: false
+ blanklines: false
+ ignore:
+ envs: [development]
-# Exclude these files from your production _site
exclude:
- - Gemfile
- - Gemfile.lock
- - LICENSE
+ - '*.gem'
+ - '*.gemspec'
+ - tools
- README.md
- - CNAME
+ - CHANGELOG.md
+ - LICENSE
+ - gulpfile.js
+ - node_modules
+ - package*.json
+
+jekyll-archives:
+ enabled: [categories, tags]
+ layouts:
+ category: category
+ tag: tag
+ permalinks:
+ tag: /tags/:name/
+ category: /categories/:name/
+
+plugins:
+ - jekyll-redirect-from
+
+jekyll_compose:
+ default_front_matter:
+ drafts:
+ description:
+ image:
+ category:
+ tags:
+ posts:
+ description:
+ image:
+ category:
+ tags:
+ published: false
+ sitemap: false
+
\ No newline at end of file
diff --git a/_data/assets/cross_origin.yml b/_data/assets/cross_origin.yml
new file mode 100644
index 0000000000000..13e37cf95dc5a
--- /dev/null
+++ b/_data/assets/cross_origin.yml
@@ -0,0 +1,62 @@
+# CDNs
+
+cdns:
+ # Google Fonts
+ - url: https://fonts.googleapis.com
+ - url: https://fonts.gstatic.com
+ args: crossorigin
+ - url: https://fonts.googleapis.com
+ # jsDelivr CDN
+ - url: https://cdn.jsdelivr.net
+
+# fonts
+
+webfonts: https://fonts.googleapis.com/css2?family=Lato&family=Source+Sans+Pro:wght@400;600;700;900&display=swap
+
+# Libraries
+
+jquery:
+ js: https://cdn.jsdelivr.net/npm/jquery@3/dist/jquery.min.js
+
+bootstrap:
+ css: https://cdn.jsdelivr.net/npm/bootstrap@4/dist/css/bootstrap.min.css
+ js: https://cdn.jsdelivr.net/npm/bootstrap@4/dist/js/bootstrap.bundle.min.js
+
+bootstrap-toc:
+ css: https://cdn.jsdelivr.net/gh/afeld/bootstrap-toc@1.0.1/dist/bootstrap-toc.min.css
+ js: https://cdn.jsdelivr.net/gh/afeld/bootstrap-toc@1.0.1/dist/bootstrap-toc.min.js
+
+fontawesome:
+ css: https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5.11.2/css/all.min.css
+
+search:
+ js: https://cdn.jsdelivr.net/npm/simple-jekyll-search@1.10.0/dest/simple-jekyll-search.min.js
+
+mermaid:
+ js: https://cdn.jsdelivr.net/npm/mermaid@8/dist/mermaid.min.js
+
+dayjs:
+ js:
+ common: https://cdn.jsdelivr.net/npm/dayjs@1/dayjs.min.js
+ locale: https://cdn.jsdelivr.net/npm/dayjs@1/locale/:LOCALE.min.js
+ relativeTime: https://cdn.jsdelivr.net/npm/dayjs@1/plugin/relativeTime.min.js
+ localizedFormat: https://cdn.jsdelivr.net/npm/dayjs@1/plugin/localizedFormat.min.js
+
+countup:
+ js: https://cdn.jsdelivr.net/npm/countup.js@1.9.3/dist/countUp.min.js
+
+magnific-popup:
+ css: https://cdn.jsdelivr.net/npm/magnific-popup@1/dist/magnific-popup.min.css
+ js: https://cdn.jsdelivr.net/npm/magnific-popup@1/dist/jquery.magnific-popup.min.js
+
+lozad:
+ js: https://cdn.jsdelivr.net/npm/lozad/dist/lozad.min.js
+
+clipboard:
+ js: https://cdn.jsdelivr.net/npm/clipboard@2/dist/clipboard.min.js
+
+polyfill:
+ js: https://polyfill.io/v3/polyfill.min.js?features=es6
+
+mathjax:
+ js: https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-chtml.js
diff --git a/_data/assets/self_host.yml b/_data/assets/self_host.yml
new file mode 100644
index 0000000000000..ae5a399cd8109
--- /dev/null
+++ b/_data/assets/self_host.yml
@@ -0,0 +1,51 @@
+# fonts
+
+webfonts: /assets/lib/fonts/main.css
+
+# Libraries
+
+jquery:
+ js: /assets/lib/jquery-3.6.0/jquery.min.js
+
+bootstrap:
+ css: /assets/lib/bootstrap-4.6.1/bootstrap.min.css
+ js: /assets/lib/bootstrap-4.6.1/bootstrap.bundle.min.js
+
+bootstrap-toc:
+ css: /assets/lib/bootstrap-toc-1.0.1/bootstrap-toc.min.css
+ js: /assets/lib/bootstrap-toc-1.0.1/bootstrap-toc.min.js
+
+fontawesome:
+ css: /assets/lib/fontawesome-free-5.15.4/css/all.min.css
+
+search:
+ js: /assets/lib/simple-jekyll-search-1.10.0/simple-jekyll-search.min.js
+
+mermaid:
+ js: /assets/lib/mermaid-8.13.10/mermaid.min.js
+
+dayjs:
+ js:
+ common: /assets/lib/dayjs-1.10.7/dayjs.min.js
+ locale: /assets/lib/dayjs-1.10.7/locale/en.min.js
+ relativeTime: /assets/lib/dayjs-1.10.7/plugin/relativeTime.min.js
+ localizedFormat: /assets/lib/dayjs-1.10.7/plugin/localizedFormat.min.js
+
+countup:
+ js: /assets/lib/countup.js-1.9.3/countUp.min.js
+
+magnific-popup:
+ css: /assets/lib/magnific-popup-1.1.0/magnific-popup.css
+ js: /assets/lib/magnific-popup-1.1.0/jquery.magnific-popup.min.js
+
+lozad:
+ js: /assets/lib/lozad-1.16.0/lozad.min.js
+
+clipboard:
+ js: /assets/lib/clipboard-2.0.9/clipboard.min.js
+
+polyfill:
+ js: /assets/lib/polyfill-v3-es6/polyfill.min.js
+
+mathjax:
+ js: /assets/lib/mathjax-3.2.0/tex-chtml.js
diff --git a/_data/contact.yml b/_data/contact.yml
new file mode 100644
index 0000000000000..05da2f21ac4c1
--- /dev/null
+++ b/_data/contact.yml
@@ -0,0 +1,30 @@
+# The contact options.
+
+-
+ type: github
+ icon: 'fab fa-github'
+-
+ type: twitter
+ icon: 'fab fa-twitter'
+-
+ type: email
+ icon: 'fas fa-envelope'
+ noblank: true # open link in current tab
+-
+ type: rss
+ icon: 'fas fa-rss'
+ noblank: true
+
+# Uncomment and complete the url below to enable more contact options
+# -
+# type: mastodon
+# icon: 'fab fa-mastodon' # icons powered by
+# url: '' # Fill with your mastodon account page
+# -
+# type: linkedin
+# icon: 'fab fa-linkedin' # icons powered by
+# url: '' # Fill with your Linkedin homepage
+# -
+# type: stack-overflow
+# icon: 'fab fa-stack-overflow'
+# url: '' # Fill with your stackoverflow homepage
diff --git a/_data/locales/bg-BG.yml b/_data/locales/bg-BG.yml
new file mode 100644
index 0000000000000..fe601bb77edc0
--- /dev/null
+++ b/_data/locales/bg-BG.yml
@@ -0,0 +1,83 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Публикация
+ category: Категория
+ tag: Тагове
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Начало
+ categories: Категории
+ tags: Тагове
+ archives: Архив
+ about: За мен
+
+# the text displayed in the search bar & search results
+search:
+ hint: търси
+ cancel: Отмени
+ no_results: Упс! Не са намерени резултати.
+
+panel:
+ lastmod: Наскоро обновени
+ trending_tags: Популярни тагове
+ toc: Съдържание
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Тази публикация е лицензирана под :LICENSE_NAME от автора.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Някои права запазени.
+ verbose: >-
+ Освен ако не е посочено друго, публикациите в блога на този сайт са лицензирани
+ под лиценза Creative Commons Attribution 4.0 (CC BY 4.0) от автора.
+
+meta: Създадено чрез :PLATFORM и :THEME тема.
+
+not_found:
+ statment: Съжалявам, но този на този URL адрес няма налично съдържание.
+
+notification:
+ update_found: Налична е нова версия на съдържанието.
+ update: Обнови
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Автор
+ posted: Публикувана
+ updated: Обновена
+ words: думи
+ pageview_measure: преглеждания
+ read_time:
+ unit: мин
+ prompt: четиво
+ relate_posts: Още за четене
+ share: Споделете
+ button:
+ next: По-нови
+ previous: По-стари
+ copy_code:
+ succeed: Копирано!
+ share_link:
+ title: Копирай линк
+ succeed: Линкът е копиран успешно!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Прикрепен
+
+# categories page
+categories:
+ category_measure:
+ singular: категория
+ plural: категории
+ post_measure:
+ singular: публикация
+ plural: публикации
diff --git a/_data/locales/de-DE.yml b/_data/locales/de-DE.yml
new file mode 100644
index 0000000000000..3088a3c45ee18
--- /dev/null
+++ b/_data/locales/de-DE.yml
@@ -0,0 +1,82 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Eintrag
+ category: Kategorie
+ tag: Tag
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Startseite
+ categories: Kategorien
+ tags: Tags
+ archives: Archiv
+ about: Über
+
+# the text displayed in the search bar & search results
+search:
+ hint: Suche
+ cancel: Abbrechen
+ no_results: Ups! Keine Einträge gefunden.
+
+panel:
+ lastmod: Kürzlich aktualisiert
+ trending_tags: Beliebte Tags
+ toc: Inhalt
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Dieser Eintrag ist vom Autor unter :LICENSE_NAME lizensiert.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Einige Rechte vorbehalten.
+ verbose: >-
+ Alle Einträge auf dieser Seite stehen, soweit nicht anders angegeben, unter der Lizenz Creative Commons Attribution 4.0 (CC BY 4.0).
+
+meta: Powered by :PLATFORM with :THEME theme.
+
+not_found:
+ statment: Entschuldigung, dieser Link verweist auf keine vorhandene Ressource.
+
+notification:
+ update_found: Eine neue Version ist verfügbar.
+ update: Neue Version
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Von
+ posted: Veröffentlicht
+ updated: Aktualisiert
+ words: Wörter
+ pageview_measure: Aufrufe
+ read_time:
+ unit: Minuten
+ prompt: lesen
+ relate_posts: Weiterlesen
+ share: Teilen
+ button:
+ next: Nächster Eintrag
+ previous: Eintrag vorher
+ copy_code:
+ succeed: Kopiert!
+ share_link:
+ title: Link kopieren
+ succeed: Link erfolgreich kopiert!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Angepinnt
+
+# categories page
+categories:
+ category_measure:
+ singular: Kategorie
+ plural: Kategorien
+ post_measure:
+ singular: Eintrag
+ plural: Einträge
diff --git a/_data/locales/en.yml b/_data/locales/en.yml
new file mode 100644
index 0000000000000..14394a6aec4ce
--- /dev/null
+++ b/_data/locales/en.yml
@@ -0,0 +1,83 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Post
+ category: Category
+ tag: Tag
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Home
+ categories: Categories
+ tags: Tags
+ archives: Archives
+ about: About
+
+# the text displayed in the search bar & search results
+search:
+ hint: search
+ cancel: Cancel
+ no_results: Oops! No results found.
+
+panel:
+ lastmod: Recently Updated
+ trending_tags: Trending Tags
+ toc: Contents
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: This post is licensed under :LICENSE_NAME by the author.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Some rights reserved.
+ verbose: >-
+ Except where otherwise noted, the blog posts on this site are licensed
+ under the Creative Commons Attribution 4.0 International (CC BY 4.0) License by the author.
+
+meta: Powered by :PLATFORM with :THEME theme.
+
+not_found:
+ statment: Sorry, we've misplaced that URL or it's pointing to something that doesn't exist.
+
+notification:
+ update_found: A new version of content is available.
+ update: Update
+
+# ----- Posts related labels -----
+
+post:
+ written_by: By
+ posted: Posted
+ updated: Updated
+ words: words
+ pageview_measure: views
+ read_time:
+ unit: min
+ prompt: read
+ relate_posts: Further Reading
+ share: Share
+ button:
+ next: Newer
+ previous: Older
+ copy_code:
+ succeed: Copied!
+ share_link:
+ title: Copy link
+ succeed: Link copied successfully!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Pinned
+
+# categories page
+categories:
+ category_measure:
+ singular: category
+ plural: categories
+ post_measure:
+ singular: post
+ plural: posts
diff --git a/_data/locales/es-ES.yml b/_data/locales/es-ES.yml
new file mode 100644
index 0000000000000..ee3a20f9e4760
--- /dev/null
+++ b/_data/locales/es-ES.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Entrada
+ category: Categoría
+ tag: Etiqueta
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Inicio
+ categories: Categorías
+ tags: Etiquetas
+ archives: Archivo
+ about: Acerca de
+
+# the text displayed in the search bar & search results
+search:
+ hint: Buscar
+ cancel: Cancelar
+ no_results: ¡Oops! No se encuentran resultados.
+
+panel:
+ lastmod: Actualizado recientemente
+ trending_tags: Etiquetas populares
+ toc: Contenido
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Esta entrada está licenciada bajo :LICENSE_NAME por el autor.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Algunos derechos reservados.
+ verbose: >-
+ Salvo que se indique explícitamente, las entradas de este blog están licenciadas
+ bajo la Creative Commons Attribution 4.0 International (CC BY 4.0) License por el autor.
+
+meta: Hecho con :PLATFORM usando el tema :THEME.
+
+not_found:
+ statment: Lo sentimos, hemos perdido esa URL o apunta a algo que no existe.
+
+notification:
+ update_found: Hay una nueva versión de contenido disponible.
+ update: Actualizar
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Por
+ posted: Publicado
+ updated: Actualizado
+ words: palabras
+ pageview_measure: visitas
+ read_time:
+ unit: min
+ prompt: ' de lectura'
+ relate_posts: Lecturas adicionales
+ share: Compartir
+ button:
+ next: Nuevo
+ previous: Anterior
+ copy_code:
+ succeed: ¡Copiado!
+ share_link:
+ title: Copiar enlace
+ succeed: ¡Enlace copiado!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Fijado
+
+# categories page
+categories:
+ category_measure: categorias
+ post_measure: entradas
diff --git a/_data/locales/fr-FR.yml b/_data/locales/fr-FR.yml
new file mode 100644
index 0000000000000..0d29a87082c49
--- /dev/null
+++ b/_data/locales/fr-FR.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Post
+ category: Catégorie
+ tag: Tag
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Accueil
+ categories: Catégories
+ tags: Tags
+ archives: Archives
+ about: A propos de
+
+# the text displayed in the search bar & search results
+search:
+ hint: recherche
+ cancel: Annuler
+ no_results: Oups ! Aucun résultat trouvé.
+
+panel:
+ lastmod: Récemment mis à jour
+ trending_tags: Tags tendance
+ toc: Contenu
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Cet article est sous licence :LICENSE_NAME par l'auteur.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Certains droits réservés.
+ verbose: >-
+ Sauf mention contraire, les articles de ce site sont publiés sous licence
+ sous la licence Creative Commons Attribution 4.0 International (CC BY 4.0) par l'auteur.
+
+meta: Propulsé par :PLATFORM avec le thème :THEME
+
+not_found:
+ statment: Désolé, nous avons égaré cette URL ou elle pointe vers quelque chose qui n'existe pas.
+
+notification:
+ update_found: Une nouvelle version du contenu est disponible.
+ update: Mise à jour
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Par
+ posted: Posté
+ updated: Mis à jour
+ words: mots
+ pageview_measure: vues
+ read_time:
+ unit: min
+ prompt: lire
+ relate_posts: Autres lectures
+ share: Partager
+ button:
+ next: Plus récent
+ previous: Plus ancien
+ copy_code:
+ succeed: Copié !
+ share_link:
+ title: Copier le lien
+ succeed: Lien copié avec succès !
+ # pinned prompt of posts list on homepage
+ pin_prompt: Épinglé
+
+# categories page
+categories:
+ category_measure: catégories
+ post_measure: posts
diff --git a/_data/locales/hu-HU.yml b/_data/locales/hu-HU.yml
new file mode 100644
index 0000000000000..395a8091c1030
--- /dev/null
+++ b/_data/locales/hu-HU.yml
@@ -0,0 +1,81 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Bejegyzés
+ category: Kategória
+ tag: Címke
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Kezdőlap
+ categories: Kategóriák
+ tags: Címkék
+ archives: Archívum
+ about: Rólam
+
+# the text displayed in the search bar & search results
+search:
+ hint: keresés
+ cancel: Mégse
+ no_results: Oops! Nincs találat a keresésre.
+
+panel:
+ lastmod: Legutóbb frissítve
+ trending_tags: Népszerű Címkék
+ toc: Tartalom
+ links: Blog linkek
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: A bejegyzés :LICENSE_NAME licenccel rendelkezik.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Néhány jog fenntartva.
+ verbose: >-
+ Az oldalon található tartalmak
+ Creative Commons Attribution 4.0 International (CC BY 4.0) licenccel rendelkeznek,
+ hacsak másképp nincs jelezve.
+
+meta: Készítve :PLATFORM motorral :THEME témával.
+
+not_found:
+ statment: Sajnáljuk, az URL-t rosszul helyeztük el, vagy valami nem létezőre mutat.
+
+notification:
+ update_found: Elérhető a tartalom új verziója.
+ update: Frissítés
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Szerző
+ posted: Létrehozva
+ updated: Frissítve
+ words: szó
+ pageview_measure: látogató
+ read_time:
+ unit: perc
+ prompt: elolvasni
+ relate_posts: További olvasnivaló
+ share: Megosztás
+ button:
+ next: Újabb
+ previous: Régebbi
+ copy_code:
+ succeed: Másolva!
+ share_link:
+ title: Link másolása
+ succeed: Link sikeresen másolva!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Kitűzve
+
+# categories page
+categories:
+ category_measure: kategória
+ post_measure: bejegyzés
diff --git a/_data/locales/id-ID.yml b/_data/locales/id-ID.yml
new file mode 100644
index 0000000000000..59ec6617062f5
--- /dev/null
+++ b/_data/locales/id-ID.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Postingan
+ category: Kategori
+ tag: Tagar
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Beranda
+ categories: Kategori
+ tags: Tagar
+ archives: Arsip
+ about: Tentang
+
+# the text displayed in the search bar & search results
+search:
+ hint: Cari
+ cancel: Batal
+ no_results: Ups! Tidak ada hasil yang ditemukan.
+
+panel:
+ lastmod: Postingan Terbaru
+ trending_tags: Tagar Terpopuler
+ toc: Konten
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Postingan ini dilisensikan di bawah :LICENSE_NAME oleh penulis.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Sebagian konten dilindungi.
+ verbose: >-
+ Kecuali jika dinyatakan, Postingan blog di situs ini dilisensikan
+ di bawah Lisensi Creative Commons Attribution 4.0 International (CC BY 4.0) oleh penulis.
+
+meta: Didukung oleh :PLATFORM dengan tema :THEME.
+
+not_found:
+ statment: Maaf, kami gagal menemukan URL itu atau memang mengarah ke sesuatu yang tidak ada.
+
+notification:
+ update_found: Versi konten baru tersedia.
+ update: Perbarui
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Oleh
+ posted: Diterbitkan
+ updated: Diperbarui
+ words: kata
+ pageview_measure: dilihat
+ read_time:
+ unit: menit
+ prompt: baca
+ relate_posts: Postingan Lainya
+ share: Bagikan
+ button:
+ next: Terbaru
+ previous: Terlama
+ copy_code:
+ succeed: Disalin!
+ share_link:
+ title: Salin tautan
+ succeed: Tautan berhasil disalin!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Disematkan
+
+# categories page
+categories:
+ category_measure: kategori
+ post_measure: Postingan
diff --git a/_data/locales/ko-KR.yml b/_data/locales/ko-KR.yml
new file mode 100644
index 0000000000000..2fb9391b77a06
--- /dev/null
+++ b/_data/locales/ko-KR.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: 포스트
+ category: 카테고리
+ tag: 태그
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: 홈
+ categories: 카테고리
+ tags: 태그
+ archives: 아카이브
+ about: 정보
+
+# the text displayed in the search bar & search results
+search:
+ hint: 검색
+ cancel: 취소
+ no_results: 검색 결과가 없습니다.
+
+panel:
+ lastmod: 최근 업데이트
+ trending_tags: 인기 태그
+ toc: 바로가기
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: 이 기사는 저작권자의 :LICENSE_NAME 라이센스를 따릅니다.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: 일부 권리 보유
+ verbose: >-
+ 명시되지 않는 한 이 사이트의 블로그 게시물은 작성자의
+ Creative Commons Attribution 4.0 International(CC BY 4.0) 라이선스에 따라 사용이 허가되었습니다.
+
+meta: Powered by :PLATFORM with :THEME theme.
+
+not_found:
+ statment: 해당 URL은 존재하지 않습니다.
+
+notification:
+ update_found: 새 버전의 콘텐츠를 사용할 수 있습니다.
+ update: 업데이트
+
+# ----- Posts related labels -----
+
+post:
+ written_by: By
+ posted: 게시
+ updated: 업데이트
+ words: 단어
+ pageview_measure: 조회
+ read_time:
+ unit: 분
+ prompt: 읽는 시간
+ relate_posts: 관련된 글
+ share: 공유하기
+ button:
+ next: 다음 글
+ previous: 이전 글
+ copy_code:
+ succeed: 복사되었습니다!
+ share_link:
+ title: 링크 복사하기
+ succeed: 링크가 복사되었습니다!
+ # pinned prompt of posts list on homepage
+ pin_prompt: 핀
+
+# categories page
+categories:
+ category_measure: 카테고리
+ post_measure: 포스트
diff --git a/_data/locales/my-MM.yml b/_data/locales/my-MM.yml
new file mode 100644
index 0000000000000..9990c763cada5
--- /dev/null
+++ b/_data/locales/my-MM.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: ပို့စ်
+ category: ကဏ္ဍ
+ tag: နာမ(တက်ဂ်)
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: အဓိကစာမျက်နှာ
+ categories: ကဏ္ဍများ
+ tags: နာမ(တက်ဂ်)များ
+ archives: မှတ်တမ်းတိုက်
+ about: အကြောင်းအရာ
+
+# the text displayed in the search bar & search results
+search:
+ hint: ရှာဖွေမည်
+ cancel: ဖျက်သိမ်းမည်
+ no_results: အိုး! ဘာမှမရှိပါ
+
+panel:
+ lastmod: မကြာသေးမီကမွမ်းမံထားသည်
+ trending_tags: ခေတ်စားနေသည့်တက်ဂ်များ
+ toc: အကြောင်းအရာများ
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: ဤပို့စ်သည်စာရေးသူ၏ :LICENSE_NAME လိုင်စင်ရထားသည်။
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: မူပိုင်ခွင့်အချို့ကို လက်ဝယ်ထားသည်။
+ verbose: >-
+ အခြားမှတ်သားထားချက်များမှလွဲ၍ ဤဆိုက်ရှိ ဘလော့ဂ်ပို့စ်များသည် စာရေးသူ၏
+ Creative Commons Attribution 4.0 International (CC BY 4.0) အောက်တွင် လိုင်စင်ရထားပါသည်။
+
+meta: Powered by :PLATFORM with :THEME theme.
+
+not_found:
+ statment: ဝမ်းနည်းပါသည်၊ ကျွန်ုပ်တို့သည် အဆိုပါ URL ကို မှားယွင်းစွာ နေရာချထားခြင်း သို့မဟုတ် ၎င်းသည် မရှိသောအရာကို ညွှန်ပြနေပါသည်။
+
+notification:
+ update_found: အကြောင်းအရာဗားရှင်းအသစ်ကို ရနိုင်ပါပြီ။
+ update: အပ်ဒိတ်
+
+# ----- Posts related labels -----
+
+post:
+ written_by: ကရေးသားခဲ့သည်။
+ posted: တင်ထားခဲ့သည်။
+ updated: မွမ်းမံထားခဲ့သည်။
+ words: စကားလုံးများ
+ pageview_measure: အမြင်များ
+ read_time:
+ unit: မိနစ်
+ prompt: ဖတ်ပါမည်
+ relate_posts: နောက်ထပ်ဖတ်ရန်
+ share: မျှဝေရန်
+ button:
+ next: အသစ်များ
+ previous: အဟောင်းများ
+ copy_code:
+ succeed: ကူးယူလိုက်ပြီ။
+ share_link:
+ title: လင့်ခ်ကို ကူးယူရန်
+ succeed: လင့်ခ်ကို ကူးယူလိုက်ပြီ။
+ # pinned prompt of posts list on homepage
+ pin_prompt: ချိတ်ထားသည်။
+
+# categories page
+categories:
+ category_measure: ကဏ္ဍများ
+ post_measure: ပို့စ်များ
diff --git a/_data/locales/pt-BR.yml b/_data/locales/pt-BR.yml
new file mode 100644
index 0000000000000..59209aeec9b10
--- /dev/null
+++ b/_data/locales/pt-BR.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Post
+ category: Categoria
+ tag: Tag
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Home
+ categories: Categorias
+ tags: Tags
+ archives: Arquivos
+ about: Sobre
+
+# the text displayed in the search bar & search results
+search:
+ hint: Buscar
+ cancel: Cancelar
+ no_results: Oops! Nenhum resultado encontrado.
+
+panel:
+ lastmod: Atualizados recentemente
+ trending_tags: Trending Tags
+ toc: Conteúdo
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Esta postagem está licenciada sob :LICENSE_NAME pelo autor.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Alguns direitos reservados.
+ verbose: >-
+ Exceto onde indicado de outra forma, as postagens do blog neste site são licenciadas sob a
+ Creative Commons Attribution 4.0 International (CC BY 4.0) License pelo autor.
+
+meta: Feito com :PLATFORM usando o tema :THEME.
+
+not_found:
+ statment: Desculpe, a página não foi encontrada.
+
+notification:
+ update_found: Uma nova versão do conteúdo está disponível.
+ update: atualização
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Por
+ posted: Postado em
+ updated: Atualizado
+ words: palavras
+ pageview_measure: visualizações
+ read_time:
+ unit: min
+ prompt: " de leitura"
+ relate_posts: Leia também
+ share: Compartilhar
+ button:
+ next: Próximo
+ previous: Anterior
+ copy_code:
+ succeed: Copiado!
+ share_link:
+ title: Copie o link
+ succeed: Link copiado com sucesso!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Fixado
+
+# categories page
+categories:
+ category_measure: categorias
+ post_measure: posts
diff --git a/_data/locales/ru-RU.yml b/_data/locales/ru-RU.yml
new file mode 100644
index 0000000000000..3cd937c64765d
--- /dev/null
+++ b/_data/locales/ru-RU.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Публикация
+ category: Категория
+ tag: Тег
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Домашняя страница
+ categories: Категории
+ tags: Теги
+ archives: Архив
+ about: О сайте
+
+# the text displayed in the search bar & search results
+search:
+ hint: поиск
+ cancel: Отменить
+ no_results: Ох! Ничего не найдено.
+
+panel:
+ lastmod: Недавно обновлено
+ trending_tags: Популярные теги
+ toc: Содержание
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Публикация защищена лицензией :LICENSE_NAME.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Некоторые права защищены.
+ verbose: >-
+ Публикации на сайте защищены лицензией Creative Commons Attribution 4.0 International (CC BY 4.0),
+ если в тексте публикации не указано иное.
+
+meta: Powered by :PLATFORM with :THEME theme.
+
+not_found:
+ statment: Извините, эта ссылка указывает на ресурс который не существует.
+
+notification:
+ update_found: Доступна новая версия контента.
+ update: Обновлять
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Автор
+ posted: Время публикации
+ updated: Обновлено
+ words: слов
+ pageview_measure: просмотров
+ read_time:
+ unit: минут
+ prompt: чтения
+ relate_posts: Вам также может быть интересно
+ share: Поделиться
+ button:
+ next: Предыдущая публикация
+ previous: Следующая публикация
+ copy_code:
+ succeed: Скопировано успешно!
+ share_link:
+ title: Скопировать ссылку
+ succeed: Ссылка успешно скопирована!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Закреплено
+
+# categories page
+categories:
+ category_measure: категории
+ post_measure: публикации
diff --git a/_data/locales/tr-TR.yml b/_data/locales/tr-TR.yml
new file mode 100644
index 0000000000000..f7c25671370fb
--- /dev/null
+++ b/_data/locales/tr-TR.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Gönderi
+ category: Kategori
+ tag: Etiket
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Ana Sayfa
+ categories: Kategoriler
+ tags: Etiketler
+ archives: Arşiv
+ about: Hakkında
+
+# the text displayed in the search bar & search results
+search:
+ hint: Ara...
+ cancel: İptal
+ no_results: Hop! Öyle bir şey bulamadım.
+
+panel:
+ lastmod: Yeni Güncellendi
+ trending_tags: Yükselen Etiketler
+ toc: İçindekiler
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Bu gönderi :LICENSE_NAME lisansı altındadır.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/deed.tr
+
+ # Displayed in the footer
+ brief: Bazı hakları saklıdır.
+ verbose: >-
+ Aksi belirtilmediği sürece, bu sitedeki gönderiler Creative Commons Atıf 4.0 Uluslararası (CC BY 4.0) Lisansı altındadır.
+ Kısaca sayfa linkini de vererek paylaşabilir veya düzenleyip paylaşabilirsin.
+
+meta: :PLATFORM ve :THEME teması.
+
+not_found:
+ statment: Üzgünüz, bu linki yanlış yerleştirdik veya var olmayan bir şeye işaret ediyor.
+
+notification:
+ update_found: İçeriğin yeni bir sürümü mevcut.
+ update: Güncelle
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Yazan
+ posted: Gönderilme Tarihi
+ updated: Güncellenme Tarihi
+ words: sözcük
+ pageview_measure: görüntülenme
+ read_time:
+ unit: dakikada
+ prompt: okunabilir
+ relate_posts: Benzer Gönderiler
+ share: Paylaş
+ button:
+ next: İleri
+ previous: Geri
+ copy_code:
+ succeed: Kopyalandı.
+ share_link:
+ title: Linki kopyala
+ succeed: Link kopyalandı.
+ # pinned prompt of posts list on homepage
+ pin_prompt: Sabitlendi
+
+# categories page
+categories:
+ category_measure: kategori
+ post_measure: gönderi
diff --git a/_data/locales/uk-UA.yml b/_data/locales/uk-UA.yml
new file mode 100644
index 0000000000000..6925e42a32afc
--- /dev/null
+++ b/_data/locales/uk-UA.yml
@@ -0,0 +1,79 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Публікація
+ category: Категорія
+ tag: Тег
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Домашня сторінка
+ categories: Категорії
+ tags: Теги
+ archives: Архів
+ about: Про сайт
+
+# the text displayed in the search bar & search results
+search:
+ hint: пошук
+ cancel: Скасувати
+ no_results: Ох! Нічого не знайдено.
+
+panel:
+ lastmod: Нещодавно оновлено
+ trending_tags: Популярні теги
+ toc: Зміст
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Публікація захищена ліцензією :LICENSE_NAME.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Деякі права захищено.
+ verbose: >-
+ Публікації на сайті захищено ліцензією Creative Commons Attribution 4.0 International (CC BY 4.0),
+ якщо інше не вказано в тексті.
+
+meta: Powered by :PLATFORM with :THEME theme.
+
+not_found:
+ statment: Вибачте, це посилання вказує на ресурс, що не існує.
+
+notification:
+ update_found: Доступна нова версія вмісту.
+ update: Оновлення
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Автор
+ posted: Час публікації
+ updated: Оновлено
+ words: слів
+ pageview_measure: переглядів
+ read_time:
+ unit: хвилин
+ prompt: читання
+ relate_posts: Вас також може зацікавити
+ share: Поділитися
+ button:
+ next: Попередня публікація
+ previous: Наступна публікація
+ copy_code:
+ succeed: Успішно скопійовано!
+ share_link:
+ title: Скопіювати посилання
+ succeed: Посилання успішно скопійовано!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Закріплено
+
+# categories page
+categories:
+ category_measure: категорії
+ post_measure: публікації
diff --git a/_data/locales/vi-VN.yml b/_data/locales/vi-VN.yml
new file mode 100644
index 0000000000000..592000df18c54
--- /dev/null
+++ b/_data/locales/vi-VN.yml
@@ -0,0 +1,77 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: Bài viết
+ category: Danh mục
+ tag: Thẻ
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: Trang chủ
+ categories: Các danh mục
+ tags: Các thẻ
+ archives: Lưu trữ
+ about: Giới thiệu
+
+# the text displayed in the search bar & search results
+search:
+ hint: tìm kiếm
+ cancel: Hủy
+ no_results: Không có kết quả tìm kiếm.
+
+panel:
+ lastmod: Mới cập nhật
+ trending_tags: Các thẻ thịnh hành
+ toc: Mục lục
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: Bài viết này được cấp phép bởi tác giả theo giấy phép :LICENSE_NAME.
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: Một số quyền được bảo lưu.
+ verbose: >-
+ Trừ khi có ghi chú khác, các bài viết đăng trên trang này được cấp phép bởi tác giả theo giấy phép Creative Commons Attribution 4.0 International (CC BY 4.0).
+meta: Trang web này được tạo bởi :PLATFORM với chủ đề :THEME.
+
+not_found:
+ statment: Xin lỗi, chúng tôi đã đặt nhầm URL hoặc đường dẫn trỏ đến một trang nào đó không tồn tại.
+
+notification:
+ update_found: Đã có phiên bản mới của nội dung.
+ update: Cập nhật
+
+# ----- Posts related labels -----
+
+post:
+ written_by: Viết bởi
+ posted: Đăng lúc
+ updated: Cập nhật lúc
+ words: từ
+ pageview_measure: lượt xem
+ read_time:
+ unit: phút
+ prompt: đọc
+ relate_posts: Bài viết liên quan
+ share: Chia sẻ
+ button:
+ next: Mới hơn
+ previous: Cũ hơn
+ copy_code:
+ succeed: Đã sao chép!
+ share_link:
+ title: Sao chép đường dẫn
+ succeed: Đã sao chép đường dẫn thành công!
+ # pinned prompt of posts list on homepage
+ pin_prompt: Bài ghim
+
+# categories page
+categories:
+ category_measure: danh mục
+ post_measure: bài viết
diff --git a/_data/locales/zh-CN.yml b/_data/locales/zh-CN.yml
new file mode 100644
index 0000000000000..42fcfbc84ca43
--- /dev/null
+++ b/_data/locales/zh-CN.yml
@@ -0,0 +1,78 @@
+# The layout text of site
+
+# ----- Commons label -----
+
+layout:
+ post: 文章
+ category: 分类
+ tag: 标签
+
+# The tabs of sidebar
+tabs:
+ # format: :
+ home: 首页
+ categories: 分类
+ tags: 标签
+ archives: 归档
+ about: 关于
+
+# the text displayed in the search bar & search results
+search:
+ hint: 搜索
+ cancel: 取消
+ no_results: 搜索结果为空
+
+panel:
+ lastmod: 最近更新
+ trending_tags: 热门标签
+ toc: 文章内容
+
+copyright:
+ # Shown at the bottom of the post
+ license:
+ template: 本文由作者按照 :LICENSE_NAME 进行授权
+ name: CC BY 4.0
+ link: https://creativecommons.org/licenses/by/4.0/
+
+ # Displayed in the footer
+ brief: 保留部分权利。
+ verbose: >-
+ 除非另有说明，本网站上的博客文章均由作者按照知识共享署名 4.0 国际 (CC BY 4.0) 许可协议进行授权。
+
+meta: 本站由 :PLATFORM 生成，采用 :THEME 主题。
+
+not_found:
+ statment: 抱歉，我们放错了该 URL，或者它指向了不存在的内容。
+
+notification:
+ update_found: 发现新版本的内容。
+ update: 更新
+
+# ----- Posts related labels -----
+
+post:
+ written_by: 作者
+ posted: 发表于
+ updated: 更新于
+ words: 字
+ pageview_measure: 次浏览
+ read_time:
+ unit: 分钟
+ prompt: 阅读
+ relate_posts: 相关文章
+ share: 分享
+ button:
+ next: 下一篇
+ previous: 上一篇
+ copy_code:
+ succeed: 已复制！
+ share_link:
+ title: 分享链接
+ succeed: 链接已复制！
+ # pinned prompt of posts list on homepage
+ pin_prompt: 顶置
+
+# categories page
+categories:
+ category_measure: 个分类
+ post_measure: 篇文章
diff --git a/_data/share.yml b/_data/share.yml
new file mode 100644
index 0000000000000..1206f4d744a98
--- /dev/null
+++ b/_data/share.yml
@@ -0,0 +1,27 @@
+# Sharing options at the bottom of the post.
+# Icons from
+
+platforms:
+ -
+ type: Twitter
+ icon: "fab fa-twitter"
+ link: "https://twitter.com/intent/tweet?text=TITLE&url=URL"
+ -
+ type: Facebook
+ icon: "fab fa-facebook-square"
+ link: "https://www.facebook.com/sharer/sharer.php?title=TITLE&u=URL"
+ -
+ type: Telegram
+ icon: "fab fa-telegram"
+ link: "https://t.me/share/url?url=URL&text=TITLE"
+
+ # Uncomment below if you need to.
+ # -
+ # type: Linkedin
+ # icon: "fab fa-linkedin"
+ # link: "https://www.linkedin.com/sharing/share-offsite/?url=URL"
+ #
+ # -
+ # type: Weibo
+ # icon: "fab fa-weibo"
+ # link: "http://service.weibo.com/share/share.php?title=TITLE&url=URL"
diff --git a/_includes/analytics.html b/_includes/analytics.html
deleted file mode 100644
index 5f346aee620c1..0000000000000
--- a/_includes/analytics.html
+++ /dev/null
@@ -1,16 +0,0 @@
-{% if site.google_analytics %}
-
-
-
-{% endif %}
diff --git a/_includes/disqus.html b/_includes/disqus.html
deleted file mode 100644
index c4b4d2394f04a..0000000000000
--- a/_includes/disqus.html
+++ /dev/null
@@ -1,17 +0,0 @@
-{% if site.disqus %}
-
-
-
-
-
-{% endif %}
\ No newline at end of file
diff --git a/_includes/meta.html b/_includes/meta.html
deleted file mode 100644
index b8f4a3308354a..0000000000000
--- a/_includes/meta.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- {% if page.excerpt %}
-
-
- {% else %}
-
-
- {% endif %}
-
-
- {% if page.title %}
-
-
- {% endif %}
\ No newline at end of file
diff --git a/_includes/svg-icons.html b/_includes/svg-icons.html
deleted file mode 100644
index 7a64482cf3e20..0000000000000
--- a/_includes/svg-icons.html
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if site.footer-links.dribbble %}{% endif %}
-{% if site.footer-links.email %}{% endif %}
-{% if site.footer-links.facebook %}{% endif %}
-{% if site.footer-links.flickr %}{% endif %}
-{% if site.footer-links.github %}{% endif %}
-{% if site.footer-links.instagram %}{% endif %}
-{% if site.footer-links.linkedin %}{% endif %}
-{% if site.footer-links.pinterest %}{% endif %}
-{% if site.footer-links.rss %}{% endif %}
-{% if site.footer-links.twitter %}{% endif %}
-{% if site.footer-links.stackoverflow %}{% endif %}
-{% if site.footer-links.youtube %}{% endif %}
-{% if site.footer-links.googleplus %}{% endif %}
\ No newline at end of file
diff --git a/_layouts/default.html b/_layouts/default.html
deleted file mode 100644
index b2939c0bc4483..0000000000000
--- a/_layouts/default.html
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- {% if page.title %}{{ page.title }} – {% endif %}{{ site.name }} – {{ site.description }}
-
- {% include meta.html %}
-
-
-
-
-
-
-
-
-
-
-
- Written on {{ page.date | date: "%B %e, %Y" }}
-
-
- {% include disqus.html %}
-
diff --git a/_plugins/posts-lastmod-hook.rb b/_plugins/posts-lastmod-hook.rb
new file mode 100644
index 0000000000000..1fd6ecf9d5fb3
--- /dev/null
+++ b/_plugins/posts-lastmod-hook.rb
@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+#
+# Check for changed posts
+
+Jekyll::Hooks.register :posts, :post_init do |post|
+
+ commit_num = `git rev-list --count HEAD "#{ post.path }"`
+
+ if commit_num.to_i > 1
+ lastmod_date = `git log -1 --pretty="%ad" --date=iso "#{ post.path }"`
+ post.data['last_modified_at'] = lastmod_date
+ end
+
+end
diff --git a/_posts/2014-3-3-Hello-World.md b/_posts/2014-3-3-Hello-World.md
deleted file mode 100644
index d4665b6d18e9e..0000000000000
--- a/_posts/2014-3-3-Hello-World.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: post
-title: You're up and running!
----
-
-Next you can update your site name, avatar and other options using the _config.yml file in the root of your repository (shown below).
-
-
-
-The easiest way to make your first post is to edit this one. Go into /_posts/ and update the Hello World markdown file. For more instructions head over to the [Jekyll Now repository](https://github.com/barryclark/jekyll-now) on GitHub.
\ No newline at end of file
diff --git a/_posts/2018-10-26-it-works-on-my-machine.md b/_posts/2018-10-26-it-works-on-my-machine.md
new file mode 100644
index 0000000000000..9929566d06eed
--- /dev/null
+++ b/_posts/2018-10-26-it-works-on-my-machine.md
@@ -0,0 +1,24 @@
+---
+title: It works on my machine
+date: '2018-10-26T00:00:00.000Z'
+categories:
+ - Testing
+redirect_from:
+ - /it-works-on-my-machine/
+---
+
+So, you just found this great bug and it's returned "cannot reproduce", or you have been told "it works on my machine", classic right?
+
+As a tester, in this situation, it can be easy to get defensive. Am I being told I am making it up? Am I being disrespected, why should I raise bugs if they are not important enough to fix?
+
+My suggestion, turn this on its head and consider this for a moment. Time to get technical! What details can be added to help identify the root cause of the issue? Can you do more investigation and help understand what is different between the environment you tested on, and the one the developer tried to reproduce it in?
+
+### Ways you could add value in response to "it works on may machine" in include:
+
+1. Identifying the exact build or deployment you observed the issue on, and check is this the same build the developer is checking against? Can you check the build they are using, maybe the issue is already fixed, but you haven't been given the latest code?
+2. Identify what platform are you both using. If it's web, make sure to check not only the Browser, but the version of that browser. If it's mobile, what version of Android or iOS is installed?
+3. Is there any additional logging you can get to help add context? If you can find an exception being thrown that is captured in a log, this can go a long way towards helping identify the issue.
+4. If you can continue to reproduce the issue, can you give the Developer access to your machine or environment? If your remote, can you setup a screen sharing session? At a minimum, it should be easy enough to capture a video of the steps. for this, I use Open Broadcast Software Studio ([https://obsproject.com/download](https://obsproject.com/download) "https://obsproject.com/download")), but many alternatives exist.
+5. If any of these have helped get to the root of the problem and get the bug fixes, try and use them more often in your usual bug reports, and see if you can reduce your "Works on my machine" count.
+
+I hope my thoughts on this are useful, I am really interested to know if you agree, disagree, or even better have additional hints and tips! if you do, please let me know on twitter: [https://twitter.com/fullsnacktester](https://twitter.com/fullsnacktester "https://twitter.com/fullsnacktester")
diff --git a/_posts/2018-11-15-selenium-ide-is-back-for-chrome-and-firefox.md b/_posts/2018-11-15-selenium-ide-is-back-for-chrome-and-firefox.md
new file mode 100644
index 0000000000000..7093433bb6a3b
--- /dev/null
+++ b/_posts/2018-11-15-selenium-ide-is-back-for-chrome-and-firefox.md
@@ -0,0 +1,44 @@
+---
+title: Selenium IDE is back for Chrome and Firefox!
+date: '2018-11-15 01:09'
+categories:
+ - Automation
+redirect_from:
+ - /selenium-ide-is-back-for-chrome-and-firefox/
+---
+
+Selenium's official IDE is back! with a "Record/Playback session overhaul". The old Selenium IDE Firefox plugin version from "back in the day", before it became unusable in 2017, with version 55 of Firefox ([https://seleniumhq.wordpress.com/2017/08/09/firefox-55-and-selenium-ide/](https://seleniumhq.wordpress.com/2017/08/09/firefox-55-and-selenium-ide/ "https://seleniumhq.wordpress.com/2017/08/09/firefox-55-and-selenium-ide/")).
+
+Selenium IDE "Next Generation", has current Chrome and Firefox plugins, that work with the latest versions of the browsers.
+
+
+
+### Does the new "Official" IDE offer any benefits?
+
+I really need to spend some more time with the IDE to do it justice. My initial reaction so far:
+
+* Debugging tests is pretty straightforward
+* The "If, else if, else and end" logic if very useful for creating basic conditional flow
+ * An example where this might be useful, is if you want to accept Cookie consent, but only if you haven't done so already
+* The saved tests appear to be stored in JSON, and so far I don't see an obvious way to convert them into something more useful you can continue "real" development with in a framework of your choice. So your stuck loading the tests back into SIDE or..
+* There is an Node/NPM Based "SIDE" test runner, I haven't had time to check this out yet but this is the suggested route for using SIDE tests in CI.
+
+### Should you care?
+
+First off, I didn't spend much time in the "old" IDE, and I've only had a very short look at the new. So I'm not yet very well placed to judge.
+
+What I do know, is that in the absence of the Official IDE, alternatives have been created. For example if you want a Chrome plugin for Capture and Playback, you may already be using Katalon Recorder ([https://chrome.google.com/webstore/detail/katalon-recorder-selenium/ljdobmomdgdljniojadhoplhkpialdid](https://chrome.google.com/webstore/detail/katalon-recorder-selenium/ljdobmomdgdljniojadhoplhkpialdid "https://chrome.google.com/webstore/detail/katalon-recorder-selenium/ljdobmomdgdljniojadhoplhkpialdid")).
+
+One of the nice things about Katalon Recorder, is that unlike SIDE, you can export into a number of useful formats. In fact you can match up Katalon Recorder and then convert these for using in SeleniumBase. [https://github.com/seleniumbase/SeleniumBase/tree/master/seleniumbase/utilities/selenium_ide](https://github.com/seleniumbase/SeleniumBase/tree/master/seleniumbase/utilities/selenium_ide "https://github.com/seleniumbase/SeleniumBase/tree/master/seleniumbase/utilities/selenium_ide"). This approach gives you flexibility to do capture and record, and then make more maintainable tests, using patterns such as the Page Object Model.
+
+### Give it ago, and make up your own mind
+
+**Release notes:**
+
+[https://github.com/SeleniumHQ/selenium-ide/releases/tag/v3.4.0](https://github.com/SeleniumHQ/selenium-ide/releases/tag/v3.4.0 "https://github.com/SeleniumHQ/selenium-ide/releases/tag/v3.4.0")
+
+**Download:**
+
+Chrome extension: [https://chrome.google.com/webstore/detail/selenium-ide/mooikfkahbdckldjjndioackbalphokd](https://chrome.google.com/webstore/detail/selenium-ide/mooikfkahbdckldjjndioackbalphokd "https://chrome.google.com/webstore/detail/selenium-ide/mooikfkahbdckldjjndioackbalphokd")
+
+Firefox extension: [https://addons.mozilla.org/en-GB/firefox/addon/selenium-ide/](https://addons.mozilla.org/en-GB/firefox/addon/selenium-ide/ "https://addons.mozilla.org/en-GB/firefox/addon/selenium-ide/")
diff --git a/_posts/2019-02-10-Automated rest api testing with python.md b/_posts/2019-02-10-Automated rest api testing with python.md
new file mode 100644
index 0000000000000..1b6ef07753092
--- /dev/null
+++ b/_posts/2019-02-10-Automated rest api testing with python.md
@@ -0,0 +1,63 @@
+---
+title: Automated REST API Testing with Python
+date: '2019-02-19 00:00:00 +0000'
+categories:
+ - Automation
+tags:
+ - automation
+redirect_from:
+ - /Automated-rest-api-testing-with-python/
+---
+
+
+Last time out I introduced you to the start of my journey to automate all the "test" things in Python. I continue that journey now by switching focus away from frontend, to Restful Web APIs. You can look back at my last post [here](https://www.dowen.me.uk/posts/how-I-am-learning-to-test-the-internet-with-seleniumbase/ "How I am learning to test The Internet with SeleniumBase").
+
+## Explore, Request, Assert
+
+For this leg of the Journey, I will be using the python modules [requests](https://pypi.org/project/requests/ "Requests: HTTP for Humans") and [pyassert](https://pypi.org/project/pyassert/ "pyassert is an assertion library for the Python programming language.").
+
+## Exploring APIs
+
+
+
+Before you can make requests and you need to understand the API your testing. For this I recommend using a Rest Client. While you may already have mad skills in cURL, for the rest of us I suggest using [Postman](https://www.getpostman.com "Postman Simplifies API Development."), [Insomnia](https://insomnia.rest "Insomnia Debug APIs like a human, not a robot Finally, a REST client you'll love") or [SoapUI](https://www.soapui.org "SoapUI The Most Advanced REST & SOAP Testing Tool in the World").
+
+If, like me, you want to develop your API testing skills in a safe place, outside of any work projects, there are some great options!
+
+Ministry of Testing has a resource page listing some of those options [Websites To Practice Testing](https://www.ministryoftesting.com/dojo/lessons/websites-to-practice-testing "Here's a handy list of websites for software testers to practice their testing on that you might find it useful."). The one I am using is [Restful Booker](https://restful-booker.herokuapp.com "An API playground created by Mark Winteringham for those wanting to learn more about API testing and tools") by [Mark Winteringham](https://www.mwtestconsultancy.co.uk "MW Test Consultancy").
+
+Start your exploration using API documentation. For Restful booker, you can find that [here](https://restful-booker.herokuapp.com/apidoc/index.html "API documentation for the playground API restful-booker.").
+
+To learn more about testing APIs and using Postman, I suggest the free course [Exploring Service APIs through Test Automation](https://testautomationu.applitools.com/exploring-service-apis-through-test-automation/ "Exploring Service APIs through Test Automation") by [Amber Race](https://twitter.com/ambertests "Amber Race on Twitter").
+
+## Making Requests
+
+Inspired by the article [API Integration in Python – Part 1](https://realpython.com/api-integration-in-python/ "How to Make Friends and Influence APIs"), I started by making a Python client to abstract interactions with the Restful Booker API. The article is not focused on testing, but instead shows us how to Constructing an API Library, using Requests.
+
+This pattern of abstraction is great and we can use it along side an assertion framework to do some robust testing.
+
+You can take a closer look at my API Library for Restful Booker, and my rest code on the [Pybooker](https://github.com/dowenb/pybooker "Example of making using and testing an API in python") GitHub Repository.
+
+
+
+This basic example makes a GET request to the URL , and prints the resulting JSON response body into the Python console. Running it gives us:
+
+
+
+Because the method returns the response object, we can not only get the JSON body, but also useful information like the HTTP Status code.
+
+Requests can make use of a wide range of HTTP methods, explore it and see what you can do!
+
+## Asserting That
+
+OK so now we can make Requests, and access the returned response in an object. With this, we can start implementing some automated checks, to see if we are getting back what we expect.
+
+To do this, I have made use of the module [pyassert](https://pypi.org/project/pyassert/ "pyassert is an assertion library for the Python programming language."), you could also use other assertion libraries such as [fluentcheck](https://github.com/csparpa/fluentcheck "Fluent assertions for Python"). I am using Pytest to run my tests.
+
+
+
+While you can assert on almost every aspect of the response, the most basic check is the response returned 'OK'. This means we made a valid request, and the service didn't throw an internal server error.
+
+One step further would be to assert on the HTTP Status code. For example for a GET you expect to succeed you might expect "200 Success", and for creating a new item with POST you might expect "201 Created".
+
+You can read more about http status codes [HTTP STATUS DOGS](https://httpstatusdogs.com "Hypertext Transfer Protocol Response status codes. And dogs.") or [HTTP Cats](https://http.cat "HTTP Cats").
diff --git a/_posts/2019-02-10-Automation - Just do it!.md b/_posts/2019-02-10-Automation - Just do it!.md
new file mode 100644
index 0000000000000..78649b71325c5
--- /dev/null
+++ b/_posts/2019-02-10-Automation - Just do it!.md
@@ -0,0 +1,61 @@
+---
+title: Automation - Just do it!
+date: '2019-02-10 10:00:00 +0000'
+categories:
+ - Automation
+redirect_from:
+ - /Automation-Just-do-it!/
+---
+
+It can be a daunting task to create an automation strategy, get resources signed off, heir or train automation engineers.
+
+But what is the alternative, and is it a good idea?
+
+## "Just do it!"
+
+### What might this look like?
+
+* Making use of personal development time, or putting in some extra hours and learning to do some automation yourself (regardless if your day job is developing or testing)
+* Having some kind of informal agreement either your manager or the projects manager. This might be along the lines of "give me a little time, I'll put in a little time".
+* You might not see the benefit in this project/sprint, and setting expectations is important.
+
+### What are the benefits of this?
+
+* Personal development, over time you will gain confidence and be able to contribute some valuable automation
+* If things go well, you may be able to gain some value sooner then you would think
+* Build momentum by having something to show now, instead of a plan on what you will commit to later
+* If you can prove the concept, it might be easier to get sign off for more resource to be spent on future automation projects
+
+### What are the disadvantages?
+
+* Without proper resources, there is a high risk of running out of time to deliver anything useful before the current sprint/project is finished
+* If things go badly, it might turn people off to investing properly in future automation
+* Automation is code, so you can easily build technical debt by treating it as a side project
+
+## What if you want to develop your automation skills without trying them out on a customers project?
+
+Fortunately for this, there are two great options:
+
+1. Use one of the fantastic resources for practice testing such as
+ * [http://the-internet.herokuapp.com](http://the-internet.herokuapp.com "http://the-internet.herokuapp.com")
+ * [http://testingchallenges.thetestingmap.org](http://testingchallenges.thetestingmap.org "http://testingchallenges.thetestingmap.org")
+ * [https://automationintesting.online/#/](https://automationintesting.online/#/ "https://automationintesting.online/#/")
+ * [https://restful-booker.herokuapp.com](https://restful-booker.herokuapp.com "https://restful-booker.herokuapp.com")
+ * more available (free sign up required): [https://www.ministryoftesting.com/dojo/lessons/websites-to-practice-testing](https://www.ministryoftesting.com/dojo/lessons/websites-to-practice-testing "https://www.ministryoftesting.com/dojo/lessons/websites-to-practice-testing")
+2. Contribute tests to an open source project
+
+## Bottom line
+
+I know it's a cop out, but as with almost every this vs that article you will read today, the answer isn't one of the two options but both.
+
+Or at least, that has been my strategy:
+
+* Just do it! learn as much as I can about automation and practice on anything I can get my hands on. I am doing this through a combination of Self Development time signed off by my manager, and my own time on evenings and weekends.
+* Encourage, Support and knowledge share with other testers in my team, and via communities such as the Testers.Chat slack from Ministry of Test.
+* Start creating test strategies that include automation.
+* Create and support others to create proof on concept automation projects for client and internal projects
+* Consider automation skills as desirable and interestingly essential skills when hiring or planning future test resource
+
+### Is this working out for me?
+
+Yes, in that I am having a lot of fun developing my automation skills. Is it contributing significantly to the success of projects I am working on? I will have to get back to you on that, it's early days!
diff --git a/_posts/2019-02-10-how-I-am-learning-to-test-the-internet-with-seleniumbase.md b/_posts/2019-02-10-how-I-am-learning-to-test-the-internet-with-seleniumbase.md
new file mode 100644
index 0000000000000..87da944812c83
--- /dev/null
+++ b/_posts/2019-02-10-how-I-am-learning-to-test-the-internet-with-seleniumbase.md
@@ -0,0 +1,175 @@
+---
+title: How I am learning to test The Internet with SeleniumBase
+date: '2019-02-10 14:00:00 +0000'
+categories:
+ - Automation
+redirect_from:
+ - /how-I-am-learning-to-test-the-internet-with-seleniumbase/
+---
+
+Goal: I have a simple, ambitious big hairy goal Learn how to "Automate all the (test) things, in Python". This is Part 1 on my journey towards this goal.
+
+For context I consider myself experienced as a tester, but a relative newbie as a developer. I have been involved in one successful automation project using Powershell, and one failed automation project using .NET Framework and Selenium.
+
+## Go learn Python! Somewhere else
+
+What I won't be touching on in any point during this series, is how to install or use the basics of Python. This is well covered ground, and the Python Docs are a great place to start if this is what your after. [https://docs.python.org/3/](https://docs.python.org/3/)
+
+## SeleniumBase
+
+SeleniumBase is a test framework that wraps Selenium and extends Pytest, and also works with Nose test. I have selected SeleniumBase as my web test framework of choice, after a brief evaluation for a few reasons:
+
+* Low barrier to entry, it's really easy to write and run your first test
+* The competition where mostly based in JavaScript (WebDriver.io and NightWatch.js), I found them flaky to get running out of the box
+* I wanted to avoid Java, for personal preference *The maintainer is VERY responsive via Twitter and Git issues, and has helped me and added functionality. I can't emphasis enough how much confidence this gives me.
+* Finally and maybe most important, I was moments away from taking another direction, and got a recommendation from the kind folks at the Ministry of Testing Testers.Chat slack community to make use of Python and SeleniumBase to start my automation journey, 100 times thank you!
+
+I found Getting up and running with SeleniumBase is easy, following their own instructions, so I am not going to cover this ground. [http://seleniumbase.com/](http://seleniumbase.com/)
+
+## The Internet
+
+Sure I could, and have, tried creating some automation against client projects. But here is where I come across some problems in terms of developing my skills:
+
+1. I cannot share details of this work with others, my nature it is confidential
+2. I am limited to solving the challenges for the given project
+3. Things change, so a lot of what I learned is about maintaining references to page elements
+
+The solution? The Internet! no, not that internet. [http://the-internet.herokuapp.com](http://the-internet.herokuapp.com).
+
+### Easy, right?
+
+On first glance, the list of individual pages of isolated examples looks like it should be super easy to automate with any Selenium based framework. Turns out, for me at least, each example I have tried to automate so far has thrown up some interesting mini challenge I have had to spend time thinking about and researching. This is great news! Because it validates it as a useful resource to hone my skills.
+
+## Follow along, on GitHub
+
+If you want to follow me on my journey, feel free to check out my GitHub repository: [https://github.com/dowenb/seleniumbase-example/tree/master/the_internet](https://github.com/dowenb/seleniumbase-example/tree/master/the_internet).
+
+## Examples so far
+
+At the time of writing, I have taken on automating tests against 3 of the examples on The Internet. Let's take a closer look at each. As some background my work is contained in two files:
+
+* The Internet Objects (Page Object model)
+* The Internet Test (Tests, run in Pytest)
+
+### Helper _url(path) function
+
+```Python
+def _url(path, prefix='http://'):
+ base_url = 'the-internet.herokuapp.com'
+ return prefix + base_url + path
+```
+
+Using this helper function allows me to manage my base URL in one place. It's probably a little over complicated, but you will understand why I did this in the first example below, basic auth.
+
+### Basic Auth
+
+```Python
+#the_internet_objects.py
+class BasicAuth(object):
+ url = _url('/basic_auth', prefix='http://admin:admin@')
+ success_text = '#content > div > p'
+```
+
+The basic problem I had to solve for this example, is how to pass the username and password for basic auth. I understand, the method I have choosen is far from production ready. If i find myself in a situation where I am testing pre-production code that uses basic auth, happy days.
+
+```Python
+#the_internet_test.py
+from seleniumbase import BaseCase
+from the_internet_objects import BasicAuth, BrokenImages, CheckBoxes
+
+class MyTestClass(BaseCase):
+
+ def test_basic_auth(self):
+ self.open(BasicAuth.url)
+ self.assert_text(
+ 'Congratulations! You must have the proper credentials.',
+ BasicAuth.success_text
+ )
+```
+
+Note the class inheriting from BaseCase, self.open and self.assert. This is SeleniumBase in action. For more details on basic SeleniumBase functionality, read the examples in the docs: [https://github.com/seleniumbase/SeleniumBase/tree/master/examples](https://github.com/seleniumbase/SeleniumBase/tree/master/examples)
+
+One gotcha, if you don't name your test definition 'test_thing', Pytest won't find it.
+
+### Broken Images
+
+```Python
+#the_internet_objects.py
+class BrokenImages(object):
+ url = _url('/broken_images')
+ image1 = '#content > div > img:nth-child(2)'
+ image2 = '#content > div > img:nth-child(3)'
+ image3 = '#content > div > img:nth-child(4)'
+```
+
+Again I am making use of the Page Object model pattern. Following the SeleniumBase examples, all I am doing is storing strings that are the selectors for the elements I will find in my tests. I am not returning objects here, but I am abstracting the locators so I have a "single source of truth" to update when the web app I am testing is updated, and my references break.
+
+```Python
+#the_internet_test.py
+from seleniumbase import BaseCase
+from the_internet_objects import BasicAuth, BrokenImages, CheckBoxes
+
+class MyTestClass(BaseCase):
+ def test_broken_images(self):
+ self.open(BrokenImages.url)
+ self.assertGreater(int(self.get_attribute(BrokenImages.image1, 'naturalWidth')), 0)
+ self.assertGreater(int(self.get_attribute(BrokenImages.image2, 'naturalWidth')), 0)
+ self.assertGreater(int(self.get_attribute(BrokenImages.image3, 'naturalWidth')), 0)
+```
+
+This was my first experiment using the get_attributes function. I adapted this method from an equivalent I found researching the challenge online. Getting naturalWidth of 0 appeared to be a widely accepted method to assert if an image is broken. Note, this is a failing test, and that is to be expected a two of the images ARE broken, and I am asserting that they should not be.
+
+I can think of at least two things I have not done to make this example elegant:
+
+\*The check for a broken image could be abstracted into a helper method
+\*Instead of static references to three images, all images could be iterated
+
+Feel free to send me a pull request if you find time to do either of these enhancements, or folk my examples and do this for yourself. Either way, let me know!
+
+### Check Boxes
+
+```Python
+#the_internet_objects.py
+class CheckBoxes(object):
+ url = _url('/checkboxes')
+ checkbox1 = '#checkboxes > input[type="checkbox"]:nth-child(1)'
+ checkbox2 = '#checkboxes > input[type="checkbox"]:nth-child(3)'
+```
+
+Nothing exciting here, just another basic object model. the only gotcha is that checkbox 2 is the 3rd child, not he 2nd. I believe this is because the 2nd child is the text label for checkbox 1. Answers on a postcard.
+
+```Python
+#the_internet_test.py
+from seleniumbase import BaseCase
+from the_internet_objects import BasicAuth, BrokenImages, CheckBoxes
+
+class MyTestClass(BaseCase):
+
+ def isChecked(self, checkBox):
+ try:
+ self.get_attribute(checkBox, 'checked')
+ return True
+ except:
+ return False
+
+ def test_checkboxes(self):
+ self.open(CheckBoxes.url)
+ #checkbox1 should default unchecked, and a click should leave it checked
+ self.assert_false(self.isChecked(CheckBoxes.checkbox1), 'Checkbox1 should be unchecked')
+ self.click(CheckBoxes.checkbox1)
+ self.assert_true(self.isChecked(CheckBoxes.checkbox1), 'Checkbox1 should be unchecked')
+ #checkbox2 should default checked, and a click should leave it unchecked
+ self.assert_true(self.isChecked(CheckBoxes.checkbox2), 'Checkbox2 should be checked')
+ self.click(CheckBoxes.checkbox2)
+ self.assert_false(self.isChecked(CheckBoxes.checkbox2), 'Checkbox2 should be unchecked')
+```
+
+Unlike in the Broken Images example, here I have created a helper method. I am using .get_attribute(), this time I need to work around the fact the method throws an example if the attribute is not found. It turns out, the "checked" attribute is added and removed from the element when the check-box is checked and unchecked.
+
+If you think if anything more interesting I can test with checkboxes, or again a way to more elegantly iterate them, let me know!
+
+## Thanks
+
+A big thank you to the folks at SeleniumBase, who can be found on Twitter [https://twitter.com/SeleniumBase](https://twitter.com/SeleniumBase)
+Another big shout out to the folks at Ministry of Testing [https://www.ministryoftesting.com](https://www.ministryoftesting.com) for an inspiring community and excellent collection of resources.
+And finally thank you to Dave Haeffner, [http://davehaeffner.com/](http://davehaeffner.com/), for The Internet [https://github.com/tourdedave/the-internet](https://github.com/tourdedave/the-internet)
diff --git a/_posts/2021-10-22-find-me-on-the-web.md b/_posts/2021-10-22-find-me-on-the-web.md
new file mode 100644
index 0000000000000..a1cd4d1e1ecd5
--- /dev/null
+++ b/_posts/2021-10-22-find-me-on-the-web.md
@@ -0,0 +1,28 @@
+---
+title: Places you can find me online
+date: '2021-10-22 00:00:00 +0100'
+tags:
+ - twitter
+ - social Media
+ - links
+categories:
+ - About Ben
+redirect_from:
+ - /find-me-on-the-web/
+---
+
+Since starting this site and blog, I have expanded my online presence with a number of other sites that I post on. While I should probably consolidate my content in one place, for now let me tell you where else you can find me!
+
+### Full Snack Tester
+
+The home page of my Full Snack Tester website has links to the majority of my social media and projects:
+
+[https://www.fullsnacktester.com/](https://www.fullsnacktester.com/ "https://www.fullsnacktester.com/")
+
+My current Twitter account is also [@fullsnacktester](https://twitter.com/FullSnackTester)
+
+### Quick summary of other links
+
+* [https://linktr.ee/dowenb](https://linktr.ee/dowenb "https://linktr.ee/dowenb")
+* [https://www.linkedin.com/in/dowenb/](https://www.linkedin.com/in/dowenb/ "https://www.linkedin.com/in/dowenb/")
+* [https://dev.to/dowenb](https://dev.to/dowenb "https://dev.to/dowenb")
diff --git a/_posts/2021-10-22-what-does-quality-mean-to-me.md b/_posts/2021-10-22-what-does-quality-mean-to-me.md
new file mode 100644
index 0000000000000..40f6f12f6b4f6
--- /dev/null
+++ b/_posts/2021-10-22-what-does-quality-mean-to-me.md
@@ -0,0 +1,87 @@
+---
+title: What does quality mean to me?
+date: '2021-10-22 00:00:00 +0100'
+tags:
+ - quality
+ - testing
+categories:
+ - About Ben
+redirect_from:
+ - /what-does-quality-mean-to-me/
+---
+
+There are many definitions of Software and Product "Quality". For a long time, earlier in my career, I did much to ignore the topic and felt it was intangible. The definitions that I had at the time were all about only the Correctness, the strict conformance to well specified requirements.
+
+Over the last 3+ years I've massively increased my external communication with the wider testing community. I've read blogs, watched presentations and I've tested a bunch more software.
+
+Now, I'm approaching a point I've got some kind of grasp of software quality, in a way that can be usefully and concisely defined.
+
+## What does quality mean to me?
+
+### I posted this one Twitter:
+
+
+
+> What does quality mean to me? Goodness, Usefulness and Correctness at a point of time, with a context that takes into account ethics, customer success, business success, competitor products and the wider industry. That allows for "good enough" in that context to be enough!
+
+### Context, at a point in time
+
+In my experience, users and other people who matter make their judgement on the quality of your product taking into account external influences, such as current competition and competing solutions. They are also likely to be influenced based on current local, national or global situations, such as Brexit or the COVID-19 Pandemic.
+
+And that is before you take into account the influence on their judgement from personal factors, such as fanatical independence, levels of stress, mood and any other thing you could possibly think of. These individual influences are difficult to take into account, and realistically we probably won't be able to account for them all, but instead simply accept the risks this raises in many cases.
+
+So, the product is judged based on it's Goodness, Usefulness and Correctness alongside other external influences. As such any measurement of quality is only a snapshot of the current sentiment of the group of people who you have been able to gather at the point feedback is collected.
+
+For example Windows XP was considered by many as a huge leap forward in quality when it was first released in 2001. But how would you feel if I gave you XP to use now?
+
+So, the code many not change, the product is the same, but the quality may be reduced over time as context changes.
+
+## My definition doesn't exist in isolation
+
+In order to come to this definition, I've spoke to, read and consumed from many great Testers. Notability [Dan Ashby](https://twitter.com/DanAshby04), whom I am now lucky enough to work with, and [Stu C](https://twitter.com/StooCrock).
+
+### Quality Panel
+
+I also took part in a [Quality Panel](https://www.ministryoftesting.com/dojo/series/the-ministry-of-testing-podcast-2021/lessons/mot-podcast-quality-panel) discussion for the MoT Podcast, alongside [Gem Hill](https://twitter.com/Gem_Hill), Alsa Tabatabei and [Lee Marshall]().
+
+### Quality Aspects
+
+In the last few months, I've started making use of [Risk Storming,](https://riskstormingonline.com/) and I love it! The focus the Test Sphere cards can give you on Quality Aspects (aka Quality Characteristics) are really powerful.
+
+
+
+If we take a single Characteristic, say **Installability**, now we can focus not on the risks to the whole product, not on the quality of the whole product. We can focus just on this one aspect.
+
+When we break down product quality into smaller parts, and prioritize them, it can make it much more tangible and we can make more useful assessments.
+
+### Implicit and Explicit asks
+
+One thing the focus on Quality Aspects, and the definition of quality beyond correctness really brings to light is that checking for Correctness really isn't enough, not even close. And to this end, testing Acceptance Criteria and explicit requirements falls way short.
+
+A really great explanation of this is written up by another fantastic tester, and Exploratory Testing legend, [Callum Akehurst-Ryan](https://callumakehurstryansblog.wordpress.com/about-me/)**,** in the post [WHY CHECKING AN AC ISN’T ENOUGH](https://callumakehurstryansblog.wordpress.com/2021/08/25/why-checking-an-ac-isnt-enough/).
+
+### On accessing and measuring quality
+
+OK, so now I've defined what quality means to me. But, is this useful?
+
+I feel that this short definition hides a huge amount of detail, of course it does, it's only a single Tweet. It also assumes you already have a really clear idea what I mean by Goodness, Usefulness and Correctness, and if you have consumed anything from Dan Ashby, you probably have this context, if not go and read [Dan Ashby's Adapting Crosby’s 4 absolutes of quality into a software context](https://danashby.co.uk/2019/09/30/adapting-crosbys-4-absolutes-of-quality-into-a-software-context/).
+
+What I'm missing, still, is a way to strike a balance on how to measure and describe the current quality of a product, and report on that usefully. On one side, there is the huge amount of valuable and highly contextual detail you can gain from detailed testing notes and detailed reports. On the other, the "gut feel" RAG rating, or star rating.
+
+Details are great, for communicating with Engineers and the team, but are hard to "report upwards". RAG statuses, or traffic light style ratings are _course_ and really don't provide enough context to be an honest current reflection of quality. Both ways have risks, and are not appropriate to communicate with everyone.
+
+To be clear, I don't have the answer here, I'm still working on it.
+
+## References
+
+[Dan Ashby's Adapting Crosby’s 4 absolutes of quality into a software context](https://danashby.co.uk/2019/09/30/adapting-crosbys-4-absolutes-of-quality-into-a-software-context/)
+
+[Quality Advocates with Dan Ashby, How “Good” is your Product? \[YouTube\]](https://www.youtube.com/watch?v=XMDm44QYHw8)
+
+[A Useable Definition of Quality](https://dragonsforelevenses.com/2021/09/03/a-useable-definition-of-quality/)
+
+[Modern Testing Principles](https://www.ministryoftesting.com/dojo/lessons/modern-testing-principles)
+
+[WHY CHECKING AN AC ISN’T ENOUGH](https://callumakehurstryansblog.wordpress.com/2021/08/25/why-checking-an-ac-isnt-enough/)
+
+[Windows XP](https://en.wikipedia.org/wiki/Windows_XP)
diff --git a/_posts/2021-11-08-testing-for-developers.md b/_posts/2021-11-08-testing-for-developers.md
new file mode 100644
index 0000000000000..b85e9e4431c3d
--- /dev/null
+++ b/_posts/2021-11-08-testing-for-developers.md
@@ -0,0 +1,73 @@
+---
+title: Testing for Developers
+tags:
+ - testing
+ - teams
+ - industry
+date: '2021-11-08 00:00:00 +0000'
+categories:
+ - Testing for Developers
+redirect_from:
+ - /testing-for-developers/
+---
+
+## Developers can't test and other lies
+
+Developers can't test, testers just break code and don't even use tools in their testing! After all Testers are just failed Developers, right?
+
+OK these are maybe some of the more extreme myths about software testing, and I bet you have heard some hum-dinners in your time.
+
+I like to think, we can all benefit from learning more about testing and assessing quality, I know I still have loads more to learn. And while I've cross-posted some of my blogs onto Developer focused communities, now I'm going a step further and creating a series I'm calling **Testing for Developers**.
+
+## The premise
+
+* Bring together people from Tester and Developer communities
+* Bust some myths and misconceptions about testing and quality
+* Collaborate with Developers to learn and share more about Testing
+* Create an accessible resource that anyone can use to learn more about Testing
+
+## How it will work
+
+* I will collaborate with Developers and Testers to map out ideas and produce content
+* We will write blogs, record Rackets and maybe record YouTube videos
+* Work created as part of the series will link back here
+* Where work is created with others, it will primarily or additionally be posted and there accounts, and will be linked to or reproduced here
+* Credit will always be given to all contributors for work done together, wherever it's published
+
+## Topics
+
+A short list, and longer mind-map, of initial thoughts for topics. Please feel free to contribute more!
+
+* Myths about Testing
+* Skills overlap between Testers and Developers
+* Working together to assess quality
+* Building successful Dev/Test relationships
+* Metrics and how they can help or hinder
+
+
+
+## Follow along
+
+This is work in progress, I will eventually make a permanent link and ways to follow along on social media.
+
+For now, you can link back here: [https://www.dowen.me.uk/posts/testing-for-developers/](https://www.dowen.me.uk/posts/testing-for-developers/ "https://www.dowen.me.uk/posts/testing-for-developers/")
+
+## Get involved
+
+Want to add to the series, help out with ideas or co-author some work? Get in touch!
+
+You can find me [ben@dowen.me.uk](mailto:ben@dowen.me.uk), [@FullSnackTester](https://twitter.com/FullSnackTester "Full Snack Tester on Twitter") on Twitter or [dowenb ](https://www.linkedin.com/in/dowenb/ "Ben Dowen on LinkedIn")on LinkedIn.
+
+# Articles
+
+## The skills that Testers and Developers share
+
+[Bob Salmon](https://twitter.com/BobTechThoughts "@BobTechThoughts on Twitter") writes:
+
+> The idea that programmers and testers are different kinds of people with different kinds of skills is sometimes helpful, but not always. It can help to match people to jobs or show where people have different strengths. But it can also lead to [tribalism](https://randomtechthoughts.blog/2019/06/26/competence-vs-tribalism/) – you’re different from me so you’re worse than me. In this article I’ll go into a few areas where I think programmers use skills in their normal day-to-day activities that overlap with the skills that testers often use in theirs. I hope that this helps to break down unhelpful barriers between the groups, and improves mutual appreciation for the skills others have.
+>
+> This was inspired by a conversation with [Ben Dowen](https://twitter.com/FullSnackTester), who is a tester and active member of the wider testing community. He was looking for a tame developer to work with on some blogging, I volunteered, and this is a result of the conversation that followed. It’s part of a bigger project he’s running, that’s trying to [help bring developers and testers closer together](https://www.dowen.me.uk/posts/testing-for-developers/).
+
+Read the full article on Bob's blog:
+
+[https://randomtechthoughts.blog/2021/11/09/the-skills-that-developers-and-testers-share/](https://randomtechthoughts.blog/2021/11/09/the-skills-that-developers-and-testers-share/ "https://randomtechthoughts.blog/2021/11/09/the-skills-that-developers-and-testers-share/")
diff --git a/_posts/2022-04-03-so-youve-been-asked-to-do-some-testing.md b/_posts/2022-04-03-so-youve-been-asked-to-do-some-testing.md
new file mode 100644
index 0000000000000..73f8b907c532f
--- /dev/null
+++ b/_posts/2022-04-03-so-youve-been-asked-to-do-some-testing.md
@@ -0,0 +1,264 @@
+---
+title: 'So you''ve been asked to do some testing, where do you start?'
+date: '2022-10-05 01:00:00 +0100'
+tags:
+ - testing
+ - beginner
+categories:
+ - How to
+redirect_from:
+ - /so-youve-been-asked-to-do-some-testing/
+---
+
+So, you're minding your own business, enjoying life. Maybe you're working as a Project Manager, a Product Owner, a Team Lead, or maybe you just happen to work for a University and are the one who knows your Excel from your USB port.
+
+And then it happens. You have the need to Test some software. Maybe it is the new version of a system being rolled out in the office, or it might be the product your team is working on, depending on your context.
+
+However it happened, Software Testing isn't normally your job, but here you are, being asked to do it anyway. If this is you, read on! I'm here to help.
+
+## Don't panic
+
+The first thing I'm here to tell you, is don't panic! I can't promise everything will be OK, but I can reassure you that you're not the first, and won't be the last person to get this request. And I hope I can give you enough pointers here so you can make a fair job of it. How knows, you maybe even enjoy it.
+
+## Why test software
+
+I recently contributed, via Twitter, to a Blog post by James Tomas [Why do they test software](https://qahiccupps.blogspot.com/2022/03/why-do-they-test-software.html). If you want some inspiration on why you might want to test software, beyond having been asked to, I suggest you check it out.
+
+You might also want to consider some definitions of Software Quality, here are a few links that can help you do that:
+
+* "Quality is value to some person." - Gerald Marvin Weinberg
+* [The Quality and Testing Information Model - Ministry of Testing](https://www.ministryoftesting.com/dojo/lessons/the-quality-and-testing-information-model)
+* [What does quality mean to me? - Ben Dowen](https://www.dowen.me.uk/posts/what-does-quality-mean-to-me)
+* [Adapting Crosby’s 4 absolutes of quality into a software context](https://danashby.co.uk/2019/09/30/adapting-crosbys-4-absolutes-of-quality-into-a-software-context/)
+
+## Where to start
+
+### Start to figure your scope and context
+
+It can be overwhelming starting to test software if you haven't done it before. One great thing to do early on is to start mapping out your context and understand the scope of what you're being asked to do.
+Scope is another what if saying, what is and isn't included. It is a very different prospect if you are being asked to test a single new feature, or assess the suitability of an entire application or hosted solution.
+
+If the scope of what you are being asked to do isn't clear, start by making some assumptions and then check these against whomever passed you on this work.
+
+**You can ask things like:**
+
+* Who is the testing for?
+* Who will want to hear about what I find?
+* What testing has already been done?
+* What functionality is new, and what existed already?
+* Can I see notes from anything that has been done so far?
+* Will additional testing be done after I'm done?
+* Who can I speak to if I have questions about the product/feature?
+* If I find issues, where can I raise them?
+* Is there time budgeted to fix any issues I find?
+
+As well as the scope, trying to understand what you will and won't be expected to do, you may want to get other context.
+
+**You should find out:**
+
+* Are there any rules, regulations or standards that need to be met?
+* Who makes the judgement on if we are compliant with these standards?
+* Are aspects like security, performance and accessibility already being considered by others?
+* Are there other parts of the company that need to get involved in accepting or releasing this software?
+
+### Choosing what to test
+
+OK, so you now have a potentially scary amount of context. Stay calm! Now you need to choose what to test, or at least what to test first.
+
+We can split this down into parts:
+
+* Figure out some things you could test
+* Choose the best thing to test next
+* Do some testing
+* Understand and discuss what you found so far
+* Cycle around until you have done enough testing
+
+### Figure out some things you could test
+
+On anything beyond the most trivial of software applications, there is so much that could be tested that it isn't possible to test it all, and definitely not quickly enough to be useful.
+
+So our first task is going broad, what could we test? For this, I like to do a number of things that I hope should be very doable without a huge amount of prior experience:
+
+* Speak to people involved in the software project. If you can, speak to the Developers, or the Vendor.
+ * Why do they need the new product/feature, what problem is it solving?
+ * What is keeping people up at night, what are they worried might go wrong?
+ * How people imagine the system/product/feature will typically be used?
+ * Who is expected to be using the system, if you can speak to these people ask them how they hope to use it?
+ * When do they expect to be using it?
+* Then I like to use a mind map to capture the answers
+ * To go one step further, for each node in the mind map, start asking "What if?" and record additional questions to be answered
+ * Review the mind map with others involved in the project, and record the feedback on the mind map too
+
+There are many free and paid tools to help build Mind Maps. [Miro](https://miro.com/) and [FreeMind](http://freemind.sourceforge.net/wiki/index.php/Main_Page) are popular. If you prefer you can use Pen and Paper, although this is more difficult to do collaboratively if you are not co-located with your team.
+
+### Choose the best thing to test next
+
+A [Risk Based Testing](https://www.guru99.com/risk-based-testing.html) approach can be very useful, and it is about understanding what might go wrong, how likely it is to go wrong and what impact it will have if it does go wrong.
+
+If you followed the steps above, you have a mind map of some things you could test. Have a think what the impact would be if you found a defect in one of the areas you identified? What impact would it have?
+
+As well as identifying those things that higher impact if they go wrong, also consider how easy or even possible it will be to test. Try and choose something that would be bad if it went wrong, and you have a fair chance of being able to do!
+
+## Do some testing
+
+You may be asking by now, [what do tests look like](https://www.ministryoftesting.com/dojo/lessons/what-do-tests-look-like)? And the answer, of course, is it depends.
+
+There are many different types of tests, the mainly fit into two basic categories:
+
+* Checks for what we know to expect
+* Investigations to learn
+
+Test Cases, also known as Test Scripts, fit into the Checks category. While these can take many formats they typically include some common parts:
+
+* Pre-conditions, the system state before the test starts
+* Steps to be carried out
+* Expected results, the desired system state after the test is done
+* Actual result, the observed sate of the system after the test is done
+
+You make hear these called different things. In the world of Unit Testing, there is the pattern [Arrange, Act, Assert](https://docs.microsoft.com/en-us/visualstudio/test/unit-test-basics?view=vs-2022#write-your-tests) and in [Behavior Driven Development (BDD)](https://cucumber.io/docs/bdd/) there is the Given, When, Then pattern.
+
+In a typical check the actual result is recorded and compared against the expected result, and if the two fail to match the test fails. In some cases instead of an exact match, a test might check the actual result is similar to the expectation, or close enough to be acceptable. A check that expects a numerical result may accept values within a range, or one that is equal or lower then the expectation.
+
+Investigative testing can take different forms, typically [Exploratory Testing](https://callumakehurstryansblog.wordpress.com/2021/09/17/ask-me-anything-exploratory-testing/). In Exploratory Testing we are investigating to learn answers to questions where we don't have explicit expectations or a pre-defined set of steps to follow. This doesn't mean Exploratory Testing is chaotic or unstructured, [Exploratory Testing is not Ad-Hoc Testing](https://callumakehurstryansblog.wordpress.com/2021/11/02/why-adhoc-testing-is-not-exploratory-testing/). Learn more about [How to Explore with Intent - Exploratory Testing Self-Management](https://www.ministryoftesting.com/dojo/lessons/how-to-explore-with-intent-exploratory-testing-self-management).
+
+### Take notes
+
+Taking testing notes is a skill, and one worth practicing and learning more about. It is a great start to make notes for yourself, to document what you did for future reference, and help you answer questions when people ask you what you covered in your testing.
+
+For exploratory sessions, where you are not looking at "pass / fail" but instead doing investigative testing to discover information, notes are even more important, because they will form part of the communication back to the team, or others in the project.
+
+For taking notes of exploration, I like to use a very simple template:
+
+***
+
+**Mission**
+
+What was the intention of this testing session. You could put a charter here, like "Explore , using to discover ", but equally you could use any format that makes sense for you. This is simply your statement of intent.
+
+**Summary**
+
+* Write this last
+* Use bullet points
+* Cover findings, outcomes and actions
+* This should help make notes more consumable for folks who won't read the detail
+
+**Notes**
+
+Free form notes, that includes thoughts, questions, answers, things you did and found.
+
+I also like to capture snippets of log messages, any commands I typed, screenshots of things I found interesting.
+
+***
+
+You can read more about testing notes, and other more structure templates like Session Based Testing:
+
+* [Notes on notes, James Thomas](https://qahiccupps.blogspot.com/2022/04/notes-on-testing-notes.html)
+* [Testing IRL - Session Based Test Management, Cassandra H. Leung](https://www.cassandrahl.com/blog/how-to-document-testing-with-sbtm-testing-irl-part-2/)
+
+## What to avoid
+
+### Being forced to play gatekeeper
+
+It is very likely, now you have assumed the role of Tester, willingly or otherwise, that you will be asked to pass judgement on the release of the product, or acceptance of the service.
+
+If you can resist the pressure to make this choice alone, instead focus on gathering facts (use your testing notes!) and having discussions with the team. Together, you can make an informed choice as to if you should proceed.
+
+### Believing misconceptions about testing
+
+There are many myths, legends and misconceptions about Software Testing. Don't fall for it!
+
+Here are some great place to go for some myth busting:
+
+* [Ten Misconceptions About Software Testing - That Non-Testers Share, Kate Paulk]()
+
+## Starting and finishing on time
+
+### How long will it take?
+
+You may well be asked, how long will testing take? While this sounds like an innocent question, there is no one right answer, so don't feel bad if you don't have one!
+
+Unless you have prior art, that is you have done a similar thing before, you're very unlikely to be able to produce an accurate estimation as to how long work will take.
+
+I'm sorry I'm not being much help on this one, mainly because while I've been working in testing for 10 years, and tried loads of ways to try and do estimates, they are all awful and they rarely stand up to reality.
+
+I appreciate this may not be very helpful, and if I get some better advice for you I'll come back and update this article!
+
+### When to stop testing
+
+So, you may not know how long it was going to take, but when do you stop?
+
+The answer for this is, again, tricky but you can consider a few things:
+
+* Does your team have confidence they understand enough about the change, and how it will impact users?
+* Do you have more open questions you need to answer?
+* Do you have any good ideas left on what testing could be done?
+* Is there a good way to know if the change has been successfully received by users?
+ * Monitoring of the system
+ * Feedback loop with real users
+* Can you roll back the change, or or get it fixed quickly, if there is a problem?
+
+Finally I will mention, testing is never really _done_, until the system you are testing is used for the last time by it's last user. But what is important, is are you done testing for now, enough to give it to the users to start using?
+
+### When is testing done, done?
+
+I like the way Callum talks about being done, in his Exploratory Testing AMA, and I paraphrase "You're done when you stop learning useful information".
+
+* [Ask Me Anything: Exploratory Testing, Callum Akehurst-Ryan](https://cakehurstryan.com/2021/09/17/ask-me-anything-exploratory-testing/)
+* [Ask Me Anything: Exploratory Testing \[Recording\], Callum Akehurst-Ryan]()
+
+Of course, you may have a time-box or a deadline for testing a feature. In this case, you may need to set expectations, communicate what you would like to do, and how much you might expect to do within the time available.
+
+This can be especially tricky if you're also holding down a different role, and testing is just yet another task with urgent priority. Be kind to yourself, learn what you can and work with others make the choice to finish.
+
+## Other unanswered questions for another day
+
+I'm confident, because I've had good feedback (Thanks sis!) that this won't answer all your questions. And I appreciate, I may of gone way too deep in some areas if you truly are jumping in for the first time, or in a non-testing role.
+
+Here are some topics I may visit in the future, and when I do I'll update this article, or link to the new one:
+
+* Testing terms explained, what is a defect anyway, and is it the same as a bug?
+* What is the difference between a _product_, a _system_ and _software_?
+* How to test a system we didn't build, say one provided by a vendor?
+* Example testing session, what does testing really LOOK like?
+
+## Resources
+
+### Books
+
+* [Agile Testing Condensed - by Janet Gregory and Lisa Crispin](https://leanpub.com/agiletesting-condensed)
+* [Explore it! By Elisabeth Hendrickson](https://www.amazon.co.uk/Explore-Increase-Confidence-Exploratory-Testing/dp/1937785025)
+* [Would Heu-Risk it? by Lena Wiberg](https://leanpub.com/wouldheuriskit)
+* [Exploratory Testing by Maaret Pyhäjärvi](https://leanpub.com/exploratorytesting)
+* [Testing Stories - by Melissa Fisher and an ensemble of great testers](https://leanpub.com/testing_stories)
+
+### Blog posts and articles
+
+* [How to Test Anything - James Thomas](https://qahiccupps.blogspot.com/2020/05/how-to-test-anything.html)
+* [Why do they test software - James Thomas](https://qahiccupps.blogspot.com/2022/03/why-do-they-test-software.html)
+* [What does quality mean to me? - Ben Dowen](https://www.dowen.me.uk/posts/what-does-quality-mean-to-me/)
+* [Adapting Crosby’s 4 absolutes of quality into a software context](https://danashby.co.uk/2019/09/30/adapting-crosbys-4-absolutes-of-quality-into-a-software-context/)
+* [Testing is an underrated skill in Testing (Test Automation isn’t everything) - Louise Gibbs](https://louisegibbstest.wordpress.com/2022/03/24/testing-is-an-underrated-skill-in-testing-test-automation-isnt-everything/)
+* [What Is Exploratory Testing? An Alternative To Scripted Testing And Try To Break It Testing - Ministry of Testing](https://www.ministryoftesting.com/dojo/lessons/what-is-exploratory-testing-an-alternative-to-scripted-testing-and-try-to-break-it-testing)
+
+### Testing Communities
+
+* [Ministry of Testing Club](https://club.ministryoftesting.com)
+* [The Test Chat - Telegram](https://bit.ly/TTCTelegram)
+* [The Test Tribe](https://www.thetesttribe.com)
+* [Testers Hangout - Discord](https://discord.gg/Nu64rg3EC2)
+* [Testers Hangout - Google Hangouts](https://bit.ly/testerhangout)
+
+### Cheat sheets
+
+* [Software Test Planning Checklist - Ministry of Testing](https://www.ministryoftesting.com/dojo/series/the-testing-planet-2019/lessons/the-software-testing-planning-checklist)
+* [Test Heuristics Cheat Sheet - Ministry of Testing](https://www.ministryoftesting.com/dojo/lessons/test-heuristics-cheat-sheet)
+* [Testing Guid - Chris Kenst](https://guides.kenst.com/)
+
+### Tools
+
+* [FreeMind](http://freemind.sourceforge.net/wiki/index.php/Main_Page)
+* [Miro](https://miro.com/)
+* [Postman](https://www.postman.com)
+ [Insomnia](https://insomnia.rest/)
+* [Chrome Dev tools Docs](https://developer.chrome.com/docs/devtools/)
+* [Resources for Software Testers - Ministry of Testing](https://www.ministryoftesting.com/dojo/series/resources) - Requires free login.
diff --git a/_posts/2022-05-25-building-your-toolbox-and-sharpening-your-tools.md b/_posts/2022-05-25-building-your-toolbox-and-sharpening-your-tools.md
new file mode 100644
index 0000000000000..1e2754d6981de
--- /dev/null
+++ b/_posts/2022-05-25-building-your-toolbox-and-sharpening-your-tools.md
@@ -0,0 +1,73 @@
+---
+title: Building your toolbox and sharpening your tools
+tags:
+ - testing
+ - automation
+ - tools
+date: '2022-05-25 00:00:00 +0100'
+categories:
+ - How to
+redirect_from:
+ - /building-your-toolbox-and-sharpening-your-tools/
+---
+
+Too long, didn't read:
+
+* Tools can include mental models, methods or software
+* Get inspired by following people on social media, read blogs and attend conferences
+* Learn new tools from resources such as presentations, blogs. books, tutorials and courses
+* Create regular opportunities to practice using tools, so you can be comfortable using them and even teaching others
+
+## Quality Engineering
+
+Tester? Quality Engineer? QA? There are many named roles in Software Testing, that can imply different work and scope, but often involve some of the same core skills.
+
+What is your bag? People, Process, or Product? This is the question that has led Meg to have a Job role existential crisis!
+
+In response I gleefully welcome Meg to my world, where I attempt to blend all of these things into my current role as a Quality Engineer.
+
+
+
+[https://twitter.com/FullSnackTester/status/1529206878793871361](https://twitter.com/FullSnackTester/status/1529206878793871361 "https://twitter.com/FullSnackTester/status/1529206878793871361")
+
+Think about this a bit more, what did I mean and how can it be helpful for others?
+
+## Build your toolbox
+
+As I have grown in software testing over my career, I like to think I've made progress becoming a better Tester. A large part of what that means to me, is that I have expanded my toolbox. I know more ways to solve problems, so not every problem looks like a nail and I reach for my hammer less and less.
+
+### What are tools?
+
+In this context, as well as software tools such as Postman, I also mean thinking tools like MindMaps, and techniques like Exploratory Testing.
+
+If you want a toolbox that covers People, Process and Product, you will need to collect a broad range of tools.
+
+### Learn from resources
+
+The primary way to learn new things, is to start by consuming resources. You may already be familiar with learning from Books, Courses, Blogs and other resources.
+
+Resources I've learned from include:
+
+* \[Book\] [Explore It!](https://www.amazon.co.uk/Explore-Increase-Confidence-Exploratory-Testing/dp/1937785025) -[ Elisabeth Hendrickson](https://twitter.com/testobsessed)
+* \[Course\] [Test Automation University](https://testautomationu.applitools.com/)
+* \[Blog\] [QA Hiccupps](https://qahiccupps.blogspot.com/) - [James Thomas](https://twitter.com/qahiccupps)
+* \[Blog\] [A Tester's Journey]() -[ Lisi Hocke](https://twitter.com/lisihocke)
+* \[Newsletter\] [Software Testing Weekly](https://softwaretestingweekly.com/)
+
+### Learn by experimentation
+
+Another excellent way of learning new tools, techniques and methods I've used is by finding opportunities to try things out.
+
+By running short experiments, we can quickly find out if something is worth further effort to learn deeper. While I have tried out many tools and run many short experiments, I don't have a useful example to share.
+
+## Sharpen your tools
+
+Now you know a bunch of new things, you have new tools in your toolbox! This is a great start, because it expands your knowledge base and helps you choose more specific tools for the problems you encounter.
+
+What I find, is that however much knowledge I consume, however much theory I ingest, I don't feel comfortable using tools until I've spent a good amount of time being uncomfortable and practice using them.
+
+Around the start of the year I had done some good learning Exploratory Testing form resources, but I was not comfortable using it regularly.
+
+In order to sharpen my Exploratory Testing skills I setup regular sessions to practice, every week and on the software my team is working on. This worked better then I hoped, and I am now comfortable Exploring and working with others introduce them to the method.
+
+In summary: Create regular opportunities to practice using tools.
diff --git a/_posts/2022-05-28-when-is-a-tester-not-a-tester.md b/_posts/2022-05-28-when-is-a-tester-not-a-tester.md
new file mode 100644
index 0000000000000..f7d267b6930d1
--- /dev/null
+++ b/_posts/2022-05-28-when-is-a-tester-not-a-tester.md
@@ -0,0 +1,146 @@
+---
+title: When is a Tester not a Tester?
+tags:
+ - testing
+ - quality
+ - quality Engineer
+date: '2022-05-28 00:00:00 +0100'
+categories:
+ - About Ben
+redirect_from:
+ - /when-is-a-tester-not-a-tester/
+---
+
+
+
+There are many competing thoughts on Software Testing and especially the roles we take on for those of us, as I do, who self define as Software Testers.
+
+How much is too much? Are there any boundaries, and should they exist? If Testing is an activity, and Quality is a whole team responsibility, who are the Testers?
+
+I'm going to indulge in discussing some thoughts and asking some questions. What I won't do is give definitive answers, because as it should be, your context will be different to mine.
+
+## Agile Teams
+
+For the approximately the first two years of my career I worked in an independent Test team, working on a Waterfall project. All work was estimated, and planned and was assigned to me. There was some comfort in this, I didn't have to spend time figuring out if I was doing valuable work, I just did as I was told as well as I could.
+
+Every since Citrix, where I was working in my early career, went though an "Agile Transformation", I have joined teams and worked alongside Developers.
+
+I'm confident independent Test teams still exist, and some companies will still be working in Waterfall. My context, is that Agile and indeed being agile, is now how I expect to work and where I have experience.
+
+Food for thought, the [Scrum Guide](https://scrumguides.org/scrum-guide.html#scrum-team "Scrum Guide Teams") defines a Scrum teams as consisting of:
+
+* Developers
+* Product Owner
+* Scrum Master
+
+There is no role in the guide for Tester.
+
+## Modern Software Testing Principles
+
+The [Modern Testing Principles](https://www.ministryoftesting.com/dojo/lessons/modern-testing-principles) - by [Alan Page](https://twitter.com/alanpage "Alan Page on Twitter") and [Brent Jensen](https://twitter.com/BrentMJensen "Brent Jensen on Twitter") have gained some popularity, and caused some controversy in the Software Testing and Development communities.
+
+Some read the principles to mean there should be no distinct role for Testers, and instead all members of the team should share testing responsibilities.
+
+Outrageous, you might a say, if as me you are someone who self-defines as a Software Tester.
+
+But wait a moment, this also lines up with the Scrum Guide! So, what is there left for us Software Testers to do?
+
+## The many roles of the Software Tester
+
+While I identify as a Software Tester, that has never been my exact job title.
+
+Roles I have held are:
+
+* Software Test Engineer
+* Software Quality Analyst
+* Quality Manager
+* QA Engineer
+* Quality Engineer
+
+In all of these roles, I have done some things that are similar, and some things that are wildly different.
+
+In all these roles, I have tested software. With the exception of my first few years at Citrix, I have always been a member of an agile team. The different teams I've been on have all done agile differently, but I've always joined in with whatever ceremonies and activities the team as done as part of building software.
+
+As part of agile teams, I have:
+
+* Written user stories and set acceptance criteria
+* Refined work items (stories, tasks, etc) and added estimates
+* Managed backlogs and prioritized work
+* Taken part in and run stand-ups and retrospectives
+
+I've also done many other communication and glue work type of tasks. In one role, when working for a small consultancy, I worked very closely with clients. Reproducing bugs and even helping to determine if things where not bugs, but in fact missing requirements that may need extra payments.
+
+In some of my roles, I've also done some very technical tasks, that you may or may not consider part of Software Testing:
+
+* Developed testing tools
+* Developed automated checking frameworks
+* Fixed bugs in configuration and code
+* Built infrastructure, software and hardware for test labs
+
+Some of the things I've done, could of been done by a Product Manager, a Business Analyst, a Scrum Master, a Designer, a Software Developer, a Solutions Architect or one of many other roles.
+
+Food for thought: Does this mean I've been doing loads of "not Tester" work? Or does it mean the role of a Tester has wide and varied, and can be flexible enough to fill gaps that could be taken on by other roles?
+
+Besides Scrum Master and Developer, many of these roles are also not defined in the Scrum guide.
+
+## So who is doing all the testing?
+
+So, if it's not being done by Software Testers, whatever their role and title, who is going to do all that testing?
+
+Are we really going to take a huge step backwards in the Software industry, and stop testing?
+
+This is where we need to have a think about context and maturity. Some teams may well do just fine with testing being done wholly by people who are titled as Developers.
+
+What about when your existing Software Developers don't have experience in testing software? Or maybe their idea of testing is no more advanced then checking against the acceptance criteria and maybe some unit tests.
+
+A Product Owner might take on some parts of what a Software Tester does. Some people I've worked with that have Product in their title have wanted to try things out for themselves, they have asked great questions in demos and given team good feedback. This works great when your team is making Websites or other software that can be demoed visually. It's less useful for teams working on back-end APIs or libraries.
+
+What about automation, you might say? Automation is great, and should be a health part of your software development process. In my experience automation is not sufficient to evaluate the usefulness of software, access its value or experience the usability, emotional response or goodness. I've also seen some pretty awful automation, that hasn't covered risks and has missed the key, high priority parts of what a product should do.
+
+When developing automation myself, I've often found it is the analysis and testing I've done on the journey to build it, that has found the bugs, not the automation itself. In my experience, automation is not the answer in and of itself.
+
+## Quality Engineering
+
+The return of the Software Tester! But this time, we are more likely to be called Quality Coach, or as I am a Quality Engineer.
+
+I'm still learning about Quality Engineering, and what it is like to be a Quality Engineer. I've been a QE now for about 11 months at time of writing. And so far, it feels a lot like being a Software Tester, but with a wider scope and some opportunities for coaching.
+
+So, is Quality Engineer just another way of saying Tester? Maybe. I hope not. I've had some very interesting conversations about Quality Engineering with [Stu Crock](https://twitter.com/StooCrock "Stu Crock on Twitter"), [Neil Younger](https://www.linkedin.com/in/neil-younger/ "Neil Younger on LinkedIn"), [Jessica Bane](https://www.linkedin.com/in/jessica-bane-testing-mermaid/ "Jessica Bane on LinkedIn") and [Dan Ashby](https://twitter.com/DanAshby04 "Dan Ashby on Twitter"). Full disclosure, I currently work with Dan at [Ada Health](https://ada.com/ "Ada Health Website").
+
+All agree that Quality Engineering is about more then simply the act of doing all the testing, within the context of a single team. The topic of coaching and supporting teams comes up often, and the idea of teaching by doing.
+
+Quality Engineering could easily include building frameworks to support other people to do testing. Advocating for a whole team approach to quality, and considering quality issues beyond the immediate deliverable of the team, software. Quality Engineering also includes work to improve Processes, Designs, and generally improve the support for teams to produce better products.
+
+Like Testing, Quality Engineering is not the same to all people. The main question is still the same: Does Quality Engineering, mean we need people with the role of Quality Engineer? This is where there is some disagreement, and again it comes down to context and maturity.
+
+Can you do Quality Engineering without having any Quality Engineers or Testers? Yes! At least Stu is currently doing just that right now in his context. He is in a context where he is the Head of Quality Engineering in a company that has no Testers, no Quality Engineers. And last I checked in with Stu, it was going very well.
+
+In another context, Neil and Jessica are at Omnipresent. They are currently scaling quickly, with new teams coming on board often. Neil started as the only Quality Engineer, [but is now hiring](https://www.linkedin.com/feed/update/urn:li:activity:6927559055351672832/ "Neil is hiring QEs") others to support him as the number of teams that get value from a QE is growing faster then he scan scale the support he alone gives.
+
+Finally to my own context. I work at Ada Health, a health technology company operating in a world where our software is classified as a medical device, and such requires compliance with regulation. Dan started two years ago at Ada Health as Director of Quality Services, and has proceeded to build an amazing team of Quality Engineers, that I am proud to be part of. In my context, most teams have their own Quality Engineer.
+
+As a Quality Engineer at Ada Health, I belong to an agile team. It has been an interesting journey finding my feet as a QE, working with Developers some of whom had never worked with a Tester (of any role or title) before.
+
+As well as supporting my immediate team, I have the pleasure of extending my scope and working with other teams in my group to support their testing activities. I am having a huge amount of success working with the Medical Knowledge Engineers (Doctors) to bring practices from Software Testing to their world of testing for medical correctness and safety.
+
+## Testing Advocacy
+
+[Karen Todd](https://www.linkedin.com/in/karen-todd-48b242114/ "Karen Todd on LinkedIn") has been doing an amazing job talking about Testing Advocacy, and working with the community to define the term. If you haven't already seen it, I highly recommend you check out [@KarenTestsStuff on YouTube](https://www.youtube.com/channel/UCaILiR0XEzf0Y1QvibzybCQ "Karen Tests Stuff on YouTube"), where she has a number of great interviews discussing the topic.
+
+I have my own reasons for considering myself a Testing Advocate:
+
+* I support and promote the craft of software testing, at work and in the community
+* I support the community to recognize contributions to software testing
+* I coach others in the joy of testing
+
+## Long live Software Testers
+
+[Nicola Lindgren](https://twitter.com/NicolaLindgren "Nicola Lindgren on Twitter") recently [asked on Twitter ](https://twitter.com/NicolaLindgren/status/1530504214547505155 "Nicola's post on Twitter")if a job tittle matters. At the time of writing, the poll is on 55% Yes, 45% No with 88 votes cast and 17 hours to go.
+
+The context of her question was about seniority, and if you would take a job with a less senior title when moving jobs. But another way to think about the question is if job role matters to you?
+
+To me, it matters. It matters because it helps shape the way I think about the role, and therefore the way I set myself expectations and this influences actions I take. It matters because it shapes the way others see the role, and their expectations.
+
+Job title and role are not the only thing that matter, and both can be overcome or outgrown by context and communication.
+
+In summary, I have always been, and never been, and always will be a Software Tester.
diff --git a/_posts/2022-05-31-software-testing-development-and-agile-blogs.md b/_posts/2022-05-31-software-testing-development-and-agile-blogs.md
new file mode 100644
index 0000000000000..6dccea70c6ad4
--- /dev/null
+++ b/_posts/2022-05-31-software-testing-development-and-agile-blogs.md
@@ -0,0 +1,65 @@
+---
+title: 'Software Testing, Development and Agile Blogs'
+tags:
+ - software
+ - testing
+ - development
+ - agile
+ - blogs
+date: '2022-05-31 00:00:00 +0100'
+categories:
+ - Community
+redirect_from:
+ - /software-testing-development-and-agile-blogs/
+---
+
+I learn a lot from blogs. So I was very excited when a thread I started on [Twitter](https://twitter.com/FullSnackTester/status/1531181120859123714) and then [LinkedIn](https://www.linkedin.com/posts/dowenb_softwaretesting-activity-6937332208307200000-V1dP?utm_source=linkedin_share&utm_medium=member_desktop_web) asking for blogs on Software Testing and Development I could follow, there was a truly excellent response.
+
+At the time of writing, there are 44 blogs shared in total across the two threads, I've gathered the full list together here so I can find them later. I hope it is also a useful resource for others.
+
+The list is ordered alphabetically by URL and is otherwise an unordered list.
+
+* [http://agiletester.ca/blog](http://agiletester.ca/blog "http://agiletester.ca/blog") - [**Janet Gregory**](https://twitter.com/janetgregoryca) and [**Lisa Crispin**](https://twitter.com/lisacrispin)
+* [http://agiletestingfellow.com/blog](http://agiletestingfellow.com/blog "http://agiletestingfellow.com/blog") - [**Janet Gregory**](https://twitter.com/janetgregoryca) and [**Lisa Crispin**](https://twitter.com/lisacrispin)
+* [http://lisacrisin.com](http://lisacrispin.com "http://lisacrispin.com") - [**Lisa Crispin**](https://twitter.com/lisacrispin)
+* [http://www.eliasnogueira.com/](http://www.eliasnogueira.com/ "http://www.eliasnogueira.com/") - [**Elias Nogueira**](https://twitter.com/eliasnogueira)
+* [https://adventuresinqa.com/](https://adventuresinqa.com/ "https://adventuresinqa.com/") - [**Daniel Knott**](https://twitter.com/dnlkntt)
+* [https://agile-and-testing.chriss-baumann.de/](https://agile-and-testing.chriss-baumann.de/ "https://agile-and-testing.chriss-baumann.de/") - [**Christian Baumann**](https://twitter.com/chrissbaumann)
+* [https://automationpnda.com/](https://automationpanda.com/ "https://automationpanda.com/") - [**Pandy Knight**](https://twitter.com/AutomationPanda)
+* [https://bjtestingtalks.wordpress.com/](https://bjtestingtalks.wordpress.com/ "https://bjtestingtalks.wordpress.com/") - [**Balaji Santhanagopalan**](https://www.linkedin.com/in/balaji-santhanagopalan-82a63a108/)
+* [https://callumakehurstryansblog.wordpress.com/](https://callumakehurstryansblog.wordpress.com/ "https://callumakehurstryansblog.wordpress.com/") - [**Callum Akehurst-Ryan**](https://twitter.com/CAkehurstRyan)
+* [https://cristianomcunha.com/](https://cristianomcunha.com/ "https://cristianomcunha.com/") - [**Cristiano Cunha**](https://twitter.com/Melioth)
+* [https://critical-qa.info/](https://critical-qa.info/ "https://critical-qa.info/") - [**Loivado**](https://twitter.com/Loivado)
+* [https://dev.to/ashleygraf_](https://dev.to/ashleygraf_ "https://dev.to/ashleygraf_") - [**Ashley Graf**](https://twitter.com/ashleygraf_)
+* [https://dev.to/walmyrlimaesilv](https://dev.to/walmyrlimaesilv "https://dev.to/walmyrlimaesilv") - [**Walmyr Filho**](https://twitter.com/walmyrlimaesilv)
+* [https://emnaayadi.com/](https://emnaayadi.com/ "https://emnaayadi.com/") - [**Emna Ayadi**](https://twitter.com/emna__ayadi)
+* [https://filiphric.com/](https://filiphric.com/ "https://filiphric.com/") - [**Filip Hric**](https://twitter.com/filip_hric)
+* [https://fishouthebox.medium.com/](https://fishouthebox.medium.com/ "https://fishouthebox.medium.com/") - [**Melissa Fisher**](https://twitter.com/fishouthebox)
+* [https://flynnbops.github.io/](https://flynnbops.github.io/ "https://flynnbops.github.io/") - [**Aaron Flynn**](https://twitter.com/flynnbops)
+* [https://g33klady.com/](https://g33klady.com/ "https://g33klady.com/") - [**Hilary aka H-Bomb**](https://twitter.com/g33klady)
+* [https://github.com/NoriSte/all-my-contributions#articles](https://github.com/NoriSte/all-my-contributions#articles "https://github.com/NoriSte/all-my-contributions#articles") - [**Stefano Magni**](https://twitter.com/NoriSte)
+* [https://janetgregory.ca/blog/](https://janetgregory.ca/blog/ "https://janetgregory.ca/blog/") - [**Janet Gregory**](https://twitter.com/janetgregoryca)
+* [https://jlottosen.wordpress.com/](https://jlottosen.wordpress.com/ "https://jlottosen.wordpress.com/") - [**Jesper**](https://twitter.com/jlottosen)
+* [https://medium.com/@iamfaisalkhatri](https://medium.com/@iamfaisalkhatri "https://medium.com/@iamfaisalkhatri") - [**Faisal Khatri**](https://twitter.com/mfaisal_khatri)
+* [https://mfaisalkhatri.github.io/](https://mfaisalkhatri.github.io/ "https://mfaisalkhatri.github.io/") - [**Faisal Khatri**](https://twitter.com/mfaisal_khatri)
+* [https://mfaisalkhatri.hashnode.dev/](https://mfaisalkhatri.hashnode.dev/ "https://mfaisalkhatri.hashnode.dev/") - [**Faisal Khatri**](https://twitter.com/mfaisal_khatri)
+* [https://mindfultester.com/](https://mindfultester.com/ "https://mindfultester.com/") - [**ir. Han Toan Lim**](https://twitter.com/MIndfulTester)
+* [https://nicolalindgren.com/](https://nicolalindgren.com/ "https://nicolalindgren.com/") - [**Nicola Lindgren**](https://twitter.com/NicolaLindgren)
+* [https://qualitybits.tech/](https://qualitybits.tech/ "https://qualitybits.tech/") - [**Lina Zubyte**](https://twitter.com/buggylina)
+* [https://randomtechthoughts.blog/](https://randomtechthoughts.blog/ "https://randomtechthoughts.blog/") - [**Bob Salmon**](https://twitter.com/BobTechThoughts)
+* [https://responsibleautomation.wordpress.com/](https://responsibleautomation.wordpress.com/ "https://responsibleautomation.wordpress.com/") - [**Paul Grizzaffi**](https://twitter.com/pgrizzaffi)
+* [https://rieckpil.de/](https://rieckpil.de/ "https://rieckpil.de/") - [**Philip Riecks**](https://twitter.com/rieckpil)
+* [https://russmorley.net/](https://russmorley.net/ "https://russmorley.net/") - [**Russell Morley**](https://www.linkedin.com/in/russell-morley/)
+* [https://scrolltest.com/](https://scrolltest.com/ "https://scrolltest.com/") - [**Pramod Dutta**](https://twitter.com/itstechmode)
+* [https://seasidetesting.com/](https://seasidetesting.com/ "https://seasidetesting.com/") - [**Stephan Kämper**](https://twitter.com/S_2K)
+* [https://sowmyasridharamurthy.blogspot.com/](https://sowmyasridharamurthy.blogspot.com/ "https://sowmyasridharamurthy.blogspot.com/") - [**Sowmya Sridharamurthy**](https://twitter.com/Someoooww)
+* [https://testandanalysis.home.blog/](https://testandanalysis.home.blog/ "https://testandanalysis.home.blog/") - [**Mike Harris**](https://twitter.com/TestAndAnalysis)
+* [https://testersdigest.blogspot.com/](https://testersdigest.blogspot.com/ "https://testersdigest.blogspot.com/?m=1") - [**Dheeraj Gambhir**](https://twitter.com/dheerajgambhir)
+* [https://testingtitbits.com/](https://testingtitbits.com/ "https://testingtitbits.com/") - [**Rahul Parwal**](https://twitter.com/parwalrahul)
+* [https://thetesttherapist.com/](https://thetesttherapist.com/ "https://thetesttherapist.com/") - [**Mohamed Tarek**](https://twitter.com/motareksamir)
+* [https://typeshare.co/vernonrichards](https://typeshare.co/vernonrichards "https://typeshare.co/vernonrichards") - [**Vernon Richards**](https://twitter.com/TesterFromLeic)
+* [https://wiert.me/](https://wiert.me/ "https://wiert.me/") - [**Jeroen Wiert Pluimers**](https://twitter.com/jpluimers)
+* [https://www.lisihocke.com/](https://www.lisihocke.com/ "https://www.lisihocke.com/") - [**Lisi Hocke**](https://twitter.com/lisihocke)
+* [https://www.mariedrake.com/](https://www.mariedrake.com/ "https://www.mariedrake.com/") - [**Marie Drake**](https://twitter.com/mcruzdrake)
+* [https://www.softwaretester.blog/](https://www.softwaretester.blog/ "https://www.softwaretester.blog/") - [**Benjamin Bischoff**](https://twitter.com/BischoffDev)
+* [https://www.zeljkovic.sh/blog/](https://www.zeljkovic.sh/blog/ "https://www.zeljkovic.sh/blog/") - [**Aleksandar Zeljković**](https://twitter.com/a_zeljkovic)
diff --git a/_posts/2022-06-01-creating-software-is-a-team-sport.md b/_posts/2022-06-01-creating-software-is-a-team-sport.md
new file mode 100644
index 0000000000000..de528b0d9324a
--- /dev/null
+++ b/_posts/2022-06-01-creating-software-is-a-team-sport.md
@@ -0,0 +1,43 @@
+---
+title: Building software is a team sport
+tags:
+ - agile
+ - software
+ - devops
+ - quality
+date: '2022-06-01 00:00:00 +0100'
+categories:
+ - Quality
+redirect_from:
+ - /creating-software-is-a-team-sport/
+---
+
+As I recently [posted on Twitter](https://twitter.com/FullSnackTester/status/1531900848955174912?s=20&t=brWbrVy_OYBSqPrVSCh5xQ), I really believe that building great software products, services and solutions is a team sport. In some team sports, teams are made up of a fixed number of people, playing fixed roles. In others, squads of multidisciplinary players swap in and out for each game, even mid game.
+
+
+
+Photo by NEOSiAM 2021: [https://www.pexels.com/photo/selective-focus-photography-of-foosball-table-595229/](https://www.pexels.com/photo/selective-focus-photography-of-foosball-table-595229/ "https://www.pexels.com/photo/selective-focus-photography-of-foosball-table-595229/")
+
+Then there are the supporting roles, the people who coach the team, the physio who keep them well. How many people does it take to allow two formula one drivers to race a single race, for one team? Hundreds at least!
+
+Building software based products is a similar story, one of teams of people coming together all playing important roles. And like sports, how many people, in what roles, is dependent on a number or key things. Two of these factors are scale and budget.
+
+At the most basic, ten people could out together two five-a-side football teams, hire a pitch and play a game of football. They have no coach, or physio or any of the many other supporting roles. How many people do Manchester United have? Scale, budget, context.
+
+Teams building software are no different. One developer can make software. Budget is low, but there is only one mouth to feed (and maybe their Family). At this scale, any bug fix interrupts development. If multiple customers have competing priorities, one has to wait.
+
+Anything new must be learnt before they can use it. If they go on vacation everything stops. There is no one else to support customers. Some customers will avoid using products from a single developer, because in their context they need uninterrupted support. So... We scale.
+
+As we scale companies, we might have goals we want to achieve with this new capacity. Being able to attract larger customers with deeper pockets and commit for longer. Scope for taking holidays. Building new features faster. Build and operate reliable products.
+
+This is where we start to introduce roles. We no longer have only Developers. Now we have people who look after Product, Sales, Support, Operations, Legal, HR, Quality and more. Depending on context, and scale, these maybe people or services from other organisations.
+
+Somewhere along the way, as the company grows we might run into problems. We grew our budget, added roles but we still haven't met our goals and some of us are miss the days a small team could ship their own product without help.
+
+One way we might try and fix this, is by shaping our teams into multidisciplinary powerhouses. With Devs, Ops, Product and Quality all together, maybe more too! This power team can play their part of the game. But did we solve our problem? Meet our goals? Are we tracking them?
+
+Over time, sports teams and hope they are supported have evolved. Formula One today is light years ahead of where it was in the 1980s. And so too software teams and organisational structures change.
+
+What is important is to understand your goals, identify your problems and measure your progress. Don't get distracted by how others are playing the game, focus on what works for your team! This is a journey. I've heard again and again "No such thing as a DevOps engineer"
+
+I've also heard, that there should be no Testers. Just Developers who are coached and taught how to test. This might work great for some teams That doesn't mean you should feel bad for having your DevOps and QEs in your success team. In your current context, budget and scale.
diff --git a/_posts/2022-06-07-interviews-with-testers.md b/_posts/2022-06-07-interviews-with-testers.md
new file mode 100644
index 0000000000000..b7b5d7143c4a1
--- /dev/null
+++ b/_posts/2022-06-07-interviews-with-testers.md
@@ -0,0 +1,79 @@
+---
+title: Meet the Testers
+tags:
+ - testing
+ - community
+ - interview
+date: '2022-06-07 00:00:00 +0100'
+categories:
+ - Community
+redirect_from:
+ - /interviews-with-testers/
+---
+
+What better way to learn about the amazing people in the Software Testing Community then reading and watching their interviews.
+
+In this short post I will introduce you to the Tester of The Day winner and community interviews, and direct you to some other great hosts who interview amazing testers!
+
+
+
+Photo by fauxels: [https://www.pexels.com/photo/top-view-photo-of-people-near-wooden-table-3183150/](https://www.pexels.com/photo/top-view-photo-of-people-near-wooden-table-3183150/ "https://www.pexels.com/photo/top-view-photo-of-people-near-wooden-table-3183150/")
+
+## Tester of The day Winners Interviews
+
+The Tester of The Day winners interviews are a great way to get a little more insight into the amazing contributors to the Software Testing Community.
+
+We have classics, like the [interview from winner number 1, Chris McMahon](https://interviews.testeroftheday.com/interviews/2021/02/13/chris-mcmahon.html). Chris goes into some really excellent depth and his story about his favorite bug is not to be missed!
+
+Make sure to check out the full list of interviews: [https://interviews.testeroftheday.com/](https://interviews.testeroftheday.com/ "https://interviews.testeroftheday.com/")
+
+Are you a winner of Tester of The Day? why not add your interview, simply fill out this form: [https://testeroftheday.com/forms/interview](https://testeroftheday.com/forms/interview "https://testeroftheday.com/forms/interview")
+
+## Tester of The Day Community Interviews
+
+It's not only winners that get the opportunity to complete an interview for the Tester of The Day site! So far a [Rhual Singh](https://interviews.testeroftheday.com/interviews/2021/04/18/rahul-singh.html), [Andrew Palmer](https://interviews.testeroftheday.com/interviews/2021/04/18/andrew-palmer.html) and [Alexander Podelko](https://interviews.testeroftheday.com/interviews/2021/04/18/alexander-podelko.html) have taken the opportunity.
+
+Want to join in and add your own interview? Simply fill out this form [https://testeroftheday.com/forms/community-interview](https://testeroftheday.com/forms/community-interview "https://testeroftheday.com/forms/community-interview")
+
+## Nicola Lindgren Interviews
+
+[Nicola](https://twitter.com/NicolaLindgren) has been interviewing Testers since 2013! Starting with [an interview with Markus Gaertner](https://nicolalindgren.com/2013/05/30/interview-with-markus-gaertner/), with hard hitting questions like "Where do you see software testing going in the next 5 years?" and "When your friends (outside of IT) ask you “What do you do as a software tester?”, what do you tell them?" it's worth a read to learn what Markus has to say.
+
+And don't let the early start fool you, Nicola is still active in 2022, if anything more so with 7 interviews so far this year, phew! The [latest interview is with the amazing Lisi Hocke](https://nicolalindgren.com/2022/05/14/interview-with-lisi-hocke/), discussing ensemble testing.
+
+You can check out all of Nicola's interviews here: [https://nicolalindgren.com/categories/interviews/](https://nicolalindgren.com/categories/interviews/ "https://nicolalindgren.com/categories/interviews/")
+
+**BONUS**: Nicola is now doing video interviews and posting them on her [new YouTube channel](https://youtube.com/playlist?list=PLY8Q7oWc4F1TqgsggrzoCTRPcJ4NZzO--).
+
+## Testing Tales with The Pirate Tester
+
+[Lee "Ahoy there" Marshall](https://twitter.com/ThePirateTester), aka The Pirate Tester, takes on a different approach with video series [Testing Tales](https://twitter.com/ThePirateTester). Lee has already posted interviews with 5 amazing people, including at least one "not a tester", [Bob Salmon](https://www.youtube.com/watch?v=0LhwCzsYDco&list=PLk1f2uumbghTWUgX8KKE5qwy7mxIMFa35&index=2).
+
+Full disclosure, I've done an interview with Lee myself, spoiler alert it maybe some weeks before it is posted as he has a terrific backlog of videos to edit and post. So make sure you like and subscribe, as the YouTubers love to say.
+
+You can find the [Testing Tales Playlist here](https://www.youtube.com/watch?v=vwofmO1CmyE&list=PLk1f2uumbghTWUgX8KKE5qwy7mxIMFa35).
+
+## Testing Advocacy with Karen Tests Stuff
+
+More video interviews, this time Karen Todd, aka @KarenTestsStuff on [Twitter](https://twitter.com/KarenTestsStuff) and [YouTube](https://www.youtube.com/channel/UCaILiR0XEzf0Y1QvibzybCQ). Karen is taking on the topic of Software Testing Advocacy, and has now discussed it with some really great members of the community including [Beth Marshall](https://www.youtube.com/watch?v=W4d_s52FdPg&list=PLoGM4JmbNY0yLVNOdyWUttA8sCnBPlQ-V&index=3), [Erin Hess](https://www.youtube.com/watch?v=Dtuy4HYWDdM&list=PLoGM4JmbNY0yLVNOdyWUttA8sCnBPlQ-V&index=6) and [Simon Tomes](https://www.youtube.com/watch?v=isQCYFmbNUw&list=PLoGM4JmbNY0yLVNOdyWUttA8sCnBPlQ-V&index=5).
+
+[Check out the full playlist of here.](https://www.youtube.com/watch?v=sOGaYJgnQVw&list=PLoGM4JmbNY0yLVNOdyWUttA8sCnBPlQ-V)
+
+## Contract Testing Podcast with Lewis Prescott
+
+Lewis hosts a [podcast focusing on contract testing](https://www.pactman.co.uk/contract-testing-podcast), and interviews fantastic testers who are on their contract testing journey, and also bring other interesting insights to the table.
+
+Lewis recently [interviewed AJ Wilson](https://www.pactman.co.uk/contract-testing-podcast/episode/ac0227b7/exploratory-testing-apis-with-aj-wilson) and discussed Exploratory Testing API's, definitely worth checking out!
+
+You can listen to all of the episodes at: [https://www.pactman.co.uk/contract-testing-podcast](https://www.pactman.co.uk/contract-testing-podcast "https://www.pactman.co.uk/contract-testing-podcast")
+
+## But what about???
+
+Did I miss some other places Testers are being interviewed? Let me know! I'll add em on.
+
+#### Updated
+
+2022-06-09:
+
+* Added Contract Testing Podcast with Lewis Prescott
+* Added Nicola's YouTube channel
diff --git a/_posts/2022-06-16-software-testing-community.md b/_posts/2022-06-16-software-testing-community.md
new file mode 100644
index 0000000000000..5efc26d7a957d
--- /dev/null
+++ b/_posts/2022-06-16-software-testing-community.md
@@ -0,0 +1,105 @@
+---
+title: Software Testing Community
+tags:
+ - community
+ - testing
+date: '2022-06-16 00:00:00 +0100'
+categories:
+ - Community
+redirect_from:
+ - /software-testing-community/
+---
+
+I have a lot to thank the Software Testing Community for, you are all a really amazing bunch of human beings!
+
+The community helps me to learn, challenges me, lifts my mood and even supports me when I'm looking for new opportunities. I've made friends, and been inspired. For this I'm very grateful.
+
+So, what is out there, and how can you get involved?
+
+
+
+Photo by Dio Hasbi Saniskoro: [https://www.pexels.com/photo/people-doing-group-hand-cheer-3280130/](https://www.pexels.com/photo/people-doing-group-hand-cheer-3280130/ "https://www.pexels.com/photo/people-doing-group-hand-cheer-3280130/")
+
+## Association for Software Testing
+
+> The Association for Software Testing (AST) is a professional organization for software testers. We strive to build a testing community that views the role of testing as skilled, relevant, and essential to the production of faster, better, and less expensive software products. We value a scientific approach to developing and evaluating techniques, processes, and tools. We believe that a self-aware, self-critical attitude is essential to understanding and assessing the impact of new ideas on the practice of testing.
+
+Source: [https://associationforsoftwaretesting.org/about-the-ast-a-professional-body-for-testers/](https://associationforsoftwaretesting.org/about-the-ast-a-professional-body-for-testers/ "https://associationforsoftwaretesting.org/about-the-ast-a-professional-body-for-testers/")
+
+Full disclosure, I am an AST member! I took advantage of their new "Pay what you can" model, and with this membership is really very accessible. AST have a Slack group, blog syndication for members and run CAST, [the Conference of the Association for Software Testing](https://associationforsoftwaretesting.org/conference/).
+
+Website: [https://associationforsoftwaretesting.org/](https://associationforsoftwaretesting.org/ "https://associationforsoftwaretesting.org/")
+
+Twitter: [https://twitter.com/AST_News](https://twitter.com/AST_News "https://twitter.com/AST_News")
+
+LinkedIn: [https://www.linkedin.com/company/association-for-software-testing/](https://www.linkedin.com/company/association-for-software-testing/ "https://www.linkedin.com/company/association-for-software-testing/")
+
+## Ministry of Testing
+
+> Our Story
+>
+> We’ve come a long way from our modest beginnings in 2007. The long timers in our community will know that Ministry of Testing started out at The Software Testing Club. A humble forum that, over the years, grew into an amazing and thriving online community of testers. The Software Testing Club forum is now switched off, but our online community continues to grow and discuss all things testing on our shiny new forum [The Club](https://club.ministryoftesting.com/).
+
+Source: [https://www.ministryoftesting.com/about](https://www.ministryoftesting.com/about "https://www.ministryoftesting.com/about")
+
+Website: [https://www.ministryoftesting.com/](https://www.ministryoftesting.com/ "https://www.ministryoftesting.com/")
+
+Forum: [https://club.ministryoftesting.com/](https://club.ministryoftesting.com/t/welcome-to-the-club-by-ministry-of-testing/8?u=fullsnacktester "https://club.ministryoftesting.com/")
+
+Slack: [https://www.ministryoftesting.com/slack_invite](https://www.ministryoftesting.com/slack_invite "https://www.ministryoftesting.com/slack_invite")
+
+Twitter: [https://twitter.com/ministryoftest](https://twitter.com/ministryoftest "https://twitter.com/ministryoftest")
+
+LinkedIn: [https://www.linkedin.com/company/ministry-of-testing/](https://www.linkedin.com/company/ministry-of-testing/ "https://www.linkedin.com/company/ministry-of-testing/")
+
+### Ministry of Testing Meetups
+
+You can't get much more local testing community then the MoT meet-ups! They are a great way to meet Testers in your local area, and an amazing opportunity to present.
+
+Many of the best in the industry started by presenting at meet-ups such as these, and they still often bring their talks to meet-ups first, to test their ideas and practice ahead of larger conferences.
+
+List of meetups: [https://www.ministryoftesting.com/meetups](https://www.ministryoftesting.com/meetups "https://www.ministryoftesting.com/meetups")
+
+## Test Automation University
+
+TAU is an amazing resource to learn, for free, about Test Automation! There is also an active slack community, with channels focusing around each course and more generally helping each-other learn.
+
+Website: [https://testautomationu.applitools.com/](https://testautomationu.applitools.com/ "https://testautomationu.applitools.com/")
+
+Slack: [https://tauslacksignupapp.herokuapp.com/](https://tauslacksignupapp.herokuapp.com/ "https://tauslacksignupapp.herokuapp.com/")
+
+Twitter: [https://twitter.com/TestAutomationU](https://twitter.com/TestAutomationU "https://twitter.com/TestAutomationU")
+
+LinkedIn: [https://www.linkedin.com/company/testautomationu/](https://www.linkedin.com/company/testautomationu/ "https://www.linkedin.com/company/testautomationu/")
+
+LinkedIn:
+
+## Test Tribe
+
+> This is a story of passion for Software Testing. A story of making change happen. A story of sincere attempt to bring more glory to the craft of Testing.
+
+The Test Tribe run a regular events and have a thriving [community on Discord](https://discord.gg/4qcSKMjVhY).
+
+Website: [https://www.thetesttribe.com/](https://www.thetesttribe.com/ "https://www.thetesttribe.com/")
+
+Join the community: [https://www.thetesttribe.com/community/](https://www.thetesttribe.com/community/ "https://www.thetesttribe.com/community/")
+
+Twitter: [https://twitter.com/the_test_tribe](https://twitter.com/the_test_tribe "https://twitter.com/the_test_tribe")
+
+LinkedIn: [https://www.linkedin.com/company/thetesttribe/](https://www.linkedin.com/company/thetesttribe/ "https://www.linkedin.com/company/thetesttribe/")
+
+## The Test Chat
+
+The Test Chat is primarily a large group on Telegram, and I do mean large! At time of writing there are over 4500 members.
+
+Telegram: [https://t.me/joinchat/UKDuiCJi-pPpv_9a](https://t.me/joinchat/UKDuiCJi-pPpv_9a)
+
+Twitter: [https://twitter.com/TheTestChat](https://twitter.com/TheTestChat "https://twitter.com/TheTestChat")
+
+## Testers Hangout
+
+Started by [Lee "The Pirate Tester" Marshall](https://twitter.com/ThePirateTester) as a support network around the start of the UK Lock-down in 2020. The Testers Hangout has grown organically and has been a great way for me to meet some really amazing human beings from the world of Software Testing!
+
+Google Hangout: [https://bit.ly/testerhangout](https://bit.ly/testerhangout "https://bit.ly/testerhangout")
+
+Discord Group: [https://discord.gg/Nu64rg3EC2](https://discord.gg/Nu64rg3EC2 "https://discord.gg/Nu64rg3EC2")
diff --git a/_posts/2022-06-18-how-to-nominate-someone-for-testeroftheday.md b/_posts/2022-06-18-how-to-nominate-someone-for-testeroftheday.md
new file mode 100644
index 0000000000000..29f94e2ec0579
--- /dev/null
+++ b/_posts/2022-06-18-how-to-nominate-someone-for-testeroftheday.md
@@ -0,0 +1,41 @@
+---
+title: 'How to nominate someone for #TesterOfTheDay'
+tags:
+ - community
+ - tester of the day
+date: '2022-06-18 00:00:00 +0100'
+categories:
+ - Tester of The Day
+redirect_from:
+ - /how-to-nominate-someone-for-testeroftheday/
+---
+
+[Tester of The Day](https://www.testeroftheday.com/) is a daily celebration of the excellent contributions made to the [testing community](https://www.dowen.me.uk/posts/interviews-with-testers/). Winners are announced on Twitter and LinkedIn using the hash-tag #TesterOfTheday. On Twitter the [@TesterOfTheDay](https://twitter.com/testeroftheday) bot also re-tweets that hashtag.
+
+Winners are also listed on the Tester of The Day website, in the [Testers Hall of Fame](https://www.testeroftheday.com/)!
+
+Started in 2020, the award is now in the 3rd year. You can view the complete 2020 and 2021 hall of fames at [https://2020.testeroftheday.com/](https://2020.testeroftheday.com/ "https://2020.testeroftheday.com/") and [https://2021.testeroftheday.com/](https://2021.testeroftheday.com/ "https://2021.testeroftheday.com/").
+
+
+
+## Who can be nominated
+
+Quality is everyone's responsibility, and the craft of testing can be practiced by anyone, regardless of their designated role in their current job. So naturally anyone can be nominated to win Tester of The Day.
+
+Past winners have made impactful contributions, at their place of work, to the wider testing community or personally to the person who nominated them. All these contributions are valuable and deserve celebrating!
+
+## What to include in your nomination
+
+Please include Twitter and LinkedIn social media links for yourself and the person you're nominating if at all possible. One of the benefits to the winner is the opportunity to gain followers, and for the community that they can discover great people to follow!
+
+For the Nomination text, please give some insight into how the nominee made an impact on you, their teammates or the wider community. This is your chance to celebrate their success, as the nomination text is used on the Hall of Fame, Twitter and Linkedin.
+
+Note, if the nomination text is too long, it will be truncated on Twitter, I will do my best to cut the text down in a way that makes sense.
+
+## Fill out the form
+
+The key form to make a nomination can be found here:
+
+[https://testeroftheday.com/forms/nominate](https://testeroftheday.com/forms/nominate "https://testeroftheday.com/forms/nominate")
+
+Please fill out all the fields you can, including your own details so I can credit you for your nomination!
diff --git a/_posts/2022-06-20-why-i-m-excited-for-testbash-world.md b/_posts/2022-06-20-why-i-m-excited-for-testbash-world.md
new file mode 100644
index 0000000000000..f726fef98d5be
--- /dev/null
+++ b/_posts/2022-06-20-why-i-m-excited-for-testbash-world.md
@@ -0,0 +1,50 @@
+---
+title: Why I'm excited for TestBash World
+tags:
+ - community
+ - conference
+ - minastry of testing
+date: '2022-06-20 00:00:00 +0100'
+categories:
+ - Conferences
+redirect_from:
+ - /why-i-m-excited-for-testbash-world/
+---
+
+I'm getting really excited now for [TestBash World](https://www.ministryoftesting.com/events/testbash-world-2022)! Let me tell you why.
+
+## What is TestBash World?
+
+A free online Software Testing conference, that will go for 24 full hours run by [The Ministry of Testing](https://www.ministryoftesting.com/), TestBash World is set to be, huge!
+
+When? June 22nd 22:00 BST (GMT+1) for 24 hours
+
+Where? Online, go sign up now it's free:
+
+[https://www.ministryoftesting.com/events/testbash-world-2022](https://www.ministryoftesting.com/events/testbash-world-2022 "https://www.ministryoftesting.com/events/testbash-world-2022")
+
+## TestBash online events are awesome
+
+I've been two some previous TestBash events online, such as TestBash Home 2020 and 2021 and recently TestBash Careers. They are packed full of excellent talks, a mix of new speakers and famous names.
+
+Most importantly, the atmosfear in the chat running alongside really makes it a nice place to be while you lean. Talks are recorded, and get made available a week or two after the events. But the real magic is watching live, if you can!
+
+## Great line-up
+
+There are some many great sessions in the 24 hour line up!
+
+I'm really looking forward to the event kicking off with the amazing [Melissa Fisher](https://twitter.com/fishouthebox) with a talk titled "Using Brain Science to Build Better Products".
+
+Other topics early in the line-up include [Francis Ho](https://twitter.com/TheFrancisHo) on Whole Team Owning Quality and #TesterOfTheDay winner, [Brittany Stewart](https://twitter.com/Brittish_Beauty) on Shifting Left.
+
+## I'm taking part!
+
+As well as looking forward to attending TestBash Home, I'm also volunteering for the first few hours of the day. I'll be posting relevant links into the chat, and copying questions over to The Club.
+
+I'm also taking part in a panel discussion on how to get more involved with the MoT Community. I'm super excited for this session, lead by [Bart Knaack](https://twitter.com/Btknaack) I will be discussing alongside two amazing humans, [Louise Gibbs](https://twitter.com/Louise_J_Gibbs) and [Karen Todd](https://twitter.com/KarenTestsStuff)!
+
+## You can get on stage, for 99 seconds
+
+If you've ever been to a TestBash event, you will know about the famous 99 second talks. Your chance to get up on stage, and talk about any topic you like for 99 seconds.
+
+I've done 99s talks at a few TestBash online events, and I love it. I cannot recommend it enough. So start thinking now, what will you talk about?
diff --git a/_posts/2022-07-10-tester-of-the-day-winner.md b/_posts/2022-07-10-tester-of-the-day-winner.md
new file mode 100644
index 0000000000000..dae565a3434fd
--- /dev/null
+++ b/_posts/2022-07-10-tester-of-the-day-winner.md
@@ -0,0 +1,40 @@
+---
+title: Tester of The Day Winner
+tags:
+ - recognition
+ - tester of the day
+date: '2022-07-10 00:00:00 +0100'
+categories:
+ - Tester of The Day
+redirect_from:
+ - /tester-of-the-day-winner/
+---
+
+So, you've just found out you've won [#TesterOfTheDay](https://www.testeroftheday.com/)? Congratulations!
+
+
+
+Photo by Nataliya Vaitkevich: [https://www.pexels.com/photo/golden-statuette-and-stars-on-yellow-background-6532373/](https://www.pexels.com/photo/golden-statuette-and-stars-on-yellow-background-6532373/ "https://www.pexels.com/photo/golden-statuette-and-stars-on-yellow-background-6532373/")
+
+## What does it mean?
+
+It means someone has recognised your contribution to the world of Software Testing. This may have been because of work you did to help the person who nominated you directly, their team or your contributions to the software testing community. Whatever you did, thank you!
+
+Your win will have been announced on Twitter and LinkedIn using the hashtag #TesterOfTheDay. On Twitter these are re-tweeted by [@TesterOfTheDay](https://twitter.com/TesterOfTheDay) bot.
+
+You will also be entered into the Testing Hall of Fame website, at [https://www.testeroftheday.com/](https://www.testeroftheday.com/ "https://www.testeroftheday.com/").
+
+## What do do next?
+
+Bask in the glory of victory! After that there are two excellent, and optional things you can do!
+
+1. Complete [this form](https://testeroftheday.com/forms/interview), to take part in the Winners Interviews series. If you do so, your interview will appear on [https://interviews.testeroftheday.com/](https://interviews.testeroftheday.com/ "https://interviews.testeroftheday.com/"), alongside interviews with other winners.
+2. Next, if you know another excellent human being who deserves to win, nominate them! Simply [fill out this form](https://testeroftheday.com/forms/nominate), or [find out more here.](https://www.dowen.me.uk/posts/how-to-nominate-someone-for-testeroftheday/)
+
+## Not won yet?
+
+Sounds great being a winner for Tester of The Day! and it is!
+
+Not had your chance to shine yet? Fear not, the best way to win is by letting those you work with, in your team, your company or in your testing community how to make a nomination. Then do awesome stuff, and hope they take the hint. You can even go one step further, and nominate them first, they make share the love and nominate you right back!
+
+You must know how to nominate someone by now? right if not, see this post: [https://www.dowen.me.uk/posts/how-to-nominate-someone-for-testeroftheday/](https://www.dowen.me.uk/posts/how-to-nominate-someone-for-testeroftheday/ "https://www.dowen.me.uk/posts/how-to-nominate-someone-for-testeroftheday/")
diff --git a/_posts/2022-07-24-the-7th-modern-testing-principle.md b/_posts/2022-07-24-the-7th-modern-testing-principle.md
new file mode 100644
index 0000000000000..de03e90f03aa3
--- /dev/null
+++ b/_posts/2022-07-24-the-7th-modern-testing-principle.md
@@ -0,0 +1,50 @@
+---
+title: The 7th Principle of Modern Testing
+tags:
+ - testing
+date: '2022-07-24 00:00:00 +0100'
+categories:
+ - Testing
+redirect_from:
+ - /the-7th-modern-testing-principle/
+---
+
+[Huib Schoots](https://twitter.com/huibschoots) recently Tweeted from [RTC - Romanian Testing Conference](https://twitter.com/RomaniaTesting), about a talk by [Conor Fitzgerald](https://twitter.com/conorfi), where he spoke about the Modern Testing Principles.
+
+
+
+From his Tweet, I see that Huib doesn't agree with Principle 7. As you might be able to see from the slide, Conor has abbreviated the principles, so let's remind ourselves of Principle 7 in full:
+
+_"7. We expand testing abilities and knowhow across the team; understanding that this may reduce (or eliminate) the need for a dedicated testing specialist." -_ [_AB Testing_](https://www.moderntesting.org/)
+
+This is the 7th of the 7 Modern Testing Principles, as created by AB Testing. If you're interested, go read the full list, it's short and consumable and you can better make up your own opinions. See: [https://www.moderntesting.org/](https://www.moderntesting.org/ "https://www.moderntesting.org/").
+
+Full disclosure, I was not at the conference and I didn't get to watch Conor's presentation. So my reactions are based on the Tweet, and the original principles.
+
+## My take on Principle 7
+
+I have my own opinions on this, from my own experience, context and opinions. And [I shared these in the thread](https://twitter.com/FullSnackTester/status/1550931166148034560). Here is my response:
+
+1\. Testing software, the activity is a combination of theory that can be taught, and practice that can be done.
+
+2\. Those skills take time, effort and mental capacity to get good at. It's an investment not everyone is willing to, or has capacity to do.
+
+3\. Though ensemble testing, and other collaborative ways of working, anyone involved in using of creating software can usefully and meaningfully contribute to the testing effort. In doing so, they may pick up some theory and skills in testing.
+
+4\. Having a person who is able to focus on the role of Testing, had a good opportunity to learn and practice the craft of testing in a deeper way, faster, then someone who splits their capacity between Testing and other activities. Testers can be efficient force multipliers
+
+5\. Having experience in other part of product development can give a dedicated Tester skills that are advantageous to their Testing work. Be this product management, software development, design, operations, security, infrastructure, support or other roles.
+
+6\. By working collaboratively, we can get some of the advantages of knowing testing deeply, software development and other roles deeply and combine them, without one person needing to already know all these things. Accelerating access to the benefit of this wide knowledge.
+
+***
+
+I clearly wasn't as far away from the original intention of Principle 7 as I thought I might have been. Not least because [Alan Page](https://twitter.com/alanpage) appears to agree with me, [in this Tweet](https://twitter.com/alanpage/status/1550942384845770752?s=20&t=d9zDpJ1VB0ev-tpQD8sOgQ):
+
+
+
+Reading some other responses to the thread, there is clearly a bunch of different opinions around if Developers can test, where there was some commonality and agreement it was that:
+
+1. Deep and skilful testing takes time and dedication to learn
+2. Anyone able and willing to put in that time and dedication could learn how to test deeply
+3. In order for anyone to be successful in becoming a skilful testers, they must have the right support, a desire and capacity to do so
diff --git a/_posts/2022-08-14-the-future-of-software-testing.md b/_posts/2022-08-14-the-future-of-software-testing.md
new file mode 100644
index 0000000000000..a39e0ede717ff
--- /dev/null
+++ b/_posts/2022-08-14-the-future-of-software-testing.md
@@ -0,0 +1,68 @@
+---
+title: The Future of Software Testing
+tags:
+ - testing
+ - ministry of testing
+ - bloggers club
+date: '2022-08-14 00:00:00 +0100'
+categories:
+ - Testing
+redirect_from:
+ - /the-future-of-software-testing/
+---
+
+This post is part of the Ministry of Testing Bloggers Club, the August topic is "[The Future Of The Tester Role](https://club.ministryoftesting.com/t/bloggers-club-august-2022-the-future-of-the-tester-role/61680?u=fullsnacktester)".
+
+I will give you a brief insight into my Past and Present as a Software Tester, and make some predictions for my future. Will this translate into the future for others? I guess we will have to wait and see.
+
+## The Past
+
+Like many, I started my career in a team of Testers, in my case the System 1 test team at Citrix. Over the course of my 5 years at Citrix, we transition from a central team with director level line-management to a distributed team.
+
+We still had a Test Manager, who was my line manager. What did change is that I moved from working in a central team, to working directly with a team, alongside developers. We started to adopt Agile ceremonies, such as stand-ups, backlog grooming, story point poker estimations, yes my friends, we did an "Agile Transformation". Fun times.
+
+While I gained in closeness to the Developers, I also lost out, as previously I had been able to do a lot of pair working in the test team, now I was a lone Tester among Devs.
+
+After Citrix, I had a number of other roles and titles. I did a stint as a Quality Manager, where I managed people and testing at a small consultancy. I picked up a year and half experience almost exclusively writing test automation, again in a team with devs, this time they paired with me, I leaned a lot but I wasn't able to influence meaningful change.
+
+## The Present
+
+Presently, I am a Quality Engineer at Ada Health. I'm working in a backend team, alongside developers and another tester. I also get to get involved in wider projects across the group, and the org.
+
+I'm finding it a very challenging, and fulfilling learning experience having been removed from some of the constraints that had been holding me back in past roles. I am no longer tied down to a central team, nor is my scope limited to my direct team. I have the opportunity to influence at multiple levels and I'm encouraged and supported to contribute to the wider community.
+
+I'm also thrilled to be able to learn from an amazing group of fellow Quality Engineers at Ada, their joint level of experience is exceptional and they share knowledge gladly.
+
+I'm well aware it's a privilege to work in such a role, and I hope more and more people get the opportunity to move into such roles if they want them in the future.
+
+## The Future, for me
+
+So, what is my future looking like? Well, currently I have a very broad range of skills, some deep and some shallow. And I want to grow in multiple dimensions, I want to pick up more specialisations, such as Security, and go deeper with some of my shallow skills like Performance testing.
+
+Ultimately, the more I mature into my career the more I realise it's all about the people. The people I work with, and support directly in my role. The people who use the software that my team creates, internally, and then people who ultimately use our products.
+
+As such, my main growth area for the future, is to further focused on my impact on people, using my technical skills as a foundation to make this possible.
+
+What might this look like?
+
+* Deeper exploration, with more concise summaries and debriefs
+* Focus on definitive, actionable information discovery
+* Teaching and Coaching others, so they can make use of testing skills themselves
+* Testing beyond code, working closer with product to make sure we build the right thing
+
+## The Future, for the role
+
+My predictions for the role of the Software Tester in the future, let's say 5-10 years scale:
+
+* Tooling and frameworks will continue to reduce the need for some parts of testing
+* Developers will be expected to pick up more testing skills and do more testing
+* Experienced Testers will be expected to work across multiple teams
+* As test automation gets easier with better tooling, and testers get more experienced, the lines between Tester and Dev blur further
+* Exploratory Testing grows in popularity as a compliment to automation, and scripted step-based testing is limited in regulated industries and those orgs who traditionally move slower
+* Due to the cyclical nature of the industry, centralised test teams make comeback
+
+## When is a Tester, Not a Tester
+
+If you enjoyed this post, you might like another one I wrote a little while back:
+
+[https://www.dowen.me.uk/posts/when-is-a-tester-not-a-tester/](https://www.dowen.me.uk/posts/when-is-a-tester-not-a-tester/ "https://www.dowen.me.uk/posts/when-is-a-tester-not-a-tester/")
diff --git a/_posts/2022-08-15-how-to-test-anything-in-5-steps.md b/_posts/2022-08-15-how-to-test-anything-in-5-steps.md
new file mode 100644
index 0000000000000..f9c6263dc3c41
--- /dev/null
+++ b/_posts/2022-08-15-how-to-test-anything-in-5-steps.md
@@ -0,0 +1,85 @@
+---
+title: How to test anything in 5 steps
+tags:
+ - testing
+ - quality
+ - process
+date: '2022-08-15 00:00:00 +0100'
+categories:
+ - Testing
+redirect_from:
+ - /how-to-test-anything-in-5-steps/
+---
+
+How to test anything:
+
+1. **Capture** what you know so far and build a model
+2. **Review** the model with others, identify what is important
+3. **Explore** by running experiments to learn what you don't know
+4. **Update** the model based on what you know now
+5. **Repeat** this cycle until you stop finding useful information
+
+## Capture
+
+We all build models of the things that we test, these might be mental models we keep in our head, informal models such as mind-maps or more formal models such as state transition diagrams.
+
+Build models that help describe the behaviour of the system you are testing, and capture the information in a way you can easily share and review with others.
+
+## Review
+
+Reviewing work with others is important for a number of reasons, mainly because by updating it with input from multiple people we can reduce bias from what we know ourselves and get closer to a truth that is useful.
+
+You can use questions get useful feedback on your model, such as:
+
+* What is missing?
+* What isn't correct?
+* What is important?
+* Does this feel right?
+* Does this sound right?
+* Does it add up?
+
+## Explore
+
+Now you've got an iteration of your model, you have some ideas about how the system should behave so it's time to test those ideas against the current reality of the system.
+
+The goal here is to explore to learn useful information, where to focus is going to depend on your context. Here are some things you might want to learn:
+
+* If reviewers didn't agree, find out how the system behaves now?
+* You identified behaviours that are important, do they indeed behave as you expect?
+
+Your model will have gaps, open questions, fill those knowledge gaps with exploration. You can run your exploratory testing in many ways, use your current model as a guide about what is important, and how you think the system should behave.
+
+It's very important you take good notes as you explore, so you can discuss your findings with your team and use the outcome of that conversation to update your model.
+
+## Update
+
+Reflect on what you've learned during this iteration and make sure to update your model based on what you know now. Maybe you found surprises during your exploration, and now you know more, put it in the model.
+
+You will need to make choices as a team if a surprise you find is a bug, or intended behaviour that you haven't modelled yet, so keep them involved as you go.
+
+## Repeat
+
+This process is a cycle, that you can continue to repeat as you continue to test the system.
+
+On each iteration, you will learn more, if you stop learning useful information that your team can use to make better choices, you're done for now.
+
+When the next change comes along, you can build on existing models and create new ones as appropriate. It need not be a single model that you build, use whatever is appropriate for this iteration of the cycle.
+
+## How others test anything
+
+My esteemed colleague [James Thomas](https://twitter.com/qahiccupps) as his own take on how to test anything, these are complementary to what I've said above and less cyclical.
+
+You can read find out more about James's approach:
+
+[https://qahiccupps.blogspot.com/2020/05/how-to-test-anything.html](https://qahiccupps.blogspot.com/2020/05/how-to-test-anything.html "https://qahiccupps.blogspot.com/2020/05/how-to-test-anything.html")
+
+[https://youtu.be/Lj6RjWA-arI](https://youtu.be/Lj6RjWA-arI "https://youtu.be/Lj6RjWA-arI") \[In 3 minutes\]
+
+## Graphical Test Planning
+
+My cyclical approach to testing is based on the **Capture**, **Review** **Update** from Graphical Test Planning (GTP), developed by Hardeep Sharma from Citrix Systems, many years ago.
+
+You can learn a little more about GTP here:
+[https://sites.google.com/site/gtpfortest/](https://sites.google.com/site/gtpfortest/ "https://sites.google.com/site/gtpfortest/")
+
+Graphical Test Planning describes a way to model system behaviour in Structured Relationship Diagrams, and how to write Test Case Diagrams that model how to test single observable behaviours.
diff --git a/_posts/2022-09-18-how-to-make-a-start-with-test-automation.md b/_posts/2022-09-18-how-to-make-a-start-with-test-automation.md
new file mode 100644
index 0000000000000..381726c24f861
--- /dev/null
+++ b/_posts/2022-09-18-how-to-make-a-start-with-test-automation.md
@@ -0,0 +1,89 @@
+---
+title: How to make a start with Test Automation
+tags:
+ - automation
+ - testing
+ - introduction
+date: '2022-09-18 00:00:00 +0100'
+categories:
+ - Automation
+redirect_from:
+ - /how-to-make-a-start-with-test-automation/
+---
+
+Sometimes, people ask me how to make a start in Test Automation, or as you might correctly hear it called automated checks. While there is no one answer, because of course it depends, I can pose some questions for you to ask yourself and point you to some great resources, so lets goooo!
+
+
+
+Photo by Tara Winstead: [https://www.pexels.com/photo/robot-pointing-on-a-wall-8386440/](https://www.pexels.com/photo/robot-pointing-on-a-wall-8386440/ "https://www.pexels.com/photo/robot-pointing-on-a-wall-8386440/")
+
+## Do I need to learn to code to build automation?
+
+No, but yes, well it depends!
+
+There are many tools that exist that do not require explicit programming language knowledge to build automation. Most of these tools do benefit from knowledge of how [**control flow**](https://developer.mozilla.org/en-US/docs/Glossary/Control_flow) and [**conditions**]( "https://developer.mozilla.org/en-US/docs/Glossary/Conditional")work, even if they don't need you to understand the syntax for a language.
+
+Concepts like [**if and else statements**](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Control_flow_and_error_handling#if...else_statement) and [**loops** ](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Loops_and_iteration)are pretty much unavoidable, and if you want to automate web pages you're going to need some idea about [**locators**](https://www.selenium.dev/documentation/webdriver/elements/finders/), and it wouldn't hurt to understand the [**Document Object Model**](https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Introduction) (DOM).
+
+Learning to code can also bring a bunch of other benefits, like better understanding the software you're testing and being able to have a different level of conversation with developers. So while learning to code is not a requirement for being a Tester or automating checks, I highly recommend giving it a go.
+
+## Transition from manual to automation
+
+If you're already working in Software Testing, but haven't yet written any automation and want to make a start, there are a few questions to ask yourself:
+
+1. Are you looking to skill up to add automation as part of your current role at your current employer?
+2. Are you looking to take on a new role, at your current employer or elsewhere?
+3. Do you already know how to code, and are simply looking to gain experience in new tool or framework to start your journey?
+
+Of course, as well as your desire, you will need the opportunities, if you don't already know what is available with your current employer it might be worth finding out by asking around.
+
+If you've never written code, then instead of learning test automation right off the bat, you might want to pick a language and learn the fundamentals first. There are many free, and paid ways to learn how to code.
+
+Some great places to start:
+
+* [https://www.freecodecamp.org](https://www.freecodecamp.org/ "https://www.freecodecamp.org/")
+* [https://www.codecademy.com/](https://www.codecademy.com/ "https://www.codecademy.com/")
+* [https://www.w3schools.com/](https://www.w3schools.com/ "https://www.w3schools.com/")
+
+Finally, if you have the opportunity to pair with a developer or existing test automation engineer, take it! If you don't already have this opportunity, seek it out. Learning by doing, with the help of others is super valuable and will speed up your learning no end.
+
+## Use automation to aid testing
+
+There is no need to limit your use of automation and tools to a suite of automated checks that you might typically consider test automation. In fact if you do, you are probably doing automation and testing a disservice.
+
+There are multiple proponents of using code and tools to support exploratory testing in different ways, one of them who I am lucky enough to work with presently is James Thomas. You can learn more about how James [**Explores with Automation**](https://www.ministryoftesting.com/dojo/series/meetups/lessons/exploring-with-automation-with-james-thomas).
+
+A champion on using code in testing is [**Maaret Pyhäjärvi**](https://twitter.com/maaretp), just one fine example of her work is [**Exploratory Testing on Computer Interfaces (APIs)**](https://youtu.be/CjS3wVXQt34), a Keynote from API Conference in 2019.
+
+And of course, there is [**Mark Winteringham**](https://twitter.com/2bittester) and [**Richard Bradshaw**](https://twitter.com/FriendlyTester) who coined the term [**Automation in Testing**](https://automationintesting.com/), and have produced fantastic courses, workshops and tools for learning how to get the best out of Automation, well beyond automated checks.
+
+## Best language to learn for automation
+
+So, where to start? Java, Python, JavaScript, C#? Tell me damnit!
+
+While I can totally understand why you would want a general answer as to what language to use, there isn't one definitive answer.
+
+So, I will ask you to consider the following:
+
+1. What do you want to learn first? If you haven't got any experience in any language, go spend some time looking at what is available and if any of them make good sense to you. If you already know a bit of something , start there!
+2. Are you looking to grow yourself within your current role in your current job? If so, speak to your team, see what would be useful for you to learn next
+3. If you're looking to grow skills to pick up a new role, look at what is popular in your target area of the world. The popularity of one language over another might be different for the places you are considering working for. Try and find people working in the geographical location you're targeting, recruiters or hiring managers, and ask them.
+4. Careers are long, if you spend time learning the fundamentals of coding, testing, and automating checks using code then you can apply much of those skills across multiple tools and languages. Yes, there is a learning curve to picking up a new thing, but it gets easier with every new one you try.
+
+## Resources for learning
+
+One of the absolute best resources for learning Test Automation in my experience is the [**Test Automation University**](https://testautomationu.applitools.com/). Not only is it free, but the content is written by and for testers, so it's way more relevant then the odd testing focused chapter in a code course otherwise written for developers. The are even some introductions into coding on there, for example this course on [**Java Programming**](https://testautomationu.applitools.com/java-programming-course/) by [**Angie Jones**](https://twitter.com/techgirl1908) and this [**Introduction to JavaScript**](https://testautomationu.applitools.com/javascript-tutorial/) by **Mark Thompson.** There is even a whole learning path for [**Codeless automation**](https://testautomationu.applitools.com/learningpaths.html?id=codeless-path).
+
+If you don't have a background in computer science, you may also get a kick out of the [**Base.cs podcast**](https://www.codenewbie.org/basecs). In each episode the co-hosts [**Vaidehi Joshi**](https://twitter.com/vaidehijoshi) and [**Saron Yitbarek**](https://twitter.com/saronyitbarek) introduce and discuss a topic in an approachable way, with great anecdotes, many of them food related and you know I dig that!
+
+## Practice apps and challenges
+
+The [**Restful Booker**](https://automationintesting.online/#/) is a great practice app for exploration or automation. It's a REST API and a frontend for a functional Bed & Breakfast, Shady Meadows.
+
+The [**Evil Tester,**](https://www.eviltester.com/) [**Alan Richardson**](https://twitter.com/eviltester) has created a series of [**API Challenges**](https://www.eviltester.com/page/tools/apichallenges/) that help you explore many of the aspects ot APIs that you might want to test, and therefore automate. While this isn't strictly an automation challenge, you could turn it into one by writing code to beat the challenge! I've started to give this a go myself, but it's work in progress.
+
+Want more? There is a great [**post on The Club **](https://club.ministryoftesting.com/t/products-and-sites-to-practice-testing-on/1242), where loads of people have shared products and sites they have used to practice testing on. You can even go add your own!
+
+## Just start
+
+Finally, It's way better to [**start**](https://www.dowen.me.uk/posts/Automation-Just-do-it!/), then spend too much time worrying about where to start. You can also change your mind and try something else later if you don't like where you end up! I'm looking forward to hearing how your automation journey progresses, make sure to hit me up on Twitter, [**@FullsnackTester**](https://twitter.com/FullSnackTester), and let me know!
diff --git a/_posts/2022-10-01-who-is-ben-dowen-the-full-snack-tester.md b/_posts/2022-10-01-who-is-ben-dowen-the-full-snack-tester.md
new file mode 100644
index 0000000000000..971944ed16e0d
--- /dev/null
+++ b/_posts/2022-10-01-who-is-ben-dowen-the-full-snack-tester.md
@@ -0,0 +1,45 @@
+---
+title: 'Who is Ben Dowen, The Full Snack Tester?'
+tags:
+ - quality
+ - bio
+ - ben dowen
+ - full snack tester
+date: '2022-10-01 00:00:00 +0100'
+categories:
+ - About Ben
+redirect_from:
+ - /who-is-ben-dowen-the-full-snack-tester/
+---
+
+Find out a bit more about Ben Dowen, the Full Snack Tester.
+
+
+
+## Celebrating the Community of Software Testing
+
+I celebrate those who contribute to the craft and community of software testing. I encourage a collaborative, whole team approach to testing and strongly believe everyone involved in building software should contribute to testing it.
+
+One of the ways I do this, is by running [Tester of The Day](https://testeroftheday.com/ "Tester of The Day"), a regular celebration of people who contribute to the craft and community of Software Testing. You don't need to be in a testing role to win Tester of The Day! Indeed many winners in the hall of fame hold roles in development and product areas.
+
+You can find out more about Software Testing communities [here](https://www.dowen.me.uk/posts/software-testing-community/).
+
+## Technical, full stack, background
+
+I have a technical background, built up throughout my career that enables me to test systems at many different levels. I explore systems from the infrastructure, where software lives, backend services, APIs, and persistence layers (database), right the way up to where users interact with the end product.
+
+You can read more about my thoughts about how this applies to test automation in my post [Anatomy of test automation](https://dev.to/dowenb/anatomy-of-test-automation-e9o).
+
+## System and team boundaries
+
+In my experience, I find the most impactful bugs are typically found at system and team boundaries. I find the integrations and hand offs are prone to miscommunication, and unnecessary friction.
+
+I believe strongly that [building software is a team sport](https://www.dowen.me.uk/posts/creating-software-is-a-team-sport/), and experienced software quality and testing practitioners can play a very valuable role as they contribute to a teams overall success in shipping great software.
+
+## Thoughts on Software Quality
+
+I understand quality as the combination of usefulness, goodness and correctness, observed from a perspective at a point in time. I also find the definition of quality as the absence of unnecessary friction useful, although I'm yet to combine these two definitions.
+
+Find out more about what quality means to me [here](https://www.dowen.me.uk/posts/what-does-quality-mean-to-me/ "What quality means to me blog post").
+
+Over Photo by Mo Abrahim: [https://www.pexels.com/photo/popcorn-in-ceramic-bowl-3537844/](https://www.pexels.com/photo/popcorn-in-ceramic-bowl-3537844/ "https://www.pexels.com/photo/popcorn-in-ceramic-bowl-3537844/")
diff --git a/_posts/2022-10-05-ten-years-in-testing-ask-me-anything.md b/_posts/2022-10-05-ten-years-in-testing-ask-me-anything.md
new file mode 100644
index 0000000000000..78e0ac36682a2
--- /dev/null
+++ b/_posts/2022-10-05-ten-years-in-testing-ask-me-anything.md
@@ -0,0 +1,159 @@
+---
+title: 'Ten years in testing, ask me anything!'
+tags:
+ - ama
+ - questions
+ - about
+date: '2022-10-06 00:00:00 +0100'
+categories:
+ - About Ben
+redirect_from:
+ - /ten-years-in-testing-ask-me-anything/
+---
+
+July 2012, now a little over ten years ago I started as a Software Test Engineer at Citrix Systems, in the model village of Cambourne in Cambridgeshire, UK.
+
+Since then, I've had the pleasure of testing a lot of great software, covering a huge range of technologies and business domains.
+
+This summer, [I invited you to ask me anything](https://twitter.com/FullSnackTester/status/1543175591582732288), and you did!
+
+I didn't answer those questions at the time, and then [I asked you to AMA again](https://twitter.com/FullSnackTester/status/1547878296276201475), and that time I answered directly on Twitter.
+
+So, finally, after months of delay, here are my responses to your original questions.
+
+
+
+Photo by Pixabay: [https://www.pexels.com/photo/questions-answers-signage-208494/](https://www.pexels.com/photo/questions-answers-signage-208494/ "https://www.pexels.com/photo/questions-answers-signage-208494/")
+
+## Question 1
+
+[
+𝑫𝒂𝒏 𝑨𝒔𝒉𝒃𝒚, @DanAshby04](https://twitter.com/DanAshby04)
+
+> Question: _Have you ever felt the urge to move out of testing?_
+
+Answer: Yes. I've been tempted a few times to focus on a more hands-on developer role, or a more product focused Product Owner type role. Fun fact, I also once applied for a role as a Scrum Master, but didn't even get an interview.
+
+The main reason for considering these alternative roles, in both directions, is to be able to more directly influence positive outcomes for users, while still supporting and promoting testing and quality.
+
+For now, I can satisfy both of these desires by pushing the boundaries of my role as a Quality Engineer.
+
+> Question: Do you think you'll still be testing in 10 years from now?
+
+Will I still be testing software? Yes, 100%. Will my role still be "Software Tester"? I doubt it, and in some ways it never has, but always will be.
+
+See my post [When is a Tester not a Tester?](https://www.dowen.me.uk/posts/posts/when-is-a-tester-not-a-tester/)
+
+> Question: What's been your biggest "high" in testing in your 10 year career so far?
+
+Winner a "Make it happen" award for my work on Customer Empathy at Citrix was a pretty huge high! Putting engineers in front of real customers was a thrill.
+
+A major highlight of that journey was supporting a customer who I had brought into the office, to do a presentation at a Citrix user group reflecting back their experience, and encouraging others to get involved.
+
+> Question: What did you do before being a tester, and how has it helped you in testing?
+
+Directly before being a Tester, I completed a degree at University in "Forensic and Security Technologies". There are so many things from my time at university that help me in Testing.
+
+A 3 highlights include:
+
+* My year as an elected officer in the students union, that taught me about advocacy and representation
+* My modules on Business Analysis and Design, where I learned about gathering and analysing requirements
+* Principles of forensic computing, where I learned about the concept of documenting things in a way that another competent person can reproduce my work
+
+Going way back to college, when I was interning in the IT Department, one very big lesson that has helped me in my whole career in technology, especially testing, is this one thing:
+
+_"Computers don't have problems, people have problems. When solving a problem, remember to think about the person before you think about the computer." - L. Coxall_
+
+## Question 2
+
+[Karen Tests Stuff, @KarenTestsStuff](https://twitter.com/KarenTestsStuff)
+
+> Question: What piece of advice would have saved you the most heartache, had you known it earlier in your career?
+
+Answer: I am technical, and when developers called me non-technical, what they might really meant was "I don't want to be challenged about this bit, because I'm not confident about it myself".
+
+## Question 3
+
+[James Thomas, @qahiccupps](https://twitter.com/qahiccupps)
+
+> Question: Most significant perspective change.
+
+Answer: My perspective on why I should test software has changed from:
+Then: "to find defects, before the customers do",
+
+Now: "to discover information, to support better choices and build a better product"
+
+> Question: Stuff you did that you wouldn't do again
+
+Answer: OK, I think this calls for a list, no particular order:
+
+* Write BDD Given, When, Then style test cases, that are only ever executed by a human
+* Manage a team of testers, while also still having full-time duty as a tester
+* Spend 6 months modelling and writing tests, before I got my hands on the feature
+* Work in the Betting and Gambling space, I want to focus on domains with positive outcomes for users
+* Wait until I'm angry and frustrated for a prolonged period of time before I start looking for another job
+
+> Question: Most useful defaults based on your experience
+
+Answer: Another list:
+
+* Test in public, by this I mean tell the team what I'm testing and when, and share my notes openly
+* Favor pairing and group working, over doing it myself and working in isolation
+
+> Question: Why you stayed in testing
+
+Answer:
+
+* Interesting, challenging, and varied work
+* The Testing Community give me a lot of energy
+* I'm still learning new things, ten years in
+* I strongly believe in making software better for people
+
+## Question 4
+
+[Adrian Yorke, @adrian_yorke](https://twitter.com/adrian_yorke)
+
+> Question: What advice would you give your 10 years younger self?
+
+Answer: You don't need to put in extra hours at work to impress your manager to progress your career. Instead, make the most of the time you spend at work and look at ways to avoid waste.
+
+## Question 5
+
+[Richard Forjoe 费乔](https://twitter.com/rforjoe), [@rforjoe](https://twitter.com/rforjoe)
+
+Replying to [@FullSnackTester](https://twitter.com/FullSnackTester)
+
+> Question: What has changed / improved in the industry during that period?
+
+Answer: Two complementary things, the raise of good automation tools and frameworks that are easy to pick up and use, and the rise of the Exploratory Testing movement, where investigative testing is valued as complementary to automation.
+
+> How have you improved your testing craft?
+
+Answer: In 10 years? I've learned everything I know! Most recently, this year, I've focused on growing how I do Exploratory Testing, and how I collaborate and pair with others to do testing together.
+
+> Question: Where do you feel you’ve added the most value to companies & yourself ?
+
+Answer: To companies, I like to think that my value can be measured in both better outcomes for users, and increased enthusiasm for testing in the teams I've worked with.
+
+Value for myself? I've become much more confident, technically and in my communication with others. I've grown a real love for the craft of testing, and gained a huge online community that I value deeply.
+
+> Question: Top 2 mental health challenges you’ve overcome/still deal with, testing related?
+
+Answer:
+
+1. I want to change the world, by doing all the things and making colossal impact. And I constantly have to fight my urge to do all the things, otherwise I lose myself to hours of extra work, mostly in my own time, investing in projects I'll never finish. And then I carry the mental load of that unfinished work with me. I need to give myself a break more often, and learn to disconnect.
+2. I bring my work frustration and stress back into my family life, and my family suffer for it. This puts strain on my relationship, yes there is a theme here!
+
+## Question 6
+
+[𓂆 Aya Mohamed Fouad](https://twitter.com/AyaMFouad)
+
+[@AyaMFouad](https://twitter.com/AyaMFouad)
+
+Replying to [@FullSnackTester](https://twitter.com/FullSnackTester)
+
+> Question: Did you ever have to deal with imposter syndrome? If yes, how do you handle that?
+
+Answer: A few times, I've found myself working with (at work, or in the community) absolute legends from the testing world. And I've sometimes fallen into the trap of comparing myself to others, instead of the me from yesterday. And this has on occasion knocked my confidence and distracted me.
+
+I've thankfully never suffered as badly with imposter syndrome as I know some others have, nor can I pinpoint one thing I've done to track and handle it. While I would like to think I handled it by being kind to myself, and appreciating how far I've come and what I've accomplished, in reality I probably rather pushed myself to try and emulate the success of others, sometimes more successfully than others.
diff --git a/_posts/2022-10-23-dark-new-look-and-feel.md b/_posts/2022-10-23-dark-new-look-and-feel.md
new file mode 100644
index 0000000000000..f348b16a1bc72
--- /dev/null
+++ b/_posts/2022-10-23-dark-new-look-and-feel.md
@@ -0,0 +1,34 @@
+---
+layout: post
+title: Dark new look and feel
+description: 'Announcing a new look and feel to the website, now with dark mode!'
+image:
+ path: /uploads/pexels-junior-teixeira-2047905.jpg
+ width: 1000
+ height: 420
+ alt: Laptop with dark background
+category: Announcement
+tags:
+ - website
+ - announcement
+date: '2022-10-23 22:58 +0100'
+---
+
+
+
+If you're a returning visitor, first of all, Thank You!, you might have already noticed things look a little different.
+
+I have updated the theme I am using from [Architect](https://pages-themes.github.io/architect/) to [Chirpy](https://chirpy.cotes.page/). This brings a number of useful features:
+
+* Dark mode (optional)
+* Search
+* Categories
+* Archives
+
+All posts now live in a /posts/ directory, and I managed to setup redirects using [jekyll-redirect-from](https://github.com/jekyll/jekyll-redirect-from) for all existing posts, so links should still work. If you run into a broken link, please let me know.
+
+I'm still working on getting the tags and catagories right. I expect I'll continue to refine them over time.
+
+I hope you enjoy the new look and feel, please let me know what you think.
+
+Photo by Junior Teixeira:
diff --git a/_posts/2022-11-01-anatomy-of-test-automation-2nd-edition.md b/_posts/2022-11-01-anatomy-of-test-automation-2nd-edition.md
new file mode 100644
index 0000000000000..fb944e086ebed
--- /dev/null
+++ b/_posts/2022-11-01-anatomy-of-test-automation-2nd-edition.md
@@ -0,0 +1,172 @@
+---
+title: Anatomy of test automation 2nd Edition
+tags:
+ - devops
+ - cicd
+ - infrastructure
+ - automation
+date: '2022-11-01 00:00:00 +0000'
+categories:
+ - Automation
+description: >-
+ Test automation is about more than code, it takes infrastructure, process and
+ strategy
+image:
+ path: /uploads/pexels-karolina-grabowska-7269622.jpg
+ height: 1000
+ width: '420'
+---
+
+A year or so ago, I had some ideas about the broader topic of Automation, and how it takes more than a sequence of steps with some assertions to make it successful. My original post can be found here: [https://dev.to/dowenb/anatomy-of-test-automation-e9o](https://dev.to/dowenb/anatomy-of-test-automation-e9o "https://dev.to/dowenb/anatomy-of-test-automation-e9o")
+
+Rather then bring the original post over to my personal blog as is, I'm going to attempt to update it and make it easier to consume.
+
+## System under test and supporting environment
+
+
+
+In the beginning, you need the correct version of the System Under Test. In this example diagram, we can see a hypothetical systems diagram that shows the environment, if the System Under Test, was the Audit Service.
+
+This maybe as simple as taking the latest build of a single isolated service. More likely, this will involve getting matching versions of multiple services that work together to form a system.
+
+This task alone may not be trivial, more than likely it can be automated with help of a Continuous Integration (CI) platform. Something like Jenkins that can be configured to kick off builds when you commit changes to source control.
+
+There are many useful technologies you can use to help you here, such as Docker, to spin up environments built of one or many components.
+
+There are a few different approaches you can take to test environments, these generally fall into shared or isolated. Each has different advantages, let's take a look.
+
+### Use shared, long lived environments
+
+Shared environments are useful because they can often support being used by multiple people at once. This means the whole team, or even multiple teams can be looking at the same consistent snapshot of the system, and it's different builds at once. This means you can have a shared experience of the system, and it can avoid the "works on my machine" problems when reproducing issues.
+
+You can also use shared environments to work with external teams or customers, these are sometimes called integration environments and may be abbreviated to int.
+
+Another advantage of such shared, longer lived environments is they may look closer to a production setup, although typically they are scaled down for cost purposes.
+
+The downside of shared environments are:
+
+* Difficult or impossible to isolate test date and shared state
+* Requires maintenance if test data nears clearing out or it gets corrupt
+* Needs updating with latest versions as new things get release and when taking a new version this may interrupt testing in progress
+
+Shared environments that have shared state, e.g databases, are typically sub-optimal for use in automation, but can support exploratory testing.
+
+The cost consideration for long-lived environments, is that depending on hosting they may be costing money while they are not being used. This can be somewhat mitigated, if they can be shutdown automatically outside of hours of use.
+
+### Isolated, on demand environments
+
+Isolated environments that are created on demand, live for only as long as they are needed and are then destroyed offer huge advantages to test automation.
+
+On demand environments that are built as needed, often supported by container technology such as Docker, can consist of multiple services. This maybe a combination of software build by your team, other teams in the company, and supporting services such as Databases, Queuing, Proxies, Load balancers, and mocks of third party systems.
+
+On demand environments may also be used for exploratory testing, where experiments can be run against a configured set of versions for the various components of the system under test.
+
+The cost consideration for isolated environments, is that each new environment adds cost, because all parts of the system under test and supporting services are spun up together. This is why typically, isolated environments are created on-demand and are short lived. They serve their purpose, and are then removed. This can be very cost effective overall.
+
+One disadvantage of on-demand environments is the extra time it takes to spin up, this can add minutes to your automation run, before tests have even started.
+
+### Isolated or Shared Environments?
+
+The two are not mutually exclusive, you could have isolated environments for automation, and shared environments to aid exploration. It really depends if you are optimising for cost, freedom of configuration, isolation or speed.
+
+However you approach it, getting the environment and setup for the system under test right is not a trivial task, and requires investment. If you have infrastructure, ops or devops type folk at work, make use of them. If you're really lucky, you might have a platform engineering team that can set-up some of this magic for you.
+
+## Test scenario
+
+Okay, the big one, once we have our environment all setup and supporting our SUT, we can focus on what to test.
+
+### Problem solving
+
+You likely have some kind of motivation for introducing test automation. Take some time to make your desired outcomes explicit, and figure out how you might measure your success.
+
+Maybe you are hoping to release faster? or you might be interested in providing faster feedback for problems that are normally caught late, or not caught at all!
+
+### Risks and choosing what to test
+
+ Before we break down our tests, let us take a moment to consider what problem we are trying to solve, and what risks we want to address.
+
+It has often been said before, that simply trying to automate a stack of existing regression test scripts is a receipt for a failed automation effort. But what alternatives exist?
+
+1. Take a risk-based approach, use techniques such as [Risk Storming](https://www.ministryoftesting.com/testsphere/riskstorming) to identify key quality aspects and the risks to them, and focus your efforts there
+2. Identify tests that are error prone or difficult to run by hand, and focus there
+3. Identify tests where automation can bring value due to an expanded range of inputs, or simulate realistic load
+4. Identify the path though your system under test that gives the most business value, for example completing an order, the critical paths that must work, and focus there
+5. Play [The Nightmare Headline Game](https://www.oreilly.com/library/view/explore-it/9781941222584/f_0022.html) from [Explore It!](https://www.oreilly.com/library/view/explore-it/9781941222584/) by [Elisabeth Hendrickson](https://twitter.com/testobsessed)
+
+Once you have identified some risks, or high value focus areas, you will need to prioritise where to start. If you don't already have your own generic approach to prioritisation, fear not! As [James Thomas](https://twitter.com/qahiccupps) has kindly shared his, in this blog post [Order, Order!](https://qahiccupps.blogspot.com/2019/04/order-order.html)
+
+### Prerequisites
+
+In addition to all the setup you've done to get this far you might still need a bit more. Maybe you need some Customers, and Stock, so you can exercise Orders?
+
+
+
+### Test data
+
+If your inputs and outputs are static, this might be trivial. For me, I often work with non trivial test data that requires some level of templating.
+
+I often need to make sure dates represent today, even if I wrote the test and captured the data months ago.
+
+In some cases test data can be generated automatically using libraries like faker. I know some tools, like Mockoon include Faker out the box.
+
+Once you know what shape your test data may take, you might want to create scripts to pre-seed databases if you are using isolated environments. You may also wan to reset data to a known state, if you are using shared environments.
+
+### System state (Given)
+
+Now your going to want to get your system into the starting state.
+
+Some examples:
+
+* A customer exists
+* Stock is available
+* The customer has no outstanding orders
+
+This is something your automation framework really should handle.
+
+### Action (When)
+
+This is the core of the test. Stimulating the users action or a sequence of multiple actions that we expect to make some change to the system state.
+
+Examples:
+
+* New customer is registered
+* Order is placed
+* Stock is allocated
+
+### Assertion of expected result (Then)
+
+This is where we have a coded assertion. I don't mean we need to be using a programming language, but we need to have an unambiguous way to choose if the actual results we got are what we expect.
+
+If they match our coded expectations the test passed, otherwise it falls. The term for the source of knowledge you used to determine if a test past is often called an oracle, you can learn more about oracles in this Ministry of Testing 99 second introduction:
+
+[https://www.ministryoftesting.com/dojo/lessons/99-second-introduction-to-oracles](https://www.ministryoftesting.com/dojo/lessons/99-second-introduction-to-oracles "https://www.ministryoftesting.com/dojo/lessons/99-second-introduction-to-oracles")
+
+While we can make test smart to an extent and we can look for shapes and ranges, ultimately we can only assert on what we can expect.
+
+## Logging and reporting
+
+Analysing logs and making reports can definitely be fully or partially Automated.
+
+This might take the form of some Console output that can be captured by your CI System and be linked to a build. It could also take the form of a HTML report, complete with graphs, screenshots, API responses to even video recording.
+
+What you will probably miss is the contextual logging. The logs from the dependencies and more distant parts of your SUT. This can also be captured and logged, but takes a fair amount more thought.
+
+## Minimal Experiment
+
+Of course this maximalist description describes pretty much an end to end or system integration test.
+
+As expert's like [Mark Winteringham](https://twitter.com/2bittester), [Richard Bradshaw](https://twitter.com/FriendlyTester) and [Alan Richardson](https://twitter.com/eviltester) would tell you, you can get great value from Automation and Tools to support your testing way short of an end to end test.
+
+I've done this myself on plenty of occasions by creating tools to capture or generate test data, of by mocking APIs to support my Exploratory Testing.
+
+I would encourage you to start with the smallest possible experiment that brings you value, and then build up to a more complete suite of test automation over time. Your team will benefit from faster feedback from tooling quickly, before you finish a full setup.
+
+## Automation strategy requires support
+
+[Building software is a team game](https://www.dowen.me.uk/posts/creating-software-is-a-team-sport/), and Software Quality even more so. I encourage you to work with teams and individuals across your company to share expertise and get help. If you're lucky, you maybe have some type of platform engineering team who can help you with the CI/CD setup and building test environments.
+
+Getting investment to support an automation strategy takes effort, especially, as I hope you can now see, it takes a lot more to get right then simply writing a few tests in a framework and hoping for the best.
+
+If you were not convinced already that to succeed, an automation strategy needs support and buy in from many people in various roles, I hope you're now a convert. And I wish you luck getting the help and support you need to make automation a success in your team.
+
+Cover Photo by [Karolina Grabowska](https://www.pexels.com/photo/models-of-organs-7269622/)
diff --git a/_posts/2022-11-01-where-to-start-bringing-automation-into-your-team.md b/_posts/2022-11-01-where-to-start-bringing-automation-into-your-team.md
new file mode 100644
index 0000000000000..68dad97be2fb2
--- /dev/null
+++ b/_posts/2022-11-01-where-to-start-bringing-automation-into-your-team.md
@@ -0,0 +1,43 @@
+---
+title: Where to start bringing automation into your team
+tags:
+ - automation
+date: '2022-11-01 00:00:00 +0000'
+categories:
+ - Automation
+description: 3 steps to get started bringing test automation into your team
+image:
+ path: /uploads/pexels-tara-winstead-8386434-10x14.jpg
+ height: 420
+ width: '1000'
+---
+
+[Krystina Prendergast](https://twitter.com/RuinAerlin) asked on Twitter:
+
+> You advocated to have automation added to your test team... and somehow got it approved with no idea what framework or tools you want to use, let alone an automation strategy. What is the first step you take?
+
+And this was my response:
+
+### 1. Set a foundation
+
+If you haven't already, go take this free course, [Setting a Foundation for Successful Test Automation](https://testautomationu.applitools.com/setting-a-foundation-for-successful-test-automation/)
+
+### 2. Identify the problem
+
+Identify the problem you want to solve with automation, I'm thinking:
+
+* What risks, to what important functionality do you want to cover first?
+* Where do you want to see improvements? Time to release? More coverage per build?
+* Testability / support exploration?
+
+### 3. Design a small experiment
+
+Design the smallest possible experiment that has a chance of giving you something useful. Nothing motivates better then results!
+
+Maybe write one small test, and experiment how to get it running, progressively more usefully.
+
+* Locally, your machine
+* Locally, anyone in the team
+* In a shared environment, part of a CI pipeline
+
+Header Photo by [Tara Winstead](https://www.pexels.com/photo/person-reaching-out-to-a-robot-8386434/)
diff --git a/_posts/2022-12-22-collaborating-to-build-better-software.md b/_posts/2022-12-22-collaborating-to-build-better-software.md
new file mode 100644
index 0000000000000..74bfdcfac2d71
--- /dev/null
+++ b/_posts/2022-12-22-collaborating-to-build-better-software.md
@@ -0,0 +1,222 @@
+---
+layout: post
+title: Collaborating to build better software
+description: >-
+ A journey talking about testing and building better software though
+ collaboration
+image:
+ path: /uploads/ben_ensemble_talk_header_1000x337.jpg
+ width: 1000
+ height: 337
+ alt: >-
+ Ben dressed as an elf with a santa hat giving his talk at Automation
+ Advocates
+category: Testing
+tags: null
+date: '2022-12-23 10:50 +0000'
+---
+
+
+## A goal for growth
+
+This year I set myself a goal:
+
+*Increase my confidence talking about software testing and bring my joy of testing to people who build software but are not specialised in testing.*
+
+To kick things off I went in search of an audience that included developers, product managers, designers or other people involved in building software, but don't identify as Testers. The "shout it from the roof tops" method, thankfully my direct approach paid off, and via the power of the excellent software testing and development community, I found some opportunities to speak.
+
+Over 2022, I developed an interactive talk and over 4 events I was able to speak to people about testing. I was honoured to be able to speak with 3 private companies, and at the Automation Advocates meetup. At all the events there was a mix of people who worked in different roles, developers, designers, product and project managers and of course plenty of testers as well for good measure.
+
+## Talk the talk
+
+### Setting the scene
+
+I intentionally selected audiences from mixed backgrounds, roles and experience of software testing and quality. As such, I start off my talk with my take on the key themes of Quality, Testing and Ensembles.
+
+#### Quality in Software
+
+
+
+In summary, I described quality as the combination of:
+
+* **Goodness**, emotional response. How a product or service makes you feel.
+* **Usefulness**, how well can the user archive their goal that won't be to use the software, but to complete their task.
+* **Correctness**, often the main focus and still important, but to be balanced with the first two aspects.
+* From a **Perspective**, the perception of quality will be influenced by the one experiencing the software, their current mood, situation, intentions and experience with similar or competing products.
+* At a point in **Time**, the perception of quality will change over time as user expectations evolve. Windows XP moved the quality of the Windows Operating system on a huge step when it was released, but is now considered outdated and would likely not meet user expectations of a modern operating system.
+* Quality needs to be **Good Enough**, that is it should be good, and it should meet expectations, but perfect doesn't exist and we must be pragmatic how we balance different aspects of quality. What is good enough is highly dependant on context, for example you don't want to rush a Medical Device, but a game may deliver joy when only half finished.
+
+You can read more about how I think about quality in my post, [What does quality mean to me?](https://www.dowen.me.uk/posts/what-does-quality-mean-to-me/)
+
+A shout-out to [Dan Ashby](https://twitter.com/DanAshby04) and his post [Adapting Crosby’s 4 absolutes of quality into a software context](https://danashby.co.uk/2019/09/30/adapting-crosbys-4-absolutes-of-quality-into-a-software-context/), that has significantly influence my current thinking on quality.
+
+#### Why do we test software?
+
+
+
+There maybe many reasons why you might want to test software. These are some of the reasons I test software:
+
+* To learn, though investigation, how the software behaves in a given scenario. This helps us understand how that might make users feel (Goodness), and if it delivers the value with expect (Usefulness). From those learnings, the team can make informed decisions including changes to the design or implementation.
+* To observe how the software behaves in a given scenario, under load or with a set of variables. To attempt to disprove our current hypothesis on how the software currently operates so we can work towards making it work the way we intend (Correctness).
+* To prevent predictable failures, this is very much inline with the formal definitions and is often the sole focus for testing. Preventing failures is important, but not sufficient in the context of my understanding of Quality.
+* To improve, by getting a better understanding of the software we can notice opportunities to add functionality and improve quality. These are not defects, but opportunities to make improvements that may not have already been noticed.
+* To ship software, with confidence we understand the current state of quality inline with our context and appetite for risk.
+* Money, in many aspects. Including Software Testing being my career, I test because I get paid. But also, we test software to reduce avoidable costs from uncaught defects that become production incidents.
+
+What might software testing look like tomorrow? I've already started thinking about this, in my post [The Future of Software Testing](https://www.dowen.me.uk/posts/the-future-of-software-testing/).
+
+#### Pair and Ensemble Testing
+
+
+
+Ensemble working is the new name for what you might know as mobbing or mob programming. It is a way of working where a multi-disciplinary team all work on the same thing, at the same time, around the same computer. Ensemble testing is using the ensemble way of working, to carry out a software testing activity. While this works especially well for Exploratory Testing, it could work for any testing activity including test analysis, design and even coding automated checks.
+
+This year, I've focused on two complimentary elements of Software Testing, *Collaboration* and *Exploration*. I've carried out regular ensemble testing sessions with Medical Knowledge Engineers at Ada, the Medical Doctors who code our Medical Knowledge. This has been a hugely rewarding experience, where we have learned a lot together, including how to successfully work together working on the same work, at the same computer, at the same time (Ensemble).
+
+Throughout our sessions we carried our regular reflections, and I gathered some great feedback. This is what I learned:
+
+* In my experience, ensembles are very powerful in groups of 2-6. However I'm very keen to see how far I can scale to large groups in special contexts.
+* Having different people, who have a range of live experience and expertise brings significant value that is hard to match with solo testing.
+* Diversity of thought was a huge advantage time and time again during testing sessions, because by thinking about things in different ways and from different perspectives we found potential issues that would otherwise be easy to miss.
+* Verbalising and taking deliberate actions as a group helped us share knowledge quickly as we worked on our ask. For example, engineers in the group picked up on different tools and using those tools in different context than they would normally do.
+* We all learned more depth about why others do things a given way, that helps us reflect on why we do things our way.
+* When the right people are in the room, we can take quick and decisive action, such as making the choice to change a model or design during a testing ensemble.
+* Though the combination of diversity of background, thinking and roles we were able to notice and reduce some of our bias in our work. For example bringing understanding of the problems around access to health care in some regions into our shared context while testing medical models.
+* The experience of working in paris and ensemble groups was sociable, and a lot of fun, compared to what was previously a lonely task. This was especially true for those working remote.
+
+### Ensemble, Leaning Together
+
+Each of the four times I've run the event so far, I have engaged with the audience to form an ensemble, and together we worked though 3 questions. Collectively we came up with talking points, thoughts, answers and further questions based on the ordinal questions posed.
+
+Each time I ran the session, there were different unique points that the ensemble came up with. While there were some recurring themes, each time we had different examples and perspectives on the those common points, and some points there were unique to the group.
+
+### 3 Questions
+
+Let us take a look now at the 3 questions, I will include the output from the ensemble with the group for the [Automation Advocates Meet-Up](https://www.meetup.com/automation-advocates/), because this was the most recent and was a public event.
+
+In order to provide a prompt, I used a prop for the discussion in the form of a very basic requirement with 3 acceptance criteria.
+
+Requirement: *Users must be able to login to the web shop*
+
+1. Login is accepted for valid users
+2. Login is rejected for invalid users
+3. Multiple failed attempts blocks further attempts
+
+I also encouraged conversation from the experiences of teh group, that were not focused on the basic web shop example.
+
+#### Why might it not be enough to simply check acceptance criteria have been met?
+
+
+
+Spoiler alert, it isn't enough simply to check acceptance criteria have been met. Discussion with this ensemble, similar to the past groups came up with some of the following themes:
+
+* Missing detail not covered by the webshop requirement or the acceptance criteria for example:
+ * What session management? Logout, session times out?
+ * What happens with lost credentials, will there be password reset?
+ * Can users ever be unblocked, after failed login attempts?
+* Operational, or non-functional requirements that might be implied, such as:
+ * Security
+ * Performance
+ * Accessability and other 'illities
+* Vague, ambiguous, missing or unspecified details
+* Validity of the acceptance criteria themselves
+ * Where did these criteria come from?
+ * Is there opportunity to add more criteria when we think of them later?
+* And finally, do we understand the problem being solved sufficiently in the first place
+
+In conclusion, user stories with acceptance criteria are an example of *explicit* requirements. The main reason checking these alone is not enough is because there are also many implicit requirements we need to consider.
+
+Resources to learn more about these topics:
+
+* [EXPLORING NON FUNCTIONAL REQUIREMENTS BY FINDING LOW HANGING FRUIT
+](https://cakehurstryan.com/2022/01/13/exploring-non-functional-requirements-by-finding-low-hanging-fruit/) - by [Callum (Ryan) Akehurst-Ryan](https://www.linkedin.com/in/cakehurstryan/)
+* [Testing Against Acceptance Criteria And Beyond | Interview with Ben Dowen](https://youtu.be/OKCQHOkve-E) - by [Nicola Lindgren](https://www.linkedin.com/in/nicolalindgren/)
+* [Step by step guide: Testing without requirements little requirements](https://nicolalindgren.com/step-by-step-guide-testing-without-requirements-little-requirements/) - by [Nicola Lindgren](https://www.linkedin.com/in/nicolalindgren/)
+* [A11Y WITH ADY: SIMPLE TESTS FOR ACCESSIBILITY EVERY TESTER SHOULD KNOW](https://www.thebigtesttheory.com/blog/2022/11/5/a11y-with-ady-simple-tests-for-accessibility-every-tester-should-know) - by [Ady Stokes](https://www.linkedin.com/in/a11yadystokes/)
+
+#### How can we make implicit requirements explicit?
+
+
+
+So, wer now know checking explicit requirements, such as user stories with acceptance criteria is not enough, and there are loads of missing or implicit requirements. So how can we expose those implicit requirements, and make them more explicit?
+
+Again, as an ensemble we came up with some great answers and had some great discussions. I also got some good answers across other ensembles and I've done some thinking on this myself, collectively the highlights are:
+
+* Conversations, with stakeholders, users, anyone involves in building or using the software
+* Modelling, by capturing models of the way the system is expected to behave we can have better conversations, such as:
+ * State transition diagram
+ * Work flow and data flow diagrams
+* Low fidelity wire-frames
+* Mock ups and prototypes
+* User testing
+ * Interviews and observations
+ * Focus groups
+* Pair and ensemble testing
+* Example Mapping and BDD
+* Standards, guidance and recommendations
+* Service Level Agreements and Service Level Objectives
+ * Downtime
+ * Response latency
+ * How fast incidents are resolved
+* Threat Modelling
+* Risk Storming
+
+Resources to learn more about these topics:
+
+* [Step by step guide: Testing without requirements little requirements](https://nicolalindgren.com/step-by-step-guide-testing-without-requirements-little-requirements/) - by [Nicola Lindgren](https://www.linkedin.com/in/nicolalindgren/)
+* [Web Content Accessibility Guidelines](https://www.w3.org/WAI/standards-guidelines/wcag/)
+* [UK Government Design System](https://design-system.service.gov.uk/)
+* [The Open Web Application Security Project® (OWASP), Top Ten](https://owasp.org/www-project-top-ten/)
+* [Let's Go Threat Modelling](https://www.ministryoftesting.com/dojo/lessons/let-s-go-threat-modelling) - by [Richard Adams](https://www.linkedin.com/in/richard-adams-9613b47/)
+* [The Power of Example Mapping!
+](https://www.ministryoftesting.com/dojo/lessons/the-power-of-example-mapping) - by [Kiruthika Ganesan](https://www.linkedin.com/in/kiruthikaganesan/)
+* [RiskStorming In Agile Teams With TestSphere](https://www.ministryoftesting.com/dojo/lessons/riskstorming-in-agile-teams-with-testsphere) - by [Gem Hill](https://www.linkedin.com/in/gem-hill-69644a71/lisi)
+
+#### How can we get a better outcome by testing together, in pairs and ensembles?
+
+
+
+The third and final question starts to get a bit meta, as ensemble we collaboratively come up with ways we can use collaborative working to get better outcomes. We need not limit ourselves to the activity of testing, although that is the main focus still.
+
+The themes this time are:
+
+* Benefits we get, when we do work together
+ * Shortcuts we can learn from each other, be that literal keyboard shortcuts or ways of getting the system into a given state quickly
+ * By bringing in people with coding skills, we can create tools to support our testing as we go
+ * If we find problems during testing, we can dig deeper and go directly into debugging, even fixing issues together live
+ * It's a great opportunity to build empathy and teamwork
+* How we can best work together
+ * Bringing in diverse skills and experience, "fresh eyes" can be very useful
+ * Have conversations and communicate, within the ensemble and with the wider team
+ * Find new, better questions to ask, of ourselves and the software
+
+There are loads of amazing resources to learn more about working collaboratively, in an ensemble or otherwise. My esteemed colleague and international speaker [Lisi Hocke](https://www.lisihocke.com/p/about-me.html) has compiled a fantastic list, recommend you check it out if you want to learn more:
+[Recommended Resources: Collaboration](https://www.lisihocke.com/p/collaboration.html#ensemble)
+
+## In reflection
+
+Well done on getting this far! I will now take a moment to reflect on how I think things went.
+
+### Did I meet my goal?
+
+Yes, I am now more comfortable speaking about testing to mixed groups. I have a long way to go to be as good as I want to be at both speaking and sharing the joy of testing, but I've made a start I'm proud of.
+
+I really enjoyed the interactive, slides + short ensemble workshop style, and I want to see if I can build on this for future talks.
+
+### What would I do differently?
+
+I would put more effort into working my example requirement. I brought it in as a prop, based on feedback, shortly before the first time I gave the talk. And while I had time to improve it between events, I didn't invest such time.
+
+Another thing I would do differently is try and keep the theme a bit tighter. This talk crossed purposes, talking about implicit and explicit requirements, and ensemble testing. While they did add together to add value, next time I want to either spell that out more explicitly, or pick a more tightly related theme.
+
+### Whats next?
+
+I don't currently have any plans to run this talk again, at least not in it's current form. I'm hoping to start dreaming up version 2.0, evolving the format and refining the theme. If you have any feedback for me, it would be very much appreciated and I will try and use it for future talks.
+
+If you're very keen on me running the talk again with your team, or for your meetup, I could be convinced. So feel free to get in touch.
+
+## Watch the Recording
+
+In the mean time, the event for [Automation Advocates Meet-Up](https://www.meetup.com/automation-advocates/) was recorded, and is available for free on [YouTube](https://youtu.be/CvSTtOtx3BE), so if you want to watch it for yourself jump right in!
+
+
diff --git a/_posts/2023-07-28-content-creation-goals.md b/_posts/2023-07-28-content-creation-goals.md
new file mode 100644
index 0000000000000..06b5306df67a1
--- /dev/null
+++ b/_posts/2023-07-28-content-creation-goals.md
@@ -0,0 +1,25 @@
+---
+layout: post
+title: Content creation goals
+date: 2023-07-27T23:00:00.000Z
+categories: Announcement
+tags:
+ - behind the scenes
+ - planning
+draft: false
+---
+
+It feels like it has been ages since I last wrote on my blog. Over the last few months, I've had dips where I've not created much content, or I've posted it directly on The Club, instead of on my personal blog. It's OK to take a break, but now I want to get back into it.
+
+So I don't need to come up with topics from scratch every time I want to put something new out, I'm making a plan. You know I mean business when I say, I've created a spreadsheet, everyone loves a good spreadsheet, right?
+
+
+
+I've come up with a number of Themes, and even some draft titles for content I want to post this year. I've also planned a cadence, however fast I write, I'm going to aim to publish 1 post a week, maximum. This should you to consume my content consistently, as I produce it as I have capacity.
+
+I'll also check back in off-cycle at some point, and let you know how I'm getting on. Wish me luck. Oh and you'll still find me over on the [Ministry of Testing Club](https://club.ministryoftesting.com/ "Ministry of Testing - The Club"), where I might try out some of my content or ask questions ahead of time.
+
+Updated to say, I'm a little ahead of schedule, and I couldn't resist posting my first new blog early!
+
+Check it out:
+[https://www.dowen.me.uk/posts/what-makes-up-a-software-stack/](https://www.dowen.me.uk/posts/what-makes-up-a-software-stack/)
diff --git a/_posts/2023-07-28-what-makes-up-a-software-stack.md b/_posts/2023-07-28-what-makes-up-a-software-stack.md
new file mode 100644
index 0000000000000..53e1f9a55cbea
--- /dev/null
+++ b/_posts/2023-07-28-what-makes-up-a-software-stack.md
@@ -0,0 +1,94 @@
+---
+layout: post
+title: What makes up a software stack
+date: '2023-07-28T23:00:00.000Z'
+categories: Testing
+tags:
+ - technical
+ - full-stack-testing
+image: /uploads/pexels-christina-petsos-11753327.jpg
+---
+
+
+I like to think of a software stack, also referred to as a technology stack, as the different layers of technology that build on top of eachother in order to make a functioning system.
+
+What goes into that software stack depends on a great many things, there are some frequently seen, common layers and some more exotic ones depending on the architecture of your system and how it has evolved over time.
+
+## Classic Web Development Stacks
+
+When I started learning about web development, in the early 2000's if you must know, the classic stack was LAMP. LAMP stands for [Linux](https://www.linux.org/), [Apache](https://httpd.apache.org/), [MySQL](https://www.mysql.com/) and [PHP](https://www.php.net/), using this collection of technologies you had Linux as the foundational operating system, Apache as the webserver, MySQL as the persistence in the form of a relational database. Finally PHP would combine with HTML, CSS and JavaScript to provide both backend business logic, the connection to the database and frontend presentation to the user.
+
+And if you were to test an application running on a classic LAMP stack, you would need an environment where you could deploy these technologies. You also need to choose how deep to go, and what risks you might want to test for at in each part of the stack.
+
+It would be totally understandable to stop short of testing the Linux OS itself, however I can think of more than one time a misconfigured or out of date Linux installation has cause a compatibility issue or security bug.
+
+## Modern Web Development Stacks
+
+While the classic LAMP stack still exists, there is a very good chance you are developing or testing a more modern wizz-bang software application that uses a newer stack. MERN stands for [MongoDB](https://www.mongodb.com/), [Express.js](https://expressjs.com/), [React ](https://react.dev/)and [Node.js](https://nodejs.org/).
+
+Here we have a NoSQL Document Storage Database, in MongoDB and then a lot of JavaScript. Express.js describes itself as "Fast, unopinionated, minimalist web framework for Node.js", and Node.js is itself a an open-source cross platform JavaScript runtime environment. React is a library for web and native interfaces.
+
+## Beyond web development
+
+Of course, web applications are far from the only software systems out there. Mobile apps bring additional technology to the stack, as do Desktop applications. There are also more exotic or specialised software systems you might get involved testing, like firmware, control software for industrial systems.
+
+There is also software in embedded devices from smart fridges to medical devices, and these may interact with web based backend services, or may operate independently without an internet connection at all. In 2023, no internet, I know right? Madness.
+
+I won't cover all possible stacks here, I probably couldn't if I tried, as rather than looking like clean show-home like system architectures, most systems evolved over time to also include "that old bit nobody remembers how it works", and "that bit that runs on a database from the 80's, bit it still makes money so it won't get replaced unless it dies".
+
+OK, maybe I'm showing both my age and some point from some very specific jobs with that last one, but the point stands that there maybe a mix of stacks across your company, that are somehow stuck together to form the product your systems know and love.
+
+## Common themes
+
+There are some common parts to most software stacks, and while beyond web development there are some differences, key components are shared across almost all software.
+
+### Presentation and user interface
+
+Be it a web page in a browser, an app on your phone or the Point of Sale software on those love em or hate em self-checkout tills, most software has some way to present information to the user and allow some kind of interaction.
+
+This layer is likely one part of the software you test, that you know very well, after all it's the easiest entry point of exploratory testing and it is the bit you can see, hear, touch or maybe shout at (I'm looking at you, voice assistance speakers).
+
+### Business logic, backend and third party services
+
+Not all systems are so clean that all logic is abstracted away from the Presentation layer and into backend services, in fact it's safe to say some business logic will likely sit alongside the UI layer of your application.
+
+Dig a bit deeper, and there is also very likely backend services that embody much more logic. I use services plural, as the majority of systems I've worked on have had more than a single backend service. These backend services are where your system does processing, makes decisions and ships data off to the persistence layer.
+
+Things to watch out for at this layer include business logic, that either supports the frontend or may be hidden from it and had to spot directly. It's also worth identifying third parties you interact with, this will often take place via API calls using HTTP requests, but not always. Examples of third party services are PayPal or Stripe for payment processing or UPS for logistics.
+
+### Persistence
+
+The persistence doesn't only include databases that store documents or structured data, at this layer you can also find other types of storage. For example, filestorage is one way data is persisted in a system, think about where all those images go when you past them into your ticket management system, it probably isn't a database.
+
+In the same way logic can leak into the presentation layer in the UI, the persistence layer is another place logic and rules can live. These might be semantics such as the data types of fields, the encoding and compression of files or a number of other things that will depend on your system.
+
+Many times I've seen errors cause by truncated data in fields that have a data type that simply cannot storage the value the backend tries to put in them, and depending on the configuration and logic at this layer, there maybe no error passed back.
+
+### Operating Environment
+
+All the moving parts that make up your application need somewhere to live, and this operating environment in modern systems if often itself another complex layered system. And can further be broken down, although I'll spare you some detail, you can dig very deep here if you wish.
+
+The foundation of the Operating Environment is the hardware the software runs on, this might be abstracted away for you by a Cloud provider or some in-house system of virtual machines and related orchestration.
+
+The architecture of the computer processors, CPUs, can have a profound impact on what software can run on higher layers of the system. The two major hardware architectures are ARM and x86.
+
+The operating systems running on the hardware can also have a big influence on what software can be run, although a majority of mainstream server software now runs on either Windows or Linux, developing for iOS still has a large dependency on Apple hardware and MacOS software.
+
+On top of the Hardware and the OS, many other dependencies exist that can influence things, these maybe system level versions of runtime environments, such as [Java](https://www.java.com/), [.NET](https://dotnet.microsoft.com/en-us/), [Ruby](https://www.ruby-lang.org/en/) or Node, or tools and libraries that your software expects to be available. And all these need to be kept up to date, with each new version introducing bug fixes, and possible incompatibilities, so this layer has its own challenges for sure.
+
+No discussion of the Operating Environment would be complete, without mentioning containers. [Docker](https://www.docker.com/), [containerd](https://containerd.io/), and the orchestration built on top such as kubernetes, and helm, bring some solutions to the problems above. Dependencies can be managed in an isolated way for each container, so each service can use the correct versions of Java and Node. Of course, this is another thing to learn, configure and manage, and adds it's own complexity.
+
+## Where to learn more
+
+A bunch of links to learn more about software stacks:
+
+* [Top 10 tech stacks for software development in 2023](https://www.imaginarycloud.com/blog/tech-stack-software-development/ "Top 10 tech stacks for software development in 2023")
+* [ARM vs x86: What's the difference?](https://www.redhat.com/en/topics/linux/ARM-vs-x86)
+* [Xcode, used to build iOS apps on Mac OS](https://developer.apple.com/xcode/)
+* [Failing for the Right Reason - a Fresh Look on TDD](https://www.ministryoftesting.com/testbash-talks/64f70bd6?s_id=15416741)
+* [Multitier architecture (Wikipedia)](https://en.wikipedia.org/wiki/Multitier_architecture)
+* [LAMP software bundle (Wikipedia)](https://en.wikipedia.org/wiki/LAMP_\(software_bundle\))
+* [MEAN solution stack (Wikipedia)](https://en.wikipedia.org/wiki/MEAN_\(solution_stack\))
+* [MERN Stack Explained](https://www.mongodb.com/mern-stack)
+
+Header image: [Photo by Christina Petsos](https://www.pexels.com/photo/cake-with-colorful-layers-11753327/)
diff --git a/_posts/2023-08-01-how-many-yaks-have-you-shaved-this-week.md b/_posts/2023-08-01-how-many-yaks-have-you-shaved-this-week.md
new file mode 100644
index 0000000000000..8252eb7371e30
--- /dev/null
+++ b/_posts/2023-08-01-how-many-yaks-have-you-shaved-this-week.md
@@ -0,0 +1,41 @@
+---
+layout: post
+title: How many Yak's have you shaved this week?
+date: 2023-07-31T23:00:00.000Z
+draft: false
+image: /uploads/medium-yak.jpg
+categories: Quality
+tags:
+ - process
+ - agile
+---
+
+A quick bonus post today, I'm enjoying writing long-form posts weekly, but I wanted to sneak in a little one, enjoy.
+
+## Yaks
+
+You know all those seemingly meaningless tasks you need to do, to cover come short-term problems, just so you can eventually get to the bigger problem and start solving it?
+
+Maybe it's the test environment you need to build by hand, so you can install your system under test, to then actually start testing a build. The goal isn't to build a test environment, it's to test the software, or better to ship working software.
+
+Or you may find yourself completing some less-useful tasks, as procrastination, so you can put off that big important task a little longer (like writing this blog post, Ben....).
+
+You can describe this as Yak Shaving, a term based off an episode of a 1990's TV show, Ren and Stimpy. You can [read more about the etymology here](https://en.wiktionary.org/wiki/yak_shaving).
+
+## How many have you shaved?
+
+So, how many Yaks have you shaved this week? Does it feel like you're always shaving Yaks, and never get time to get into the meat of the problem?
+
+I'd leave to hear from you, your opinion on Yak Shaving, and what you might do about it.
+
+You can get in touch with me on the socials, start the conversations "[Yakety yak](https://www.youtube.com/watch?v=epCN0f7FTIY)", or don't, it's up to you:
+
+Twitter: [FullSnackTester](https://twitter.com/fullsnacktester)
+
+Blue Sky: [FullSnackTester](https://bsky.app/profile/fullsnacktester.bsky.social)
+
+LinkedIn: [dowenb](https://www.linkedin.com/in/dowenb/)
+
+Mastodon: [FullSnackTester](https://sw-development-is.social/web/@fullsnacktester)
+
+Hero image: [Photo by Kelly](https://www.pexels.com/photo/close-up-photo-of-yak-with-long-horns-2382741/), via [Pexels.com](https://www.pexels.com/)
diff --git a/_posts/2023-08-02-testing-notes.md b/_posts/2023-08-02-testing-notes.md
new file mode 100644
index 0000000000000..4a0598fbf0045
--- /dev/null
+++ b/_posts/2023-08-02-testing-notes.md
@@ -0,0 +1,29 @@
+---
+layout: post
+title: Testing notes
+date: 2023-08-01T23:00:00.000Z
+draft: false
+image: /uploads/notebook.jpg
+tags:
+ - test notes
+ - testing
+---
+
+Testing notes are an essential part of how I do software testing, if you don't use them no shade from me, but I need my notes!
+
+Over the years, I've taken notes in very different ways, and using different tools. How I take exploratory testing notes now, differs widely to how I took notes while I was mostly using test cases, and each of those evolved over time.
+
+I'm interested to know, where do you keep your notes? Do you add comments to tickets? Scribble on paper?
+
+My preference is to have test notes pages in confluence, and edit them as I go, and then if needed I copy details into other tools or provide links. You can even do a neat trick where confluence pages are embedded into Jira tickets.
+
+What do I like about my method? Simply
+
+* Confluence works well with multiple people editing a document at once, great for ensemble testing!
+* It has enough formatting and embedding of media options to be useful
+* Using templates and macros it's a low barrier to creating a new page, so I can jump into making notes quickly
+* It's visible to others very quickly without me needing to explicitly share it, so I'm doing everything visibly
+
+How do you take your notes, and why?
+
+Photo by [Kelly Sikkema](https://unsplash.com/@kellysikkema?utm_source=unsplash\&utm_medium=referral\&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/photos/9OGNpJPVMZ8?utm_source=unsplash\&utm_medium=referral\&utm_content=creditCopyText)
diff --git a/_posts/2023-08-04-this-week-in-testing.md b/_posts/2023-08-04-this-week-in-testing.md
new file mode 100644
index 0000000000000..ccb99281cfe0a
--- /dev/null
+++ b/_posts/2023-08-04-this-week-in-testing.md
@@ -0,0 +1,20 @@
+---
+layout: post
+title: This Week in Testing
+date: 2023-08-03T23:00:00.000Z
+draft: false
+image: /uploads/this-week-in-testing.PNG
+categories: Community
+tags:
+ - MoT
+---
+
+Today I had the immense honour of co-hosting the LinkedIn audio event, [This Week in Testing](https://www.linkedin.com/events/thisweekintesting-w-b31stjuly207091795661565673472/comments/), with the most excellent Community Boss, [Simon Tomes.](https://www.linkedin.com/in/simontomes/)
+
+I really enjoyed co-hosting. I've been on panels, I've presented, and I've facilitated and hosted a bunch of work meetings, but this is my first time co-hosting a community event with the [Ministry of Testing](https://www.ministryoftesting.com/), turns out I love it.
+
+Getting the opportunity to encourage conversations and support others to come and have their say, while also getting to throw in my own stories here and there, it's pretty addictive, and I'm already wondering when I might be able to do it again.
+
+I found out recently that one of my team members really dislikes facilitating or hosting events, especially outside of our team. He actively dislikes it and avoids it. Reflecting on this, I realised that it's something I've grown very comfortable with, and I've had a bunch of positive feedback for sessions I facilitate.
+
+Over all, hosting is great, would recommend. Especially if you get to co-host with Simon!
diff --git a/_posts/2023-08-07-that-shiny-new-feature-works-so-what.md b/_posts/2023-08-07-that-shiny-new-feature-works-so-what.md
new file mode 100644
index 0000000000000..fa88e496d318c
--- /dev/null
+++ b/_posts/2023-08-07-that-shiny-new-feature-works-so-what.md
@@ -0,0 +1,82 @@
+---
+layout: post
+title: 'That shiny new feature works, so what?'
+date: 2023-08-06T23:00:00.000Z
+draft: false
+image: /uploads/cube-small.jpg
+categories: Quality
+tags:
+ - quality engineering
+ - technical
+ - full-stack-testing
+---
+
+## What does it mean, to say your feature is complete?
+
+![]()
+
+In software delivery teams I've worked in, we have often been responsible for parts of products. Sometimes this means we have been responsible for one or more services, and nothing beyond the responsibility of that service. Other times, the team has been responsible for a vertical stripe of functionality that crosses one or more backend services and the frontend that goes with it.
+
+In almost all cases, we haven't been responsible for the whole system at once, the responsibility has been split up across multiple teams in some way. This means there has been times the team I've been in has declared a feature as complete, and then handed it over to another team. And the other way, our team has had to handle features implemented by other teams, that now change the product our services of features operate in.
+
+All this means, that the concept of complete exists within the boundaries of responsibility, and it can mean different things to different people. So, when do we stop testing? When *our bit* is done? When the feature is available to customers? When we start collecting and analysing the first days, week, months worth of tracking data?
+
+I find it very valuable to explore what complete means for the team I'm in, and to communicate this concept of completeness for us, and see how that fits with other teams who work on the same product. Inevitability, releases have gone better when the relationship between the teams has been strong, and we've worked together to avoid a hard hand-off, aka "throwing it over the wall".
+
+## So what does this mean in context of the whole product?
+
+![Hand with golden pen, looking out over multiple question marks on paper. Intended to describe asking a question, what does it mean?]( "Photo by Leeloo Thefirst: https://www.pexels.com/photo/question-marks-on-paper-crafts-5428833/")
+
+So, your feature is complete. Time to celebrate, are ship parties still a thing? But wait, does this mean the value has been delivered? I've recently been working in a team that relies on the efforts of another team to release a new version of our mobile app, including all the other features that are going into the release, before users get their hands on our efforts. If they they are prevented from releasing for any reason, tough luck, our changes won't get out yet.
+
+OK so it isn't so bad waiting for another team before our code gets into the hands of customers, typically they ship every 2 weeks. As we share a code base or two, there is some scope of us to support each other, but also to step on each others toes.
+
+Most of this could be considered Developer Experience, so us now take a look at another point of view, from the end user. Does your new wizz-bang feature work sympathetically with the existing features? Does it have the same options for high-contrast colours? Can you print the results, or email them to yourself like you can on the other screens, no? Well this could cause users a headache!
+
+Your feature doesn't live in isolation, so doing a good job means taking into account the wider user experience. Some of this should come out during ideation or design, but it doesn't mean you shouldn't continue to test for it as you develop the feature. Often, implementation drifts from design and the end result might add unintended friction.
+
+## Now what can you do next to make it a success?
+
+
+
+Okay, we've looked at some details into why a feature being complete doesn't really mean it's done, done. Now, some thoughts on how we can turn this into a success.
+
+### Identify team dependencies
+
+In the end, it always comes down to people. Build an explicit list not just of the teams, but the people who you depend on, and are dependent on you, to deliver valuable features to the end user. Network with these people, learn their names, learn the goals and priorities of their teams.
+
+Do enough, so that when you need to ask for help, or forgiveness, it feels like it is coming from a respected colleague, who understands their situation. It is amazing how quickly minor problems can be resolved, if you can work well together has humans.
+
+You can also share our the relationships across your team, so you're not leaving everything to one person, and instead sharing the responsibility. This has the added bonus that you can all value the work that goes into building and maintaining relationships with other teams and key people.
+
+### Identify code integrations
+
+Direct dependencies are hopefully more obvious to map out, especially if work has already been done to maintain a system architecture diagram that shows how things hang together.
+
+It can be easy to miss how a change in one feature can impact other parts of the system up and downstream. So you also need to take time to map out more distant dependencies and relationships, and take time to appreciate how new changes will impact things.
+
+### Create cross-team structures
+
+So depending how your organisation is setup, you may have cross-functional teams of Testers or Architects, maybe Designers. They might already spend a lot of effort building relationships and identifying dependencies and relationships, if you're lucky enough to have these people, use them!
+
+It's also possible that there are topics that simply fall through the gaps, and are not covered either by any one team, or collectively by groups of teams. For this, you can setup cross-team structures, you can call these guilds, or virtual teams, or anything else that makes sense for you.
+
+The key thing is, to make space to speak to each other, be that via a chat channel, regular or on-demand meeting, so you remember to focus on the topics that would otherwise be missed.
+
+You can also make sure of structures you might already have on a cross-team, or group level, to discuss upcoming planned work, and see what other teams think about it.
+
+## Summary
+
+* Done for you might not mean done for everyone involved in getting your work in front of users
+* Considering the wider context of your teams work, will help you identify blockers to delivering value
+* It all comes down to humans, get to know the humans involved in getting your code in front of users
+
+## One more thing
+
+I hope you found this insight interesting, and my suggestions for improvement useful. I'd love to hear about your experiences.
+
+As I sign off, I wanted to share this. A friend at work sent me a link, and it made me chuckle more than a little bit, and it felt very relevant to this blog, so I'm including it here.
+
+[https://youtu.be/y8OnoxKotPQ](https://youtu.be/y8OnoxKotPQ)
+
+Heading [Photo by Pixabay](https://www.pexels.com/photo/colorful-color-play-concentration-54101/)
diff --git a/_posts/2023-08-09-05-ways-testing-mobile-is-different-from-web.md b/_posts/2023-08-09-05-ways-testing-mobile-is-different-from-web.md
new file mode 100644
index 0000000000000..4f3fa0541d9f4
--- /dev/null
+++ b/_posts/2023-08-09-05-ways-testing-mobile-is-different-from-web.md
@@ -0,0 +1,64 @@
+---
+layout: post
+title: 5 ways testing mobile is different from web
+date: 2023-08-08T23:00:00.000Z
+draft: false
+categories: Testing
+tags:
+ - specialist
+ - web
+ - mobile
+image: /uploads/pexels-jessica-lewis-583842.jpg
+---
+
+## 1 Hardware
+
+Web apps run on almost any device, from a games console to a tricked-out multi-core desktop PC with a giant high-resolution screen. In contrast, mobile apps typically run on Android, iOS, or both across many generations of mobile phones, tablets, and smartwatches.
+
+For really testing the user experience for mobile apps, having physical devices is a huge advantage, although it can get expensive fast. Locally running simulators and hosted device farms can be very helpful to get device testing coverage but are less ideal for really feeling the experience users will get.
+
+## 2 Automation
+
+Automating against web has both very mature tools, as well as a huge range of options, many of them use Selenium and the WebDriver protocols at their core. For web, locators are relatively easy to obtain via either CSS selectors or XPATH, and plenty of tooling exists to help you out there.
+
+On mobile, it's a little trickier to get going, you can't just dev tools in a browser to look up selectors, although there is tooling to help you out depending on your app architecture, for example, the studio mode on Maestro. As far as I can tell, mobile automation relies on identifying elements based on accessibility labels or types and indexes.
+
+The mobile equivalent for Selenium is Appium, and there are again other tools built on top. As well as Appium and other cross-platform solutions, each platform has native tools for testing native apps, I haven't used these myself but I know they are out there. Do you have experience writing automation using native tooling? I'd love to hear how it's different from cross-platform tools.
+
+One tool I've been learning recently is [Maestro](https://maestro.mobile.dev/), it seems pretty promising so far. One tool I know of that can test both web and apps, although I haven't used it in anger, is [NightWatch.js,](https://nightwatchjs.org/guide/mobile-app-testing/introduction.html) it's on my list of options to check out in the future.
+
+## 3 Accessibility
+
+Testing for web accessibility is way easier, not least before the [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/TR/WCAG21/) are written with the Web in mind. Two difficulties I've found so far with testing for mobile accessibility are the frustrating inconsistency in accessibility features and tooling to test on each platform.
+
+Google's Android has [Accessibility Scanner](https://support.google.com/accessibility/android/answer/6376570?hl=en-GB), and Apple iOS has the [Accessibility Inspector,](https://developer.apple.com/library/archive/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXTestingApps.html) one comes as an app to install on your device, real or emulated, and the other is a tool built into Apple MacOS you use together with the iPhone Simulator.
+
+In contrast, web has a ton of tools, from Axe-based inspectors and automation to browser extensions to simulate different colour blindness types, or even simulate cognitive and physical impairments.
+
+## 4 Up and running
+
+There are 3 main test environments you will need for mobile:
+
+1. On a real mobile device, you can touch and hold
+2. On a PC or Mac, using a simulator or emulator
+3. Via CI/CD to run automated builds, tests, and deployments of your apps
+
+CI/CD can be especially painful, especially for Apple devices where you still can't escape the need for an Apple device at some point in the chain. Hosted platforms do exist to solve this problem, at a price, such as [bitrise](https://bitrise.io/).
+
+Oh did I mention, web will run on almost anything, so CI/CD can run pretty much anywhere, a win for web.
+
+## 5 Risks
+
+While web and mobile maybe share a bunch of common risks to quality, both need to be fast, secure, and usable, mobile does have some unique risks.
+
+Is your app something people might try and use while driving? Therefore you might need to introduce a driving mode to reduce the risk users feel the need to get hands-on with their devices.
+
+Hogging too much processing power and battery? Risk the automated management tools in Android and Apple laying the smack down on your Candy-Crushing ass and counting 1, 2, 3.
+
+Not unique to mobile, especially as progressive web apps are a thing, but having a sudden lack of internet connection, or change of network is way more common on mobile, as is using VPN and switching between locations on a whim.
+
+## That's all folks
+
+I hope you found this interesting and valuable. What other differences, or similarities, between Web and Mobile apps can you think about? How might they impact your testing?
+
+Hero image: [Photo by Jessica Lewis](< https://www.pexels.com/photo/iphone-6-earpods-and-macbook-on-flat-lay-photography-583842/>)
diff --git a/_posts/2023-08-20-successful-collaborative-testing-sessions.md b/_posts/2023-08-20-successful-collaborative-testing-sessions.md
new file mode 100644
index 0000000000000..df5ac8882a92c
--- /dev/null
+++ b/_posts/2023-08-20-successful-collaborative-testing-sessions.md
@@ -0,0 +1,129 @@
+---
+layout: post
+title: Successful collaborative testing sessions
+date: 2023-08-19T23:00:00.000Z
+draft: false
+image: /uploads/pexels-canva-studio-3153201.jpg
+categories: Testing
+tags:
+ - collaboration
+ - pair
+ - ensemble
+---
+
+In my recent experience, I've found a few things that help set up a successful collaborative testing session.
+
+I've used these to collaborate with members of my team, across multiple disciplines from Product and Data, to Software Developer, for context I'm the only software tester on my team, but not the only one doing testing.
+
+I've also used these techniques when setting up cross-team sessions, including even broader disciplines such as medical knowledge, quality, and safety.
+
+## Agree on the mission
+
+Setting up the scope for a session is even more important when working with others. The trick is finding the right scope, one that narrows your focus so you don't get lost while giving you enough freedom to explore.
+
+I often follow the Test Charter format, from Explore It! (https://www.oreilly.com/library/view/explore-it/9781941222584/) by Elisabeth Hendrickson (https://www.linkedin.com/in/testobsessed/):
+
+Explore \ using \ to discover \
+
+What I have found useful, is getting ideas from the person or group I will be collaborating with, and then formatting it into a charter and sharing it back, making adjustments until we agree.
+
+This usually only takes a few minutes, and if we come up with multiple we can also set up more sessions. I found this works better than trying to coach people to write in the charter format, at least until people have done a few sessions and get used to the concept.
+
+## Make time and space
+
+How long it takes to do a valuable session of testing varies depending on the group and the work, typically I've found 45 to 90 mins is a good range.
+
+Any more than 90 mins and I would highly recommend taking a break and splitting up into multiple sessions.
+
+Make sure to block time in calendars, and pick a time everyone can comfortably make, when working across time zones beware of lunchtime.
+
+If you're lucky enough to be co-located in an office, make sure to book an appropriate working space and give people time to come along, and set up. Usually, either one screen, keyboard and mouse, or a screen share when remote, works best.
+
+## Bring together the right people
+
+Small groups work well, think 2-5 people. Try out different testing sessions with different mixes of people, to get a broader and more devise view of the software, you might be surprised by the things you find that you might have missed on your own.
+
+People I often invite to testing sessions, and why:
+
+1\. The developers who worked on the feature. I find involving them in the testing gives a much shorter feedback cycle, and they learn things to check for themselves in the future. I also learn a lot from them about the software and they tend to be great at configuring it to do useful things, like extra logging.
+
+2\. Domain specialists, in my case this often means Medical Quality, obviously this is specific to my domain, and your specialists might be different.
+
+3\. Open invite to my whole team. Sometimes I simply book a slot in our team calendar for testing a feature and invite the whole team as optional attendees. The great thing about this is, everyone feels included, and anyone who turns up is self-selected, and invested in joining in.
+
+4\. Product Manager. I find this one especially useful when I'm trying to discover if a flow or scenario has sufficiently low friction from a user-facing point of view. If my Product Manager is surprised by a flow, there is probably a missing story and we can raise it there and then.
+
+5\. Other, related, teams. I find it very useful to test with other teams that are responsible for shared components or might be impacted by our team's work. In my context, another team is primarily responsible for our Mobile App, which we contribute new features to.
+
+Again, I don't invite everyone to every session, but rather I try and guess who might be useful, and interested. Try not to limit yourself, rather hold more sessions and invite more people as an experiment, until you find what works well. Mixing things up to bring in fresh eyes can also be useful, there is no need to stick to the same group each time.
+
+## Setup the software
+
+In my context, typically either I run the software that is being tested, or I invite one of the developers who is joining the session to run it.
+
+For me, this usually requires some upfront work, to pull the right branch, build the right version and start the right complementary docker compose.
+
+If you can, give yourself time before the session to get things up and running and document your configuration. This will save you time, so you can focus on your mission.
+
+If you're using a shared environment, or someone else will be running things locally, make sure they have time before the session to set things up and agree on what versions you will be testing against.
+
+A final tip, make sure to turn on whatever level of logging you need, and remember to load up tools that can help you observe and manipulate the software and the environment it's running in. This could include an HTTP client, a proxy tool, or a Database Client.
+
+## Take notes
+
+I find it challenging to facilitate a session, drive the software and take all the notes myself, so I like to ask the group to help me out.
+
+A favor of "multi-player" text editors, such as confluence, in a pinch a Google Doc would work as well. If needed, you can tidy up the notes and throw them in an official tool later.
+
+You probably don't need to write down every thought, and everything you do. You will want to capture enough detail of the steps you take, your expectations, and your observations to make meaningful conclusions.
+
+I like to pull out the key items covered, findings, and action points to a summary at the top of the notes. This makes them more management friendly and supports debriefing with anyone in the team who wasn't involved.
+
+## Choose your own adventure
+
+At regular intervals during the session, I find it useful to take a moment to re-state the mission and choose what to do next.
+
+Use what you've learned so far, to help you come up with a few ideas for what to do next, and together pick a path and follow it.
+
+I find it very useful to use these short pauses to bring in anyone who hasn't spoken for a while.
+
+Keep picking new paths until your time-box is up. If there is more to learn, plan another session.
+
+## Group reflection
+
+Making time, about 5-10 minutes, at the end of the session to reflect is a great way to practice continuous improvement.
+
+When working with groups who were not traditional software testers, I found writing down the reflections very powerful.
+
+Across a few months of working with a group of talented Medical Knowledge Engineers (Doctors who code), I picked up on some themes:
+
+* Working collaboratively was a lot of fun, they liked the social aspect
+* Bringing multiple points of view reduced potential biases from testing alone
+* They learned a lot from observing how others test
+* There is huge value in thinking aloud as we tested
+* The opportunity for domain knowledge sharing was appreciated and valuable
+
+## Go forth, and test together!
+
+In summary, I strongly encourage you to go forth and form some groups and practice collaborative testing.
+
+* Agree on a mission
+* Invite 2-5 people
+* Setup the software
+* Take notes
+* Share an adventure
+* Reflect on the experience
+
+## Other resources
+
+Not for the first time, I'm going to call out [Lisi Hocke's](https://www.linkedin.com/in/lisihocke/) excellent list of collaboration resources, especially the section on working in an Ensemble.
+
+[https://www.lisihocke.com/p/collaboration.html#ensemble](https://www.lisihocke.com/p/collaboration.html#ensemble)
+
+Explore It? Explore It! by Elisabeth Hendrickson
+
+[https://youtu.be/9FKY1Is0lgs](https://youtu.be/9FKY1Is0lgs) \[Video]
+
+[https://www.oreilly.com/library/view/explore-it/9781941222584/](https://www.oreilly.com/library/view/explore-it/9781941222584/) \[Book]
+
+[Hero image, Photo by Canva Studio](https://www.pexels.com/photo/man-in-black-crew-neck-t-shirt-sitting-beside-woman-in-gray-crew-neck-t-shirt-3153201/)
diff --git a/_posts/2023-09-01-zooming-in-and-out.md b/_posts/2023-09-01-zooming-in-and-out.md
new file mode 100644
index 0000000000000..93536881d568c
--- /dev/null
+++ b/_posts/2023-09-01-zooming-in-and-out.md
@@ -0,0 +1,69 @@
+---
+layout: post
+title: Zooming in and out
+date: 2023-09-04T23:00:00.000Z
+draft: false
+categories: Testing
+tags:
+ - models
+ - systems analysis
+ - systems thinking
+image: /uploads/pexels-ethan-sees-2853432.jpg
+---
+
+Over my career in Software Testing, I've had the pleasure to analyze and model a lot of systems. Some of them have had tons of formal architecture models and others have had little more than a few epics and user stories held together by smart engineers and sticky tape.
+
+One of the things I've found useful over that time is zooming in and zooming out. That is, thinking about each part of the system to a different depth, and drawing different scopes that include more or less of the bigger picture.
+
+## Zooming in
+
+Software systems are made up of many moving parts, and each one of those parts can have its own complications. Exploring the depth of each component can help you find quality issues and areas for improvement that bring benefits across the whole platform.
+
+### How deep can you go?
+
+There are many ways you can go deeper into a single service that is part of a bigger system. Depending on the context, you could:
+
+* Investigate calls to an API, dig into every possible header and body option, and follow each path until it either computes and outputs, fetches something from a database, or writes back to one.
+* Identify each 3rd party API the service calls, what information are you providing to the API and what is returned? Read the docs for the 3rd party API, are there options you are not using?
+* Find the key internal methods of the system, can you follow the logic? Try reading the unit tests, or even modify the unit tests to explore even further.
+* Do the Dev's have a profiling tool, so you can look at exactly where processing time and memory are spent?
+ From a modeling point of view, drawing the major behaviors, inputs, outputs, and dependencies can be useful. Pay attention to interactions with other services, databases, and the use of third-party libraries or imported dependencies.
+* Finally, dig into configurations, and environment variables. Identify what configuration is used in different deployments, like local, dev, vs production.
+
+### Questions you can ask
+
+* How can we configure the service to run with the highest level of logging, say debug or trace?
+* What dependencies, either from third parties or other teams, does the service rely on?
+* Can you trigger failure modes, and observe what would happen if dependent services were unavailable or invalid input was provided?
+* What would happen if I/O (reads and writes) didn't respond in time? This could be databases, file systems, or calls to other services.
+
+## Zooming out
+
+While many small parts make the whole, how they are connected together, the purpose, scope, and scale of the wider system is critically important. Often, it's easy to miss the bigger picture when your team is focused on contributing an individual service. You might want to pair up with systems architects, testers, and software developers from other teams to model and test across team boundaries.
+
+While traditionally, centralized test teams or systems integration teams might have handled this task, now teams seem hyper-focused on avoiding the need to interact with the whole system. While mitigating work, like contract tests, can help individual integrations, having a wide systems overview at some point can bring benefits to overall quality.
+
+### How wide to go
+
+This is where context really matters, even more than when zooming in. In order to zoom out the furthest you can go, you might need to go beyond your comfort zone.
+
+I've taken the time to look at parts of the system built and operated by other teams, 3rd party services, and even our customer's systems. It has brought benefits from gaining a greater understanding than I could ever have had if I had self-limited myself to the systems my team works on directly.
+So, how far can you?
+
+* Gather any system documentation you can find, you will likely need to speak with other development teams, and maybe other functions like operations, support, or customer success.
+* Pair up with a team that handles one of the other services, that your teams work interacts with. Together, you might find out-of-date documentation, missing knowledge, and concepts that have been misunderstood.
+* Think about parts, or collections of system functions or services that work together to accomplish a wider goal, what is that goal? Are there gaps in testing for it?
+* Look at system logging, can you trace when one system hands off to another? What about if the customer's data goes to, or comes from a third party, can you see it in the logs?
+* How much of the wider system is available in your testing environments? What about running locally?
+* Do you have system-level automation tests that cover key flows, are they up to date? What do they actually cover?
+* Are there exit points in your system, where you or your users interact with the real world? e.g if your system delivers flowers, do they arrive fresh? How quickly would you know if the delivery was missed, and the poor flowers were degrading in quality sat in a sorting office?
+
+### Questions you can ask
+
+* What patterns and tools are you using to communicate between different parts of your system? Is it all HTTP requests, or are there events and message queues?
+* What marketing tools and middleware are you using? How are these integrated into your systems, and who is responsible for adding or updating events when you introduce new features?
+* What analytics and data tracking are you using, both for observability intro production performance and to understand how your users use the system? Who is implementing these events, and who is analyzing the results? Can you use the event data to make a judgment on quality? Or maybe understand if an experiment is working?
+* Are there multiple services that rely on common dependencies, say a version of Java or Node? are they all equally up to date, or is there a mix of versions being used? Could this be a problem?
+* What combination of versions of each part of the system have been tested together? Has the combination that hits production next been fully tested as it will be deployed?\* What does the Long Term Support look like for the versions of your dependencies look like?\* Hosted database systems such as MongoDB, or infrastructure elements like Kubernetes have ever-increasing minimum versions, when are the current versions end of life?
+* What maintenance work is planned for the underlying infrastructure? Is that even under your control?
+* Who is responsible for handling service arrangements, contracts, payments etc with your providers? If the production Database goes down, do you know who to call? And do THEY know who to escalate it to?
diff --git a/_posts/_draft_2024-06-19-help-your-team-learn-test-automation.md b/_posts/_draft_2024-06-19-help-your-team-learn-test-automation.md
new file mode 100644
index 0000000000000..73e975644bf81
--- /dev/null
+++ b/_posts/_draft_2024-06-19-help-your-team-learn-test-automation.md
@@ -0,0 +1,22 @@
+---
+layout: post
+title: Help your team learn test automation
+date: 2024-06-18T23:00:00.000Z
+draft: true
+categories: How to
+tags:
+ - learning
+ - coaching
+ - leadership
+ - automation
+---
+
+I recently had a great conversation with a member of the software testing community, who works as a leader and wanted advice on how to help his team learn test automation. This is a summary of some of the advice I shared, that reflects my own experience in learning and helping others learn.
+
+1. An automation project is a wider topic than just the individuals who are going to learn how to design the tests and write the code. It involves investment from the whole team, and indeed the company. This could be in the form of paying for tools and infrastructure, but more likely it will be an investment in time. Time for people to up-skill and also time to implement successful automation itself.
+2. One of the biggest barriers I faced helping my teams start automating, was lack of will of management to invest in their learning and the construction of the automation itself. So don't miss the step of identifying who you need to align with, and taking time to understand the goals you're trying to hit, so you know what success looks like.
+3. Everybody learns differently, some of us like to simply be given a task, and jump straight in to doing real work, figuring out just what we need as we go. Others prefer to have read the manual, to understand the task and the theory and foundational knowledge first, and only then tackle the meaty problem. Both are relatable and can be supported, and it can be that people transition from one style to another as they gain confidence. Don't assume one size fits all here.
+4. Try and gather a collection of different possible learning material, and let your team experiment with learning in different ways. Give them time to experiment, in as safe a way as possible. Some of your team might feel brave enough to get help and support from a group, but others may prefer to pair 1:1 with a trusted person before they know enough to join a wider group setting.
+5. I found I learned the most, when I paired with someone experienced, such as a developer on my team, and completed real test automation tasks together, as part of our sprint. Sometimes I would lead, and take direction, other times my partner would lead and I would direct. Either way, I learned a huge amount, while seeing progress of doing meaningful work. This was very very effective, and honestly I recommend doing this not just for a few hours one off, but for multiple hours a day, for weeks. It's an excellent work of working and learning, I cannot stress enough how powerful and useful this was for both of us.
+
+Hero image: [Photo by Helena Lopes](https://www.pexels.com/photo/a-man-in-black-jacket-reading-a-book-3471028/)
diff --git a/_sass/_highlights.scss b/_sass/_highlights.scss
deleted file mode 100644
index 57c7b72f07617..0000000000000
--- a/_sass/_highlights.scss
+++ /dev/null
@@ -1,84 +0,0 @@
-
-.highlight {
- background-color: #efefef;
- padding: 7px 7px 7px 10px;
- border: 1px solid #ddd;
- -moz-box-shadow: 3px 3px rgba(0,0,0,0.1);
- -webkit-box-shadow: 3px 3px rgba(0,0,0,0.1);
- box-shadow: 3px 3px rgba(0,0,0,0.1);
- margin: 20px 0 20px 0;
- overflow: scroll;
-}
-
-code {
- font-family:'Bitstream Vera Sans Mono','Courier', monospace;
-}
-
-.highlight .c { color: #586E75 } /* Comment */
-.highlight .err { color: #93A1A1 } /* Error */
-.highlight .g { color: #93A1A1 } /* Generic */
-.highlight .k { color: #859900 } /* Keyword */
-.highlight .l { color: #93A1A1 } /* Literal */
-.highlight .n { color: #93A1A1 } /* Name */
-.highlight .o { color: #859900 } /* Operator */
-.highlight .x { color: #CB4B16 } /* Other */
-.highlight .p { color: #93A1A1 } /* Punctuation */
-.highlight .cm { color: #586E75 } /* Comment.Multiline */
-.highlight .cp { color: #859900 } /* Comment.Preproc */
-.highlight .c1 { color: #586E75 } /* Comment.Single */
-.highlight .cs { color: #859900 } /* Comment.Special */
-.highlight .gd { color: #2AA198 } /* Generic.Deleted */
-.highlight .ge { color: #93A1A1; font-style: italic } /* Generic.Emph */
-.highlight .gr { color: #DC322F } /* Generic.Error */
-.highlight .gh { color: #CB4B16 } /* Generic.Heading */
-.highlight .gi { color: #859900 } /* Generic.Inserted */
-.highlight .go { color: #93A1A1 } /* Generic.Output */
-.highlight .gp { color: #93A1A1 } /* Generic.Prompt */
-.highlight .gs { color: #93A1A1; font-weight: bold } /* Generic.Strong */
-.highlight .gu { color: #CB4B16 } /* Generic.Subheading */
-.highlight .gt { color: #93A1A1 } /* Generic.Traceback */
-.highlight .kc { color: #CB4B16 } /* Keyword.Constant */
-.highlight .kd { color: #268BD2 } /* Keyword.Declaration */
-.highlight .kn { color: #859900 } /* Keyword.Namespace */
-.highlight .kp { color: #859900 } /* Keyword.Pseudo */
-.highlight .kr { color: #268BD2 } /* Keyword.Reserved */
-.highlight .kt { color: #DC322F } /* Keyword.Type */
-.highlight .ld { color: #93A1A1 } /* Literal.Date */
-.highlight .m { color: #2AA198 } /* Literal.Number */
-.highlight .s { color: #2AA198 } /* Literal.String */
-.highlight .na { color: #93A1A1 } /* Name.Attribute */
-.highlight .nb { color: #B58900 } /* Name.Builtin */
-.highlight .nc { color: #268BD2 } /* Name.Class */
-.highlight .no { color: #CB4B16 } /* Name.Constant */
-.highlight .nd { color: #268BD2 } /* Name.Decorator */
-.highlight .ni { color: #CB4B16 } /* Name.Entity */
-.highlight .ne { color: #CB4B16 } /* Name.Exception */
-.highlight .nf { color: #268BD2 } /* Name.Function */
-.highlight .nl { color: #93A1A1 } /* Name.Label */
-.highlight .nn { color: #93A1A1 } /* Name.Namespace */
-.highlight .nx { color: #555 } /* Name.Other */
-.highlight .py { color: #93A1A1 } /* Name.Property */
-.highlight .nt { color: #268BD2 } /* Name.Tag */
-.highlight .nv { color: #268BD2 } /* Name.Variable */
-.highlight .ow { color: #859900 } /* Operator.Word */
-.highlight .w { color: #93A1A1 } /* Text.Whitespace */
-.highlight .mf { color: #2AA198 } /* Literal.Number.Float */
-.highlight .mh { color: #2AA198 } /* Literal.Number.Hex */
-.highlight .mi { color: #2AA198 } /* Literal.Number.Integer */
-.highlight .mo { color: #2AA198 } /* Literal.Number.Oct */
-.highlight .sb { color: #586E75 } /* Literal.String.Backtick */
-.highlight .sc { color: #2AA198 } /* Literal.String.Char */
-.highlight .sd { color: #93A1A1 } /* Literal.String.Doc */
-.highlight .s2 { color: #2AA198 } /* Literal.String.Double */
-.highlight .se { color: #CB4B16 } /* Literal.String.Escape */
-.highlight .sh { color: #93A1A1 } /* Literal.String.Heredoc */
-.highlight .si { color: #2AA198 } /* Literal.String.Interpol */
-.highlight .sx { color: #2AA198 } /* Literal.String.Other */
-.highlight .sr { color: #DC322F } /* Literal.String.Regex */
-.highlight .s1 { color: #2AA198 } /* Literal.String.Single */
-.highlight .ss { color: #2AA198 } /* Literal.String.Symbol */
-.highlight .bp { color: #268BD2 } /* Name.Builtin.Pseudo */
-.highlight .vc { color: #268BD2 } /* Name.Variable.Class */
-.highlight .vg { color: #268BD2 } /* Name.Variable.Global */
-.highlight .vi { color: #268BD2 } /* Name.Variable.Instance */
-.highlight .il { color: #2AA198 } /* Literal.Number.Integer.Long */
\ No newline at end of file
diff --git a/_sass/_reset.scss b/_sass/_reset.scss
deleted file mode 100644
index 120eebf95c9d3..0000000000000
--- a/_sass/_reset.scss
+++ /dev/null
@@ -1,53 +0,0 @@
-
-/***************/
-/* MEYER RESET */
-/***************/
-
-html, body, div, span, applet, object, iframe,
-h1, h2, h3, h4, h5, h6, p, blockquote, pre,
-a, abbr, acronym, address, big, cite, code,
-del, dfn, em, img, ins, kbd, q, s, samp,
-small, strike, strong, sub, sup, tt, var,
-b, u, i, center,
-dl, dt, dd, ol, ul, li,
-fieldset, form, label, legend,
-table, caption, tbody, tfoot, thead, tr, th, td,
-article, aside, canvas, details, embed,
-figure, figcaption, footer, header, hgroup,
-menu, nav, output, ruby, section, summary,
-time, mark, audio, video {
- margin: 0;
- padding: 0;
- border: 0;
- font-size: 100%;
- font: inherit;
- vertical-align: baseline;
-}
-// HTML5 display-role reset for older browsers
-article, aside, details, figcaption, figure,
-footer, header, hgroup, menu, nav, section {
- display: block;
-}
-body {
- line-height: 1;
-}
-ol, ul {
- list-style: none;
-}
-blockquote, q {
- quotes: none;
-}
-blockquote:before, blockquote:after,
-q:before, q:after {
- content: '';
- content: none;
-}
-table {
- border-collapse: collapse;
- border-spacing: 0;
-}
-// Apply a natural box layout model to all elements
-// from: http://www.paulirish.com/2012/box-sizing-border-box-ftw/
-*, *:before, *:after {
- -moz-box-sizing: border-box; -webkit-box-sizing: border-box; box-sizing: border-box;
-}
diff --git a/_sass/_svg-icons.scss b/_sass/_svg-icons.scss
deleted file mode 100644
index a62ab2a06fe7e..0000000000000
--- a/_sass/_svg-icons.scss
+++ /dev/null
@@ -1,20 +0,0 @@
-.svg-icon {
- width: 40px;
- height: 40px;
- display: inline-block;
-
- &.dribbble { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPjxwYXRoIGQ9Ik0wLjIyNDU4MDY4OCwzMCBDMC4yMjQ1ODA2ODgsMTMuNDMxNDU2NyAxMy40NTQ5NDEsMCAyOS43NzU0MTkzLDAgQzQ2LjA5NTg5NzYsMCA1OS4zMjYyNTc5LDEzLjQzMTQ1NjcgNTkuMzI2MjU3OSwzMCBDNTkuMzI2MjU3OSw0Ni41Njg1NDMzIDQ2LjA5NTg5NzYsNjAgMjkuNzc1NDE5Myw2MCBDMTMuNDU0OTQxLDYwIDAuMjI0NTgwNjg4LDQ2LjU2ODU0MzMgMC4yMjQ1ODA2ODgsMzAgWiBNMC4yMjQ1ODA2ODgsMzAiIGZpbGw9IiNFQTRDODkiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD48cGF0aCBkPSJNNDYuODIwMTQwMiwyOS44MzA2MzA3IEM0Ni44MjAxNDAyLDMwLjk5MTA2NjIgNDYuNzAzOTM4MSwzMi4xNDk4OTIgNDYuNDc1Njk1OCwzMy4yNzk0NzczIEM0Ni4yNTMxMzQ4LDM0LjM4MjIzNjMgNDUuOTIzNDg4MSwzNS40NjQ4NzU3IDQ1LjQ5MTY0NDQsMzYuNDk5ODMxNCBDNDUuMDY5NzA5OSwzNy41MTY0NzgzIDQ0LjU0NjM3MSwzOC40OTYxNzIgNDMuOTM0ODQwMiwzOS40MDk4MDYyIEM0My4zMzI0MjU4LDQwLjMxNzY3MjcgNDIuNjM4NDUwMiw0MS4xNjk0MDUzIDQxLjg3NjEwMSw0MS45NDU4MjM0IEM0MS4xMTIxMDAzLDQyLjcxODg4ODEgNDAuMjcxNDY4Myw0My40MjI0NzI5IDM5LjM3ODkxMiw0NC4wMzc1MzEyIEMzOC40NzczMDUzLDQ0LjY1NDkzNjcgMzcuNTEyMjc5Niw0NS4xODYyMzAxIDM2LjUxMTcxMjgsNDUuNjE3MTkzNCBDMzUuNDkyMjUyNSw0Ni4wNTM5MjQ0IDM0LjQyNDg5NzUsNDYuMzg4NTgxNSAzMy4zNDExNTk0LDQ2LjYxNDQ1ODMgQzMyLjIyODYxODUsNDYuODQ3MTA4OCAzMS4wODQ2MzIzLDQ2Ljk2NTg4MTkgMjkuOTQxNTcwOSw0Ni45NjU4ODE5IEMyOC43OTc2NTA4LDQ2Ljk2NTg4MTkgMjcuNjUzNzMwNyw0Ni44NDcxMDg4IDI2LjU0Mjc3NTIsNDYuNjE0NDU4MyBDMjUuNDU3Mzg1NSw0Ni4zODg1ODE1IDI0LjM5MDA5NjcsNDYuMDUzOTI0NCAyMy4zNzE0MjkxLDQ1LjYxNzE5MzQgQzIyLjM3MDkyODQsNDUuMTg2MjMwMSAyMS40MDQ5Nzc4LDQ0LjY1NDkzNjcgMjAuNTAzMzcxMSw0NC4wMzc1MzEyIEMxOS42MTA4MTQ4LDQzLjQyMjU0IDE4Ljc3MDE4MjgsNDIuNzE4ODg4MSAxOC4wMDc4MzM2LDQxLjk0NTgyMzQgQzE3LjI0NDY5MTcsNDEuMTY5NDA1MyAxNi41NTA3MTYxLDQwLjMxNzY3MjcgMTUuOTQ3NDQyOSwzOS40MDk4MDYyIEMxNS4zMzkyMTUxLDM4LjQ5NjE3MiAxNC44MTUwMTc1LDM3LjUxNjQxMTIgMTQuMzkxNDMxNCwzNi40OTk4MzE0IEMxMy45NTk1MjE2LDM1LjQ2NDg3NTcgMTMuNjI5MDgyMywzNC4zODIxNjkyIDEzLjQwNTcyODUsMzMuMjc5NDc3MyBDMTMuMTc5OTMwNCwzMi4xNDk4OTIgMTMuMDY0NTIxMSwzMC45OTEwNjYyIDEzLjA2NDUyMTEsMjkuODMwNjMwNyBDMTMuMDY0NTIxMSwyOC42NjkzMjM1IDEzLjE3OTg2NDQsMjcuNTA4MDE2MiAxMy40MDU3OTQ1LDI2LjM4MDkxMjMgQzEzLjYyOTE0ODMsMjUuMjc4MTUzMyAxMy45NTk1ODc3LDI0LjE5MzgzNzMgMTQuMzkxNDk3NSwyMy4xNjA1NTgyIEMxNC44MTUwODM1LDIyLjE0MzE3MzYgMTUuMzM5MjgxMiwyMS4xNjI2MDggMTUuOTQ3NTA5LDIwLjI0ODkwNjggQzE2LjU1MDc4MjIsMTkuMzQwMzAyNSAxNy4yNDQ3NTc3LDE4LjQ5MDE3OTUgMTguMDA3ODk5NiwxNy43MTI4ODk2IEMxOC43NzAyNDg4LDE2LjkzOTc1NzggMTkuNjEwODgwOCwxNi4yMzc4NDk2IDIwLjUwMzQzNzEsMTUuNjIzNzMwMyBDMjEuNDA1MDQzOCwxNS4wMDM3MDkyIDIyLjM3MDk5NDQsMTQuNDcyNDgyOCAyMy4zNzE0OTUxLDE0LjA0MDcxNDcgQzI0LjM5MDE2MjcsMTMuNjAzMDQ0OSAyNS40NTczODU1LDEzLjI2NzU4MjkgMjYuNTQyODQxMywxMy4wNDMzODI4IEMyNy42NTM3OTY3LDEyLjgxMjQ3NiAyOC43OTc3MTY5LDEyLjY5NTMxMjUgMjkuOTQxNjM3LDEyLjY5NTMxMjUgQzMxLjA4NDY5ODMsMTIuNjk1MzEyNSAzMi4yMjg2MTg1LDEyLjgxMjQ3NiAzMy4zNDEyMjU1LDEzLjA0MzM4MjggQzM0LjQyNDk2MzYsMTMuMjY3NjUgMzUuNDkyMjUyNSwxMy42MDMxMTIgMzYuNTExNzc4OSwxNC4wNDA3MTQ3IEMzNy41MTIyNzk2LDE0LjQ3MjQxNTggMzguNDc3MzcxNCwxNS4wMDM3MDkyIDM5LjM3ODk3ODEsMTUuNjIzNzMwMyBDNDAuMjcxNTM0NCwxNi4yMzc4NDk2IDQxLjExMjIzMjQsMTYuOTM5NzU3OCA0MS44NzYxNjcxLDE3LjcxMjg4OTYgQzQyLjYzODUxNjMsMTguNDkwMTc5NSA0My4zMzI0OTE4LDE5LjM0MDMwMjUgNDMuOTM0OTA2MiwyMC4yNDg5MDY4IEM0NC41NDYzNzEsMjEuMTYyNjA4IDQ1LjA2OTcwOTksMjIuMTQzMjQwNyA0NS40OTE2NDQ0LDIzLjE2MDU1ODIgQzQ1LjkyMzQ4ODEsMjQuMTkzODM3MyA0Ni4yNTMxMzQ4LDI1LjI3ODE1MzMgNDYuNDc1Njk1OCwyNi4zODA5MTIzIEM0Ni43MDM5MzgxLDI3LjUwODAxNjIgNDYuODIwMTQwMiwyOC42NjkzMjM1IDQ2LjgyMDE0MDIsMjkuODMwNjMwNyBaIE0yMy43OTE3MTIsMTYuNTk1MTA3OSBDMTkuNzcyMjY5LDE4LjUyMjAzNTYgMTYuNzcyMzUyMywyMi4yODIwNjY0IDE1LjgzNjkyMjEsMjYuODEzNTUyMyBDMTYuMjE2OTA3NiwyNi44MTY5MDU2IDIyLjIyMzM0NzEsMjYuODkzODk2OCAyOS4xNDM3NDY4LDI1LjAyNzE5NCBDMjYuNjQ5MDY4MSwyMC41Mjc0OTcxIDIzLjk4Mzc1MjcsMTYuODU1Mzg5MyAyMy43OTE3MTIsMTYuNTk1MTA3OSBaIE0zMC4zMzc5Mzk3LDI3LjI4MDQ2MjcgQzIyLjkxNjQ2MzgsMjkuNTM2MDc4OCAxNS43OTQ5MDcsMjkuMzczNzgwMSAxNS41Mzk0NDc0LDI5LjM2Mzc4NzMgQzE1LjUzNTI4NTUsMjkuNTIxMDU2MSAxNS41Mjc4ODY2LDI5LjY3MzI5NDkgMTUuNTI3ODg2NiwyOS44MzA2MzA3IEMxNS41Mjc4ODY2LDMzLjU4OTc4OTYgMTYuOTI0ODIyMSwzNy4wMTY4Mzk5IDE5LjIyMDkyMDEsMzkuNjA4MTE5MSBDMTkuMjE1OTY1NCwzOS42MDA1NDA2IDIzLjE2MDQyODgsMzIuNDk2Mjg1NiAzMC45Mzg3Njg2LDI5Ljk0Mjc2NDMgQzMxLjEyNjY0NzQsMjkuODc5MTg2MiAzMS4zMTc4OTUzLDI5LjgyMjI0NzUgMzEuNTA3NDI1NiwyOS43NjcwNTI2IEMzMS4xNDU2NzMsMjguOTM1NDM5NiAzMC43NTA4MjM3LDI4LjEwMjA4MjkgMzAuMzM3OTM5NywyNy4yODA0NjI3IFogTTM5LjQ2MDU2NCwxOC44NDgzMDk2IEMzNi45MjI5NDU0LDE2LjU3NjY2NDkgMzMuNTkwOTM3OCwxNS4xOTg3MzU4IDI5Ljk0MTU3MDksMTUuMTk4NzM1OCBDMjguNzcwNDMzNSwxNS4xOTg3MzU4IDI3LjYzMzkxMjIsMTUuMzQyNjU4NSAyNi41NDUyMTk1LDE1LjYwODcwNzYgQzI2Ljc2MTEwODMsMTUuOTAzMjU5NSAyOS40Njg1MDQ5LDE5LjU0OTQ4IDMxLjkzMzUyMTksMjQuMTQ0NDc3IEMzNy4zNzIxNjMyLDIyLjA3NDU2NTUgMzkuNDI1MDg5LDE4LjkwMTgyNzkgMzkuNDYwNTY0LDE4Ljg0ODMwOTYgWiBNMzIuNDg5ODI1NCwzMi4xOTE3NDA5IEMzMi40NTc3MTk2LDMyLjIwMjUzODUgMzIuNDI1NjEzNywzMi4yMTE4NjA2IDMyLjM5NDIzNDUsMzIuMjIzNTMgQzIzLjg4OTkyNDgsMzUuMjMzMzIxNiAyMS4xMTI3MjcyLDQxLjI5ODkxNTEgMjEuMDgyNjc5Myw0MS4zNjUxMjg2IEMyMy41Mjk2NDYyLDQzLjI5Njk5MzIgMjYuNTk4Nzk1Myw0NC40NjI1MjU2IDI5Ljk0MTU3MDksNDQuNDYyNTI1NiBDMzEuOTM3NjE3OCw0NC40NjI1MjU2IDMzLjgzODkzMjUsNDQuMDQ5OTM4MyAzNS41Njg4MTc3LDQzLjMwMjg5NSBDMzUuMzU1MzczMSw0Mi4wMjQ0MjQyIDM0LjUxODA0NDIsMzcuNTQzMTcwNCAzMi40ODk4MjU0LDMyLjE5MTc0MDkgWiBNMzcuOTk2MDQ3Niw0MS45NjU4NzYgQzQxLjIzMjQ2NDMsMzkuNzQ4Njg4NSA0My41MzEwMDY1LDM2LjIyNzk0NzYgNDQuMTcyMTk5LDMyLjE0OTgyNDkgQzQzLjg3NTUxNywzMi4wNTI3ODExIDM5Ljg0MjkyNzcsMzAuNzU2NzM5MSAzNS4xOTA1NDk4LDMxLjUxMzk3NjMgQzM3LjA4MTE2MjUsMzYuNzg4NDgxNiAzNy44NDkzMjUxLDQxLjA4NDAzMDkgMzcuOTk2MDQ3Niw0MS45NjU4NzYgWiBNMzMuMDQyODkxOSwyNi4zMjQ5MTI2IEMzMy4zNzc0MjcxLDI3LjAyMjcyOTggMzMuNzAxMzkyNSwyNy43MzI5NTQxIDM0LjAwMDUxODgsMjguNDQ2NzMyOSBDMzQuMTA2ODc3NywyOC43MDI3ODkyIDM0LjIxMDcyNjMsMjguOTUzODE1NiAzNC4zMTIwNjQ2LDI5LjIwNDc3NDkgQzM5LjI2MzU2ODcsMjguNTcyMjEyNSA0NC4xNDE3NDQ2LDI5LjYzNjQ3NTkgNDQuMzUwMzAwNiwyOS42Nzk5MzQ0IEM0NC4zMTczMzYsMjYuMjExMTAyMyA0My4wOTUwNjcsMjMuMDI3NTAwMSA0MS4wNzI2NjE2LDIwLjUzNTA3NTUgQzQxLjA0NTQ0NDMsMjAuNTc0MzA4OSAzOC43MzM2ODk4LDIzLjk2NTQxMiAzMy4wNDI4OTE5LDI2LjMyNDkxMjYgWiBNMzMuMDQyODkxOSwyNi4zMjQ5MTI2IiBpZD0iUGF0aCIgZmlsbD0iI0ZGRkZGRiIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPjxwYXRoIGQ9Ik01OS4zMjYyNTc5LDMwIEM1OS4zMjYyNTc5LDQ2LjU2ODU0MzMgNDYuMDk1ODk3Niw2MCAyOS43NzU0MTkzLDYwIEMyMy43MjI1NDA1LDYwIDE4LjA5NDcwNTEsNTguMTUyNTEzNCAxMy40MDkzMjQ0LDU0Ljk4Mjc3NTQgTDQ3LjI2OTU0NTgsNS44MTk0MTEwMyBDNTQuNTgxNDQzOCwxMS4yODA2NTAzIDU5LjMyNjI1NzksMjAuMDc3Nzk3MyA1OS4zMjYyNTc5LDMwIFogTTU5LjMyNjI1NzksMzAiIGlkPSJyZWZsZWMiIGZpbGwtb3BhY2l0eT0iMC4wOCIgZmlsbD0iIzAwMDAwMCIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPjwvc3ZnPgo=); }
- &.email { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPg0KICAgIDxwYXRoIGQ9Ik0wLjIyNDU4MDY4OCwzMCBDMC4yMjQ1ODA2ODgsMTMuNDMxNDU2NyAxMy40NTQ5NDEsMCAyOS43NzU0MTkzLDAgQzQ2LjA5NTg5NzYsMCA1OS4zMjYyNTc5LDEzLjQzMTQ1NjcgNTkuMzI2MjU3OSwzMCBDNTkuMzI2MjU3OSw0Ni41Njg1NDMzIDQ2LjA5NTg5NzYsNjAgMjkuNzc1NDE5Myw2MCBDMTMuNDU0OTQxLDYwIDAuMjI0NTgwNjg4LDQ2LjU2ODU0MzMgMC4yMjQ1ODA2ODgsMzAgWiBNMC4yMjQ1ODA2ODgsMzAiIGZpbGw9IiNGRkZGRkYiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCiAgICA8cGF0aCBkPSJNMzUuMDM4NDMyNCwzMS42Mzg0MDA2IEw0Ny4yMTMxMTQ4LDQwLjU3NjQyNjQgTDQ3LjIxMzExNDgsMjAgTDM1LjAzODQzMjQsMzEuNjM4NDAwNiBaIE0xMy43NzA0OTE4LDIwIEwxMy43NzA0OTE4LDQwLjU3NjQyNjQgTDI1Ljk0NDkxMjksMzEuNjM3MTQ5MSBMMTMuNzcwNDkxOCwyMCBaIE0zMC40OTE4MDMzLDM1Ljk4NDQ4OTEgTDI3LjU4NTEwMzcsMzMuMjA2NTIxNyBMMTMuNzcwNDkxOCw0MiBMNDcuMjEzMTE0OCw0MiBMMzMuMzk4MTc2MiwzMy4yMDY1MjE3IEwzMC40OTE4MDMzLDM1Ljk4NDQ4OTEgWiBNNDYuMjA5ODM2MSwyMCBMMTQuNzczNzcwNSwyMCBMMzAuNDkxODAzMywzMi40NTQ5MzA0IEw0Ni4yMDk4MzYxLDIwIFogTTQ2LjIwOTgzNjEsMjAiIGlkPSJTaGFwZSIgZmlsbD0iIzMzMzMzMyIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KICAgIDxwYXRoIGQ9Ik01OS4zMjYyNTc5LDMwIEM1OS4zMjYyNTc5LDQ2LjU2ODU0MzMgNDYuMDk1ODk3Niw2MCAyOS43NzU0MTkzLDYwIEMyMy43MjI1NDA1LDYwIDE4LjA5NDcwNTEsNTguMTUyNTEzNCAxMy40MDkzMjQ0LDU0Ljk4Mjc3NTQgTDQ3LjI2OTU0NTgsNS44MTk0MTEwMyBDNTQuNTgxNDQzOCwxMS4yODA2NTAzIDU5LjMyNjI1NzksMjAuMDc3Nzk3MyA1OS4zMjYyNTc5LDMwIFogTTU5LjMyNjI1NzksMzAiIGlkPSJyZWZsZWMiIGZpbGwtb3BhY2l0eT0iMC4wOCIgZmlsbD0iIzAwMDAwMCIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KPC9zdmc+); }
- &.facebook { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPg0KICAgIDxwYXRoIGQ9Ik0wLjExMjI5MDM0NCwzMCBDMC4xMTIyOTAzNDQsMTMuNDMxNDU2NyAxMy4zNDI2NTA2LDAgMjkuNjYzMTI5LDAgQzQ1Ljk4MzYwNzMsMCA1OS4yMTM5Njc2LDEzLjQzMTQ1NjcgNTkuMjEzOTY3NiwzMCBDNTkuMjEzOTY3Niw0Ni41Njg1NDMzIDQ1Ljk4MzYwNzMsNjAgMjkuNjYzMTI5LDYwIEMxMy4zNDI2NTA2LDYwIDAuMTEyMjkwMzQ0LDQ2LjU2ODU0MzMgMC4xMTIyOTAzNDQsMzAgWiBNMC4xMTIyOTAzNDQsMzAiIGZpbGw9IiMzQjU5OTgiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCgk8cGF0aCBkPSJNMzIuMTM0MTQ1Nyw0Ni4zMTk2NzI5IEwzMi4xMzQxNDU3LDI5Ljk5ODA4OTEgTDM2LjU2NTc1NjUsMjkuOTk4MDg5MSBMMzcuMTUzMDQwNiwyNC4zNzM1ODA5IEwzMi4xMzQxNDU3LDI0LjM3MzU4MDkgTDMyLjE0MTY3NSwyMS41NTg0NjA0IEMzMi4xNDE2NzUsMjAuMDkxNTAyIDMyLjI3ODc3MDcsMTkuMzA1NDcyMiAzNC4zNTEyMDYsMTkuMzA1NDcyMiBMMzcuMTIxNjY4NiwxOS4zMDU0NzIyIEwzNy4xMjE2Njg2LDEzLjY4MDMyNzEgTDMyLjY4OTQzMDQsMTMuNjgwMzI3MSBDMjcuMzY1NTk5NSwxMy42ODAzMjcxIDI1LjQ5MTc0OSwxNi40MDg4MTg3IDI1LjQ5MTc0OSwyMC45OTcyODM1IEwyNS40OTE3NDksMjQuMzc0MjE3OSBMMjIuMTczMjE3MywyNC4zNzQyMTc5IEwyMi4xNzMyMTczLDI5Ljk5ODcyNiBMMjUuNDkxNzQ5LDI5Ljk5ODcyNiBMMjUuNDkxNzQ5LDQ2LjMxOTY3MjkgTDMyLjEzNDE0NTcsNDYuMzE5NjcyOSBaIE0zMi4xMzQxNDU3LDQ2LjMxOTY3MjkiIGlkPSJQYXRoIiBmaWxsPSIjRkZGRkZGIiBza2V0Y2g6dHlwZT0iTVNTaGFwZUdyb3VwIj48L3BhdGg+DQoJPHBhdGggZD0iTTU5LjIxMzk2NzYsMzAgQzU5LjIxMzk2NzYsNDYuNTY4NTQzMyA0NS45ODM2MDczLDYwIDI5LjY2MzEyOSw2MCBDMjMuNjEwMjUwMiw2MCAxNy45ODI0MTQ3LDU4LjE1MjUxMzQgMTMuMjk3MDM0MSw1NC45ODI3NzU0IEw0Ny4xNTcyNTU0LDUuODE5NDExMDMgQzU0LjQ2OTE1MzQsMTEuMjgwNjUwMyA1OS4yMTM5Njc2LDIwLjA3Nzc5NzMgNTkuMjEzOTY3NiwzMCBaIE01OS4yMTM5Njc2LDMwIiBpZD0icmVmbGVjIiBmaWxsLW9wYWNpdHk9IjAuMDgiIGZpbGw9IiMwMDAwMDAiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCjwvc3ZnPg==); }
- &.flickr { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPg0KICAgIDxwYXRoIGQ9Ik0wLjMzNjg3MTAzMiwyOS41MDgxOTY3IEMwLjMzNjg3MTAzMiwxMy4yMTEyNjg5IDEzLjU2NzIzMTMsMCAyOS44ODc3MDk3LDAgQzQ2LjIwODE4OCwwIDU5LjQzODU0ODMsMTMuMjExMjY4OSA1OS40Mzg1NDgzLDI5LjUwODE5NjcgQzU5LjQzODU0ODMsNDUuODA1MTI0NiA0Ni4yMDgxODgsNTkuMDE2MzkzNCAyOS44ODc3MDk3LDU5LjAxNjM5MzQgQzEzLjU2NzIzMTMsNTkuMDE2MzkzNCAwLjMzNjg3MTAzMiw0NS44MDUxMjQ2IDAuMzM2ODcxMDMyLDI5LjUwODE5NjcgWiBNMC4zMzY4NzEwMzIsMjkuNTA4MTk2NyIgZmlsbD0iI0ZGMDA4NCIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KICAgIDxwYXRoIGQ9Ik0yMi40OTk5NzM1LDIzLjYwNjU1NzQgQzE4Ljk2Mzc2MzUsMjMuNjA2NTU3NCAxNi4wOTczMTgzLDI2LjQ2ODgwMTcgMTYuMDk3MzE4MywyOS45OTk5NDcyIEMxNi4wOTczMTgzLDMzLjUzMTE0NTUgMTguOTYzNzYzNSwzNi4zOTMzODk4IDIyLjQ5OTk3MzUsMzYuMzkzNDQyNiBDMjYuMDM2MjM2NSwzNi4zOTM0NDI2IDI4LjkwMjY4MTcsMzMuNTMxMTQ1NSAyOC45MDI2ODE3LDI5Ljk5OTk0NzIgQzI4LjkwMjY4MTcsMjYuNDY4ODAxNyAyNi4wMzYyODk0LDIzLjYwNjUwNDUgMjIuNDk5OTczNSwyMy42MDY1NTc0IFogTTIyLjQ5OTk3MzUsMjMuNjA2NTU3NCIgaWQ9IlBhdGgiIGZpbGw9IiNGRkZGRkYiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCiAgICA8cGF0aCBkPSJNMzEuODU3NzY1NiwyOS45OTk5NDcyIEMzMS44NTc3NjU2LDMzLjUzMTE0NTUgMzQuNzI0MjEwOCwzNi4zOTM0NDI2IDM4LjI2MDQyMDgsMzYuMzkzNDQyNiBDNDEuNzk2NzM2NiwzNi4zOTM0NDI2IDQ0LjY2MzEyOSwzMy41MzExNDU1IDQ0LjY2MzEyOSwyOS45OTk5NDcyIEM0NC42NjMxMjksMjYuNDY4ODU0NSA0MS43OTY2ODM3LDIzLjYwNjU1NzQgMzguMjYwNDIwOCwyMy42MDY1NTc0IEMzNC43MjQxNTc5LDIzLjYwNjU1NzQgMzEuODU3NzY1NiwyNi40Njg4NTQ1IDMxLjg1Nzc2NTYsMjkuOTk5OTQ3MiBaIE0zMy44MjY0MDAxLDMwIEMzMy44MjY0MDAxLDI3LjU1NTQ2MDggMzUuODA4MDkwNCwyNS41NzM3NzA1IDM4LjI1MjYyOTYsMjUuNTczNzcwNSBDNDAuNjk3MTY4OCwyNS41NzM3NzA1IDQyLjY3ODg1OTEsMjcuNTU1NDYwOCA0Mi42Nzg4NTkxLDMwIEM0Mi42Nzg4NTkxLDMyLjQ0NDUzOTIgNDAuNjk3MTY4OCwzNC40MjYyMjk1IDM4LjI1MjYyOTYsMzQuNDI2MjI5NSBDMzUuODA4MDkwNCwzNC40MjYyMjk1IDMzLjgyNjQwMDEsMzIuNDQ0NTM5MiAzMy44MjY0MDAxLDMwIFogTTMzLjgyNjQwMDEsMzAiIGlkPSJQYXRoIiBmaWxsPSIjRkZGRkZGIiBza2V0Y2g6dHlwZT0iTVNTaGFwZUdyb3VwIj48L3BhdGg+DQogICAgPHBhdGggZD0iTTU5LjIxMzk2NzYsMjkuNjg1ODI1MiBDNTkuMjEzOTY3Niw0NS45ODI3NTMxIDQ1Ljk4MzYwNzMsNTkuMTk0MDIxOSAyOS42NjMxMjksNTkuMTk0MDIxOSBDMjMuNjEwMjUwMiw1OS4xOTQwMjE5IDE3Ljk4MjQxNDcsNTcuMzc2ODIyIDEzLjI5NzAzNDEsNTQuMjU5MDQ2OSBMNDcuMTU3MjU1NCw1LjkwMTYzOTM0IEM1NC40NjkxNTM0LDExLjI3MzM1MDEgNTkuMjEzOTY3NiwxOS45MjYyODE2IDU5LjIxMzk2NzYsMjkuNjg1ODI1MiBaIE01OS4yMTM5Njc2LDI5LjY4NTgyNTIiIGlkPSJyZWZsZWMiIGZpbGwtb3BhY2l0eT0iMC4wOCIgZmlsbD0iIzAwMDAwMCIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KPC9zdmc+); }
- &.github { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPg0KICAgIDxwYXRoIGQ9Ik0wLjMzNjg3MTAzMiwzMCBDMC4zMzY4NzEwMzIsMTMuNDMxNDU2NyAxMy41NjcyMzEzLDAgMjkuODg3NzA5NywwIEM0Ni4yMDgxODgsMCA1OS40Mzg1NDgzLDEzLjQzMTQ1NjcgNTkuNDM4NTQ4MywzMCBDNTkuNDM4NTQ4Myw0Ni41Njg1NDMzIDQ2LjIwODE4OCw2MCAyOS44ODc3MDk3LDYwIEMxMy41NjcyMzEzLDYwIDAuMzM2ODcxMDMyLDQ2LjU2ODU0MzMgMC4zMzY4NzEwMzIsMzAgWiBNMC4zMzY4NzEwMzIsMzAiIGlkPSJHaXRodWIiIGZpbGw9IiMzMzMzMzMiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCiAgICA8cGF0aCBkPSJNMTguMjE4NDI0NSwzMS45MzU1NTY2IEMxOS42MDY4NTA2LDM0LjQ1MDc5MDIgMjIuMjg0NTI5NSwzNi4wMTU2NzY0IDI2LjgwMDcyODcsMzYuNDQ4NTE3MyBDMjYuMTU2MTAyMywzNi45MzY1MzM1IDI1LjM4MTc4NzcsMzcuODYzMDk4NCAyNS4yNzQ5ODU3LDM4LjkzNDI2MDcgQzI0LjQ2NDQzNDgsMzkuNDU3NDc0OSAyMi44MzQ3NTA2LDM5LjYyOTY2IDIxLjU2NzQzMDMsMzkuMjMxMDY1OSBDMTkuNzkxODQ2OSwzOC42NzE3MDIzIDE5LjExMTkzNzcsMzUuMTY0MjY0MiAxNi40NTMzMzA2LDM1LjY2MzY5NTkgQzE1Ljg3NzM2MjYsMzUuNzcyMTQ0IDE1Ljk5MTc5MzMsMzYuMTUwNzYwOSAxNi40ODk1NjcsMzYuNDcyMjk5OCBDMTcuMzAwMTE3OSwzNi45OTU1MTQxIDE4LjA2Mjk4OTQsMzcuNjUwMDA3NSAxOC42NTEzNTQxLDM5LjA0MzY2IEMxOS4xMDMzNTU0LDQwLjExMzg3MSAyMC4wNTMxMzA0LDQyLjAyNTk4MTMgMjMuMDU2OTM2OSw0Mi4wMjU5ODEzIEMyNC4yNDg5MjM2LDQyLjAyNTk4MTMgMjUuMDg0MjY3OSw0MS44ODMyODY1IDI1LjA4NDI2NzksNDEuODgzMjg2NSBDMjUuMDg0MjY3OSw0MS44ODMyODY1IDI1LjEwNzE1NCw0NC42MTQ0NjQ5IDI1LjEwNzE1NCw0NS42NzYxMTQyIEMyNS4xMDcxNTQsNDYuOTAwNDM1NSAyMy40NTA3NjkzLDQ3LjI0NTc1NjkgMjMuNDUwNzY5Myw0Ny44MzQ2MTA4IEMyMy40NTA3NjkzLDQ4LjA2NzY3OSAyMy45OTkwODMyLDQ4LjA4OTU1ODggMjQuNDM5NjQxNSw0OC4wODk1NTg4IEMyNS4zMTAyNjg1LDQ4LjA4OTU1ODggMjcuMTIyMDg4Myw0Ny4zNjQ2NjkzIDI3LjEyMjA4ODMsNDYuMDkxODMxNyBDMjcuMTIyMDg4Myw0NS4wODA2MDEyIDI3LjEzODI5OTMsNDEuNjgwNjU5OSAyNy4xMzgyOTkzLDQxLjA4NjA5ODIgQzI3LjEzODI5OTMsMzkuNzg1NjczIDI3LjgzNzI4MDMsMzkuMzczNzYwNyAyNy44MzcyODAzLDM5LjM3Mzc2MDcgQzI3LjgzNzI4MDMsMzkuMzczNzYwNyAyNy45MjQwNTcsNDYuMzE1Mzg2OSAyNy42NzA0MDIyLDQ3LjI0NTc1NjkgQzI3LjM3Mjg4MjMsNDguMzM5NzUwNCAyNi44MzYwMTE1LDQ4LjE4NDY4ODcgMjYuODM2MDExNSw0OC42NzI3MDQ5IEMyNi44MzYwMTE1LDQ5LjM5ODU0NTggMjkuMDE2ODcwNCw0OC44NTA1OTc4IDI5LjczOTY5MTEsNDcuMjU3MTcyNSBDMzAuMjk4NDk0NSw0Ni4wMTY2NzkxIDMwLjA1NDM3NTYsMzkuMjA3MjgzNCAzMC4wNTQzNzU2LDM5LjIwNzI4MzQgTDMwLjY1MDM2OSwzOS4xOTQ5MTY1IEMzMC42NTAzNjksMzkuMTk0OTE2NSAzMC42ODM3NDQ2LDQyLjMxMjMyMjIgMzAuNjYzNzE5Miw0My43MzczNjc1IEMzMC42NDI3NDAyLDQ1LjIxMjgzMTcgMzAuNTQyNjEzNCw0Ny4wNzkyNzk3IDMxLjQyMDg2OTIsNDcuOTU5MjMwOSBDMzEuOTk3NzkwNyw0OC41Mzc2MjA1IDMzLjg2ODczMyw0OS41NTI2NTYyIDMzLjg2ODczMyw0OC42MjUxNCBDMzMuODY4NzMzLDQ4LjA4NTc1MzYgMzIuODQzNjI0NSw0Ny42NDI0NDg1IDMyLjg0MzYyNDUsNDYuMTgzMTU2NCBMMzIuODQzNjI0NSwzOS40Njg4OTA1IEMzMy42NjE4MDQyLDM5LjQ2ODg5MDUgMzMuNTM4NzkxMSw0MS42NzY4NTQ3IDMzLjUzODc5MTEsNDEuNjc2ODU0NyBMMzMuNTk4ODY3Myw0NS43Nzg4NTQ0IEMzMy41OTg4NjczLDQ1Ljc3ODg1NDQgMzMuNDE4NjM4OSw0Ny4yNzMzNDQ2IDM1LjIxOTAxNTYsNDcuODk5Mjk5MSBDMzUuODU0MTA2MSw0OC4xMjA5NTE3IDM3LjIxMzkyNDUsNDguMTgwODgzNSAzNy4yNzc4MTUsNDcuODA4OTI1NyBDMzcuMzQxNzA1NSw0Ny40MzYwMTY3IDM1LjY0MDUwMjEsNDYuODgxNDA5NiAzNS42MjUyNDQ2LDQ1LjcyMzY3OTEgQzM1LjYxNTcwODgsNDUuMDE3ODE1NSAzNS42NTY3MTMxLDQ0LjYwNTkwMzIgMzUuNjU2NzEzMSw0MS41Mzc5NjUxIEMzNS42NTY3MTMxLDM4LjQ3MDAyNyAzNS4yNDM4MDg5LDM3LjMzNjA3OSAzMy44MDQ4NDI2LDM2LjQzMjM0NTMgQzM4LjI0NTcwODIsMzUuOTc2NjczMiA0MC45OTM5NTI3LDM0Ljg4MDY4MiA0Mi4zMzM3NDU4LDMxLjk0NTA2OTUgQzQyLjQzODM2MTksMzEuOTQ4NDk2NiA0Mi44NzkxNDkxLDMwLjU3Mzc3NDIgNDIuODIxOTgzNSwzMC41NzQyNDgyIEM0My4xMjIzNjQyLDI5LjQ2NTk4NTMgNDMuMjg0NDc0NCwyOC4xNTUwOTU3IDQzLjMxNjg5NjQsMjYuNjAyNTc2NCBDNDMuMzA5MjY3NywyMi4zOTMwNzk5IDQxLjI4OTU2NTQsMjAuOTA0Mjk3NSA0MC45MDE0NTQ2LDIwLjIwNTA5MyBDNDEuNDczNjA4MiwxNy4wMTgyNDI1IDQwLjgwNjA5NTYsMTUuNTY3NTEyMSA0MC40OTYxNzkxLDE1LjA2OTk4MjkgQzM5LjM1MTg3MTksMTQuNjYzNzc4NCAzNi41MTQ5NDM1LDE2LjExNDUwODggMzQuOTY1MzYwOCwxNy4xMzcxNTQ4IEMzMi40MzgzNDksMTYuMzk5ODk4NCAyNy4wOTgyNDg2LDE2LjQ3MTI0NTggMjUuMDk1NzEwOSwxNy4zMjc0MTQ2IEMyMS40MDA1NTIyLDE0LjY4NzU2MDggMTkuNDQ1Njk0LDE1LjA5MTg2MjggMTkuNDQ1Njk0LDE1LjA5MTg2MjggQzE5LjQ0NTY5NCwxNS4wOTE4NjI4IDE4LjE4MjE4ODEsMTcuMzUxMTk3IDE5LjExMTkzNzcsMjAuNjU2OTU5OCBDMTcuODk2MTExMywyMi4yMDI4MjAxIDE2Ljk5MDIwMTQsMjMuMjk2ODEzNiAxNi45OTAyMDE0LDI2LjE5NjM3MTggQzE2Ljk5MDIwMTQsMjcuODI5NzUxNiAxNy4xODI4MjY0LDI5LjI5MTg5NzYgMTcuNjE3NjYzMiwzMC41Njg1NDA0IEMxNy41NjQzNTc3LDMwLjU2ODQwOTMgMTguMjAwODQ5MywzMS45MzU5Nzc3IDE4LjIxODQyNDUsMzEuOTM1NTU2NiBaIE0xOC4yMTg0MjQ1LDMxLjkzNTU1NjYiIGlkPSJQYXRoIiBmaWxsPSIjRkZGRkZGIiBza2V0Y2g6dHlwZT0iTVNTaGFwZUdyb3VwIj48L3BhdGg+DQogICAgPHBhdGggZD0iTTU5LjQzODU0ODMsMzAgQzU5LjQzODU0ODMsNDYuNTY4NTQzMyA0Ni4yMDgxODgsNjAgMjkuODg3NzA5Nyw2MCBDMjMuODM0ODMwOCw2MCAxOC4yMDY5OTU0LDU4LjE1MjUxMzQgMTMuNTIxNjE0OCw1NC45ODI3NzU0IEw0Ny4zODE4MzYxLDUuODE5NDExMDMgQzU0LjY5MzczNDEsMTEuMjgwNjUwMyA1OS40Mzg1NDgzLDIwLjA3Nzc5NzMgNTkuNDM4NTQ4MywzMCBaIE01OS40Mzg1NDgzLDMwIiBpZD0icmVmbGVjIiBmaWxsLW9wYWNpdHk9IjAuMDgiIGZpbGw9IiMwMDAwMDAiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCjwvc3ZnPg==); }
- &.instagram { background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9Im5vIj8+Cjxzdmcgd2lkdGg9IjQwcHgiIGhlaWdodD0iNDBweCIgdmlld0JveD0iMCAwIDYwIDYwIiB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHhtbG5zOnNrZXRjaD0iaHR0cDovL3d3dy5ib2hlbWlhbmNvZGluZy5jb20vc2tldGNoL25zIj4KICAgIDx0aXRsZT5JbnN0YWdyYW08L3RpdGxlPgogICAgPGRlc2NyaXB0aW9uPkNyZWF0ZWQgd2l0aCBTa2V0Y2ggKGh0dHA6Ly93d3cuYm9oZW1pYW5jb2RpbmcuY29tL3NrZXRjaCk8L2Rlc2NyaXB0aW9uPgogICAgPGRlZnM+PC9kZWZzPgogICAgPGcgaWQ9IlBhZ2UtMSIgc3Ryb2tlPSJub25lIiBzdHJva2Utd2lkdGg9IjEiIGZpbGw9Im5vbmUiIGZpbGwtcnVsZT0iZXZlbm9kZCIgc2tldGNoOnR5cGU9Ik1TUGFnZSI+CiAgICAgICAgPGcgaWQ9Ikluc3RhZ3JhbSIgc2tldGNoOnR5cGU9Ik1TQXJ0Ym9hcmRHcm91cCI+CiAgICAgICAgICAgIDxnIHNrZXRjaDp0eXBlPSJNU0xheWVyR3JvdXAiPgogICAgICAgICAgICAgICAgPHBhdGggZD0iTTAuNzg2MDMyNDA4LDMwIEMwLjc4NjAzMjQwOCwxMy40MzE0NTY3IDE0LjAxNjM5MjcsMCAzMC4zMzY4NzEsMCBDNDYuNjU3MzQ5NCwwIDU5Ljg4NzcwOTcsMTMuNDMxNDU2NyA1OS44ODc3MDk3LDMwIEM1OS44ODc3MDk3LDQ2LjU2ODU0MzMgNDYuNjU3MzQ5NCw2MCAzMC4zMzY4NzEsNjAgQzE0LjAxNjM5MjcsNjAgMC43ODYwMzI0MDgsNDYuNTY4NTQzMyAwLjc4NjAzMjQwOCwzMCBaIE0wLjc4NjAzMjQwOCwzMCIgZmlsbD0iIzUxN0ZBNCIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPgogICAgICAgICAgICAgICAgPHBhdGggZD0iTTQyLjgyNjkyMzEsNDUuMTcxNzkxNyBDNDQuMDU0MTA5Myw0NC45MDczNzc3IDQ1LjA1Njg4MzQsNDMuODY4MDE2OSA0NS4yOTY3NDI2LDQyLjYxNDc3MjcgQzQ1LjMyMjQ4NzcsNDIuNDc5Mjk4NiA0NS4zNDEzNjc1LDQyLjM0MTY0NjQgNDUuMzYzMjUwOSw0Mi4yMDU3MzY3IEw0NS4zNjMyNTA5LDE3Ljc5NDI2MzMgQzQ1LjM0MjIyNTcsMTcuNjYwNTMxNiA0NS4zMjQyMDQxLDE3LjUyNjM2NDMgNDUuMjk4NDU4OSwxNy4zOTMwNjgzIEM0NS4wMzU0MjkxLDE2LjAyNTY5NDcgNDMuOTI0NTI1MywxNC45NjQ1NTM2IDQyLjU2MDQ2MDYsMTQuNzc1MDY0MSBDNDIuNTAzODIxMywxNC43Njc2NTg4IDQyLjQ0ODQ2OTIsMTQuNzU1MDI2MSA0Mi4zOTI2ODgsMTQuNzQ1MDA3MSBMMTguMjgxMDU0MSwxNC43NDUwMDcxIEMxOC4xMzU1OTM5LDE0Ljc3MTU3OTIgMTcuOTg5Mjc1NSwxNC43OTE2MTcyIDE3Ljg0NTk2MDgsMTQuODI0NzIzNCBDMTYuNTE0NTA2NywxNS4xMzI2OTgzIDE1LjUyOTMyNTEsMTYuMjIxMjgyNyAxNS4zMzk2NjksMTcuNTkwODM0MyBDMTUuMzMxOTQ1NSwxNy42NDc4OTkgMTUuMzIwMzYwMSwxNy43MDQ1MjggMTUuMzEwNDkxMiwxNy43NjE1OTI3IEwxNS4zMTA0OTEyLDQyLjIzOTcxNDEgQzE1LjMzNzk1MjcsNDIuMzk0NzkwNiAxNS4zNTk4MzYxLDQyLjU1MTE3MzkgMTUuMzk0MTYzLDQyLjcwNTM3OTEgQzE1LjY4ODUxNiw0NC4wMjcwMTM5IDE2Ljc5OTg0ODksNDUuMDUxNTYzOSAxOC4xMjE4NjMxLDQ1LjIyNDA2NDcgQzE4LjE4NTc5Nyw0NS4yMzE5MDU2IDE4LjI1MDE1OTksNDUuMjQ0NTM4MyAxOC4zMTQwOTM3LDQ1LjI1NDk5MjkgTDQyLjM1OTY0ODQsNDUuMjU0OTkyOSBDNDIuNTE1ODM1Nyw0NS4yMjc5ODUyIDQyLjY3MjQ1MjEsNDUuMjA1NzY5MiA0Mi44MjY5MjMxLDQ1LjE3MTc5MTcgWiBNMTguNTYxNjc2NCwyNy4xOTgxNjkyIEMxOC41NjE2NzY0LDMxLjcxMzI0NjMgMTguNTYxMjQ3MywzNi4yMjgzMjM1IDE4LjU2MjEwNTUsNDAuNzQzNDAwNiBDMTguNTYyMTA1NSw0MS4zOTI4OTIyIDE5LjExNjA1NTYsNDEuOTUxMzQxNiAxOS43NTU4MjI5LDQxLjk1MTM0MTYgQzI2LjgwODI4MTcsNDEuOTUxNzc3MiAzMy44NjAzMTE0LDQxLjk1MTc3NzIgNDAuOTEyNzcwMSw0MS45NTEzNDE2IEM0MS41NTg1NDQ3LDQxLjk1MTM0MTYgNDIuMTA5NDkxMiw0MS4zOTM3NjM0IDQyLjEwOTQ5MTIsNDAuNzM5NDgwMSBDNDIuMTA5OTIwMywzNi4yMjk2MzAzIDQyLjEwOTQ5MTIsMzEuNzIwMjE2MSA0Mi4xMDk0OTEyLDI3LjIxMDgwMTggTDQyLjEwOTQ5MTIsMjcuMTE3MTQ2MSBMMzkuMjQwNjIxNywyNy4xMTcxNDYxIEMzOS42NDU2Nzg5LDI4LjQzMTM3NTUgMzkuNzcwMTEzOSwyOS43NjgyNTY1IDM5LjYxMTM1MiwzMS4xMzA4Mzg0IEMzOS40NTE3MzIsMzIuNDkzODU1OSAzOS4wMTkyMTMzLDMzLjc2MjM0NjUgMzguMzE0NjUzOSwzNC45MzM2OTY0IEMzNy42MDk2NjU1LDM2LjEwNjM1MzIgMzYuNjk1NzEyMSwzNy4wNzc3NTkxIDM1LjU3NjY1NTcsMzcuODUwOTYzMyBDMzIuNjc2MDMzOCwzOS44NTY1MDI3IDI4Ljg1NzE2NzcsNDAuMDMyOTIzOSAyNS43NzkzMzMzLDM4LjI3OTE2NiBDMjQuMjIzNDY3MiwzNy4zOTM1NzQ5IDIzLjAwMTg1OTEsMzYuMTU4NjI2MiAyMi4xNTAxMjMyLDM0LjU2NzM1MDEgQzIwLjg3OTU5OTQsMzIuMTkyODUwOCAyMC42NzY2NDE2LDI5LjcwMDczNzMgMjEuNDIxOTY0MiwyNy4xMTQ5NjgxIEMyMC40NzAyNTEyLDI3LjExNTgzOTMgMTkuNTIyNDAwMSwyNy4xMTU4MzkzIDE4LjU2MTY3NjQsMjcuMTE1ODM5MyBMMTguNTYxNjc2NCwyNy4xOTgxNjkyIFogTTI0LjI0NzQ5NiwyOS45MDYzNDQzIEMyNC4xOTk0MzgzLDMzLjM2NTUwNzYgMjYuOTI3MTM4NSwzNi4xMDc2NiAzMC4xOTcyMDM1LDM2LjE3OTA5OTggQzMzLjU5OTg1NjEsMzYuMjUzMTUzMSAzNi4zNTIwMTQyLDMzLjQ5MzE0MDcgMzYuNDIzNjcxNiwzMC4xMzYzNDUzIEMzNi40OTcwNDUzLDI2LjY3NDU2ODQgMzMuNzQ2NjAzNSwyMy44MTUyMzczIDMwLjMzNzA4NTYsMjMuODE3NDE1NCBDMjcuMDAzOTQ0OSwyMy44MTUyMzczIDI0LjI5NDI2NjQsMjYuNTM3Nzg3NSAyNC4yNDc0OTYsMjkuOTA2MzQ0MyBaIE00MC45NTQzOTE1LDIyLjU2OTgzNCBDNDEuNTkwNzI2MSwyMi41NTM3MTY1IDQyLjEwOTA2MjEsMjIuMDAwMDU4NyA0Mi4xMDkwNjIxLDIxLjM1MzE4MDggQzQyLjEwOTQ5MTIsMjAuMzkwMDUxNSA0Mi4xMDk0OTEyLDE5LjQyNjQ4NjUgNDIuMTA5MDYyMSwxOC40NjMzNTcyIEM0Mi4xMDkwNjIxLDE3Ljc3MjQ4MjkgNDEuNTcwNTU5MSwxNy4yMjI3NDU2IDQwLjg5MDg4NjcsMTcuMjIyMzA5OSBDMzkuOTQ0NzUxOSwxNy4yMjE4NzQzIDM4Ljk5ODYxNzEsMTcuMjIxNDM4NyAzOC4wNTIwNTMyLDE3LjIyMjMwOTkgQzM3LjM3NDA5NzIsMTcuMjIzMTgxMiAzNi44MzM4Nzc5LDE3Ljc3NDIyNTMgMzYuODMzNDQ4OCwxOC40NjUwOTk2IEMzNi44MzMwMTk3LDE5LjQxOTk1MjQgMzYuODMwNDQ1MiwyMC4zNzQ4MDUyIDM2LjgzNjg4MTUsMjEuMzMwMDkzNiBDMzYuODM3NzM5NiwyMS40NzI1Mzc0IDM2Ljg2NDM0MywyMS42MjA2NDQxIDM2LjkwODk2NzksMjEuNzU1NjgyNiBDMzcuMDc4ODg2LDIyLjI2NDAzNzIgMzcuNTM3NTc5LDIyLjU3NTkzMjUgMzguMDk5MjUyNywyMi41Nzg1NDYyIEMzOC41NTU4MDAzLDIyLjU3OTQxNzQgMzkuMDEyMzQ3OSwyMi41NzgxMTA2IDM5LjQ2OTMyNDUsMjIuNTc4MTEwNiBDMzkuOTYzNjMxNywyMi41NzI0NDc3IDQwLjQ1OTY1NTIsMjIuNTgyMDMxIDQwLjk1NDM5MTUsMjIuNTY5ODM0IFogTTQwLjk1NDM5MTUsMjIuNTY5ODM0IiBpZD0iUGF0aCIgZmlsbD0iI0ZGRkZGRiIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPgogICAgICAgICAgICAgICAgPHBhdGggZD0iTTU5Ljg4NzcwOTcsMzAgQzU5Ljg4NzcwOTcsNDYuNTY4NTQzMyA0Ni42NTczNDk0LDYwIDMwLjMzNjg3MSw2MCBDMjQuMjgzOTkyMiw2MCAxOC42NTYxNTY4LDU4LjE1MjUxMzQgMTMuOTcwNzc2MSw1NC45ODI3NzU0IEw0Ny44MzA5OTc1LDUuODE5NDExMDMgQzU1LjE0Mjg5NTUsMTEuMjgwNjUwMyA1OS44ODc3MDk3LDIwLjA3Nzc5NzMgNTkuODg3NzA5NywzMCBaIE01OS44ODc3MDk3LDMwIiBpZD0icmVmbGVjIiBmaWxsLW9wYWNpdHk9IjAuMDgiIGZpbGw9IiMwMDAwMDAiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4KICAgICAgICAgICAgPC9nPgogICAgICAgIDwvZz4KICAgIDwvZz4KPC9zdmc+); }
- &.linkedin { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPg0KICAgIDxwYXRoIGQ9Ik0wLjQ0OTE2MTM3NiwzMCBDMC40NDkxNjEzNzYsMTMuNDMxNDU2NyAxMy42Nzk1MjE3LDAgMzAsMCBDNDYuMzIwNDc4MywwIDU5LjU1MDgzODYsMTMuNDMxNDU2NyA1OS41NTA4Mzg2LDMwIEM1OS41NTA4Mzg2LDQ2LjU2ODU0MzMgNDYuMzIwNDc4Myw2MCAzMCw2MCBDMTMuNjc5NTIxNyw2MCAwLjQ0OTE2MTM3Niw0Ni41Njg1NDMzIDAuNDQ5MTYxMzc2LDMwIFogTTAuNDQ5MTYxMzc2LDMwIiBmaWxsPSIjMDA3QkI2IiBza2V0Y2g6dHlwZT0iTVNTaGFwZUdyb3VwIj48L3BhdGg+DQogICAgPHBhdGggZD0iTTIyLjQ2ODAzOTIsMjMuNzA5ODE0NCBMMTUuNzgwODM2NiwyMy43MDk4MTQ0IEwxNS43ODA4MzY2LDQ0LjEzNjk1MzcgTDIyLjQ2ODAzOTIsNDQuMTM2OTUzNyBMMjIuNDY4MDM5MiwyMy43MDk4MTQ0IFogTTIyLjQ2ODAzOTIsMjMuNzA5ODE0NCIgaWQ9IlBhdGgiIGZpbGw9IiNGRkZGRkYiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCiAgICA8cGF0aCBkPSJNMjIuOTA4NDc1MywxNy4zOTA4NzYxIEMyMi44NjUwNzI3LDE1LjM4ODAwODEgMjEuNDU2MjkxNywxMy44NjI1MDQgMTkuMTY4NjQxOCwxMy44NjI1MDQgQzE2Ljg4MDk5MTgsMTMuODYyNTA0IDE1LjM4NTQwNTcsMTUuMzg4MDA4MSAxNS4zODU0MDU3LDE3LjM5MDg3NjEgQzE1LjM4NTQwNTcsMTkuMzUyMjU3OSAxNi44MzY3ODgsMjAuOTIxNjg4NiAxOS4wODE4MzY2LDIwLjkyMTY4ODYgTDE5LjEyNDU3MTQsMjAuOTIxNjg4NiBDMjEuNDU2MjkxNywyMC45MjE2ODg2IDIyLjkwODQ3NTMsMTkuMzUyMjU3OSAyMi45MDg0NzUzLDE3LjM5MDg3NjEgWiBNMjIuOTA4NDc1MywxNy4zOTA4NzYxIiBpZD0iUGF0aCIgZmlsbD0iI0ZGRkZGRiIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KICAgIDxwYXRoIGQ9Ik00Ni41ODQ2NTAyLDMyLjQyNDY1NjMgQzQ2LjU4NDY1MDIsMjYuMTUwMzIyNiA0My4yODU2NTM0LDIzLjIzMDE0NTYgMzguODg1MTY1OCwyMy4yMzAxNDU2IEMzNS4zMzQ3MDExLDIzLjIzMDE0NTYgMzMuNzQ1MDk4MywyNS4yMTI4MTI4IDMyLjg1NzU0ODksMjYuNjAzNjg5NiBMMzIuODU3NTQ4OSwyMy43MTAzNTY3IEwyNi4xNjk1NDQ5LDIzLjcxMDM1NjcgQzI2LjI1NzY4NTYsMjUuNjI3MTMzOCAyNi4xNjk1NDQ5LDQ0LjEzNzQ5NiAyNi4xNjk1NDQ5LDQ0LjEzNzQ5NiBMMzIuODU3NTQ4OSw0NC4xMzc0OTYgTDMyLjg1NzU0ODksMzIuNzI5Mjk2MSBDMzIuODU3NTQ4OSwzMi4xMTg3OTYzIDMyLjkwMDk1MTQsMzEuNTA5Nzg3NyAzMy4wNzc3NjY5LDMxLjA3MjY4OTggQzMzLjU2MTA3MTMsMjkuODUzMDQ1OCAzNC42NjE0OTM3LDI4LjU5MDI4ODUgMzYuNTA4OTc0NywyOC41OTAyODg1IEMzOC45Mjk3NzAzLDI4LjU5MDI4ODUgMzkuODk3NDQ3NiwzMC40NjM0MTAxIDM5Ljg5NzQ0NzYsMzMuMjA4NDIyNiBMMzkuODk3NDQ3Niw0NC4xMzY5NTM3IEw0Ni41ODQzODMyLDQ0LjEzNjk1MzcgTDQ2LjU4NDY1MDIsMzIuNDI0NjU2MyBaIE00Ni41ODQ2NTAyLDMyLjQyNDY1NjMiIGlkPSJQYXRoIiBmaWxsPSIjRkZGRkZGIiBza2V0Y2g6dHlwZT0iTVNTaGFwZUdyb3VwIj48L3BhdGg+DQogICAgPHBhdGggZD0iTTU5LjU1MDgzODYsMzAgQzU5LjU1MDgzODYsNDYuNTY4NTQzMyA0Ni4zMjA0NzgzLDYwIDMwLDYwIEMyMy45NDcxMjEyLDYwIDE4LjMxOTI4NTgsNTguMTUyNTEzNCAxMy42MzM5MDUxLDU0Ljk4Mjc3NTQgTDQ3LjQ5NDEyNjQsNS44MTk0MTEwMyBDNTQuODA2MDI0NSwxMS4yODA2NTAzIDU5LjU1MDgzODYsMjAuMDc3Nzk3MyA1OS41NTA4Mzg2LDMwIFogTTU5LjU1MDgzODYsMzAiIGlkPSJyZWZsZWMiIGZpbGwtb3BhY2l0eT0iMC4wOCIgZmlsbD0iIzAwMDAwMCIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KPC9zdmc+); }
- &.pinterest { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPg0KICAgIDxwYXRoIGQ9Ik0wLjg4MzgzMzY3NSwzMCBDMC44ODM4MzM2NzUsMTMuNDMxNDU2NyAxMy45MDA4MDExLDAgMjkuOTU4MDQ1OSwwIEM0Ni4wMTUyOTA3LDAgNTkuMDMyMjU4MSwxMy40MzE0NTY3IDU5LjAzMjI1ODEsMzAgQzU5LjAzMjI1ODEsNDYuNTY4NTQzMyA0Ni4wMTUyOTA3LDYwIDI5Ljk1ODA0NTksNjAgQzEzLjkwMDgwMTEsNjAgMC44ODM4MzM2NzUsNDYuNTY4NTQzMyAwLjg4MzgzMzY3NSwzMCBaIE0wLjg4MzgzMzY3NSwzMCIgZmlsbD0iI0NCMjAyNyIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KICAgIDxwYXRoIGQ9Ik0xNy41ODY5MTY1LDI1LjY1NjQ4OTQgQzE3LjU4NjkxNjUsMjguOTU5MDYxOCAxOC43OTg2ODUxLDMxLjg5NzE2OTggMjEuMzk3Njk0MSwzMi45OTIwNTU5IEMyMS44MjM4Njk2LDMzLjE3MTgzNTYgMjIuMjA1NjA4NywzMi45OTgyNDA1IDIyLjMyOTIwMzcsMzIuNTExMzYzOCBDMjIuNDE1MTgyOSwzMi4xNzQ0MTAxIDIyLjYxODU1NjYsMzEuMzI0MzQ4NSAyMi43MDkyODk0LDMwLjk3MDMzMzkgQzIyLjgzMzkxNzksMzAuNDg4Nzg4OCAyMi43ODU1NTQ2LDMwLjMxOTg4NTQgMjIuNDQxNjM4LDI5LjkwMDE4NjIgQzIxLjY5MjIxNCwyOC45ODgwNjU0IDIxLjIxMzMzNSwyNy44MDcyMzQ4IDIxLjIxMzMzNSwyNi4xMzQ2MjI0IEMyMS4yMTMzMzUsMjEuMjgyMDYzMSAyNC43MzE4NjYyLDE2LjkzNzkyIDMwLjM3NTQ4NzcsMTYuOTM3OTIgQzM1LjM3MjgxODgsMTYuOTM3OTIgMzguMTE4MzY0NCwyMC4wODg2NSAzOC4xMTgzNjQ0LDI0LjI5NjUxODggQzM4LjExODM2NDQsMjkuODMzMDA4NyAzNS43NDM4MTA2LDM0LjUwNTc4ODIgMzIuMjE4NjY1NiwzNC41MDU3ODgyIEMzMC4yNzE5NDA3LDM0LjUwNTc4ODIgMjguODE0NjM1NSwzMi44NDQ0Nzg3IDI5LjI4MTczMzcsMzAuODA2OTc1NCBDMjkuODQxMDExNSwyOC4zNzQ1MTEyIDMwLjkyNDQzMTQsMjUuNzQ5MjU4MyAzMC45MjQ0MzE0LDIzLjk5MzQ3MzggQzMwLjkyNDQzMTQsMjIuNDIxNzM0MiAzMC4xMDY4MDI4LDIxLjExMDgxMzkgMjguNDE0NzA4NCwyMS4xMTA4MTM5IEMyNi40MjQ1ODA2LDIxLjExMDgxMzkgMjQuODI1OTA1OCwyMy4yMzUxMTQ4IDI0LjgyNTkwNTgsMjYuMDgwODgwNCBDMjQuODI1OTA1OCwyNy44OTMzOTI1IDI1LjQxOTQ5MjYsMjkuMTE5MjIxNCAyNS40MTk0OTI2LDI5LjExOTIyMTQgQzI1LjQxOTQ5MjYsMjkuMTE5MjIxNCAyMy4zODI4NjE2LDM4LjAyMzExNTMgMjMuMDI1OTI0MiwzOS41ODI0ODU2IEMyMi4zMTQ5NDI4LDQyLjY4ODAwNDEgMjIuOTE5MDcwMyw0Ni40OTQ5NDA3IDIyLjk3MDEyMDQsNDYuODc5NDUxOCBDMjMuMDAwMDg5MSw0Ny4xMDcyMTU0IDIzLjI4Mzg2MTYsNDcuMTYxMzgzOSAyMy40MTI0MTcsNDYuOTg5MjgxNiBDMjMuNTk1OTQ5NCw0Ni43NDIxMTEyIDI1Ljk2NjE2MjksNDMuNzIyNzUwNCAyNi43NzIwMTA3LDQwLjcwNTczNTYgQzI2Ljk5OTk3OTUsMzkuODUxNDA4OCAyOC4wODA5MTkyLDM1LjQyNzcxOSAyOC4wODA5MTkyLDM1LjQyNzcxOSBDMjguNzI3NDE2MiwzNi43MDAyNTIzIDMwLjYxNzA5NzMsMzcuODIxMTU2NCAzMi42MjY2NTMyLDM3LjgyMTE1NjQgQzM4LjYwODgxNzYsMzcuODIxMTU2NCA0Mi42Njc0MDUyLDMyLjE5MzgxNjkgNDIuNjY3NDA1MiwyNC42NjE0MDk4IEM0Mi42Njc0MDUyLDE4Ljk2NTgyNjYgMzcuOTkyMDgyNSwxMy42NjEzNjU2IDMwLjg4NjE5NTUsMTMuNjYxMzY1NiBDMjIuMDQ0ODExMiwxMy42NjEzNjU2IDE3LjU4NjkxNjUsMjAuMjAyMTA1MyAxNy41ODY5MTY1LDI1LjY1NjQ4OTQgWiBNMTcuNTg2OTE2NSwyNS42NTY0ODk0IiBpZD0iUGF0aCIgZmlsbD0iI0ZGRkZGRiIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KICAgIDxwYXRoIGQ9Ik01OS4wMzIyNTgxLDMwIEM1OS4wMzIyNTgxLDQ2LjU2ODU0MzMgNDYuMDE1MjkwNyw2MCAyOS45NTgwNDU5LDYwIEMyNC4wMDI3OTQxLDYwIDE4LjQ2NTczMDIsNTguMTUyNTEzNCAxMy44NTU5MjAzLDU0Ljk4Mjc3NTQgTDQ3LjE3MDAwOSw1LjgxOTQxMTAzIEM1NC4zNjM5NzMyLDExLjI4MDY1MDMgNTkuMDMyMjU4MSwyMC4wNzc3OTczIDU5LjAzMjI1ODEsMzAgWiBNNTkuMDMyMjU4MSwzMCIgaWQ9InJlZmxlYyIgZmlsbC1vcGFjaXR5PSIwLjA4IiBmaWxsPSIjMDAwMDAwIiBza2V0Y2g6dHlwZT0iTVNTaGFwZUdyb3VwIj48L3BhdGg+DQo8L3N2Zz4=); }
- &.rss { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPg0KICAgIDxwYXRoIGQ9Ik0wLjExMjI5MDM0NCwzMCBDMC4xMTIyOTAzNDQsMTMuNDMxNDU2NyAxMy4zNDI2NTA2LDAgMjkuNjYzMTI5LDAgQzQ1Ljk4MzYwNzMsMCA1OS4yMTM5Njc2LDEzLjQzMTQ1NjcgNTkuMjEzOTY3NiwzMCBDNTkuMjEzOTY3Niw0Ni41Njg1NDMzIDQ1Ljk4MzYwNzMsNjAgMjkuNjYzMTI5LDYwIEMxMy4zNDI2NTA2LDYwIDAuMTEyMjkwMzQ0LDQ2LjU2ODU0MzMgMC4xMTIyOTAzNDQsMzAgWiBNMC4xMTIyOTAzNDQsMzAiIGZpbGw9IiNFMThGMDAiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCiAgICA8cGF0aCBkPSJNMjYuNTE0Nzc1NSwzOC43NTcxMjk2IEMyNi41MTQ3NzU1LDM2LjgxOTI5MzQgMjQuOTU3NTAyMSwzNS4yMjkxNjU2IDIzLjAyOTcwNDcsMzUuMjI5MTY1NiBDMjEuMTA5NDMzMSwzNS4yMjkxNjU2IDE5LjU0OTI3NzUsMzYuODE5MjkzNCAxOS41NDkyNzc1LDM4Ljc1NzEyOTYgQzE5LjU0OTI3NzUsNDAuNzA1MjA2OCAyMS4xMDk0MzMxLDQyLjI3NzYxNiAyMy4wMjk3MDQ3LDQyLjI3NzYxNiBDMjQuOTU3NDIyLDQyLjI3NzYxNiAyNi41MTQ2OTU0LDQwLjcwNTI4ODEgMjYuNTE0Nzc1NSwzOC43NTcxMjk2IFogTTM2LjgwNzU0MzMsNDIuMjcwMDU3MSBDMzYuODA3NTQzMywzMi42MDU1ODQ3IDI5LjA2MjY0OCwyNC43NDQyNzA1IDE5LjU0OTI3NzUsMjQuNzQ0MjcwNSBMMTkuNTQ5Mjc3NSwyOS44MzE4MDE3IEMyMi44MTI4OTg2LDI5LjgzMTgwMTcgMjUuODgxNzMwMywzMS4xMjcyMTQ1IDI4LjE5MjA2MDksMzMuNDc0MDQyOSBDMzAuNDk5OTg5NSwzNS44MTU5MTMzIDMxLjc3MzI4NTMsMzguOTQ1NDUxMyAzMS43NzMyODUzLDQyLjI3MDEzODQgTDM2LjgwNzU0MzMsNDIuMjcwMDU3MSBaIE00NS42ODcxNDgyLDQyLjI2NzUzNzUgQzQ1LjY4NzE0ODIsMjcuNjM0Njg3OCAzMy45NjA0MDE0LDE1LjcyMjM4NCAxOS41NDkyNzc1LDE1LjcyMjM4NCBMMTkuNTQ5Mjc3NSwyMC44MTIzNTM1IEMzMS4xODY5MTYsMjAuODEyMzUzNSA0MC42NjA0OTYsMzAuNDM4ODY5IDQwLjY2MDQ5Niw0Mi4yNjczNzQ5IEw0NS42ODcxNDgyLDQyLjI2NzUzNzUgWiBNNDUuNjg3MTQ4Miw0Mi4yNjc1Mzc1IiBpZD0iUGF0aCIgZmlsbD0iI0ZGRkZGRiIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KICAgIDxwYXRoIGQ9Ik01OS4yMTM5Njc2LDMwIEM1OS4yMTM5Njc2LDQ2LjU2ODU0MzMgNDUuOTgzNjA3Myw2MCAyOS42NjMxMjksNjAgQzIzLjYxMDI1MDIsNjAgMTcuOTgyNDE0Nyw1OC4xNTI1MTM0IDEzLjI5NzAzNDEsNTQuOTgyNzc1NCBMNDcuMTU3MjU1NCw1LjgxOTQxMTAzIEM1NC40NjkxNTM0LDExLjI4MDY1MDMgNTkuMjEzOTY3NiwyMC4wNzc3OTczIDU5LjIxMzk2NzYsMzAgWiBNNTkuMjEzOTY3NiwzMCIgaWQ9InJlZmxlYyIgZmlsbC1vcGFjaXR5PSIwLjA4IiBmaWxsPSIjMDAwMDAwIiBza2V0Y2g6dHlwZT0iTVNTaGFwZUdyb3VwIj48L3BhdGg+DQo8L3N2Zz4=); }
- &.stackoverflow { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDAiIGhlaWdodD0iNDAiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6c3ZnPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI+DQogIDxwYXRoIGZpbGw9IiM5MTkxOTEiIGQ9Im03LjI5NDA3NSwyMy4xMTAxODhsMi4zODU4NjQsMC4wMjMyMzdsLTAuMDgzMTc3LDEwLjU1MjY3OWwxNS44NzgyMjEsMGwwLC0xMC41MTQ1MDVsMi41MTQwNSwwbDAsMTMuMDc3NDFsLTIwLjcwNzg0MywwbDAuMDEyODksLTEzLjEzODgxNWwtMC4wMDAwMDUsLTAuMDAwMDA2eiIvPg0KICA8cmVjdCBmaWxsPSIjOTE5MTkxIiB5PSIyOS4zNDg4NjIiIHg9IjExLjE4NDU4MiIgaGVpZ2h0PSIyLjYyODYyNiIgd2lkdGg9IjEyLjQzNzkzOCIvPg0KICA8cmVjdCBmaWxsPSIjYTc4YjY4IiB0cmFuc2Zvcm09Im1hdHJpeCgwLjUzOTU3MzM0MTAzMDQ3MTcsMC4wNTE3MjY2OTg0ODM5OTIwNCwtMC4wNTIwNzU4NjQ3ODAwMzI1MiwwLjUzNTk1NTUyNjQxMDg2NjUsMy42NjExNDE2NjQ4Njc4MzI1LDEuNDA2NzI1NTcyNzY2NjYxNCkgIiB5PSI0MS41MjQzNDciIHg9IjE4LjQ5MTI1IiBoZWlnaHQ9IjUuMDAzOTIzIiB3aWR0aD0iMjMuMDY2ODY0Ii8+DQogIDxyZWN0IGZpbGw9IiNjMTk2NTMiIHRyYW5zZm9ybT0ibWF0cml4KDAuNTIxNjk5ODY3NjIzODk1OCwwLjE0NjI1NTg2MDkyMjc4OTkyLC0wLjE0NzI0MzExOTMxNjAyNDIsMC41MTgyMDE4OTM4Mjc1NDE2LDMuNjYxMTQxNjY0ODY3ODMyNSwxLjQwNjcyNTU3Mjc2NjY2MTQpICIgeT0iMjcuNDM4NTE1IiB4PSIyNC45MDcwNzYiIGhlaWdodD0iNS4wMDM5MjMiIHdpZHRoPSIyMy4wNjY4NjQiLz4NCiAgPHJlY3QgZmlsbD0iI2Q0OGMyOCIgdHJhbnNmb3JtPSJtYXRyaXgoMC40NjQwMDkwMjQ0MjYxMjE2LDAuMjc4MzgzMDczOTI4ODQ3NSwtMC4yODAyNjIyMTkzMTUxMzUzLDAuNDYwODk3ODY1MDk5NzY5OTMsMy42NjExNDE2NjQ4Njc4MzI1LDEuNDA2NzI1NTcyNzY2NjYxNCkgIiB5PSI3LjQ2MTA5MiIgeD0iMzAuMDg5Mzk2IiBoZWlnaHQ9IjUuMDAzOTIzIiB3aWR0aD0iMjMuMDY2ODY0Ii8+DQogIDxyZWN0IGZpbGw9IiNmZTg5MDgiIHRyYW5zZm9ybT0ibWF0cml4KDAuMzE1NzIyMjcwMDE0MzMwNCwwLjQzNzY5MzU2MDg5OTk2MDIsLTAuNDQwNjQ4MDg2MjAxOTY2NCwwLjMxMzYwNTM2NjYwNjg4NzM3LDMuNjYxMTQxNjY0ODY3ODMyNSwxLjQwNjcyNTU3Mjc2NjY2MTQpICIgeT0iLTIwLjM0MzgwMyIgeD0iMjguNDg4MzAzIiBoZWlnaHQ9IjUuMDAzOTIzIiB3aWR0aD0iMjMuMDY2ODY0Ii8+DQogIDxyZWN0IGZpbGw9IiNmZjdhMTUiIHRyYW5zZm9ybT0ibWF0cml4KDAuMDg5MzQwMjMwNDgyMTY3NiwwLjUzMTA4MjgzMzM4NDMxNzksLTAuNTM0NjY3NzU2MjgyMTI5OSwwLjA4ODc0MTIwODMxNTI0NTg1LDMuNjYxMTQxNjY0ODY3ODMyNSwxLjQwNjcyNTU3Mjc2NjY2MTQpICIgeT0iLTQ3LjA0NTkyNyIgeD0iMTQuMTU4MjAzIiBoZWlnaHQ9IjUuMDAzOTIzIiB3aWR0aD0iMjMuMDY2ODY0Ii8+DQo8L3N2Zz4NCg==); }
- &.twitter { background-image: url(data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDBweCIgaGVpZ2h0PSI0MHB4IiB2aWV3Qm94PSIwIDAgNjAgNjAiIHZlcnNpb249IjEuMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sbnM6c2tldGNoPSJodHRwOi8vd3d3LmJvaGVtaWFuY29kaW5nLmNvbS9za2V0Y2gvbnMiPg0KICAgIDxwYXRoIGQ9Ik0wLDMwIEMwLDEzLjQzMTQ1NjcgMTMuNDUwODY2MywwIDMwLjA0MzM1MjYsMCBDNDYuNjM1ODM4OSwwIDYwLjA4NjcwNTIsMTMuNDMxNDU2NyA2MC4wODY3MDUyLDMwIEM2MC4wODY3MDUyLDQ2LjU2ODU0MzMgNDYuNjM1ODM4OSw2MCAzMC4wNDMzNTI2LDYwIEMxMy40NTA4NjYzLDYwIDAsNDYuNTY4NTQzMyAwLDMwIFogTTAsMzAiIGZpbGw9IiM0MDk5RkYiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4NCiAgICA8cGF0aCBkPSJNMjkuMjk5NzY3NSwyMy44ODc5Nzc2IEwyOS4zNjI3MjA2LDI0LjkyNjA0NTMgTDI4LjMxMzUwMTYsMjQuNzk4OTM1IEMyNC40OTQzNDQ1LDI0LjMxMTY3ODcgMjEuMTU3ODI4MSwyMi42NTkyNDQ0IDE4LjMyNDkzNjgsMTkuODg0MDAyMyBMMTYuOTM5OTY3NywxOC41MDY5NzM3IEwxNi41ODMyMzMzLDE5LjUyMzg1NjMgQzE1LjgyNzc5NTYsMjEuNzkwNjU3MiAxNi4zMTA0MzYzLDI0LjE4NDU2ODQgMTcuODg0MjY0OCwyNS43OTQ2MzI1IEMxOC43MjM2NCwyNi42ODQ0MDQ4IDE4LjUzNDc4MDYsMjYuODExNTE1MiAxNy4wODY4NTg0LDI2LjI4MTg4ODggQzE2LjU4MzIzMzMsMjYuMTEyNDA4MyAxNi4xNDI1NjEzLDI1Ljk4NTI5OCAxNi4xMDA1OTI1LDI2LjA0ODg1MzIgQzE1Ljk1MzcwMTksMjYuMTk3MTQ4NiAxNi40NTczMjcsMjguMTI0OTg4NSAxNi44NTYwMzAyLDI4Ljg4NzY1MDUgQzE3LjQwMTYyNDEsMjkuOTQ2OTAzMyAxOC41MTM3OTYyLDMwLjk4NDk3MDkgMTkuNzMwODkwMiwzMS41OTkzMzc1IEwyMC43NTkxMjQ4LDMyLjA4NjU5MzggTDE5LjU0MjAzMDgsMzIuMTA3Nzc4OCBDMTguMzY2OTA1NSwzMi4xMDc3Nzg4IDE4LjMyNDkzNjgsMzIuMTI4OTYzOSAxOC40NTA4NDMxLDMyLjU3Mzg1IEMxOC44NzA1MzA3LDMzLjk1MDg3ODYgMjAuNTI4Mjk2NywzNS40MTI2NDc0IDIyLjM3NDkyMjEsMzYuMDQ4MTk5IEwyMy42NzU5NTM2LDM2LjQ5MzA4NTIgTDIyLjU0Mjc5NzEsMzcuMTcxMDA2OSBDMjAuODY0MDQ2NywzOC4xNDU1MTk0IDE4Ljg5MTUxNSwzOC42OTYzMzA5IDE2LjkxODk4MzMsMzguNzM4NzAxIEMxNS45NzQ2ODYyLDM4Ljc1OTg4NiAxNS4xOTgyNjQyLDM4Ljg0NDYyNjIgMTUuMTk4MjY0MiwzOC45MDgxODE0IEMxNS4xOTgyNjQyLDM5LjEyMDAzMTkgMTcuNzU4MzU4NSw0MC4zMDYzOTUgMTkuMjQ4MjQ5NSw0MC43NzI0NjYyIEMyMy43MTc5MjI0LDQyLjE0OTQ5NDggMjkuMDI2OTcwNSw0MS41NTYzMTMyIDMzLjAxNDAwMjcsMzkuMjA0NzcyMiBDMzUuODQ2ODk0LDM3LjUzMTE1MjggMzguNjc5Nzg1MywzNC4yMDUwOTkzIDQwLjAwMTgwMTIsMzAuOTg0OTcwOSBDNDAuNzE1MjcwMSwyOS4yNjg5ODE1IDQxLjQyODczOSwyNi4xMzM1OTM0IDQxLjQyODczOSwyNC42Mjk0NTQ1IEM0MS40Mjg3MzksMjMuNjU0OTQyIDQxLjQ5MTY5MjIsMjMuNTI3ODMxNyA0Mi42NjY4MTc0LDIyLjM2MjY1MzcgQzQzLjM1OTMwMiwyMS42ODQ3MzE5IDQ0LjAwOTgxNzgsMjAuOTQzMjU1IDQ0LjEzNTcyNCwyMC43MzE0MDQ0IEM0NC4zNDU1Njc4LDIwLjMyODg4ODQgNDQuMzI0NTgzNSwyMC4zMjg4ODg0IDQzLjI1NDM4MDEsMjAuNjg5MDM0MyBDNDEuNDcwNzA3OCwyMS4zMjQ1ODYgNDEuMjE4ODk1MiwyMS4yMzk4NDU4IDQyLjEwMDIzOTIsMjAuMjg2NTE4MyBDNDIuNzUwNzU1LDE5LjYwODU5NjUgNDMuNTI3MTc3LDE4LjM3OTg2MzQgNDMuNTI3MTc3LDE4LjAxOTcxNzQgQzQzLjUyNzE3NywxNy45NTYxNjIzIDQzLjIxMjQxMTMsMTguMDYyMDg3NiA0Mi44NTU2NzY5LDE4LjI1Mjc1MyBDNDIuNDc3OTU4LDE4LjQ2NDYwMzYgNDEuNjM4NTgyOCwxOC43ODIzNzk0IDQxLjAwOTA1MTQsMTguOTczMDQ0OSBMMzkuODc1ODk0OSwxOS4zMzMxOTA4IEwzOC44NDc2NjAzLDE4LjYzNDA4NCBDMzguMjgxMDgyLDE4LjI1Mjc1MyAzNy40ODM2NzU2LDE3LjgyOTA1MiAzNy4wNjM5ODgsMTcuNzAxOTQxNiBDMzUuOTkzNzg0NiwxNy40MDUzNTA5IDM0LjM1NzAwMywxNy40NDc3MjEgMzMuMzkxNzIxNSwxNy43ODY2ODE4IEMzMC43Njg2NzQsMTguNzQwMDA5MyAyOS4xMTA5MDgsMjEuMTk3NDc1NyAyOS4yOTk3Njc1LDIzLjg4Nzk3NzYgWiBNMjkuMjk5NzY3NSwyMy44ODc5Nzc2IiBpZD0iUGF0aCIgZmlsbD0iI0ZGRkZGRiIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KICAgIDxwYXRoIGQ9Ik02MC4wODY3MDUyLDMwIEM2MC4wODY3MDUyLDQ2LjU2ODU0MzMgNDYuNjM1ODM4OSw2MCAzMC4wNDMzNTI2LDYwIEMyMy44ODk1OTI1LDYwIDE4LjE2Nzk1OTgsNTguMTUyNTEzNCAxMy40MDQ0ODk1LDU0Ljk4Mjc3NTQgTDQ3LjgyOTA0NzgsNS44MTk0MTEwMyBDNTUuMjYyODEwOCwxMS4yODA2NTAzIDYwLjA4NjcwNTIsMjAuMDc3Nzk3MyA2MC4wODY3MDUyLDMwIFogTTYwLjA4NjcwNTIsMzAiIGlkPSJyZWZsZWMiIGZpbGwtb3BhY2l0eT0iMC4wOCIgZmlsbD0iIzAwMDAwMCIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPg0KPC9zdmc+); }
- &.youtube { background-image: url(data:image/svg+xml;base64,<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg width="40px" height="40px" viewBox="0 0 60 60" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:sketch="http://www.bohemiancoding.com/sketch/ns">
    <title>YouTube</title>
    <description>Created with Sketch (http://www.bohemiancoding.com/sketch)</description>
    <defs></defs>
    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" sketch:type="MSPage">
        <g id="YouTube" sketch:type="MSArtboardGroup">
            <g id="Youtube" sketch:type="MSLayerGroup">
                <path d="M0.449161376,30 C0.449161376,13.4314567 13.6795217,0 30,0 C46.3204783,0 59.5508386,13.4314567 59.5508386,30 C59.5508386,46.5685433 46.3204783,60 30,60 C13.6795217,60 0.449161376,46.5685433 0.449161376,30 Z M0.449161376,30" id="YouTube" fill="#CD332D" sketch:type="MSShapeGroup"></path>
                <path d="M43.3055802,30.4283125 C44.7231802,31.8623516 44.7385158,38.9418535 44.7385158,38.9827559 C44.7385158,38.9827559 44.7270316,46.0991133 43.3055802,47.5381387 C41.8938624,48.9691426 29.9943279,49 29.9943279,49 C29.9943279,49 18.096474,48.9691426 16.6810449,47.5382109 C15.2654757,46.1040996 15.2615542,39.0364492 15.2615542,38.9827559 C15.2615542,38.941998 15.2654057,31.8623516 16.6810449,30.4283125 C18.0966141,28.9964414 29.9943279,28.9773633 29.9943279,28.9784473 C29.9943279,28.9773633 41.8938624,28.9964414 43.3055802,30.4283125 Z M22.0366792,44.8838945 L20.0983683,44.8838945 L20.0983683,34.5990508 L18.0945133,34.5990508 L18.0945133,32.8515234 L24.0404642,32.8515234 L24.0405342,34.5990508 L22.0366792,34.5990508 L22.0366792,44.8838945 Z M27.9883722,43.9077305 C27.6682848,44.2699258 27.3403545,44.5435957 26.9951979,44.7307637 C26.651862,44.9219063 26.3200803,45.0133223 25.9960714,45.0133223 C25.596785,45.0133223 25.3016968,44.8839668 25.0973618,44.6173789 C24.898699,44.3515137 24.7964615,43.9586055 24.7964615,43.4281035 L24.7964615,36.0061348 L26.5149618,36.0061348 L26.5149618,42.8150742 C26.5149618,43.0260176 26.5515852,43.1772695 26.6211207,43.2707812 C26.6963283,43.3663164 26.8139714,43.4121328 26.9740501,43.4121328 C27.0994661,43.4121328 27.2614356,43.3494063 27.4542863,43.2250371 C27.6490977,43.099584 27.8245821,42.942334 27.9884422,42.7503242 L27.9884422,36.0062793 L29.7068725,36.0062793 L29.7068025,44.8839668 L27.9883722,44.8839668 L27.9883722,43.9077305 Z M34.370373,44.9962676 C34.0328492,44.9962676 33.7338395,44.9337578 33.4715233,44.8043301 C33.2093471,44.6750469 32.9604058,44.4759551 32.7368138,44.2033691 L32.7368138,44.8839668 L30.9991965,44.8839668 L30.9991965,32.8515234 L32.7368138,32.8515234 L32.7368138,36.7256113 C32.9701394,36.4568555 33.2150892,36.248875 33.473554,36.1096914 C33.7357302,35.9684121 34.0001472,35.8986758 34.2661047,35.8986758 C34.8119549,35.8986758 35.226647,36.0877949 35.5120717,36.4640098 C35.8013478,36.8431152 35.9441302,37.3973926 35.9441302,38.1238789 L35.9441302,43.0498652 C35.9439901,43.677709 35.8088406,44.1594316 35.5390316,44.4948887 C35.2709733,44.8311406 34.8795297,44.9962676 34.370373,44.9962676 Z M38.6170105,42.3303887 C38.6170105,42.7981641 38.6731011,43.1215527 38.7847921,43.3036621 C38.9004745,43.483748 39.0933252,43.5724902 39.3672657,43.5724902 C39.6525504,43.5724902 39.8512832,43.4957441 39.965075,43.342541 C40.076976,43.1892656 40.1367079,42.8529414 40.1367079,42.3303887 L40.1367079,41.9254121 L41.9052766,41.9254121 L41.9052766,42.3812637 C41.9052766,43.2918828 41.691068,43.9774668 41.2572589,44.4401836 C40.8291919,44.8979863 40.1848856,45.1257676 39.3286816,45.1257676 C38.5590993,45.1257676 37.9515565,44.8838945 37.5099045,44.3942949 C37.0681124,43.9078027 36.8443804,43.2368887 36.8443804,42.3811914 L36.8443804,38.3945859 C36.8443804,37.6273418 37.0893302,36.9963906 37.5753785,36.5127168 C38.0612867,36.0281035 38.6861959,35.7863027 39.4577389,35.7863027 C40.2445475,35.7863027 40.8501996,36.0111211 41.2725245,36.4599629 C41.6948494,36.9077207 41.9052066,37.5526191 41.9052066,38.3945859 L41.9052066,40.6575117 L38.6170105,40.657584 L38.6170105,42.3303887 Z M33.9923043,37.5386719 C34.1136588,37.6938262 34.1735308,37.9216797 34.1735308,38.221293 L34.1735308,42.8050293 C34.1735308,43.0905508 34.1214317,43.2915938 34.0232556,43.4160352 C33.9249396,43.5434395 33.770533,43.606166 33.5603158,43.606166 C33.4138221,43.606166 33.2769219,43.5722012 33.1456237,43.5096191 C33.012645,43.447832 32.8756047,43.3393613 32.7368138,43.1961309 L32.7368138,37.6651367 C32.8543869,37.5427188 32.9720301,37.4521699 33.0915639,37.3943574 C33.2112378,37.334666 33.3326624,37.3077832 33.4560476,37.3077832 C33.6874125,37.3077832 33.8668883,37.3853965 33.9923043,37.5386719 Z M38.7945256,37.5844883 C38.6749918,37.7395703 38.6171506,38.0083262 38.6171506,38.379627 L38.6171506,39.2762266 L40.136918,39.2762266 L40.136918,38.379627 C40.136918,38.0083984 40.0752254,37.7397871 39.9555515,37.5844883 C39.8398691,37.4182051 39.6451276,37.3396523 39.3847021,37.3396523 C39.1109017,37.3396523 38.9141995,37.4182051 38.7945256,37.5844883 Z M38.7945256,37.5844883" id="Path" fill="#FFFFFF" sketch:type="MSShapeGroup"></path>
                <path d="M19.197838,12 L21.7917294,20.0030566 L21.7917294,25.2545273 L23.9712088,25.2545273 L23.9712088,19.7552578 L26.5072589,12 L24.2912261,12 L22.9451924,17.2982266 L22.8082222,17.2982266 L21.392583,12 L19.197838,12 Z M29.5467938,15.2294063 C30.3471173,15.2294063 31.0048686,15.4661484 31.5178767,15.9399219 C32.0269634,16.4126113 32.2835376,17.0226055 32.2835376,17.7680254 L32.2835376,22.8193926 C32.2835376,23.6552891 32.0328456,24.3101602 31.5333524,24.7868965 C31.027977,25.2625488 30.3394845,25.501459 29.4581413,25.501459 C28.6134214,25.501459 27.9345925,25.2545996 27.4253657,24.7651445 C26.9200603,24.2734492 26.6636263,23.6117129 26.6636263,22.7808027 L26.6634862,17.713248 C26.6634862,16.9539531 26.9238417,16.3508965 27.4465134,15.9030664 C27.9672944,15.4542246 28.6692319,15.2294063 29.5467938,15.2294063 Z M29.4541498,23.8074805 C29.716536,23.8074805 29.9228317,23.7319629 30.079059,23.5836016 C30.2334656,23.4322773 30.3106339,23.2263926 30.3106339,22.9655859 L30.3106339,17.6385254 C30.3106339,17.4246914 30.2314349,17.2524824 30.0733169,17.1200918 C29.9151989,16.9887852 29.7088332,16.9240352 29.4541498,16.9240352 C29.2169728,16.9240352 29.0260828,16.9887852 28.8775583,17.1200918 C28.7309946,17.2524824 28.655787,17.4245469 28.655787,17.6385254 L28.655787,22.9656582 C28.6557169,23.2333301 28.7270731,23.4392871 28.8639733,23.5875762 C29.0009436,23.7348535 29.1977157,23.8074805 29.4541498,23.8074805 Z M37.4406491,25.2545996 L37.4406491,24.1748789 C37.0876496,24.5719063 36.7155331,24.8775176 36.3277309,25.0844141 C35.9420294,25.2923945 35.5678122,25.3960234 35.2051491,25.3960234 C34.7539737,25.3960234 34.4202312,25.2496855 34.1927878,24.9591055 C33.967095,24.6675137 33.8533033,24.2316797 33.8533033,23.6484238 L33.8533033,15.4761211 L35.7857321,15.4761211 L35.7857321,22.9725957 C35.7857321,23.2044961 35.8301984,23.3716465 35.9111481,23.4751309 C35.9902071,23.5787598 36.1232559,23.6313691 36.3046224,23.6313691 C36.445374,23.6313691 36.6267405,23.5617773 36.8445905,23.4254121 C37.0605497,23.2881074 37.2611732,23.112791 37.440509,22.8979453 L37.440509,15.4761211 L39.3769993,15.4761211 L39.3769993,25.2545996 L37.4406491,25.2545996 Z M37.4406491,25.2545996" id="Path" fill="#FFFFFF" sketch:type="MSShapeGroup"></path>
                <path d="M59.5508386,30 C59.5508386,46.5685433 46.3204783,60 30,60 C23.9471212,60 18.3192858,58.1525134 13.6339051,54.9827754 L47.4941264,5.81941103 C54.8060245,11.2806503 59.5508386,20.0777973 59.5508386,30 Z M59.5508386,30" id="reflec" fill-opacity="0.08" fill="#000000" sketch:type="MSShapeGroup"></path>
            </g>
        </g>
    </g>
</svg>); }
- &.googleplus { background-image: url(data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9Im5vIj8+Cjxzdmcgd2lkdGg9IjQwcHgiIGhlaWdodD0iNDBweCIgdmlld0JveD0iMCAwIDYwIDYwIiB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHhtbG5zOnNrZXRjaD0iaHR0cDovL3d3dy5ib2hlbWlhbmNvZGluZy5jb20vc2tldGNoL25zIj4KICAgIDx0aXRsZT5Hb29nbGUgKzwvdGl0bGU+CiAgICA8ZGVzY3JpcHRpb24+Q3JlYXRlZCB3aXRoIFNrZXRjaCAoaHR0cDovL3d3dy5ib2hlbWlhbmNvZGluZy5jb20vc2tldGNoKTwvZGVzY3JpcHRpb24+CiAgICA8ZGVmcz48L2RlZnM+CiAgICA8ZyBpZD0iUGFnZS0xIiBzdHJva2U9Im5vbmUiIHN0cm9rZS13aWR0aD0iMSIgZmlsbD0ibm9uZSIgZmlsbC1ydWxlPSJldmVub2RkIiBza2V0Y2g6dHlwZT0iTVNQYWdlIj4KICAgICAgICA8ZyBpZD0iR29vZ2xlLSsiIHNrZXRjaDp0eXBlPSJNU0FydGJvYXJkR3JvdXAiPgogICAgICAgICAgICA8ZyBza2V0Y2g6dHlwZT0iTVNMYXllckdyb3VwIj4KICAgICAgICAgICAgICAgIDxwYXRoIGQ9Ik0wLjExMjI5MDM0NCwyOS41MDgxOTY3IEMwLjExMjI5MDM0NCwxMy4yMTEyNjg5IDEzLjM0MjY1MDYsMCAyOS42NjMxMjksMCBDNDUuOTgzNjA3MywwIDU5LjIxMzk2NzYsMTMuMjExMjY4OSA1OS4yMTM5Njc2LDI5LjUwODE5NjcgQzU5LjIxMzk2NzYsNDUuODA1MTI0NiA0NS45ODM2MDczLDU5LjAxNjM5MzQgMjkuNjYzMTI5LDU5LjAxNjM5MzQgQzEzLjM0MjY1MDYsNTkuMDE2MzkzNCAwLjExMjI5MDM0NCw0NS44MDUxMjQ2IDAuMTEyMjkwMzQ0LDI5LjUwODE5NjcgWiBNMC4xMTIyOTAzNDQsMjkuNTA4MTk2NyIgZmlsbD0iI0QzNDgzNiIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPgogICAgICAgICAgICAgICAgPHBhdGggZD0iTTU4LjI5NTc2NzIsMjIuNzE1NzA0OSBMNTEuMzA3NTkxNSwyMi43MTU3MDQ5IEw1MS4zMDc1OTE1LDMwLjQ2OTIwNzkgTDQ4LjAxMzY2MjMsMzAuNDY5MjA3OSBMNDguMDEzNjYyMywyMi43MTU3MDQ5IEw0MC4zMjc4Njg5LDIyLjcxNTcwNDkgTDQwLjMyNzg2ODksMTkuNDg4NjU5IEw0OC4wMTM2NjIzLDE5LjQ4ODY1OSBMNDguMDEzNjYyMywxMS44MDMyNzg3IEw1MS4zMDc1OTE1LDExLjgwMzI3ODcgTDUxLjMwNzU5MTUsMTkuNDg4NjU5IEw1Ny4xNzUyNDk2LDE5LjQ4ODY1OSBDNTcuNjA4NjI1NiwyMC41MzUzODMzIDU3Ljk4MzUwNDMsMjEuNjEyNDcyNiA1OC4yOTU3NjcyLDIyLjcxNTcwNDkgWiBNNTguMjk1NzY3MiwyMi43MTU3MDQ5IiBpZD0iU2hhcGUiIGZpbGw9IiNGRkZGRkYiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4KICAgICAgICAgICAgICAgIDxwYXRoIGQ9Ik04LjIzMDMzODgzLDQ4LjYwNTA4MTEgQzkuMDU2NjMyNTQsNDcuMjE3NTUzNiAxMC4zMzc4NjM5LDQ1Ljg1MzQgMTIuMjM1OTMwOCw0NC43MzIzODI4IEMxNi41MTg2MjMxLDQyLjExMjA5MjEgMjIuMjg2NjQyMSw0MS43NjYwMTU5IDI1LjQwNTgyODMsNDEuNTY4MjU4MSBDMjQuNDQwMzY1OSw0MC4zMzIyNzE5IDIzLjMyNjM3MDgsMzkuMDIyMTI2NSAyMy4zMjYzNzA4LDM2Ljg3MTUxMDUgQzIzLjMyNjM3MDgsMzUuNzA5NjgzNSAyMy42NzI5NDcxLDM1LjAxNzUzMTIgMjQuMDE5NTIzMywzNC4yMDE3ODAzIEMyMy4yNTIxMDQ1LDM0LjI3NTkzOTUgMjIuNTA5NDQxMSwzNC4zNTAwOTg2IDIxLjgxNjI4ODYsMzQuMzUwMDk4NiBDMTQuNTEzNDMxOSwzNC4zNTAwOTg2IDEwLjM3OTI3MjMsMjguOTExNzU5MyAxMC4zNzkyNzIzLDIzLjU0NzU3OTEgQzEwLjM3OTI3MjMsMjAuMzgzNDU0NCAxMS44Mzk4NDM3LDE2Ljg2ODMwOTYgMTQuNzg1NzQxOCwxNC4zMjQ2NSBDMTguNzIxODU3OCwxMS4wOTM3ODIgMjMuNDAwNjM3MiwxMC41NDI1MzIxIDI3LjExMzk1NDIsMTAuNTQyNTMyMSBMNDEuMjk4ODI1LDEwLjU0MjUzMjEgTDM2Ljg5MjM1NTUsMTMuMDE2OTc2NSBMMzIuNjM0NDE4NywxMy4wMTY5NzY1IEMzNC4yMTg3NjczLDE0LjMyNDY1IDM3LjUxMTI0MTcsMTcuMDc1OTU1MyAzNy41MTEyNDE3LDIyLjMxMTU5MjkgQzM3LjUxMTI0MTcsMjcuNDAzODU2MSAzNC42MTQ4NTQ0LDI5LjgwMTY2OTQgMzEuNzQzMjIyNiwzMi4wNzU4ODQgQzMwLjgyNzI3MTEsMzIuOTY1Nzk0MSAyOS44MTIyOTc4LDMzLjkyOTg2MzMgMjkuODEyMjk3OCwzNS40Mzc3NjY1IEMyOS44MTIyOTc4LDM2Ljk0NTY2OTcgMzAuODI3MjcxMSwzNy43ODYxNDAzIDMxLjU5NDY5LDM4LjQwNDEzMzQgTDM0LjA3MDIzNDYsNDAuMzMyMjcxOSBDMzcuMTE1MTU0NSw0Mi44NTM2ODM4IDM5Ljg2MzAwOTEsNDUuMjAyMDU3NiAzOS44NjMwMDkxLDQ5Ljk0ODI0NDcgQzM5Ljg2MzAwOTEsNTMuMDc4MTc5MiAzOC40MDAyNTI5LDU2LjIxOTY2MDMgMzUuNTUwMTgxMSw1OC42MzA1MzAyIEMzNC4wMTY3MDEyLDU4Ljg4MDE3NzUgMzIuNDQzNTc1Myw1OS4wMTE5NjcxIDMwLjg0MDQzMjQsNTkuMDE2MjgzOSBDMzMuNzM0NDYwMyw1Ny43NDg2MzExIDM1LjIzMzc0MDYsNTUuNDI5MjU1NiAzNS4yMzM3NDA2LDUyLjY0MjY5NDYgQzM1LjIzMzc0MDYsNDkuMTMyNDkzOCAzMi45ODA5OTUsNDcuMjc4NTE0NSAyNy43MzI4NDAzLDQzLjU0NTgzNjEgQzI3LjE4ODIyMDUsNDMuNDk2Mzk2NiAyNi44NDE2NDQyLDQzLjQ5NjM5NjYgMjYuMTQ4NDkxNyw0My40OTYzOTY2IEMyNS41Mjk2MDU2LDQzLjQ5NjM5NjYgMjEuODE2Mjg4Niw0My42MTk5OTUzIDE4LjkxOTkwMTQsNDQuNTg0MDY0NSBDMTcuNDA5ODE5MSw0NS4xMjc4OTg0IDEzLjAwMzM0OTcsNDYuNzg0MTIgMTMuMDAzMzQ5Nyw1MS42Nzg2MjU0IEMxMy4wMDMzNDk3LDUyLjIxMDUzODQgMTMuMDYwMDU2Myw1Mi43MjYyMzA4IDEzLjE3MDY5NTEsNTMuMjIyOTAwMSBDNS45MTIzMTMsNDcuODQ2Mjg5OCA5LjA1NjYzMjU5LDQ4LjYwNTA4MjQgOC4yMzAzMzg4Myw0OC42MDUwODExIFogTTMxLjQ0NjE1NzMsMjUuNDc1NzE3NiBDMzEuNDQ2MTU3MywyMC41MDcwNTMgMjguNTAwMjU5MiwxMi44MTE4MDI4IDIyLjc4MTc1MSwxMi44MTE4MDI4IEMyMC45OTkzNTg5LDEyLjgxMTgwMjggMTkuMDY4NDM0LDEzLjcwNjY1NjggMTcuOTU0NDM5LDE1LjA4MzU0NTUgQzE2Ljc5MDkzMywxNi41MjcxNzc0IDE2LjQ0NDM1NjcsMTguMzgxMTU2NyAxNi40NDQzNTY3LDIwLjE2MDk3NjkgQzE2LjQ0NDM1NjcsMjQuNzgzNTY1MyAxOS4xMTc5NDQ5LDMyLjQyMTk2MDEgMjUuMDU5MjUyMSwzMi40MjE5NjAxIEMyNi43NjczNzc5LDMyLjQyMTk2MDEgMjguNjI0MDM2NCwzMS41ODE0ODk1IDI5LjczODAzMTUsMzAuNDkzODIxNiBDMzEuMzIyMzgwMSwyOC45MTE3NTkzIDMxLjQ0NjE1NzMsMjYuNzExNzAzOCAzMS40NDYxNTczLDI1LjQ3NTcxNzYgWiBNMzEuNDQ2MTU3MywyNS40NzU3MTc2IiBpZD0iUGF0aCIgZmlsbD0iI0ZGRkZGRiIgc2tldGNoOnR5cGU9Ik1TU2hhcGVHcm91cCI+PC9wYXRoPgogICAgICAgICAgICAgICAgPHBhdGggZD0iTTU5LjI3OTM3MzcsMjkuNjg1ODI1MiBDNTkuMjc5MzczNyw0NS45ODI3NTMxIDQ2LjA0OTAxMzQsNTkuMTk0MDIxOSAyOS43Mjg1MzUxLDU5LjE5NDAyMTkgQzIzLjY3NTY1NjMsNTkuMTk0MDIxOSAxOC4wNDc4MjA4LDU3LjM3NjgyMiAxMy4zNjI0NDAyLDU0LjI1OTA0NjkgTDQ3LjIyMjY2MTUsNS45MDE2MzkzNCBDNTQuNTM0NTU5NSwxMS4yNzMzNTAxIDU5LjI3OTM3MzcsMTkuOTI2MjgxNiA1OS4yNzkzNzM3LDI5LjY4NTgyNTIgWiBNNTkuMjc5MzczNywyOS42ODU4MjUyIiBpZD0icmVmbGVjIiBmaWxsLW9wYWNpdHk9IjAuMDgiIGZpbGw9IiMwMDAwMDAiIHNrZXRjaDp0eXBlPSJNU1NoYXBlR3JvdXAiPjwvcGF0aD4KICAgICAgICAgICAgPC9nPgogICAgICAgIDwvZz4KICAgIDwvZz4KPC9zdmc+); }
-
-}
diff --git a/_sass/_variables.scss b/_sass/_variables.scss
deleted file mode 100644
index e56c1c5a68e15..0000000000000
--- a/_sass/_variables.scss
+++ /dev/null
@@ -1,27 +0,0 @@
-
-//
-// VARIABLES
-//
-
-// Colors
-$blue: #4183C4;
-
-// Grays
-$black: #000;
-$darkerGray: #222;
-$darkGray: #333;
-$gray: #666;
-$lightGray: #eee;
-$white: #fff;
-
-// Font stacks
-$helvetica: Helvetica, Arial, sans-serif;
-$helveticaNeue: "Helvetica Neue", Helvetica, Arial, sans-serif;
-$georgia: Georgia, serif;
-
-// Mobile breakpoints
-@mixin mobile {
- @media screen and (max-width: 640px) {
- @content;
- }
-}
\ No newline at end of file
diff --git a/_tabs/about.md b/_tabs/about.md
new file mode 100644
index 0000000000000..db12750b36845
--- /dev/null
+++ b/_tabs/about.md
@@ -0,0 +1,43 @@
+---
+# the default layout is 'page'
+icon: fas fa-info-circle
+order: 4
+---
+
+I am currently a Quality Engineer [@adahealth](https://twitter.com/adahealth), where I work across the Medical Platform group, working alongside Software Engineers, AI Scientists and Medical Knowledge Engineers.
+
+I started my adventure into software testing and exploring quality ten years ago in 2012. In this time I have developed a keen sense of [what quality means to me](https://www.dowen.me.uk/posts/what-does-quality-mean-to-me/ "What quality means to me"), and [reflected on my various roles](https://www.dowen.me.uk/posts/when-is-a-tester-not-a-tester/ "When is a software tester not a software tester").
+
+I have worked in a range of domains, across Enterprise Virtualisation, Consultancy, Racing and Betting and now Health Technology. Demonstrating skills in various technologies hosted on platforms including bare metal and virtualisation up to enterprise solutions to modern cloud infrastructure.
+
+I've worked on modern NodeJS micro-services running high performance event driven architectures. mobile and web apps, backend APIs and AI powered libraries.
+
+I use a combination of test analysis, automation and tool building and collaborative exploratory testing to support teams to build better software.
+
+I support the testing community, [advocating for software testing](https://youtu.be/lZgtN0d9i4w "Ben talking with Karen Tests Stuff on YouTube"), and celebrated those in the community via [Tester of The Day.](https://www.testeroftheday.com "Tester of The Day")
+
+## Portfolio
+
+My portfolio is work in progress, at this time it is a good landing page to my various projects and social media presence. Over time I will develop it further.
+
+[https://www.fullsnacktester.com](https://www.fullsnacktester.com "https://www.fullsnacktester.com")
+
+## Tester of The Day
+
+The daily celebration of the software testing community, started in 2020 has gone from strength to strength.
+
+[Testers Hall of Fame](https://www.testeroftheday.com "Testers Hall of Fame")
+
+[How to nominate someone for Tester of The Day](https://www.dowen.me.uk/posts/how-to-nominate-someone-for-testeroftheday/ "How to nominate for tester of the day").
+
+## Appearances
+
+[I have appeared as a guest on a number of podcasts, panel discussions and YouTube.](https://www.dowen.me.uk/posts/appearances/)
+
+## Contact me
+
+I am especially active on Twitter, and occasionally check LinkedIn.
+
+[https://twitter.com/fullsnacktester](https://twitter.com/fullsnacktester "FullSnackTester on Twitter")
+
+[https://www.linkedin.com/in/dowenb/](https://www.linkedin.com/in/dowenb/ "https://www.linkedin.com/in/dowenb/")
diff --git a/_tabs/appearances.md b/_tabs/appearances.md
new file mode 100644
index 0000000000000..d0696877ac599
--- /dev/null
+++ b/_tabs/appearances.md
@@ -0,0 +1,41 @@
+---
+# Details of my public appearances
+icon: fas fa-microphone
+order: 5
+---
+
+I have appeared as a guest on a number of podcasts, panel discussions and YouTube.
+
+## Test Bash
+
+### Discussion: How To Get More Involved with the MoT Community - Louise Gibbs, Karen Todd and Ben Dowen
+
+[https://www.ministryoftesting.com/dojo/series/testbash-world-2022/lessons/discussion-how-to-get-more-involved-with-the-mot-community-louise-gibbs-karen-todd-and-ben-dowen](https://www.ministryoftesting.com/dojo/series/testbash-world-2022/lessons/discussion-how-to-get-more-involved-with-the-mot-community-louise-gibbs-karen-todd-and-ben-dowen "https://www.ministryoftesting.com/dojo/series/testbash-world-2022/lessons/discussion-how-to-get-more-involved-with-the-mot-community-louise-gibbs-karen-todd-and-ben-dowen")
+
+## Podcasts
+
+### MoT Podcast - Quality Panel
+
+[https://ministryoftesting.com/dojo/series/the-ministry-of-testing-podcast-2021/lessons/mot-podcast-quality-panel](https://ministryoftesting.com/dojo/series/the-ministry-of-testing-podcast-2021/lessons/mot-podcast-quality-panel "https://ministryoftesting.com/dojo/series/the-ministry-of-testing-podcast-2021/lessons/mot-podcast-quality-panel")
+
+### TestSphere Roulette Episode 7 - Beren Van Daele And Ben Dowen
+
+[https://www.ministryoftesting.com/dojo/lessons/testsphere-roulette-episode-7-beren-van-daele-and-ben-dowen](https://www.ministryoftesting.com/dojo/lessons/testsphere-roulette-episode-7-beren-van-daele-and-ben-dowen "https://www.ministryoftesting.com/dojo/lessons/testsphere-roulette-episode-7-beren-van-daele-and-ben-dowen")
+
+### MoT Podcast - Adam meets Ben Dowen
+
+[https://www.ministryoftesting.com/dojo/lessons/mot-podcast-adam-meets-ben-dowen](https://www.ministryoftesting.com/dojo/lessons/mot-podcast-adam-meets-ben-dowen "https://www.ministryoftesting.com/dojo/lessons/mot-podcast-adam-meets-ben-dowen")
+
+### The Testing Show: API Testing
+
+[https://qualitestgroup.com/insights/podcasts/the-testing-show-api-testing/](https://qualitestgroup.com/insights/podcasts/the-testing-show-api-testing/ "https://qualitestgroup.com/insights/podcasts/the-testing-show-api-testing/")
+
+## YouTube
+
+### Testing Against Acceptance Criteria And Beyond - Interview with Ben Dowen
+
+[https://youtu.be/OKCQHOkve-E](https://youtu.be/OKCQHOkve-E "https://youtu.be/OKCQHOkve-E")
+
+### Advocacy for YOUR Context - feat. Ben Dowen
+
+[https://youtu.be/lZgtN0d9i4w](https://youtu.be/lZgtN0d9i4w "https://youtu.be/lZgtN0d9i4w")
\ No newline at end of file
diff --git a/_tabs/archives.md b/_tabs/archives.md
new file mode 100644
index 0000000000000..1b42e9552cd25
--- /dev/null
+++ b/_tabs/archives.md
@@ -0,0 +1,6 @@
+---
+layout: archives
+icon: fas fa-archive
+order: 3
+---
+
diff --git a/_tabs/categories.md b/_tabs/categories.md
new file mode 100644
index 0000000000000..2d241be9264eb
--- /dev/null
+++ b/_tabs/categories.md
@@ -0,0 +1,5 @@
+---
+layout: categories
+icon: fas fa-stream
+order: 1
+---
diff --git a/_tabs/tags.md b/_tabs/tags.md
new file mode 100644
index 0000000000000..c8e213afa1758
--- /dev/null
+++ b/_tabs/tags.md
@@ -0,0 +1,5 @@
+---
+layout: tags
+icon: fas fa-tag
+order: 2
+---
diff --git a/about.md b/about.md
deleted file mode 100644
index bc21f5731bf4b..0000000000000
--- a/about.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-layout: page
-title: About
-permalink: /about/
----
-
-Some information about you!
-
-### More Information
-
-A place to include any other types of information that you'd like to include about yourself.
-
-### Contact me
-
-[email@domain.com](mailto:email@domain.com)
\ No newline at end of file
diff --git a/assets/admin/.gitignore b/assets/admin/.gitignore
new file mode 100644
index 0000000000000..c6a8f8ff67706
--- /dev/null
+++ b/assets/admin/.gitignore
@@ -0,0 +1,2 @@
+index.html
+assets/
\ No newline at end of file
diff --git a/assets/img/favicons/android-chrome-192x192.png b/assets/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000000..85df3b2ec0adc
Binary files /dev/null and b/assets/img/favicons/android-chrome-192x192.png differ
diff --git a/assets/img/favicons/android-chrome-384x384.png b/assets/img/favicons/android-chrome-384x384.png
new file mode 100644
index 0000000000000..e2e86d936c357
Binary files /dev/null and b/assets/img/favicons/android-chrome-384x384.png differ
diff --git a/assets/img/favicons/apple-touch-icon.png b/assets/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000000..e78c002bc2dc0
Binary files /dev/null and b/assets/img/favicons/apple-touch-icon.png differ
diff --git a/assets/img/favicons/favicon-16x16.png b/assets/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000000..7e79cf3a0396c
Binary files /dev/null and b/assets/img/favicons/favicon-16x16.png differ
diff --git a/assets/img/favicons/favicon-32x32.png b/assets/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000000..39f9f009667d1
Binary files /dev/null and b/assets/img/favicons/favicon-32x32.png differ
diff --git a/assets/img/favicons/favicon.ico b/assets/img/favicons/favicon.ico
new file mode 100644
index 0000000000000..d6c2559dcf3c0
Binary files /dev/null and b/assets/img/favicons/favicon.ico differ
diff --git a/assets/img/favicons/mstile-150x150.png b/assets/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000000..d8c5d4d246443
Binary files /dev/null and b/assets/img/favicons/mstile-150x150.png differ
diff --git a/assets/img/favicons/safari-pinned-tab.svg b/assets/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000000..9933dc2482d63
--- /dev/null
+++ b/assets/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,90 @@
+
+
+
diff --git a/assets/lib/.editorconfig b/assets/lib/.editorconfig
new file mode 100644
index 0000000000000..cdded4641a870
--- /dev/null
+++ b/assets/lib/.editorconfig
@@ -0,0 +1,11 @@
+root = true
+
+[*]
+charset = utf-8
+# 2 space indentation
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = true
+# Unix-style newlines with a newline ending every file
+end_of_line = lf
+insert_final_newline = true
diff --git a/assets/lib/.gitignore b/assets/lib/.gitignore
new file mode 100644
index 0000000000000..30d49dba11209
--- /dev/null
+++ b/assets/lib/.gitignore
@@ -0,0 +1,4 @@
+# hidden files
+.*
+!.git*
+!.editorconfig
diff --git a/assets/lib/LICENSE b/assets/lib/LICENSE
new file mode 100644
index 0000000000000..7a71a7a357425
--- /dev/null
+++ b/assets/lib/LICENSE
@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2022 Cotes Chung
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/assets/lib/README.md b/assets/lib/README.md
new file mode 100644
index 0000000000000..cbb26e4e2590b
--- /dev/null
+++ b/assets/lib/README.md
@@ -0,0 +1,51 @@
+# Static Assets for Chirpy Jekyll Theme
+
+## Introduction
+
+Static assets (libraries/plugins/web-fonts) required by the [_Chirpy_][chirpy] based website to run. It provides the opportunity to choose self-host assets in production or development mode.
+
+## Usage
+
+- If you want to use these assets only in local development:
+
+ Go to the root of your site and clone the assets as follows.
+
+ ```console
+ $ cd assets/lib
+ $ git submodule init
+ $ git submodule update
+ ```
+
+ And then set your site configuration options:
+
+ ```yml
+ # _config.yml
+ assets:
+ self_host:
+ enabled: true
+ env: development
+ ```
+
+- If you expect the assets to be self-hosted when your website is published:
+
+ Keep the `_config.yml` options as follows:
+
+ ```yml
+ # _config.yml
+ assets:
+ self_host:
+ enabled: true
+ ```
+
+ And then update the GitHub Actions workflow in `.github/workflows/pages-deploy.yml`:
+
+ ```diff
+ steps:
+ - name: Checkout
+ uses: actions/checkout@v2
+ with:
+ + submodules: true
+ ```
+
+[assets]: https://github.com/cotes2020/chirpy-static-assets
+[chirpy]: https://github.com/cotes2020/jekyll-theme-chirpy
diff --git a/assets/lib/bootstrap-4.6.1/bootstrap.bundle.min.js b/assets/lib/bootstrap-4.6.1/bootstrap.bundle.min.js
new file mode 100644
index 0000000000000..3af2dc364474c
--- /dev/null
+++ b/assets/lib/bootstrap-4.6.1/bootstrap.bundle.min.js
@@ -0,0 +1,7 @@
+/*!
+ * Bootstrap v4.6.1 (https://getbootstrap.com/)
+ * Copyright 2011-2021 The Bootstrap Authors (https://github.com/twbs/bootstrap/graphs/contributors)
+ * Licensed under MIT (https://github.com/twbs/bootstrap/blob/main/LICENSE)
+ */
+!function(t,e){"object"==typeof exports&&"undefined"!=typeof module?e(exports,require("jquery")):"function"==typeof define&&define.amd?define(["exports","jquery"],e):e((t="undefined"!=typeof globalThis?globalThis:t||self).bootstrap={},t.jQuery)}(this,(function(t,e){"use strict";function n(t){return t&&"object"==typeof t&&"default"in t?t:{default:t}}var i=n(e);function o(t,e){for(var n=0;n=4)throw new Error("Bootstrap's JavaScript requires at least jQuery v1.9.1 but less than v4.0.0")}};u.jQueryDetection(),i.default.fn.emulateTransitionEnd=function(t){var e=this,n=!1;return i.default(this).one(u.TRANSITION_END,(function(){n=!0})),setTimeout((function(){n||u.triggerTransitionEnd(e)}),t),this},i.default.event.special[u.TRANSITION_END]={bindType:l,delegateType:l,handle:function(t){if(i.default(t.target).is(this))return t.handleObj.handler.apply(this,arguments)}};var f="bs.alert",d=i.default.fn.alert,c=function(){function t(t){this._element=t}var e=t.prototype;return e.close=function(t){var e=this._element;t&&(e=this._getRootElement(t)),this._triggerCloseEvent(e).isDefaultPrevented()||this._removeElement(e)},e.dispose=function(){i.default.removeData(this._element,f),this._element=null},e._getRootElement=function(t){var e=u.getSelectorFromElement(t),n=!1;return e&&(n=document.querySelector(e)),n||(n=i.default(t).closest(".alert")[0]),n},e._triggerCloseEvent=function(t){var e=i.default.Event("close.bs.alert");return i.default(t).trigger(e),e},e._removeElement=function(t){var e=this;if(i.default(t).removeClass("show"),i.default(t).hasClass("fade")){var n=u.getTransitionDurationFromElement(t);i.default(t).one(u.TRANSITION_END,(function(n){return e._destroyElement(t,n)})).emulateTransitionEnd(n)}else this._destroyElement(t)},e._destroyElement=function(t){i.default(t).detach().trigger("closed.bs.alert").remove()},t._jQueryInterface=function(e){return this.each((function(){var n=i.default(this),o=n.data(f);o||(o=new t(this),n.data(f,o)),"close"===e&&o[e](this)}))},t._handleDismiss=function(t){return function(e){e&&e.preventDefault(),t.close(this)}},r(t,null,[{key:"VERSION",get:function(){return"4.6.1"}}]),t}();i.default(document).on("click.bs.alert.data-api",'[data-dismiss="alert"]',c._handleDismiss(new c)),i.default.fn.alert=c._jQueryInterface,i.default.fn.alert.Constructor=c,i.default.fn.alert.noConflict=function(){return i.default.fn.alert=d,c._jQueryInterface};var h="bs.button",p=i.default.fn.button,m="active",g='[data-toggle^="button"]',_='input:not([type="hidden"])',v=".btn",b=function(){function t(t){this._element=t,this.shouldAvoidTriggerChange=!1}var e=t.prototype;return e.toggle=function(){var t=!0,e=!0,n=i.default(this._element).closest('[data-toggle="buttons"]')[0];if(n){var o=this._element.querySelector(_);if(o){if("radio"===o.type)if(o.checked&&this._element.classList.contains(m))t=!1;else{var r=n.querySelector(".active");r&&i.default(r).removeClass(m)}t&&("checkbox"!==o.type&&"radio"!==o.type||(o.checked=!this._element.classList.contains(m)),this.shouldAvoidTriggerChange||i.default(o).trigger("change")),o.focus(),e=!1}}this._element.hasAttribute("disabled")||this._element.classList.contains("disabled")||(e&&this._element.setAttribute("aria-pressed",!this._element.classList.contains(m)),t&&i.default(this._element).toggleClass(m))},e.dispose=function(){i.default.removeData(this._element,h),this._element=null},t._jQueryInterface=function(e,n){return this.each((function(){var o=i.default(this),r=o.data(h);r||(r=new t(this),o.data(h,r)),r.shouldAvoidTriggerChange=n,"toggle"===e&&r[e]()}))},r(t,null,[{key:"VERSION",get:function(){return"4.6.1"}}]),t}();i.default(document).on("click.bs.button.data-api",g,(function(t){var e=t.target,n=e;if(i.default(e).hasClass("btn")||(e=i.default(e).closest(v)[0]),!e||e.hasAttribute("disabled")||e.classList.contains("disabled"))t.preventDefault();else{var o=e.querySelector(_);if(o&&(o.hasAttribute("disabled")||o.classList.contains("disabled")))return void t.preventDefault();"INPUT"!==n.tagName&&"LABEL"===e.tagName||b._jQueryInterface.call(i.default(e),"toggle","INPUT"===n.tagName)}})).on("focus.bs.button.data-api blur.bs.button.data-api",g,(function(t){var e=i.default(t.target).closest(v)[0];i.default(e).toggleClass("focus",/^focus(in)?$/.test(t.type))})),i.default(window).on("load.bs.button.data-api",(function(){for(var t=[].slice.call(document.querySelectorAll('[data-toggle="buttons"] .btn')),e=0,n=t.length;e0,this._pointerEvent=Boolean(window.PointerEvent||window.MSPointerEvent),this._addEventListeners()}var e=t.prototype;return e.next=function(){this._isSliding||this._slide(C)},e.nextWhenVisible=function(){var t=i.default(this._element);!document.hidden&&t.is(":visible")&&"hidden"!==t.css("visibility")&&this.next()},e.prev=function(){this._isSliding||this._slide(S)},e.pause=function(t){t||(this._isPaused=!0),this._element.querySelector(".carousel-item-next, .carousel-item-prev")&&(u.triggerTransitionEnd(this._element),this.cycle(!0)),clearInterval(this._interval),this._interval=null},e.cycle=function(t){t||(this._isPaused=!1),this._interval&&(clearInterval(this._interval),this._interval=null),this._config.interval&&!this._isPaused&&(this._updateInterval(),this._interval=setInterval((document.visibilityState?this.nextWhenVisible:this.next).bind(this),this._config.interval))},e.to=function(t){var e=this;this._activeElement=this._element.querySelector(D);var n=this._getItemIndex(this._activeElement);if(!(t>this._items.length-1||t<0))if(this._isSliding)i.default(this._element).one(N,(function(){return e.to(t)}));else{if(n===t)return this.pause(),void this.cycle();var o=t>n?C:S;this._slide(o,this._items[t])}},e.dispose=function(){i.default(this._element).off(".bs.carousel"),i.default.removeData(this._element,E),this._items=null,this._config=null,this._element=null,this._interval=null,this._isPaused=null,this._isSliding=null,this._activeElement=null,this._indicatorsElement=null},e._getConfig=function(t){return t=a({},A,t),u.typeCheckConfig(y,t,k),t},e._handleSwipe=function(){var t=Math.abs(this.touchDeltaX);if(!(t<=40)){var e=t/this.touchDeltaX;this.touchDeltaX=0,e>0&&this.prev(),e<0&&this.next()}},e._addEventListeners=function(){var t=this;this._config.keyboard&&i.default(this._element).on("keydown.bs.carousel",(function(e){return t._keydown(e)})),"hover"===this._config.pause&&i.default(this._element).on("mouseenter.bs.carousel",(function(e){return t.pause(e)})).on("mouseleave.bs.carousel",(function(e){return t.cycle(e)})),this._config.touch&&this._addTouchEventListeners()},e._addTouchEventListeners=function(){var t=this;if(this._touchSupported){var e=function(e){t._pointerEvent&&I[e.originalEvent.pointerType.toUpperCase()]?t.touchStartX=e.originalEvent.clientX:t._pointerEvent||(t.touchStartX=e.originalEvent.touches[0].clientX)},n=function(e){t._pointerEvent&&I[e.originalEvent.pointerType.toUpperCase()]&&(t.touchDeltaX=e.originalEvent.clientX-t.touchStartX),t._handleSwipe(),"hover"===t._config.pause&&(t.pause(),t.touchTimeout&&clearTimeout(t.touchTimeout),t.touchTimeout=setTimeout((function(e){return t.cycle(e)}),500+t._config.interval))};i.default(this._element.querySelectorAll(".carousel-item img")).on("dragstart.bs.carousel",(function(t){return t.preventDefault()})),this._pointerEvent?(i.default(this._element).on("pointerdown.bs.carousel",(function(t){return e(t)})),i.default(this._element).on("pointerup.bs.carousel",(function(t){return n(t)})),this._element.classList.add("pointer-event")):(i.default(this._element).on("touchstart.bs.carousel",(function(t){return e(t)})),i.default(this._element).on("touchmove.bs.carousel",(function(e){return function(e){t.touchDeltaX=e.originalEvent.touches&&e.originalEvent.touches.length>1?0:e.originalEvent.touches[0].clientX-t.touchStartX}(e)})),i.default(this._element).on("touchend.bs.carousel",(function(t){return n(t)})))}},e._keydown=function(t){if(!/input|textarea/i.test(t.target.tagName))switch(t.which){case 37:t.preventDefault(),this.prev();break;case 39:t.preventDefault(),this.next()}},e._getItemIndex=function(t){return this._items=t&&t.parentNode?[].slice.call(t.parentNode.querySelectorAll(".carousel-item")):[],this._items.indexOf(t)},e._getItemByDirection=function(t,e){var n=t===C,i=t===S,o=this._getItemIndex(e),r=this._items.length-1;if((i&&0===o||n&&o===r)&&!this._config.wrap)return e;var a=(o+(t===S?-1:1))%this._items.length;return-1===a?this._items[this._items.length-1]:this._items[a]},e._triggerSlideEvent=function(t,e){var n=this._getItemIndex(t),o=this._getItemIndex(this._element.querySelector(D)),r=i.default.Event("slide.bs.carousel",{relatedTarget:t,direction:e,from:o,to:n});return i.default(this._element).trigger(r),r},e._setActiveIndicatorElement=function(t){if(this._indicatorsElement){var e=[].slice.call(this._indicatorsElement.querySelectorAll(".active"));i.default(e).removeClass(T);var n=this._indicatorsElement.children[this._getItemIndex(t)];n&&i.default(n).addClass(T)}},e._updateInterval=function(){var t=this._activeElement||this._element.querySelector(D);if(t){var e=parseInt(t.getAttribute("data-interval"),10);e?(this._config.defaultInterval=this._config.defaultInterval||this._config.interval,this._config.interval=e):this._config.interval=this._config.defaultInterval||this._config.interval}},e._slide=function(t,e){var n,o,r,a=this,s=this._element.querySelector(D),l=this._getItemIndex(s),f=e||s&&this._getItemByDirection(t,s),d=this._getItemIndex(f),c=Boolean(this._interval);if(t===C?(n="carousel-item-left",o="carousel-item-next",r="left"):(n="carousel-item-right",o="carousel-item-prev",r="right"),f&&i.default(f).hasClass(T))this._isSliding=!1;else if(!this._triggerSlideEvent(f,r).isDefaultPrevented()&&s&&f){this._isSliding=!0,c&&this.pause(),this._setActiveIndicatorElement(f),this._activeElement=f;var h=i.default.Event(N,{relatedTarget:f,direction:r,from:l,to:d});if(i.default(this._element).hasClass("slide")){i.default(f).addClass(o),u.reflow(f),i.default(s).addClass(n),i.default(f).addClass(n);var p=u.getTransitionDurationFromElement(s);i.default(s).one(u.TRANSITION_END,(function(){i.default(f).removeClass(n+" "+o).addClass(T),i.default(s).removeClass("active "+o+" "+n),a._isSliding=!1,setTimeout((function(){return i.default(a._element).trigger(h)}),0)})).emulateTransitionEnd(p)}else i.default(s).removeClass(T),i.default(f).addClass(T),this._isSliding=!1,i.default(this._element).trigger(h);c&&this.cycle()}},t._jQueryInterface=function(e){return this.each((function(){var n=i.default(this).data(E),o=a({},A,i.default(this).data());"object"==typeof e&&(o=a({},o,e));var r="string"==typeof e?e:o.slide;if(n||(n=new t(this,o),i.default(this).data(E,n)),"number"==typeof e)n.to(e);else if("string"==typeof r){if("undefined"==typeof n[r])throw new TypeError('No method named "'+r+'"');n[r]()}else o.interval&&o.ride&&(n.pause(),n.cycle())}))},t._dataApiClickHandler=function(e){var n=u.getSelectorFromElement(this);if(n){var o=i.default(n)[0];if(o&&i.default(o).hasClass("carousel")){var r=a({},i.default(o).data(),i.default(this).data()),s=this.getAttribute("data-slide-to");s&&(r.interval=!1),t._jQueryInterface.call(i.default(o),r),s&&i.default(o).data(E).to(s),e.preventDefault()}}},r(t,null,[{key:"VERSION",get:function(){return"4.6.1"}},{key:"Default",get:function(){return A}}]),t}();i.default(document).on("click.bs.carousel.data-api","[data-slide], [data-slide-to]",O._dataApiClickHandler),i.default(window).on("load.bs.carousel.data-api",(function(){for(var t=[].slice.call(document.querySelectorAll('[data-ride="carousel"]')),e=0,n=t.length;e0&&(this._selector=a,this._triggerArray.push(r))}this._parent=this._config.parent?this._getParent():null,this._config.parent||this._addAriaAndCollapsedClass(this._element,this._triggerArray),this._config.toggle&&this.toggle()}var e=t.prototype;return e.toggle=function(){i.default(this._element).hasClass(P)?this.hide():this.show()},e.show=function(){var e,n,o=this;if(!(this._isTransitioning||i.default(this._element).hasClass(P)||(this._parent&&0===(e=[].slice.call(this._parent.querySelectorAll(".show, .collapsing")).filter((function(t){return"string"==typeof o._config.parent?t.getAttribute("data-parent")===o._config.parent:t.classList.contains(F)}))).length&&(e=null),e&&(n=i.default(e).not(this._selector).data(j))&&n._isTransitioning))){var r=i.default.Event("show.bs.collapse");if(i.default(this._element).trigger(r),!r.isDefaultPrevented()){e&&(t._jQueryInterface.call(i.default(e).not(this._selector),"hide"),n||i.default(e).data(j,null));var a=this._getDimension();i.default(this._element).removeClass(F).addClass(R),this._element.style[a]=0,this._triggerArray.length&&i.default(this._triggerArray).removeClass(H).attr("aria-expanded",!0),this.setTransitioning(!0);var s="scroll"+(a[0].toUpperCase()+a.slice(1)),l=u.getTransitionDurationFromElement(this._element);i.default(this._element).one(u.TRANSITION_END,(function(){i.default(o._element).removeClass(R).addClass("collapse show"),o._element.style[a]="",o.setTransitioning(!1),i.default(o._element).trigger("shown.bs.collapse")})).emulateTransitionEnd(l),this._element.style[a]=this._element[s]+"px"}}},e.hide=function(){var t=this;if(!this._isTransitioning&&i.default(this._element).hasClass(P)){var e=i.default.Event("hide.bs.collapse");if(i.default(this._element).trigger(e),!e.isDefaultPrevented()){var n=this._getDimension();this._element.style[n]=this._element.getBoundingClientRect()[n]+"px",u.reflow(this._element),i.default(this._element).addClass(R).removeClass("collapse show");var o=this._triggerArray.length;if(o>0)for(var r=0;r=0)return 1;return 0}(),Y=U&&window.Promise?function(t){var e=!1;return function(){e||(e=!0,window.Promise.resolve().then((function(){e=!1,t()})))}}:function(t){var e=!1;return function(){e||(e=!0,setTimeout((function(){e=!1,t()}),V))}};function z(t){return t&&"[object Function]"==={}.toString.call(t)}function K(t,e){if(1!==t.nodeType)return[];var n=t.ownerDocument.defaultView.getComputedStyle(t,null);return e?n[e]:n}function X(t){return"HTML"===t.nodeName?t:t.parentNode||t.host}function G(t){if(!t)return document.body;switch(t.nodeName){case"HTML":case"BODY":return t.ownerDocument.body;case"#document":return t.body}var e=K(t),n=e.overflow,i=e.overflowX,o=e.overflowY;return/(auto|scroll|overlay)/.test(n+o+i)?t:G(X(t))}function $(t){return t&&t.referenceNode?t.referenceNode:t}var J=U&&!(!window.MSInputMethodContext||!document.documentMode),Z=U&&/MSIE 10/.test(navigator.userAgent);function tt(t){return 11===t?J:10===t?Z:J||Z}function et(t){if(!t)return document.documentElement;for(var e=tt(10)?document.body:null,n=t.offsetParent||null;n===e&&t.nextElementSibling;)n=(t=t.nextElementSibling).offsetParent;var i=n&&n.nodeName;return i&&"BODY"!==i&&"HTML"!==i?-1!==["TH","TD","TABLE"].indexOf(n.nodeName)&&"static"===K(n,"position")?et(n):n:t?t.ownerDocument.documentElement:document.documentElement}function nt(t){return null!==t.parentNode?nt(t.parentNode):t}function it(t,e){if(!(t&&t.nodeType&&e&&e.nodeType))return document.documentElement;var n=t.compareDocumentPosition(e)&Node.DOCUMENT_POSITION_FOLLOWING,i=n?t:e,o=n?e:t,r=document.createRange();r.setStart(i,0),r.setEnd(o,0);var a,s,l=r.commonAncestorContainer;if(t!==l&&e!==l||i.contains(o))return"BODY"===(s=(a=l).nodeName)||"HTML"!==s&&et(a.firstElementChild)!==a?et(l):l;var u=nt(t);return u.host?it(u.host,e):it(t,nt(e).host)}function ot(t){var e=arguments.length>1&&void 0!==arguments[1]?arguments[1]:"top",n="top"===e?"scrollTop":"scrollLeft",i=t.nodeName;if("BODY"===i||"HTML"===i){var o=t.ownerDocument.documentElement,r=t.ownerDocument.scrollingElement||o;return r[n]}return t[n]}function rt(t,e){var n=arguments.length>2&&void 0!==arguments[2]&&arguments[2],i=ot(e,"top"),o=ot(e,"left"),r=n?-1:1;return t.top+=i*r,t.bottom+=i*r,t.left+=o*r,t.right+=o*r,t}function at(t,e){var n="x"===e?"Left":"Top",i="Left"===n?"Right":"Bottom";return parseFloat(t["border"+n+"Width"])+parseFloat(t["border"+i+"Width"])}function st(t,e,n,i){return Math.max(e["offset"+t],e["scroll"+t],n["client"+t],n["offset"+t],n["scroll"+t],tt(10)?parseInt(n["offset"+t])+parseInt(i["margin"+("Height"===t?"Top":"Left")])+parseInt(i["margin"+("Height"===t?"Bottom":"Right")]):0)}function lt(t){var e=t.body,n=t.documentElement,i=tt(10)&&getComputedStyle(n);return{height:st("Height",e,n,i),width:st("Width",e,n,i)}}var ut=function(t,e){if(!(t instanceof e))throw new TypeError("Cannot call a class as a function")},ft=function(){function t(t,e){for(var n=0;n2&&void 0!==arguments[2]&&arguments[2],i=tt(10),o="HTML"===e.nodeName,r=pt(t),a=pt(e),s=G(t),l=K(e),u=parseFloat(l.borderTopWidth),f=parseFloat(l.borderLeftWidth);n&&o&&(a.top=Math.max(a.top,0),a.left=Math.max(a.left,0));var d=ht({top:r.top-a.top-u,left:r.left-a.left-f,width:r.width,height:r.height});if(d.marginTop=0,d.marginLeft=0,!i&&o){var c=parseFloat(l.marginTop),h=parseFloat(l.marginLeft);d.top-=u-c,d.bottom-=u-c,d.left-=f-h,d.right-=f-h,d.marginTop=c,d.marginLeft=h}return(i&&!n?e.contains(s):e===s&&"BODY"!==s.nodeName)&&(d=rt(d,e)),d}function gt(t){var e=arguments.length>1&&void 0!==arguments[1]&&arguments[1],n=t.ownerDocument.documentElement,i=mt(t,n),o=Math.max(n.clientWidth,window.innerWidth||0),r=Math.max(n.clientHeight,window.innerHeight||0),a=e?0:ot(n),s=e?0:ot(n,"left"),l={top:a-i.top+i.marginTop,left:s-i.left+i.marginLeft,width:o,height:r};return ht(l)}function _t(t){var e=t.nodeName;if("BODY"===e||"HTML"===e)return!1;if("fixed"===K(t,"position"))return!0;var n=X(t);return!!n&&_t(n)}function vt(t){if(!t||!t.parentElement||tt())return document.documentElement;for(var e=t.parentElement;e&&"none"===K(e,"transform");)e=e.parentElement;return e||document.documentElement}function bt(t,e,n,i){var o=arguments.length>4&&void 0!==arguments[4]&&arguments[4],r={top:0,left:0},a=o?vt(t):it(t,$(e));if("viewport"===i)r=gt(a,o);else{var s=void 0;"scrollParent"===i?"BODY"===(s=G(X(e))).nodeName&&(s=t.ownerDocument.documentElement):s="window"===i?t.ownerDocument.documentElement:i;var l=mt(s,a,o);if("HTML"!==s.nodeName||_t(a))r=l;else{var u=lt(t.ownerDocument),f=u.height,d=u.width;r.top+=l.top-l.marginTop,r.bottom=f+l.top,r.left+=l.left-l.marginLeft,r.right=d+l.left}}var c="number"==typeof(n=n||0);return r.left+=c?n:n.left||0,r.top+=c?n:n.top||0,r.right-=c?n:n.right||0,r.bottom-=c?n:n.bottom||0,r}function yt(t){return t.width*t.height}function Et(t,e,n,i,o){var r=arguments.length>5&&void 0!==arguments[5]?arguments[5]:0;if(-1===t.indexOf("auto"))return t;var a=bt(n,i,r,o),s={top:{width:a.width,height:e.top-a.top},right:{width:a.right-e.right,height:a.height},bottom:{width:a.width,height:a.bottom-e.bottom},left:{width:e.left-a.left,height:a.height}},l=Object.keys(s).map((function(t){return ct({key:t},s[t],{area:yt(s[t])})})).sort((function(t,e){return e.area-t.area})),u=l.filter((function(t){var e=t.width,i=t.height;return e>=n.clientWidth&&i>=n.clientHeight})),f=u.length>0?u[0].key:l[0].key,d=t.split("-")[1];return f+(d?"-"+d:"")}function wt(t,e,n){var i=arguments.length>3&&void 0!==arguments[3]?arguments[3]:null,o=i?vt(e):it(e,$(n));return mt(n,o,i)}function Tt(t){var e=t.ownerDocument.defaultView.getComputedStyle(t),n=parseFloat(e.marginTop||0)+parseFloat(e.marginBottom||0),i=parseFloat(e.marginLeft||0)+parseFloat(e.marginRight||0);return{width:t.offsetWidth+i,height:t.offsetHeight+n}}function Ct(t){var e={left:"right",right:"left",bottom:"top",top:"bottom"};return t.replace(/left|right|bottom|top/g,(function(t){return e[t]}))}function St(t,e,n){n=n.split("-")[0];var i=Tt(t),o={width:i.width,height:i.height},r=-1!==["right","left"].indexOf(n),a=r?"top":"left",s=r?"left":"top",l=r?"height":"width",u=r?"width":"height";return o[a]=e[a]+e[l]/2-i[l]/2,o[s]=n===s?e[s]-i[u]:e[Ct(s)],o}function Nt(t,e){return Array.prototype.find?t.find(e):t.filter(e)[0]}function Dt(t,e,n){return(void 0===n?t:t.slice(0,function(t,e,n){if(Array.prototype.findIndex)return t.findIndex((function(t){return t.name===n}));var i=Nt(t,(function(t){return t.name===n}));return t.indexOf(i)}(t,0,n))).forEach((function(t){t.function&&console.warn("`modifier.function` is deprecated, use `modifier.fn`!");var n=t.function||t.fn;t.enabled&&z(n)&&(e.offsets.popper=ht(e.offsets.popper),e.offsets.reference=ht(e.offsets.reference),e=n(e,t))})),e}function At(){if(!this.state.isDestroyed){var t={instance:this,styles:{},arrowStyles:{},attributes:{},flipped:!1,offsets:{}};t.offsets.reference=wt(this.state,this.popper,this.reference,this.options.positionFixed),t.placement=Et(this.options.placement,t.offsets.reference,this.popper,this.reference,this.options.modifiers.flip.boundariesElement,this.options.modifiers.flip.padding),t.originalPlacement=t.placement,t.positionFixed=this.options.positionFixed,t.offsets.popper=St(this.popper,t.offsets.reference,t.placement),t.offsets.popper.position=this.options.positionFixed?"fixed":"absolute",t=Dt(this.modifiers,t),this.state.isCreated?this.options.onUpdate(t):(this.state.isCreated=!0,this.options.onCreate(t))}}function kt(t,e){return t.some((function(t){var n=t.name;return t.enabled&&n===e}))}function It(t){for(var e=[!1,"ms","Webkit","Moz","O"],n=t.charAt(0).toUpperCase()+t.slice(1),i=0;i1&&void 0!==arguments[1]&&arguments[1],n=Qt.indexOf(t),i=Qt.slice(n+1).concat(Qt.slice(0,n));return e?i.reverse():i}var Ut={placement:"bottom",positionFixed:!1,eventsEnabled:!0,removeOnDestroy:!1,onCreate:function(){},onUpdate:function(){},modifiers:{shift:{order:100,enabled:!0,fn:function(t){var e=t.placement,n=e.split("-")[0],i=e.split("-")[1];if(i){var o=t.offsets,r=o.reference,a=o.popper,s=-1!==["bottom","top"].indexOf(n),l=s?"left":"top",u=s?"width":"height",f={start:dt({},l,r[l]),end:dt({},l,r[l]+r[u]-a[u])};t.offsets.popper=ct({},a,f[i])}return t}},offset:{order:200,enabled:!0,fn:function(t,e){var n,i=e.offset,o=t.placement,r=t.offsets,a=r.popper,s=r.reference,l=o.split("-")[0];return n=Rt(+i)?[+i,0]:function(t,e,n,i){var o=[0,0],r=-1!==["right","left"].indexOf(i),a=t.split(/(\+|\-)/).map((function(t){return t.trim()})),s=a.indexOf(Nt(a,(function(t){return-1!==t.search(/,|\s/)})));a[s]&&-1===a[s].indexOf(",")&&console.warn("Offsets separated by white space(s) are deprecated, use a comma (,) instead.");var l=/\s*,\s*|\s+/,u=-1!==s?[a.slice(0,s).concat([a[s].split(l)[0]]),[a[s].split(l)[1]].concat(a.slice(s+1))]:[a];return u=u.map((function(t,i){var o=(1===i?!r:r)?"height":"width",a=!1;return t.reduce((function(t,e){return""===t[t.length-1]&&-1!==["+","-"].indexOf(e)?(t[t.length-1]=e,a=!0,t):a?(t[t.length-1]+=e,a=!1,t):t.concat(e)}),[]).map((function(t){return function(t,e,n,i){var o=t.match(/((?:\-|\+)?\d*\.?\d*)(.*)/),r=+o[1],a=o[2];return r?0===a.indexOf("%")?ht("%p"===a?n:i)[e]/100*r:"vh"===a||"vw"===a?("vh"===a?Math.max(document.documentElement.clientHeight,window.innerHeight||0):Math.max(document.documentElement.clientWidth,window.innerWidth||0))/100*r:r:t}(t,o,e,n)}))})),u.forEach((function(t,e){t.forEach((function(n,i){Rt(n)&&(o[e]+=n*("-"===t[i-1]?-1:1))}))})),o}(i,a,s,l),"left"===l?(a.top+=n[0],a.left-=n[1]):"right"===l?(a.top+=n[0],a.left+=n[1]):"top"===l?(a.left+=n[0],a.top-=n[1]):"bottom"===l&&(a.left+=n[0],a.top+=n[1]),t.popper=a,t},offset:0},preventOverflow:{order:300,enabled:!0,fn:function(t,e){var n=e.boundariesElement||et(t.instance.popper);t.instance.reference===n&&(n=et(n));var i=It("transform"),o=t.instance.popper.style,r=o.top,a=o.left,s=o[i];o.top="",o.left="",o[i]="";var l=bt(t.instance.popper,t.instance.reference,e.padding,n,t.positionFixed);o.top=r,o.left=a,o[i]=s,e.boundaries=l;var u=e.priority,f=t.offsets.popper,d={primary:function(t){var n=f[t];return f[t]l[t]&&!e.escapeWithReference&&(i=Math.min(f[n],l[t]-("right"===t?f.width:f.height))),dt({},n,i)}};return u.forEach((function(t){var e=-1!==["left","top"].indexOf(t)?"primary":"secondary";f=ct({},f,d[e](t))})),t.offsets.popper=f,t},priority:["left","right","top","bottom"],padding:5,boundariesElement:"scrollParent"},keepTogether:{order:400,enabled:!0,fn:function(t){var e=t.offsets,n=e.popper,i=e.reference,o=t.placement.split("-")[0],r=Math.floor,a=-1!==["top","bottom"].indexOf(o),s=a?"right":"bottom",l=a?"left":"top",u=a?"width":"height";return n[s]r(i[s])&&(t.offsets.popper[l]=r(i[s])),t}},arrow:{order:500,enabled:!0,fn:function(t,e){var n;if(!qt(t.instance.modifiers,"arrow","keepTogether"))return t;var i=e.element;if("string"==typeof i){if(!(i=t.instance.popper.querySelector(i)))return t}else if(!t.instance.popper.contains(i))return console.warn("WARNING: `arrow.element` must be child of its popper element!"),t;var o=t.placement.split("-")[0],r=t.offsets,a=r.popper,s=r.reference,l=-1!==["left","right"].indexOf(o),u=l?"height":"width",f=l?"Top":"Left",d=f.toLowerCase(),c=l?"left":"top",h=l?"bottom":"right",p=Tt(i)[u];s[h]-pa[h]&&(t.offsets.popper[d]+=s[d]+p-a[h]),t.offsets.popper=ht(t.offsets.popper);var m=s[d]+s[u]/2-p/2,g=K(t.instance.popper),_=parseFloat(g["margin"+f]),v=parseFloat(g["border"+f+"Width"]),b=m-t.offsets.popper[d]-_-v;return b=Math.max(Math.min(a[u]-p,b),0),t.arrowElement=i,t.offsets.arrow=(dt(n={},d,Math.round(b)),dt(n,c,""),n),t},element:"[x-arrow]"},flip:{order:600,enabled:!0,fn:function(t,e){if(kt(t.instance.modifiers,"inner"))return t;if(t.flipped&&t.placement===t.originalPlacement)return t;var n=bt(t.instance.popper,t.instance.reference,e.padding,e.boundariesElement,t.positionFixed),i=t.placement.split("-")[0],o=Ct(i),r=t.placement.split("-")[1]||"",a=[];switch(e.behavior){case"flip":a=[i,o];break;case"clockwise":a=Wt(i);break;case"counterclockwise":a=Wt(i,!0);break;default:a=e.behavior}return a.forEach((function(s,l){if(i!==s||a.length===l+1)return t;i=t.placement.split("-")[0],o=Ct(i);var u=t.offsets.popper,f=t.offsets.reference,d=Math.floor,c="left"===i&&d(u.right)>d(f.left)||"right"===i&&d(u.left)d(f.top)||"bottom"===i&&d(u.top)d(n.right),m=d(u.top)d(n.bottom),_="left"===i&&h||"right"===i&&p||"top"===i&&m||"bottom"===i&&g,v=-1!==["top","bottom"].indexOf(i),b=!!e.flipVariations&&(v&&"start"===r&&h||v&&"end"===r&&p||!v&&"start"===r&&m||!v&&"end"===r&&g),y=!!e.flipVariationsByContent&&(v&&"start"===r&&p||v&&"end"===r&&h||!v&&"start"===r&&g||!v&&"end"===r&&m),E=b||y;(c||_||E)&&(t.flipped=!0,(c||_)&&(i=a[l+1]),E&&(r=function(t){return"end"===t?"start":"start"===t?"end":t}(r)),t.placement=i+(r?"-"+r:""),t.offsets.popper=ct({},t.offsets.popper,St(t.instance.popper,t.offsets.reference,t.placement)),t=Dt(t.instance.modifiers,t,"flip"))})),t},behavior:"flip",padding:5,boundariesElement:"viewport",flipVariations:!1,flipVariationsByContent:!1},inner:{order:700,enabled:!1,fn:function(t){var e=t.placement,n=e.split("-")[0],i=t.offsets,o=i.popper,r=i.reference,a=-1!==["left","right"].indexOf(n),s=-1===["top","left"].indexOf(n);return o[a?"left":"top"]=r[n]-(s?o[a?"width":"height"]:0),t.placement=Ct(e),t.offsets.popper=ht(o),t}},hide:{order:800,enabled:!0,fn:function(t){if(!qt(t.instance.modifiers,"hide","preventOverflow"))return t;var e=t.offsets.reference,n=Nt(t.instance.modifiers,(function(t){return"preventOverflow"===t.name})).boundaries;if(e.bottomn.right||e.top>n.bottom||e.right2&&void 0!==arguments[2]?arguments[2]:{};ut(this,t),this.scheduleUpdate=function(){return requestAnimationFrame(i.update)},this.update=Y(this.update.bind(this)),this.options=ct({},t.Defaults,o),this.state={isDestroyed:!1,isCreated:!1,scrollParents:[]},this.reference=e&&e.jquery?e[0]:e,this.popper=n&&n.jquery?n[0]:n,this.options.modifiers={},Object.keys(ct({},t.Defaults.modifiers,o.modifiers)).forEach((function(e){i.options.modifiers[e]=ct({},t.Defaults.modifiers[e]||{},o.modifiers?o.modifiers[e]:{})})),this.modifiers=Object.keys(this.options.modifiers).map((function(t){return ct({name:t},i.options.modifiers[t])})).sort((function(t,e){return t.order-e.order})),this.modifiers.forEach((function(t){t.enabled&&z(t.onLoad)&&t.onLoad(i.reference,i.popper,i.options,t,i.state)})),this.update();var r=this.options.eventsEnabled;r&&this.enableEventListeners(),this.state.eventsEnabled=r}return ft(t,[{key:"update",value:function(){return At.call(this)}},{key:"destroy",value:function(){return Ot.call(this)}},{key:"enableEventListeners",value:function(){return Pt.call(this)}},{key:"disableEventListeners",value:function(){return Ft.call(this)}}]),t}();Vt.Utils=("undefined"!=typeof window?window:global).PopperUtils,Vt.placements=Bt,Vt.Defaults=Ut;var Yt=Vt,zt="dropdown",Kt="bs.dropdown",Xt=i.default.fn[zt],Gt=new RegExp("38|40|27"),$t="disabled",Jt="show",Zt="dropdown-menu-right",te="hide.bs.dropdown",ee="hidden.bs.dropdown",ne="click.bs.dropdown.data-api",ie="keydown.bs.dropdown.data-api",oe='[data-toggle="dropdown"]',re=".dropdown-menu",ae={offset:0,flip:!0,boundary:"scrollParent",reference:"toggle",display:"dynamic",popperConfig:null},se={offset:"(number|string|function)",flip:"boolean",boundary:"(string|element)",reference:"(string|element)",display:"string",popperConfig:"(null|object)"},le=function(){function t(t,e){this._element=t,this._popper=null,this._config=this._getConfig(e),this._menu=this._getMenuElement(),this._inNavbar=this._detectNavbar(),this._addEventListeners()}var e=t.prototype;return e.toggle=function(){if(!this._element.disabled&&!i.default(this._element).hasClass($t)){var e=i.default(this._menu).hasClass(Jt);t._clearMenus(),e||this.show(!0)}},e.show=function(e){if(void 0===e&&(e=!1),!(this._element.disabled||i.default(this._element).hasClass($t)||i.default(this._menu).hasClass(Jt))){var n={relatedTarget:this._element},o=i.default.Event("show.bs.dropdown",n),r=t._getParentFromElement(this._element);if(i.default(r).trigger(o),!o.isDefaultPrevented()){if(!this._inNavbar&&e){if("undefined"==typeof Yt)throw new TypeError("Bootstrap's dropdowns require Popper (https://popper.js.org)");var a=this._element;"parent"===this._config.reference?a=r:u.isElement(this._config.reference)&&(a=this._config.reference,"undefined"!=typeof this._config.reference.jquery&&(a=this._config.reference[0])),"scrollParent"!==this._config.boundary&&i.default(r).addClass("position-static"),this._popper=new Yt(a,this._menu,this._getPopperConfig())}"ontouchstart"in document.documentElement&&0===i.default(r).closest(".navbar-nav").length&&i.default(document.body).children().on("mouseover",null,i.default.noop),this._element.focus(),this._element.setAttribute("aria-expanded",!0),i.default(this._menu).toggleClass(Jt),i.default(r).toggleClass(Jt).trigger(i.default.Event("shown.bs.dropdown",n))}}},e.hide=function(){if(!this._element.disabled&&!i.default(this._element).hasClass($t)&&i.default(this._menu).hasClass(Jt)){var e={relatedTarget:this._element},n=i.default.Event(te,e),o=t._getParentFromElement(this._element);i.default(o).trigger(n),n.isDefaultPrevented()||(this._popper&&this._popper.destroy(),i.default(this._menu).toggleClass(Jt),i.default(o).toggleClass(Jt).trigger(i.default.Event(ee,e)))}},e.dispose=function(){i.default.removeData(this._element,Kt),i.default(this._element).off(".bs.dropdown"),this._element=null,this._menu=null,null!==this._popper&&(this._popper.destroy(),this._popper=null)},e.update=function(){this._inNavbar=this._detectNavbar(),null!==this._popper&&this._popper.scheduleUpdate()},e._addEventListeners=function(){var t=this;i.default(this._element).on("click.bs.dropdown",(function(e){e.preventDefault(),e.stopPropagation(),t.toggle()}))},e._getConfig=function(t){return t=a({},this.constructor.Default,i.default(this._element).data(),t),u.typeCheckConfig(zt,t,this.constructor.DefaultType),t},e._getMenuElement=function(){if(!this._menu){var e=t._getParentFromElement(this._element);e&&(this._menu=e.querySelector(re))}return this._menu},e._getPlacement=function(){var t=i.default(this._element.parentNode),e="bottom-start";return t.hasClass("dropup")?e=i.default(this._menu).hasClass(Zt)?"top-end":"top-start":t.hasClass("dropright")?e="right-start":t.hasClass("dropleft")?e="left-start":i.default(this._menu).hasClass(Zt)&&(e="bottom-end"),e},e._detectNavbar=function(){return i.default(this._element).closest(".navbar").length>0},e._getOffset=function(){var t=this,e={};return"function"==typeof this._config.offset?e.fn=function(e){return e.offsets=a({},e.offsets,t._config.offset(e.offsets,t._element)),e}:e.offset=this._config.offset,e},e._getPopperConfig=function(){var t={placement:this._getPlacement(),modifiers:{offset:this._getOffset(),flip:{enabled:this._config.flip},preventOverflow:{boundariesElement:this._config.boundary}}};return"static"===this._config.display&&(t.modifiers.applyStyle={enabled:!1}),a({},t,this._config.popperConfig)},t._jQueryInterface=function(e){return this.each((function(){var n=i.default(this).data(Kt);if(n||(n=new t(this,"object"==typeof e?e:null),i.default(this).data(Kt,n)),"string"==typeof e){if("undefined"==typeof n[e])throw new TypeError('No method named "'+e+'"');n[e]()}}))},t._clearMenus=function(e){if(!e||3!==e.which&&("keyup"!==e.type||9===e.which))for(var n=[].slice.call(document.querySelectorAll(oe)),o=0,r=n.length;o0&&a--,40===e.which&&adocument.documentElement.clientHeight;n||(this._element.style.overflowY="hidden"),this._element.classList.add(pe);var o=u.getTransitionDurationFromElement(this._dialog);i.default(this._element).off(u.TRANSITION_END),i.default(this._element).one(u.TRANSITION_END,(function(){t._element.classList.remove(pe),n||i.default(t._element).one(u.TRANSITION_END,(function(){t._element.style.overflowY=""})).emulateTransitionEnd(t._element,o)})).emulateTransitionEnd(o),this._element.focus()}},e._showElement=function(t){var e=this,n=i.default(this._element).hasClass(ce),o=this._dialog?this._dialog.querySelector(".modal-body"):null;this._element.parentNode&&this._element.parentNode.nodeType===Node.ELEMENT_NODE||document.body.appendChild(this._element),this._element.style.display="block",this._element.removeAttribute("aria-hidden"),this._element.setAttribute("aria-modal",!0),this._element.setAttribute("role","dialog"),i.default(this._dialog).hasClass("modal-dialog-scrollable")&&o?o.scrollTop=0:this._element.scrollTop=0,n&&u.reflow(this._element),i.default(this._element).addClass(he),this._config.focus&&this._enforceFocus();var r=i.default.Event("shown.bs.modal",{relatedTarget:t}),a=function(){e._config.focus&&e._element.focus(),e._isTransitioning=!1,i.default(e._element).trigger(r)};if(n){var s=u.getTransitionDurationFromElement(this._dialog);i.default(this._dialog).one(u.TRANSITION_END,a).emulateTransitionEnd(s)}else a()},e._enforceFocus=function(){var t=this;i.default(document).off(_e).on(_e,(function(e){document!==e.target&&t._element!==e.target&&0===i.default(t._element).has(e.target).length&&t._element.focus()}))},e._setEscapeEvent=function(){var t=this;this._isShown?i.default(this._element).on(ye,(function(e){t._config.keyboard&&27===e.which?(e.preventDefault(),t.hide()):t._config.keyboard||27!==e.which||t._triggerBackdropTransition()})):this._isShown||i.default(this._element).off(ye)},e._setResizeEvent=function(){var t=this;this._isShown?i.default(window).on(ve,(function(e){return t.handleUpdate(e)})):i.default(window).off(ve)},e._hideModal=function(){var t=this;this._element.style.display="none",this._element.setAttribute("aria-hidden",!0),this._element.removeAttribute("aria-modal"),this._element.removeAttribute("role"),this._isTransitioning=!1,this._showBackdrop((function(){i.default(document.body).removeClass(de),t._resetAdjustments(),t._resetScrollbar(),i.default(t._element).trigger(me)}))},e._removeBackdrop=function(){this._backdrop&&(i.default(this._backdrop).remove(),this._backdrop=null)},e._showBackdrop=function(t){var e=this,n=i.default(this._element).hasClass(ce)?ce:"";if(this._isShown&&this._config.backdrop){if(this._backdrop=document.createElement("div"),this._backdrop.className="modal-backdrop",n&&this._backdrop.classList.add(n),i.default(this._backdrop).appendTo(document.body),i.default(this._element).on(be,(function(t){e._ignoreBackdropClick?e._ignoreBackdropClick=!1:t.target===t.currentTarget&&("static"===e._config.backdrop?e._triggerBackdropTransition():e.hide())})),n&&u.reflow(this._backdrop),i.default(this._backdrop).addClass(he),!t)return;if(!n)return void t();var o=u.getTransitionDurationFromElement(this._backdrop);i.default(this._backdrop).one(u.TRANSITION_END,t).emulateTransitionEnd(o)}else if(!this._isShown&&this._backdrop){i.default(this._backdrop).removeClass(he);var r=function(){e._removeBackdrop(),t&&t()};if(i.default(this._element).hasClass(ce)){var a=u.getTransitionDurationFromElement(this._backdrop);i.default(this._backdrop).one(u.TRANSITION_END,r).emulateTransitionEnd(a)}else r()}else t&&t()},e._adjustDialog=function(){var t=this._element.scrollHeight>document.documentElement.clientHeight;!this._isBodyOverflowing&&t&&(this._element.style.paddingLeft=this._scrollbarWidth+"px"),this._isBodyOverflowing&&!t&&(this._element.style.paddingRight=this._scrollbarWidth+"px")},e._resetAdjustments=function(){this._element.style.paddingLeft="",this._element.style.paddingRight=""},e._checkScrollbar=function(){var t=document.body.getBoundingClientRect();this._isBodyOverflowing=Math.round(t.left+t.right)',trigger:"hover focus",title:"",delay:0,html:!1,selector:!1,placement:"top",offset:0,container:!1,fallbackPlacement:"flip",boundary:"scrollParent",customClass:"",sanitize:!0,sanitizeFn:null,whiteList:{"*":["class","dir","id","lang","role",/^aria-[\w-]*$/i],a:["target","href","title","rel"],area:[],b:[],br:[],col:[],code:[],div:[],em:[],hr:[],h1:[],h2:[],h3:[],h4:[],h5:[],h6:[],i:[],img:["src","srcset","alt","title","width","height"],li:[],ol:[],p:[],pre:[],s:[],small:[],span:[],sub:[],sup:[],strong:[],u:[],ul:[]},popperConfig:null},We={animation:"boolean",template:"string",title:"(string|element|function)",trigger:"string",delay:"(number|object)",html:"boolean",selector:"(string|boolean)",placement:"(string|function)",offset:"(number|string|function)",container:"(string|element|boolean)",fallbackPlacement:"(string|array)",boundary:"(string|element)",customClass:"(string|function)",sanitize:"boolean",sanitizeFn:"(null|function)",whiteList:"object",popperConfig:"(null|object)"},Ue={HIDE:"hide.bs.tooltip",HIDDEN:"hidden.bs.tooltip",SHOW:"show.bs.tooltip",SHOWN:"shown.bs.tooltip",INSERTED:"inserted.bs.tooltip",CLICK:"click.bs.tooltip",FOCUSIN:"focusin.bs.tooltip",FOCUSOUT:"focusout.bs.tooltip",MOUSEENTER:"mouseenter.bs.tooltip",MOUSELEAVE:"mouseleave.bs.tooltip"},Ve=function(){function t(t,e){if("undefined"==typeof Yt)throw new TypeError("Bootstrap's tooltips require Popper (https://popper.js.org)");this._isEnabled=!0,this._timeout=0,this._hoverState="",this._activeTrigger={},this._popper=null,this.element=t,this.config=this._getConfig(e),this.tip=null,this._setListeners()}var e=t.prototype;return e.enable=function(){this._isEnabled=!0},e.disable=function(){this._isEnabled=!1},e.toggleEnabled=function(){this._isEnabled=!this._isEnabled},e.toggle=function(t){if(this._isEnabled)if(t){var e=this.constructor.DATA_KEY,n=i.default(t.currentTarget).data(e);n||(n=new this.constructor(t.currentTarget,this._getDelegateConfig()),i.default(t.currentTarget).data(e,n)),n._activeTrigger.click=!n._activeTrigger.click,n._isWithActiveTrigger()?n._enter(null,n):n._leave(null,n)}else{if(i.default(this.getTipElement()).hasClass(Fe))return void this._leave(null,this);this._enter(null,this)}},e.dispose=function(){clearTimeout(this._timeout),i.default.removeData(this.element,this.constructor.DATA_KEY),i.default(this.element).off(this.constructor.EVENT_KEY),i.default(this.element).closest(".modal").off("hide.bs.modal",this._hideModalHandler),this.tip&&i.default(this.tip).remove(),this._isEnabled=null,this._timeout=null,this._hoverState=null,this._activeTrigger=null,this._popper&&this._popper.destroy(),this._popper=null,this.element=null,this.config=null,this.tip=null},e.show=function(){var t=this;if("none"===i.default(this.element).css("display"))throw new Error("Please use show on visible elements");var e=i.default.Event(this.constructor.Event.SHOW);if(this.isWithContent()&&this._isEnabled){i.default(this.element).trigger(e);var n=u.findShadowRoot(this.element),o=i.default.contains(null!==n?n:this.element.ownerDocument.documentElement,this.element);if(e.isDefaultPrevented()||!o)return;var r=this.getTipElement(),a=u.getUID(this.constructor.NAME);r.setAttribute("id",a),this.element.setAttribute("aria-describedby",a),this.setContent(),this.config.animation&&i.default(r).addClass(Pe);var s="function"==typeof this.config.placement?this.config.placement.call(this,r,this.element):this.config.placement,l=this._getAttachment(s);this.addAttachmentClass(l);var f=this._getContainer();i.default(r).data(this.constructor.DATA_KEY,this),i.default.contains(this.element.ownerDocument.documentElement,this.tip)||i.default(r).appendTo(f),i.default(this.element).trigger(this.constructor.Event.INSERTED),this._popper=new Yt(this.element,r,this._getPopperConfig(l)),i.default(r).addClass(Fe),i.default(r).addClass(this.config.customClass),"ontouchstart"in document.documentElement&&i.default(document.body).children().on("mouseover",null,i.default.noop);var d=function(){t.config.animation&&t._fixTransition();var e=t._hoverState;t._hoverState=null,i.default(t.element).trigger(t.constructor.Event.SHOWN),e===He&&t._leave(null,t)};if(i.default(this.tip).hasClass(Pe)){var c=u.getTransitionDurationFromElement(this.tip);i.default(this.tip).one(u.TRANSITION_END,d).emulateTransitionEnd(c)}else d()}},e.hide=function(t){var e=this,n=this.getTipElement(),o=i.default.Event(this.constructor.Event.HIDE),r=function(){e._hoverState!==Re&&n.parentNode&&n.parentNode.removeChild(n),e._cleanTipClass(),e.element.removeAttribute("aria-describedby"),i.default(e.element).trigger(e.constructor.Event.HIDDEN),null!==e._popper&&e._popper.destroy(),t&&t()};if(i.default(this.element).trigger(o),!o.isDefaultPrevented()){if(i.default(n).removeClass(Fe),"ontouchstart"in document.documentElement&&i.default(document.body).children().off("mouseover",null,i.default.noop),this._activeTrigger.click=!1,this._activeTrigger.focus=!1,this._activeTrigger.hover=!1,i.default(this.tip).hasClass(Pe)){var a=u.getTransitionDurationFromElement(n);i.default(n).one(u.TRANSITION_END,r).emulateTransitionEnd(a)}else r();this._hoverState=""}},e.update=function(){null!==this._popper&&this._popper.scheduleUpdate()},e.isWithContent=function(){return Boolean(this.getTitle())},e.addAttachmentClass=function(t){i.default(this.getTipElement()).addClass("bs-tooltip-"+t)},e.getTipElement=function(){return this.tip=this.tip||i.default(this.config.template)[0],this.tip},e.setContent=function(){var t=this.getTipElement();this.setElementContent(i.default(t.querySelectorAll(".tooltip-inner")),this.getTitle()),i.default(t).removeClass("fade show")},e.setElementContent=function(t,e){"object"!=typeof e||!e.nodeType&&!e.jquery?this.config.html?(this.config.sanitize&&(e=ke(e,this.config.whiteList,this.config.sanitizeFn)),t.html(e)):t.text(e):this.config.html?i.default(e).parent().is(t)||t.empty().append(e):t.text(i.default(e).text())},e.getTitle=function(){var t=this.element.getAttribute("data-original-title");return t||(t="function"==typeof this.config.title?this.config.title.call(this.element):this.config.title),t},e._getPopperConfig=function(t){var e=this;return a({},{placement:t,modifiers:{offset:this._getOffset(),flip:{behavior:this.config.fallbackPlacement},arrow:{element:".arrow"},preventOverflow:{boundariesElement:this.config.boundary}},onCreate:function(t){t.originalPlacement!==t.placement&&e._handlePopperPlacementChange(t)},onUpdate:function(t){return e._handlePopperPlacementChange(t)}},this.config.popperConfig)},e._getOffset=function(){var t=this,e={};return"function"==typeof this.config.offset?e.fn=function(e){return e.offsets=a({},e.offsets,t.config.offset(e.offsets,t.element)),e}:e.offset=this.config.offset,e},e._getContainer=function(){return!1===this.config.container?document.body:u.isElement(this.config.container)?i.default(this.config.container):i.default(document).find(this.config.container)},e._getAttachment=function(t){return Be[t.toUpperCase()]},e._setListeners=function(){var t=this;this.config.trigger.split(" ").forEach((function(e){if("click"===e)i.default(t.element).on(t.constructor.Event.CLICK,t.config.selector,(function(e){return t.toggle(e)}));else if("manual"!==e){var n=e===Me?t.constructor.Event.MOUSEENTER:t.constructor.Event.FOCUSIN,o=e===Me?t.constructor.Event.MOUSELEAVE:t.constructor.Event.FOCUSOUT;i.default(t.element).on(n,t.config.selector,(function(e){return t._enter(e)})).on(o,t.config.selector,(function(e){return t._leave(e)}))}})),this._hideModalHandler=function(){t.element&&t.hide()},i.default(this.element).closest(".modal").on("hide.bs.modal",this._hideModalHandler),this.config.selector?this.config=a({},this.config,{trigger:"manual",selector:""}):this._fixTitle()},e._fixTitle=function(){var t=typeof this.element.getAttribute("data-original-title");(this.element.getAttribute("title")||"string"!==t)&&(this.element.setAttribute("data-original-title",this.element.getAttribute("title")||""),this.element.setAttribute("title",""))},e._enter=function(t,e){var n=this.constructor.DATA_KEY;(e=e||i.default(t.currentTarget).data(n))||(e=new this.constructor(t.currentTarget,this._getDelegateConfig()),i.default(t.currentTarget).data(n,e)),t&&(e._activeTrigger["focusin"===t.type?qe:Me]=!0),i.default(e.getTipElement()).hasClass(Fe)||e._hoverState===Re?e._hoverState=Re:(clearTimeout(e._timeout),e._hoverState=Re,e.config.delay&&e.config.delay.show?e._timeout=setTimeout((function(){e._hoverState===Re&&e.show()}),e.config.delay.show):e.show())},e._leave=function(t,e){var n=this.constructor.DATA_KEY;(e=e||i.default(t.currentTarget).data(n))||(e=new this.constructor(t.currentTarget,this._getDelegateConfig()),i.default(t.currentTarget).data(n,e)),t&&(e._activeTrigger["focusout"===t.type?qe:Me]=!1),e._isWithActiveTrigger()||(clearTimeout(e._timeout),e._hoverState=He,e.config.delay&&e.config.delay.hide?e._timeout=setTimeout((function(){e._hoverState===He&&e.hide()}),e.config.delay.hide):e.hide())},e._isWithActiveTrigger=function(){for(var t in this._activeTrigger)if(this._activeTrigger[t])return!0;return!1},e._getConfig=function(t){var e=i.default(this.element).data();return Object.keys(e).forEach((function(t){-1!==Le.indexOf(t)&&delete e[t]})),"number"==typeof(t=a({},this.constructor.Default,e,"object"==typeof t&&t?t:{})).delay&&(t.delay={show:t.delay,hide:t.delay}),"number"==typeof t.title&&(t.title=t.title.toString()),"number"==typeof t.content&&(t.content=t.content.toString()),u.typeCheckConfig(Ie,t,this.constructor.DefaultType),t.sanitize&&(t.template=ke(t.template,t.whiteList,t.sanitizeFn)),t},e._getDelegateConfig=function(){var t={};if(this.config)for(var e in this.config)this.constructor.Default[e]!==this.config[e]&&(t[e]=this.config[e]);return t},e._cleanTipClass=function(){var t=i.default(this.getTipElement()),e=t.attr("class").match(je);null!==e&&e.length&&t.removeClass(e.join(""))},e._handlePopperPlacementChange=function(t){this.tip=t.instance.popper,this._cleanTipClass(),this.addAttachmentClass(this._getAttachment(t.placement))},e._fixTransition=function(){var t=this.getTipElement(),e=this.config.animation;null===t.getAttribute("x-placement")&&(i.default(t).removeClass(Pe),this.config.animation=!1,this.hide(),this.show(),this.config.animation=e)},t._jQueryInterface=function(e){return this.each((function(){var n=i.default(this),o=n.data(Oe),r="object"==typeof e&&e;if((o||!/dispose|hide/.test(e))&&(o||(o=new t(this,r),n.data(Oe,o)),"string"==typeof e)){if("undefined"==typeof o[e])throw new TypeError('No method named "'+e+'"');o[e]()}}))},r(t,null,[{key:"VERSION",get:function(){return"4.6.1"}},{key:"Default",get:function(){return Qe}},{key:"NAME",get:function(){return Ie}},{key:"DATA_KEY",get:function(){return Oe}},{key:"Event",get:function(){return Ue}},{key:"EVENT_KEY",get:function(){return".bs.tooltip"}},{key:"DefaultType",get:function(){return We}}]),t}();i.default.fn.tooltip=Ve._jQueryInterface,i.default.fn.tooltip.Constructor=Ve,i.default.fn.tooltip.noConflict=function(){return i.default.fn.tooltip=xe,Ve._jQueryInterface};var Ye="bs.popover",ze=i.default.fn.popover,Ke=new RegExp("(^|\\s)bs-popover\\S+","g"),Xe=a({},Ve.Default,{placement:"right",trigger:"click",content:"",template:'
]({{ site.baseurl }}/)
diff --git a/CNAME b/CNAME
index 8b137891791fe..4b6e08d90863f 100644
--- a/CNAME
+++ b/CNAME
@@ -1 +1 @@
-
+www.dowen.me.uk
diff --git a/Gemfile b/Gemfile
new file mode 100644
index 0000000000000..ba2fe4aede03f
--- /dev/null
+++ b/Gemfile
@@ -0,0 +1,28 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gem "jekyll-theme-chirpy", "~> 6.0", ">= 6.0.1"
+
+group :test do
+ gem "html-proofer", "~> 5.0.7"
+end
+
+# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
+# and associated library.
+platforms :mingw, :x64_mingw, :mswin, :jruby do
+ gem "tzinfo", ">= 1", "< 3"
+ gem "tzinfo-data"
+end
+
+# Performance-booster for watching directories on Windows
+gem 'wdm', '~> 0.1.1', :install_if => Gem.win_platform?
+
+# Jekyll <= 4.2.0 compatibility with Ruby 3.0
+gem 'nokogiri', '~> 1.15', '>= 1.15.2'
+
+gem "webrick", "~> 1.7"
+
+gem 'jekyll-redirect-from'
+
+gem 'jekyll-compose', group: [:jekyll_plugins]
diff --git a/Gemfile.lock b/Gemfile.lock
new file mode 100644
index 0000000000000..d5c16db47547a
--- /dev/null
+++ b/Gemfile.lock
@@ -0,0 +1,164 @@
+GEM
+ remote: https://rubygems.org/
+ specs:
+ Ascii85 (1.1.1)
+ addressable (2.8.6)
+ public_suffix (>= 2.0.2, < 6.0)
+ afm (0.2.2)
+ async (2.12.0)
+ console (~> 1.25, >= 1.25.2)
+ fiber-annotation
+ io-event (~> 1.6)
+ bigdecimal (3.1.8)
+ colorator (1.1.0)
+ concurrent-ruby (1.3.3)
+ console (1.25.2)
+ fiber-annotation
+ fiber-local (~> 1.1)
+ json
+ em-websocket (0.5.3)
+ eventmachine (>= 0.12.9)
+ http_parser.rb (~> 0)
+ ethon (0.16.0)
+ ffi (>= 1.15.0)
+ eventmachine (1.2.7)
+ ffi (1.17.0-x64-mingw-ucrt)
+ ffi (1.17.0-x86_64-linux-gnu)
+ fiber-annotation (0.2.0)
+ fiber-local (1.1.0)
+ fiber-storage
+ fiber-storage (0.1.2)
+ forwardable-extended (2.6.0)
+ google-protobuf (4.27.1-x64-mingw-ucrt)
+ bigdecimal
+ rake (>= 13)
+ google-protobuf (4.27.1-x86_64-linux)
+ bigdecimal
+ rake (>= 13)
+ hashery (2.1.2)
+ html-proofer (5.0.9)
+ addressable (~> 2.3)
+ async (~> 2.1)
+ nokogiri (~> 1.13)
+ pdf-reader (~> 2.11)
+ rainbow (~> 3.0)
+ typhoeus (~> 1.3)
+ yell (~> 2.0)
+ zeitwerk (~> 2.5)
+ http_parser.rb (0.8.0)
+ i18n (1.14.5)
+ concurrent-ruby (~> 1.0)
+ io-event (1.6.4)
+ jekyll (4.3.3)
+ addressable (~> 2.4)
+ colorator (~> 1.0)
+ em-websocket (~> 0.5)
+ i18n (~> 1.0)
+ jekyll-sass-converter (>= 2.0, < 4.0)
+ jekyll-watch (~> 2.0)
+ kramdown (~> 2.3, >= 2.3.1)
+ kramdown-parser-gfm (~> 1.0)
+ liquid (~> 4.0)
+ mercenary (>= 0.3.6, < 0.5)
+ pathutil (~> 0.9)
+ rouge (>= 3.0, < 5.0)
+ safe_yaml (~> 1.0)
+ terminal-table (>= 1.8, < 4.0)
+ webrick (~> 1.7)
+ jekyll-archives (2.2.1)
+ jekyll (>= 3.6, < 5.0)
+ jekyll-compose (0.12.0)
+ jekyll (>= 3.7, < 5.0)
+ jekyll-include-cache (0.2.1)
+ jekyll (>= 3.7, < 5.0)
+ jekyll-paginate (1.1.0)
+ jekyll-redirect-from (0.16.0)
+ jekyll (>= 3.3, < 5.0)
+ jekyll-sass-converter (3.0.0)
+ sass-embedded (~> 1.54)
+ jekyll-seo-tag (2.8.0)
+ jekyll (>= 3.8, < 5.0)
+ jekyll-sitemap (1.4.0)
+ jekyll (>= 3.7, < 5.0)
+ jekyll-theme-chirpy (6.5.5)
+ jekyll (~> 4.3)
+ jekyll-archives (~> 2.2)
+ jekyll-include-cache (~> 0.2)
+ jekyll-paginate (~> 1.1)
+ jekyll-redirect-from (~> 0.16)
+ jekyll-seo-tag (~> 2.8)
+ jekyll-sitemap (~> 1.4)
+ jekyll-watch (2.2.1)
+ listen (~> 3.0)
+ json (2.7.2)
+ kramdown (2.4.0)
+ rexml
+ kramdown-parser-gfm (1.1.0)
+ kramdown (~> 2.0)
+ liquid (4.0.4)
+ listen (3.9.0)
+ rb-fsevent (~> 0.10, >= 0.10.3)
+ rb-inotify (~> 0.9, >= 0.9.10)
+ mercenary (0.4.0)
+ nokogiri (1.16.6-x64-mingw-ucrt)
+ racc (~> 1.4)
+ nokogiri (1.16.6-x86_64-linux)
+ racc (~> 1.4)
+ pathutil (0.16.2)
+ forwardable-extended (~> 2.6)
+ pdf-reader (2.12.0)
+ Ascii85 (~> 1.0)
+ afm (~> 0.2.1)
+ hashery (~> 2.0)
+ ruby-rc4
+ ttfunk
+ public_suffix (5.1.1)
+ racc (1.8.0)
+ rainbow (3.1.1)
+ rake (13.2.1)
+ rb-fsevent (0.11.2)
+ rb-inotify (0.11.1)
+ ffi (~> 1.0)
+ rexml (3.3.0)
+ strscan
+ rouge (4.3.0)
+ ruby-rc4 (0.1.5)
+ safe_yaml (1.0.5)
+ sass-embedded (1.77.5-x64-mingw-ucrt)
+ google-protobuf (>= 3.25, < 5.0)
+ sass-embedded (1.77.5-x86_64-linux-gnu)
+ google-protobuf (>= 3.25, < 5.0)
+ strscan (3.1.0)
+ terminal-table (3.0.2)
+ unicode-display_width (>= 1.1.1, < 3)
+ ttfunk (1.8.0)
+ bigdecimal (~> 3.1)
+ typhoeus (1.4.1)
+ ethon (>= 0.9.0)
+ tzinfo (2.0.6)
+ concurrent-ruby (~> 1.0)
+ tzinfo-data (1.2024.1)
+ tzinfo (>= 1.0.0)
+ unicode-display_width (2.5.0)
+ wdm (0.1.1)
+ webrick (1.8.1)
+ yell (2.2.2)
+ zeitwerk (2.6.16)
+
+PLATFORMS
+ x64-mingw-ucrt
+ x86_64-linux
+
+DEPENDENCIES
+ html-proofer (~> 5.0.7)
+ jekyll-compose
+ jekyll-redirect-from
+ jekyll-theme-chirpy (~> 6.0, >= 6.0.1)
+ nokogiri (~> 1.15, >= 1.15.2)
+ tzinfo (>= 1, < 3)
+ tzinfo-data
+ wdm (~> 0.1.1)
+ webrick (~> 1.7)
+
+BUNDLED WITH
+ 2.4.13
diff --git a/LICENSE b/LICENSE
index 40e6030143cb3..a6f6c9fed8620 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,20 +1,21 @@
-The MIT License (MIT)
+MIT License
-Copyright (c) 2015 Barry Clark
+Copyright (c) 2021 Cotes Chung
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
\ No newline at end of file
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
index 45c202063a374..c1b0375c34f23 100644
--- a/README.md
+++ b/README.md
@@ -1,120 +1,46 @@
-> March, 2016: If you're on an old version of Jekyll Now and run into a) build warnings or b) syntax highlighting issues caused by [Jekyll 3 and GitHub Pages updates](https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0), just :sparkles:[update your _config.yml](https://github.com/barryclark/jekyll-now/pull/445/files):sparkles: and you'll be set!
+# Chirpy Starter [](https://rubygems.org/gems/jekyll-theme-chirpy) [][mit]
-# Jekyll Now
+When installing the [**Chirpy**][chirpy] theme through [RubyGems.org][gem], Jekyll can only read files in the folders `_includes`, `_layout`, `_sass` and `assets`, as well as a small part of options of the `_config.yml` file from the theme's gem. If you have ever installed this theme gem, you can use the command `bundle info --path jekyll-theme-chirpy` to locate these files.
-**Jekyll** is a static site generator that's perfect for GitHub hosted blogs ([Jekyll Repository](https://github.com/jekyll/jekyll))
+The Jekyll organization claims that this is to leave the ball in the user’s court, but this also results in users not being able to enjoy the out-of-the-box experience when using feature-rich themes.
-**Jekyll Now** makes it easier to create your Jekyll blog, by eliminating a lot of the up front setup.
+To fully use all the features of **Chirpy**, you need to copy the other critical files from the theme's gem to your Jekyll site. The following is a list of targets:
-- You don't need to touch the command line
-- You don't need to install/configure ruby, rvm/rbenv, ruby gems :relaxed:
-- You don't need to install runtime dependencies like markdown processors, Pygments, etc
-- If you're on Windows, this will make setting up Jekyll a lot easier
-- It's easy to try out, you can just delete your forked repository if you don't like it
+```shell
+.
+├── _config.yml
+├── _data
+├── _plugins
+├── _tabs
+└── index.html
+```
-In a few minutes you'll be set up with a minimal, responsive blog like the one below giving you more time to spend on writing epic blog posts!
+In order to save your time, and to prevent you from missing some files when copying, we extract those files/configurations of the latest version of the **Chirpy** theme and the [CD][CD] workflow to here, so that you can start writing in minutes.
-
+## Prerequisites
-## Quick Start
+Follow the instructions in the [Jekyll Docs](https://jekyllrb.com/docs/installation/) to complete the installation of `Ruby`, `RubyGems`, `Jekyll` and `Bundler`.
-### Step 1) Fork Jekyll Now to your User Repository
+## Installation
-Fork this repo, then rename the repository to yourgithubusername.github.io.
+[**Use this template**][use-template] to generate a brand new repository and name it `
-
-