forked from ProjectAliceDev/aoserror
-
Notifications
You must be signed in to change notification settings - Fork 0
/
faq.html
executable file
·28 lines (25 loc) · 1.92 KB
/
faq.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
---
faq:
- question: What is Jekyll?
answer: Jekyll is a simple, blog-aware, static site generator. It takes a template directory containing raw text files in various formats, runs it through a converter (like Markdown) and our Liquid renderer, and spits out a complete, ready-to-publish static website suitable for serving with your favorite web server.
- question: What is front matter?
answer: The front matter is where Jekyll starts to get really cool. Any file that contains a YAML front matter block will be processed by Jekyll as a special file. The front matter must be the first thing in the file and must take the form of valid YAML set between triple-dashed lines
- question: What is a static file?
answer: A static file is a file that does not contain any YAML front matter. These include images, PDFs, and other un-rendered content.
- question: What is a collection?
answer: Not everything is a post or a page. Maybe you want to document the various methods in your open source project, members of a team, or talks at a conference. Collections allow you to define a new type of document that behave like Pages or Posts do normally, but also have their own unique properties and namespace.
- question: What is a data file?
answer: In addition to the built-in variables available from Jekyll, you can specify your own custom data that can be accessed via the Liquid templating system. Jekyll supports loading data from YAML, JSON, and CSV files located in the `_data` directory. Note that CSV files must contain a header row.
---
<h1>FAQ</h1>
<section class="faq">
<ul>
{% for item in page.faq %}
<li><a href="#{{ item.question | slugify }}">{{ item.question }}</a></li>
{% endfor %}
</ul>
{% for item in page.faq %}
<h2 id="{{ item.question | slugify}}">{{ item.question }}<a class="header-link" href="#{{ item.question | slugify }}">#</a></h2>
{{ item.answer | markdownify }}
{% endfor %}
</section>