Manuel Matuzović

I really enjoy the site below. TIL (CSS) https://www.matuzo.at/til Blog https://www.matuzo.at/blog

Odd, I've always used it to mean removing everything that doesn't meet expectations. I've got at least a few people who agree with my usage. https://www.matuzo.at/blog/html-boilerplate/ > I’m cutting the mustard at JS module support. If a browser supports JavaScript modules, it means that it’s a browser that supports modern JavaScript, such as modules, ES 6 syntax, fetch, etc. https://decadecity.net/blog/2014/03/06/cutting-the-mustard > The phrase "cutting the mustard" was coined by the BBC responsive news team to describe a technique of setting a minimum standard that a browser must meet in order to get an enhanced experience. Browsers that meet this minimum standard are said to cut the mustard. I guess this is the OG https://archive.li/ANEHs but my parents use this phrase so I would be hard pressed to believe this is where it came from.

Manual Matuzovic has a good HTML boilerplate, and he goes line-by-line into what it does. https://www.matuzo.at/blog/html-boilerplate/

Note: It's entirely possible to build a site that scores a 100 on Lighthouse, but be an abject failure in Accessibility compliance. We've done it ourselves on my team inadvertently (combo-box failure), so never forget that actual, manual testing with screen readers is 100% necessary. Automation often works against you when it comes to achieving compliance. To wit, you can create a really, really inaccessible site that scores 100 on Lighthouse: https://www.matuzo.at/blog/building-the-most-inaccessible-site-possibl…

Here's some of my tips for a handwritten HTML site, since the author wished more tips existed: - consider using an HTML boilerplate template like this one if you don't know where to start: https://www.matuzo.at/blog/html-boilerplate/ - consider using a CSS template, or a CSS reset, if you don't know where to start with styling. Pico CSS is a good drop-in: https://picocss.com/. Frontend devs always blog about their CSS resets, like this one: https://piccalil.li/blog/a-more-modern-css-reset/. But if you're someone inclined to write their own HTML, then you'll probably also want to write your own CSS. This takes time to learn. Especially learning how to design the page without looking crappy - I copy my last page as a template whenever writing a new page - I don't worry about code duplication. If I need to refactor duplicated content, I use search and replace across files in vim (like https://nithinbekal.com/posts/vim-search-replace/). Hopefully your editor/IDE has something similar, and hopefully you're comfortable with regexes - markdown + pandoc + scripting is a common solution. Technically it's not handwriting HTML at this point -- it's hacking together your own static site generator instead of using an existing framework -- but no biggie - frontend people have made a lot of live reload tools over time. Here's a couple: https://nitoyon.github.io/livereloadx/ and https://github.com/tapio/live-server. Personally, I've cobbled together something with…