FANDOM


This is the talk page for discussing improvements to the Admin Tools Wiki page.

  • Be polite
  • Assume good faith
  • Be welcoming

Dots at the end

There are dots at the end which are linked to Special:Upload and Special:Import. Is this necessary? Barring justification, I intend to remove them.   — Jeff G. ツ 22:54, October 27, 2011 (UTC)

You’re only just now noticing them? Face-surprise Deep last Winter when we were, essentially, transitioning from a Wikipedia-oriented test site to a Wikia-oriented test site, and the only people editing here were You, Jempcorp, and I, I was uploading and importing so much that I got tired of typing in the Special:Upload and Special:Import commands. Those “dots” served as quicklinks to those two input screens. If you think they are that noticeable or detrimental to the look of the mainpage, please remove them. I don’t need them anywhere near as much anymore. Face-smile Thanks!SpikeToronto 23:18, October 27, 2011 (UTC)
I think it might help to have those links in the toolbox on the left side (at least in Monobook) before removing the dots.   — Jeff G. ツ 16:46, October 28, 2011 (UTC)
Special:Upload is already there. My only problem with having Special:Import there — and I thought about this back at the time — is that it is such a powerful tool that, if the Special:Export was not done correctly prior to the import, it can overwrite scores of existing templates, which all have to be manually fixed. This may sound familiar to you as it was something I did on my first Special:Import. Face-blush This is why I did not add both of them to the Monobook sidebar at the time. In Oasis, I have added them to my own customizable toolbar at the bottom of the screen under My tools, which is why I do not use the dots so much any more (still use them, but now only 50% of the time, or so). Do you share my concerns about Special:Import? Thanks! — SpikeToronto 18:52, October 28, 2011 (UTC)

2012 Revision of Main Page

A discussion was begun at the Noticeboard regarding the redesign of the Main Page. Since that time, Rappy and I have taken the bull by the horns and worked up a new look for the main page. It can be viewed at Admin Tools Wiki/2012 Revision. It is still a work in progress and is not ready to be rolled out. For instance, in the Recent Wiki Activity module, we still need to insert in the h2 an Add a page button.

Feedback would be greatly appreciated. Please leave comments, suggestions, etc., right below here on this talkpage. Thanks! — SpikeToronto 02:33, December 26, 2011 (UTC)

Suggestions/Comments/Etc. 1

  • Pictogram voting comment Suggestion  I think that the elements could benefit from a small–scale box-shadow similar in appearance to the one used by the WikiaRail. TK999 17:59, December 28, 2011 (UTC)
    • Pictogram voting comment Comment:  I have to admit to chuckling a little when I read your suggestion TK. Face-smile When Rappy and I were working on this the other day, I kept thinking at the back of my mind, “Here’s some more stuff for TK to shadow!” Face-tongue. Seriously though, I think that you are right, for the sake of consistency. Face-smile Thanks!SpikeToronto 08:28, December 30, 2011 (UTC)
  • Pictogram voting question Question:  I notice that the Twitter follow button located in the Twitter h2 moves around. Sometimes it is where it belongs — right-justifed in the heading block. Other times, it is way over to the left “attached” to the actual h2 heading. Thanks! — SpikeToronto 09:27, December 30, 2011 (UTC)
    • Yes check Done  Tweaked the order a bit, hopefully that's enough to fix it. TK999 09:44, December 30, 2011 (UTC)
    • Pictogram voting comment Comment:  Nah. Didn’t fix it. It caused the h2 heading and the twitter feed box to merge. This took away the nice styling of the feed box. Also, a previous edit (largelarger) caused the heading at the top of the page to be rendered at normal size. I reverted all of our edits back to revision #36009 with this edit. The odd thing is, after the page has drawn, if I Ctrl-F5, the Twitter follow button will end up where it belongs: at the extreme right of the Twitter h2 (i.e., h2 id="mp-twit-h2"). Thanks! — SpikeToronto 10:09, December 30, 2011 (UTC)
      • Just viewed it with Firefox 12.0 alpha on Windows Vista and it looks okay—it appears in the correct place from the start. TK999 10:59, December 30, 2011 (UTC)
      • How is it behaving with other browsers, or other versions of Firefox? Thanks! — SpikeToronto 11:03, December 30, 2011 (UTC)
        • Internet Explorer 9 displays it underneath the h2 until it loads the page, whereupon it renders correctly. TK999 11:14, December 30, 2011 (UTC)
        • See, I’m using Win7/IE9 and it does not render it at the extreme right of the blue h2 box until I re-draw the page via Ctrl-F5. Face-confused Thanks! — SpikeToronto 14:00, December 30, 2011 (UTC)
  • Purple question mark   Okay guys. So what else is needed to roll out the 2012 version of our main page? I’d like to get it out ASAP. Rappy, I believe that you still had some coding you wanted to change, but I cannot remember what exactly. Thanks! — SpikeToronto 03:57, January 2, 2012 (UTC)
    • Pictogram voting comment Comment:  No changes that I notice/recall. Rappy 06:31, January 2, 2012 (UTC)

Monobook

I just noticed that we have’t finished with the Monobook version of the mainpage. Please see

http://admintools.wikia.com/wiki/Admin_Tools_Wiki?useskin=monobook
to see what I mean. Also, to see the Monobook version at its best, be sure to [dismiss] the sitenotice at the top of the page. Thanks! — SpikeToronto 13:26, January 2, 2012 (UTC)

Wow! It brought a huge smile to my face when I logged in and discovered all the work that Rappy had been doing on the Main Page today! Face-grin I did notice a few things when looking at Monobook in IE9 that may not relate to Firefox.
  • In Recent Wiki Activity, the Add a page button is not drawing inside of a button. It is just appearing as text: Add a page.
  • The Blog listing looks great with regard to alignment, etc. However, why are the avatars and other graphical elements that show in the Oasis blog listing not showing in the Monobook blog listing?
Face-smile Thanks!SpikeToronto 21:47, January 2, 2012 (UTC)
For the same reason you don't see your avatar on this page. Wikia made Oasis 'prettier' but never did the same for Monobook. Rappy 22:47, January 2, 2012 (UTC)

Rolled out: Oasis

Yes check Done  On January 1, 2012, I moved the new page onto the main page. The old one is now archived at Admin Tools Wiki/2011 Version. After that, Rappy spent some time adjusting various CSS/JS elements in the MediaWiki namespace to get the page to function correctly now that it had been rolled out. If there are any issues with the new main page, please comment here on the main page’s talkpage. Face-smile Thanks!SpikeToronto 09:19, January 2, 2012 (UTC)

Rolled out: Monobook

I forgot to mention that Rappy has made the changes necessary for the main page to work in Monobook. — SpikeToronto 08:54, January 8, 2012 (UTC)

Suggestions/Comments/Etc. 2 (Tabs)

With these edits, I used tabs to reduce the size of the left side of the Main Page. Thoughts? Ideas? Suggestions? Face-smile Thanks!SpikeToronto 11:48, January 6, 2012 (UTC)

Ambox notice UPDATE:  I added these modifications to the tab view on the Main Page. The file MediaWiki:Common.css/tabView.css is then imported into MediaWiki:Common.css. What I do not know how to do is to limit these modifications to the mainpage only. An unfortunate side effect of the current, wiki-wide implementation is that it impacts the use of TabView anywhere at ATW (example). If anyone can figure out how to limit the application of MediaWiki:Common.css/tabView.css to the mainpage only, that would be great! Face-smile Thank youSpikeToronto 12:20, January 6, 2012 (UTC)

Yes check Done   TK999 13:31, January 6, 2012 (UTC)
Thanks TK! I did some sampling and MediaWiki:Common.css/tabView.css is no longer impacting pages other than the mainpage. Face-smile Thanks!SpikeToronto 15:27, January 6, 2012 (UTC)
I personally don't like it. It leaves the right side 1 mile long while it leaves the left side 'lacking' (a reverse of what we had). The left side should be more prominent than the right, IMO. I really don't like tabview being used on main pages unless there is much more content to flesh it out. Rappy 21:33, January 6, 2012 (UTC)

Suggestions/Comments/Etc. 3

Original Query:

Two things: Remove the ugly twitter widget. THIS IS WIKIA! Secondly, maybe make some css so the tabview turns gray? Apart from that great job. Best, — Kangaroopowah(Talk) 05:18, January 8, 2012 (UTC)

from “Main Page Redesign” at User talk:SpikeToronto

Response:

I’ll respond in order:

  1. The Twitter widget is convenient. It fulfills the same function as {{Wiki News}}, but for ATW members who may not have visited the wiki since any new announcements were posted. Whereas one only becomes aware of the announcements produced by {{Wiki News}} when one visits the wiki, the Twitter feed will permit ATW members to get the same announcements when they haven’t had the time to visit ATW.
  2. I don’t understand exactly what you want to turn grey in the tabview? Right now, the selected tab is a sort of  SkyBlue  while the unselected tab is  Grey . What else was it that you were suggesting should turn grey in the tabview?
    • I should point out that the tabview staying on the main page is still under discussion (see above).

Face-smile Thanks!SpikeToronto 09:54, January 8, 2012 (UTC)

For the moment let's forget about the tabs since that isn't very important. The thing about the twitter widget... well what's the point of putting it on the wiki's main page. If someone hasn't visited the wiki in a while and wants to see something that you posted on Twitter then they would go to Twitter. Also it helps staff disregard the arguments that they're turning into facebook. If they are integrating Twitter into our wikis, well they have every right to go facebook on us. Finally the google + icons and whatnot are ridiculous. This is not a content wiki and as such only Mediawiki users come here. Seeing as that is the case there is no need to show off this wiki. There is almost no viable competitor to this wiki that exists and I have seen the other testwiki. All the widgets do are taking up space and taking away from what the purpose of this wiki is. --Kangaroopowah(Talk) 22:29, January 8, 2012 (UTC)

Part of the idea of the Twitter widget was (1) it might eliminate {{Wiki News}} entirely, and (2) it collects the latest wiki news in a convenient manner on the main page. I see your point that if we go ahead and add social networking stuff to our site, then it may send the message to Wikia that we have been successfully co-opted to their social networking goals and objectives. However, Wikia is not going to deviate from its corporate strategic plan, an integral part of which is Wikia challenging Facebook, Twitter, etc., for a share of the social networking market. That train has left the station and is going full steam ahead to Wikia’s intended destination smack in the middle of social networking territory.

As for the Google+ icons, etc., I assume you are talking about the footer way at the bottom of the page. For now, that is just some experimentation that is being gone through. Like the tabs, it is not entirely final. But, the Google+ and the Facebook buttons are on the user’s account, not ATW’s. What I mean is that when one clicks on the Facebook button, one is connected to one’s Facebook account, not ATW’s; ATW does not have a Facebook page and, with all probability, never will. Finally, the Twitter button is not for tweeting; it merely subscribes the user to ATW’s newsfeed (which, as you can see, is highly popular Face-smile-big).

I hope this clarifies things somewhat. I too am not overly sympathetic to Wikia’s social networking plans, but these small implementations let us here at ATW approach that realm on our own terms. Face-smile Thanks!SpikeToronto 10:43, January 9, 2012 (UTC)

While I disagree with your logic, I do understand it and I won't press that further. However, can you remove the blog listing. We never use blogs and it just clogs up space. Best, --Kangaroopowah(Talk) 02:34, January 10, 2012 (UTC)
We also cannot be too hidebound and rigid in the face of new technology and opportunities. It is one thing to become a social networking site, but it is another thing altogether to use some of the tools of social networking to enhance the quality of a non-social networking site and to improve its productivity. Think of their use here as merely productivity tools. Face-smileSpikeToronto 07:02, January 11, 2012 (UTC)
Yes but all the blog does is take up space. It has almost never used and it just takes away from the niceness of the main page. You say that it will improve our productivity? I seriously doubt that. --Kangaroopowah(Talk) 21:12, January 15, 2012 (UTC)

┌────────────────┘
Hey ’roo. When I first read your comment, back when you posted it, I didn’t really have anything to add. But, since you’ve nudged me to take another look, here are some thoughts. Visually the bloglist takes up space because the left side of the main page is currently tabbed. As I said, the tabs may be dropped, with us returning to the fully opened up mainpage; I seem to be the only one who likes the tab idea. And, while I like the tabs, I do not like the imbalance it creates between the two sides of the page. As for productivity, I was referring to the rest of the right, mainpage, “siderail” and other things to be added to it. The bloglisting is not intended to be a productivity tool, per se. Hence why it is at the bottom of the column. From time to time, certain blogs, could fall into the productivity category when they are presenting new changes to the wiki in greater detail than a sitenotice or tweet permits. For the most part, however, the blogs are for community building. I would like anyone who wants to, to write a user blog on whatever topic is of interest to them (so long as it is not simply nonsense, and is coherent, salient, and has something to say). I’d even like to see Kangaroopower write a blog! St. Valentine’s Day is coming up. Want to give us your thoughts on love and romance? The St. Valentine’s Day Massacre? Whatever you did it would be uniquely your own and topical! — SpikeToronto 06:40, January 22, 2012 (UTC)

Changing skins

{{Edit protected}}

- [[Admin Tools Wiki:Wikipedia skin|Click here]]

+ [{{fullurl:{{FULLPAGENAME}}|useskin=monobook}} Click here]

--218.186.15.10 (talk) 08:53, March 14, 2012 (UTC)

Thanks for your suggestion, 218.186.15.10! The only thing is, the two things are not equal.
  • [[Admin Tools Wiki:Wikipedia skin|Click here]] takes the reader to a set of instructions for changing from the default Oasis skin to the Monobook skin, from that point on.
  • [{{fullurl:{{FULLPAGENAME}}|useskin=monobook}} Click here] displays the current page in the Monobook skin. Once the visitor leaves that page, their skin reverts back to Oasis.
Being able to look at a particular page in Monobook would not be a bad idea. This can be done by adding the skin switch script skinSwitch.js to your personal JS. Face-smile Thank youSpikeToronto 03:04, March 15, 2012 (UTC)
Then what about just adding "To view Admin Tools Wiki in MonoBook anonymously, although you will still see advertisements, [{{fullurl:{{FULLPAGENAME}}|useskin=monobook}} Click here]" to Admin Tools Wiki: Wikipedia skin? — Preceding unsigned comment added by 218.186.15.10 (talk) , 04:22, March 17, 2012 (UTC)
But, what you suggest will only show that page in Monobook. Once you surf to another page at ATW, it will go back to Oasis. Here, give it a try on this page, and then afterwards surf to another page on the wiki and see what happens:
Click here
If you want to discuss this some more right now, you can join our IRC channel #admintools. I’m there right now. Or, we can continue discussing it here on the talk page. Face-smile Thanks!SpikeToronto 04:30, March 17, 2012 (UTC)

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.