Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Browser incompatibilities.
I use Firefox, Firefox is not a niche/unused browser. There is ZERO excuse for your web forms or pages to not work correctly because I'm using it. At the very least, all sites should be compatible with the latest form of Edge (gross), Chrome, Firefox and Safari. Those are considered Mainstream browsers. If your site fails to work on them properly, that's one of the easiest ways to make me disappear off the site.
Another big UI thing is infinite load pages. I don't care about the next article in line, give the user a sidebar or bottom container that contains related content, then I as a user can decide to click it or not.
And one last thing that many don't take into consideration. Have a functional print layout of the page. So many sites don't bother making a print layout but, as a user if I see something that I like, I might save it to a PDF, or print it out to show the family. When I do that I don't need the headers(except maybe the title box?), banners, footers, splash screen, ad boxes, comments etc. I only really need the main body content. The print layout will show the URL if enabled, so I can always find my way back to the page without it. A lot of times if I am doing this, it's because it's significantly easier to show my family then having to somehow get them to visit the page.
The part about having proper print layout of the site is actually interesting to me. I just learned about it recently and was curious about how there was explicit CSS support for this. This introduces an entirely new perspective on how a website should be designed to offer reliable print support that I am willing to learn.
Yea, not many sites bother but, the action makes it so much better, especially if the main content was supposed to be something that the user is supposed to digest such as a recipe or wiki site.
The
@media print
css at-rule makes it super easy as well. just hide everything but what you want to show, and adjust the margins how you like it.