Have something to say?
Collapsible Groups
Allow groups to collapse their topology and have them appear as one component. To avoid recreating SvelteFlow edges just for visual representation, another mechanism should be followed, such as: Reset relative coordinates of all nested components, so that they overlay on each other and make them invisible. Then all inter-group connections get terminated on a single [x,y] coordinate. A collapsed group should conditionally show a visual representation that it has been collapsed, such as cloud or box or similar. Collapse controls should be simple = collapse & open (what is the right word for the opposite?).
Agentic AI Support
Plug the Enfors model to an AI Agent to be able to create diagrams by chatting with a bot.
Keyboard Navigation
Implement keyboard shortcuts so that Enfors can be used completely without a pointing device. This will match the philosophy (no drag and drop, fast).
Overlay Support
Enfors should be able to model common overlay networks such as SD-WAN, EVPN, basic tunnels, etc. Depends on Logical Topology Support.
Logical Topology
Currently, only the physical topology is supported. The scene should support toggling between physical and logical topologies. In physical topology view, users can add and remove links. In logical topology view, users can add and remove networks. Pure Layer 2 components, such as Layer 2 switches, are not displayed in the logical view.
Optional Diagram Frame
Create an optional frame outside the diagram that includes: Author, Role, Company, Client Name, Timestamp Legend (Connection Colors) — dynamic based on what is being used
Blueprint Skeleton
Ensure that at the root level, only three types of layers are supported: Central locations Connectivity Other locations Allow central locations to be vertically flipped (or implement sort of abstraction).
Link Labels
Allow labeling links, similarly to coloring groups. Users could use colors to differentiate different kind of connections from each other such as speeds, media types, etc. These should be kept separate from group colors as they target links and not groups. Such an approach will allow managing link colors (public, shared, and private) the same way as other entities.
Team Support
Implement a team support that helps multiple accounts share custom components, blueprints, flows, colors, etc. Each entity can be either private (visible for creator) or shared (visible for team members). Team administrators should be able to optionally disable using generic entities or creating new ones (such as components, blueprints, colors) and provide custom sets for consistency across the whole team.