diff --git a/files/ko/_redirects.txt b/files/ko/_redirects.txt index 49e20eecd93aa9..05a8d55c7ae665 100644 --- a/files/ko/_redirects.txt +++ b/files/ko/_redirects.txt @@ -354,9 +354,6 @@ /ko/docs/MDN/Contribute/Structures/Compatibility_tables /ko/docs/MDN/Structures/Compatibility_tables /ko/docs/MDN/Contribute/Structures/Macros /ko/docs/MDN/Structures/Macros /ko/docs/MDN/Contribute/Structures/Macros/Commonly-used_macros /ko/docs/MDN/Structures/Macros/Commonly-used_macros -/ko/docs/MDN/Contribute/Tools /ko/docs/MDN/Tools -/ko/docs/MDN/Contribute/Tools/KumaScript /ko/docs/MDN/Tools/KumaScript -/ko/docs/MDN/Contribute/Tools/KumaScript/Troubleshooting /ko/docs/MDN/Tools/KumaScript/Troubleshooting /ko/docs/MDN/Getting_started /ko/docs/MDN/Contribute/Getting_started /ko/docs/MDN/Guidelines/Best_practices /ko/docs/MDN/Guidelines/Conventions_definitions /ko/docs/MDN/Guidelines/Code_guidelines/Code_guidelines /ko/docs/MDN/Guidelines/Code_guidelines/General @@ -417,14 +414,12 @@ /ko/docs/Node_server_without_framework /ko/docs/Learn/Server-side/Node_server_without_framework /ko/docs/Notable_bugs_fixed_in_Firefox_3 /ko/docs/Mozilla/Firefox/Releases/3/Notable_bugs_fixed /ko/docs/Online_and_offline_events /ko/docs/Web/API/Navigator/onLine -/ko/docs/Plugins/Guide/Scripting_plugins /ko/docs/Glossary/Plugin /ko/docs/SVG /ko/docs/Web/SVG /ko/docs/SVG/Tutorial /ko/docs/Web/SVG/Tutorial /ko/docs/SVG:Tutorial /ko/docs/Web/SVG/Tutorial /ko/docs/SVG_In_HTML_Introduction /ko/docs/Web/SVG/Tutorial/SVG_In_HTML_Introduction /ko/docs/SVG_improvements_in_Firefox_3 /ko/docs/Mozilla/Firefox/Releases/3/SVG_improvements /ko/docs/SVG_in_Firefox /ko/docs/Web/SVG/SVG_1.1_Support_in_Firefox -/ko/docs/Scripting_Plugins /ko/docs/Glossary/Plugin /ko/docs/The_Importance_of_Correct_HTML_Commenting /ko/docs/Learn/HTML/Introduction_to_HTML/Getting_started#HTML_comments /ko/docs/The_XSLT_JavaScript_Interface_in_Gecko /ko/docs/Web/XSLT/XSLT_JS_interface_in_Gecko /ko/docs/The_XSLT_JavaScript_Interface_in_Gecko/Introduction /ko/docs/Web/XSLT/XSLT_JS_interface_in_Gecko/Introduction diff --git a/files/ko/_wikihistory.json b/files/ko/_wikihistory.json index 95a0fc8182d87a..fa8e310d4fcf38 100644 --- a/files/ko/_wikihistory.json +++ b/files/ko/_wikihistory.json @@ -721,13 +721,6 @@ "enfroze" ] }, - "Glossary/Plugin": { - "modified": "2019-01-16T15:11:14.478Z", - "contributors": [ - "teoli", - "Anonymous" - ] - }, "Glossary/Polyfill": { "modified": "2019-11-18T11:28:34.172Z", "contributors": [ @@ -2656,32 +2649,6 @@ "Netaras" ] }, - "MDN/Tools": { - "modified": "2020-09-30T16:51:24.922Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "zziuni", - "frankradio", - "galcyurio", - "Vi01et", - "jswisher" - ] - }, - "MDN/Tools/KumaScript": { - "modified": "2020-11-30T12:49:14.835Z", - "contributors": [ - "chrisdavidmills", - "mfuji09" - ] - }, - "MDN/Tools/KumaScript/Troubleshooting": { - "modified": "2020-09-30T16:51:25.656Z", - "contributors": [ - "chrisdavidmills", - "Silvermist" - ] - }, "MDN/Yari": { "modified": "2019-09-06T03:29:26.311Z", "contributors": [ diff --git a/files/ko/glossary/dhtml/index.html b/files/ko/glossary/dhtml/index.html index f729271ac6ce73..58afb1c615b767 100644 --- a/files/ko/glossary/dhtml/index.html +++ b/files/ko/glossary/dhtml/index.html @@ -21,11 +21,6 @@

Documentation

-

커뮤니티

- -

{{ DiscussionList("dev-ajax", "mozilla.dev.ajax") }} -

도구

diff --git a/files/ko/glossary/index.html b/files/ko/glossary/index.html index 4dbd0c6429808a..b11de2f32dd1d6 100644 --- a/files/ko/glossary/index.html +++ b/files/ko/glossary/index.html @@ -14,18 +14,12 @@ ---

웹 기술은 문서화 및 코딩에 쓰이는 전문 용어와 약어 목록을 포함합니다. 이 용어 사전은 웹을 성공적으로 이해하고 구축하기 위해 알아야 할 단어와 약자의 정의를 제공합니다.

-

용어 사전

- -

{{GlossaryList({"split":"h3", "css":"multiColumnList"})}}

-

용어 사전에 기여하기

용어 사전은 끝없이 진행 중인 작업입니다. 여러분은 새 항목을 작성하거나 기존 항목의 개선을 도울 수 있습니다. 가장 쉬운 시작법은 다음 버튼을 누르거나 아래에 제안된 용어 중 하나를 고르는 겁니다.

용어 사전에 새 항목 추가하기

-

{{GlossaryList({"terms":[], "filter":"notdefined", "css":"multiColumnList"})}}

-

혹시 용어 사전에 기여하는 법에 관해 더 알고 싶다면, 용어 사전 문서화 상태 페이지를 확인하세요.

정답 확인.

다음에는?

-

{{ nextPage("/en-US/docs/CSS/Getting_Started/Lists", "리스트") }}Stylesheet에 내용물을 추가 하는 일반 방법으로 리스트로 표기하는 방법이 있다. 다음장에는 specify style for 리스트 elements를 위한 스타일 표기법에 대해 알아보자.

+

Stylesheet에 내용물을 추가 하는 일반 방법으로 리스트로 표기하는 방법이 있다. 다음장에는 specify style for 리스트 elements를 위한 스타일 표기법에 대해 알아보자.

diff --git a/files/ko/mdn/guidelines/conventions_definitions/index.html b/files/ko/mdn/guidelines/conventions_definitions/index.html index 1386fbe2f3eebc..2bef526365335e 100644 --- a/files/ko/mdn/guidelines/conventions_definitions/index.html +++ b/files/ko/mdn/guidelines/conventions_definitions/index.html @@ -31,5 +31,4 @@

콘텐츠 복사하기

  • 클립보드에서 콘텐츠를 붙여 넣으세요.
    • -
  • 때때로 말 그대로 많은 페이지에 같은 콘텐츠를 사용하고 싶습니다. 이 경우에, 한 페이지에 콘텐츠를 두고, 그 뒤에 한 페이지에서 다른 페이지로 내용물을 삽입참조(transclude)하는 {{TemplateLink("Page")}} 매크로를 사용하는 것이 최선이 될 수 있습니다. 이런 식으로 하면, 소스 페이지의 텍스트가 갱신될 때마다, 대상 페이지도 갱신됩니다 (즉, 이는 강제-새로고침 또는 대상 페이지가 예정된 재빌드가 이루어질 때 일어납니다).
    • diff --git a/files/ko/mdn/guidelines/writing_style_guide/index.html b/files/ko/mdn/guidelines/writing_style_guide/index.html index f13e33a34f86f0..a981326e161a20 100644 --- a/files/ko/mdn/guidelines/writing_style_guide/index.html +++ b/files/ko/mdn/guidelines/writing_style_guide/index.html @@ -149,7 +149,7 @@

    Sections, paragraphs, and newlines

    Use heading levels in decreasing order: {{HTMLElement("h2")}} then {{HTMLElement("h3")}} then {{HTMLElement("h4")}}, without skipping levels.

    -

    H2 is the highest level allowed because H1 is reserved for the page title. If you need more than three or four levels of headers, consider breaking up the article into several smaller articles with a landing page, and linking them together using the following macros: {{TemplateLink("Next")}}, {{TemplateLink("Previous")}}, and {{TemplateLink("PreviousNext")}}.

    +

    H2 is the highest level allowed because H1 is reserved for the page title. If you need more than three or four levels of headers, consider breaking up the article into several smaller articles with a landing page, and linking them together using the following macros: \{{Next}}, \{{Previous}}, and \{{PreviousNext}}.

    Heading dos and donts

    @@ -297,11 +297,11 @@

    Styling mentions of HTML elements

    Element names
    -
    Use the {{TemplateLink("HTMLElement")}} macro, which creates a link to the page for that element. For example, writing \{{HTMLElement("title")}} produces "{{HTMLElement("title")}}". If you don't want to create a link, enclose the name in angle brackets and use the "Inline Code" style (e.g., <title>).
    +
    Use the \{{HTMLElement}} macro, which creates a link to the page for that element. For example, writing \{{HTMLElement("title")}} produces "{{HTMLElement("title")}}". If you don't want to create a link, enclose the name in angle brackets and use the "Inline Code" style (e.g., <title>).
    Attribute names
    Use "Inline Code" style to put attribute names in code font. Additionally, put them in bold face when the attribute is mentioned in association with an explanation of what it does, or the first time it's used in the article.
    Attribute definitions
    -
    Use the {{TemplateLink("htmlattrdef")}} macro (e.g., \{{htmlattrdef("type")}}) for the definition term, so that it can be linked to from other pages easily by simply using the {{TemplateLink("htmlattrxref")}} macro (e.g., \{{htmlattrxref("attr","element")}}) to reference attribute definitions.
    +
    Use the \{{htmlattrdef}} macro (e.g., \{{htmlattrdef("type")}}) for the definition term, so that it can be linked to from other pages easily by simply using the \{{htmlattrxref}} macro (e.g., \{{htmlattrxref("attr","element")}}) to reference attribute definitions.
    Attribute values
    Use the "Inline Code" style to apply <code> to attribute values, and don't use quotation marks around string values, unless needed by the syntax of a code sample.
    For example: "When the type attribute of an <input> element is set to email or tel ..."
    @@ -614,7 +614,7 @@

    HTML elements

    Use "elements" to refer to HTML and XML elements, rather than "tags". In addition, they should almost always be wrapped in "<>", and should be in the {{HTMLElement("code")}} style.

    -

    When you reference a given element for the first time in a section, you should use the {{TemplateLink("HTMLElement")}} macro to create a link to the documentation for the element (unless you're writing within that element's reference document page).

    +

    When you reference a given element for the first time in a section, you should use the \{{HTMLElement}} macro to create a link to the documentation for the element (unless you're writing within that element's reference document page).