Fix Blueprint section layout on very small screens

This commit is contained in:
Connor Chan 2019-09-18 15:22:34 -07:00
parent fc08bd9aa3
commit 086605dc42
1 changed files with 10 additions and 10 deletions

View File

@ -113,46 +113,46 @@ stylesheet: index
</div> </div>
<div class="grid"> <div class="grid">
<div class="blueprint-items col-6_md-12 grid"> <div class="blueprint-items col-6_md-12 grid">
<div class="blueprint-bullet col-1"> <div class="blueprint-bullet col-1_xs-2">
<img src="{{ "/images/separation.svg" | relative_url }}" /> <img src="{{ "/images/separation.svg" | relative_url }}" />
</div> </div>
<div class="blueprint-item col-11"> <div class="blueprint-item col-11_xs-10">
<h3>A strong separation of concerns.</h3> <h3>A strong separation of concerns.</h3>
<p>Developers can define workloads without worrying about implementation details, <p>Developers can define workloads without worrying about implementation details,
environment constraints, or policies. Administrators can define environment specifics, environment constraints, or policies. Administrators can define environment specifics,
and policies. Enable a higher degree of reusability and reduce complexity.</p> and policies. Enable a higher degree of reusability and reduce complexity.</p>
</div> </div>
<div class="blueprint-bullet col-1"> <div class="blueprint-bullet col-1_xs-2">
<img src="{{ "/images/portability.svg" | relative_url }}" /> <img src="{{ "/images/portability.svg" | relative_url }}" />
</div> </div>
<div class="blueprint-item col-11"> <div class="blueprint-item col-11_xs-10">
<h3>Workload portability across cloud providers.</h3> <h3>Workload portability across cloud providers.</h3>
<p>As a multicloud workload and resource orchestrator, Crossplane manages workloads <p>As a multicloud workload and resource orchestrator, Crossplane manages workloads
(container, serverless, others) and resources they consume (databases, message queues, (container, serverless, others) and resources they consume (databases, message queues,
buckets, data pipelines, and others) across clouds and on-premise environments.</p> buckets, data pipelines, and others) across clouds and on-premise environments.</p>
</div> </div>
<div class="blueprint-bullet col-1"> <div class="blueprint-bullet col-1_xs-2">
<img src="{{ "/images/agenda.svg" | relative_url }}" /> <img src="{{ "/images/agenda.svg" | relative_url }}" />
</div> </div>
<div class="blueprint-item col-11"> <div class="blueprint-item col-11_xs-10">
<h3>Open source that doesnt have an agenda.</h3> <h3>Open source that doesnt have an agenda.</h3>
<p>Crossplane is open source software released under the Apache 2.0 license. Crossplane is <p>Crossplane is open source software released under the Apache 2.0 license. Crossplane is
a true community-driven effort to define a control plane that can span multiple cloud a true community-driven effort to define a control plane that can span multiple cloud
providers, many regions and offerings.</p> providers, many regions and offerings.</p>
</div> </div>
<div class="blueprint-bullet col-1"> <div class="blueprint-bullet col-1_xs-2">
<img src="{{ "/images/extensibility.svg" | relative_url }}" /> <img src="{{ "/images/extensibility.svg" | relative_url }}" />
</div> </div>
<div class="blueprint-item col-11"> <div class="blueprint-item col-11_xs-10">
<h3>Built with high levels of extensibility.</h3> <h3>Built with high levels of extensibility.</h3>
<p>Leverages tried and tested Kubernetes machinery to provide a high level of extensibility <p>Leverages tried and tested Kubernetes machinery to provide a high level of extensibility
around APIs, resource controllers, schedulers and other components. This empowers the around APIs, resource controllers, schedulers and other components. This empowers the
community to build on top of it easily.</p> community to build on top of it easily.</p>
</div> </div>
<div class="blueprint-bullet col-1"> <div class="blueprint-bullet col-1_xs-2">
<img src="{{ "/images/cycle.svg" | relative_url }}" /> <img src="{{ "/images/cycle.svg" | relative_url }}" />
</div> </div>
<div class="blueprint-item col-11"> <div class="blueprint-item col-11_xs-10">
<h3>Full lifecycle management of resources.</h3> <h3>Full lifecycle management of resources.</h3>
<p>A resource controller is responsible for the entire lifecycle of a resource. This <p>A resource controller is responsible for the entire lifecycle of a resource. This
resource is responsible for provisioning, health, scaling, failover, and actively resource is responsible for provisioning, health, scaling, failover, and actively