meta data for this page
- en
This is an old revision of the document!
Welcome
to the world of uiTotalLauncherManual and It's Dokuwiki
uiTLM is glad you decided to visit this page. It's a first step for many in deciding whether to Register, what Benefits are to be gained, and answer some questions about Total Launcher and lessen it's learning curve with the uiTLM “Easier Easy” guide … even contribute with error correction and learning tips for other users.
So, let's get started with what can be helpful in this next step.
Benefits of Registration
Navigation Around the Wiki
There are many aids available with uiTLM to research and find areas of interest related to the Total Launcher application. Learn more
Wiki Concepts: Getting Started
Before starting to edit and contribute to pages, a few “Big Picture” concepts for more easily managing documentation is shown
DokuWiki Syntax: The Essentials
DokuWiki is designed to be simple. There is noneed to learn complex code … just “wrap” text in a few special characters. To learn more ++++click here.|
Headings
Headings use equals signs '='. Use more for smaller sub-sections. Notice how the number of ”=“ decreases on both sides as the subheading becomes lower.
- ====== Page Title ======
- ===== Section Title =====
- ==== Sub-Section ====
Headings use equals signs `=`.
- The more equal signs used, the larger or higher the heading. The '=' must start on the left margin.
- `====== Top Level Title ======` (Main page title)
- `===== Section Title =====`
- `==== Sub-Section ====`
Formatting Text
- Bold:
text - Italic:
text - Underline:
text Monospaced:text(Useful for file paths or variables)
Paragraphs and New Lines
DokuWiki handles “spacing” differently than a standard word processor.
- New Paragraph: Press Enter twice to leave a blank line. This is the best way to keep text readable.
- Forced New Line: If you want to drop to the next line without starting a new paragraph, type two backslashes followed by a space:
> The “SprintDoc” Rule: Always leave a blank line before and after a list, table, or code block to ensure the layout doesn't “break.”
Lists
Building lists is all about the indentation and steps.
- For bullet point: Use two spaces from the left margin and an asterisk ”'*
* For numbered list: Use two spaces from the left margin and a dash-* To create further indentation for either: add 2 more spaces to the previous indentationwiki- First bullet item
- Second bullet item
- Indented sub-item (four spaces)
- First numbered item
- Second numbered item
==== Links ==== To link to another page, a section on the eisting or other page or a website, use opening and closing double square brackets around the pagename * Internal: <code>pagename</code> * Internal with custom name: <code> Clickable Text</code> * External: <code> Google</code> === Media === To display any media use opening and closing curly braces (
) * Images (PNG, jpg gif, webp) * Video (animated gifs mp41)), use curly braces. * All media on a page must be located in themedinamespace * Media for a page is to be located in page namespace for the media * Example: write about a fish and insert a fish.png. The page is fish.tx * The fish lives in a “pond” (namespace/folder) * The link would be
*filename.ext*
— Displays the image at its original size. *
— Displays the image at 50 pixels wide (resizing made easy). === Simple Tables === Tables are built using vertical bars|for (cells) and carets for^'' (headers). Alignment can be specific for each cell or heading: - To center contents leave 2 spaces between the beginning and ending cell or header marker,
- leave 1 space for left aligned entries.
| Goal | Syntax | |
| Header 1 | Header 2 | |
|---|---|---|
| Content A | Content B |
Special Note for the “SprintDoc” Template
- Save often: The preview button is your best friend.
- Whitespace matters: Always leave one empty line between a paragraph and a list or table to make sure the “SprintDoc” template displays everything perfectly.
</WRAP>
Discussion