This revision has been submitted to the devs to push the change, so unless there are any critical issues, this is the final version and I will not be modifying it anymore.

(I have cut down the post body to make the request clearer for reviewers; you can view the revision history for the original question.)

The current modal that appears for someone asking for the first time doesn't really contain helpful information for our site; however, we can change it.

After deliberating with the community, I formally the following.

Change the text before the note about searching the site for duplicates to:

Welcome to Code Golf & Coding Challenges! We host recreational coding challenges & related questions including code golf, fastest code and code golfing tips. All challenges must have an objective scoring criterion, and should avoid these listed points.

Questions about help with general programming-related issues are off-topic here and will be closed.

Please post your challenge as a draft to our Sandbox for Proposed Challenges for a few days first for feedback. Doing so allows you to correct issues you might otherwise miss before posting to the main site.

Change the text after the aforementioned note to:

The following bullet points only apply to non-challenge questions

Remove the third bullet point.

  • \$\begingroup\$ There's a big problem. You can't customize the big 1 2 3 part, at least not from what the post says. You can only insert information in a paragraph above the existing text. \$\endgroup\$ – Redwolf Programs Jun 10 at 3:12
  • 1
    \$\begingroup\$ @RedwolfPrograms Yes, but we can disable the 3rd part from what I've been told, and all we can do is do our best to clarify in the paragraph before it. \$\endgroup\$ – hyper-neutrino Mod Jun 10 at 3:13
  • 1
    \$\begingroup\$ Just append "Ignore everything below this". \$\endgroup\$ – A username Jun 10 at 5:49
  • \$\begingroup\$ Related \$\endgroup\$ – caird coinheringaahing Jun 10 at 8:17
  • \$\begingroup\$ This is just a comment, but can we add a link to the basic question template? \$\endgroup\$ – A username Jun 11 at 9:12
  • \$\begingroup\$ @Ausername Where is that? \$\endgroup\$ – hyper-neutrino Mod Jun 11 at 12:45
  • \$\begingroup\$ @hyper-neutrino Template for Challenges. It's a good general resource, but I don;t think its a necessary thing to add \$\endgroup\$ – caird coinheringaahing Jun 11 at 15:57
  • \$\begingroup\$ @cairdcoinheringaahing Ah, thanks. That's in the sidebar so we can probably point them there and trim even more content out, I think. \$\endgroup\$ – hyper-neutrino Mod Jun 11 at 16:01
  • \$\begingroup\$ Related: MSE post announcing the introduction, which specifies what you can and cannot change. (You cannot change anything from "Before you post," and down) \$\endgroup\$ – Peilonrayz Jun 13 at 10:44
  • \$\begingroup\$ @Peilonrayz Thanks for the info; I'll keep that in mind! \$\endgroup\$ – hyper-neutrino Mod Jun 13 at 10:45
  • 1
    \$\begingroup\$ A weird idea -- can we put enough empty lines after our text so that the irrelevant default text is no longer visible? \$\endgroup\$ – xnor Jun 16 at 0:45
  • \$\begingroup\$ @xnor Testing shows that that would make the modal scrollable which is more confusing, sadly :( Also, the "Start Writing" button would disappear too. \$\endgroup\$ – hyper-neutrino Mod Jun 16 at 1:28

Yaakov kindly updated this to include the information you wished. It'd require a bigger change to make it possible to get rid of the bullet points but I'll discuss internally about whether that's something we want to request. I know this would be great for y'all but with the number of devs we have currently, it'd be a decision of whether this was higher priority than other things - so we can discuss internally but I'm not making any promises.

Screenshot of the new asking a good question modal with the text as described in the question.


Asking a good question

This is a site for competitive coding enthusiasts. We host coding challenges, such as code golf, and related questions, such as golfing tips. We require that all new challenges have an objective scoring criterion, so the winner can be appropriately and fairly chosen. Questions about help with general programming-related issues are off-topic here - those belong on Stack Overflow.

We suggest you post your challenge draft to our Sandbox for Proposed Challenges before posting it to main, in order to help find out if it's a duplicate, clear up any ambiguities or otherwise get feedback. Doing so allows you to correct potential issues before actually posting the challenge.

Be aware that the two bullet points below are not generally relevant to our site - we're simply unable to change them.

Thoughts? This may be a little long (and I can cut down the paragraph about the Sandbox if so), and the bit about irrelevance seems odd.

Changed the wording slightly to fit hyper-neutrino's answer better, as that's the standard site terminology.

Changed some wordings thanks to Luis Mendo's suggestion

  • 1
    \$\begingroup\$ I don't believe those two options are available for us to change, unfortunately. At least, assuming I interpreted Catija correctly. I will ask again but I doubt it, I think the best they can do is get rid of the third point. \$\endgroup\$ – hyper-neutrino Mod Jun 10 at 13:08
  • 1
    \$\begingroup\$ For point 1., "challenge" and "problem" are close enough that it doesn't matter much. So the only significant issue is 2. All I can suggest is preceding it with a note saying that "research" in point 2. really means "the scoring criteria". \$\endgroup\$ – Ray Butterworth Jun 10 at 13:19
  • \$\begingroup\$ @RayButterworth I mainly included the bullets as more of a hopeful thing. The "meat" of the suggestion is the text above the "Before you post, ..." \$\endgroup\$ – caird coinheringaahing Jun 10 at 13:26
  • \$\begingroup\$ It might be a good idea to add that the three last bullets aren't relevant to CGCC. You might also want to add that tips questions are on-topic. \$\endgroup\$ – user Jun 10 at 15:32
  • \$\begingroup\$ @user Good point, edited \$\endgroup\$ – caird coinheringaahing Jun 10 at 15:36
  • 2
    \$\begingroup\$ A couple of suggestions, in case you want to incorporate them: "criteria" should be "criterion". "Doing so makes it significantly simpler": I would say something more explicit, such as "Doing so allows you to correct potential issues before actually posting the challenge" \$\endgroup\$ – Luis Mendo Jun 10 at 20:58
  • 1
    \$\begingroup\$ @LuisMendo That's a significantly better way of putting it, I;ve edited that in :) \$\endgroup\$ – caird coinheringaahing Jun 10 at 21:00
  • \$\begingroup\$ 'This is a site for competitive coding enthusiasts' no it isn't. Code golf is not competitive programming and this will only confuse people. \$\endgroup\$ – rak1507 Jun 11 at 18:32
  • \$\begingroup\$ @rak1507 Code golf is competitive coding - we compete to create the shortest code. Additionally, this is more or less standard terminology used to describe the site, see the welcome page, the help center, the info box etc. \$\endgroup\$ – caird coinheringaahing Jun 11 at 19:05
  • \$\begingroup\$ Unfortunately competitive coding or competitive programming is already an established term that means something very different, and I think terms should be unambiguous to avoid any potential confusion. \$\endgroup\$ – rak1507 Jun 11 at 21:12
  • \$\begingroup\$ The sentence should be "Be aware that the [three] bullet points below ...". \$\endgroup\$ – Peilonrayz Jun 13 at 10:36
  • \$\begingroup\$ @Peilonrayz According to hyper (see the question body), we're able to disable the third bullet point (but only the third one), so this answer assumes that we're disabling it \$\endgroup\$ – caird coinheringaahing Jun 13 at 11:49

To add to caird coinheringaahing's version, since we have decided to allow non-challenge questions, I propose the addition of this point in the middle of the current first paragraph and to replace the advisory on Stack Overflow, and splitting the SO point to a new paragraph (or keep it in the first):

This is a site for competitive coding enthusiasts. We host coding challenges, such as code golf. We require that all new challenges have an objective scoring criteria, so the winner can be appropriately and fairly chosen. We also allow code golf or code challenge related questions (such as tips), and a list of acceptable non-challenge questions can be found in this FAQ.

Questions about help with general programming-related issues are off-topic here - those belong on Stack Overflow.


We have a Welcome to CGCC page, we should link it in the popup. Specifically, the section on Asking.

I propose adding this paragraph after everything mentioned so far but before the note about ignoring the two bullet points:

We welcome you to Code Golf & Coding Challenges Stack Exchange. The FAQ on Asking good questions contains more details and goes more in-depth on advice for asking on this site. By following the advice in this popup and on that FAQ page, we hope that all new users will be able to understand the scope of this site and have a positive first experience with our community.


Posting a new challenge

Welcome to Code Golf and Coding Challenges Stack Exchange! This is a site where coding enthusiasts congregate to solve competitive challenges, not a general Q&A site for coding. All challenges must have an objective scoring criterion such that the winner may be fairly chosen. Questions asking for help with specific coding problems should be posted on Stack Overflow, although we do allow questions here asking for tips on code golfing.

All challenges not tagged should first be drafted in the sandbox for proposed challenges, where feedback can be given. It is recommended to leave ideas there for at least 72 hours.

Once the challenge has been through a week's time in the sandbox, there are several more things to keep in mind:

  • Unless your challenge is tagged , it should not be language specific. This excludes participation from certain members and is discouraged.
  • Unless the input/output format plays a crucial role in the challenge, avoid cumbersome I/O formats. Forcing certain methods of input or output further takes away from the main task.

Next, make sure to search the website to make sure that your challenge has not been posted by someone else.

Once you have performed all of the above tasks, you're ready to post your challenge!


Thoughts? Maybe the end part, couldn't think of anything to say.

  • 1
    \$\begingroup\$ "You're ready" suggests you don't need to post in the Sandbox right now. Could you maybe change that? \$\endgroup\$ – user Jun 10 at 21:30
  • 1
    \$\begingroup\$ @user I have edited it. \$\endgroup\$ – Recursive Co. Jun 11 at 15:36
  • \$\begingroup\$ I was talking about the part at the very start of the question, since a first time asker isn't ready if they haven't posted in the Sandbox first. \$\endgroup\$ – user Jun 11 at 15:43
  • \$\begingroup\$ @user Sorry for the misunderstanding. Would something along the lines of "Welcome to Code Golf and Coding Challenges Stack Exchange!" be more suitable? \$\endgroup\$ – Recursive Co. Jun 11 at 15:54
  • 1
    \$\begingroup\$ That sounds good, yeah. Also, saying "a week's time" may discourage people, even if it's a good suggestion. Maybe change that to "at least 72 hours" instead? \$\endgroup\$ – user Jun 11 at 15:55
  • \$\begingroup\$ I'm concerned that "coding enthusiasts congregate to solve competitive challenges" will sounds to people like we solve challenges from Leetcode or HackerEarth or similar. how about "coding enthusiasts congregate to create and solve competitive challenges"? \$\endgroup\$ – xnor Jun 16 at 0:33

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .