mNo edit summary |
mNo edit summary |
||
Line 32: | Line 32: | ||
*** CONFIRM ("can't hurt; link to [https://github.com/orgs/TASBotL3C/projects/1/views/5 GitHub Project]") | *** CONFIRM ("can't hurt; link to [https://github.com/orgs/TASBotL3C/projects/1/views/5 GitHub Project]") | ||
** how much technical information should be here vs on TASVideos? | ** 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 at this time [...]" | *** "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 [[:Category:Ambassadors|Ambassadors]], how should individuals be categorised? | * apart from [[:Category:Ambassadors|Ambassadors]], how should individuals be categorised? | ||
** "DWYW" | ** "DWYW" | ||
** to that end, a definition of "notability" for inclusion here would be helpful | ** to that end, a definition of "notability" for inclusion here would be helpful | ||
*** "anyone who was credited for any event/showcase" | *** "anyone who was credited for any event/showcase" |
Revision as of 08:13, 3 July 2023
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 they 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 follow Wikipedia's linking guidelines (only link first mention, avoid adjacent links).
Use redirect shorthands as much as you like, 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.
Familiarise yourself with what templates exist. Hit up YoshiRulz on Discord if you want help making new ones.
TODOs:
- finish moving event pages to
Category
namespaceGDQ
(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
- use dynamic content, or at least templates, for boxes on main page
- infobox for appearances: date/time, location, run/presentation, link to prev/next of type, link to prev/next
- infobox for individuals: real name, contributions/specialisations, day job, links to profiles
- FOR ADMINS:
- Pages to delete (don't mind redlink, you can still see the subpages)
- need to enable ParserFunctions extension to do arithmetic for navigation-by-year templates, conditionality for date template...
- consider installing PortableInfobox extension (infoboxes can be made with just ParserFunctions'
#if
, but it's a pain, and I hear PortableInfobox gives nice results on mobile) - consider enabling CategoryTree extension
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 [...]"
- is there any point advertising upcoming events on the main page?
- apart from Ambassadors, how should individuals be categorised?
- "DWYW"
- to that end, a definition of "notability" for inclusion here would be helpful
- "anyone who was credited for any event/showcase"