# ignition.designer.model.DesignerContext

**URL:** <https://forum.inductiveautomation.com/t/ignition-designer-model-designercontext/6206>\
**Category:** Module Development\
**Created:** [April 11, 2013, 12:05pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-model-designercontext/6206 "2013-04-11T12:05:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [April 25, 2013, 9:43pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-model-designercontext/6206/2 "2013-04-25T21:43:10Z")

</div>

Hi there. Bad news & good news.

The bad news is that you’re doing it all wrong.

The good news is that the right way to do it is pretty easy. In your Designer module hook, you want to add a new node to the nav tree.

1. Create your workspace implementation, and register it using context.registerResourceWorkspace()
2. Make your node by creating a subclass of AbstractNavTreeNode. Make sure to override getWorkspaceName() to return the name of your workspace (this is what will automatically switch to your workspace when the node is selected)
3. Add your node using context.getProjectBrowserRoot().addChild()

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-designer-model-designercontext/6206)._