Add blog posts
This commit is contained in:
1 parent
fbc314b535
commit
255b8fb7f2
3 files changed
+62
-1
No files matched your search
@@ -25,5 +25,4 @@ vite.config.ts.timestamp-*
|
|||||||
bun.lock
|
bun.lock
|
||||||
Update.md
|
Update.md
|
||||||
PROJECT.md
|
PROJECT.md
|
||||||
content/blog/
|
|
||||||
blogs/
|
blogs/
|
||||||
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
title: Building a Native Blog Into My Site
|
||||||
|
author: Sir Blob
|
||||||
|
date: 2026-07-19
|
||||||
|
tags: meta, svelte, sveltekit
|
||||||
|
excerpt: Why I ripped out the old blog redirect and wrote a small markdown blog engine instead.
|
||||||
|
---
|
||||||
|
|
||||||
|
For a while, clicking Blog in the navbar just sent you off to a separate site. It worked, but it never felt like *part* of this project.
|
||||||
|
|
||||||
|
## Why bother
|
||||||
|
|
||||||
|
A few reasons pushed me to build this in:
|
||||||
|
|
||||||
|
- One theme, one codebase, one deploy
|
||||||
|
- Full control over the reading experience
|
||||||
|
- An excuse to write a tiny markdown renderer from scratch
|
||||||
|
|
||||||
|
## How it works
|
||||||
|
|
||||||
|
Every post is a plain markdown file that lives in the `blogs` directory at the root of the project. Each file starts with a small frontmatter block containing a title, a date, a comma separated list of tags, and a short excerpt. Everything after that block is just markdown.
|
||||||
|
|
||||||
|
Headings, `inline code`, [links](https://svelte.dev), lists, blockquotes, and fenced code blocks all render into the same terminal styled theme as the rest of the site.
|
||||||
|
|
||||||
|
```js
|
||||||
|
function greet(name) {
|
||||||
|
return `Hello, ${name}!`;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
Thanks for reading the first post.
|
||||||
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
title: Personal Website v5.0.0
|
||||||
|
author: Sir Blob
|
||||||
|
date: 2026-07-10
|
||||||
|
tags: meta, svelte, sveltekit
|
||||||
|
excerpt: Why I ripped out the old blog redirect and wrote a small markdown blog engine instead.
|
||||||
|
---
|
||||||
|
|
||||||
|
For a while, clicking Blog in the navbar just sent you off to a separate site. It worked, but it never felt like *part* of this project.
|
||||||
|
|
||||||
|
## Why bother
|
||||||
|
|
||||||
|
A few reasons pushed me to build this in:
|
||||||
|
|
||||||
|
- One theme, one codebase, one deploy
|
||||||
|
- Full control over the reading experience
|
||||||
|
- An excuse to write a tiny markdown renderer from scratch
|
||||||
|
|
||||||
|
## How it works
|
||||||
|
|
||||||
|
Every post is a plain markdown file that lives in the `blogs` directory at the root of the project. Each file starts with a small frontmatter block containing a title, a date, a comma separated list of tags, and a short excerpt. Everything after that block is just markdown.
|
||||||
|
|
||||||
|
Headings, `inline code`, [links](https://svelte.dev), lists, blockquotes, and fenced code blocks all render into the same terminal styled theme as the rest of the site.
|
||||||
|
|
||||||
|
```js
|
||||||
|
function greet(name) {
|
||||||
|
return `Hello, ${name}!`;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
Thanks for reading the first post.
|
||||||
Reference in new issue
Block a user