On 11/12/17 10:22, Thibaut Perrin wrote: > Hello Fabien, > > First, thank you for even trying for what seems to be an impossible task :( > > Quick points : > - if it was decided not to continue, what would happen to the current > wiki ? Dismantled or would it remain as read-only for documentation > purpose ? > - What about Sphinx <http://www.sphinx-doc.org/en/stable/> ? seems to be > frequentely used nowadays > - As you mentioned, a solution of the type of github with pull requests > for documentation updates might be a solution here. > > There is a wiki feature <https://guides.github.com/features/wikis/> on > Github. I don't know to which extend it would fit the needs of the project. > > Hope this helps, > > Thibaut So far there is no decision, reason why I started this thread :) I guess our target would be to convert (and sanitize ?) existing content anyway as we don't want to lose such content. Then either replacing wiki.centos.org with new solution (but trying to keep the same structure so that all the things in cache for search engines and/or articles pointing to wiki can still work) or move to something different and indeed keeping existing wiki.centos.org in Read-Only mode I'd like to avoid Github specifically but having something else that would permit to use ACO (https://acccounts.centos.org) as auth source. I already played with gitea and it works with openid so self-hosted git instance using ACO works fine. (but that's a different thread) We should divide all parts into specific areas. Benefits of using .md means being able to switch to something else even later and not be tied to $yet_another_tool to generate the web part. (just my idea) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ CentOS-docs mailing list CentOS-docs@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos-docs
