Merge pull request #109 from sajattack/master

document the components of redox

src/SUMMARY.md

@@ -33,6 +33,7 @@
     - [GUI](./explore/gui.md)
 
 - [The design](./design/design.md)
+    - [Components](./design/components.md)
     - [URLs, schemes and resources](./design/urls_schemes_resources.md)
         - [URLs](./design/url/urls.md)
             - [Aren't they weakly typed?]()

src/design/components.md

+Components of Redox
+===================
+
+Redox is made up of several discrete components. 
+
+* ion - shell
+* TFS/RedoxFS - filesystem
+* kernel 
+* drivers
+* orbital - DE/WM/Display Server
+
+## Orbital subcomponents
+* orbterm - terminal
+* orbdata - images, fonts, etc.
+* orbaudio - audio
+* orbutils - bunch of applications
+* orblogin - login prompt
+* orbtk - like gtk but orb
+* orbfont - font rendering library
+* orbclient - display client 
+* orbimage - image rendering library 
+
+## Core Applications
+* Sodium - text editor
+* orbutils
+  * background
+  * browser
+  * calculator
+  * character map
+  * editor
+  * file manager
+  * launcher
+  * viewer
+

src/userspace/porting/cross_compiling.md

+Cross-compiling
+===============
+
+Cross-compiling a program for Redox is easy thanks to the Redox Cookbook. To get started, navigate to the cookbook folder in the Redox git repository. Build scripts in the cookbook are called recipes, so naturally they reside in the recipes folder. In this example, we'll be cross-compiling foo. Let's make a folder for our recipe.
+
+```sh
+$ cd recipes
+$ mkdir foo
+```
+
+Now open your favourite text editor and create a file called recipe.sh. If you like, you can base your script off one of the other ones in the recipes folder. Here is our recipe.sh for foo:
+
+```
+```