1. Added a link to copy & paste the guidelines into your own threads at the bottom.
2. Added example to Choose the right Channel. More to follow.
3. Added a short guide for replying. In progress.

Might have been stated more then once, but I will definitely pass on a thread or not continue if a) op seems they just want the answer to copy and paste. People generally don't learn that way. Put some effort into understanding and learning from the road block b) Research the question before. 99% of the time the answer is available somewhere. Many times I perceive the op hits an issue and goes straight to a forum to get an answer. As stated, you generally don't learn from the issue and will continue to have the same issue later c) one of the great and maybe not so great things about PHP is there can be hundreds of ways to solve an issue, just because you may not like the answer doesn't mean it's wrong. Plus no one over the internet is going to understand your coding style. Trial and error, testing and just plain old trying it out goes a long way.

Food for thought....

@mstnorris here is just a short snippet to be used until we get rewarded with a sticky thread option as @Ruffles suggested, maybe on the side bar. Btw, I find this thread very useful actually, it is like a little check list that could make ones mind re-think the issue.

( If Operating system relates to the issue )
Homestead: yes/no if no, then what are you using
OS & OS version:

Laravel version: php artisan --version
Ultimate Goal:
Error Exception: ( if any )
Code sample: ( if any )
Third Party Packages: ( if any )
More info on Posting Topics

echo '<snippet>
<em><small>( If Operating system relates to the issue )</small><em><br>
<em>Homestead: yes/no if no, then what are you using</em><br>
<em>OS & OS version: </em><br>

<em> Laravel version: <small>php artisan --version</small></em><br>
<em>Ultimate Goal: </em><br>
<em>Error Exception: <small>( if any ) </small></em><br>
<em>Code sample: <small>( if any ) </small></em><br>
<em>Third Party Packages: <small>( if any ) </small></em><br>
<em><a href="https://laracasts.com/discuss/channels/general-discussion/guidelines-for-posting-on-laracastscom" >More info on Posting Topics</a></em><br>
</snippet>';

[Updated] removed trailing space [Updated] closed italic tag

@mstnorris Please remove the trailing edit from the copy text provided for the quick linking.

@jekinney thank you, would you please write that in such a way that I can paste it into the guidelines either under the current headings, I will make new ones if need be.

@em57 all of the guidelines are technically if any as the post may not be a question. What edits would you suggest I make, what you wrote above is just a synopsis of the whole thing.

@usman thank you, and done. :)

Hey @mstnorris , I denote ( if any ) for clarity, it might be better to place it else where or remove it! So here are my thoughts, I think from the perspective of someone coming to the forum looking for help, they may need to digest the guidelines really quickly to get up to speed.

@em57 I've added this paragraph (second one in the guidelines). May need a little tweaking but I think it sums it up. I have to bear in mind that most people won't read the text anyway, they will just see the headings, but that is after all why I put them in so it should get the point across anyhow.

If you're completely new here then I suggest taking a few minutes to read over this post before posting anything yourself. You won't always need to include examples from all of the information contained here but it is a good starting point. If you have been around a while and just want a refresher on what information is useful to others' when helping you out then just skim over the headings and you'll find what you need.

Added Have you already looked?

Added Things of interest namely, two links to good resources on Stack Overflow

@mstnorris Good jobs and God advice, Thank you so much !

Mark this post as seen by me and this comment serves as a bump to keep it on top. :-)

I don't think we should bump this post all the time though.. I mean it will look kinda spammy! We can at least refer to it when users struggle with asking a question

This forum needs "pinned" posts, where Jeffrey could pin this so it stays at the top (or make his own version of this). Each sub-forum could probably benefit from a slight variation...for example people shouldn't ask for code review in the "general" section. At least not anymore.

@BENderIsGr8te Indeed, that's a better idea then bumping this post all the time...

I have emailed @JeffreyWay to this effect but I haven't got a reply (as yet). We all know how busy he has been because of all the videos he's just posted. And, he may not want to put the guidelines as a sticky, however I see no reason not to, and you guys think so too.

Thanks for all the support.

I just noticed that the link of this thread is on the side under "Most Recent Lesson"!

Man Jeffrey really rocks with these smooth updates all the time :P

@Ruffles yeah I emailed Jeffrey after a few people said it should be a "sticky" post at the top and he agreed, so he's linked to it in the sidebar which is awesome!

I think that the community here is awesome and it's great that @JeffreyWay took a suggestion from the community and added a link to this thread in the sidebar in Discussions so that users have access to it.

Thanks @mstnorris will keep these in mind from now on :-)

Awesome list, a few suggestions:

• Backtraces are helpful, if you are using artisan and get an exception use -vvv. This is a real problem solver.
• Again backtraces are helpful in case of 500 internal server error messages, check your website's error log provided by your webserver first, it might also contain a backtrace. Perhaps explain about app.debug option too?

Nice that this has been stickied. Great work @mstnorris

• Added "Before you start" section at the top. I want to add a "Common gotchas" - things to look out for, things to do before asking a question; that sort of thing. Any suggestions will be considered and added to the Guidelines.
• Added "Don't hijack a thread" section.

@mstnorris I suggest adding under polite something like this:

This forum is not a commercial platform. As such contributions from other users to help you on your code issues or advice on how to solve "complications" are done as an unpaid effort by these users. As such, respect that someone actually did take time to open the thread, read your question and type out an answer.

reason

@luceos thank you, I've added your suggestion :)

Hey let's bump this one again.

Sorry about this, but I'm testing if I can post a reply, because I'm unable to post a conversation. I mean, I solve the captcha successfully but the "Post Conversation" button does not become active and click-able. I assume new users can not post conversations right away?

I cannot post a question in the forum. I am logged in and have just created my account recently. The Post Question Button does not enable after captcha verification even though I get a green check box. Has anyone else experienced this?

Less bump you up. Maybe some folks will read you.

<form>
<input />
</form>

@MSTNORRIS - how can i include a screenshot on laracast when i ask queations