diff --git a/.travis.yml b/.travis.yml index e4188d85ea..f2a2a153dd 100644 --- a/.travis.yml +++ b/.travis.yml @@ -9,7 +9,7 @@ before_script: # the `install` step will run `bundle install` by default. script: - bundle exec jekyll build - - bundle exec htmlproofer ./_site --assume-extension --only-4xx --checks-to-ignore=ImageCheck,ScriptCheck --allow-missing-href --allow-hash-href + - bundle exec htmlproofer ./_site --assume-extension --only-4xx --allow-hash-href env: global: diff --git a/docs/_clef/Overview.md b/docs/_clef/Overview.md index f38949f71b..7e7b4bef91 100644 --- a/docs/_clef/Overview.md +++ b/docs/_clef/Overview.md @@ -51,7 +51,7 @@ The basic premise being, The general flow for signing a transaction using e.g. geth is as follows: -![image](sign_flow.png) +![Sign flow](sign_flow.png) Clef relies on __sign-what-you-see__. To provide as much context as possible, @@ -65,14 +65,14 @@ Clef relies on __sign-what-you-see__. To provide as much context as possible, One setup scenario is to use virtualization, e.g. within QubesOS, where to Clef is deployed on a non-networked machine (`ethvault` below) -![](clef_qubes_qrexec.png) +![Qubes](clef_qubes_qrexec.png) Another option is to deploy Clef on a separate physical device, e.g. USB Armory, and access the CLI-UI via SSH on the interface provided by the USB ethernet adapter, and expose HTTP interface via tunneling. -![](https://inversepath.com/images/usbarmory_coin_web.jpg) +![USB armory from Inverse Path](https://inversepath.com/images/usbarmory_mark-one/usbarmory_coin_web.jpg) ## Multi-user setup @@ -122,9 +122,9 @@ Enter password to approve: This is called the `internal api`, or `ui-api`. -![](clef_architecture_pt1.png) +![Clef architecture 1](clef_architecture_pt1.png) -![](clef_architecture_pt2.png) +![Clef architecture 2](clef_architecture_pt2.png) ### Rules @@ -247,13 +247,13 @@ In order to use rules, keystore passwords must be stored in `clef`. Clef uses an The `clef` daemon can be wrapped by an external process, which can then take the part of a UI. -![](clef_architecture_pt3.png) +![Clef architecture 3](clef_architecture_pt3.png) QT UI on Ubuntu -![](https://raw.githubusercontent.com/holiman/qtsigner/master/screenshot.png) +![QT UI on Ubuntu](https://raw.githubusercontent.com/holiman/qtsigner/master/screenshot.png) GTK UI on Qubes -![](https://raw.githubusercontent.com/ethereum/go-ethereum/master/cmd/clef/docs/qubes/qubes_newaccount-2.png) +![GTK UI on Qubes](https://raw.githubusercontent.com/ethereum/go-ethereum/master/cmd/clef/docs/qubes/qubes_newaccount-2.png) ### Rules for UI apis @@ -298,6 +298,6 @@ a corresponding (or exceeding) feature set: * EIP 191/712 - signing typed data Clef can even sign Clique headers in a private network -![](clef_architecture_pt4.png) +![Clef architecture 4](clef_architecture_pt4.png) diff --git a/docs/_developers/Libraries-and-Inproc-Ethereum-Nodes.md b/docs/_developers/Libraries-and-Inproc-Ethereum-Nodes.md index e787d1f945..61978aa4af 100644 --- a/docs/_developers/Libraries-and-Inproc-Ethereum-Nodes.md +++ b/docs/_developers/Libraries-and-Inproc-Ethereum-Nodes.md @@ -41,7 +41,7 @@ To get you hands dirty, here's a code snippet that will * Display some initial infos about your node * Subscribe to new blocks and display them live as they arrive - +Android in-process node ```java import org.ethereum.geth.*; diff --git a/docs/_interface/JavaScript-Console.md b/docs/_interface/JavaScript-Console.md index 907bb01278..18950c8a74 100644 --- a/docs/_interface/JavaScript-Console.md +++ b/docs/_interface/JavaScript-Console.md @@ -72,6 +72,6 @@ In addition to the full functionality of JS (as per ECMA5), the ethereum JSRE is # Management APIs -Beside the official [DApp API](https://github.com/ethereum/wiki/JSON-RPC) interface the go ethereum node has support for additional management API's. These API's are offered using [JSON-RPC](http://www.jsonrpc.org/specification) and follow the same conventions as used in the DApp API. The go ethereum package comes with a console client which has support for all additional API's. +Beside the official [DApp API](https://github.com/ethereum/wiki/wiki/JSON-RPC) interface the go ethereum node has support for additional management API's. These API's are offered using [JSON-RPC](http://www.jsonrpc.org/specification) and follow the same conventions as used in the DApp API. The go ethereum package comes with a console client which has support for all additional API's. [The management API has its own page](management-apis). diff --git a/index.html b/index.html index 2d9055f63f..5fa8d5e448 100644 --- a/index.html +++ b/index.html @@ -14,7 +14,7 @@ css:
- + Geth mascot
@@ -25,7 +25,7 @@ css:

See our website or read the docs for more infos!

- + Ethereum logo
@@ -36,7 +36,7 @@ css:

See our repository and downloads section for the code!

- + Geth mascot