Skip to content

[Enhancement]: add a clear, tight explanation of WFO #17

Description

@eenblam

The core prose describing WFO on the main docs page is quite generic. It would be great to have a clear, tight explanation of what the Orchestrator actually does. (i.e. focus in on modeling the lifecycle of (network) products as a service.)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions