Miguel said: That is, keep the number of children nodes at a bare minimum and use flex/grid to make stuff look like what you want. [...] [...] Also, comment your code as much as you can. That will help out newcomers and probably yourself in the long road. Always aim for readability, less code does not means better code, specially when it comes to maintenance. With the sheet's I've created or worked a bunch on in the last 9 months or so, I've tried to follow Google HTML/CSS Style Guide to keep my code as readable as possible, without trying to wrangle it to perfection. I'd be curious on what people think of my " Feast of Legends "(simple sheet) or " Hc Svnt Dracones 2E "(moderate size, more organized)-sheets. Neither are efficiently written, but are organized and commented in a way that more than makes up for being less effective. If anyone would happen to take one or two minutes to skim through them and give an opinion, I'd greatly appreciate it. I usually try to have a bunch of general CSS, and when I create each section I end up creating adjustments to each, only at times going back and bundling things I repeat to be general styles. Miguel said: Same with CSS, if you keep you snippets generalized instead specific, you should be good enough without a css compiler. Sure, it might be good enough, but the simple fact that you can nest things with SCSS reduce the lines of code you work with in CSS, which already by itself should be a good enough reason to try use it even if you'd otherwise use no other features of it. Which reminds me, I really should try that with some of my sheets, as a starting point. The " Building Character Sheets "- wiki page has a " Best Practice "-section(and by extension, the help-center version ), that I've been heavily involved in writing. It contains similar advice, split by topics, but is starting to become somewhat long if much more of advice here would be added. Would be great if some of the fine folks here could take a second look at it. As the main article have grown, I've tried to create new pages for sections that grows too large, and there is starting to be a good bunch of advice here that might work better as a separate page linked to the page. Maybe I'll get started on moving some of the things to the wiki at some point. When I get started with using PUG or SCSS in my sheets, I might make a short guide on the things.