Point the docs at the Cookbook and invite people to post recipes - #223
Merged
Conversation
The Cookbook discussion category already holds three recipes, and nothing in the docs points there — so they only exist for people who happen to browse Discussions. Add a page that links the category, previews what's in it, and says how to contribute. The page lands in a new "Community" sidebar group rather than under Automation: two of the three current recipes are automation and one is keybinds, so the grouping that generalizes is who writes them, not what they're about.
thdxg
added
documentation
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
macterm | cdc766f | Commit Preview URL Branch Preview URL |
Aug 03 2026, 04:37 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Cookbook discussion category already holds three recipes, and nothing on the docs site points there. Adds
/docs/cookbook.Why
The recipes only exist for people who happen to browse Discussions — the docs never mention the category, so a reader following the sidebar has no way to learn it's there. That also cuts the other way: nowhere in the docs invites anyone to post a workflow, which is what a cookbook needs to grow past whatever the maintainer wrote.
What
New page —
website/docs/pages/90-cookbook.md, served at/docs/cookbook:discussions/new?category=cookbook, plus three guidelines aimed at recipes someone else can actually adopt — lead with what it gets you, include the whole config rather than a fragment, name the minimum version.One clause in the introduction so the page is reachable from
/docs/and not just the sidebar.The sidebar group is a judgment call
The page opens a new Community group rather than filing under Automation. Two of the three current recipes are automation and one is keybinds, so the axis that generalizes is who writes them, not what they cover — and it leaves somewhere obvious for future community-facing pages. Easy to move if you'd rather not add a group for one page.
Verified
bun run build:docsrenders 10 pages; sidebar shows Community → Cookbook active; page is insitemap.xml. Rendered at desktop and mobile — no console errors, no horizontal overflow, lists match existing pages (Tailwind preflight suppresses bullet markers site-wide; Command palette computes identically, so that's not new here). All ten external links return 200, and the extensionless/docs/cookbookresolves underwrangler dev— worth checking separately, since a plain static server can't serve those URLs.Follow-up, not in this PR
The "Three to start with" list is curated by hand, so it goes stale as outside recipes land. If that turns into a chore, the alternative is dropping the enumeration and letting the category page speak for itself.