This is awesome. Thanks for making this happen. Can anyone submit those centos-infra tickets pointing to the documentation or does that need to be done by a SIG member? Thanks, Jack On Wed, Sep 29, 2021 at 6:12 AM Fabian Arrotin <arrfab at centos.org> wrote: > As pre-announced on the centos-devel list in another thread, and also > per Automotive SIG request (https://pagure.io/centos-infra/issue/458) , > we'd like to announce new https://sigs.centos.org virtual host, > rendering SIG documentation (if they want to) > > The system is based on markdown documents, rendered through mkdocs > (https://mkdocs.org) > > How can you request your SIG namespace on it ? > > # prepare a git repository with your .md files and a mkdocs.yml file > (see https://www.mkdocs.org/getting-started/) > # create a centos-infra ticket on https://pagure.io/centos-infra/issues > with : > - sig name and description > - git origin for your project (where your .md files are stored) : it > can be wherever you want, so github, gitlab, pagure.io or even > git.centos.org if you ask for a project to be created there for your SIG > # once created (by ansible), your content will be automatically rendered > and visible under https://sigs.centos.org/<sig_name> (example : > https://sigs.centos.org/hyperscale/ , already "live") > > Once you'll have just accepted PR or pushed commits to your git > repository, it will be picked up, rendered and push to > https://sigs.centos.org vhost. > > Suggestion : if your SIG has such documentation online, it would be good > to just have a pointer in wiki to the new place, (or even move > instructions - if you have some - to the dedicated SIG doc site) > > -- > Fabian Arrotin > The CentOS Project | https://www.centos.org > gpg key: 17F3B7A1 | twitter: @arrfab > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20211001/c22c8268/attachment-0004.html>