Website

Definitely, that would be great.

Under http://theforeman.org/manuals/1.10/index.html#4.4.8OSSpecificNotes would be best I think. We already have notes for FreeBSD and SLES, so adding a Windows section would make sense.

To add that, you'd edit manuals/1.10/index.md to add the section and then create _includes/manuals/1.10/4.4.8.3_prov_windows.md with the content. Note that 1.10 is the actively developed manual, but you could equally copy it back to 1.9 once done if you wished.

I think 1.10 is a good start..

I suppose screenshots go there?

static/images/screenshots

Are there any style guides you want me to consider?
Is there a maximum number of sub heading levels?

Yes, that looks right.

We don't have any style guide unfortunately, and the manual is written by a number of people with varying English skills. I'd just suggest sticking to a third person style.

Only about four levels of subheadings are numbered automatically. You'll find beyond five that the levels are difficult to tell apart, so avoid having the reader distinguish between say a level five or level six heading.

In the doc, I do reference my own project witch is needed to create installation media.

Basically there are two parts. I'd suggest:

- Leave out the part on how to create the media (and reference to the external project to create them?) thus only describing on how to get the foreman part working with the WAIK templates (I'll try to get them in community templates ;)

- Or, keep the whole part?
I like the fist better, since this offers a clear break and the docs would get quite large.

What do you think?

For the record: Opened PR209 on commuity-templates

[1] https://github.com/theforeman/community-templates/pull/209

I don't know the details, but yes, I'd generally agree the docs shouldn't go into a lot of detail about how to create the images. Ideally you could reference external docs from your project if that's possible, or consider putting it on the wiki if it's not up to the same standard as the main docs.