diff --git a/config/exercise_readme.go.tmpl b/config/exercise_readme.go.tmpl
deleted file mode 100644
index 106e2f61..00000000
--- a/config/exercise_readme.go.tmpl
+++ /dev/null
@@ -1,42 +0,0 @@
-# {{ .Spec.Name }}
-
-{{ .Spec.Description -}}
-{{- with .Hints }}
-{{ . }}
-{{ end }}
-## Getting Started
-
-Make sure you have read [D page](http://exercism.io/languages/d) on
-exercism.io.  This covers the basic information on setting up the development
-environment expected by the exercises.
-
-## Passing the Tests
-
-Get the first test compiling, linking and passing by following the [three
-rules of test-driven development](http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd).
-Create just enough structure by declaring namespaces, functions, classes,
-etc., to satisfy any compiler errors and get the test to fail.  Then write
-just enough code to get the test to pass.  Once you've done that,
-uncomment the next test by moving the following line past the next test.
-
-```D
-static if (all_tests_enabled)
-```
-
-This may result in compile errors as new constructs may be invoked that
-you haven't yet declared or defined.  Again, fix the compile errors minimally
-to get a failing test, then change the code minimally to pass the test,
-refactor your implementation for readability and expressiveness and then
-go on to the next test.
-
-Try to use standard D facilities in preference to writing your own
-low-level algorithms or facilities by hand.  [DRefLanguage](https://dlang.org/spec/spec.html)
-and [DReference](https://dlang.org/phobos/index.html) are references to the D language and D standard library.
-
-{{ with .Spec.Credits }}
-## Source
-
-{{ . }}
-{{ end }}
-## Submitting Incomplete Solutions
-It's possible to submit an incomplete solution so you can see how others have completed the exercise.
diff --git a/exercises/shared/.docs/help.md b/exercises/shared/.docs/help.md
new file mode 100644
index 00000000..d1870f52
--- /dev/null
+++ b/exercises/shared/.docs/help.md
@@ -0,0 +1,8 @@
+# Help
+
+To get help if you're having trouble, you can use one of the following resources:
+
+- [DRefLanguage](https://dlang.org/spec/spec.html) contains the D language specification
+- [DReference](https://dlang.org/phobos/index.html) contains the D standard library documentation
+- [/r/dlang](https://www.reddit.com/r/dlang) is the D subreddit.
+- [StackOverflow](http://stackoverflow.com/questions/tagged/d) can be used to search for your problem and see if it has been answered already. You can also ask and answer questions.
diff --git a/exercises/shared/.docs/tests.md b/exercises/shared/.docs/tests.md
new file mode 100644
index 00000000..a299d920
--- /dev/null
+++ b/exercises/shared/.docs/tests.md
@@ -0,0 +1,29 @@
+# Tests
+
+You can run the tests by running the following command in the exercise's directory:
+
+```bash
+dub test
+```
+
+## Passing the Tests
+
+Get the first test compiling, linking and passing by following the [three
+rules of test-driven development](http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd).
+Create just enough structure by declaring namespaces, functions, classes,
+etc., to satisfy any compiler errors and get the test to fail. Then write
+just enough code to get the test to pass. Once you've done that,
+uncomment the next test by moving the following line past the next test.
+
+```D
+static if (all_tests_enabled)
+```
+
+This may result in compile errors as new constructs may be invoked that
+you haven't yet declared or defined. Again, fix the compile errors minimally
+to get a failing test, then change the code minimally to pass the test,
+refactor your implementation for readability and expressiveness and then
+go on to the next test.
+
+Try to use standard D facilities in preference to writing your own
+low-level algorithms or facilities by hand.