* **I'm not technical enough to set up Giterary, but I like some of the features, and the price is right. What can I do?**

There's a lot going on, I know. TODO.

* **Markdown is *okay*, but I like X better. Do you support that?**

Probably? Is it text-based? Is it easy to edit from an HTML textarea tag? Well, there are certainly places to add such things, but there isn't anything particularly fancy. For the programmers out there, it's a PHP switch statement, that passes off handling to a function that is assumed to return valid HTML. However, a lot of work goes into making Markdown-specific editing possible (with the addition of annotations, the live Markdown preview, etc.)

* **I don't understand why I would ever use partitioning. Why would I ever want to split up my document?**

Valid question. It's more of a feature for people who, prior to writing in Giterary, or prior to sane document management practices, worked only in single, monolithic documents (see: one great big Word document, or something like that). A feature like that is useful because it lets you split up a larger work into smaller, more manageable chunks.

* **Something broke, and my repository is messed up. Giterary isn't helping at all. I don't want to start over. Please help.**

TODO: Solve using an external git client...

* **Is Giterary supported on X, X being my operating system?**

TODO: OS agnosticism. Anything that supports PHP, and git, and a web server.

* **I have a healthy degree of paranoia, does Giterary support file encryption?**

Not at the moment, but it's an interesting and precarious feature. For instance: you could implement it such that you would have to enter an extra password in order to "unlock" a file for editing. However, unless said paranoid individual isn't *also* paranoid about their network traffic, it's possible that the submission of that password could be intercepted.

So: it's possible. An extra extension handler, plus perhaps a modified form element, and you'd be in business. But it certainly wouldn't be perfect, and would play hell with Giterary's diff mechanisms.

* **What coding conventions were used in the application, if any, you talentless hack?**

You can read about some of the [[CONVENTIONS|programming conventions]], if you really want..

* **What license is Giterary released under?**

TODO: That's a... very good question.

* **There already exist industry standard word processing and novel writing tools, cheaply available, reliable, and better documented than this. Giterary is destined to fail.**

TODO: Wow. No punches pulled.

* **Does Giterary support X method of authentication? Y method of authorization? How can I allow thisgive person A permissions to do this, but not person B?**

TODO: There is only so much I can do to predict what people will use Giterary for, or who the will want to be able to use Giterary.