coreyja/coreyja.com

New and Hopefully Improved Personal Site

👋 Hey I'm Corey

Pronouns: He/Him

Welcome to my Github profile!

Hey! I'm Corey, a web developer and content creator. I'm passionate about Rust programming and love sharing my knowledge and experience through my videos and streams. My goal is to create educational and engaging content that developers of all skill levels can enjoy. Whether you're just starting out or an experienced pro, I hope you'll find something useful in my videos. I also have a Discord server where viewers are welcome to join, ask questions, provide feedback, and hang out with me and the community. I'm always open to feedback and suggestions, so please don't hesitate to reach out and let me know what you'd like to see from me. Thanks for stopping by!

Discord: https://discord.gg/RrXRfJNQJX

Links

Twitch: https://twitch.tv/coreyja
Youtube: https://www.youtube.com/@Coreyja
Blog: https://coreyja.com
Fediverse: https://toot.cat/@Coreyja - @[email protected]

Sponsorship

I'm grateful to have the opportunity to create content that I love, and I'm always looking for ways to improve and grow.

If you're a fan of my work and want to see more, consider supporting me through Github Sponsors. Your sponsorship helps me continue creating educational and engaging content for the programming community, and it also includes some special perks for you!

All sponsors will receive my eternal gratitude, and those who join my Discord server will also get a special role and access to some private, sponsor-only channels. Thank you for your support!

https://github.com/sponsors/coreyja

Popular Repos

coreyja.com's Issues

Support `hr` in Markdown

Ideally with support for --- in MD

Blog post h1 etc elements should be anchor links

I really like it when I can link to sections of blogs by their anchor tags! Lets build this for my headings!

The 'issue' is that we don't have a great way to get an 'id' for the tag. We only have access to the full HTML content, but there is no guarantee what kind of element that is...

Complete Homepage

Add robots.txt file

Are there other similar in spirit files that I should add?

Posts page should redirect 'extra' versions to the cononical

So if the markdown file is some_post/index.md

We should make some_post/ the 'canonical'
And have some_post/index.md forward to some_post/

Right now we do some of this 'canonicalizing' and then render the page if we find one. Instead we want to use HTTP redirects so you are ALWAYS on the correct/shorter URL when reading an artible

This is important for SEO, since we need the content to live on a single stable URL

Validate that all images linked exist

This is kinda a two parter!

In the fix for #14 (which is in #22) we create a 'canonical' url that we link to. This always ends in a /

This however causes issues for the 'named markdown' style post, that also has images:
https://beta.coreyja.com/posts/BattlesnakeMinimax/Minimax%20in%20Battlesnake/

In the new version we link to ^^ on the index page, but then the images fail to load. This is because we are looking for images inside the BattlesnakeMinimax/Minimax%20in%20Battlesnake/ directory when they really live in BattlesnakeMinimax/

1. We could make more changes to how images load so that we can keep the same blog markdown
2. ORR we could have named markdown files look up a directory for their images.

I like option 2) because it is simpler. It doesn't involve directory traversal at runtime, we simply just need to setup the files correctly in the repo
BUTT I do NOT want to be responsible for making sure my images are linked up correctly on my own

The repo ALSO has the images, so we should be able to verify that all images in markdown actually exist. This probably lives in the CLI!

Lazy Load Post Images

Use the loading=lazy HTML property to lazy load all blog post images

Syntax Highlighting Should Not Embed CSS With Code

Right now our Markdown render plops down a chunk of CSS right next to each codeblock

Instead we should include a style tag on pages (probably just all pages) that references this CSS.

Question: Does this want to be served from the frontend package? If so do we need to crate deps around a bit

Create `db` crate to shove all Database Interactions into

Inspired by this Twitch Chat

opusbopus: though in larger projects i generally make a 'db' library for my other projects so the migrations would be in db/migrations/ which makes it a tad nicer buttt you probably dont want/need that lol

Create a Light Mode

Add sitemap.xml

I think google will like it if I add a sitemap, at least listing all the posts since those links should be easy

Ability to show code blocks with some lines highlghted

So we can walk line by line through code snippets

Add Social Card Embed Things

Make it so when I post in Discord or other apps we can generate the embed things nicely

For TIL's would be really cool if we could just embed the whole content I think

Posts Index should link to shortened post urls

If the blog file is currently index.md we point to that full URL from the posts index page

I think we want to link to the 'shortest' version

Local Dev should hold onto open port while recompiling

Right now with just cargo watch we 'lose' the port while we re-compile.

It would be really cool if we recompiled WHILE still serving the old version, and only switched over once compiling was done

One step further would be to actually spin both up side by side, and not accept requests to the new version until it is able to respond (is already booted)

Add Analytics

Add analytics framework to count page counts and stuff

Likely want to make a new db for this but could just put it in the db I already have if it's simpler

RSS Feed

Fix OTEL Headers

coreyja Brand Aesthetic

Requirements:

• General Brand Aesthetic
• Font Ideas
• Logo Ideas
• Inspirations and Things to Avoid

Pinterest: https://pin.it/4uXWcwB

Brand Aesthetic Here: https://github.com/coreyja/coreyja.com/blob/main/brand/aesthetic.md

coreyja.com Description and Feature List

Create appropriate sized images

We should resize large images so that we don't have to load excessively large images

We should probably do the thing where we send multiple sizes that can be used at different viewports

Add Newsletter Embed