尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 README ↗Choose your tap date. Tap Planner works backward and tells you when to begin.
Pinter tells you how long a BrewPack takes. It doesn't tell you when to start if you want it ready for a particular day. Tap Planner does that arithmetic (fermentation, an optional cold crash, and conditioning, counted backward from your tap date) and then gets out of the way.
No accounts, no database, nothing stored. Every calculation happens in your browser.
| Page | Use it when | |
|---|---|---|
| 🍺 | BrewPack planner at / | You're brewing an official pack and want its recommended or minimum timing |
| 🧪 | Custom planner at /custom | You're brewing your own recipe, or overriding a pack's timing |
| 🔄 | Multi-Pinter planner at /rotation | You run several Pinters and want a beer and ready date for each, then one calendar file |
| 📅 | Release timeline at /releases | You want to know when a pack appeared, or when a seasonal might return |
| 🏷️ | Brew labels at /labels | You want to know what's actually in the fridge |
| 📖 | Brewing schedule at /schedule | You want every pack's timing at a glance, or a PDF to hand to someone |
A catalogue of every BrewPack: its photo, style, ABV, recommended brewing and conditioning days, total days, and Pinter's minimums. It is meant for people who don't use the app at all.
| Get it as | Link |
|---|---|
| PDF, nine pages, US Letter | tap-planner.vercel.app/schedule/pdf |
| CSV, for a spreadsheet | tap-planner.vercel.app/schedule/csv |
| Web page, with search, filters and sorting | tap-planner.vercel.app/schedule |
The PDF is built like a small book. Page 1 is a cover with a clickable contents list, page 2 is a one-page quick reference of every pack, and the rest are sections by beer family: IPAs and Pale Ales, Lagers and Pilsners, Stouts and Dark Beers, Wheat, Belgian and Sour, and Ciders and Seltzers. Discontinued and unavailable packs get a section of their own at the end. Your PDF viewer's bookmark panel lists the sections, every page is numbered, and the text is searchable.
The links never change. When the catalog updates, the same addresses serve the new file, so share them freely.
The schedule catalogue was Jack Paul's idea, and it grew from the original schedule document he created.
Pick a pack, pick the day you want to pour, and Tap Planner counts backward:
(brewing or fermentation) + cold crash + conditioning = total lead time
For a 24 December tap date with 5 brewing days and 7 conditioning days, it tells you to start on 12 December, and shows every stage in between.
You can switch between recommended and minimum timing, add 1 to 3 days of cold crash, and it will tell you plainly when a date isn't achievable rather than quietly producing a schedule that starts in the past.
Add schedule to calendar downloads a standard .ics file with each stage
as an all-day event spanning its real date range. It is generated in your
browser. Tap Planner never asks for calendar access and adds nothing
automatically.
Print a business-card-size label for each brew: name, style, ABV, brew and tap dates, batch number, tasting notes.
Save the card instead as a PNG at 300dpi or an SVG, which stays sharp at any size. Both are built in the browser from the card on screen.
Any paper works, but a fridge is cold, humid, and prone to condensation.
| Paper | Verdict |
|---|---|
| Waterproof synthetic (vinyl, polypropylene) | Best: immune to condensation |
| Matte photo paper, RC-coated | Great: resists moisture, still writable |
| Cardstock, 65 to 110lb | Good: stiff and cheap, softens if it gets damp |
| Plain printer paper | Works: goes wrinkly in a few days |
Two things matter more than the paper:
A strip of clear packing tape over the front laminates any card for about a cent.
Pinter has never published release dates, so these are estimates worked out from timestamps on the online store. Treat it as trivia and a rough guide to when seasonals reappear, not a source of truth. Anything marked Approx. is month-only on purpose, because a pack that goes away and comes back has its store date overwritten by the return.
The density strip plots one mark per release event by month, so launch waves and quiet stretches are visible as shape. A filled tick is a launch, an open ring is a pack coming back; hover either and the pair links up.
Every pack in the catalog is shown with Pinter's own product photography:
Where a photo isn't available (a custom recipe, or a pack that leaves the store before it is ever captured), Tap Planner generates a label design from the beer style instead, so a card never comes out blank. Colour comes from the style and the motif from its family: hops for the IPAs, grain for the lagers, roasted beans for the stouts.
Images are stored locally and served from this app. Nothing is hotlinked, and nothing is fetched from Pinter at runtime.
Scheduled workflows check Pinter's public BrewPack listing, validate the catalog, rebuild the release timeline, regenerate the brewing schedule PDF and CSV, run lint and a production build, and open a pull request.
Changes merge themselves, with guard rails. After a workflow validates a change, the pull request merges automatically once the required check passes. Anything that touches files outside the catalog data and pack shots, removes a file, drops more than three packs, or rewrites a large amount of data is held open instead, and the owner is notified.
Tap Planner is an independent community project. It is not affiliated with, endorsed by, or sponsored by Pinter. "Pinter", BrewPack names, and all official product images and artwork are the property of their respective owners, and are used here only to identify the pack you are brewing.
Use Tap Planner for planning. Continue using the official Pinter app for brewing instructions, safety guidance, product support, and decisions during your brew.
Developer documentation: setup, project structure, the BrewPack pipeline, the image policy, and deployment.
Built for better brew planning. 🍻