Hey, I'm new here, was wondering how something should be formatted. So in the japanese version of Trio of Towns, one of Ford's name choices for his daughter is リン, which is the Japanese word for Phosphorous. The English version changes that option to Marie (in reference to Marie Curie).
Should I replace Rin/Lynn (リン) with Marie on the page, and maybe make a note in a reference/trivia section at the bottom of the page?
Hey, I'm writing this as a continuation of this thread. Apparently, it looks like the infoboxes aren't portable anymore, old drafts were either approved and then reverted by Mai (for reasons I couldn't find in edit summaries or walls of either of you) or deleted by you after some time, also for unknown reasons. Related CSS was removed as well. I managed to make portable drafts again and here's a side-by-side comparison of them (to spare you having to import my common.css and then view my sandbox afterwards). What was the reason for reverting them last time and do you think they could be applied again?
And no, I'm not a Vanguard member nor I'm representing them.
Currently on vacation, but saw your message and thought I'd respond. I think we've just used some older boxes/coding and didn't really get around to updating. As for why reverting was done, I'm not too sure. Generally speaking, I only mess around with infoboxes if I want wording changed, a row added, or if I notice vandalism. Mai owns her own wikia and knows a lot more about coding the infoboxes than I do, so she would have done a lot more work on them than I have. Admittedly, instead of a sandbox, I might make a minor change and then revert it right away if I've noticed something doesn't work/a mistake has been made. This might be the reason for the reverts.
I recently made some changes to infoboxes on another wikia by editing our .css over there. I'm sure changes could be applied to make the infoboxes portable if you let me know what changes need to be made in the common .css .
Ah, I see. Should I contact Mai in future if the changes get reverted again? She seemed inactive and the previous thread was on your wall so I decided to contact you instead.
The changes that need to be made to MediaWiki:Wikia.css is inserting the CSS from my common.css to the bottom of it. After you apply it I can go through the drafts I made (this, this, this, this, this and this) and approve them one by one so you'll be able to see portable infoboxes in effect on articles. Of course, you can also apply the sitewide CSS and check my sandbox/play around with the drafts to see if they fit your needs before they go live on articles. If you don't see the effects of the CSS immediately after inserting it, try clearing your cache and if that doesn't work either you can view my sandbox in debug mode that should be ignoring cache.
Approving your drafts are easy enough. When you say insert your CSS, do you mean insert ALL of it BELOW ours without making any changes to our current Media.css?
Mai is somewhat active, she just manages her own wikia and is an admin on a few others as well. I am definitely the more active of the two of us though, yes. I'm much better about information gathering and actually contributing to articles than I am coding and what not though. I've left a message on her wall linking to this thread. But nothing will really change once the changes are applied, so I don't think it makes much of a difference. I just get a little confused as to which code I should be manipulating on the .css, but I know about approving the changes and what not to get the changes live and running.
Yeah, I meant insert all of the CSS from my common.css below the current site CSS on MediaWiki:Wikia.css without any changes to other CSS. If you want to make sure you copied the CSS correctly, open it raw, click CTRL+A to select it all and CTRL+C to copy it.
Hey there, Nix! I hope you're doing well. I just wanted you to know that Aurelia's page is pretty much done! I don't know how to remove the stub saying that it needs more information or even how to say that it doesn't need a cleanup. When you find time will you be able to take care of it for me?
I'm not sure if you still are active on here or are into HM anymore, but lately I've seen that certain people and sites claim that Castanet, the setting in Harvest Moon: Animal Parade, is an island. All this time, for the 4+ irl years I've been playing the game, I believed that Castanet was the name of a large portion of the continent where Animal Parade took place. If it is true that Castanet is an island, may you direct in me towards the evidence that proved that Castanet is Ann island? Thank you very much, and thank you especially for contributing so much to the Harvest Moon fandom. (Also, I'm deeply in love with Bo as well; I SOO wish she was a bachelor... :()
Commenting where? If you're talking about the commenting people can make at the bottom of a page, we've had that turned off for a few years now probably at this point. The reasoning was that it was a breeding ground for spam, people arguing, spoiler, etc. If you want to ask a question, ask it in the page's talk page. You could also ask at the help desk or on our walls. :)
Hello! I'm Wowa, and I'm representing Fandom's Vanguard team. We're users who volunteer to help communities adopt to new technologies and features, like content portability. We've identified your community as a high priority for introducing the Portable Infobox tool, which has a lot of benefits for your community. Rather than get into all of the metrics and numbers (though I can present some of those if you're interested), I'll keep it simple. I'd like upgrade the Infobox templates themselves so that they can be accessible on any current and future platform. Maintaining them if you want to make changes should be very simple.
I've added drafts for all of your current infoboxes which you can modify or approve early if you'd like. I've put the styling here. Here's a full list of all the drafts:
It's because I rejoined Vanguard recently and haven't had the time to edit the members list again. I took a major break from Fandom until 2 weeks ago, so I still have some other things to take care of first.
I don't really understand templates that well past what little work I've done here and on the other few wikias that I'm an admin of. The more complicated, the less I understand. All I really know is that they work on this wikia with the code we've built.
Maybe I'm daft, but I really don't understand this process at all. The drafts really aren't showing me a good represenation of what would change.. they look virtually the same. Does all this small change really do is make it more viewable on mobile and portable devices?
Maybe leave a message on Mai is Me's wall too. She owns her own wikia and has done a lot more work with templates and stuff than I have. I guess I'm not opposed to changing it, but I want to be able to make changes and edit if necessary without having to relearn how to do so with these new changes. I also vote against making changes to the way the template looks, in terms of the color and way the information is laid out.
The HM64Shops, Infobox CVG and Quest infoboxes are not being used. So no need to really do up work on them. Thanks for reminding me that I need to delete them.
I'd be more than happy to explain the process to you. The aim of the process is to make new infoboxes that look the same and have the same functions on desktop computers. However, the infoboxes become significantly better on mobile devices. About 50% of Fandom's views come from mobile devices, so it's important that infoboxes look good for them too.
So I assure you that portable infoboxes will give the same results on desktop computers while improving them on mobile devices.
If you can't make a decision based on this information, just tell me and I'll contact Mai as you suggested.
Alright, this means that you can delete the current 3 infoboxes, as well as their drafts.
Nix, I have like no place to speak here, but I'd like to say that I admin a wiki who got the same thing done to them. It hoestly doesn't change the looks, but helps them be able to be viewed on mobile, they generally appear glitchy or not there when they're unportable, it's a pain but it does help significantly.
I've taken a look at the code for the Infobox Character as an example. It doesn't seem like it would be difficult to make edits or change things if necessary. If it functions the same on a desktop (which I use), I guess it doesn't really affect me or other desktop editors that much, but would help with viewership. I suppose I'm not seeing any cons.
Would you be willing to do work on one template, tell me when you're done and then let me view it to just to see the finished product before continuing with the other templates? Would be much appreciated.
I agree with Wildheart, that's exactly the purpose of portable infoboxes!
The code is rather structured and simple in comparison with wiki table syntax, so it's easier to learn, yes. If you still happen to have any questions, I'm happy to answer them of course.
I actually already created drafts for every single infobox template that is/was used on at least one article, the full list is in my first message. You can take a look at the product in a sandbox if you want to do that.
I'm noticing that a lot of the images in the character boxes are either way smaller or way bigger than they were previously without the image size being changed. Could this be a change in the template?
Portable infoboxes generally scale images automatically to prevent the loss of image quality caused by manual user input. Sometimes this process isn't optimal and needs some tweaking (e.g. some images use very much vertical space in certain cases) which I can do. I just need to identify the specific problem to create a fix. :)
Oh, it's because the image's resolution is only 100 pixels in width. Scaling it up would make it look pixelated. If you still prefer to make them as big as possible, while risking image quality loss, I can arrange that.
Our images aren't incredibly high quality to begin with. In the sense that the games we cover aren't really in HD either. I think that the loss of quality would be worth trying. I feel like 100 pixels is too small.
Well, communities give images a specific width, so it looks good on desktop computers. That's all fine, but this often leads to problems on mobile devices since they are completely different from desktop computers.
As the image resize function was mostly used in the way I described above, Fandom decided to remove this feature from portable infoboxes. The specific problem with your images is that they have a very low resolution and need to be displayed as big images, which is something Fandom doesn't really expect.
There is a last solution to this problem doable by CSS, however it is incompatible with your current image width syntax and would require a separate |image width= parameter. It also would only support some fixed image widths (so for example widths like 100,120,150,180,200,...) as defining a CSS theme for 300 possible image widths would slow the CSS down harshly.
This is a rather inconvenient solution and rather to be seen as a last resort, but if you really want to preserve the feature in some way, I can arrange that.
I think that we are in a unique situation where the images we do have can't really be displayed in a higher quality. Very few images exist of characters for the infoboxes, and the ones we have are usually the best ones that are available. Images could be resized possibly and re-uploaded. I'm not sure how the rest of the community feels, but I think that the way it is now is still better than limiting it to 100px. It's just a matter of fixing some images than, as a lot of them do look pretty good the way that they are in full size. Rather than having all of the images across the board limited to the very small size at 100px.
I agree. Reworking 50+ images (at least that's my approximation) would be quite a bit of work, so it can be reduced to editing those few images that cause problems. I'll leave the current code then as it is, so the images will stay full-width!