Created git structure, .github template and initial project commit.

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,51 @@
+---
+name: Bug Report
+about: Create a report to help us fix a bug you have found.
+---
+
+### Describe the Bug
+
+_A clear and concise description of what the bug is._
+
+### To Reproduce
+
+_Steps to reproduce the behaviour:_
+
+  1. Go to '...'
+  1. Click on '...'
+  1. Scroll down to '...'
+  1. See error
+
+### Expected behaviour
+
+_A clear and concise description of what you expected to happen._
+
+### Screenshots
+
+_If applicable, add screenshots to help explain your problem._
+
+![Example Screenshot][screenshot-1]
+
+### Specifications
+
+**Desktop (please complete the following information):**
+
+  - Hardware: [e.g. MacBook Pro (13-inch, Mid 2012)] 
+  - OS: [e.g. macOS 10.13.4]
+  - Browser: [e.g. Chrome, Safari, IE]
+  - Version: [e.g. 61, 11.1, 9]
+
+**Smartphone (please complete the following information):**
+
+  - Device: [e.g. iPhoneX]
+  - OS: [e.g. iOS11.1]
+  - Browser: [e.g. stock browser, safari]
+  - Version: [e.g. 22]
+
+### Additional Context
+
+_Add any other context about the problem here._
+
+[//]: # (Add links to any screenshots or other relevant information below)
+
+[screenshot-1]: https://ws3.sinaimg.cn/large/006tKfTcly1fr6kihddwhj30b008j74g.jpg

.github/ISSUE_TEMPLATE/CUSTOM.md

@@ -0,0 +1,25 @@
+---
+name: General Report
+about: A general issue report to help improve our project.
+---
+
+### Expected Behaviour 
+
+_What did you expect to happen when you encountered this issue?_
+
+### Actual Behaviour
+
+_What actually happened instead?_
+
+### Steps to Reproduce the Problem
+
+_Detail the steps below to help us reproduce the problem you encountered._
+
+  1. Go to '...'
+  1. Click on '...'
+  1. Scroll down to '...'
+  1. See error
+
+### Specifications
+
+_The version of the project you are using, operating system, hardware and anything else that you think may be relevant to reporting this problem._

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,20 @@
+---
+name: Feature Request
+about: Suggest an idea or feature for this project.
+---
+
+### Is your feature request related to a problem? Please describe.
+
+_A clear and concise description of what the problem is. e.g. I'm always frustrated when [...]_
+
+### Describe the solution you'd like
+
+_A clear and concise description of what you want to happen._
+
+### Describe alternatives you've considered
+
+_A clear and concise description of any alternative solutions or features you've considered._
+
+### Additional Context
+
+_Add any other context or screenshots about the feature request here._

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,41 @@
+## Checklist
+
+_Confirm you have completed the following actions prior to submitting this PR._
+
+ - [ ] There is an existing issue report for this PR.
+ - [ ] I have forked this project.
+ - [ ] I have created a feature branch.
+ - [ ] My changes have been committed.
+ - [ ] I have pushed my changes to the branch.
+
+## Title
+
+_Give your PR a short title summarising the patch, bug fix or feature._
+
+## Description
+
+_Ensure the PR description clearly describes the problem and solution and provide as much relevant information as possible._
+
+## Issue Resolution
+
+_Tell us which issue this PR fixes._
+
+This Pull Request Fixes #
+
+## Proposed Changes
+
+_List your proposed changes below._
+
+ - 
+ - 
+ - 
+
+## New or Changed Features
+
+_Does this PR provide new or changed features or enhancements? If so, what is included in this PR?_
+
+ - 
+ - 
+ - 
+
+@justinhartman

.gitignore

@@ -0,0 +1 @@
+.git/

CHANGELOG.md

@@ -0,0 +1,12 @@
+# Change-Log for ${domain}
+
+Below is a detailed change-log, along with specific tasks completed, for each
+version released to date for ${domain}.
+
+## Version 0.0.1
+### ??/??/2018
+
+- [#new](#new)
+    + Initial Release
+- [#enhancement](#enhancement)
+- [#bugfix](#bugfix)

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,35 @@
+# 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/Automated-LAMP-with-trusted-localhost-SSL/issues
+[new-issue]: https://github.com/justinhartman/Automated-LAMP-with-trusted-localhost-SSL/issues/new