Pages for wireframe
(Modeled after Steve's list)

I use the term "block" and "component" as described in the document
that gives the structure of Rob's book, available at
   http://aimath.org/~farmer/print/fcla_structure.pdf

The list below assumes that the document is a collection of
nested blocks. Each block contains "components" that are things
like text, images, and code, and a block can contain other blocks.
The components of a block have an interpretation which is built into
the specification of the block.  For example, a particular component
might be text, which is the caption of an image.

A list of example blocks is at the end of this file.

Start a new book
 -choose a structure for the book
  (eg, chapters with sections, no subsections, exercises at
       the end of each chapter, list of elements that can occur
       in each section.)
 -enter basic information: title, author(s), licensing

Author/privileged user add material to the book.
 -start a new chapter
 -rearrange the chapters and change chapter titles
 -add/modify the components of a chapter
 -start a new section in a chapter/rearrange sections/
  change the names of sections
 -add a new block to a section/rearrange the blocks
    in a section
    Special cases of this include: adding an exercise to
      the exercise section, adding an image and its caption,
      or adding a sidebar with the biography of a famous scientist.
 -add material to the components of a block
    It would be nice to see examples of everything in Rob's book,
    and also Guichard's calculus book, after I look at it more closely.

Non-privileged user submit a suggested exercise.  This involves
navigating to the particular exercise set, clicking "add exercise",
and entering the contents just like an author would.  But the
exercise is held in a queue until approved by the author.

Author views submitted exercise and decides to accept/reject/edit it.
This involves navigating to the particular exercise set, seeing
the pending exercise, and then performing the chosen action.

Author looks at the the table of contents of the book and sees
that there is a pending exercise in a particular section.  The author
clicks a link to go to that page to deal with the exercise.

User makes a marginal note, only visible to them.

User makes a marginal note and sends it to the author.

Non-privileged user suggests a different wording for a paragraph.
Author deals with the suggestion.

Author blocks input from a particular user

Author runs "check for print-on-demand," which produces a list of
items which need to be addressed before a proper print-on-demand
version can be created, and produces a PDF preview of the
print-on-demand version.



===========Example Blocks==========

There are about a dozen examples in the document that
describes the structure of Rob's book:

http://aimath.org/~farmer/print/fcla_structure.pdf

Note 1: most blocks should have a "descriptive title" field,
which is helpful for finding the material.  The descriptive title
would not actually appear in the public view of the document.

Note 2: we only describe the items in a block that an author would
enter.  The block also has other information, such as where it
appears among the list of sibling blocks in its parent block,
who last edited it, etc, but this is not routinely available
to the author.


Other examples:

Figure and caption.  The components are the source file for the
image, text for the captions, and possibly a label.

Sage interact.  This is like a figure and caption, except that
the "figure" is a sage cell.