View source for Talk:Main Page

{{talkheader}}
{{Archives}}
== Templates for he-or-she in articles ==

I had a bad idea, which I didn't think through, and took too far. So, here you go: a set of templates to allow The [[Great Random]] to choose the gender of the pronouns in your GodWiki writing!

In brief:

* {{Tlx|He-or-She}}: You'll get either <code>He</code> or <code>She</code>, chosen at <small>kinda-</small>random.
* {{Tlx|he-or-she}}: You'll get either <code>he</code> or <code>she</code>, chosen at <small>kinda-</small>random.

If you're with me so far, I'll assume you can extrapolate to understand the following templates too:

* {{Tlx|Him-or-Her}} and {{Tlx|him-or-her}}
* {{Tlx|His-or-Hers}} and {{Tlx|his-or-hers}}
* {{Tlx|Hero-or-Heroine}} and {{Tlx|hero-or-heroine}}
* {{Tlx|Heroes-or-Heroines}} and {{Tlx|heroes-or-heroines}}

Every one of these can take the optional parameter {{para|or|<var>anything at all</var>}} (as in, for example, {{Tlx|he-or-she|or{{=}}1}}). If  {{para|or|<var>anything</var>}} is present, you'll instead get either <code>he or she</code> or <code>she or he</code> instead.

These are safe to use inline with combining forms. As in: <code>Now {{Tl|he-or-she}}'s the winner!</code> will produce the expected <code>Now he's the winner!</code> or <code>Now she's the winner!</code>.

There's more information (and an important note about an error I can't fix, which could cause you to panic unnecessarily) in the [[Template:He-or-she/Documentation|documentation for <nowiki>{{he-or-she}}</nowiki>]] (and if you can fix that error, brilliant!).

'''''Great, [[Djonni]], but what's the point?'''''

Rather than every single wiki page using ''he'' (or even ''he or she'') as a default choice, this can allow you to have the choice made for you as to what gender will be used in an article. These templates will ''consistently'' choose the same pronoun for a given page; you can be sure that it will consistently choose the same {{he-or-she}}, {{him-or-her}}, {{his-or-hers}}, {{hero-or-heroine}}, etc, and won't switch unexpectedly between them. Then, if you copy-paste the same wiki-code into another page (or transclude it), it will be consistent with ''that'' page. Or, if you prefer, just use it to set an article gender once, and follow that gender choice through the rest of the text, whatever you like. It's a 50/50 diceroll for the gender of a page, to use however you want.

'''''If you want more'''''

I'm done with this collection of templates for now (it was a ''much'' larger set that I first expected already), but if people indicate they would like to use templates like this in a more use cases, these further templates could be made pretty easily:

* {{Tlf|God-or-Goddess}} and corresponding lowercases, plurals, and possessives (a full paradigm of 6 templates altogether)
* The inverted order templates, for when you want to (e.g.) refer to a secondary character, ''he'', that your primary protagonist, ''she'', interacts with. These would be structured as {{Tlf|She-or-He}}, etc. That set expands out to another 10 templates, plus 6 more for {{Tlf|Goddess-or-God}}

I'll do the work if there's an indication that anyone likes this idea and would want to use them! :)

'''''Dude, they're ''still'' binary genders.'''''

Yeah, I know. ''All'' of Godville is binary gendered, and it's out-of-scope for me to fix that with a couple of cute little templates. Sorry. If you can propose a ''sensible'' way that I can promote inclusion of non-binary gender anywhere then I'm honestly all ears, I don't have any ideas, good ''or'' bad. But this at least offers something to erode the monotony of male-gendered content on the GodWiki. And hey, since I haven't built the {{Tlf|she-or-he}} counterpart templates, I guess by default I'm also not promoting heteronormativity, so... Yeah, there's that.

Okay, I'm gonna go do something else now. If you have questions, comments, criticism, or requests, please let me know, here, [[Talk:Djonni|here]], or by direct message on Godville. -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 13:46, 1 November 2018 (UTC)

: I've used the {{Tlx|he-or-she}} family of templates in today's update to the [[Template:Featured|Featured Article]] on the main page. It should read fairly seamlessly, and give a concrete example of how it might be used. You'll also note that when appearing on the [[Main Page]] and in the original [[Template:Featured]] page the templates render as <code>he</code> in both places. So speaketh the [[Great Random]]!

: If there are any issues with these templates in the Featured Article at all, I encourage you to [https://wiki.godvillegame.com/index.php?title=Template:Featured&action=edit&undoafter=88986&undo=88987 undo the edit] where I put them in, and to [https://wiki.godvillegame.com/index.php?title=Talk:Main_Page&action=edit&section=9 explain the problem] here for us. -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 10:56, 2 November 2018 (UTC)

:: {{m|idea}} It wouldn't be difficult to implement a parameter {{para|daily|<var>anything</var>}} that will switch the gender every day. I kind of like that idea, it's perfect for use cases like the Main Page etc. -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 11:18, 2 November 2018 (UTC)

::: {{m|done}} The existing set of templates now support a parameter, {{para|daily|<var>anything</var>}}, which switches the gender for the text each day. If you want to see it in action, the current (at the time of this note) [[Template:Featured|Featured Article]] snippet on the [[Main Page]] is now using it, and so each day when the cache of the Main Page is refreshed, the text of the Featured Article will change gender. (I am here assuming that the cache is refreshed daily. That may not be the case; a couple of days observation will reveal the real behaviour.)

::: {{m|thankyou}} Also, after some effort by the talented {{god|FerdNYC}}, the error described in the docs is no longer an issue. I'll update the docs to explain how the template behaves before a new page is saved.

::: Finally, both of these changes make the creation of the inverted template set (<code>{{Tlf|she-or-he}}</code> et cetera) a must. So I'll get to work on that too. (Probably before I update the docs, so I only gotta do that once.) I think I'll make them as essentially wrappers for the current set, though, using a new {{para|reverse|<var>anything</var>}} option, so that improvements are less arduous. (Perhaps I should simply implement a master function (<code>{{Tlf|m-or-f}}</code>?) which takes {{para|male|<var>him</var>}} and {{para|female|<var>her</var>}} text inputs? Then behaviour changes would be completely consistent to the entire set. Hmmm.) -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 13:15, 3 November 2018 (UTC)

:::: {{m|done}} Instead of making an entire set of {{tlf|she-or-he}}, each of the gender-selection templates now supports the {{para|invert|<var>anything</var>}} parameter to switch the focus of the gender when required to write sensible sentences. More detail and examples are given in the documentation for the {{tl|m-or-f}} template which is now the basis of the whole set (and can be used to construct your own God-or-Goddess or any function you like. More info in the docs.)

:::: Oh, and while writing the docs I realised I'd missed the possessive adjectives, so I've added {{tl|his-or-her}} and {{tl|His-or-Her}} to the set. So now, {{he-or-she|daily=1}} can hold {{his-or-her|daily=1|invert=1}} hand in the moonlight, and make sense.

:::: I'm going to start subtly including these templates in some key places around the GodWiki, especially for content in highly-visible places like the Main Page. But they're there for everyone's use, so if you want to, enjoy!

:::: Please leave any relevant comments, questions, or requests here. For now, I consider this little template project concluded. :) Cheers -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 17:05, 3 November 2018 (UTC)

{{outdent|:::::}} {{tqi|If you can propose a ''sensible'' way that I can promote inclusion of non-binary gender anywhere then I'm honestly all ears|q=yes}} Personally I've become pretty big on singular "they" (and equivalent forms), for the general case of genderless pronoun usage. And it doesn't even require any templates! 😉 

You do have to get used to reading things like, "The hero brushed themself off and continued on their way," which parses pretty weird at first. Also, '''holy ''wow''''' do some people get irrationally pissed off at that usage, accusing you of everything from PC capitulation to eroding the fabric of society. But I say screw those people, since they insist on being <nowiki>{{dicks-and-or-vaginas}}</nowiki>. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 13:07, 4 November 2018 (UTC)

: (Note that my example also requires the reader to consider "hero" a genderless noun, which is a topic about which there has been plenty of debate, and strong arguments made on both sides.) -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 13:21, 4 November 2018 (UTC)

:: Oh I absolutely agree on "they", but as you also pointed out, it's not, erm... ''universally'' agreed upon. ;) The genderlessness of "hero" is also interesting, but since all of Godville differentiates between {{heroes-or-heroines|daily=1}} and {{heroes-or-heroines|daily=1|invert=1}}, I feel like defaulting to 'hero' in the Goville context is defaulting to male-focussed language.

:: But! If any editor wishes to, ''they'' are welcome to use any language they like when describing or failing to describe the gender of any characters. Of course. :) -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 14:09, 4 November 2018 (UTC)

::: [[Image:cross.png]] "Not that there's anything wrong with that!" 
::: [[Image:tick.png]] "No, of course not!" -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 19:57, 5 November 2018 (UTC)

== Guild infoboxes now automatically link to guild pages ==

[[User:Djonni|Djonni]] had the excellent idea to have {{tl|Guild}} generate links to guild pages ''automatically'', instead of requiring a {{para|stats}} argument to provide the URL. So, that's now in place, and a lot of Guild articles should contain '''Guild Page:''' links that didn't have them before.

If for some reason you would prefer '''not''' to have that link shown on a guild article, passing a {{para|stats|no}} argument to the {{tl|Guild}} template will disable the automatic link generation.

And if the automatic link is generated ''wrong'' for some reason, {{para|stats|<var>url</var>}} still works to manually supply a URL. (This also means that older guild articles that include a {{para|stats|<var>url</var>}} argument will continue to function same as always. But {{para|stats|<var>url</var>}} is no longer '''necessary''' to have a '''Guild Page:''' link show up.)

For most Guild articles, {{para|stats}} should '''not''' be included in the template arguments anymore. It's easier to just let the template generate the link automatically. (It's up to the editors of existing guild articles, whether you remove {{para|stats}} if it's already set.) 

The other link parameter, {{para|forum|<var>url</var>}}, is still required if you want to display a forum link. There's no way the template can automatically determine the correct URL for guild forums. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 12:53, 4 November 2018 (UTC)

== Decorations were hung on the artifacts with care ==

'''''Note:''' this template has since been renamed more generally as {{tlx|Decorate item}}''

Inspired by the [[Halloween 2018]] article's extensive use of example pumpkin-decorated artifact names, and by the fact that just ''writing'' e.g. "🎃[[golden pumpkin]]🎃" doesn't quite look right (the pumpkins are too close to the text), I've created a new set of templates specifically to produce these "decorated" strings, but with nicer formatting and line-wrapping protection.

The general-purpose template is {{tlx|decorate artifact}}, but more convenient wrappers have been created for known Godville decorations:

* {{tlx|pumpkins}}: for decorating Halloween artifacts, e.g.
:: {{tlx|pumpkins|<nowiki>[[golden pumpkin]]</nowiki>|}} → {{pumpkins|[[golden pumpkin]]}}
* {{tlx|party}}: for decorating celebration-related artifacts (like the anniversary specials), e.g.
:: {{tlx|party|<nowiki>[[3000-days gold coin]]</nowiki>|}} → {{party|[[3000-days gold coin]]}}

Templates for additional standard decorations will be added as they appear, or [[Template talk:Decorate artifact|upon request]]. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 15:39, 7 November 2018 (UTC)

:* {{tlx|turkey}} was aded for Thanksgiving, and produces the first one-sided decoration:
::: {{tlx|turkey|<nowiki>[[roasted turkey]]</nowiki>}} → {{turkey|[[roasted turkey]]}} -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 04:13, 4 December 2018 (UTC)

== A new link template for Guild pages ==

A new linking template, {{tlx|Guild link}}, has been added to the wiki. Use it to conveniently link to the official Godville page for the named [[Guilds|Guild]].

The same way: {{tlx|God|<var>God name</var>|}} => {{God|<var>God name</var>}}

You can now use: {{tlx|Guild link|<var>Guild name</var>|}} => {{Guild link|<var>Guild name</var>}}

(Hopefully the emoji shield in front of the Guild's name shows up everywhere. If not, in particular if you see an empty rectangle or any sort of question-mark symbol, please reply and let me know — include the details of what browser, device, operating system, etc. you're using.)

For example: {{tlx|Guild link|Bobius|}} => {{Guild link|Bobius}}

There's also a plaintext mode, just add {{para|plain|yes}}. {{tlx|Guild link|Eternal|plain{{=}}yes}} => {{Guild link|Eternal|plain=yes}}.

(That's used in the {{tlx|Guild}} infobox template, to generate the '''Guild Page:''' links.)

Full details, including available parameters and more examples, are in the documentation at {{tlx|Guild link}}. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 15:53, 11 November 2018 (UTC)

== And a new link template for Pantheon positions... ==

... just to complete the set!

{{Tl|Pantheon link}} can now be used to create a nicely formatted (or plain) link to a Pantheon on the Godville game page, and can optionally link directly to a specific position in that pantheon. It is expected to be used primarily on [[:Category:Gods|God]] or [[:Category:Guilds|Guild]] pages, though be aware that if your pantheon position is volatile you may prefer not to link directly to it.

So now, just as {{tlx|God|<var>God name</var>}} => {{God|<var>God name</var>}}<br />
and {{tlx|Guild link|<var>Guild name</var>}} => {{Guild link|<var>Guild name</var>}},

now {{tlx|Pantheon link|<var>pantheon</var>}} => {{Pantheon link|pantheon}}

And, more usefully, to link to a specific pantheon position:<br />
{{tlx|Pantheon link|<var>pantheon</var>|15}} => {{Pantheon link|pantheon|15}}.

As with the shield in {{Tl|Guild link}}, hopefully the trophy emoji appears correctly on any device. Should it not, reply here and let us know, with what browser, device, operating system, etc. you're using.

Some quick examples:

:{{Tlx|Pantheon link|taming|237}} => {{Pantheon link|taming|237}}
:{{Tlx|Pantheon link|savings|20|text{{=}}short}} => {{Pantheon link|savings|20|text=short}}
:{{Tlx|Pantheon link|wood|1102|plain{{=}}yes}} => {{Pantheon link|wood|1102|plain=yes}}
:{{Tlx|Pantheon link|storytelling|51|text{{=}}none|plain{{=}}yes}} => {{Pantheon link|storytelling|51|text=none|plain=yes}}
:<code><nowiki>[[Pantheon of Gratitude]]: '''</nowiki>{{tlp|Pantheon link|gratitude|123|text{{=}}none|plain{{=}}yes}}<nowiki>'''</nowiki></code> => [[Pantheon of Gratitude]]: '''{{Pantheon link|gratitude|123|text=none|plain=yes}}'''

More details and examples are in the documentation at the {{tl|Pantheon link}} page. Take a quick look there to see how to use it with any pantheon you'd like (though it best suits pantheons where your position is quite stable, as it can't update itself magically with your current position). If you have any questions not covered in the documentation, please feel free to ask, either here or on [[Template talk:Pantheon link]]. -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 13:16, 13 November 2018 (UTC)

== Sign template updates requiring page edits ==

{{Sign|title=This template needs to be fixed|text=These fixes will require the editing of Guild articles by a non-Guild-member (specifically, me — [[User:FeRDNYC|FeRDNYC]]), which is normally not permitted by the Godwiki rules. I request that everyone understand the reasons behind this one-time, limited violation of those rules.}}
===The plan===
The {{tlx|Sign}} template, which is used to create notices like the one above, has several issues with how its parameters are specified. You can find a long, detailed explanation of those issues at [[Template talk:Sign|the Talk page for the template]], if you're interested. But the important point here is, those issues are going to be fixed. The fixes, however, will affect ''existing'' uses of {{tlx|Sign}} in Godwiki articles.
===What this means for you (the editor of an article containing {{tlx|Sign}})===
# If your article contains a sign transclusion with parameters like {{tlx|Sign|bordercolor{{=}}red}} or {{tlx|Sign|bgcolor{{=}}#91A3B0}}, those parameters will '''start''' working, where up until now they have been ignored. This will change the appearance of the sign, perhaps in unwanted ways. If so, simply remove the {{para|bgcolor}}, {{para|bordercolor}}, or {{para|outerbordercolor}} arguments so that the sign will use the default values, like it was previously.
# If your article contains a transclusion with parameters like {{para|bordercolor|ee8822}}, those parameters will ''break'' due to the changes. If this happens, '''I will fix them for you''', by changing them to e.g. {{para|bordercolor|#ee8822}}. You will not have to do anything. That is the reason for this announcement, and for the request that Guild members understand why a non-member will be editing their Guild page. My changes on any Guild articles will be limited to editing {{tlx|Sign}} parameters '''''only'''''.

If there are any affected {{tlx|Sign}} transclusions on user pages (it doesn't ''look'' like it, so far), I won't be able to fix them. I'll try to leave explanatory notes on the associated Talk pages, if those cases arise.

I don't plan to start these changes immediately (I want to give people time to digest this announcement, for one thing), but they will be happening soon and most likely will be completed by the end of the week. If anyone has any objections or issues, you have the floor... -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 21:56, 18 November 2018 (UTC)

: <strike>{{m|partlydone}}</strike>
: The color-parameter changes are complete. {{tlx|Sign|bgcolor{{=}}|bordercolor{{=}}|outerbordercolor{{=}}}} now accepts '''any''' valid CSS color string, e.g. {{para|bgcolor|red}} or {{para|bordercolor|rgb(100,150,0)}}. If specifying color by hex color value (i.e. <code>#RGB</code> or <code>#RRGGBB</code>), you ''must'' include  the leading <code>#</code> sign.
:; Guild pages edited
:* [[The Ancestry Knight]]
:* [[Lucky God Casino]] (three places)
:* [[I AM]] (two places)
:* [[Open Bar]]
:* [[404]]
: The only change that remains to be done is the fix to {{para|imgwidth}}, and the only page that will be affected ''there'' is [[Open Bar]] (again). I'll get to that another time. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 00:24, 23 November 2018 (UTC)
:: {{m|done}} 
:: Completely done, {{para|imgwidth}} syntax is updated in {{tlx|Sign}} and all three pages which make use of that parameter ([[Open Bar]], [[Template:Godwiki event construction]], and [[Template:Godwiki event review]]) have been modified accordingly. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 11:52, 12 January 2019 (UTC)

== Default picture and auto-templating for Artifact and Monster infoboxes ==

Just like {{tlx|Equipment}} since its inception, {{tlx|Artifact}} and {{tlx|Monster}} now have default "generic" images that they will use whenever an image is not supplied via {{para|image|<var>filename</var>}}. They will also (again just like {{tlx|Equipment}}) auto-template those articles as {{tlx|Picture}}-needed, adding them to the [[:Category:Pictures needed|Pictures needed]] hidden category.

To avoid double-templating, I removed the manual {{tlx|Picture}} templating from any {{tlx|Artifact}}-using articles which already had it. (There were only two, [[Orange bag]] and [[Heart warmer]].)

I tried to also get all of the {{tlx|Monster}} articles which contained manual {{tlx|Picture}} templates. There were far more of those, and I can't promise I didn't miss any. If you see any articles with '''two''' "Pictures needed" hatnotes (that's a message box at the top of the page), please edit the article source to remove the "{{tlx|Picture}}" template, as the infobox is now automatically supplying it. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 02:45, 23 November 2018 (UTC)

== Navbar line on navboxes ==

Now that we have a {{tlx|Navbar}} template (which I imported for use with the new {{tlx|Infobox}} code, though that isn't ready yet), we can have our Navbox templates show links to make them easier to modify. I've installed a Navbar on just {{tlx|Navboxauras}} for now, as an experiment. It's the three letters (for View • Talk • Edit) in the upper left corner that let you access the navbox template more easily:

{{Navboxauras}}

Navbars on ''infoboxes'' tend to have fallen out of favor on MediaWiki sites (and I may still end up disabling them on our new infoboxes, before they're released), because they lead to people who want to update infobox data trying to edit the template ''code'', when they '''should''' be editing the template ''transclusion'' in the article they're reading. 

But with Navboxes, there's nothing to edit in the article, and you ''do'' need to edit the template code to modify them. So, it's a little different. There is still the danger, though, that the links will lead to inexperienced people messing up the Navbox templates more frequently. So I guess that's one reason for experimenting on just one template, first, to see if {{tlx|Navboxauras}} becomes the target of increased problem editing.

Let me know if anyone has any thoughts or objections. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 05:25, 25 November 2018 (UTC)

:How about we have a version for Infoboxes that simply omits the 'edit' option? I think there's definitely merit in a clear link directly to the documentation and talk pages for an infobox. -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 16:16, 25 November 2018 (UTC)

:: Hmm, that's definitely an option technically, so yeah that could be one way to go. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 05:27, 26 November 2018 (UTC)

== <strike>Preview</strike> Rollout of new Infoboxes ==

For a while now, I've been working on adapting the master {{tlx|Infobox}} code from the English Wikipedia for use here at the GodWiki, with the aim being to reimplement our Infoboxes. Using {{tlx|Infobox}} as the base template gives us access to more advanced features and formatting, and gives the infoboxes a more modern and cohesive look.

For this first round I'm focusing only on the three main infoboxes — certainly {{tlx|Town}} would also be updated, and most likely {{tlx|Guild}}, the user infoboxes, etc. as well, but that would all come later.

There's some initial discussion between [[User:Djonni|Djonni]] and myself at [[Talk:Djonni#Preview Release!]] for anyone interested, but the real point is that I feel like the effort has progressed far enough to seek commentary and input from a wider audience. 

Anyone interested is welcome to take a look at [[User:FeRDNYC/Sandbox]], which contains a series of Artifact, Equipment, and Monster articles showcasing different possible forms of the new infobox templates for those articles. Where there are differences between them, or different versions of the same thing, it means that I'm trying out different possible formattings. As it says in the intro to that page, any and all input is welcome and encouraged — there's a link to the associated Talk page if anyone has any thoughts, positive or negative, on any or all of the infoboxes shown there. 

'''Most''' helpful to me, at this stage, would be firm preferences of the form, "I like (this formatting) much better than (that formatting), you should definitely go with the first one." But, as I said, ''any'' input is welcome. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 03:50, 29 November 2018 (UTC)

: {{m|started}}

: The new {{tlx|Town}} is now live. I spot-checked a bunch of articles and saw no obvious problems, but if you '''do''', please feel free to use the "T" link in the bottom-right corner of the infobox to access [[Template talk:Town]]. You can report problems or anything else there.

: If all goes well, I'll hopefully take at least {{tlx|Artifact}} and {{tlx|Equipment}} live later today, with {{tlx|Monster}} to follow shortly after. Thanks especially to {{god|Djonni}} and {{god|SourceRunner}}, who provided invaluable feedback and advice during testing. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 17:59, 16 December 2018 (UTC)

:: {{m|doing}}

:: {{tlx|Artifact}} and {{tlx|Equipment}} are also now updated. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 02:43, 17 December 2018 (UTC)

::: {{m|done}}

::: With the deployment of {{tlx|Monster}}, the four main article infoboxes are now updated and live. Please use the 'T' link at the bottom of any of them, to report problems on the associated Talk page. Other wiki infoboxes (guild/user-related) will be updated time permitting. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]])

:::: The new infoboxes look SO GOOD in the wild! You put a ''lot'' of work and thought into them and it really shows. Thank you '''''so''''' much for your effort on these.

:::: Amazing what a nice fresh coat of paint will do around the place! -- [[User:Djonni|Djonni]] ([[User talk:Djonni|talk]]) 06:26, 19 December 2018 (UTC)

== A humble proposal ==

This proposal and discussion has been archived to [[Talk:JanuWiki 2019/Archive]].

== Fixes for mobile content layout ==

So, I have an ''idea'' for how to blanket address the general mobile-browser formatting issue of content/headings being hidden by, cut off by, or improperly squeezed in alongside infoboxes and other right-floated elements (like the Archive box on Talk pages), without having to modify individual pages. The ''correct'' way to solve this problem would be with modifications to the site CSS, but lacking the ability to make such modifications I'm proposing the following band-aid fix.

For those not familiar with the issue, see:
* The second, fourth, and sixth images in [https://imgur.com/a/bWh75T4 this set of screenshots] from {{god|S624}}
* [https://imgur.com/a/zDv7djX These screenshots] also from {{god|S624}}
* [https://imgur.com/a/8dTiBXT This screenshot] or [https://imgur.com/a/6JNnEBS this screenshot] from {{god|Terezka}}

I've also written up [[User:FeRDNYC/Administrative requests#Content obscured by infoboxes on mobile|an incomplete technical dissection of the issue]] for those interested. The later update also explains both my initial idea for addressing the issue, and this (rethought) second plan that I'm now proposing. The first plan involved editing each page where content was wrapping incorrectly, whereas the new plan involves only editing the handful of templates which create infoboxes or other floated content.

My proposal is to add an invisible spacer to the end of each template which creates floated content ({{tlx|Monster}}, {{tlx|Equipment}}, {{tlx|Artifact}}, {{tlx|Town}}, {{tlx|Guild}}, {{tlx|Archives}}, etc.), immediately following the floated block. Because this spacer will have a fixed minimum width, if it fits alongside the floated block then it will simply cause an empty paragraph's worth of vertical whitespace at the top-left of the float. However, if there ''isn't'' room for the spacer alongside the float, then it will push any content which follows it (whether headings, body text, etc.) down '''below''' the floated block, preventing any of the uncomfortable layouts seen in the screenshots above.

To visually demonstrate what I'm suggesting, I've created '''[https://imgur.com/a/A47nhQg a screenshot gallery across a range of screen formats and orientations, and various wiki skins]'''. The screenshots present examples of how a test page would render first without, and then with, the invisible spacer. (The location of the normally-invisible spacer is highlighted with a "<code>div</code>" callout in all screenshots starting from the fifth.)

Making this change should fix all affected pages, and hopefully on all affected devices, without any of the individual pages needing to be modified in any way.

Thoughts? -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 14:41, 17 January 2019 (UTC)
:: Seems quite the revolution. It's gonna be a lot to add it to every concerned page, but in the end it will be way better it seems. Great thanks to you! [[User:WardPhoenix|WardPhoenix]] ([[User talk:WardPhoenix|talk]]) 15:02, 17 January 2019 (UTC)

::: Modifying the templates definitely sounds easier/less involved than editing each page. I like the look of the solution, too. Is there a reason behind choosing the fixed width to specifically be 180 px? (That's what I think I'm reading, at least.) It works well, but I'm curious. -- [[User:SourceRunner|SourceRunner]] ([[User talk:SourceRunner|talk]]) 15:11, 17 January 2019 (UTC)

:::: @WardPhoenix: The advantage to the proposed fix is that it specifically ''doesn't'' require modifying every page — only a few templates. The alternative would be to correct every page which is rendering incorrectly, which would indeed be a huge chore. As proposed, as few as two templates need to be edited. (If I decide the right way to go is to stick the fix into {{tlx|Infobox}} itself — rather than the derived templates like {{tlx|Monster}} and {{tlx|Town}} etc. — then that covers 95% of the problem instances in one shot.)

:::: @SourceRunner: The width is specified as <code>15em</code>, so the exact size will vary based on device resolution, but the actual value is basically arbitrary. Its effect is to impose a required (minimum) width for the area to the left of a floated template, before it's allowed to have content placed alongside. The width used is certainly open to adjustment — my goal is to find a value that's wide enough to prevent situations like [https://i.imgur.com/NIdHi8t.png this] or [https://i.imgur.com/7g9Alrb.png this], without leaving excessively-large blank areas next to infoboxes and the like. (Keeping in mind that any ''headings'' that are allowed to render in that space will be cut off unless the space is wide enough to wrap all of the words into it.)

:::: Basically, I'm trying to avoid creating either of these situations:
<div style="border:1px solid gray;padding:0.2em;width:20em;float:left;margin-right:1em;margin-left:8em;">
<div style="float:right;background-color:#88f;width:15em;height:8em;"> </div>
<div style="display:inline-block;min-width:4em;height:1px;"> </div>
<div style="font-size: 1.5em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA; overflow: hidden;">Too narrow, heading truncated</div>
</div>
<div style="border:1px solid gray;padding:0.2em;width:20em;float:left;margin-right:1em;">
<div style="float:right;background-color:#88f;width:5em;height:8em;"> </div>
<div style="display:inline-block;min-width:16em;height:1px;"> </div>
Too wide, content pushed out when it could comfortably fit alongside.
</div>
{{clear}}
:::: ...Keeping in mind that the width of the left-hand space in those boxes will vary by quite a lot, based on factors like screen size, orientation, etc. Choosing the right <code>min-width</code> value to achieve the proper balance is completely a matter of intuition / trial-and-error. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 19:04, 17 January 2019 (UTC)

::::: (By using a width in <code>em</code> units, the size of the spacer is defined based on the font size in use. Specifically, it's the width of 15 letter 'm' characters. So, currently, the minimum available space to render text to the left of floated content would be this large: <span style="white-space:no-wrap;background-color:black;color:#3f3;">mmmmmmmmmmmmmmm</span>.) -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 19:12, 17 January 2019 (UTC)
: This seems to have introduced a new problem, at least on my iPhone 5S using the vector skin. The info box now appears not at the top, but after the first paragraph, so sometime half way down the page, and also, the box is cut off on the right side of the screen. Here’s a screenshot of the problem : https://imgur.com/a/2TTpUYv —[[User:Holy Spirit of Hell|Holy Spirit of Hell]] ([[User talk:Holy Spirit of Hell|talk]]) 02:16, 18 January 2019 (UTC)

:: @HSoH: This hasn't been done yet, so nothing's changed. That's just how the mobile skin lays the page out. The first content paragraph (the same one that would come before "Contents") gets placed before the infobox, in the mobile Vector rendering. (Doesn't happen with WPTouch, the mobile "Desktop" view.) That's another thing that's beyond our control.

:: If it seems like things have changed recently with a certain article's layout, most likely it previously had a JanuWiki header. When the header is in place, ''it'' becomes the "first paragraph", so the infobox renders immediately after it. Remove the header, and the first content paragraph moves up above the infobox. Been that way all along, and nothing we can do about it, alas. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 02:30, 18 January 2019 (UTC)

:: The infoboxes sticking off the left edge of the screen in the mobile app, that's also been happening all along, to varying degrees on various devices. It only happens in the Godville app browser — load the same page in mobile Chrome or Firefox, and it renders perfectly. I have no idea what the devs are doing to break page layout in their mobile app, but <span style="font-family:monospace; font-weight:bold;">¯\_(ツ)_/¯</span>. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 02:30, 18 January 2019 (UTC)

::: No, this is definitely a new issue, it happens on all info boxes and all skins and did not look like this before. Before today, infoboxes were only slightly cut off, with the words sitting right on the margin, still legible. And the info box appearing halfway down the page is also something new and appears on all pages, even ones that haven’t been recently changed. Though if nothing about the info boxes themselves has changed, I have no clue what the cause could be. 

::: I’ve now noticed that the pages do have the correct layout on the mobile version of the desktop, but the infoboxes are still the same. —[[User:Holy Spirit of Hell|Holy Spirit of Hell]] ([[User talk:Holy Spirit of Hell|talk]]) 19:31, 18 January 2019 (UTC)

::: On further experimentation, the page and all others render the exact same way in mobile Firefox and Chrome, it is broken in every fashion that I can access it with my iPhone 5S. Furthermore, using the mobile ‘desktop’ version, the infoboxes have shifted even further to the left side of the screen, cutting off more text, something has definitely changed [[User:Holy Spirit of Hell|Holy Spirit of Hell]] ([[User talk:Holy Spirit of Hell|talk]]) 21:06, 19 January 2019 (UTC)

:::: I think that's a great and clever solution with the tools that are available! Even though it's a band-aid fix, I think it looks good and serves its purpose well. --[[User:Terezka|Terezka]] ([[User talk:Terezka|talk]]) 20:23, 18 January 2019 (UTC)

::::: Agreed on good workaround. Congrats [[User:FeRDNYC|FeRDNYC]]. -- [[User:S624|S624]] ([[User talk:S624|talk]]) 20:27, 18 January 2019 (UTC)

{{outdent|:::::}} Thanks, all. This fix is now in place for {{tlx|Archives}} and all templates based on {{tlx|Infobox}}: {{tlx|Monster}}, {{tlx|Equipment}}, {{tlx|Artifact}}, {{tlx|Town}}. (That list will expand to include {{tlx|Guild}} when I release the new Guild template — see [[User:FeRDNYC/Sandbox]] — which will most likely happen some time this weekend.) I'm not planning to screw around with other templates like {{tlx|Usergod}}/{{tlx|Usergoddess}} or {{tlx|Hero}}, for the moment. If anyone can think of any right-floated templates '''other''' than the ones I just mentioned which would be candidates for this fix, please let me know. I'm currently not coming up with any.

The {{tlx|spacer}} addition can be disabled on any page where it's causing a problem by adding {{para|spacer|no}} to the template arguments, and it can be disabled globally by undoing the appropriate edit at [[Template:Archives]] and/or [[Template:Infobox]]. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 15:38, 19 January 2019 (UTC)

: Re: {{god|Holy Spirit of Hell}}'s comments, above, which use the [[Beerburglar]] page as an example (but are '''not''' limited to that page, I understand)...

: {{tqb|Before today, infoboxes were only slightly cut off, with the words sitting right on the margin, still legible. And the info box appearing halfway down the page is also something new and appears on all pages, even ones that haven’t been recently changed. Though if nothing about the info boxes themselves has changed, I have no clue what the cause could be.}} 

: You can see from the edit history for [https://wiki.godvillegame.com/index.php?title=Template:Infobox&action=history Template:Infobox] and [https://wiki.godvillegame.com/index.php?title=Template:Monster&action=history Template:Monster] that, before today (the 19th), the most recent changes of any sort were 6 days ago on the 13th (for [[Template:Infobox]], not counting that edit on the 14th to undo the previous change), or 10 days ago (for [[Template:Monster]]) — nothing changed on the 18th (the day your "Before today" referenced) at all. 

: Those changes on the 13th '''''could've''''' affected infobox layout on the iPhone, though they ''shouldn't'' have since I just removed some DIVs that were put in place for the old Minerva mobile skin that's not in use anymore. More likely to have affected layout would be the changes on the 9th, which did involve changes to widths and font sizes. But if anything's been changed more recently than that, it must've been done outside of the wiki content.

: {{tqb|On further experimentation, the page and all others render the exact same way in mobile Firefox and Chrome, it is broken in every fashion that I can access it with my iPhone 5S. Furthermore, using the mobile ‘desktop’ version, the infoboxes have shifted even further to the left side of the screen, cutting off more text, something has definitely changed}}

: Yeah, sorry, that was me being unclear. The thing about Firefox/Chrome was Android-specific; it wouldn't apply to iPhone since [https://www.howtogeek.com/184283/why-third-party-browsers-will-always-be-inferior-to-safari-on-iphone-and-ipad/ all web browsers on iPhone use the Safari layout engine], so differences would not be expected or... well, ''possible'' really. 

: And as far as the iPhone, I'm still milking that free BrowserStack trial, and its screenshot service corroborates your experience regarding the cut-off infoboxes on iPhone 5 ([https://imgur.com/a/prOgKo2 screenshots]) — but notice that it's ''only'' on iPhone 5, at least of the devices represented. (A sadly very limited list which I have no control over, now that I've exhausted the live-testing portion of my free trial.)

: But on the question of '''why''' it's rendering like that on the iPhone: I have no idea, sorry. I don't have an iPhone or have access to an iPhone, and since I don't have any way to test on iOS devices (or a reasonable substitute) anymore, I don't have any way to reproduce or examine the issue. Which does not occur on any devices I '''do''' have access to.

: Just looking at the screenshots, it sort of ''looks'' like the issue could be related to the image size, like it's too large for the display... but I last changed '''that''' [https://wiki.godvillegame.com/index.php?title=Template:Infobox_image&action=history on December 9] so it would be weird if it's only coming up now. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 23:26, 19 January 2019 (UTC)

:: {{god|FeRDNYC}}, the display size on the SE, which your simulator shows working correctly, if shifted downwards, has the same display size, so I don’t think the image size is the problem. The difference is in the processor and the RAM, with the SE being a lot more powerful, so that probably has something to do with it. 


:: I’m not sure that I’ve looked at any normal GodWiki articles between the 13th and the day of my first reply, so the formatting change could be what has shifted the infoboxes, since there it has changed and there seems to be nothing else that could have caused it —[[User:Holy Spirit of Hell|Holy Spirit of Hell]] ([[User talk:Holy Spirit of Hell|talk]]) 01:55, 20 January 2019 (UTC)

::: Ah, sorry — the Imgur captions are ''below'' the images they respond to, so the '''first''' screenshot with the shifting-off-the-left-edge issue is actually the iPhone SE. I misremembered which model it was because 5 and S look the same and Apple's naming scheme is fucking moronic. All the ''rest'' of the screenshots are different Android devices. (The "Shifted down" on the next image — the Nexus 5 — is just because BrowserStack's Android device testbeds don't assemble long web content screenshots seamlessly, so there are visible page breaks every screen-length... the first of which happens to fall right before the infobox, on that device.)

::: If it's possible the issue started on the 13th, then it could be the removal of those DIVs I suppose. In which case, that sucks, because they were causing crazy-excessive margins around the infoboxes on desktop, so they really need to not be there. (They were never ''correct'' in the first place, I was abusing the CSS of the now-disabled mobile skin to avoid a table-sizing issue.) I'd suggest reporting the issue with infobox layout on iOS to the Godville devs. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 04:49, 20 January 2019 (UTC)

== Formatting g.e. dates ==

Inspired by the work {{god|WardPhoenix}} and {{god|SourceRunner}} were doing on the [[Godbuster]] article, which makes excellent use of g.e. dates, I realized that we should be doing more to assist with and standardize the formatting of those dates. (Why this article in particular triggered the idea, I can't say, but it happened to strike me while reading it.) Basically:
# The dates and the "g.e." after them should really be connected ''by a '''non-breaking''' space'', so they won't be broken up by line-wrapping.
# That's something that a template can easily take care of.

My initial idea was to just change template {{tlx|ge}} so it would add "<code>&amp;nbsp;g.e.</code>" to the end of the output, but it's used all over the wiki in places where it's expected '''not''' to do that, and it would be a massive pain to change them all.

Instead I hacked up a new template {{tlx|date ge}} — it works like {{tlx|ge}} in many ways, '''except''' it always appends "<code>&amp;nbsp;g.e.</code>" to its output, and you can use {{tlx|date ge|<var>number</var>}} to format a g.e. date without conversion.

So, to borrow some examples from [[Template:GE/Documentation#Examples of use|the documentation]]:
<div style="margin-left:1.6em;border:1px solid #888;padding:0.2em;">
;<code><nowiki>[[</nowiki>Godville (game)|Godville]] was born on {{tlf|date ge|ge{{=}}0}}!</code> {{nobold|''appears as:''}}
: [[Godville (game)|Godville]] was born on {{date ge|ge=0}}!

;<code>The 5th of August 2013 was {{tlf|date ge|1183}}</code> {{nobold|''appears as:''}}
:The 5th of August 2013 was {{date ge|1183}}

;<code>The 15th of December 2011 was {{tlf|date ge|12|15|2011}}</code> {{nobold|''appears as:''}}
:The 15th of December 2011 was {{date ge|12|52|2011}}
</div>
'''TL;DR''': Basically,
# Anywhere you're writing "<code><var>number</var> g.e.</code>", you can instead use {{tlx|date ge|<var>number</var>}} and the date will be formatted properly to protect against line wrapping. 
# Anywhere you're writing "<code>{{tlf|ge|<var>mm</var>|<var>dd</var>|<var>yyyy</var>}} g.e.</code>" can become "{{tlx|date ge|<var>mm</var>|<var>dd</var>|<var>yyyy</var>}}" to take advantage of the same protection.
And to illustrate the main reason for this template (besides the fact that typing "<code>&amp;nbsp;g.e.</code>" constantly is a pain), here's the difference vs. just typing "{{tlx|ge|1|26|2019}}<code> g.e.</code>" or "<code><var>number</var> g.e.</code>" with a normal space:
<div style="margin-left:1.6em;border:1px solid #888;padding:0.2em;width:9em;float:left;">
Before:<br>
:Written&nbsp;on&nbsp;{{ge|1|26|2019}}<br>g.e.
</div>
<div style="margin-left:1.6em;border:1px solid #888;padding:0.2em;width:9em;float:left;">
After:<br>
:Written&nbsp;on<br>{{date ge|1|26|2019}}
</div>{{clear}}
-- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 21:26, 26 January 2019 (UTC)

== Activation cost in Artifact infobox ==

The {{tlx|Artifact}} template now supports a {{para|cost}} parameter, used to specify the activation cost of [[activatable artifacts]]. Possible values are:
:{{para|cost|0}} – Requires no godpower to activate (can also be: <code>free</code>,<code>none</code>,<code>0%</code>)
:{{para|cost|50}} – Requires 50% of godpower to activate (can also be: <code>50%</code>)
See it in use at [[Subplot thickener]].
-- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 23:02, 26 January 2019 (UTC)