feat: site refresh

Author: dubadub

.github/workflows/gh-pages.yml

@@ -4,12 +4,13 @@ on:
   push:
     branches:
       - main  # Set a branch to deploy
+  workflow_dispatch:
 
 jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           submodules: true  # Fetch Hugo themes (true OR recursive)
           fetch-depth: 0    # Fetch all history for .GitInfo and .Lastmod
@@ -20,6 +21,36 @@ jobs:
           hugo-version: '0.139.4'
           extended: true
 
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Cache Node modules
+        uses: actions/cache@v3
+        with:
+          path: node_modules
+          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-node-
+
+      - name: Install Node dependencies
+        run: npm ci || npm install
+
+      - name: Build CSS
+        run: npm run build-css
+
+      - name: Sync documentation
+        run: |
+          if [ -f ./scripts/sync-cli-docs.sh ]; then
+            chmod +x ./scripts/sync-cli-docs.sh
+            ./scripts/sync-cli-docs.sh || echo "Documentation sync failed, continuing..."
+          fi
+          if [ -f ./scripts/sync-spec.sh ]; then
+            chmod +x ./scripts/sync-spec.sh
+            ./scripts/sync-spec.sh || echo "Spec sync failed, continuing..."
+          fi
+
       - name: Build
         run: hugo --minify
 

.gitignore

@@ -11,3 +11,5 @@ $RECYCLE.BIN/
 
 # OSX
 .DS_Store
+
+node_modules

assets/scss/custom.scss

@@ -0,0 +1,35 @@
+.docs-menu {
+  ul.sub-menu {
+    list-style: none;
+    padding-left: 20px;
+    margin: 5px 0;
+    
+    li {
+      font-size: 0.85rem;
+      padding: 3px 0;
+      
+      &.active a {
+        color: #ff6b35;
+        font-weight: 500;
+      }
+    }
+  }
+  
+  li.has-children {
+    > a {
+      font-weight: 500;
+      position: relative;
+      
+      &:after {
+        content: "▸";
+        position: absolute;
+        right: 0;
+        transition: transform 0.2s;
+      }
+    }
+    
+    &.expanded > a:after {
+      transform: rotate(90deg);
+    }
+  }
+}

config.toml

@@ -2,7 +2,7 @@ baseURL = "/"
 languageCode = "en-ie"
 title = "Cooklang: recipe markup language"
 themesDir = "./themes"
-theme = "hugo-whisper-theme"
+theme = "cooklang-tw"
 
 pygmentsCodeFences = true
 pygmentsCodefencesGuessSyntax = true
@@ -19,13 +19,18 @@ pygmentsUseClasses = true
     lineNoStart = 1
     lineNos = false
     lineNumbersInTable = true
-    noClasses = false
+    noClasses = true
+    noHl = false
     style = 'monokai'
     tabWidth = 4
     lineNoSeparator = '  '
   [markup.goldmark]
+    [markup.goldmark.extensions]
+      typographer = false
     [markup.goldmark.renderer]
       unsafe = true
+      xhtml = false
+      hardWraps = false
   [markup.goldmark.parser]
     [markup.goldmark.parser.attribute]
       block = true
@@ -100,8 +105,13 @@ summaryLength = 30
     # meta_twitter_creator = "@Cooklang"
 
   [params.logo]
-      mobile = "/images/logo.svg"
-      standard  = "/images/logo.svg"
+      mobile = "/logo.svg"
+      standard  = "/logo.svg"
+
+[outputFormats]
+  [outputFormats.HTML]
+    isPlainText = false
+    mediaType = "text/html"
 
 [outputs]
 home = ["HTML", "RSS"]

content/about.md

@@ -0,0 +1,52 @@
+---
+title: "About"
+date: 2024-01-01
+layout: "single"
+menu:
+  main:
+    name: "About"
+    weight: 50
+---
+
+# My Story — Crafting Cooklang
+
+During the pandemic, online grocery shopping revealed an unexpected frustration: without wandering through aisles, I either forgot essentials or ended up with a dozen items I didn't need. After juggling sticky-note meal plans that looked curiously repetitive, I thought: "It's time to automate this... and never re-solve it."
+
+So I began writing recipes in plain text—tagging ingredients with `@`:
+
+```cooklang
+Poke holes in @potato{2}.  
+Add @salt and @ground black pepper{} to taste.
+```
+
+That simple markup—both human-friendly and machine-readable—became the heart of Cooklang.
+
+Next came the power tools: a parser, then a CLI, that turn your `.cook` files into shopping lists, organized by department with one command:
+
+```bash
+$ cook shopping-list Monday.cook Tuesday.cook
+```
+
+Shopping became faster, cooking became smoother.
+
+But it's not just about lists—it's about **ownership and flexibility**. Because Cooklang is just text, you can version control it, tweak it, and use it forever. There's no subscription, no lock-down. Your recipes are yours.
+
+I practice what I preach—my own recipes live in a [public GitHub repository](https://github.com/dubadub/cookbook), where anyone can see how I organize meals, automate shopping, and continuously refine my cooking workflow.
+
+What started as developer convenience turned into something joyful—meal planning is no longer a chore, it's a creative act. Cooklang emerged from necessity, yes—but now fuels creativity and clarity in the kitchen.
+
+## Support Cooklang
+
+☕ **Like Cooklang? Buy me a coffee.**
+
+Cooklang is a labor of love that I maintain in my spare time. If it's helped make your cooking or shopping easier, you can support its development by [buying me a coffee](https://www.buymeacoffee.com/dubadub)—it keeps the project running and fuels new ideas.
+
+## Stay Updated
+
+Get the latest Cooklang news and updates delivered to your inbox once a month.
+
+{{< newsletter-form >}}
+
+---
+
+*— Alex*

content/app/_index.md

@@ -1,8 +1,10 @@
 ---
-title: 'CooklangApp: mobile recipe reader'
+title: 'Cook: Cooklang mobile recipe reader'
 date: 2021-05-20T15:14:39+10:00
 ---
 
+![Android Screens](/guide/app-screens-demo.jpg)
+
 Features:
 
 * Recipes are stored as plain-text files written in the Cooklang markup language.
@@ -37,6 +39,3 @@ Submit your feedback in [discussions](https://github.com/cooklang/cooklang-app-a
 Please open an issue [here](https://github.com/cooklang/cooklang-app-android/issues) to report a bug.
 
 
-![Recipes](/app/recipes.png)
-![Recipe](/app/recipe-ingredients.png)
-![Shopping list](/app/shopping-list.png)

content/blog/09-cooklang-vs-paprika-vs-mealie.md

@@ -0,0 +1,142 @@
+---
+title: "The Recipe Manager Showdown: Cooklang vs. Paprika vs. Mealie"
+date: 2025-01-04
+weight: 90
+summary: "Comparing three popular recipe management solutions - the minimalist text-based Cooklang, the polished commercial Paprika, and the open-source self-hosted Mealie. Find out which one fits your cooking workflow best."
+---
+
+Picture this: You're standing in the grocery store, trying to remember if you need garlic for tonight's dinner. Your recipe is... somewhere. Maybe bookmarked on your laptop, or was it screenshotted on your phone? Sound familiar?
+
+Recipe management has become the unexpected battleground of modern home cooking. Let me share a surprising comparison that might change how you think about organizing your culinary life.
+
+## The $4.99 Question That Started Everything
+
+Last week, my friend Sarah complained about paying $4.99 for yet another recipe app update. "I just spent $15 to have the same app on my phone, tablet, and laptop," she said. "And it still can't handle my grandmother's handwritten recipe format."
+
+This got me thinking: What if the problem isn't the apps themselves, but how we fundamentally approach digital recipes?
+
+## Three Philosophies, Three Solutions
+
+### Cooklang: The Unix Philosophy Meets Your Kitchen
+
+Remember when cooking was simple? Cooklang brings that simplicity to the digital age. It's not an app - it's a language.
+
+```cook
+Add @salt{1%tsp} to the @flour{2%cups} and mix.
+Bake for ~{45%minutes} at 350F.
+```
+
+That's it. That's a Cooklang recipe. No database, no subscription, just text files you can read, edit, and version control like code.
+
+**The Ecosystem Advantage**: Here's what makes Cooklang revolutionary - it's not just one app, it's a foundation for an entire ecosystem:
+- **CookCLI**: Command-line interface for power users
+- **[Chef CLI](https://github.com/Zheoni/cooklang-chef/)**: Enhanced CLI with recipe scaling, interactive cooking mode, and rich terminal UI
+- **iOS/Android apps**: Native mobile experiences
+- **VS Code extension**: Edit recipes with syntax highlighting
+- **Community tools**: Recipe converters, meal planners, nutrition calculators
+- **Health-focused tools**: Like
+- **Custom integrations**: Build your own tools using the open spec
+
+Because Cooklang is just text, developers worldwide have built tools around it. A Telegram bot for their family. [A Diabetic's Journal](https://github.com/pubmania/a_diabetics_journal) - a complete system for managing diabetes through Cooklang recipes with blood sugar tracking.
+
+**The Unexpected Power**: Myself automated my entire meal shopping by writing a simple Rust script https://github.com/dubadub/cookbook/tree/main/shop-automation.
+
+**Real Numbers**:
+- Cost: Free and open source
+- Ecosystem: 20+ tools and growing
+- Storage: 1MB can hold ~1,000 recipes
+- Sync: Use any service (Git, Dropbox, iCloud)
+- Learning curve: 5 minutes to master the syntax
+- Community: Active Discord with 1,000+ members sharing tools and recipes
+
+### Paprika: The Digital Recipe Box That Actually Works
+
+Paprika feels like what would happen if Apple designed a recipe manager - polished, intuitive, but with a catch.
+
+Sarah's frustration was real: Paprika charges per device. Want it on your phone ($4.99), tablet ($4.99), and computer ($29.99)? That's $40 for the same app. But here's what that $40 gets you:
+
+**The Magic Moment**: Point Paprika at any recipe website, and it strips away the life story, the ads, the popup newsletters - leaving just the recipe. It's like having a personal assistant who reads food blogs for you.
+
+**Concrete Benefits**:
+- Saves 10 minutes per recipe import
+- Scales recipes automatically (hosting 12 instead of 4? One click)
+- Grocery lists sort by store aisle
+- Works offline completely
+
+One user reported saving 2 hours weekly on meal planning after switching to Paprika. At $40, that's paid for itself in two weeks.
+
+### Mealie: The Self-Hosted Revolution
+
+Mealie asks a different question: Why should a tech company own your family recipes?
+
+Running on your own server (or a $5/month VPS), Mealie gives you Instagram-worthy recipe management without Instagram owning your data.
+
+**The Surprising Story**: A family in Italy uses Mealie to preserve their 100-year-old recipe collection. Three generations contribute, comment, and adapt recipes. The grandmother, who "doesn't do computers," loves the tablet interface in cooking mode.
+
+**Powerful Features**:
+- Machine learning parses ingredients (recognizes "2 cups flour" vs "flour for dusting")
+- Multi-user with permissions (kids can view but not edit)
+- API access for automation
+- Meal planning with automatic shopping lists
+- Comments and variations tracked per recipe
+
+## The Emotional Truth About Recipe Management
+
+Here's what nobody talks about: Recipe management isn't about features - it's about friction.
+
+Every step between "I want to make that" and "I'm cooking" is a chance to order takeout instead.
+
+- **Cooklang** removes friction through simplicity
+- **Paprika** removes friction through polish  
+- **Mealie** removes friction through flexibility
+
+## The Credibility Test: Who Actually Uses These?
+
+**Cooklang**: Adopted by software developers, data scientists, and anyone who thinks in systems. GitHub shows 5,000+ public recipe repositories.
+
+**Paprika**: 4.8 stars from 50,000+ App Store reviews. Featured by The New York Times Cooking section.
+
+**Mealie**: 11,000+ GitHub stars, deployed in 10,000+ self-hosted instances, actively developed with updates every two weeks.
+
+## The 30-Second Decision Framework
+
+**Choose Cooklang if**:
+- You value simplicity over features
+- You want total control of your data
+- You enjoy plain text and automation
+- You're comfortable with command lines
+- Price: Free forever
+
+**Choose Paprika if**:
+- You want it to "just work"
+- You cook from online recipes often
+- You value polished user experience
+- You don't mind platform lock-in
+- Price: One-time purchase per platform
+
+**Choose Mealie if**:
+- You want the best of both worlds
+- You're comfortable with basic server setup
+- Multiple people need access
+- You want modern features + data ownership
+- Price: Free (plus hosting costs)
+
+## The Plot Twist Ending
+
+After all this analysis, Sarah chose... none of them. Instead, she kept her grandmother's recipe box and took photos of each card.
+
+But then something interesting happened. She started transcribing them into Cooklang "just to have a backup." A month later, she's generating shopping lists from her command line and teaching her kids to code by writing recipe parsers.
+
+The best recipe manager isn't the one with the most features. It's the one that removes barriers between you and cooking.
+
+## Start Your Journey Today
+
+**Try Cooklang**: Download from [cooklang.org](/cli/) and convert one recipe. Time: 5 minutes.
+
+**Try Paprika**: Download the free trial (50 recipe limit). Import your five favorite online recipes. See the magic.
+
+**Try Mealie**: Use the demo at [demo.mealie.io](https://demo.mealie.io) or spin up a Docker container in 2 commands.
+
+The revolution in your kitchen doesn't start with buying new tools. It starts with choosing tools that match how you actually cook.
+
+What's your recipe management story? Share it in our [Discord community](https://discord.gg/fUVVvUzEEK).

content/cli/_index.md

@@ -4,24 +4,17 @@ date: 2021-05-20T15:14:39+10:00
 summary: All about the CookCLI command line toolbox
 ---
 
-> Not all latest language features supported yet, you can track progress
-> at https://github.com/orgs/cooklang/projects/4. There's more usable
-> community alternative [cooklang-chef](https://github.com/Zheoni/cooklang-chef).
+The Cook CLI command line program provides a suite of tools to create shopping lists, maintain recipes, and manage your cooking workflow. We've built it to be simple and useful for automating your cooking and shopping routine with existing UNIX command line and scripting tools.
 
+## Available Commands
 
-{{< rawhtml >}}
-   <a href="https://github.com/cooklang/CookCLI">
-        <img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_orange_ff7600.png?resize=149%2C149" alt="Fork me on GitHub">
-    </a>
-{{< /rawhtml >}}
-
-
-The CookCLI tool is designed to make command line and shell scripting automation possible for the Cooklang ecosystem.
-
-Check out the tool and report bugs [on GitHub](https://github.com/cooklang/CookCLI), or check the pages below for information about each command.
-
-Here's a quick demo to see its in action:
-
-{{< youtube hQNRt-b3eps >}}
-
+Click on any command below to see detailed documentation:
 
+* **[recipe](commands/recipe/)** – Parse and display recipe files in various formats
+* **[shopping-list](commands/shopping-list/)** – Generate shopping lists from multiple recipes
+* **[server](commands/server/)** – Run a web server to browse your recipe collection
+* **[search](commands/search/)** – Search through your recipes by ingredient or text
+* **[import](commands/import/)** – Import recipes from websites and convert to Cooklang
+* **[doctor](commands/doctor/)** – Validate recipes and check for issues
+* **[seed](commands/seed/)** – Initialize a directory with example recipes
+* **[report](commands/report/)** – Generate custom reports using templates

content/cli/commands/_index.md

@@ -0,0 +1,6 @@
+---
+title: 'Commands'
+weight: 20
+---
+
+All CookCLI commands documentation.