Merge branch 'master'
Conflicts: INDEX.md
This commit is contained in:
gauthiier
parent
53a644827a
commit
e83f9c5116
50
INDEX.md
50
INDEX.md
@ -1,40 +1,60 @@
|
|||||||
---
|
---
|
||||||
|
title: wwwrite
|
||||||
|
author: gauthiier
|
||||||
bibliography: wwwrite.bib
|
bibliography: wwwrite.bib
|
||||||
|
cover: img/DSP6.png
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
# Intent
|
# Intent
|
||||||
|
|
||||||
|
|
||||||
This site is intended to introduce humanities research writers how to write text in a modern fashion using their computers. The aim of the lessons listed below are points of departure for the practice of writing text using simple, basic yet advance systems and technologies. Part of this endeavour is first and foremost to empower writers to use these systems in presenting simple didactic material working towards bootstrapping their understanding of writing technologies and help them develop a new type of literacy (albeit an electronic one). Another goals of this site is to present the historical trajectories of modern writing systems by emphasising on their phylogenesis. Computerised writing systems and related methods (as we will see) have a long history following that of writing itself; the double-valance between the practice of writing and the mode of inscription (technologies) is an important (research) topic in the humanities [@pontin_how_2012; @kirschenbaum_bookwriting_2013; @kirschenbaum_mechanisms:_2012; @kittler_discourse_1990].
|
This site is intended to introduce humanities research writers how to write text in a modern fashion using their computers. The aim of the lessons listed below are points of departure for the practice of writing text using simple, basic yet advance systems and technologies. Part of this endeavour is first and foremost to empower writers to use these systems in presenting simple didactic material working towards bootstrapping their understanding of writing technologies and help them develop a new type of literacy (albeit an electronic one). Another goals of this site is to present the historical trajectories of modern writing systems by emphasising on their phylogenesis. Computerised writing systems and related methods (as we will see) have a long history following that of writing itself; the double-valance between the practice of writing and the mode of inscription (technologies) is an important (research) topic in the humanities [@pontin_how_2012; @kirschenbaum_bookwriting_2013; @kirschenbaum_mechanisms:_2012; @kittler_discourse_1990].
|
||||||
|
|
||||||
# Philosophy
|
# Philosophy
|
||||||
|
|
||||||
The idea in compiling this site-lesson is two fold:
|
The idea in compiling this site-lesson is two fold:
|
||||||
|
|
||||||
(1) present an alternative to the use of proprietary software for writing academic texts:
|
(1) Present an alternative to the use of proprietary software for writing academic texts:
|
||||||
|
|
||||||
Considering the hegemonic use of proprietary software to write academic and non-academic texts (MS Word, Google Docs, Apple Pages, etc.) it is important to underline alternatives as these software not only “hide” their inner workings to scrutiny but most importantly may fall short in providing writers with adequate functionality required in writing academic texts [^1]. Obfuscation is impractical (and problematic) obviously so for academics in the Humanities.
|
>Considering the hegemonic use of proprietary software to write academic and non-academic texts (MS Word, Google Docs, Apple Pages, etc.) it is important to underline alternatives as these software not only “hide” their inner workings to scrutiny but most importantly may fall short in providing writers with adequate functionality required in writing academic texts [^1]. Obfuscation is impractical (and problematic) obviously so for academics in the Humanities.
|
||||||
|
|
||||||
|
|
||||||
We believe in texts that we can read, that is, we will utilise (as much as possible) software which is made “open” for us to read the source code and formats that are [human-readable](https://en.wikipedia.org/wiki/Human-readable_medium) as opposed to solely [machine-readable](https://en.wikipedia.org/wiki/Machine-readable_data). Hence, throughout the lessons, we will be inspecting files and writing ones that are augmented with special codes that machines can understand. This idea of writing "meta-data" into the text or more precisely _markup_ text in a file is very important in making sure the text is human _and_ machine readable.
|
>We believe in texts that we can read, that is, we will utilise (as much as possible) software which is made “open” for us to read the source code and formats that are [human-readable](https://en.wikipedia.org/wiki/Human-readable_medium) as opposed to solely [machine-readable](https://en.wikipedia.org/wiki/Machine-readable_data). Hence, throughout the lessons, we will be inspecting files and writing ones that are augmented with special codes that machines can understand. This idea of writing "meta-data" into the text or more precisely _markup_ text in a file is very important in making sure the text is human _and_ machine readable.
|
||||||
|
|
||||||
(2) to offer a glimpse into methods, practices and systems of software writing:
|
(2) Offer a glimpse into methods, practices and systems of software writing:
|
||||||
|
|
||||||
As you may already know, writing software is primarily a textual-based practice. Writing code is all about text, keyboards, text editors, line count, syntax and the likes. Hence an important amount of systems and technologies have been devised for the composition of software (as text). From syntax highlighting to version control, these systems have a long history and can possibly provide academic writers with powerful literary tools that can enable them to bolster their prose[^2]. In exposing (and historicising) these systems our objective is for the reader to relate to modern software writing systems not as merely a tool but as system with a culture. In no way we expect readers to become "programmers", far from this, we would rather present them the basics of writing text using (modern) computer systems while hoping that they'll develop a critical stance on these systems' genesis, conditions, limitations and capabilites.
|
>As you may already know, writing software is primarily a textual-based practice. Writing code is all about text, keyboards, text editors, line count, syntax and the likes. Hence an important amount of systems and technologies have been devised for the composition of software (as text). From syntax highlighting to version control, these systems have a long history and can possibly provide academic writers with powerful literary tools that can enable them to bolster their prose.[^2] In exposing (and historicising) these systems our objective is for the reader to relate to modern software writing systems not as merely a tool but as system with a culture. In no way we expect readers to become "programmers", far from this, we would rather present them the basics of writing text using (modern) computer systems while hoping that they'll develop a critical stance on these systems' genesis, conditions, limitations and capabilites.
|
||||||
|
|
||||||
# Scheme
|
# Scheme
|
||||||
|
|
||||||
The current site is segmented in six lessons covering the (very) basics of writing academic texts on a computer[^3]. The overall composition of these lessons are by no mean derived from "Principles" or (even worst) "Best-practices" but rather stand as loosely coupled set of lessons that can be traversed all together (or not) in a short period of time. The site is neither a manual nor a manifesto. It covers the fundamentals such as: looking up how text is encoded/decoded in computer memory, presents how one can manipulate files and issue computing commands using what is known as a terminal, introduces a markup language (markdown) that is used to format and annotate text, introduces a text / document processor (pandoc) which converts files written in a format into another, it looks at how to compile and maintain a bibliography using open source software (Zotero) and export references into a document, and finally discuss how to style (colour, margins, cover image, etc.) a given ouput from the text / document processor.
|
|
||||||
|
|
||||||
(1) Lesson 1: Text Encoding
|
The current site is segmented in six lessons covering the (very) basics of writing academic texts on a computer.[^3] The overall composition of these lessons is by no mean derived from obscure "Principles" or (even worst) "Best-practices" but rather stand as loosely coupled set of lessons that can be traversed all together (or not) in a short period of time. The site is neither a manual nor a manifesto and should be seen as a starting point into further developing (creative) technics and methods in text writing.
|
||||||
looking up how text is encoded/decoded in computer memory,
|
|
||||||
(2) Lesson 2: Terminal
|
|
||||||
(3) Lesson 3: Markup / Markdown
|
|
||||||
(4) Lesson 4: (Text) Processor
|
|
||||||
(5) Lesson 5: Bibliographer
|
|
||||||
(6) Lesson 6: Styling
|
|
||||||
|
|
||||||
|
* [Lesson 1: Text Encoding](/)
|
||||||
|
|
||||||
|
>Covers fundamentals of representation of text looking up how text is encoded/decoded as data.
|
||||||
|
|
||||||
|
* [Lesson 2: Terminal](/)
|
||||||
|
|
||||||
|
>Presents how one can manipulate files and issue computing commands using what is known as a terminal.
|
||||||
|
|
||||||
|
* [Lesson 3: Markup / Markdown](/)
|
||||||
|
|
||||||
|
>Introduces a markup language ([Markdown](http://daringfireball.net/projects/markdown/)) that is used to format and annotate text.
|
||||||
|
|
||||||
|
* [Lesson 4: (Text) Processor](/)
|
||||||
|
|
||||||
|
>Introduces a text / document processor ([Pandoc](http://johnmacfarlane.net/pandoc/)) which converts files written in a format into another.
|
||||||
|
|
||||||
|
* [Lesson 5: Bibliographer](/)
|
||||||
|
|
||||||
|
>Looks at how to compile and maintain a bibliography using open source software ([Zotero](https://www.zotero.org)) and export references into a document
|
||||||
|
|
||||||
|
* [Lesson 6: Styling](/)
|
||||||
|
|
||||||
|
>Discuss how to style (colour, margins, cover image, etc.) a given output from the text / document processor
|
||||||
|
|
||||||
|
As a final note worth mentioning (before delving further): all the lessons of this site, including this page, have been (are) written using the aforementioned encodings and systems. Hence, for the curious, the reader can lookup the files, modify and compile them to bootstrap their writing project. Whatever you see on this site is made available for you to read, modify, etc.
|
||||||
|
|
||||||
# References
|
# References
|
||||||
|
|
||||||
|
|||||||
476
style/style.css
Normal file
476
style/style.css
Normal file
@ -0,0 +1,476 @@
|
|||||||
|
/*
|
||||||
|
Style.css
|
||||||
|
A revised Pandoc/Markdown/Multi-Markdown CSS stylesheet tailored for html5
|
||||||
|
output for the wwwriting site hosted on ....
|
||||||
|
Author: gauthiier
|
||||||
|
Revised: 10 Feb 2015
|
||||||
|
|
||||||
|
This file is based on:
|
||||||
|
|
||||||
|
Buttondown
|
||||||
|
A Markdown/MultiMarkdown/Pandoc HTML output CSS stylesheet
|
||||||
|
Author: Ryan Gray
|
||||||
|
Date: 15 Feb 2011
|
||||||
|
Revised: 21 Feb 2012
|
||||||
|
|
||||||
|
General style is clean, with minimal re-definition of the defaults or
|
||||||
|
overrides of user font settings. The body text and header styles are
|
||||||
|
left alone except title, author and date classes are centered. A Pandoc TOC
|
||||||
|
is not printed, URLs are printed after hyperlinks in parentheses.
|
||||||
|
Block quotes are italicized. Tables are lightly styled with lines above
|
||||||
|
and below the table and below the header with a boldface header. Code
|
||||||
|
blocks are line wrapped.
|
||||||
|
|
||||||
|
All elements that Pandoc and MultiMarkdown use should be listed here, even
|
||||||
|
if the style is empty so you can easily add styling to anything.
|
||||||
|
|
||||||
|
There are some elements in here for HTML5 output of Pandoc, but I have not
|
||||||
|
gotten around to testing that yet.
|
||||||
|
*/
|
||||||
|
|
||||||
|
/* NOTES:
|
||||||
|
|
||||||
|
Stuff tried and failed:
|
||||||
|
|
||||||
|
It seems that specifying font-family:serif in Safari will always use
|
||||||
|
Times New Roman rather than the user's preferences setting.
|
||||||
|
|
||||||
|
Making the font size different or a fixed value for print in case the screen
|
||||||
|
font size is making the print font too big: Making font-size different for
|
||||||
|
print than for screen causes horizontal lines to disappear in math when using
|
||||||
|
MathJax under Safari.
|
||||||
|
*/
|
||||||
|
|
||||||
|
/* ---- Front Matter ---- */
|
||||||
|
|
||||||
|
/* Pandoc header DIV. Contains .title, .author and .date. Comes before div#TOC.
|
||||||
|
Only appears if one of those three are in the document.
|
||||||
|
*/
|
||||||
|
|
||||||
|
div#header, header
|
||||||
|
{
|
||||||
|
/* Put border on bottom. Separates it from TOC or body that comes after it. */
|
||||||
|
border-bottom: 1px solid #aaa;
|
||||||
|
margin-bottom: 0.5em;
|
||||||
|
}
|
||||||
|
|
||||||
|
.title /* Pandoc title header (h1.title) */
|
||||||
|
{
|
||||||
|
text-align: center;
|
||||||
|
}
|
||||||
|
|
||||||
|
.author, .date /* Pandoc author(s) and date headers (h2.author and h3.date) */
|
||||||
|
{
|
||||||
|
text-align: center;
|
||||||
|
}
|
||||||
|
|
||||||
|
/* Pandoc table of contents DIV when using the --toc option.
|
||||||
|
NOTE: this doesn't support Pandoc's --id-prefix option for #TOC and #header.
|
||||||
|
Probably would need to use div[id$='TOC'] and div[id$='header'] as selectors.
|
||||||
|
*/
|
||||||
|
|
||||||
|
div#TOC, nav#TOC
|
||||||
|
{
|
||||||
|
/* Put border on bottom to separate it from body. */
|
||||||
|
border-bottom: 1px solid #aaa;
|
||||||
|
margin-bottom: 0.5em;
|
||||||
|
}
|
||||||
|
|
||||||
|
@media print
|
||||||
|
{
|
||||||
|
div#TOC, nav#TOC
|
||||||
|
{
|
||||||
|
/* Don't display TOC in print */
|
||||||
|
display: none;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
/* ---- Headers and sections ---- */
|
||||||
|
|
||||||
|
h1, h2, h3, h4, h5, h6
|
||||||
|
{
|
||||||
|
/* font-family: "Helvetica Neue", Helvetica, "Liberation Sans", Calibri, Arial, sans-serif; /* Sans-serif headers */
|
||||||
|
|
||||||
|
font-family: "Liberation Serif", "Georgia", "Times New Roman", serif; /* Serif headers */
|
||||||
|
|
||||||
|
page-break-after: avoid; /* Firefox, Chrome, and Safari do not support the property value "avoid" */
|
||||||
|
}
|
||||||
|
|
||||||
|
/* Pandoc with --section-divs option */
|
||||||
|
|
||||||
|
div div, section section /* Nested sections */
|
||||||
|
{
|
||||||
|
margin-left: 2em; /* This will increasingly indent nested header sections */
|
||||||
|
}
|
||||||
|
|
||||||
|
p {}
|
||||||
|
|
||||||
|
/* Main container for the whole content / body section -- html5 */
|
||||||
|
content {
|
||||||
|
width: 70%;
|
||||||
|
display: inline-block;
|
||||||
|
margin: auto;
|
||||||
|
}
|
||||||
|
|
||||||
|
blockquote
|
||||||
|
{
|
||||||
|
font-style: italic;
|
||||||
|
}
|
||||||
|
|
||||||
|
li /* All list items */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
li > p /* Loosely spaced list item */
|
||||||
|
{
|
||||||
|
margin-top: 1em; /* IE: lack of space above a <li> when the item is inside a <p> */
|
||||||
|
}
|
||||||
|
|
||||||
|
ul /* Whole unordered list */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
ul li /* Unordered list item */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
ol /* Whole ordered list */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
ol li /* Ordered list item */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
hr {}
|
||||||
|
|
||||||
|
/* ---- Some span elements --- */
|
||||||
|
|
||||||
|
sub /* Subscripts. Pandoc: H~2~O */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
sup /* Superscripts. Pandoc: The 2^nd^ try. */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
em /* Emphasis. Markdown: *emphasis* or _emphasis_ */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
em > em /* Emphasis within emphasis: *This is all *emphasized* except that* */
|
||||||
|
{
|
||||||
|
font-style: normal;
|
||||||
|
}
|
||||||
|
|
||||||
|
strong /* Markdown **strong** or __strong__ */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
/* ---- Links (anchors) ---- */
|
||||||
|
|
||||||
|
a /* All links */
|
||||||
|
{
|
||||||
|
/* Keep links clean. On screen, they are colored; in print, they do nothing anyway. */
|
||||||
|
text-decoration: none;
|
||||||
|
}
|
||||||
|
|
||||||
|
@media screen
|
||||||
|
{
|
||||||
|
a:hover
|
||||||
|
{
|
||||||
|
/* On hover, we indicate a bit more that it is a link. */
|
||||||
|
text-decoration: underline;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
@media print
|
||||||
|
{
|
||||||
|
a {
|
||||||
|
/* In print, a colored link is useless, so un-style it. */
|
||||||
|
color: black;
|
||||||
|
background: transparent;
|
||||||
|
}
|
||||||
|
|
||||||
|
a[href^="http://"]:after, a[href^="https://"]:after
|
||||||
|
{
|
||||||
|
/* However, links that go somewhere else, might be useful to the reader,
|
||||||
|
so for http and https links, print the URL after what was the link
|
||||||
|
text in parens
|
||||||
|
*/
|
||||||
|
content: " (" attr(href) ") ";
|
||||||
|
font-size: 90%;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
/* ---- Images ---- */
|
||||||
|
|
||||||
|
img
|
||||||
|
{
|
||||||
|
/* Let it be inline left/right where it wants to be, but verticality make
|
||||||
|
it in the middle to look nicer, but opinions differ, and if in a multi-line
|
||||||
|
paragraph, it might not be so great.
|
||||||
|
*/
|
||||||
|
vertical-align: middle;
|
||||||
|
max-width: 100%;
|
||||||
|
}
|
||||||
|
|
||||||
|
div.figure /* Pandoc figure-style image */
|
||||||
|
{
|
||||||
|
/* Center the image and caption */
|
||||||
|
margin-left: auto;
|
||||||
|
margin-right: auto;
|
||||||
|
text-align: center;
|
||||||
|
font-style: italic;
|
||||||
|
}
|
||||||
|
|
||||||
|
/** EXXXTRA **/
|
||||||
|
figure /* Pandoc figure-style image */
|
||||||
|
{
|
||||||
|
/* Center the image and caption */
|
||||||
|
margin-left: auto;
|
||||||
|
margin-right: auto;
|
||||||
|
text-align: center;
|
||||||
|
font-style: italic;
|
||||||
|
}
|
||||||
|
|
||||||
|
p.caption /* Pandoc figure-style caption within div.figure */
|
||||||
|
{
|
||||||
|
/* Inherits div.figure props by default */
|
||||||
|
}
|
||||||
|
|
||||||
|
/* ---- Code blocks and spans ---- */
|
||||||
|
|
||||||
|
pre, code
|
||||||
|
{
|
||||||
|
background-color: #fdf7ee;
|
||||||
|
/* BEGIN word wrap */
|
||||||
|
/* Need all the following to word wrap instead of scroll box */
|
||||||
|
/* This will override the overflow:auto if present */
|
||||||
|
white-space: pre-wrap; /* css-3 */
|
||||||
|
white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
|
||||||
|
white-space: -pre-wrap; /* Opera 4-6 */
|
||||||
|
white-space: -o-pre-wrap; /* Opera 7 */
|
||||||
|
word-wrap: break-word; /* Internet Explorer 5.5+ */
|
||||||
|
/* END word wrap */
|
||||||
|
}
|
||||||
|
|
||||||
|
pre /* Code blocks */
|
||||||
|
{
|
||||||
|
/* Distinguish pre blocks from other text by more than the font with a background tint. */
|
||||||
|
padding: 0.5em; /* Since we have a background color */
|
||||||
|
border-radius: 5px; /* Softens it */
|
||||||
|
/* Give it a some definition */
|
||||||
|
border: 1px solid #aaa;
|
||||||
|
/* Set it off left and right, seems to look a bit nicer when we have a background */
|
||||||
|
margin-left: 0.5em;
|
||||||
|
margin-right: 0.5em;
|
||||||
|
}
|
||||||
|
|
||||||
|
@media screen
|
||||||
|
{
|
||||||
|
pre
|
||||||
|
{
|
||||||
|
/* On screen, use an auto scroll box for long lines, unless word-wrap is enabled */
|
||||||
|
white-space: pre;
|
||||||
|
overflow: auto;
|
||||||
|
/* Dotted looks better on screen and solid seems to print better. */
|
||||||
|
border: 1px dotted #777;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
code /* All inline code spans */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
p > code, li > code /* Code spans in paragraphs and tight lists */
|
||||||
|
{
|
||||||
|
/* Pad a little from adjacent text */
|
||||||
|
padding-left: 2px;
|
||||||
|
padding-right: 2px;
|
||||||
|
}
|
||||||
|
|
||||||
|
li > p code /* Code span in a loose list */
|
||||||
|
{
|
||||||
|
/* We have room for some more background color above and below */
|
||||||
|
padding: 2px;
|
||||||
|
}
|
||||||
|
|
||||||
|
/* ---- Math ---- */
|
||||||
|
|
||||||
|
span.math /* Pandoc inline math default and --jsmath inline math */
|
||||||
|
{
|
||||||
|
/* Tried font-style:italic here, and it messed up MathJax rendering in some browsers. Maybe don't mess with at all. */
|
||||||
|
}
|
||||||
|
|
||||||
|
div.math /* Pandoc --jsmath display math */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
span.LaTeX /* Pandoc --latexmathml math */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
eq /* Pandoc --gladtex math */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
/* ---- Tables ---- */
|
||||||
|
|
||||||
|
/* A clean textbook-like style with horizontal lines above and below and under
|
||||||
|
the header. Rows highlight on hover to help scanning the table on screen.
|
||||||
|
*/
|
||||||
|
|
||||||
|
table
|
||||||
|
{
|
||||||
|
border-collapse: collapse;
|
||||||
|
border-spacing: 0; /* IE 6 */
|
||||||
|
|
||||||
|
border-bottom: 2pt solid #000;
|
||||||
|
border-top: 2pt solid #000; /* The caption on top will not have a bottom-border */
|
||||||
|
|
||||||
|
/* Center */
|
||||||
|
margin-left: auto;
|
||||||
|
margin-right: auto;
|
||||||
|
}
|
||||||
|
|
||||||
|
thead /* Entire table header */
|
||||||
|
{
|
||||||
|
border-bottom: 1pt solid #000;
|
||||||
|
background-color: #eee; /* Does this BG print well? */
|
||||||
|
}
|
||||||
|
|
||||||
|
tr.header /* Each header row */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
tbody /* Entire table body */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
/* Table body rows */
|
||||||
|
|
||||||
|
tr {
|
||||||
|
}
|
||||||
|
tr.odd:hover, tr.even:hover /* Use .odd and .even classes to avoid styling rows in other tables */
|
||||||
|
{
|
||||||
|
background-color: #eee;
|
||||||
|
}
|
||||||
|
|
||||||
|
/* Odd and even rows */
|
||||||
|
tr.odd {}
|
||||||
|
tr.even {}
|
||||||
|
|
||||||
|
td, th /* Table cells and table header cells */
|
||||||
|
{
|
||||||
|
vertical-align: top; /* Word */
|
||||||
|
vertical-align: baseline; /* Others */
|
||||||
|
padding-left: 0.5em;
|
||||||
|
padding-right: 0.5em;
|
||||||
|
padding-top: 0.2em;
|
||||||
|
padding-bottom: 0.2em;
|
||||||
|
}
|
||||||
|
|
||||||
|
/* Removes padding on left and right of table for a tight look. Good if thead has no background color*/
|
||||||
|
/*
|
||||||
|
tr td:last-child, tr th:last-child
|
||||||
|
{
|
||||||
|
padding-right: 0;
|
||||||
|
}
|
||||||
|
tr td:first-child, tr th:first-child
|
||||||
|
{
|
||||||
|
padding-left: 0;
|
||||||
|
}
|
||||||
|
*/
|
||||||
|
|
||||||
|
th /* Table header cells */
|
||||||
|
{
|
||||||
|
font-weight: bold;
|
||||||
|
}
|
||||||
|
|
||||||
|
tfoot /* Table footer (what appears here if caption is on top?) */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
caption /* This is for a table caption tag, not the p.caption Pandoc uses in a div.figure */
|
||||||
|
{
|
||||||
|
caption-side: top;
|
||||||
|
border: none;
|
||||||
|
font-size: 0.9em;
|
||||||
|
font-style: italic;
|
||||||
|
text-align: center;
|
||||||
|
margin-bottom: 0.3em; /* Good for when on top */
|
||||||
|
padding-bottom: 0.2em;
|
||||||
|
}
|
||||||
|
|
||||||
|
/* ---- Definition lists ---- */
|
||||||
|
|
||||||
|
dl /* The whole list */
|
||||||
|
{
|
||||||
|
border-top: 2pt solid black;
|
||||||
|
padding-top: 0.5em;
|
||||||
|
border-bottom: 2pt solid black;
|
||||||
|
}
|
||||||
|
|
||||||
|
dt /* Definition term */
|
||||||
|
{
|
||||||
|
font-weight: bold;
|
||||||
|
}
|
||||||
|
|
||||||
|
dd+dt /* 2nd or greater term in the list */
|
||||||
|
{
|
||||||
|
border-top: 1pt solid black;
|
||||||
|
padding-top: 0.5em;
|
||||||
|
}
|
||||||
|
|
||||||
|
dd /* A definition */
|
||||||
|
{
|
||||||
|
margin-bottom: 0.5em;
|
||||||
|
}
|
||||||
|
|
||||||
|
dd+dd /* 2nd or greater definition of a term */
|
||||||
|
{
|
||||||
|
border-top: 1px solid black; /* To separate multiple definitions */
|
||||||
|
}
|
||||||
|
|
||||||
|
/* ---- Footnotes ---- */
|
||||||
|
|
||||||
|
a.footnote, a.footnoteRef { /* Pandoc, MultiMarkdown footnote links */
|
||||||
|
font-size: small;
|
||||||
|
vertical-align: text-top;
|
||||||
|
}
|
||||||
|
|
||||||
|
a[href^="#fnref"], a.reversefootnote /* Pandoc, MultiMarkdown, ?? footnote back links */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
@media print
|
||||||
|
{
|
||||||
|
a[href^="#fnref"], a.reversefootnote /* Pandoc, MultiMarkdown */
|
||||||
|
{
|
||||||
|
/* Don't display these at all in print since the arrow is only something to click on */
|
||||||
|
display: none;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
div.footnotes /* Pandoc footnotes div at end of the document */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
div.footnotes li[id^="fn"] /* A footnote item within that div */
|
||||||
|
{
|
||||||
|
}
|
||||||
|
|
||||||
|
/* You can class stuff as "noprint" to not print.
|
||||||
|
Useful since you can't set this media conditional inside an HTML element's
|
||||||
|
style attribute (I think), and you don't want to make another stylesheet that
|
||||||
|
imports this one and adds a class just to do this.
|
||||||
|
*/
|
||||||
|
|
||||||
|
@media print
|
||||||
|
{
|
||||||
|
.noprint
|
||||||
|
{
|
||||||
|
display:none;
|
||||||
|
}
|
||||||
|
}
|
||||||
71
style/template.html5
Normal file
71
style/template.html5
Normal file
@ -0,0 +1,71 @@
|
|||||||
|
<!DOCTYPE html>
|
||||||
|
<html$if(lang)$ lang="$lang$"$endif$>
|
||||||
|
<head>
|
||||||
|
<meta charset="utf-8">
|
||||||
|
<meta name="generator" content="pandoc">
|
||||||
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
|
||||||
|
$for(author-meta)$
|
||||||
|
<meta name="author" content="$author-meta$">
|
||||||
|
$endfor$
|
||||||
|
$if(date-meta)$
|
||||||
|
<meta name="dcterms.date" content="$date-meta$">
|
||||||
|
$endif$
|
||||||
|
<title>$if(title-prefix)$$title-prefix$ - $endif$$pagetitle$</title>
|
||||||
|
<style type="text/css">code{white-space: pre;}</style>
|
||||||
|
<!--[if lt IE 9]>
|
||||||
|
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
|
||||||
|
<![endif]-->
|
||||||
|
$if(quotes)$
|
||||||
|
<style type="text/css">q { quotes: "“" "”" "‘" "’"; }</style>
|
||||||
|
$endif$
|
||||||
|
$if(highlighting-css)$
|
||||||
|
<style type="text/css">
|
||||||
|
$highlighting-css$
|
||||||
|
</style>
|
||||||
|
$endif$
|
||||||
|
$for(css)$
|
||||||
|
<link rel="stylesheet" href="$css$">
|
||||||
|
$endfor$
|
||||||
|
$if(math)$
|
||||||
|
$math$
|
||||||
|
$endif$
|
||||||
|
$for(header-includes)$
|
||||||
|
$header-includes$
|
||||||
|
$endfor$
|
||||||
|
</head>
|
||||||
|
<body>
|
||||||
|
$for(include-before)$
|
||||||
|
$include-before$
|
||||||
|
$endfor$
|
||||||
|
<content>
|
||||||
|
$if(title)$
|
||||||
|
$if(cover)$
|
||||||
|
<figure>
|
||||||
|
<img src="$cover$"/>
|
||||||
|
</figure>
|
||||||
|
$endif$
|
||||||
|
<header>
|
||||||
|
<h1 class="title">$title$</h1>
|
||||||
|
$if(subtitle)$
|
||||||
|
<h1 class="subtitle">$subtitle$</h1>
|
||||||
|
$endif$
|
||||||
|
$for(author)$
|
||||||
|
<h2 class="author">$author$</h2>
|
||||||
|
$endfor$
|
||||||
|
$if(date)$
|
||||||
|
<h3 class="date">$date$</h3>
|
||||||
|
$endif$
|
||||||
|
</header>
|
||||||
|
$endif$
|
||||||
|
$if(toc)$
|
||||||
|
<nav id="$idprefix$TOC">
|
||||||
|
$toc$
|
||||||
|
</nav>
|
||||||
|
$endif$
|
||||||
|
$body$
|
||||||
|
</content>
|
||||||
|
$for(include-after)$
|
||||||
|
$include-after$
|
||||||
|
$endfor$
|
||||||
|
</body>
|
||||||
|
</html>
|
||||||
Loading…
x
Reference in New Issue
Block a user