ErickRamirezAU commented on code in PR #169:
URL: https://github.com/apache/cassandra-website/pull/169#discussion_r955826006


##########
site-content/source/modules/ROOT/pages/community/ask_good_questions.adoc:
##########
@@ -0,0 +1,82 @@
+= Ask Good Questions
+:page-layout: basic
+:description: A guide to asking good questions to get better answers.
+:sectids!:
+
+== Welcome and thank you for being part of the Apache Cassandra community!
+
+:!figure-caption:
+.Image credit: https://www.pexels.com/@diohasbi/[Dio Hasbi Saniskoro on 
Pexels^]
+image::community/community-ask_good_questions.jpg[Supporting each other]
+
+ 
+
+Asking good questions will often get you a faster response and even better 
answers. So what makes a good question? This guide should help you draft a 
well-asked question.
+
+'''
+
+==== Before asking a question
+
+We encourage you to do a bit of research first. See if your question has 
already been answered in various channels:
+
+* For **developer questions** including coding or driver issues, 
https://stackoverflow.com/questions/tagged/cassandra[search on Stack Overflow^].
+* For **admin or ops questions** including installation or maintenance issues, 
https://dba.stackexchange.com/questions/tagged/cassandra[search on DBA Stack 
Exchange^].
+* Search the user mailing list archives.
+* Search in the https://the-asf.slack.com/archives/CJZLTM05A[#cassandra 
channels on ASF Slack^] (requires https://s.apache.org/slack-invite[account 
signup^]).
+
+Make sure you check the Cassandra logs and application logs because the log 
entries often give clues.

Review Comment:
   Thanks, I'll do that. 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to