Effectively Using Gaea Community

General
, ,
1

[!summary]+
This wiki explains how to use Gaea Community well:

  • finding answers quickly
  • posting in the right place
  • writing useful help, bug, and feedback topics
  • following official information
  • using bookmarks, voting, solutions, and notifications
  • formatting posts with Markdown, callouts, tables, dropdowns, grids, carousels, and keyboard-key styling

and it is large

If you are new here, you may want to start with:

This wiki can be maintained and edited by T3 users or above.

Table of Contents

Show/Hide

Community Basics

Finding Information

Posting Well

Forum Tools

Post Customisation and Formatting

[!attention]
If table-of-contents links do not jump correctly on this forum, the section headings still provide a clear manual index.

Community Basics

Use this section to understand what the forum is for, when to use chat, when to use topics, and where to post.

01. Start Here: What This Community Is For

Gaea Community works best as more than a fast chat.

It is a place for:

  • searchable answers
  • official updates
  • support questions
  • bug reports
  • workflow feedback
  • feature ideas
  • learning resources
  • finished showcases
  • shared files
  • Long term knowledge

[!success]
Good topics become future answers.
A clear post today can help someone else through search tomorrow, next month, or a year from now. This is one of the biggest goals.

[!tip]-
Use chat for quick conversation.
Use topics when the information should be searchable, linkable, bookmarkable, and useful later.

[!example]Back to Contents

02. Quick Start: What Should I Do?

Goal Best action
Find an answer Search first, use quotes for exact phrases
Ask for help Include the goal, relevant flow/node/tool, expected result, actual result, screenshots, and what you tried
Report a bug Include version, Diagnostics - Watson receipt code, steps, evidence, expected result, and actual result
Suggest an idea Explain the problem, why it matters, current workaround, and suggested improvement
Share a workflow Use headings, screenshots, node links, and examples
Follow official updates Use bookmarks, reminders, and notification settings
Share images Use image grids, carousel blocks, or normal images with lightbox
Make long-term knowledge Use Markdown, callouts, tables, dropdowns, and clear section headers

[!tip]
If your post could help other users later, structure it like a reference page, not just a quick message.

[!example]Back to Contents

03. Chat or Topic?

Use chat for quick, lightweight conversation.

Use a topic when:

  • the answer should be searchable later
  • files or screenshots matter
  • the discussion may help other users in future
  • you want a solved answer
  • the discussion needs a longer feedback thread
  • the information should be bookmarkable or linkable
Use chat for Use a topic for
Quick back-and-forth Help requests
Casual clarification Bug reports
Short updates Tutorials
Small questions Feature feedback
Live discussion Official or reusable answers
Temporary conversation Anything that may become long-term knowledge

[!hint]
Useful chat should become a topic.

If a chat discussion becomes structured, useful, or reusable, ask staff/admins to help turn it into a proper topic where appropriate.

[!example]Back to Contents

04. Choose the Right Category

Use the category that best matches your main goal.

Category Use for
General Broad community discussion and forum-wide topics
Using Gaea > Ask for Help Troubleshooting and workflow questions
Learning Guides, articles, videos, tutorials, and learning resources
Feedback > Bugs Product issues and reproducible bugs
Feedback > Ideas Feature suggestions and workflow improvements
Feedback > Forums Feedback about this forum itself
WIP Feedback Critique on work in progress
Gallery Finished showcases and portfolio-style posts
Share Files Reusable files, resources, and shared assets

If your topic could fit more than one place, choose the category based on your primary purpose, then use tags to add context.

[!warning]
Do not post the same issue in multiple categories.

If it is already being discussed, add useful details to the existing topic instead, the composer often states if it finds something similar.

Finding Information

Use this section to search better, find official updates, and link Gaea docs.

[!example]Back to Contents

05. Search: Find Answers Fast

Before starting a new topic, try the search bar.

Useful examples:

"Gaea 3" order:latest

gaea2unreal categories:using-gaea,learning order:latest

udim with:images

tags:resources categories:learning

status:solved categories:using-gaea after:YYYY/MM/DD

in:wiki community

"Cellular" order:latest

"Height Remap" "Unreal"

[!tip] Search Tips

  • Use "quotes" for exact phrases.
  • Add order:latest when recency matters more than relevance.
  • Add with:images when looking for visual workflows or node examples.
  • Search by category or tag when you already know the area.
  • Use in:title when searching for topic titles only.
  • Use in:first when searching original posts only.
  • Use in:wiki when looking for maintained wiki content.
  • Look for solved topics and useful issue-state tags.

Exact search is especially useful for terms like Gaea, erosion, build, export, Unreal, and node names because these can appear in many unrelated discussions.

Advanced search ideas

Try these when normal search gives too many results:

after:30
order:views
order:likes
in:title
in:first
in:official
with:images
status:solved
categories:using-gaea
tags:resources

Examples:

"Cellular" with:images
"Unreal" "Height Remap" order:latest
in: official "Gaea 3"
status:solved "tiled build"
in: resources

06. Search First, Then Ask Better

If you searched but did not find a clear answer, mention what you searched for.

[!check] A Good Example
I searched for “Height Remap”, “Unreal node”, and “Gaea 2.3 export”, but I could not find a current answer for this workflow.

This helps others understand what you already tried and prevents repeated answers.

[!success]
Searching first does not mean you cannot ask.

It means your question becomes easier to answer well.

[!example]Back to Contents

07. Link Gaea Docs and Node References

When discussing a specific Gaea node, workflow, bridge, or setting, link the relevant documentation when possible.

Example full docs link:

https://docs.gaea.app/reference/nodes/primitive/cellular.html

vs

Example Node Shortcut:

/cellular

Now this is just a very simple link in context
/cellular

Use node shortcuts when discussing:

  • node-specific help
  • graph breakdowns
  • tutorials
  • feedback about a node
  • compositing workflows
  • export/import workflows
  • examples using specific nodes

[!hint]
This works in chats and topics

Example: node-specific question

[!fail]Less useful:
How do I make this pattern better?

[!check] More useful:
How can I use /cellular to create larger broken-up terrain regions before erosion?

[!question]If a shortcut is not available
How can I use the Cellular node to create larger broken-up terrain regions before erosion?
Docs:
Cellular - Gaea Documentation - QuadSpinner

Posting Well

Use this section to ask for help, report bugs, give feedback, and share screenshots clearly.

[!example]Back to Contents

08. Write Searchable Topic Titles

A good title should include the most important context.

Title Formula

Gaea version + node/tool/workflow + problem or goal

Examples:

Less useful More useful
Help please Gaea 2.3 crash when baking Cellular node in tiled build
Unreal problem Height Remap changes terrain elevation when exporting back to Unreal
How do I make this better? How can I reduce terracing after Erosion before Unreal export?
Bug? File node fails to load 16-bit heightmap after project reload
Gaea 3 Where should we track current Gaea 3 official updates?

[!success]
Strong titles help everyone.

They make topics easier to search, easier to answer, and easier to turn into long-term knowledge.

[!example]Back to Contents

09. Ask for Help Well

A strong help post gives enough context for someone else to understand the goal, the result, and what you already tried.

Include:

  • what you are trying to do
  • relevant node/tool/workflow
  • Gaea version if relevant
  • target app or bridge if relevant
  • what you expected
  • what happened instead
  • what you already tried
  • screenshots, files, logs, or graph images where useful
  • related docs or topics

[!important]

  • General help posts do not need full hardware details.

  • If the issue is a technical bug, crash, install problem, or support-worthy issue, use the Diagnostics / Watson workflow sharecodes in the bug report section.

  • If the supoprt is genuinly for Quadspinner only then use the Support ticket system instead, this is especially important for sensitive information

Lightweight Help Request Template

Copy/paste lightweight help request template 
## What I am trying to do

Explain the goal.

## Relevant node, tool, graph area, or workflow

Node/tool:
Bridge/export target if relevant:
Docs link or node shortcut if useful:

## Gaea version

Exact version/build if relevant.

## What I expected

Describe the result you thought would happen.

## What happened instead

Describe the actual result.

## What I already tried

List searches, settings, tests, or workaround attempts.

## Screenshots / files

Add graph overview, node settings, viewport result, export result, logs, or files where useful.

## Related topics or docs

Paste links to relevant docs or existing forum topics.

[!tip]
Screenshots are often faster than paragraphs for visual terrain problems.
But the opposite is also true if it’s more engine errors or anomalies

[!example]Back to Contents

10. Report Bugs Clearly

Bug reports should mirror the information QuadSpinner support needs.

For technical problems, crashes, or reproducible issues, use Gaea Diagnostics

[!important]
If you can generate a Diagnostics / Watson Log Receipt code, include that instead of manually listing OS, GPU, drivers, and hardware details.

The diagnostics package already contains technical information that helps support investigate the issue.
Log Receipt/sharecode, is safe to post on the forums only Quadspinner can access them.

Example:

0A7-20241113

Bug Report Template

Copy/paste bug report template 
## Summary

One-sentence description of the issue.

## Gaea version

Exact version/build if known.

## Diagnostics / Watson receipt code

Example: 0A7-20241113

If you cannot generate a receipt code, say why.

## Relevant node, tool, graph area, or workflow

Node/tool:
Bridge/export target:
Project type:
Docs link or node shortcut if useful:

## What I expected

Describe what should have happened.

## What happened instead

Describe the actual result.

## Steps to reproduce

1.
2.
3.

## Evidence

Screenshots:
Screen recording:
Error message:
Project file or small test file, if safe to share:

## What I already tried

List any workaround attempts, searches, resets, rebuilds, or settings changes.

## Search notes

I searched for:
-
-

[!danger]
Do not share sensitive information publicly.

Before uploading screenshots, logs, project files, or diagnostics files, check for:

  • license keys
  • TXN
  • screenshots of account page
  • email addresses
  • account details
  • private file paths
  • client/project names
  • unreleased work
  • personal information

[!example]Back to Contents

11. Give Useful Feedback and Feature Ideas

Good feedback explains the problem, not only the requested solution.

Include:

  • the problem
  • why it matters
  • who it affects
  • current workaround
  • suggested improvement
  • examples or screenshots
  • priority

Feedback Template

Copy/paste feedback or feature idea template 
## Problem

What is difficult, confusing, slow, missing, or error-prone?

## Why it matters

Who does this affect?
How often does it happen?
What workflow does it block or slow down?

## Current workaround

How are users solving it now?

## Suggested improvement

What would make this better?

## Example

Add screenshots, mockups, workflow examples, docs links, or related topics.

## Priority

Nice-to-have / important / workflow-blocking
Less useful More useful
Please change this This workflow takes five repeated steps; a shortcut would reduce setup time
This is bad This setting is unclear because the viewport result looks correct but export changes the height
Add this feature Here is the workflow problem, current workaround, and suggested implementation

[!tip]
Feedback works best with examples.

A screenshot, before/after comparison, or small workflow case often explains the issue faster than a long description.

[!example]Back to Contents

12. Share Screenshots and Visual Examples

Gaea is visual, so images might end up essential.

Good screenshots include:

  • full graph overview
  • close-up of relevant nodes
  • node properties panel
  • data view panel
  • viewport result
  • export/import result
  • error message or build log if relevant

[!hint]

  • [grid mode=carousel]...[/grid]
    is a fantastic way to show case multiple images and keep your screen estate cleaner
  • The forum mostly support images and gifs, video should be externally linked in.

[!example]Back to Contents

1 Like
2

In This Section

Show/Hide

Forum Tools

Post Customisation and Formatting

[!attention]
If table-of-contents links do not jump correctly on this forum, the section headings still provide a clear manual index.

Forum Tools

Use this section to understand bookmarks, voting, likes, solutions, notifications, and trust levels.

[!example]Back to Contents

13. Use Replies Well

Use replies to keep topics useful and focused.

  • Use Like when you agree or found something useful.
  • Use a normal reply when continuing the same topic.
  • Quote only the part you are responding to.
  • If your reply becomes a different problem, create a linked topic using
    Reply as linked topic instead of derailing the original one.
  • If an answer solves the issue, mark the solution where that option is available.
  • If an issue has already been reported, add useful reproduction details instead of starting a duplicate.

[!success]
Useful replies add new information.

Examples:

  • reproduction steps
  • version details
  • screenshots
  • logs
  • workaround
  • confirmation that the issue also happens on another setup

[!example]Back to Contents

14. Stay Notified Without Overload

You do not need to live on the forum all day.

Use the tools that match your workflow:

  • watch topics you care about closely
  • track categories or tags you follow regularly
  • bookmark posts you want to revisit
  • use reminders for things to come back to
  • enable the forum as an app in your browser if you want a desktop-like experience
  • use email digests if you prefer a catch-up workflow

Notification Levels

Level Use when…
Watching You want notifications for all activity
Watching First Post You want to know when new topics are created, without every reply
Tracking You want unread counts and normal awareness
Normal You only need replies or mentions
Muted You do not want the category/topic appearing prominently

[!tip]
For official update areas, consider Watching First Post or bookmarking important topics.

That keeps you informed without turning every reply into a notification.

[!example]Back to Contents

15. Use Bookmarks as a Personal Follow-Up System

Bookmarks are useful for keeping track of important topics.

Use bookmarks for:

  • official updates
  • known issues
  • tutorials you want to try
  • answers you may need later
  • posts you want to reply to
  • topics you want to revisit
  • wiki pages
  • useful node/workflow explanations

[!tip]
Bookmark official information.

If an official topic is important to you, bookmark it and set a reminder instead of trying to remember where it was.

Example bookmark names:

Check after next Gaea update
Useful Unreal height workflow
interesting node example
Known issue to revisit
Good template

[!example]Back to Contents

16. Trust Levels

Trust Levels unlock more participation over time through reading and healthy activity.

In short:

  • read broadly
  • like useful content
  • reply where you can add value
  • keep posts tidy and constructive
  • avoid spammy or duplicate posting
  • help keep useful topics accurate

See: Trust Levels

[!example]Back to Contents

17. Voting, Likes, Solutions, and Wiki Posts

Use forum tools to make useful information easier to identify.

Tool Use it for
Like Thanking someone or marking a useful reply
Vote Supporting ideas or requests when voting is enabled
Solution Marking the answer if the category supports solved topics
Bookmark Saving something for later
Quote Replying to a specific point clearly
Edit Fixing mistakes or improving a post
Wiki Maintaining long-term community information

[!success]
If a reply solves your issue and the category supports solutions, mark it as the solution.

This helps future users find the answer faster.

See: Topic voting

Post Customisation and Formatting

Use this section to make posts clear, readable, compact, and visually useful.

[!example]Back to Contents

18. Rich Text Editor vs Markdown Editor

Discourse may let you switch between a Rich Text editor and a Markdown editor.

Both are useful.

Editor mode Best for Why use it
Rich Text Quick replies, simple posts, casual discussion Easier and more visual
Markdown Wikis, guides, templates, bug reports, callouts, image grids, tables, code blocks More precise and maintainable

[!important]
Use Markdown when the post should become long-term knowledge.

This includes wikis, tutorials, bug reports, structured feedback, and reusable examples.

Use Rich Text when...

Use Rich Text when you are:

  • replying casually
  • giving quick feedback
  • writing a short answer
  • adding simple bold text, links, or images
  • not worried about exact structure

Rich Text is good for speed.

Use Markdown when...

Use Markdown when you are:

  • making a wiki
  • writing a guide
  • sharing a tutorial
  • posting a bug report
  • using callouts
  • using details dropdowns
  • using image grids
  • writing code/log examples
  • creating copy/paste templates
  • formatting something others may reuse later

Markdown is good for structure.

[!example]Back to Contents

19. Composer Tools: Toolbar, Shortcuts, and Menus

Discourse does not currently behave like a full right-click Markdown context-menu editor in the same way some desktop writing apps do.

Instead, use:

  • the composer toolbar
  • the composer actions/options menu
  • keyboard shortcuts
  • Rich Text editor controls
  • Markdown syntax
  • callout controls when Quote Callouts are enabled

[!tip]
For quick writing, use the toolbar or Rich Text editor.

For structured posts, wiki pages, guides, bug reports, templates, and examples, use Markdown mode when possible.

Useful Composer Controls

Tool Best used for
Toolbar buttons Bold, italic, links, quotes, uploads, lists, tables, details, and other common formatting
Actions/options menu Extra composer tools that may not fit in the main toolbar
Keyboard shortcuts Fast formatting without leaving the keyboard
Rich Text mode Visual writing and quick replies
Markdown mode Precise structure, templates, code blocks, callouts, and reusable formatting
Callout controls Changing callout type, title, folding, and layout when enabled

[!note]
Some toolbar buttons, menu items, and shortcuts may vary depending on browser, device, editor mode, theme components, and forum configuration.

If a shortcut does not work here, do not document it as a confirmed shortcut.

Mentions

You can use mentions to help your topics or chats have rich context

Code Type Render
#official channel mention Official
#official::tag tag mention official
/Cellular custom Gaea node reference to docs /cellular

[!example]Back to Contents

20. Keyboard-Key Styling with kbd

Use <kbd> when showing keyboard shortcuts.

Markdown / HTML

<kbd>Ctrl</kbd> + <kbd>Q</kbd>

Result

Ctrl + Q

Use this for:

  • keyboard shortcuts
  • composer shortcuts
  • Gaea shortcuts
  • browser shortcuts
  • clear step-by-step instructions

Examples:

For Forum Rich Editor Composer

Press Ctrl + Q to insert an empty callout.

Press Ctrl + K to add or edit a link.

Press Ctrl + B for bold text.

For Gaea

Press Ctrl + B to open Build Options

Press Ctrl + G to group selected nodes.

Press Ctrl + shift + LMB dragging on the graph to shift nodes on the right the right.

[!tip]
Use <kbd> for keyboard keys, not for normal buttons in the Gaea UI.

For interface buttons, write the button name in bold instead.

Example:

Click Send Online in Gaea Diagnostics.

[!example]Back to Contents

21. Callouts

Callouts make important information stand out.

Fast Callout Shortcut

Use this shortcut in the composer:

Ctrl + Q

Rendered as:

Ctrl + Q

Basic Callout

Markdown:

> [!tip]
> Use quotes in search when looking for an exact phrase.

Result:

[!tip]
Use quotes in search when looking for an exact phrase.

Callout with Custom Title

Markdown:

> [!warning] Before posting a bug report
> Search first to check whether the issue already has a topic.

Result:

[!warning] Before posting a bug report
Search first to check whether the issue already has a topic.

Folded Callout: Closed by Default

Markdown:

> [!example]- Click to expand examples
> This content starts hidden.
>
> Use this for longer examples, advanced notes, or optional detail.

Result:

[!example]- Click to expand examples
This content starts hidden.

Use this for longer examples, advanced notes, or optional detail.

Folded Callout: Open by Default

Markdown:

> [!todo]+ My expanded checklist
> * [x] Search existing topics
> * [ ] Add screenshots
> * [ ] Include Gaea version
> * [ ] Link relevant docs

Result:

[!todo]+ My expanded checklist

  • Search existing topics
  • Add screenshots
  • Include Gaea version
  • Link relevant docs

Useful Callout Types

Type Best used for
[!note] General notes
[!abstract] Summaries, TLDRs, section overviews
[!info] Neutral explanations
[!todo] Checklists and action lists
[!tip] Helpful advice
[!success] Good examples, solved patterns, recommended behaviour
[!question] FAQ-style entries
[!warning] Common mistakes, things to check first
[!failure] Missing, failed, or not-working examples
[!danger] Serious warnings or sensitive information
[!bug] Known issues, reproducible problems, temporary limitations
[!example] Demonstrations and before/after examples
[!quote] Quoted or cited material

Good Example vs Weak Example Using Callouts

Markdown:

> [!summary] Strong topic title
> `Gaea 2.3 crash when baking Cellular node in tiled build`
>
> This includes the version, node, action, and problem.

> [!warning] Weak topic title
> `Gaea broken`
>
> This is hard to search, hard to diagnose, and not useful for future readers.

Result:

[!success] Strong topic title
Gaea 2.3 crash when baking Cellular node in tiled build

This includes the version, node, action, and problem.

[!note] Weak topic title
Gaea broken

This is hard to search, hard to diagnose, and not useful for future readers.

[!example]Back to Contents

22. Dropdowns and Foldouts

Dropdowns are useful when something is helpful but too long to show by default.

Use them for:

  • templates
  • long examples
  • logs
  • advanced notes
  • before/after breakdowns
  • troubleshooting steps
  • admin notes
  • tables that would make the main post too long

Basic Dropdown

Markdown:

[details="Click to expand"]
Hidden content goes here.
[/details]

Result:

Click to expand

Hidden content goes here.

Dropdown Containing a Table

Markdown:

[details="List"]
| Setting | Description |
|----|----|
| **callouts** | Define the callouts. |
| **callout_fallback_type** | Default callout type when the specified type is not found. |
| **callout_background_opacity** | Global background opacity for callouts. |
| **callout_title_font_weight** | Global font weight for callout titles. |
[/details]

Result:

List
Setting Description
callouts Define the callouts.
callout_fallback_type Default callout type when the specified type is not found.
callout_background_opacity Global background opacity for callouts.
callout_title_font_weight Global font weight for callout titles.

[!warning]
Do not paste the rendered HTML from a Discourse post unless you know exactly why you need it.

Use the source syntax instead:

[details="Title"] ... [/details]

Dropdown Containing a Template

Markdown:

[details="Copy/paste bug report template"]
~~~text
## Summary

## Gaea version

## Diagnostics / Watson receipt code

## Relevant node, tool, graph area, or workflow

## What I expected

## What happened instead

## Steps to reproduce

1.
2.
3.

## Evidence

## What I already tried
~~~
[/details]

Result:

Copy/paste bug report template 
## Summary

## Gaea version

## Diagnostics / Watson receipt code

## Relevant node, tool, graph area, or workflow

## What I expected

## What happened instead

## Steps to reproduce

1.
2.
3.

## Evidence

## What I already tried

[!example]Back to Contents

23. Tables

Tables are useful when comparing two ways of writing the same thing.

Markdown:

| Less useful | More useful |
|----|----|
| Help please | Gaea 2.3 crash when baking Cellular node in tiled build |
| It broke | Expected X, got Y, steps attached |
| How do I make this better? | How can I reduce terracing after Erosion before Unreal export? |

Result:

Less useful More useful
Help please Gaea 2.3 crash when baking Cellular node in tiled build
It broke Expected X, got Y, steps attached
How do I make this better? How can I reduce terracing after Erosion before Unreal export?

[!tip]
Tables work best for short comparisons.

If the explanation gets long, use callouts or dropdowns instead.

You can insert tables from the composer in the (+) for better writing flow.

[!example]Back to Contents

24. Checklists and To-Do Lists

Checklists are useful for guides, bug reports, feedback posts, and wiki maintenance.

Markdown:

* [x] Search existing topics
* [x] Add Gaea version
* [ ] Add screenshots
* [ ] Link related docs
* [ ] Mark solution if solved

Result:

  • Search existing topics
  • Add Gaea version
  • Add screenshots
  • Link related docs
  • Mark solution if solved

[!tip]
Checklists can be updated by those with editing permissions on that topic or

Checklist Inside a Callout thst can expand and colllapse

Markdown:

> [!todo]+ Before posting a bug report
> * [x] Search existing topics
> * [ ] Include exact Gaea version
> * [ ] Add reproduction steps
> * [ ] Add screenshots or files
> * [ ] Remove private information

Result:

[!todo]+ Before posting a bug report

  • Search existing topics
  • Include exact Gaea version
  • Add reproduction steps
  • Add screenshots or files
  • Remove private information

[!example]Back to Contents

25. Code Blocks and Inline Code

Use code blocks when exact text matters.

Good for:

  • logs
  • templates
  • file paths
  • search examples
  • commands
  • node lists
  • settings
  • copy/paste examples

Markdown:

~~~text
"Gaea 3" order:latest
gaea2unreal categories:using-gaea,learning order:latest
udim with:images
in:wiki community

Result:

~~~text
"Gaea 3" order:latest
gaea2unreal categories:using-gaea,learning order:latest
udim with:images
in:wiki community

Use inline code for exact words, node names, settings, paths, and short values.

Markdown:

Use `Cellular`, `Height Remap`, `tiled build`, or `/cellular` when naming the exact thing.

Result:

Use Cellular, Height Remap, tiled build, or /cellular when naming the exact thing.

[!example]Back to Contents

26. Image Grids, Carousels, and Lightbox Images

Use the right image layout for the job.

Layout Best for
Normal image grid Several screenshots shown compactly
Carousel / scrollable image block Step-by-step image sequences if enabled
Normal uploaded images with lightbox Images that need close inspection or strict ordering

[!example]Back to Contents

Image Layout Option 1: Normal Image Grid

Use [grid] when several screenshots explain one issue or workflow.

Markdown:

[grid]
![graph overview](upload://...)
![node settings](upload://...)
![viewport result](upload://...)
![export result](upload://...)
[/grid]

image
image1920Ă—1165 331 KB

image
image1670Ă—626 59.6 KB

Best for:

  • graph overview
  • node settings
  • viewport result
  • export result
  • before/after comparisons
  • bug report evidence

[!note]
Replace upload://... with the actual image links inserted by the forum after uploading images.

[!warning]
Image grids may reorder images to balance the layout.

If order matters, number your captions:

  • 1 - graph overview
  • 2 - node settings
  • 3 - viewport result
  • 4 - export result

Image Layout Option 2: Carousel / Scrollable Image Block

Some posts may support a carousel-style image block where readers can move left and right through images.

Markdown:

[grid mode=carousel]
![image](upload://aF8dUQO5rLlhxu8UC8PX03rBOqL.jpeg)
![image](upload://iAH2GsRKeks8wif6RjoSJ3bD4z5.png)

[/grid]

image
image1920Ă—1165 331 KB

image
image1670Ă—626 59.6 KB

Best for:

  • step-by-step visual workflows
  • compact tutorials
  • before / during / after breakdowns
  • node setting comparisons
  • image-heavy examples that should not make the post too long

Image Layout Option 3: Normal Images and Lightbox

Sometimes the best option is to upload images normally with crtl + v or drag and drop.

Users can usually click or tap an image to view it larger. If several images are in the post, the image viewer may allow moving between them.

Best for:

  • images that need close inspection
  • ordered screenshots
  • single important result images
  • detailed UI screenshots
  • cases where grid layout makes images too small

[!example]Back to Contents

27. Node > Documentation Custom Shortcut

There is a custom /{nodeName} formula that allows users to post in both chat and topics and node name and it creates a direct node reference link to the Gaea docs.

Example:

/cellular

/cellular

Use node shortcuts for:

  • node-specific help
  • tutorials
  • graph breakdowns
  • bug reports
  • workflow examples
  • feedback about a specific node

[!example]Back to Contents

4 Likes