Tribal SQL Template

Here….


…is the Tribal SQL template for chapters (docx version; lemme know if you need a different format).

We’re going with the ePub route for starters, so we’ll have a set of minimalist guidelines. We’ll use the attached template.

In short:  

  • Keep formatting simple. Use Header2 style for the chapter heading, Header3 for section headings.
  • Don’t change the font from the Normal style. You may use bold, italic, underline.
  • Complex content doesn’t display right on ereaders: charts, tables, text boxes, embedded objects.  Instead, use high quality JPG images. (You can just screenshot an existing table and save it in MSPaint as a JPG).
  • No page numbers, breaks, headers, or footers. 
  • Hyperlinks are okay. If we release this in a print version too, we’ll have to convert hyperlinks to a list of links at the end of each chapter.

Enjoy!

4 thoughts on “Tribal SQL Template

  • Why JPEGs and not PNG? JPEG is lossy and designed for photographs. PNG would be better suited for something like a table.

    Also, my chapter has code samples? Can we have a style for code samples with a monospaced font?

    • If I remember correctly, the Lulu guidelines say jpg. one of us should look that up.

      And yeah, use the CODE style in Word. I’ll standardize it when everything gets compiled.

  • One question with the links. I was thinking of having two categories of links. The first would be links I want in the printed form (as in the the urls printed out), and the second is me linking the shit out of things as I would for something in electronic formation.

    Basically, I’m going to provide urls for things you need to download like PHP and the PHP SQL driver in the book. In the ebook version I want it to look like a wikipedia article. The first time I make an API call or use any other word that has an entire page dedicated to it on php.net or msdn, I will link to it.

Leave a Reply

Your email address will not be published. Required fields are marked *