recursal/Fanatic-Fandom huggingface dataset:
Giri - 3

Neymiş, artık iki kişi sayıldığı için yatağın üçte ikisi ona ait olmalıymış. İyi ki ağırlıklarımıza göre yapmadı hesabı. Gerçi bunun dışında oldukça komik görünüyor. Her zaman merak etmişimdir, iğne batırsam sahiden patlar mı? Çocukken bu soruyu sorduğumda gerizekalıymışım gibi bakmışlardı bana ama ben de herhalde biliyorum öyle olmadığını. Balon değil ya bu...

Bugün büyük kazandım. Sanırım haddinden büyük. Ama ne yapayım, kartları düzgün karıştırsalardı. Zaten iki, üç deste kart ancak var. Ben de elbette ezberledim hangi kartın arkasında hangi zedelenme olduğunu. Biraz da şansla o kartlar gelirse, "Aç" diyorum ve oyun benim oluyor.

DiMaggio'ya bugün sonunda istediği şu salak rozeti verebileceğim. Kendisi kullanmayacak sanırım, eminim yine bir başka kadınla ilgili. O kadar istediğine göre sanırım karşılığında ben de daha fazla şey isteyebilirim. Geçen gün gözümün ucuyla depoda gördüğüm o "Fancy Lads" yazılı kutu epey ilgimi çekmişti. Sahiden bu adamın bunca şeyi nereden bulduğunu artık merak ediyorum.
Giri - 9

Bugün kantinde eskiden çok sık yaşadığım ama uzun süredir başıma gelmeyen bir şey oldu. Kavga. Artık kabul ettiler sanmıştım ama anlaşılan o ki, kabul etmemişler. Neymiş, üç kağıtçılık yapıyormuşum. Aslında bu sefer tamamen haklılar. Çarkçılardan birisi ile mi konuştular acaba yoksa şu DiMaggio'mu gidip onlara anlattı ne olduğunu?

Normalde büyümezdi bu iş ama sanırım bu defa kızdırdıklarım içerisinde çok fazla insan var. Onlar da bahse girmeselermiş. Ben kimseyi zorlamadım ki. Ne yani, bu yüzden hapse mi atacaklar beni? Gerçi kavgayı bahsi kaybedenler başlatsa da, bağıranların içerisinde hayatlarını tehlikeye attığımı söyleyenler bile vardı. Galiba açlığa dayanamayanlar kafalarında hayal kurmaya başlamış. Oyunda yüksek puan yaparak nasıl hayatlarını tehlikeye atabilirim ki?
Giri - 11

Vay canına. Ben çok daha uzun süre kalırım sanıyordum ama anlaşılan Margaret'in yeterince büyüdüğünü düşündüler ve sanırım bir çocuk daha yapmak için hapishane pek uygun değil.

25 yıl boyunca burada yaşayan birisi olarak, karanlık günler hakkındaki hikayelerin dışında yaşanan tek heyecan verici şey ben hapisteyken yaşandı. Vault kapılarını açtı. Bir grup dışarıya gönderildi. Nedenini kimse bilmiyorum ama sanırım çarkçıların kafasını meşgul eden şeyle bir ilgisi var.

Dışarıya gönderilen grup, kısa süre sonra geri gelmiş. Pek anlatmıyorlar ama zaten anlatacak çok kişi de yok. Pete bu yolculukta ölmüş. Anlaşılan anlatabilecek sadece DiMaggio kalmış ama o da pek konuşkan değil.

Pete için sanırım gereğinden fazla üzüldüm. Demek sevmişim bu adamı. Tabi bir de, onca işi yapan usta çarkçı oydu. Zaten sistemleri çöken bu yerde onun kaybı, oldukça zararlı olsa gerek.
Giri - 4

İzlediğimiz filmlerde bahsi geçen "aşk" kelimesini sonunda yaşadım sanırım. Yani, böyle olmalı en azından. Ne kadar da güzelmiş bu şeyler. İyi ki kutuyu göz ucuyla da olsa farketmişim. Ve iyi ki DiMaggio o rozeti çok istiyormuş. Baksana, adam kendisine saklamak istiyormuş. Abur cubur ama adam sahiden kendisine saklamak istiyormuş. Ve ben nedenini yedikten sonra anladım. Evet, aşk bu olmalı.
Vault 46 Yönetim Konseyi

Vault 46 için Overseer Gary Coffey II mutlak lider olsa da, genel gündelik işler ile uğraşan ve gene hayatın sürmesini sağlayan sıradan kararlar veren bir konsey bulunmaktadır. Vault sakinleri arasında resmi ismi yerine topluluğa Kocabaşlar ve üyelerine de Kocabaş denilmektedir.

Bu konsey düzenli olarak toplanmakta ve Vault içi durumu değerlendirmektir. Her toplantı sonrası kararlar Overseer'a sunulmaktadır ve onun onayından sonra uygulamaya girmektedir. Overseer toplantılara bazen uzaktan ses veya görüntü ile katılmaktadır ancak kişisel olarak toplantıda bulunduğu duyulmamış bir olaydır.

Konsey üyeleri bir seçim ile değil, yönettikleri departmanlarda gerçekleşen terfiler ile koltuklarına sahip olurlar. Bu üst seviye terfileri ve iş değişikliklerini onaylan ise Overseer'dır. Konseyin bir lideri olmasa da, geleneksel olarak Başçarkçı bu görevi üstlenir.

**Vault 46 Yönetim Konseyi Üyeleri**

* Başçarkçı Bobby Lester
* Su Rehabilitasyon Yöneticisi Ruby Ortiz
* Sağlık ve Bilimsel Çalışmalar Lideri Anne Peters
* Gıda Dağıtım Yetkilisi Colin Hester
* Ambar Amiri Serenity Colen
* Enerji Üretim ve Dağıtım Amiri Eugene Law
* İş Gücü Dağıtım Yöneticisi Ethan Simon
* Güvenli Lideri Christine Sawyer
その他非生物

## スイートアップル農園BB

http://www.nicovideo.jp/watch/sm23202466

漁業
--

http://www.nicovideo.jp/watch/sm24204643

## マイリトルアドバルーンBB

http://www.nicovideo.jp/watch/sm26269899

http://seiga.nicovideo.jp/seiga/im4903165

## ポニーのしっぽがいっぱい　素材集

http://www.nicovideo.jp/watch/sm27071584　一部抜粋

## トワイライトが出たり入ったり

http://www.nicovideo.jp/watch/sm26535711

Silver Spoon's Cooking Laboratory
http://www.nicovideo.jp/watch/sm26326191 上記と同素材

## お正月

http://www.nicovideo.jp/watch/sm27912632

箒

http://www.nicovideo.jp/watch/sm27847773
Giri-1

Babam sonunda izin verdi. Ne de olsa artık ben de bir baba adayıyım. Yaşasın kendi bilgisayarım. En iyisi sakladığım şu bir kutu cipsi tırtıklayayım biraz. Pek doyurucu değil belki ama tadını çıkarmadan yaşamanın neresi güzel ki? Babam hala büyümediğimi iddia etse de cips sevmek için illa çocuk mu olmak gerek? Viski de seviyorum, ona ne demeli? Gerçi çocukken de severdim bu mereti ama neyse..

Müstakbel karım aslında fena birisi değil. En azından Maggie'nin kocasına yaptığını yapmıyor. Gerçi, Maggie türünün sanıyorum ki tek örneği. Çok fazla film izliyor olsa gerek. Sahiden insanlar sadece çocuk yaptıkları birisine bu kadar bağımlı olmalı mı? Acaba eskiden böyle miydik? Neyse, iyi ki bu değişmiş.

Cips bitiyor. Güya tırtıklayacaktım. Gideyim de benimle bir kaç el daha oyun atacak birilerini bulayım. Eminim DiMaggio'ya vermelik bir kaç şey bulabilirim. Ah bir keşfetsem adamın bu kadar abur cuburu nereden bulduğunu...
ヴィラン

# トリクシー

## トリとグリ.GB

https://www.nicovideo.jp/watch/sm42450148

# クリサリス／チェンジリング

## コミック版チェンジリングBB集その1

http://www.nicovideo.jp/watch/sm24646383　一部抜粋

## コミック版チェンジリングBB集その2

http://www.nicovideo.jp/watch/sm24871376　一部抜粋

## もぐもぐクリサリス.RB

https://www.nicovideo.jp/watch/sm42226510

# シルバースプーン／ダイヤモンドティアラ

## SSDTGB

http://www.nicovideo.jp/watch/sm26172145

シルバースプーン

ダイヤモンドティアラ

Silver Spoon's Cooking Laboratory

http://www.nicovideo.jp/watch/sm26326191　上記と同素材

# キングソンブラ

## コミック版キングソンブラBB集その2

http://www.nicovideo.jp/watch/sm25821948　一部抜粋

# スターライトグリマー

## 歩く村長GB

http://www.nicovideo.jp/watch/sm25990215

http://www.nicovideo.jp/watch/sm27720655

## トリとグリ.GB

https://www.nicovideo.jp/watch/sm42450148
Giri - 14

Katılmış olduğum seyahat sırasında ele geçirme şansı bulduğum Radscorpion zehir bezlerini, laboratuvarda analiz etmeyi başardık. Daha önceden sadece bir takım tahminlere göre gelişi güzel hazırladığımız panzehirleri, bundan sonra daha kaliteli üretebilme şansımız olacak.

Belki bu yeni panzehir, öncekinin yarattığı inanılmaz kötü mide bulantısına neden olmaz. Gerçi, belki zehir buna neden oluyordu. Zehirlenip, tedavi edilmemiş kimseye bunu sorma şansımız olmadı. Nitekim ölüyorlar. Ölülerle konuşmak mümkün mü?

Belki.

Yeterince viski içerseniz.

Öyle değil mi, Mike? Çok uzun zaman olmuştu...
その他生物

# その他

## 着色手描きトワイダンスBB

http://www.nicovideo.jp/watch/sm27688007

上記の差分

# クリーチャー

## ラリなめくじ.xlsx

http://www.nicovideo.jp/watch/sm26060692

http://seiga.nicovideo.jp/seiga/im4836436

## 子供向けエイリアンBB

http://www.nicovideo.jp/watch/sm29512698

藻

http://www.nicovideo.jp/watch/sm27424009

## トリクシー　手書きお尻ふりふり素材　GB

http://www.nicovideo.jp/watch/sm28838442

ＢＢ
--

http://www.nicovideo.jp/watch/sm24341839

## アレのBB2

http://www.nicovideo.jp/watch/sm22872544

無題
--

http://www.nicovideo.jp/watch/sm28295398
Poison

Vault 46 'nın yakınlarında olduğu bilinen bir yerleşim yeridir. Poisonous Voices isimli bir radyo istasyonuna sahiptir.

Radyo yayınlarından anlaşıldığı kadarıyla Jamie Mckenzie isimli bir lider tarafından yönetilmektedir ve gene Poison isimli bir içecek üretmektedir. Temiz su ve elektrik vaat etmektedir. Ayrıca radyo kanalında Jasper  isimli muhafız başının, dinleyicilere şehrin etrafını saran tellere elektrik verildiğinden yaklaşmamaları gerektiği uyarısını yayınlamaktadır.

İçeceği dışında şehrin en önemli özelliği çok soğuk kış aylarında yer altından gelen sıcak buharlar ile nispeten konforlu bir hal almasıdır. Bu da şehrin nüfusunu özellikle kış aylarında çok yüksek seviyelere çıkarmaktadır.

Vault-46 ile Poison arasındaki anlaşma gerçekleştikten sonra içecek dışında ayrıca üretmeye başladığı uyuşturucu şehrin gelirleri açısından iyiye gitmesine sebep olmuştur. Anlaşma sonrası Mckenzie daha çok paralı asker ve silah stoğuna sahip bir noktadadır.
Vault Yakınlarındaki Anıt

Vault 46'dan birkaç kilometre uzakta bulunan ve eski iki aracın dik bir şekilde üst üste durmasıyla oluşturulmuş bir anıt veya kalıntıdır. Yukarıdaki aracın kapıları açıktır ve yere paralel durmaktadır. Uzaktan kenarları kısa bir "t"' yi andırmaktadır.

Benzer bir anıt da gene aynı vadi içerisinde bulunmaktadır. Bu yapıda gene eski arabalar ile yapılmıştır ve "T" harfini andırmaktadır.
Giri - 6

Çok sinirlendiler. Ama ne yazık ki ne yaptığımı anlayabilecek kişiler çarkçılar ve hiç birisi kafalarını kaldırmıyor yaptıkları işten şu sırada. Umursayacaklarını bile sanmıyorum. Sahi, ne üstünde çalışıyorlar ki bu kadar? Normalde her şeyin hemen duyulduğu bu yerde, bu bilgi saklı kalıyor. Sürekli gülümseyen Pearl bile şu sıralar sürekli dalgın. Neyse, şans yine yüzüme gülüyor.
Screen

The **screen** is the display part of the device you use. Whatever type of device or screen you use, portability should support a reasonable aspect ratio or orientation.

## Desktop Screen vs. Mobile Device Screen

The screen on a desktop varies greatly from the screen on a mobile device. In fact, that is the real reason that content portability exists today. Whether on a Mobile Device Screen or on a Desktop Screen, you are able to edit easily and efficiently due to different designs, different content sizes, etc.

## See also

* What does portable mean?
* Why should your content be portable?
Kule Sakinleri

Kule Sakinleri Rol Yapma ve Strateji Oyunları Derneği, İzmir'de kurulmuş bir topluluktur. FRP dışında minyatür ve kart strateji oyunları etkinlikleri de gerçekleşmektedir.

Facebook Grup Sayfası: https://www.facebook.com/groups/kulesakinleri/

Facebook Sayfası: https://www.facebook.com/kulesakinleri

Web Sayfası: http://www.kulesakinleri.org
Overseer Gary Coffey II

Vault 46'da overseer görevini yerine getiren yöneticidir. Bu görevi uzun süredir sürdürmektedir. Yaşının kestirilmesi çok zor ancak görüntü olarak atmışlarında görünen beyaz tenli bir erkekdir. Çok nadir görülmektedir. Oldukça büyük bir elektrikli sandalye kullanmaktadır.

Karanlık Günler dönemininde yaşayan ve o günleri bilen tek kişidir.
Curated Main Page tool

The **Curated Main Page tool** is a now removed set of settings for managing curated content that was replaced with the Mobile Main Page tool. For admins, it was accessed by an Edit Curated Content button[*Citation needed*] to the right of the Edit button on the main page via desktop browsers and an "Edit Main Page" link on the main page from the mobile skin.

## See also

* Curated Content
* ~~Help:Curated Main Page~~
* Help:Mobile Main Page
* Mobile Main Page
その他モブ（ポニー）

# ボンボン

## ガニ股GB

http://www.nicovideo.jp/watch/sm26287876　下記の修正版

MLP BB集 + 使用例
http://www.nicovideo.jp/watch/sm23205607　上記と同素材

# リリー・バレー

## リリー・バレーGB素材1

https://www.nicovideo.jp/watch/sm42822833

# ロータスブロッサム

## ロータスブロッサムGB

http://www.nicovideo.jp/watch/sm24247723

樹になったフラッターシャイBB

http://www.nicovideo.jp/watch/sm24782903 上記の改良版

# フォトフィニッシュ

## トワイライトが出たり入ったり

http://www.nicovideo.jp/watch/sm26535711

Silver Spoon's Cooking Laboratory
http://www.nicovideo.jp/watch/sm26326191　上記と同素材

# モードパイ

## 歩行するモードパイGB

https://www.nicovideo.jp/watch/sm42404080

## モードパイ「ヘイ」.GB

https://www.nicovideo.jp/watch/sm42414076

# その他

## ワイルドファイアBB

http://www.nicovideo.jp/watch/sm26887855

ワイルドファイア差分BB

http://www.nicovideo.jp/watch/sm26895561　上記の差分
Parser function

**Parser functions** are a very useful set of wikitext functions that operate similar to magic words and for the most part includes the previously separate string functions (since 2009). These functions are included in part as built-in MediaWiki engine functionality, but largely from the ParserFunctions extension. Parser functions primarily include logical functions like `{{#if:...}}`, `{{#ifeq:...}}`, and `{{#switch:...}}`, but also includes a few utility functions like `{{#time:...}}` and `{{#titleparts:...}}`.

## Step-by-step use

1. Identify the parser function that is appropriate for the task you are trying to do. There are a wide variety of parser functions, so be sure to do your research.
2. Identify the proper syntax for the parser function you wish to use.
In this step-by-step guide, we will be using the `{{#ifexpr:}}` (if expression) parser function, its syntax is: {{#ifexpr: *expression* | *value if true* | *value if false* }}
3. Fill in the syntax.
{{#ifexpr: 1 > 0 | yes | no }}
In the example above, we filled in the mathematical expression (1 > 0), set the function to say "yes" if 1 > 0 is mathematically correct and say "no" if 1 > 0 is mathematically incorrect.
4. Save the page and verify that the function seems to be returning the expected value. In our example, "yes" should be returned because 1 is indeed greater than 0.
{{#ifexpr: 1 > 0 | yes | no }} → **yes**.
Note what would have happened if we had tweaked the expression but kept the returned values the same. The equation proves false because 0 is not greater than 1 and "no" is returned.
{{#ifexpr: 1 < 0 | yes | no }} → **no**.

While the above example might seem different, because one should always know 1 > 0, the performance and power of the parser function is revealed when it is passed a parameter. Let's say you are designing an infobox for a wiki about a TV show. You want to include a character's age and determine if they are an adult or not.

If within the infobox you have `{{#ifexpr: {{{Age}}} >= 18 | This character is an adult. | This character is not an adult. }}`, the code would say "This character is an adult" if the given age of the character is at or above 18. If the given age was less than 18, the code would instead say "this character is not an adult."

## ParserFunctions Extension

The ParserFunctions extension is a popular MediaWiki extension that adds numerous useful parser functions on a wiki. This extension is enabled by default across all of Fandom and includes most of the functions found in the now deprecated extension StringFunctions.

## What can parser functions do?

ParserFunctions extension has functions for mathematical operations, if/else statements, and time functions. To view a complete list of these functions, go to extension's official help page.

## See also

* Help:Parser functions
* String function
* Help:Wikitext
* InfoboxBuilder
* Lua

## External links

**Note:** *This is a **generic*** section***stub**. Expand it by clicking  Edit to right of the section title.*
* Extension:ParserFunctions at MediaWiki.org
	+ Help:Extension:ParserFunctions
* Extension:StringFunctions (inlcudes help documentation) at MediaWiki.org
Giri - 10

Vay canına. Bunu hiç düşünmemiştim. Anlaşılan bahsi kazandıktan sonra elime geçen viskilerin hepsini o kadar hızlı içmemeliymişim. Yediğim cipslerin paketlerinden bir kaçını, atmam gereken yere değil, kullanılmayan kısımlardan birisine bırakmışım. Nasıl yapmışsam bunu.

Ben dahil hepimiz Radroach'lardan bıkmış durumdayız ve bu yaptığım tam da onların ilgisini çekecek bir şey. Gerçi bunu yaptığımı da hiç hatırlamıyorum ama neden olmasın ki? İlk defa içki yüzünden ne yaptığımı hatırlayamadığım bir zaman değil bu. Bir sınır belirlemem gerekiyordu ama sanırım artık çok geç. Zaten şans asıl bu anlarda yüzüme gülse şaşarım. Büyük ihtimalle hapsedecekler beni. Eh, ben yokken bozulmazsın umarım. Zira epey bir süre ortalarda olmayacağım gibi bir his var içimde.

Acaba oradayken cips bulma şansım olur mu?
フラッターシャイ

## ロケットランチャーをぶっ放すフラッターシャイ

http://www.nicovideo.jp/watch/sm20745076

ロケットランチャーを撃ちこむフラッターシャイ　縮小版【使用例付き】

http://www.nicovideo.jp/watch/sm20750835　上記の縮小版

## すごくうれしそうなフラタシャイGB

http://www.nicovideo.jp/watch/sm22980479　下記の補正板

うれしそうなフラタシャイGB 他

http://www.nicovideo.jp/watch/sm22970637　上記と同素材

## トランスフォームするフラタGB

http://www.nicovideo.jp/watch/sm27079295

http://www.nicovideo.jp/watch/sm27089694 上記の修正版

## しまっちゃうフラタBB

http://www.nicovideo.jp/watch/sm27611777

http://www.nicovideo.jp/watch/sm27715339
Themes/FandomWikis

## FandomWikis

The **FandomWikis** infobox theme was created to replace the turquoise-colored infoboxes present on Fandom's official wikis, such as the Dev wiki, the Portability Hub, and Community Central.

It employs the dark gray color schemes of the standard 2016 Fandom wiki design to present an infobox that fits more naturally on the page.
Infoboxes

**Infoboxes** are templates that usually appear on the right side of a desktop screen. They are similar to infographs or sidebars in magazine articles; designed to present a summary of the topic of the page. They give important points in an organized and quickly readable format. They are generally made using templates, to create consistency across a community.

## The Basics

* What are infoboxes?
* How to create infobox templates
* How to use an infobox in an article
* Case study: Building your first infobox

## Advanced Info

* What are the benefits of making your infoboxes portable?
* How to style your portable infoboxes
* Frequently asked questions
* Best practices

## Technical Information for Pros

* Classic, portable, Lua: Different types of infoboxes
* Tips and tricks to spruce up your infoboxes

## See also

* w:Help:Infoboxes
* Portable Infoboxes
Captions versus headers in portable infoboxes

The standard way of thinking about captions for infobox images is this:

```
<image source="image">
    <caption source="caption"/>
</image>

```

You stick a caption within image tags. Simple. Straightforward. And yet: *not* great if you come from a community with a penchant for writing longish captions. On mobile, captions get truncated. So if you really need to have the entirety of your captions visible, consider making your captions *headers*.

That is:

```
<image source="image"/>
<header>{{{caption|}}}</header>

```

Headers are always visible in Mercury and on the desktop **in their entirety**, and — contrary to what you might think — **they're not required to be within a group tag**.

But what, you might ask, happens to the other, "proper" headers? Well, that's a stylistic choice on your part. You can leave them inside <header> tags and give only the first header special styling. Since the "caption" is probably always going to be the first header in the box, some `nth-child(1)` styling will likely work for you.

Or if you don't like that, you could make all your "proper" headers things that reside in <navigation> tags.

Or if even *that* doesn’t appeal, you could consider whether you really *need* to have "proper" headers at all. Your infobox might be small enough that an image, a caption and a few points of data will work for you.

## See also

* Flex-centering and portable infoboxes
* Getting the buttons you want on collapsible groups
* Styling horizontal groups
* Styling lists within portable infoboxes
Turning off auto-hyphenation in portable infoboxes

By default, portable infoboxes will try to fit in as much text as possible on any given line, and then break words with a hyphen when it reaches the end of the line. If you're a part of a community that doesn’t like this method of line-breaking, it’s easy to turn off.

```
.portable-infobox .pi-navigation,
.portable-infobox .pi-header,
.portable-infobox .pi-caption,
.portable-infobox .pi-data-value,
.portable-infobox .pi-data-label {
     -webkit-hyphens:none;
     -moz-hyphens:none;
     -ms-hyphens:none;
     hyphens:none;
}

```

But even though you can turn it off, you might not find it makes that much difference to how many lines are used to accommodate your text. In fact, in some instances, turning off hyphenation *could* make your total line usage *increase*.

## See also

* Captions versus headers in portable infoboxes
* Flex-centering and portable infoboxes
* Getting the buttons you want on collapsible groups
* Styling horizontal groups
* Styling lists within portable infoboxes
Themes/GreenPlus/theme.css

/\*

```
\*/
.portable-infobox {
 font-family: Plantin MT Std;
 border: 2px ridge #117511;
 margin-right: 4px;
 box-shadow: 2px 3px 5px #595959;
}

.portable-infobox a, portable-infobox a:visited {
 color: #00799C
}

.pi-background {
 background: #99FF66; /\*For browsers that don't support gradients\*/
 background: linear-gradient(#99ff66, #44cc00);
}

.pi-title {
 background-color: #337800;
 text-align: center;
 color: #FFFFFF;
 border-bottom: 2px ridge #117511 !important;
}

.pi-image {
 border-bottom: 1px solid #117511;
}

.pi-caption {
 color: #11AA11;
}

.pi-header {
 background-color: #33CC33;
 border-bottom: 1px solid #117511 !important;
}

.pi-border-color {
 border-color: #006400;
}

.pi-tab-link.pi-item-spacing.current {
 background-color: #008000;
 color: #FFFFFF;
 border-color: #006400;
}

.pi-tab-link.pi-item-spacing {
 border-color: #006400;
}

.pi-image-collection-tab-content {
 background: none;
}
/\*

```
\*/
Flex-centering and portable infoboxes

Portable infoboxes use flexbox markup — something generally not present in older wikitext versions. If you’re going to be managing your community’s infobox styling, it’s a great idea to delve into flexbox code. Here’s a good starting place, though it’s by no means the only such resource on the web.

One of the most frequent requests we get having to do with flexbox has to do with ‘’vertical’’ centering. How, users ask, can you vertically center both the data label and the data value?

It’s actually pretty simple, but you have to remember to specify several vendor codes. Since you’ll likely want to make every infobox on your wiki behave this way, let’s take a look at how to do it globally:

```
.portable-infobox .pi-data-label,
.portable-infobox .pi-data-value {
	   padding: 0;
        display:-webkit-flex;
        display:flex;
}
.pi-data .pi-data-label,
.pi-data .pi-data-value {
        -ms-flex-preferred-size:auto;
        -webkit-flex-basis:auto;
           -moz-flex-basis:auto;
                flex-basis:auto;
        -webkit-align-items:center;
           -moz-align-items:center;
                align-items:center;
                width:50%;
}

```

Of course, you don’t have to do it exactly like this. You may find that you want to specify a flex-basis other than “auto”. You may not like a straight 50/50 split between the width of the data labels and values. But this gives you a starting point, wherein the positioning of the labels and values are in the vertical center of the cell, and all cells are equally wide.

## See also

* Captions versus headers in portable infoboxes
* Getting the buttons you want on collapsible groups
* Styling horizontal groups
* Styling lists within portable infoboxes
Radscorpion Mağaraları

Vault'un açıldığı vadide yakın sayılabilecek tek yükseltidir. Büyük

birkaç mağara vardır. İçeride çok sayısda Radscorpion olduğu
bilinmektedir.

Karanlık Yeniden - Zaman Çizgisi  T+27'de de mağara derinlerine gidip gördükleri tüm radscorpionları bir grup Wasteland Dweller haklamıştır. Bölgede hala çok sayıda radscorpion bulunsa da en büyük mağara geçici bir süre bu yaratıklardan temizlenmiştir.

T+71'de mağaralardan bir tanesi kalıcı olarak Vault'un dış üssü haline getirildi. Duygusal bir yaklaşımla "Ev" ismi verildi.
Table

How to create beautiful portable tables? Glad you asked!

## What is a table?

Just like regular tables around the web, a table on a wiki is a rectangular, HTML structure with columns and rows. Of course, there are many variations that can make them far more complicated (captions, headers, columns spanning cells, row spanning cells, etc.), but this is what they are at their base. In Fandom wikis, tables can be constructed with via a GUI-based editor (classic editor or visual editor) or source editor (also source editing mode in classic editor or source editing mode in visual editor) in HTML or wikitext.

## Guidelines

### Use tables only for displaying tabular information

Tables should not be used for positioning and design. Tables force a rigid layout on your page elements, when they need to be flexible to adapt to different screen sizes.

### Avoid in-line styles and custom classes

Instead, use the `article-table` class like so in this wikitext example:

```
{| class="article-table"
! Header
<!-- ... -->

```

### Classes allowed in tables

The classes listed below won't affect the community's portability:

* article-table
* WikiaTable
* wikitable
* sortable
* mw-collapsible
* mw-collapsed

### Avoid nested tables or tables within tables

These may cause wide tables that require a lot of unnecessary scrolling in some devices.

## Example

### Good table

This table is easy to read and has a reasonable amount of rows and columns.

 Arthas the Lich King

#### Bad table (too wide)

This table easily goes beyond the border of a standard A4 page, making it cumbersome to read on both the desktop and mobile devices.

## Alternatives for tables

To control the layout of an article in a portable manner you can use `div`s with CSS to achieve columns. There are three options:

* the `float` CSS property with percentage widths, which are good containers.

```
<div style="float:left; width:50%">
I'm the left one!
</div>
<div style="float:left; width:50%">
And I'm the right one!
</div>

```

* multi-column layout properties, mainly well-suited to large bodies of text.

```
<div style="column-count:2; column-rule:1px dotted #ccc;">
This text will appear in the first column. That might depend on the quantity of text used inside the container. The latter portion of the text will overflow into the second column. This does depend on the number of columns you have as well.
</div>

```

* flexbox properties, which also support horizontal and vertical alignment.

```
<div class="flex container">
    <div class="flex item">1</div>
    <div class="flex item">2</div>
</div>

```

```
.flex {
 display: flex;
}
.container {
 flex-direction: row;
}
.item {
 flex: 1 0 0;
}

```

## References

1. ↑ HTML Techniques for Web Content Accessibility Guidelines 1.0 . Retrieved from http://www.w3.org/TR/WCAG10-HTML-TECHS/#tables. Access date: 11-12-2015

## See also

* w:Help:Avoiding nested tables
* w:Help:Tables
Browser

**Browser** is usually short for web browser or perhaps HTML browser (but these days, lots of markup languages are supported like CSS, XHTML, some XML extensions, etc). For most people this means mainstream browsers like Chrome, Firefox, and Safari, but can include so many others like Edge, Konqueror, Opera, and Internet Explorer.

In terms of portability, the goal is to support the broadest range of browsers, assuming they support the standards correctly.

## Supported Browsers

 Safari | 7.1+

 Chrome for Mobile | Android 4.4, 5.0-5.1, 6.0
Themes/Green/theme.css

```
.pi-theme-Green {
 border: 5px solid green !important;
 background-color: darkred !important;
 color: white !important;}
.pi-theme-Green .pi-title {
 font-weight: bold !important;
 border-bottom: 5px solid green !important;
 font-size: 175% !important;}
.pi-theme-Green .pi-header {
 font-weight: bold !important;
 background: darkgreen !important;
 border-bottom: 5px solid black !important;
 font-size: 100% !important;
 padding-left: 25px !important;}
.pi-theme-Green a {
 color: greeb !important;}
.pi-theme-Green .pi-item:not(:last-child) {
 border-bottom: 5px solid black !important;}
.pi-theme-Green .pi-image img {
 border-bottom: 5px solid black !important;}
.pi-theme-Green .pi-caption {
 color: white !important;
 border-bottom: 0px solid black !important;
 font-style: normal !important;
.pi-theme-Green .pi-item:last-child {
 border-bottom: none !important;}
.pi-theme-Green .pi-group {
 border-bottom: none !important;
}

```
Desktop

**Desktop** usually refers non-portable, non-mobile devices and the technologies around enabling and using those devices, but includes such devices as laptop computers which generally run the same type of OS (Windows, Mac OS X, etc.) as desktop computers. Desktop computers allow software developers to make certain types of assumptions that can be more forgiving of the power and screen space allowed to use that software.

## See also

* Differences between desktop and mobile
* Orientation
Themes/LotRF/theme.css

/\*

```
\*/
.portable-infobox a {
 color:#337800;
}

.portable-infobox {
 background:#e7f4d2;
 color:#000;
 border-bottom: 20px solid #25883d;
 border-radius: 5px 5px 5px 5px;
}

.portable-infobox .pi-title {
 border-radius: 5px 5px 0 0;
 background-color: #25883d;
 background-image: -moz-linear-gradient(top,#30b04f 35%,#25883d 65%);
 background-image: -webkit-gradient(linear,0% 0%,0% 100%,color-stop(35%,#30b04f),color-stop(65%,#25883d));
 background-image: -o-linear-gradient(top,#30b04f 35%,#25883d 65%);
 background-image: -ms-linear-gradient(top,#30b04f 35%,#25883d 65%);
}

.portable-infobox .pi-header {
 background-image:none;
 background-color: #25883d;
 border-top: 1px solid #b9c3a8;
}

.portable-infobox .pi-header,
.portable-infobox .pi-title {
 color:#F5F5DC;
}

.portable-infobox .pi-secondary-background,
.portable-infobox .pi-header,
.portable-infobox .pi-title {
 background-color: #25883d;
}

.portable-infobox .pi-navigation {
 background-color: #e7f4d2;
}

.portable-infobox .pi-navigation {
 border: 1px solid #F5F5DC;
}

.portable-infobox .pi-data:not(:last-of-type) {
 border-bottom: 1px solid #F5F5DC;
}

.portable-infobox .pi-group,
.portable-infobox .pi-data:last-of-type + .pi-group,
.portable-infobox .pi-horizontal-group .pi-horizontal-group-item:not(:first-child) {
 border:none;
}
/\*

```
\*/
Converting infoboxes

The **infobox migration** makes converting infoboxes to the new **portable infoboxes** code easy!

## How to convert an infobox

### Review the new infobox template draft

It's a good idea to look at the original markup and familiarize yourself with **the help page**, both of which are linked in the edit page you just landed on. **Not all elements may carry over into the draft version**, particularly for more complex infoboxes, so make sure to check it over, and add to or modify it as needed.

## Background

Infoboxes are everywhere on Fandom. Pages that include at least one infobox comprise about 60% of traffic in each individual community. And that's for good reason! Infoboxes are popular both here and on Wikipedia because they're a simple, powerful way to summarize a wiki's content.

This graph helps illustrate just how mobile-oriented the future is. Not just for Fandom, but for the web as a whole. For example, take a look at the recent trends and future growth predictions for mobile traffic, it's staggering.

Infoboxes are special here because not only are they integral to Fandom, but their wikitext and styling simply don't translate well to devices that aren't a desktop or laptop. We've used "hacky" solutions for a long time, one engineer says a workaround was "does it have two columns? Then it's an infobox.", but the time has come for us to have a real, sustainable solution for infoboxes.

**Fandom traffic is changing, and infoboxes need to change with it.**

## Need help?

If you've already tried converting your infoboxes, but can't quite work it out, or if you don't know how to give your new infoboxes the look they deserve, you can request help from other community members!
Portability/Features

Several tools have been designed to aid in the creation and dissemination of information.

## Feature development stages

Fandom generally follows a minimum viable product approach to software development, so features can be loosely grouped under 4 main stages:

* Prototype (MVP) - feature is under active development and is generally only available to staff and/or select communities
* Limited beta - feature is being tested by few communities
* General Release - feature is enabled for all users
* Dormant - feature is either no longer actively developed or has been removed

## References

1. ↑ Life cycle of a feature at Fandom
2. ↑ The Future of Infoboxes on Fandom
3. ↑ Technical Update: August 24, 2015
4. ↑ Introducing Curated Main Pages
5. ↑ Template Types: A Smarter Categorization System
Themes/Plant

## Viva Piñata Plant

### Authors

Matthew CenanceAuthor inspected code from the Plants vs. Zombies Heroes Plants infobox theme

Theme inspired by the old non-portable theme of the infoboxes found on the Viva Piñata Wiki. The main (title and header) background color is `#80bf41`. The data value label background color is `#a7d37c` and the data value background color is `#F2EDE8`.

*You don't have to add attribution but adding it is a way of saying thank to the author.*
Themes/Boku-No-Hero-Academia/theme.css

```
.portable-infobox.pi-theme-myheroaca {
 border: 1px solid gold;
 padding: 2px;
 font-size: smaller;
}
.pi-theme-myheroaca a {
 color: #cc960e;
}
.pi-theme-myheroaca .pi-image-collection-tabs,
.pi-theme-myheroaca .pi-font,
.pi-theme-myheroaca .pi-secondary-font {
 font-size: 11px !important;
}
.pi-theme-myheroaca .pi-title,
.pi-theme-myheroaca .pi-header {
 text-align: center;
 color: #FFFFFF;
 background: #8B0000;
 font-weight: bold;
 border-color: transparent;
 padding: 4px;
}
.pi-theme-myheroaca .pi-title {
 font-size: 16px;
}
.pi-theme-myheroaca .pi-image, .pi-theme-myheroaca .pi-image-collection {
 margin-bottom: 1em;
}
.pi-theme-myheroaca, .pi-theme-myheroaca .pi-image-collection-tab-content {
 background: transparent;
}
.pi-theme-myheroaca .pi-image-collection-tabs .pi-tab-link {
 background: transparent;
 border-style: none;
 margin: 0;
 padding: 0
}
.pi-theme-myheroaca .pi-image-collection-tabs .pi-tab-link:not(:last-of-type):after {
 content: "•";
 font-weight: normal;
 width: 1em;
 padding-right: 3px
}
.pi-theme-myheroaca .pi-group,
.pi-theme-myheroaca .pi-group .pi-data:last-child {
 border: none;
}
.pi-theme-myheroaca .pi-data {
 padding: 4px;
}
.pi-theme-myheroaca .pi-group:nth-child(2) .pi-data:nth-child(3) .pi-data-value {
 font-style: italic;
}
.pi-theme-myheroaca .pi-border-color {
 border-color: #999;
}
.pi-theme-myheroaca .pi-navigation {
 text-align: center;
 font-weight: bold;
 background: #8B0000;
 padding: 4px;
}
.pi-theme-myheroaca .pi-navigation a {
 color: #FFFFFF;
 text-align: center;
}

```
Themes/Plant/theme.css

/\*

```
\*/
/\* Theme for Plant infoboxes \*/
.pi-theme-plant .pi-title { /\* Header/Title Color \*/
 background-color: #80bf41; /\* Primary Background Color \*/
 color: #ffffff; /\* Text Color of white \*/
}
.pi-theme-plant .pi-secondary-background { /\* Header/Title Color \*/
 background-color: #80bf41; /\* Primary Background Color \*/
 color: #ffffff; /\* Text Color of white \*/
}
.pi-theme-plant .pi-data { /\* Data Padding Removal \*/
 background-color: #F2EDE8; /\* Tertiary Background Color \*/
 padding: 0px 0px;
 vertical-align: middle; /\* Align the text vertically centered \*/
}
.pi-theme-plant .pi-data .pi-data-label { /\* Data Label Color \*/
 background-color: #a7d37c; /\* Secondary Background Color \*/
 padding: 0px 0px;
 border: 10px solid #a7d37c; /\* Add the border of the same color as the secondary background color \*/
}
.pi-theme-plant .pi-data .pi-data-value { /\* Data Value Color \*/
 background: #F2EDE8; /\* Tertiary Background Color \*/
 padding: 0px 0px;
 border: 10px solid #F2EDE8; /\* Add the border of the same color as the tertiary background color \*/
}
.pi-theme-plant .pi-image { /\* Image Color \*/
 background: #F2EDE8; /\* Tertiary Background Color \*/
}
.pi-theme-plant .pi-data, .pi-theme-plant .pi-group {
 border-bottom-width: 0;
}
/\*

```
\*/
Themes/PvZH Zombies/theme.css

/\*

```
 \*/
body.page-Themes\_PvZH\_Zombies{
 background: #fde url("https://prod-media-pvzheroes.pulse.ea.com/content/pvzheroes/en\_US/news/september-game-updates/\_jcr\_content/sixteenNine.img.jpg");
}
.portable-infobox {
 width: 255px !important;
 background: #fff;
 border: 2px solid #fff !important;
}
.portable-infobox .pi-title {
 font-size: 15px;
 background-color: #373854;
 margin: 4px 2px !important;
 font-weight: 900 !important;
 text-align: center;
 color: #fff;
}
.pi-image {
 border: #373854 solid 1px;
 margin: 2px;
 line-height: 130%;
}
img.pi-image-thumbnail {
 max-width: 100%;
}
.portable-infobox .pi-secondary-background{
 background-color: #493267;
}
.portable-infobox .pi-header {
 padding: 2px 0;
 margin: 0 2px 2px 2px;
 font-weight: bold;
 text-align: center;
 background-color: #9E379F;
 color: #fff;
}
.portable-infobox .pi-item-spacing {
 padding: 0 2px;
}
.pi-border-color {
 border-color: transparent;
}
.pi-data .pi-data-label {
 font-weight: bold;
 text-align: right;
 -ms-flex-preferred-size: auto;
 -webkit-flex-basis: auto;
 -moz-flex-basis: auto;
 /\*flex-basis: auto;
 display: -webkit-flex;
 display: flex;
 -webkit-align-items: center;
 align-items: center;
 -webkit-justify-content: center;
 justify-content: center;\*/
 line-height: 140%;
 background-color: #21ca27;
 color: #fff;
 width: 40%;
 padding-right: 10px !important;
}
.pi-data .pi-data-value {
 text-align: left;
 -ms-flex-preferred-size: auto;
 -webkit-flex-basis: auto;
 -moz-flex-basis: auto;
 flex-basis: auto;
 line-height: 140%;
 background: #fff;
 width: 60%;
}
.pi-data-value: last-child {
 -ms-flex-preferred-size: auto;
 -webkit-flex-basis: auto;
 -moz-flex-basis: auto;
 flex-basis: auto;
 width: 100% !important;
 text-align: left;
}
div.pi-data-value.pi-font img {
 display: inline !important;
}
.portable-infobox .pi-data-label div {
background-color: #21CA27 !important;
color: White !important;
}

```
Parameter

**Parameters** are bits of data you send to command-line apps, functions (if it were a programming language), or in the case of wikis, templates. Since the first case doesn't really apply to Fandom wikis, we'll talk mostly about templates, but a little about functions (since Fandom wikis use Lua, the programming language).

If you use templates in the form of `{{mytemplate|...}}` you have probably seen parameters as the parts that show up after the template name. So an parameters would be like this: `{{mytemplate|paramvalue1|namedparam1=somevalue}}` There are lots of variations for how you can use parameters in templates, but so much depends on how the template decides to use them and which types of parameters, the wide variety is unfortunately out of the scope of this article.

Lua also uses parameters, but in a different way. Most Lua modules (they live in pages starting with Module:) take parameters passed to them by templates via something you might see called `{{#invoke:...}}`. Lua also uses parameters when declaring and calling functions, but it looks more like this `function myFunction( param0, param1 )` when declaring a function or this `myFunction( passparam0, passparam1 )` when calling a function. As with templates, the workings of parameters in Lua is out of the scope of this article.

## See also

* w:Help:Lua
* w:Help:Templates
Themes/Mercury

## Mercury

The **Mercury** theme was created to imitate the standard design of the Mercury skin's portable infoboxes. Two stylesheets exist that may be used depending upon whether or not the image element comes before or after the title element in the infobox code.

Please note that this particular theme is still a work in progress, and the author may undertake additional changes in the future.
Themes/LotR/theme.css

/\*

```
\*/

.portable-infobox a {
 color:#2b54b5;
}

.portable-infobox {
 background:#fff;
 color:#000;
 border-bottom: 20px solid #266438 ;
 border-radius: 8px 8px 8px 8px;
}

.portable-infobox .pi-title {
 background-color: #266438;
 background-image: -moz-linear-gradient(top,#34894d 35%,#266438 65%);
 background-image: -webkit-gradient(linear,0% 0%,0% 100%,color-stop(35%,#34894d),color-stop(65%,#266438));
 background-image: -o-linear-gradient(top,#34894d 35%,#266438 65%);
 background-image: -ms-linear-gradient(top,#34894d 35%,#266438 65%);
 border-radius:8px 8px 0 0;
}

.portable-infobox .pi-header {
 background-image:none;
 background-color: #266438;
}

.pi-collapse .pi-header::after {
 border-color: #F5F5DC;
}

.portable-infobox .pi-header,
.portable-infobox .pi-title {
 color:#F5F5DC;
 text-align:center;
}

.portable-infobox .pi-secondary-background,
.portable-infobox .pi-header,
.portable-infobox .pi-title {
 background-color: #266438;
}

.portable-infobox .pi-navigation {
 background-color: #fff;
}

.portable-infobox .pi-navigation,
.portable-infobox .pi-data {
 border-bottom: 1px solid #ccc;
 border-left: 1px solid #ccc;
 border-right: 1px solid #ccc;
}

.portable-infobox .pi-data-label {
 padding-right:15px
}
.portable-infobox .pi-group,
.portable-infobox .pi-data:last-of-type + .pi-group,
.portable-infobox .pi-horizontal-group .pi-horizontal-group-item:not(:first-child) {
 border:none;
}

.portable-infobox .pi-image,
.portable-infobox .pi-horizontal-group {
 border-right:1px solid #ccc;
 border-left:1px solid #ccc;
}

/\*

```
\*/
Themes/Sun and Moon/theme.css

/\*

```
 \*/
@import 'https://fonts.googleapis.com/css?family=Open+Sans';

.portable-infobox {
 background: transparent;
 font-family: 'Open Sans', sans-serif;
 width: 280px;
}

.pi-image,
.portable-infobox .pi-data:nth-child(even) {
 background-color: rgba(255, 255, 255, .2);
}

.portable-infobox .pi-data:nth-child(odd) {
 background-color: rgba(255, 255, 255, .3);
}

.pi-border-color,
.pi-collapse .pi-header::after {
 border-color: rgba(255, 255, 255, 0.75);
}

.portable-infobox .pi-item-spacing {
 padding: 0;
}

.pi-data {
 line-height: 35px;
}

.pi-data-label {
 text-transform: uppercase;
 padding: 7px 22px 7px;
 font-size: 0.7rem;
 border-right: 1px solid rgba(255, 255, 255, 0.75);
 text-align: right;
}

.pi-data-value {
 padding: 7px 0 7px 22px;
 font-size: 0.8rem;
}

.pi-header,
.pi-title,
.pi-navigation,
.pi-horizontal-group {
 text-align: center;
 padding: 8px 0 !important;
 background-color: rgba(255, 255, 255, .4);
 border-bottom: 1px solid rgba(255, 255, 255, 0.75) !important;
}
/\*

```
 \*/
Styling lists within portable infoboxes

Wikitext makes it pretty easy to style lists. But styling them *within portable infoboxes* might be less familiar to you.

## Styling bulleted lists

Generating bulleted lists is a breeze in wikitext. You know the drill:

```
*Vulcans
** Spock
*** T'Pring
** Tuvok
*** T'Pel
** T'Pol
*** Kos

```

But how do you style that within a portable infobox?  Well you could just accept the default. But the chances are that by the time you got to the spouses of the more famous Vulcans in this list — especially if this were in a horizontal list — you'd get some funky indentation.

So consider some general styling for unordered lists, like this:

```
.portable-infobox .pi-data-value ul {
   text-indent:-1em;
   padding-left:1.5em;
   padding-top:.25em
}

```

If you're trying to better place an unordered list within a horizontal group, you may find that you'll need to add something like this, just to keep things even more tightly controlled:

```
.pi-horizontal-group .pi-horizontal-group-item {
   text-align:left!important;
   padding:2px 5px 5px 5px!important
}

```

Obviously, those aren't the only values that'll work, but they're a good place to start.

### Styling lists created with wikitext colons

Some communities don't create traditional unordered lists. Sometimes, lists are created through colons, like this:

```
Vulcans
:Spock<br/>Tuvok<br/>T'Pol

```

In ordinary wikitext, this would generate some horizontal separation between **Vulcans** and the **list** of Vulcans. But in PI code, you've got to **specify** that space — and you've got to !important it. Let's say, just for fun, that you only wanted it to apply to a theme called "species".  You'd have to do this:

```
.pi-theme-species dl {
   margin:1em 0!important;
}

```

Oh, and dig this: while you can change the margins, the values above are what naturally occur in default wikitext.

## See also

* Captions versus headers in portable infoboxes
* Flex-centering and portable infoboxes
* Getting the buttons you want on collapsible groups
* Styling horizontal groups
* Turning off auto-hyphenation in portable infoboxes
Infobox/Types

There are multiple ways to design even the simplest infobox. They can be designed using Lua, JavaScript, Portable Infoboxes, Tables, Wikitext, and HTML tags or a mixture of all of the above.

## Comparison matrix

CSS
* Inline styling
* Hard to write
* Nothing built-in
* Not portable
* Inefficient
 Lua | Lua
* Infinite parameters
* Inline styling
* Must learn programming
 Portable | XML | Low
* Insert dialog (VE)
* Infobox Builder
* Europa theme
* Easy to write
* Built-in features
* Portable
* Internal API
* Visually design
* No inline styling
Themes/Boku-No-Hero-Academia

## Toshinori Yagi

* Hero Form
* True Form

**Toshinori Yagi**, more commonly known as **All Might**, is a supporting character of *My Hero Academia*.

This infobox theme is based on the character infobox of the Boku No Hero Academia Wiki.

The input and images are sourced from the All Might article of the wiki, which has further information on the character.
Themes/GOTF

## GOTF

The **GOTF** infobox theme is designed to improve the infobox design present on the *Game of Thrones* Fanon wiki by providing a number of mobile-friendly infobox designs and an updated color scheme created to match that of the wiki.

The finished design was implemented on the wiki in question with approval from the resident bureaucrat.(ref)
Themes/Alpha/theme.css

/\*

```
\*/
.pi-theme-alpha {
 background-color: #faebff;
 font-size: 12px;
 border-color: #800080;
 }

.pi-theme-alpha .pi-font {
 color: black;
 font-size: 100%;

.pi-theme-alpha .pi-image {
 border: 2px groove #800080;

 }

.pi-theme-alpha .pi-header {
 font-size: 140%;
 color: #ffffff;
 background-color: #800080;

 }

.pi-theme-alpha .pi-title {
 font-size: 180%;
 text-align: center;
 color: white;
 background-color: #800080;

 }

/\*

```
\*//\*Category:Stylesheets/\*/\*\*/
Themes/Squares/theme.css

/\*

```
 \*/
/\* Infobox Squares (made by 2Actimv) \*/
@import url(https://fonts.googleapis.com/css?family=Kanit);

.pi-theme-Squares {
 background: transparent !important;
 font-family: 'Kanit', Arial, sans-serif !important;
 font-weight: 300 !important;
 color: black !important;
}

.pi-theme-Squares a {
 color: maroon !important;
}

.pi-theme-Squares .pi-header {
 padding-left: 20px !important;
}

.pi-theme-Squares .pi-title {
 font-weight: bold !important;
}

.pi-theme-Squares .pi-background {
 background: transparent !important;
}

.pi-theme-Squares .pi-font {
 font-family: 'Kanit', Arial, sans-serif !important;
 font-weight: 300 !important;
 color: black !important;
}

.pi-theme-Squares .pi-item-spacing {
 padding: 5px 10px;
}

.pi-theme-Squares .pi-border-color {
 border-color: transparent !important;
}

.pi-theme-Squares .pi-item {
 margin-top: 0px !important;
 margin-bottom: 0px !important;
 background: linear-gradient(red, yellow) !important;
}

.pi-theme-Squares .pi-horizontal-group .pi-header {
 background: linear-gradient(red, yellow) !important;
}

.pi-theme-Squares .pi-item .pi-image {
 background: transparent !important;
}

.pi-theme-Squares .pi-caption {
 background: linear-gradient(red, yellow) !important;
 color: black !important;
 font-style: normal !important;
}

.pi-theme-Squares .pi-horizontal-group-item {
 background: linear-gradient(red, yellow) !important;
}

.pi-theme-Squares .pi-group {
 margin: 0px !important;
}
/\*

```
 \*//\*Category:Stylesheets/\*/\*\*/
Themes

There are multiple ways to change the appearance, or theme, of an infobox, but the complexity of the task depends mainly on the type of infobox being used.

## Portable infoboxes

Portable infoboxes can be both the easiest to theme and, conceivably, the hardest to theme. This is because they have a default theme based on the colors chosen in the theme designer. While these can be changed or improved using MediaWiki:Common.css, the only users allowed to change it are admins/bureaucrats.

### Theme gallery

Steven Universe exampleMy Singing Monster example
## Classic infoboxes

The appearance of classic infoboxes can be changed by any user by relying on inline styling, although some more complex changes can only be achieved by admins.

## See also

* Infoboxes
* Skin
* Portable Infoboxes/Themes