manifestations

the digital atelier — where it all starts. a personal workspace and reference, the ideas that grew with my needs, the dumps from my mind, the curated content i wished i had, the list of things that i care about, everything i cherished in one place. a living archive.

• kept the codebase lean and current for around 8 years now
• developed a personal design system, with responsive and native css workflows
• hand-crafted svg logos and favicons, every path and shape written from scratch
• integrated sveltekit with pocketbase for full-stack, server-side workflows
• experimented with git submodules — not the way to go
• maintained a monorepo with clean internal tooling and streamlined workflows
• evolved best practices for javascript and ts — later distilled into mauss
• evolved best practices for svelte and kit — later distilled into syv

filesystem-based content processor. shaped by a long-standing need to fully own and preserve my content, aubade treats your filesystem as a database. it recursively processes directories containing at least one markdown file, turning it and its sibling files into structured data.

• built a recursive file reader that transforms directories into structured JSON
• wrote a minimal, dependency-free YAML-like parser from scratch
• implemented safe, static metadata injection directly into markdown content
• designed a table of contents generator with nested, stable heading anchors
• wrote a transformer that links sibling entries in a sorted list
• explored static code highlighting with zero runtime cost
• no-build native JS with JSDoc is nice, but writing TS with strict inference is better

practical functions and reusable configurations. lightweight utilities for modern JavaScript and TypeScript with zero dependencies, designed for clarity and composability with minimal runtime footprint.

• finally cracked shared config: one install, one link, and it's good to go
• learned how to design functional utilities that stay pure and composable
• figured out clean patterns for making utilities SSR-safe by default
• explored tree-shakeability and how to enforce it through structure
• organized modules by concern, not by type — clarity over convention
• refined my taste for naming, defaults, and safe fallback behaviors

practical svelte components and utilities. lightweight, idiomatic building blocks with thoughtful APIs: not just reusable, but adaptable. each piece shaped by real needs and refined until it disappears into the flow of the app.

• designed intuitive submodules to keep the scope focused and scalable
• prioritized SSR-first and progressive enhancement from the start
• learned how to build components that feel native to Svelte, not bolted on
• built single-purpose drop-ins that quietly do everything they should
• shaped APIs to balance clean abstraction with hands-on control

opinionated formatting powered by Prettier. made to keep package.json files clean and consistent, it sorts top-level keys in the order that i think makes sense, and exposes a parser for package-like files with different names.

• learned how Prettier's plugin system works under the hood
• figured out how to support custom files without muddying user config
• felt the quiet joy of something that just works — and never thinking about it again

part of ignatiusmb/prettier-plugin-suite

my base stylesheet — a minimal, opinionated layer of typographic and layout defaults. a tiny css file that i reach for in every project for a clean and consistent styling. it's my reset and my design sense in single file.

• refined my baseline styles into something i could reuse everywhere
• learned how little css you actually need to feel at home in a new project

a personal starter template — download, unzip, and start building. it's the setup i reach for every time. it's got everything i need, and nothing i don't.

• trimmed setup scripts, config files, and folder structure down to the essentials