Непереведённая статья
Вы можете помочь проекту переведя её до конца. |
Это развивающееся руководство о том, как внести свой вклад в вики и над чем работать.
Целью писателей Habitica является создание и поддержка аккуратного, обновляемого, завершённого, и лёгкого в использовании справочника для игроков Habitica. Присоединяйтесь к писателям в гильдии Wizards of the Wiki, чтобы задавать вопросы, обсуждать правки и узнавать много нового.
Быстрые советы[]
Советы из этого раздела и краткая справочная информация для печати справа - содержат некоторые важные пункты этих рекомендаций, но, пожалуйста, прочтите эту страницу Wiki для получения полной информации.
- Тон должен быть информативным и полу-профессиональным. Используйте третье лицо (прим., игрок, они) в вводной части статьи. Вы можете использовать второе лицо в последующих параграфах и предложениях, но никогда не пишите от первого лица.
- Длина страницы или раздела должна быть настолько длинной, насколько требуется, но не больше; она должна быть информативной и сжатой.
- Используйте форматирование текста (прим., жирное начертание, курсив) умеренно. Не используйте цвета и оформление в тексте (прим., зачеркивание, подчеркивание, надчеркивание).
- Используйте правописание русского языка. Пишите полными предложениями за исключением таблиц. Capitalize Habitica terms that have a special meaning in the context of Habitica (e.g., XP, Dailies, Tavern).
- Добавьте соответствующие внутренние и внешние ссылки на статью.
- Избегайте раскрытия информации о предстоящих изменениях, дополнениях, или событиях; если раскрываемая функция уже добавлена в игру, используйте шаблоны {{spoiler start}} и {{spoiler end}}.
- Добавьте изображения, если они будут полезны в контексте статьи; перед добавлением, попробуйте поискать нужное вам изображение через Служебная:Изображения, а также в различных категориях изображений, чтобы избежать дубликатов. При обновлении существующего изображение, загружайте новую версию того же самого файла, вместо загрузки нового изображения.
- Добавьте categories в статьи, если очевидная/полезная категория отсутствует. Проверьте страницу категории для информации перед добавлением её на страницу, и воздержитесь от создания категорий, которые не используются.
- После внесения изменений, укажите конкретно, что вы изменили в специальном поле снизу. Это поможет остальным редакторам проверить вашу работу
- Переименовывайте страницу только в случае крайней необходимости; Если вы это делаете, используйте Ссылки сюда для исправления ссылок на страницу.
- Если вы считаете, что страница должна быть удалена, перейдите в «Классический редактор -> Источник»
{{delete|Причина удаления}}
и введите в верхней части страницы; Укажите причину удаления. - Присоединяйтесь к гильдии Wizards of the Wiki. Отправьте сообщение, когда у вас появятся вопросы. Обсудите потенциальные крупные изменения там, прежде чем вы их сделаете.
С чего начать[]
You can begin contributing to the Habitica Wiki by signing up for a Wikia account. Your username does not have to be the same as your Habitica username in order for you to earn credit for your work when requesting a contributor tier. Be sure to sign in to Wikia every time you edit so you can get credit for your edits and so that we can recognize your contributions.
После регистрации, если вы хотите полностью окунуться в сообщество Habitica Wiki и редакторов Wikia, не стесняйтесь заполнить страницу своего профиля некоторой информацией о себе и создайте блог-сообщение о том, как вы используете свои привычки и ежедневные задания. Давайте познакомимся с вами!
If you are new to wikis, you may want to read the tutorial and view the list of help pages for guidance.
Если вам нужна помощь в редактировании, прочтите Help:Editing или учебное пособие.
О чём писать[]
Наполнение вики — это не просто создание абсолютно новых страниц; это также поддержание качества существующих.
Starting scribes with little to no previous Wikia creating or editing experience may want to begin by helping clean up existing articles. All of the Wiki Scribes are volunteer writers of various writing and national backgrounds who make changes at multiple points during the day; we will never quite be rid of typos and grammatical errors, so fixing the little things (even missing periods) has value. Consider making minor edits as a way to learn how to navigate the site and use the editor instead of trying to jump in immediately by making large additions to pages or creating full articles.
Habitica is an ever-evolving product; new features are added regularly, and some updates supersede previous facts about features. Scribes are encouraged to make changes to related pages as they find them. In addition to the Wizards of the Wiki guild mentioned above, where suggestions for editing ideas are often posted, you can consult the following to learn about and keep track of updates to Habitica:
- Bailey announcements
- GitHub Releases page
- Habitica Blog
- Habitica Tumblr
По мере того, как вам становится удобнее редактирование вики, ознакомьтесь с разделом «Beyond the Classic Editor:Advanced Wiki Editing», чтобы узнать, как сделать более продвинутые изменения.
Before making major changes, use each article's talk page to discuss article contents, resolve any conflicts, and talk about anything specific to the article. Respect is key. Remember to sign edits to talk pages. For more general discussions, use the Wizards of the Wiki guild.
Одним из хороших источников редактирования идей является список страниц с предлагаемыми изменениями.
Просмотр и (при необходимости) редактирование или удаление спекулятивного контента помогает сохранить точность wiki.
You can find a list of useful templates at Category:Templates, some of which are documented on Habitica Wiki:Templates.
Новые редакторы вики должны проявлять осторожность перед внесением следующих типов правки:
- Edits to existing pages in The Keep. Since pages in The Keep are often personal pages (e.g., pages dedicated to a party, guides about how a particular player likes to use Habitica), most pages in the Keep do not need to be edited, even to add clarity/links or fix problems like formatting issues (exceptions include violations of the Community Guidelines). If a page in The Keep is not one person’s or party’s personal page and seems to be worth editing, please ask about it in the Wizards of the Wiki guild.
- Edits to pages with the Under Construction banner. Wiki editors may already be actively working on these pages, so additional edits, however minor, may disrupt their workflow. If you are interested in working on one of these pages, take a look at the history of the page (accessible via the Edit button’s dropdown menu, via the My Tools menu on the Wikia toolbar, or by appending
?action=history
to the end of the page’s URL). If there are recent edits, get in touch with the editor(s) responsible expressing your interest in helping with the page. If there are no recent edits, take a look at the Talk page for any notes on what needs to be done and feel free to ask about how to proceed in the Wizards of the Wiki guild. - Links to wiki pages that do not currently exist. Note that the Habitica Wiki avoids using broken links. Additionally, for the most part, the links listed at Special:WantedPages do not need to be edited (nor those pages created) as they are generally from old wall messages/blog posts.
Подписка на правки[]
If you want to follow changes to this wiki, or look out for new users and edits, use recent changes.
Если вы хотите следить за изменениями в этой вики или следить за новыми пользователями и редакторами, используйте "последние изменения".
Советы новичкам вики[]
- Using the source editor (rather than the visual or classic editor) is recommended, as it is more powerful, allows for more precise editing, and enables you to view helpful comments that may have been left by other editors. You can make it your default editor via the "Preferred editor" dropdown in the editing tab of your Wikia preferences. If the source editor is not your default editor, you can still access it by clicking the dropdown arrow on a page's "Edit" button.
- Badges help determine contributor tiers for scribes. One way of earning badges is by editing the wiki for a certain amount of consecutive days. The following are tips related to maintaining your editing streaks:
- When you first create a wiki account, set your timezone immediately in your Preferences. Changing the timezone can reset your editing streak.
- Wiki editing streaks are counted as edits per UTC day. To ensure you keep your streak, set a Daily to edit the wiki after midnight.
- While points from wiki badges are used as a rough guideline to determine eligibility for contributor tiers, they are not as important as the quality of your contributions to the wiki. Things that earn you badges but don't improve the wiki, such as pointless comments on old blog posts, will 'not' help you earn a contributor tier.
Стиль[]
Тон[]
Тон статьи должен быть информативным и полупрофессиональным. Basically, this means opening all articles with clear-cut and concise definitions of the topic in question, followed by a well-organized and thorough rundown of the topic in detail. Stick with the third person only in the openings, using words like "player" and "user" rather than "you." Once you get into the meat of an article, it should be fine to use the second person, as most articles will have instructions for users of the site to follow. Never use the first person under any circumstances. Writing in all caps is considered yelling, and as such it is an improper tone for this Wiki.
Длина статьи[]
The article should be straight to the point and only as long as needed (especially for broader topics). However, do not go on a tangent and add fluff. Shorter articles are generally more accessible and usable than really long ones. Referencing related pages, however, is recommended and helpful for users in general. Always write the best that you can on all of your contributions.
Форматирование[]
Текст[]
Форматирование текста может включать полужирный или курсивный текст, но не стоит злоупотреблять данными выделителями.Текст с большим содержанием отформатированных слов отвлекает читателя и снижает общую читабельность текста. Do not use text-decoration (overline, underline, etc.). Usual formatting of text does not need strikethrough, and underlined text can easily be confused with hyperlinks.
Отступы[]
Margins and Padding are names for space around an element, be it text, image, table, etc. As a wiki editor, you usually do not have to worry about this. When you get further into it, this can be handled via CSS and the style attribute. You can read up on the use here: margins and padding.
Правописание[]
В этой вики мы следуем стандартным правилам грамматики русского языка.
This includes (but is not limited to) spacing and punctuation. Use one space between sentences. Abbreviations should be followed by periods (for example, e.g. and i.e.). Entries should be made in sentences, not note form, unless entering data in a list or table. If you see improper grammar in a wiki page, feel free to edit it! In addition, make sure you double-check (and maybe even triple-check) your edits after writing them to make sure you don't have any grammar bugs lurking on the page.
Use singular "they" when you need a gender-neutral third-person pronoun. This is more inclusive and less awkward than alternatives like "he/she", and is accepted in many English style guides.
American English is the standard for spelling rules on this wiki. This means that color, personalize, and center are the correct spelling, whereas colour, personalise, and centre are not. The one exception to this rule is the spelling of grey. While American English generally uses gray as the standard spelling, this wiki, as well as Habitica, does not. In order to remain consistent with the rest of the wiki and between the wiki and Habitica, the standard spelling shall be grey (read more). Don't make an edit solely to change British English to American English unless it interferes with the functioning of a link or it is the incorrect spelling of a name. It is acceptable to change it while other substantial edits are being done, though.
Капитализация[]
Написание с прописной буквы отдельного слова неформально называется капитализация (англ. capitalization).
Рекомендуется писать с прописной буквы только первое слово названия, а также имена собственные (Америка, Habitica), входящие в название. (За исключением случая, когда игрок выбрал свое отображаемое имя в нижнем регистре; пожалуйста, уважайте выбор игрока и используйте тот же регистр, что и он. Например, имя модератора deilann не должно писаться как «Deilann».
Это же касается названий праздников, ежегодных событий, достижений и других вещей, например: День наречения Habitica, Зимняя страна чудес, Тройное бинго.
Термины имеющие особый смысл в контексте Habitica должны писаться с прописной буквы. Например, эта Сила — характеристика персонажа; а просто сила — уже что-то иное (напр., "Я хочу увеличить свою физическую силу, поэтому я создам несколько заданий с атрибутом Сила"). Слова, которые относятся к более общим понятиям в игре пишутся со строчной буквы. Например, «меч» в Habitica имеет тот же смысл в реальном мире, и поэтому пишется в нижнем регистре.
Таблицы ниже дают несколько примеров этих инструкций.
Capitalized | Example |
---|---|
События | Summer Splash |
Аббревиатуры | XP, HP, MP, GP |
Задачи | Задачи, Ежедневные дела, Привычки, Награды |
Атрибуты персонажа | Сила, Интеллект, Телосложение, Восприятие |
Названия классов | Лекарь, Разбойник, Воин, Маг |
Инвентарь | Chain Mail, Orb of Rebirth |
Имена боссов (но имя также должно соответствовать свитку квеста) | The Dread Drag'on of Dilatory, The SnackLess Monster |
Названия предысторий | Fairy Ring |
Названия яиц, питомцев, скакунов | Яйцо волка, Пустынная лиса |
Другие слова, которые имеют уникальное значение в Habitica | the Tavern, Perfect Day, Grey Daily, Cron |
Not capitalized |
Example |
---|---|
еда | картофель |
names of items that a player can possess several of | hatching potions |
Gameplay terms that a) are not unique to Habitica and b) are unlikely to have another relevant meaning | quest, party, boss, drop, health |
Заглавные буквы заголовков и подзаголовков см. в разделе «Заголовки разделов» ниже.
Как было отмечено выше, запись КРУПНЫМИ буквами считается криком, и, как таковой, это неприличный тон для этой Wiki.
If you need more information, please see Wikipedia.
Таблицы[]
Таблицы должны быть стилизованы так, как они появляются, при использовании функция добавления таблицы в режиме визуального редактирования(классического редакторования). Это не относится к классификационным или чрезмерно большим таблицам (см. «Питомцы »). Для этого в режиме исходного кода используются следующие параметры:
border="0" cellpadding="1" cellspacing="1" class="article-table" style="width: 500px;
Example header | More header |
---|---|
Table contents |
More contents |
If you'd like to create tables using a graphical interface, TablesGenerator.com allows you easily create MediaWiki tables that then be copy-pasted into the wiki.
Цвета[]
Используйте цвета таким образом, чтобы не нарушать общую цветовую гамму текста. Не желательно часто использовать цвет, так как это может привести к путанице. Например, цветной текст можно спутать с неработающими ссылками или ссылками на другие страницы.
Ссылки[]
Relevant internal links to articles help readers browse the wiki and help avoid dead-end pages. External links to GitHub issues and Trello cards can provide useful behind the scenes or historical information. Do not link to wiki pages that do not currently exist as the Habitica Wiki avoids using broken links.
When creating links on a page, make sure that you link to the current page for the topic in question, and that the target link in the source code (or edit link box) is appropriately capitalized.
You can add internal links by putting double square brackets around text designating the title of the page you want to link to. For example, [[Gold Points]]
becomes Gold Points. You can also use a vertical bar (|) to customize the link title. For example, typing [[Gold Points|gold]]
will produce gold. You can add external links by placing the URL within single square brackets. For example, [http://www.tablesgenerator.com/mediawiki_tables TablesGenerator.com]
becomes TablesGenerator.com. Note the use of a space (not a bar |) to separate the URL from the optional link text.
Because the wiki is a work in progress, pages are occasionally consolidated, removed, or renamed. For example, the Gold Points page has previously been named Gold Points (GP) and Gold Coins. To prevent issues when other sites have linked to the pages on the wiki that no longer exist, the admins leave redirect links to deleted pages. This means that when new internal links are created, the auto-fill suggestion box includes these old link names. When wiki users click these old links, they are redirected to the new page. The new page alerts the user to the old link redirect with a message below the page title, "Redirected from [old page name]", as can be seen using the links in the above example. Link targets that are not capitalized in the source code also give this message. This issue does not affect functionality of the wiki, but using the correct link and preventing these messages improves the wiki's sense of professionalism.
Множественное число и добавление суффиксов ссылкам[]
Plural versions of links can be formed by appending an 's' after the closing brackets. For example, [[Rogue]]s
displays as Rogues. This has several benefits over the alternative ([[Rogue|Rogues]]
): it is easier to type, clearer to read in the source code, and less likely to result in typos. This also works when adding a suffix (e.g., ‑ing, ‑ed, or ‑est) to a link. However, it is not necessary to make an edit solely to change link code from, say, [[Rogue|Rogues]]
to [[Rogue]]s
.
Межъязыковые ссылки[]
Interlanguage links connect different language versions of the same page. For more information about interlanguage links, see Help:Interlanguage links.
When copying pages in order to create new ones of the same type, e.g., using an existing Quest page as a template for a new Quest page, be sure not to copy/import the interlanguage links. Having an incorrect link to a translated page can be confusing for wiki users, especially if the page they originally wanted to read does not exist or is not fully translated at that point.
Информативный текст ссылки[]
The text for links should be informative. Avoid generic link text such as "link" or "page"; instead, use text that provides more information about the page being linked to. For example, "created a page outlining how to adapt Habitica to ADHD" is uninformative, whereas "created a page outlining how to adapt Habitica to ADHD" demonstrates good practice.
This is for the benefit of partially sighted and blind people using screen readers. Screen readers allow users to navigate from link to link while having the text for each link read aloud, so it is beneficial for link text to be informative about the subject matter of the link. This allows users to more easily determine when they want to follow the link or to direct the screen reader to read the surrounding text.
Названия статей[]
При создании новой страницы не используйте круглые скобки () в заголовке. Вики-страницы со скобками в названии будут давать сбои из-за конфликта с форматированием в Таверне.
Заголовки разделов[]
Liberal use of headers breaks up articles, enables easier reading, and allows the automatic generation of tables of contents. However, too many subheadings makes the text harder to read, especially if related content is being broken up unnecessarily. To keep text easy to follow, try to strike a balance in the number of headings used.
Headers and subheadings should not be changed unnecessarily. They can be linked to from other pages and from locations outside the wiki (e.g., Habitica itself, GitHub, and blog posts) so any change to a heading will make these links nonfunctional. If it is essential to change a header, correct all links leading there from elsewhere in the Habitica wiki. Also, search likely locations in the Habitica website (habitica.com) for links to the heading. If you find any, create a new issue in GitHub to ask that the link be changed.
Headers and subheadings are capitalized according to the rules described in Composition titles (a form of title case). However, if you see an existing header that does not have correct capitalization, please do not change it unless you are certain that there are no links to it.
Инфобоксы[]
Individual item pages should have an infobox with an image, the tooltip description, and buy/sell prices - instead of listing this info in paragraph form. Example code for the template is as follows.
{{infobox item | title = Snowball | image = Inventory special snowball.png | imagewidth = 51 [default: 210 pixels] | imagecaption = Throw a snowball at a party member. | buy = 1 [[Файл:Gem.svg|link=Самоцветы]] | sell = - }}
Содержание (TOC)[]
The table of contents (TOC) will automatically generate after the fourth main sub-heading. The TOC can be forced to appear with less than four sub-headings by including the following code in the source view of the editor at the start of the wiki document: __TOC__ To shift the TOC to the right of the page, enter the following code into the source view of the editor at the top of the wiki document:
{| align="right" | __TOC__ |}
Математические выражения и формулы[]
The Habitica wiki supports mathematical markup using a variant of LaTeX. This is well documented in the Wikia Community Documentation, with further details about specific markup elements available in the Wikipedia help pages.
By default, the mathematical markup should render as black text with a transparent background, e.g.:
<math>{y = x^2 + 7x - 2}</math>
produces
Note that currently you can only enter mathematical markup in the source editor.
Эмодзи[]
Emoji are rarely used in the wiki - usually only when quoting text from Habitica that contains them. If copying and pasting the emoji doesn't work, another way to include an emoji in a wiki page is to write its HTML entity in the source editor. For example, for 🐘, you would write 🐘
(its HTML entity with decimal number) or 🐘
(its HTML entity with hexadecimal number) - it doesn't matter which one.
You can find an emoji's HTML entity on the internet. One good place to look it up is FileFormat.Info. Either find the emoji in their list of emoji, then click on the corresponding Unicode link on the right side, or enter the emoji's name (in this example, "elephant") in the search field.
There are emoji which don't have a corresponding Unicode character and for which this method doesn't work - but in most cases, it does.
Another good source to look up different versions of emoji and copy them directly is Emojipedia.
Как избежать спойлеров[]
When looking for new information to add to the main namespace, stick to features that are already implemented, visible, and accessible to all players on Habitica. Information about planned or upcoming features available on GitHub and the various Trello boards may contain spoilers that the staff wish to keep as surprises for players. This is particularly important for world events, particularly those with multiple event-based reveals like the battles with world bosses. It is, of course, okay to discuss quest lines in designated areas like the Camp.
For spoilers of already implemented content, such as resolution text for boss or collection quests, you can use the templates for spoilers: Template:Spoiler start and Template:Spoiler end. The spoiler warning template, Template:Spoiler, should be used on pages such as the Camp, where most or all content are spoilers.
Изображения[]
Images should be added if they are useful in the context of the article, for example, if they help make a concept more clear, with the exception of the Whats New pages which should match the Bailey announcements in old news.
Before uploading a new image, search for it in Special:Images and in the various Images categories. The image you want might already be uploaded and if so, you should not upload a duplicate (see Replacing v. Deleting below for more information). If it has not already been uploaded, you can find most of the original Habitica images used on the website (including items, food, pets, and mounts) in GitHub under the website/assets/sprites/spritesmith and website/assets/sprites/spritesmith_large directories in the "habitrpg" repository.
Типы файлов[]
Изображения должны быть загружены в формате PNG с максимально доступным разрешением. В особых случаях допускаются различные форматы изображений (например, если необходим анимированный GIF).
Images should have transparent backgrounds unless the background is essential to understanding the information that the image is trying to present.
Названия файлов[]
Standard images from Habitica, such as images of equipment and pets, as well as quest-related images, should use the file names that are used in Habitica itself; this is of especial importance for equipment and quest scrolls. For example, the Winter 2015 Healer armor has the file name broad_armor_special_winter2015Healer.png. File names can be found in GitHub under website/assets/sprites/spritesmith/. Don't use file names beginning with "shop_..." even if the shop version of the image is uploaded; instead, use the file name for the normal version of the image (e.g., use weapon_healer_1.png rather than shop_weapon_healer_1.png).
Other images such as example avatars or task should be uploaded named with generic but descriptive titles. The name should accurately reflect the content of the image, distinguishing it from other images, without describing elements of the image that may be changed as Habitica evolves.
Try to avoid using words in the name that would be inaccurate should the image need to be updated in the future to represent changes to Habitica. For example, the image on the right was uploaded to show what the buff icon looks like on an avatar. It was correctly named Avatar_Buff.png.
Avoid including any words in the image's name that are likely to become irrelevant when the image changes:
- Dates (e.g., Avatar_Buff_August_2014.png)
- Version numbers (e.g., Avatar_Buff_version_1.png) or words indicating a new version (e.g., Avatar_Buff_updated.png or Avatar_Buff_modified.png)
- Avatar names (e.g., Deborah_Buff.png)
- Elements in the image that might change when the site is updated, such as colors or shapes (e.g., Buff_White_Arrow.png)
An exception can be made if it is absolutely necessary and not likely to change (e.g., July_2014_Mystery_Item.png).
Подписи[]
Используйте подпись, чтобы объяснить, что изображено на картинке, а также для уточнения, почему именно она была добавлена на эту страницу
Ширина подписей[]
When paired with smaller images, some captions may wrap undesirably as seen to the right.
You can use the {{infobox item}} template as follows to render the image without undesired wrapping:
{{infobox item | title = | image = Inventory special snowball.png | imagecaption = Throw a snowball at a party member. }}
Заменить или удалить?[]
Outdated images should be replaced rather than deleted if at all possible. Go to the image's page, then select the drop-down menu on the edit button next to the title. You will see the following options: History and Replace. Click on replace, then use the form displayed to upload the updated image. You can write a brief description of what has changed in the image, or why a new version is needed.
Once the form is submitted, the old version of the image will be replaced by the new one, but the old version will still be available in the file's history tab.
Note: There is an ongoing issue with the Wikia caching so that for a little while after a replacement image is uploaded, the old image still shows. Wikia seems to occasionally have very aggressive caching that can hold on to the old version of an image for hours. It should rectify itself within a day, but if it doesn't, the issue can be reported to wiki staff and they'll manually clear out their cache. See also the Wikia Community Central's Help:Purge page.
Using this method to replace an old image has a lot of advantages over uploading a completely new image. It means that you can see all versions of an image in one place, and it's very easy to revert to an old version if needed. It means that all links on the wiki and elsewhere will keep on working. It reduces clutter in the wiki's "Photo" section because there's only one entry for each image.
Most importantly, it makes it impossible for anyone to accidentally use an old version of an image. Someone who's editing a page and needs to choose an image will find it hard to pick the right one, and if more than one similar image is used across the site, then all of them have to be updated when Habitica changes. But if new versions of images are uploaded to "replace" old images rather than uploaded as new images, this issue disappears.
Check out this thread for more explanation of why it's generally better to replace rather than delete.
Авторское право[]
All images on the wiki must have accurate copyright (license) information in their descriptions. Images from Habitica (artwork, screenshots, etc) are licensed under the CC-by-NC-SA 3.0 license. If your image is not from Habitica, please make sure you are allowed to use it (i.e., using it on the Habitica wiki does not break any copyright licenses).
You can add license information when you upload the image to the wiki (that's easiest and is strongly recommended) or you can edit the image after you've uploaded it.
To add a license when you are uploading an image, when you get to the "Upload Photo" screen:
- click on the "More options" link that you'll see near the bottom right
- find the "Licensing" drop-down list
- select the appropriate option; for images from Habitica (artwork, screenshots, etc), use "This is licensed under under the Creative Commons Attribution-NonCommercial-Share-Alike license."
To add a license to an existing image:
- click on the image to open it in a pop-up screen
- click on the "more info" button at the top right of that screen to go to the image's own wiki page
- click on the "edit" button (note: the source editor is recommended; if it is not your default editor, click the dropdown arrow on the "edit" button to access it)
- in the text area that you will then see, copy and paste this text: == Licensing ==
- on a new line under that text, paste in the correct code for the appropriate license:
- for images from Habitica (artwork, screenshots, etc), all you need to paste in is "{{CC-BY-NC-SA}}" (without the quote marks)
- for images from other sources, find the appropriate license code at Wikia's Help:Image copyright tags page
- in the "Edit summary" box to the left of the edit page, paste in this text or similar: "adding copyright information"
- click the "Publish" button.
Добавление пробелов и предотвращение неуклюжего перекрытия[]
If the image is creating issues with the layout, you can add the following code to create a clear space to fix it.
{{clr}}
Промо-арт вики[]
Some pages have decorative promotional art, depicting Habiticans engaging in activities relevant to the material on the page. These images can add flavor and help break up large areas of text. If you find a page that could benefit from this type of art and have an idea for it, submit your idea to the appropriate card on the Pixel Art Trello. Once your idea is approved, it will be added to a list of scenes needed. Artisans will then be able to claim and create the scene.
As wiki promotional art is decorative, it does not require captions.
Видео[]
Videos from Youtube and Vimeo can be included, but should only be used if they improve the article significantly.
Категории[]
Categories can be added to articles to group them according to a certain topic. However, having too many categories, especially when they contain very few pages, have vague topics, or are similar to other categories, can add unnecessary clutter to the wiki and make it more difficult for users to find the most helpful categories. Please refrain from adding categories that are not already in use without first discussing your idea with other experienced Scribes, such as in the Wizard of the Wiki guild.
Category pages (for example, Category:Contributing) can optionally contain one to two sentences to explain what the category is for. This is not necessary when the intention is obvious. Category pages should never contain more content than that because their primary purpose is to be a list of related articles. Check the page for a category before adding articles to the category, since it may contain guidance about what pages should or should not be added.
Most categories are reserved for certain types of pages--in particular, the categories listed in the Category Index should only be used for main wiki pages, unless noted otherwise (e.g. Category:Guilds and Category:Parties are for pages in the Armory). To avoid clutter, please don't add these categories to other types of pages (templates, blog posts, files, etc.).
Описание изменений[]
When making edits, write a short summary of the changes that have been made in the 'Edit Summary' box before publishing. Depending on the edit, a few words may suffice, but major edits may need longer summaries or the inclusion of rationales. Providing these summaries allows other scribes to quickly get a sense of what has changed. It is also extremely helpful when filling out contributor tier applications, as these summaries are shown as part of the edit histories on user profiles in the 'Contributions' tab. In addition, it makes finding specific changes in a series of edits much easier.
If you have trouble remembering to fill out the edit summary, you can (if you have an account) set your user preferences to remind you if you forget to leave one. In the "Editing" section of your preferences, check the box reading "Prompt me if I leave a blank edit summary" (the third checkbox under "Editing experience") and save the change. This will remind you to fill in your edit summary if you leave it blank on any page (except your own user page) on any Wikia wiki. If your edit summary is blank and you click "Publish" you will be given a reminder reading "Reminder: You have not provided an edit summary. If you click Publish again, your edit will be published without one". You then have the option to type an edit summary as recommended or just save your edit without one.
Переименование страниц[]
On rare occasions, pages may need to be renamed. When pages are renamed, Wikia will automatically create a redirect page that will take old links to the new site. However, links on the wiki will not be updated automatically. The wiki will still function, but users will be alerted to the fact that the link is old with a message below the page title, "Redirected from [old page name]". To eliminate this message and maintain the sense of professionalism that the wiki strives for, you can use the special page WhatLinksHere to find those out of date links that renaming has created, and fix them. Simply type the old page title into the appropriate box, and they will be displayed.
Удаление[]
Есть случаи, когда страницы могут быть переименованы, также были случаи, когда страницы будут удалены. Только администраторы вики могут удалять страницы. Если вы считаете, что страница должна быть удалена, откройте классический редактор, а затем вкладку «Исходный код». В верхней части страницы добавьте следующий код с указанием причины для удаления:
{{delete|Reason for deletion}}
Keep in mind that at this time, redirect pages are a permanent fixture for the wiki. The wiki is here to provide information to the users in a way that's convenient for them to use. Broken external links, whether from an outside site, the Habitica forums, or a page that a user bookmarked, make it less convenient for the readers to use the wiki. Therefore, redirect pages are kept in place so that these links will not give a "404 Page Not Found" error. This ensures that wiki users have a better experience when trying to locate information, and increases the wiki's efficiency in providing consistent, up-to-date information. Remember, our goal is to create and maintain an accurate, up-to-date and easy-to-use guide for players of Habitica, so if there is a redirect page that you firmly feel needs to be deleted, at the top of the page add the deletion code with the reason that the page should be deleted. From there, the wiki admins will discuss the reason and make a decision, and the page will either be deleted, or the deletion code can be removed.
Создание песочницы пользователя[]
Песочница-это страница, которую можно использовать для практики редактирования, изучения форматирования и составления черновиков без обязательной публикации на главной странице. Если вы из тех, кто учится на практике, наличие песочницы, где вы можете опробовать код, форматирование и дизайн, может быть очень полезным. Ниже приведены шаги по созданию вашей песочницы.
1. Go to your user page. You can do this by clicking on your user icon at the top right of any wiki page. You may have to click twice if the first click opens up the menu.
2. Add /Sandbox to the end of your URL. Click on the URL box in your browser, deselect the text, and type in /Sandbox at the very end of. Go to this page.
3. Since you have not yet created your sandbox, you will have the option to do so here. Right next to the page title, click the Create button.
4. If it opens up in the visual editor, select the option to open the source editor. You can find this option by clicking on the drop-down menu next to the Cancel and Publish buttons, and selecting Source Editor.
5. Paste the following code into the text box:
{{Sandbox}} <!--EDIT BELOW THIS LINE-->
6. Below this pasted text, you can begin to practice editing. One idea to begin with is to add a table of contents and links to useful templates and code that you often need to look up.
7. Whenever you are finished editing in the source editor, click Apply Changes on the bottom right of the frame.
8. Click on Publish to save your page.
9. To find your Sandbox easily, add a link to it on your profile page. You can do so by pasting the following code into the source editor of your user page (found by clicking on your user icon, selecting Edit Profile under the Profile tab, and selecting the Source Editor option), replacing "Username" with your own username:
[[User:Username/Sandbox|My Sandbox]]
10. Voila! You now have a Sandbox of your own! Experiment with it as you please!
Другие советы по аккаунту вики[]
Панель инструментов[]
Если у вас есть учетная запись вики, вы можете использовать панель инструментов, расположенную в нижней части экрана, для использования ярлыков и других инструментов для выполнения различных функций. Вы можете найти более подробную информацию на панели инструментов здесь.
Список доступных инструментов панели инструментов см. на этой странице.
Отключение рекламы[]
Если у вас есть учетная запись Wiki и вы хотите отключить рекламу, вы можете перейти на страницу настроек, прокрутить вниз до объявлений и выбрать «Не показывать все объявления», а затем сохранить свои настройки.
Обновление страниц[]
Иногда страницы могут вести себя странно, как будто не показываются изменения. Если это происходит, попробуйте добавить ?action=purge
в конец URL-адреса и перейти по этому адресу. Это приведёт к перезагрузке страницы и устранению многих проблем.
Получение ранга участника[]
Пожалуйста, прочитайте The Keep: The Knights Chambers, чтобы понять процесс запроса уровня участника для вики-редакторов, которые являются основными. Обратите внимание, что шаблон приложения работает только в том случае, если у вас есть редактор исходного кода в качестве редактора по умолчанию, он не работает если ваш редактор по умолчанию является визуальным редактором. Вы можете изменить это предпочтение на вкладке редактирования ваших настроек Wikia.
Если у вас уже есть какой-то другой способ "участия"(вклада), то подавайте заявку на следующий уровень (но если вы подадите заявку на неправильный уровень, вы попадете в нужный уровень, поэтому не имеет значения, подали вы её правильно). Например, если вы находитесь на уровне 3 (например, от Socialite, Storyteller и Artisan), то подайте заявку на уровень 4.
Вы можете зарабатывать очки wiki, зарабатывая значки , но не слишком беспокоитесь о полученние вами вики-баллов. Очки - это только одно требование для получения награды уровня; Вклады значимого содержания - истинные критерии для получения уровня Участника.
The entries in the application are checked manually to see how much they count towards tiers (which is why assigning wiki tiers is so slow). Please note that when pursuing wiki badges for editing streaks, the cutoff time is in UTC rather than your designated time zone. You may want to keep that in mind if you're working towards earning those badges! For wiki editors living in places that obey Daylight Savings Time, be aware that your deadline for making changes will shift along with the time change as well.
When tiers are assigned, it's usually for a body of work in a single field (e.g., a pure Scribe tier or a pure Blacksmith tier). Occasionally, there are case-by-case exceptions to this rule.
Once you've been awarded a tier, do not keep updating the same application; you can start a new application for your next tier. Also note that every contribution should be mentioned only on one application. For example, if you've added a section to the Pets page and mentioned it on your tier 1 application, and are then awarded that tier, then that contribution should not be included in your tier 2 application.
Более высокие уровни всегда сложнее получить, чем предыдущие.
One overriding rule that can change everything else: The staff (and occasionally moderators for the low tiers) have final say over tiers and can make decisions that might conflict with the other guidelines. However, this would only be done for a good reason that seems fair to the staff and moderators. One recent example is the first tier given to WikiFAQ_bot - it was given long before a Socialite would usually get a tier, but it was clear that WikiFAQ_bot was being useful and the tier was awarded to allow the bot's name to stand out.