this post was submitted on 24 Apr 2025
15 points (100.0% liked)
Privacy
37170 readers
227 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Something about how hugo is cooking everything down into a /public directory is breaking the overlay images (like the next/prev arrow). I'm sure I can track it down but since I'm pretty inexperienced this will take me some time (at cursory glance all the paths seemed good, so I'm not sure why it's broken).
I would also prefer to host it myself so maybe I should just do this...
Looks like
../ means previous directory so if CSS is public/css you want public/images.
OK, looks like the image paths are correct. It's something about the JS that fades them in. If I toggle the opacity property on/off then suddenly it works fine, until I refresh, so something funky is going on there. At least I know the structure is correct hugo-wise so it's just a matter of tracking down the fade-in issue.
Yeah I see nothing that using a local version that would cause that... Hmm next I would try mixing CDN ref and local ref for js/CSS try to pinpoint what one is making it buggy.
I'm starting to think it's something super specific to the particular hugo theme I'm using and how it wants users to insert custom js/css to get it all baked down into the right place in the final output. I'll keep bashing on it, thanks for your help!
Edit: OK this is kind of hilarious considering the community I posted to, but I actually think it works fine but something about my Librewolf setup is breaking it. It works fine in Firefox and Chrome, and since I jump around between them as I work I just happened to test in Librewolf right as I made this change. Not to get too far into the weeds but I think I'm going to just go ahead with not linking cloudflare. Thanks again.
Ah I didn't think of the image references! Yeah probably better off downloading the whole library when it requires the other assets too. Its likely soft linking at point of the css file and you'd need assets paths stored in reference to the CSS file.