Description of problem: ECS is often required to publish beta content on access.redhat.com. When a guide is released as beta content, there are several things that need to be changed: The version number has -beta appended to it A beta disclaimer should be added to the guide explaining what the purpose of the beta and stating that the beta is not supported. (Could be a single topic automatically added to the beginning of the guide i.e, topic 21349). If we have a standardized way of generating the beta guides, it could simplify the process and ensure we're delivering a consistent message around the purposes of beta products and the accompanying beta guides.