Proper layouting

This commit is contained in:
Tony Garnock-Jones 2019-08-18 22:08:55 +01:00
parent fc0ee42a98
commit 9f61059449
15 changed files with 429 additions and 37 deletions

View File

@ -1,11 +1,9 @@
---
projectpages: "https://gitlab.com/tonyg/preserves"
projecttree: "https://gitlab.com/tonyg/preserves/tree/master"
projectpages: "https://gitlab.com/preserves/preserves"
projecttree: "https://gitlab.com/preserves/preserves/tree/master"
title: "Preserves: an Expressive Data Language"
no_site_title: true
---
<title>Preserves: an Expressive Data Language</title>
<link rel="stylesheet" href="preserves.css">
# Preserves: an Expressive Data Language
This [repository]({{page.projectpages}}) contains a
[proposal](preserves.html) and
@ -13,9 +11,23 @@ This [repository]({{page.projectpages}}) contains a
*Preserves*, a new data model and serialization format in many ways
comparable to JSON, XML, S-expressions, CBOR, ASN.1 BER, and so on.
**WARNING** Everything in this repository is experimental and in flux!
The design of Preserves is not finalised and may change drastically.
Please offer any feedback you may have with this in mind.
> **WARNING** Everything in this repository is experimental and in
> flux! The design of Preserves is not finalised and may change
> drastically. Please offer any feedback you may have with this in
> mind.
## Core documents
- [Preserves tutorial](TUTORIAL.html)
- [Preserves specification](preserves.html), including semantics,
textual syntax, and compact binary syntax
## Additional resources
- Some [conventions for common data types](conventions.html)
- [Open questions](questions.html); see also the
[issues list]({{page.projectpages}}/issues)
- [Why not Just Use JSON?](why-not-json.html)
## Contact

View File

@ -1,6 +1,5 @@
---
---
<link rel="stylesheet" href="preserves.css">
TODO:

View File

@ -1,11 +1,10 @@
---
no_site_title: true
title: "Preserves: a tutorial"
---
<title>Preserves: a tutorial</title>
<link rel="stylesheet" href="preserves.css">
# Preserves: a tutorial
By Christopher Lemmer Webber and Tony Garnock-Jones
By Christopher Lemmer Webber and Tony Garnock-Jones
August 2019.
*This document, like Preserves itself, is released under*
*[version 2.0 of the Apache license](./LICENSE).*

View File

@ -5,3 +5,12 @@ highlighter: rouge
baseurl: "/preserves"
url: "/"
defaults:
-
scope:
path: ""
values:
layout: page
title: "Preserves"

8
_layouts/page.html Normal file
View File

@ -0,0 +1,8 @@
---
layout: skeleton
extra_html_headers: >
<link rel="stylesheet" href="{{ site.baseurl }}/normalize.css">
<link rel="stylesheet" href="{{ site.baseurl }}/preserves.css">
---
<h1>{{ page.title }}</h1>
{{ content }}

16
_layouts/skeleton.html Normal file
View File

@ -0,0 +1,16 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>{% unless page.no_site_title %}{{ site.title }}: {% endunless %}{{ page.title }}</title>
<meta name="author" content="Tony Garnock-Jones">
<meta name="viewport" content="width=device-width, initial-scale=1.0">{{
page.extra_html_headers | liquify }}{{
layout.extra_html_headers | liquify }}
</head>
<body>
{{ content }}
</body>
</html>

11
_plugins/liquify.rb Normal file
View File

@ -0,0 +1,11 @@
# http://stackoverflow.com/questions/14487110/include-jekyll-liquid-template-data-in-a-yaml-variable
module Jekyll
module LiquifyFilter
def liquify(input)
Liquid::Template.parse(input).render(@context)
end
end
end
Liquid::Template.register_filter(Jekyll::LiquifyFilter)

View File

@ -1,9 +1,6 @@
---
title: "Conventions for Common Data Types"
---
<title>Preserves: Conventions for Common Data Types</title>
<link rel="stylesheet" href="preserves.css">
# Preserves: Conventions for Common Data Types
The `Value` data type is essentially an S-Expression, able to
represent semi-structured data over `ByteString`, `String`,

349
normalize.css vendored Normal file
View File

@ -0,0 +1,349 @@
/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */
/* Document
========================================================================== */
/**
* 1. Correct the line height in all browsers.
* 2. Prevent adjustments of font size after orientation changes in iOS.
*/
html {
line-height: 1.15; /* 1 */
-webkit-text-size-adjust: 100%; /* 2 */
}
/* Sections
========================================================================== */
/**
* Remove the margin in all browsers.
*/
body {
margin: 0;
}
/**
* Render the `main` element consistently in IE.
*/
main {
display: block;
}
/**
* Correct the font size and margin on `h1` elements within `section` and
* `article` contexts in Chrome, Firefox, and Safari.
*/
h1 {
font-size: 2em;
margin: 0.67em 0;
}
/* Grouping content
========================================================================== */
/**
* 1. Add the correct box sizing in Firefox.
* 2. Show the overflow in Edge and IE.
*/
hr {
box-sizing: content-box; /* 1 */
height: 0; /* 1 */
overflow: visible; /* 2 */
}
/**
* 1. Correct the inheritance and scaling of font size in all browsers.
* 2. Correct the odd `em` font sizing in all browsers.
*/
pre {
font-family: monospace, monospace; /* 1 */
font-size: 1em; /* 2 */
}
/* Text-level semantics
========================================================================== */
/**
* Remove the gray background on active links in IE 10.
*/
a {
background-color: transparent;
}
/**
* 1. Remove the bottom border in Chrome 57-
* 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.
*/
abbr[title] {
border-bottom: none; /* 1 */
text-decoration: underline; /* 2 */
text-decoration: underline dotted; /* 2 */
}
/**
* Add the correct font weight in Chrome, Edge, and Safari.
*/
b,
strong {
font-weight: bolder;
}
/**
* 1. Correct the inheritance and scaling of font size in all browsers.
* 2. Correct the odd `em` font sizing in all browsers.
*/
code,
kbd,
samp {
font-family: monospace, monospace; /* 1 */
font-size: 1em; /* 2 */
}
/**
* Add the correct font size in all browsers.
*/
small {
font-size: 80%;
}
/**
* Prevent `sub` and `sup` elements from affecting the line height in
* all browsers.
*/
sub,
sup {
font-size: 75%;
line-height: 0;
position: relative;
vertical-align: baseline;
}
sub {
bottom: -0.25em;
}
sup {
top: -0.5em;
}
/* Embedded content
========================================================================== */
/**
* Remove the border on images inside links in IE 10.
*/
img {
border-style: none;
}
/* Forms
========================================================================== */
/**
* 1. Change the font styles in all browsers.
* 2. Remove the margin in Firefox and Safari.
*/
button,
input,
optgroup,
select,
textarea {
font-family: inherit; /* 1 */
font-size: 100%; /* 1 */
line-height: 1.15; /* 1 */
margin: 0; /* 2 */
}
/**
* Show the overflow in IE.
* 1. Show the overflow in Edge.
*/
button,
input { /* 1 */
overflow: visible;
}
/**
* Remove the inheritance of text transform in Edge, Firefox, and IE.
* 1. Remove the inheritance of text transform in Firefox.
*/
button,
select { /* 1 */
text-transform: none;
}
/**
* Correct the inability to style clickable types in iOS and Safari.
*/
button,
[type="button"],
[type="reset"],
[type="submit"] {
-webkit-appearance: button;
}
/**
* Remove the inner border and padding in Firefox.
*/
button::-moz-focus-inner,
[type="button"]::-moz-focus-inner,
[type="reset"]::-moz-focus-inner,
[type="submit"]::-moz-focus-inner {
border-style: none;
padding: 0;
}
/**
* Restore the focus styles unset by the previous rule.
*/
button:-moz-focusring,
[type="button"]:-moz-focusring,
[type="reset"]:-moz-focusring,
[type="submit"]:-moz-focusring {
outline: 1px dotted ButtonText;
}
/**
* Correct the padding in Firefox.
*/
fieldset {
padding: 0.35em 0.75em 0.625em;
}
/**
* 1. Correct the text wrapping in Edge and IE.
* 2. Correct the color inheritance from `fieldset` elements in IE.
* 3. Remove the padding so developers are not caught out when they zero out
* `fieldset` elements in all browsers.
*/
legend {
box-sizing: border-box; /* 1 */
color: inherit; /* 2 */
display: table; /* 1 */
max-width: 100%; /* 1 */
padding: 0; /* 3 */
white-space: normal; /* 1 */
}
/**
* Add the correct vertical alignment in Chrome, Firefox, and Opera.
*/
progress {
vertical-align: baseline;
}
/**
* Remove the default vertical scrollbar in IE 10+.
*/
textarea {
overflow: auto;
}
/**
* 1. Add the correct box sizing in IE 10.
* 2. Remove the padding in IE 10.
*/
[type="checkbox"],
[type="radio"] {
box-sizing: border-box; /* 1 */
padding: 0; /* 2 */
}
/**
* Correct the cursor style of increment and decrement buttons in Chrome.
*/
[type="number"]::-webkit-inner-spin-button,
[type="number"]::-webkit-outer-spin-button {
height: auto;
}
/**
* 1. Correct the odd appearance in Chrome and Safari.
* 2. Correct the outline style in Safari.
*/
[type="search"] {
-webkit-appearance: textfield; /* 1 */
outline-offset: -2px; /* 2 */
}
/**
* Remove the inner padding in Chrome and Safari on macOS.
*/
[type="search"]::-webkit-search-decoration {
-webkit-appearance: none;
}
/**
* 1. Correct the inability to style clickable types in iOS and Safari.
* 2. Change font properties to `inherit` in Safari.
*/
::-webkit-file-upload-button {
-webkit-appearance: button; /* 1 */
font: inherit; /* 2 */
}
/* Interactive
========================================================================== */
/*
* Add the correct display in Edge, IE 10+, and Firefox.
*/
details {
display: block;
}
/*
* Add the correct display in all browsers.
*/
summary {
display: list-item;
}
/* Misc
========================================================================== */
/**
* Add the correct display in IE 10+.
*/
template {
display: none;
}
/**
* Add the correct display in IE 10.
*/
[hidden] {
display: none;
}

View File

@ -1,6 +1,5 @@
---
---
<link rel="stylesheet" href="preserves.css">
Motivations goals and priorities would be good - up front
- so, I say values have an order and can be compared but NOT WHY that's useful

View File

@ -1,6 +1,7 @@
body {
font-family: palatino, "Palatino Linotype", "Palatino LT STD", "URW Palladio L", "TeX Gyre Pagella", serif;
box-sizing: border-box;
line-height: 1.414;
}
@media screen {
body { padding-top: 2rem; max-width: 40em; margin: auto; font-size: 120%; }
@ -8,7 +9,7 @@ body {
}
@media print {
@page { size: letter; margin: 4rem 0rem 4.333rem 0rem; }
body { margin-left: 4.5rem; margin-right: 4.5rem; }
body { margin-left: 4.5rem; margin-right: 4.5rem; line-height: 0.98; }
h1, h2 { page-break-before: always; margin-top: 0; }
h1:first-of-type, h2:first-of-type { page-break-before: auto; }
hr+* { page-break-before: always; margin-top: 0; }
@ -18,7 +19,7 @@ h1, h2, h3, h4, h5, h6 { color: #4f81bd; }
h2 { border-bottom: solid #4f81bd 1px; }
pre, code { background-color: #eee; font-family: "DejaVu Sans Mono", monospace; }
code { font-size: 75%; }
pre { padding: 0.33rem; }
pre { padding: 0.33rem; line-height: 1; }
body {
counter-reset: section 0 subsection 0 appendix 0;

View File

@ -1,9 +1,7 @@
---
no_site_title: true
title: "Preserves: an Expressive Data Language"
---
<title>Preserves: an Expressive Data Language</title>
<link rel="stylesheet" href="preserves.css">
# Preserves: an Expressive Data Language
Tony Garnock-Jones <tonyg@leastfixedpoint.com>
August 2019. Version 0.0.6.

View File

@ -1,9 +1,6 @@
---
title: "Open questions"
---
<title>Preserves: Open questions</title>
<link rel="stylesheet" href="preserves.css">
# Open questions
Q. Should "symbols" instead be URIs? Relative, usually; relative to
what? Some domain-specific base URI?

View File

@ -1,9 +1,6 @@
---
title: "Representing Values in Programming Languages"
---
<title>Preserves: Representing Values in Programming Languages</title>
<link rel="stylesheet" href="preserves.css">
# Preserves: Representing Values in Programming Languages
**NOT YET READY**

View File

@ -1,9 +1,9 @@
---
title: "Why not Just Use JSON?"
---
<title>Preserves: Why not Just Use JSON?</title>
<link rel="stylesheet" href="preserves.css">
# Why not Just Use JSON?
Tony Garnock-Jones <tonyg@leastfixedpoint.com>
September 2018.
<!-- JSON lacks semantics: JSON syntax doesn't denote anything -->