I currently have no plans to enable the Discussions module, as I don't think it is that useful. I'm planning to create a new (technically a relaunch) Discord channel for discussions anyways, which I think is far more effective than the Discussions module.
As for the mobile main page, unclassified templates, and non-portable infoboxes, these are my own faults with managing this wiki. I guess you can say I'm somewhat amateur at wiki management; I have no idea how the CSS works, no idea how to change templates, and no idea what my vision of the wiki will be. I had looked over the mobile main page, unclassified templates, and non-portable infoboxes a few times before, but I always did a half-assed job at them. Combined with the fact that I had been having difficulties with my life IRL, I really had not been doing too well with managing the wiki.
I was promoted to bureaucrat at a time when I was just about the only real active editor left on the wiki, and the admins all wanted to retire or had retired. I accepted the bureaucrat position because I thought I would do a good job at it, only to realize after a few years of bumbling that I'm not good at managing wikis.
Thanks for the quick reply, and sorry to hear you're having IRL difficulties! I would be happy to help you with the "backend" management of Wikis and I can certainly give a hand with templates, too. Let me know once the Discord server is made and I'd be happy to join it (if you want me there, that is), for a more direct line of communication. In the meanwhile, feel free to add me on Discord (my ID is The Embraced One#6059) if you'd like to chat with me easier about Wiki stuff.
Hmmm... I wonder if you can offer some help on Infobox templates. As you know, many of our infoboxes are not portable infoboxes. I tried to convert some of them to portable infoboxes, but I haven't been able to convert all the infoboxes into portable infoboxes due to several issues:
Firstly, I just don't know how all the infobox CSS works. I don't really have in mind of a good infobox design myself, so I tried to make a new portable infobox that looked exactly like the old one; this didn't work because I don't know how everything in MediaWiki:Wikia.css works, and my result still looks different from the old infobox. Compare Template:Infobox_faction and Template:Infobox_faction/Draft; I don't feel satisfied with what I have in the draft. I want it to look exactly like the old one, and I just don't know how.
Related the above, I'm afraid to edit the CSS because there is a lot of complex stuff in them, many of which are vital to the function of the wiki. An older, now inactive admin built almost all of the wiki's CSS from the ground up, adding a lot of complex but vital functionalities that I barely understand. I am very scared of editing the CSS at all because I'm certain at least some of our current basic wiki functionalities are built upon these complex code, which I might easily break.
Related to infoboxes, there is this one infobox called Template:Infobox_patch that is completely different from a standard infobox that I'm really not sure if a portable infobox can replicate. Just take a look at it. I didn't dare to touch anything related to it in the CSS.
I don't even know where to start addressing these problems, so I just gave up.
This is very useful, thanks for the list! I'll investigate whether/how it's possible to replicate that infobox style as in the old Infobox_faction, and let you know!
As for the CSS, would you want anything changed there, or is it just that you dont understand what's in it, therefore you dont want to mess with it?
The last infobox you linked cannot be replicated with an actual infobox, but could be replicated using a navbox instead. They are not best practice exactly, but if that's what the Wiki is used to, it should be fine as long as you dont put too many links in it (like it is right now). You can read more about them here .
New Infobox Faction: Looks pretty good so far. The size is just right, though the font size should be smaller.
CSS: I don't have anything I want to change right now (now that I have help with the portable infobox thing), but I do wish that I can have somebody give me a rundown of what is in that CSS page so I can clean it up in the future if I want to.
Update infobox: I'm OK with your suggestion, though I do have to note that this infobox actually appears on mobile devices despite it not using portable infobox markup. I'm not sure if a navbox would appear on mobile devices.
Hi, the infobox should now be correct, let me know what you think.
My team leader had a read through the CSS and removed some deprecated stuff and left comments. Please have a look and let me know if there are nay parts in there that you'd like further elaboration/clarification for.
Navboxes appear on mobile, so I think it'd be safe to change the patch notes infobox into one. I can make a template draft for your review if you'd like.
Hi, Im just checking in to see about the other suggestions, such as the mobile main page improvement, unclassified templates and non-portable infoboxes. Please let me know if you need help in any of these areas.
Hello Wuzh. Since I've inherited the Wiki Manager position from TEO, I'll also be inheriting their leftover work. I was wondering what the status was on the suggestions that were offered. I would be willing to do the work myself if you're not interested. Please let me know, thanks!
Hey Wuzh, thanks for giving me the Trusted User role. I did not expect to see that coming. However, I am just asking, do we need skin families for EACH skin including singular skins that only appear on one weapon? I personally think that could still count as a skin family, but we would have hundreds of pages of singular skin families. Do you have any suggestions for it?
Wait. Also, how am I supposed to put information into the tables for the knife finishes? The first 5 knives (Gut Knife, Bayonet, M9 Bayonet, Karambit, and Flip Knife) with the same finish could be obtained from multiple cases.
I'm sorry. I meant the information table that showed the skin's information. My question is, since some knives come from multiple cases, how am I supposed to put the information in the table? Or should I just not include the info for the knives? Also, for my Neon Kimono and Black Laminate pages, should I just call the families "Kimono" and "Laminate"?
For the knives, since one knife can come from multiple cases, you should include all the cases where the knife appears, and use the "rowspan" format specifier to have the information of one knife span multiple cases.
For example. Here I used rowspan to have one skin cover multiple collections.
As for the names, right now I feel like it is better off if you would split off all of them into their own pages. Each skin family name should be split into their own page. (In fact Isaac should be split from Asiimov.) You can include a See Also section with links to link to other associated skin families.
I still do not understand how the rowspan works. I went on Help:Table on Wikipedia to search how it works, but I still do not get it. Do you have to put the rowspan on the collection and the collection icon inside the columns before the actual collection icons and names?
Hey, Wuzh, sorry for my inactivity on the wiki. However, I now understand how to add images to tables, so I will add both the collection image as well as the name with a link to the page. After I finish my Asiimov page, I want you to see it and tell me what to add/edit. Thank you!
Yes, to indicate which skin is from which case. We're going to have to mix up some different icons, since the R8 Revolver | Fade and the Fade Knives come from cases, as the other Fade skins are from collections.
Hi Wuzh, I just recently noticed a few missing things in the map galleries, especially the Dust 2 Collection. The R8 | Revolver Amber Fade was released for a long time already, but I didn't see it in the gallery section "Collection" until I added it. How often are the skin galleries updated? A couple months ago, I had to add missing skins that were not updated since the Horizon Case in the weapon galleries. If no one assumes responsibility for these pictures, I will try my best to add missing information and items. Also, I am not sure how you like my skin gallery edits. Are you fine with them? Also, in Skins/List, I am planning to reorganize the collections in order of release, rather than alphabetical order, just like the last editor did with the cases and new collections. I will, however put the first skins collections ever released in alphabetical order.
The wiki has been going pretty slow recently, due to the reduced activity from some of the older users. These skin galleries are currently not managed by anyone; though I have been planning for a total rework, I have not been able to go through with it due to IRL difficulties.
Your current edits are... OK I guess. However, these edits would most likely be rendered moot if I go through with my rework plans. My rework plan is quite extensive. It involves creating individual pages for every single skin families in the game, in the same vein as the Liquidpedia CSGO wiki. Meanwhile, all skin collection images are to be deleted from the map galleries, and Skins/List would be reworked so it no longer uses a table format. I would suggest you to hold off editing on Skins/List for now (it's the first part of my rework plans), though the skin gallery edits are fine.
Hey, I can do that for you. Asiimov, Redline, Sand Dune, I am a big guy about skins although I didn't have CSGO early in the day. If you are busy, would you lile me to help you? If you want, I can get a head start at making the skin family pages. I guess I'll just need to include the case/collection it is from, the artist (comunity-made skins), and the description.
Hello, I'm The Embraced One or TEO, and I'm the Fandom Wiki Manager for the Counter-Strike Wiki as well as an admin on Sekiro and the Hollow Knight Wikis in my free time. I'm here to act as a liaison between you and Fandom Staff and help you and your community. If you ever have any questions or issues related to the Wiki, its features (editing, templates, layouts, etc.), or anything else, feel free to reach out to me on my message wall and I will be happy to help out!
Long time no seen! I'm sorry I was focusing on trying to rank up to Lieutenant Rank 21 to get CSGO Prime. However, when I was adding the newer skins to the page P250/Gallery, I noticed that someone accidentally put a picture of a P250| Vino Primo (from the 2018 Inferno Collection) instead of a P250 Facility Draft in the 2018 Nuke Collection. Check these 2 links to distinguish the differences.