Docs improvements (#109)

* Fixing code samples to C# with VS2015 highlighting

* Organising docs
Adding custom styles

Author: SteveWilkes

docs/src/Collections.md

@@ -12,12 +12,12 @@ The following collection types are supported by default:
 - `Collection<T>`
 - `HashSet<T>`
 - `ISet<T>`
-- [`Dictionary<string, T>`](Dictionary-Mapping)
-- [`IDictionary<string, T>`](Dictionary-Mapping)
+- [`Dictionary<string, T>`](/Dictionary-Mapping)
+- [`IDictionary<string, T>`](/Dictionary-Mapping)
 
 Generic `List<T>` instances are created for interface-type members except `ISet<T>`, which uses a `HashSet<T>`. If a member is already populated with a non-readonly collection (e.g. an array), the existing object will be reused.
 
-[Updates](Performing-Updates) and [merges](Performing-Merges) of collections of identifiable objects (i.e. Entities) are performed in an id-aware manner.
+[Updates](/Performing-Updates) and [merges](/Performing-Merges) of collections of identifiable objects (i.e. Entities) are performed in an id-aware manner.
 
 ## Null Source Collections
 

docs/src/Configuration.md

@@ -1,4 +1,4 @@
-For most cases, derived types are supported without configuration.
+For many cases, derived type mapping is supported without configuration.
 
 For example, with the following classes:
 
@@ -50,4 +50,4 @@ var resultAnimals = Mapper.Map(sourceAnimals).ToANew<AnimalDto[]>();
 // resultAnimals[1] is of type DogDto
 ```
 
-In the second example above, the `Dog` -> `DogDto` and `Cat` -> `CatDto` types are paired by convention based on the names of the original `Animal` -> `AnimalDto` pairing. You can configure [type pairs](Pairing-Derived-Types) which don't have a consistent naming convention, and [in which assemblies](Assembly-Scanning) to look for derived types.
+In the second example above, the `Dog` -> `DogDto` and `Cat` -> `CatDto` types are paired by convention based on the names of the original `Animal` -> `AnimalDto` pairing. You can configure [type pairs](/configuration/Pairing-Derived-Types) which don't have a consistent naming convention, and [in which assemblies](/configuration/Assembly-Scanning) to look for derived types.

docs/src/Configuring-Object-Identifiers.md

@@ -1,9 +1,9 @@
 AgileMapper has extensive support for mapping to and from Dictionaries. Out of the box:
 
 * Only dictionaries with string keys are supported
-* Dictionary keys must match target member names exactly, ignoring case ([configurable](Dictionary-Mapping-Configuration#configuring-keys))
-* Parent and child member names are matched to dictionary keys separated with a dot ([configurable](Dictionary-Mapping-Configuration#configuring-separators)), or flattened - with no separator
-* Enumerable elements are matched to dictionary keys by their index inside square brackets ([configurable](Dictionary-Mapping-Configuration#configuring-element-indexes))
+* Dictionary keys must match target member names exactly, ignoring case ([configurable](/configuration/Dictionary-Mapping#configuring-keys))
+* Parent and child member names are matched to dictionary keys separated with a dot ([configurable](/configuration/Dictionary-Mapping#configuring-separators)), or flattened - with no separator
+* Enumerable elements are matched to dictionary keys by their index inside square brackets ([configurable](/configuration/Dictionary-Mapping#configuring-element-indexes))
 * Dictionaries can contain all or a mixture of value type values, collections and complex types - anything with a matching key is used
 * Target members with no matching key in the dictionary are ignored
 
@@ -49,7 +49,7 @@ The created `contactDetails` will have the following property values:
     * "07890 654321" and
     * "01234 987654"
 * `Addresses` set to a new, 1-element `List<Address>` containing an `Address`:
-    * With `HouseNumber` set to '123' ([parsed](Type-Conversion) from the string)
+    * With `HouseNumber` set to '123' ([parsed](/Type-Conversion) from the string)
     * With `StreetName` set to "Dictionary Street"
 
 Note that the `StreetName` key had no separator, but the mapping works anyway.
@@ -91,4 +91,4 @@ The created `Dictionary` will have the following keys and values:
 
 ## Configuration
 
-Dictionary mapping is [highly configurable](Dictionary-Mapping-Configuration).
+Dictionary mapping is [highly configurable](/configuration/Dictionary-Mapping).

docs/src/Derived-Types.md

@@ -1,10 +1,10 @@
-AgileMapper's [dictionary mapping](Dictionary-Mapping) also applies to [ExpandoObject](https://docs.microsoft.com/en-us/dotnet/api/system.dynamic.expandoobject?view=netframework-4.7.1)s, which are mapped using their `IDictionary<string, object>` interface.
+AgileMapper's [dictionary mapping](/Dictionary-Mapping) also applies to [ExpandoObject](https://docs.microsoft.com/en-us/dotnet/api/system.dynamic.expandoobject?view=netframework-4.7.1)s, which are mapped using their `IDictionary<string, object>` interface.
 
 Out of the box:
 
-* Member names must match target member names exactly, ignoring case ([configurable](Dynamic-Mapping-Configuration#configuring-member-names))
-* Parent and child member names are matched to ExpandoObject member names separated with an underscore ([configurable](Dynamic-Mapping-Configuration#configuring-separators)), or flattened - with no separator
-* Enumerable elements are matched to ExpandoObject member names by their index separated by underscores ([configurable](Dynamic-Mapping-Configuration#configuring-element-indexes))
+* Member names must match target member names exactly, ignoring case ([configurable](/configuration/Dynamic-Mapping#configuring-member-names))
+* Parent and child member names are matched to ExpandoObject member names separated with an underscore ([configurable](/configuration/Dynamic-Mapping#configuring-separators)), or flattened - with no separator
+* Enumerable elements are matched to ExpandoObject member names by their index separated by underscores ([configurable](/configuration/Dynamic-Mapping#configuring-element-indexes))
 * ExpandoObjects can contain all or a mixture of value type values, collections and complex types - anything with a matching member name is used
 * Target members with no matching member in the ExpandoObject are ignored
 
@@ -89,4 +89,4 @@ The created `ExpandoObject` (in both cases) will have the following member names
 
 ## Configuration
 
-Dynamic mapping is [highly configurable](Dynamic-Mapping-Configuration).
+Dynamic mapping is [highly configurable](/configuration/Dynamic-Mapping).

docs/src/Dictionary-Mapping.md

@@ -4,7 +4,7 @@ Mapping to entities - an object with a member decorated with a [`KeyAttribute`](
 
 Members decorated with a `KeyAttribute` are not mapped, unless the mapping is a deep clone. Entity key values are usually generated by a data store, and some ORMs will throw an exception if a key value is updated in code.
 
-If you need to map to a `KeyAttribute` member, you can override this behaviour by configuring a [custom data source](Configuring-Member-Values).
+If you need to map to a `KeyAttribute` member, you can override this behaviour by configuring a [custom data source](/configuration/Member-Values).
 
 ### Optional Related Entity Keys
 

docs/src/Dynamic-Mapping.md

@@ -9,7 +9,7 @@ Flags enums are mapped automatically from numeric, string, enum and character so
 
 ### Enum Mapping Mismatches
 
-[Mapping plans](Using-Execution-Plans) warn you of enum mapping mismatches when mapping from one enum type to another. For example, a mapping between the following enums:
+[Mapping plans](/Using-Execution-Plans) warn you of enum mapping mismatches when mapping from one enum type to another. For example, a mapping between the following enums:
 
 ```cs
 // Source enum:
@@ -25,7 +25,7 @@ enum PaymentTypeUk { Cash, Card, Cheque }
 //  - PaymentTypeUs.Check matches no PaymentTypeUk
 ```
 
-`PaymentTypeUk.Cheque` also mismatches, but the mapping is going from `PaymentTypeUs` -> `PaymentTypeUk`, and it only matters that all *source* values can be mapped to target values. This mismatch would cause an exception if you use [mapping validation](Validating-Mappings).
+`PaymentTypeUk.Cheque` also mismatches, but the mapping is going from `PaymentTypeUs` -> `PaymentTypeUk`, and it only matters that all *source* values can be mapped to target values. This mismatch would cause an exception if you use [mapping validation](/Validating-Mappings).
 
 ## Configuring Enum Pairs
 
@@ -38,7 +38,7 @@ Mapper.WhenMapping
 
 ...which removes the enum mapping mismatch warning from the mapping plan, and stops the validation exception.
 
-Enum pairing can also be configured [inline](Inline-Configuration):
+Enum pairing can also be configured [inline](/configuration/Inline):
 
 ```cs
 Mapper.Map(usTransaction).ToANew<UkTransaction>(cfg => cfg

docs/src/Entity-Mapping.md

@@ -22,7 +22,7 @@ customerDto.Map().OnTo(customer);
 
 ### Using an Instance-Scoped Mapper
 
-Mappings performed via these extension methods use the default mapper - the same one you map with via the [static Mapper API](Static-vs-Instance-Mappers). To use an instance mapper with an extension method, use:
+Mappings performed via these extension methods use the default mapper - the same one you map with via the [static Mapper API](/Static-vs-Instance-Mappers). To use an instance mapper with an extension method, use:
 
 ```cs
 // Deep-clone a Customer using 

docs/src/Enum-Mapping.md

@@ -1,7 +1,7 @@
 By default:
 
 * Writable fields and properties, single-parameter methods prefixed with 'Set', constructor parameters and non-null, readonly complex type or enumerable members (except arrays) are targeted
-* Target members are matched to [compatibly-typed](Type-Conversion) source members by name
+* Target members are matched to [compatibly-typed](/Type-Conversion) source members by name
 * Source members prefixed with 'Get' are matched without the prefix - [`GetHashCode`](https://msdn.microsoft.com/en-us/library/system.object.gethashcode%28v=vs.100%29.aspx) and [`GetType`](https://msdn.microsoft.com/en-us/library/system.object.gettype(v=vs.100).aspx) are ignored
 * Members named `Id`, `<Type name>Id`, `Identifier` or `<Type name>Identifier` are matched
 * Target members with no compatible source member are ignored.
@@ -37,7 +37,7 @@ public class Address
 When mapping `CustomerViewModel` to `Customer`:
 
  - `Customer.Name` is populated using `CustomerViewModel.Name`
- - The `Customer.CustomerId` Guid is populated using the [parsed](Type-Conversion) `CustomerViewModel.Id` string
+ - The `Customer.CustomerId` Guid is populated using the [parsed](/Type-Conversion) `CustomerViewModel.Id` string
  - `Customer.HomeAddress` is populated with a new `Address` instance if one does not already exist
  - `Customer.HomeAddress.Line1` is populated using `CustomerViewModel.HomeAddressLine1`
  - `Customer.WorkAddress` is get-only, so is ignored if it's null