Refactor the site to use Docusaurus

PROBLEM:

The existing site is using out of date versions of Docsy and Hugo. We
need to either upgrade those components, or use the time to switch to
a different static site generator.

SOLUTION:

Use Docusaurus. Jeff has had a good experience using it with Holos, so
let's use the opportunity to switch the site to Docusaurus.

This commit refactors the existing site content to use Docusaurus with
the following details:

* Removed the Logo blog as it really doesn't serve us well.
* Used undraw.co SVG graphics on the landing page.
* Removed "Google Partners" because evidently we aren't anymore.
* Setup redirects to the existing site URLs so Google won't complain.

OUTCOME:

Our existing site content, but on a different static site generation
platform, and one that is easy for us to update.

Author: glarizza

Diff for: .gitignore

@@ -1,6 +1,20 @@
-/public
-resources/
-node_modules/
-package-lock.json
-.hugo_build.lock
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
 .DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

Diff for: README.md

@@ -1,138 +1,41 @@
-# Docsy Example
+# Website
 
-[Docsy][] is a [Hugo theme module][] for technical documentation sites, providing easy
-site navigation, structure, and more. This **Docsy Example Project** uses the Docsy
-theme component as a hugo module and provides a skeleton documentation structure for you to use.
-You can clone/copy this project and edit it with your own content, or use it as an example.
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
 
-In this project, the Docsy theme component is pulled in as a Hugo module, together with other module dependencies:
+### Installation
 
-```bash
-$ hugo mod graph
-hugo: collected modules in 566 ms
-hugo: collected modules in 578 ms
-github.com/google/docsy-example github.com/google/[email protected]
-github.com/google/docsy-example github.com/google/docsy/[email protected]
-github.com/google/docsy/[email protected] github.com/twbs/[email protected]+incompatible
-github.com/google/docsy/[email protected] github.com/FortAwesome/[email protected]
 ```
-
-You can find detailed theme instructions in the [Docsy user guide][].
-
-This Docsy Example Project is hosted on [Netlify][] at [example.docsy.dev][].
-You can view deploy logs from the [deploy section of the project's Netlify
-dashboard][deploys], or this [alternate dashboard][].
-
-This is not an officially supported Google product. This project is currently maintained.
-
-## Using the Docsy Example Project as a template
-
-A simple way to get started is to use this project as a template, which gives you a site project that is set up and ready to use. To do this: 
-
-1. Click **Use this template**.
-
-2. Select a name for your new project and click **Create repository from template**.
-
-3. Make your own local working copy of your new repo using git clone, replacing https://github.com/me/example.git with your repo’s web URL:
-
-```bash
-git clone --depth 1 https://github.com/me/example.git
+$ yarn
 ```
 
-You can now edit your own versions of the site’s source files.
-
-If you want to do SCSS edits and want to publish these, you need to install `PostCSS`
+### Local Development
 
-```bash
-npm install
+```
+$ yarn start
 ```
 
-## Running the website locally
-
-Building and running the site locally requires a recent `extended` version of [Hugo](https://gohugo.io).
-You can find out more about how to install Hugo for your environment in our
-[Getting started](https://www.docsy.dev/docs/getting-started/#prerequisites-and-installation) guide.
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
 
-Once you've made your working copy of the site repo, from the repo root folder, run:
+### Build
 
 ```
-hugo server
+$ yarn build
 ```
 
-## Running a container locally
-
-You can run docsy-example inside a [Docker](https://docs.docker.com/)
-container, the container runs with a volume bound to the `docsy-example`
-folder. This approach doesn't require you to install any dependencies other
-than [Docker Desktop](https://www.docker.com/products/docker-desktop) on
-Windows and Mac, and [Docker Compose](https://docs.docker.com/compose/install/)
-on Linux.
-
-1. Build the docker image 
-
-   ```bash
-   docker-compose build
-   ```
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
 
-1. Run the built image
+### Deployment
 
-   ```bash
-   docker-compose up
-   ```
+Using SSH:
 
-   > NOTE: You can run both commands at once with `docker-compose up --build`.
-
-1. Verify that the service is working. 
-
-   Open your web browser and type `http://localhost:1313` in your navigation bar,
-   This opens a local instance of the docsy-example homepage. You can now make
-   changes to the docsy example and those changes will immediately show up in your
-   browser after you save.
-
-### Cleanup
-
-To stop Docker Compose, on your terminal window, press **Ctrl + C**. 
-
-To remove the produced images run:
-
-```console
-docker-compose rm
 ```
-For more information see the [Docker Compose
-documentation](https://docs.docker.com/compose/gettingstarted/).
-
-## Troubleshooting
-
-As you run the website locally, you may run into the following error:
-
-```
-➜ hugo server
-
-INFO 2021/01/21 21:07:55 Using config file: 
-Building sites … INFO 2021/01/21 21:07:55 syncing static files to /
-Built in 288 ms
-Error: Error building site: TOCSS: failed to transform "scss/main.scss" (text/x-scss): resource "scss/scss/main.scss_9fadf33d895a46083cdd64396b57ef68" not found in file cache
+$ USE_SSH=true yarn deploy
 ```
 
-This error occurs if you have not installed the extended version of Hugo.
-See this [section](https://www.docsy.dev/docs/get-started/docsy-as-module/installation-prerequisites/#install-hugo) of the user guide for instructions on how to install Hugo.
-
-Or you may encounter the following error:
+Not using SSH:
 
 ```
-➜ hugo server
-
-Error: failed to download modules: binary with name "go" not found
+$ GIT_USER=<Your GitHub username> yarn deploy
 ```
 
-This error occurs if you have not installed the `go` programming language on your system.
-See this [section](https://www.docsy.dev/docs/get-started/docsy-as-module/installation-prerequisites/#install-go-language) of the user guide for instructions on how to install `go`.
-
-
-[alternate dashboard]: https://app.netlify.com/sites/goldydocs/deploys
-[deploys]: https://app.netlify.com/sites/docsy-example/deploys
-[Docsy user guide]: https://docsy.dev/docs
-[Docsy]: https://github.com/google/docsy
-[example.docsy.dev]: https://example.docsy.dev
-[Hugo theme module]: https://gohugo.io/hugo-modules/use-modules/#use-a-module-for-a-theme
-[Netlify]: https://netlify.com
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

Diff for: babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};

Diff for: blog/announcing-ois.md

@@ -0,0 +1,30 @@
+---
+date: 2015-09-20 18:33:10
+title:  "Announcing Open Infrastructure Services, LLC"
+authors: ["jmccune"]
+---
+
+Hello, World!
+
+I'm a little sad to say I've left [Puppet Labs][puppetlabs] after over 5 years
+working for the company and working on [Puppet][puppet].  It was a difficult
+decision, but I'm pleased to announce that I've decided to start my own
+independent consulting business, [Open Infrastructure Services, LLC][website].
+I'll be helping clients with their Puppet related problem while also focusing
+on bringing creative solutions to bear on complex infrastructures.  Please
+[email me][email] for more information, I'd love to hear how I could help you
+and your business.
+
+```puppet
+company { "Open Infrastructure Services, LLC":
+  ensure  => running,
+  founder => "Jeff McCune",
+  website => "http://openinfrastructure.co",
+  email   => "[email protected]",
+}
+```
+
+[puppetlabs]: http://puppetlabs.com
+[email]: mailto://[email protected]
+[website]: http://openinfrastructure.co
+[puppet]: http://github.com/puppetlabs/puppet

Diff for: blog/authors.yml

@@ -0,0 +1,29 @@
+endi:
+  name: Endilie Yacop Sucipto
+  title: Maintainer of Docusaurus
+  url: https://github.com/endiliey
+  image_url: https://github.com/endiliey.png
+
+yangshun:
+  name: Yangshun Tay
+  title: Front End Engineer @ Facebook
+  url: https://github.com/yangshun
+  image_url: https://github.com/yangshun.png
+
+slorber:
+  name: Sébastien Lorber
+  title: Docusaurus maintainer
+  url: https://sebastienlorber.com
+  image_url: https://github.com/slorber.png
+
+jmccune:
+  name: Jeff McCune
+  title: CEO of Open Infrastructure Services
+  url: https://github.com/jeffmccune
+  image_url: https://github.com/jeffmccune.png
+  
+glarizza:
+  name: Gary Larizza
+  title: Principal Consultant
+  url: https://github.com/glarizza
+  image_url: https://github.com/glarizza.png

Diff for: blog/introducing-gary/index.md

@@ -0,0 +1,61 @@
+---
+title:  "Welcome Gary Larizza"
+slug: welcome-gary
+date:   2017-10-21 12:06:00
+description: "Gary Larizza joins Open Infrastructure Services"
+authors: ["jmccune"]
+---
+
+<!--
+Since Docusaurus uses MDX, below is an example of how you would
+resize an existing image by importing it and doing inline styling.
+
+NOTE: You *NEED* the newline space between the import statement
+and the tag that uses it or else npm will raise an error.
+-->
+
+import Gary from '/img/gary.png';
+
+<img src={Gary} style={{width: 200}} align="left" hspace="20" vspace="20"/>
+
+Open Infrastructure Services is growing!  I'm excited to announce [Gary
+Larizza][gary], has joined Open Infrastructure Services as a Principal
+Consultant.  Gary and I first started working together on Puppet back in 2010 in
+Portland, Oregon.  From that first day working together I was struck by Gary's
+attitude and desire to dive deep in the guts of Puppet to figure out what's
+_really_ going on.  Fast forward to 2017, and I've found myself visiting [Shit
+Gary Says][garyblog] on a daily basis while working on Puppet types and
+providers.  Gary's ability to assimilate complex information, distill that
+information into the essential bits customers value, and communicate that
+essential information with humor and empathy has been invaluable to me
+personally.  A great example of this depth, humor, and empathy is, [Seriously,
+what is this provider doing?][garyprovider]
+
+Gary and I both started out working in education in Ohio, though separately from
+one another.  We were bought together in Portland, OR by two australians from
+the other side of the world, Nigel Kersten and James Turnbull.
+
+Gary and I share that special bond that only comes from successfully dealing
+with a classroom full of computers delivered a couple of weeks before school
+starts with the latest and greatest Mac OS X major release, chock full of
+changes and new surprises.
+
+Please check out Gary's post, [Some Other Beginning's End][garypost] on this new
+beginning for both of us.
+
+[Contact][contact] us with your automation and cloud infrastructure goals.  We'd
+both love to help you handle changes faster and more confidently through
+automated cloud infrastructure.
+
+Gary is also a [Puppet][puppet] certified consultant and a member of the Puppet
+Services Delivery Partner Program.  We're here to help achieve your goals
+whether you're expanding your Puppet investment, upgrading to the latest version
+and language features, or just getting started.
+
+[puppet]: https://puppet.com/product
+[gary]: http://garylarizza.com/
+[garyblog]: http://garylarizza.com/blog/
+[garypost]: http://garylarizza.com/blog/2017/08/25/some-other-beginnings-end/
+[garyprovider]: http://garylarizza.com/blog/2013/12/15/seriously-what-is-this-provider-doing/
+[avatar]: /img/gary-460.png
+[contact]: /#contact

Diff for: blog/introducing-nate/index.md

@@ -0,0 +1,24 @@
+---
+title:  "Welcome Nate McCurdy"
+slug: welcome-nate
+date:   2018-12-03 12:00:00
+description: "Nate McCurdy joins Open Infrastructure Services"
+authors: ["jmccune"]
+---
+
+import Nate from '/img/nate.jpg';
+
+<img src={Nate} style={{width: 200}} align="left" hspace="20" vspace="20"/>
+
+
+Open Infrastructure Services is growing!  I'm excited to announce [Nate
+McCurdy][nate], has joined Open Infrastructure Services as a Cloud
+Infrastructure Consultant.  Nate brings over a decade of experience helping
+companies with their digital transformation, configuration management, and
+breaking down walls between development and operations teams.
+
+Nate is also a [Google][google] certified Cloud Architect and helping streamline
+large enterprise hybrid clouds to date.
+
+[nate]: https://github.com/natemccurdy
+[google]: https://cloud.google.com/certification/cloud-architect