I need to fill this in with some longer form content to get an idea of what it looks like. This stylesheet is getting close to being done (maybe), but there are still some text spacing things, etc. I also haven't done anything with mdx-components yet, and I suspect that will come up eventually.

It's bothering me that hljs parses code on the frontend. I really feel like I should be able to get something set up to parse it on build so it's just part of the static output.

That's enough inane stream of consciousness filler content for now! I hope you didn't read this hoping it was going to be something interesting 😅

Here's a code block:

#include <iostream>

template <typename T>
void print(T value) {
    std::cout << value << std::endl;
}

int main(int argc, char* argv[]) {
	const std::string message = "Hello, Blog!";
    print(message);
    return 0;
}

Here's some javascript too:

function sayHello() {
	console.log("Hello, Blog!");
}

Here's some css (I don't have that parser set up, so idk what hljs is going to do with it):

.some-class {
	@apply some-other-class;

	color: red;
}

Here's an image:

I forgot to test some more formatting stuff in the paragraphs like italicized text and bold text and strikethrough text and bold italicized text

Here's a bulleted list:

• Item 1
• Item 2
• Item 3

Here's a numbered list:

1. Item 1
2. Item 2
3. Item 3

While I'm testing this, let's make a running todo list:

• Code syntax highlighting
• Constrain articles to a max width
• Finalize paragraph styling
• • Looks like strikethrough text isn't coming through
• Style lists
• Also style this checklist because this ain't it
• Code overflows code blocks on small screen sizes. Fix that
• It looks like we're not exactly parsing markdown checklists, maybe we need to find a github-flavor parser
• Delete all of this fake content and publish the first real post