Merge pull request #245 from iluwatar/design-principles
PR for Document design principles #208
This commit is contained in:
		
							
								
								
									
										11
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										11
									
								
								README.md
									
									
									
									
									
								
							| @@ -21,6 +21,17 @@ Reusing design patterns helps to prevent subtle issues that can cause major | ||||
| problems, and it also improves code readability for coders and architects who | ||||
| are familiar with the patterns. | ||||
|  | ||||
| # Getting started | ||||
|  | ||||
| Before you dive into the material, you should be familiar with various  | ||||
| [Programming/Software Design Principles](http://webpro.github.io/programming-principles/).  | ||||
|  | ||||
| Once you are familiar with these concepts you can start drilling down into patterns by any of the following approaches | ||||
|  | ||||
|  - Using difficulty tags, `Difficulty-Beginner`, `Difficulty-Intermediate` & `Difficulty-Expert`. | ||||
|  - Using pattern categories, `Creational`, `Behavioral` and others. | ||||
|  - Search for a specific pattern. Can't find one? Please report a new pattern [here](https://github.com/iluwatar/java-design-patterns/issues). | ||||
|  | ||||
| # How to contribute | ||||
|  | ||||
| If you are willing to contribute to the project you will find the relevant information in our [developer wiki](https://github.com/iluwatar/java-design-patterns/wiki). | ||||
|   | ||||
		Reference in New Issue
	
	Block a user