...
ArchNav is a highly versatile platform that supports a wide variety of use cases. However it brings complexity when designing a clickable image, The process requires taking a snapshot of an existing image, converting it to a PNG file (if not already a PNG), using an external tool to draw shapes around objects in the image to generate the needed coordinates and lastly to store the coordinate attributes in a JSON object. This has the potential to be more time-consuming and error-prone when compared to creating OVERLAYS using an SVG editor to create diagrams with embedded links. SVGs with embedded links however has have less versatility than ArchNav has demonstrated.
As a platform ArchNav is not a resource or storage hog since most of its file files are generated dynamically on demand using PHP and Javascript and none of the items linked from an image reside locally.
Documentation residing in the read the docs is always up to date and the most current. The ArchNav will require a separate manual update of the links pointing to the documentation in addition to the current RTD updates whenever there is a new release of ONAP.
>capture need for infra' maintenance → budget ramification beyond this eval,
RECOMMENDATION
- facade design approach.
As is the tool can be supported by people with the right technical skill set, however, to broaden the scope and make it accomodating for controbution contribution from technical and non-technical members of the community, a graphical approach would be ideal,,,,
...