Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2024 Poal.co

1.3K

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)

[–] • 0 pt

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

That account from the post you linked has been temp banned twice on /s/poaldev for making up and spamming false reports because admins refused to bend to his demands.

We used to have a lab preview for incoming features, but took it down when we migrated poal resources and services.

It will come back, we can't promise when though.

[–] • 0 pt

The user's behavior does not invalidate his point. There are many users here who have the proper skill sets and would be willing to donate time and effort. Sub owners want to not be caught by surprise. We need better mechanisms to collaborate.

[–] • 0 pt

The user's behavior does not invalidate his point.

It does. Making false reports (like a brat throwing a tantrum) because you don't know what you're doing with CSS.

We need better mechanisms to collaborate.

I already answered that.

"The lab will come back, we can't promise when though."

[–] • 0 pt

we can't promise when though.

And that is part of my point... collaboration requires communication, visibility and transparency