I was planning on doing what I did for articles, until it occurred to me that an article is not a book!
Currently, for articles, I have have a PHP page which is a a template for the page and then I have a variable that grabs the article from MySQL and dump it into the body of the page template. The article has already been marked up as HTML.
That works okay for a 1-5 page article, but what would I do with even a 200 page guide? I guess I could break it up into 20-30 page chapters, but I'm not even sure if there is a datatype that would take that much data, plus maybe I would make the database choke?!
No, they are buying access to an online book which some people have accused me of selling a big web page?!
Later on I hope to sell PDFs and eBooks, but for no - to lessen piracy concerns - I am just selling access to online books.
To be clear, whether I did this as static web pages or use the database to populate things, it is still driven on a member having the correct access to the book/guide/whatever.
I would love to sell printed books, but it isn't cost effective.
For a small company like mine, a 500 page printed book might cost me $50-$60 when I can only sell the book for $40.
By contrast, if I sell an online book, I have 100% profit.
If my business takes off, it would be great to offer all formats.