My work on the #WordPress Gutenberg editor back in 2018, which was essentially to replace the date picker with a different component and then tweaking some accessibility related things clocked in at 111 hours.
It could have been a day's work in an optimal environment.
This mainly had to do with waiting for feedback and dealing with management and leadership issues.
The date picker was then replaced a couple of years later with a different component.
Looking at some designs of old websites, I'm impressed by how much difference texture can make. I've been putting gradients on everything because #CSS lets me, and I can also make triangle and simple shapes, but I can't create, for example, polka dots or carpet patterns in pure CSS. I'm struggling to make actual image files to use in my #webdesign. So far I made a 4x4 dot pattern and I think it made a previously pure white background much better.
@aral But I'm not a commons-nist. If someone can create a business on top of free code, they probably have something of value to offer. I don't believe restrictive licenses incentive contributions at all. I think they just stop people who would profit from freely available code from starting their enterprises. I don't see this as a net plus as projects that could have been made weren't due to GPL's ideology.
@alda so, does it work well as an e-commerce platform...? I haven't been using Wordpress since 2012 so I'm not sure about what has been determined about this.
@iamdtms this is part of the CSS code Wordpress includes by default (the 'global-styles' stylesheet). I'm just going crazy all these unnecessary body selectors.
@shalien afaik all the problems with #lemmy are problems with the #fediverse. It would have worked just fine if it was an unfederated open source reddit clone.
#TIL: #CSS order doesn't reorder elements for screen readers because some of them don't even load CSS. This is some bullshit, to be honest. There's seems to be no way to make float: right; work with a floated element that's supposed to come after the main body logically. If this can't be fixed with #HTML then CSS should at least let me float into the previous element instead of into the next.
"Recently I decided to stop using the word semantics. Instead I talk about the UX of HTML. And all of a sudden my students are not allergic to HTML anymore but really interested. Instead of explaining the meaning of a certain element, I show them what it does."
The first door of the #HTMHell calendar has been opened and @vasilis approach really resonates with me. I'm a visual learner, and I also like to do stuff instead of reading about it.
@stvfrnzl@vasilis it's been my view that "semantic HTML" is promoted by people who have no idea what semantics mean. Tech is built on APIs, on agreed interfaces and protocols. Semantic HTML proposes a standard without use case. Nobody can tell me who is writing code that searches for <article> tags on a page and does something with it, or <hgroup>, <small>, etc. The only use case so far has been merely an aria-label shortcut.
@davidbisset imo this was a huge mistake. HTML/CSS/JS have vastly overgrown what they were designed to do. We should have a separate technology that ran in the browser, a web 3.0, with a web3:// protocol or something like that instead of http, and ditched HTML/CSS/JS. When you look hard at it, HTML is designed for a single self-contained document like a PDF. HTML never supported even the idea of a "website" from 20 years ago. The reactive monstrosities we have today are wholly incompatible.