1. Congrat to the idea…!
2. This is not realy true - there are a lot of printer drivers, which simulate a printer, but write to a "pdf" - file - with all options available you need.

I think, the print command/Link at the bottom is not so bad ! :)

What we need here in wikidot, is more the "print"-CSS dependent commands… like formfeed before or after a line.- I can remember. there was such a wish and I think Ed JOhnsin fiund a little solution.

Idea one: Why not use Google Docs API? It's easy to "upload" a html file (EDIT: actualy - upload from a printable version url) to anyone with a Google account. Then export to DOC, PDF, RTF and lots of others as well…… I found the ability to do this in PHP. http://code.google.com/apis/documents/docs/1.0/developers_guide_php.html

Just curious, but wouldn't this mean that you couldn't copyright your book.

And what 3 readers?

James Kanjo made this some time ago.

I imagine you could use feedbooks to get it into pdf, epub, or mobi if you format the book so your content is in the first wikidot division of the pages you draw it from, and appropriately organized.

I've been mulling starting a collection of my own serial shorts in a blog here. One thing standing in my way is a good bookish theme. There are a couple of paper/folder themes on the theme site but nothing has quite struck my fancy. And when I start to try to create my own, I just get a headache.

I picture a side bar theme where the sidebar is separated from the main content by a fold, like the middle of an open book. Main content has a full page-like interface with a little bulge on one side and pages leafing out on the other. Side content is just a partial page, the bulge and then it cuts off. Top nav is old style book binding. Someday I'm actually going to get around to that.

I am, admittedly, a writer not a programmer but I have a sufficiently developed left brain that I can muck about with Wiki Markup Language and get things done. Perhaps not elegantly so, but I'm learning as I go.

I was very excited when I ran across this post about a book template, as I've just started a collaborative blogging project with another writer. The automatic numbering feature and elegant little buttons that lead from one piece to the next are just stunning. It seemed to me that this template would work really well for our collaborative effort with just a bit of customization. And that naive assumption is where the trouble began…

So I cloned the template as a new site http://jtd.wikidot.com/ and set to work. The problem is that we're writing articles for a blog, not a book. So we need neither chapters nor appendicies. I thought it would be a snap to change the titles to something more appropriate, but have been unable to do so because I can't get into the module where those terms are set up (don't laugh, I already feel like an idiot). Ideally, I'd like to pop in and set up three levels for this: Project, Topic, and Article, then get on with the writing.

It strikes me that this bit of customization might make a nice variation on the book template, targeting journalists and bloggers who write serial pieces.

Any thoughts for a javascript-disabled wordsmith? I'm really new to Wikidot, so even some pointers to the appropriate pages in the documentation might help me. Many thanks in advance for sharing your wisdom.

Not to mock or anything, but I've experienced that wiikidot doesn't perform so well with large chunks of text. The cursor takes more than a split second to react when there is a substantial amount of text in the edit part. For me, Wikidot is just not the tool suitable for these kinds of tasks. At least, not with the hardware I am using.

The solution of typing the text offline and once in a while pasting it in the wikidot is not a solution.

If the book is a one-person project, then work offline in general. And if more than one person is involved, then this wonderful page-lock feature is missing. And, with using wikis in a collaborative way: The hard part is in general to get the people to do something different than what they are used to (eg type in their pre-installed word processor, and emailing the Most Recent Version around). Sloppyness in copy-pasting the material in the wiki also after just a bit of work is very likely to occur.

Sorry to say, but wikidot is not my preferred application to work on a book.