On 7/8/15 7:41 AM, Martin Preisler wrote:
I wrote a small blog post about a new feature in SSG 0.1.24 -
building one HTML guide for each profile we ship and providing
a convenient switcher.

http://martin.preisler.me/2015/07/scap-security-guide-now-has-an-html-guide-for-each-profile/

It includes a screenshot and a live demo :-) Feedback appreciated.

From the posting:

We plan to install these guides in downstream packages (e.g. Fedora). Instead of bundling them with the main package we will create a subpackage -doc with the guides and other optional documentation material.


That means we have:
- openscap-scanner
- scap-security-guide
- scap-security-guide-docs

Having multiple naming schemes is a bit confusing, especially for new users. Is it time to repackage SSG as openscap-content?

e.g
openscap-scanner
openscap-workbench
openscap-content
openscap-content-docs