Docs: recipe landing page (#3122)

This commit is contained in:
Rizel Scarlett
2025-06-28 00:00:06 -04:00
committed by GitHub
parent d7fa8aed5c
commit 7899cd0c02
12 changed files with 231 additions and 27 deletions

View File

@@ -0,0 +1,8 @@
{
"label": "Recipes",
"position": 1,
"link": {
"type": "doc",
"id": "guides/recipes/index"
}
}

View File

@@ -0,0 +1,75 @@
---
title: Recipes
hide_title: true
description: Reusable and shareable AI workflows
---
import Card from '@site/src/components/Card';
import styles from '@site/src/components/Card/styles.module.css';
<h1 className={styles.pageTitle}>Recipes</h1>
<p className={styles.pageDescription}>
Recipes are reusable workflows that package extensions, prompts, and settings together. Share proven workflows with your team and reproduce successful results consistently.
</p>
<!-- will replace with Recipe video once live -->
<!-- <div className="video-container margin-bottom--lg">
<iframe
width="100%"
height="400"
src="https://www.youtube.com/embed/D-DpDunrbpo"
title="Vibe coding with Goose"
frameBorder="0"
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
allowFullScreen
></iframe>
</div> -->
<div className={styles.categorySection}>
<h2 className={styles.categoryTitle}>📚 Documentation & Guides</h2>
<div className={styles.cardGrid}>
<Card
title="Shareable Recipes"
description="Share a Goose session setup (including tools, goals, and instructions) as a reusable recipe that others can launch with a single click."
link="/docs/guides/recipes/session-recipes"
/>
<Card
title="Recipe Reference Guide"
description="Complete technical reference for creating and customizing recipes in Goose via the CLI."
link="/docs/guides/recipes/recipe-reference"
/>
</div>
</div>
<div className={styles.categorySection}>
<h2 className={styles.categoryTitle}>🛠️ Tools & Generators</h2>
<div className={styles.cardGrid}>
<Card
title="Recipe Generator"
description="Interactive tool that creates a shareable Goose recipe URL that others can use to launch a session with your predefined settings."
link="/recipe-generator"
/>
<Card
title="Recipe Cookbook"
description="Browse our collection of ready-to-use recipes. Find and adapt recipes for common development scenarios."
link="/recipes"
/>
</div>
</div>
<div className={styles.categorySection}>
<h2 className={styles.categoryTitle}>📝 Featured Blog Posts</h2>
<div className={styles.cardGrid}>
<Card
title="Championship Driven Development"
description="Recipes to accelerate your developer team's workflow."
link="/blog/2025/05/09/developers-ai-playbook-for-team-efficiency"
/>
<Card
title="A Recipe for Success"
description="The value of scaling agentic workflows with recipes."
link="/blog/2025/05/06/recipe-for-success"
/>
</div>
</div>

View File

@@ -1,7 +1,7 @@
---
sidebar_position: 18
sidebar_position: 2
title: Recipe Reference Guide
sidebar_label: Recipe Reference Guide
description: Complete technical reference for creating and customizing recipes in Goose via the CLI.
---
Recipes are reusable Goose configurations that package up a specific setup so it can be easily shared and launched by others.

View File

@@ -1,7 +1,6 @@
---
sidebar_position: 5
title: Create a Recipe from Your Session
sidebar_label: Shareable Recipes
sidebar_position: 1
title: Shareable Recipes
description: "Share a Goose session setup (including tools, goals, and instructions) as a reusable recipe that others can launch with a single click"
---

View File

@@ -39,7 +39,7 @@ Commit your code changes early and often. This allows you to rollback any unexpe
Administrators can use an [allowlist](/docs/guides/allowlist) to restrict Goose to approved extensions only. This helps prevent risky installs from unknown MCP servers.
### Set up starter templates
You can turn a successful session into a reusable "[recipe](/docs/guides/session-recipes)" to share with others or use again later—no need to start from scratch.
You can turn a successful session into a reusable "[recipe](/docs/guides/recipes/session-recipes)" to share with others or use again later—no need to start from scratch.
### Embrace an experimental mindset
You dont need to get it right the first time. Iterating on prompts and tools is part of the workflow.