I know I am not suppose to ask another wiki manager for a different one but I need help. Max Payne Wiki which I just got my admin key got have masssive problem related to the wiki like the infoboxes clour is not changing, categories is not updated, redlinks templates that can't be removed normally and other problems I haven't encountered. Since you are the template expert, could come to thye Max Payne Wiki and see you can solve some of it?
Hi, I would be more than happy to take on the Max Payne Wiki if you would like me to!
One thing that immediately comes to mind, is that a lot of Wiki features are not enabled. I would suggest enabling them in the Wiki Features section in the Admin Panel, or I can enable them for you. These are Message Wall and Europa Infobox theme (this is causing the infobox issue).
Europa infobox means infoboxes use the wiki's theme: "Enable a new look for your infoboxes to fully benefit from your wiki's color theme!", that's the problem you were describing when yoiu said "infobox colour not changing", correct?
As for the Message Walls, they dont affect the infoboxes but since this Wiki you admin already uses Message Walls I figured you might want to update the Wiki's old Talk Pages into Message Walls. Message Walls are more user friendly and make it more likely for contributors to stick around, while Talk Pages can look more confusing and less straightforward to those new to editing. This is why I recommended turning it on.
Could you please clarify what your intention is with changing infobox colours?
"we still have other templates problems to deal with especially the testcases and sandboxes redlinks" - please link the templates in question so I can investigate
" why the infoboxes in Max Payne Wiki have extra bar on the top unlike normal ones?" - i fixed this, it was an issue with the noinclude tags after the infobox code. Let me know if other templates have this and I'll update them!
You see the notices where they have quotes, that the customatzation that I want
Another question, what cause your infobox to not saved, when I create an infobox, it tries to save once but can't and save twice, it loops perpetually. What cause the problem and is there a way to prevent it? I had to edit manually instead through source editor
Actually I have some questions regarding this navbox template, how many variations would you make from it? Considering the current template with its if functions, if might be better to make a new navbox template than rewriting the current one. It'd help to know how many big groups and subgroups you'd want, and whether you want this template to also feature if functions?
After some further investigation into the template, it seems that a navbox like this would require the Lua Module and some pretty complex implementation.
After consulting my team, I've been advised to link you articles on why you should reconsider the choice of using navboxes. One of it is Progressive Design - it's to do with portability, and the other one is about Navigation .
I would suggest you read this and rethink navboxes before we proceed further with this.
Should I use navbox or not? I read the articles and they told me about displaying data. I think it is better to use navbox since there is other wiki that might need to use and maybe help editors to understand navbox better. The articles mentioned tabbers, in what way to use them?
If an article is part of a group of articles, and order doesn't matter, consider whether that navbox group should be a category instead. Categories are easily navigated using Mercury and Mobile Main Pages, and can be linked to in wikitext. They can also hold narrative or data content just like an article, which is seen in Mercury. Context and describing what that group is are more important to readers and search engines alike than a pool of links, as relevance and relationship are key to understanding.
If an article is part of a group, but has an ordered relationship with one or more of them (like a previous / next relationship), those are data fields that can and should be navigated in an infobox.
If an article has a one-to-one relationship with a parallel article (for example, it links to the gallery or some other subpage of the main article), links in the <navigation> tag of a Portable Infobox are ideal.
Tabs used at the top of pages to move through sub-articles and to parallel articles are still common on a lot of communities, but make for a very tricky design pattern. In some cases, the tabs used for navigation will cause a blank page to appear on mobile devices. For most articles, the easier way to link to articles with a specific relationship is in the infobox, as mentioned above.
They are hidden in most cases on the Fandom mobile skin due to usability concerns, as they are on Wikipedia’s mobile skin and apps. Clustering links together in blocks is not finger friendly, and there are historically few good ways to lay these out on small, tall devices like mobile devices. Also, repeating the same exact block of code on multiple articles, particularly on short articles, detracts from their uniqueness and has a negative SEO effect.
Sidebars (sometimes called vertical navboxes) are navboxes similar to infoboxes in layout, and their functions are replicated in the <navigation> tag of Portable Infoboxes. Usage in this manner is a good idea, as it provides mobile-friendly page switching in the “above the fold” area and consistently looks good on small screen devices.
as for the infobox, I said twice already that I need a specific list of data you'd like to display, otherwise I cannot create the template.
With the infobox issue, what is it that you are having trouble with when it comes to attempting to create the battle infobox? Have you tried reading this and this ? I'm here to advise and help you but I cannot just do things for you as if I was a regular editor. I can help you find the relevant documentation and help you if you get stuck however.