i kind of wanna make a mobile version of my #neocities website so more people are able to see it easily but also like….. wahhh poor you you have to use your computer the way god intended to view
@ultraloveheaven@computerfairi.es hmmm it could be!
@gavi glad i asked! oops lmao
@ultraloveheaven i coded a separate barebones html-only version of my mainPage so ppl can switch between that and the 1080p-desktop-required one via button or menu.
just need to make the button and add the html file.
@bluejorts hope i don’t sound dumb but how do you do this? ty for the tip :•)
@ultraloveheaven so, your main page is the "index.html" file in the "Home" folder on the neocities dashboard, yea?
1. add a new folder to "Home"
2. make your 'more accessible version' the "index.html" there
3. add links to each other on both pages to switch between them
(main page has a link to accessible page; accessible page links to main)
i did it this way because my alternative is html-only (which was easier to code) and i have a personal challenge to avoid javascript.
html-only means the site will be read however the user's browser settings say, which is better for people who have to use accessibility-focused browsers.
if you just want your custom site but with a more flexible (mobile-ready) layout, focus on the CSS and use a button, link, or drop-down menu to change the theme (like how people have themes for different backgrounds, day/night etc). that's making a javascript event that switches css elements or entire stylesheets, though.
looking up "theme switching neocities" can get you started there. 'squidknees.net' is a great example of an accessible personal website.
@bluejorts thank you for this :•)
@ultraloveheaven i vehemently disagree with the notion that every single personal website needs to be 100% accessible as inflicted upon netizens by the corporate web 2.0
@ultraloveheaven that said my website is entirely navigable by text-only browser lynx and equally unbrowseable by mobile phone because phones are meant to be used for calls
@ultraloveheaven source i am a certified netizen hope this helps!
@mavica_again this validates my feelings towards this quite a bit. thank you - do you do this with just alt text, or is there more involved in making the site fully accessible thru lynx? btw i have a gbcamera photo of me and my bf on my site :•)
@ultraloveheaven generally it has to do with not using JavaScript to build your DOM and keeping the DOM simple and organized so that things appear in the right order in text instead of relying on JS or CSS to dictate how the elements are ordered on the screen
@mavica_again i code everything into the HTML document!
@ultraloveheaven the HTML describes the DOM but it can still have inline CSS and JS if you want
i prefer to keep them in separate files because that way you don't have to repeat and maintain CSS for every single page, you can just reuse a single file
@mavica_again def sounds simpler than repeating page to page like i do but i’m also dumb and don’t know a better way to code my site at the moment. it doesn’t seem to be slow and i have a template i just copy and paste and add my content to. thank you for engaging with me on this
@ultraloveheaven you just move your CSS into a separate file and link it in the head tag
@ultraloveheaven to be honest coding for two completely different screens is not easy, and it's ok to slowly work around it as time goes. If you worry too much about it from the start, you risk sacrificing your more unfiltered artistic view.
The only suggestion I feel like giving is to use flexbox, both because it's such a good tool and because it's easier to remodel it into a mobile view more than anything else.
@memo it is so daunting to imagine making an entirely duplicated, mobile-friendly version of the site, and you’re completely right in that it distorts the vision i have for viewing and experiencing it. i’d have to update double the pages i have now with any menu changes
wait actually is this an accessibility issue