fork/Graphite
1
0
Fork 0
mirror of https://github.com/GraphiteEditor/Graphite.git synced 2026-10-05 10:18:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update links from graphite.rs to graphite.art

Browse Source
This commit is contained in:
Keavon Chambers
2025-12-06 18:10:27 -08:00
parent a5cf62a90b
commit fb0fab0622
100 changed files with 575 additions and 576 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/content/volunteer/guide/graphene/networks-and-nodes.md
+1 -1
View File
@@ -13,7 +13,7 @@ Any (sub)graph can import/export data from/to the outside world. For example, a
In the Graphite editor UI, here is an example graph of artwork that imports no data but exports its content to the canvas:
<img src="https://static.graphite.rs/content/features/mockup-node-graph.avif" onerror="this.onerror = null; this.src = this.src.replace('.avif', '.png')" alt="Node graph UI mockup" />
<img src="https://static.graphite.art/content/features/mockup-node-graph.avif" onerror="this.onerror = null; this.src = this.src.replace('.avif', '.png')" alt="Node graph UI mockup" />
The graph shown above represents the full artwork, meaning it's the root-level graph in its document. But there is nothing special about that graph compared to any subgraph. To avoid the confusion of calling it a graph or subgraph which comes with implications about user-facing concepts in the context of a document, we will use the less-ambiguous term **network** in the context of Graphene's internal concepts and codebase.