Skip to content

Commit 6d48d71

Browse files
glarizzaglarizza
committed
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.
1 parent 5ca00c2 commit 6d48d71

File tree

91 files changed

+17938
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

91 files changed

+17938
-0
lines changed

‎.gitignore

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Dependencies
2+
/node_modules
3+
4+
# Production
5+
/build
6+
7+
# Generated files
8+
.docusaurus
9+
.cache-loader
10+
11+
# Misc
12+
.DS_Store
13+
.env.local
14+
.env.development.local
15+
.env.test.local
16+
.env.production.local
17+
18+
npm-debug.log*
19+
yarn-debug.log*
20+
yarn-error.log*

‎README.md

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
# Website
2+
3+
This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
4+
5+
### Installation
6+
7+
```
8+
$ yarn
9+
```
10+
11+
### Local Development
12+
13+
```
14+
$ yarn start
15+
```
16+
17+
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
18+
19+
### Build
20+
21+
```
22+
$ yarn build
23+
```
24+
25+
This command generates static content into the `build` directory and can be served using any static contents hosting service.
26+
27+
### Deployment
28+
29+
Using SSH:
30+
31+
```
32+
$ USE_SSH=true yarn deploy
33+
```
34+
35+
Not using SSH:
36+
37+
```
38+
$ GIT_USER=<Your GitHub username> yarn deploy
39+
```
40+
41+
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.

‎babel.config.js

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

‎blog/announcing-ois.md

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

‎blog/authors.yml

+29
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
endi:
2+
name: Endilie Yacop Sucipto
3+
title: Maintainer of Docusaurus
4+
url: https://github.com/endiliey
5+
image_url: https://github.com/endiliey.png
6+
7+
yangshun:
8+
name: Yangshun Tay
9+
title: Front End Engineer @ Facebook
10+
url: https://github.com/yangshun
11+
image_url: https://github.com/yangshun.png
12+
13+
slorber:
14+
name: Sébastien Lorber
15+
title: Docusaurus maintainer
16+
url: https://sebastienlorber.com
17+
image_url: https://github.com/slorber.png
18+
19+
jmccune:
20+
name: Jeff McCune
21+
title: CEO of Open Infrastructure Services
22+
url: https://github.com/jeffmccune
23+
image_url: https://github.com/jeffmccune.png
24+
25+
glarizza:
26+
name: Gary Larizza
27+
title: Principal Consultant
28+
url: https://github.com/glarizza
29+
image_url: https://github.com/glarizza.png

‎blog/introducing-gary/index.md

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

‎blog/introducing-nate/index.md

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

‎blog/liftoff/index.md

+75
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
date: 2015-10-06 13:39:00
3+
title: "Lift Off!"
4+
slug: lift-off
5+
authors: ["jmccune"]
6+
---
7+
8+
3.. 2.. 1.. Lift Off!
9+
---
10+
11+
<a href="https://www.flickr.com/photos/spacexphotos/16698990175/in/photostream/" target="_blank">
12+
13+
import Liftoff from './liftoff.jpg';
14+
import Jeff from '/img/jeff.jpeg';
15+
import ProPuppet from './propuppet.jpg';
16+
17+
<img src={Liftoff} style={{width: 800}}></img>
18+
</a>
19+
20+
I'm pleased to announce Open Infrastructure Services, LLC is open for business!
21+
Here's some information about myself and the services I have available. Please
22+
[email][email-me] me with any questions about how I can help.
23+
24+
<img src={Jeff} align="left" hspace="8" style={{width: 200}}></img>
25+
26+
Open Infrastructure Services is founded by me, [Jeff McCune][jeff], a veteran
27+
systems administrator and software developer with over 15 years of experience.
28+
Before starting my consulting business I was at [Puppet Labs][puppetlabs] as a software
29+
developer working on [Puppet][puppet], [Facter][facter], [Puppet
30+
Server][puppet-server], and other internal tools like
31+
[crossfader](https://github.com/puppetlabs/crossfader). Prior to that, I was a
32+
professional services engineer at Puppet Labs, traveling the world working with
33+
customers and the open source community on matters of system architecture,
34+
availability, security, and continuous delivery workflows.
35+
36+
<a href="http://www.amazon.com/Pro-Puppet-James-Turnbull/dp/1430230592" target="_blank">
37+
<img src={ProPuppet} align="right" hspace="8" style={{width: 200}}></img>
38+
</a>
39+
40+
While traveling for Puppet Labs, I also co-authored [Pro Puppet][pro-puppet], the
41+
best-selling book about how to quickly get started and then scale Puppet toward
42+
full automation.
43+
44+
45+
Before Puppet Labs I worked at [Netsmart Technologies][ntst] where I was
46+
responsible for our hosted SaaS datacenters. Puppet and DevOps practices
47+
played a key part of my success at Netsmart. We were able to implement SAS-70
48+
II compliance in a matter of months using a well defined change management
49+
process, and detailed automated reports integrated with Puppet and [Splunk][splunk].
50+
51+
Prior to Netsmart Technologies, I worked at the Mathematics Department at Ohio
52+
State University. There, I learned about automation, [cfengine][cfengine],
53+
started using [Puppet][puppet], and fully automated our Mac OS X workstations
54+
and labs. In order to achieve full automation for PowerPC and Intel based
55+
systems, I reverse engineered Apple's boot service discovery protocol and
56+
patched ISC DHCP to behave as an automated network boot server for Mac OS X. I
57+
presented on Puppet at Apple's Worldwide Developer Conference.
58+
59+
Please [contact me][contact] if you have a need for professional, intelligent
60+
and creative solutions to the infrastructure problems that are holding you back
61+
from delivering your applications.
62+
63+
[jeff]: https://about.me/jeffmccune
64+
[avatar]: /img/jeff-200.jpg
65+
[puppet]: http://github.com/puppetlabs/puppet
66+
[facter]: http://github.com/puppetlabs/facter
67+
[puppet-server]: http://github.com/puppetlabs/puppet-server
68+
[pro-puppet-img]: /img/pro-puppet.jpg
69+
[puppetlabs]: https://puppetlabs.com
70+
[pro-puppet]: http://www.amazon.com/Pro-Puppet-James-Turnbull/dp/1430230592
71+
[ntst]: http://www.ntst.com
72+
[splunk]: http://www.splunk.com
73+
[contact]: /contact/
74+
[cfengine]: http://cfengine.com/
75+
[email-me]: mailto://[email protected]

‎blog/liftoff/liftoff.jpg

334 KB
Loading

‎blog/liftoff/propuppet.jpg

41.3 KB
Loading

‎blog/privacy.md

+79
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
date: 2023-05-23 12:00:00
3+
title: "Privacy Policy"
4+
authors: ["jmccune"]
5+
---
6+
7+
_Last Updated: January, 2024_
8+
9+
**Privacy Policy of Open Infrastructure Services LLC**
10+
11+
## Overview
12+
13+
We at Open Infrastructure Services LLC respect your privacy and are committed to protecting your personal data. This privacy policy will inform you about how we look after your personal data when you visit our website (regardless of where you visit it from) and tell you about your privacy rights and how the law protects you.
14+
15+
## Important Information and Who We Are
16+
17+
Open Infrastructure Services LLC provides custom software development and consulting services. This privacy policy aims to give you information on how Open Infrastructure Services LLC collects and processes your personal data through your use of this website, including any data you may provide through this website.
18+
19+
## The Data We Collect About You
20+
21+
We may collect, use, store, and transfer different kinds of personal data about you, which we have grouped together as follows:
22+
- Identity Data includes first name, last name, username, or similar identifier.
23+
- Contact Data includes email address and telephone numbers.
24+
- Technical Data includes internet protocol (IP) address, your login data, browser type and version, time zone setting and location, browser plug-in types and versions, operating system and platform, and other technology on the devices you use to access this website.
25+
26+
## How Is Your Personal Data Collected?
27+
28+
We use different methods to collect data from and about you, including through:
29+
- Direct interactions. You may give us your Identity, Contact, and Financial Data by filling in forms or by corresponding with us by post, phone, email, or otherwise.
30+
- Automated technologies or interactions. As you interact with our website, we may automatically collect Technical Data about your equipment, browsing actions, and patterns.
31+
32+
## How We Use Your Personal Data
33+
34+
We will only use your personal data when the law allows us to. Most commonly, we will use your personal data in the following circumstances:
35+
- Where we need to perform the contract we are about to enter into or have entered into with you.
36+
- Where it is necessary for our legitimate interests (or those of a third party) and your interests and fundamental rights do not override those interests.
37+
- Where we need to comply with a legal obligation.
38+
39+
## Data Security
40+
41+
We have put in place appropriate security measures to prevent your personal data from being accidentally lost, used, or accessed in an unauthorized way, altered, or disclosed.
42+
43+
## Data Retention
44+
45+
We will only retain your personal data for as long as necessary to fulfill the purposes we collected it for, including for the purposes of satisfying any legal, accounting, or reporting requirements.
46+
47+
## Your Legal Rights
48+
49+
Under certain circumstances, you have rights under data protection laws in relation to your personal data, including the right to request access, correction, erasure, restriction, transfer, to object to processing, to portability of data, and (where the lawful ground of processing is consent) to withdraw consent.
50+
51+
## Third-party Links
52+
53+
This website may include links to third-party websites, plug-ins, and applications. Clicking on those links or enabling those connections may allow third parties to collect or share data about you. We do not control these third-party websites and are not responsible for their privacy statements.
54+
55+
## Third-Party Subprocessors
56+
57+
Available on Request
58+
59+
## Contact Us
60+
61+
For any and all privacy-related matters, questions or comments, or to exercise a right under the EU’s GDPR, the UK’s GDPR or the CCPA, you may contact us in writing or by email. Our contact information is as follow:
62+
63+
Open Infrastructure Services, LLC
64+
65+
1675 SW MARLOW AVE STE 404
66+
67+
Portland, OR 97225
68+
69+
United States
70+
71+
Phone: +1 (669) 444-1014
72+
73+
Email: [email protected]
74+
75+
Website: https://openinfrastructure.co
76+
77+
## Changes to the Privacy Policy
78+
79+
We may update this privacy policy from time to time. We encourage you to review this privacy policy frequently to be informed of how we are protecting your information.

0 commit comments

Comments
 (0)