Rikketik
Industrial portfolio platform built in SvelteKit: project pages, technical writing, strong visual identity, and a self-hosted static deployment shape that stays honest about its current state.
About This Project
Rikketik has moved beyond a placeholder front page. The current repo shows a real public platform with a proper projects index, detailed project pages, markdown-driven technical writing, an about surface, and a visual identity that holds together across the whole site.
The honest read is not brochure fiction. This is still an evolving platform, but it already behaves like a serious shipped surface: static-first SvelteKit build, structured content, feed and sitemap output, and a deployment path that suits self-hosted infrastructure instead of depending on rented mystery boxes.
Current Highlights
- Public project yard with proper detail pages instead of throwaway teaser cards
- Markdown/mdsvex publishing flow for technical writeups, case-study style pages, RSS, sitemap, and structured content output
- Industrial visual identity with strong typography, operator profile framing, layered backgrounds, and consistent reusable components
- Static-first deployment path via prerendered SvelteKit output, Docker/Nginx serving, and self-hosted infra friendliness
- Evolving live platform that stays honest about what is already shipped versus what is still being sharpened
- Built as a durable front door for the wider Rikketik yard rather than a disposable portfolio theme
Current State
Right now this project reads like a real site, not a dressed-up placeholder. The public side has enough shape to stand on its own: homepage, about page, blog index and post routes, projects index and detail routes, plus the supporting SEO and feed plumbing that make it behave like a serious shipped surface.
It is still evolving, and that honesty matters. The platform already has a solid public skeleton and a distinct identity, but it is still being tightened and extended in the open instead of pretending to be finished brochureware.
Public Platform
- Featured projects, project detail pages, and technical writeups all live inside one consistent visual system
- Profile framing, background context, and site-wide metadata are already wired into the public front end
- Content is compile-time loaded and prerendered instead of bolted onto a runtime CMS
- The site keeps the tone direct and inspectable instead of hiding behind empty product-language theatre
Build and Deployment Shape
The infrastructure story is grounded. The site builds to static output, ships with Docker and nginx config, and fits neatly into self-hosted deployment lanes without needing a permanent Node runtime in production.
That matters because Rikketik is meant to reflect the same values as the work around it: control, inspectable outputs, and infrastructure that belongs to the operator.