Update file names

niqjohnson · niqjohnson · commit c054fdb0be46 · 2019-01-04T16:05:37.000-05:00
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,9 @@
 All notable changes to this project will be documented in this file.
 
+## 2019-01-04
+
+- Renamed some pages to better reflect their content
+
 ## 2017-11-08
 
 - Add PyPI guide
diff --git a/README.md b/README.md
@@ -26,14 +26,14 @@ browser support standards.
 - [Building your project's front-end](guides/build.md)
 - [Code review guide](guides/code-reviews.md)
 - [Documenting your work](guides/documentation.md)
-- [Creating CommonJS modules](guides/javascript-modules-commonjs.md)
+- [Creating CommonJS modules](guides/creating-commonjs-modules.md)
 - [Git and GitHub](guides/git.md)
-- [Authoring, testing, and publishing npm modules](guides/npm.md)
+- [Authoring, testing, and publishing npm modules](guides/authoring-npm-modules.md)
 - [Publishing Python packages to PyPI](guides/pypi.md)
 - [Screen reader differences](guides/screen-reader-differences.md)
-- [Front-end testing](guides/testing.md)
-- [Browser testing with Sauce Labs](guides/sauce-labs.md)
-- [Using npm modules in projects](guides/npm-usage.md)
+- [Front-end testing](guides/front-end-testing.md)
+- [Browser testing with Sauce Labs](guides/browser-testing-with-sauce-labs.md)
+- [Using npm modules in projects](guides/using-npm-modules-in-projects.md)
 - [Unit testing Django and Wagtail](guides/unittesting-django-wagtail.md)
 
 ## Tools
diff --git a/guides/authoring-npm-modules.md b/guides/authoring-npm-modules.md
@@ -2,7 +2,7 @@
 
 Whenever possible, we should write JavaScript as small modules that can be published to [npm](https://www.npmjs.com/). This document includes guidelines for authoring and publishing these modules.
 
-*If you are looking for guidelines on using Node modules, see [npm-usage.md](npm-usage.md).*
+*If you are looking for guidelines on using Node modules, see [using-npm-modules-in-projects.md](using-npm-modules-in-projects.md).*
 
 The [full list of CFPB published node modules](https://www.npmjs.com/~cfpb) is availble on npm.
 
diff --git a/guides/browser-support.md b/guides/browser-support.md
@@ -119,7 +119,7 @@ browsers:
 We use a mix of [Sauce Labs](https://saucelabs.com/) and
 [localtunnel](https://localtunnel.github.io/www/) to manually test our site.
 Be sure to review both the
-[testing](https://github.com/cfpb/development/blob/master/guides/testing.md)
+[testing](https://github.com/cfpb/development/blob/master/guides/front-end-testing.md)
 and [accessibility](https://github.com/cfpb/development/blob/master/guides/accessibility.md)
 guides when reviewing sites locally.
 
diff --git a/guides/browser-testing-with-sauce-labs.md b/guides/browser-testing-with-sauce-labs.md
diff --git a/guides/creating-commonjs-modules.md b/guides/creating-commonjs-modules.md
diff --git a/guides/front-end-testing.md b/guides/front-end-testing.md
@@ -6,13 +6,13 @@ Extol the [testing pyramid](https://docs.google.com/presentation/d/1NFjgq5SbQ4cr
 
 ## Manual testing & browser support QA
 
-Refer to the [Sauce Labs Guide](sauce-labs.md) for instructions on using Sauce Labs to manually test your application in a range of browsers and virtual machines.
+Refer to the [Sauce Labs Guide](browser-testing-with-sauce-labs.md) for instructions on using Sauce Labs to manually test your application in a range of browsers and virtual machines.
 
 ## Unit tests
 
 If your code has logic, it should have unit tests. As seen in the pyramid, unit tests should comprise the majority of your tests. Why? Unit tests can be executed quickly, they can be easily automated, they're maintainable and they promote good practices by requiring your code to be written in concise, modular chunks.
 
-A unit test verifies that a single discrete piece of your codebase works as expected. That "piece" could be a JavaScript function, a CommonJS/AMD module or some other unit of functionality. It's vaguely defined but don't let that scare you. Start by choosing one of the test frameworks below and writing tests for individual JavaScript methods. There are many guides about writing [JavaScript](http://alistapart.com/article/writing-testable-javascript) [unit](http://www.smashingmagazine.com/2012/06/27/introduction-to-javascript-unit-testing/) [tests](http://www.htmlgoodies.com/beyond/javascript/testing-javascript-using-the-jasmine-framework.html) that serve as great introductions. At CFPB we like to separate our JavaScript into discrete [npm modules](https://github.com/cfpb/development/blob/master/guides/npm.md). This makes testing easier because each module includes self-contained tests.
+A unit test verifies that a single discrete piece of your codebase works as expected. That "piece" could be a JavaScript function, a CommonJS/AMD module or some other unit of functionality. It's vaguely defined but don't let that scare you. Start by choosing one of the test frameworks below and writing tests for individual JavaScript methods. There are many guides about writing [JavaScript](http://alistapart.com/article/writing-testable-javascript) [unit](http://www.smashingmagazine.com/2012/06/27/introduction-to-javascript-unit-testing/) [tests](http://www.htmlgoodies.com/beyond/javascript/testing-javascript-using-the-jasmine-framework.html) that serve as great introductions. At CFPB we like to separate our JavaScript into discrete [npm modules](https://github.com/cfpb/development/blob/master/guides/authoring-npm-modules.md). This makes testing easier because each module includes self-contained tests.
 
 ### Test frameworks
 - [Jest](https://jestjs.io) is a comprehensive testing framework for Node and browser JavaScript.
diff --git a/guides/using-npm-modules-in-projects.md b/guides/using-npm-modules-in-projects.md
@@ -2,7 +2,7 @@
 
 This document provides general guidelines for using [npm](https://www.npmjs.com/) with CFPB projects.
 
-*If you are looking for guidelines on publishing Node modules, see [npm.md](npm.md).*
+*If you are looking for guidelines on publishing Node modules, see [authoring-npm-modules.md](authoring-npm-modules.md).*
 
 Show me the code! Do you prefer seeing how something works instead of
 instructions? If so, check out this pull request to the Amortize module. Each
diff --git a/standards/javascript.md b/standards/javascript.md
@@ -40,7 +40,7 @@ exist.
 
 This style guide assumes you're using a module system such as [CommonJS][1],
 [AMD][2], [ES6 Modules][3], or any other kind of module system. If you are
-using CommonJS, refer to the [CommonJS guide](javascript-modules-commonjs.md)
+using CommonJS, refer to the [CommonJS guide](creating-commonjs-modules.md)
 for structuring your modules. Modules systems provide individual scoping,
 avoid leaks to the `global` object, and improve code base organization by
 **automating dependency graph generation**, instead of having to resort to
