- Linting (HTML): Use double-quotes for attributes, remove redundant type=text/css,

indent/lbs, consistent non-use of HTML namespace, consistent indents, consistent charset
    casing
- Linting (Markdown): Add `.remarkrc`, use proper hierarchical headings, use consistent
    heading format, trailing spaces
- `composer.json`: consistent property spacing
- License: Add `.txt` extension, update copyright date, and reflect type (MIT) in file name
- Credits: Add self
- npm: Add `package.json` (version 3.0.0-alpha.1 for npm release only; just reserving name)

docs/ReleaseInstructions.md

@@ -1,11 +1,11 @@
-Creating a new svg-edit release
-============
+# Creating a new svg-edit release
 
 ## Update the main project
 
   1. Update the VERSION variable in Makefile.
-  2. Update the CHANGES file with a summary of all changes.
-  3. Commit these changes with `git commit -m "Updating Makefile and CHANGES for release X.Y"`.
+  2. Update `version` in `package.json`
+  3. Update the CHANGES file with a summary of all changes.
+  4. Commit these changes with `git commit -m "Updating Makefile and CHANGES for release X.Y"`.
 
 The above steps can be done on a fork and committed via a pull request.
 
@@ -33,6 +33,10 @@ The above steps can be done on a fork and committed via a pull request.
 
 You will need to be a member of the SVGEdit GitHub group to do this step.
 
+## Publish to npm
+
+1. `npm publish`
+
 ## Update the project docs
 
-  Update `README.md` with references and links to the shiny new release.
+Update `README.md` with references and links to the shiny new release.