From 8f2731905212f6e7eb2d9793ad20b8b448c54ccf Mon Sep 17 00:00:00 2001 From: Florian Merz Date: Thu, 11 Feb 2021 14:51:31 +0100 Subject: unslug tr: move --- files/tr/mdn/about/index.html | 138 +++++++ files/tr/mdn/at_ten/index.html | 36 ++ files/tr/mdn/community/index.html | 53 --- .../howto/create_and_edit_pages/index.html | 11 + .../editor_incelemesi_nasil_yapilir/index.html | 48 --- .../index.html | 11 - files/tr/mdn/editor/basics/index.html | 427 --------------------- files/tr/mdn/editor/index.html | 13 - files/tr/mdn/hakkinda/index.html | 138 ------- files/tr/mdn/kuma/index.html | 26 -- files/tr/mdn/kuma/server_charts/index.html | 63 --- .../troubleshooting_kumascript_errors/index.html | 75 ---- .../tools/kumascript/troubleshooting/index.html | 75 ++++ files/tr/mdn/tools/page_watching/index.html | 44 --- files/tr/mdn/yari/index.html | 26 ++ 15 files changed, 286 insertions(+), 898 deletions(-) create mode 100644 files/tr/mdn/about/index.html create mode 100644 files/tr/mdn/at_ten/index.html delete mode 100644 files/tr/mdn/community/index.html create mode 100644 files/tr/mdn/contribute/howto/create_and_edit_pages/index.html delete mode 100644 files/tr/mdn/contribute/howto/editor_incelemesi_nasil_yapilir/index.html delete mode 100644 files/tr/mdn/contribute/howto/sayfalar_nasil_olusturulur_duzenlenir/index.html delete mode 100644 files/tr/mdn/editor/basics/index.html delete mode 100644 files/tr/mdn/editor/index.html delete mode 100644 files/tr/mdn/hakkinda/index.html delete mode 100644 files/tr/mdn/kuma/index.html delete mode 100644 files/tr/mdn/kuma/server_charts/index.html delete mode 100644 files/tr/mdn/kuma/troubleshooting_kumascript_errors/index.html create mode 100644 files/tr/mdn/tools/kumascript/troubleshooting/index.html delete mode 100644 files/tr/mdn/tools/page_watching/index.html create mode 100644 files/tr/mdn/yari/index.html (limited to 'files/tr/mdn') diff --git a/files/tr/mdn/about/index.html b/files/tr/mdn/about/index.html new file mode 100644 index 0000000000..b3b9e67a31 --- /dev/null +++ b/files/tr/mdn/about/index.html @@ -0,0 +1,138 @@ +--- +title: MDN Web Docs Hakkında +slug: MDN/Hakkinda +tags: + - Dokümantasyon + - Lisanslar + - Telif Hakkı + - Topluluk +translation_of: MDN/About +--- +
{{MDNSidebar}}
+ +
{{IncludeSubNav("/en-US/docs/MDN")}}
+ +

MDN Web Docs (previously known as MDN — the Mozilla Developer Network) is an evolving learning platform for Web technologies and the software that powers the Web, including:

+ + + +

Hedefimiz

+ +

MDN's mission is simple: provide developers with the information they need to easily build projects on the open Web. If it's an open technology exposed to the Web, we want to document it.

+ +

We also provide documentation about Mozilla products and how to build and contribute to Mozilla projects.

+ +

If you're not sure whether a particular topic should be covered on MDN, read Does this belong on MDN?

+ +

Nasıl yardım edebilirsin

+ +

You don't need to be a professional coder or writer to help MDN! We have lots of ways you can help, from reviewing articles to be sure they make sense, to contributing text, to adding sample code. In fact, there are so many ways to help that we have a Getting Started page that helps you pick tasks to do based on your interests and how much time you have to spare!

+ +

You can also help by promoting MDN on your own blog or website.

+ +

MDN topluluğu

+ +

Our community is a global one. We have amazing contributors all around the world who work in lots of different languages. If you'd like to learn more about us, or if you need help with MDN, check out our discussion forum or IRC channel! You can also keep up with what we're up to by following our Twitter account, @MozDevNet. You can also send tweets our way if you see something wrong or if you'd like to offer feedback (or great big thank yous) to our writers and contributors.

+ +

Using MDN Web Docs content

+ +

MDN's content is available free of charge, and under open source licenses.

+ +

Telif hakları ve lisanslar

+ +

MDN's content is entirely available under various open source licenses. This section covers the types of content we provide and what licenses are in effect for each.

+ +

Documentation and articles

+ +

MDN wiki documents have been prepared with the contributions of authors from both inside and outside the Mozilla Foundation. Unless otherwise indicated, the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version.

+ +

When reusing MDN content, you need to ensure two things:

+ +
    +
  1. +

    Attribution is given to the original content.

    + +

    Please attribute "Mozilla Contributors" and include a hyperlink (online) or URL (in print) to the specific wiki page for the content being sourced. For example, to provide attribution for this article, you can write:

    + +
    +

    About MDN by Mozilla Contributors is licensed under CC-BY-SA 2.5.

    +
    + +

    Note that in the example, "Mozilla Contributors" links to the history of the cited page. See Best practices for attribution for further explanation.

    +
    2. +
  2. +

    Your reuse is published under the same license as the original content—CC-BY-SA v2.5 or any later version.

    +
    3. +
+ +

Code samples and snippets

+ +

Code samples added on or after August 20, 2010 are in the public domain (CC0). No licensing notice is necessary, but if you need one, you can use: "Any copyright is dedicated to the Public Domain. http://creativecommons.org/publicdomain/zero/1.0/".

+ +

Code samples added to this wiki before August 20, 2010 are available under the MIT license; you should insert the following attribution information into the MIT template: "© <date of last wiki page revision> <name of person who put it in the wiki>".

+ +

You can determine which license a code sample is available under by browsing through the article's history. To view the history:

+ +
    +
  1. Click the Edit in wiki button in the article header.  This takes you to the same article on the editable, wiki version of MDN Web Docs (but does not actually put the article in edit mode).  
    2. +
  2. Click the gear-shaped icon in the header of the wiki article, and choose History in the menu that appears.
    3. +
  3. Click View All, and then look for the most recent revision that occurred before August 20, 2010 (if any).
    4. +
  4. Click the date stamp of that revision to see the version of the article on that date.
    5. +
+ +

If the sample exists in the revision you selected, then it was added before the licensing changed and is available under the terms of the MIT license. If it is not there, or there are no revisions before August 20, 2010, then it was added after the change and is in the public domain.

+ +

Contributions

+ +

If you wish to contribute to this wiki, you must make your documentation available under the Attribution-ShareAlike license (or occasionally an alternative license already specified by the page you are editing), and your code samples available under Creative Commons CC-0 (a Public Domain dedication). Adding to this wiki means you agree that your contributions will be made available under those licenses.

+ +

Some older content was made available under a license other than those described above; these are indicated at the bottom of each page by way of an Alternate License Block.

+ +
+

No new pages may be created using alternate licenses.

+
+ +

Copyright for contributed materials remains with the author unless the author assigns it to someone else.

+ +

If you have any questions or concerns about anything discussed here, please contact the MDN administrators.

+ +

Logos, trademarks, service marks and wordmarks

+ +
+

The rights in the trademarks, logos, and service marks of the Mozilla Foundation, as well as the look and feel of this web site, are not licensed under the Creative Commons license, and to the extent they are works of authorship (like logos and graphic design), they are not included in the work that is licensed under those terms. If you use the text of documents, and wish to also use any of these rights, or if you have any other questions about complying with our licensing terms for this collection, you should contact the Mozilla Foundation here: licensing@mozilla.org.

+ +

Linking to MDN

+ +

See this article for guidance on linking to MDN for best practices when linking.

+ +

Downloading content

+ +

Single pages

+ +

You can retrieve the content of a single page on MDN by adding URL parameters to specify what format you want.

+ +

Third-party tools

+ +

You can view MDN content via third-party tools like Dash (for macOS) and Zeal (for Linux and Windows).

+ +

Kapeli also publishes offline MDN docs covering HTML, CSS, JavaScript, SVG, and XSLT.

+ +

Reporting problems with MDN Web Docs

+ +

See How to report a problem on MDN.

+ +

History of MDN Web Docs

+ +

The MDN Web Docs (previously Mozilla Developer Network (MDN), previously Mozilla Developer Center (MDC), a.k.a. Devmo) project started in early 2005, when the Mozilla Foundation obtained a license from AOL to use the original Netscape DevEdge content. The DevEdge content was mined for still-useful material, which was then migrated by volunteers into this wiki so it would be easier to update and maintain.

+ +

The name was changed to MDN Web Docs in June 2017. See The Future of MDN: A Focus on Web Docs for the rationale behind this decision.

+ +

You can find more history of MDN on our 10th anniversary celebration page, including an oral history by some of the people who were involved.

+ +

Mozilla Hakkında

+ +

Whether you want to learn more about who we are, how to be a part of Mozilla or just where to find us, you've come to the right place. To find out what drives us and makes us different, please visit our mission page.

diff --git a/files/tr/mdn/at_ten/index.html b/files/tr/mdn/at_ten/index.html new file mode 100644 index 0000000000..ee5981fb1d --- /dev/null +++ b/files/tr/mdn/at_ten/index.html @@ -0,0 +1,36 @@ +--- +title: MDN 10'unda +slug: MDN_onunda +translation_of: MDN_at_ten +--- +
İnternetinizin 10 yıldır belgelenmesini kutlayın.
+ +
+
+

MDN'in Tarihi

+ +

2005'in başında, idealistlerden oluşan küçük bir takım, tüm Web geliştiriciler için yeni, ücretsiz ve topluluk yapımı bir online kaynak oluşturmak için yola çıktı. Dahice ama sıradışı fikirleri günümüzün Mozilla Developer Network'ü haline geldi—Tüm açık kaynak web projeleri için ham madde. On yıldan sonra, Global topluluğumuz her zamankinden daha büyük,ve  hala beraber dökümantasyon, web teknolojileri için örnek kod ve öğrenme kaynakları, CSS, HTML, JavaScript ve özgür Web'i güçlü kılan herşeyi oluşturmaya devam ediyoruz.

+ +

Daha Fazla about the history

+ +

MDN'e katkı

+ +

On yıldır, MDN topluluğu özgür Web'i belgeliyor. Yazım hatalarını düzeltmeden yep yeni bir API'nin tüm takımını yazmaya, herkes sunmak için bir şeye sahip ve no contribution is too large or too small. Mozillians topluluğumuzun seçkin üyeleri tarafından 90,000 üzerinde yazılmış veya tercüme edilmiş sayfaya sahibiz. Sen de onlardan biri olabilirsin.

+ +

Daha fazla about contributing

+ +

 

+ +

 

+
+ +
{{TenthCampaignQuote}}
+ + + +
    +
  1. MDN 10'unda
    2. +
  2. MDN'in tarihi
    3. +
  3. MDN'e katkı
    4. +
+
diff --git a/files/tr/mdn/community/index.html b/files/tr/mdn/community/index.html deleted file mode 100644 index 76cdfb75bf..0000000000 --- a/files/tr/mdn/community/index.html +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Join the MDN community -slug: MDN/Community -tags: - - MDN Meta - - Rehber - - Topluluk -translation_of: MDN/Community ---- -
{{MDNSidebar}}
- -
{{IncludeSubnav("/en-US/docs/MDN")}}
- -
-

MDN web dökümanları vikiden daha fazlasıdır: Açık Web teknolojileri hakkında dökümanlar oluşturulan , birlikte çalışan yazılım geliştiricilerinden oluşan bir topluluktur. 

-
- -

MDN'e katkıda bulunmanızdan hoşnut oluruz, bunun yanında MDN topluluğuna katılmanız bizi daha da mutlu eder. Aşağıda nasıl bağlanacağınza dair üç adım verilmiştir.

- -
    -
  1. MDN üyeliği oluşturun.
    2. -
  2. Tartışmalara katılın.
    3. -
  3. Ne olduğunu takip edin.
    4. -
- -

Topluluk nasıl çalışır

- -

Sonraki paragraflar MDN topluluğunun nasıl çalıştığını açıklamaktadır..

- -
-
-
-
Topluluk Görevleri
-
Çeşitli sorumluları olan çeştili roller anlatılmaktadır.
-
Döküman Turları 
-
Döküman turlarının organizyonu ve çeşitli öneriler, kısayollar paylaşılmaktadır.
-
Ne olduğunu Takip Edin
-
MDN sizi   Mozilla Developer Network Topluluğu taradından oluşturulur.  Burada nasıl bilgi paylaşılacağı anlatılmaktadır.
-
- -
-
-
- -
-
-
MDN Topluluk Tartışmaları
-
MDN'deki "işler" MDN web sitesinde görülür ancak topluluk tartışmalara (Eşzamanlı) ve Anlık Mesajlaşma toplantıları ile işleyişe katkıda bulunabilir.
-
Topluluk İçinde Çalışmak
-
Katkı hakkındaki en önemli konulardan biri MDN topluluğu ile nasıl çalışılacağını bilmektir. Bu makale çeşitli öneriler ile yazarlar ve geliştiriciler arasında bağlantı  kurmada yardımcı olmayı amaçlamaktadır.
-
-
-
diff --git a/files/tr/mdn/contribute/howto/create_and_edit_pages/index.html b/files/tr/mdn/contribute/howto/create_and_edit_pages/index.html new file mode 100644 index 0000000000..7986219ff5 --- /dev/null +++ b/files/tr/mdn/contribute/howto/create_and_edit_pages/index.html @@ -0,0 +1,11 @@ +--- +title: Sayfalar nasıl oluşturulur ve düzenlenir +slug: MDN/Contribute/Howto/Sayfalar_nasil_olusturulur_duzenlenir +tags: + - Başlangıç + - Giriş + - Klavuz + - Nasıl +translation_of: MDN/Contribute/Howto/Create_and_edit_pages +--- +
bilgisayar tamircisi
diff --git a/files/tr/mdn/contribute/howto/editor_incelemesi_nasil_yapilir/index.html b/files/tr/mdn/contribute/howto/editor_incelemesi_nasil_yapilir/index.html deleted file mode 100644 index 026332438c..0000000000 --- a/files/tr/mdn/contribute/howto/editor_incelemesi_nasil_yapilir/index.html +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Bir editör incelemesi nasıl yapılır? -slug: MDN/Contribute/Howto/Editor_incelemesi_nasil_yapilir -translation_of: MDN/Contribute/Howto/Do_an_editorial_review ---- -
{{MDNSidebar}}
{{IncludeSubnav("/en-US/docs/MDN")}}
- -

Editör incelemeleri bir yazıda yazım hataları, imla hataları, dil bilgisi, kullanım veya metinsel hataları düzeltmekten ibarettir. Katkıda bulunanların tamamı dil uzmanları değildir, ancak bilgilerine bakılmaksızın, kopyalama, düzenleme ve son okuma/düzeltmeye ihtiyaç duyan son derece yararlı makale yazmış olacaklardır. Bu bir editör incelemesinde yapılır.

- -

Bu makale, MDN'nin içeriğinin doğru olduğundan emin olmak için bir editör incelemesinin nasıl yapılacağını açıklar.

- -
-
Görev nedir?
-
Bir "editör incelemesi gerektiriyor" olarak işaretlenmiş makalelerin kopyalama-düzenleme ve son okuması/düzenlemesi.
-
Nerede yapılması gerekiyor?
-
Bir "editör incelemesi gerektiriyor" olarak işaretlenmiş makalelerde yapılması gerekiyor.
-
Görevi yapmak için bilmeniz gereken şey nedir?
-
İyi İngilizce dil bilgisi ve yazım becerilerine sahip olmanız gerekir. Bir editör incelemesi, dil bilgisi, yazım denetimi ve ifadelerin doğru ve mantıklı olmasını sağlamak ve MDN yazım sitili rehberinin izlenmesiyle ilgilidir.
-
Bunu yapmanın adımları nelerdir?
-
-
    -
  1. İncelenecek bir makale seçin: -
      -
    1. Editörlük incelemesine ihtiyaç duyan makaleler listesine gidin. Bu liste, editör incelemesinin talep edildiği tüm sayfaları listeler.
      2. -
    2. İngilizce başlığına sahip ve sayfa yolu Template ile başlamayan bir sayfa seçin. (Template: sayfalar MDN makro kodu içermektedir.)
      3. -
    3. Sayfayı yüklemek için makale bağlantısını tıklayın.
      4. -
    -
    2. -
  2.  Yazım hatalarını, dil bilgisini veya kullanım hatalarını yakından takip ederek makaleyi okuyun. Seçtiğiniz ilk sayfa sizin için uygun değilse farklı bir sayfaya geçmekten çekinmeyin..
    3. -
  3. Herhangi bir hata yoksa makaleyi gözden geçirilmiş olarak işaretlemek için düzenlemenize gerek yoktur. Sayfanın sol kenar çubuğundaki "hızlı inceleme" kutusunu bulun:
    - Screenshot of the editorial review request sidebar box
    4. -
  4. Editöryel(Editorial) kutusundaki seçimi kaldırın ve Kaydet(Save) düğmesine tıklayın.
    5. -
  5. Düzeltilmesi gereken hatalar bulursanız: -
      -
    1. Sayfanın üst kısmındaki Düzenle(Edit) düğmesini tıklayın; Bu sizi MDN editörüne getiriyor.
      2. -
    2. Bulduğunuz yazım hatalarını, yazım kurallarını, dilbilgisi veya kullanım hatalarını düzeltin. Her şeyi düzeltmek zorunda değilsiniz, ancak tüm makalenin tam bir incelemesini yaptığınızı makul bir derecede eminseniz, editörlük inceleme talebini yerine getirdiğinizden emin olun..
      3. -
    3. Makalenin en altında Revizyon Yorumu (Revision Comment) düğmesine basın; açıklama kısmına 'Editöryel inceleme: sabit yazım hataları, dilbilgisi ve yazım denetimi' gibi birşey yazabilirsiniz. Bu diğer katkıda bulunanlar ve site editorleri tarafından sayfada ne değişti neden değiştiyi bilmeleri içindir.
      4. -
    4. İnceleme Gerekli mi(Review Needed)? Editöryel(Editorial) kutusunun seçimini kaldırın. Bu, sayfanın Revizyon Yorumu(Revision Comment) bölümünün hemen altında yer alır.
      5. -
    5. Yayınla (Publish) düğmesine tıklayın.
      6. -
    -
    6. -
- -
-

Değişiklikleriniz kaydedildikten hemen sonra görünmeyebilir; Sayfa işlenirken ve kaydedilirken bir gecikme olabilir.

-
-
-
diff --git a/files/tr/mdn/contribute/howto/sayfalar_nasil_olusturulur_duzenlenir/index.html b/files/tr/mdn/contribute/howto/sayfalar_nasil_olusturulur_duzenlenir/index.html deleted file mode 100644 index 7986219ff5..0000000000 --- a/files/tr/mdn/contribute/howto/sayfalar_nasil_olusturulur_duzenlenir/index.html +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Sayfalar nasıl oluşturulur ve düzenlenir -slug: MDN/Contribute/Howto/Sayfalar_nasil_olusturulur_duzenlenir -tags: - - Başlangıç - - Giriş - - Klavuz - - Nasıl -translation_of: MDN/Contribute/Howto/Create_and_edit_pages ---- -
bilgisayar tamircisi
diff --git a/files/tr/mdn/editor/basics/index.html b/files/tr/mdn/editor/basics/index.html deleted file mode 100644 index cf3f1475a1..0000000000 --- a/files/tr/mdn/editor/basics/index.html +++ /dev/null @@ -1,427 +0,0 @@ ---- -title: MDN editor basics -slug: MDN/Editor/Basics -translation_of: MDN/Editor/Basics ---- -
{{MDNSidebar}}

Editing content on MDN is easy; you can use the built-in WYSIWYG editor to create, edit, and improve articles and other pages almost anywhere on the site. The editor window, shown below, is comprised of eight key boxes. This section will provide information about each section so you know how to use our entire editing environment.

-
-

Note: We're constantly working on improvements to MDN, so there will be times when this documentation or the screen shots below may be slightly out-of-date. We'll periodically update this documentation, though, to avoid it being unusably behind.

-
-

-

Page controls

-

The page controls area offers buttons affecting the page as a whole:

-
-
- Save and keep editing
-
- Saves the page without closing the editor; this lets you periodically save your work, creating an entry in the page history that you can revert to if you need to, or in case you need to stop working and come back to it later. This option is not available when creating new pages. See {{anch("The revision comment box")}} to learn how to include a revision comment on your saved article.
-
- Save changes
-
- Saves the page and closes the editor, returning you to view the page in standard browsing mode. See {{anch("The revision comment box")}} to learn how to include a revision comment on your saved article.
-
- Preview changes
-
- Opens a new tab or window showing the page as it exists in your editor, rendered as if you were browsing to it. This includes executing any macros you use in-content. Your work is not saved when you use this option. This lets you check to be sure you haven't made any errors in your macro syntax or other formatting that may prevent the page from rendering correctly.
-
- Discard changes
-
- Cancels your edit, disposing of any changes you've made without saving them. You're returned to the page in standard browsing mode.
-
-

The page info box

-

The page info box contains information about the page, but also can be expanded to offer additional page controls. By default, it displays the page's title and the date and time at which a local draft was saved; the local draft, stored on your computer, is used as a backup in case you accidentally navigate away from the editor or your browser crashes.

-

You can click the "Edit Page Title and Properties" link to switch to a view offering additional page controls. This view looks like this:

-

-

This view allows you to change the page's display title and the depth of the page's table of contents. The display title is the title shown in the browser's title bar (or tab bar) and as the title of the page at the top of the article and in the breadcrumb bar, as appropriate. It doesn't affect the page's URL.

-
-

Note: It's worth noting that we prefer short URLs and descriptive titles; for example, the article about the Kuma API has the title "The Kuma API" but its URL slug (the part after the site's root) is Project:MDN/Kuma/API, where "API" represents this page.

-
-

The TOC (table of contents) level lets you specify how deeply into the article's heading levels the table of contents automatically displayed on the page should go. By default, heading levels {{HTMLElement("h2")}} through {{HTMLElement("h4")}} are included in the TOC, so that the TOC has a three-level depth. However, you can set this to any of those, as well as "No TOC" (to not display a TOC at all, such as on landing pages) or to show all levels in the TOC.

-

As is the case with all changes you might make, changes in the page info box do not take effect unless you save the page.

-

The toolbar

-

The editor's toolbar offers features that let you adjust the appearance and flow of the article as you work. There are two rows of buttons (more if the width of your window is narrow enough that they wrap, but generally two) and a third row that shows the hierarchy of HTML elements leading up to where you are. In the screenshot below, for example, you're writing inside a top-level {{HTMLElement("p")}} block.

-

-

The toolbar's buttons are divided into seven groups. Let's look at each; we will examine the buttons in each group in order left-to-right.

-

Document options

-

The document options box provides options for document-level manipulations:

-

 

-
-
- Source mode toggle
-
- The source mode toggle button lets you toggle between editing using the WYSIWYG interface and in raw HTML source mode. We strongly request that you try to avoid using source mode, as it's very easy to wind up with content that doesn't match our style guide or, worse, doesn't work right at all. Currently, though, the editor has some quirks that make it impossible to do certain things without resorting to source mode.
-
- Save and keep editing
-
- A duplicate for the main "Save and keep editing" button.
-
- Save and exit
-
- Just like the main "Save changes" button.
-
- Paste as plain text
-
- Opens a dialog into which you can paste text; the text has all styling stripped from it so that you don't inadvertently introduce unwanted styles into the site content. Once you've pasted your text, you can (optionally) make changes, then click a button to insert it into the article you're working on.
-
-
-

Note: When pasting content into MDN, please be aware that if pasting styled content (including, for example, syntax highlighting in code being copied from another site) that you may be bringing along unwanted and unneeded additional styles or classes. Please be careful not to do this; if necessary, review your edit in source mode to remove these unnecessary styles and classes (or check it before pasting, or use the "Paste as plain text" option instead).

-
-
-
- Paste from Word
-
- On Windows, lets you paste text from Microsoft Word and have it adjusted to work reasonably well in MDN's wiki. We prefer for you to not use this (the results will work but are not typically style guide compliant), but it's there for a few teams that need it.
-
- Check spelling
-
- Starts the spell checker.
-
- Spell check as you type
-
- Presents a submenu that lets you control and configure the as-you-type spell checker.
-
- Find
-
- Opens the Find panel in "Find" mode, which lets you search your document for a specified string.
-
- Replace
-
- Opens the Find panel in "Find and replace" mode, allowing you to find strings and replace them with new ones.
-
-

It's worth noting that the Find and Replace buttons both take you to the same dialog box, which offers several configurable options for finding and optionally replacing text.

-

Block-level options

-

These buttons provide options affecting or creating blocks in your article.

-
-
- Insert/remove bulleted list
-
- Creates or removes a bulleted list from your article. Once you're working in a bulleted list, each time you press return, you will start a new bullet. The tab key can be used to indent a level, and shift-tab will outdent a level. Pressing return on an empty bullet will exit bullet list mode. Right-clicking on the list lets you choose to edit the list's properties (specifically, the shapes of the bullets).
-
- Insert/remove numbered list
-
- Creates or removes a numbered list from your article. Once you're working in a numbered list, each time you press return, you will start a new bullet. The tab key can be used to indent a level, and shift-tab will outdent a level. Pressing return on an empty bullet will exit numbered list mode. Right-clicking the list offers the option to open the properties dialog for the list; the properties include the style of the numbers (numbers, letters, Roman numerals, etc, and what number to start with).
-
- Definition list
-
- Creates a new definition list. Definition lists consist of a series of titles and definitions (this list you're reading right now is an example).
-
- Definition title
-
- Creates a new title in a definition list. If you're not already editing a definition list, a new one is created for you. Pressing return after entering a definition title automatically starts you editing a definition description.
-
- Definition description
-
- Creates a new description in a definition list. Pressing return on a description line automatically starts a new title. Pressing return twice will exit definition list mode.
-
- Decrease indent
-
- Shifts the indentation level to the left once; this is the same as shift-tab while in a list.
-
- Increase indent
-
- Shifts the indentation level to the right once; this is the same as tab while in a list.
-
- Blockquote
-
- Inserts a blockquote. Please do not use this. Blockquotes are not part of our standard style guide, and this button will be removed in the near future.
-
- Image
-
- Inserts a new image into the article. See {{anch("Adding images to an article")}} below for details on how to use this option.
-
- Table
-
- Inserts a table into the article. See {{anch("Working with tables")}} for more information on tables in articles.
-
- Text color
-
- Lets you set the text foreground color. Please do not use this. We will switch to using CSS styles for all coloring soon.
-
- Background color
-
- Lets you set the text background color. Please do not use this. We will switch to using CSS styles for all coloring soon.
-
- Text direction left-to-right
-
- Sets LTR as the current text typing direction. Used only when covering localization/internationalization topics.
-
- Text direction right-to-left
-
- Sets RTL as the current text typing direction. Used only when covering localization/internationalization topics.
-
-

Maximize

-

This is an odd box, in that it consists of just one button: Maximize. This button causes the editor interface (that is, the toolbar and the edit box) to take over your entire browser window, giving you as much space as possible to write.

-

Headings

-

The heading buttons let you insert a heading. Click one of these buttons to create a new heading at the corresponding depth. By default, H2 through H4 are included in the table of contents, but you can change this, as described in {{anch("The page info box")}}.

-

Formatting styles

-

The next box is a drop-down menu offering a selection of special formatting options. These are:

-
-
- None
-
- Removes all styling from the current block.
-
- Note box
-
- Creates a note box, as seen below. You should always start a note box with "Note:" in bold letters.
-
-
-

Note: This is a note box.

-
-
-
- Warning box
-
- Creates a warning box, as seen below. These should always begin with "Warning:" in bold letters.
-
-
-

Warning: This is a warning box.

-
-
foo = bar()
-
-
- Callout box
-
- Creates a new callout box. We are phasing this kind of box out in favor of a new design, so it shouldn't be used for new content.
-
- Two columns
-
- Makes the selected text or the current block two columns instead of one, on browsers that support it.
-
- Three columns
-
- Makes the selected text or the current block three columns instead of one, on browsers that support it.
-
- Syntax box
-
- Creates a syntax box, such as the one shown below. You need to use the "PRE" button as well, to create a {{HTMLElement("pre")}} block inside it. You probably won't see the yellow box until you do.
-
- Right sidebar
-
-
- Special note
- This is a right sidebar.
- Creates a light grey sidebar that floats to the right of content. You may enter small amounts of text in these boxes to draw special attention to them.
-
- SEO summary
-
- This special style is used to indicate a sentence or two that should be used as the article's summary for SEO purposes. It's also used by macros that automatically construct landing pages. If you don't specify this, MDN automatically uses the first paragraph of your article, but sometimes that's not the optimal text (or it's too much text), so this lets you override that.
-
-

Code samples and redirects

-

These buttons are mostly used for providing preformatted text (usually code samples), but our "insert redirect" button is, for some reason, here too.

-
-
- PRE
-
- Inserts a {{HTMLElement("pre")}} (preformatted text) block, or turns the current block into one. All code samples or examples of text output to a terminal should be in one of these blocks.
-
- Syntax highlighter
-
- The syntax highlighter lets you choose a language for which to apply syntax highlighting to the{{HTMLElement("pre")}} (preformatted text) block; if you're not already in such a block, this will create one for you. Simply choose the language and you're good to go.
-
- Insert code sample template
-
- This button is used by the live sample system to help you quickly insert a new live sample. You don't need to use it, but it's there for convenience. See {{anch("Using the live sample system")}} for details on using this and other live sample features.
-
- Insert code sample iframe
-
- Inserts an {{HTMLElement("iframe")}} into the document, displaying a given live sample. See {{anch("Using the live sample system")}} for details on using this and other live sample features.
-
- Create a redirect
-
- Inserts a redirect. See {{anch("Creating redirects")}} for further information.
-
- -

The final group of toolbar buttons includes options for creating and maintaining links and anchors, as well as for applying inline styles to content.

-
-
- Link
-
- Creates a new link. This button opens the link editor dialog, which is covered under {{anch("Creating and editing links")}} below.
-
- Unlink
-
- Removes the link at the insertion point.
-
- Anchor
-
- Creates an anchor at the insertion point.
-
- Bold
-
- Toggles boldface text mode.
-
- Italic
-
- Toggles italic text mode.
-
- Underline
-
- Toggles underlined text mode.
-
- Code
-
- Toggles {{HTMLElement("code")}} mode. This is used for inline presentation of variable names, function names, object names, filenames, and so forth.
-
- Strike through
-
- Toggles strikethrough mode.
-
- Superscript
-
- Toggles superscript mode. Please note that we don't use footnotes on MDN, so you should rarely if ever need this button.
-
- Remove format
-
- Removes the current formatting from the selection.
-
- Align left
-
- Makes the current block left-aligned. Please do not use this. We will be using CSS styles for all alignment tasks starting very soon.
-
- Center
-
- Centers the current block. Please do not use this. We will be using CSS styles for all alignment tasks starting very soon.
-
- Align right
-
- Makes the current block right-aligned. Please do not use this. We will be using CSS styles for all alignment tasks starting very soon.
-
-

The edit box

-

The edit box is, of course, where you actually do your writing. Right-clicking in the edito box will offer appropriate additional options depending on the context of your click; clicking in a table will offer table-related options and clicking in a list will offer list-related options, for example.

-

The revision comment box

-

After you've made your changes, it's strongly recommended you add a comment to your revision. This is displayed in the revision history for the page, as well as on the Revision Dashboard. It helps to explain or justify your changes to others that may review your work later. To add a revision comment, simply type the note into the revision comment box before clicking either of the save buttons at the top of the page.

-
-

Note: We know that the revision comment box being so far away from the save buttons doesn't make any sense. We're working on design changes that will fix that.

-
-

The tags box

-

Page tags help categorize and organize information, and help us identify pages that need special attention. Tags are also used to mark pages that are obsolete and may need to be deprecated or even deleted. It's incredibly useful to have good, clean tags on pages, so be sure to have good tags on articles you contribute to.

-

The tag box is near the bottom of the editor page, and looks like this:

-

The tag editing box showing three tags.

-

Adding a tag

-

To add a new tag, simply click in the box and start typing:

-

Screen thot: the tag box after typing a new tag but before pressing Enter.

-

Here we see the three already existing tags (as button-like objects) and our new tag as unadorned text. When we press Enter or Tab key (or comma), the new tag is committed to the list, and the list looks like this:

-

Screen shot: the tag box with our new tag in place.

-

For a list of recommended tags, as well as a usage guide for specific tags, please see MDN tagging standards.

-

Removing a tag

-

There are two ways to remove a tag: you can click on the "x" icon next to its name in its button, or you can click to its right in the editor box and press the delete key on your keyboard.

-

Committing your changes

-

Your changes are not saved unless you click one of the save buttons at the top of the editor window. Scroll back to the top of the window if you don't see the buttons, then click one of the two green save buttons. Now your change has been committed.

-

The reviews box

-

MDN uses reviews to try to monitor and improve the quality of its content. This works by setting a flag on an article indicating that a review is needed. You can learn more about technical reviews and editorial review in the How to guides.

-

To request a review on the article you've worked on, simply toggle on the checkbox next to the type of review that's needed. Technical reviews should be requested any time you make changes to the explanation of how something technical works, while editorial reviews are a good idea when you've made changes and would like someone to review your writing and style choices.

-

Be sure to click one of the save buttons after making your selections, to commit your review request.

-

The attachments box

-

The attachments box lets you upload files to MDN for use in MDN content, as well as see what files are being used by the current document.

-
-

Note: Due to a quirk in our current implementation, files are not associated with pages unless they're actually used in the page. So if you upload an attachment and don't make use of it before you save the article, it will not appear on the attachments list. So be sure to link to it or embed the image right away.

-
-

To add an attachment to the page, simply click the "Attach Files" button; this expands the attachment box to look like this:

-

-

As you see, there's a table that lets you select a file to upload, then give it a title and, optionally, a description and an additional comment. The title is mandatory, and should describe the file so its usage context is understandable. Once the fields are filled out and you've selected your file, click the "Upload" button to send it to MDN.

-
-

Note: Only a select few types of files are permitted as attachments on MDN: GIF, JPEG, PNG, SVG, and HTML. Photoshop images are permitted but should be avoided except in very specific cases. Any other file types will not be allowed by the upload form.

-
-

Feel free to open this page in the editor and look at its attachment list at the bottom to get a feel for it.

-

Once a file has been attached, it will appear (by its title, as you specified in the form) in the image properties dialog box when using images in your article. See {{anch("Adding images to an article")}} for details on this interface. To link to other types of files, copy the URL from the attachments box and use that as your link target when adding links to the page using the link button in the toolbar.

-

Keyboard shortcuts

-

There are a number of convenient keyboard shortcuts available to help you avoid taking your hands off the keyboard while you work.  The shortcuts are listed for Windows and Linux; on Mac, instead of using the Control key, you can use the Command key.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ShortcutDescription
Ctrl-ASelect all
Ctrl-CCopy to clipboard
Ctrl-VPaste from clipboard
Ctrl-XCut
Ctrl-ZUndo
Ctrl-YRedo
Ctrl-KOpen link editor
Ctrl-BBold
Ctrl-IItalic
Ctrl-OToggle <code> style.
Ctrl-Shift-OToggle source view mode.
Ctrl-PToggles the <pre> style on the current block.
Ctrl-UUnderline
Ctrl-SSave changes and close the editor
Ctrl-Shift-SSave changes without closing the editor
Ctrl-2 through Ctrl-6Select header level 2-6
Ctrl-Shift-LToggles between bulleted list, numbered list, and paragraph format
TabIncreases indent level if in indent mode, otherwise inserts two spaces as a tab.  Inside tables, this jumps to the next cell, or inserts a new row if there is no next cell.  If the cursor is currently in the page title or in a header, the cursor jumps to the next paragraph.
Shift-TabDecreases indent level if in indent mode.  Inside tables, this jumps to the previous cell, or inserts a new row if there is no previous cell.  If the cursor is currently in the page title or in a header, the cursor jumps to the next paragraph.
Shift-SpaceInserts a non-breaking space (&nbsp;)
Shift-Enter -

Exits out of the current block.  For example, if you're currently editing a <pre> block, shift-Enter exits the block, putting you back in the body of the article.

-
-

Note: Not currently implemented; see {{bug(780055)}}.

-
-
- diff --git a/files/tr/mdn/editor/index.html b/files/tr/mdn/editor/index.html deleted file mode 100644 index 99c8d58ea1..0000000000 --- a/files/tr/mdn/editor/index.html +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: MDN Düzenleyici Rehberi -slug: MDN/Editor -tags: - - Landing - - MDN - - NeedsTranslation - - TopicStub -translation_of: MDN/Editor ---- -

Sayfada düzenleme uygulaması MDN Web dökümanları wiki sayfası, yeni içerik sağlamak için kolaylık sağlar. Bu rehber bu düzenleyiciyi nasıl kullanıp üretim verimliliğinizi nasıl arttıracağınızı gösterecek. Lütfen Mozilla Sözleşmesini okuyun herhangi bir düzenleme yapmadan evvel.

- -

MDN stil rehberi biçimlendirme ve içeriğin stili konusunda bilgilere sahiptir. Tercih edilen dilbilgisi ve yazım kuralları dahil.

diff --git a/files/tr/mdn/hakkinda/index.html b/files/tr/mdn/hakkinda/index.html deleted file mode 100644 index b3b9e67a31..0000000000 --- a/files/tr/mdn/hakkinda/index.html +++ /dev/null @@ -1,138 +0,0 @@ ---- -title: MDN Web Docs Hakkında -slug: MDN/Hakkinda -tags: - - Dokümantasyon - - Lisanslar - - Telif Hakkı - - Topluluk -translation_of: MDN/About ---- -
{{MDNSidebar}}
- -
{{IncludeSubNav("/en-US/docs/MDN")}}
- -

MDN Web Docs (previously known as MDN — the Mozilla Developer Network) is an evolving learning platform for Web technologies and the software that powers the Web, including:

- - - -

Hedefimiz

- -

MDN's mission is simple: provide developers with the information they need to easily build projects on the open Web. If it's an open technology exposed to the Web, we want to document it.

- -

We also provide documentation about Mozilla products and how to build and contribute to Mozilla projects.

- -

If you're not sure whether a particular topic should be covered on MDN, read Does this belong on MDN?

- -

Nasıl yardım edebilirsin

- -

You don't need to be a professional coder or writer to help MDN! We have lots of ways you can help, from reviewing articles to be sure they make sense, to contributing text, to adding sample code. In fact, there are so many ways to help that we have a Getting Started page that helps you pick tasks to do based on your interests and how much time you have to spare!

- -

You can also help by promoting MDN on your own blog or website.

- -

MDN topluluğu

- -

Our community is a global one. We have amazing contributors all around the world who work in lots of different languages. If you'd like to learn more about us, or if you need help with MDN, check out our discussion forum or IRC channel! You can also keep up with what we're up to by following our Twitter account, @MozDevNet. You can also send tweets our way if you see something wrong or if you'd like to offer feedback (or great big thank yous) to our writers and contributors.

- -

Using MDN Web Docs content

- -

MDN's content is available free of charge, and under open source licenses.

- -

Telif hakları ve lisanslar

- -

MDN's content is entirely available under various open source licenses. This section covers the types of content we provide and what licenses are in effect for each.

- -

Documentation and articles

- -

MDN wiki documents have been prepared with the contributions of authors from both inside and outside the Mozilla Foundation. Unless otherwise indicated, the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version.

- -

When reusing MDN content, you need to ensure two things:

- -
    -
  1. -

    Attribution is given to the original content.

    - -

    Please attribute "Mozilla Contributors" and include a hyperlink (online) or URL (in print) to the specific wiki page for the content being sourced. For example, to provide attribution for this article, you can write:

    - -
    -

    About MDN by Mozilla Contributors is licensed under CC-BY-SA 2.5.

    -
    - -

    Note that in the example, "Mozilla Contributors" links to the history of the cited page. See Best practices for attribution for further explanation.

    -
    2. -
  2. -

    Your reuse is published under the same license as the original content—CC-BY-SA v2.5 or any later version.

    -
    3. -
- -

Code samples and snippets

- -

Code samples added on or after August 20, 2010 are in the public domain (CC0). No licensing notice is necessary, but if you need one, you can use: "Any copyright is dedicated to the Public Domain. http://creativecommons.org/publicdomain/zero/1.0/".

- -

Code samples added to this wiki before August 20, 2010 are available under the MIT license; you should insert the following attribution information into the MIT template: "© <date of last wiki page revision> <name of person who put it in the wiki>".

- -

You can determine which license a code sample is available under by browsing through the article's history. To view the history:

- -
    -
  1. Click the Edit in wiki button in the article header.  This takes you to the same article on the editable, wiki version of MDN Web Docs (but does not actually put the article in edit mode).  
    2. -
  2. Click the gear-shaped icon in the header of the wiki article, and choose History in the menu that appears.
    3. -
  3. Click View All, and then look for the most recent revision that occurred before August 20, 2010 (if any).
    4. -
  4. Click the date stamp of that revision to see the version of the article on that date.
    5. -
- -

If the sample exists in the revision you selected, then it was added before the licensing changed and is available under the terms of the MIT license. If it is not there, or there are no revisions before August 20, 2010, then it was added after the change and is in the public domain.

- -

Contributions

- -

If you wish to contribute to this wiki, you must make your documentation available under the Attribution-ShareAlike license (or occasionally an alternative license already specified by the page you are editing), and your code samples available under Creative Commons CC-0 (a Public Domain dedication). Adding to this wiki means you agree that your contributions will be made available under those licenses.

- -

Some older content was made available under a license other than those described above; these are indicated at the bottom of each page by way of an Alternate License Block.

- -
-

No new pages may be created using alternate licenses.

-
- -

Copyright for contributed materials remains with the author unless the author assigns it to someone else.

- -

If you have any questions or concerns about anything discussed here, please contact the MDN administrators.

- -

Logos, trademarks, service marks and wordmarks

- -
-

The rights in the trademarks, logos, and service marks of the Mozilla Foundation, as well as the look and feel of this web site, are not licensed under the Creative Commons license, and to the extent they are works of authorship (like logos and graphic design), they are not included in the work that is licensed under those terms. If you use the text of documents, and wish to also use any of these rights, or if you have any other questions about complying with our licensing terms for this collection, you should contact the Mozilla Foundation here: licensing@mozilla.org.

- -

Linking to MDN

- -

See this article for guidance on linking to MDN for best practices when linking.

- -

Downloading content

- -

Single pages

- -

You can retrieve the content of a single page on MDN by adding URL parameters to specify what format you want.

- -

Third-party tools

- -

You can view MDN content via third-party tools like Dash (for macOS) and Zeal (for Linux and Windows).

- -

Kapeli also publishes offline MDN docs covering HTML, CSS, JavaScript, SVG, and XSLT.

- -

Reporting problems with MDN Web Docs

- -

See How to report a problem on MDN.

- -

History of MDN Web Docs

- -

The MDN Web Docs (previously Mozilla Developer Network (MDN), previously Mozilla Developer Center (MDC), a.k.a. Devmo) project started in early 2005, when the Mozilla Foundation obtained a license from AOL to use the original Netscape DevEdge content. The DevEdge content was mined for still-useful material, which was then migrated by volunteers into this wiki so it would be easier to update and maintain.

- -

The name was changed to MDN Web Docs in June 2017. See The Future of MDN: A Focus on Web Docs for the rationale behind this decision.

- -

You can find more history of MDN on our 10th anniversary celebration page, including an oral history by some of the people who were involved.

- -

Mozilla Hakkında

- -

Whether you want to learn more about who we are, how to be a part of Mozilla or just where to find us, you've come to the right place. To find out what drives us and makes us different, please visit our mission page.

diff --git a/files/tr/mdn/kuma/index.html b/files/tr/mdn/kuma/index.html deleted file mode 100644 index d08ef04685..0000000000 --- a/files/tr/mdn/kuma/index.html +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: 'Kuma: MDN''s wiki platform' -slug: MDN/Kuma -tags: - - Kuma - - Landing - - MDN - - NeedsTranslation - - TopicStub -translation_of: MDN/Kuma ---- -
{{MDNSidebar}}{{IncludeSubnav("/en-US/docs/MDN")}}
- -

Kuma is the Django code that powers MDN Web Docs.

- -

{{SubpagesWithSummaries}}

- -

Get involved with Kuma

- -

To get involved with Kuma:

- - diff --git a/files/tr/mdn/kuma/server_charts/index.html b/files/tr/mdn/kuma/server_charts/index.html deleted file mode 100644 index 2b3859dfa9..0000000000 --- a/files/tr/mdn/kuma/server_charts/index.html +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Server charts -slug: MDN/Kuma/Server_charts -tags: - - Kuma - - MDN Meta Türkçe -translation_of: MDN/Kuma/Server_charts ---- -
{{MDNSidebar}}{{IncludeSubnav("/en-US/docs/MDN")}}
- -

This page lists MDN server status charts.

- -

Last 30 minutes

- -

Error Rate

- -

{{EmbedNewRelicChart("2fKQPvMkSwU", 300)}}

- -

Kuma web app response time (Average)

- -

{{EmbedNewRelicChart("43yJ3xwUecU", 300)}}

- -

Kuma web app response time (Percentiles)

- -

{{EmbedNewRelicChart("6NzEi7ZBdoN", 300)}}

- -

Last 24 Hours

- -

Error Rate

- -

{{EmbedNewRelicChart("kVeeXx52g0l", 300)}}

- -

Kuma web app response time (Average)

- -

{{EmbedNewRelicChart("2yWkQ9WbEZW", 300)}}

- -

Kuma web app response time (Percentiles)

- -

{{EmbedNewRelicChart("aeFnbLonmvx", 300)}}

- -

Last 3 Days

- -

Error Rate

- -

{{ EmbedNewRelicChart("iv2F4gQYjFX", 300)}}

- -

Kuma web app response time (Average)

- -

{{EmbedNewRelicChart("ddTq7AKgyaG", 300)}}

- -

Kuma web app response time (Percentiles)

- -

{{EmbedNewRelicChart("bRmyM6ujKA8", 300)}}

- -

Last 3 Months

- -

Error Rate

- -

{{EmbedNewRelicChart("fjJ7HnGYNLd", 300)}}

- -

Kuma web app response time (Average)

- -

{{EmbedNewRelicChart("sIaVOeAxNx", 300)}}

diff --git a/files/tr/mdn/kuma/troubleshooting_kumascript_errors/index.html b/files/tr/mdn/kuma/troubleshooting_kumascript_errors/index.html deleted file mode 100644 index c910d90ae0..0000000000 --- a/files/tr/mdn/kuma/troubleshooting_kumascript_errors/index.html +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Troubleshooting KumaScript errors -slug: MDN/Kuma/Troubleshooting_KumaScript_errors -tags: - - HRCTelekom - - KumaScript - - Kılavuz - - MDN Meta - - sabır -translation_of: MDN/Tools/KumaScript/Troubleshooting ---- -
{{MDNSidebar}} 
- -
-

KumaScript bir sayfada görünen hatalar onların büyük korkutucu kırmızı kutularda, okuyuculara-koyarak, ama neyse bir MDN hesabı olan herkese böyle bir hatayı düzeltmek için bir belgeyi düzenleyebilir çok olabilir. Bir sayfa bir hata varsa bunun listesine eklenir hatalarla belgeler . Sitesi editörler düzenli bulup düzeltme hataları için bu listeyi gözden geçirin. Bu makale KumaScript hatası dört tip ayrıntıları ve bazı bunları düzeltmek için uygulayabileceğiniz adımları tekrarlayın.

-
- -

DocumentParsingError

- -

DocumentParsingErrorKumaScript belgenin kendisinde sorun anlayış şey olduğunda hataları görünür. En sık karşılaşılan neden bir yazım hatasıdır makro .

- -

Kontrol:

- -
-
Bir makro çağırmak amacı gütmeden küme parantezleri kullanın.
-
bir makro uğramadan bir belgede yazma \ {gerekiyorsa böyle bir \ ile kaçabilir: \\{
-
Makro parametrede özel karakterin kullanın.
-
Eğer onlar böyle bir \ ile kaçan edilebilir bir makro parametrenin bir "a \ içini ya kullanmanız gerekirse: \\ya\"
-
Makro parametreler arasındaki virgül eksik.
-
Makro parametreler ancak parametrelerin listesinin sonunda bir virgül (,) ile sınırlanmış olması gerekir; örneğin \{\{anch("top", "Back to top")}}.
-
Bir makro çağrısı içinde görünen HTML etiketleri
-
Eğer bir makroya stil uygularsanız, örneğin bir, çünkü çoğu zaman kıracak </code>etiketinin kaynak kodda makro kodu içinde görünmüş olabilir. Orada ne olduğunu görmek ve gereksiz stil kaldırmak için kaynak görünümünü kontrol edin.
-
- - - -

TemplateLoadingError

- -

TemplateLoadingErrorKumaScript bulmakta zorluk sahip olduğunda hataları görünür makro bir sayfada dahil etmek.

- -

Kontrol:

- -
-
Makro adları veya yeniden adlandırılmış makroları yanlış yazılmış.
-
Sen doğru adlandırılmış olup olmadığını görmek için makro için şablon sayfasını ziyaret deneyebilirsiniz. Şablon sayfanın URL adresinin sonuna şablon adını ekleyerek yapılabilir https://developer.mozilla.org/en-US/docs/Template: — örneğin şablon sayfası \{\{anch("top", "Back to top")}}  olan https://developer.mozilla.org/en-US/docs/Template:anch .
-
- Kısmi bir listesi vardır MDN'yi için makrolar bakıyorsun mevcut makro veya onun doğru / yeni yazım içerebilir.
-
- -
-

İpucu: Sen hızlı ve kolay yapabiliriz bir ekleyerek belirli bir makro atlamak için arama anahtar kelimesini Firefox'a. <<< DAHA ÇOK YAKINDA >>

-
- -

TemplateExecutionError

- -

TemplateExecutionErrorKumaScript makro bir hatayla karşılaştığında hataları görünür. Bu hatalar sadece yönetici kullanıcılar tarafından sabit ve böcek olarak rapor alınması gerektiği ortaya edilebilir.

- -

Zaten sabit edilmemiş olduğunu görmek için bir hata kontrolü bildirmeden önce. Sen basılı tutarak size sayfanın yeni bir kopyasını vermek KumaScript zorlayarak yapabilirsiniz shiftEğer (sayfayı yenileyin iken Shift + Ctrl + R Windows / Linux üzerinde Shift + Cmd + R Mac'te).

- -

Hata devam ederse, Hata bildir . Sayfanın URL'sini ve hata metnini ekleyin.

- -

Hata & Bilinmeyen

- -

Bu kategori hataları onlar hata diğer tür biri değilse sonuna kadar olduğunu.

- -

Genellikle (ama her zaman değil) bu hatalar MDN'yi tüm etkileyen bir sorun ile ilgilidir ve bir iki dakika bekledikten sonra basılı tutarak uzak silinebilir shiftsayfayı yenileyin ederken ( Shift + Ctrl + R Windows / Linux üzerinde, Shift + Cmd + R Mac),. Bu hata devam ederse lütfen bir hatayı bildirmek . Sayfanın URL'sini ve hata metnini ekleyin.

- -

HRC Telekom

- -

ağaçlı tepe

- -

HurCloud

- -

Sebir Teknoloji

diff --git a/files/tr/mdn/tools/kumascript/troubleshooting/index.html b/files/tr/mdn/tools/kumascript/troubleshooting/index.html new file mode 100644 index 0000000000..c910d90ae0 --- /dev/null +++ b/files/tr/mdn/tools/kumascript/troubleshooting/index.html @@ -0,0 +1,75 @@ +--- +title: Troubleshooting KumaScript errors +slug: MDN/Kuma/Troubleshooting_KumaScript_errors +tags: + - HRCTelekom + - KumaScript + - Kılavuz + - MDN Meta + - sabır +translation_of: MDN/Tools/KumaScript/Troubleshooting +--- +
{{MDNSidebar}} 
+ +
+

KumaScript bir sayfada görünen hatalar onların büyük korkutucu kırmızı kutularda, okuyuculara-koyarak, ama neyse bir MDN hesabı olan herkese böyle bir hatayı düzeltmek için bir belgeyi düzenleyebilir çok olabilir. Bir sayfa bir hata varsa bunun listesine eklenir hatalarla belgeler . Sitesi editörler düzenli bulup düzeltme hataları için bu listeyi gözden geçirin. Bu makale KumaScript hatası dört tip ayrıntıları ve bazı bunları düzeltmek için uygulayabileceğiniz adımları tekrarlayın.

+
+ +

DocumentParsingError

+ +

DocumentParsingErrorKumaScript belgenin kendisinde sorun anlayış şey olduğunda hataları görünür. En sık karşılaşılan neden bir yazım hatasıdır makro .

+ +

Kontrol:

+ +
+
Bir makro çağırmak amacı gütmeden küme parantezleri kullanın.
+
bir makro uğramadan bir belgede yazma \ {gerekiyorsa böyle bir \ ile kaçabilir: \\{
+
Makro parametrede özel karakterin kullanın.
+
Eğer onlar böyle bir \ ile kaçan edilebilir bir makro parametrenin bir "a \ içini ya kullanmanız gerekirse: \\ya\"
+
Makro parametreler arasındaki virgül eksik.
+
Makro parametreler ancak parametrelerin listesinin sonunda bir virgül (,) ile sınırlanmış olması gerekir; örneğin \{\{anch("top", "Back to top")}}.
+
Bir makro çağrısı içinde görünen HTML etiketleri
+
Eğer bir makroya stil uygularsanız, örneğin bir, çünkü çoğu zaman kıracak </code>etiketinin kaynak kodda makro kodu içinde görünmüş olabilir. Orada ne olduğunu görmek ve gereksiz stil kaldırmak için kaynak görünümünü kontrol edin.
+
+ + + +

TemplateLoadingError

+ +

TemplateLoadingErrorKumaScript bulmakta zorluk sahip olduğunda hataları görünür makro bir sayfada dahil etmek.

+ +

Kontrol:

+ +
+
Makro adları veya yeniden adlandırılmış makroları yanlış yazılmış.
+
Sen doğru adlandırılmış olup olmadığını görmek için makro için şablon sayfasını ziyaret deneyebilirsiniz. Şablon sayfanın URL adresinin sonuna şablon adını ekleyerek yapılabilir https://developer.mozilla.org/en-US/docs/Template: — örneğin şablon sayfası \{\{anch("top", "Back to top")}}  olan https://developer.mozilla.org/en-US/docs/Template:anch .
+
+ Kısmi bir listesi vardır MDN'yi için makrolar bakıyorsun mevcut makro veya onun doğru / yeni yazım içerebilir.
+
+ +
+

İpucu: Sen hızlı ve kolay yapabiliriz bir ekleyerek belirli bir makro atlamak için arama anahtar kelimesini Firefox'a. <<< DAHA ÇOK YAKINDA >>

+
+ +

TemplateExecutionError

+ +

TemplateExecutionErrorKumaScript makro bir hatayla karşılaştığında hataları görünür. Bu hatalar sadece yönetici kullanıcılar tarafından sabit ve böcek olarak rapor alınması gerektiği ortaya edilebilir.

+ +

Zaten sabit edilmemiş olduğunu görmek için bir hata kontrolü bildirmeden önce. Sen basılı tutarak size sayfanın yeni bir kopyasını vermek KumaScript zorlayarak yapabilirsiniz shiftEğer (sayfayı yenileyin iken Shift + Ctrl + R Windows / Linux üzerinde Shift + Cmd + R Mac'te).

+ +

Hata devam ederse, Hata bildir . Sayfanın URL'sini ve hata metnini ekleyin.

+ +

Hata & Bilinmeyen

+ +

Bu kategori hataları onlar hata diğer tür biri değilse sonuna kadar olduğunu.

+ +

Genellikle (ama her zaman değil) bu hatalar MDN'yi tüm etkileyen bir sorun ile ilgilidir ve bir iki dakika bekledikten sonra basılı tutarak uzak silinebilir shiftsayfayı yenileyin ederken ( Shift + Ctrl + R Windows / Linux üzerinde, Shift + Cmd + R Mac),. Bu hata devam ederse lütfen bir hatayı bildirmek . Sayfanın URL'sini ve hata metnini ekleyin.

+ +

HRC Telekom

+ +

ağaçlı tepe

+ +

HurCloud

+ +

Sebir Teknoloji

diff --git a/files/tr/mdn/tools/page_watching/index.html b/files/tr/mdn/tools/page_watching/index.html deleted file mode 100644 index 4df3df166a..0000000000 --- a/files/tr/mdn/tools/page_watching/index.html +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Watch or subscribe to a page or set of pages -slug: MDN/Tools/Page_watching -translation_of: MDN/Tools/Page_watching ---- -
{{MDNSidebar}}
- -

MDN'deki bir sayfaya abone olmak, her güncellendiğinde veya değiştirildiğinde e-postayla bilgilendirilmenizi sağlar. İzle düğmesi her MDN sayfasının sağ üst köşesinde bulunur. Abonelik seçeneklerine erişmek için, imleci İzleme menüsünü açıklamak için İzle düğmesinin üzerine getirin:

- -

MDN's Watch menüsünün ekran görüntüsü

- -

Yalnızca bir sayfayı veya o sayfayı ve alt sayfalarını izlemek için bir seçenek belirleyin.

- -

Bir sayfaya abone olun

- -

Bir kullanıcı yalnızca bir sayfayı her düzenlediğinde bir e-posta bildirimi almak için ilk " Sayfa Başlığına Abone Ol" seçeneğini tıklayın .

- -

Bir sayfaya ve tüm alt makalelerine abone olun

- -

Bir kullanıcı o sayfayı ve alt sayfalarını her düzenlediğinde bir e-posta bildirimi almak için ikinci " Sayfa Başlığına ve tüm alt makalelerine abone ol" seçeneğini tıklayın . Buna abonelik talebinde bulunulduktan sonra eklenen alt sayfalar da dahildir, bu nedenle gelecekte daha fazla alt sayfa oluşturulacaksa, bunlar için de bildirim alırsınız.

- -

Bir sayfadan aboneliği iptal et

- -

Aboneliği iptal etmek ve bir sayfayı izlemeyi durdurmak için, İzleme menüsünü tekrar açın ve " Sayfa Başlığından Aboneliği İptal Et " i tıklayın. " Sayfa Başlığından Aboneliği İptal Et" i yalnızca bir sayfaya abone olursanız görürsünüz. Artık sayfa her değiştiğinde bir e-posta almayacaksınız.

- -

Sayfa değişikliği e-postaları

- -

Bir sayfaya abone olursanız, her değişiklik kaydedişinde bir e-posta alırsınız. Bu e-postalar notifications@developer.mozilla.org adresinden gelir ve MDN hesabınıza kayıtlı e-posta adresine gönderilir. Her mesajın bir başlığı vardır:

- -
[MDN] Sayfa " Sayfa başlığı " kullanıcı adına göre değişti
- -

İleti, başlıktaki bilgilerin tekrarlanmasıyla başlar, ardından içeriğin tam olarak neyin değiştiğini gösteren standart bir farkını sunar. Değişiklikler, HTML kaynak kodu olarak gösterilir; bu, MDN bağlamında kullanılmazsa okunması biraz garip olabilir.

- -

Farkın altında, değişiklik üzerinde hareket etmek için kullanabileceğiniz faydalı bağlantıların bir listesi vardır:

- - - -

E-postanın altında, e-postayı hangi aboneliğin oluşturduğunu belirten bir bildirim bulunur, örneğin "HTML öğesi başvurusu ve tüm alt makaleleri üzerinde düzenlemelere abone oldunuz" ve abonelikten çıkma bağlantısı. Aboneliği iptal etmek için bağlantıyı tıklatırsanız, bu izleme isteği için artık ileti almayacaksınız.

diff --git a/files/tr/mdn/yari/index.html b/files/tr/mdn/yari/index.html new file mode 100644 index 0000000000..d08ef04685 --- /dev/null +++ b/files/tr/mdn/yari/index.html @@ -0,0 +1,26 @@ +--- +title: 'Kuma: MDN''s wiki platform' +slug: MDN/Kuma +tags: + - Kuma + - Landing + - MDN + - NeedsTranslation + - TopicStub +translation_of: MDN/Kuma +--- +
{{MDNSidebar}}{{IncludeSubnav("/en-US/docs/MDN")}}
+ +

Kuma is the Django code that powers MDN Web Docs.

+ +

{{SubpagesWithSummaries}}

+ +

Get involved with Kuma

+ +

To get involved with Kuma:

+ + -- cgit v1.2.3-54-g00ecf