Skip to content
This repository has been archived by the owner on Sep 23, 2020. It is now read-only.

Commit

Permalink
minor style updates, and added content for submission page
Browse files Browse the repository at this point in the history
  • Loading branch information
JoeMorgan committed Aug 23, 2015
1 parent 72d3a26 commit c2df433
Show file tree
Hide file tree
Showing 12 changed files with 144 additions and 94 deletions.
6 changes: 3 additions & 3 deletions _data/navigation.yml
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Site navigation links

- title: What Is Devops?
url: /what-is-devops/

- title: About
url: /about/

- title: What Is Devops?
url: /what-is-devops/

- title: Submit a Post
url: /submission/
3 changes: 1 addition & 2 deletions _includes/_scripts.html
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="{{ site.url }}/assets/js/vendor/jquery-1.9.1.min.js"><\/script>')</script>
<script src="{{ site.url }}/assets/js/vendor/jquery-2.1.4.min.js"></script>
<script src="{{ site.url }}/assets/js/scripts.min.js"></script>
{% if site.owner.google.analytics %}
<!-- Asynchronous Google Analytics snippet -->
Expand Down
114 changes: 59 additions & 55 deletions _layouts/home.html
Original file line number Diff line number Diff line change
Expand Up @@ -12,70 +12,74 @@
{% include _browser-upgrade.html %}

<section>
{% include _navigation.html %}
{% if page.image.feature %}
<div class="image-wrap">
<img src=
{% if page.image.feature contains 'http' %}
"{{ page.image.feature }}"
{% else %}
"{{ site.url }}/images/{{ page.image.feature }}"
{% endif %}
alt="{{ page.title }} feature image">
{% if page.image.credit %}
<span class="image-credit">Photo Credit: <a href="{{ page.image.creditlink }}">{{ page.image.credit }}</a></span>
{% endif %}
</div><!-- /.image-wrap -->
{% endif %}
{% include _navigation.html %}
{% if page.image.feature %}
<div class="image-wrap">
<img src=
{% if page.image.feature contains 'http' %}
"{{ page.image.feature }}"
{% else %}
"{{ site.url }}/images/{{ page.image.feature }}"
{% endif %}
alt="{{ page.title }} feature image">
{% if page.image.credit %}
<span class="image-credit">Photo Credit: <a href="{{ page.image.creditlink }}">{{ page.image.credit }}</a></span>
{% endif %}
</div><!-- /.image-wrap -->
{% endif %}
</section>


<main id="main" role="main">
<div class="article-author-side">
{% include _author-bio.html %}
</div>
<div id="index">
<div class="article-author-side">
{% include _author-bio.html %}
</div>
<div id="index">

{% for post in site.posts limit:1 %}
<article>
{% if post.link %}
<h1 class="link-post"><a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a>
<a href="{{ post.link }}" target="_blank" title="{{ post.title }}"><i class="fa fa-link"></i></a></h1>
{% else %}
<h1><a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a></h1>
{{ post.content | truncate: 1000}}
{% if post.content.size > 1000 %}
<p class="read-more-link">
<a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">Read more</a>
</p>
{% endif %}
{% endif %}
</article>
{% endfor %}
<p class="callout">
Introducing the devops movement to digital experts of all disciplines, to change the way we work.
</p>

{% if site.posts.size > 1 %}
<section class="recent-posts">
<h3><a href="{{ site.url}}/posts/">Recent Posts</a></h3>
{% for post in site.posts limit:5 offset:1 %}
<article>
{% if post.link %}
<h2 class="link-post"><a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a>
<a href="{{ post.link }}" target="_blank" title="{{ post.title }}"><i class="fa fa-link"></i></a></h2>
{% else %}
<h2><a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a></h2>
<p>{{ post.excerpt | strip_html | truncate: 160 }}</p>
{% endif %}
</article>
{% endfor %}
</section>
{% endif %}
</div><!-- /#index -->
{% for post in site.posts limit:1 %}
<article>
{% if post.link %}
<h1 class="link-post"><a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a>
<a href="{{ post.link }}" target="_blank" title="{{ post.title }}"><i class="fa fa-link"></i></a></h1>
{% else %}
<h1><a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a></h1>
{{ post.content | truncate: 1000}}
{% if post.content.size > 1000 %}
<p class="read-more-link">
<a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">Read more</a>
</p>
{% endif %}
{% endif %}
</article>
{% endfor %}

{% if site.posts.size > 1 %}
<section class="recent-posts">
<h3><a href="{{ site.url}}/posts/">Recent Posts</a></h3>
{% for post in site.posts limit:5 offset:1 %}
<article>
{% if post.link %}
<h2 class="link-post"><a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a>
<a href="{{ post.link }}" target="_blank" title="{{ post.title }}"><i class="fa fa-link"></i></a></h2>
{% else %}
<h2><a href="{{ site.url }}{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a></h2>
<p>{{ post.excerpt | strip_html | truncate: 160 }}</p>
{% endif %}
</article>
{% endfor %}
</section>
{% endif %}
</div><!-- /#index -->
</main><!-- /#main -->

<div class="footer-wrap">
<footer>
{% include _footer.html %}
</footer>
<footer>
{% include _footer.html %}
</footer>
</div><!-- /.footer-wrap -->

{% include _scripts.html %}
Expand Down
13 changes: 0 additions & 13 deletions _posts/2015-08-09-hello-world.md

This file was deleted.

20 changes: 20 additions & 0 deletions _posts/2015-08-23-hello-world.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
layout: post
title: Hello World
author: joe_morgan
excerpt: "Do you feel like you're on the outside of the devops movement, looking in? Are you excited about automation and measurement as tools to improve the way you work, but you don't typically play in the ops space? This is the place for you. Welcome to Devops for the Rest of Us."
tags: [devops, bizdevops, hello world, meta blog]
comments: true
---

Do you feel like you're on the outside of the devops movement, looking in? Are you excited about automation and measurement as tools to improve the way you work, but you don't typically play in the ops space? This is the place for you. Welcome to Devops for the Rest of Us.

I lead a group of front-end developers at a [digital ad agency](http://sapientnitro.com "SapientNitro.com") in Boston. Front-end dev has seen an explosion in tooling and complexity over the last few years, and so we're starting to see

Do you feel like you're on the outside of the devops movement, looking in? Are you excited about automation and measurement as tools to improve the way you work, but you don't typically play in the ops space? This is the place for you. Welcome to Devops for the Rest of Us.

I lead a group of front-end developers at a [digital ad agency](http://sapientnitro.com "SapientNitro.com") in Boston. Front-end dev has seen an explosion in tooling and complexity over the last few years, and so we're starting to see Do you feel like you're on the outside of the devops movement, looking in? Are you excited about automation and measurement as tools to improve the way you work, but you don't typically play in the ops space? This is the place for you. Welcome to Devops for the Rest of Us.

I lead a group of front-end developers at a [digital ad agency](http://sapientnitro.com "SapientNitro.com") in Boston. Front-end dev has seen an explosion in tooling and complexity over the last few years, and so we're starting to see Do you feel like you're on the outside of the devops movement, looking in? Are you excited about automation and measurement as tools to improve the way you work, but you don't typically play in the ops space? This is the place for you. Welcome to Devops for the Rest of Us.

I lead a group of front-end developers at a [digital ad agency](http://sapientnitro.com "SapientNitro.com") in Boston. Front-end dev has seen an explosion in tooling and complexity over the last few years, and so we're starting to see
10 changes: 9 additions & 1 deletion _sass/typography.scss
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,9 @@ h5 {
h6 {
@include font-size(14);
}

h3{
margin-top:1rem;
}
/*
Links
========================================================================== */
Expand Down Expand Up @@ -162,6 +164,12 @@ p {
}
}

.callout{
font-size:1.4rem;
margin-bottom:3rem;
font-style:italic;
}

/*
=======
/*
Expand Down
2 changes: 1 addition & 1 deletion about/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ author: joe_morgan
tags: [about, bio, joe, Sapient, CMTOu]
comments: false
image:
feature: shapes-3.png
feature: shapes-2.png
---

At a glance, Devops for the Rest of Us may seem odd. A devops blog that intentionally shifts the focus <i>away</i> from development and IT operations? What gives?
Expand Down
1 change: 0 additions & 1 deletion assets/js/_main.js
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,6 @@ var changeClass = function (r,className1,className2) {
// Creating our button in JS for smaller screens
var menuElements = document.getElementById('site-nav');
menuElements.insertAdjacentHTML('afterBegin','<button type="button" role="button" id="menutoggle" class="navtoogle navicon-lines-button x" aria-hidden="true"><span class="navicon-lines"></span>menu</button>');

// Toggle the class on click to show / hide the menu
document.getElementById('menutoggle').onclick = function() {
changeClass(this, 'navtoogle active', 'navtoogle');
Expand Down
4 changes: 4 additions & 0 deletions assets/js/vendor/jquery-2.1.4.min.js

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
layout: home
author: joe_morgan
excerpt: ""
tags: [Jekyll, theme, responsive, blog, template]
tags: [devops, ways of working, introduction, recent posts]
image:
feature: shapes-1.png
---
57 changes: 43 additions & 14 deletions submission/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,25 +2,54 @@
layout: page
title: Submit a Post
author: joe_morgan
tags: [post submission, how-to]
tags: [post submission, how-to, github, email submission]
comments: false
image:
feature: shapes-4.png
---

## Outline ##
{% include _toc.html %}

This page describes how this blog is built to allow anyone to contribute posts, and describes how to do so.
Maybe you have an idea for how to apply devops principles to your job, outside of the intersection of development and operations. Or maybe you disagree with something I've said on this site so vehemently that a simple comment isn't enough to properly shred my viewpoint. Maybe you just want all of the wealth and recognition that comes from contributing to an open source blog.

1. Why you should want to submit a blog post
1. Speak to people outside of the typical devops community
2. Speak to leaders and practicioners in the devops space
2. How to submit
1. Fork my repo on github
2. Create a markdown file in the _posts folder (following specified naming conventions)
3. Make a pull request
3. Rules for submission
1. Opinion pieces are ok
2. Nothing derogatory, spiteful, or inflammatory (though challenges to established ideas are welcome)
3. For the most part, don't make pull requests for changes to the blog outside of the _posts folder (though if you really want to improve upon the blog in some objective way, I'm open to it)
Well, why not author a post of your own? One of the neat things about this blog is that it <i>is</i> open source, and anyone can contribute. Given the intended reach of this site, there are a couple ways that you could write a post, depending on whether or not you're comfortable with <a href="https://github.com/" target="_blank" title="GitHub">GitHub</a>.

##Ways to Contribute##

###Fork the Repo on GitHub###

If you're a technologist or you're otherwise familiar with git and GitHub, you'll probably find it easiest to simply fork <a href="https://github.com/JoeMorgan/devopsfortherestofus" target="_blank" title="Devops for the Rest of Us on GitHub">the repository</a>, draft your content, and make a pull request.

This blog uses <a href="http://jekyllrb.com/" target="_blank" title="Jekyll &bull; Simple, blog-aware, static sites">Jekyll</a>, so you can draft your content using Markdown. New posts are stored in the /_posts folder, so just add a file and name it appropriately for the date of publication (e.g., the Hello World post for this blog is named "2015-08-23-hello-world.md").

Each post should have some YAML "front matter" at the top to tell Jekyll how to create the static page. This is really just simple metadata, and you can use one of the existing posts as a starting point. For example, the front matter for my Hello World post looks like this:

{% highlight html %} {% raw %}---
layout: post
title: Hello World
author: joe_morgan
excerpt: "Do you feel like you're on the outside of the devops movement, looking in? Are you excited about automation and measurement as tools to improve the way you work, but you don't typically play in the ops space? This is the place for you. Welcome to Devops for the Rest of Us."
tags: [devops, bizdevops, hello world, meta blog]
comments: true
---{% endraw %} {% endhighlight %}

You may notice that it includes a reference to author. If you don't want my ugly mug next to your post, you'll have to do one more thing before making your pull request: simply update /data/authors.yml with an entry for yourself, and if you want a bio picture, put it in the /images folder (with the file name listed under "avatar" in the authors.yml). You only have to do this once, even if you're planning on writing multiple posts.

That's probably all you'll need to update. Though if you had a good idea for improving the site, you could make edits elsewhere in the codebase, I suppose. We just might need to talk it through before I accept the request.

And please remember to follow the general [submission guidelines](#submission-guidelines).

That's it! Now you can list experience with Jekyll on your resume.

###Send Me Your Post Content###

Yup, the old school way. Since this is a simple static site, we're not going to deal with logins, draft states, and permissions. Unless you're [comfortable using GitHub](#fork-the-repo-on-github), the best way for your voice to be heard on the blog is to simply reach out to me with your idea.

You can draft the post content over <a href="mailto:{{ site.owner.email }}" target="_blank">email</a>, along with some info about you for the sidebar (name, email, bio, an avatar picture to use, and any social info you want displayed).

Assuming you've followed the general [submission guidelines](#submission-guidelines), I'll draft the post and let you know when it's live. Easy, no?

##Submission Guidelines##
1. Content in some way relates to devops
2. Nothing derogatory, spiteful, or inflammatory; i.e., no trolling
3. Opinion pieces are okay (encouraged, even!)
6 changes: 3 additions & 3 deletions what-is-devops/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,14 +3,14 @@ layout: page
title: What Is Devops?
author: joe_morgan
tags: [devops, bizdevops, history of devops, automation, Lean IT, theory of constraints, The Three Ways]
comments: false
comments: true
image:
feature: shapes-2.png
feature: shapes-3.png
---

People have been defining and redefining devops for years. The intent here isn't to propose yet another definition, but to try to describe the thinking behind the modern devops movement and to provide a gentle introduction for those of you who are new to the topic. For you seasoned devops professionals, please jump in and correct me if I go astray.

It may be obvious from the word devops&mdash;technically called a <a href="https://en.wikipedia.org/wiki/Portmanteau" target="_blank" title="Wikipedia">portmanteau</a>, but I prefer "frankenword"&mdash;that this all started as a way to combine development and operations. To bridge the gap between coders and infra people. But why? What gap are we talking about?
It may be obvious from the word devops&mdash;technically called a <a href="https://en.wikipedia.org/wiki/Portmanteau" target="_blank" title="Wikipedia">portmanteau</a>, but I prefer "frankenword"&mdash;that this all started as a way to combine development and operations. To bridge the gap between coders, who build products, services, and experiences, and infrastructure teams, who provision hardware and configure environments to bring that code out into the world. But why? What gap are we talking about?


##Build and Release##
Expand Down

0 comments on commit c2df433

Please sign in to comment.