CookLang and the tools we’ve built to use it, you can:

• simplify your personal recipe management;
• streamline your shopping routine;
• make cooking more fun.

Here’s how the CookLang ecosystem makes that happen:

• All recipes are human-readable text files.
• Everything is a file. No databases. And you have complete control over your information.
• All the tools are simple, focused, and efficient; the UNIX way.

Getting Started

Create a recipe file, where each line is a step in the recipe. Tag your ingredients with @ and {}, then save your file. For a complete reference on CookLang, see the language specification page.

Install a recipe viewer. We support a few tools for viewing CookLang recipes:

• The CookCLI program for Mac and Linux provides a webserver for presenting your recipes, viewable with any web browser.
• The iOS app for iPad and iPhone allows you to read your recipe files directly from iCloud.

Cook something! Open a recipe on your viewer of choice, whip out the ingredients, and make something tasty.

CookCLI

The Cook CLI command line program provides a suite of tools to create shopping lists and maintain recipes. We’ve built it to be simple and useful for automating your cooking and shopping routine with existing UNIX command line and scripting tools. It can also function as a webserver for your recipes, making them browsable on any device with a web browser.

Add sample recipes:

$ cook seed
$ tree .
.
├── Baked Potato Soup.cook
...
├── Neapolitan Pizza.cook
...
├── README.md
├── Root Vegetable Tray Bake.cook
...
└── config
    └── aisle.conf

3 directories, 15 files

Check “Neapolitan Pizza”: