Mini Content Journey (RHOSO team)

Reviewers:

• Technical: rhn-engineering-beagles 
• Peer: jamsmith@redhat.com 
• QE: ashtempl 

Is this feature fully supported or technical preview?

• Full support: Documentation will be published on the customer portal

Does the procedural content need to be tested by QE?

• Yes: QE needs to create a doc testing ticket per How-to Jira with the docs team

Does the documentation epic need a release note in addition to the feature?

• No: The engineering feature will have a release note.

What stage of the user journey are you targeting?

• Adopt: Greenfield feature (Early stage customer use)

Who is your target persona?

• RHOSO admin:  Platform Engineer

What type of information does the user need to know in order to use the feature?

Most likely, there will be no changes to the current customer-facing tech preview doc, except to remove the tech preview labels.

Are there any existing upstream or internal resources that the writer can use for planning and drafting the content? Consider the situational context of the existing content. Do a Google search for any possible resources that might help.

• No

Does the content require input from multiple DFGs?

• No: Stories are not required unless the epic needs to be divided to user stories that can be delivered separately (for personal use, consider sub-tasks instead)

Does the content need to be included in any of the following guides?

• Validated architecture (VA) guide: Is the content a part of a VA workflow, such as HCI, NFV, BGP, etc?
• Planning guide: Are there prerequisites or planning decisions to add to the Planning guide? 
• Deployment/Customization guide: Does the feature need to be enabled during the deployment  process, or can it be enabled post-deployment?
• Adoption/minor updates guide: Are there any considerations or impact of this feature on adoption from pre-18 environments or from earlier 18z versions?
• No