The existing repo you have can be used for the docs if you'd prefer.

So you want the Workstation WG to maintain its own separate repository for documentation on the new docs website? And the only initial content would be the third-party repositories policy? That doesn't sound very encouraging.

Why would this be better handled by us than by the people working on the docs website?

@catanzaro my understanding is that this is for policy documentation set and written by this working group, not user documentation which is open to all to contribute too but which lives in a different repository.

We have this page on docs.fp.o for technical teams:
https://docs.fedoraproject.org/en-US/fesco/teams/

And this one for Modularity, as an example:
https://docs.fedoraproject.org/en-US/modularity/

I think using another subsite like that would induce less cognitive load, esp. on less familiar contributors.

Also @pbokoc @asamalik @ryanlerch -- let me know if that idea is way out of whack with your docs strategy.

If for the working group to document processes, policies, and similar topics, I would do what @pfrields suggested. That would fit nicely.

In the WG meeting today, @otaylor sugges-ted we could have a 'fedora-docs/workstation' or 'fedora-workstation/docs' say.

I can't find any specific action for me here, but let me at least say I'm happy to help.

You can use any pagure repository you like, the documentation can be in the root of the repository, or in a subdirectory in case there is other content also.

There is a template with the structure: https://pagure.io/fedora-docs/template

Please let me know how can I help.

Agreed: use https://pagure.io/fedora-workstation repo to store Workstation WG docs and have them included in overall docs.fp.o site (+1: 6, 0: 0, -1: 0)

Excellent! If you want to have the docs sources in a sub-directory, have a look at the CommOps repo — they have it like that: https://pagure.io/fedora-commops