It makes sense to share the documentation too. In future, other products may join the party. The business rules followed by the back-end process and the UI experience are therefore the same in both Confluence and JIRA. The libraries and UI plugin are currently used in two separate products, Confluence and JIRA. The user directory management framework itself consists of a set of back-end libraries and a user interface plugin. Why content reuse makes sense for this documentation A directory can be an internal directory, with data stored on the product database, or an external LDAP directory like Active Directory, or even another application that manages the user information and directory connections. Using the software, administrators can connect various types of user directory to their application, and manage the directory connections. A user directory is a place where you store information about users and groups. The documentation describes a software framework for managing user directories. The chunks are used in the Confluence administration guide and the JIRA administration guide. The reusable chunks of documentation are in the User Management (USERMAN) space on our documentation wiki. So I thought you may like to read about it. Since we do all our documentation on a wiki, this was an interesting and rewarding exercise. When designing the documentation, one of the primary goals was efficient and effective content reuse. Recently I finished developing the documentation for a new user directory management framework that’s incorporated into two of our products.

Sequence diagram online giffy