max / makenotwork

Describe the project page, and the last hand-written feed link is gone `/p/{slug}` is a described document. `templates/pages/project.html` and `ProjectTemplate` are gone, the route stays the axum handler it was, and with it the third and last `<link rel="alternate">` this server wrote by hand: every feed the site publishes is now said by a screen and spelled by `FeedKind`. Four behaviours the vocabulary took over, and two scripts deleted with them: - The section tabs are a `TabGroup` whose children carry a label, so the strip and the switching are the renderer's. `page-project.js` is gone. - The gallery goes through `quasi::widgets::carousel::region`, the described half of the widget the Askama macro already called, so the storefront and the three templates still calling that macro cannot be two carousels. - The tip offer's disclosure is `Slot::showing_at_most_one`. - The share link is `Act::copies`. Three things did not survive. The grid/list toggle: two view copies of one set with the choice in localStorage, where the list copy carried strictly less than the grid copy, so what it offered was one full view and one lossy one. There is no member for how densely a list is drawn and there should not be. `.follow-btn.is-selected`, for the reason the profile lost it. And the promo code's `<details>`, because a `Reveal` names its control by name and every tier card would have named the same one. Two places stay markup and the module header says why. The section bodies have been through `render_creator_markdown` -- media paths rewritten against the CDN under the creator's id, off-platform media stripped, video files turned into `<video>` -- none of which is derivable from the source, so handing quasi the source would drop three transforms silently. The report dialogue is a control opening a dialogue, which `RegionKind::Modal` is not; it is now `ReportModalTemplate` over the file `pages/item.html` still includes, so there is one copy of the markup and two callers. `helpers::redirect_to` is new. A described form is an htmx post, and both Stripe checkout handlers end at a 303 the browser follows inside the XHR, leaving htmx to swap a cross-origin fetch into the control that sent it. That is the failure `c7b0d3c1` hit on the header's Log Out, and this is `logout_handler`'s pair spelled once for the three sites the conversion made. Claiming a free item says the surface is stale rather than answering into a region: the row it was pressed in is not a region, and the item is owned now, so a reload leaves a card offering the library instead of a status line stuck in a card that still says Add.