Wikipedia

User:Utl jung/sandbox/LD40807

< User:Utl jung | sandbox

Going in

edit

This session will cover:

  • What you need to know about Wiki markup (or Wikitext) to edit comfortably enough in most situations
    • Topics are broken out by task (e.g. formatting, linking, communicating with other editors) and include exercises
    • We will cover templates in greater depth during August's second Wikidata Working Hours session (Monday 17th).
  • Tips and tricks for making Wiki markup editing work for you

This session will be useful if:

  • You have mostly edited Wikipedia (or some other Wikimedia project) with the Visual Editor, and have limited experience with the text (source) editor
  • You find the source view of Wikimedia projects confusing or complicated
  • You are somewhat familiar with the content, but wish to revisit it or just want some practice
  • You're a Wiki markup master but you've stepped away for six years and would like a refresher

You will need:

Basics

edit

Wiki markup (or Wikitext) is one of many lightweight markup languages (LML) that prioritise human readability.

  • Wiki markup works across all MediaWiki-based platforms, including all Wikimedia projects and other wikis built on MediaWiki
  • Technically, Wikitext refers to text snippets or documents written in the Wiki markup language. But many use the terms interchangeably.
  • Other LMLs include Markdown and GitHub Flavored Markdown.
  • By comparison, HTML allows you to do more things but compromises on human readability.

Here is a table demonstrating how Wiki Markup compares to HTML (from Wiki#Basic syntax):

MediaWiki syntax (the "behind the scenes" code used to add formatting to text) Equivalent HTML (another type of "behind the scenes" code used to add formatting to text) Rendered output (seen onscreen by a regular web user) 
"Take some more [[tea]]," the March Hare said to Alice, very earnestly.

"I've had '''nothing''' yet," Alice replied in an offended tone, "so I can't take more."

"You mean you can't take ''less''," said the Hatter. "It's very easy to take ''more'' than nothing."

<p>"Take some more <a href="/wiki/Tea" title="Tea">tea</a>," the March Hare said to Alice, very earnestly.</p>

<p>"I've had <b>nothing</b> yet," Alice replied in an offended tone, "so I can't take more."</p>

<p>"You mean you can't take <i>less</i>," said the Hatter. "It's very easy to take <i>more</i> than nothing."</p>
"Take some more tea," the March Hare said to Alice, very earnestly.

"I've had nothing yet," Alice replied in an offended tone, "so I can't take more."

"You mean you can't take less," said the Hatter. "It's very easy to take more than nothing."

As we begin, you may find it helpful to turn on syntax highlighting!

  • This feature colours your syntax to make it easier (and more fun!) to use Wikitext.
  • To enable it, toggle the button ( ) that appears in the toolbar.
  • If you're curious about how this works, see: Extension:CodeMirror.

Formatting

edit

Characters

edit
  • Bold: Use three apostrophes(') on either side. '''foo'''
  • Italics: Use two apostrophes(') on either side. ''foo''
  • Bold + Italics: Use five apostrophes(') on either side. '''''foo'''''
  • Strikethrough: Use the template {{strikethrough}}. {{strikethrough|foo}}
  • Underline: Use the template {{underline}}. {{underline|foo}}
  • small caps: Use the template {{smallcaps}}. {{smallcaps|foo}}
edit

To format a link, add the apostrophes around the parentheses: '''[[foo]]''' If you do it the other way around, it will not work since the parentheses interpret the apostrophes as part of the page name.

Line breaks

edit
  • If you press ⌅ Enter once, it will place a line break in the markup but not in the rendered result.
  • If you press ⌅ Enter twice, it will insert a line break in the rendered result.
  • Lists are an exception. These require one, not two, markup line breaks.
  • To insert a line break without pressing ⌅ Enter twice, type <br>, <br/>, or {{pb}}. But, use sparingly.

Make lists

edit

Bullet lists

edit 
* a
* b
** c

produces:

  • a
  • b
    • c

Numbered lists

edit 
# a
# b
## c

produces:

  1. a
  2. b
    1. c
edit

Internal pages

edit
  • Use [[foo]] to link to an article
  • Use a pipe (|) to insert a parameter which changes what the link says. For example:

Images

edit

Link images in the same way that you would link any other internal page. For example, [[File:Abacus 6.png]] gives:

 

Extended syntax for an image looks something like this: 

[[File:Name|Type|Border|Location|Alignment|Size|link=Link|alt=Alt|page=Page|lang=Langtag|Caption]]

Here, only File is technically necessary. Most images only require: 

[[File:Name|thumb|alt=Alt|Caption]]

Here, thumb stands in for the size parameter.

Alt text
edit

Please: always insert alt text! Alt text describes visual content for users of screen readers and other visual-to-auditory assistive technologies. Rule of thumb: write out alt text as if you're describing the image to someone in another room.

Other language Wikipedias

edit
  • Look up the two-letter language code per ISO 639-1.
    • This is the same two-letter code at the beginning of the URL which takes you to that specific language Wikipedia.
    • For example, en.wikipedia.org with the ISO 639-1 code en (English) takes you to the English Wikipedia.
  • Use : two-letter language code : article name to link directly to the other-language Wikipedia page
    • For example, [[:fa:زرتشت]] gives fa:زرتشت. This is the Farsi page for Zarathustra
    • You can use what's called the "pipe trick" (add a pipe symbol(|) to the end of the article name) to have the output only display the article name
    • Or, as you did in previous sections, use a pipe (|) to insert a parameter which changes what the link says

Pages that exist in other languages but not in English

edit

Other Wikimedia projects

edit

Wikidata and Reasonator

edit
edit
  • Use [foo] to add an external, non-Wikimedia link
    • Technically, any link (even internal links) can be made this way, but the internal link rules (using [[foo]]) make those look much cleaner
  • Use a space ( ) to label the link. For example:

Communication

edit

Sign

edit
  • Signing is an etiquette on anonymous platforms! Use tildes(~) to sign off on comments, add yourself to Wikiprojects, etc.
    • ~~~: Three tildes(~) produce your signature Utl jung (talk)
    • ~~~~: Four tildes(~) produce your signature + timestamp Utl jung (talk) 17:13, 7 August 2020 (UTC)
      • Use this one on talk pages
    • ~~~~~: Five tildes(~) produce a timestamp 17:13, 7 August 2020 (UTC)

Ping

edit
  • You can notify ("ping") a user by making an edit that links to their user page.
    • Typing @Username will not automatically ping the user.
  • There are many ways to do this. To use myself (User:Utl_jung) as an example, you can write:
    • {{u|Utl_jung}} gives Utl_jung and notifies the user (this option does not append an "@")
    • {{ping|Utl_jung}} gives @Utl jung: and notifies the user
    • {{re|Utl_jung}} gives @Utl jung: and notifies the user

Indent

edit

On talk pages, add a colon(:) to indent every time you reply within a thread. For example: 

Hello world! ~~~~
:I see your comment. ~~~~
::{{re|Utl_jung}} I, too, see your comment. ~~~~

produces:

Hello world! Utl jung (talk) 17:13, 7 August 2020 (UTC)

I see your comment. Utl jung (talk) 17:13, 7 August 2020 (UTC)
@Utl jung: I, too, see your comment. Utl jung (talk) 17:13, 7 August 2020 (UTC)

Outdent

edit

Once there are too many indents, it can help to {{outdent}} ({{out}} for short) for better readability. For example: 

[...]
:::::The latest in a long thread of comments. ~~~~
{{out|:::::}}{{re|Utl_jung}} Let's reset the indents for readability. ~~~~

produces:

[...]

The latest in a long thread of comments. Utl jung (talk) 17:13, 7 August 2020 (UTC)

@Utl jung: Let's reset the indents for readability. Utl jung (talk) 17:13, 7 August 2020 (UTC)

Documentation

edit

When writing documentation, it can help to know a few templates and HTML snippets which make it easier to distinguish input from output.

  • Use <nowiki>...</nowiki> to escape all contained Wiki markup
  • Use <code>...</code> to stylise contained text as code
  • Use {{tl}} to write about a template without triggering the template itself
    • To use, write: {{tl + | + template name + }}
    • For example, {{tl|archival records}} displays the link to, but does not trigger, {{archival records}}

Transclusion

edit

To transclude any source page (within a single MediaWiki project, such as en:Wikipedia), use the following code in the target page:

{{SOURCEPAGE}}

Any time you write the code ({{SOURCEPAGE}}) in a target page, you are telling Wikipedia software to put the entire content of SOURCEPAGE in the target page.

In the example below, look at target page A and SOURCEPAGE B.

If B is transcluded in A, Wikipedia software will include in that specific place not the code ({{B}}) itself but the content of source page B (which is just the word foo).

The top row shows how target pages A, P, and Q will look with the changes in code seen in the bottom row to transclude source page B. Note the position of the code in each example target page.

The source page content, foo, will not be highlighted or boxed on the target page. (Foo is in a light blue box here for ease of illustration and understanding.)


Transclusion creates a "live" link between a source page and the target page(s) where the source page's contents appear. This means that when you edit a source page, you will be updating its content across all the target pages that include it. Let's say you create a source page in Wikipedia with the address, date, and time of a local Wikimedia event that you want to invite 50 local editors to. Next, you transclude the invitation source page onto your talk page as well as the talk pages of the other 50 editors. A week later you discover the place for the event must be moved. You would then update the source page, and the new address will automatically appear on all the other attendees' talk pages. You could also tell the editors to invite people you may have missed. They could then simply transclude the invitation source page into other editors' talk pages themselves.

Remember to be extremely careful about editing any source page, especially if it contains transclusions from other source pages. Breaking existing transclusions in a source page is called breakage. Please avoid breakage(s) because not only the larger source page you are editing and all the target pages that include it will be affected. So will both the already embedded (now broken) source page that was used to add content to the larger source page, as well as every target page where the embedded source page was transcluded.

Journey ahead

edit

Once comfortable with the basics of Wiki markup, I highly recommend that you reference these wonderful existing documentation pages to do more and more things with Wiki markup!

Nifty customisation!

edit
  • Syntax highlighter tool - allows custom coloured highlighting for Wiki markup syntax.
    • Enable under Preferences (user toolbar in the top right) > Gadgets
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Utl_jung/sandbox/LD40807&oldid=1141928326"