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.
Embrace hypertext—link to other pages (and also other sites, such as [[wikipedia:]]), but do also follow Wikipedia's linking guidelines: only link first mention, avoid adjacent links, don't over-link common concepts/entities (TASBot, in our case).
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). {{infobox appearance}} handles this for you.
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
- upload images (list existing media)
- please use WebP to minimise filesize:
magick convert input.png -define webp:lossless=true output.webp
- please use WebP to minimise filesize:
- populate TASBot_Wiki:Copyrights with a license (CC BY 2.0?)
- consider adding
{{#babel:}}template for user pages - fix quick search API
- I researched as far as 'Generators' +
prefixsearchand gave up --yoshi
- I researched as far as 'Generators' +
- can the PortableInfobox link an image's media page rather than hotlink?
TODOs
- finish moving event pages to
Categorynamespace- 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 correctlyclose enough now thanks to TheMas - 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. --yoshicould 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
qxxor something --yoshi
- for natural languages, there's mw:Extension:Babel, and it may be possible to hack in programming languages as
- Done,
- infobox for appearances: date/time, location, run/presentation, link to prev/next of type, link to prev/next
- Done except the navigation (which was the key part, but shush I'll get to it) --yoshi
- consider redirecting (not sure how when
#REDIRECTonly allows local links) e.g. desync to TASVideos.org/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]]- + easy on a technical level
- - no way to see valid link targets without visiting TASVideos
- - same problems as above re: "delegating" content to TASVideos
- - introduces chance for link-rot
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
)
- CONFIRM (
- how much technical information should be here vs on TASVideos?
- tl;dr:
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 [...]
In essence, we should first and foremost ensure things like replay device and console verification documentation is complete (enough) on the TASVideos wiki. As CompuCat pointed out however, our needs and perspective is a bit different, and there's no harm in us also having technical details on the TASBot wiki with a perspective more geared toward live presentations at charity events. In fact, that's where I see the TASBot community as differentiated from the TASVideos side when it comes to on-hardware work; the TASBot community is centered around having our cute robot mascot play video games during public presentations, and our needs are going to involve things like proper presentation with visualization on camera that aren't relevant for just seeing if something syncs on hardware. To that end, I think there's room to have the core concepts explained from the different perspectives even if some of it may end up overlapping documentation on the TASVideos side. More documentation (so long as it isn't wholly inaccurate) is always better. There's another caveat here - despite my best efforts, it's still a lot harder for folks to edit wiki entries on TASVideos whereas anyone willing to share an email address is able to edit the TASBot Wiki
- tl;dr:
- is there any point advertising upcoming events on the main page?
- 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