NEW /int/craft Wiki

We're so back.

User Tools

Site Tools

Trace:
article_guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
article_guidelines [2023/05/30 00:22] – intcraftwikiadminarticle_guidelines [2023/09/16 21:55] (current) – intcraftwikiadmin
Line 1: Line 1:
 ====== Article Guidelines ====== ====== Article Guidelines ======
  
-A lot of what I've written here so far is way too academic, hopefully that can change. I don't actually care what you write about or how formally you do it; do whatever you want. The only thing strictly off-limits is doxxing. That includes posting real names, IRL locations more precise than a country, and IRL pictures, as well as posting pictures of trains or something about a jester. The only exception is in regards to somebody like [[wolfdevon|Devon]] who has a well-attested identity, so... yeah, basically just Devon.+A lot of what I (the admin) have written here so far is way too academic, hopefully that can change. I don't actually care what you write about or how formally you do it; do whatever you want. The only thing strictly off-limits is doxxing. That includes posting real names, IRL locations more precise than a country, and IRL pictures, as well as posting pictures of trains or something about a jester. The only exception is in regards to somebody like [[wolfdevon|Devon]] who has a well-attested identity, so... yeah, basically just Devon.
  
 With that out of the way... With that out of the way...
Line 13: Line 13:
 So speaking of, here's the [[wiki:syntax|formatting syntax guide]]. So speaking of, here's the [[wiki:syntax|formatting syntax guide]].
  
-A couple things I want to point to specifically are the [[wiki:syntax#sectioning|headings]] and [[wiki:syntax#media_files|image links]]. For headings, I always start my articles with six ='s, for example, ''%%====== Page Title ======%%'', to write the article name with the biggest font size, and then, if the article is long enough to have subsections, go down to five ='s, then four, etc. So, you should follow that convention if you care about consistency. For image links, notice how spaces before or after the filename affects its location. Kinda quirky. [[wiki:syntax#tables|Tables]] work the same way. Also, you pretty much always need to use "?" to resize the image (as in, ''%%{{image.png?250}}%%'' for 250px wide), or it will take up the whole page. Also also, you can see the images currently on the site in the [[https://intcraft.wiki/article_guidelines?do=media&ns=|Media Manager]] (upper right), and you can upload new ones there, too.+A couple things I want to point to specifically are the [[wiki:syntax#sectioning|headings]] and [[wiki:syntax#media_files|image links]]. For headings, I always start my articles with six ='s, for example, ''%%====== Page Title ======%%'', to write the article name with the biggest font size, and then, if the article is long enough to have subsections, go down to five ='s, then four, etc. So, you should follow that convention if you care about consistency. For image links, notice how spaces before or after the filename affects its location. Kinda quirky. [[wiki:syntax#tables|Tables]] work the same way. Also, you pretty much always need to use "?" to resize the image (as in, ''%%{{image.png?280}}%%'' for 280px wide), or it will take up the whole page. Also also, you can see the images currently on the site in the [[https://intcraft.wiki/article_guidelines?do=media&ns=|Media Manager]] (upper right), and you can upload new ones there, too.
  
 I also have some extensions installed here to give us more features. This is some advanced shit. The most important of these is called [[https://www.dokuwiki.org/plugin:wrap|Wrap]], which basically allows us to split pages into multiple elements (such as two columns). It has some more autistic syntax (just linked it) but you shouldn't need to worry about it unless you're doing something crazy. I also have some extensions installed here to give us more features. This is some advanced shit. The most important of these is called [[https://www.dokuwiki.org/plugin:wrap|Wrap]], which basically allows us to split pages into multiple elements (such as two columns). It has some more autistic syntax (just linked it) but you shouldn't need to worry about it unless you're doing something crazy.
  
-We also have [[https://www.dokuwiki.org/plugin:imagebox|ImageBox]], which lets us have captioned Wikipedia-style images, by using extra ['s like this: ''%%[{{ImagePath|Caption}}]%%''. Very simple. See [[intcraft-chan|/int/craft-chan]] for an example. If you do this, use ?250 to keep a consistent 250px wide.+We also have [[https://www.dokuwiki.org/plugin:imagebox|ImageBox]], which lets us have captioned Wikipedia-style images, by using extra ['s like this: ''%%[{{image.png?280|Caption}}]%%''. Very simple. See [[intcraft-chan|/int/craft-chan]] for an example. If you do this, use ?280 to keep a consistent 280px wide.
  
-We also have [[https://www.dokuwiki.org/plugin:tablewidth|Table Width]] (you'll see why in a sec), [[https://www.dokuwiki.org/plugin:wrapadd|Wrap Plus]], and [[https://www.dokuwiki.org/plugin:pageredirect|Page Redirect]]. Be careful when using redirects, as once you create one, you can't undo it (only I can). By the way, I already created redirects for all the iteration articles (wow!) so you can create a link to [[i33]] or [[35.0]], and the links will resolve the correct place.+We also have [[https://www.dokuwiki.org/plugin:tablewidth|Table Width]] (you'll see why later), [[https://www.dokuwiki.org/plugin:wrapadd|Wrap Plus]], [[https://www.dokuwiki.org/plugin:pageredirect|Page Redirect]], and [[https://www.dokuwiki.org/plugin:toctweak|TocTweak]].
  
 Most of this is not really necessary to know. You should find that writing and page formatting is pretty straight-forward. But you were autistic enough to come to this website and click the link to this page anyway, so now you know all the extra shit. Most of this is not really necessary to know. You should find that writing and page formatting is pretty straight-forward. But you were autistic enough to come to this website and click the link to this page anyway, so now you know all the extra shit.
Line 34: Line 34:
 Notes on naming convention: I generally prefer to use mineman usernames rather than Discord tranny names for player pages, except in cases where for whatever reason the player is usually not referred to by any one username (like [[Jonathan]]). I also try to use a proper name for iteration articles when possible (but the redirects mentioned earlier also work). Using slashes in the article names kinda fucks things up, so avoid using them. For example, the homepage is just ''intcraft.wiki/intcraft'' rather than ''%%intcraft.wiki//int/craft%%''. Notes on naming convention: I generally prefer to use mineman usernames rather than Discord tranny names for player pages, except in cases where for whatever reason the player is usually not referred to by any one username (like [[Jonathan]]). I also try to use a proper name for iteration articles when possible (but the redirects mentioned earlier also work). Using slashes in the article names kinda fucks things up, so avoid using them. For example, the homepage is just ''intcraft.wiki/intcraft'' rather than ''%%intcraft.wiki//int/craft%%''.
  
-After you make an article, remember to link it on the homepage under the proper category (!!!).+==== Page redirects ==== 
 + 
 +Like Wikipedia, a redirect is a page which automatically sends visitors to another page, usually an article or section of an article. For example, [[Doneions]] redirects to [[Onions]]. 
 + 
 +To create a redirect, make a blank article with the text ''%%~~REDIRECT>:page~~%%'', with ''page'' being the page you want to redirect to. Be careful when doing this though, as once you create a redirect, you can't undo it (only I can). By the way, I already created redirects for all the iteration articles (wow!) so you can create a link to [[i34]] or [[34.0]], and the links will resolve the correct place. 
 + 
 +<WRAP center round tip 60%> 
 +If you make a new article, link it on the homepage in the proper place! We want to have EVERY page listed there, for ease of navigation. 
 +</WRAP>
  
 ===== Infoboxes ===== ===== Infoboxes =====
Line 56: Line 64:
 | **In-game name**  | TheSpookyBone, cupkaits  | | **In-game name**  | TheSpookyBone, cupkaits  |
 | **First iteration**  | 28  | | **First iteration**  | 28  |
-| **Metagroup**  | Various • SpookyBone's  |+| **Metagroup**  | Various\\ SpookyBone's  |
 | **Nationality**  | {{flag_us.png?24}} American  | | **Nationality**  | {{flag_us.png?24}} American  |
 | **Ethnicity**  | Mutt  | | **Ethnicity**  | Mutt  |
 | ** Years active**  | 2019--2022  | | ** Years active**  | 2019--2022  |
-| **Associated players**  | Crippo • [[Stryker]] • [[Falklands]]  |+| **Associated players**  | [[Crippo]]\\ [[Stryker]]\\ [[Falklands]]  |
 </WRAP> </WRAP> </WRAP> </WRAP>
  
Line 74: Line 82:
  
 |< 19.2em 40% >| |< 19.2em 40% >|
-| **In-game name**  | TheSpookyBone, cupkaits  |+| **In-game name**  | TheSpookyBone\\ cupkaits  |
 | **First iteration**  | 28  | | **First iteration**  | 28  |
-| **Metagroup**  | Various • SpookyBone's  |+| **Metagroup**  | Various\\ SpookyBone's  |
 | **Nationality**  | {{flag_us.png?24}} American  | | **Nationality**  | {{flag_us.png?24}} American  |
 | **Ethnicity**  | Mutt  | | **Ethnicity**  | Mutt  |
 | ** Years active**  | 2019--2022  | | ** Years active**  | 2019--2022  |
-| **Associated players**  | Crippo • [[Stryker]] • [[Falklands]]  |+| **Associated players**  | [[Crippo]]\\ [[Stryker]]\\ [[Falklands]]  |
 </WRAP> </WRAP> </WRAP> </WRAP>
 </code> </code>
Line 94: Line 102:
 The ''%%----%%'' creates a horizontal line (just for aesthetics). The ''%%----%%'' creates a horizontal line (just for aesthetics).
  
-Next we create another 19.2 width table. We need to do this because the line separates us from the previous table. This time, the ''40%'' specifies that the first line should be 40% of the width. I use 40% for player and iteration articles, but you can change this for your purposes. The rest should be pretty simple to figure out what it does. Only thing to note is that we have one space before the text and two spaces after, to align the text in the cell to the left. Also I'm using this> • copypasta ascii character for a separator (and in some other places, for bullet points).+Next we create another 19.2 width table. We need to do this because the line separates us from the previous table. This time, the ''40%'' specifies that the first line should be 40% of the width. I use 40% for player and iteration articles, but you can change this for your purposes. The rest should be pretty simple to figure out what it does. One thing to note is that we have one space before the text and two spaces after, to align the text in the cell to the left. Another is that we use ''%%\\ %%'' for a newline separator (everything in one row of a table must be written in one line).
  
 You can see that we have the US flag uploaded here as ''flag_us.png'', and a bunch of others are already in too. These follow the format of ''flag_'' and the two-character country code (like Discord flag emojis), except for some historical flags which are ''flag_'' and something longer. If you upload more flags, please use this format. I got the ones so far from Wikipedia. You can see that we have the US flag uploaded here as ''flag_us.png'', and a bunch of others are already in too. These follow the format of ''flag_'' and the two-character country code (like Discord flag emojis), except for some historical flags which are ''flag_'' and something longer. If you upload more flags, please use this format. I got the ones so far from Wikipedia.
Line 100: Line 108:
 When you make an infobox, put it below your ''%%====== Article title ======%%'' but above your text content. Also, since the right-side placement conflicts with the default Table of Contents location (and I can't be assed to change that), disable the Table of Contents by putting ''%%~~NOTOC~~%%'' at the beginning of every article that uses an infobox. Most shit won't be long enough to need having a Table of Contents anyway. When you make an infobox, put it below your ''%%====== Article title ======%%'' but above your text content. Also, since the right-side placement conflicts with the default Table of Contents location (and I can't be assed to change that), disable the Table of Contents by putting ''%%~~NOTOC~~%%'' at the beginning of every article that uses an infobox. Most shit won't be long enough to need having a Table of Contents anyway.
  
-**All this too autistic for you? Understandable.** The good thing is, you can just copy-paste a template and edit what you want. We have some further down the page. First, one more (more complicated) example, for a battle article: [[Battle of Paris]].+**All this too autistic for you? Understandable.** The good thing is, you can just copy-paste a template and edit what you want. We have some on the [[Infobox templates]] page (also on the sidebar). I will explain one more (more complicated) example, for a battle article: [[Battle of Paris]].
  
 ==== Example for a battle ==== ==== Example for a battle ====
Line 116: Line 124:
 | **Date**  | 30 January 2021  || | **Date**  | 30 January 2021  ||
 | **Location**  | Paris and surroundings  || | **Location**  | Paris and surroundings  ||
-| **Result**  | <WRAP> +| **Result**  | French victory\\ • Siege of France lifted\\ • Norse Brittany returned to French control\\ • Franco-German frontline pushed back to pre-war state  ||
-French victory\\ +
-• Siege of France lifted\\ +
-• Norse Brittany returned to French control\\ +
-• Franco-German frontline pushed back to pre-war state</WRAP>  ||+
 ^  Belligerents  ^^^ ^  Belligerents  ^^^
-| <WRAP> {{flag_fr.png?24}} France\\ +| {{flag_fr.png?24}} France\\ • {{flag_ch.png?18}} Switzerland\\ **Supported by:**\\ • {{flag_nl.png?24}} Netherlands\\ • {{flag_ru.png?24}} Russian Empire\\ • {{flag_bz.png?24}} Byzantine Sovereignty\\ • {{flag_pt.png?24}} Portugal  || {{flag_reich.png?24}} Deutsches Kaiserreich\\ {{flag_kalmar.png?24}} Kalmar Union\\ **Supported by:**\\ • {{flag_uk.png?24}} British Empire  |
-• {{flag_ch.png?18}} Switzerland\\ +
-**Supported by:**\\ +
-• {{flag_nl.png?24}} Netherlands\\ +
-• {{flag_ru.png?24}} Russian Empire\\ +
-• {{flag_bz.png?24}} Byzantine Sovereignty\\ +
-• {{flag_pt.png?24}} Portugal +
-</WRAP>  || <WRAP> {{flag_reich.png?24}} Deutsches Kaiserreich\\ +
-{{flag_kalmar.png?24}} Kalmar Union\\ +
-**Supported by:**\\ +
-• {{flag_uk.png?24}} British Empire +
-</WRAP>  |+
 ^  Commanders and leaders  ^^^ ^  Commanders and leaders  ^^^
-| {{flag_fr.png?24}} stryker123abc  || <WRAP> {{flag_reich.png?24}} LeiteArts10\\ +| {{flag_fr.png?24}} stryker123abc  || {{flag_reich.png?24}} LeiteArts10\\ {{flag_kalmar.png?24}} Lemon_Shot  |
-{{flag_kalmar.png?24}} Lemon_Shot </WRAP>  |+
 ^  Strength  ^^^ ^  Strength  ^^^
-| <WRAP> 30\\ +| 30\\ **(At peak)**  || 50\\ **(At peak)**  |
-**(At peak)**</WRAP>  || <WRAP> +
-50\\ +
-**(At peak)**</WRAP>  |+
 </WRAP></WRAP> </WRAP></WRAP>
  
Line 157: Line 146:
 | **Date**  | 30 January 2021  || | **Date**  | 30 January 2021  ||
 | **Location**  | Paris and surroundings  || | **Location**  | Paris and surroundings  ||
-| **Result**  | <WRAP> +| **Result**  | French victory\\ • Siege of France lifted\\ • Norse Brittany returned to French control\\ • Franco-German frontline pushed back to pre-war state  ||
-French victory\\ +
-• Siege of France lifted\\ +
-• Norse Brittany returned to French control\\ +
-• Franco-German frontline pushed back to pre-war state</WRAP>  ||+
 ^  Belligerents  ^^^ ^  Belligerents  ^^^
-| <WRAP> {{flag_fr.png?24}} France\\ +| {{flag_fr.png?24}} France\\ • {{flag_ch.png?18}} Switzerland\\ **Supported by:**\\ • {{flag_nl.png?24}} Netherlands\\ • {{flag_ru.png?24}} Russian Empire\\ • {{flag_bz.png?24}} Byzantine Sovereignty\\ • {{flag_pt.png?24}} Portugal  || {{flag_reich.png?24}} Deutsches Kaiserreich\\ {{flag_kalmar.png?24}} Kalmar Union\\ **Supported by:**\\ • {{flag_uk.png?24}} British Empire  |
-• {{flag_ch.png?18}} Switzerland\\ +
-**Supported by:**\\ +
-• {{flag_nl.png?24}} Netherlands\\ +
-• {{flag_ru.png?24}} Russian Empire\\ +
-• {{flag_bz.png?24}} Byzantine Sovereignty\\ +
-• {{flag_pt.png?24}} Portugal +
-</WRAP>  || <WRAP> {{flag_reich.png?24}} Deutsches Kaiserreich\\ +
-{{flag_kalmar.png?24}} Kalmar Union\\ +
-**Supported by:**\\ +
-• {{flag_uk.png?24}} British Empire +
-</WRAP>  |+
 ^  Commanders and leaders  ^^^ ^  Commanders and leaders  ^^^
-| {{flag_fr.png?24}} stryker123abc  || <WRAP> {{flag_reich.png?24}} LeiteArts10\\ +| {{flag_fr.png?24}} stryker123abc  || {{flag_reich.png?24}} LeiteArts10\\ {{flag_kalmar.png?24}} Lemon_Shot  |
-{{flag_kalmar.png?24}} Lemon_Shot </WRAP>  |+
 ^  Strength  ^^^ ^  Strength  ^^^
-| <WRAP> 30\\ +| 30\\ **(At peak)**  || 50\\ **(At peak)**  |
-**(At peak)**</WRAP>  || <WRAP> +
-50\\ +
-**(At peak)**</WRAP>  |+
 </WRAP></WRAP> </WRAP></WRAP>
 </code> </code>
  
-There's basically two major things that are different here.+There's basically one major thing that's different here:
  
 The first table with title and picture is the same, but this time we create the second table with three columns: first column width is ''5em'', '' - '' creates a second column with unspecified width, and ''50%'' sets the third column to 50% width. Why? Because we are using different column widths within the one table: we want the column with date, location, and result to be narrow, but in the later sections the table is split in half. We can achieve this by combining columns. In the first part, the left side is in column 1 and the right side is in columns 2+3 (every ''|'' is a column boundary, so we use ''||'' to use the width of two columns, like ''| A  | B  ||''). In the second part, the left side takes up columns 1+2 and the right side is the half-width column 3 (''| A  || B  |''). Note we never use column 2 on its own, it just exists to transfer its width for aesthetic reasons. Like I said, kinda hacky. The first table with title and picture is the same, but this time we create the second table with three columns: first column width is ''5em'', '' - '' creates a second column with unspecified width, and ''50%'' sets the third column to 50% width. Why? Because we are using different column widths within the one table: we want the column with date, location, and result to be narrow, but in the later sections the table is split in half. We can achieve this by combining columns. In the first part, the left side is in column 1 and the right side is in columns 2+3 (every ''|'' is a column boundary, so we use ''||'' to use the width of two columns, like ''| A  | B  ||''). In the second part, the left side takes up columns 1+2 and the right side is the half-width column 3 (''| A  || B  |''). Note we never use column 2 on its own, it just exists to transfer its width for aesthetic reasons. Like I said, kinda hacky.
  
-The second difference is that we have lists, across multiple lines, inside a single table cell. To do this, we have a ''%%<WRAP>%%'' element and within it use ''\\'' as a line separator. For example, this is one row of the table:+Why not have multiple tables, instead of the three-column shit? Aesthetic reasons, that's it. Any other way creates too much dead space. 
 + 
 +Hopefully all this explanation has helped you know how this works, so you can make your own infoboxes. It took me a while to figure out the best way to do it. 
 + 
 +References for the look of Wikipedia infoboxes: 
 + 
 +[[wp>Markus Persson|Notch]] [[wp>World War 2]] [[wp>Battle of Stalingrad]] [[wp>M1 Abrams]] 
 + 
 +Again, see [[Infobox templates]] for more stuff you can copy. 
 + 
 + 
 +==== Old Wikipedia-style Table of Contents ==== 
 + 
 +Infoboxes break the default upper-right corner Table of Contents location. To insert an in-body Table of Contents, simply put this after your opening paragraphs:
  
 <code> <code>
-| **Result**  | <WRAP> +~~NOTOC~~ 
-French victory\\ +{{INLINETOC 2-5 width18}}\\
-• Siege of France lifted\\ +
-• Norse Brittany returned to French control\\ +
-• Franco-German frontline pushed back to pre-war state</WRAP>  ||+
 </code> </code>
  
-The code can get hard to read. But this is what produces the best results. Why not have multiple tables, instead of the three-column shit, and why not just use multiple rows for lists? Aesthetic reasons, that's it. Any other way creates too much dead space. +Note: You don't need ''~''''~NOTOC~~'' if you already have it at the top of the page (all the templates start with it at the top).
- +
-Hopefully all this explanation has helped you know how this works, so you can make your own infoboxes. It took me a while to figure out the best way to do it.+
  
-References for the look of Wikipedia infoboxes: [[wp>Markus Persson|Notch]] [[wp>World War 2]] [[wp>Battle of Stalingrad]] [[wp>M1 Abrams]]+Note 2: This fucks up the Preview, but only the Preview. The published page will have only one TOC if you do it right.
  
-===== Infobox article templates to copy+paste ======+\\
  
-See [[Infobox templates]].+t. intcraftwikiadmin
article_guidelines.1685420538.txt.gz · Last modified: 2023/05/30 00:22 by intcraftwikiadmin
Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki