Paper Menus Beat Passing a Phone

Every menu this site generates is built to be printed: actual paper, styled like something a waiter would hand you, listing the night's games as courses.

That sounds like a gimmick until you host with one. Whoever's holding the phone ends up steering the conversation, and everyone else waits their turn to look. Paper on the table has no owner: everyone reads it at once, points at things, and argues productively. It also makes the night feel planned, even if you generated it four minutes before the doorbell.

Generate a menu, hit print in your browser, and what comes out isn't a screenshot of the webpage. The header, the navigation links, the reroll and lock buttons, the whole generate form — all of it is written to disappear specifically when a printer is the target, so what's left is just the three courses, laid out for paper rather than shrunk to fit it. The date gets added in, since that's useful on paper and pointless on a screen you're looking at right now. Box art and thumbnails drop out too, on purpose: a restaurant menu doesn't run photos of the food, and a page of small blurry cover images would look more like a shopping list than a menu anyway. What's left is just the game names, the courses they belong to, and the details that actually help you decide, printed at a size meant to be read from across a table, not squinted at.

On the page, each course gets its own header and a one-line description above the picks: First Course under "Light," Main Course under "Medium," Chef's Special under "Heavy" (more on why the night is split into exactly those three bands, elsewhere). That phrasing is deliberate, written to read the way an actual restaurant menu reads, so what comes out of the printer looks like something a server would hand you, not a printed webpage with the buttons still stuck to it. If somebody vetoes a pick after the page is already printed, reroll it and print again. It costs a sheet of paper, and the new menu replaces the old one at the table the same way changing your order replaces what the kitchen was about to cook.

The layout defaults to a standard letter page, so it comes out of pretty much any home or office printer without fighting your browser's print settings. If nothing's plugged in, or you'd rather send it than pin it up, use "save as PDF" in the same print dialog instead of an actual printer. It's the identical layout, just as a file, and a PDF is easier to drop into a group chat than a phone photo of a piece of paper.

Some hosts skip the table entirely and tape the menu to the door or the fridge instead, so people see the three courses on the way in rather than after they've already sat down and started negotiating anyway.

A shared note or doc solves the ownership problem too, technically, but it still needs a device pointed at it, and that device is doing seventeen other things in the hour before the game starts. Paper doesn't buzz with a text mid-negotiation, doesn't need someone to unlock it, and doesn't get borrowed to look up a rule once the game's underway. It just sits there on the table, doing the one job.

Printing also solves a smaller problem: the awkwardness of a game night that clearly wasn't planned. A stack of boxes pulled off a shelf ten minutes before the doorbell reads as improvised, even when the game choices are good. A menu sitting on the table when people walk in reads as intentional, whether or not that's actually true. Nobody needs to know it took four minutes.

If you host a recurring game night, keep the old menus. A stack of them turns into a surprisingly good record of what your group actually played all year, and it settles at least one annual argument about who picked the game nobody liked. It also means that by December you have a paper trail of every "we should play this again sometime" that never happened, which is either useful or depressing depending on the group. Either way, it's a better record than trying to remember which Tuesday you finally got Gloomhaven back on the table.