SOLVED
Navigation included
Forge treats navigation as a first-class object, managed the same way as content. Your agent can create, update, and remove navigation items through the same access rules that govern content.
Get started
No dashboard required.
Your AI handles publishing through a structured API. Your team stays in the tools they already use.
Full control, zero risk.
Role-based access means your AI can only do what you allow. Draft content never leaks.
Live in minutes.
Connect once. From that point, a conversation is all it takes to publish.
Navigation is often the part that ends up getting hardcoded. A developer writes it once, it works, and nobody touches it until something breaks or the structure changes. When that happens, it is a code change -- not a content change.
Forge treats navigation as a first-class object, managed the same way as content.
Managed, not hardcoded
Your navigation structure lives in the same system as your content. You update it without a code deployment -- no hardcoded menus, no recompile. Your AI agent can manage it -- create items, update labels, reorder, remove. The same access rules apply: what a token is allowed to do with content, it is allowed to do with navigation.
Why this matters when you use agents
An AI agent that can publish content but cannot update navigation has an incomplete picture of your site. If your agent is managing a content section that needs a corresponding navigation entry, that should be one operation -- not two separate systems.
When navigation is a first-class object, your agent can keep structure and content in sync without you managing the gap between them.
What stays in code
Not everything has to be dynamic. If you want parts of your navigation fixed -- always present, not manageable by your agent -- that is an option too. Forge supports both modes, and you choose per item.
Ready to put your AI to work?
Forge is open source and self-hosted. Get started in minutes.