@Miraz Ooh, I bet this will excite a lot of people š
A couple of comments:
All of the quotes in the copy-pasteable code sections are curly rather than straight
I got confused that the naming-a-custom-template screenshot used pagination rather than banner, until I went back a re-read; maybe a note with its caption like you do in the list-of-templates caption that follows?
FYI, you can almost always make a browser load changed CSS if you do a āforce-reloadā; itās usually
Cmd-Shift-Ron Macs (Ctrl-Shift-Ron Win/Lin, and maybe long-press on Reload icon on iOS?), which tells the browser to ignore the cache and any cache-age headers and fetch the files from the server again.
@smokey FWIW on point 3, hard refresh doesn't always work. IDK if it's an entire Micro.blog thing no matter what or if it's to do with some sort of network thing outside of the US but there can definitely be an issue with the performance of publishing CSS edits.
Aside from those external variables even earlier this evening Manton admitted it was currently slower than it should be so I imagine that particular case was some sort of server side performance issue.
// @Miraz
@simonwoods Yeah, if thereās some sort of server-side caching going on, or CDN that has expiration rules, or a load-balancer slow to pick up the latest changes, or so forth, those all could serve stale content even when the browser requests the newest stuff :-( Or just network crud. Thanks for the heads up. // @Miraz
@smokey Thanks Smokey. I shall make changes as per your feedback. And yes, I cheated with a couple of screenshots, but that doesn't payā¦ I'll fix them. š
@simonwoods @smokey Sometimes all my hard refresh tricks fail and I have to switch to another browser or do something really serious to force the issue.