Blogging for Red Hat Advanced Cluster Management

      -When you create a blog report issue, keep the issue in the Untriaged pipeline and specify the `ACM Blogs` component. A writer will triage the issue.
      -Give a summary of your blog idea by completing the summary outline at the end of this template.
      -Add the product version label that is applicable to the draft blog.
      -Add your draft blog to the [blog-drafts repository](https://github.com/open-cluster-management/blog-drafts). Post the link to your draft and contact your writer/editor.
      -When your draft is being reviewed, update your pipeline to In Progress. Blog editing can take place in the repository, in the issue comments, or during a live meeting, depending on needs and availability.

Important:

Generally expect at least a 2-week delay between
submitting your reviewed blog and publication. See the Playbook
for more details.

Writing guidance for your blog:

      -Verify that the author's name is added to the blog draft.
      -If you have to link to other blogs, link only to other blogs that are published.
      -Reference the product documentation as a source of truth for specific details.
      -Reference our open community, [open-cluster-management](https://github.com/open-cluster-management), for specific details, as well.
      -Spell out the product name (for example, do not use ACM). For examples of how you should reference the product, see the Official Red Hat product and solution names list.
      -Preview your blog draft to verify indentations and numbers are aligned appropriately. Select the preview tab in GitHub or GitLab.
      -Double-check spelling.
      -Good practice to give credit to others helping with your blog.

Note: Highly suggest that you add borders around your images because it
is hard to see where the content ends and the images begin. It would
increase accessibility and readability.

1. Choose the type of blog update

      [ ] New blog
      [ ] Update to a published blog

2. Link to the blog(s) that require an update
https://www.openshift.com/blog

      -
      -

3. Blog information

      -Title:
      -Blog audience:
      -Blog main idea:
      -Call to action (what can you do with this knowledge after you read the blog)?

During our tool transition, there was no issue created for this blog and fell off of my radar. Creating this blog issue now bc the author has been responsive and still interested in publishing, plus this is great practice for Faisa when she is ready.