All posts by

Staff are not likely to hack their system for you. Your best solution is to create a new account.

I agree, JS is not harder than C or C++, and in fact it's pretty similar in syntax. Learning JS is definitely a good idea, but for the wiki is not very relevant.

You can use ready JS snippets from Dev wiki without any special request. But then again, all this styling is not about JS.

JavaScript has very little to do with that, if any. It's Wikitext and CSS.

I get that, and the main page of the BGS wiki is truly amazing, but that's not something you build in one day, even if you already know wiki coding. You can learn through the work, and the help forum here is always open.

Another thing that you may be confused about, since you said you are currently familiar only with the Visual Editor, is that the code used for advanced editing and templates is Wikitext, not JavaScript. JavaScript is used for specific special features, many of them are not even relevant to visitors on the wiki.

None of the code is necessary for editing. Of course, being experienced with advanced options is useful, but the way to learn is through your needs. Define what you want to achieve, then look for learning how to achieve that.

Even if you do reach into adding custom JavaScript features, you will usually use ready features and don't have to expertise. Even users who write JS features on Dev wiki, rarely have to write JS code specifically for a wiki they admin. And depending on what you mean by "major changes", those may not be even allowed due to the customization policy.

Learning basic CSS can be very helpful though for customization, but even then the cutsomization allowed is limited, and also don't apply to the mobile view which you definitely should take in account.

In the CSS, you can replace

.text-rainbow {

with

.text-rainbow,
a[href$=":Kyumeli1"] {

You can suggest features with the same contact form, but I won't expect anything like that to be added anytime soon.

You can preserve that auto-categorization and make it selective to be applied only for content pages in the main namespace, like that:

<includeonly>{{#if:{{NAMESPACE}}||[[Category:Locations]]}}</includeonly>

Also, Parkour2906, <onlyinclude> is for excluding everything else from being transcluded.

I doubt Staff will know such a detail, but I recall auto-advancing slidshows myself and I'm only on Fandom about one year.

To TableWiz:

1. There is a trick to view normal pages in full-width so you can see the effect of main page column tags: https://starzpower.fandom.com/fr/wiki/Wiki_Power/Sandbox?diff=prev

2. I'm confused about why in your code there is a left column both out of the tabber and inside the tabber. That also seems to push the tab labels toward the right.

Can you describe the steps you made in more details? I can assure you we are not trying to mislead you with non-correct instructions.

@Mendes2 I am a bit confused about the last point. As far as I'm aware, directly including images from any site other than Fandom wikis is not possible, even not from Wikipedia, while including background images by CSS is technically possible from any source browsers can reach.

Edit: About the main point - I agree, when the images represent a necessary portion of the content. Images for additional decoration are not problematic to be added by CSS, and I doubt they affect SEO.

That's the shortest way - two actions, import and export.

Or if you want, you can just copy the source code over, but make sure to credit the source wiki in the edit summary.

There is actually one way you can, only for the desktop version - not for mobile. You can put external images as background images of elements by using site CSS, and with the right setup you can get it to look like an <img>.

Yes, that's what I mean, and unfortunately I don't have anything else to suggest. I'm used to help out with stuff, but building a family tree with code, even with the given templates, is very complicated. Not something I can figure out in less than a few hours, put aside teaching others.