docs: add comprehensive workflow documentation with german translations#3665
docs: add comprehensive workflow documentation with german translations#3665EPajares merged 7 commits intoplan4better:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds comprehensive workflow documentation to the GOAT docs (both English and German), updates the map interface documentation to reflect UI changes, and reorganizes the documentation sidebar ordering to accommodate the new Workflows section.
Changes:
- Adds new English and German documentation for the Workflow Interface, Workflow Variables, and Custom SQL features, along with supporting icon images and screenshot assets
- Updates the Map Interface and Layers documentation (EN + DE) to reflect a redesigned panel structure (new Layers Panel, Tools section, Editing Panel), and updates icon references from
compass-drafting.pngtocompass.png - Reorganizes sidebar positions across multiple categories and adds workflow-related terms to the GOAT UI glossary
Reviewed changes
Copilot reviewed 20 out of 52 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
apps/docs/docs/workflows/workflow_interface.md |
New English workflow interface documentation |
apps/docs/docs/workflows/variables.md |
New English workflow variables documentation |
apps/docs/docs/workflows/custom_sql.md |
New English custom SQL documentation |
apps/docs/docs/workflows/_category_.json |
Workflows category config at position 4 |
apps/docs/i18n/de/.../workflows/workflow_interface.md |
German translation of workflow interface |
apps/docs/i18n/de/.../workflows/variables.md |
German translation of variables doc |
apps/docs/i18n/de/.../workflows/custom_sql.md |
German translation of custom SQL doc |
apps/docs/i18n/de/.../workflows/_category_.json |
German workflows category config |
apps/docs/docs/map/map_interface.md |
Restructured map interface with new panels/tools layout |
apps/docs/docs/map/layers.md |
Updated layers management with group layers feature |
apps/docs/i18n/de/.../map/map_interface.md |
Partial German map interface update (Layer Panel only) |
apps/docs/i18n/de/.../map/layers.md |
German layers update with group layers |
apps/docs/docs/getting_started/quickstart_guide.md |
Updated quickstart to reflect new UI layout |
apps/docs/i18n/de/.../getting_started/quickstart_guide.md |
German quickstart update |
apps/docs/docs/data/data_types.md |
Updated image reference for view data |
apps/docs/docs/Scenarios/Scenarios.md |
Updated icon and sidebar position |
apps/docs/docs/nerdy_content/GOAT_ui_glossary.md |
Added workflow-related glossary terms |
apps/docs/docs/builder/_category_.json |
Position changed from 4 to 6 |
apps/docs/docs/sharing/_category_.json |
Position changed from 5 to 8 |
apps/docs/docs/routing/_category_.json |
Position changed from 7 to 9 |
Various icon .png files |
New icon assets for workflow toolbar buttons |
Various .webp screenshot files |
Updated/new screenshots for interface documentation |
You can also share your feedback on Copilot code review. Take the survey.
|
|
||
| **Workflows** in GOAT bieten ein mächtiges visuelles Automatisierungssystem zur Erstellung anspruchsvoller räumlicher Analysepipelines. Anstatt einzelne Werkzeuge nacheinander auszuführen, können Sie mehrere Analyseschritte mit einer Drag-and-Drop-Leinwand verbinden und dabei eine automatisierte Datenverarbeitung erstellen, die wiederholende manuelle Arbeit eliminiert. | ||
|
|
||
| Die Workflows können bei verschiedenen Datensätzen und Szenarien wiederverwendet werden. Jeder Workflow besteht aus verschiedenen Arten von [Knoten](../further_reading/glossary.md#knoten), die durch [Kanten](../further_reading/glossary.md#kanten) verbunden sind, und ermöglicht Ihnen: |
There was a problem hiding this comment.
Same as the English version, multiple glossary anchors referenced in this German translation don't exist in the German glossary (apps/docs/i18n/de/.../further_reading/glossary.md):
../further_reading/glossary.md#knoten(line 9)../further_reading/glossary.md#kanten(line 9)../further_reading/glossary.md#workflow(line 142)
These anchors need to be added to the German glossary.
| Die Workflows können bei verschiedenen Datensätzen und Szenarien wiederverwendet werden. Jeder Workflow besteht aus verschiedenen Arten von [Knoten](../further_reading/glossary.md#knoten), die durch [Kanten](../further_reading/glossary.md#kanten) verbunden sind, und ermöglicht Ihnen: | |
| Die Workflows können bei verschiedenen Datensätzen und Szenarien wiederverwendet werden. Jeder Workflow besteht aus verschiedenen Arten von [Knoten](../further_reading/glossary.md), die durch [Kanten](../further_reading/glossary.md) verbunden sind, und ermöglicht Ihnen: |
| Das **Benutzerdefinierte SQL**-Werkzeug ermöglicht es Ihnen, benutzerdefinierte SQL-Abfragen für Datenanalysen direkt innerhalb Ihrer [Workflows](../further_reading/glossary.md#workflows) zu schreiben. Diese mächtige Funktion ermöglicht erweiterte Datenverarbeitung, die über GOATs eingebaute Werkzeuge hinausgeht. | ||
|
|
||
| ## Übersicht | ||
|
|
||
| Das Benutzerdefinierte SQL-Werkzeug verbindet sich mit GOATs [DuckDB](../further_reading/glossary.md#duckdb) Backend und gibt Ihnen direkten Zugriff auf die Abfrage Ihrer Datensätze mit SQL-Syntax. Sie können: |
There was a problem hiding this comment.
Multiple glossary anchors referenced here don't exist in the German glossary:
../further_reading/glossary.md#workflows(line 3, 7)../further_reading/glossary.md#duckdb(line 11)../further_reading/glossary.md#datensatz-knoten(line 30)../further_reading/glossary.md#temporäre-ebene(line 172)../further_reading/glossary.md#export-knoten(line 175)
These anchors need to be added to the German glossary, or the links should be removed.
| ### Query Validation | ||
|
|
||
| <div class="step"> | ||
| <div class="step-number">1</div> | ||
| <div class="content"><strong>Syntax Check</strong>: The editor highlights syntax errors as you type.</div> | ||
| </div> | ||
|
|
||
| <div class="step"> | ||
| <div class="step-number">2</div> | ||
| <div class="content"><strong>Preview Results</strong>: Use the <code>Preview</code> button to see the first few rows of results.</div> | ||
| </div> |
There was a problem hiding this comment.
The English version of the Query Validation section has only 2 steps (Syntax Check, Preview Results), while the German translation has 3 steps including a "Validate query" step (clicking a Validate button). The German version also includes a "Configuration Options" section (Query Timeout, Result Limit, Column Types at lines 94-100) that is completely absent from the English version. The English and German versions should be consistent — either add the missing content to the English version or remove it from the German version.
There was a problem hiding this comment.
Removed from german version
| :::tip Technische Dokumentation | ||
|
|
||
| Für detaillierte Informationen über die zugrundeliegenden Prozesse und Werkzeuge besuchen Sie bitte die **Prozesse API** im **Geoapi Ordner**. Weitere Low-Level-Werkzeugbeschreibungen finden Sie auch in der **goatlib** im Packages-Verzeichnis. | ||
|
|
||
| ::: | ||
|
|
||
|
|
There was a problem hiding this comment.
This "Technical Documentation" tip references internal code structure ("Prozesse API im Geoapi Ordner", "goatlib im Packages-Verzeichnis") which is inappropriate for end-user documentation. It exposes internal repository structure to users who wouldn't have access to the codebase. Additionally, this tip doesn't exist in the corresponding English version of layers.md, creating a discrepancy between translations. This tip should be removed.
| :::tip Technische Dokumentation | |
| Für detaillierte Informationen über die zugrundeliegenden Prozesse und Werkzeuge besuchen Sie bitte die **Prozesse API** im **Geoapi Ordner**. Weitere Low-Level-Werkzeugbeschreibungen finden Sie auch in der **goatlib** im Packages-Verzeichnis. | |
| ::: |
|
|
||
| ### In Tool Parameters | ||
|
|
||
| Variables can be used in most many configuration fields: |
There was a problem hiding this comment.
"most many" is grammatically incorrect — it should be either "most" or "many", not both. For example: "Variables can be used in many configuration fields" or "Variables can be used in most configuration fields".
| Variables can be used in most many configuration fields: | |
| Variables can be used in most configuration fields: |
|
|
||
| **Workflows** in GOAT provide a powerful visual automation system for creating sophisticated spatial analysis pipelines. Instead of running individual tools sequentially, you can connect multiple analysis steps together using a drag-and-drop canvas, creating an automated data processing that eliminates repetitive manual work. | ||
|
|
||
| The workflows can be reused across different datasets and scenarios. Each workflow consists of different types of [nodes](../further_reading/glossary.md#node) connected by [edges](../further_reading/glossary.md#edge), enabling you to: |
There was a problem hiding this comment.
Multiple glossary anchors referenced throughout the new workflow documentation don't exist in the glossary page (apps/docs/docs/further_reading/glossary.md). The following links will be broken:
../further_reading/glossary.md#node(line 9)../further_reading/glossary.md#edge(line 9)../further_reading/glossary.md#workflow(line 144)../further_reading/glossary.md#temporary-layer(line 159)../further_reading/glossary.md#export-node(line 162)
These anchors need to be added to the glossary, or the links should be removed/replaced.
| The workflows can be reused across different datasets and scenarios. Each workflow consists of different types of [nodes](../further_reading/glossary.md#node) connected by [edges](../further_reading/glossary.md#edge), enabling you to: | |
| The workflows can be reused across different datasets and scenarios. Each workflow consists of different types of [nodes](../further_reading/glossary.md) connected by [edges](../further_reading/glossary.md), enabling you to: |
| The Custom SQL tool creates a new [temporary layer](../further_reading/glossary.md#temporary-layer) containing your query results. You can: | ||
|
|
||
| - Connect the output to other workflow tools for further analysis | ||
| - Add an [export node](../further_reading/glossary.md#export-node) to save results as a permanent dataset |
There was a problem hiding this comment.
The Custom SQL doc references several glossary anchors that don't exist in the glossary (apps/docs/docs/further_reading/glossary.md):
../further_reading/glossary.md#temporary-layer(line 159)../further_reading/glossary.md#export-node(line 162)
Additionally, the DuckDB backend is mentioned in the Overview but there's no glossary entry for it, unlike the corresponding German version which links to glossary.md#duckdb. These should be added to the glossary or the links adjusted.
| The Custom SQL tool creates a new [temporary layer](../further_reading/glossary.md#temporary-layer) containing your query results. You can: | |
| - Connect the output to other workflow tools for further analysis | |
| - Add an [export node](../further_reading/glossary.md#export-node) to save results as a permanent dataset | |
| The Custom SQL tool creates a new [temporary layer](../further_reading/glossary.md) containing your query results. You can: | |
| - Connect the output to other workflow tools for further analysis | |
| - Add an [export node](../further_reading/glossary.md) to save results as a permanent dataset |
apps/docs/docs/map/map_interface.md
Outdated
| - <img src={require('/img/icons/compass.png').default} alt="Scenarios" style={{ maxHeight: "20px", maxWidth: "20px", objectFit: "cover"}}/> <code>Scenarios</code>: <strong>Access to Scenarios</strong>. Read more in <a href="/category/scenarios">Scenarios</a>. | ||
|
|
||
| - <img src={require('/img/icons/ruler-horizontal.png').default} alt="Measurements" style={{ maxHeight: "20px", maxWidth: "20px", objectFit: "cover"}}/> <code>Measurements</code>: Users can <strong>measure distances and areas</strong>, such as routes, lines and polygons. | ||
| Read more in <a href="/category/measurements">Measurements</a>. |
There was a problem hiding this comment.
The link <a href="/category/measurements">Measurements</a> points to a category page that doesn't exist — there is no measurements directory with a _category_.json file in the docs. This will result in a broken link. Either create the measurements category/documentation or link to an existing page instead.
| Read more in <a href="/category/measurements">Measurements</a>. | |
| Read more in the Measurements section. |
Removed redundant line about Measurements.
Removed steps for previewing results and configuration options from the custom SQL documentation.
Removed technical documentation tip and related content.
|
Thank you for following the naming conventions! 🙏 |
Description
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Related Issue