-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable wiki on fteqw repo #224
Comments
FTEQW has its very own section on QuakeWiki, and people can contribute details to extensions/builtins on this page here |
I feel it would be better to have the documentation/tutorials with the project/code. Feel free to close if you prefer people use QuakeWiki. |
As for my two cents on the issue: I agree the documentation situation with FTE has never been great and really scattered. @Shpoike had a wiki on triptohell.info (FTE's old site), there is the "unofficial" yet semi-official FTE section on quakewiki.org, @eukara has some great FTEQCC stuff documented on his personal site, and we have some basic (WIP) documentation we will soon be committing inside the repo. I think including some documentation inside the repo is going to be a good step, and while the idea of a git based wiki is appealing we also mirror and host on a Gitea and I don't know how cross compatible that is with Github's wiki system. I also would like to help out quakewiki.org, as I think it is a great open alternative to Fandom, but perhaps it should just be a companion wiki. Overall there is just a lot to maintain, there's a lot of options, and we sadly haven't had the time for it. I'd like to hear @Shpoike thoughts as well as what the community would find the most sensible approach. |
there's some technical stuff in fte's specs/ dir and noone's ever asked me about it so I don't think anyone really cares. I still need to kill/disable the wiki on qss's repo. :s |
Enabling the wiki on the repo would allow us to provide more documentation for FTE QC extensions and functions, beyond the one line comments dumped to the defs file.
The text was updated successfully, but these errors were encountered: