As the site grows we have more and more people writing code. At the very least we have Sub owners investing time and effort into CSS code. We need to start having more robust dev, test and deployment practices. There are two issues I see here
1) No code is perfect. We have folks here who would gladly do some testing on new major features before they go live. Have things like new global themes available in a sagging site for a few days before it goes live could catch a lot of issues.
2) Sub owners need to be able to test CSS changes someplace, both the CSS they are writing for their subs and a place to do compatibility testing against new global CSS like the new Day Theme. Sometime we see problems like https://poal.co/s/Poaldev/293498 ...folks need a little bit of warning before major changes so they can update their CSS
As the site grows we have more and more people writing code. At the very least we have Sub owners investing time and effort into CSS code. We need to start having more robust dev, test and deployment practices. There are two issues I see here
1) No code is perfect. We have folks here who would gladly do some testing on new major features before they go live. Have things like new global themes available in a sagging site for a few days before it goes live could catch a lot of issues.
2) Sub owners need to be able to test CSS changes someplace, both the CSS they are writing for their subs and a place to do compatibility testing against new global CSS like the new Day Theme. Sometime we see problems like https://poal.co/s/Poaldev/293498 ...folks need a little bit of warning before major changes so they can update their CSS
(post is archived)