Fix non-markdownified titles in showcase

content-changes.md

@@ -23,6 +23,8 @@ This is no longer a site navigation link and is instead a button along with "Fil
 
 ### Getting Started
 
+* The [Quick Start][] has been completely updated for more consistent heading structure, etc. Also, **I may delete the "deployment" section of the Quick Start** since this a) adds unnecessary length, making the guide less "quick" and b) detracts from the new "hosting and deployment" section, which offers better advice, and c) is redundant with [Hosting on Github](https://hugodocsconcept.netlify.com/hosting-and-deployment/hosting-on-github/). For example, the Quick Start didn't mention that files already written to public are not necessarily erased at build time. This can cause problems with drafts. I think the other options—e.g. Arjen's Wercker tutorial—are more viable and represent better practices for newcomers to Hugo. If future versions of Hugo include baked-in deployment features, I think it's worth reconsidering adding the deployment step back to the Quick Start.
+
 ### Content
 
 ### Themes
@@ -179,4 +181,8 @@ apache license - 60
 
 ## Content Organization: Source
 
-**[See tree.md at the root of this repository](tree.md).**
+**[See tree.md at the root of this repository](tree.md).**
+
+
+
+[Quick Start]: https://hugodocsconcept.netlify.com/getting-started/quick-start/

content/hosting-and-deployment/hosting-on-github.md

@@ -92,8 +92,9 @@ After a short while you'll see the updated contents on your GitHub Pages site.
 
 ### Putting it into a script
 
-To automate these steps, you can create a script _scripts/publish_to_ghpages.sh_ with the following contents:
+To automate these steps, you can create a script with the following contents:
 
+{{% input "publish_to_ghpages.sh" %}}
 ```sh
 #!/bin/sh
 
@@ -125,9 +126,9 @@ hugo
 echo "Updating gh-pages branch"
 cd public && git add --all && git commit -m "Publishing to gh-pages (publish.sh)"
 ```
+{{% /input %}}
 
-This will abort if there are pending changes in the working directory and also makes sure that all previously existing output files are removed.
-Adjust the script to taste, e.g. to include the final push to the remote repository if you don't need to take a look at the gh-pages branch before pushing. Or adding `echo yourdomainname.com >> CNAME` if you set up for your gh-pages to use customize domain.
+This will abort if there are pending changes in the working directory and also makes sure that all previously existing output files are removed. Adjust the script to taste, e.g. to include the final push to the remote repository if you don't need to take a look at the gh-pages branch before pushing. Or adding `echo yourdomainname.com >> CNAME` if you set up for your gh-pages to use customize domain.
 
 ## Deployment with Git 2.4 and Earlier
 
@@ -147,12 +148,12 @@ The other steps are the same as with the worktree approach.
 
 ## Hosting Personal or Organization Pages
 
-As mentioned [in this GitHub's article](https://help.github.com/articles/user-organization-and-project-pages/), besides project pages, you may also want to host a user/organization page. Here are the key differences:
+As mentioned [in this GitHub Help article](https://help.github.com/articles/user-organization-and-project-pages/), you can host a user/organization page in addition to project pages. Here are the key differences in GitHub Pages websites for Users and Organizations:
 
 1. You must use the `username.github.io` naming scheme.
 2. Content from the `master` branch will be used to build and publish your GitHub Pages site.
 
-It becomes much simpler in that case: we'll create two separate repos, one for Hugo's content, and a git submodule with the `public` folder's content in it.
+It becomes much simpler in this case: we'll create two separate repos, one for Hugo's content, and a git submodule with the `public` folder's content in it.
 
 ### Step-by-step Instructions
 

data/sitenavigation.yml

@@ -60,7 +60,7 @@ tutorials:
   url: "tutorials"
   haschildren: true
   sortsubpagesby: "title"
-  desc: "Community-aggregated articles and code examples for approaching different projects  Hugo"
+  desc: "Community-aggregated articles and code examples for approaching different projects with Hugo"
 developertools:
   order: 10
   title: "Developer Tools"

themes/hugodocs/layouts/section/showcase.html

@@ -9,7 +9,7 @@
 		{{$base := .Site.BaseURL}}
 
 		{{- range .Data.Pages.ByPublishDate.Reverse -}}
-		{{$title := .Title}}
+		{{$title := .Title | markdownify}}
 			<li class="showcase-site">
 			<div class="image-wrapper">
 				<a href="{{.Params.sitelink}}" target="_blank">