-
Notifications
You must be signed in to change notification settings - Fork 16
guidelines
Radosław Kujawa edited this page Jan 14, 2016
·
1 revision
Try to keep the same structure and style as in already existing examples:
- Top level directories separate examples per language used.
- Keep each example in a separate subdirectory.
- Keep the file names and their extensions short, correct, suggesting what is inside of the file.
- Don't use spaces in file names (replace them with "-" where needed).
- The code should be formatted to make it as easy to read and understand as possible (committing unformatted code is not acceptable).
- Each example subdirectory should have additional README.md (in Markdown format) file explaining:
- What does the example do.
- How does it work.
- How to build it.