To that end, we're open-sourcing a project we built called markdown-to-confluence which is able to mirror posts we write in Journal (or any Markdown posts, for that matter) to an upstream Confluence instance. However, we feel it's important to make our findings available to the wider company. This works fine for many use cases, but it didn't fit the requirements we needed to take daily notes without breaking from our workflow. However, while Journal opens the door for us as a Lab to communicate our findings more regularly and effectively within the team, it also has the potential to introduce a serious problem with any research group: becoming a silo of information.įor background, most of Duo uses Confluence for sharing information. Since adopting it across our team, we've seen the quality and quantity of our research notes go up. We made Journal because we recognized that writing and sharing research notes is a critical part of the research process.

IntroductionĪ couple of months ago, we open-sourced Journal, the system we use here in Duo Labs to share research notes within the team.

How to use confluence rest api