diff --git a/assets/sass/_hubspot.scss b/assets/sass/_hubspot.scss index e0b0237b9030..380591bc85b9 100644 --- a/assets/sass/_hubspot.scss +++ b/assets/sass/_hubspot.scss @@ -77,7 +77,11 @@ } input { - @apply block py-3 px-4 rounded-l rounded-r-none text-gray-600 w-56; + @apply block py-3 px-4 rounded-l rounded-r-none text-gray-600; + + @screen md { + @apply w-56; + } &.hs-button { @apply block btn btn-lg btn border-none py-3 px-4 rounded-r rounded-l-none w-auto; diff --git a/assets/sass/_pagination.scss b/assets/sass/_pagination.scss index c9661ad83b25..47ec8a1c591c 100644 --- a/assets/sass/_pagination.scss +++ b/assets/sass/_pagination.scss @@ -9,7 +9,11 @@ } > span, > a { - @apply block px-4 py-2; + @apply block px-2 py-1; + + @screen md { + @apply text-sm px-4 py-2; + } } a { diff --git a/assets/sass/_pricing.scss b/assets/sass/_pricing.scss new file mode 100644 index 000000000000..63672559aee7 --- /dev/null +++ b/assets/sass/_pricing.scss @@ -0,0 +1,31 @@ +.pricing-item-heading { + @apply bg-gray-200 text-purple-700 text-sm font-display font-bold border-b border-gray-300 px-2 py-4; + + @screen md { + @apply text-base p-4; + } +} + +.pricing-item { + @apply flex items-center border-b border-gray-100 text-xs text-center; + + @screen md { + @apply text-sm border-b border-gray-200; + } + + .pricing-item-label { + @apply w-1/4 border-gray-200 text-left p-2 font-bold; + + @screen md { + @apply font-bold py-4 px-8; + } + } + + .pricing-item-value { + @apply w-1/4 p-2; + + @screen md { + @apply p-4; + } + } +} diff --git a/assets/sass/styles.scss b/assets/sass/styles.scss index e8ed057d24a8..d192a0b35ae4 100644 --- a/assets/sass/styles.scss +++ b/assets/sass/styles.scss @@ -16,6 +16,7 @@ @import "langchoose"; @import "no-select"; @import "pagination"; +@import "pricing"; @import "search"; @import "section-nav"; @import "tables"; diff --git a/content/why-pulumi/delivering-cloud-native-infrastructure-as-code.md b/content/why-pulumi/delivering-cloud-native-infrastructure-as-code.md index 888045e5580d..1fd91c8655af 100644 --- a/content/why-pulumi/delivering-cloud-native-infrastructure-as-code.md +++ b/content/why-pulumi/delivering-cloud-native-infrastructure-as-code.md @@ -53,11 +53,11 @@ As usual, the future is unevenly distributed. A quick look at Google Trends over #### Interest Over Time, 5 Years to Current Date - + We can redraw this picture as an adoption curve across these evolutions approximately as follows: - + Each of these evolutions has opportunity, but also embedded cost: cost to switch, cost of skills, and cost of workflows and tools. Each also carries risk through isolated stovepipes: limited numbers of experts to attend to a given paradigm. @@ -97,7 +97,7 @@ Using real languages changes everything. [The Pulumi Cloud Development Platform] At the center of Pulumi is an open source cloud object model, coupled with an evaluation runtime that understands how to take programs written in any language, understand the cloud resources necessary to execute them, and then plan and manage those resources in a robust way. This cloud runtime and object model is inherently language- and cloud-neutral, enabling Pulumi to support many languages and clouds rapidly. - + Pulumi aims to provide a solution to the challenges of cloud application development and delivery by providing a consistent programming model for cloud native development: @@ -167,7 +167,7 @@ Because infrastructure is now linked to application code, and because of the eph Previously there was very limited tooling at the very point of collaboration needed by development and devops teams. Pulumi connects those teams and improves the required workflows. - + **Delivering Cloud 'Stacks'.** A core concept in Pulumi is the idea of a "stack." A stack is an isolated instance of a cloud program whose resources and configuration are distinct from all other stacks. A team might have a stack each for production, staging, and testing, or perhaps for each single- tenanted environment. Pulumi's CLI makes it trivial to spin up and tear down lots of stacks. This opens up workflows that might not have previously even attempted, such as each developer having her own stack, spinning up (and tearing down) a fresh stack to test out each Pull Request, or even splitting tiers of your service into many stacks that are linked together - all of which is applicable and useful in cloud application deliver scenarios. @@ -282,7 +282,7 @@ Learning Machine suffered from a loss of productivity and an inability to meet b By using Pulumi, Learning Machine were able to reduce 25,000 LoC of ad-hoc scripts to 500 LoC of JavaScript that could be understood across all teams, enabling the development team to take accountability for service delivery to meet business needs. Additionally, moving to Pulumi removes lock-in to a specific cloud, and has enabled Learning Machine to begin work on their on-premises private cloud service. - + > Pulumi has given our team the tools and framework to achieve a unified development and DevOps model, boosting productivity and taking our business to any cloud environment that our customers need. We retired 25,000 lines of complex code that few team members understood and replaced it with 100s of lines in a real programming language. diff --git a/layouts/page/pricing.html b/layouts/page/pricing.html index 0e76d0f95fbd..053168c22578 100644 --- a/layouts/page/pricing.html +++ b/layouts/page/pricing.html @@ -25,7 +25,7 @@

Plans for teams of all sizes.

$50
per month

For teams just getting started deploying cloud applications and infrastructure.

-