wiki functionality
Not planned
I would like to request a Wiki functionality. That could for example be used as a kind of publication portal. This would help to describe the different types of architecture in a more helpful matter than a bunch of views and easier accessible. Links to views could be added to the wiki pages and views added as clickable images as a kind of preview for example. Also direct links to objects and attributes would add value.
This would for example also make it easier to create reference architectures for example.
Of course there are other applications/wiki's that could be used, but having it in BlueDolphin would make it better integrated and for example if there is an update to an object and/or view, the wiki would then be updated automatically ensuring it is always up-to-date. This could apply for all domains: architecture/archimate, bpmn and data.
-
Official comment
Hello all,
Wiki functionality is not on our roadmap.
Thanks,
Team ValueBlue
-
Nice idea Sander van der Linden but you do know a wiki generally does way more than publish images. Maybe it's easier to enable BD to publish all objects and use another application as Wiki, facilitate user interaction there.
How would you feel about the following:
- turning a view into an object with attributes
- makin all objects available through an API
The AMEFF definition already describes how to export objects (including views), there is an API, what's the harm in creating an AMEFF API feed?
Check out the following:
- https://valueblue.zendesk.com/hc/en-us/community/posts/360010253259-Abillity-to-add-Metadata-to-a-View-and-show-it-on-the-view
- https://valueblue.zendesk.com/hc/en-us/community/posts/4409128953362-Share-a-view-as-an-embeded-picture-real-time-change-in-other-applications-such-as-Confluence
- probably other I missed so far
0 -
I think both are different use cases. Of course I know that a wiki does more than pictures, otherwise it would not be of added value. The pictures/views would support the other content of the wiki. The reason why I suggest adding this into BD instead of a separate wiki (of which there are plenty), is due to the relations between all the objects and between the different types of views. I think it will be difficult to have the same kind of dynamic and always having up to date information outside of the platform. Security might be an issue for some customers there. Actually, the links you provided also mention this.
It is not that hard to create an export of an view (either AMEFF or PNG) and put that in an external application. One issue with that is, is that the PNG is static and the AMEFF must be understood by the external application, which is not that common. I don't know if Confluence understands AMEFF, we don't use Confluence.
0
Post is closed for comments.
Comments
3 comments