TASBot Wiki:Village pump

NEED MORE CONTENT in general (historians wanted). Fill out redlinks or add to existing articles (and category pages).

Categories are arguably a direct upgrade to articles in that pages can have multiple parent categories, and categories have a nice UI for navigating to subpages. The longer URI is why you shouldn't just use them for everything.

UH-OH ENCOUNTERED: Special:Search defaults to main (article) namespace only! (This is the "full search". I assume the quick search only looks for article titles, but it doesn't seem to be working.) --yoshi
- Pretty sure it's configurable since it searches 6 namespaces incl. the manual and extensions catalog on MediaWiki.org. --yoshi

Embrace hypertext—link to other pages (and also other sites, such as Wikipedia), but do follow Wikipedia's linking guidelines (only link first mention, avoid adjacent links).

Use redirect shorthands wherever you feel they fit, with one exception: tagging pages with a category will not work if you use a redirect. You may still use the redirect when making a normal/inline link to the category page, such as [[:Category:SGDQ|]] ⟶ SGDQ.

On that note, when tagging pages for appearances with categories, put the year category first, then the event category if it exists (or will later i.e. a redlink).

Familiarise yourself with what templates exist. Hit up User:YoshiRulz if you want help making new ones.

TODOs for admins

There are 5 pages to delete
use dynamic content, or at least templates, for boxes on main page
- I can draft this, but the main page is edit-restricted for obvious reasons --yoshi
upload images? PortableInfobox doesn't seem to accept hotlinking images
populate TASBot_Wiki:Copyrights with a license (CC BY 2.0?)
consider adding {{#babel:}} template for user pages

TODOs

~~finish moving event pages to Category namespace~~ on hold, see top
- GDQ (split and/or rename and/or merge w/ Category:Summer Games Done Quick)
- MAGFest (split and/or rename and/or merge w/ Category:Super MAGFest)
- MAGWest Go
infobox for individuals
- Done, but it doesn't render correctly when used in the main namespace (example)? This happens regardless of whether it's transcluded directly or via e.g. a User page. I think it may be the same issue as this... a thread with no replies... There's also this, which was closed as a duplicate of a seemingly unrelated issue, but maybe the suggested fix for the latter is worth a try. --yoshi
- consider adding fields for country/flag and for pronouns
  - ~~on that note, should look into magic words for pronouns. I think I saw ones that can conjugate by gender using dictionaries, so simple pronoun lookups should be possible.~~ looked into it (and ended up copying over the template) and it doesn't seem like it (the magic word) can be linked to an arbitrary table/list. the conjugation thing is a different magic word and isn't useful since we're English-only. --yoshi
    - ~~could always create dummy accounts for everyone...~~ would only need 3—User:DummyAccM/User:DummyAccF/User:DummyAccNB—in addition to a name/handle → gender lookup --yoshi
- could add email, but I'd like to have it deobfuscate on click (with JS) if it's going to be included, and with a personal site field it's kind of redundant --yoshi
- consider adding field for (programming) languages spoken
  - for natural languages, there's mw:Extension:Babel, and it may be possible to hack in programming languages as qxx or something
infobox for appearances: date/time, location, run/presentation, link to prev/next of type, link to prev/next
consider redirecting (not sure how when #REDIRECT only allows local links) e.g. desync to /Glossary#Desync
- - introduces chance for link-rot
  - + can leave notes for TASVideos editors
- - not everyone can add to that glossary
  - + yet
- counter-proposal: could instead make a Template:TASVideosG (for glossary) and use {{TASVideosG|term}} instead of [[term]]
  - - no way to see valid link targets without visiting TASVideos

Qs for dwango:

I take it the focus here is on history, so...
- is there any point advertising upcoming events on the main page?
  - CONFIRM (can't hurt; link to GitHub Project)
- how much technical information should be here vs on TASVideos?
  - we should put [technical info] on TASVideos. However, I have one pause here; there is a huge barrier to entry for TASVideos [wiki] at this time [...]
apart from Ambassadors, how should individuals be categorised?
- DWYW
  - pages can be in multiple categories, so I guess could just have one cat per role/specialty?
- to that end, a definition of "notability" for inclusion here would be helpful
  - anyone who was credited for any event/showcase