Notes on Cookie and the projects built with it.
Most landing page projects lose their first weekend to setup: picking a framework, wiring up a build pipeline, arguing about a component library. Cookie skips that by keeping the whole stack to two things you already know, Jekyll and Tailwind CSS, with no build step beyond what’s already wired up.
A common point where teams outgrow a landing page theme is documentation. The marketing site is on one stack, the docs end up on another, GitBook, Mintlify, a separate Docusaurus deploy, and suddenly there are two build systems, two design languages, and two places for content to drift out of sync.
You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.