<p>Just wondering if maybe for the next event the front page poll for favourite new girl shouldn't include the Abyssals (or, at least reskin versions). I mention because this looking at the recent one the clear winner is the re-coloured of Cruiser Tsu, and to be presumptious here I doubt that most people actually consider a pre-existing enemy painted a new colour as their fave, and I suspect someone may have repeatedly voted for a laugh. </p>

<p>Hello! </p><p>I am Jr Mime, a Fandom Wiki Manager for this community, the lovely Kancolle Wiki. </p><p>I am here to help the community, you, for any questions, issues about the wiki, editing, formatting, scripting, etc. I am also a liaison to full-time Fandom staff members. </p><p>Feel free to contact me on my talk page for any specific questions, or directly post on this forum thread. </p><p>It will be a pleasure working with you! - Jr Mime (talk) _[VSTF] 22:31, May 16, 2019 (UTC) </p>

<p>https://twitter.com/KanColle_STAFF/status/1090779006348156928 </p><p>The official clarified that they did not make any DMCA claims. May the administrators forward this message to Famdom? </p>

<p>Around October, a certain staff member who was running the public discord went rogue, doing very bad things, all of which has now been known as the TLBA incident. Although the incident has been resolved, what was known as the Public Wikia Discord was reduced to rubble and ruins. Seasons have passed, cicadas were crying and kuso's were busy sinking their ships, but today, we proudly announce that the Public Wikia Discord has finally been restored to fully functional conditions and will open up once again! </p> <h2><span class="mw-headline" id="So.2C_what_changed.3F">So, what changed?</span></h2> <p>The first thing we did was get rid of the discord partnership, as the perks did not help us at all and it only caused more trouble than it was worth. As a result, we are able to provide a more relaxed stance on the rules as well as increase the tolerance level. To give an example, images that might have been classified as NSFW under the old guidelines might no longer be banned under the new ones (it's not a porn galore though, mind you). </p><p>As part of the restoration, we have assembled a new team of moderators to help us out with this project. Some are familiar, some are newfaces, but they all share the same excitement in wanting to work together with the community in order to create a fun place for us admirals to enjoy. Also, there won't be a second TLBA, <s>or at least we hope so</s>. :> </p><p>Unlike its previous incarnation, this server will start at a much smaller scale. The current server consists of the following: </p>

• Announcement channels to provide you with the latest dev tweets and the announcements the Wikia staff wants to make to the community.
• A lounge for your everyday discussions.
• An art corner, for you know, art.
• A dedicated channel for Wikia related support.
• Channels for providing suggestions or ideas to improve the server/wikia.

<p>As time passes and the server grows though, we will slowly expand and build upon the suggestions the community provides us with in order for us all to feel home here. </p><p>If any of the above piqued your interests, don't wait and join right away using the following discord link: https://discord.gg/HT32GFQ </p>

<p>Maybe I am not getting the correct understanding of the editor, but well: </p><p>
</p><p>
When I try to edit the box (table) in the top-right corner of such a page, it does not show up after clicking "edit". </p><p>For example: https://kancolle.wikia.com/wiki/Sagiri </p><p>I tried to add world 7-1 as a place to drop, but I could not find the position for this data in edit-mode. As if the code for this box is filtered. </p><p>Is this a bug? Can it be helped somehow? </p><p>I noticed outdated data for a few other shipgirls as well, but I am having the same issue at their pages. </p>

<p>After a spat between the internal disputes within staff leading up to de-linking of KC wikia and KC wikia (public) Discord along with growing distrust between KC wikia members including myself. I want to convey that I am retiring from the scenes as described above, before I take my leave there are a few topics I want to address. </p><p>First and foremost is that I thank you all for your cooperation with both myself and the KC wikia operations thus far and for spending your time with me. It has been a long journey and I intend to move onwards with my life. </p><p>The topic I want to address most importantly with the collaboration between KC wikia, KC Reddit (Discord) as well as EN KC wiki (Discord). As you all have been aware of the frictions within KC wikia amounted to a growing distrust within staff ranks and that I am to retire from my positions. I shall leave that in the hands of XhacKX (jasperchua99) to maintain the bond between the three English platforms. As some of you may be aware, the re-ignition of the bonds between the three English platforms was not possible without XhacKX's help along with McDerp, to which to these day I am indebited for their continued assistance in making it possible. If in the case of XhacKX being an unfavourable person to contact, you have the following contacts within KC wikia and these are as follows: gk (がか), Mikado (Admiral Mikado), Zel-melon and Kruss. </p><p>With regards to the actual details involving the spat with KC wikia members leading up to the de-linking, this is a topic I do not wish to discuss. For more information you are free to consult with whoever you want as I am no longer interested in discussing the internal politics and shall leave that to whoever wants to take on that role. So please take this into consideration as I am about to formally end as being a point of contact for KC wikia related activities. </p><p>As an added bonus, and for the last topic I want to address. I leave you with some of the imgur albums I have compiled personally. You are free to take these with a grain of salt however I will leave it as it is. As I am formally retiring, I want to make it clear that I no longer hold liable nor accountable for my activities hereforth with KC wikia and any of the collaboration that KC wikia is associated with. </p>

• https://imgur.com/a/fS49ZZL
• https://imgur.com/a/wcv00vR

<p>On a final note to those who have read up to this far. I thank you for once again for having spent your time reading this. With this said and done, I intend to also retire from my duties as an Administrator of KC wikia and will begin a certain sequence of events that are necessary to move on with life. I wish you all the very best of your own goals. </p>

<p>先ずは、私自身の日本語は下手です、申し訳ありません。この日本語版を見る皆さんへ、自動翻訳サービス（例：グーグル翻訳やピングー翻訳や等）を使っていません。ご注意下さい。私は「Crazy teitoku」と申します、ツイッターのアカウントは「@tuxsavvy」と申します。 </p><p>1) 背景情報 8月21日に検証wiki共同メンバーと英wikia共同メンバーを協力関係について初めてミーティングを持ちました。関係共同メンバー及び関係共同メンバーの役職についてはこれを見て下さい： 検証wikiaのメンバー：
＊びいかめ氏（共同代表、引退しました）、
＊ウィル氏（共同代表、引退しました）、
＊Ki_puzzle氏（現代表？、引退します）、
＊夢路氏（役員？引退しました）
英wikiaのメンバー：
＊jasperchua99氏 (英wikiaのdiscordの創立者、英wikiaのコンテンツ・モデレーター）、
＊がか氏（英wikiaの運営担当およびビューロクラット）、
＊御門（提督）氏（通訳担当、英wikiaのアドミン）、
＊私（通訳補佐、英wikiaのアドミン）
会議はdiscordで行われました、特に非公開グループチャットと非公開チャンネルにおいて。 </p><p>2) 目標とその後の経過について 検証wikiからの共同代表と役員、および英wikiのメンバーはdiscordでミーティングを行っていました。最初のアプローチは検証wiki共同メンバーによって行われました。当初の計画では英wikiの設計を使い、検証wikiを攻略wikiのような完全なwikiにリフォームする予定でした。先ずは通常海域（例：鎮守府海域や、南西諸島海域や、北方海域等）を初めに作ります。後で、イベント海域を作るつもりでした。英wikiの海域などのデータ（例：艦娘や、装備や、その他のデータ）を使う予定でした。 しかし、目標はデータ等をそのまま移植するだけではなく、英wikiの財産を翻訳することで、日本人のためにわかりやすい日本語のwikiを作るつもりでした。最終的な目標は、英wikiのデザインをもとに独自のwikiを作ることにありました。 この協力関係は公式のものではありませんでした。というのも、計画について話し合う途中に検証wikiでの内部紛争が発生したからです。検証wikiの内部紛争については非公開チャンネルとツイッターからある程度は理解しています。

検証wikiのメンバーと英wikiのメンバーの協力のもと、検証wikiでの作業は既に始まっていました。しかし、同時に初秋イベントが始まったため、検証wikiでの作業の進捗状況は一時的に止まりました。双方ともにやるべきことで手が一杯でした（新しいイベント情報の整理、イベントの進行、およびその他諸々の雑務もありました）。最終的に「翻訳と検証wikiでの作業を一時的に停止しましょう」と検証wikiのメンバーが提案しました。この原因は検証wikiの内部紛争にありましたので、内部紛争の解決が優先されました。

検証wikiのメンバー間の内部紛争と検証wikiが解散する前の時点で沈黙の瞬間が山ほどありました。「一体何が起こっているのだろう」と私たち英wikiのメンバーは考えていました。大まかな原因は知っていますが、詳しくはわかりませんでしたから、本当の原因は何だろうとたくさん思索しました。

3) 後処理と現時点での考え 英wikiでの連絡、通信や翻訳を担当している人はびいかめ氏から「この協力関係を解消して下さい」とのメッセージを受け取りました。ウィル氏も同様の考えでした。理由は「翻訳に割ける人員がいないこと、また組織を縮小すること」でした。

検証wikiと英wikiの協力関係中に実際何があったかどうか、そして検証wikiの内部で何が起こっていたか、今でも、はっきり確認できていません。しかし、全ての英語の艦これSNS/Wikiサービス（英艦これRedditと、英艦これWiki、と英wikia）はこの協力関係には興味が津々でした。ですから、今でも一緒に協力してくれる日本人を探しています。そもそも「艦これ」は日本人のためのゲーム、そして日本語で作られているゲームです。ですから日本人と一緒に協力するのは最高だと考えています。

検証wikiの内部紛争についてもっと情報を集めるまで、「協力関係を完全に解消します」とは私自身言いたくはありません。明言しておきますが、私たちは検証wikiの内部紛争には関わっていません。ですから、内部紛争と関わりなく、今も検証を続けている人たちと対話したい、そして理解したいと考えています。現状はこの協力関係はあくまでも一時的な解消です。私たちは新たな対立を引き起こすことは望んでいません。あくまでも慎重にアプローチをしたいと思っています。

ずっと前から私は英語と日本語の艦これコミュニティを結び付けたいと思っています。でも今日まだそれは「緊張をほぐす」程度の段階のような気がします。あまり日本語でコミュニケートできませんし、ポリシーの違いもあります。ですから、今はまだ傍観者でいようと思っています。ブロークンな日本語で意見を言おうとは考えていません。

この日本語版は匿名の日本語話者によって編集されています。

Formal announcement to (temporarily) discontinue the collaboration with Kensho wikia (ja.kancolle.wikia.com): </p><p>First and foremost, I have to apologise with my crap Japanese. Those of you reading only my Japanese version of the announcement, please be aware that I am not using machine translation tools (Google Translate, Bing Translate, etc). I am Crazy teitoku, also known as "@tuxsavvy" on twitter. </p><p>1) Background information On August 21st there was a meeting between Kensho wikia members amongst the select few staff members from English Kancolle wikia. The members and their roles are as follows: Representing Kensho wikia: </p>

• biikame (co-chairperson, retired),
• Willlain (co-chairperson, retired),
• Ki_puzzle (co-chairperson, current but retiring),
• yumeji (member of the board?, retired)

<p>Representing English Kancolle wikia: </p>

• jasperchua99 (founder of English KC wikia Discord, content moderator),
• gk (Responsible for English KC wikia operations, sole bureaucrat),
• Admiral Mikado (Interpreter, admin on English KC wikia),
• myself (Crazy teitoku, lesser translator, admin on English KC wikia)

<p>The discussion happened in Discord, mostly in private areas such as group direct messages and private channel. </p><p>2) Proposals and visible changes Kensho wikia co-chairpeople along with members of their board members approached us on KC wikia via the Discord server initially with the intention to use English KC wikia's layout as a base to transform their Kensho wikia into a full-fledge wiki (similar to Kouryaku wiki). Starting off with the regular world maps but with intentions to also focus on event maps and other existing assets (such as ship girls, equipment, etc) that English KC wikia has. This is not just a simple affair of copy and pasting English contents onto Kensho wikia as-is but the intention was to translate into Japanese so that Japanese readers can understand the content. </p><p>The collaboration was not deemed official as the proposed changes has not been fully made and that there were internal disputes within Kensho wikia as was later revealed in both the private chat on Discord as well as twitter. </p><p>A few of the members from both sides has been involved in laying the initial stages on the Kensho wikia but because Early Fall 2018 Event was underway it was difficult to concurrently handle several tasks at once (updating wiki with event information, dealing with the actual event, etc) from both sides. Ultimately Kensho wikia members decided to temporarily halt their translation operation on their side and to deal with internal disputes as a priority before continuing on. </p><p>There were several moments of where the communication between the two parties were quiet including the time when Kensho wikia members were to deal with the internal disputes leading up to disbanding what was then the representatives from Kensho wikia's side. On English Kancolle wikia side, not a lot of information was known on what was happening in Kensho wikia's side during those quiet times however there were speculations on what may have happened. </p><p>3) Aftermath and final thoughts biikame from Kensho wikia who has been communicating in both Japanese and English with members of private group chat decided to formally announce the discontinuation in the translation project citing the lack of members available along with scaling back of their operations. </p><p>What wasn't and hasn't been made clear to this day was exactly what had happened internally during the informal collaboration between the two wikis. At the time there were hype from mostly the English KC platform (consisting of primarily KC Reddit, EN KC wiki and KC wikia) that we were able to be able to work with Japanese and to build a bridge with them considering afterall KC is a Japanese game. </p><p>Personally, I was hoping to be able to continue working with members of the Japanese KC side and consider this discontinuation as temporary until more information can be gathered on exactly what had happened. A few members has been wanting to salvage what was then the Kensho community but to my knowledge they are not involved with commenting directly on the now disbanded Kensho wikia's forums. Those of us who still wants to salvage the members are doing so via a more cautious approach that doesn't involve open confrontation and being ignorant on the whole issue. </p><p>To this day, I have been keenly wishing that the English KC community could be able to break the ice between the Japanese KC community however it has been very tough despite not being able to communicate in Japanese and not agreeing with some of their policies. I continue to observe their proceedings and wish to not be loud as to announce with my broken Japanese. </p><p>The Japanese version of this announcement was proofread by an anonymous proofreader. </p>

<p>So I just found out the Rinkichou trivia I added to Asashio's page just got deleted, so did the Japanese-Taiwanese source dispute about Tsushima's fate and final role, and let's just say having your hard work reverted by the click of a finger isn't necessarily the most enjoyable thing on earth.

Yes, I can imagine that these are probably not important to some, but hey, this is the trivia section. If the most serious shipbuilding scandal in the whole history of the IJN aren't important enough even just to be part of "trivia", I don't think I'm sure what is important enough instead. (The "I am Aoba" trivia I added to Aoba's page survived, though)

Perhaps I should ask the opinions of the moderators here before adding more? I've been thinking about adding, say, Intrepid's nickname in the Japanese players' community (and some other "what-I-think-are-trivia" stuff) for a long time, but after all this I'm not sure if I should do that anymore.
Edit: I just checked some more pages and the scale of this so-called "cleanup" is beyond what I first thought. There are descriptions about the ships' fate and wreck information being deleted, which are very, very basic elements of trivia.
Seriously, I have to ask: just what are the mods' plan for trivia sections? Are you guys planning on keeping it at all? </p>

<div class="center"><div class="floatnone"></div></div> <p>For those of you who are familiar with Discord service, we now have a public server in which you can interact with other KC wikia players along with KC wikia staff! </p><p>The link to the public server is here (in case you cannot see the Discord link to the right of the Kancolle Wikia interface): </p> <div style="font-size:24px; color:blue; text-align:center; font-weight:bold; margin:25px 0px 10px 0px;">https://discord.gg/vEnBuqv</div> <div style="font-size:18px; color:black; text-align:center; font-weight:bold; margin:25px 0px 10px 0px;">We Look forward to seeing you there!</div> <p>
</p>

<p>Update: currently, using visual editors <i>may</i> be ok. It is still a good idea to use source editor for pages that use advanced coding (for example, templates), such as event pages. </p><p>To anyone planning on editing the wikia, go to your preferences and change the preferred editor to source. Classic rich-text editor is bugged at the moment and using it would only ruin the page layout every time you click edit. </p><p> </p><p>To get some assistance with how to use source editor, you may want to refer to this page. </p><p>More technical information will be edited into this OP thread, so stay tuned. </p><p>Technical information: </p>

• This issue mainly affects "public namespaces". Examples of these include (but are not limited to):
  • Winter 2018 Event
  • Events
  • Quests
• You do not need to run the same test for your own comments, user page, talk page or even any page within Sandbox. The bug will be isolated to those areas and are not deemed as critical to anyone else except yourself. However, you will need to disable visual editors and classic rich-text editors when editing public facing pages *especially* the ongoing (as of writing) Winter 2018 Event.

<p>Credits: </p>

• Tsubakura

<p>I am fully aware that the debate on the designation for the Kaibokans has long ended. However, I found that the direct USN equivalent is a Patrol Coastal Escort. Hull/ ship designation PCE. Has anyone else come across this designation? </p><p>Similarities: </p><p>-Displacement  </p><p>-Roles: Convoy escort, coastal defense, ASW focus </p><p>-Speed and propulsion: Diesel engines, speed </p><p>Sources  </p><p>http://www.navsource.org/archives/12/02idx.htm </p><p>https://en.wikipedia.org/wiki/PCE-842-class_patrol_craft </p>

<p>Greetings, </p><p>Seeing that after the implementation of the October 25 Update or September Ranking Rewards the Wikia has implemented a new template specifically designed for equipment pages, I would like to know how can these be edited, or where to find information regarding the new template. </p><p>Regards. </p>

<p>
<font size="5">KC3KAI HAS BEEN FIXED! You can update it manually by enabling Developer mode and force update your Extension. If you have no idea what I just said, follow the steps here: https://github.com/KC3Kai/KC3Kai/wiki/Updating </font> </p><p>
For those who are in need of information. KC-Reddit (in name only) Discord are a good source that can help provide you with fast but uncertain information: https://discordapp.com/invite/RtSadWM </p> <hr><p>A lot of you (those who started the event) will notice by now that the viewers, specifically, KC3-Kai, the browser extension that majority of us in this English community used, to put in an easy to understand terms, is screwed. </p><p>To elaborate a bit, this is due mainly to the implementation of the new 7-ships fleet and the new formation (the phallic looking one), which all rooted back to API-issue. In order words, imagine you're in charge of delivering a package but the address changed overnight so now you're trying your best to salvage something but not to the optimal result. </p><p>As such, convenient tools such as "Battle Predictors" WILL NOT WORK. Additionally, Replays and Records will not act properly. You WILL SEE a bunch of errors showing up. Please understand this. </p><p>Furthermore, this also affects us, the editors/staffs who put these up as the flow of information will become slower due to inaccessibility to easily-obtainable data, e.g. routing. As such, editing will be slower to ensure accuracy although trigger-happy mammals can still update information. </p><p>As to some other bugs that might show up: </p>

• 0 Resources if you're around hard-cap
• PvP not working properly

<p>These should be fixed soon, hopefully. </p><p>Please understand this situation, thank you. </p><p>NOTE: Just in case (some people did ask before), we do not have any affiliation with the developers who made Kantai Collection (TM). We are a bunch of volunteered <s>slaves</s> editors providing information to the English community that is kinda recognized by the JP community. </p>

<p>Hi Kancolle Wiki </p><p>FANDOM is conducting a small test that will compare usage of the Visual Editor with the usage of the classic editor. The purpose of the test is to determine which editor brings more success to newer users. As part of that test, we will be disabling the Visual Editor as the default editor on this community for several months. Users who have the Visual Editor selected in their user preferences will get the classic editor when clicking the main 'Edit' button during the test period. However, VisualEditor will remain available as the secondary editing option on the 'Edit' drop-down menu. </p><p>I am letting the community leadership know about this test since some users may be surprised by the altered experience. Giving them a different experience is the point of the test, of course. We request that you refrain from making any community-wide announcement about the test; to get the most accurate results, it's better for users to have no expectation of a change before they encounter it. Obviously this post is public, and it's fine to point individual users here if they inquire about the change. </p><p>Please let us know if you have any questions! Thank you. </p>

<p>Greetings, fellow editors </p><p>I have been working on some methods to structure a large volume of information and handle navigation of pages clusters (main article and subspaces + partials ecosystem) such as event pages, guides, combat mechanics and of course our front page. Without an index of these pages clusters, it is very difficult for readers find information in the cluster and for our editors to update the pages. </p><p>I have been working on the issue for a while and I have reached some interesting results I would like to share. After that, I will invite everyone to take a look at the new front page design in a sandbox and give feedback / suggestions to improve the design before I make it official. </p> <h2><span class="mw-headline" id="Shiny_new_toys">Shiny new toys</span></h2> <p>What I came up with last December is navigation hubs--a map of a cluster similar to Template:Tutorialportal or Template:Equipmentlist but designed as an individual page instead of a simple table. This allows the application of visual hierarchy to the index without compromising the hierarchy of the page containing the index. </p> <div style="float:left;width:50%;"> <div style="position:relative;overflow:hidden;height:150px;margin:5px;background:rgba(250,250,255,0.1);;border:none"> <div style="position:absolute;z-index:2;overflow-y:scroll;overflow-x: hidden;height:150px;width:100%;"> <h3><span class="mw-headline" id="Tiles">Tiles</span></h3> <p>This results in the creation of Template:Tile. The template is designed to act like an item in search results. It gives a short snippet of the page and a link to the full page. </p><p>The snippet is created by clipping a partial transclusion of the full page. Vertical scrollbar can be enabled as an option </p> </div> </div> <hr></div> <div style="float:left;width:50%;"> <div style="position:relative;overflow:hidden;height:210px;margin:5px;background:rgba(148,101,55,0.4);;border:none"> <div style="position:absolute;top:-80px;opacity:0.2;z-index:1;"></div> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:160px;width:100%;"> <h3><span class="mw-headline" id=""></span></h3> <p>
</p> <dl><dt>Description </dt><dd>A template to generate metro-styled tiles. </dd><dd>These are float:left HTML dividers and they can be stacked horizontally or vertically, creating highly customized table cells. </dd><dd>To stop tiles and other content from stacking horizontally, put {{Clear}} where the stacking should stop </dd><dt>Syntax </dt><dd>Fill in the form below. Some fields can be omitted (see simplified sample for mandatory fields) <dl><dd>{{Tile
</dd><dd>| header=
</dd><dd>| content= </dd><dd>| image=
</dd><dd>| source=
</dd><dd>| size= </dd><dd>| width=
</dd><dd>| height=
</dd><dd>| rgba=
</dd><dd>| text-color= </dd><dd>| text-height= </dd><dd>| image-pos= </dd><dd>| opacity= </dd><dd>| source-pos= </dd><dd>| float= </dd><dd>}} </dd></dl></dd></dl><dl><dt>Main arguments </dt><dd>header <dl><dd>Set the text in h3 header. Default value is hidden </dd></dl></dd><dd>content <dl><dd>Set the content written on top of the tile. To source the content from a partial within the main namespace, use {{:<Page>}} </dd></dl></dd><dd>image <dl><dd>Set the background overlay image. Default is hidden. </dd></dl></dd><dd>source <dl><dd>This field creates a footer with a "See more >" link to the sourced partial. Default is hidden. </dd></dl></dd></dl><dl><dt>Styling arguments </dt><dd>width <dl><dd>Set the width of the tile. Default value is 50%. </dd></dl></dd><dd>height <dl><dd>Set the height of the tile. Default value is 360px </dd></dl></dd><dd>rgba <dl><dd>Set the color and opacity of the tile (see CSS3 Colors tutorial for more information). Default value is 250,250,255,0.1 </dd></dl></dd><dd>text-color <dl><dd>Set the color of the text. This color styling is not restricted to rgba definition. Default value is set by the wiki's theme. </dd></dl></dd><dd>text-height <dl><dd>Set the height of the inner text box. The text box is set to hidden overflow; texts that go outside the set height are cropped. Default value is 288px. </dd></dl></dd><dd>image-pos <dl><dd>Set the position of the background image within the tile. Default value is top:0px;left:0px </dd><dd>opacity </dd><dd>Set the opacity of the background image. Default value is 0.2 </dd><dd>source-pos </dd><dd>Set the position of the "See more" link and the footer. Default value is bottom:20px;right:10px; </dd><dd>float </dd><dd>Set the float direction of the tile. Default value is left. </dd></dl></dd></dl><dl><dt>Full width tile </dt></dl>

{{Tile
|header=Resources management
|content={{:Sandbox/Guides/Resources}}
|source=Sandbox/Guides/Resources
|image=CL_Ooyodo_Kai_321_Full.png
|rgba=188,191,195,0.2
|width=100%
}}

<div style="float:left;width:100%"> <div style="position:relative;overflow:hidden;height:360px;margin:5px;background:rgba(188,191,195,0.2);;border:none"> <div style="position:absolute;top:0px;left:0px;opacity:0.2;z-index:1;"></div> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:288px;width:100%;"> <h3><span class="mw-headline" id="Resources_management">Resources management</span></h3> <p>Sandbox/Guides/Resources </p> </div> <div style="position:absolute;z-index:3;height:16px;bottom:20px;right:10px;"> <p><span style="font-size:12px;">See more ></span> </p> </div> </div> <hr></div> <dl><dt>Double height tile </dt></dl>

{{Tile
|header=Resources management
|content={{:Sandbox/Guides/Resources}}
|source=Sandbox/Guides/Resources
|image=CL_Ooyodo_Kai_321_Full.png
|rgba=188,191,195,0.2
|height=741px
|text-height=628px
}}

<div style="float:left;width:50%;"> <div style="position:relative;overflow:hidden;height:741px;margin:5px;background:rgba(188,191,195,0.2);;border:none"> <div style="position:absolute;top:0px;left:0px;opacity:0.2;z-index:1;"></div> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:628px;width:100%;"> <h3><span class="mw-headline" id="Resources_management_2">Resources management</span></h3> <p>Sandbox/Guides/Resources </p> </div> <div style="position:absolute;z-index:3;height:16px;bottom:20px;right:10px;"> <p><span style="font-size:12px;">See more ></span> </p> </div> </div> <hr></div> <div style="clear:both;"></div> <dl><dt>Quarter tile </dt></dl>

{{Tile
|image=CL_Ooyodo_Kai_321_Full.png
|rgba=188,191,195,0.2
|size=300px
|width=25%
|height=180px
|text-height=113px
}}
{{Tile
|header=high opacity
|image=CL_Ooyodo_Kai_321_Full.png
|rgba=188,191,195,1
|size=300px
|width=25%
|height=180px
|text-height=113px
|opacity=1
}}
{{Tile
|header=reposition
|image=CL_Ooyodo_Kai_321_Full.png
|rgba=188,191,195,0.2
|size=300px
|width=25%
|height=180px
|text-height=113px
|image-pos=top:-60px;left:-60px
}}
{{Tile
|header=default
|size=300px
|width=25%
|height=180px
|text-height=113px
|image-pos=top:-60px;left:-60px
}}

<div style="float:left;width:25%"> <div style="position:relative;overflow:hidden;height:180px;margin:5px;background:rgba(188,191,195,0.2);;border:none"> <div style="position:absolute;top:0px;left:0px;opacity:0.2;z-index:1;"></div> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:113px;width:100%;"> <h3><span class="mw-headline" id="_2"></span></h3> </div> </div> <hr></div> <div style="float:left;width:25%"> <div style="position:relative;overflow:hidden;height:180px;margin:5px;background:rgba(188,191,195,1);;border:none"> <div style="position:absolute;top:0px;left:0px;opacity:1;z-index:1;"></div> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:113px;width:100%;"> <h3><span class="mw-headline" id="high_opacity">high opacity</span></h3> </div> </div> <hr></div> <div style="float:left;width:25%"> <div style="position:relative;overflow:hidden;height:180px;margin:5px;background:rgba(188,191,195,0.2);;border:none"> <div style="position:absolute;top:-60px;left:-60px;opacity:0.2;z-index:1;"></div> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:113px;width:100%;"> <h3><span class="mw-headline" id="reposition">reposition</span></h3> </div> </div> <hr></div> <div style="float:left;width:25%"> <div style="position:relative;overflow:hidden;height:180px;margin:5px;background:rgba(250,250,255,0.1);;border:none"> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:113px;width:100%;"> <h3><span class="mw-headline" id="blank">blank</span></h3> </div> </div> <hr></div> </div> <div style="position:absolute;z-index:3;height:16px;bottom:20px;right:10px;"> <p><span style="font-size:12px;">See more ></span> </p> </div> </div> <hr></div> <div style="clear:both;"></div> <p>Tiles will be competing against current tabview + collapsible, as well as tabber implementations in various pages clusters. The first implementation of Tile is in Help:Guides and it demonstrates how a navigation hub might look like. </p> <div style="float:left;width:80%"> <div style="position:relative;overflow:hidden;height:340px;margin:5px;background:rgba(250,250,255,0.1);;border:none"> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:300px;width:100%;"> <h3><span class="mw-headline" id="Clickbox">Clickbox</span></h3> <p>Remember that Template:ItemStack I introduced two years ago? When linking to a page using the built-in image link, there exists a blind spot over the text area as seen below </p><p><span style="position:relative;display:inline;"><span style="font-size:12px; font-weight:800; position:absolute; color:#f61; right:4px;bottom:-18px; text-shadow: #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px">x7</span></span> This issue has then been fixed using an invisible clickbox overlay, the same kind used in interactive maps: </p><p><span style="position:relative;display:inline;"><span style="font-size:12px; font-weight:800; position:absolute; color:#f61; right:4px;bottom:-18px; text-shadow: #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px, #fff 0px 0px 5px">x7</span><span style="position:absolute;top:-15px;left:1px;opacity:0"></span></span> </p> </div> <div style="position:absolute;z-index:3;height:16px;bottom:20px;right:10px;"> <p><span style="font-size:12px;">See more ></span> </p> </div> </div> <hr></div> <div style="float:left;width:100%"> <div style="position:relative;overflow:hidden;height:210px;margin:5px;background:rgba(250,250,255,0.1);;border:none"> <div style="position:absolute;z-index:2;overflow-y:hidden;overflow-x: hidden;height:160px;width:100%;"> <h3><span class="mw-headline" id="Animated_tiles">Animated tiles</span></h3> <p>Combining Tile, clickbox overlay and Oasis theme's default classes and it is possible to create a variety of responsive elements. One of which is as seen below </p> <div class="wds-button" style="position:relative;overflow:hidden;height:80px;padding:0px;float:left;width:18%;margin:5px;border:none"> <div style="position:absolute;top:-260px;left:-70px;;opacity:0.6;z-index:1;"></div> <div style="position:absolute;z-index:2;left:0px;bottom:0px;overflow:hidden;height:80px;"> <div style="color:white;padding:10px"><h3><span class="mw-headline" id="Na">Na</span></h3> </div></div> <div style="position:absolute;z-index:3;width:100%;80px;left:0px;top:0px;overflow:hidden;opacity:0"> <p> </p> </div> </div> <div class="wds-button" style="position:relative;overflow:hidden;height:80px;padding:0px;float:left;width:18%;margin:5px;border:none"> <div style="position:absolute;top:-270px;left:-40px;;opacity:0.6;z-index:1;"></div> <div style="position:absolute;z-index:2;left:0px;bottom:0px;overflow:hidden;height:80px;"> <div style="color:white;padding:10px"><h3><span class="mw-headline" id="No">No</span></h3> </div></div> <div style="position:absolute;z-index:3;width:100%;80px;left:0px;top:0px;overflow:hidden;opacity:0"> <p> </p> </div> </div> <div class="wds-button" style="position:relative;overflow:hidden;height:80px;padding:0px;float:left;width:18%;margin:5px;border:none"> <div style="position:absolute;top:-250px;left:-10px;;opacity:0.6;z-index:1;"></div> <div style="position:absolute;z-index:2;left:0px;bottom:0px;overflow:hidden;height:80px;"> <div style="color:white;padding:10px"><h3><span class="mw-headline" id="De">De</span></h3> </div></div> <div style="position:absolute;z-index:3;width:100%;80px;left:0px;top:0px;overflow:hidden;opacity:0"> <p> </p> </div> </div> <div class="wds-button" style="position:relative;overflow:hidden;height:80px;padding:0px;float:left;width:18%;margin:5px;border:none"> <div style="position:absolute;top:-260px;left:-10px;;opacity:0.6;z-index:1;"></div> <div style="position:absolute;z-index:2;left:0px;bottom:0px;overflow:hidden;height:80px;"> <div style="color:white;padding:10px"><h3><span class="mw-headline" id="Su">Su</span></h3> </div></div> <div style="position:absolute;z-index:3;width:100%;80px;left:0px;top:0px;overflow:hidden;opacity:0"> <p> </p> </div> </div> </div> <div style="position:absolute;z-index:3;height:16px;bottom:20px;right:10px;"> <p><span style="font-size:12px;">See more ></span> </p> </div> </div> <hr></div> <div style="clear:both;"></div> <h2><span class="mw-headline" id="Front_page_overhaul">Front page overhaul</span></h2> <p>All the above elements are designed to be used in the new front page design and future navigation hubs. As the front page is a high traffic area, it is necessary to make a site-wide announcement ahead of time. I myself am very interested in hearing feedback and suggestions from everyone on how to better organize and improve the design. </p> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:60px;border-top:none;border-left:6px solid #006cb0;overflow:hidden;display:block;margin:5px;float:left;"> <p>Click on this message to visit the sandbox page. </p> <div style="position:absolute;z-index:3;width:100%;60px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p> </p> </div> </div> <p>
Feedback I'm looking for in particular are: </p> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid lime;overflow:hidden;display:block;margin:5px;float:left;"> <p>I expected <item> to be at <location>. </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid lime;overflow:hidden;display:block;margin:5px;float:left;"> <p>I expected <action> to have <effect>. </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid lime;overflow:hidden;display:block;margin:5px;float:left;"> <p>I use <item> a lot. Please make it more accessible. </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid lime;overflow:hidden;display:block;margin:5px;float:left;"> <p>I think <item> should belong to <dropdown> or <section> </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid lime;overflow:hidden;display:block;margin:5px;float:left;"> <p>I think <item> should be on top/below/before/after <item> </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid lime;overflow:hidden;display:block;margin:5px;float:left;"> <p>I prefer <item> to be of <style> or in <color> </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid lime;overflow:hidden;display:block;margin:5px;float:left;"> <p>I find <item> to be working incorrectly in <browser> or <monitor size> </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div style="clear:both;"></div> <h3><span class="mw-headline" id="Known_issues">Known issues</span></h3> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid red;overflow:hidden;display:block;margin:5px;float:left;"> <p>Dropdown list should be displayed on hover, not click </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid red;overflow:hidden;display:block;margin:5px;float:left;"> <p>Color of animated tiles and buttons cannot be changed </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:70px;border-top:none;border-left:6px solid gray;overflow:hidden;display:block;margin:5px;float:left;"> <p><s>Broken mobile compatibility</s> </p> <dl><dd>Issue dropped. Wikia uses its own mobile front page which cannot be edited </dd></dl><div style="position:absolute;z-index:3;width:100%;70px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> <div class="wds-global-navigation__link" style="position:relative;width:100%;height:30px;border-top:none;border-left:6px solid red;overflow:hidden;display:block;margin:5px;float:left;"> <p>Monobook skin does not have comparable Oasis's button classes </p> <div style="position:absolute;z-index:3;width:100%;30px;left:0px;top:-20px;overflow:hidden;opacity:0"> <p></p><noscript></noscript> </div> </div> </style></item></item></item></section></dropdown></item></item></effect></action></location></item>

<p>I click play and no sound plays, it diffently is sending something, the specker bar/meter? is showing that something is playing, it just won't play on the speakers  </p>