0.6.0: downloads, and filters you can see

Download a resume as PDF, DOCX or Markdown (#28)

Every published resume is now a file you can hand to someone, from a Download card on the candidate page:

/candidates/<slug>/resume.md      the stored document, untouched
/candidates/<slug>/resume.html    the page, standalone
/candidates/<slug>/resume.docx    pandoc, straight from the Markdown
/candidates/<slug>/resume.pdf     weasyprint, from the board's own HTML and CSS

The PDF goes through the styled HTML rather than through pandoc's own PDF writer, so the file and the web page stay the same document instead of two designs maintained separately. An uploaded original wins over a regenerated one: if somebody handed the board a PDF, asking for a PDF gives that back rather than a PDF rebuilt from a parse of it. The runtime image gains weasyprint; a browser would render it too and would add about 350MB for one button.

Subscribe to what is on the screen, not to its tags (#29)

The filter strip only ever knew about tags, so narrowing to remote work changed the results and appeared nowhere: no chip naming it, and, because the strip was gated on there being a tag, no Clear and no Subscribe either.

Now every active filter is a removable chip and Subscribe carries the whole query:

/?tags=javascript&workplace=remote  ->  Subscribe = /feed?workplace=remote&tags=javascript

/feed had parsed the full query since #26 and then described itself by its tags alone, so every narrowing of one tag advertised the same rel=self. Also here: a tag clicked on a result card kept the rest of the search instead of starting a new one, and /candidates stopped offering the everything-feed as its Subscribe link.

Follow employers and candidates, and post updates (#30)

Follows and updates, with one additive migration (0010_updates_and_follows.sql, all create … if not exists).

The stats tag is a script, and the policy lets it run (#33)

#31 added the CrawlProof tag as Next.js's <Script> component. This is a Hono app rendering server-side JSX, next is not a dependency, and import Script from "next/script" fails tsc, which fails the build, which fails the image. master was red from #31 until this landed.

The quieter half: fixing the import alone would have left script-src 'self' in place, so the browser would have dropped the script from crawlproof.com and said so only in a console nobody has open. The stats would have read as an audience of nobody rather than as a bug. Both halves are fixed, and a test now renders the layout and checks the policy permits the host the page loads from.

Full changelog: v0.5.0...v0.6.0