From 7133fd85167c4f33d305d54408825fd6b06ecf31 Mon Sep 17 00:00:00 2001 From: Alex Chaffee Date: Sat, 24 Mar 2018 15:36:30 -0400 Subject: [PATCH] docs(seed): clarify repack, fix a couple broken links --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 332a0aebaf..7d97028d4e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -493,7 +493,7 @@ These HTML files are self-contained and run their own tests -- open a browser JS > **Note**: These in-browser tests should work for simple JavaScript challenges. But other types of challenges may not fare so well. For HTML challenges, challenge tests assume that the solution HTML is the only HTML on the whole page, so jQuery selectors may select seed *and* solution elements. For React / Modern JS challenges, we would need to transpile JSX or ES6 before running the tests. -`npm run repack` gathers up the unpacked/edited HTML files into challenge-block JSON files. After running repack, use `git diff` to see the changes. +`npm run repack` gathers up the unpacked/edited HTML files into challenge-block JSON files. After running repack, use `git diff` to see the changes in your console, and `npm run seed` to see the changes in your local freeCodeCamp app instance. When editing the unpacked files, you must only insert or edit lines between comment fences like `` and ``. In descriptions, you can insert a paragraph break with ``.