Playbooks and how to implement them

For a while now, I have been trying to iron out how to create groups of focused articles, or instructions. In many ways, these would be like small books of how to's, much like I have started for My Book and IPS Customization. After considering this for a while, I have decided to go for a different approach. I call them Playbooks.

As part of the 2022 focus I will look closer at the Atlassian and Development sections, and in those I have 6 planned playbooks defined at the moment: Jira Cloud Playbook, Confluence Cloud Playbook, Invision Community Playbook, HTML Reference Playbook, CSS Reference Playbook and JavaScript Reference Playbook.

As always, I will start slow and expand later. So I plan to take a look at the design I already have for Products and Companies and rebuild that for the display view. The databases already have a list of activities based on bugs and fixes I wanted to make, so it is not really a big change besides what I already had planned.  I will need to dive into some other database templates also however, or rather the database relationship templates.

I was considering having one big database for playbooks, but decided to go for individual ones. One reason is that Pages only have two levels in the navigation widget that does not change as you go deeper in the tree. Another reason is that it is more difficult to make changes to the individual playbooks. This means that there will be a lot of databases over time, but I can live with that.

I am planning this up using Clickup, which I recently started looking at. It is a very nice tool and I will write more about it in the future when I have had some time to play around with it some more.