The RH and IBM style guides contain thousands of recommendations to help brand, style, and improve technical communication. Not all of the guidelines will work (or be welcomed) in the open-source community project.

As a team of RH writers contributing to the upstream docs, we need to be consistent in our approach. 

As a Quarkus docs team writer switching from the downstream docs to the upstream docs, I need clear guidance as to which bits of our style guides I should apply as a priority to my content development in the upstream community.

This task is done when

• All writers in the Quarkus docs team have identified the top style areas that we could add value to the community docs.
  • (we can use the security guide as a starting point to help us to prioritise which style guide items would add the most value.)
• The writers have discussed the top 5 style areas with our CS, DPM, and the Quarkus Community doc leads and agreed on the items.

This list will feed into the work to define a Quarkus Community docs style guide.