working on some docs

docs/manual/BODY.adoc

@@ -1,4 +1,5 @@
 include::USER.adoc[]
 include::DEV.adoc[]
+include::FAQ.adoc[]
 
-include::FOOT.adoc[]
+include::FOOT.adoc[]

docs/manual/FAQ.adoc

@@ -0,0 +1,9 @@
+= FAQ
+
+[partintro]
+.What good is software if nobody understands it?
+--
+Here you will find some answers to Frequently Asked Questions I've received about this project. Please be sure to check this list before opening a bug report or sending a patch!
+--
+
+include::faq/INDEX.adoc[]

docs/manual/USER.adoc

@@ -18,6 +18,6 @@ This manual will give you the information you need to build your very own live G
 --
 
 include::user/GETTING_STARTED.adoc[]
-
+include::user/IMPORTANT_CONCEPTS.adoc[]
 include::user/PROJECT_LAYOUT.adoc[]
 

docs/manual/dev/FUNCTIONS.adoc

@@ -3,3 +3,6 @@ text
 
 == Moar Functions
 and more text.
+
+
+

docs/manual/faq/INDEX.adoc

@@ -0,0 +1 @@
+include::WHYARCH.adoc[]

docs/manual/faq/WHYARCH.adoc

@@ -0,0 +1,5 @@
+== Why Arch Linux?
+Because it's a very easy-to-use, simple, https://wiki.archlinux.org/[well-documented] distro. It's no-frills and incredibly flexible/customizable, and can be made rather slim (and is out of the box, in fact). It's also very friendly to run as a chroot inside any other distro or as a chroot host to any other distro.
+
+Plus they have tarballs all ready for chroot easily accessible.
+

docs/manual/user/GETTING_STARTED.adoc

@@ -32,5 +32,50 @@ or native git protocol:
 The git protocol is much faster, but at a cost of lessened security.
 
 === Prerequisites
-Here's a complete list of prerequisites:
+This is a list of software you'll need available to build with BDisk.
 
+TIP: Your distro's package manager should have most if not all of these available, so it's unlikely you'll need to install from source.
+
+NOTE: Some versions may be higher than actually needed (especially _gcc_).
+
+CAUTION: You will need at least about *15GB* of free disk space, depending on what options you enable. Each architecture chroot (i.e. x86_64, i686) is about 3.5GB after a build using the default package set (more on that later), each architecture release tarball (what we use to build the chroots) is approximately 115MB each, and each squashed image per architecture is 1.1GB (if you use the default package set). If you don't understand what this means quite yet, don't worry- we'll go into more detail later on.  Just know that you'll need a fair bit of free disk space.
+
+==== Necessary
+These are needed for using BDisk.
+
+* https://www.python.org/[Python] (>=3.5)
+* https://github.com/dosfstools/dosfstools[dosfstools]
+* http://gcc.gnu.org[gcc (multilib)] (>=6.x)
+* http://gcc.gnu.org[gcc-libs (multilib)] (>=6.x)
+* http://libburnia-project.org[libisoburn]
+* http://squashfs.sourceforge.net[squashfs-tools] (>=4.2)
+
+These are required Python modules:
+
+* https://pypi.python.org/pypi/humanize[Humanize]
+* http://jinja.pocoo.org/[Jinja2]
+* https://pypi.python.org/pypi/psutil[PSUtil]
+* https://pypi.python.org/pypi/validators[Validators]
+
+==== Optional
+While not strictly necessary, these will greatly enhance your BDisk usage. I've included some reasons why you might want to install them.
+
+NOTE: If you do not wish to install any of these or cannot install them, be sure to disable the relevant options in the `build.ini` file (we'll talk about that later).
+
+* https://git-scm.com/[git]
+** For autodetection of version, automatically making commits for your project, etc.
+* https://www.gnupg.org/[gpg/gnupg] (>=2.1.11)
+** For automatically signing releases, verifying downloaded files from the Internet as part of the build process, etc. It's okay if you don't have a key set up!
+* https://rsync.samba.org/[rsync]
+** For syncing built ISOs to a fileserver, syncing to a remote iPXE server, syncing to a traditional PXE/TFTP server, etc.
+
+These are optional Python modules:
+
+* https://pypi.python.org/pypi/GitPython[GitPython]
+** (Same reasons as _git_)
+* https://pypi.python.org/pypi/pygpgme[PyGPGME]
+** (Same reasons as _gpg/gnupg_)
+* https://pypi.python.org/pypi/patch[Patch]
+** For branding iPXE environments per your `build.ini`.
+* https://pypi.python.org/pypi/pyOpenSSL[PyOpenSSL]
+** To set up a PKI when building iPXE; used to create trusted/verified images.

docs/manual/user/IMPORTANT_CONCEPTS.adoc

@@ -0,0 +1,10 @@
+== Important Concepts
+If this is your first foray into building live distros, there are some terms and concepts we need to understand first. This will simplify the process later on.
+
+=== Terms
+
+An *operating system* is what your programs (email client, web browser, etc.) run on.
+
+There are two basic types of booting systems that communicate between the *hardware* (the physical computer itself and its components) and the operating system: https://en.wikipedia.org/wiki/BIOS[*BIOS*] (Basic Input/Output System) which has been around for quite some time and the newer https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface[*UEFI*] (Unified Extensible Firmware Interface). Don't worry, you don't need to memorize what they're acronyms for and there won't be an exam- just remember that BIOS is an older technology and UEFI is the newer one- and that they operate differently.
+
+*GNU/Linux*, sometimes just referred to as _Linux_ (And there is a difference between the terminologies, but it's nuanced. You are welcome to https://www.gnu.org/gnu/linux-and-gnu.en.html[read up on it] though!), is an example of an operating system. Other examples include _Windows_, _macOS_ (previously _OS X_), _iOS_, _Android_, and a whole slew of others.