Skip to content

Commit 6afd6c3

Browse files
committed
Update format
1 parent 7d62272 commit 6afd6c3

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

Contributing.md

+5-6
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,25 @@
11
## Contributing
22

3-
I'm trying to make informative and entertaining questions about topics that I like. Interested in contributing to my repo? Fork this repo and start preparing your question. After you prepared a question about an interesting topic, open a pull request. I'll try to merge as soon as possible. If you found any mistake or you have advice, feel free to open an issue. Here's the format. Please be careful to follow the format for nice and clean repo.
3+
I'm trying to make informative and entertaining questions about topics that I like. Interested in contributing to my repo? Fork this repo and start preparing your exercise. After you prepared a exercise about an interesting topic, open a pull request. I'll try to merge as soon as possible. If you found any mistake or you have advice, feel free to open an issue. Here's the format. Please be careful to follow the format for nice and clean repo.
44

55
#### Structure
66

77
- Exercises must be under [here](exercises), as topic-name.md format.
88
- If you want to give some materials for exercises, you should put them under a directory which has the **same** name with your exercise. Then put that directory [here](exercises/materials).
99

10-
#### Questions
10+
#### Theoretical
1111

12-
1. At the first line, use ```### Question - Topic Name```.
12+
1. At the first line, use ```### Theoretical - Topic Name```.
1313
2. Give information about topic.
1414
3. Ask the question and show additional materials if available.
1515
4. Write example input and output.
1616
5. Give extra information, resources and links.
1717

18-
#### Answers
18+
#### Practical
1919

20-
1. At the first line, use ```### Answer - Topic Name```.
20+
1. At the first line, use ```### Practical - Topic Name```.
2121
2. Describe how you write the code.
2222
3. Give code using **suitable** markdown format.
23-
4. Go to question link.
2423

2524
#### Readme
2625

0 commit comments

Comments
 (0)