Instructions for this SF demo

1. Fork this book (make a copy) so that you can save your changes. You should see a blue button above that says "Fork this book". Click that!
2. Make a couple minutes worth of edits. Some suggestions:
   • In this page of the book
     • Add some math (There is a button in the toolbar, you can add x^2 if you want).
       
     • Add a "Note to reader", or a "Definition"
       
   • In the Table of Contents Pane (the column to the left)
     • Add a new page or chapter to the book
     • Move things around in the TOC. This will be autosaved. 
   • Copy a section, math, or a block (quote, image, etc.) from another part of this book.
     • Open the Legal Guide Introduction
     • Copy Philip's quote (use the "copy quotation" link)
     • Open "Instructions" or your new page, click inside it, and use the paste button to paste it. (The need to click is a bug, but ...)
3. Save your changes. Click "Save All" which should be blue. It will turn gray when the changes have been saved.
4. See your book in different formats. Note that these are very alpha versions and the formatting isn't beautiful yet. 
   • Web views: 
     • Go to http://oerpub.github.io/sf-demo-book to see two different web views of the original book. Click on the first one, because this one has annotation.
     • Add an annotation with your Hypothes.is account from yesterday.
     • See the Stuff for later, to see your own edits online.
       
       
   • PDF: Check out  prototype PDF generation system for this book at pdf.oerpub.org/oerpub/sf-demo-book/. It automatically updates the PDF when any of the content of the book changes.
   • EPUB: If you technically-inclined, see below how to view the EPUB of the book using Readium. 

Stuff for later if you want to see more

1. More edits. Some suggestions:
   • In this page of the book
     • Add an image (to see the license and attribution stuff)
     • Add a table. and then add some rows and columns and see the preview in action.
   • Copy a page from another book into this one.
     • Open the Siyavula book using the Book Picker
     • Open "Momentum and Impulse" and then drag "Momentum" into this book. This will goof up the reader that is based on EPUBjs though because it isn't yet handling math
2. See your book in different formats.
   1. WEB:
      • Go to http://<your-github-id>.github.io/sf-demo-book to see the edits that you made. For example, if you are oerpub21, you would go to http://oerpub21.github.io/sf-demo-book. This sometimes takes 10 to 15 minutes to show up. 
        
   2. PDF: Setting up your own book to autogenerate a PDF (do this later if you are interested).
      
      • Go to your repository on github. http://github.com/<your-github-login>/sf-demo-book/settings/hooks.
      • Select "WebHool URLs"
      • Enter http://pdf.oerpub.org
      • Click Test Hook
      • Open http://pdf.oerpub.org to download your book

   3. EPUBs: The books are stored in EPUB format on github and you can almost just download the zip and view it with Readium (an in-browser EPUB reference implementation reader done by IDPF). If you want to give it a try, download the zip of the sf demo repo. You have to do two things to make it work with Readium.

      1. Unpack the book and remove the second book from container.xml
      2. Rezip just the contents of the folder demo-book-master, rather than zipping the folder itself.
      3. You should now be able to view the book using the Readium Chrome extension.
3. Collaboration
   • If you are comfortable with Github, you can add collaborators onto your copy of the book and experiment with the primitive collaboration features.
   • What works
     • You can add things to the TOC and everyone will see the new content.
     • You can retitle things and move things around and everyone will see it. If you do these things at the same time, you may lose some of the moves.
     • You can each change a separate piece of content/module in the book. You will be able to see each other's changes update in the editor.
     • You cannot edit in the same content/module and have something reasonable happen. You will lose edits.