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 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 interace. The most famous wiki being “Wikipedia.” 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. #### 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: > 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:commitbefore=HEAD^,commitafter=HEAD,plain=yes|Changes caused by HEAD commit]] Would render to… > Changes caused by HEAD commit ### File Structures and naming TODO * This is a link to a test document (song lyrics). Note that it is cognizant of the “path” hierarchy, treating path elements as directories, both aesthetically but also stored as such on the backend (useful for organizing documents into sane directory structures). * The ability to move documents with relative ease. ### Searching TODO * Basic search capabilities. ## Dealing with Files in Giterary There are some things to know about dealing with files 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. 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. ### Markdown, and then some 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. ### Annotations * If a document is annotated, it can be read normally by keeping the mouse “out” of the document display area. However, when enabling decorations with the “Decorations” checkbox, the style will change to highlight annotations in yellow, and upon hovering over the annotations, show the annotated comments on the highlighted areas. This is to allow for external comments without necessarily disrupting readability. ### Decorations * Have the ability to render collections of documents, to help with the overall organization of a body of work, and to allow for easy re-ordering without changing the contents of the component documents. * Similar to annotation highlighting, documents can also detect dialog-looking text elements and highlight them. * Documents can be written and will be rendered by default in Markdown syntax, however nothing ties you to a specific format. Different syntax engines can be added, as well as default rendering can be overridden to display in alternate formats. See: Plain text, Hard-wrapped plain text ### Tables of Contents * Automatic table of contents generation ### CSVs ### Collections ### Drafts * A 10-second timer saves a temporary draft of your edit to the server in the event you lose connectivity. To recover the draft, either return to edit the page you were editing prior, or hit “Drafts” to see a list of unsaved drafts. ### Statistics * Document Statistics (also works on aggregated collection documents) ## The Wonder World of git * The ability to view global history, as well as history specific to one or more files. * See intuitive, helpful "diff” page, demonstrating the capabilities of the backend difference engine. * Building from the “diff,” you can also "cherrypick" changes (keeping some, discarding others), and use them to build a new version of your document. * 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.