This blog post describes how to use the editor tools to ask questions.
The goal is simple - good quality questions, and good quality answers!
This post shows how to insert code and photos into the editor, and some quick ideas/reminders on useful things to help accelerate question-asking.
To start, browse to an area of the site of interest if you like, or use the blue menu bar, or click in the search box to find your question or area of interest.
If you can't find what you want, click on Create and then Discussion as shown in red here:
If you've not browsed to a place, then it may prompt you for a suitable area. Pick one - (say) Raspberry Pi or Arduino as examples, but there are many choices. If you're reporting website issues, then choose Feedback and Support. If you're not sure, pick the closest one to your intended topic - you can always change it later after you've typed your question, before you finally post it.
If you've not already browsed to a place, you'll see this:
Here is an outline of some of the most useful tools available in the editor (click to enlarge):
Most important of all - pictures say a thousand words, and can clarify detail. Don't forget to insert (ideally non-blurry) images.
These are just suggestions! All may not apply.
1. My Goal in detail
(e.g. climb a mountain next year)
2. What things I'm trying to solve
(e.g. establish how high I am)
3. What constraints I have
(e.g. cost, software experience, hardware experience)
4. What hardware, tools and software I'm using
(e.g. part number, link to the tools and software)
5. Diagram or sketch to show the scenario, and what I've attempted
6. Where I believe the problem lies, or which part I need help on
(e.g. unexpected response from the part I'm using)
7. Non-blurry photographs of the set-up (zoomed out for context, and detail), and video if needed
Non-fuzzy, focussed Overview Photo (for context)
Non-fuzzy, focussed Detail Photo:
8. Code snippet or schematic showing the problem area
(use Syntax Highlighting from the Editor Tools, it will end up looking like this):
// Syntax Highlighting Example ("It makes it easier to understand");
9. Entire code and schematics if possible in attachments