Remove bower artifacts

README.md

@@ -40,8 +40,7 @@ All exercises live in `exercises` folder. Here's the standard folder structure:
 │  └─ <ExerciseName>.purs
 ├─ test
 │  └─ Main.purs
-├─ packages.dhall
-└─ spago.dhall
+└─ spago.yaml
 ```
 
 Creating a new exercise requires modification to:
@@ -54,9 +53,8 @@ Creating a new exercise requires modification to:
 The remaining files:
 
 - `test/Main.purs` - contains tests
-- `spago.dhall` and `packages.dhall` - these are copied from the template
-  project `template/*.dhall` and should not be directly modified (see the
-  following section)
+- `spago.yaml` - copied from the template project and should not be directly
+  modified (see the following section)
 
 #### Steps for adding a new exercise
 
@@ -68,7 +66,7 @@ The remaining files:
 - Add exercise details to `config.json`
 - Add tests to `test/Main.purs`
 - Add your solution to `examples/src/<ExerciseName>.purs`
-- Run `bin/test.sh` to make sure all tests pass
+- Run `scripts/ci` to make sure all tests pass
 - Commit, push and make a pull request
 - Check that GitHub CI passes
 

reference/implementing-a-concept-exercise.md

@@ -45,17 +45,17 @@ languages
                 ├── src
                 |   └── <NAME>.purs
                 ├── test
-                |   └── Test.purs
-                └── bower.json
+                |   └── Main.purs
+                └── spago.yaml
 </pre>
 
 ## Step 1: Add code files
 
 These are files specific to the PureScript track:
 
 - `src/<NAME>.purs`: the stub implementation file, which is the starting point for students to work on the exercise.
-- `test/Test.purs`: the test suite.
-- `bower.json`: the bower project file.
+- `test/Main.purs`: the test suite.
+- `spago.yaml`: the Spago project configuration.
 - `.meta/Exemplar.purs`: an exemplar implementation that passes all the tests.
 
 ## Step 2: Add documentation files