Difference between revisions of "StaffList"
From Sega Retro
(Created page with "{{TODO}} I made this template to replace the old manual lists of staff members. Thing is, Sega has employed literally thousands of people over its existence, so if you list 1...") |
(i always forget to turn off minor edits with talk) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 30: | Line 30: | ||
Or do we just let the categories do it -[[User:Black Squirrel|Black Squirrel]] ([[User talk:Black Squirrel|talk]]) 14:04, 3 November 2024 (EST) | Or do we just let the categories do it -[[User:Black Squirrel|Black Squirrel]] ([[User talk:Black Squirrel|talk]]) 14:04, 3 November 2024 (EST) | ||
| + | :Your 'subpages for StaffLists' idea is a good idea. As for sorting by role, that's tough. I don't see any issues with how you have it here: essentially we're sorting by the first entry in the Role= field. I've usually approached this field by entering their most relevant role first, and their least important last - "Producer, Lead Tester, Tester". I think that's probably how most people do it. This also might be one of those things where we have to rely on the contributors to do their own formatting. Which goes against wanting to take care of that template-side, but.... I mean I guess you could have something that sits between PersonBob and this tabled StaffList which checks all PersonBob's role= entries against a static list, sorts that, and returns it to the tabled Stafflist. I don't even know if that's possible, or way too much work. | ||
| + | |||
| + | :I also couldn't imagine any other field from PersonBob to include that'd be strictly necessary other than name and role. I mean I can totally imagine us getting all fancy and having a teeny image of the dev's face next to their name (no wider than the line itself.) dunno how legible that'd turn out but gosh what a flex [[User:CartridgeCulture|CartridgeCulture]] ([[User talk:CartridgeCulture|talk]]) 16:34, 3 November 2024 (EST) | ||
Latest revision as of 16:34, 3 November 2024
 |
This task is unfinished This is a wiki task that requires more thought or peer review. An important issue that needs to be solved, which will appear at the top of Sega Retro:Todo until this message is removed. |
I made this template to replace the old manual lists of staff members. Thing is, Sega has employed literally thousands of people over its existence, so if you list 15 years' worth with
{{StaffList|Sega Corporation (2000-2015)|employees=yes}}
it hits the DPL limit at about the half-way mark.
We can get over that - that isn't the issue. The problem is Sega has employed literally thousands of people over its existence, which means the list is massive and dominates the page.
I think a sub-page is required. But do we still want flat list of names, or something more akin to Category:Lists of games, where there's a bit more detail, e.g.
| Name | Role |
|---|---|
| Akihito Fujiwara | Lead Programmer |
| Akane Hayashi | Artist |
| Akihito Hiroyoshi | Artist, designer |
| Akio Horii | Designer, Director, Producer |
| Akira Iizuka | Programmer |
| Akira Iketani | Artist |
| Akira Kai | Artist |
| Akihiko Kohno | Engineer |
| Akiko Kuroda | Producer |
| Akira Mikame | Artist |
| Akikazu Mizuno | Designer |
| Akira Motegi | Engineer |
| Akira Nishikawa | Tester |
| Akira Nishino | Executive, Producer, Technical Support |
| Akinori Nishiyama | Artist, Director[1], Producer |
| Akihiro Noguchi | Artist |
| Ai Ogata | Marketing |
| Akira Ohe | Programmer |
| Akio Sakai | Artist |
| Ai Sawayanagi | |
| Akio Setsumasa | Programmer |
| Akihiro Suzuki | Artist |
| Akihiko Tamai | Programmer |
| Akira Terasawa | Tester |
| Ai Tsushima | Artist |
| Akira Wako | Engineer |
(this is a reduced list)
Thing is, it's not very sortable if someone has multiple roles. Any field from PersonBob will work btw.
Or do we just let the categories do it -Black Squirrel (talk) 14:04, 3 November 2024 (EST)
- Your 'subpages for StaffLists' idea is a good idea. As for sorting by role, that's tough. I don't see any issues with how you have it here: essentially we're sorting by the first entry in the Role= field. I've usually approached this field by entering their most relevant role first, and their least important last - "Producer, Lead Tester, Tester". I think that's probably how most people do it. This also might be one of those things where we have to rely on the contributors to do their own formatting. Which goes against wanting to take care of that template-side, but.... I mean I guess you could have something that sits between PersonBob and this tabled StaffList which checks all PersonBob's role= entries against a static list, sorts that, and returns it to the tabled Stafflist. I don't even know if that's possible, or way too much work.
- I also couldn't imagine any other field from PersonBob to include that'd be strictly necessary other than name and role. I mean I can totally imagine us getting all fancy and having a teeny image of the dev's face next to their name (no wider than the line itself.) dunno how legible that'd turn out but gosh what a flex CartridgeCulture (talk) 16:34, 3 November 2024 (EST)