philschatz

// Take a look at the generated CSS (they are equivalent)
// Uncomment the .preface and .appendix lines to see why the @part is necessary.

#part {
  // The Part>content-counter prefixes any labels you want to number depending on
  // which part of the book they occur in.
  // For example: "Table 4.3" in a chapter and "Table A3" in an appendix
  .content-counter(preface;  @before; @after) { content: @before @after; }
  .content-counter(chapter;  @before; @after) { content: @before counter(chapter) '.' @after; }
  .content-counter(appendix; @before; @after) { content: @before counter(appendix, upper-alpha) @after; }

philschatz

Stylesheet Refactoring

Goals

The main goals of re-factoring the book stylesheets are as follows:

• Separate style rules from selectors. This will allow an easy transition to different DOM structures (Eg, Moving from Docbook to XHTML).
• To be able to style books by supplying alternate “slots” -- style rules for specific logical pieces of a book (An exercise, a section in a chapter, a solution in an exercise, a figure in a feature, etc.)

Design

philschatz

table[data-phil-1] {
  border: 1px solid !important; 
  border-collapse: collapse;
}

th[data-phil-2] {
  border: 1px solid !important;
}

td[data-phil-3] {

philschatz

Reasons for HTML & CSS+

Background

It would be easy if:

• a piece of content is in exactly 1 book (overriding titles, collection context matters)
• links would point to places within the current doc
• could layout each page individually (PDF page breaks)

philschatz

First, Links!

1. CSS Coverage of all CCAP books

• Once you have the HTML, each book takes 3-5min for coverage, 10-min for regression-prep, and 1min for diff/regression test

2. Diff of Precalculus PR
3. Polyfills vs Browser rendering

Use css-polyfills to do HTML+CSS diff

• Build a single file

philschatz

#!/bin/bash

# To run this file you will need:
#
# - python
# - phantomjs
# - xsltproc
# - genhtml (or `brew install lcov`): Optional

# Example books:

philschatz

Weekend Case Study: "Show PDF build logs in real time (like travis-ci) using web sockets"

Code: https://github.com/philschatz/pdf-ci Demo: http://pdf.oerpub.org

Motivation

1. PDf build log needs to be (eventually) persisted

philschatz

USER =
  email:
  firstname:
  fullname:
  id:
  othername:
  suffix:
  surname:
  title:
  website:

philschatz

Exploratory "bits" to test over the weekend

(in no particular order)

Module Page:

• Change hostname and reload the Backbone.Model
• Replace Metadata Language with dropdown
• Add "draft" color
• Fix editor toolbar

philschatz

<?xml version="1.0" ?>
<xsl:stylesheet
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  xmlns:c="http://cnx.rice.edu/cnxml"
  xmlns="http://cnx.rice.edu/cnxml"
  version="1.0">


<!-- Identity tranform -->
<xsl:template match="@*|node()">