I suggest making the Gitter home for PostCSS a clearer crossroads. For a new user looking for support from Gitter, they are presented with the PostCSS Gitter home page that shows two rooms. Each room may not appear the way that best directs a user
All Rooms
postcss
Transforming CSS with JS plugins
JavaScriptFrameworkCSS
postcss.org
A possible, undesirable, interpretation would be:
Hm, a generic postcss room—looks good. Oh! And a mystery postcss.org room… ".org", eh. Maybe, there, I can get staff to look at my questions.
Yes, most users should know that postcss is where to get implementation questions answered. But, there are some users coming to the postcss.org room, and asking questions that would be better directed to the postcss room. I suggest using the descriptions (and tags, if possible) to clarify the rooms' purpose even more.
New descriptions will not reduce all misdirected traffic, but they should reduces some, and having them would be more professional and clear, with (assumption warning) minimal effort. Example descriptions:
I suggest making the Gitter home for PostCSS a clearer crossroads. For a new user looking for support from Gitter, they are presented with the PostCSS Gitter home page that shows two rooms. Each room may not appear the way that best directs a user
JavaScript
Framework
CSS
A possible, undesirable, interpretation would be:
Yes, most users should know that
postcss
is where to get implementation questions answered. But, there are some users coming to thepostcss.org
room, and asking questions that would be better directed to thepostcss
room. I suggest using the descriptions (and tags, if possible) to clarify the rooms' purpose even more.New descriptions will not reduce all misdirected traffic, but they should reduces some, and having them would be more professional and clear, with (assumption warning) minimal effort. Example descriptions:
JavaScript
Framework
CSS
Website