Skip to content
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.

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

docs: update 'How Garden Works' guide #3227

Merged
merged 2 commits into from
Sep 20, 2022
Merged

docs: update 'How Garden Works' guide #3227

merged 2 commits into from
Sep 20, 2022

Conversation

eysi09
Copy link
Collaborator

@eysi09 eysi09 commented Sep 14, 2022

What this PR does / why we need it:

This commit adds a bit more content and explanations to the 'How Garden Works' guide.

In particular it only focuses on the core framework and leaves out individual plugins.

The plan is to follow up with separate plugin specific guides.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

This commit adds a bit more content and explanations to the 'How Garden
Works' guide.

In particular it only focuses on the core framework and leaves
out individual plugins.

The plan is to follow up with separate plugin specific guides.
@@ -5,21 +5,136 @@ title: How Garden Works

# How Garden Works

Garden Core is a standalone tool that can run from CI or from a developer’s machine. It allows you to codify a complete description of your stack, including how it's built, deployed and tested, using the [Stack Graph](https://docs.garden.io/basics/stack-graph)—making your workflows reproducible and portable.
For those that prefer something a bit more visual, we recommend checking out this [short introduction video](https://www.youtube.com/watch?app=desktop&v=3gMJWGV0WE8) to how Garden works:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Errant colon at the end there.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those pesky colons. Gone now.

@eysi09 eysi09 force-pushed the docs-new-how-to-guide branch from 9e98b03 to 5f89119 Compare September 14, 2022 17:34
@edvald edvald merged commit 2947b38 into master Sep 20, 2022
@edvald edvald deleted the docs-new-how-to-guide branch September 20, 2022 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants