✨Winter Ray✨

when you go to my front page you see a bunch of images. if you click on an image, that sends you to that gallery's page. for example click on florions thumbnail, you go to florions photoshoot.

i would have built this by starting every gallery html file with the same copy pasted stuff and swapping in the relevant images. but my florions page is not just one html file, it is two. there is a site/galleries/ florions html which exclusively includes the embeds for the images (hosted on ko-fi), and then there is a site/ florions html which just says use the css with these variations (for example number of columns to arrange the images in) and pull images from the site/galleries/ florions html.

which means that every time i update the site, everyone who follows me on neocities first gets treated to a plain white page of just the images at full size on top of each other. and then because of the way neocities handles this stuff, the next thing they'll see is a blank gallery update page with the css fully loaded in but no images. i don't understand enough about rss to know if this problem will carry through for that?

this has been making it very hard for me to change things around the website. especially adding new pages, like an animal drawings page, or even just splitting my index gallery into pages, since it's getting a bit long. the index gallery is the same css + adjustments + pull images from this separate html file deal as the individual galleries. it works really well at making things simple and straightforward for updating, but upgrading is so confusing.

i'd also really like to do that thing where you add a #[something] in your link to automatically load the page scrolled down to a certain heading. this way i wouldn't need a million different html files for all of my different florions: they could all sit together on the same page for improvement to be easily seen, but the index gallery would still feature thumbnails of the fresh stuff at the top.

cohost was my go to place for help with website building. i wish i had more time to learn before the website becomes my main thing...

You must log in to comment.

in reply to @wolf-and-ghostling's post:

蒸しルビー @YuushaRuby9/14/2024, 9:08 PM

I don’t have time today but if no one else can help by tomorrow then hmu on discord

🦁 woxi @wolf-and-ghostling9/14/2024, 9:08 PM

thank you 💖💖💖😭

mattcolewilson 🎃@mattcolewilson9/14/2024, 11:06 PM

I haven't interacted with them in like a year, but 32 Bit Cafe is generally a great place to get help with this sort of thing. There's a discord server and I believe the folks there would be happy to help, if Cohosters don't solve it in time. All their info is here: https://32bit.cafe/

🦁 woxi @wolf-and-ghostling9/14/2024, 11:11 PM

oh this is very good !! thank you so much. i shall go look

karma chameleon @candiedreptile9/14/2024, 11:12 PM

i'd also really like to do that thing where you add a #[something] in your link to automatically load the page scrolled down to a certain heading. this way i wouldn't need a million different html files for all of my different florions: they could all sit together on the same page for improvement to be easily seen, but the index gallery would still feature thumbnails of the fresh stuff at the top.

this one's easy: add a unique ID to the header or div element you'd like to jump to, then you can make links that are just <a href="#id">. the IDs should be letters, numbers, dashes, no spaces. for example

<a href="#jump">clicking this link</a>
<h1 id="jump">will jump to here</h1>

i was doing this just the other day so you can see it in action by hitting the ol "view source" on this page

i don't know enough to help you quickly with your main question unfortunately