@wikipedia Wikipedia should underline its in-article links. Often these are long noun phrases with two or more links in them, and you can’t know which words are links without hovering.
I know removing underlines has been basically de facto design on the web for the last 20 years, but it is bad for usability.
Hey #WebDev people... Do you know of any good examples of sites that deal with large volumes of page content, but AVOID the "mega menu" UI system - such as the one here https://www.matalan.co.uk/
I'm of the opinion that they're terrible for performance, hard to use (especially hover triggered), hard to design for flexibility and versatility, and should be avoided.
Amazon's "All" sidebar is better; but what other systems have you seen?
A very well written article, that argues why it is the best time to invest in Web Components rather than anyone else's flavor of the month Front End Framework.
「 I had "separated my concerns", but there was still a very obvious coupling between my CSS and my HTML. Most of the time my CSS was like a mirror for my markup; perfectly reflecting my HTML structure with nested CSS selectors.
My markup wasn't concerned with styling decisions, but my CSS was very concerned with my markup structure.
Maybe my concerns weren't so separated after all 」
— Adam Wathan
Habe vor ein paar Tagen hier gelesen, dass einige Entwickler Gitea nutzen, um öffentliche GitHub Repos zu sichern, da so ein Repo auch mal schnell verschwinden kann. Wird halt ärgerlich, wenn man so Dependencies im Projekt hat.
Leider ist mir eben nur aufgefallen, dass diese Dependencies ja auch wieder Dependencies haben können.
Vielleicht sollte man eher den vendor und node_modules Order regelmäßig sichern.
Könnte auch weiter hoffen, dass so eine Situation nie passiert...
I finally got around to posting on my blog (it's been too long), with my retrospective on PyCon, as well as how I somehow (accidentally?) became a co-maintainer of an open source project.
The new project is another one of those "awesome" lists.
I'll probably write more about it at a later time, but if you have a passing interest in Python-based web design sans JavaScript, you may want to check it out.
The repo is a curated collection of Python packages using the PyHAT 🐍 🤠 stack (or some variation of it).
PyHAT: Python HTMX ASGI Tailwind
If you're looking for a declarative way of creating web apps, this may be for you!
Just had a go with https://github.com/Juerd/tootpick for adding a mastodon share button to a @getkirby website I am working on as suggested by https://spreadmastodon.org First site using Kirby after years on another CMS and I am loving the way it works. Tootpick looks very professional as well. #webdev
Day 39 of #100daysofcode#webdev is done, and it was again all about the four different kinds of loops in #javascript in action. The sheer amount of helper constants is kind of overwhelming for me, and I think I'll have to repeat some of the lectures before moving on. Day 40 up to day 40 are a milestone project, so I will find out quite quickly how well I understood all the control structure stuff...
Finally realized I should be using dictation more for inputting text.
Having previously used Chrome "Speech Recognition" API for voice-to-text in websites. I'm both surprised and disappointed that the accuracy of MacOS's built-in dictate feature is noticeably worse than Chrome's.
What happened to the Apple that broke new ground with a revolutionary voice assistant? #accessibility#webdev#apple
#NMROnline has a growing software library, with titles integrated into seamless and efficient workflows, built with industry standards and best practices.
Do you work in #webdev? I want you to order an old phone from ebay right now. Like a Samsung Galaxy S4 or something. Go visit your website with it. Did you have a good experience? Well, 1 in every 10 visitors has that experience. Fix your shit.
Sometimes we got to build workarounds to get around bugs that are not within our reach to fix (eg. a 3rd party library).
Those workarounds should be as short-lived as possible and to know when something is a workaround and when it's safe to be removed, we need to document it.
I ran into this at work while doing a code review the other day and decided to write a blog post.
I’ve spent the last few months crafting my own home on the Web, and I wanted to make sure it presented me as a human, not defined solely by my work as a #DesignEngineer / #WebDev.
This has also been a great opportunity to finally use #Svelte & #SvelteKit in a project. I love how easy it was to learn and how intuitive it is, as someone who started with vanilla HTML and CSS
Pulled all the third-party includes off the Podcast Business Journal website. No more Google Fonts, no more calls to Facebook, no more dynamic forms. Much better for privacy. Next, to shift it all to an Amazon S3 bucket, say goodbye to Wordpress, and start with a new CMS. #webdev
I'm including in my project an abstraction layer for data access so that when I inevitably feel the need to switch to a different library (or database!), the code I'll need to change will be contained.
One option I'd tried was TS first, but couldn't represent all the column/indexing/FK relationships.