Gift cards get a Digital PDF option
Printable gift cards had one export path: a fold-and-cut sheet with the back face printed upside down so it reads right side up once folded. That made sense on paper but broke anyone trying to save the card as a normal PDF, since the back page came out inverted with no fold to fix it. The gift card page now offers a Format choice next to the print button: Fold card keeps the original single-sheet layout for printing and folding by hand, and the new Digital PDF option lays the front and back out as two separate upright pages with a page break between them, so saving to PDF from the print dialog produces a clean two-page file in the right order.
488 words
Added a Fold card / Digital PDF format toggle to the gift card page.
Digital PDF mode renders front and back as two upright pages instead of a folded, upside-down sheet.
Portail v2.3.3 shipped on 2026-09-28 as a patch release focused on gift cards get a digital pdf option. Printable gift cards had one export path: a fold-and-cut sheet with the back face printed upside down so it reads right side up once folded. That made sense on paper but broke anyone trying to save the card as a normal PDF, since the back page came out inverted with no fold to fix it. The gift card page now offers a Format choice next to the print button: Fold card keeps the original single-sheet layout for printing and folding by hand, and the new Digital PDF option lays the front and back out as two separate upright pages with a page break between them, so saving to PDF from the print dialog produces a clean two-page file in the right order. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.
The main changes were direct: added a fold card / digital pdf format toggle to the gift card page, and digital pdf mode renders front and back as two upright pages instead of a folded, upside-down sheet. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.
This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.3.3 moved that contract forward in its own narrow lane.
The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.
The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.
Screenshots
