Finalise publication page design

_config.yml

@@ -32,3 +32,5 @@ scholar:
 
   group_by: year
   group_order: descending
+
+  repository: papers

_layouts/publication.html

@@ -8,26 +8,15 @@ menu: false
       <div class="card-block">
         <h5 class="card-title">Venue</h5>
         <p class="card-text">{{ page.entry.booktitle }}</p>
-      </div>
-      <div class="card-block">
         <h5 class="card-title">Publication Year</h5>
         <p class="card-text">{{ page.entry.year }}</p>
-      </div>
-      <div class="card-block">
         <h5 class="card-title">Keywords</h5>
         <p class="card-text">{{ page.entry.keywords }}</p>
-      </div>
-      <div class="card-block">
-        <h5 class="card-title">DOI</h5>
-        <p class="card-text"><a href="http://dx.doi.org/{{ page.entry.doi }}">{{ page.entry.doi }}</a>
-      </div>
-      <div class="card-block">
-        <h5 class="card-title">ISBN</h5>
-        <p class="card-text">{{ page.entry.isbn }}</p>
-      </div>
-      <div class="card-block">
-        <h5 class="card-title">BibTeX</h5>
-        <textarea class="form-control" rows="10">{{ page.entry.bibtex }}</textarea>
+        <h5 class="card-title">Identifiers</h5>
+        <ul class="site-card-list">
+          <li>DOI: <a href="http://dx.doi.org/{{ page.entry.doi }}">{{ page.entry.doi }}</a></li>
+          <li>ISBN: {{ page.entry.isbn }}</li>
+        </ul>
       </div>
     </div>
   </div>
@@ -42,8 +31,25 @@ menu: false
     </p>
     {% endif %}
 
+    <h3>Full Text</h3>
+    <p>{{ page.entry.numpages }} pages</p>
+    <ul class="fa-ul">
+      {% if page.link %}<li><a href="{{ page.link }}"><i class="fa fa-li fa-file-text-o"></i>Authors' Preprint</a></li>{% endif %}
+      <li><a href="http://dx.doi.org/{{ page.entry.doi }}"><i class="fa fa-li fa-external-link"></i>Published Edition</a></li>
+    </ul>
+
+    {% comment %}
     <h3>Supplementary Material</h3>
+    <ul class="fa-ul">
+      <li><a href=""><i class="fa fa-li fa-file-text-o"></i>Technical Report</a></li>
+      <li><a href=""><i class="fa fa-li fa-file-archive-o"></i>Download (.zip)</a></li>
+      <li><a href=""><i class="fa fa-li fa-code-fork"></i>Code Repository</a></li>
+      <li><a href=""><i class="fa fa-li fa-file-code-o"></i>Code File</a></li>
+    </ul>
+    {% endcomment %}
 
+    <h3>Export Citation</h3>
+    <textarea class="form-control" rows="10">{{ page.entry.bibtex }}</textarea>
   </div>
 </div>
 

css/blog.css

@@ -180,6 +180,11 @@ h6, .h6 {
 }
 
 
+.site-card-list {
+  list-style-position: inside;
+  padding-left: 0px;
+}
+
 /*
  * Footer
  */

papers/README.md

+Paper Downloads
+===============
+
+Papers and supporting supplimentary material should be placed in this directory.
+
+Check with the publisher's T&Cs to determine which version of the paper you are allowed to publish here. Often it is
+only the pre-print edition that is passed to the publisher **before** they make any changes. The final proof copy and
+the publisher's own copy is often not permitted to be published.
+
+The paper should also be deposited into [Imperial Spiral](http://spiral.imperial.ac.uk/).
+
+Files should be named by their key in the publications BibTeX file, suffixed with the appropriate extension.
+
+Technical reports should be named as ***bibtex_key***.techreport.***ext***
+
+Additional file types are also supportable, see /_layouts/publication.html to add extra ones to the supplimentary
+material section of a publication page.

publications.bib

@@ -17,7 +17,24 @@ title: Publications
   Keywords                 = {JavaScript, mechanised Semantics, Coq},
   Location                 = {San Diego, CA, USA},
   Numpages                 = {14},
-  Abstract                 = { This is the abstract for the paper. },
+  Abstract                 = {
+  JavaScript is the most widely used web language for client-side
+  applications.  Whilst the development of JavaScript was initially just led
+  by implementation, there is now increasing momentum behind the ECMA
+  standardisation process. The time is ripe for a formal, mechanised
+  specification of JavaScript, to clarify ambiguities in the ECMA
+  standards, to serve as a trusted reference for high-level language
+  compilation and JavaScript implementations, and  to provide a platform for
+  high-assurance proofs of language properties.
+
+  We present JSCert, a formalisation of the current ECMA standard in
+  the Coq proof assistant, and JSRef, a reference interpreter for JavaScript
+  extracted from Coq to OCaml.  We give  a Coq proof that JSRef is correct with respect to
+  JSCert and assess JSRef using test262, the ECMA  conformance test
+  suite. Our methodology ensures  that JSCert is a comparatively  accurate 
+  formulation of the English standard, which will only improve as time goes on. We have
+  demonstrated that modern techniques of mechanised specification can handle the complexity of JavaScript.
+  }
 }
 
 @InProceedings{Gardner2008Local,