The following document is a set of usage examples for the features available in Giterary. They are provided as "suggestions" for how to manage and use the features, but by no means are the extent of how to use the features.

##The Structure of Giterary Components

The first thing you should know is that Giterary is a wiki, or rather, belongs to a family of computer software that calls themselves "wikis."

### What is a wiki?

A wiki is an application that lets you navigate and edit a web of documents and document references from a single interface. The most famous wiki being "[Wikipedia](http://wikipedia.org)." You may have heard of them.

Wikis are powerful tools because they allow you to efficiently organize and navigate your information while providing multiple users the ability to update and maintain the content. They vary in ubiquity and in features, given special use cases, extensibility, and popularity. Giterary's wiki features are inspired largely by [Mediawiki](http://www.mediawiki.org/wiki/MediaWiki) and [MoinMoin](http://moinmo.in/) (both excellent examples of full featured and extensible wiki software).

### File Structures and naming

#### Naming Files

#### Files, Directories, and "Dirification"

### Creating New Files and Directories

TODO

### Searching

TODO

## Objects and the Navigation Thereof

There are some things to know about dealing with files, directories, and navigating them within Giterary.

### File extensions

If a file has an extension (*MyFile.txt*, *MyTable.csv*, *MyNotes.md*, etc.) that extensions handling (as determined by Giterary) will be used by default when displaying the page (*txt* or *text* for purely textual documents, *md* or *markdown* for Markdown syntax documents, *csv* for Comma Separated Values formatted files, and so on).

For files with no extension (*Chapter1*, *01-Wednesday*, *HelpFile*) a default renderer is chosen, and that renderer is configured to be the Markdown renderer by default. See later in this document for explanations of Markdown.

You can also override the renderer by specifying different "as=someextensionname" on the URL of a document. This is useful for rendering something as its underlying source code (*as=text*), readable text (*as=wrap*). For instance, this document as:

* [[index:file=jrhoades/jot/2012/11/17-Sat,as=text|Plain text]]

* [[index:file=jrhoades/jot/2012/11/17-Sat&as=wrap|Hard-wrapped plain text]]

### Decorations

In addition to the formatting provided by Markdown syntax and other HTMl formatting tags, Giterary also provides additional "decorations" to a document. These decorations are "hidden" by default, but are present in the Giterary interface by selecting the "Decorations" checkbox at the top of a document display, or by hitting the letter "d."

The decorations currently available are:

* Annotations

* Dialog highlighting

* Invisible headings (these will be described in the Table of Contents section).

#### Annotations

Annotations in documents are ways to highlight and provide notes to a document without necessarily changing it. This is useful for editing and document feedback, providing additional information for other authors, or being able to refer to other portions of your Giterary repository without disrupting the document's readability.

**Note**: Annotations are "hidden" by default, and only appear when you enable decorations. If you are browsing from Giterary, hit the "Decorations" button at top, or hit "d" to enable the examples below.

<annotate>

This text is annotated.

<comment>This text is "annotating" the original text.</comment>

</annotate>

Renders to this:

> <annotate>This text is annotated.<comment>This text is "annotating" the original text.</comment></annotate>

Note that with the above syntax, you need not put the "comment" tags at the end of the "annotate" content, nor are you limited to one comment tag within the annotation.

There is also a simplified syntax for this that allows you to provide minimally disruptive annotation syntax in your content, and specify your annotation text either explicitly next to the annotate or later in the document (allowing for a "reference" section, similar to the Markdown feature of allowing the definition of a URL to be apart from its usage.

\{The quick brown fox jumped over the lazy dog.}(This is my note.)

...or...

\{The quick brown fox jumped over the lazy dog}[referencetag]

...and elsewhere in the document...

\{reference_tag}: This is my note.

Would generate the following:

> {This is some annotated text.}(This text is annotating)

> ...or...

> {This is some annotated text.}[referencetag]

{referencetag}: This text is annotating.

#### Dialog Highlighting

Dialog highlighting attempts to show a user the approximate balance between dialog content and non-dialog content in a document.

Dialog content generally follows the format of:

> "Something something," she said.

Which consists of:

* Content with double quotes, and...

* The quoted content ending with a punctuation mark (commas, periods, exclamation point, question mark, ellipsis,etc.), and...

* Not part of a "list" ("Item 1," "Item 2," and "Item 3").

Note that these are very generic and unsophisticated dialog detection mechanisms, meant to be useful only in common cases. Some consideration is taken for different quoting characters (UTF-8 left quotes and right quotes), but it can only guess as to the different ways you may write dialog.

### Tables of Contents

Giterary takes it upon itself to create a table of contents based on the elements within your documents. In Markdown, if you have a line that looks like this:

Header Title

------------

...or like this...

Header Title

============

...or like this...

## Header Title

...you have specified that there should be a "header" element with the text *Header Title*. This will generate the appropriate HTML element (the h1, h2, h3, h4, h5, or h6 tags) according to the "level" of header. Refer to the Markdown syntax documentation for more complex header generation.

Each of these header elements are then detected by Giterary upon rendering, and can be turned into "bookmarks" as part of an automatically generated table of contents. Depending on your screen geometry (window width of your browser), this table of contents will appear either at the top of your document, or to the right of your document.

Giterary makes one departure from Markdown's normal "header" output, in that it treats the h6 (header level 6) elements differently. Rather than displaying h6 elements like the rest of the headers, they will be invisible, but still be treated as "bookmarking" elements. With this, you can treat h6 headings as invisible placemarkers within larger documents. This is useful if you want to maintain bookmarks within a document, but not disrupt the formatting of the document with headings.

For example:

###### This is a hidden heading

Will generate a *This is a hidden heading* table of contents item, but not render within the document (as you should not see below)

###### This is a hidden heading

As part of the decorations functionality, enabling decorations on a document with invisible headings will display the headings at their position within the document.

### Comma Separated Values Files (CSV files)

A CSV file (Comma Separated Value) file is a file whose content consists of tabular data stored in a text document, with line of text representing a "row" of data, and different columns specified by a list of fields, separated by commas.

For example:

Year,Month,'Day of Month',Note

2013,01,18,'Today I drank beer. Perhaps I drank too much.'

2013,01,19,'Today I drank tea. It's not the same as coffee.'

These files will be rendered as dynamic tables within your document, like so:

<table class="tabulizer">

<thead><tr class="header"><th class="header headerSortDown"><span>Year</span></th><th class="header"><span>Month</span></th><th class="header"><span>Day of Month</span></th><th class="header"><span>Note</span></th></tr></thead> <tbody><tr class="odd"><td>2013</td><td>01</td><td>18</td><td>Today I drank beer. Perhaps I drank too much.</td></tr><tr class="even"><td>2013</td><td>01</td><td>19</td><td>Today I drank tea. It's not the same as coffee.</td></tr></tbody> </table>

These CSVs will assume the first row of data is "header" data. It will then put it in an HTML table that can be sorted by the user.

One can also specify default sorting methods with the following syntax:

* !Year sorts the column "Year" in least-to-greatest order.

* ^Year sorts the column "Year" in greatest-to-least order.

* !#Year sorts the column "Year" in least-to-greatest order, treating all elements as numbers.

* !@Year sorts the column "Year" in least-to-greatest order, treating all elements as strings.

You can mix and match the sorting "hints" as you wish.

### Collections

Collections have the purpose of rendering multiple documents within your Giterary repository at once. This is done as a special rendering of the *collection* or *collect* file extensions. Contents of these files are simply lists of other file paths (*MyFile*, *Wherever/I/Put/My/File.txt*).

For example:

/DarkAndStormyNight/Chapters/Chapter1

/DarkAndStormyNight/Chapters/Chapter2

/DarkAndStormyNight/Chapters/Chapter3

Will render the files *Chapter1*, *Chapter2*, and *Chapter3* in succession on a single page. This is useful for stitching together a larger document (the entirety of a book, for instance), of which you have broken into smaller, more manageable pieces (chapters, in this case).

By editing the collection, you can re-order its component parts by changing the order of the paths referenced in the collection document. For instance, if you decided to put Chapter3 before Chapter 2:

/DarkAndStormyNight/Chapters/Chapter1

/DarkAndStormyNight/Chapters/Chapter3

/DarkAndStormyNight/Chapters/Chapter2

Time travel novels are notoriously difficult to write, but this should help to order your components without having to change the underlying contents.

You can also use the collection documents to include an entire subtree of your Giterary repository. For instance, for the user "jrhoades," they may have a collection that contains the following:

jrhoades/jot/201*/*

Use of the asterisk wildcard lets you match all documents matching the collection query. Documents will be rendered in order of directory traversal, and in alphanumeric order. The above example will render all "jot" files for the user "jrhoades" for the years 2010-2019.

### Statistics

TODO

* [[stats:file=jrhoades/jot/2012/11/17-Sat|Document Statistics]] (also works on aggregated [[stats:file=Coulton/Jonathan/Artificial_Heart/All_Songs.collection|collection documents]])

### Partitioning

TODO

## Document Editing

### The editor

### Giterary-specific Syntax

#### Wikilinks

Wikilinks are a special syntax that you include in the text of your document that allow you to generate a hyperlink to a different document when your original document is rendered.

For example:

\[[ANameOfYourDocument]]

Turns into something like this:

> [[ANameOfYourDocument]]

You can also specify "display" text along with your link, like so:

\[[ANameOfYourDocument|Click here to view my document]]

Which turns into something like this:

> [[ANameOfYourDocument|Click here to view my document]]

Depending on whether that document *exists* (that is, is present in the latest and greatest version of your wiki content), the link may be colored differently. This is to show which pages you can expect to see content from when clicking on them, and if you would expect to create new content when clicking on them.

#### Functional Links

In addition to "wiki"-style links, you can use "functional" linking syntax to generate links that perform functions around Giterary. These involve using a known "prefix" based on Giterary functions, and specifying the parameters that would be used within that link. For instance, determining the "diff" between two commits within Giterary might look like this.

\[[diff:commit_before=HEAD^,commit_after=HEAD,plain=yes|Changes caused by HEAD commit]]

Would render to...

> [[diff:commit_before=HEAD^,commit_after=HEAD,plain=yes|Changes caused by HEAD commit]]

### Markdown, and then some

[Markdown syntax](http://daringfireball.net/projects/markdown/syntax) is a useful way to write without having to worry about syntax.

To quote the author:

> *Markdown is intended to be as easy-to-read and easy-to-write as is feasible.*

> *Readability, however, is emphasized above all else. A Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions.*

This usage document is written in Markdown format. You can view its contents by selecting **Other Options > ...Readable Text** when displayed in Giterary.

There are many great features to Markdown for document formatting. It is highly recommended you familiarize yourself with its function.

**Additional Note**: One of Markdown's features is that it will allow HTML tags to be embedded within it (to provide features that Markdown can't provide). Giterary supports this "HTML pass-through," however, only for a limited subset of HTML (for security reasons).

### Live Preview

### Commit Notes

### Preview vs. Submit

### Drafts

When editing a document, a timer will periodically trigger to determine if you have made significant changes in the editor. If so, it will send a "draft" portion back to the Giterary server, containing the contents and the commit against which the draft was being written.

These drafts can be used to recover writing lost after the disruption of an Internet connection, power failure, or a failure to distinguish "Control-W" from "Control-Q" as a keyboard command.

These commits can be recovered by logging in and visiting the "My Drafts" page, which will list all recent unsaved drafts. Clicking on "edit" for a draft from here will load the editor page with the last known draft contents against the document you were editing.

## The Wonderful World of Version Control

TODO

### Terms from git

* repository

* commit

* clone

* push

* pull

### History

TODO

### Comparing Different Versions, or "Diffs"

TODO

### Blame

TODO

### Cherrypicking

TODO

### Reversion

----

* The ability to view [[history:|global history]], as well as history [[history:file=Home|specific to one or more files]].

* See intuitive, helpful [[diff:commit_before=9b587a7e9accf5adf697903cf740acaf53cbce9b,commit_after=2cbf089170ce780bb6406f226727f05b495192ee|"diff" page]], demonstrating the capabilities of the backend difference engine.

* Building from the "diff," you can also [[cherrypick:commit_before=9b587a7e9accf5adf697903cf740acaf53cbce9b,commit_after=2cbf089170ce780bb6406f226727f05b495192ee|"cherrypick"]] changes (keeping some, discarding others), and use them to build a new version of your document.

* [[Coulton.dir/Jonathan.dir/Artificial_Heart.dir|Directory listings]] to help with navigating document organizational trees.

* A nice feature, though hard to demonstrate here, is that the system supports a very powerful "offline" mode, using the ability of the backend versioning system (Git) to act as a distributed file database. A computer, external to the system and with no local installation of the Giterary tool, can clone the Giterary repository to its filesystem, make edits with a user's favorite text editor, and push them back to the server without a) fear of losing work due to Internet connectivity, or b) having to be concerned with making edits that have to be "shoehorned" back into the main editing system.