Metamation Developer Notes

  • Developer Notes
  • Resource Map
  • Tools
    • Code Formatting
    • Configuring Git
    • Assignments
    • Testing with Windows Sandbox
    • Single Binary Applications
    • Self-Updating Applications
  • Flux Workflow
    • Flux Workflow
    • Flux Development Style Guide
    • Release notes for Flux
    • SonarCloud analysis for Flux
    • Build a Flux SDK Program
    • Shipping Flux
    • Flux.Test
      • BasicBendAuto Test
      • LaserAuto.cs Detailed Documentation
      • Laserexample:Test1
  • Technical Notes
    • File formats
      • .FX File Format
      • Au(Gold) streams
      • .GEO File Format
      • .LST File Format
      • .LST file - technology
      • .BNC File Format
      • .WAD Files: Flux Resource Packages
      • .Curl Files: ASCII config information
    • Folders App
      • Data\Bendtools
      • Data\Machines
    • FluxCode
      • Welcome & Repo Map
      • Architecture & System Context
      • Subsystem *Bend* (Press Brake)
      • Subsystem *BCell* (Bend Cell Automation)
      • API Maps
      • Data Model Catalog
      • Design Patterns -- A Reader's Guide
      • Tests and Golden Paths
      • Guided Code Tours
      • CAM Glossary with Code Mapping
      • Assignments
      • Flux Onboarding Handbook
    • Data flow
      • Part
        • Part.Dwg
        • Part.Load
        • Part.Load to Part.Dwg
      • BendTech.cs
      • Bend Technology
      • Laser Cutting Technology
    • LTS (Long term support mechanism)
    • Machine ID Scheme
  • FluxTester
    • Commands and Scripts
    • Command Cookbook
    • Script Commands
    • BendTooling.cs Test Inventory
    • LaserTooling.cs Test Steps
    • Fluxtester Recipe Book
    • Nesting.cs Overview
    • Nesting.cs Recipe Book
    • Job.cs Overview
    • Job.cs Recipe Book
  • Software license
  • 3d party software
    • Python
  • Documentation
    • Bento documentation
      • Structure of a Bento page
      • Attributes
    • Software
      • Software Requirement
      • Installation
      • Git workflow for documentation contributors
    • Quick start guide
    • Workflow
      • Roles and responsibilities
      • Analyze
      • Edit
      • Proofread
      • Pre-Publish
      • Publish
      • Release cycle
      • Information required for Documentation Team
      • Checklist for Documenters
    • Styleguide
    • Flavoring
    • Translation
      • Ordering translation for a new document
    • Citations
    • Annotation
Documentation
/
Styleguide

Styleguide

General guidelines

  1. Remove spaces in folder names and filenames.

    Incorrect Correct

    My File.adoc

    MyFile.adoc

    Quick Start/

    QuickStart/

    imagetitle.png

    ImageTitle.png

  2. Remove hyphens in folder names and filenames.

    Incorrect Correct

    Release-Notes.adoc

    ReleaseNotes.adoc

    Tech-Notes/

    TechNotes/

    image-title.png

    ImageTitle.png

  3. Use PascalCase for all filenames and folder names.

    Incorrect Correct

    styleguide.adoc

    Styleguide.adoc

    releaseNotes/

    ReleaseNotes/

  4. Avoid having more than one blank line anywhere in an AsciiDoc document.

    Incorrect Correct
    == Section A
    
    
    
    == Section B
    == Section A
    
    == Section B
  5. Avoid trailing spaces at the end of any line.

    How to enable auto-trimming in Visual Studio Code

    To handle this automatically in Visual Studio Code, open Settings (Ctrl+,), search for Trim Trailing Whitespace, and enable the checkbox. This will remove trailing spaces every time you save a file.

  6. Keep lines under 100 characters. Split longer lines into multiple lines.

    How to add a vertical ruler in Visual Studio Code

    To visually identify long lines, add a ruler at column 100 in Visual Studio Code. Open Settings (Ctrl+,), search for Editor: Rulers, click Edit in settings.json, and add the following:

    "editor.rulers": [100]

    This displays a vertical line at column 100, making it easy to spot lines that need to be split.

    Incorrect Correct
    This is a very long line that exceeds the hundred character limit and makes the document harder to read and review.
    This is a very long line that exceeds
    the hundred character limit and makes
    the document harder to read and review.

Links

Cross-references (links within the documentation)

Use xref: to link to other pages within the documentation. The path is relative to the current file. The format is xref: followed by the relative path, a # separator, and the link text in square brackets.

Examples
AsciiDoc markup Result

xref:Software/Git#[Git Workflow]

Git Workflow

xref:../Tools/ConfigureGit#_git_installation[Git Installation]

Git Installation

To link to a specific section within a page, append the section anchor after #:

xref:Index#_documentation_index[Documentation Index] renders as Documentation Index

External links

Use link: or a bare URL to link to external websites.

Syntax
link:https://example.com[Link Text]
Example
link:https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/[AsciiDoc Syntax Quick Reference]

To link to a specific section on an external page, include the anchor in the URL:

link:https://fluxbook-en.onrender.com/bend/editing/editbend.html#_editing_a_hem_bend[Editing a Hem Bend]

Images

Every AsciiDoc file that uses images should declare the images directory at the top of the file using :imagesdir: img. This tells AsciiDoc to look for images in the img folder relative to the current file. Save all images as .png files using PascalCase naming in the corresponding img folder.

Block images

Block images appear on their own line and are used for screenshots, diagrams, and figures. The syntax uses image followed by two colons, the filename, and attributes in square brackets.

Format Description

image::Photo.png[Alt text]

Basic block image with alt text

image::Photo.png[Alt text,width=600]

Block image with a named width attribute

image::Photo.png[Alt text,600]

Block image with width as a positional attribute

Inline images

Inline images appear within a line of text, such as icons or small graphics. Use image followed by a single colon instead of two.

For example, Click the image:Icon.png[Button,16] renders a small image inline with the text.

Image titles

Add a title above a block image using a . prefix on the line before the image declaration. For example:

.Git workflow overview
image::Workflow.png[]

This renders a captioned figure with the title displayed above the image.

Keyboard shortcuts

Use the kbd:[] macro to display keyboard shortcuts in a styled format. This requires the :experimental: attribute to be set at the top of the file.

The format is kbd: followed by the key combination in square brackets. Use + to separate multiple keys in a combination.

Examples
AsciiDoc markup Result

kbd:[Ctrl+C]

Ctrl+C

kbd:[Ctrl+Shift+P]

Ctrl+Shift+P

kbd:[Enter]

Enter

kbd:[Ctrl,]+

Ctrl+,

kbd:[F5]

F5

Use keyboard shortcuts inline with text:

Press kbd:[Ctrl+S] to save the file.

This renders as: Press Ctrl+S to save the file.

Contents

  • General guidelines
  • Links
  • Cross-references (links within the documentation)
  • External links
  • Images
  • Block images
  • Inline images
  • Image titles
  • Keyboard shortcuts
Checklist for Documenters Flavoring

      Copyright © 2025 TRUMPF Metamation. All rights reserved.

    Compiled by Bento