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
/
Workflow
/
Roles and responsibilities

Roles and responsibilities

Product Owners and Product Experts

Product owners and product experts play a crucial role in the documentation process. They are responsible for providing the necessary information and input to the documentation team to create accurate and comprehensive documentation for the products.

Product owners are responsible for their own product documentation. Product owners should regularly check their documentation to ensure it is complete and readable. Product owners must evaluate the release notes, open a case in Fogbugz, establish priorities, and notify the documentation team.

  • Minor updates (like updating screenshots) don’t need a lengthy description. Just create a FogBugz case for Documentation with reference to the relevant release note.

  • Major updates and new features require Product Owners to define the substance of the documentation. It is needed to include high-quality images (.png files) with the input files. Provide the input in asciidoc format (if possible) or in a basic word document for the documentation team to work with.

  • Minute updates can be added directly in the respective product’s GitHub repository. Create a FogBugz case to inform the documentation team about this minute update. This will help the documentation team in processing the branch for review and merge.

Procedure for minute updates in GitHub:

  1. Navigate to the file you want to edit.

  2. Click on Edit this file icon and edit your changes.

directcommit
  1. After editing, click Commit changes…​ to create a new branch with a commit message.

commitchanges
Source .adoc file
preview
Preview of the source .adoc file
  1. Type the commit message, add description, select Creating a new branch for this commit, and type the branch name.

proposechange
Create new branch for the commit
  1. Click Propose changes to create a pull request.

openpr
Propose changes to create a pull request
  1. Goto the Pull Request and assign it to documentation team member.

  2. After the documentation team has reviewed and merged the changes into the main branch, close the FogBugz case.

Documentation Team

The documentation team is responsible for:

  • Updating the documentation according the Fogbugz cases created by the Product Owners.

  • Work on major updates (convert input file to asciidoc format), commit changes and assign pull request for review.

Complex Document Tasks

For complex file conversions or creating complex document structures, reach out to the documentation team directly.

Contents

  • Product Owners and Product Experts
  • Documentation Team
  • Complex Document Tasks
Workflow Analyze

      Copyright © 2025 TRUMPF Metamation. All rights reserved.

    Compiled by Bento