naming: say when to name an interface, and that Kathara cannot take one
wiki: say what each notation is for, and point at a topology that uses it
wiki: finish the terminology change, and give every page a way out The substitution left the word in a few places and left Basic-Concepts arguing with its own definition: the callout said a topology is both files, and the page below kept saying "change topology" for editing the DOT file. A reader ends a page believing whatever it said last. - the graph is called the graph where the graph is meant - "topology file" only where a platform is named; the cross-platform places name topo.yaml and spec.yaml instead - Upgrading names netroub, which the CHANGELOG already warns about, as the downstream tool that reads generated files by path - Basic-Concepts and Command-Reference had no outgoing links at all; both now end somewhere, and the class table and param_rule reach the pages that explain them - two links pointed at nothing (a Graphviz-style path, an anchor with a slash in it) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wiki: say topology where a topology is meant, and stop saying scenario scenario is netroub's word - a configuration together with the events that happen in it, defined in its papers and in its own schema, where a scenario is a topology plus events. This documentation had taken it for what a reader writes, which would have left two projects by the same author using one word for two things. What you write - the DOT file and the YAML that configures it - is a topology, which is how this field already speaks: containerlab calls its own file a topology definition and puts the nodes' images and configuration in it. Basic-Concepts and Home say so before the word is used. Where only the graph is meant the pages now say the DOT file, and topology file is left to mean what a platform reads.
wiki: the parts a reader needs that were only in the code What a module may implement and when each hook runs, so that reading a module is possible without reading the framework. What the three platforms differ in, as one table - including the one that catches people, that containerlab and TiNET run a startup command without a shell while Kathara's is a shell script, so a command with && in it works on one and silently does the wrong thing on the others. DOT syntax: xlabel is read on edges and subgraphs, not only on nodes, and why (Graphviz draws label across the picture); a node's label is deliberately not a class. And how a lab spanning machines is drawn. Dropped mountsourcepath, which is documented but never read by anything, and a note promising that legacy FormatStyle field names still work - they were removed, and an unknown key is now an error.
add Template-System
add some contents