Any code base that starts to grow in size and complexity will benefit from applying formatting and linting rules. Since I am firmly in the camp of stricter lints == better, I tend to turn Clippy up to 11 pedantic mode.
So far we have only done block level parsing for our markdown source. Let's add functionality to parse inline (span) elements. How hard can it be? Let's say this gave me more trouble than I expected, mostly because I went in with some wrong assumptions.
Let's split this weird one page blog into multiple pages!
When I push a commit to main, I want my changes to be deployed automatically. For this, we need a CI/CD tool. Obviously we could use an existing one, but where's the fun in that?
When creating this blog I hacked together a quick style, but it is not quite mobile friendly, so let's fix that.
This is my blog about building my own blog, starting with a homebrew static site generator. As the purpose of this blog is to learn stuff by building stuff, I will be building my own instead of using an existing tool!