Ewoud Kohl van Wijngaarden

> To use this section, you must have foreman-maintain installed (how do they do that?) For Foreman on EL, you can `yum/dnf install` it. For Debian you can't. The software...

I've revisited this a bit and opened https://github.com/theforeman/foreman-documentation/pull/979 which is certainly not a solution, but a step in the right direction.

I just noticed you had a PR for this that I didn't review, but I greatly appreciate you taking this on.

Today the specific bits live here: https://github.com/theforeman/foreman-documentation/blob/cc8251a173392e7dfb04a379abaffab5c5d48298/guides/common/modules/con_prerequisites-for-bare-metal-provisioning.adoc#L13 Still looks relevant.

This escalated a bit in size and it now removes more lines than it adds. Individual commits explain what's going on.

> * I think it's generally bad practice to set an attribute somewhere throughout the docs and never unset it. If it's relevant for all guides > guides/common/attributes*. If it's...

@asteflova I think shorter, more focused guides are the answer to the "not specific enough" header problem. If you have an (External) Authentication guide then "Using LDAP" is not so...

Short or long headers aren't a problem. Too short or too long is. Question is, what makes it 'too'. You're right that it's very much a case by case thing.

The outline I have written out can be considered a base for an assembly. The steps I had in mind were: * Enhance existing assembly to be complete * Complete...

> This sounds like a networking guide. Networking guide could be an overloaded term, because networking can mean a lot of things. Networking can also mean how you set up...