notes & write-ups

blog

notes and write-ups on what i'm building and learning.

rebuilding this site as plain static files

this site used to be a single-page app with a router, a component tree and a build step. it now ships as seven hand-written HTML files, one stylesheet and one small script — no framework, no bundler, no server.

the trade is deliberate: a page load is a document, navigation is a link, and every view keeps working even if JavaScript fails. the only runtime behaviour left is the handful of things that genuinely need it.

what stayed dynamic

  • Discord presence, pulled from Lanyard and refreshed every minute.
  • The project carousel and its detail panel.
  • Copy buttons on contact, and the Telegram profile dialog.

everything else — the blurred backdrop, the floating nav, the stack grid, the page transitions — is CSS. no hydration, no client routing, no layout shift.

discord presence without a backend

the profile row on the home page is not a screenshot. it reads my real Discord status, avatar, custom status and current track, which usually means a bot token, a websocket and something always running.

instead the page asks api.lanyard.rest for my user id. Lanyard keeps the gateway connection open on its side and exposes a JSON snapshot with permissive CORS, so a static page can read it directly. one fetch, one render, one interval.

the catch is that the account has to be in the Lanyard server, and the response is only as fresh as its cache. for a personal site both are fine — the failure mode is a quiet "status unavailable", not a broken page.