Digiclass:Tutorial: Difference between revisions
(first version of tutorial page (with thanks to Becky, Elli, Darcy, Tom, Sarah, Paolo, etc.)) |
(→Lists) |
||
| Line 97: | Line 97: | ||
[https://www.mediawiki.org/wiki/Help:Lists# Media Wiki Help page on Lists] | [https://www.mediawiki.org/wiki/Help:Lists# Media Wiki Help page on Lists] | ||
=== 4. Template for a common page GB === | |||
<pre> | |||
==Available== | |||
* URL | |||
==Editor== | |||
* Name·s | |||
==Description== | |||
… | |||
[[category:category1]] | |||
[[category:category2]] | |||
</pre> | |||
The template above is as generic and minimal as possible, so that you can copy it to create a new page or refer to it for reference when editing and improving a page (see following sections). Some pages may have slightly different formats, and we will discuss these shortly too. The four main sections of this minimalist page are: | |||
1. '''Available''': where to find the resource in question. This is most commonly a URL, or possibly multiple URLs (live version, project code, documentation wiki, etc.), but may also include links to a library catalogue, or just information about an offline media format, or the fact that a project or tool is legacy or defunct. There should always be at least one entry under this heading. For consistency, please format this content in a list (even if there is only one item). | |||
2. '''Editor''': the person or persons responsible for authoring or curating the resource in question. If applicable, you may prefer to use the heading <nowiki>==Author==</nowiki>, <nowiki>==Director==</nowiki> or similar for this section. Please do not list an entire project team along with titles, roles, job descriptions, honorifics, links to home pages, etc. in this section (they belong on the project’s own webpage); it is really designed just to list one or a short list of the key people responsible for an entire project. | |||
3. '''Description''': at a minimum this should include a few lines of text, as found on the project’s “About” page, explaining the key features of the resource. If this is copied wholesale from the project page, rather than paraphrased in your own words or reviewed from a user perspective, please make this clear by surrounding the text with <nowiki><blockquote></nowiki>, and noting at the top “Taken from the project page” and today’s date (in year-month-day format). | |||
4. '''Categories''': These are invisible tags that you should list at the bottom of the page, in the form <nowiki>[[category:Projects]]</nowiki> etc. | |||
Revision as of 17:09, 26 November 2025
Overview
The Digital Classicist Wiki contrains three broad types of page:
- Projects, which may be based on fixed-term funding or long-term research by single scholars or teams, often including a concrete (usually digital) output
- Tools, including those not specific to classics or ancient studies, but which are also used to study, find or transform ancient data
- Methods, overview or FAQs, which do not necessary address individual projects or tools (but may in some cases link to several)
Most pages include the following structure, as appropriate:
- Available (where the project or tool can be found, URL or other information (including library records, description of legacy resources)
- Authors/editors, naming the lead individuals responsible for the resource, project leads, etc.
- Description, in the editor's own words or quoted (with attribution) from the project website
- Several categories, to help users browse to the resource. See the list of categories.
Tutorial
- tba: Link to video tutorial
1. Request an account
The “Create Account” option in this wiki has been disabled to limit spambots, so accounts have to be created for you by one of the administrators. Please contact any one of the people listed at Administrators to request an account. Please give a brief explanation of who you are and the reason for your interest in editing the Wiki.
Your username and password will be sent to you when your account is created. The default format for your username will be “ForenameSurname”. If you have a usual or preferred name that may not be obvious to the administrator from your email, please provide that information in the email requesting access.
2. Log in
In the upper-right corner, click “Log in.” Enter your username and password (as provided in step 1, above). If this is your first time logging in, you should change your password to something both more secure and memorable.
3. Wiki Syntax
It is possible to use the wiki markup toolbar at the top of the editing area to insert markup as you edit. However, you should be familiar with the conventions used in wiki markup, especially if you are editing an existing page. The following are the most commonly used formatting codes in the Digital Classicist wiki. Mediawiki provides a comprehensive guide to formatting, linking and other markup.
Headings
Enclose the heading text in equal signs.
- = Level 1 heading = will create a level-one heading (equivalent to html <h1>)
- == Level 2 heading == will create a level-two heading (equivalent to html <h2>)
- === Level 3 heading === will create a level-three heading (equivalent to html <h3>)
- up to
- ====== Level 6 heading ====== will create a level-six heading (equivalent to html <h6>)
Try to use headings in sequence, so that you only use level 4 if it is preceded by levels 1, 2, and 3 for example. If there are 4 or more headings (of any level) in a document, a table of contents will automatically be generated at the top of the page.
Note: In order for headings to render correctly, there should be no spaces at the beginning of the line.
Italic
''italicized txt'' renders as italicized txt
Bold
'''bolded txt''' renders as bolded txt
Links
Links usually have two parts: the link text, which is what a user sees and clicks on, and the URL, the actionable link address. In some cases, these are the same, as when a URL is visible and clickable in a document.
There are two main permutations of link syntax.
- To link to a page in the Digital Classicist Wiki, just put the name of the page inside double square brackets. For example, [[Prosopographia Imperii Romani]] will display as Prosopographia Imperii Romani and link to the project description page. Note that the text inside the double square brackets is the name of the page, not the actual link. If you would like link text that differs from the page name, you can use the full syntax, which includes the link text separated from the link address by a vertical bar. For example, [[Prosopographia Imperii Romani|Roman Prosopography]] will display as Roman Prosopography but link to the same page as in the fist example.
- To link to an external page, the syntax is similar but not identical. The link text and link address are enclosed in single square brackets, and there is no need for the vertical bar to separate them. For example, [http://nytimes.com New York Times] will display as New York Times and link to the NY Times web site. You can also specify only the link address without square brackets, if you want the URL to be the visible, clickable link. http://nytimes.com will display as http://nytimes.com. Single square brackets around the URL only will create a numbered reference linking to that address: [http://nytimes.com] will display as [1].
Lists
Lists are indicated by putting an asterisk or a hash mark at the beginning of a line. Each line in unordered or bullet list begins with an asterisk. A second level is indicated using two asterisks, with additional asterisk rendering as further nesting.
* First unordered list item * Second unordered list item ** A nested item *** A further nested item
renders as:
- First unordered list item
- Second unordered list item
- A nested item
- A further nested item
- A nested item
Ordered or numbered lists work exactly the same way, but instead of an asterisk, you insert a hash mark.
# First unordered list item # Second unordered list item ## A nested item ### A further nested item
renders as:
- First unordered list item
- Second unordered list item
- A nested item
- A further nested item
- A nested item
4. Template for a common page GB
==Available== * URL ==Editor== * Name·s ==Description== … [[category:category1]] [[category:category2]]
The template above is as generic and minimal as possible, so that you can copy it to create a new page or refer to it for reference when editing and improving a page (see following sections). Some pages may have slightly different formats, and we will discuss these shortly too. The four main sections of this minimalist page are:
1. Available: where to find the resource in question. This is most commonly a URL, or possibly multiple URLs (live version, project code, documentation wiki, etc.), but may also include links to a library catalogue, or just information about an offline media format, or the fact that a project or tool is legacy or defunct. There should always be at least one entry under this heading. For consistency, please format this content in a list (even if there is only one item). 2. Editor: the person or persons responsible for authoring or curating the resource in question. If applicable, you may prefer to use the heading ==Author==, ==Director== or similar for this section. Please do not list an entire project team along with titles, roles, job descriptions, honorifics, links to home pages, etc. in this section (they belong on the project’s own webpage); it is really designed just to list one or a short list of the key people responsible for an entire project. 3. Description: at a minimum this should include a few lines of text, as found on the project’s “About” page, explaining the key features of the resource. If this is copied wholesale from the project page, rather than paraphrased in your own words or reviewed from a user perspective, please make this clear by surrounding the text with <blockquote>, and noting at the top “Taken from the project page” and today’s date (in year-month-day format). 4. Categories: These are invisible tags that you should list at the bottom of the page, in the form [[category:Projects]] etc.