CLICK HERE to visit the new NS2 Wiki! Please do not rely on any information here as it may be inaccurate and/or out of date! For help with NS2, hop onto the official Discord server!

Talk:Community Portal

From NS2 community wiki
Jump to: navigation, search

Layout of Lua data

We need to create some form of standard for laying out data within the wiki. User:Deathbob has began to format the pages using prefixes (Example: Lua/Objects, Lua/Objects/Weapon, etc); however, I believe this is not an effective waying of laying out the data.
We should take a page or two (or the whole damn book) from the Garry's Mod Lua wiki. Categories and Templates are effective ways to lay the data and provide means for even the most inexperienced users to contribute to the wiki.
Please discuss here. Deco 07:05, 11 April 2010 (UTC)

I already took a page or two from the Garry's Mod wiki so taking more wouldn't be that bad. One thing I highly disagree with is images for data types. The images are ok for server/client but there was discussion that there is only the server api and no client only api so that may not be needed at all. But this is all moot because this wiki would need extended images for it to work. We also are missing parsers which means no {{#if: }}. I was going to bring this up on the forums because both would be nice to have. I do agree with naming functions as a . of the object/library (A.func). I would highly recommend subpaging, this doesn't really add any editing overhead as every aspect of it will eventually be templated and the template will handle the paths. My biggest concern is naming collisions with the rest of the site, someone could really want a rifle page and we already have it with lua. It also gives at a glance information about what it is when they see the title. Taking the function page will probably be good. Another thing that bugs me about the Garrys mod way is the "GIANT PAGE OF FUNCTIONS." You end up with links to libraries that scroll you down the page but if you click the library name there it takes you to the libraries page. This is an inconsistancy, the only place in my opinion where clicking the library name should not take you to the library page is the TOC. I think we could just as easily have a page that lists libraries and a brief description of the library that links to the library, then have every function page in a category that people can browse.
Main page
Library/Object list with brief description
Function / Hook List with brief description
Function page with full description
Deathbob 15:17, 11 April 2010 (UTC)
Also very library / object has a link to a library / object page which are worthless stubs. I am very much trying to make every page get the biggest bang for the buck. Deathbob 15:19, 11 April 2010 (UTC)
I'll be idling on #ns2wiki if you want to chatDeathbob 21:04, 11 April 2010 (UTC)