update the docs

Author: Mahmoudz

docs/_settings/config.toml

@@ -47,44 +47,44 @@ googleAnalytics = ""
 # ------- MENU START -----------------------------------------
 
 [[menu.main]]
-	name   = "Introduction"
+	name   = "Overview"
 	url    = "/"
-	weight = 0
+	weight = 1
 
 [[menu.main]]
-	name   = "Getting started"
+	name   = "Getting Started"
 	url    = "getting-started/"
-	weight = 10
+	weight = 2
 
 [[menu.main]]
 	name   = "Documentation"
 	url    = "documentation/"
-	weight = 20
+	weight = 3
 
 [[menu.main]]
 	name   = "Related Projects"
 	url    = "related-projects/"
-	weight = 30
+	weight = 4
 
 [[menu.main]]
 	name   = "Help & Questions"
 	url    = "help/"
-	weight = 40
+	weight = 5
 
 [[menu.main]]
 	name   = "Contributing"
 	url    = "contributing/"
-	weight = 50
+	weight = 6
 
 [[menu.main]]
 	name   = "License"
 	url    = "license/"
-	weight = 60
+	weight = 7
 
 # ------- MENU END -----------------------------------------
 
 [blackfriday]
-	smartypants	= false
-	fractions = false
-	smartDashes = false
-	plainIDAnchors = false
+	smartypants	= true
+	fractions = true
+	smartDashes = true
+	plainIDAnchors = true

docs/_settings/content/contributing/index.md

@@ -1,7 +1,7 @@
 ---
 title: Contributing
 type: index
-weight: 50
+weight: 6
 ---
 
 
@@ -143,4 +143,4 @@ from the main (upstream) repository:
 
 
 <br>
-### Happy Coding :)
+### Happy Coding :)

docs/_settings/content/documentation/index.md

@@ -1,7 +1,7 @@
 ---
 title: Documentation
 type: index
-weight: 20
+weight: 3
 ---
 
 
@@ -1308,15 +1308,15 @@ Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requ
 ## Improve speed on MacOS
 
 Sharing code into Docker containers with osxfs have very poor performance compared to Linux. You can get around this issue by using NFS to share your files betwen your host and your container.
-  
+
 > How to share files using NFS (d4m-nfs)
 
 [d4m-nfs](https://github.com/IFSight/d4m-nfs) automatically mount NFS volume instead of osxfs one.
 
 1) Update the Docker [File Sharing] preferences:
 
-Click on the Docker Icon > Preferences > (remove everything form the list except `/tmp`). 
- 
+Click on the Docker Icon > Preferences > (remove everything form the list except `/tmp`).
+
 2) Restart Docker.
 
 3) Clone the [d4m-nfs](https://github.com/IFSight/d4m-nfs) repository to your `home` directory.
@@ -1354,7 +1354,7 @@ docker-compose up -d nginx mysql
 
 <br>
 <a name="Common-Problems"></a>
-## Common Problems 
+## Common Problems
 
 *Here's a list of the common problems you might face, and the possible solutions.*
 

docs/_settings/content/getting-started/index.md

@@ -1,13 +1,11 @@
 ---
-date: 2017
-title: Getting started
-weight: 10
+title: Getting Started
+type: index
+weight: 2
 ---
 
 
 
-
-<a name="Requirements"></a>
 ## Requirements
 
 - [Git](https://git-scm.com/downloads)
@@ -16,8 +14,6 @@ weight: 10
 
 
 
-
-<a name="Installation"></a>
 ## Installation
 
 Choose the setup the best suits your needs.
@@ -114,8 +110,6 @@ Do the same for each project `project2.conf`, `project3.conf`,...
 
 
 
-
-<a name="Usage"></a>
 ## Usage
 
 **Read Before starting:**
@@ -183,12 +177,3 @@ DB_HOST=mysql
 
 If you need a special support. Contact me, more details in the [Help & Questions](#Help) section.
 
-
-
-
-
-
-
-
-
-

docs/_settings/content/help/index.md

@@ -1,7 +1,7 @@
 ---
 title: Help & Questions
 type: index
-weight: 40
+weight: 5
 ---
 
 Join the chat room on [Gitter](https://gitter.im/LaraDock/laradock) and get help and support from the community.

docs/_settings/content/index.md

@@ -1,7 +1,7 @@
 ---
-title: Welcome to Laradock
+title: Overview
 type: index
-weight: 0
+weight: 1
 ---
 
 LaraDock strives to make the PHP development experience easier and faster.

docs/_settings/content/license/index.md

@@ -1,7 +1,7 @@
 ---
 title: License
 type: index
-weight: 60
+weight: 7
 ---
 
 [MIT License](https://github.com/laradock/laradock/blob/master/LICENSE) (MIT)

docs/_settings/content/related-projects/index.md

@@ -1,7 +1,7 @@
 ---
 title: Related Projects
 type: index
-weight: 30
+weight: 4
 ---
 
 

docs/contributing/index.html

@@ -180,9 +180,9 @@
 
 
 
-<a  title="Introduction" href="http://laradock.io/">
+<a  title="Overview" href="http://laradock.io/">
 
-	Introduction
+	Overview
 </a>
 
 
@@ -198,9 +198,9 @@
 
 
 
-<a  title="Getting started" href="http://laradock.io/getting-started/">
+<a  title="Getting Started" href="http://laradock.io/getting-started/">
 
-	Getting started
+	Getting Started
 </a>
 
 
@@ -336,26 +336,26 @@ <h1>Contributing </h1>
 
 
 
-<h2 id="guidelines:d680e8a854a7cbad6d490c445cba2eba">Guidelines</h2>
+<h2 id="guidelines">Guidelines</h2>
 
 <p>Your contribution is more than welcome.</p>
 
-<h3 id="got-a-question-or-problem:d680e8a854a7cbad6d490c445cba2eba">Got a Question or Problem?</h3>
+<h3 id="got-a-question-or-problem">Got a Question or Problem?</h3>
 
 <p>If you have questions about how to use LaraDock, please direct your questions to the discussion on <a href="https://gitter.im/LaraDock/laradock">Gitter</a>. If you believe your question could help others, then consider opening an <a href="https://github.com/laradock/laradock/issues">Issue</a> (it will be labeled as Question).</p>
 
-<h3 id="found-an-issue:d680e8a854a7cbad6d490c445cba2eba">Found an Issue?</h3>
+<h3 id="found-an-issue">Found an Issue?</h3>
 
 <p>If you find a bug in the source code or a mistake in the documentation, you can help us by
 submitting an <a href="https://github.com/laradock/laradock/issues">Issue</a>. Even better you can submit a Pull Request with a fix.</p>
 
-<h3 id="want-a-feature:d680e8a854a7cbad6d490c445cba2eba">Want a Feature?</h3>
+<h3 id="want-a-feature">Want a Feature?</h3>
 
 <p>You can request a new feature by submitting an <a href="https://github.com/laradock/laradock/issues">Issue</a> (it will be labeled as Feature Suggestion). If you would like to implement a new feature then consider submitting a Pull Request.</p>
 
-<h2 id="coding-guidelines:d680e8a854a7cbad6d490c445cba2eba">Coding Guidelines</h2>
+<h2 id="coding-guidelines">Coding Guidelines</h2>
 
-<h3 id="support-new-software:d680e8a854a7cbad6d490c445cba2eba">Support new Software</h3>
+<h3 id="support-new-software">Support new Software</h3>
 
 <ul>
 <li><p>Create folder with the software name.</p></li>
@@ -371,7 +371,7 @@ <h3 id="support-new-software:d680e8a854a7cbad6d490c445cba2eba">Support new Softw
 <li><p>Add the software in the <code>Readme</code>.</p></li>
 </ul>
 
-<h3 id="edit-existing-software:d680e8a854a7cbad6d490c445cba2eba">Edit existing Software</h3>
+<h3 id="edit-existing-software">Edit existing Software</h3>
 
 <ul>
 <li><p>Open the software (container) folder.</p></li>
@@ -384,17 +384,17 @@ <h3 id="edit-existing-software:d680e8a854a7cbad6d490c445cba2eba">Edit existing S
 <li><p>Make sure to update the <code>Readme</code> in case you made any changes.</p></li>
 </ul>
 
-<h2 id="issue-pr-submission-guidelines:d680e8a854a7cbad6d490c445cba2eba">Issue/PR Submission Guidelines</h2>
+<h2 id="issue-pr-submission-guidelines">Issue/PR Submission Guidelines</h2>
 
-<h3 id="submitting-an-issue:d680e8a854a7cbad6d490c445cba2eba">Submitting an Issue</h3>
+<h3 id="submitting-an-issue">Submitting an Issue</h3>
 
 <p>Before you submit your issue search the archive, maybe your question was already answered.</p>
 
-<p>If your issue appears to be a bug, and hasn't been reported, open a new issue.
+<p>If your issue appears to be a bug, and hasn&rsquo;t been reported, open a new issue.
 Help us to maximize the effort we can spend fixing issues and adding new
 features, by not reporting duplicate issues.</p>
 
-<h3 id="before-submitting-a-pull-request-pr:d680e8a854a7cbad6d490c445cba2eba">Before Submitting a Pull Request (PR)</h3>
+<h3 id="before-submitting-a-pull-request-pr">Before Submitting a Pull Request (PR)</h3>
 
 <p>Always Test everything and make sure its working:</p>
 
@@ -403,7 +403,7 @@ <h3 id="before-submitting-a-pull-request-pr:d680e8a854a7cbad6d490c445cba2eba">Be
 <li>Before editing anything:
 
 <ul>
-<li>Test building the container (docker-compose build --no-cache container-name) build with no cache first.</li>
+<li>Test building the container (docker-compose build &ndash;no-cache container-name) build with no cache first.</li>
 <li>Test running the container with some other containers in real app and see of everything is working fine.</li>
 </ul></li>
 <li>Now edit the container (edit section by section and test rebuilding the container after every edited section)
@@ -414,12 +414,12 @@ <h3 id="before-submitting-a-pull-request-pr:d680e8a854a7cbad6d490c445cba2eba">Be
 </ul></li>
 </ul>
 
-<h3 id="submitting-a-pr:d680e8a854a7cbad6d490c445cba2eba">Submitting a PR</h3>
+<h3 id="submitting-a-pr">Submitting a PR</h3>
 
 <p>Consider the following guidelines:</p>
 
 <ul>
-<li><p>Search <a href="https://github.com/laradock/laradock/pulls">GitHub</a> for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.</p></li>
+<li><p>Search <a href="https://github.com/laradock/laradock/pulls">GitHub</a> for an open or closed Pull Request that relates to your submission. You don&rsquo;t want to duplicate effort.</p></li>
 
 <li><p>Make your changes in a new git branch:</p>
 
@@ -454,7 +454,7 @@ <h3 id="submitting-a-pr:d680e8a854a7cbad6d490c445cba2eba">Submitting a PR</h3>
 
 <p><em>WARNING. Squashing or reverting commits and forced push thereafter may remove GitHub comments on code that were previously made by you and others in your commits.</em></p>
 
-<h3 id="after-your-pr-is-merged:d680e8a854a7cbad6d490c445cba2eba">After your PR is merged</h3>
+<h3 id="after-your-pr-is-merged">After your PR is merged</h3>
 
 <p>After your pull request is merged, you can safely delete your branch and pull the changes
 from the main (upstream) repository:</p>
@@ -483,7 +483,7 @@ <h3 id="after-your-pr-is-merged:d680e8a854a7cbad6d490c445cba2eba">After your PR
 
 <p><br></p>
 
-<h3 id="happy-coding:d680e8a854a7cbad6d490c445cba2eba">Happy Coding :)</h3>
+<h3 id="happy-coding">Happy Coding :)</h3>
 
 
 			<aside class="copyright" role="note">