Fixes issue where css, fonts and images aren't loading.

CHANGELOG.md

@@ -0,0 +1,34 @@
+# Change-Log for Apache Error Pages
+
+Below is a detailed change-log, along with specific tasks completed, for each version released to date for Apache Error Pages.
+
+## Version 1.0.1 (14/05/2018)
+
+- [#new](#new)
+  - Added `CHANGELOG.md`, `CODE_OF_CONDUCT.md` and `CONTRIBUTING.md` files.
+- [#enhancement](#enhancement)
+  - Checked in Visual Studio Code workspace file for users of VS Code.
+  - Install instructions now included in `README.md` file.
+  - Updated `README.md` file with minifying setup included.
+- [#bugfix](#bugfix)
+  - Set absolute path to css folder (`/ErrorPages/css/`) to ensure that the resources load when running on a production server.
+  - Rebuilt all `/dist/` files with the new changes.
+
+## Version 1.0.0 (13/05/2018)
+
+Grab everything you need from the `/dist/` folder. All other files support the creation of the files in this folder.
+
+- [#new](#new)
+  - HTML was minified but JavaScript is still unminified.
+  - CSS has been minified although I am unclear what the advantage has been. (?)
+- [#enhancement](#enhancement)
+  - If you're insterested, there is a script that does the minification from source. This file is contained in [src/scripts/minify][script]. Simply run that file and it will:
+    - Delete the `/dist/css/` folder.
+    - Delete all the error pages (`rm -f ../dist/*.html`).
+    - Recreate the `/dist/css/` folder.
+    - Minify the HTML for all files in the `/src/` directory.
+    - Minify the CSS for all the files in `/src/css/` directory.
+    - Output the HTML and CSS to the `/dist/` folder.
+- [#bugfix](#bugfix)
+
+[script]: src/scripts/minify

CODE_OF_CONDUCT.md

@@ -0,0 +1,88 @@
+# Contributor Covenant Code of Conduct
+
+## Table of Contents
+
+- [Our Pledge](#our-pledge)
+- [Our Standards](#our-standards)
+- [Our Responsibilities](#our-responsibilities)
+- [Scope](#scope)
+- [Enforcement](#enforcement)
+- [Attribution](#attribution)
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as 
+contributors and maintainers pledge to making participation in our project and 
+our community a harassment-free experience for everyone, regardless of age, 
+body size, disability, ethnicity, gender identity and expression, level of 
+experience, nationality, personal appearance, race, religion, or sexual 
+identity and orientation.
+
+## Our Standards
+
+Examples of behaviour that contributes to creating a positive environment 
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behaviour by participants include:
+
+* The use of sexualised language or imagery and unwelcome sexual attention or 
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic 
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a 
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable 
+behaviour and are expected to take appropriate and fair corrective action in 
+response to any instances of unacceptable behaviour.
+
+Project maintainers have the right and responsibility to remove, edit, or 
+reject comments, commits, code, wiki edits, issues, and other contributions 
+that are not aligned to this Code of Conduct, or to ban temporarily or 
+permanently any contributor for other behaviours that they deem inappropriate, 
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces 
+when an individual is representing the project or its community. Examples of 
+representing a project or community include using an official project e-mail 
+address, posting via an official social media account, or acting as an 
+appointed representative at an online or offline event. Representation of a 
+project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behaviour may be 
+reported by contacting the project team [by clicking here][email]. The project 
+team will review and investigate all complaints, and will respond in a way 
+that it deems appropriate to the circumstances. The project team is obligated 
+to maintain confidentiality with regard to the reporter of an incident. 
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good 
+faith may face temporary or permanent repercussions as determined by other 
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], 
+version 1.4, available at 
+[http://contributor-covenant.org/version/1/4][version].
+
+[//]: # (Make sure to change the email address below to your)
+[//]: # (project-specific email.)
+
+[email]: mailto:justin@hartman.me?subject=Contributor+Covenant+Code+of+Conduct
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,27 @@
+# How to Contribute to This Project
+
+## Did You Find a Bug?
+
+- **Ensure the bug was not already reported** by searching on GitHub under [Issues][issues].
+- If you're unable to find an open issue addressing the problem, [open a new one][new-issue]. Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behaviour that is not occurring.
+
+## Did You Write a Patch That Fixes a Bug?
+
+- Open a new GitHub pull request with the patch.
+  - Fork this project
+  - Create your feature branch: `git checkout -b my-new-feature`
+  - Commit your changes: `git commit -am 'Add some feature'`
+  - Push to the branch: `git push origin my-new-feature`
+  - Submit a pull request :tada:
+- Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
+
+## Do You Intend to Add a New Feature or Change an Existing One?
+
+- Suggest your change as a [new issue][new-issue] using the label `enhancement`, **BEFORE** you start writing code.
+
+Thanks for contributing! :heart:
+
+[//]: # (Simply change the URL's below to your own project information)
+
+[issues]: https://github.com/justinhartman/Apache-Error-Pages/issues
+[new-issue]: https://github.com/justinhartman/Apache-Error-Pages/issues/new