Merge pull request #230 from justwriteclick/build

Fix duplication issue and add SSG Performance Considerations

Author: annegentle

_learn/00-github-for-docs-files.md

@@ -233,40 +233,13 @@ _site
 .DS_Store
 ```
 
-For Hugo, you want to ignore these files and folders. The `static` folder could be named `public`, depending on your configuration
-```
-static
-.DS_Store
-```
-
-## Ignoring operating system files or generated files
-
-In GitHub repos, you can place a `.gitignore` file that contains the file extensions or folder names that you want to keep out of source control. When a file extension or folder is in the `.gitignore` file, even when you use the `git add .` command, those files and folders are not added to the commit.
-
-This exclusion is useful so that you do not have a lot of difficult merges on output HTML files or operating system tracking files.
-
-For Sphinx, you want to ignore these files and folders to avoid merge conflicts:
-
-```
-build
-.DS_Store
-```
-
-For Jekyll, you want to ignore these files and folders:
-
-```
-_site
-.DS_Store
-```
-
 For Hugo, you want to ignore these files and folders. The `static` folder could be named `public`, depending on your configuration.
 ```
 static
-public # depends on configuration
+public # depends on the configuration
 .DS_Store
 ```
 
 ## Additional resources
-[Learning Git and GitHub resources on help.github.com](https://help.github.com/articles/git-and-github-learning-resources/)
-[GitHub Guides](https://guides.github.com/)
+[Learning Git and GitHub resources on docs.github.com]([https://docs.github.com/en/get-started/quickstart/git-and-github-learning-resources](https://docs.github.com/en/get-started/quickstart/git-and-github-learning-resources))
 [Pro Git](https://git-scm.com/book/en/v2)

_posts/12-ssg-performance.md _learn/12-ssg-performance.md_posts/12-ssg-performance.md renamed to _learn/12-ssg-performance.md

@@ -1,8 +1,9 @@
 ---
 title: "Static Site Generator performance considerations"
+layout: learn
 image:
-  path: /images/so-simple-sample-image-4.jpg
-  thumbnail: /images/site-logo.png
+  path: /images/learn/ssg-performance.png
+  thumbnail: /images/learn/ssg-performance-400×225.png
 ---
 
 When you start building large documentation sites, or gluing together multiple documentation sets, you might look for performance gains in the build time. Having smaller doc sites helps with this, so that you can build with your static site generator systems in parallel, but also look for incremental builds or ways to measure build times to look for areas where the build is slowed down and then find a root cause for the slower performance.