You rock. I totally appreciate it. Get me to solve a duplicate key in postgres, sure, but the only the simplest CSS makes sense and I only barely even understand the syntax of javascript.
BUT Wait.
On a completely unrelated note, I just made it so on my wife’s Kanban site clicking the site logo goes to the TODO category. I made theme component that allows setting the home page to an arbitrary URL. I did it like this:
<script type="text/discourse-plugin" version="0.8">
const { setDefaultHomepage } = require('discourse/lib/utilities');
if (settings.home_url_override) {
setDefaultHomepage(settings.home_url_override);
}
</script>
Maybe I should just do something like that instead? Though I’m not sure how to know which categories want their home page remapped. Maybe a site setting with an array of category IDs? I think I can google my way through getting the current category and seeing if that ID is in an array in a site setting.
EDIT: Hmm, but I can’t tell how in a <script type="text/javascript"> to tell what the category of the current . . . page? . . . is to selectively change the setDefaultHomepage.
Does that seem easier?
But back to the original solution
I think that sounds right to me, but that doesn’t mean much.
I think it’s that somehow the<h1> does the Right Thing, but that the <a> is going to the site home?
I’m just a caveman. I don’t quite know what that means. There’s some stuff that seems a lot like that in the javascript already. Would I make a whole-nuther one of those $(document).ready(function() { things? or add just another $(".title #site-text-logo").click(function(event){ in there somehow?
The thing I tried didn’t seem to do anything different.
I sort of understood this one better and did this:
/* keep tiny bit near logo from linking to home page */
.title a {pointer-events: none;}
This one changed something! And I see that it worked because now none of the logo will do anything.