diff --git a/docs/CaseGroupsAndStatistics.md b/docs/CaseGroupsAndStatistics.md
index 6739b69407..72c59c0637 100644
--- a/docs/CaseGroupsAndStatistics.md
+++ b/docs/CaseGroupsAndStatistics.md
@@ -9,7 +9,7 @@ permalink: /docs/casegroupsandstatistics/
 
 ## Grid Case Groups and Statistics
 
-![](images/GridCaseGroupTree.png)
+![]({{ site.baseurl }}/images/GridCaseGroupTree.png)
 
 **Grid Case Group**'s are designed to make it easy to calculate statistics per cell and per timestep of a large number of Eclipse simulation Cases with identical Grids (often labeled *realizations*).
  
@@ -21,7 +21,7 @@ The easiest way to create a **Grid Case Group** is to use the Import command:
 **File->Import->Create Grid Case Group from Files**
 
 An import dialog is opened: 
-![](images/CreateGridCaseGroupFromFileDialog.png) 
+![]({{ site.baseurl }}/images/CreateGridCaseGroupFromFileDialog.png) 
 
 1. Add one or more search folders to the list on the left.
 2. The EGRID or GRID files found in these directories and sub directories are shown in the list to the right.
@@ -50,7 +50,7 @@ After creating a grid case group, an empty **Statistics Case** is created for yo
 #### Setting up and Calculate
 The properties of an uncalculated and a calculated  **Statistics Case** is shown below:
 
-![](images/StatisticsCaseProperties.png)  ![](images/StatisticsCasePropertiesCalculated.png)
+![]({{ site.baseurl }}/images/StatisticsCaseProperties.png)  ![]({{ site.baseurl }}/images/StatisticsCasePropertiesCalculated.png)
 
 - **Compute**: Starts to calculate requested statistical Properties.
 - **Edit** : Deletes the calculated results, and makes the controls to edit the setup available.
diff --git a/docs/Faults.md b/docs/Faults.md
index c84b912905..c674630d5c 100644
--- a/docs/Faults.md
+++ b/docs/Faults.md
@@ -8,7 +8,7 @@ permalink: /docs/faults/
 
 ## Faults
 
-ResInsight can import faults from `*.DATA` files, and is available in the ![](images/draw_style_faults_24x24.png) **Faults** item in the **Project Tree**. The imported faults are ordered in ascending order based on name.
+ResInsight can import faults from `*.DATA` files, and is available in the ![]({{ site.baseurl }}/images/draw_style_faults_24x24.png) **Faults** item in the **Project Tree**. The imported faults are ordered in ascending order based on name.
 
 As import of faults can be time consuming, reading of faults can be disabled from **Preferences -> Read fault data**
 
@@ -21,15 +21,15 @@ ResInsight will detect all cell faces with no matching neighbor. All detected ce
 ### Toolbar control
 Visualization mode and mesh lines can be controlled from the toolbar.
 
-- ![](images/draw_style_faults_24x24.png) Toggle button to control faults only visualization mode
-- ![](images/draw_style_surface_24x24.png) Shows surface visualization
-- ![](images/draw_style_surface_w_fault_mesh_24x24.png) Shows mesh lines on faults
-- ![](images/draw_style_faults_label_24x24.png) Shows labels for faults  
+- ![]({{ site.baseurl }}/images/draw_style_faults_24x24.png) Toggle button to control faults only visualization mode
+- ![]({{ site.baseurl }}/images/draw_style_surface_24x24.png) Shows surface visualization
+- ![]({{ site.baseurl }}/images/draw_style_surface_w_fault_mesh_24x24.png) Shows mesh lines on faults
+- ![]({{ site.baseurl }}/images/draw_style_faults_label_24x24.png) Shows labels for faults  
 
 ### Common Fault Options
-By clicking the ![](images/draw_style_faults_24x24.png) **Faults** item in the **Project Tree**, the following options are displayed: 
+By clicking the ![]({{ site.baseurl }}/images/draw_style_faults_24x24.png) **Faults** item in the **Project Tree**, the following options are displayed: 
 
- ![](images/FaultProperties.png)
+ ![]({{ site.baseurl }}/images/FaultProperties.png)
  
 
 - **Show labels**: Displays one label per fault with fault name
diff --git a/docs/GettingStarted.md b/docs/GettingStarted.md
index 3988003ab8..c7810a15d9 100644
--- a/docs/GettingStarted.md
+++ b/docs/GettingStarted.md
@@ -18,7 +18,7 @@ Installation instructions for ResInsight can be found here: [Installation and Co
 The application has a main area and several docking windows. The different docking 
 windows can be managed from the **Windows** menu or directly using the local menu bar of the docking window.
 
-![ResInsight User Interface](images/ResInsightUIFullSizeWindows.png)
+![ResInsight User Interface]({{ site.baseurl }}/images/ResInsightUIFullSizeWindows.png)
 
 
 #### Docking Windows
@@ -41,13 +41,13 @@ In the main area of the application, several 3D views can be open at the same ti
 
 *TIP:* To see views next to each other select the **Restore down** icon in the application show here for Windows :
 
-![Restore Down](images/RestoreDown.PNG)
+![Restore Down]({{ site.baseurl }}/images/RestoreDown.PNG)
 
 #### Editing the views
 
 Most of the settings and features of ResInsight is accessible through the **Project Tree** and the **Property Editor**. Selecting an item in the **Project Tree** activates the corresponding 3D View, and shows the item properties in the **Property Editor** available for editing. 
 
-Toggling a checkbox next to an item in the **Project Tree** will toggle visibility in the 3D view. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. ![](images/TreeViewToggle.png)
+Toggling a checkbox next to an item in the **Project Tree** will toggle visibility in the 3D view. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. ![]({{ site.baseurl }}/images/TreeViewToggle.png)
 
 Context menu commands are also available to do special operations on a selected set of items.
 
@@ -56,17 +56,17 @@ Context menu commands are also available to do special operations on a selected
 A *Case* in ResInsight means a Grid model with a particular set of results or property data. There are  
 three different Case types: 
 
-##### Result case ![](images/Case24x24.png) 
+##### Result case ![]({{ site.baseurl }}/images/Case24x24.png) 
 This is a Case based on the results of an Eclipse analysis, read from a grid file together with restart data.
 
-##### Input case ![](images/EclipseInput24x24.png) 
+##### Input case ![]({{ site.baseurl }}/images/EclipseInput24x24.png) 
 This Case type is based on a `*.GRDECL` file, or a part of an Eclipse *Input* file. This Case type supports loading single ASCII files defining Eclipse Cell Properties, and also to export modified property sets to ASCII files.
 Each of the Eclipse properties is listed as separate entities in the **Project Tree**, and can be renamed and exported.
 
-#####  Statistics case ![](images/Histogram24x24.png)
+#####  Statistics case ![]({{ site.baseurl }}/images/Histogram24x24.png)
 This is a Case type that belongs to a *Grid Case Group* and makes statistical calculations based on the source cases in the Grid Case Group. 
 
-#### Grid Case Groups ![](images/GridCaseGroup24x24.png) 
+#### Grid Case Groups ![]({{ site.baseurl }}/images/GridCaseGroup24x24.png) 
 
 A **Grid Case Group** is a group of **Result Cases** with identical grids, but generally different active cells, initial values and results. These cases are called *Source Cases*. 
 
@@ -99,7 +99,7 @@ ResInsight supports the following type of Eclipse input data:
 
 The X and Y grid data can be negated in order to make the Grid model appear correctly in ResInsight. This functionality is accessible in the **Property Editor** for all Case types as the toggle buttons **Flip X Axis** and **Flip Y Axis** as shown in the example below.
  
-![](images/CaseProperties.png)
+![]({{ site.baseurl }}/images/CaseProperties.png)
 
 
 ### Model navigation 
@@ -148,10 +148,10 @@ Statistics calculations, property sets you generate by using Octave, and well pa
 
 ### Export options
 #### Snapshot images 
-##### Single View ![](images/SnapShot.png) ![](images/SnapShotSave.png)
+##### Single View ![]({{ site.baseurl }}/images/SnapShot.png) ![]({{ site.baseurl }}/images/SnapShotSave.png)
 Image export of current 3D view can be launched from **File -> Export -> Snapshot To File**. A snapshot can also be copied to clipboard using **Edit->Copy Snapshot To Clipboard**. 
 
-##### All Views ![](images/SnapShotSaveViews.png)
+##### All Views ![]({{ site.baseurl }}/images/SnapShotSaveViews.png)
 If a project contains multiple views, all views can be exported using **File -> Export -> Snapshot All Views To File**. 
 
 It is also possible to snapshot all views from the command line. See  [ Command Line Arguments]      (CommandLineParameters.md)
@@ -160,7 +160,7 @@ It is also possible to snapshot all views from the command line. See  [ Command
 
 
 #### Export of Eclipse Properties as ASCII data
-Eclipse Properties can be exported to Eclipse ASCII files by activating the context menu for a **Cell Result**. ![](images/ExportProperty.png) 
+Eclipse Properties can be exported to Eclipse ASCII files by activating the context menu for a **Cell Result**. ![]({{ site.baseurl }}/images/ExportProperty.png) 
 
 The command will export the property set currently loaded and shown in the 3D View to a file with the following format:
 
diff --git a/docs/OctaveInterface.md b/docs/OctaveInterface.md
index 2fd0102742..d53f30e912 100644
--- a/docs/OctaveInterface.md
+++ b/docs/OctaveInterface.md
@@ -17,7 +17,7 @@ The Octave functions are documented in [ Octave Interface Reference](OctaveInter
 ### Script management 
 Octave scripts are available in the **Scripts** folder in the **Project Tree**. 
 
-![](images/OctaveScriptTree.png)
+![]({{ site.baseurl }}/images/OctaveScriptTree.png)
 
 This folder contains an entry for each of the directories you have added as a **Script Folder**. Each of the folder lists available `*.m` files and sub directories. The tree is continuously updated to reflect the file structure on disk.
 
@@ -40,7 +40,7 @@ A script can be started by navigating to the script in the **Project Tree**, and
 #### With a case selection
 One script can be executed on many cases by first selecting a set of cases, and then activating **Execute script** from the context menu for the case selection. The script is then executed once pr selected case. Each time ResInsight's *Current Case* is updated, making it accessible from the Octave script. 
 
-![](images/ExecuteOctaveScriptOnSelectedCases.png)
+![]({{ site.baseurl }}/images/ExecuteOctaveScriptOnSelectedCases.png)
 
 
 
diff --git a/docs/RegressionTestSystem.md b/docs/RegressionTestSystem.md
index a70f97f1f5..df36920674 100644
--- a/docs/RegressionTestSystem.md
+++ b/docs/RegressionTestSystem.md
@@ -23,7 +23,7 @@ To be able to run regression tests you need the **compare** tool from the [Image
 You can start the tests either from the command line or from the ResInsight Gui.
 From the ResInsight Gui select : **File->Testing->Regression Test Dialog**
 
-![](images/RegressionTestDialog.png)
+![]({{ site.baseurl }}/images/RegressionTestDialog.png)
 
 Specify location of compare tool in **Folder containing compare**. The current working directory of ResInsight is temporarily changed to this path during execution.
 
diff --git a/docs/ReservoirViews.md b/docs/ReservoirViews.md
index d89309c699..e024d229da 100644
--- a/docs/ReservoirViews.md
+++ b/docs/ReservoirViews.md
@@ -18,12 +18,12 @@ Below is a description of the most important View settings and their properties.
 
 The **Cell Result** item defines which Eclipse property the 3D View uses for the main cell color. The property can be chosen in the property panel of the **Cell Result** item. The mapping between cell values and color is defined by the **Legend Definition**  ![](images/Legend.png) along with some appearance settings on the Legend itself. (Number format etc.)
 
-### Cell Edge Results ![](images/EdgeResult_1.png)
+### Cell Edge Results ![]({{ site.baseurl }}/images/EdgeResult_1.png)
 
 The **Cell Edge Result** visualization mode is one of ResInsight's special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. 
 This will show the MULT property values *different from 1.0* along the correct edges of the cells. In effect this highlights the faults and makes it easy to verify all the MULT values in one go.
 
-![](images/CellEdgeExample.png)
+![]({{ site.baseurl }}/images/CellEdgeExample.png)
 
 ResInsight supports all properties ending with X, Y, Z and X-, Y-, Z-. However, it is only the MULT property that ignores values of 1.0.
 
@@ -38,7 +38,7 @@ The **Results Histogram** shows a histogram of the complete time series of the c
 - The mean value ( a blue line ) 
 - P10 and P90 ( red lines )
 
-![](images/HistogramExample.png)
+![]({{ site.baseurl }}/images/HistogramExample.png)
 
 
 ### Cell Filters
@@ -59,7 +59,7 @@ A new range filter can be added by activating the context menu for the **Range F
 
 Below is a snapshot of the **Property Editor** of the **Range Filter** :
 
-![](images/RangeFilterProperties.png)
+![]({{ site.baseurl }}/images/RangeFilterProperties.png)
 
  - **Filter Type** : The filter can either make the specified range visible ( *Include* ), or remove the range from the View ( *Exclude* ).
  - **Grid** :  This option selects which of the grids the range is addressing.
@@ -73,7 +73,7 @@ The **Width** labels shows the number of active cells from the start of the acti
 
 **Property filters** apply to the results of the **Range filters**. Below is a snapshot of the **Property Editor** of the **Property Filter**.
   
-![](images/PropertyFilterProperties.png)
+![]({{ site.baseurl }}/images/PropertyFilterProperties.png)
 
 This filter filters the cells based on a property value range (Min - Max). Cells in the range are either shown or hidden depending on the **Filter Type** ( *Include* / *Exclude* ). Exclude-filters removes the selected cells from the **View** even if some other filter includes them.
 
@@ -91,7 +91,7 @@ The latter is handled internally as a special range filter, and adds cells to th
 
 The Property Editor of the **Simulation Wells** item is shown below: 
 
-![](images/SimulationWellsProperties.png)
+![]({{ site.baseurl }}/images/SimulationWellsProperties.png)
 
 
 
@@ -122,7 +122,7 @@ The pipe geometry generated for MSW's are based on the topology of the well (bra
 ###### Dummy branches
 Often MSW's are modeled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.
 
-![](images/MSWDummyBranchExample.png)
+![]({{ site.baseurl }}/images/MSWDummyBranchExample.png)
 
 ###### Picking reveals Segment/Branch info
 
@@ -136,7 +136,7 @@ This is particularly important to notice for the **Show Well Pipe** and **Range
  
 The properties of a single well are shown below.
 
-![](images/WellProperties.png)
+![]({{ site.baseurl }}/images/WellProperties.png)
 
 One option needs further explanation:
 
diff --git a/docs/WellPaths.md b/docs/WellPaths.md
index 6f358c79a4..73ccdeb558 100644
--- a/docs/WellPaths.md
+++ b/docs/WellPaths.md
@@ -13,7 +13,7 @@ In addition, a Statoil specific solution to retrieve Well Trajectories from thei
 
 ### Ascii Well Trajectories
 
-The command **File -> Import -> Import Well Paths From File** will read the well paths in the selected file, and create one entry for each trajectory under the  ![](images/WellCollection.png) **Wells** item in the **Project Tree**. 
+The command **File -> Import -> Import Well Paths From File** will read the well paths in the selected file, and create one entry for each trajectory under the  ![]({{ site.baseurl }}/images/WellCollection.png) **Wells** item in the **Project Tree**. 
 
 The supported ASCII format is quite flexible but the main requirements are: 
 
@@ -55,19 +55,19 @@ The trajectory data is not copied into the ResInsight project as such. The proje
 
 The command **File -> Import -> Import Well Paths From SSI-hub** launches a wizard to guide you through the process of selecting the well trajectories you need.
 
-After completing the wizard, the wells imported are accessible as Items under the  ![](images/WellCollection.png) **Wells** item in the **Project Tree**.
+After completing the wizard, the wells imported are accessible as Items under the  ![]({{ site.baseurl }}/images/WellCollection.png) **Wells** item in the **Project Tree**.
 
 The trajectory data is not copied into the  ResInsight project as such, but is stored in files in a directory called *ProjectFileName_wellpaths* in the same directory as your project file.   
 
 ### Well Trajectory visualization
 
-All the imported well trajectories are available below the ![](images/WellCollection.png) **Wells** item in the **Project Tree**. 
+All the imported well trajectories are available below the ![]({{ site.baseurl }}/images/WellCollection.png) **Wells** item in the **Project Tree**. 
 
-![](images/WellsInTree.png)
+![]({{ site.baseurl }}/images/WellsInTree.png)
 
 The visible wells are always shown in all the 3D Views in the complete project, so the toggles and settings control the overall project visibility of the Well Trajectories. The **Property Editor** of the **Wells** item is shown below 
 
-![](images/WellPathCollectionProperties.png)
+![]({{ site.baseurl }}/images/WellPathCollectionProperties.png)
 
 - **Global well path visibility** This option forces the well paths on or off, ignoring the individual settings unless it is set to Individual.
 - **Clip Well Paths** This option hides the top of the Well Trajectories to avoid displaying the very long lines from the reservoir to the sea surface.