basic structure for Write feature

This commit is contained in:
Jason Costello 2016-10-03 12:51:57 -07:00
parent b992e8e3e3
commit 37d97623d7
2 changed files with 34 additions and 3 deletions

View File

@ -19,9 +19,10 @@
@include lato-light();
}
h3 {
h3{
font-size: 18px;
letter-spacing: 1px;
text-transform: uppercase;
}
p{
@ -31,6 +32,11 @@
font-weight: 300;
}
p.lead{
font-size: 24px;
max-width: 30em;
}
.icn{
display: block;
width: 186px;
@ -59,13 +65,18 @@
}
}
#feature-overview{
padding-bottom: 120px;
border-bottom: 2px solid #E6E7E8;
}
.feature-card {
height: 230px;
border: 2px solid #E6E7E8;
padding:20px;
font-size: 18px;
h3 {
h3{
margin:0;
padding: 0;
color: $purple;
@ -74,7 +85,7 @@
text-transform: uppercase;
}
p {
p{
font-weight: 400;
text-transform: uppercase;
letter-spacing: 1px;

View File

@ -35,6 +35,26 @@
</div>
</div>
<div class="feature" id="feature-write">
<div class="container">
<div class="row">
<div class="col-sm-12">
<h2>Infrastructure as code</h2>
<p class="lead">Define infrastructure as code to increase operator productivity through collaboration and automation.</p>
</div>
<div class="col-sm-4">
<h3>Collaborate &amp; share</h3>
<p>Terraform configuration and state can be stored in version control,
shared, and collaborated on by teams of operators.</p>
<h3>Evolve your infrastructure</h3>
<p>Track the complete history of infrastructure versions.</p>
<h3>Automation friendly</h3>
<p>If it can be codified, it can be automated.</p>
</div>
</div>
</div> <!-- /container -->
<div class="feature-skew" id="feature-auto-bg"></div>
</div> <!-- /feature -->