Talk:Main Page

From GodWiki
Jump to: navigation, search

This is the talk page for discussing improvements to the Main Page article.
This is not a forum for general discussion about the article's subject.

Article policies
  • Opinionated research if possible
  • Neutral point of view when appropriate
  • Humour
  • Verifiability
  • Be polite
  • Assume good faith
  • No personal attacks
  • Do not bite the newcomers
  • Respond in a mature manner
  • Be welcoming
  • Maintain civility at all times


This page has an /Archive

Old and/or inactive discussions have been moved to the archive subpage.

New convenience template for referencing Godville Blog posts

Since the Godville Blog is one of the few outside resources we ever cite as a reference on this wiki (see History, especially), and in the interest of encouraging more of that (where appropriate), I've created a new convenience template {{Cite blog}} for creating links to Godville Blog posts.

Just give it a post number, and it'll create a link to that post. If you leave out the post number, it'll just provide a general link to the blog (as seen in my opening paragraph):

Wikicode Renders as
{{Cite blog|117}} Godville Blog, post 117
{{Cite blog|116|To the Point}} Godville Blog, post 116: To the Point
{{Cite blog}} Godville Blog

More documentation, including an example of how the template can be used in creating citation references in articles, can be found on the template page. I may add additional parameters, like the ability to provide a title for the linked post, if there's any interest. -- FeRDNYC (talk) 13:50, 1 September 2018 (UTC)

Worth mentioning that God Djonni later added the ability to include post titles as well, for even nicer citation formatting. See the second example in the table above. -- FeRDNYC (talk) 23:04, 14 November 2018 (UTC)

Main Page styling tweaks

I just tweaked a bunch of style/layout code on the Main Page, all minor changes individually but they add up to a perceptible difference, hopefully for the better. In case anyone notices there have been changes and is curious what they were, details of the changes made:

  • Styling of section boxes cleaned up:
    • The heading is now "attached" to the border on three sides, and shares its color; hopefully that looks a bit cleaner
    • Some boxes had mismatched header/border colors, I've fixed all that up
    • The inner spacing/margins was also inconsistent between boxes, now they use identical outer margins and (except for 'Random Image') identical internal padding
  • Section colors updated:
    • 'Random Image' now matches: purple header/borders, light purple background (the background and borders were light blue, before)
    • 'Did You Know?' now has a color scheme of its own, in shades of orange (just because)
    • The blues of 'Intro...' are bluer, the greens of 'Featured...' are greener
  • The boxes no longer touch each other (it always looked weird with the different border colors)
  • 'rem' units are used much more extensively (rather than 'em' or 'px'), which should give more consistent scaling

I should really make a "Godwiki Announcements" template/page for this stuff, instead of stuffing it on the Talk page. -- FeRDNYC (talk) 00:51, 8 September 2018 (UTC)

Deprecation of Template:Pet

Following some discussion, we've decided to retire the {{Pet}} template, and instead use {{Monster}} for all Monster articles (including Boss-Monsters and Pets), so that improvements will be shared among the various types automatically.

I've placed the following notice at the top of the {{Pet}} documentation:

Important.png

This Template Is Deprecated — USE {{Monster|pet=yes}} INSTEAD

{{Monster}} can now create Pet infoboxes (since all Pets are Monsters), it should be used instead of this template. The syntax is exactly the same, simply add |pet=yes to the code. So, for example...
OLD: {{Pet|image=example.jpg |description=A beast |levels=12-32 |totem=A Guild}}
NEW: {{Monster|image=example.jpg |description=A beast |pet=yes |levels=12-32 |totem=A Guild}}
See Template:Monster for full documentation.
This change will allow Pet articles to benefit from any improvements made to {{Monster}}.

I'll go through and convert the existing Category:Pets articles that use {{Pet}} over to {{Monster|pet=yes}} when I can (except for Alpha Centaur which is already converted), but please use {{Monster|pet=yes}} on new Pet articles (or updated ones), and feel free to convert any uses of {{Pet}} that you happen to come across. Thanks! -- FeRDNYC (talk) 00:52, 18 September 2018 (UTC)

Oh, and just for the record, |pet= can actually be set to any common positive-state value, so |pet=y, |pet=true, |pet=1, |pet=on, etc. are all just as good. -- FeRDNYC (talk) 00:55, 18 September 2018 (UTC)

Yellowtick.png Partly done — I'm now about 2/3 of the way through the Pet articles, 15 more to go. -- FeRDNYC (talk) 00:46, 19 September 2018 (UTC)

Tick.png Done — As of now, there are no articles on the wiki containing {{Pet}} transclusions. All Pet articles which feature an infobox are now using {{Monster|pet=yes}}. Please stick to that format when updating or adding new Pet articles. {{Pet}} should no longer be used. -- FeRDNYC (talk) 21:00, 20 September 2018 (UTC)

New, reformatted Omnibus List

Tick.png Done - The new Omnibus List design is live.

Previous update
See today's announcement at Talk:Omnibus List regarding a new version of the Omnibus List that's now in testing. It uses a modernized, responsive (size-adaptive) layout, to better fit screen sizes both large and small.
A testing/demo version of the new Omnibus List can be found at: User:FeRDNYC/Sandbox
Please leave any/all feedback at Talk:Omnibus List. -- FeRDNYC (talk) 01:00, 22 October 2018 (UTC)

-- FeRDNYC (talk) 13:42, 29 October 2018 (UTC)

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:

  • {{He-or-She}}: You'll get either He or She, chosen at kinda-random.
  • {{he-or-she}}: You'll get either he or she, chosen at kinda-random.

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

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

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

There's more information (and an important note about an error I can't fix, which could cause you to panic unnecessarily) in the documentation for {{he-or-she}} (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 she, her, hers, 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:

  • {{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 {{She-or-He}}, etc. That set expands out to another 10 templates, plus 6 more for {{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 {{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, here, or by direct message on Godville. -- Djonni (talk) 13:46, 1 November 2018 (UTC)

I've used the {{he-or-she}} family of templates in today's update to the 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 he 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 undo the edit where I put them in, and to explain the problem here for us. -- Djonni (talk) 10:56, 2 November 2018 (UTC)
Ideaicon.png Idea: It wouldn't be difficult to implement a parameter |daily=anything that will switch the gender every day. I kind of like that idea, it's perfect for use cases like the Main Page etc. -- Djonni (talk) 11:18, 2 November 2018 (UTC)
Tick.png Done The existing set of templates now support a parameter, |daily=anything, 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) 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.)
Smiley.png Thank you 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 ({{she-or-he}} 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 |reverse=anything option, so that improvements are less arduous. (Perhaps I should simply implement a master function ({{m-or-f}}?) which takes |male=him and |female=her text inputs? Then behaviour changes would be completely consistent to the entire set. Hmmm.) -- Djonni (talk) 13:15, 3 November 2018 (UTC)
Tick.png Done Instead of making an entire set of {{she-or-he}}, each of the gender-selection templates now supports the |invert=anything 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 {{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 {{his-or-her}} and {{His-or-Her}} to the set. So now, she can hold his 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 -- Djonni (talk) 17:05, 3 November 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── If you can propose a sensible way that I can promote inclusion of non-binary gender anywhere then I'm honestly all ears 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 {{dicks-and-or-vaginas}}. -- 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.) -- 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 heroines and heroes, 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. :) -- Djonni (talk) 14:09, 4 November 2018 (UTC)
Cross.png "Not that there's anything wrong with that!"
Tick.png "No, of course not!" -- FeRDNYC (talk) 19:57, 5 November 2018 (UTC)

Guild infoboxes now automatically link to guild pages

Djonni had the excellent idea to have {{Guild}} generate links to guild pages automatically, instead of requiring a |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 |stats=no argument to the {{Guild}} template will disable the automatic link generation.

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

For most Guild articles, |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 |stats= if it's already set.)

The other link parameter, |forum=url, 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. -- 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 {{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 {{decorate artifact}}, but more convenient wrappers have been created for known Godville decorations:

  • {{pumpkins}}: for decorating Halloween artifacts, e.g.
{{pumpkins|[[golden pumpkin]]}}🎃golden pumpkin🎃
  • {{party}}: for decorating celebration-related artifacts (like the anniversary specials), e.g.
{{party|[[3000-days gold coin]]}}🎉3000-days gold coin🎉

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

  • {{turkey}} was aded for Thanksgiving, and produces the first one-sided decoration:
{{turkey|[[roasted turkey]]}}🦃roasted turkey -- FeRDNYC (talk) 04:13, 4 December 2018 (UTC)

A new link template for Guild pages

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

The same way: {{God|God name}} => God God name

You can now use: {{Guild link|Guild name}} => ⚜️ Guild name

(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: {{Guild link|Bobius}} => ⚜️ Bobius

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

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

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

And a new link template for Pantheon positions...

... just to complete the set!

{{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 God or 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 {{God|God name}} => God God name
and {{Guild link|Guild name}} => ⚜️ Guild name,

now {{Pantheon link|pantheon}} => 🏆 Pantheon of Pantheon

And, more usefully, to link to a specific pantheon position:
{{Pantheon link|pantheon|15}} => 🏆 Pantheon of Pantheon: 15th.

As with the shield in {{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:

{{Pantheon link|taming|237}} => 🏆 Pantheon of Taming: 237th
{{Pantheon link|savings|20|text=short}} => 🏆 Savings: 20th
{{Pantheon link|wood|1102|plain=yes}} => Pantheon of Arkeology: 1102nd
{{Pantheon link|storytelling|51|text=none|plain=yes}} => 51st
[[Pantheon of Gratitude]]: '''{{Pantheon link|gratitude|123|text=none|plain=yes}}''' => Pantheon of Gratitude: 123rd

More details and examples are in the documentation at the {{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. -- Djonni (talk) 13:16, 13 November 2018 (UTC)

Sign template updates requiring page edits

Important.png

This template needs to be fixed

These fixes will require the editing of Guild articles by a non-Guild-member (specifically, me — 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 {{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 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 {{Sign}} in Godwiki articles.

What this means for you (the editor of an article containing {{Sign}})

  1. If your article contains a sign transclusion with parameters like {{Sign|bordercolor=red}} or {{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 |bgcolor=, |bordercolor=, or |outerbordercolor= arguments so that the sign will use the default values, like it was previously.
  2. If your article contains a transclusion with parameters like |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. |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 {{Sign}} parameters only.

If there are any affected {{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... -- FeRDNYC (talk) 21:56, 18 November 2018 (UTC)

Yellowtick.png Partly done
The color-parameter changes are complete. {{Sign|bgcolor=|bordercolor=|outerbordercolor=}} now accepts any valid CSS color string, e.g. |bgcolor=red or |bordercolor=rgb(100,150,0). If specifying color by hex color value (i.e. #RGB or #RRGGBB), you must include the leading # sign.
Guild pages edited
The only change that remains to be done is the fix to |imgwidth=, and the only page that will be affected there is Open Bar (again). I'll get to that another time. -- FeRDNYC (talk) 00:24, 23 November 2018 (UTC)

Default picture and auto-templating for Artifact and Monster infoboxes

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

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

I tried to also get all of the {{Monster}} articles which contained manual {{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 "{{Picture}}" template, as the infobox is now automatically supplying it. -- FeRDNYC (talk) 02:45, 23 November 2018 (UTC)

Navbar line on navboxes

Now that we have a {{Navbar}} template (which I imported for use with the new {{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 {{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:

Auras
Standard Auras Abstinence Audibility Baiting Bliss Concussion Confusion Curiosity Hoarding Huckstering Hunting Immortality Pacifism Rage Reviving Totemism Trail
Event Auras Censorship Overcensorship Spookiness ██████████‎

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 {{Navboxauras}} becomes the target of increased problem editing.

Let me know if anyone has any thoughts or objections. -- 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. -- Djonni (talk) 16:16, 25 November 2018 (UTC)
Hmm, that's definitely an option technically, so yeah that could be one way to go. -- FeRDNYC (talk) 05:27, 26 November 2018 (UTC)

Preview Rollout of new Infoboxes

For a while now, I've been working on adapting the master {{Infobox}} code from the English Wikipedia for use here at the GodWiki, with the aim being to reimplement our Infoboxes. Using {{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 {{Town}} would also be updated, and most likely {{Guild}}, the user infoboxes, etc. as well, but that would all come later.

There's some initial discussion between 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. -- FeRDNYC (talk) 03:50, 29 November 2018 (UTC)

Started.png Started
The new {{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 {{Artifact}} and {{Equipment}} live later today, with {{Monster}} to follow shortly after. Thanks especially to God Djonni and God SourceRunner, who provided invaluable feedback and advice during testing. -- FeRDNYC (talk) 17:59, 16 December 2018 (UTC)

A humble proposal

TL;DR
I think the GodWiki's (just about) ready for an event around creating content and bringing new, inexperienced, dormant or aspiring content creators from the general player population across the threshold. I talk about the general concept, getting involved, what needs to happen first, but to cut to the actual plan, start here.

This edit by God Terezka, nominating Special:WantedPages for the Feature Article, got me thinking.

A huge amount of effort (and thousands and thousands of Talk bytes) has gone into renovating and improving the GodWiki recently, after a long period of neglect as various major early contributors and editors became inactive over the years. A portion of the player base has definitely noticed this reinvigoration, and it might be my imagination but I feel like overall engagement with the wiki has been slowly creeping upwards.

As we know, the majority of active users are still doing one of two things: contributing to their own (guild/god/hero) pages, and contributing to the Omnibus & List pages. But non-trivial contributions to creative content on the GodWiki is less common, even among those of us who use the wiki on a regular or semi-regular basis.

So, here's my humble proposal for discussion and consideration: A GodWiki New Years Resolution — a January Content Drive.

I think the time is ripe for a little fanfare, relaunching a refreshed GodWiki to the player community at large. But first:

  1. There need to be enough people who think this is a good idea that it has enough momentum to carry it through the month (and doesn't rely on any one person too much, as real life always takes precedence);
  2. We need to agree that the GodWiki's ready to have a spotlight shone on it, which I think will need us to reach some milestones; and
  3. We need to agree on what we'd actually do! :)

If it went ahead, I would think of a content drive for January as an experiment, to see if doing this kind of thing regularly might work.

1. Enough people involved. By "involved", I mean in helping me to think through, preparing for (see next), and carrying an event across the month of January: shaking the pompoms and posting updates in the forums, keeping track of created content on a dedicated page (see below), just little things like that. The metric for this would be if folks are participating in this talk topic, to make suggestions, express interest or concerns, what have you (in other words, if you'd like this to happen, say so!). If this idea gets no love, I'll archive it myself and we can carry on with business as usual. I don't expect the sort of thing I have in mind would be very demanding of anyone's time, but if it's being driven by just one person and that person disappears unexpectedly for half of the month (if, say, for example, that hypothetical person were juggling two new jobs, settling into a new home, what have you), well, that would be a failed experiment.

2. Is the GodWiki ready: There are a few projects that are being tinkered with that would need to be in at least a final draft stage (with stable parameters and behaviour), otherwise we'll end up giving new editors a confusing, unstable experience, whereas I'm hoping to give people who're inexperienced contributors to the Wiki a great experience. Here's a non-canonical collection of what I've thought of as preconditions to aim for, in descending order of importance in my mind:

3. Yeah, yeah, what's the actual idea, Djonni? God you write a lot of bullsh... words sometimes: My first thought, though I'm certainly open to other ideas, would be to structure a content drive around a content theme. As I mentioned above, if it went well there's no reason that later content drives couldn't happen for different themes.

Some ideas for a theme for a January content drive:

  • Every heroine and hero's favourite theme: Beer! — Votes from: Djonni (talk)
  • Seasonally relevant: Winter — Votes from:
  • Insert additional ideas here

(Please feel free to expand the list or cast a vote above by adding your name. Pro-tip: Three tildes (~~~) will automatically insert your name.)

I imagine we would put together a wiki page for the event where we list wanted content within the scope of the theme, articles not yet created, stubs, and pictures needed. When someone creates or contributes content for the theme, we (or they themselves) can update the list giving the author recognition (more visible and permanent than the page's history or the recent changes list).

Here's a content survey of the proposed theme:

Beer
Monsters
Artifacts
Equipment
Quests
Other

Probably everything in Navbox taverns:

Loosely related

I imagine a few ways to keep the content drive going through the month.

1. The forums. Announcement of the content drive and, assuming there's any response, regular updates on what's going on. This would probably be restricted to Wiki Questions Thread. I'm happy to take lead on the forum launch, but I'm equally happy for someone else to if you're keen.

2. A tracking page. Designed and probably maintained by a handful of us. Text about the content drive, establishing expectations, emphasising wiki values (Be Bold, be respectful, write to your best ability — I don't want to exclude people for whom English isn't a first language, etc), pointers to how to get started (see guidelines and manuals Todo, above), and a table tracking progress. Perhaps use {{diaryquest}} for some dressing.

I imagine a table that might look a bit like this (up for discussion, of course):

January Content Drive (as at ~~~~~)
Type Article Created By
Monster Beer Golem
Monster Beerburglar God Djonni(U • C • T)  ⚜️ The Forsakens Lament
...

Other columns ("Additional edits by", etc) may become relevant as the month proceeds, but no need to overcomplicate it to begin with.

3. Stimulate some friendly inter-guild rivalry. I think there are some guilds that would be pretty enthusiastic about waving their banner on this! And so I think a guild leagues table would be fun. This might need some points system, perhaps loosely emulating the Pantheon of Adventure, details to be worked out. Something like this at the top of the page might be enough to get a few guild councils talking, and a few guild leaders rabble-rousing.

Guild Leagues (as at ~~~~~)
Guild Points Emblem
⚜️ Guild 1 100 [[File: Emblem from guild wiki page|5em|link=Guild wiki page]]
⚜️ Guild 2 80 [[File: Emblem from guild wiki page|2em|link=Guild wiki page]]
... 2em

4. Partial hijack of the Main Page. I thought that a hijacking of {{Mainpageintro}} for the month would help too, for those who come to the GodWiki but don't frequent the forums and don't read Talk pages.

Anyway, this is more than enough words for now. If you like the general idea, and would like to see it go ahead in any form, let us know here. Here, I'll make it easy — copy this: 👍 -- ~~~~, click this, and paste it at the very bottom of the page!

Side Job

As suggested by God SourceRunner here, there may be a side job to reward editors for quality edit[s] to improve articles written by others in the content drive.

  • This would probably require allocating articles to editors, to avoid collisions and give fair chance to those not always online/checking
  • What constitutes a quality edit is the sole discretion of the judge, God SourceRunner, but guidelines will be clear
    • Preserve authors intent, respect authorial voice
    • Spelling, grammar, punctuation
      • Do we need an official style guide?
    • Technical edits (just fixing templates, categories, whitespace/layout, etc) are separate to these edits
    • Edit summaries are required
  • Contributing editors, participating editors, whatever we call them, would volunteer and nominate themselves
  • An author may request a review of their article, or an article may be chosen (by whom? SourceRunner, myself?) for review
    • Perhaps a {{Sign}} or two might be needed...

Perhaps other Side Jobs might stimulate some creativity (as well as some guild points and bragging rights). Some possibilities:

  • Create one full new article with image in each of the Monster, Artifact, and Tavern groups
  • Write an article that makes reference to 3 other content drive pages that you have either created or improved

Comments

  • I didn't get through nearly all of this yet, because it is very long, but also part of the reason is that I'm on my phone and it kind of sucks to read there. In the spirit of drawing people in and making things accessible, please reformat:
    • That box next to the intro, because 50% of the width of a phone screen is tiny and ugly
────────────────────────────────────────────────────────────────────────────────────────────────────
Tick.png Done, hopefully, ironically I'm also on my phone right now so can't properly check desktop 😇 --Djonni (talk) 00:38, 7 December 2018 (UTC)
────────────────────────────────────────────────────────────────────────────────────────────────────
  • The tables, which end up with columns too narrow to read.
────────────────────────────────────────────────────────────────────────────────────────────────────
Started, will look again in the morning --Djonni (talk) 00:38, 7 December 2018 (UTC)
────────────────────────────────────────────────────────────────────────────────────────────────────
I will sit down and read this later when I'm at my computer, but a lot of people only access the wiki via the phone app. -- FeRDNYC (talk) 00:04, 7 December 2018 (UTC)

Navbox and other technical details

A draft navbox for content drive pages, intentionally eye-catching:

🍺 JanuWiki 2019 🍺
🍺 En-Lager-ing the GodWiki 🍺
Complete article • ✒️ Stub • 📷 Picture required
Monsters Ale-chemist 🍻 Boozerker 🍻 Barbeerian 🍻 Beer Cub 🍻 Beer Golem 🍻 Beer Hunter 🍻 Beer Mugger 🍻 Beerburglar 🍻 Beerkat ✒️📷 🍻 Beerserker 🍻 Beerwolf ✒️📷 🍻 Boartender ✒️📷
Artifacts Bar tab 🍻 Beer-battered beer 🍻 Beer-scented soap ✒️📷 🍻 Bottle of beer from a wall 🍻 Bottle of domesticated beer 🍻 Bottle of holy ale 🍻 Dungeon brew 🍻 Exclamation pint 🍻 Fairy ale 🍻 Flask of witch's brewski 🍻 “Free beer” ticket 🍻 Instant beer tablet 🍻 Pint of no return 🍻 Portable beer cooler 🍻 Pot of strange brew 🍻 Strange brew 🍻 Vanishing pint 🍻 “Wish you were beer” postcard
Equipment Bartenderizer 🍻 Beer goggles
Quests Deliver some sour gnomish beer to the dark elves 🍻 Find out how to turn a golden brick into a pint of beer 🍻 Sing all of “99 bottles of beer on the wall!” 🍻 Sit in a tavern and write fake diary entries 🍻 Brew a storm in a teacup
Skills Beer belly ✒️📷
Taverns All Inn The Battle Toad Boatmurdered Caravanserai The Den of Iniquity The Drunken Clam Dunquestin The Glass Cannon Khaki-colored Dragon The Mended Drum Molotov's Cocktail Bar Progress Bar The Rumor Mill The Rusty Goblin Shepherd’s Stuff Space Bar The Sword & Sandal The Whinery

-- Djonni (talk) 07:35, 11 December 2018 (UTC)

A draft navbox for content drive pages, intentionally eye-catching

Well it's certainly eye-catching, I'll have to give you that. -- FeRDNYC (talk) 21:39, 14 December 2018 (UTC)
P.S> Are eyes supposed to bleed when caught? Asking for a friend. -- FeRDNYC (talk) 21:40, 14 December 2018 (UTC)
In all seriousness, though, due to the extremely high number of red links, specifically, I'm really not sure "yellow-tan-ish" is the best background color for the list cells. That's kinda hard for me to read, I can't imagine how it looks to someone with color-impaired vision. -- FeRDNYC (talk) 21:43, 14 December 2018 (UTC)
Message received! You make a good point about vision impaired users. Reprised the draft to tone down everything but the title area — still, I think, attention-getting without being so... exsanguinary. -- Djonni (talk) 17:44, 15 December 2018 (UTC)
Woohoo! Oh, contrast, how I've missed you! -- FeRDNYC (talk) 18:23, 15 December 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────

Draft hatnotes for works in progress or under review:

75px-WrenchTF2.png

JanuWiki Article Under Construction

This article is the target of the creative efforts of {{{author}}} as part of the JanuWiki 2019 Content Drive. If you have a [[technical edit]] to make, please write a clear edit summary (beginning with "Technical edit:"), or speak to a [[contributing editor]].

Last edit: today by FeRDNYC. See history.

Stub sign.png

JanuWiki Article Under Review

This article by {{{author}}} in being reviewed by {{{editor|editors}}} as part of the JanuWiki 2019 Content Drive. If you have a [[technical edit]] to make, please write a clear edit summary (beginning with "Technical edit:"), or speak to a [[contributing editor]].

Last edit: today by FeRDNYC. See history.

Perhaps another for completed articles whose points have been counted towards totals, so authors can easily see that they've been credited for the work. This type of this might be a nice image for that (or for some other use in the event), though the file at that link is not free for reuse (so can easily make something similar). -- Djonni (talk) 12:56, 16 December 2018 (UTC)

Responses

  • As far as new infoboxes (I saw something go by about that), I can have those ready in, as you say, "final draft" form within 3-5 days at the outside. (Also add {{town}} to the list, because there's no point in a redesign without our most consistently used infobox.)
Regarding the main page, though, rather than changing the intro box, I'd suggest adding an additional banner above the featured/intro boxes, something that'll obviously stand out as different and changed. I honestly don't think most wiki visitors would even notice if the intro box changed. I can put structure together for that with only a day or two notice, if the content is relatively straightforward.
That's all I caught in a quick skim, like I said more later. -- FeRDNYC (talk) 00:13, 7 December 2018 (UTC)
So, I've had some positive responses, mostly through direct messages. I'm not sure if that bodes well enough to go ahead, but I'm going to continue the preparation just in case. I mean, what if it's a big flop and we create a better GodWiki for nothing?
Since there was no commentary or suggestions about the theme, I'm narrowing down on Beer. I think it offers a nice variety of article types, and is such a strong theme throughout Godville that, hopefully, everyone has an opportunity to contribute. With the theme including so many different kinds of monster, artifacts, even taverns, I don't think a creator needs to be a beer drinker (or a drinker at all) to find inspiration there. (If you don't think it offers you a chance to contribute, speak now or forever hold your peace.)
I've expanded the beer list above with a handful of extra items I'd missed, and pared off the list of winter items for the sake of focus. I'm going to work on guideline articles and concept for the tracking page. (If anyone has ideas or suggestions for either, they're welcome.)

I've trimmed the text above just a bit. Any comments on this plan are still welcome below. -- Djonni (talk) 07:35, 11 December 2018 (UTC)