Revert "Updated community resources page"

This reverts commit d0999b6.

Author: nickclark2016

.github/ISSUE_TEMPLATE/resource-request-template.md

@@ -0,0 +1,12 @@
+---
+name: Resource request template
+about: Used to request resources.
+title: "[RESOURCE REQUEST]"
+labels: ''
+assignees: ''
+
+---
+
+### What topic do you want covered?
+
+### Do you have a preference for API or language used to discuss the topic?

LaTexMD/index.md

@@ -0,0 +1,16 @@
+# Using LaTex in markdown
+
+Since GitHub markdown doesn't natively support LaTex, we use markdeep.  
+Specifically, a slightly modified version of markdeep to look like GitHub markdown.
+
+Using markdeep is relatively straight forward. You write your markdown as you normally would, and use the special markdeep syntax for its extra features (the syntax is explained on [their website](https://casual-effects.com/markdeep/)).  
+Besides that you add the script snippets at the bottom of your markdown file, and save it with the extension `.md.html`. Note that the index file must be named `index.html` if you're using markdeep features.
+The script snippets can be found in [template.md.html](template.md.html).
+
+# Requirements
+
+1. You are not allowed to use a different style sheet, we want all pages to look uniform across the website.
+2. In the script tags use **relative** paths to the style sheet and script.  
+This is so that the markdown can be viewed in the browser without a webserver. Which also makes it easier to write as you can test it locally.
+3. When linking to normal markdown, use paths ending in `filename.html` and not `filename.md`, this is to make the browsing experience on GitHub pages leaner. When the path ends with `index.md` just supply the folder path.  
+As far as I know there's no way to link to both as with normal GitHub markdown, where we can just point to the .md file and have it be transformed to the html path in GitHub pages. So we opt for linking to the generated HTML versions here.

LaTexMD/template.md.html

@@ -0,0 +1,20 @@
+# This is the LaTex template
+
+The stuff below will make sure the markdown gets transformed to viewable markdown in your browser.
+
+This markdown flavor has a few differences from GitHub markdown:
+* Nested lists don't have to be aligned, 2 spaces are enough.
+* To insert a single newline, use <code>&lt;br/&gt;</code> instead of 2 spaces and a return.
+* To insert raw HTML as inline code use raw code tags with escaped greater/smaller than brackets.
+* To insert raw HTML as code between 3 backticks, escape greater/smaller than brackets.<br/>
+  The escapes are `&amp;lt;` for < and `&amp;gt;` for >.
+
+Now for some LaTex: $\vec{c}=\vec{ac}a+\sum_{j=0}^{c}\vec{c}+\max\left(\vec{n}\cdot\frac{\vec{l_p}_j-\vec{p}}{\|\vec{l_p}_j-\vec{p}},0\right)\vec{l_c}_j\left(\frac{i_j}{\left(\vec{l_p}_j-\vec{p}\right)\cdot\left(\vec{l_p}_j-\vec{p}\right)}\right)\vec{sc}$.
+
+For more information on the features see https://casual-effects.com/markdeep/
+
+<!-- Markdeep: -->
+<style class="fallback">body{visibility:hidden;white-space:pre;font-family:monospace}</style>
+<script src="../scripts/markdeep.js"></script>
+<script>window.alreadyProcessedMarkdeep||(document.body.style.visibility="visible")</script>
+<link rel="stylesheet" href="../css/github-markdown.css"/>

_config.yml

@@ -0,0 +1,10 @@
+title: Graphics Programming Resources
+plugins:
+    - jekyll-relative-links
+relative-links:
+    enabled: true
+    collections: true
+include:
+    - CONTRIBUTING.md
+    - CODE_OF_CONDUCT.md
+    - LICENSE.md