Skip to content

Undo an accidental UI change to the production framework guide #172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Parent: Fixing sample usage module path for VPC deployment config
merged 1 commit into from
Feb 7, 2022
Merged

Undo an accidental UI change to the production framework guide #172

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 1 addition & 43 deletions _docs-sources/guides/production-framework/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,53 +1,11 @@
import Card from "/src/components/Card"
import { CardList } from "/src/components/CardGroup"

# The Gruntwork Production Framework

In this guide, we are going to share our opinionated, step-by-step framework for successfully going to production on
the public cloud. At Gruntwork, we've had the privilege to work with everything from tiny startups to massive Fortune
50 companies to some of the world's largest government agencies, and this document captures the common patterns we've
seen that actually worked.

<div style={{maxWidth: "640px", margin: "auto", marginTop: "3rem"}}>

## The Elements of the Gruntwork Production Framework

<CardList style={{marginTop: 0}}>

<Card
title="Service Catalog"
href="./ingredients/service-catalog"
icon="/img/icons/service-catalog.svg">
Your company's vetted, tested, reusable, off-the-shelf solutions for infrastructure and appliactions.
</Card>
<Card
title="Landing Zone"
href="./ingredients/landing-zone"
icon="/img/icons/landing-zone.svg">
The basic structure for your cloud accounts, including auth, guard rails, and other scaffolding.
</Card>
<Card
title="CI / CD"
href="./ingredients/ci-cd-pipeline"
icon="/img/icons/ci-cd.svg">
A Continuous Integration / Continuous Delivery pipeline to automate builds, tests, and deployments.
</Card>
<Card
title="Self-service"
href="./ingredients/self-service"
icon="/img/icons/self-service.svg">
Allow developers to deploy and manage their own apps and infrastructure.
</Card>
<Card
title="Automatic Updates"
href="./ingredients/automatic-updates"
icon="/img/icons/auto-update.svg">
Kepp all your application and infrastructure dependencies up to date, automatically.
</Card>

</CardList>

</div>
![Gruntwork Production Framework](/img/guides/production-framework/gruntwork-production-framework-small.png)

This is not another high-level, vague "cloud operating model" document that is heavy on buzzwords but light on
actionable content. Instead, you'll find a clear mental model of how to think about cloud usage, plus a set of
Expand Down
46 changes: 2 additions & 44 deletions docs/guides/production-framework/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,53 +1,11 @@
import Card from "/src/components/Card"
import { CardList } from "/src/components/CardGroup"

# The Gruntwork Production Framework

In this guide, we are going to share our opinionated, step-by-step framework for successfully going to production on
the public cloud. At Gruntwork, we've had the privilege to work with everything from tiny startups to massive Fortune
50 companies to some of the world's largest government agencies, and this document captures the common patterns we've
seen that actually worked.

<div style={{maxWidth: "640px", margin: "auto", marginTop: "3rem"}}>

## The Elements of the Gruntwork Production Framework

<CardList style={{marginTop: 0}}>

<Card
title="Service Catalog"
href="./ingredients/service-catalog"
icon="/img/icons/service-catalog.svg">
Your company's vetted, tested, reusable, off-the-shelf solutions for infrastructure and appliactions.
</Card>
<Card
title="Landing Zone"
href="./ingredients/landing-zone"
icon="/img/icons/landing-zone.svg">
The basic structure for your cloud accounts, including auth, guard rails, and other scaffolding.
</Card>
<Card
title="CI / CD"
href="./ingredients/ci-cd-pipeline"
icon="/img/icons/ci-cd.svg">
A Continuous Integration / Continuous Delivery pipeline to automate builds, tests, and deployments.
</Card>
<Card
title="Self-service"
href="./ingredients/self-service"
icon="/img/icons/self-service.svg">
Allow developers to deploy and manage their own apps and infrastructure.
</Card>
<Card
title="Automatic Updates"
href="./ingredients/automatic-updates"
icon="/img/icons/auto-update.svg">
Kepp all your application and infrastructure dependencies up to date, automatically.
</Card>

</CardList>

</div>
![Gruntwork Production Framework](/img/guides/production-framework/gruntwork-production-framework-small.png)

This is not another high-level, vague "cloud operating model" document that is heavy on buzzwords but light on
actionable content. Instead, you'll find a clear mental model of how to think about cloud usage, plus a set of
Expand Down Expand Up @@ -219,5 +177,5 @@ Gruntwork to help you implement this framework.


<!-- ##DOCS-SOURCER-START
{"sourcePlugin":"local-copier","hash":"8e70078144f75a63e78b504b6c04e253"}
{"sourcePlugin":"local-copier","hash":"0f5e3c087339ab8a712c9fa33f909206"}
##DOCS-SOURCER-END -->