From a6b4e7a00a36ea2f1edbe9da9f36d974e58c94b3 Mon Sep 17 00:00:00 2001 From: Rob Szumski Date: Fri, 23 Oct 2015 23:12:04 +0000 Subject: [PATCH] sq: improve responsiveness --- static/css/pages/plans.css | 33 +++++++++++--- static/partials/plans.html | 92 +++++++++++++++++++++----------------- 2 files changed, 78 insertions(+), 47 deletions(-) diff --git a/static/css/pages/plans.css b/static/css/pages/plans.css index 6507f3fcf..e7615df07 100644 --- a/static/css/pages/plans.css +++ b/static/css/pages/plans.css @@ -75,6 +75,7 @@ .plans-panel .tab-pane .plan-col { padding-left: 12px; padding-right: 12px; + margin-bottom: 30px; } .plans-panel .plan-col:before { @@ -162,15 +163,15 @@ } .plans-panel .faq-features { - margin-top: 60px; + margin-top: 15px; border-top: 1px solid #ddd; } .plans-panel .features-col { background-color: #f9f9f9; padding: 30px; - border: 1px solid #ddd; - border-top: 0px; + border-bottom: 1px solid #ddd; + border-top: none; } .plans-panel .row-container { @@ -184,7 +185,7 @@ } .plans-panel .tab-content { - margin-bottom: 30px; + margin-bottom: 0px; } .plans-panel .features-col .features-title { @@ -220,15 +221,37 @@ margin-bottom: 12px; } +.plans-panel .features-col .features-list li p { + display: none; +} + +@media (min-width: 992px) { + .plans-panel .features-col .features-list li p { + display: block; + } + .plans-panel .features-col { + border-right: none; + border-left: 1px solid #ddd; + } +} + .plans-panel .faq-col { - padding: 50px; + padding-bottom: 0px; padding-top: 30px; padding-left: 30px; + padding-right: 30px; + margin-bottom: 20px } .plans-panel .faq-col h4 { color: #2e79b9; margin-top: 50px; + font-weight: 500; + margin-bottom: 23px; +} + +.plans-panel .faq-col p+h4 { + margin-top: 40px; } .plans-panel .faq-col h4:first-child { diff --git a/static/partials/plans.html b/static/partials/plans.html index ec4915cc1..444490266 100644 --- a/static/partials/plans.html +++ b/static/partials/plans.html @@ -171,7 +171,7 @@
-
+
$12/mo @@ -194,7 +194,7 @@
-
+
$25/mo @@ -218,7 +218,7 @@
-
+
$50/mo @@ -242,7 +242,7 @@
-
+
Larger Plans @@ -278,65 +278,73 @@
-
+
All plans include:
-
    -
  • - Continuous Integration - Build your containers in response to git pushes: GitHub, BitBucket, Gitlab and others -
    • +
    +
    +
      +
    • + Continuous Integration +

      Build your containers in response to git pushes: GitHub, BitBucket, Gitlab and others

      +
      • -
    • - 30-Day Free Trial - Your first 30 days are free on Quay.io. Test it out and start building containers! -
      • +
    • + 30-Day Free Trial +

      Your first 30 days are free on Quay.io. Test it out and start building containers!

      +
      • -
    • - Public Repositories - Provide a public download page for your container. The best part, they’re free! -
      • +
    • + Public Repositories +

      Provide a public download page for your container. The best part, they're free!

      +
      • -
    • - Robot Accounts - Create credentials designed for deploying software automatically. -
      • +
    • + Robot Accounts +

      Create credentials designed for deploying software automatically.

      +
      • +
    +
    -
  • - Teams - Teams can collectively have access to manage specific repositories on your account. -
    • +
    +
      +
    • + Teams +

      Teams can collectively have access to manage specific repositories on your account.

      +
      • -
    • - SSL Encryption - Transit between Quay.io and your servers is secured automatically. -
      • +
    • + SSL Encryption +

      Transit between Quay.io and your servers is secured automatically.

      +
      • -
    • - Logging & Auditing - Auditing is essential for everything in your CI pipeline. Actions via API and UI are tracked. -
      • +
    • + Logging & Auditing +

      Auditing is essential for everything in your CI pipeline. Actions via API and UI are tracked.

      +
      • -
    • - Invoice History - Download past invoices for your billing team or purchasing departement. -
      • -
    +
  • + Invoice History +

    Download past invoices for your billing team or purchasing departement.

    +
    • +
+
+
-
+

How do I use Quay with my servers and code?

Using Quay with your infrastructure is separated into two main actions: building containers and distributing them to your servers.

You can configure Quay to automatically build containers of your code on each commit. Integrations with GitHub, Bitbucket, GitLab and self-hosted Git repositories are supported. Each built container is stored on Quay and is available to be pulled down onto your servers.

-

To distribute your private containers onto your servers, Docker or rkt must be configured with the correct credientials. Quay has sophisticated access controls – organizations, teams, robot accounts, and more – to give you full control over which servers can pull down your containers. An API can be used to automate the creation and management of these credentials.

+

To distribute your private containers onto your servers, Docker or rkt must be configured with the correct credientials. Quay has sophisticated access controls — organizations, teams, robot accounts, and more — to give you full control over which servers can pull down your containers. An API can be used to automate the creation and management of these credentials.

How is Quay optimized for a team environment?

-

Quay’s permission model is designed for teams. Each new user can be assigned to one or more teams, with specific permissions. Robot accounts, used for automated deployments, can be managed per team as well. This system allows for each development team to manage their own credentials.

+

Quay's permission model is designed for teams. Each new user can be assigned to one or more teams, with specific permissions. Robot accounts, used for automated deployments, can be managed per team as well. This system allows for each development team to manage their own credentials.

Full logging and auditing is integrated into every part of the application and API. Quay helps you dig into every action for more details.