The blog where you’re reading this
If you're reading this post, you're reading the feature that shipped today. A first-party editorial surface at /blog, four categories (devlog, guides, reviews,
If you're reading this post, you're reading the feature that shipped today. A first-party editorial surface at /blog, four categories (devlog, guides, reviews, industry), markdown posts rendered server-side with marked, a magazine-inspired layout with per-category accent colours, per-post BlogPosting + BreadcrumbList JSON-LD, a proper RSS 2.0 feed at /blog/rss.xml, and a sitemap entry so Google can find every post. The admin form has a live markdown preview, so what you type is what ships. Publishing stamps the timestamp on the first publish; un-publishing preserves the original date so re-publishing doesn't churn RSS readers or Google's indexation memory.
The ulterior motive: every catalogue section on the site is an auto-generated signal from the data, New on PornBoxd, Studio Spotlight, Freshly Reviewed. Good, but all of them derived. There was no first-party voice on the site. A blog is where a one-person project gets to sound like a person. It's also where long-form SEO content (studio retrospectives, VR guides, JAV glossaries) will live when there's time to write them, and where guides + reviews + industry notes can stack up into their own archive over time.
After shipping the blog, I did the only-slightly-strange thing of using it to document its own creation. Every day of work since the repo opened on 2026-04-07, the phase-one skeleton, the first real import, the SEO "Loading..." embarrassment, the scraper-date dead-end, the JAV launch, got a retroactive devlog dated to the day the work actually happened. Eight entries before this one. The archive doesn't start empty; it starts honest. If you're here on day one of the public blog, welcome, scroll down.