4 ms·
SvelteKit using the static adapter to render everything to static HTML - except a few islands of with dynamic components like for the image gallery - and MDsvex
by akiselev 2y ago
SvelteKit using the static adapter to render everything to static HTML - except a few islands of with dynamic components like for the image gallery - and MDsvex to convert markdown to Svelte components with some extra remark plugins to simplify crosslinking, Tailwind for the CSS with some design copied from the excellent TailwindUI, Github Actions to push the static pages to GitHub Pages, and a CNAME on my domain pointing at the Pages URL. I have an Ink.js TUI utility to manage some bits of the blog like optimize static assets, update metadata or un/publish a post, etc.
For search I just generate a JSON file with all my posts and use Fuse.js to search against it locally in the browser.
- tnolet 2y agowhat do you like about Svelte in this case?
- akiselev 2y agoI want to include interactive visualizations and other custom JS components in blog posts. I've worked with React and Svelte extensively as a frontend dev in the past so SvelteKit was the easy choice (much lighter weight than Next, et al). It's familiarity more than anything. I've gotten around to starting a personal blog several times and abandoned each attempt because I found the blog generators like Hugo and Jekyll hard to customize. Just doing it as a static SvelteKit site eliminated all of the problems at the expensive of a few hours setting up the tech stack. This allowed me to focus on the HTML when I wanted to style the site, markdown when I wanted to write, and Svelte when I add interactive components.