Re-organizing the main page seems like a good way to go about things since a lot of things are missing. Not satisfied with current list, needs work.

Character

  • Species
  • Class
  • Crew Skills

Basics

  • Achievements
  • Cartel Market
  • Codex
  • Datacrons
  • Galactic Reputation
  • Legacy
  • Pets
  • Titles
  • Warzones

Gameplay

  • Arenas
  • Conquest
  • Events
  • Flashpoints
  • Galactic Starfighter
  • Heroic Missions
  • Operations
  • Space Combat
  • Warzones


Universe

  • Lore
  • Planets

Arirthos (talk) 14:35, 13 January 2019 (UTC)

Statistics:

  • Number of legitimate articles on SWTOR Wiki: 33,817
  • Currently running MediaWiki version: 1.33.3
  • Total number of pages (including templates, talk pages, and the like): 78,781
  • Total uploaded files: 13,120
  • Number of admins: 1
  • Number of registered users across all of wiki: 28,459,996
  • Number of articles per user: 0.001
  • Number of pages per user: 0.003
  • Number of files per user: 0
  • Number of articles per admin: 33817
  • Number of pages per admin: 78781
  • Number of files per admin: 13120
  • Number of users per admin: 28459996
  • Number of articles for every File:2.578 articles
  • Number of non-article pages for every article: 1.33

Arirthos (talk) 20:11, 15 February 2019 (UTC)

UCX implementation

Hi! I’m Héctor, one of the Fandom Community Managers. I’m here to talk with you about the upcoming changes we will experiment on the wikis when the new UCX will be released. As a result, we’ll have to adapt the current content - mainly the design and implemented code - to ensure they’re compatible and operational.

Specifically talking, the UCX will mainly affect the Frontpage, the design (logo, background, favicon, themes), the CSS/JS used and some templates that should adapt their look to it. While the wiki will still be migrated some weeks later, I’m here to work alongside you to anticipate all the work regarding review, improvements and adaptation to the new skin.

If you agree, I’ll start soon, reviewing the mentioned elements and describing to you what work should be done. For the case of the design, I can work with the future version, that will be working once the wiki will be migrated. Regarding the frontpage, templates and the code, I can work and implement the changes now, to have them properly working both in the present and the future, but having all the changes done in advance.

Let me know if you have any comments about it and we can explore together the upcoming changes. Thanks! --CuBaN VeRcEttI (Contact) 16:50, 10 May 2021 (UTC)

Hi Héctor. Been a bit busy with work stuff of late, but if there's anything I can do to help with the updates (it's been awhile since I've edited the front page) please let me know. Arirthos (talk) 22:04, 11 May 2021 (UTC)
Hi again! I've taken a quick look to the wiki in the UCX test version, and I have to admit it looks pretty well! Some stuff I've found:
The frontpage shows the Section 2 (right column) placed after section 1 (left column). You can make changes if you want, but it actually looks fine.
The infoboxes doesn't have their styling. Both content inside Hydra.css and Hydradark.css won't work with the UCX, so their content has to be moved to Common.css
Some templates and tables with custom background color for dark theme (like the tables in the Jaesa page or the Datacron navbox) don't fit with the light theme. --CuBaN VeRcEttI (Contact) 12:35, 12 May 2021 (UTC)
So, to do:
Infobox styling to be moved from Hydra.css/Hydradark.css to Common.css?
The table template needs to be updated, then? Any suggestions on a more neutral colour for both dark/light theme? Is it possible to see an example of what light mode would look like with this wiki? Arirthos (talk) 01:26, 13 May 2021 (UTC)
Yes. You can move it to Common.css or Fandomdesktop.css (the new skin that will replace Hydra). There's actually no need to move all, but only they styling stuff you think will need to keep the customization for some templates (frontpage, infoboxes, navboxes, tables), as long as it will be compatible with both themes.
Regarding readability for both themes, you can basically do two options: trying to use neutral color for both - as you suggested - or adding variables for both themes. There will be a way to make them compatible with both themes.
In addition, another useful way I found and I applied on other wikis is to style the templates for a theme (in this case, dark) but instead of using concrete colors, using css variables based on the Theme Designer. With this, you can style a theme and the other will automatically be working with its alternative colors. Tell me what option you prefer and I can advance the work until you'll be able to check it.
Unfortunately, you're not able to see and test yet the UCX, but in some weeks the option will be available for the admins. CuBaN VeRcEttI (Contact) 12:02, 13 May 2021 (UTC)
I copied over everything from Hydradark.css to the Common.css just to be safe. Honestly, when I did the CSS when I took over the wiki I cobbled together what I could. I'm by far no expert, sadly. lol. I'm sure there's a lot of unnecessary stuff in there given the amount of errors/notices I see in the edit UI that probably needs a professional eye to have a look and prune unnecessary bloat, but so long as nothing obviously breaks I think we're fine for now?
I can't recall if there is a way to identify any pages that use tables for me to go in and edit - I don't think most are based on any kind of template framework that we used. I wouldn't mind having a variable that changes based on theme, but in either event I'll have to do some looking when I have time to find the pages with tables. If you could set that up in CSS that would be great! Arirthos (talk) 02:43, 14 May 2021 (UTC)
I didn't check the MW pages yet. While it's fine for now, I'd suggest just the opposite. Keep all the customizations on Hydradark.css, and only move to Common.css or Fandomdesktop.css whatever we really want to include in the new skin. Then I can even change things, like using the same palette for templates but making some changes to have it compatible with both themes (light/dark), changing concrete colors by CSS variables (while you can still use these concrete colors for the current skin inside Hydradark).
If you agree, I'm doing the suggested change, and starting re-styling some stuff in FD.css for the new skin, with the main intention of making it compatible with both themes. --CuBaN VeRcEttI (Contact) 10:35, 14 May 2021 (UTC)

I've been working a bit more on your wiki, and I can say it's almost done (except for important details I'm explaining now).

  • The frontpage now works perfectly after importing the code to fandomdesktop.css, and it suits fine with both themes.
  • Additionally, the infoboxes now are also styled (after the import) and if they use their classes, will work fine with both themes at the same time. I'm not sure if you have any infobox with additionaly custom code inside them or even in each page (affecting the design, basically the background, text and link colors), but I had that problem on other wikis before (feel free to check it).
  • While the navbox in the Jaesa page now works fine with both themes, unfortunately that's not the case for other templates and tables:
  • In the Jaesa page you have some tables, and they're using concrete colors in the page itself. That's a problem, because we can't define general colors for all and it basically affects the adaptation to the light theme. Same for the datacron template, for instance. You will have to change all the tables and templates that uses specific colors inside the pages, and change that codes for general classes. Then this classes can be defined with concrete colors (mainly for this skin) and for the UCX with CSS variables (to make them compatible with both themes). This is actually not a problem related only with the UCX, but this use is not recommended because it's later too difficult to make any change (for instance, if you would make some slight change to the general design). --CuBaN VeRcEttI (Contact) 12:54, 14 May 2021 (UTC)