Welcome to Project Trident!
This document is designed to unify the style of documentation contributions to Project Trident. It outlines the tools needed for documentation and elements of style for the project. The goal is to encourage contribution to the project by providing reference materials and guidelines, lowering the barriers to entry for new contributors.
Contributors are encouraged to reference this style guide when writing Trident documentation. Documentation Pull Requests are quickly reviewed for relevancy to the project, then merged. Trident documentation will be periodically reviewed and edited to conform to this style guide.
All documentation is stored as Markdown files in the trident-website repository on GitHub. These files are published to http://www.project-trident.org as articles.
All articles must begin with a header block with a few specific elements:
+++
title = "Article Title"
menutitle = "Article title in website sidebar"
description = "Brief description of article. Appears on the website."
pre = "<i class='fa fa-font'></i> "
+++
Every documentation file needs an introduction section explaining the goal of the document and a summary of the most useful procedure.
Trident Basic Style Elements:
Element | Markup | Example |
---|---|---|
Headings | #, ##, ###, ####, ##### |
# Title of Document ## Main Section of Document |
Empty space around paragraphs and elements | Enter key. |
# Example Section Text for the example section. New paragraph for the example. Ending this paragraph and section. # Next Example Section |
Links | [link text](www.full-link.com) |
The [Trident website](https://www.project-trident.org) |
Lists | 1. OR #. OR - |
1. Enumerated list. #. Autonumbered list. - Unordered list. |
Images |  |
 |
Graphical Interface Item | **Bold Text that Matches the Item Name Exactly** | **Insight** file manager |
Examples or an exact string to type | One backtick (`) for inline text. Three backticks (```) for blocks. | “Open a terminal and type `ls`” becomes “Open a terminal and type ls “ |
Markdown Escape Character | \ | Use a backtick (\\ ).` |
The rest of this document provides more details about Trident documentation tools and more guidelines for writing style.
This section outlines the tools that Trident uses to build and publish its documentation.
Project Trident uses the Hugo site generator to create the Project Trident website. The website is created from files stored in the trident-website repository. Documentation articles are written with the Markdown syntax. The online GitHub web editor can be used to write and test Markdown files. There is no requirement to download or use a text editing program.
All documentation articles are contained in the /hugo-site/content directory of the trident-website repository.
Adding a new file or editing an existing article will trigger rebuilding the website.
The website updates every
The following sections explain the different standards that Trident applies to documentation contributions. These sections have a “top-down” approach, starting with universal elements that are applied to every file and zooming in to describe specific markup to use for text elements.
Every Markdown file needs to include several elements:
Store images in the /static/images subdirectory of the hugo-site.
Create images as .png files and name them according to a descending order of description: trident-installer-disk.png
Image syntax in a Markdown file is 
Image: 
Table:
| Syntax | Description |
| ----------- | ----------- |
| Header | Title |
| Paragraph | Text |
Fenced Code Block:
```
{
"firstName": "John",
"lastName": "Smith",
"age": 25
}
```
Footnote: Here's a sentence with a footnote. [^1]
[^1]: This is the footnote.
Heading ID: ### My Great Heading {#custom-id}
Strikethrough: ~~The world is flat.~~
Task List: - [x] Write the press release
- [ ] Update the website
- [ ] Contact the media
Here is specific syntax usage used by Project Trident:
*italic*
**bold**
Translation system is still to be determined. Update this section when the translation system is finalized.
Translation files are stored in .