I’ve been working on redesigning an existing modal at work this week and I managed to make this glorious nightmare with a badly placed <div class="d-flex"> tag. When I saw it, I couldn’t stop laughing. In that spirit, here are a couple of other design-focused links I’ve run into over the last week or so: The UX of LEGO Interface Panels These “CSS crimes” turn social media posts into games Not All Zeros are Equal
Me: Oh, let me change the theme, it won’t that big of a deal. time passes Me: Six hours isn’t bad, right? So, yes: I did change a few colors. And the font, and the entire theme. And I made a colophon page and managed to actually code it in properly. Which is pretty exciting, not gonna lie. Anyhow. I’m sure some things look funky and I didn’t notice....
It has been a week here. I have: successfully wrangled custom radio button hover and focus states the html radio buttons were offset from the custom ones and moving them helped the hover happen in the right places I am still mad at whoever originally coded the component, though got a chunk of coding done for the mobile version of the site footer the desktop version is good to go, but I have a few more bootstrap/flexbox things to figure out helped a user regain access to their account using nothing more than an old photograph of their phone’s screen and a vague list of tasks....
So here I am, in the wee hours of the morning, having frittered away the last 7 hours of my life on a few “quick” updates to the site. Except I kept thinking of new ways to do things or fixing errors with the style sheets to the point where, except for the general layout and the little cactus icon up there (which is going to be replaced soon, I swear), it’s basically a whole new theme....
The spaghetti that is this site’s CSS is really something else–to the point where using the override files just doesn’t work because there’s so much stuff squirreled away in different places and it all takes different precedence. I’ve made a kanban board for the things I want to do and a bunch of them include “refactor and consolidate X, Y, or Z.” I suspect that when I’m done, it’ll be an entirely new template....
And of course, no sooner than I finished my previous post and decided to deploy the site than I ran into a bunch of problems, some bigger than others. First, I had to set the DNS record to point at GitHub Pages. And that takes time to propogate and I am impatient. The DNS wasn’t propogating and GH was tellng me that I’d configured something wrong, so it recommended that I set A records to point at the GitHub Pages IP addresses…except it didn’t actually link to where I could find those IP addresses. I finally found them buried in GH’s documentation, but I’ll be damned if I can find the page again, even with searching through my browser history. I also set up the CNAME record at the same time. Then I had to set up the GitHub workflow to actually deploy from my repo to the page–and unbeknownst to me, there was a critical piece of missing information from the workflow as written. And that piece of information was setting cname: peculiar.monster in the deploy script. Seriously. CNAME kept on disappearing from the gh-pages branch and I couldn’t figure out why until I looked at this GH Action which mentioned setting CNAME, while the Hugo-specific action–the one I chose to use–did not mention it anywhere. No wonder it was being removed! So, with that sorted, I turned my attention to why either the theme or Hugo wasn’t respecting my ` ...