We've found that Plone folks can't easily find a task that they want to perform because we force them to think of performing the role of Admin, Devops, Developer, and other roles to find the task within that role. This is a silly arbitrary structure because most Plone developers perform all roles, so we might as well lump them all together in a single Develop guide.

In #1768 (comment) there was a discussion about all the guides. However, later discussion in #1875 (comment) overrode that thought, and now we have a clear direction.

In #1902 its purpose is to create content for how to work with the Plone site admin interface. Note that a "Plone site administrator" is clearly defined as someone working with the Plone site admin interface, and not the same as an "Administrator" which never was clearly defined as administering a specific thing.