diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 32eb494..fb95673 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,20 +1,3 @@
 # Contributing
 
-## C++
-
-Doogie follows the [Chromium Style Guide](https://chromium.googlesource.com/chromium/src/+/master/styleguide/c++/c++.md)
-for C++ code except for anything listed below.
-
-* Forward decls only when necessary. No need to worry about compile times (yet).
-* We use a singleton here and there as necessary
-* Avoid slots, use method references
-* Class decls are usually public, protected, and private. But here they are public, signals, public slots, protected,
-  protected slots, private, and private slots
-* Prefer default by-value capture on local lambdas
-* Obviously, some styles have to be broken to confirm to Qt, e.g. name format for overridden methods
-* No file-level comments
-* Passing around raw pointers is ok in Qt land, at least for now
-
-## JavaScript
-
-For JS code in tests, follow [Standard Style](https://www.npmjs.com/package/standard).
\ No newline at end of file
+See the [contributing section in the user guide](docs/guide/develop.md#contributing).
\ No newline at end of file
diff --git a/README.md b/README.md
index fa03256..e313bb8 100644
--- a/README.md
+++ b/README.md
@@ -1,95 +1,7 @@
 
 # Doogie
 
-A power browser
+A Chromium-based web browser with tree-style pages. MIT licensed.
 
-## Building
-
-### Windows Prerequisites
-
-Before running the build script on Windows, you must have the prerequisites:
-
-* Latest Qt (5.x) installed w/ `qmake.exe` on the `PATH`
-* Latest CMake installed w/ `cmake.exe` on the `PATH`
-* Latest Python (2.x) installed w/ `python.exe` on the `PATH`
-* Latest Go installed w/ `go.exe` on the `PATH`
-* [MSVC 2015 Build Tools](http://landinghub.visualstudio.com/visual-cpp-build-tools) installed w/ the following
-  executed to put 64-bit VC compiler on the `PATH`:
-  `"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64`
-* Latest [Windows 64-bit standard dist of CEF](http://opensource.spotify.com/cefbuilds/index.html#windows64_builds)
-  extracted w/ `CEF_DIR` environment variable set to the base CEF extracted dir
-* This repo cloned w/ the shell at the `src` folder
-
-### Linux Prerequisites
-
-(NOTE: Linux support is not yet complete)
-
-Before running the build script on Windows, you must have the prerequisites:
-
-* Latest Qt (5.x) installed w/ `qmake` on the `PATH`
-* Latest CMake installed w/ `cmake` on the `PATH`
-* Latest Python (2.x) installed w/ `python` on the `PATH`
-* Latest Go installed w/ `go` on the `PATH`
-* Latest GCC installed w/ `gcc` and `g++` on the `PATH`
-* Latest Make installed w/ `make` on the `PATH`
-* Latest [Linux 64-bit standard dist of CEF](http://opensource.spotify.com/cefbuilds/index.html#linux64_builds)
-  extracted w/ `CEF_DIR` environment variable set to the base CEF extracted dir
-* Latest GTK 2.x installed and on the library path
-* This repo cloned w/ the shell at the `src` folder
-
-### MacOS Prerequisites
-
-(TODO)
-
-### Running Build
-
-The application uses the CEF C++ wrapper, which can be built via:
-
-    go run build.go build-cef
-
-Now the application can easily be run via:
-
-    go run build.go run
-
-That will run the `debug` version. For the `release` version, run:
-
-    go run build.go run release
-
-Internally, that just builds and runs the exe. To just build, call `build` instead. To package a deployment artifact
-from a previously run build, `package` is used. For example, to package a `release` deployment artifact from a
-previously run `release` build, run:
-
-    go run build.go package release
-
-Once complete, the package(s) will in `release/package` (e.g. doogie.zip in Windows)
-
-### Testing
-
-There are two types of tests, unit and integration tests at `tests/unit` and `tests/integration` respectively.
-
-#### Integration Tests
-
-The integration tests are not yet integrated in `build.go`. The tests are written in node.js. Make sure you have the
-latest LTS release of node installed and navigate to `src/tests/integration`. To setup the test infrastructure, run:
-
-    npm install
-
-To run the tests, make sure a debug instance of Doogie is running then run
-
-    npm test
-
-#### Unit Tests
-
-Assuming CEF is built (see the first "Running Build" step), unit tests can be run with:
-
-    go run build.go unit-test
-
-Like the `run` command, the `unit-test` command can be given a `release` target, otherwise it defaults to `debug`.
-
-### Development
-
-To do a lint check of the code, have the
-[Chromium depot_tools](https://chromium.googlesource.com/chromium/tools/depot_tools.git) cloned somewhere and set the
-`DEPOT_TOOLS_DIR` env var to the dir. Then run:
-
-    go run build.go lint
+See the [website](https://cretz.github.io/doogie/) or look directly at the guide pages in [docs/guide/](docs/guide/) for
+things like [build instructions](docs/guide/develop.md#building).
\ No newline at end of file
diff --git a/docs/404.html b/docs/404.html
index ab5a52c..91eea10 100644
--- a/docs/404.html
+++ b/docs/404.html
@@ -1,5 +1,6 @@
 ---
-layout: default
+layout: page
+title: Not Found
 ---
 
 <style type="text/css" media="screen">
diff --git a/docs/_layouts/default.html b/docs/_layouts/default.html
index 55bc1bb..239cdff 100644
--- a/docs/_layouts/default.html
+++ b/docs/_layouts/default.html
@@ -4,7 +4,7 @@
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0"> 
     <meta name="keywords" content="doogie, browser, web browser, chromium, tree style" />
-    <meta name="description" content="Doogie is a Chromium-based power browser with tree-style pages" />
+    <meta name="description" content="Doogie is a Chromium-based web browser with tree-style pages" />
     <link rel="shortcut icon" href="{{ site.github.url }}/img/doogie-icon.png">
     <title>
       {% if page.title %}{{ page.title }} - Doogie{% else %}Doogie - A Power Browser{% endif %}
diff --git a/docs/_layouts/guide.html b/docs/_layouts/guide.html
index 79b1851..ea65801 100644
--- a/docs/_layouts/guide.html
+++ b/docs/_layouts/guide.html
@@ -2,8 +2,20 @@
 layout: page
 ---
 
-<!-- Super simple hiding menu on mobile -->
+<!-- Guide-specific CSS -->
 <style type="text/css">
+  /* Don't let the images stretch the width */
+  img {
+    max-width: 100%;
+    max-height: 100%;
+  }
+
+  /* Move code blocks out a bit */
+  pre {
+    margin-left: 20px;
+  }
+
+  /* Super-simple hiding menu on mobile */
   @media screen and (max-width: 500px) {
     .guide-menu {
       display: none;
diff --git a/docs/guide/browser.md b/docs/guide/browser.md
index 62976c7..e32a85d 100644
--- a/docs/guide/browser.md
+++ b/docs/guide/browser.md
@@ -5,22 +5,79 @@ title: Browser Usage
 
 # Browser Usage
 
+![Browser Area](../img/screenshot-browser-area.png)
+
+The central area of Doogie is the browser window which changes depending upon which browser is current in the
+[page tree](page-tree). The top of the page tree has an address bar and buttons for navigating and reloading the page.
+Hovering over a link will show the URL for the link at the bottom of the browser area.
+
 ## Navigation
 
-### Address Bar
+![Navigation Bar](../img/screenshot-navigation-bar.png)
+
+In the top bar, there are buttons for navigating backwards and forwards which are disabled if there are no more pages in
+that direction. By holding down the mouse button on either button, a list will appear that shows all pages that can be
+jumped to. The back button may also be triggered by pressing `Ctrl+PgDn`, `Ctrl+Shift+PgUp`, or `Backspace` (while
+an edit field is not focused in the browser). The front button may also be triggered by pressing `Ctrl+PgUp`,
+`Ctrl+Shift+PgDn`, or `Shift+Backspace` (whild an edit field is not focused in the browser).
+
+When there is not a page loading, there is a refresh button to the right of the address bar. Pressing this button will
+refresh the page, utilizing the cache if available. This can also be triggered via `F5`. Pressing `Ctrl` while clicking
+the button, pressing `Ctrl+F5`, or pressing `Ctrl+R` will do a refresh without utilizing the cache (i.e. a full reload).
+
+If a page is loading, the refresh button becomes a stop button. Clicking this or pressing `Escape` will cause the page
+to stop loading.
+
+## Address Bar
+
+![Autocomplete](../img/screenshot-autocomplete-simple.png)
+
+The address bar is at the top of the browser. It contains the current URL of the page. The bar can be focused for edit
+by clicking on it, pressing `Alt+2`, or pressing `Ctrl+D`.
 
-* Getting to the address bar
+While typing a URL, an autocomplete box appears with 10 matching entries based on what has been visited before. These
+are ordered by a combination of most recent and most frequent visits. Simply use the arrow keys or the mouse to select
+which autocomplete item to navigate to. Otherwise, press enter to attempt to navigate to the URL in the field.
 
-#### Autocomplete
+An item also appears in the autocomplete for searching [DuckDuckGo](https://duckduckgo.com/) for the entered phrase. To
+use another search engine, simply use the [!bang syntax](https://duckduckgo.com/bang).
 
-### Page Load (stop/start)
+## SSL/TLS Info
 
-### Direction
+Once a page has finished loading, a lock icon will appear to the left of the address bar showing how secure the page is.
+The lock has four states:
 
-### SSL Info
+* ![No HTTPS](../img/screenshot-ssl-unlock-gray.png) unlocked and grayed out - The page is not secured by HTTPS.
+* ![Good HTTPS](../img/screenshot-ssl-lock-green.png) locked and green - The page is validly secured via HTTPS.
+* ![Mixed Content](../img/screenshot-ssl-unlock-orange.png) unlocked and orange - Only some of the page is secured via
+  HTTPS.
+* ![Bad HTTPS](../img/screenshot-ssl-unlock-red.png) locked and green - The page is on HTTPS but invalidly secured.
 
-### Zoom/fullscreen
+Unless the lock icon is grayed out, it can be clicked to see more SSL information such as the certificate itself.
+
+![SSL Info](../img/screenshot-ssl-popup.png)
 
 ## Find in Page
 
-## Dev Tools
\ No newline at end of file
+![Find in Page](../img/screenshot-find-in-page.png)
+
+Pressing `Ctrl+F` in a page opens the find bar at the bottom of the page. Typing in this field highlights found items
+and shows the total number of items. Clicking the down button or pressing `Enter` moves to the first item and
+continually doing so `Enter` goes forward. Clicking the up button or pressing `Shift+Enter` goes backwards. To remove
+the find bar, simply press `Escape` while in the find box.
+
+## Zoom and Fullscreen
+
+To zoom in on a page, press `Ctrl` and `+` (or `Ctrl` and `=`). This will zoom in the page by 10%. To zoom out by 10%,
+press `Ctrl` and `-`. To reset the zoom back to the normal 100%, press `Ctrl` and `0`.
+
+To fullscreen the current page, press `F11`. To exit fullscreen, press `F11` again or press `Escape`.
+
+## Dev Tools
+
+![Dev Tools](../img/screenshot-dev-tools.png)
+
+If the dev tools dock window is not open, pressing `F12` will open the window and open dev tools for the current page.
+If the dev tools dock window is open, but dev tools is not open for the current page, pressing `F12` or clicking the
+"open" button in the dock window will open dev tools for the current page. If the dev tools is visible and open for the
+current page, pressing `F12` will close dev tools for all pages and close the dock window.
\ No newline at end of file
diff --git a/docs/guide/bubble.md b/docs/guide/bubble.md
index db72c09..24cd0f3 100644
--- a/docs/guide/bubble.md
+++ b/docs/guide/bubble.md
@@ -5,8 +5,61 @@ title: Bubbles
 
 # Bubbles
 
-## On page tree
+A bubble is a context a page resides in. A bubble has its own settings including the cache path which means two pages
+can be side-by-side in the page tree but open in different bubbles set to different paths meaning things like cookies
+aren't shared. Or a bubble may have JavaScript disabled and a user can easily have the "no JS" bubble be the default and
+switch to a more full-featured bubble as needed.
 
-## Settings
+## On Page Tree
 
-## Examples
\ No newline at end of file
+Each bubble has a name and may have an icon that identifies it. Every page is opened in a bubble. The default bubble
+when Doogie is first installed is named "(default)" and has no icon. The icon for a page's bubble appears on the page
+tree just to the left of the **X** close button. For example, if there is a bubble for "Home" that is a green bed icon
+and another for "Work" that is a blue briefcase, here's how the pages might look opened in both:
+
+![Bubbles Simple](../img/screenshot-bubbles-simple.png)
+
+By default, a page is opened in the bubble of its parent page. If there is no parent page, a bubble is opened in the
+top-most bubble in the profile's bubble list (see [Management](#management)).
+
+### Changing a Page's Bubble
+
+To change a bubble for an individual page, right click the bubble icon (or where the icon would be if it existed) which
+is just to the left of the **X** close button for the tree.
+
+![Change Bubble](../img/screenshot-change-bubble.png)
+
+The currently selected bubble will be checked and not selectable. Select any other bubble to change it. To change the
+page to a new bubble, click `New Bubble...` and the [settings](#settings) dialog will appear. Upon successful save of
+the new bubble, the page will be changed to it.
+
+Changing the bubble for multiple pages is also supported via [page actions](page-tree#page-actions). For example, to
+change a bubble for several pages, select them and right-click.
+
+![Change Multiple Bubble](../img/screenshot-change-bubble-multiple.png)
+
+This menu can be used the same way as the individual page bubble menu. The same applies to clicked-on page, current
+page, and all pages via the page tree menu.
+
+## Management
+
+The `Bubbles` tab in the [profile settings dialog](general#profile-settings) is where bubbles are managed.
+
+![Bubbles Settings](../img/screenshot-profile-settings-bubbles.png)
+
+The top-most bubble is the bubble that top-level pages will be opened in by default. To move a bubble around in the
+list, select it and click the button for moving it down or up.
+
+Bubbles can be added, edited, or deleted here. Note, bubbles that currently have visible pages in them cannot be edited
+or deleted until all of the pages within them are closed. A new bubble can be created with `New Bubble` or via the page
+tree menu item. An eligible bubble can be edited by double clicking on it or clicking the `Edit Selected` button.
+
+### Settings
+
+The bubble's setting dialog appears when adding or editing a bubble.
+
+![Bubble Settings](../img/screenshot-bubble-settings.png)
+
+The settings dialog includes a way to set the name and icon of the bubble. The name must be unique. The icon is
+optional and, if present, a color override can be applied. All other settings are basically overrides for 
+[profile settings](general#profile-settings).
\ No newline at end of file
diff --git a/docs/guide/develop.md b/docs/guide/develop.md
index a2422d1..ec93cf3 100644
--- a/docs/guide/develop.md
+++ b/docs/guide/develop.md
@@ -3,8 +3,143 @@ layout: guide
 title: Development
 ---
 
-## Development
+# Development
 
-### Building
+Doogie is built in C++ using [CEF](https://bitbucket.org/chromiumembedded/cef) and [Qt](https://www.qt.io/). This
+section has information on [issues](#issues), [building](#building), and [contributing](#contributing).
+
+## Issues
+
+Any bugs or enhancement requests can be filed in via [GitHub issues](https://github.com/cretz/doogie/issues/). When
+filing a bug, please try to be as descriptive as possible on the issue. Ideally, provide a page or set of pages that
+trigger the error.
+
+If you are a developer, one of the easiest ways to do this is to add the pages to `src/tests/integration/resources`.
+Then by running `npm run resource-server` from `src/tests/integration` the resources can be browsed via
+http://127.0.0.1:1993 (e.g. [http://127.0.0.1:1993/hello-world.html](http://127.0.0.1:1993/hello-world.html)).
+
+## Building
+
+Building Doogie is straightforward. A [Go](https://golang.org/) script at `src/build.go` handles all building regardless
+of platform.
+
+All instructions below assume the user is in the `src` folder.
+
+### Windows Prerequisites
+
+Before running the build script on Windows, you must have the prerequisites:
+
+* Latest Qt (5.x) installed w/ `qmake.exe` on the `PATH`
+* Latest CMake installed w/ `cmake.exe` on the `PATH`
+* Latest Python (2.x) installed w/ `python.exe` on the `PATH`
+* Latest Go installed w/ `go.exe` on the `PATH`
+* [MSVC 2015 Build Tools](http://landinghub.visualstudio.com/visual-cpp-build-tools) installed w/ the following
+  executed to put 64-bit VC compiler on the `PATH`:
+  `"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64`
+* Latest [Windows 64-bit standard dist of CEF](http://opensource.spotify.com/cefbuilds/index.html#windows64_builds)
+  extracted w/ `CEF_DIR` environment variable set to the base CEF extracted dir
+* This repo cloned w/ the shell at the `src` folder
+
+### Linux Prerequisites
+
+Before running the build script on Linux, you must have the prerequisites:
+
+* Latest Qt (5.x) installed w/ `qmake` on the `PATH`
+* Latest CMake installed w/ `cmake` on the `PATH`
+* Latest Python (2.x) installed w/ `python` on the `PATH`
+* Latest Go installed w/ `go` on the `PATH`
+* Latest GCC installed w/ `gcc` and `g++` on the `PATH`
+* Latest Make installed w/ `make` on the `PATH`
+* Latest [Linux 64-bit standard dist of CEF](http://opensource.spotify.com/cefbuilds/index.html#linux64_builds)
+  extracted w/ `CEF_DIR` environment variable set to the base CEF extracted dir
+* Latest GTK 2.x installed and on the library path
+* This repo cloned w/ the shell at the `src` folder
+
+### MacOS Prerequisites
+
+(TODO)
+
+### Running Build
+
+All instructions below assume the user is in the `src` folder.
+
+The application uses the CEF C++ wrapper, which can be built via:
+
+    go run build.go build-cef
+
+This only needs to be built one time. Now the application can easily be run via:
+
+    go run build.go run
+
+That will run the `debug` version. For the `release` version, run:
+
+    go run build.go run release
+
+Internally, that just builds and runs the exe. To just build, call `build` instead. To package a deployment artifact
+from a previously run build, `package` is used. For example, to package a `release` deployment artifact from a
+previously run `release` build, run:
+
+    go run build.go package release
+
+Once complete, the package(s) will in `release/package` (e.g. doogie.zip in Windows)
+
+### Testing
+
+There are two types of tests, unit and integration tests at `src/tests/unit` and `src/tests/integration` respectively.
+
+#### Integration Tests
+
+The integration tests are not yet integrated in `build.go`. The tests are written in node.js. Make sure you have the
+latest LTS release of node installed and navigate to `src/tests/integration`. To setup the test infrastructure, run:
+
+    npm install
+
+To run the tests, make sure a debug instance of Doogie is running then run
+
+    npm test
+
+#### Unit Tests
+
+Assuming CEF is built (see the first "Running Build" step), unit tests can be run with the following in `src/`:
+
+    go run build.go unit-test
+
+Like the `run` command, the `unit-test` command can be given a `release` target, otherwise it defaults to `debug`.
+
+#### Benchmarks
+
+There are a couple of benchmarks in the application. To run them, do the following in `src/`:
+
+    go run build.go benchmark
+
+Like the `run` command, the `benchmark` command can be given a `release` target, otherwise it defaults to `debug`.
+
+## Contributing
+
+### C++
+
+Doogie follows the [Chromium Style Guide](https://chromium.googlesource.com/chromium/src/+/master/styleguide/c++/c++.md)
+for C++ code except for anything listed below.
+
+* Forward decls only when necessary. No need to worry about compile times (yet).
+* We use a singleton here and there as necessary
+* Avoid slots, use method references
+* Class decl order is usually public, protected, and private. But here they are public, signals, public slots,
+  protected, protected slots, private, and private slots
+* Prefer default by-value capture on local lambdas
+* Obviously, some styles have to be broken to confirm to Qt, e.g. name format for overridden methods
+* No file-level comments
+* Passing around raw pointers is ok in Qt land, at least for now
+
+To do a lint check of the code, have the
+[Chromium depot_tools](https://chromium.googlesource.com/chromium/tools/depot_tools.git) cloned somewhere and set the
+`DEPOT_TOOLS_DIR` env var to the dir. Then run the following in `src/`:
+
+    go run build.go lint
+
+### JavaScript
+
+For JS code in `src/tests/integration`, follow [Standard Style](https://www.npmjs.com/package/standard).
+
+Lint checks automatically occur when `npm test` is run to do the integration tests.
 
-### Contributing
\ No newline at end of file
diff --git a/docs/guide/faq.md b/docs/guide/faq.md
index bd563f4..cc09823 100644
--- a/docs/guide/faq.md
+++ b/docs/guide/faq.md
@@ -3,16 +3,35 @@ layout: guide
 title: FAQ
 ---
 
+
 # FAQ
+{:.no_toc}
+
+* toc
+{:toc}
+
+### Where is the macOS version?
+
+The original author does not use an Apple machine, and while one could be used temporarily to build an initial version,
+it might become stale if not maintained. It would be greatly appreciated if someone wanted to step up and support macOS.
+The very few parts that are platform specific are properly segregated and should be easy enough to implement. Please see
+[this issue](https://github.com/cretz/doogie/issues/19) for more details.
 
 ### Why is this so buggy?
 
 This is early alpha software and probably has a ton of bugs. This is also the original author's first foray into modern
 C++, so surely there are mistakes there. They just have to be ironed out as time goes on.
 
+Please report any [issue](develop#issues).
+
+### How do I create an "incognito" or "private mode" bubble?
+
+Simply create a bubble that has no cache. However, right now there is not a setting to prevent it from saving
+autocomplete (see [this issue](https://github.com/cretz/doogie/issues/13)).
+
 ### Where can I donate? How do you plan on monetizing?
 
-There is no monetization attempt at this early stage. If you want to donate, please consider
+There is no monetization attempt (yet?). If you want to donate, please consider
 [donating to CEF](http://www.magpcss.org/ceforum/donate.php) which this project is based on.
 
 ### Why did you choose C++ instead of a safer, more modern language?
diff --git a/docs/guide/general.md b/docs/guide/general.md
index 51ac26f..3bd9677 100644
--- a/docs/guide/general.md
+++ b/docs/guide/general.md
@@ -7,8 +7,85 @@ title: General Usage
 
 ## Dock Windows
 
-## Shortcuts
+Tool windows in Doogie appear as dock windows. This includes the [page tree](page-tree), the downloads window, the logs
+window, and more. Dock windows may be rearranged. They can be dragged to the borders of the application, just dragged
+out to remain their own floating windows, or dragged on top of existing windows to make a tabbed view of multiple dock
+windows.
+
+Every time Doogie is closed, the arrangement of the windows is stored. Then when Doogie is started again, it is restored
+the way it was when closed.
+
+### Downloads
+
+![Downloads](../img/screenshot-downloads.png)
+
+The downloads dock window shows all current and previous downloads. Clicking "Remove All Finished" removes all entries
+that are not actively downloading. Downloads may be paused/resumed and can be canceled. A completed download will have a
+folder icon next to it that, when clicked, will open the operating system's file browser to the directory where the
+download was saved to.
+
+### Logs
+
+The logs window shows all internal logs Doogie. Currently this is not configurable but will be in the future.
+
+### Request Blocker
+
+![Request Blocker](../img/screenshot-request-blocker-simple.png)
+
+The request blocker window shows all URL requests that were blocked either in the current page or in all pages. It shows
+the information about each blocked request and can be sorted by any of the pieces of information.
+
+In the upper right there is a checkbox for "Current Page" that, when checked, will only show blocked requests for the
+current page. To the right of it there is a clear button that, when pressed, will clear the currently visible blocked
+requests whether that is just for the current page or for all pages. Finally, on the far right is a settings button.
+Clicking that opens the [blocker list settings](#blocker-lists) in the profile window.
 
 ## Profiles
 
-## Request Blocker
\ No newline at end of file
+Every Doogie instance is associated with a profile. By default, a "default" profile is used. Essentially a profile is
+just a directory. A profile stores everything about Doogie except for dock window arrangement. Profiles are intended to
+be used by different users. For different browsing contexts with the same user, consider [bubbles](bubble).
+
+To change a profile, use the `Window` > `Profile` > `Change Profile` menu action. Since the entire Doogie process must
+be associated with a profile, changing a profile requires either restarting Doogie or starting a new instance of Doogie.
+
+![Change Profile](../img/screenshot-change-profile.png)
+
+There is an in-memory-only profile which will never store anything. This can be helpful for ephemeral browsing sessions
+where no storage is desired.
+
+### Profile Settings
+
+![Profile Settings](../img/screenshot-profile-settings.png)
+
+A profile has many settings including cache paths, keyboard shortcuts, [bubbles](bubble), and blocker lists. These can
+be edited via the profile settings dialog in the `Window` > `Profile` menu (except for the in-memory profile).
+
+The settings dialog has four tabs:
+
+#### Browser Settings
+
+This has the common browser settings for the entire application. Many of these can be individually overridden in
+[bubbles](bubble). Changing some of these at the profile level requires the application be restarted.
+
+#### Keyboard Shortcuts
+
+This has all keyboard shortcuts for the application. These can be changed by clicking the desired action to change. Then
+an existing shortcut can be deleted. Also, a shortcut can be added by manually entering the key sequence in the field or
+pressing `Record` and typing the sequence within a couple of seconds.
+
+#### Bubbles
+
+Bubbles are contextual browsing settings. Bubbles are described in detail in the [bubble](bubble) section. They can be
+added, edited, or deleted in the profile settings dialog. Note, bubbles which have any open pages in them cannot be
+edited or deleted until their pages are closed. Bubbles can be moved up or down which affects how they appear in the
+bubble menu. The top-most bubble is the one top-level pages will be opened in by default. See
+[bubble management](bubble#management) for more information.
+
+#### Blocker Lists
+
+This tab shows all loaded blocker lists, which ones are enabled, when the are refreshed, and more. Blocker lists use the
+[Adblock Plus filter syntax](https://adblockplus.org/filters). They can be loaded from a file or from a URL.
+
+A selected blocker list may be removed by clicking `Delete`. A reload can be forced on a selected blocker list by
+clicking `Force Reload on Save`.
\ No newline at end of file
diff --git a/docs/guide/index.html b/docs/guide/index.html
index 87acaef..63a49c8 100644
--- a/docs/guide/index.html
+++ b/docs/guide/index.html
@@ -1,5 +1,6 @@
 ---
 layout: page
+title: User Guide
 ---
 
 {% include guide-toc.html %}
\ No newline at end of file
diff --git a/docs/guide/page-tree.md b/docs/guide/page-tree.md
index f1592e7..40e4c15 100644
--- a/docs/guide/page-tree.md
+++ b/docs/guide/page-tree.md
@@ -8,6 +8,8 @@ title: Page Tree
 The page tree is a dock window that shows all the open pages in a tree-style hierarchy. The tree pages can be opened,
 moved around, closed, suspended, moved under separate workspaces or bubbles, etc.
 
+![Page Tree](../img/screenshot-page-tree-simple.png)
+
 ## Navigation
 
 The page tree has a "current" page which is signified by bolding the page's title. The current page is the one that will
@@ -19,22 +21,26 @@ Note, these are the default shortcut keys for these actions and may be altered b
 
 ## Selection
 
+![Page Selection](../img/screenshot-page-tree-selection.png)
+
 To select multiple tree pages, a normal rectangle drag can be used, starting by click-dragging off of any existing page.
 A range of tree pages can be selected by selecting one and holding shift while selecting another. Similarly, multiple
 individual tree pages may be selected by pressing ctrl while clicking them.
 
 ## Page Actions
 
-When right-clicking, a context menu appears that allows you to create a new top-level page (see "Adding a Page"), manage
-workspaces (see "Workspaces"), and affect current pages. The list of pages that can be affected can include the
-"Clicked-On Page", the "Current Page" (only if there was no clicked-on page), "Selected Pages" (if applicable), and
-"All Pages". The actions include:
+![Page Tree Menu](../img/screenshot-page-tree-menu.png)
+
+When right-clicking, a context menu appears that allows you to create a new top-level page (see
+[Adding Pages](#adding-pages)), manage workspaces (see [Workspaces](#workspaces)), and affect current pages. The list of
+pages that can be affected can include the "Clicked-On Page", the "Current Page" (only if there was no clicked-on page),
+"Selected Pages" (if applicable), and "All Pages". The actions include:
 
 * **New Child Background Page** (single page only) - Create a new child page in the background
 * **New Child Foreground Page** (single page only) - Create a new child page and navigate to it
 * **Reload Page(s)** - Reload non-suspended page(s)
-* **Suspend Page(s)** - Suspend page(s). See "Page Suspension" section for more information.
-* **Unsuspend Page(s)** - Unsuspend page(s). See "Page Suspension" section for more information.
+* **Suspend Page(s)** - Suspend page(s). See [Page Suspension](#page-suspension) section for more information.
+* **Unsuspend Page(s)** - Unsuspend page(s). See [Page Suspension](#page-suspension) section for more information.
 * **Expand Tree(s)** - Page(s) that have children will be expanded recursively
 * **Collapse Tree(s)** - Page(s) that have children will be collapsed recursively
 * **Duplicate Tree(s)** - Page tree(s) will be copied/recreated in the bottom of the tree
@@ -45,7 +51,7 @@ workspaces (see "Workspaces"), and affect current pages. The list of pages that
 * **Close Same-Host Page(s)** - Same as selecting same-host pages then doing close page(s)
 * **Close Other/Non-Selected Page(s)** - Same as close page(s) but for the other pages
 * **Close Other/Non-Selected Tree(s)** Same as close tree(s) but for the other trees
-* **Bubble** - Change the bubble for the page(s). See the "Bubbles" page of the guide for more information.
+* **Bubble** - Change the bubble for the page(s). See [Bubbles](bubble) for more information.
 
 ## Rearranging Pages
 
@@ -57,7 +63,7 @@ opening new pages with the same URLs.
 
 Pages can be collapsed or expanded by clicking the collapse/expand icon to the left of the page title.
 
-Pages can be dragged between workspaces as well. See the "Workspaces" section.
+Pages can be dragged between workspaces as well. See the [Workspaces](#workspaces) section.
 
 ## Adding Pages
 
@@ -72,15 +78,18 @@ background child. Pressing `Ctrl` and `Shift` while clicking a link will open th
 
 ## Closing Pages
 
-When a page is closed, its children are also closed if it collapsed. If the page is expanded, the children are instead
-moved up a level where the closed page used to be.
+When a page is closed, its children are also closed if it is collapsed. If the page is expanded, the children are
+instead moved up a level where the closed page used to be.
 
-To close a page, simply click the `X` to the right of the page title. To close multiple pages at once, click-drag across
-the `X` buttons of the pages to be closed. A page may also be closed by pressing `Delete` after clicking it. After
+To close the current page, press `Ctrl+F4` or `Ctrl+W`. To close any page, simply click the **X** to the right of the
+page title. To close multiple pages at once, click-drag across the **X** buttons of the pages to be closed. To close all
+pages, press `Ctrl+Shift+F4` or `Ctrl+Shift+W`. A page may also be closed by pressing `Delete` after clicking it. After
 selecting multiple pages, `Delete` can be used to close all of them.
 
 ## Page Suspension
 
+![Page Suspension](../img/screenshot-suspended-simple.png)
+
 Pages can be marked as suspended. A suspended page has all of its resources freed. It is shown as suspended by having
 the page title grayed out.
 
diff --git a/docs/img/screenshot-browser-area.png b/docs/img/screenshot-browser-area.png
new file mode 100644
index 0000000..5bb6c1e
Binary files /dev/null and b/docs/img/screenshot-browser-area.png differ
diff --git a/docs/img/screenshot-bubble-settings.png b/docs/img/screenshot-bubble-settings.png
new file mode 100644
index 0000000..c83b129
Binary files /dev/null and b/docs/img/screenshot-bubble-settings.png differ
diff --git a/docs/img/screenshot-change-bubble-multiple.png b/docs/img/screenshot-change-bubble-multiple.png
new file mode 100644
index 0000000..f35661e
Binary files /dev/null and b/docs/img/screenshot-change-bubble-multiple.png differ
diff --git a/docs/img/screenshot-change-bubble.png b/docs/img/screenshot-change-bubble.png
new file mode 100644
index 0000000..fb4c6b4
Binary files /dev/null and b/docs/img/screenshot-change-bubble.png differ
diff --git a/docs/img/screenshot-change-profile.png b/docs/img/screenshot-change-profile.png
new file mode 100644
index 0000000..a0a8e06
Binary files /dev/null and b/docs/img/screenshot-change-profile.png differ
diff --git a/docs/img/screenshot-dev-tools.png b/docs/img/screenshot-dev-tools.png
new file mode 100644
index 0000000..808647c
Binary files /dev/null and b/docs/img/screenshot-dev-tools.png differ
diff --git a/docs/img/screenshot-downloads.png b/docs/img/screenshot-downloads.png
new file mode 100644
index 0000000..a081131
Binary files /dev/null and b/docs/img/screenshot-downloads.png differ
diff --git a/docs/img/screenshot-find-in-page.png b/docs/img/screenshot-find-in-page.png
new file mode 100644
index 0000000..1097604
Binary files /dev/null and b/docs/img/screenshot-find-in-page.png differ
diff --git a/docs/img/screenshot-navigation-bar.png b/docs/img/screenshot-navigation-bar.png
new file mode 100644
index 0000000..1993f47
Binary files /dev/null and b/docs/img/screenshot-navigation-bar.png differ
diff --git a/docs/img/screenshot-page-tree-menu.png b/docs/img/screenshot-page-tree-menu.png
new file mode 100644
index 0000000..9ff9f24
Binary files /dev/null and b/docs/img/screenshot-page-tree-menu.png differ
diff --git a/docs/img/screenshot-page-tree-selection.png b/docs/img/screenshot-page-tree-selection.png
new file mode 100644
index 0000000..0acf845
Binary files /dev/null and b/docs/img/screenshot-page-tree-selection.png differ
diff --git a/docs/img/screenshot-page-tree-simple.png b/docs/img/screenshot-page-tree-simple.png
index f6ebfa4..5359c50 100644
Binary files a/docs/img/screenshot-page-tree-simple.png and b/docs/img/screenshot-page-tree-simple.png differ
diff --git a/docs/img/screenshot-profile-settings-bubbles.png b/docs/img/screenshot-profile-settings-bubbles.png
new file mode 100644
index 0000000..327b452
Binary files /dev/null and b/docs/img/screenshot-profile-settings-bubbles.png differ
diff --git a/docs/img/screenshot-profile-settings.png b/docs/img/screenshot-profile-settings.png
new file mode 100644
index 0000000..c089e7b
Binary files /dev/null and b/docs/img/screenshot-profile-settings.png differ
diff --git a/docs/img/screenshot-ssl-lock-green.png b/docs/img/screenshot-ssl-lock-green.png
new file mode 100644
index 0000000..c64ab0b
Binary files /dev/null and b/docs/img/screenshot-ssl-lock-green.png differ
diff --git a/docs/img/screenshot-ssl-popup.png b/docs/img/screenshot-ssl-popup.png
new file mode 100644
index 0000000..192867d
Binary files /dev/null and b/docs/img/screenshot-ssl-popup.png differ
diff --git a/docs/img/screenshot-ssl-unlock-gray.png b/docs/img/screenshot-ssl-unlock-gray.png
new file mode 100644
index 0000000..6838ad8
Binary files /dev/null and b/docs/img/screenshot-ssl-unlock-gray.png differ
diff --git a/docs/img/screenshot-ssl-unlock-orange.png b/docs/img/screenshot-ssl-unlock-orange.png
new file mode 100644
index 0000000..704b42b
Binary files /dev/null and b/docs/img/screenshot-ssl-unlock-orange.png differ
diff --git a/docs/img/screenshot-ssl-unlock-red.png b/docs/img/screenshot-ssl-unlock-red.png
new file mode 100644
index 0000000..dff86f5
Binary files /dev/null and b/docs/img/screenshot-ssl-unlock-red.png differ
diff --git a/docs/img/screenshot-suspended-simple.png b/docs/img/screenshot-suspended-simple.png
index 376537f..e168f0d 100644
Binary files a/docs/img/screenshot-suspended-simple.png and b/docs/img/screenshot-suspended-simple.png differ
diff --git a/docs/index.html b/docs/index.html
index 69e3f3e..2438721 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -48,8 +48,8 @@
     <a class="dos-button" href="https://github.com/cretz/doogie">
       GitHub
     </a>
-    <a class="dos-button" href="screenshots">
-      Screenshots
+    <a class="dos-button" href="#features">
+      Features
     </a>
   </div>
   <div class="desktop-only" style="text-align: center; color: white; border: 4px double white; width: 500px; text-align: center; margin: auto;">
@@ -92,7 +92,7 @@
 
   <h2>Overview</h2>
   <p>
-    Doogie is a web browser based on <a href="https://www.chromium.org">Chromium</a> (via <a href="https://bitbucket.org/chromiumembedded/cef">CEF</a>) and built using <a href="https://www.qt.io/">Qt</a>. The primary goal is to make a browser that functions more like an <a href="https://en.wikipedia.org/wiki/Integrated_development_environment">IDE</a>. In an era where web browsers continually remove or hide UI, Doogie aims to make it more visible and allow easier cross-contextual browsing. <a href="guide">Read the user guide</a>
+    Doogie is a <a href="https://www.chromium.org">Chromium</a>-based web browser with tree-style pages. It is build using <a href="https://bitbucket.org/chromiumembedded/cef">CEF</a> and <a href="https://www.qt.io/">Qt</a>. The primary goal is to make a browser that functions more like an <a href="https://en.wikipedia.org/wiki/Integrated_development_environment">IDE</a>. In an era where web browsers continually remove or hide UI, Doogie aims to make it more visible and allow easier cross-contextual browsing. <a href="guide">Read the user guide</a>
   </p>
 
   <h2>Screenshot</h2>
@@ -100,11 +100,9 @@ <h2>Screenshot</h2>
     <a href="img/screenshot-main.png">
       <img src="img/screenshot-main.png" style="max-width:100%; max-height:100%;">
     </a>
-    <br />
-    <a href="screenshots">See more screenshots</a>
   </p>
 
-  <h2>Features</h2>
+  <h2 id="features">Features</h2>
   <h4>Page Tree</h4>
   <div class="feature-item">
     <img src="img/screenshot-page-tree-simple.png" style="height: 100%;">
@@ -156,7 +154,7 @@ <h4>Autocomplete and Search</h4>
       </div>
       <br />
       <div>
-        Read more about <a href="#">Autocomplete and Search</a>
+        Read more about the <a href="guide/browser#address-bar">Address Bar</a>
       </div>
     </div>
   </div>
@@ -170,7 +168,7 @@ <h4>Request Blocker</h4>
       </div>
       <br />
       <div>
-        Read more about the <a href="#">Request Blocker</a>
+        Read more about the <a href="guide/general#request-blocker">Request Blocker</a>
       </div>
     </div>
   </div>
diff --git a/src/action_manager.cc b/src/action_manager.cc
index a24fcd0..a834493 100644
--- a/src/action_manager.cc
+++ b/src/action_manager.cc
@@ -141,7 +141,7 @@ void ActionManager::CreateActions() {
   shortcuts(ActionManager::ResetZoom, "Ctrl+0");
   shortcuts(ActionManager::FindInPage, "Ctrl+F");
   shortcuts(ActionManager::FocusPageTree, "Alt+1");
-  shortcuts(ActionManager::FocusAddressBar, "Alt+2; Ctrl+D");
+  shortcuts(ActionManager::FocusAddressBar, "Alt+2; Alt+D");
   shortcuts(ActionManager::FocusBrowser, "Alt+3");
 }
 
diff --git a/src/cef/cef_base_widget.cc b/src/cef/cef_base_widget.cc
index c165efe..9bfe9cf 100644
--- a/src/cef/cef_base_widget.cc
+++ b/src/cef/cef_base_widget.cc
@@ -25,13 +25,20 @@ void CefBaseWidget::resizeEvent(QResizeEvent* event) {
 }
 
 bool CefBaseWidget::IsForwardableKeyEvent(const CefKeyEvent& event) const {
-  // For now, we forward everything but the tab key sans mods
-  if (event.character != 9) return true;
-  bool has_mods = event.modifiers & EVENTFLAG_SHIFT_DOWN ||
-        event.modifiers & EVENTFLAG_CONTROL_DOWN ||
-        event.modifiers & EVENTFLAG_ALT_DOWN ||
+  // For now, we forward everything but:
+  //  * tab key (unless Ctrl is pressed)
+  //  * backspace while in edit field
+  // Tab check
+  if (event.character == 9) {
+    bool ctrl_down = event.modifiers & EVENTFLAG_CONTROL_DOWN ||
         event.modifiers & EVENTFLAG_COMMAND_DOWN;
-  return has_mods;
+    return ctrl_down;
+  }
+  // Backspace check
+  if (event.character == 8) {
+    return !event.focus_on_editable_field;
+  }
+  return true;
 }
 
 }  // namespace doogie
diff --git a/src/page_tree.cc b/src/page_tree.cc
index f916e71..e7f2f33 100644
--- a/src/page_tree.cc
+++ b/src/page_tree.cc
@@ -896,6 +896,9 @@ void PageTree::SetupActions() {
   connect(ActionManager::Action(ActionManager::Stop),
           &QAction::triggered,
           [=]() { CurrentItem()->Browser()->Stop(); });
+  connect(ActionManager::Action(ActionManager::Back),
+          &QAction::triggered,
+          [=]() { CurrentItem()->Browser()->Back(); });
   connect(ActionManager::Action(ActionManager::Forward),
           &QAction::triggered,
           [=]() { CurrentItem()->Browser()->Forward(); });
diff --git a/src/profile_settings_dialog.cc b/src/profile_settings_dialog.cc
index 980f91b..db53bc6 100644
--- a/src/profile_settings_dialog.cc
+++ b/src/profile_settings_dialog.cc
@@ -86,7 +86,7 @@ void ProfileSettingsDialog::closeEvent(QCloseEvent* event) {
 
 void ProfileSettingsDialog::keyPressEvent(QKeyEvent* event) {
   // Don't let escape close this if there are changes
-  if (event->key() == Qt::Key_Escape && !SettingsChanged()) {
+  if (event->key() == Qt::Key_Escape && SettingsChanged()) {
     event->ignore();
     return;
   }