-
Notifications
You must be signed in to change notification settings - Fork 60
Updating foreground.wikiproject.net to 2.1.0-xxx #311
Comments
Yes, go for it. I'm prepping 2.1-beta right now |
@Hutchy68 I just updated the skin and changed the default setting to what is shown on the features page I just created. This page still need some work as well as other docu pages like the one on tabs. |
Did you turn tabs on because default is set the false? |
No but is should if we would like to demo something. Still the tabs will not work here since the page is still using Foundation 4 syntax. |
Ok, the page for tabs is updated using Foundation 5 syntax. |
Cool, thanks a lot. I just updated the configuration page a bit. As soon as addthis is in fluff I will do final work on the page. |
@Hutchy68 The wiki is now at 2.1.0-rc Also switched over to use AddThis via Foreground and not via PCRGUIInserts as before. |
Awesome 😎 I see one little thing on footer-left to fix on mobile. I’ll create an issue. |
You are welcome. I have created the Page Title page which is also showing some general glitches that imho should be tackled:
|
@kghbln I addressed these issues as best as I could. MW is loading a legacy.module with CSS for elements. Real pain in the neck! Anyway, I merged in #322 so you can PULL down the changes on foreground.wikiproject.net and take a look. Here is a snip of my test installation with your source page code. |
@Hutchy68 Thanks a lot. Just moved in "rc.1" and is really looks great again! :) |
Hmm, sublevel enumerations and listings could perhaps be tweaked a bit? However, this is a nitpick. |
That's going to be a hard one. FYI, MW is outputting a shared css module to all skins. There is an open tracker on Phabricator here: https://phabricator.wikimedia.org/T89981 This is everything being loaded automatically 😞 by all skins. https://gist.github.com/Hutchy68/a2e6220ee471210aa522f4762df1dc06 |
Ah, now I get it. Thanks for the insight. In fifteen years I have only seen something like this twice so we should not worries about this too much. The fixes of today are a big jump forward. |
Closing as not relevant any longer |
@Hutchy68 I guess I should upgrade the wiki to 2.1.0-alpha. There we/I could test #302 but also some other CSS tweaks I have in mind and fire away the release right after. Thoughts?
The text was updated successfully, but these errors were encountered: