Uploaded image for project: 'Quarkus Documentation'
  1. Quarkus Documentation
  2. QDOCS-602

Make upstream security topics visible in PV1

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • Downstream-docs
    • None
    • Publish upstream security topics in PV1
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      To optimize visibility of upstream security topics in PV1, the process involves:

      1. Compiling an extensive security guide list: Identifying a broader range of security guides than initially anticipated.
      2. Curating RHBQ guides: Developing a selection of RHBQ guides to encapsulate related upstream guides, addressing space constraints on the RHBQ landing page.
      3. Incorporating stakeholder feedback: Presenting the guide mapping to the Security SME, Product Manager, and Tech Lead for input, refining the plan based on their feedback.
      4. Automating guide mapping: Implementing a script for efficient guide mapping.
      5. Updating synchronization list: Adjusting the file synchronization list for the /asciidoc folder to match the updated content strategy.
      6. Revising GitLab pipelines: Experimenting with and later revising GitLab pipeline configurations to better suit the project needs.
      7. Establishing PV1 folders: Creating specific PV1 folders for each RHBQ security guide.
      8. Ensuring build and verification: Conducting build and verification for each guide to ensure accuracy and completeness.

              rdlugyhe Rolfe Dlugy-Hegwer
              rdlugyhe Rolfe Dlugy-Hegwer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: