diff --git a/config.org b/config.org
index 5e06e1d..63fd32c 100644
--- a/config.org
+++ b/config.org
@@ -1,4 +1,35 @@
#+title: PWL Arch Linux Config
+#+OPTIONS: toc:3
+
+* Table of Contents :toc:
+- [[#prerequisites][Prerequisites]]
+- [[#literate-file-headers][Literate File Headers]]
+ - [[#updatesh][update.sh]]
+ - [[#packagestxt][packages.txt]]
+ - [[#pathsh][path.sh]]
+ - [[#aliassh][alias.sh]]
+ - [[#doom-emacs][Doom Emacs]]
+- [[#package-management][Package Management]]
+ - [[#arch-and-aur-packages][Arch and AUR Packages]]
+- [[#base-system][Base System]]
+ - [[#arch-linux][Arch Linux]]
+ - [[#networking][Networking]]
+ - [[#man-pages-and-texinfo][Man Pages and Texinfo]]
+- [[#desktop-environments-and-window-manager][Desktop Environments and Window Manager]]
+ - [[#lightdm][LightDM]]
+ - [[#gnome][GNOME]]
+- [[#doom-emacs-1][Doom Emacs]]
+ - [[#installation][Installation]]
+ - [[#doom-modules][Doom Modules]]
+ - [[#general-configuration][General Configuration]]
+ - [[#multilanguage-spellcheck][Multilanguage Spellcheck]]
+ - [[#latex][LaTeX]]
+ - [[#org-mode][Org Mode]]
+ - [[#python][Python]]
+- [[#shells][Shells]]
+ - [[#aliases][Aliases]]
+- [[#themeing][Themeing]]
+ - [[#doom-emacs-2][Doom Emacs]]
* Prerequisites
- Completed Arch Linux Installation
@@ -18,6 +49,7 @@
#+end_src
** packages.txt
+contains all Arch and AUR packages
#+begin_src shell :tangle pkg-list.txt
# DO NOT EDIT THIS FILE DIRECTLY
# This is a file generated from a literate programing source file
@@ -26,22 +58,203 @@
#+end_src
+** path.sh
+contains all modifications to the path variables
+#+begin_src shell :tangle path.sh
+#!/bin/sh
+# DO NOT EDIT THIS FILE DIRECTLY
+# This is a file generated from a literate programing source file
+# You should make any changes there and regenerate it from Emacs org-mode
+# using org-babel-tangle (C-c C-v t)
+
+#+end_src
+
+** alias.sh
+#+begin_src shell :tangle alias.sh
+#!/bin/sh
+# DO NOT EDIT THIS FILE DIRECTLY
+# This is a file generated from a literate programing source file
+# You should make any changes there and regenerate it from Emacs org-mode
+# using org-babel-tangle (C-c C-v t)
+
+#+end_src
+
+** Doom Emacs
+We start by simply defining the standard headers used by the three files. These headers come from the initial files generated by =doom install=, and contain either some Emacs-LISP relevant indicators like =lexical-binding=, or instructions about the contents of the file.
+*** init.el
+#+html: init.el
+#+begin_src emacs-lisp :tangle ~/.config/doom/init.el
+;;; init.el -*- lexical-binding: t; -*-
+
+;; DO NOT EDIT THIS FILE DIRECTLY
+;; This is a file generated from a literate programing source file
+;; You should make any changes there and regenerate it from Emacs org-mode
+;; using org-babel-tangle (C-c C-v t)
+
+;; This file controls what Doom modules are enabled and what order they load
+;; in. Remember to run 'doom sync' after modifying it!
+
+;; NOTE Press 'SPC h d h' (or 'C-h d h' for non-vim users) to access Doom's
+;; documentation. There you'll find a "Module Index" link where you'll find
+;; a comprehensive list of Doom's modules and what flags they support.
+
+;; NOTE Move your cursor over a module's name (or its flags) and press 'K' (or
+;; 'C-c c k' for non-vim users) to view its documentation. This works on
+;; flags as well (those symbols that start with a plus).
+;;
+;; Alternatively, press 'gd' (or 'C-c c d') on a module to browse its
+;; directory (for easy access to its source code).
+#+end_src
+#+html: packages.el
+#+begin_src emacs-lisp :tangle ~/.config/doom/packages.el
+;; -*- no-byte-compile: t; -*-
+;;; $DOOMDIR/packages.el
+
+;; DO NOT EDIT THIS FILE DIRECTLY
+;; This is a file generated from a literate programing source file
+;; You should make any changes there and regenerate it from Emacs org-mode
+;; using org-babel-tangle (C-c C-v t)
+
+;; To install a package with Doom you must declare them here and run 'doom sync'
+;; on the command line, then restart Emacs for the changes to take effect -- or
+;; use 'M-x doom/reload'.
+
+;; To install SOME-PACKAGE from MELPA, ELPA or emacsmirror:
+;;(package! some-package)
+
+;; To install a package directly from a remote git repo, you must specify a
+;; `:recipe'. You'll find documentation on what `:recipe' accepts here:
+;; https://github.com/raxod502/straight.el#the-recipe-format
+;;(package! another-package
+;; :recipe (:host github :repo "username/repo"))
+
+;; If the package you are trying to install does not contain a PACKAGENAME.el
+;; file, or is located in a subdirectory of the repo, you'll need to specify
+;; `:files' in the `:recipe':
+;;(package! this-package
+;; :recipe (:host github :repo "username/repo"
+;; :files ("some-file.el" "src/lisp/*.el")))
+
+;; If you'd like to disable a package included with Doom, you can do so here
+;; with the `:disable' property:
+;;(package! builtin-package :disable t)
+
+;; You can override the recipe of a built in package without having to specify
+;; all the properties for `:recipe'. These will inherit the rest of its recipe
+;; from Doom or MELPA/ELPA/Emacsmirror:
+;;(package! builtin-package :recipe (:nonrecursive t))
+;;(package! builtin-package-2 :recipe (:repo "myfork/package"))
+
+;; Specify a `:branch' to install a package from a particular branch or tag.
+;; This is required for some packages whose default branch isn't 'master' (which
+;; our package manager can't deal with; see raxod502/straight.el#279)
+;;(package! builtin-package :recipe (:branch "develop"))
+
+;; Use `:pin' to specify a particular commit to install.
+;;(package! builtin-package :pin "1a2b3c4d5e")
+
+;; Doom's packages are pinned to a specific commit and updated from release to
+;; release. The `unpin!' macro allows you to unpin single packages...
+;;(unpin! pinned-package)
+;; ...or multiple packages
+;;(unpin! pinned-package another-pinned-package)
+;; ...Or *all* packages (NOT RECOMMENDED; will likely break things)
+;;(unpin! t)
+#+end_src
+#+html: config.el
+#+begin_src emacs-lisp :tangle ~/.config/doom/config.el
+;;; $DOOMDIR/config.el -*- lexical-binding: t; -*-
+
+;; DO NOT EDIT THIS FILE DIRECTLY
+;; This is a file generated from a literate programing source file
+;; You should make any changes there and regenerate it from Emacs org-mode
+;; using org-babel-tangle (C-c C-v t)
+
+;; Place your private configuration here! Remember, you do not need to run 'doom
+;; sync' after modifying this file!
+
+;; Some functionality uses this to identify you, e.g. GPG configuration, email
+;; clients, file templates and snippets.
+;; (setq user-full-name "John Doe"
+;; user-mail-address "john@doe.com")
+
+;; Doom exposes five (optional) variables for controlling fonts in Doom. Here
+;; are the three important ones:
+;;
+;; + `doom-font'
+;; + `doom-variable-pitch-font'
+;; + `doom-big-font' -- used for `doom-big-font-mode'; use this for
+;; presentations or streaming.
+;;
+;; They all accept either a font-spec, font string ("Input Mono-12"), or xlfd
+;; font string. You generally only need these two:
+;; (setq doom-font (font-spec :family "monospace" :size 12 :weight 'semi-light)
+;; doom-variable-pitch-font (font-spec :family "sans" :size 13))
+
+;; There are two ways to load a theme. Both assume the theme is installed and
+;; available. You can either set `doom-theme' or manually load a theme with the
+;; `load-theme' function. This is the default:
+;; (setq doom-theme 'doom-one)
+
+;; If you use `org' and don't want your org files in the default location below,
+;; change `org-directory'. It must be set before org loads!
+;; (setq org-directory "~/org/")
+
+;; This determines the style of line numbers in effect. If set to `nil', line
+;; numbers are disabled. For relative line numbers, set this to `relative'.
+;; (setq display-line-numbers-type t)
+
+;; Here are some additional functions/macros that could help you configure Doom:
+;;
+;; - `load!' for loading external *.el files relative to this one
+;; - `use-package!' for configuring packages
+;; - `after!' for running code after a package has loaded
+;; - `add-load-path!' for adding directories to the `load-path', relative to
+;; this file. Emacs searches the `load-path' when you load packages with
+;; `require' or `use-package'.
+;; - `map!' for binding new keys
+;;
+;; To get information about any of these functions/macros, move the cursor over
+;; the highlighted symbol at press 'K' (non-evil users must press 'C-c c k').
+;; This will open documentation for it, including demos of how they are used.
+;;
+;; You can also try 'gd' (or 'C-c c d') to jump to their definition and see how
+;; they are implemented.
+#+end_src
+#+html: