Add few pages to documentation

Author: meh

_layouts/documentation.html

@@ -32,6 +32,10 @@
     {% endfor %}
 </div>
 
+{% if page.stub %}
+    <div class="warning">This page is a <b>stub</b>, please help expanding and cleaning it.</div>
+{% endif %}
+
 <div class="documentation">
     {{ content }}
 </div>

about.md

@@ -3,7 +3,7 @@ title: About Distrø
 layout: default
 ---
 
-Distrø aims to be THE distribution.
+Distrø aims to be **THE** distribution.
 
 Kernel agnostic, libc agnostic, compiler agnostic.
 

css/default.css

@@ -144,6 +144,14 @@ ul.contents {
     }
   }
 
+  .warning {
+    text-align: center;
+    margin-top: 5px;
+    color: #b21818;
+    border-bottom: 2px solid #dd1818;
+    border-top: 2px solid #dd1818;
+  }
+
   .post {
     .header {
       h2 {

css/default.scss

@@ -0,0 +1,13 @@
+---
+title: General Concepts
+layout: documentation
+
+lang: en
+---
+
+This section covers some general concepts with which you should be familiar when working
+with Distrø.
+
+{:class="contents"}
++ [Packages](/docs/en/general-concepts/packages.html)
++ [Repositories](/docs/en/general-concepts/repositories.html)

docs/en/general-concepts.md

@@ -0,0 +1,41 @@
+---
+title: Packages
+layout: documentation
+
+lang: en
+stub: true
+---
+
+Packages
+========
+In Distrø packages have various variables, like `description`, `homepage`, `license` and such,
+these variables are used by packo to help you find the packages you want to install.
+
+Tags
+----
+Having tags instead of categories makes searching and definition a lot easier, just think about
+the fact that for example, you can mask all packges made by GNU, and use in this way bsd alternatives
+or something else.
+
+You can apply various configuration to packages with certain tags, in this way configuration
+becomes super easy.
+
+Features
+--------
+Features are similiar to Gentoo USE flags, they specify (who would know) features for a package,
+for example if a package can be installed with a gtk interface you can set the gtk feature (in
+the environment or in your profile) and it will be installed with it.
+
+Each package has a set of enableable features and packages can define what features can be enabled
+at the same time to not get broken packages.
+
+Flavor
+------
+The flavor of a package is somewhat similar to features, but it's a general change to the package,
+for example there are some default flavors that can be set, `vanilla` means the package has no
+additional patches and contains what it would contain with a standard installation, then you can
+set `documentation` to enable the documentation, or it will be stripped from the package, same
+goes for `headers`. Then there's the `debug` flavor that adds debug symbols to the package.
+
+Every package can set different flavors, for example `rubinius-9999` has the flavor `hydra` which
+uses the hydra branch instead of master.

docs/en/general-concepts/packages.md

@@ -0,0 +1,52 @@
+---
+title: Repositories
+layout: documentation
+
+lang: en
+stub: true
+---
+
+Repositories
+============
+Distrø and packø are designed to easily support multiple repositories from different sources
+and types.
+
+All of this because I believe that everyone should be able to easily create alternatives and
+completely different distributions from the same technology.
+
+Obviously th choices of the package manager aren't changeable, which means you have to like Ruby
+or deal with it.
+
+There are three types of repositories, each one with their special capabilities.
+
+Source repositories
+-------------------
+Source repositories are the base of Distrø and they're pretty similar to Gentoo trees.
+
+When installing from a source repository the package gets compiled and transformed into an
+intallable package (usually a `.pko`).
+
+The binary package is then installed like it was coming from a binary package.
+
+Binary repositories
+-------------------
+Binary repositories get generated from source repositories and usually have only limited sets
+of features/flavor and just a single version.
+
+To install from a binary repository you have to specify the binary flavor or specify to install
+a package from a specific repository.
+
+Multiple binary repositories can easily co-exist if you specify as default `REPOSITORY` the
+default binary repository you're using, for example if you use the stable core2 repository
+you can add the unstable core2 repository and install only few selected packages from that
+repository without moving everything to unstable when you update.
+
+Virtual repositories
+--------------------
+A virtual repository is a Ruby script that states how to look for packages, dependencies and how to
+install and uninstall a package.
+
+Virtual repositories are really useful for wrapping other package managers to use by packo, for example
+CPAN or gem, usually other package managers have to create by hand ebuilds/whatever for every wanted
+gem, with packø you can simply add the virtual/gem repository and install packages through gem
+transparently, dependencies and such are then coordinated by packø in an automagical way.

docs/en/general-concepts/repositories.md

@@ -27,7 +27,9 @@ Contents
 
 {:class="contents"}
 * [Contributing](/docs/en/contributing.html#documentation)
+* [General concepts](/docs/en/general-concepts.html)
+* + [Packages](/docs/en/general-concepts/packages.html)
+* + [Repositories](/docs/en/general-concepts/repositories.html)
 * [Packø](/docs/packo/index.html)
 * + [Quickstart Rbuild Guide](/docs/en/packo/quickstart.html)
-* + [General concepts](/docs/en/packo/general-concepts.html)
 * + [Building Systems](/docs/en/packo/building-systems.html)

docs/en/index.md

@@ -0,0 +1,13 @@
+---
+title: Building Systems
+layout: documentation
+
+lang: en
+---
+
+This section covers various building systems which are needed to know when writing
+rbuilds.
+
+- [Autotools](/docs/en/packo/building-systems/autotools.html)
+- [CMake](/docs/en/packo/building-systems/cmake.html)
+- [Rake](/docs/en/packo/building-systems/rake.html)