Lessons We Gone And Learned From Maintaining A Fork Of A Fork
Discord
ok so they refactored all the css, and it was pretty hard to track down what in the heck was changed, so here is another Lessons We Gone And Learned From Maintaining A Fork Of A Fork - patching is good, editing in place can be fragile. i moved the custom styles from better code blocks and expanded status previews to their own set of stub scss files that then get imported at the end of the scss index, so they should override conflicting rules set previously. that keeps them nice and separate and survivable in the case of big refactorings. this is similar to the "flavours" system which takes whatever isn't overridden from base masto. i can't run the dev server rn bc my brother is in town but since these are just css changes we can uh test in prod i think https://github.com/NeuromatchAcademy/mastodon/commit/8e54a6bf891ff855104225032dd9ccfb0163acea