FANDOM


(Favicon discussion)
m (my 2 cents)
Line 256: Line 256:
 
::You already see the tooltip on the 3rd design yes? I was going to put the restriction, item descriptions and other info that would make it more in line with the in game tool tip. Its fairly complete with a few missing bits. I could even transform the rune numbers into some squares to represent the number of runes it could have. More polish than revolutionary work. --{{User:Tierrie/Sig}} 18:25, October 9, 2010 (UTC)
 
::You already see the tooltip on the 3rd design yes? I was going to put the restriction, item descriptions and other info that would make it more in line with the in game tool tip. Its fairly complete with a few missing bits. I could even transform the rune numbers into some squares to represent the number of runes it could have. More polish than revolutionary work. --{{User:Tierrie/Sig}} 18:25, October 9, 2010 (UTC)
 
:::I like the idea of including the number of runes, as well as restriction (since that's included in-game), but the item description might make the tooltip really big depending on the equipment piece, unless the font is smaller. --'''[[User:D-day|D.]]''' <span style="font-size:8pt">([[User talk:D-day|talk]] '''·''' [[Special:Contributions/D-day|contr]])</span> 18:48, October 9, 2010 (UTC)
 
:::I like the idea of including the number of runes, as well as restriction (since that's included in-game), but the item description might make the tooltip really big depending on the equipment piece, unless the font is smaller. --'''[[User:D-day|D.]]''' <span style="font-size:8pt">([[User talk:D-day|talk]] '''·''' [[Special:Contributions/D-day|contr]])</span> 18:48, October 9, 2010 (UTC)
  +
  +
:::My thoughts pretty much align with D-day's on the tooltip. I would miss the strength modifier column however since removing it reduces your ability to make a good decision on weapons based on a quick look at the table. An alternative possibility I suppose would be to have the damage column list damage*strength modifier instead of just the base damage. [[User:-Vim-|-Vim-]] ([[User talk:-Vim-|talk]]) 18:12, October 14, 2010 (UTC)

Revision as of 18:12, October 14, 2010

Forums: Index > Wiki Discussion > Project Flemeth: Shapeshifting the Wikia's Look
Note: This topic has been unedited for 3324 days. It is considered archived - the discussion is over. Do not continue it unless it really needs a response.

I started a new Dragon Age Wiki:Project Flemeth that encompasses the thematic changes that comes with the new Wikia skin. If you have artistic skills, have opinions, or just want to help out; I encourage you to read the Project and contribute any way you can. It could be as easy as finding pages and marking it with {{Adjust}} or making images, or suggestions. Cheers! -- tierrie talk contr 20:35, October 7, 2010 (UTC)


Wikia's new look is a major change to the way the Wikia is presented. Some of the templates like the Template:InfoBoxes now take up more space than they are worth. Other pages are compressed to the point where it no longer looks acceptable. The table of content and the front page of this Wikia also needs to be revised to allow the user the easiest navigation to the content.

Therefore, the purpose of this project is twofold:

  1. To revise the front page of this Wikia by improving the aesthetics and allowing a user easiest access to information
  2. Updating templates and pages to accommodate the fixed-width nature of the new Wikia


This project is in its first phase - identifying problem pages, soliciting feedback and brainstorming for design ideas.


Identifying "problem" pages

Changes to the skin should not affect the proper display of most pages. Some pages, however, will display incorrectly in the new skin. Initially, we will just identify these "problem" pages. If/when the switch to the new skin is imminent, the goal will switch to actually making the required changes.

Width

One of the largest changes in the new skin is the introduction of a 'fixed-width' content area. Pages will no longer stretch to fill the width of a screen. Instead, the width of all content on the wiki (Excepting the main page) will be restricted to 660 pixels in width. (See: Transition guide at the community wikia.) As much of our content was designed for a much larger viewing width, some templates, tables, and articles will not fit into a 660pixel wide area. Any pages that don't currently fit this size will need to be changed.

Category

If you see a page that looks like it won't display correctly in the new skin, please add {{Adjust}} to the page, and if needed, start a discussion for what changes will be required either on this project page or the article's talk page. Use discretion: if the required change is obvious (and uncontroversial), there's no need to start a discussion. However, if there is any doubt that the change would be accepted by all, err on the side of caution and start a discussion.

Layout Changes

InfoBox

Almost all our pages utilize InfoBoxes which took up a nice chunk of horizontal space in the old format. In this new one, that chunk represents nearly 30 to 40% of the 660px width available to our wiki. So, in order to maintain some semblance of sanity, the InfoBox needs to be moved, reworked, retooled or otherwise molded into a form that is acceptable to the new Wiki.

Thematic Changes

Background

Discussion at #Background discussion The splatter background has served us very well in the past but in the process of overhaul it would be nice to see if there are any other options or suggestions for background that might be an improvement over this one. If you have a mockup or a suggestion please contribute to the discussion.

Navigation

Discussion at: #Navigation discussion The navigation sidebar will be removed. In its place, there will be 4 links alongside the wiki's logo, each with 7 sub-links. As we have more than 32 links in our current navigation, we will have to reorganize our navigational links to accommodate this new style. The finalized (i.e. agreed upon) navigation will be included here.

Wordmark

Discussion at: Forum:Wordmark We need to update the Wiki's logo with what is called a word mark. Currently the Wiki's logo is this, and we're taking new suggestions for the logo. Mass Effect's wiki has some examples of gorgeous works and its a great starting off point for suggestions. Time to break out that artistic skills!

Favicon

Discussion at #Favicon discussion Although it isn't just for the new skin, a new favicon could replace the current one. The size should be 16x16, and should be transparent if it doesn't use a background. You can convert them through Converticon to test them. Post the icon(s) in .png format so everyone can see them here.


Discussions

Background discussion

Navigation discussion

The rules for the navbar is as follows

  1. 4 main categories
  2. No subtrees
  3. Should cover as many of our main sections as possible

Style 1

Here's my first suggestion

  • Dragon Age (to the Portal, not to the skimpy article)
    • Codex
    • Companions (or Characters?)
    • Classes (or Skills?)
    • Creatures
    • Downloadable Content
    • Equipment
    • Gifts
    • Location
  • Dragon Age 2
    • (to be filled out closer to the game release)
  • Guides
    • Achievements
    • Gifts
    • Romance
    • Quests
    • Walkthrough
  • Community
    • Forum
    • News (or Recent Blog Posts)
    • Manual of Style
    • Rules and Policies (or Community Guidelines)


Style 2

While I like #Style 1, it wastes an entire section for DA2 which isn't coming out for a while. Instead, I suggest we use this for a few more months until DA2 part of the wiki is fleshed out.

  • Dragon Age Series
    • Dragon Age: Origins
    • Dragon Age 2
    • Downloadable Content
    • Dragon Age: Origins - Awakening|Origins - Awakening
    • Dragon Age Journeys|Journeys
    • Dragon Age: The Stolen Throne|Novel - The Stolen Throne
    • Dragon Age: The Calling|Novel - The Calling
    • Dragon Age (comic)|Comic
    • Dragon Age (pen and paper RPG)|Pen and Paper RPG
  • Gameplay (for adjectives/verbs)
    • Achievements
    • Approval (or Gifts?)
    • Attributes
    • Romance
    • Quests
    • Skills
    • Spells and Talents
    • Walkthrough
  • World (for objects/nouns)
    • Codex
    • Companions (or Characters?)
    • Classes (or Skills?)
    • Creatures
    • Equipment
    • Gifts
    • Location
  • Community
    • Forum
    • News (or Recent Blog Posts)
    • Manual of Style
    • Rules and Policies (or Community Guidelines)


-- tierrie talk contr 23:34, October 7, 2010 (UTC)

Favicon discussion

Basic icons:

  • [1] This is the "D" from Origins. This isn't the one on BioWare's official page... this one is transparent, yay.
  • [2] ... and the "D" from DA2.

I've tried adding blood spatter, but so far, I haven't been satisfied with them (hard to read). --D. (talk · contr) 01:39, October 14, 2010 (UTC)

Here's a couple I mocked up

Style 1

Ico fav01 Ico fav01 Ico fav01

Style 2

Ico fav02 Ico fav02 Ico fav02

Style 3

Ico fav03 Ico fav03 Ico fav03

Style 4

Ico fav04 Ico fav04 Ico fav04

Style 5

Ico fav05 Ico fav05 Ico fav05
I would like to stay away from the D because that's being used by BioWare. If we take their same design it might be pushing the fair use a bit too far. -- tierrie talk contr 02:52, October 14, 2010 (UTC)

General Discussion

You (or any admin) should edit the Community Corner and probably make a blog post regarding the upcoming changes. The site notice got canned with the new skin (because of the SEO, and because it's too big... Wikia's reasonings). --D. (talk · contr) 20:51, October 8, 2010 (UTC)
Is Community Corner even used in the new Wikia? -- tierrie talk contr 22:52, October 8, 2010 (UTC)
Yes, it's still in the Wiki Activity. Whether people are going to see it is another issue (I never use MyHome). --D. (talk · contr) 22:58, October 8, 2010 (UTC)
I just learned that they've added a feature regarding the Community Corner. "Users who are active on the wiki up to 24 hours after the community corner is changed will receive a notification about the change, similar to the notification for user talk page messages. These will disappear after 24 hours if not previously dismissed by the individual users." --D. (talk · contr) 15:55, October 9, 2010 (UTC)
I just looked through MediaWiki:Community-corner and it looks like its supposed to be news. I don't see any news in my Wiki Activity section. Is that right? -- tierrie talk contr 21:09, October 11, 2010 (UTC)
The blog posts/news were added by Loleil, they're not here by default (they also overflow). The section "Thanks for visiting" is what you want to edit, or you can make another section specifically regarding the announcement. I think we all get a little sticky note (you probably got it before), but I don't know if the message on the sticky note can be changed. I haven't seen it being widely used yet (I only know of Canaanpedia, and that's because of this forum post). Blog posts seem to be more used, and would probably attract more users (since the Community-corner sticky note only shows up for 24h, which is too short). --D. (talk · contr) 21:31, October 11, 2010 (UTC)
What I meant was that I don't see it in the wiki. I assume its supposed to render on the right side of the screen, but it does not. On what pages do the corner appear to you? Maybe something's broken on my end. -- tierrie talk contr 04:37, October 12, 2010 (UTC)
Yes, it's right under the "hot spots". Have you tried looking with another browser? --D. (talk · contr) 06:00, October 12, 2010 (UTC)
I typically use Firefox with IETabs. I should clarify: I see the community corner in monaco, but I do not see it on wikia. My question was whether it is used in wikia skins. -- tierrie talk contr 20:45, October 12, 2010 (UTC)
Yes, it appears on the new skin. Have you looked with another browser, or on another wiki (logged in and as an anon)? --D. (talk · contr) 21:00, October 12, 2010 (UTC)
Looks like it does appear on Special:WikiActivity. I usually use Special:RecentChanges instead as it presents me with everything in a statistical manner. That might explain my confusion. Does it community corner appear on any other pages? -- tierrie talk contr 21:19, October 12, 2010 (UTC)
Afaik, no. --D. (talk · contr) 02:42, October 13, 2010 (UTC)

This isn't exactly within the project, but perhaps it's time for a new favicon? --D. (talk · contr) 02:42, October 13, 2010 (UTC)

Haha, put it in the scope of work! :) -- tierrie talk contr (talk) 04:34, October 13, 2010 (UTC)

Suggestions

My observations for now, in no particular order:

  • Article management tags will have to be resized. They become a problem when used with infoboxes (see The Reaper's Cudgel for an example).
  • The padding for tables can be reduced to 0.2 or 0.3. It effectively saves spaces, both in width and height.
  • For pages listing items in tables like longswords, the notes column should be changed. I don't think the description is necessary, but we should keep the notes if the item is from a DLC or in another expansion game, or if it is restricted to a character or class, or where it is found or how it is obtained (this is debatable as there is a consistency issue regarding this).

--D. (talk · contr) 15:52, October 8, 2010 (UTC)

I got a few ideas for ItemInfoBox.
  1. The first is where we can "hide" the ItemInfoBox and replace it with an icon like the spoiler. Clicking on the icon would expand the Spoilers. We can round the corners, and animate it with jQuery. It could move the article aside as it expands or it could float / hover above the article. It could remain "expanded" until turned off with a X, or it could remain "expanded" while the mouse cursor is hovering
  2. The next idea is to remove the ItemInfoBox element and move it to the left of the WikiaArticle page. This essentially gets around the width limitation by putting a hovering element to the left of the article space. That element could also open/close and scroll as the page scrolls. This idea breaks the Wikia's concept of a fixed article width and I don't think it is a good idea to do this.
  3. The third idea is to find a way to move the element to the RIGHT of the article space into the space reserved for the Recent Activity, Uploaded Photos, etc section. This is a lot harder since a css solution will most likely just float over those sections and block users from seeing it. The other solution is to hack together some javascript that took the div out and reinserted it in the right side onload.

I'll post more ideas as I come up with them. -- tierrie talk contr 19:28, October 8, 2010 (UTC)

I'm not sure with the iteminfobox. When expended, it's still going to screw up the article layout. Moreover, it seems to involve too much clicking, unless cookies are saved. I would not recommend using javascript for anything that is necessary for the wiki, unless a javascript-free option is presented.
There's going to be problems with using the sidebar or adding additional content outside the WikiaArticle space, as these suggestions break the ToU by shifting content around. Moreover, there are ads on the sidebar. --D. (talk · contr) 20:35, October 8, 2010 (UTC)
I agree that we shouldn't really be moving things outside the article space. I'm throwing ideas out there and seeing what sticks. -- tierrie talk contr 22:43, October 8, 2010 (UTC)


Style: Weapontable

One of the other options I considered during the early days when I designed this was to reduce the number of cols. Some columns can be merged to save horizontal space. For example

Instead of

Name Damage
Critical chance Armor penetration Strength modifier Runes Enhancements Notes

Blightblood may refer to:

Disambig gray This disambiguation page lists articles associated with the same title.
If an internal link led you here, you may wish to change the link to point directly to the intended article.


We can do this

Name Damage Enhancements Notes
Blightblood

Dragonbone
Requires: 31 strength

Damage: 11.20
Critical chance: 3.20%
Armor penetration: 4.00
Runes: 3
+3% melee critical chance
+2 attack
+10% critical/backstab damage
Poison: Venom
Restriction: Rogue


The tradeoff is that we can no longer sort by damage.

Alternatively, I can use the tooltip so that we can present minimal information in the table, and put all the info in the tooltip itself, like so (the tooltip needs to be expanded)

Name Damage Critical chance Armor penetration Enhancements
Blightblood may refer to:
Disambig gray This disambiguation page lists articles associated with the same title.
If an internal link led you here, you may wish to change the link to point directly to the intended article.

Dragonbone
Requires: 31 strength

11.20 3.20% 4.00 +3% melee critical chance
+2 attack
+10% critical/backstab damage
Poison: Venom

This does not have to be the final design, but we do need to implement something quickly based on what we perceive to be "most broken" from the Wikia change. We can always come back and revise them later. -- tierrie talk contr 23:10, October 8, 2010 (UTC)

I like the third format you are proposing. It's compact and I like the use of icons (I like seeing them). If another column must be added (I don't know for what though?), the columns for damage and critical chance can be further reduced. I'm just wondering what you have in mind for the tooltip. --D. (talk · contr) 00:42, October 9, 2010 (UTC)


You already see the tooltip on the 3rd design yes? I was going to put the restriction, item descriptions and other info that would make it more in line with the in game tool tip. Its fairly complete with a few missing bits. I could even transform the rune numbers into some squares to represent the number of runes it could have. More polish than revolutionary work. -- tierrie talk contr 18:25, October 9, 2010 (UTC)
I like the idea of including the number of runes, as well as restriction (since that's included in-game), but the item description might make the tooltip really big depending on the equipment piece, unless the font is smaller. --D. (talk · contr) 18:48, October 9, 2010 (UTC)
My thoughts pretty much align with D-day's on the tooltip. I would miss the strength modifier column however since removing it reduces your ability to make a good decision on weapons based on a quick look at the table. An alternative possibility I suppose would be to have the damage column list damage*strength modifier instead of just the base damage. -Vim- (talk) 18:12, October 14, 2010 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.