My stubborn criteria: * No frameworks or third-party cruft. First-party cruft only. * No javascript * No libraries. Just wholesome CSS best practices from scratch Thank you!
-
Show this thread
-
Replying to @Pinboard
IAAFS. (Frontend specialist.) 1. Use BEM. It's a methodology, not a tool. I hate it. It looks and feels awful. I also use it for every site I author. http://getbem.com/
2 replies 0 retweets 2 likes -
-
Replying to @Pinboard @nathanhammond
just some guy with an opinion but I'd highly recommend against BEM in this case. BEM is made for large shops of hundreds of developers agreeing on a verbose but explicit set of rules. It's unwieldy for one person. 2¢
1 reply 0 retweets 2 likes -
Replying to @AhoyLemon @Pinboard
I don’t feel like BEM really costs anything other than some verbosity and pays for itself in spades when you have to later figure out how things are wired together.
2 replies 0 retweets 0 likes -
The other thing is to consider development over time. Pinboard has existed for 11 years and is an archival tool—expecting to exist for many more years. Every six months or so that‘s an entirely fresh look at the CSS: there is no way you remember why you did everything.
2 replies 0 retweets 0 likes -
Replying to @nathanhammond @AhoyLemon
Yeeeah every six months. That's right!
1 reply 0 retweets 0 likes -
Replying to @Pinboard @AhoyLemon
Hah! Longer durations and you definitely don’t remember why you did anything.
1 reply 0 retweets 0 likes -
Replying to @nathanhammond @AhoyLemon
99% of the stylesheets on the site date from 2009
1 reply 0 retweets 0 likes -
Replying to @Pinboard @AhoyLemon
Then it’s almost certainly impossible to modify them without being completely unsure of what you’re breaking. I’d consider setting up visual regression testing first (http://percy.io ) before diving in so that you have a baseline for the existing state of the world.
2 replies 0 retweets 0 likes
You are like a humor factory today. Yes, let me add that to the elaborate Pinboard test suite!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.