Merge branch 'kamranahmedse:master' into master

content/roadmaps/100-frontend/content/110-build-tools/100-task-runners/100-npm-scripts.md

@@ -1 +1,8 @@
-# Npm scripts
+# npm Scripts
+
+npm scripts are the entries in the scripts field of the package.json file. The scripts field holds an object where you can specify various commands and scripts that you want to expose.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink badgeText='Read' colorScheme="yellow" href='https://www.geeksforgeeks.org/introduction-to-npm-scripts/'>Introduction to npm scripts</BadgeLink>
+<BadgeLink badgeText='Watch' href='https://www.youtube.com/watch?v=hHt3oVk3XVk'>Codevolution: npm scripts</BadgeLink>
+

content/roadmaps/101-backend/content/109-apis/100-rest.md

@@ -1 +1,9 @@
-# Rest
+# REST
+
+REST, or REpresentational State Transfer, is an architectural style for providing standards between computer systems on the web, making it easier for systems to communicate with each other. 
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.codecademy.com/article/what-is-rest'>What is REST?</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.redhat.com/en/topics/api/what-is-a-rest-api'>What is a REST API?</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm'>Roy Fielding's dissertation chapter, "Representational State Transfer (REST)"</BadgeLink>

content/roadmaps/101-backend/content/114-design-and-development-principles/104-kiss.md

@@ -1 +1,7 @@
-# Kiss
+# KISS
+
+Keep It Simple, Stupid (KISS) is a software design principle that states avoiding needless complexity is the best way to build software that is easier to maintain, understand, and contains fewer defects. A simple product that does a single thing well is better than a complex product that does many things poorly.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://deviq.com/principles/keep-it-simple'>Keep It Simple</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.interaction-design.org/literature/topics/keep-it-simple-stupid'>Keep It Simple, Stupid (Kiss)</BadgeLink>

content/roadmaps/101-backend/content/114-design-and-development-principles/105-yagni.md

@@ -1 +1,7 @@
-# Yagni
+# YAGNI
+
+You Aren't Going to Need It (YAGNI) is a software design principle from the Extreme Programming (XP) framework that states when developing software, functionality or features should not be added until they are necessary. Within agile software development in general, requirements are always open to change; any extra functionality may end up being wasted time and resources.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://martinfowler.com/bliki/Yagni.html'>Yagni</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://deviq.com/principles/yagni'>YAGNI</BadgeLink>

content/roadmaps/101-backend/content/114-design-and-development-principles/106-dry.md

@@ -1 +1,7 @@
-# Dry
+# DRY
+
+Don't Repeat Yourself (DRY) is a software design principle which encourages developers to not repeat software patterns or code. DRY encourages code reusability, often in the form of methods, functions, or subroutines. When DRY is implemented successfully, developers are able to make one change to update many related elements while avoiding making changes to unrelated elements.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://dzone.com/articles/software-design-principles-dry-and-kiss'>Software Design Principles DRY and KISS</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.1001745#s5'>Best Practices for Scientific Computing</BadgeLink>