made some pretty substantial edits to my previous post, specifically the parts on why i found gerard's post misleading, and being more clear about the subject of that post's (not david gerard) financial stake in ai
They say “great artists steal”, and I wanted to showcase how I’ve solved some problems I’ve run into on my site by showing some niche dependencies I’ve picked up. Note that these are mostly files that have originated from other sources that I’ve copied in by hand as opposed to imported.
I will go more into depth on this on a future article on how syntax highlighting on my blog works, but to summarize: I use a tool called Lezer to handle syntax highlighting. This library is part of the pipeline my blog uses for adding that syntax highlighting. This was written by Joel Gustafson and mentioned in an incredible blog post going into some of the history around syntax highlighting. I copied it into my site basically wholesale, and you can find it in my codebase here (converted to javascript from typescript for some reason). I generally prefer copying code in over importing it, because it helps me understand what the code does, and it allows me to tune the code to better fit the needs of my shitty blog.
My fancy theme picker was taken from the blog of Jim Nielsen. I thought the concept was pretty solid, and it wasn’t the hardest to bring it over to my site basically wholesale. You can find some more details in his post Building Websites With LLMs. It really checks all the boxes and I think that’s really great. You can also find the code in my blog repo.
If I am evaluating a dependency and see that it’s last been updated about 5 years ago, that’s a sure sign that I need to add it in by hand to make sure I understand what it’s doing, because if I run into any issues when using it, I don’t think the developer will ever respond to fix my issue, and I’ll have to fix it myself. If I recall correctly, that happened with rehype-truncate, which powers my read more feature. Like cohost (my beloved), my site tries to truncate my posts after seeing a line break or after reaching some sort of arbitrary word limit. This library does that truncation while avoiding breaking any html tags. You can find it in my codebase here (converted to typescript for some reason???)
if you ever need to update your comment btw just email me at [email protected]
What theme on the site is your favorite? Mine is the reddish-pinkish theme.
Okay! That's a wrap! Unfortunately, I didn't write as much as last time (65 reviews to 40 reviews, and I didn't write almost all of the reviews this time), but I still had a great time. My big lesson from this session of reviewing Netrunner cards? Get more contributors and/or bunch things up. There were way too many cards and I didn't have enough to say about all of them.
More contributors would be good. I really enjoyed seeing other people's opinions on the cards, and it would be good to set things up earlier and get more stuff involved, if that sounds neat to people. The other option would be to release reviews in batches almost entirely near launch, where I focus on talking about card packages and faction utility.
Idk this stuff is hard. Netrunner is not an easy game to talk about, although it's a great game to play! Get Elevation now! Also please follow my blog via RSS to continue seeing the stuff I put out! It's only going to get better! Or maybe i disappear off the face of the Earth for another 6 months who knows.
some recent changes to the site might result in the mouse showing up inside of the post. this is not intended. please empty your cache for my site and the mouse will go back behind the post 🥺 thank u
anyways, gotta fix some bugs with the attribution at the top of a post. I'm getting the cohost pill avatar on accident.
and the tags aren't working as expected. whoops. gotta fix that
on top of all that, a lot of things are Not Great in a "I need to write better code to prevent these issues" way. especially with the css.
I made a new system to upload to my blog via drafts. It's really jank and barely works, but that doesn't matter in the face of being able to post worser fasterer. it's like what cohost user @blep said about what cohost user @ewie (that's me) said: you gotta make it easy to post.
okay y'all. I should have fixed the comments and stuff by now. not everything is 100%, but it all should be functional. I'm gonna go to bed now. once again, please keep me posted if you see anything wrong. ty for the support and hope y'all really like the new site design!
also sorry for breaking comments on top down solutions i fixed them so i hope that's all good ty bye
Edit: I swear i fixed the comments for real now this is it they should all actually be working now