Rewrite home page and add more information and links

_config.yml

@@ -22,7 +22,6 @@ url: "" # the base hostname & protocol for your site, e.g. http://example.com
 twitter_username: ethereum
 github_username:  ethereum
 header_pages:
- - index.html
  - core.html
  - networking.html
  - interface.html

index.html

@@ -17,20 +17,27 @@ title: Home
   <li><strong>Deferred</strong> an EIP that is not being considered for immediate adoption. May be reconsidered in the future for a subsequent hard fork.</li>
 </ul>
 
-{% assign statuses = site.pages|map:"status"|uniq %}
+<h2>EIP Types</h2>
-{% assign pages = site.pages|sort:"eip" %}
+
-{% for status in statuses %}
+<p>EIPs are separated into a number of types, and each has its own list of EIPs.</p>
-  {% if status != undefined %}
+
-    <h1>{{status}}</h1>
+<h3>Standard Track</h3>
-    <table>
+<p>A <strong>Standard Track EIP</strong> describes any change that affects most or all Ethereum implementations, such as a change to the the network protocol, a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using Ethereum. Furthermore Standard EIPs can be broken down into the following categories.</p>
-      <thead>
+
-        <tr><th>Number</th><th>Title</th><th>Author</th><th>Layer</th></tr>
+<h4><a href="{{"core"|relative_url}}">Core</a></h4>
-      </thead>
+<p>Improvements requiring a consensus fork (e.g. <a href="EIPS/eip-5">EIP5</a>, <a href="EIPS/eip-101">EIP101</a>), as well as changes that are not necessarily consensus critical but may be relevant to “core dev” discussions (for example, <a href="EIPS/eip-90">EIP90</a>, and the miner/node strategy changes 2, 3, and 4 of <a href="EIPS/eip-86">EIP86</a>).</p>
-      {% for page in pages %}
+
-        {% if page.status == status %}
+<h4><a href="{{"networking"|relative_url}}">Networking</a></h4>
-          <tr><td><a href="{{page.url|relative_url}}">{{page.eip|xml_escape}}</a></td><td>{{page.title|xml_escape}}</td><td>{{page.author|xml_escape}}</td><td>{{page.layer|xml_escape}}</td></tr>
+<p>Includes improvements around devp2p (<a href="EIPS/eip-8">EIP8</a>) and Light Ethereum Subprotocol, as well as proposed improvements to network protocol specifications of whisper and swarm.</p>
-        {% endif %}
+
-      {% endfor %}
+<h4><a href="{{"interface"|relative_url}}">Interface</a></h4>
-    </table>
+<p>Includes improvements around client API/RPC specifications and standards, and also certain language-level standards like method names (<a href="EIPS/eip-59">EIP59</a>, <a href="EIPS/eip-6">EIP6</a>) and contract ABIs. The label “interface” aligns with the interfaces repo and discussion should primarily occur in that repository before an EIP is submitted to the EIPs repository.</p>
-  {% endif %}
+
-{% endfor %}
+<h4><a href="{{"erc"|relative_url}}">ERC</a></h4>
+<p>Application-level standards and conventions, including contract standards such as token standards (<a href="EIPS/eip-20">ERC20</a>), name registries (<a href="EIPS/eip-26">ERC26</a>, <a href="EIPS/eip-137">ERC137</a>), URI schemes (<a href="EIPS/eip-67">ERC67</a>), library/package formats (<a href="EIPS/eip-82">EIP82</a>), and wallet formats (<a href="EIPS/eip-75">EIP75</a>, <a href="EIPS/eip-85">EIP85</a>).</p>
+
+<h3><a href="{{"informational"|relative_url}}">Informational</a></h3>
+<p>Describes a Ethereum design issue, or provides general guidelines or information to the Ethereum community, but does not propose a new feature. Informational EIPs do not necessarily represent Ethereum community consensus or a recommendation, so users and implementers are free to ignore Informational EIPs or follow their advice.</p>
+
+<h3><a href="{{"meta"|relative_url}}">Meta</a></h3>
+<p>Describes a process surrounding Ethereum or proposes a change to (or an event in) a process. Process EIPs are like Standards Track EIPs but apply to areas other than the Ethereum protocol itself. They may propose an implementation, but not to Ethereum's codebase; they often require community consensus; unlike Informational EIPs, they are more than recommendations, and users are typically not free to ignore them. Examples include procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Ethereum development. Any meta-EIP is also considered a Process EIP.</p>