Wiki Editing Hints/ru: Difference between revisions
No edit summary |
mNo edit summary |
||
| (11 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
{{LangSwitch}} | |||
==Начало== | == Начало == | ||
# Если у вас есть что рассказать о Qt, то Wiki это место, где вы можете поделиться этим. '''But restrict your articles to Qt related topics''' | # Если у вас есть что рассказать о Qt, то Wiki это место, где вы можете поделиться этим. '''But restrict your articles to Qt related topics''' | ||
| Line 9: | Line 9: | ||
# Если кто-то уже создал страницу на эту тему, то вы увидите ее в результатах поиска. | # Если кто-то уже создал страницу на эту тему, то вы увидите ее в результатах поиска. | ||
# Вы можете редактировать все содержимое на большинстве страниц. (стр. [[WikiSyntax|Синтаксис Wiki]] поможет с разметкой) | # Вы можете редактировать все содержимое на большинстве страниц. (стр. [[WikiSyntax|Синтаксис Wiki]] поможет с разметкой) | ||
# Если нет страницы, которую вы хотите создать, то можно создать ее, нажав кнопку | # Если нет страницы, которую вы хотите создать, то можно создать ее, нажав кнопку "Create new page". | ||
# Используйте пробелы и подчеркивание для заголовков статей и категорий. — [http://developer.qt.nokia.com/forums/viewthread/2262/ см. соответствующие темы на форуме] | # Используйте пробелы и подчеркивание для заголовков статей и категорий. — [http://developer.qt.nokia.com/forums/viewthread/2262/ см. соответствующие темы на форуме] в [[ForumHelp|голосовании форума]] можно проголосовать. | ||
# Не засоряйте историю страницы, тестируя разметку, используйте [[Playground]] вместо этого. | # Не засоряйте историю страницы, тестируя разметку, используйте [[Playground]] вместо этого. | ||
==How to edit a page== | == How to edit a page == | ||
The editor provides you with the most common functions collected in a kitchen sink. That should get you quite somewhere. | The editor provides you with the most common functions collected in a kitchen sink. That should get you quite somewhere. | ||
If you prefer to write wiki code directly you can have a look at [http://warpedvisions.org/projects/textile-cheat-sheet/ this cheat sheet] | If you prefer to write wiki code directly you can have a look at [http://warpedvisions.org/projects/textile-cheat-sheet/ this cheat sheet] and practice your skills [http://textism.com/tools/textile/ at Textism.com] They provide a tool that turns Textile - the markup language our wikis use - into HTML for preview. | ||
Please, use the preview option to check your edits before you save unless you are 120% sure that you '''never''' make mistakes. | Please, use the preview option to check your edits before you save unless you are 120% sure that you '''never''' make mistakes. | ||
| Line 23: | Line 23: | ||
'''C++ code will be automatically highlighted on wiki pages!''' | '''C++ code will be automatically highlighted on wiki pages!''' | ||
==How to make your pages easy to use== | == How to make your pages easy to use == | ||
Help fellow developers find the great insights | Help fellow developers find the great insights you're sharing by following a few simple guidelines: | ||
===Write like | === Write like you're coding === | ||
Good wikis, like good code, are easy to scan and maintain. Each article should cover one topic (much like a class). Each paragraph should contribute one aspect to the topic (like a function). If you change thoughts it helps to change paragraphs so you | Good wikis, like good code, are easy to scan and maintain. Each article should cover one topic (much like a class). Each paragraph should contribute one aspect to the topic (like a function). If you change thoughts it helps to change paragraphs so you don't bury great insights where they're hard to find. | ||
===Use headers for scannability=== | === Use headers for scannability === | ||
Long articles are easier to read if you add some informative headers. Please use h1 level for your introduction and then h2 and h3 levels to outline your discussion. (The editor includes buttons for them.) Try to write your headers so they outline what you have to say all by themselves, because you can then … | Long articles are easier to read if you add some informative headers. Please use h1 level for your introduction and then h2 and h3 levels to outline your discussion. (The editor includes buttons for them.) Try to write your headers so they outline what you have to say all by themselves, because you can then … | ||
===Add a table of content=== | === Add a table of content === | ||
When readers find your article, they will scan the first page to figure out if | When readers find your article, they will scan the first page to figure out if it's what they're looking for. If your article is not much longer than one page, all you need to do is write it. If it's much longer than that, use a table of content to show the reader what's to come. Your opening paragraph plus table of content should be all the reader needs to know whether to click down or click away. | ||
All you need to do is add this tag | All you need to do is add this tag "["toc align_right="yes" depth="3"] (remove quotes surround first bracket) and the wiki engine will create the TOC for you. The tag can appear anywhere, but is helps maintainability if it appears at the beginning of your article. | ||
===Add Categories=== | === Add Categories === | ||
Add category tags to insert a link to your article in the appropriate summary pages. By adding your article to existing categories you help readers find your content. | Add category tags to insert a link to your article in the appropriate summary pages. By adding your article to existing categories you help readers find your content. | ||
If you want to create a new category and summary page, just tag your article to a category that does not yet exist. ''' | If you want to create a new category and summary page, just tag your article to a category that does not yet exist. '''<span class="category! a misspell accidentally you if created be even will it Note:"></span>''' | ||
== How to translate a page == | |||
If you translated a wiki page keep in mind that it has to be accessible from existing language versions. This is quite easy by adding or expanding the navigation at the top of the page. The navigation should follow this pattern: | |||
'''Language_of_the_page''' Language1 Language2 … side by side with their corresponding links. | |||
For example in this page (remove the space between the brackets "[ [") the following is used: | |||
<code>'''English''' [ [WikiHilfe|Deutsch]] [ [WikiPomoc|Polski]]</code> | |||
For example in this page (remove the space between the brackets | |||
In most cases you should name your page by adding the language to the end of the original title (assuming the article was originally written in English. For example, the page '''How to Foo''', translated into Italian would be named '''How to Foo Italian'''. | In most cases you should name your page by adding the language to the end of the original title (assuming the article was originally written in English. For example, the page '''How to Foo''', translated into Italian would be named '''How to Foo Italian'''. | ||
===Right-to-Left languages=== | === Right-to-Left languages === | ||
For languages that are right-to-left just add '''[right_aligned]''' to the top of the page and it will align to the right, including bullets. | For languages that are right-to-left just add '''[right_aligned]''' to the top of the page and it will align to the right, including bullets. | ||
===How to categorize a translated page=== | === How to categorize a translated page === | ||
All translated pages should be initially categorized in the same category as the original. ('''How to Foo''' gets a ''<code>Category: How To</code>'' tag.) By doing this a developer browsing for example the How To category would see an alphabetized list of all translations of the How to Foo article. | All translated pages should be initially categorized in the same category as the original. ('''How to Foo''' gets a ''<code>Category: How To</code>'' tag.) By doing this a developer browsing for example the How To category would see an alphabetized list of all translations of the How to Foo article. | ||
After this initial categorization, feel free to add more — this is a collaborative wiki. If you want, for example, a top-level category that captures all articles translated into Kannada, or for the articles categorized in the ''<code>Category:How To</code>'' you can add a ''<code>Category:Kannada::How To</code>'' tag too, | After this initial categorization, feel free to add more — this is a collaborative wiki. If you want, for example, a top-level category that captures all articles translated into Kannada, or for the articles categorized in the ''<code>Category:How To</code>'' you can add a ''<code>Category:Kannada::How To</code>'' tag too, that's probably a great benefit for those looking for such content. | ||
==Collaboration== | == Collaboration == | ||
Wikis are meant for collaborative editing. To make it as easy as possible for everybody please follow some basic rules. | Wikis are meant for collaborative editing. To make it as easy as possible for everybody please follow some basic rules. | ||
* '''Discuss your pages in the | * '''Discuss your pages in the "Wiki forum":/forums/viewforum/16/''' | ||
* Write in an understandable, informative, but not too formal language. | * Write in an understandable, informative, but not too formal language. | ||
* Structure your pages with subheadings and a healthy amount of paragraphs for easier understanding and better reading. | * Structure your pages with subheadings and a healthy amount of paragraphs for easier understanding and better reading. | ||
* Explain acronyms, at least at first use. | * Explain acronyms, at least at first use. | ||
* Use meaningful but straight to the point page names. | * Use meaningful but straight to the point page names. | ||
* | * Don't mindlessly throw away other people's work. | ||
* Use [[Tagging]] to group pages by topic. | * Use [[Tagging]] to group pages by topic. | ||
==Syntax highlighting== | == Syntax highlighting == | ||
In the toolbar you will find a code tag (an "at" sign) to make code highlighted like this: | |||
<code> | |||
#include <QtGui> | |||
#include "window.h" | |||
int main(int argv, char **args) | |||
{ | |||
QApplication app(argv, args); | |||
Window window; | |||
window.show(); | |||
return app.exec(); | |||
} | |||
</code> | |||
Inline code can be tagged like this: | Inline code can be tagged like this: ‹code›someCode(here);‹/code› to look like this <code>someCode(here);</code> | ||
Qt classes are of course supported. | Qt classes are of course supported. | ||
==Category pages== | == Category pages == | ||
Whenever you create a new category for your page the wiki software will create a landing page for it. This page is editable just like any other page. Just click on the link displayed on your page and edit away. All pages within the respective category will be displayed on this page. Why not start it with an introduction to the topic? | Whenever you create a new category for your page the wiki software will create a landing page for it. This page is editable just like any other page. Just click on the link displayed on your page and edit away. All pages within the respective category will be displayed on this page. Why not start it with an introduction to the topic? | ||
==Need help? | == Need help? == | ||
Please, take a look at the "help forum":/forums/viewforum/16/ or our "FAQ (Qt DN FAQ)":/faq | |||
Latest revision as of 22:01, 28 March 2016
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
Начало
- Если у вас есть что рассказать о Qt, то Wiki это место, где вы можете поделиться этим. But restrict your articles to Qt related topics
- Пожалуйста, убедитесь, что страница, которую вы думаете создать еще не существует. Используйте поле поиска в правом верхнем углу страницы для этой цели.
- Если кто-то уже создал страницу на эту тему, то вы увидите ее в результатах поиска.
- Вы можете редактировать все содержимое на большинстве страниц. (стр. Синтаксис Wiki поможет с разметкой)
- Если нет страницы, которую вы хотите создать, то можно создать ее, нажав кнопку "Create new page".
- Используйте пробелы и подчеркивание для заголовков статей и категорий. — см. соответствующие темы на форуме в голосовании форума можно проголосовать.
- Не засоряйте историю страницы, тестируя разметку, используйте Playground вместо этого.
How to edit a page
The editor provides you with the most common functions collected in a kitchen sink. That should get you quite somewhere.
If you prefer to write wiki code directly you can have a look at this cheat sheet and practice your skills at Textism.com They provide a tool that turns Textile - the markup language our wikis use - into HTML for preview.
Please, use the preview option to check your edits before you save unless you are 120% sure that you never make mistakes.
C++ code will be automatically highlighted on wiki pages!
How to make your pages easy to use
Help fellow developers find the great insights you're sharing by following a few simple guidelines:
Write like you're coding
Good wikis, like good code, are easy to scan and maintain. Each article should cover one topic (much like a class). Each paragraph should contribute one aspect to the topic (like a function). If you change thoughts it helps to change paragraphs so you don't bury great insights where they're hard to find.
Use headers for scannability
Long articles are easier to read if you add some informative headers. Please use h1 level for your introduction and then h2 and h3 levels to outline your discussion. (The editor includes buttons for them.) Try to write your headers so they outline what you have to say all by themselves, because you can then …
Add a table of content
When readers find your article, they will scan the first page to figure out if it's what they're looking for. If your article is not much longer than one page, all you need to do is write it. If it's much longer than that, use a table of content to show the reader what's to come. Your opening paragraph plus table of content should be all the reader needs to know whether to click down or click away.
All you need to do is add this tag "["toc align_right="yes" depth="3"] (remove quotes surround first bracket) and the wiki engine will create the TOC for you. The tag can appear anywhere, but is helps maintainability if it appears at the beginning of your article.
Add Categories
Add category tags to insert a link to your article in the appropriate summary pages. By adding your article to existing categories you help readers find your content.
If you want to create a new category and summary page, just tag your article to a category that does not yet exist.
How to translate a page
If you translated a wiki page keep in mind that it has to be accessible from existing language versions. This is quite easy by adding or expanding the navigation at the top of the page. The navigation should follow this pattern: Language_of_the_page Language1 Language2 … side by side with their corresponding links.
For example in this page (remove the space between the brackets "[ [") the following is used:
'''English''' [ [WikiHilfe|Deutsch]] [ [WikiPomoc|Polski]]
In most cases you should name your page by adding the language to the end of the original title (assuming the article was originally written in English. For example, the page How to Foo, translated into Italian would be named How to Foo Italian.
Right-to-Left languages
For languages that are right-to-left just add [right_aligned] to the top of the page and it will align to the right, including bullets.
How to categorize a translated page
All translated pages should be initially categorized in the same category as the original. (How to Foo gets a
Category: How To
tag.) By doing this a developer browsing for example the How To category would see an alphabetized list of all translations of the How to Foo article. After this initial categorization, feel free to add more — this is a collaborative wiki. If you want, for example, a top-level category that captures all articles translated into Kannada, or for the articles categorized in the
Category:How To
you can add a
Category:Kannada::How To
tag too, that's probably a great benefit for those looking for such content.
Collaboration
Wikis are meant for collaborative editing. To make it as easy as possible for everybody please follow some basic rules.
- Discuss your pages in the "Wiki forum":/forums/viewforum/16/
- Write in an understandable, informative, but not too formal language.
- Structure your pages with subheadings and a healthy amount of paragraphs for easier understanding and better reading.
- Explain acronyms, at least at first use.
- Use meaningful but straight to the point page names.
- Don't mindlessly throw away other people's work.
- Use Tagging to group pages by topic.
Syntax highlighting
In the toolbar you will find a code tag (an "at" sign) to make code highlighted like this:
#include <QtGui>
#include "window.h"
int main(int argv, char **args)
{
QApplication app(argv, args);
Window window;
window.show();
return app.exec();
}
Inline code can be tagged like this: ‹code›someCode(here);‹/code› to look like this
someCode(here);
Qt classes are of course supported.
Category pages
Whenever you create a new category for your page the wiki software will create a landing page for it. This page is editable just like any other page. Just click on the link displayed on your page and edit away. All pages within the respective category will be displayed on this page. Why not start it with an introduction to the topic?
Need help?
Please, take a look at the "help forum":/forums/viewforum/16/ or our "FAQ (Qt DN FAQ)":/faq