Greetings, all! For a while several of us have been lamenting the quality of some of our most highly-trafficked and essential articles. Many of our articles covering major topics from the films and TV shows are in need of significant updates and improvements in order for them to meet our standards and provide the highest possible quality for our readers. Some even have so many maintenance tags at the top that the content of the article isn't even visible when the page loads, and readers must scroll down to even see the intro and infobox. Now, many of these articles require more than a single editor could accomplish in a reasonable amount of time, and so most users understandably avoid attempting to tackle the issues. However, as a community, with several users dedicating time to a single article, the goal becomes much more achievable. Consider this a call to arms.
What is the goal?[]
The main goal of this project is similar to that of previous community Improvement drives. There is one big difference, though: this project does not aim to bring these articles to Featured article status. If a user decides to do so after the project has completed its goal, that is their prerogative. The main goal of this project is simply to get the article fully updated and handle any major issues, especially those for which maintenance tags have been placed. By the end of the project, the article should ideally have no maintenance tags and not be included in any maintenance categories. I would rather not make this a regularly recurring project with a new article every month or so, but rather just start the next article whenever the current one is complete. I do, however, feel like a month should be the maximum amount of time allowed for the project to continue on a single article.
How to participate[]
If you are interested in helping out with the project, all you need is a free registered FANDOM account. It is preferred that you use/create a personal workbench to make changes to the article one section at a time, and that you copy and paste the improved section into the main article when completed. This should help us avoid constant edit conflicts.
Vote[]
For the first article, I have decided to narrow it down to characters. These are often the most egregious offenders, and I would assume the most high-traffic of our articles. It is imperative that we make sure they look as professional as possible. I also do not want a massive vote for our first project, and I would rather use this first vote to determine demand and interest. Below is a list of articles several community members have selected as candidates for the project. Please vote for no more than 5 articles. Vote by signing your name with three tildes (~~~). The article with the most votes when the poll is closed will be the focus of our first project. MasterFredcerique 20:50, May 15, 2020 (UTC)
Ahsoka Tano[]
- Master
Fredcerique
- RattsT (talk)
- Zed42 (talk) 22:50, May 15, 2020 (UTC)
- Orbitball • talk • contr 23:15, May 15, 2020 (UTC)
- Cwedin(talk)
- UberSoldat93
(talk) 07:58, May 16, 2020 (UTC)
Anıl Şerifoğlu (talk)
- Mr Star Wars Amino Republic (talk)
- Wok142 03:11, May 20, 2020 (UTC)
20:27, May 23, 2020 (UTC)Erebus Open frequency
Anakin Skywalker[]
- Corellian Premier
The Force will be with you always 23:13, May 15, 2020 (UTC)
OOM 224 ༼༽{talk}༼༽
20:29, May 23, 2020 (UTC)Erebus Open frequency
BB-8[]
Ben Solo[]
- Corellian Premier
The Force will be with you always 23:13, May 15, 2020 (UTC)
Boba Fett[]
Cal Kestis[]
Cassian Jeron Andor[]
CC-2224 "Commander Cody"[]
- --Vitus InfinitusTalk 16:06, May 19, 2020 (UTC)
Cere Junda[]
- Braha'tok enthusiast (Hello there)
- Toqgers (talk)
- Orbitball • talk • contr 23:15, May 15, 2020 (UTC)
- RattsT (talk)
- Mr Star Wars Amino Republic (talk)
Chelli Lona Aphra[]
- Braha'tok enthusiast (Hello there)
- Omicron(Leave a message at the BEEP!)
Anıl Şerifoğlu (talk)
OOM 224 ༼༽{talk}༼༽
- Mr Star Wars Amino Republic (talk)
Chewbacca[]
Child, The[]
- Braha'tok enthusiast (Hello there)
- Corellian Premier
The Force will be with you always 23:13, May 15, 2020 (UTC)
- UberSoldat93
(talk) 07:58, May 16, 2020 (UTC)
CT-5597 "Jesse"[]
- Braha'tok enthusiast (Hello there)
- UberSoldat93
(talk) 07:58, May 16, 2020 (UTC)
C-3PO[]
- Corellian Premier
The Force will be with you always 23:13, May 15, 2020 (UTC)
Darth Sidious[]
Dooku[]
Ezra Bridger[]
- Master
Fredcerique
- Corellian Premier
The Force will be with you always 23:13, May 15, 2020 (UTC)
- Cwedin(talk)
Finn[]
Han Solo[]
Hondo Ohnaka[]
Iden Versio[]
Jabba Desilijic Tiure[]
Jar Jar Binks[]
Jyn Erso[]
Landonis Balthazar Calrissian[]
Leia Organa[]
Luke Skywalker[]
- Master
Fredcerique
- Zed42 (talk) 22:50, May 15, 2020 (UTC)
- Toqgers (talk)
- Orbitball • talk • contr 23:15, May 15, 2020 (UTC)
- Mr Star Wars Amino Republic (talk)
- Toprawa and Ralltiir (talk)
Mace Windu[]
Maul[]
Mitth'raw'nuruodo[]
- UberSoldat93
(talk) 07:58, May 16, 2020 (UTC)
Obi-Wan Kenobi[]
- Master
Fredcerique
- Zed42 (talk) 22:50, May 15, 2020 (UTC)
- Orbitball • talk • contr 23:15, May 15, 2020 (UTC)
OOM 224 ༼༽{talk}༼༽
Padmé Amidala[]
Poe Dameron[]
Qui-Gon Jinn[]
Rex[]
- UberSoldat93
(talk) 07:58, May 16, 2020 (UTC)
Rey Skywalker[]
Rose Tico[]
R2-D2[]
Yoda[]
Discussion[]
Notice template[]
- Let me know if you have any suggestions for the notice template to be placed at the top of the current article being worked on. Master
Fredcerique 20:50, May 15, 2020 (UTC)
- The goal of the project being to reduce the number of templates cluttering the top of a page, I propose this template replace, rather than add to, existing maintenance templates. In Ahsoka Tano's case, for example, we'd still need to keep {{Twoconflicting}} and {{Spoiler}}, but removing {{Update}}, {{Cleanup}}, and {{Image}}—which concern issues amply covered by the discussion the new {{Stardust}} template points to—would at least make the beginning of the page's content visible when the page first loads on most full-size screens, instead of requiring the user to scroll down to see even the introductory sentence. Asithol (talk) 19:38, June 2, 2020 (UTC)
- I presume anyone who had a strong objection would have voiced it, so I'm going ahead and removing them. (I also see the spoiler template has already been removed, so yay, further decluttering!) Asithol (talk) 20:31, June 4, 2020 (UTC)
- For those not part of the project, they would still need to know what needs to be done from the others as well as any additions that need to be added for Stardust on the page. We will remove those tags at the top of the article as they are needed to be removed. Currently, none of the tags are currently ready to be removed. --Mr Star Wars Amino Republic (talk) 04:00 June 5, 2020 (UTC)
- Anyone—part of the project or not, registered user or not—can click the the project page link in the Stardust template and get all the information about what's missing and what work is being done, in far more detail than would be provided by the individual maintenance templates. I feel that better serves editors, whereas most readers probably don't care about any of that, making the gauntlet of maintenance templates mere visual clutter, and reducing them down to one an improvement. Anyway, hopefully someone else will chime in, since it's hard to achieve consensus between two editors with different opinions. :) Asithol (talk) 05:02, June 5, 2020 (UTC)
- I'm inclined to agree with you, Asithol. As you've pointed out, it's in the interests of the project to reduce the visual clutter of maintenance tags. I do think that there should be an indication on the page of the specific issues though. A casual reader is unlikely to go to the project page, so perhaps we could include a drop down menu on the Stardust notice itself that lists the general issues, similar to the {{Update}} template. That way it can be hidden upon loading the page but all the tags can still be viewable on the article. RattsT (talk) 05:14, June 5, 2020 (UTC)
- That's a great solution (though I suspect a casual reader is no more likely to expand the dropdown than click a link). If someone volunteers to code that into {{Stardust}}, great. (In fact, that code could also be fashioned into a single This page has issues master template to replace all of our existing maintenance templates. That would reduce template clutter on numerous pages across the wiki.) But unless/until that happens, do you think the information is important enough to the casual reader to retain all the maintenance templates while the project is underway? Asithol (talk) 19:04, June 5, 2020 (UTC)
- Hey there, my apologies for the late response. My opinion is that if a page has issues, they should be plainly stated so that a reader doesn't have any false ideas on the quality of the article. We wouldn't want, for example, someone to read a biography that needs expansion and not have an indication that there's missing information. I think the update to the Stardust template would be the best way to go, but for now I'd say that the full maintenance tags are a necessary evil to ensure that readers get all the facts upfront. RattsT (talk) 06:11, June 6, 2020 (UTC)
- That's a great solution (though I suspect a casual reader is no more likely to expand the dropdown than click a link). If someone volunteers to code that into {{Stardust}}, great. (In fact, that code could also be fashioned into a single This page has issues master template to replace all of our existing maintenance templates. That would reduce template clutter on numerous pages across the wiki.) But unless/until that happens, do you think the information is important enough to the casual reader to retain all the maintenance templates while the project is underway? Asithol (talk) 19:04, June 5, 2020 (UTC)
- I'm inclined to agree with you, Asithol. As you've pointed out, it's in the interests of the project to reduce the visual clutter of maintenance tags. I do think that there should be an indication on the page of the specific issues though. A casual reader is unlikely to go to the project page, so perhaps we could include a drop down menu on the Stardust notice itself that lists the general issues, similar to the {{Update}} template. That way it can be hidden upon loading the page but all the tags can still be viewable on the article. RattsT (talk) 05:14, June 5, 2020 (UTC)
- Anyone—part of the project or not, registered user or not—can click the the project page link in the Stardust template and get all the information about what's missing and what work is being done, in far more detail than would be provided by the individual maintenance templates. I feel that better serves editors, whereas most readers probably don't care about any of that, making the gauntlet of maintenance templates mere visual clutter, and reducing them down to one an improvement. Anyway, hopefully someone else will chime in, since it's hard to achieve consensus between two editors with different opinions. :) Asithol (talk) 05:02, June 5, 2020 (UTC)
- For those not part of the project, they would still need to know what needs to be done from the others as well as any additions that need to be added for Stardust on the page. We will remove those tags at the top of the article as they are needed to be removed. Currently, none of the tags are currently ready to be removed. --Mr Star Wars Amino Republic (talk) 04:00 June 5, 2020 (UTC)
- I presume anyone who had a strong objection would have voiced it, so I'm going ahead and removing them. (I also see the spoiler template has already been removed, so yay, further decluttering!) Asithol (talk) 20:31, June 4, 2020 (UTC)
- Okay, I have updated your template with a dropdown menu. I have included instructions on {{Stardust}} and implemented it on Ahsoka Tano. I've put on some of the more common cleanup templates, and it should be simple for you to add more now you can see examples. Just add another beneath the update tag in the same format. Please note that I only want this to be a temporary measure while the Stardust improvements are ongoing, and I want the original templates reinstated if they remain unaddressed when {{Stardust}} is removed. While this sort of thing being implemented sitewide could work, such a change would have to go through a CT first. Tommy-Macaroni 12:58, June 22, 2020 (UTC)
- The goal of the project being to reduce the number of templates cluttering the top of a page, I propose this template replace, rather than add to, existing maintenance templates. In Ahsoka Tano's case, for example, we'd still need to keep {{Twoconflicting}} and {{Spoiler}}, but removing {{Update}}, {{Cleanup}}, and {{Image}}—which concern issues amply covered by the discussion the new {{Stardust}} template points to—would at least make the beginning of the page's content visible when the page first loads on most full-size screens, instead of requiring the user to scroll down to see even the introductory sentence. Asithol (talk) 19:38, June 2, 2020 (UTC)