diff --git a/_config.yml b/_config.yml index 7a48a3a14..adc9263cf 100644 --- a/_config.yml +++ b/_config.yml @@ -19,7 +19,7 @@ header_pages: collections: specs: output: true - permalink: /ECIPs/:slug/ + permalink: /ECIPs/:path defaults: - scope: @@ -27,7 +27,7 @@ defaults: values: layout: ecip -permalink: /:slug +permalink: /:path exclude: - Gemfile diff --git a/_includes/eiptable.html b/_includes/eiptable.html index 8c7363d7d..5bffc7ce8 100644 --- a/_includes/eiptable.html +++ b/_includes/eiptable.html @@ -8,7 +8,7 @@ } {% for status in site.data.statuses %} - {% assign eips = include.eips|where:"status",status|sort:"eip" %} + {% assign eips = include.eips|where:"status",status|sort:"ecip" %} {% assign count = eips|size %} {% if count > 0 %}
ECIPs are separated into a number of types, and each has its own list of ECIPs.
-Describes any change that affects most or all Ethereum Classic 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 Classic. Furthermore Standard ECIPs can be broken down into the following categories.
-Improvements requiring a consensus fork, as well as changes that are not necessarily consensus critical but may be relevant to “core dev” discussions.
-Includes improvements around client API/RPC specifications and standards, and also certain language-level standards like method names and contract ABIs. The label “interface” aligns with the interfaces repo and discussion should primarily occur in that repository before an ECIP is submitted to the ECIPs repository.
-Application-level standards and conventions, including contract standards such as token standards, name registries, URI schemes, library/package formats, and wallet formats.
-Describes a process surrounding Ethereum Classic or proposes a change to (or an event in) a process. Process ECIPs are like Standards Track ECIPs but apply to areas other than the Ethereum Classic protocol itself. They may propose an implementation, but not to Ethereum Classic's codebase; they often require community consensus; unlike Informational ECIPs, 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 Classic development. Any meta-ECIP is also considered a Process ECIP.
-Describes a Ethereum Classic design issue, or provides general guidelines or information to the Ethereum Classic community, but does not propose a new feature. Informational ECIPs do not necessarily represent Ethereum Classic community consensus or a recommendation, so users and implementers are free to ignore Informational ECIPs or follow their advice.
diff --git a/informational.html b/informational.html index b156069e9..f59e7dd65 100644 --- a/informational.html +++ b/informational.html @@ -3,5 +3,5 @@ title: Informational --- -{% assign eips=site.specs|where:"type","Informational" %} +{% assign eips=site.specs|where:"lang","en"|where:"type","Informational" %} {% include eiptable.html eips=eips %} diff --git a/interface.html b/interface.html index 8f9d71dc2..039b4a86e 100644 --- a/interface.html +++ b/interface.html @@ -3,5 +3,5 @@ title: Interface --- -{% assign eips=site.specs|where:"type","Standards Track"|where:"category","Interface" %} +{% assign eips=site.specs|where:"lang","en"|where:"type","Standards Track"|where:"category","Interface" %} {% include eiptable.html eips=eips %} diff --git a/meta.html b/meta.html index 21bbdc44e..05a598fbb 100644 --- a/meta.html +++ b/meta.html @@ -3,5 +3,5 @@ title: Meta --- -{% assign eips=site.specs|where:"type","Meta" %} +{% assign eips=site.specs|where:"lang","en"|where:"type","Meta" %} {% include eiptable.html eips=eips %}