Add version navigation system for multi-version documentation (2.13-4.0+)

[Copilot]

Documentation covers Dynamo 2.13-4.0+ but lacks version guidance for users visiting from different Dynamo versions. Key differences include .NET runtime changes (4.8→8→10), Python engine defaults (IronPython2→PythonNet3), and package compatibility breaks.

Changes

Core Reference Documents

• VERSION_GUIDE.md: Version matrix, migration paths, runtime differences, host integration table
• CONTRIBUTING_VERSION_GUIDE.md: Maintainer guidelines for marking version-specific content
• IMPLEMENTATION_SUMMARY.md: Technical implementation details

Version Indicators Added

Using GitBook native hint syntax at strategic decision points:

• Entry points: Homepage, navigation, introduction (3 files)
• Package management: Installation, compatibility warnings (2 files)
• Developer guides: Migration guides with version badges for 2.x/3.x/4.x (4 files)
• Python documentation: Engine version differences (IronPython2 vs PythonNet3)
• Setup & host integration: Version-specific installation notes

Example

{% hint style="warning" %}
**Package Compatibility**: Packages built for different Dynamo versions may not be compatible due to runtime changes (.NET 4.8 → .NET 8 → .NET 10). Check for version-specific builds.
{% endhint %}

Approach

Unified documentation tree with inline version markers rather than separate version branches. Minimizes maintenance overhead while providing clear version context at decision points.

Stats

• 17 files modified (3 new, 14 updated)
• 344 lines added
• 11 cross-references to central version guide

Original prompt

This is the learning material repo for Dynamo Visual Programming, which deployed to Gitbook runtime. However all the markdown files in this repo is a mix of content reflecting facts for the range of Dynamo versions from v2.13.0 to v4.0.0 (latest). Please suggest changes to better organize this repo considering currently users are going to visit a single Gitbook site entry from varies Dynamo versions.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.