Publishing Your Recipes
The Cooklang Federation indexes recipes from community members' repositories and makes them searchable. You host your recipes wherever you want — GitHub, your own website, a blog — and the federation makes them discoverable.
You keep full control. Update, remove, or modify recipes anytime.
Publishing via GitHub
The simplest approach. Put your .cook files in a public GitHub repository:
Then add your repository to the federation:
- Fork the federation repository
- Edit
config/feeds.yamland add your entry underfeeds::
- Submit a pull request
Once merged, the crawler indexes your recipes automatically and checks for updates periodically.
Publishing via RSS/Atom Feed
For blog-based sharing, create an Atom feed pointing to your .cook files:
Host both the feed and your .cook files, then add the feed URL to config/feeds.yaml with feed_type: web.
Publishing with Static Site Generators
If you run a Hugo, Jekyll, or similar site, you can serve recipes as HTML pages while keeping raw .cook files available for the federation.
Workflow
- Keep
.cooksource files in a dedicated directory - Export to Markdown for your site with CookCLI
- Copy raw
.cookfiles to your static directory for federation access
Automate with GitHub Actions
Recipe Metadata
Include metadata in your .cook files to improve discoverability:
Updating and Removing Recipes
GitHub: Edit your .cook files, commit, and push. The federation picks up changes on the next crawl.
RSS/Atom: Update your .cook files and the <updated> timestamp in your feed.
Leaving the federation: Remove your entry from feeds.yaml via pull request, or make your repository private.
See Also
- Recipe Discovery — how users find your recipes
- Federation Repository — submit your feed
- Creating Cookbooks — turn recipes into a PDF cookbook