Time Nick Message 15:37 MTDiscord @luatic big giant poke on https://github.com/luanti-org/docs.luanti.org/pull/343 16:16 MTDiscord merged 16:58 MTDiscord @rollerozxa thoughts on if it would be worth building/pulling lua_api.md (https://api.luanti.org/) in its nice rendered/broke up form into docs project? that does however mean the question of what to do with orginal minetest docs stuff 16:59 MTDiscord (context https://github.com/luanti-org/docs.luanti.org/commit/ce704eebb4d086dfdc09104ab594949db164ecb9 disclaiming lua_api.md) 17:01 MTDiscord mostly since users have been reading up on our documentation than showing up here asking more, etc 17:01 MTDiscord not sure. yes, I suppose? 17:04 MTDiscord I would like to see the nice documentation we wrote for minetest_docs to not just disappear though. but don't really know what to do since lua_api.md remains the canonical reference 17:04 MTDiscord i mean, could try and polly patch over specific methods, but...... 17:06 MTDiscord ideally we would try to push to split up lua_api.md in luanti docs and freshen it up with proper links to different sections, admonitions, etc... but that would be a big thing to push for and it's not something I personally find worth it enough 17:07 MTDiscord (always exists trying to get it merged into the engine, but i dont really have the energy to deal with that and/or wait 4 years) 17:07 MTDiscord yeah 17:07 MTDiscord let's also see what Mark is cooking 17:07 MTDiscord because that is really where we want to go 17:07 MTDiscord the web fetch short code exists mainly so i didnt have to deal with engine stupidity 😛 17:07 MTDiscord proper interlinked documentation with types and everything 17:08 MTDiscord ooo 17:08 MTDiscord and i think it might be surprisingly feasible to let a LLM rewrite lua_api.md in such a format to get us 95% there 17:08 MTDiscord sure, but i have as much faith in that as sscsm, new gui framework, etc. if it succeds would be very happy, but also in short term it shouldnt block progress if we can do reasonable things 17:10 MTDiscord I've been away from this docs project for a long time now, but I've done some contributions to SDL since then and fallen in love with their way of doing documentation 17:10 MTDiscord which is? 17:11 MTDiscord the wiki pages are populated by and synced from their C headers in the SDL repo, while wiki editors can add additional sections that stay on the wiki side. all of it syncs up nicely both ways and there is a web interface that allows you to edit the wiki like you'd expect while it creates PRs on the wiki repo on github in the backend. then they have README docs files for various things that exist in the SDL repo while also being 17:11 MTDiscord synced to the wiki so they have a permalink outside of github 17:12 MTDiscord interesting. works nicely if you don't have to wait 4 years i assume 17:14 MTDiscord yup. in general a very easy and accessible project to contribute to and feel nice about it. probably caused by both maintainers (sam lantinga and ryan gordon) being AFAIK paid to work on it... 17:15 MTDiscord switching gears to #contentdb stuff, current contentdb page is under about. not sure it makes sense to put a faq under that (and maybe cdbs other documentation) 17:16 MTDiscord then again we do have history with two rando things under it 17:16 MTDiscord which really is more of an arguement against than anything 17:17 MTDiscord c55's page is a very important part of the docs 8) 17:17 MTDiscord "(no longer online)", "(no longer online)", "(no longer online)", "(no longer online)", oh well... 17:18 MTDiscord it makes sense for cdb to be headlined in about, but then again with more docs, it would make sense to be under for creators 17:18 MTDiscord i mean, could....... have it in both places and rel canocial to the other, but seems subpar 17:19 MTDiscord not to mention the about would have to link to the other