Add provider and development relationship modeling
This commit is contained in:
@@ -19,6 +19,9 @@ The initial landscape contains Website, API, ERP, CRM and Email Platform plus tw
|
||||
|
||||
- Drag and rearrange systems on the dark LiteGraph canvas.
|
||||
- Edit or add systems, connections, scenario steps and parallel branches.
|
||||
- Group systems in explicit nested environment containers such as Azure → Subscription → Resource Group. Containers can be resized, moved with their contents, collapsed to summary nodes, and persisted independently of provider metadata.
|
||||
- Classify systems with Application, SaaS Service, Cloud Service, Development Tool and Data Store categories, plus independent tags such as Production, Test and Customer Data.
|
||||
- Use typed Data Flow, Deployment, Dependency and Source Repository relationships. Development playback includes the simulated Bitbucket commit → Azure DevOps build → website deployment journey.
|
||||
- Place reusable Website, CRM, ERP, Email Platform, Analytics and API presets, selecting only the capabilities needed for each instance.
|
||||
- Inspect labelled capability ports and fictional action payloads, expand node actions, and save customised systems as private browser-local presets.
|
||||
- Build reusable custom systems with form-based action, output and endpoint definitions. Actions support button, incoming request/event and simulated schedule triggers; outputs can run in parallel, and endpoints support multiple delayed example responses that may trigger actions.
|
||||
|
||||
Reference in New Issue
Block a user