paceaux

7 ms·

1.
by paceaux 4mo ago
ahhh. Yeah I put it there just to discourage folks from asking some LLM to summarize it. I really don't want my content fed to Sam Altman.
2.
by paceaux 4mo ago
Good for them. I build my website around topics. If you just want a raw list of everything I've written, that's the sitemap. Otherwise, just browse by topics or even the tags on the posts.
3.
by paceaux 4mo ago
You mean a sitemap? Because you're talking about a sitemap. Most blogs have a sitemap.xml that lists all of the posts. Also, why would you want to go through all 235 posts?
4.
by paceaux 4mo ago
<ruby> is going to be featured in my next article: You don't know HTML…Semantics. I'm debating whether that one will be one or two articles because I'm going to be covering everything from <ruby>, <bdi>, &lt
5.
by paceaux 4mo ago
This is called out explicitly in the article as a shift from HTML4 to HTML5.
6.
by paceaux 4mo ago
I'm not quite sure what you mean about that… I do have a disclaimer in the sidebar that makes it clear that I'm not using AI — but that's solely so that people can appreciate that I put actual effort into writing it.
7.
by paceaux 4mo ago
I'm writing articles like this just because I think the internet deserves some humanity for a change. Thanks for noticing.
8.
by paceaux 4mo ago
I will probably write an entirely separate article just on the CSS options for lists. So ... don't hold your breath. But that will come. Eventually.
9.
by paceaux 1y ago
It's like a dumpsterfire caught in a hurricane https://blog.frankmtaylor.com/2025/08/28/america-by-design-i...
10.
by paceaux 1y ago
I'm 100% convinced this was vibecoded I was doing a write-up on it from looking at the code and about 3/4's of the way through I realized, "there's no possible way a human was this bad." https://blog
11.
by paceaux 1y ago
You really might want to look into what the DOM is and how it works. When HTML reaches the browser, all the markup is parsed, and the browser creates a Document Object Model ( https://developer.mozilla.org/en-US/docs&#x2
12.
by paceaux 5y ago
So, worth explaining (as I've told other folks here), my experience is in enterprise content management, usually building good ol' fashioned websites that are running on .net and getting content from a CMS. For the entirety of my
13.
by paceaux 5y ago
To be totally honest, I originally didn't have any guidance around having a class name for .qa (this was a gist long before I made it a blog post and I'd been sharing the gist with teams for years). I had a boss point out that som
14.
by paceaux 5y ago
I've tried that approach in the past. The reason I didn't promote it in the guide is because data attributes, in my experience, were more verbose than what we needed. They were useful in cases where we needed to pass in additional
15.
by paceaux 5y ago
When I wrote the guidelines, it really was all about, "be consistent". camelCase is my preference, but really, go with what makes sense and is least disruptive. I actually REALLY like SuitCSS' recommendation and I definitely
16.
by paceaux 5y ago
Thanks. That's one of those where I have probably 100 cases in code I've written over the years and I can't find a single one when I actually needed it. I'm open to better examples.
17.
by paceaux 5y ago
I'm the original author.... and what I can say is that my area of specialization is content management; creating the CMS and the websites that consume from the CMS. So I'm not doing "app development"; I'm doing trad
18.
by paceaux 5y ago
That's a really valid criticism. I'll update it. Thanks!
19.
by paceaux 5y ago
I'm the original author. Somewhere else on my blog is an article about using BEM with content management systems (which is my area of specialization). I basically endorsed your exact practice, but with __content models__. The idea bein
20.
by paceaux 5y ago
I'm the original author All of the examples are within the last 2 years. My area of specialization is enterprise content management; I build the CMS AND the front-end for very large companies that use decoupled CMSs and web sites. And
21.
by paceaux 5y ago
original author here: That's valid and maybe I'll update the guide to explain a bit more when/where I have found getProperty() useful: I often do it when I end up having to have parity in API request: a get AND a set. If ther
22.
The Symbology of JavaScript Symbols(dev.to)
1 points by paceaux 7y ago|0 comments
23.
by paceaux 7y ago
Whoa. Don't know how this got here (I'm the presenter) I'm doing a write up of each of these 7 deadly sins. Will share links when I'm finished.