Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
It’s the start of a new year, and while lots of folks are promising to be more active, I’m going to show you how to make Promises to be lazier: JavaScript Promises, that is.
It will make more sense in a moment.
Today I'm going to show you all the things to consider when building the perfect HTML input. Despite its seemingly simple nature, there's actually a lot that goes into it.
Well, we need to start somewhere. Might as well start with the control itself.
There’s been a lot of hype lately around the CSS :has() pseudo-class. And rightly so! It’s basically the “parent selector” we’ve been asking for for years. Today I want to focus on ways we can use :has() to make HTML forms even better.
In this article I’ll be working with custom form controls that look like this:
CSS has a lot of different units that you can choose from. In many cases, there is one unit that’s clearly better than any others.
However, one question that seems to come up throughout my career is whether you should use pixels or rems on certain properties where it doesn’t seem to make a clear difference.
The first time I opened up my DevTools and changed the contents of a website, I actually thought that I had hacked it. I thought, “Oh my gosh, what sort of crazy powers have I unlocked?”
Little did I know that it was just a local change that would go away when I reload the browser. Still, it is kind of cool to think we can do that.
I recently had to work on a project with some interesting requirements:
Most of those requirements would actually be very easy to fulfill with a 3rd party provider, but that last one: that’s the tricky one. Most service providers don’t give you root-level access, which means I’d have to do this all myself on a Virtual Private Server (VPS).