Here is the repo, with almost all the functionality happening in core.cljs : https://github.com/Chase-Lambert/homepage/blob/main/src/homepage/core.cljs which I mostly adapted from the reitit frontend easy example.

If this is a #shadow-cljs thing I can move it over there.

I also noticed the routing doesn't work in the dev build when I had {:use-fragment true} either.

if you don't use fragment it's a real URL routing that's happening so i'm not surprised it fails. The real question is, why doesn't use-fragment work in dev ?

Hmmm. But setting use-fragment to true doesn't work in production either.

Basically the website is for my programming related stuff where I'm practicing learning Reagent and such so I want it to be a SPA, but I want to be able to send some people (my English students) to a specific part of the website (`/teaching`) that's separate from the other stuff on the site. Is reitit-frontend maybe not a good way to accomplish that?

Wait a second. So I actually ran the reitit frontend example to hopefully better understand how it works and noticed the url includes a # in between the root url and the route. Putting that same # in my url obviously works too. So it's been working this whole time. Oof. hahaha. Oh man. I'm probably really showing my web dev naivete here. I obviously didn't quite understand what the docs were telling me when researching what that whole use-fragment thing was signifying.

Would someone mind giving a quick breakdown on why we put that # in there?

it seems to be that the # is what signifies that the route is a URL fragment. I assume that is how you do routing alongside a SPA. So I will gear my search towards that. Anyways, thanks for allowing me to rubber duck develop with you folks. hahaha

yup, the # is a trick to implement "routing" in a SPA, that way you stay on the same page but you still have the advantages of regular routing (URL that point to the routed page, history, etc)