[00:02:23] https://jwmeeting.miraheze.org/wiki/Help:Wiki_editing/Recommendations_for_mobile_friendly_articles_on_Wikimedia_wikis [00:03:18] [1/2] how do i remove the default mode thing (i already removed DarkMode) [00:03:18] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1213637790600925184/1BRgJgW.png?ex=65f63345&is=65e3be45&hm=c7714d4ee7083013ecc6916645065c5b92b77c2eabec96394c6584d7899dcbf9& [00:06:38] [1/2] or you uncheck the extension: [00:06:38] [2/2] https://jwmeeting.miraheze.org/wiki/Special:ManageWiki/extensions#mw-section-other [00:06:54] i already did???? [00:07:31] It shouldn't be there. But It can be the cache [00:07:45] nope, still there [00:07:50] The server needs to refresh, just like Commons.css [00:08:17] i already refreshed the web page [00:08:17] It's teh server cache, not your wikipage cache [00:08:40] how do i clear it :3 (i already did ctrl + r and it did nothing) [00:09:07] Remember when you uploaded your logo? [00:09:25] It took a while, because it is the SERVER cache [00:09:37] Not your wikipage cache [00:09:58] It doesn't help ctrl+r [00:10:13] It will go away soon enough [00:11:50] a day has already passed and its still there [00:11:50] :/ [03:37:09] Go to chrome dev tools by tapping F12 the right click the reload button and choose “Empty Cache and Hard Reload” to be certain it isn’t a local cache artifact. [04:31:14] i only speak Firefox :moonch: [04:31:45] how do i use the pop up extension? [04:31:55] i enabled popups by default yet it did nothing [05:11:39] Popup? Sometimes works, sometimes don't [05:12:13] Like, it require some certain things for it to fully works as you pleased. [06:12:54] I would also double-check to ensure that it didn't get hardcoded into your MediaWiki:Sidebar page, as that also controls what displays there. [06:14:48] RE: Popups, that's one that can take a LONG while to start having the intended effect, much like Visual Editor. [06:17:28] Also worth noting: it'll only work in content (main) namespace by default [06:48:42] just for updating, can I replace Phabricator with Phorge, at this moment? [10:10:10] is there a template in meta Miraheze to show on the user page if a user is dead? [10:35:05] No, not that I am aware of [10:47:33] there is a setup for it, not sure if it's a template per se [10:47:58] [1/2] yeah not a template, but this [10:47:58] [2/2] https://meta.miraheze.org/wiki/Deceased_Mirahezians [11:05:50] There should be a userbox for this [13:00:01] [1/7] Does anyone know whether the automatically generated layout of file pages is stored in a system message? I suppose it is like this: [13:00:02] [2/7] ``` [13:00:02] [3/7] ==Summary== [13:00:02] [4/7] $1 [13:00:03] [5/7] ==Licensing== [13:00:03] [6/7] $2 [13:00:03] [7/7] ``` [13:06:22] It is, for the summary you can customize it by editing a MediaWiki interface page [13:11:34] Special:PrefixIndex?prefix=&namespace=8 [13:11:43] Here you get all system messages [13:30:48] I want to customize those two headings (`==Summary==` and `==Licensing==`), but there are so many system messages, and I don't know of any system messages that store them😵‍💫. [13:32:39] In Upload wizzard? [13:36:00] Or just uploading a file? [13:36:02] MediaWiki:Upload-default-description [13:36:59] MediaWiki:Uploadtext [13:46:10] MediaWiki:Summary [13:55:44] wait [13:55:53] I think I know where to set it up [14:07:42] [1/8] It is indeed possible that they were customized through UploadWizard🤔... My supposition comes from seeing the following file pages of layout on Wikimedia Commons: [14:07:42] [2/8] ``` [14:07:42] [3/8] =={{int:filedesc}}== [14:07:42] https://meta.miraheze.org/wiki/int:Template:filedesc [14:07:42] [4/8] ...... [14:07:43] [5/8] =={{int:license-header}}== [14:07:43] https://meta.miraheze.org/wiki/int:Template:license-header [14:07:43] [6/8] ...... [14:07:43] [7/8] ``` [14:07:44] [8/8] Because normally, those two headings should come from the corresponding strings that are in the same language as the site content language. [14:09:52] Oh... interesting. I didn't use that in my wiki so idk [14:10:39] That is only for wiki's that use many languages [14:11:04] It will pick the language of the user [14:11:44] My wiki for example only uses EN-gb [14:12:00] So I don't need to have it translated. [14:13:48] [1/3] MediaWiki:Upload-default-description [14:13:48] [2/3] ```{{Information |description = |date = |source = |author = |permission = CC-by-sa-4.0 |other versions = }}``` [14:13:48] https://meta.miraheze.org/wiki/Template:Information_ [14:13:49] [3/3] The system will put ==Summary == above it, and == License == underneath it. [14:14:33] (If you choose a license from the dropdown menu, that is) [14:14:58] I just use my own pre defined templates instead [14:30:11] [1/2] But the structure itself is hardcoded in the software, so you can change the word Summary to File information, but not the ==File Information == [14:30:11] [2/2] You can remove it afterwards though [14:32:44] So summary would be at `MediaWiki:Filedesc` and the license is at `MediaWiki:License-header` [14:33:04] indeed [14:36:51] https://cdn.discordapp.com/attachments/407537962553966603/1213857626564206653/1080933379215736862.png?ex=65f70002&is=65e48b02&hm=1f5972d2bf3aa9f89829f826bf70d3cd9b98df920b97af380e583376c6d29b51& [14:37:22] What did you have in mind? [14:43:30] `File Information` CAN be changed using `MediaWiki:Metadata` [14:44:28] It's all been listed at `Special:AllMessages` [14:44:44] Metadata shows the stuff delivered in the image itself, like the camera [14:45:14] yea, I know, but I'm talking about the File Information header [14:45:31] All of the actual messages from the software has been listed at `Special:AllMessages` [14:45:45] I know, I mentioned a few above [14:46:02] at least now you know- [14:48:58] https://jwmeeting.miraheze.org/wiki/File:Gage_Fleegle.jpg [15:06:45] [1/3] Chinese is divided into simplified and traditional forms, each with multiple variants. I want to edit two headings to accommodate the diverse content of these variants, because when the site content language is `zh`, those two headings default to outputting simplified Chinese (`zh-Hans`) content. [15:06:45] [2/3] If I can't edit those two headings, I can only use `MediaWiki:Conversiontable` to achieve certain needs. [15:06:45] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1213865150608838676/400911745767571456.png?ex=65f70704&is=65e49204&hm=adee80e0dc2097585cd647d7303ffc214eb9e135f7f7328e3157f7cccfac8fd7& [15:17:09] Ah. Okay [15:19:09] [1/3] Each message has different languages. [15:19:09] [2/3] Like MediaWiki:Metadata/zh and [15:19:09] [3/3] MediaWiki:Metadata/zh-hans [15:19:21] So each user will see it in his/her own language [15:20:00] Just change your language, and check after upload. You'll see that the language will have been changed [15:22:28] [1/3] So in: [15:22:29] [2/3] MediaWiki:Filedesc add: ```{{int:filedesc}}``` [15:22:29] https://meta.miraheze.org/wiki/int:Template:filedesc [15:22:29] [3/3] MediaWiki:License-header add:```{{int:license-header}}``` [15:22:29] https://meta.miraheze.org/wiki/int:Template:license-header [15:29:36] ok [15:38:05] I am in a great mode, but wondering, should banner images for a page have alt text? [15:38:50] I know, but those two outputted headings are not system messages. I just tried to add the corresponding i18n magic words in `MediaWiki:Filedesc` and `MediaWiki:License-header`, but an error message "Expansion depth limit exceeded" appears. [15:40:41] hmmm, strange. [15:41:25] MediaWiki:Filedesc/zh [15:41:41] MediaWiki:Filedesc/zh-hans [15:42:02] MediaWiki:License-header/zh [15:42:22] MediaWiki:License-header/zh-hans [15:42:42] They do have the system message in these languages [15:43:03] It automatically puts that between == == [15:45:10] [1/6] Commons.Wikimedia uses a different system. They translate through [15:45:10] [2/6] ```=={{int:filedesc}}== [15:45:10] https://meta.miraheze.org/wiki/int:Template:filedesc [15:45:11] [3/6] ...... [15:45:11] [4/6] =={{int:license-header}}== [15:45:11] https://meta.miraheze.org/wiki/int:Template:license-header [15:45:11] [5/6] ......``` [15:45:11] [6/6] But we have all messages translated as far as I know, in the most spoken languages [15:45:23] I am in a great mood, but wondering, should banner images for a page have alt text? [15:45:52] I always think you shoold, especially in case someone uses a screenreader [15:46:04] Alt messages are more descriptive [15:49:04] [1/2] People who are visually impaired, rely on these alt= messages. So they know what is shown. So not: "House on hill" but "A brick house on a hill with tall trees and fence. A red tile roof and a wooden green shed is beside it. People are waving." [15:49:04] [2/2] Just as example [15:49:41] Also those who are colour blind for example can use that [15:51:48] Just having to work out what to add for 300+ AI images [16:17:44] alt desc has to be as short as the context allows, so "house on hill" may be sufficient if that is all the image is meant to convey [16:20:28] For visually impaired is that to little info. [16:21:38] it's still interesting that alt image info would actually increase your scores in SEO [16:22:56] Because visually impaired people depend on it [16:23:24] Their screen readers can read what is described [16:23:55] Therefore you need to be more explanatory in your alt [16:25:18] @HandtheGene probably means what you write in the thumb under the image? [16:25:27] [1/2] https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Accessibility/Alternative_text_for_images [16:25:27] [2/2] alt text should be short and convey the same essential information as the image, so in some contexts, "house on hill" or "a house on a hill" will be sufficient., whereas other contexts may warrant a lengthier description like "A brick house on a hill with tall trees and fence. A red tile roof and a wooden green shed is beside it. People are waving." [16:25:49] LOL [16:25:53] Wikipedia [16:26:21] Wikipedia is never been friendly for visually impaired or Mobile users [16:26:31] Don't trust to much on their MOS [16:28:06] what about the ALT function that social media started adopting recently (twitter, tumvlr) [16:28:27] I rarely use any social media anymore [16:28:34] So I don't know [16:28:44] sometime it was "abused" to add more captions to the post [16:28:53] people put very detailed descriptions in ther [16:29:00] yep [16:29:24] I stay clear of twitter or Facebook or whatever, I just use discord [16:29:41] maybe implement something like that as an alternative to default alt [16:30:04] [1/3] there are other guides that say the same thing about alt text having to be short and serving the same function as the image, which depends on the context [16:30:04] [2/3] https://accessibility.psu.edu/images/alttext/ [16:30:05] [3/3] https://www.w3.org/WAI/tutorials/images/tips/ [16:31:13] point is just that you provide all of the essential information without giving superfluous details or highlighting the wrong aspects of the image, in the specific context where the image is used [16:31:35] Yeah. "House on the Hill" Try to imagine what kind I mean. [16:31:41] It’s important to not only provide ALT text, but also provide one that is useful in the context of the document. You may not need to include every detail about the image, and you may be able to skip over purely decorative images, but those that contain critical information need to have it to spelled out in the ALT text. [16:32:17] You don't need to spell out that it has a rain drain, and a chair, and grass around it [16:34:10] [1/3] But you need to describe, what kind of house it is. What the scene is. [16:34:10] [2/3] You need to be able to picture that house on the hill. [16:34:10] [3/3] Is it a wooden house, or a red brick house, does it have tiles or straw. Is et a two under one roof house, or separate [16:34:29] The blind person needs to be able to picture it in their head. [16:35:27] You do not use long sentences. But you have to share Key info to help the impaired to picture what it is. [16:36:26] If I write "House on the hill" you don't know anything else, then a house on a hill. [16:38:51] i feel like it's going in circles so i'm just gonna drop it [17:30:12] can someone remind me if col/rowspan can be placed in styling? [17:31:42] I don't think so, at least it was a HTML thing [17:31:43] I don't think so [17:32:00] But you can use grid to do pretty much the same thing [17:33:36] Maybe flexbox also [17:40:29] I just joined and am trying to make a wiki, im logged in but I dont see an edit option any ideas why ((on mobile)) [17:40:54] make a wiki, you mean requesting one right? [17:41:02] Are you on your wiki ? [17:41:12] Already made and verified [17:41:34] the wiki [17:41:36] not account [17:41:46] Yes, and im confirming that [17:42:03] Did you create a page ? [17:42:27] Yep, page is all made, it has a single edit by one other, just trying to figure out how to do it myself [17:42:57] can you link? [17:43:00] your wiki here [17:43:22] wait, on mobile [17:43:37] try to switch to desktop mode, at the very bottom [17:43:47] default mobile mode nerfs a lot of things [17:44:02] You can edit on mobile display normally [17:44:03] Ah, I see, thank you ill try [17:44:11] It's ugly and unpractical but still [17:44:41] If you don’t enjoy sanity [17:44:55] I can deal with ugly, it works thank you! [17:44:57] Ye [17:45:07] we advise to change skins, either all together to some mobile adaptive and disable MobileFrontend, or pick another for mobile mode skin [17:45:19] instead of default Minerva [17:45:30] I did some template with CSS and js on mobile [17:45:39] Why ? [17:45:57] well, as I said, Minerva disables a lot of things [17:46:02] especially for admins [17:46:26] What skin do you recommend? [17:48:45] tbh, I uses Citizen- [17:48:55] it's the only skin I use- [17:49:12] [1/3] Timeless or Cosmos, and people also seem to like Citizen [17:49:12] [2/3] but I personally would make these default skin and disable MobileFrontend altogether [17:49:13] [3/3] if you really want "traditional" skin like old Vector or Monobook, then mobile mode is needed (if you want to please mobile users) [17:52:18] Well last time we tried disabling mobile frontend it broke the wiki for mobile sooo [17:53:00] it broke? then use an responsive skin [17:54:14] yeah, the point is mobile responsivness [17:54:33] what I mean is either you pick such skin as the main one disable frontend [17:54:48]