📝 Blog Post: Creating and sharing effective Goose recipes

[taniandjerry]

Creating and Sharing Effective Goose Recipes

🚀 Goal

Create a comprehensive guide that teaches users how to create, optimize, and share effective Goose recipes for common development tasks and workflows.

🤔 Background

Recipes are one of Goose's most powerful features for automating repetitive development tasks. This blog post will help users understand how to create their own recipes and contribute to the community by sharing effective automation workflows.

🤝 How You Can Contribute

Write a practical guide based on your experience creating and sharing Goose recipes, including development processes, optimization techniques, and community contribution strategies.

🔑 Tasks and Acceptance Criteria

❗You must only assign yourself one task at a time to give everyone a chance to participate.❗

You may assign yourself another task after your current one is reviewed and accepted.

• [ ] You must host your content on your own website or channel.
• [ ] The content submitted for this task can be cross-posted across other platforms, however it will only count towards one content task. You may not reuse your content submitted for this task to get points for another task unless there are significant changes (like adding 30 seconds of extra content on YouTube).
• [ ] Add your content information directly to the documentation/src/pages/community/data/community-content.json file in the repository.
• [ ] Create a pull request with your changes for review.
• [ ] Link your submitted PR in a comment here to count towards Hacktoberfest.

Your contribution in community-content.json must include:

• [ ] Title: the title of your content
• [ ] Author: your display name and GitHub handle
• [ ] Type: Video or Blog (please choose the appropriate one)
• [ ] URL: a direct link to your content
• [ ] Thumbnail: a direct link to your blog post thumbnail, with ?w=400&h=225&fit=crop&crop=entropy&auto=format resizing at the end of the url
• [ ] Date: the date your blog is being submitted

🌟 Resources

• Recipe Contributing Guide
• Recipe Documentation
• Recipe Repository
• Community Recipes

🎊 Hacktoberfest

This issue is part of Hacktoberfest 2025! Perfect for contributors who want to help others learn about team collaboration with Goose.

To get started:

1. Comment .take on this issue to get assigned the task. Please assign yourself to one task at a time.
2. Read the contribution guidelines
3. Create a forked PR following GitHub's guide
4. Submit the pull request when ready
5. Wait for review and address any feedback

Questions?

If you have any questions or need clarification, please comment on this issue or check the Goose GitHub discussions.

Happy coding! 🎉

[TSP06]

.take

[github-actions[bot]]

Thanks for taking this issue! Let us know if you have any questions!

[992manav]

.take

[github-actions[bot]]

The issue you are trying to assign to yourself is already assigned.

[taniandjerry]

Hello @TSP06! Just wanted to let you know that I have added detailed instructions to reflect the page all submitted blogs and videos will go to! See above updated instructions and the page here https://block.github.io/goose/community/

[Shreyanshsingh23]

.take

[github-actions[bot]]

The issue you are trying to assign to yourself is already assigned.

[taniandjerry]

Hi @Shreyanshsingh23 , I've gone ahead and assigned you this issue after reopening it. Given that this is the last week of Hacktoberfest, and there have been no updates on some issues, I am relaxing on the "don't claim multiple issues" part and allowing active contributors the chance to earn more points. Let me know if you have any questions!

[Shreyanshsingh23]

Thanks @taniandjerry for assigning, I will start working on this.

[Shreyanshsingh23]

Hey @taniandjerry, I have published the article on Medium and also raised a PR #5438 which closes this issue. Please review