Meta:ICANNWiki Content Planning

Revision as of 04:43, 11 June 2024 by MarkWD (talk | contribs) (Content Guide for ICANNWiki: +Base style for articles)

This meta space for ICANNWiki Content Planning lists resources and concepts that are being worked on or need work performed in them.

Content Guide for ICANNWiki edit

Last revision in June 2024.

Base style for articles edit

  • For all articles, with the title always in bold: Article title (is/was) a (type of entity, like "registrar" or "lawyer"]
    • Then, in case of a natural person: originating from (country/territory).
    • Then, in case of a legal person: founded in (four-digits year), in (country/territory).
  • Then, write any additional essential information to close off the leading paragraph.
  • Then, create a level two heading with ==Example== to start writing specific sections, usually starting with "Origin" or "History".

Scope edit

ICANNWiki is concerned with all matters related to Internet Governance, not being limited to ICANN. The scope of this coverage is wide, but should not normally encompass subjects that would already be better covered elsewhere.

For a clear-cut example, it might be notable to outline that a person comes from a certain geographical region, for example, if they were responsible for bringing Internet connectivity to the Brazilian city of Embu das Artes. In that case, an external link to Wikipedia’s article on Embu das Artes would be ideal, rather than creating an article for ICANNWiki.

For a more subjective example, an article on router devices might be better covered by Wikipedia’s article on Router (computing), although that might not be the case if an ICANNWiki volunteer wants to contribute their expert insights into how this affects Internet Governance. Meanwhile, an article on the practice of routing traffic can be assumed to be better covered by ICANNWiki’s specialized community in our Routing article.

Style edit

Given the global nature of the ICANNWiki project and the diversity of its users, an academic tone is not expected from contributions. However, a professional tone is required. Usage of slang and stylistics outside of common language rules is discouraged exactly to ensure an even playing field for all contributors. This normalization will be enforced by community managers and administrators.

The main language of the wiki is English, and any variant of that language is accepted, with spellings such as color and colour being equally valid and with no need to normalize them. Our focus is on stabilizing the main version of the wiki before branching out to other languages, but exceptions can be made if they are coordinated with administrators.

In the case of companies, NGOs, and programs, the writing of materials relating to their work must be neutral, without marketing products or services. It is valid and welcome to state what an entity does and how that is related to Internet Governance or how that entity participates in ICANN. Entities are allowed to list their services, but that should not be done as a sales pitch. Occurrences of blatant marketing posting will be moderated.

Notability edit

The criteria for notability of an article are that of being relevant to Internet Governance or ICANN in general, without the need for further qualification as long as that connection is firmly established. The bar is intentionally set lower than that of Wikipedia in order to accommodate concepts and community members that would not otherwise be fit to be included there.

Standardization edit

  • Internet Society (ISOC) Chapters: Internet Society {Country Name} Chapter
Example: Internet Society Armenia Chapter
  • ICANN Meetings: ICANN {Number with leading zero} (as the root) + ICANN {Number with leading zero} - {Location as spelled by ICANN} (as a redirect)
Example: ICANN 41 (root) and ICANN 41 - Singapore (redirect).
Example: IGF 2007
  • Acronyms:
    • Rule: The article's full name is the root page, while its acronym should redirect to the root.
    • Exceptions: Organizations and events that are almost unanimously known by their acronym, as is the case of RALOs, NICs, and the IGF. This also applies to well-known nomenclatures of standards, like RFCs and MoUs.
Example for rule: Registration Data Access Protocol is the root and RDAP is the redirect.
Example for exception: IGF is the root and Internet Governance Forum is the redirect.

Data sources edit

Trusted sources edit

Useful sources edit

Templates edit

The contents of the templates below are presented for reference only and may not reflect their live version due to these not being directly extracted from the current source of the templates.

Template:Articles needing attention edit

This article needs attention. Please help improve it by revising it in a manner consistent with ICANNWiki's content guidelines. Pay attention to matters such as maintaining a neutral point of view and sourcing information where possible.

Template:Candidates for deletion edit

This article has been marked for deletion, most likely due to not following ICANNWiki's content guidelines. Without undergoing substantial changes, it will eventually be removed by our content managers.

Template:Major articles parallel with Wikipedia edit

This article concerns a major concept that exist in the English version of Wikipedia, which can be seen by clicking here. However, it has been deemed appropriate by our content managers to have its own unique and unrelated version in ICANNWiki.

ICANNWiki feature documentation edit

All users edit

  • Video embedding
    • Provided via Extension:EmbedVideo.
    • Usage: {{#ev:service|id|dimensions|alignment|description|container|urlargs|autoresize|valignment}}
    • Example: {{#ev:youtube|mQr3zTKvnyE}} embeds a Youtube video of ICANN 40's opening press conference.
  • Audio embedding
    • Built-in via MediaWiki.
    • Usage: [[File:Filename.extension|Caption]] (Incomplete?)
    • Example: [[File:Test.mp3|Test]] embeds a media player for the file.
  • Mathematics

SysOps and devs edit

Wiki resources edit

Wikimedia edit

Pages edit

Categories edit

Users edit

Technical edit

Meta