[reproducible-website] 01/03: Add FAQ structure
Valerie R Young
spectranaut at riseup.net
Tue Dec 20 04:03:50 UTC 2016
This is an automated email from the git hooks/post-receive script.
spectranaut-guest pushed a commit to branch faq
in repository reproducible-website.
commit 5ebbe2f6b2875d8dbbf2b5f851fc8a44cf8ce780
Author: Valerie R Young <spectranaut at riseup.net>
Date: Mon Dec 19 18:39:26 2016 -0500
Add FAQ structure
---
_config.yml | 3 +++
_data/faq.yml | 12 ++++++++++++
_faq/distribution.md | 13 +++++++++++++
_faq/myths.md | 13 +++++++++++++
_faq/testing.md | 13 +++++++++++++
_faq/upstream.md | 13 +++++++++++++
_faq/user.md | 13 +++++++++++++
_layouts/faq.html | 15 +++++++++++++++
faq.html | 47 +++++++++++++++++++++++++++++++++++++++++++++++
9 files changed, 142 insertions(+)
diff --git a/_config.yml b/_config.yml
index 883e8fd..38a01ca 100644
--- a/_config.yml
+++ b/_config.yml
@@ -15,6 +15,9 @@ collections:
output: true
events:
output: true
+ faq:
+ output: true
+
exclude:
- README
diff --git a/_data/faq.yml b/_data/faq.yml
new file mode 100644
index 0000000..1ecbb2b
--- /dev/null
+++ b/_data/faq.yml
@@ -0,0 +1,12 @@
+developer:
+ - title: ...and I want to make my software reproducible.
+ link: upstream
+ - title: ...and I want to distribute reproducible binaries.
+ link: distributor
+ - title: ...and I want to test reproduciblity in continious integration.
+ link: testing
+ - title: ...and I am worried about retaining build information in my binaries.
+ link: myths
+user:
+ - title: ...and I want to learn about the benefits of reproducibility.
+ link: user
diff --git a/_faq/distribution.md b/_faq/distribution.md
new file mode 100644
index 0000000..3c8857e
--- /dev/null
+++ b/_faq/distribution.md
@@ -0,0 +1,13 @@
+---
+title: Distribution and Packaging FAQ
+layout: faq
+permalink: /faq/distributor/
+---
+
+## Why should I, as a distributor of software, care about reproducible builds?
+
+TODO: answer
+
+## How can I, as a distribution of software, achieve reproducible builds?
+
+TODO: answer
diff --git a/_faq/myths.md b/_faq/myths.md
new file mode 100644
index 0000000..8117a14
--- /dev/null
+++ b/_faq/myths.md
@@ -0,0 +1,13 @@
+---
+title: Retaining build information FAQ
+layout: faq
+permalink: /faq/myths/
+---
+
+## What if I need to include a build path in my binary?
+
+TODO: answer
+
+## What if I need to include a build timestamp in my binary?
+
+TODO: answer
diff --git a/_faq/testing.md b/_faq/testing.md
new file mode 100644
index 0000000..6ea731a
--- /dev/null
+++ b/_faq/testing.md
@@ -0,0 +1,13 @@
+---
+title: Continuous Testing FAQ
+layout: faq
+permalink: /faq/testing/
+---
+
+## What are the benefits of continuously testing the reproduciblity of my software project?
+
+TODO: answer
+
+## How can I do it?
+
+TODO: answer
diff --git a/_faq/upstream.md b/_faq/upstream.md
new file mode 100644
index 0000000..84630fd
--- /dev/null
+++ b/_faq/upstream.md
@@ -0,0 +1,13 @@
+---
+title: Developer FAQ
+layout: faq
+permalink: /faq/upstream/
+---
+
+## Why should I write reproducible code?
+
+TODO: answer
+
+## How do I write reproducible code?
+
+TODO: answer
diff --git a/_faq/user.md b/_faq/user.md
new file mode 100644
index 0000000..18d3102
--- /dev/null
+++ b/_faq/user.md
@@ -0,0 +1,13 @@
+---
+title: User FAQ
+layout: faq
+permalink: /faq/user/
+---
+
+## What is reproducible builds?
+
+TODO: answer
+
+## Why should I care?
+
+TODO: answer
diff --git a/_layouts/faq.html b/_layouts/faq.html
new file mode 100644
index 0000000..319a5bb
--- /dev/null
+++ b/_layouts/faq.html
@@ -0,0 +1,15 @@
+---
+layout: default
+---
+<div class="post">
+ <div class="row">
+ <div class="twelve columns">
+ <header class="post-header">
+ <h1>{{ page.title }}</h1>
+ </header>
+ <article class="post-content text">
+ {{ content }}
+ </article>
+ </div>
+ </div>
+</div>
diff --git a/faq.html b/faq.html
new file mode 100644
index 0000000..2df3cf6
--- /dev/null
+++ b/faq.html
@@ -0,0 +1,47 @@
+---
+layout: page
+title: FAQ
+permalink: /faq/
+---
+
+<div class="row">
+ <div class="four columns title">
+ <h2>General</h2>
+ </div>
+ <div class="eight columns text doc-index">
+ <h4>What is a "reproducible build"?</h4>
+ <p>
+ Example answer: See definition here [link]
+ </p>
+ <h4>Have we achieved reproducible build?</h4>
+ <p>
+ Example answer: Yes! Many projects have. If you would like to see specific details for projects see here: (link)
+ </p>
+ <h4>How can I help reproducible builds?</h4>
+ <p>
+ Example answer: You can donate money somehow! Or if your are developer, check out the these things.
+ </p>
+ </div>
+</div>
+
+<div class="row" style="margin-top: 1rem;">
+ <div class="four columns title">
+ <h2>I am a developer</h2>
+ </div>
+ <div class="eight columns text doc-index">
+ {% for section in site.data.faq.developer %}
+ <h4><a href="{{ section.link | prepend: site.baseurl }}">{{ section.title }}</a></h4>
+ {% endfor %}
+ </div>
+</div>
+
+<div class="row" style="margin-top: 1rem;">
+ <div class="four columns title">
+ <h2>I am a user</h2>
+ </div>
+ <div class="eight columns text doc-index">
+ {% for section in site.data.faq.user %}
+ <h4><a href="{{ section.link | prepend: site.baseurl }}">{{ section.title }}</a></h4>
+ {% endfor %}
+ </div>
+</div>
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-website.git
More information about the Reproducible-commits
mailing list