Spectrum is now read-only. Learn more about the decision in our official announcement.


A community of developers, designers and others who love React.js. ⚛️


PSA: Posting etiquette

January 11, 2020 at 7:27am

PSA: Posting etiquette

January 11, 2020 at 7:27am (Edited 2 years ago)
Hey guys 👋,
Wanted to run a few things by you for posting better.
  • If you're asking for help, please use the #Help channel. #General is more around general discussions versus debugging. I have to move your posts when you don't.
  • If you're asking for random strangers on the internet to help fix your code, please provide the code. We can't help you otherwise. This can be done in the form of a CodePen or even Github Gist. You can also paste a snippet or two into Spectrum. Anything is better than nothing.
  • If you're asking for help, please do not title your post "Please Help me" or "Help please" or "Need help" or "Newbie here" or "react". This creates a poor experience for everyone as it offers no detail to the contents of the post. Considering Spectrum has a search box in the top right (if you're on desktop), this also helps when a user is searching for a topic. Imagine searching "React testing" and being greeted with 20 posts only titled "Need help...". You might not realize it, but I am cleaning up the titles myself and finding it to be a second job of mine these days.
  • Another thing to note. If you post something obscure and you do not clarify yourself after given time, your post will be removed. When I mean "obscure" I'm talking about odd posts I see saying stuff like "how to potato in app".
  • Please use codeblocks and please format your code blocks. If can do so here: (I've been formatting everyone's code to clean it up)
  • If you're introducing yourself by just saying "Hi, I'm So-and-So", please do this in the chatroom.
Thanks for reading and understanding! Just trying to make sure the community stays strong and everyone codes better.
Also, a big thank you to a few people I see on here always digging in and helping answer people's questions! It makes for a great community.

January 27, 2020 at 3:51pm
Considering revising these rules to also not allow obvious business self-promotion through odd blog posts.

February 4, 2020 at 10:54am
If you're doing a # Jobs posting, please use this formatting, as it's super helpful.
... followed by a link or a nice description of what the person would be working on.
  • If you want to put [FRONT END or FULL STACK] in the title, up to you.
  • If you want to put [SENIOR or JUNIOR] in the title, up to you. Even [ENTRY LEVEL] would help. You get the gist.
It's important to list your LOCATION regardless of whether it's REMOTE or not. As to an example why, I'm about to be living in NYC, and even though I'll be at a remote job, I'd likely never work for a company somewhere in India given the time difference to sync with the team. Remote rarely ever means truly remote. Remote means you work from home. It doesn't mean you can live in any country.
Open to feedback on any of this. Just trying to make it easier for people.

February 12, 2020 at 9:34am
Please format your code and especially your codeblocks for readability. I've been spending my mornings making them so the posts are actually legible. Run them though prettier or an online formatter (jsx specific).
The system isn't perfect, but it does work.
Tips. Use 3...
```js shift+return to "soft return" into the codeblock. followed by a closing of 3 ```
const Component = ({ prop, })
=> <div {}>Hello World!</div>

February 14, 2020 at 8:30am
Here's the Prettier Playground to help format your code for snippets

March 27, 2020 at 8:54pm
any thoughts on posts that are just a link to stackoverflow?

March 28, 2020 at 1:49pm
I would prefer people share their code correctly in their post. I'm unsure strictly banning linking to another place where there is discussion is the right move. I'm totally open to feedback though.
Right, I think it would be super cool if spectrum could grab the title, description, votes, resolved status, and display it as an embedded. But until then, maybe authors should do some of that?

April 2, 2020 at 2:53pm
Any thoughts on thread hijacking and duplicate posts?
I typically remove duplicate posts by the same user. You can DM me if I don't spot one.

May 20, 2020 at 4:37pm
If you are thinking of posting about a specific plug-in, library, app, it is most likely better to search their documentation versus post a question here. This channel is for React in general, and not the best resource for very specific advice.

June 4, 2020 at 2:13pm
I've updated this to not have an influx of "Hi, I'm So-and-So" posts. To be clear, it's totally fine to do this if you are showcasing something, but there's little benefit to the community for people to be scrolling through "Hi" posts. Open to feedback here if you agree/disagree. Thanks.

June 16, 2020 at 12:03pm
Please do not post React specific questions on this thread 🤠 This thread should be used for discussing the React community and ways to improve it.

July 28, 2020 at 8:57pm
Just to restate again, you can not post a wall of text talking about React and then say at the end ~"Having trouble with React? Use us to build your next React website". This isn't beneficial to the community. It's only beneficial to you, to advertise.

August 14, 2020 at 4:38pm
Please do not title your post "Help me" or "Can you help me?" or "I'm new".

September 2, 2020 at 7:28pm
To restate on job postings that are tagged [REMOTE]
"remote jobs" are not what people think. I work remote, but I'd never consider hiring/working for/with someone that is halfway across the world bc it's very hard to collaborate as a team that way. It's helpful to know location upfront. In addition, companies who hire remote may or may not have restrictions where due to tax and entity. For instance, we will likely not hire someone in India as there's no Entity setup there. Location matters, even when remote. Remote means you work from home. It doesn't mean you can live in any country.

October 19, 2020 at 5:19pm
Just as a reminder, though this might be a bit obvious. If I see duplicate posts, I will remove all until there is only one of them left.

October 26, 2020 at 7:19pm
I would prefer people share their code correctly in their post. I'm unsure strictly banning linking to another place where there is discussion is the right move. I'm totally open to feedback though.
Reposting questions from StackOverflow doesn't result in a discussion/response. Which somewhat seems to defeat the purpose of Spectrum. I'd lean towards a strict ban, or creating a dedicated sub-channel, so folks can mute those posts if they aren't interested.
I might lean towards a sub-channel, like # External Help?

November 7, 2020 at 12:35am
Hey Jon, want to respect this. 3 freinds and I built a project that automates react documentation and we were hoping we could offer our beta for free to the community here. Not sure this falls under business or self promo or not so figured I'd run it by you first?

November 9, 2020 at 2:48pm
(felipebpm) You're allowed to "Introduce" yourself and product in the #General Subchannel. You're just not allowed to post "3 common react mistakes" and link to a blog post that is also you in hopes people will hire you. For context, this was a huge problem with one particular user ruining the community experience for the rest of us. My goal here is to try and make the experience better. And I'm always open to feedback.

November 18, 2020 at 2:39pm
Open to ideas on how to solve people who ask for help but don't post any code. This is a problem 90% of the time. Thus the first comment is someone always asking for code.