<html><head></head><body><div>On Mon, 2023-02-27 at 08:32 -0800, Troy Dawson wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div>Speaks a someone who recently started a SIG, it's confusing having half the documentation in a wiki</div><div><a href="https://wiki.centos.org/SpecialInterestGroup">https://wiki.centos.org/SpecialInterestGroup</a></div><div><a href="https://wiki.centos.org/SpecialInterestGroup/AltImages">https://wiki.centos.org/SpecialInterestGroup/AltImages</a></div><div><br></div><div>and half the documentation in a different place</div><div><a href="https://sigs.centos.org/">https://sigs.centos.org/</a></div><div><a href="https://sigs.centos.org/altimages/">https://sigs.centos.org/altimages/</a></div><div><br></div><div>I've had a really hard time with my documentation because each time I talk to someone they point to a different place, and I have to literally duplicate what I did in two different places.</div><div>My vote. Drop the wiki entirely in a controlled manner.</div></div></div></blockquote><div><br></div><div>This definitely came up in our conversations. I have a data file that I use to keep track of SIGs. What I'd like to do is populate sigs.centos.org with info about every SIG from that data file. That ensures consistency, and it's easy to audit and keep up to date. Any further info SIGs want to provide should be done with the mkdocs approach currently in use on sigs.centos.org.</div><div><br></div><div>--</div><div>Shaun</div><div><br></div><div><br></div><div><span></span></div></body></html>