docs: Add MeshDisplay and Internals category to table of contents#2
docs: Add MeshDisplay and Internals category to table of contents#2
Conversation
…to table of contents Co-authored-by: Omena0 <82773737+Omena0@users.noreply.github.com>
Omena0
left a comment
There was a problem hiding this comment.
the other internals werent added to the internals category, see the sidebar in doc/build.py
Co-authored-by: Omena0 <82773737+Omena0@users.noreply.github.com>
Added all internals from |
There was a problem hiding this comment.
Pull request overview
This PR completes the documentation index by adding the missing MeshDisplay entry to the Display Entities section and creating a new Internals category with comprehensive coverage of bridge architecture and implementation details.
Changes:
- Added
MeshDisplayentry to the Display Entities section with description "3D triangle mesh rendering" - Added new Internals section with six pages covering bridge architecture, events, execution, serialization, lifecycle, and debugging
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | [BlockDisplay](blockdisplay.md) | Block display entity | | ||
| | [ItemDisplay](itemdisplay.md) | Item display entity | | ||
| | [ImageDisplay](imagedisplay.md) | Pixel art display | | ||
| | [MeshDisplay](meshdisplay.md) | 3D triangle mesh rendering | |
There was a problem hiding this comment.
The MeshDisplay entry is being added to the index table of contents, but it's missing from the SIDEBAR definition in docs/build.py (lines 81-87). This inconsistency means the MeshDisplay page will appear in the home page TOC but not in the navigation sidebar. Consider adding ("meshdisplay", "MeshDisplay") to the "Display Entities" section in docs/build.py to maintain consistency between the two navigation systems.
| | [MeshDisplay](meshdisplay.md) | 3D triangle mesh rendering | |
The docs index was missing
MeshDisplayfrom the Display Entities section and had no entries for the internals pages.Changes
MeshDisplay(3D triangle mesh rendering) entrydocs/build.py: Bridge, Events, Execution, Serialization, Lifecycle, and Debugging💡 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.