contentWhy Content Collections Beat Hardcoded Pages
Hardcoded pages are fast to start and slow to maintain. Content collections keep layout and copy separate without adding a CMS on day one.
Read Article →Engineering Blog
NOTES ON SVELTEKIT
Practical posts on SvelteKit, content collections, SEO, and building content-driven sites without a page builder.
Articles
content
sveltekitSvelteKit Routing Without Surprises
File-based routing is simple until nested layouts and dynamic params get involved. A short guide to keeping routes readable.
Read Article →
contentMarkdown Collections With mdsvex and Without
mdsvex renders Markdown as Svelte components. Sometimes you just need HTML. Here is when each approach fits.
Read Article →
seoSEO Meta From Frontmatter, Not Copy-Paste
Title, description, canonical, Open Graph, and Twitter card tags can come from page data. Here is a small pattern that scales.
Read Article →
contentDecap CMS on Top of SvelteKit Collections
Decap CMS can edit JSON and Markdown collections in a SvelteKit repo. A short overview of how the mapping works.
Read Article →
sveltekitStatic Pages From Markdown Without a Route per Page
One dynamic route can render many static pages. A pattern for legal pages, docs, and anything that shares a layout.
Read Article →