Fix Markdown rendering within summary/detail (ethereum#2059)

* Fix Markdown rendering within summary/detail

* Add vendor to .gitignore

* Remove duplicate github-pages entry from Gemfile

* Require github-pages 198

This brings in fixes to kramdown.

* Remove explicit jekyll version as github-pages brings it in as a dependency

* Update bundler dependency tree

* Fake bundler version

* use Ruby 2.3.0

* Set sane defaults for kramdown

* Fix links after kramdown update

* Remove <details> formatting from EIP-1474 as it is not working with embedded markdown

* Revert "Fix Markdown rendering within summary/detail"

* Fix email in EIP-1812

* Remove <details> formatting from EIP-1620 as it is not working with embedded markdown

.gitignore

@@ -1,3 +1,4 @@
 _site
 .sass-cache
 .jekyll-metadata
+vendor

.travis.yml

@@ -23,17 +23,17 @@ env:
 matrix:
   fast_finish: true
   include:
-    - rvm: 2.2.5
+    - rvm: 2.3.0
       env: TASK='htmlproofer'
-    - rvm: 2.2.5
+    - rvm: 2.3.0
       env: TASK='htmlproofer-external'
-    - rvm: 2.2.5
+    - rvm: 2.3.0
       env: TASK='eip-validator'
     - python: 3.3
       env: TASK='codespell'
       before_script: "sudo pip install urllib3[secure] && sudo pip install codespell"
   allow_failures:
-    - rvm: 2.2.5
+    - rvm: 2.3.0
       env: TASK='htmlproofer-external'
 
 notifications:

EIPS/eip-1057.md

@@ -238,7 +238,7 @@ The inner loop uses FNV and KISS99 to generate a random sequence from the `prog_
 
 Since the `prog_seed` changes only once per `PROGPOW_PERIOD` it is expected that while mining `progPowLoop` will be evaluated on the CPU to generate source code for that period's sequence.  The source code will be compiled on the CPU before running on the GPU.  
 
-Test vectors can be found [in the test vectors file](../assets/eip-1057/test-vectors.md#progPowInit).
+Test vectors can be found [in the test vectors file](../assets/eip-1057/test-vectors.md#progpowinit).
 
 ```cpp
 kiss99_t progPowInit(uint64_t prog_seed, int mix_seq_dst[PROGPOW_REGS], int mix_seq_src[PROGPOW_REGS])
@@ -328,7 +328,7 @@ The flow of the inner loop is:
 
 `DAG_BYTES` is set to the number of bytes in the current DAG, which is generated identically to the existing Ethash algorithm.  
 
-Test vectors can be found [in the test vectors file](../assets/eip-1057/test-vectors.md#progPowLoop).
+Test vectors can be found [in the test vectors file](../assets/eip-1057/test-vectors.md#progpowloop).
 
 ```cpp
 void progPowLoop(
@@ -488,7 +488,7 @@ digest: 11f19805c58ab46610ff9c719dcf0a5f18fa2f1605798eef770c47219274767d
 result: 5b7ccd472dbefdd95b895cac8ece67ff0deb5a6bd2ecc6e162383d00c3728ece
 ```
 
-Additional test vectors can be found [in the test vectors file](../assets/eip-1057/test-vectors.md#progPowHash).
+Additional test vectors can be found [in the test vectors file](../assets/eip-1057/test-vectors.md#progpowhash).
 ### progpow 0.9.3
 [Machine-readable test vectors](https://github.com/ethereum/EIPs/blob/ad4e73f239d53d72a21cfd8fdc89dc81eb9d2688/assets/eip-1057/test-vectors-0.9.3.json)
 

EIPS/eip-1102.md

@@ -38,7 +38,7 @@ ethereum.send('eth_requestAccounts'): Promise<string>
 
 #### Provider#enable (DEPRECATED)
 
-**Note: This method is deprecated in favor of the RPC method [`eth_requestAccounts`](#eth_requestAccounts).**
+**Note: This method is deprecated in favor of the RPC method [`eth_requestAccounts`](#eth_requestaccounts).**
 
 Providers exposed by Ethereum-enabled DOM environments define a new RPC method: `ethereum.enable()`. Calling this method triggers a user interface that allows the user to approve or reject account access for a given dapp. This method returns a `Promise` that is resolved with an `Array` of accounts if the user approves access or rejected with an `Error` if the user rejects access.
 

EIPS/eip-1123.md

@@ -1208,8 +1208,6 @@ To reference a contract type from a dependency, use the format
     section.
 
 
-<div id="address"></div>
-
 #### Address: `address`
 
 The `address` field defines the [Address](#term-address) of the
@@ -1326,8 +1324,6 @@ Every entry in the `link_references` for this bytecode **must** have a
 corresponding entry in the `link_dependencies` section.
 
 
-<div id="compiler-compiler-1"></div>
-
 #### Compiler: `compiler`
 
 The `compiler` field defines the compiler information that was used
@@ -1397,8 +1393,6 @@ The `name` field defines which compiler was used in compilation.
 </table>
 
 
-<div id="version-version-1"></div>
-
 #### Version: `version`
 
 The `version` field defines the version of the compiler. The field