It should also be noted that if you're using a custom script in your personal JS, only you would see the effect, no one else.
It can be done with DPL, but I would say it's rarely useful to just pull lines from any page. Some pages are less relevant than others. So making it pick from a prewritten list is probably better.
Put in mind that forcing it into 6 items per row might look bad on small screens.
You can check your Contributions page and sum the byte count, but it would be a weird way to measure contributions, as many good contribuutions would be mostly replacing text or even deleting text (negative bytes count) rather than adding.
Yes you can do that with a template, but are you looking for just a simple template which you supply the link names for, or something smarter?
If the later, you need to get clear rules about how to determine the links based on the current page's name or something, usually it's tad complicated because it's not always exactly "Chapter 1" "Chapter 2" etc.
Because that's how Fandom designed the mobile main page, for some reason.
I think it wasn't already stated clearly enough, so I would note that the JS solution is very limited.
It cannot make the notification go away, only mark it as read.
It cannot even do that while you're on Discussions, you must visit an actual wiki page every time.
You also must visit the desktop version of a wiki page. The mobile version won't do.
Your screenshot clearly isn't from the desktop version of a wiki page.
Although it wouldn't work anyway because the code tries to import a local script that does not exist.
Sure, if you know where to look, if you know the wiki, the templates, the tables etc. - that's a lot easier. If you need to ask what a particular CSS rule means in order to nail it down - you're welcome to ask.
I just mean that you can't this way confirm it's not used "somewhere".
I don't think that's going to work. Most of the CSS rules are applied to custom selectors that may be used on any random page around the wiki, so unless you visit that particular page you would see nothing different, even less if you are browsing another wiki.
While it's indeed a little long, it's pretty organized, and I also don't see many things that could be defined as "outdated". Of course, some of it may be unnecessary but indeed there's no simple method for checking where a certain selector is used around the site. I'm not saying there aren't methods at all, but any method I can thing about would require some tampering and I'm not sure it's worth it for ~1000 lines of CSS. In my opinion it's quite reasonable to leave it as it is.
No, it's a user-made JavaScript enhancement. Check out https://dev.fandom.com/WallGreeting
Honestly I don't think they ever shared their algoritm regarding "hot" posts. It's pretty clear it has to do with both amount of replies and time since posted, but other than that we can only guess.
I'm not entirely sure what you mean by "touching the other boxes", can you clarify?
I do see however that the layout breaks when the page isn't wide enough, it might be related to the order of the columns - the left column should come first.
The log shows up on the wiki on which the operation was performed, I guess they could technically grant it on another wiki and then the log entry would show up there and not on CC, but the role would be global regardless.
It's the same with user creation log - it shows on the wiki where you've created the account but your account is global to all Fandom wikis.
Well, the whole page is messed up, I don't even see the <div> you've talked about, and there are way too many column tags. There should be only one <mainpage-leftcolumn-start /> and one <mainpage-rightcolumn-end /> (left one should come first) with each of them having a matching <mainpage-endcolumn />
Fix that first and then we'll se what next.
The issue isn't with the width attribute, which is overriden by the CSS you added. It's the /scale-to-width-down/350 part in the image URL that reduces its quality. Unfortunately, this can't really be dealt with using CSS, only using JS.
Then please provide a link
Okay I might have misread your post.
Where does it say you're blocked?
The "include" parameter is about fetching page content, which doesn't seem relevant to what you're trying to do.
Try this:
format=,²{Ark/sandbox/ProcessSingerPage¦,}²