Manual of Style

The Manual of Style outlines a standard of clean, consistent formatting for articles on the Florr.io Community Wiki - it is advised to read this before editing or creating a new page, and though these guidelines will never be unerringly perfect in all situations, please try your best to keep to the advice outlined in this article so others may use your edits as an example when creating and editing their own articles.

Articles

Article content

One of the most important parts of wiki editing is how to structure an article properly. The structure is a powerful concept: it dictates what information the reader reads, what order they read it in, and how the information is taken in. It can influence what people contribute, where it goes, and how it might be written. Structure has the power to inform or confuse the same way good or bad writing does. Keep a well structured article, and you're more likely to have a high quality one.

If in doubt, use the templates provided for petals, mobs, talents, and areas.

Organize sections in an article in a hierarchical structure like you would an outline. Keep Wherever possible, try to have an introduction for each section: just like the article as a whole, the section should start with an introduction and then have its subsections below it, so that people can understand the content using a basic overview.

A good example of this is from the Nazar Amulet article, which provides a basic introduction that is easy to follow.

Nazar Amulet is a petal in florr.io. Its function consists of reducing one instance of damage taken by the flower by 98%. Nazar Amulet is dropped by Nazar Beetle.

Rarity styling

Use the {{Rarity}} template to display a rarity. Common, Unusual, Rare, Epic, Legendary, Mythic, Ultra, Super, and Unique can be used as arguments, as well as their respective numbers (1 for Common, 5 for Legendary, 9 for Unique, etc.)

Galleries

This section is used to show images in <gallery> tags. Using this, you can show multiple pictures, and optionally supply captions:

<gallery>
File:RelevantImage.png
File:wheels.png|caption text
File:Basic.png|link=Basic
File:Assembler.png|caption [[Assembler|with a link to its subject]]|link=Assembler
File:florrFlower.png|alt=A flower
</gallery>

caption text

caption with a link to its subject

Below is a list of all parameters supported by default galleries:

Description	Format and options	Default
Max image widths, in pixels	widths=[number]	185
Images per row	columns=[number]	Fit to page
Gallery positioning	position=[left/center/right]	left
Spacing between images	spacing=[small/medium/large]	medium
Image orientation and cropping	orientation=[none/landscape/portrait/square]	none
Caption position	captionposition=[within/below]	below
Caption alignment	captionalign=[left/center/right]	left
Caption color	captiontextcolor=[color code]	Article text color
Caption size	captionsize=[small/medium/large]	medium
Border thickness	bordersize=[none/small/medium/large]	small
Border color	bordercolor=[color code]	Theme border color
Gallery caption	caption=[text]	No caption

Infoboxes

Infoboxes summarise data relating to the title and generally appear at the top-right corner of the article content. You can view them in the article templates. Infoboxes should generally summarise all available information (e.g. Attributes); speculation, as well as "unknown" or "N/A" rows, should be avoided.

Disambiguation

A disambiguation line is sometimes put at the beginning of an article to link to another article with the same or similar title. The line should always be italicised: should the text not be obstructed by an infobox, the line should also be indented using the : character.

This page is about the petal. For the mob which shares its in-game name, see Bubble (Mob).

This page is about normal Bubble. For the magic petal variant, see Magic Bubble.

Writing

We now come to the meat of an article: the words themselves. When you're editing the Florr.io Wiki, you have to be accurate, but you also have to be interesting. Neither one can dominate; you have to balance both.

Style

• Keep your writing concise. Don't use two words where one will do. Keeping your writing simple will make it easy to understand and easy to expand on. Use complete sentences whenever possible. When you write, use grammar as a toolbox: know the rules, but only break them on purpose.
• Check your spelling and grammar. Do not use 'u' in place of 'you' or '2' in place of 'to'. Write the way you would for a class paper or a newspaper article. This makes it easier for all readers to understand, not just the ones accustomed to the same conventions you are.
• Write from an impersonal perspective. Do not use first-person pronouns like "I" or "my" when not providing an author's note. For example, do not write, "You cannot switch to the Mecha Flower team in the Factory, to the extent of my knowledge." Avoid drawing attention to the author (yourself) as much as possible.

For pages about petals with shortened aliases (e.g. Nazar Amulet => Nazar, Cogwheel => Cog, etc.), it is recommended to use the {{DISPLAYTITLE}} template to shorten its name to what is shown in the petal box. This will change the title to the argument in the title display, though the URL will not be changed.

Grammar

Since an article must be as clear as possible for all readers, editors must maintain a high level of adherence with the rules of grammatical use, to ensure clear communication. Note that a sentence that seems grammatically incorrect could be shown as it was written in Florr.io: if absolutely necessary, use [sic] to denote that this is how the sentence was written.

This cannot be emphasized strongly enough. It is imperative that the Florr.io Wiki maintains clear, concise, gramatically correct information, in the interests of us being a trustworthy source.

Tenses

Most articles should be described as facts, so use the present or future tenses.

"Basic and Rose are the first petals obtained by the flower."

"PvP can be accessed by flowers outside of Hel using Corruption."

There may be exceptions, such as when describing changes to Florr.io that have taken place through updates.

"Heavy was originally split into two petals: Heavy and Heaviest."

Tables

Use the "wikitable" or "article-table" class whenever possible, like when outlining petal / mob stats and petal drop rates, unless the "fandom-table" class suits the content better (see Hall of Fame.)

The "sortable" class can be used for overview pages like Mobs and Petals for ease of sorting by alphabetical order: this is especially convenient when info is sorted by ID.

Description	Format	Usage
Begin table	{|	Denotes the start of a table.
Table caption	|+	Denotes a caption, which will show at the top of a table.
Begin new row	|-	Introduces a new row.
Begin new header	! !!	Begins a new header. The latter is to be used on the same line.
Begin new cell	| ||	Begins a new cell. The latter is to be used on the same line.
End table	|}	Denotes the end of a table.

To view table classes, click Expand.

Here are the default classes of Fandom:

• <no class> - These tables have no class, and arrange everything in a grid with no styling. Not recommended.
• wikitable - Default MediaWiki styling of tables. Adds a simple border to all rows/columns. On table headers, it fills the background with a grey color.
• article-table - A modern-like table design. Adds a border to seperate rows (this is known as a gutter), and colors all rows with a semi-transparent grey color. The header cells are colored grey, similar to wikitable: this is recommended for most articles regarding official game content, like petal stats, petal drops, and mob stats.
• fandom-table - Similar design with wikitable, but with bigger padding and a sticky header. Recommended for design.

NOTE: All table classes on mobile are set to article-table, regardless of what the original class was.

No class

{|
! Foo !! Bar
|-
| Baz || Quux
|}

Foo	Bar
Baz	Quux

wikitable class

{| class="wikitable"
! Foo !! Bar
|-
| Baz || Quux
|}

Foo	Bar
Baz	Quux

article-table class

{| class="article-table"
! Foo !! Bar
|-
| Baz || Quux
|}

Foo	Bar
Baz	Quux

fandom-table class

{| class="fandom-table"
! Foo !! Bar
|-
| Baz || Quux
|}

Foo	Bar
Baz	Quux

Rowspan and colspan

colspan and rowspan can be used as such:

Foo	Bar
Baz	Qux
	Quux	Foobar
Bazqux	Fooqux	Quxquux

Colspan makes the cell wider, while rowspan makes the cell wider, each taking up more columns and rows respectively.

Collapsibles

There are times when an article can contain many related elements which makes it very long, like a large table documenting large amounts of content in Florr.io; using a collapsing feature enables editors to shorten the page. This feature is recommended to be used on long tables of data and large navboxes.

To make an element collapsible, simply add the class "mw-collapsible" to it. This works with divisions and tables.

This text is collapsible!

To make a collapsible element collapsed by default, simply add the class "mw-collapsed" to it as well.

This text has already been collapsed!

The 'Expand' and 'Collapse' text can be changed using "data-expandtext" and "data-collapsetext".

Whami dies in Passport to Prodigia.

Trustworthiness

The Florr.io Community Wiki, above all, must be trustworthy. Before including information, ask yourself, Where did I hear this from? Make sure all statistics are directly taken from base Florr.io (you can press ALT to view unabbreviated stats), mark all speculation as such, and do not include false information. The Florr.io Wiki has had a reputation for spreading misinformation, which is the opposite of the purpose of this wiki. Thus, those who repeatedly include misinformation will be questioned and punished.

The Florr.io Community Wiki is a place for people to learn about Florr.io without fearing the risk of being misinformed and lied to. As such, we cannot tolerate any action that intentionally encourages said risks. Repeated infractions and vandalism will get you banned. Follow the Manual of Style and do not test us.