Merge branch 'gh-pages' of github.com:turingschool/backend-curriculum…

…-site into gh-pages

module3/projects/market_money/evaluation.md

@@ -6,7 +6,7 @@ type: project
 ---
 _[Back to Market Money Home](./index)_
 
-The 'eval' for this project is going to be a bit different than other projects in the past. We are relying on you to score yourself for this project. To do that, please submit the form provided to you from your instructors. 
+The 'eval' for this project is going to be a bit different than other projects in the past. We are relying on you to score yourself for this project. To do that, please fill out and submit [this form](https://forms.gle/1o1u5Ai2UYifwY9cA) individually. 
 
 ## Feedback Session Format
 

module3/projects/market_money/index.md

@@ -60,7 +60,7 @@ Next, you'll "confirm" the import. The test suite should display as a "Postman C
 
 Within your collections in Postman, you should see one collection-- "Market Money".
 
-#### Running the Tests
+### Running the Tests
 
 There are two ways to run the test suite: one endpoint at a time, or the whole suite.
 
@@ -87,11 +87,12 @@ As it runs, it will show you which tests are passing or failing. Remember, that
 
 ## Technical Requirements
 
-The Technical Requirements for this project can be found [here](./requirements)
+The Technical Requirements for this project can be found [here](./requirements).
 
 ## Extensions
 
-After you've completed ALL 11 endpoints, you can find some extra practice ideas [here](./extensions)
+After you've completed ALL 11 endpoints, you can find some extra practice ideas [here](./extensions).
+
 ## Evaluation
 
-Evaluation details can be found [here](./evaluation)
+Evaluation details can be found [here](./evaluation).

module3/projects/market_money/requirements.md

@@ -25,15 +25,15 @@ _[Back to Market Money Home](./index)_
 /bin
 /config
 /db
-  /data                                     <-- create this folder
-    market_money_development.pgdump         <-- put the file in the data folder
-  seeds.rb                                  <-- seeds.rb is in `/db/` folder, not `/db/data/`
+  /data # <-- create this folder
+    market_money_development.pgdump # <-- put the .pgdump file in the data folder
+  seeds.rb  # <-- seeds.rb is in `/db/` folder, not `/db/data/`
 /lib
 /log
 etc
 ```
 
-  - this file is in a binary format and your browser may try to automatically download the file instead of viewing it
+  - Note that this file is in a **binary format** and your browser may try to automatically download the file instead of viewing it. Also, opening this file in VSCode directly will produce a warning, and a lot of garbled text. It is NOT meant to be human-readable. 
 
 
 4. Set up your `db/seeds.rb` file with the following content:
@@ -46,7 +46,7 @@ system(cmd)
 
 5. Run `rails db:{drop,create,migrate,seed}` and you may see lots of output including some warnings/errors from `pg_restore` that you can ignore. If you're unsure about the errors you're seeing, ask an instructor.
 
-6. Run `rails db:schema:dump` - Check to see that your `schema.rb` exists and has the proper tables/attributes that match the data in Postico. You can do the following to check to see if you have set up rails to effectively communicate with the database.
+6. Run `rails db:schema:dump` . Then, check to see that your `schema.rb` exists and has the proper tables/attributes that match the data in Postico. You can do the following to check to see if you have set up rails to effectively communicate with the database.
   * Add a `market.rb` file to your models directory
   * Create a `Market` class that inherits from `ApplicationRecord`
   * run `rails c` to jump into your rails console.
@@ -60,7 +60,7 @@ system(cmd)
   * market_vendors
 
 
-**NOTE** If your `rails new ...` project name from above is NOT exactly called "market_money" you will need to modify the `cmd` variable below to change the `-d` parameter from `market_money_development` to `<YOUR PROJECT NAME>_development` instead. If you have questions, ask your instructors.
+**NOTE** If your `rails new ...` project name from above is NOT exactly called "market_money" you will need to modify the `cmd` variable to change the `-d` parameter from `market_money_development` to `<YOUR PROJECT NAME>_development` instead. If you have questions, ask your instructors.
 
 ---
 

module3/projects/rails_engine_lite/evaluation.md

@@ -6,7 +6,7 @@ type: project
 ---
 _[Back to Rails Engine Lite Home](./index)_
 
-The 'eval' for this project is going to be a bit different than other projects in the past. We are relying on you to score yourself for this project. To do that, please submit this form. 
+The 'eval' for this project is going to be a bit different than other projects in the past. We are relying on you to score yourself for this project. To do that, please submit [this form](https://forms.gle/1o1u5Ai2UYifwY9cA). 
 
 ## Feedback Session Format
 
@@ -43,11 +43,4 @@ Choose at least one part of your project that you’d like specific feedback on.
 * Exceeds Expectations: Project demonstrates exceptionally well factored code.
 * Meets Expectations: Project demonstrates solid code quality, MVC principles, and uses a serializer for formatting JSON responses.
 * Below Expectations: Project demonstrates some gaps in code quality and/or application of MVC principles.
-* Well Below Expectations: Project demonstrates poor factoring and/or understanding of MVC.
-
-### ActiveRecord/SQL
-
-* Exceeds Expectations: Project makes good use of an advanced ActiveRecord/SQL concept not taught in class
-* Meets Expectations: Project demonstrates good use of ActiveRecord/SQL using minimal ruby to process data that could otherwise be done by the database.
-* Below Expectations: Project makes good use of ActiveRecord, but uses ruby enumerables for more than one query method.
-* Well Below Expectations: Project frequently uses Ruby where ActiveRecord could be used, or fails to use ActiveRecord effectively
+* Well Below Expectations: Project demonstrates poor factoring and/or understanding of MVC.

module3/projects/sweater_weather/index.md

@@ -24,6 +24,30 @@ Your team is working in a service-oriented architecture. The front-end will comm
 
 The project must expose all of the endpoints [listed here](./requirements)
 
+### Pre-Approved Gems
+
+This project will have you to consume multiple APIs - you should do so manually, without the use of SDKs/gems that may make it faster/easier. This is an assessment in part of your ability to read documentation, implement tooling required to test & consume one or more APIs manually, traverse complex external datasets, and refactor your application to do these things as efficiently as possible. 
+
+Here is a list of pre-approved gems you can use on this project: 
+```
+pry, debug, byebug
+simplecov # required
+rspec-rails
+capybara
+launchy
+webmock
+vcr 
+faraday
+jsonapi-serializer # optional
+factorybot
+faker
+bcrypt
+shoulda-matchers
+orderly
+```
+
+If you have questions about a gem that is not on this list, please reach out to your instructors *first*.
+
 ## Evaluation
 
 Your project will be evaluated based on [this rubric](./rubric)