diff options
Diffstat (limited to 'files/pt-pt/mdn/contribute')
10 files changed, 0 insertions, 1057 deletions
diff --git a/files/pt-pt/mdn/contribute/feedback/index.html b/files/pt-pt/mdn/contribute/feedback/index.html deleted file mode 100644 index a4e88f36f8..0000000000 --- a/files/pt-pt/mdn/contribute/feedback/index.html +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Enviar opinião sobre a MDN -slug: MDN/Contribute/Feedback -tags: - - Documentação - - Guía - - MDN - - Metadados MDN -translation_of: MDN/Contribute/Feedback ---- -<div>{{MDNSidebar}}</div> - -<div>{{IncludeSubnav("/pt-PT/docs/MDN")}}</div> - -<p>Bem-vindo à MDN! Se tiver sugestões, ou tiver problemas ao utilizar a MDN, este é o lugar certo para estar. O simples facto de estar interessado em oferecer a sua opinião/comentário faz com que faça parte da comunidade da Mozilla e nós agradecemos antecipadamente pelo seu interesse.</p> - -<p>Tem várias opções para oferecer a sua visão; este artigo irá ajudá-lo a fazer isso.</p> - -<h2 id="Atualizar_a_documentação">Atualizar a documentação</h2> - -<p>First of all, if you've seen a problem with the documentation, you should always feel free to correct it yourself. Simply <a href="/en-US/docs/MDN/Contribute/Howto/Create_an_MDN_account">sign in</a> using <a href="https://github.com/">Github</a>, then click any blue <strong>Edit</strong> button to open the <a href="/en-US/docs/MDN/Contribute/Editor">editor</a> and enter the world of contributing to MDN documentation. The documentation here is in a wiki, and is curated by a team of volunteers and paid staff, so don't be shy—your grammar doesn't have to be perfect. We'll clean it up if you make a mistake; no harm done!</p> - -<p>Para mais informação sobre a contribuição para a documentação da MDN, consulte:</p> - -<ul> - <li><a href="/pt-PT/docs/MDN/Intrudu%C3%A7%C3%A3o" title="/en-US/docs/Project:Getting_started">Iniciação na MDN</a></li> - <li><a href="/pt-PT/docs/MDN/Contribute">Contribuir para a MDN</a></li> - <li><a href="/pt-PT/docs/MDN/Contribute/Editor" title="/en-US/docs/Project:MDN_editing_interface">A interface de edição da MDN</a></li> -</ul> - -<h2 id="Junte-se_à_conversação">Junte-se à conversação</h2> - -<p>Fale connosco! Existem algumas maneiras para entrar em contacto com outras pessoas que trabalham com conteúdo na MDN.</p> - -<h3 id="Conversação_Síncrono">Conversação (Síncrono)</h3> - -<p> - </p><h3 id="Discussões_Assíncrono">Discussões (Assíncrono)</h3> - - -<p>Longer-term discussions happen on our <a href="https://discourse.mozilla-community.org/c/mdn">MDN discussion forum</a>. You can post to the forum via email to <a href="mailto://mdn@mozilla-community.org">mdn@mozilla-community.org</a>. If you join the forum, you can choose to have notifications about discussions sent to you via email as well.</p> - -<h2 id="Comunicar_um_problema">Comunicar um problema</h2> - -<h3 id="Problemas_na_documentação">Problemas na documentação</h3> - -<p>Se encontrar um problema na documentação e não conseguir corrigí-lo por qualquer motivo, poderá <a href="https://github.com/mdn/sprints/issues/new?template=issue-template.md&projects=mdn/sprints/2&labels=user-report">comunicar o problema</a>! Pode utilziar este formulário para qualquer problema da documentação, por exemplo:</p> - -<ul> - <li>uma correção simples</li> - <li>um pedido para uma parte completa de conteúdo</li> - <li>comunicar conteúdo inapropriado (incluindo "spam" e traduções erradas)</li> -</ul> - -<p>Como mencionado anteriormente, nós convidamo-lo para contribuir com as suas alterações, mas esta opção também está disponível para si.</p> - -<h3 id="Problemas_no_site">Problemas no site</h3> - -<p>Se encontrar problemas com o site da <em>Web</em> da MDN, ou tiver ideias para novas características para o site, pode <a href="https://bugzilla.mozilla.org/form.mdn">submeter um pedido à equipa de desenvolvimento da MDN</a>.</p> diff --git a/files/pt-pt/mdn/contribute/getting_started/index.html b/files/pt-pt/mdn/contribute/getting_started/index.html deleted file mode 100644 index 315613f49c..0000000000 --- a/files/pt-pt/mdn/contribute/getting_started/index.html +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: Iniciação na MDN -slug: MDN/Contribute/Getting_started -tags: - - Beginner - - Guía - - Iniciação - - Introdução - - Metadados MDN -translation_of: MDN/Contribute/Getting_started ---- -<div> -<div>{{MDNSidebar}}</div> -</div> - -<p><span class="seoSummary">Nós somos uma comunidade aberta de programadores e autores que criam recursos para uma Web melhor, independentemente da marca, navegador, ou plataforma. Qualquer pessoa pode contribuir e cada uma que o faz, torna-nos mais fortes. Juntos, nós podemos continuar a inovar na Web para o bem de todos. Isso começa aqui, consigo.</span></p> - -<p>Cada parte da MDN (desde o site até à documentação, amostras de código, e demonstrações) é criada por uma comunidade de programadores e autores. Por favor considere colaborar também!</p> - -<h2 id="3_passos_simples_para_a_MDN"><span>3 passos simples para a MDN</span></h2> - -<div class="pt" id="OutputArea" style="direction: ltr; text-align: left;"> -<div class="Wrap" id="OutputText" style="direction: ltr; text-align: left;"> -<div><span id="noHighlight_0.47920148300743626">A MDN </span><span id="ouHighlight__4_5TO4_4">é</span><span id="noHighlight_0.5491344717821757"> </span><span id="ouHighlight__7_7TO6_7">uma</span><span id="noHighlight_0.8750513674493037"> </span><em><span id="ouHighlight__9_12TO9_12">wiki</span></em><span id="noHighlight_0.7850095290312931">,</span><span id="noHighlight_0.5182284369975565"> </span><span id="ouHighlight__15_19TO15_18">onde</span><span id="noHighlight_0.018006826884430893"> </span><strong><span id="ouHighlight__21_26TO20_34">qualquer pessoa</span></strong><span id="noHighlight_0.4040337194597289"> </span><span id="ouHighlight__28_30TO36_39">pode</span><span id="noHighlight_0.9747336392889395"> </span><span id="ouHighlight__32_34TO41_49">adicionar</span><span id="noHighlight_0.7066487403238145"> </span><span id="ouHighlight__36_38TO51_51">e</span><span id="noHighlight_0.5446518252479879"> </span><span id="ouHighlight__40_43TO53_58">editar</span><span id="noHighlight_0.6426048314610565"> </span><span id="ouHighlight__45_51TO60_67">conteúdo</span><span id="noHighlight_0.8453660300988101">.</span><span id="noHighlight_0.055925875247653134"> </span><span id="ouHighlight__54_56TO70_73">N</span><span id="ouHighlight__58_62TO75_77">ão</span><span id="noHighlight_0.8092718734331236"> </span><span id="ouHighlight__64_70TO79_85">precisa</span><span id="noHighlight_0.22724740936320986"> de </span><span id="ouHighlight__72_73TO87_89">ser</span><span id="noHighlight_0.1843562915821374"> </span><span id="ouHighlight__75_75TO91_92">um</span><span id="noHighlight_0.3592619006001544"> </span><span id="ouHighlight__77_86TO94_104">programador</span><span id="noHighlight_0.285547875523669"> </span><span id="ouHighlight__88_89TO106_107">ou</span><span id="noHighlight_0.9061669056755919"> </span><span id="ouHighlight__91_94TO109_112">saber</span><span id="noHighlight_0.19684376567211204"> </span><span id="ouHighlight__98_100TO114_118">muito</span><span id="noHighlight_0.5675302021548134"> </span><span id="ouHighlight__102_106TO120_124">sobre</span><span id="noHighlight_0.11138225174850647"> </span><span id="ouHighlight__108_119TO126_136">tecnologia</span><span id="noHighlight_0.8834602769538198">.</span><span id="noHighlight_0.28454983315849447"> </span><span id="ouHighlight__122_130TO139_145">Existem várias</span><span id="noHighlight_0.8598458374371334"> </span><span id="ouHighlight__142_147TO154_159">coisas</span><span id="noHighlight_0.34892750513629345"> </span><span id="ouHighlight__149_152TO161_163">que</span><span id="noHighlight_0.9874443798556571"> </span><span id="ouHighlight__154_160TO165_172">precisam</span><span id="noHighlight_0.34244235656099486"> </span><span id="ouHighlight__162_163TO174_176">ser</span><span id="noHighlight_0.25841029026007567"> </span><span id="ouHighlight__165_168TO178_183">feitas</span><span id="noHighlight_0.32790348607369335">,</span><span id="noHighlight_0.0754749662753087"> </span><span id="ouHighlight__171_174TO186_187">desde</span><span id="noHighlight_0.45034184896804075"> </span><span id="ouHighlight__183_187TO189_195">tarefas</span><span id="noHighlight_0.889982282033675"> </span><span id="ouHighlight__176_181TO197_203">simples</span><span id="noHighlight_0.874949287144007">, tal como a </span><span id="noHighlight_0.17301975604090902">revisão de </span><span id="ouHighlight__197_208TO221_226">textos</span><span id="noHighlight_0.6149690455375806"> </span><span id="ouHighlight__210_212TO228_228">e</span><span id="noHighlight_0.9289231957504542"> </span><span id="ouHighlight__214_223TO230_239">correção de</span><span id="noHighlight_0.5040134767190689"> </span><span id="ouHighlight__225_229TO241_258">erros ortográficos</span><span id="noHighlight_0.5764830231422348"> até </span><span id="ouHighlight__231_232TO260_261">às</span><span id="noHighlight_0.31222671666655055"> mais </span><span id="ouHighlight__238_244TO263_271">complexas,</span><span id="noHighlight_0.14560557587044287"> </span><span id="ouHighlight__251_257TO273_281">tal como</span><span id="noHighlight_0.2685463990562986"> </span><span id="ouHighlight__259_265TO283_290">escrever</span><span id="noHighlight_0.19633858312747077"> </span><span id="ouHighlight__271_283TO292_303">documentação</span><span id="noHighlight_0.9021550954525854"> </span><span id="ouHighlight__267_269TO308_310">API</span><span id="noHighlight_0.34762725714498666">.</span></div> - -<div></div> -</div> -</div> - -<div class="pt" id="OutputArea" style="direction: ltr; text-align: left;"> -<div class="Wrap" id="OutputText" style="direction: ltr; text-align: left;"> -<div><span id="noHighlight_0.6939304266497809">Contribuir </span><span id="ouHighlight__13_14TO11_11">é</span><span id="noHighlight_0.754432452620986"> </span><span id="ouHighlight__16_19TO13_17">fácil</span><span id="noHighlight_0.12677613373170482"> </span><span id="ouHighlight__21_23TO19_19">e</span><span id="noHighlight_0.9169567677650025"> </span><span id="ouHighlight__25_28TO21_26">seguro</span><span id="noHighlight_0.35895146514742815">.</span><span id="noHighlight_0.11298517990296342"> </span><span id="ouHighlight__31_34TO29_33">Mesmo</span><span id="noHighlight_0.22314055925593745"> </span><span id="ouHighlight__36_37TO35_36">que cometa um erro</span><span id="noHighlight_0.4559037862176293">,</span><span id="ouHighlight__59_62TO60_64"> este é facilmente corrigido</span><span id="ouHighlight__76_76TO81_81">.</span><span id="noHighlight_0.40627264171417155"> </span><span id="ouHighlight__78_79TO83_84">Se</span><span id="noHighlight_0.2985670129310918"> não sabe ao certo qual deverá ser o aspeto final </span><span id="ouHighlight__128_129TO139_140">ou o seu vocabulário não é o mais rico</span><span id="noHighlight_0.5033058561197279">,</span><span id="noHighlight_0.03342360750842488"> </span><span id="ouHighlight__166_170TO171_173">não</span><span id="noHighlight_0.8750742285474321"> se </span><span id="ouHighlight__172_182TO178_185">preocupe</span><span id="noHighlight_0.14456605310738102">!</span><span id="noHighlight_0.7159356526709744"> </span><span id="ouHighlight__188_194TO188_192">Nós temos</span><span id="noHighlight_0.8891478782467954"> </span><span id="ouHighlight__196_196TO194_196">uma</span><span id="noHighlight_0.34570799241183214"> </span><span id="ouHighlight__198_201TO198_203">equipa</span><span id="noHighlight_0.4175451730392493"> </span><span id="ouHighlight__203_204TO205_206">de</span><span id="noHighlight_0.8630305052430338"> </span><span id="ouHighlight__206_211TO208_214">pessoas</span><span id="noHighlight_0.91504254606562"> </span><span id="ouHighlight__213_217TO216_219">cujo</span><span id="noHighlight_0.8103854016751867"> </span><span id="ouHighlight__219_221TO221_228">trabalho</span><span id="noHighlight_0.65601862530836"> </span><span id="ouHighlight__226_227TO230_230">é</span><span id="noHighlight_0.5841048903172054"> </span><span id="ouHighlight__232_235TO232_234">ter</span><span id="noHighlight_0.28754000201425867"> </span><span id="ouHighlight__229_230TO236_236">a</span><span id="noHighlight_0.8118269900735291"> </span><span id="ouHighlight__237_240TO238_244">certeza</span><span id="noHighlight_0.708513780871264"> de </span><span id="ouHighlight__242_245TO249_251">que</span><span id="noHighlight_0.9875258576783718"> o </span><span id="ouHighlight__253_260TO255_262">conteúdo</span><span id="noHighlight_0.22787459205105864"> </span><span id="ouHighlight__247_251TO264_269">da MDN</span><span id="noHighlight_0.32694403655209914"> </span><span id="ouHighlight__262_264TO271_271">é</span><span id="noHighlight_0.43821525588932086"> </span><span id="ouHighlight__266_267TO273_275">tão</span><span id="noHighlight_0.37403813332407077"> </span><span id="ouHighlight__269_272TO277_279">bom</span><span id="noHighlight_0.38391309247561567"> </span><span id="ouHighlight__274_275TO281_286">quanto</span><span id="noHighlight_0.03257742151312082"> </span><span id="ouHighlight__277_284TO288_295">possível</span><span id="noHighlight_0.10488359575747619">.</span><span id="noHighlight_0.7375956492335589"> </span><span id="ouHighlight__287_293TO298_303">Alguém</span><span id="noHighlight_0.7339586828005976"> </span><span id="ouHighlight__312_320TO310_319">certificar</span><span id="noHighlight_0.7685186939234422">-se-á de que o </span><span id="ouHighlight__322_325TO331_333">seu</span><span id="noHighlight_0.2158936316841401"> </span><span id="ouHighlight__327_330TO335_342">trabalho</span><span id="noHighlight_0.44200265413885365"> </span><span id="ouHighlight__332_333TO344_344">está</span><span id="noHighlight_0.7824145304173619"> </span><span id="ouHighlight__335_338TO346_353">conciso</span><span id="noHighlight_0.8205113491988623"> </span><span id="ouHighlight__340_342TO355_355">e</span><span id="noHighlight_0.2967837506349432"> </span><span id="ouHighlight__344_355TO357_367">bem escrito</span><span id="noHighlight_0.1417488745865505">.</span><span id="noHighlight_0.7186922743172103"> P</span><span id="ouHighlight__358_362TO370_381">artilhe</span><span id="noHighlight_0.31150297125971427"> </span><span id="ouHighlight__364_367TO383_387">o que</span><span id="noHighlight_0.25179450598587694"> </span><span id="ouHighlight__373_376TO389_392">sabe</span><span id="noHighlight_0.4558381673714762">,</span><span id="noHighlight_0.6630645323624911"> </span><span id="ouHighlight__382_387TO396_399">siga o seu instinto </span><span id="noHighlight_0.16705133535882088"> </span><span id="ouHighlight__405_407TO420_420">e</span><span id="noHighlight_0.7738893383584872"> </span><span id="ouHighlight__409_413TO422_428">confie</span><span id="noHighlight_0.8909652779069059"> </span><span id="ouHighlight__415_416TO430_431">no</span><span id="noHighlight_0.047160979487215204"> </span><span id="ouHighlight__422_425TO433_437">resto</span><span id="noHighlight_0.3498706762716407"> </span><span id="ouHighlight__427_428TO439_440">da</span><span id="noHighlight_0.4435827843376339"> </span><span id="ouHighlight__430_442TO442_451">comunidade</span><span id="noHighlight_0.423638827999702"> para o ajudar a melhorar o seu trabalho.</span></div> -</div> -</div> - -<h3 id="Passo_1_Criar_uma_conta_na_MDN">Passo 1: Criar uma conta na MDN</h3> - -<p>Para começar a contribuir na MDN precisa de ter uma conta na MDN. Para mais detalhes, por favor, consulte <a href="/pt-PT/docs/MDN/Contribute/Howto/Criar_uma_conta_MDN">como criar uma conta</a>.</p> - -<h3 id="Passo_2_Escolher_uma_tarefa">Passo 2: Escolher uma tarefa</h3> - -<div class="pt" id="OutputArea" style="direction: ltr; text-align: left;"> -<div class="Wrap" id="OutputText" style="direction: ltr; text-align: left;"> -<div><span id="ouHighlight__4_7TO6_8">Agora que</span><span id="noHighlight_0.7397612230677483"> </span><span id="noHighlight_0.8224719251874061">iniciou a sessão</span><span id="noHighlight_0.07721447543089255">,</span><span id="noHighlight_0.20180178040099794"> </span><span id="ouHighlight__28_31TO28_31">leia</span><span id="noHighlight_0.1347259088605407"> </span><span id="ouHighlight__33_35TO33_34">as</span><span id="noHighlight_0.1550906597924332"> </span><span id="ouHighlight__37_48TO36_45">descrições</span><span id="noHighlight_0.5936187806451623"> </span><span id="ouHighlight__50_51TO47_49">das</span><span id="ouHighlight__68_72TO51_55"> tarefas diferentes </span><span>em</span><span id="noHighlight_0.9921036450111824"> </span>{{anch("Tarefas disponíveis", "a lista abaixo")}},<span id="noHighlight_0.3056672720834265"> </span><span id="ouHighlight__128_130TO136_136">e</span><span id="noHighlight_0.644837387548433"> </span><span id="ouHighlight__132_137TO138_144">decid</span><span id="ouHighlight__154_160TO166_171">a qual é a mais apelativa para si</span><span id="noHighlight_0.34950865963617184">.</span><span id="noHighlight_0.23952518307785142"> </span><span id="ouHighlight__170_172TO174_177">Pode</span><span id="noHighlight_0.4532969186995154"> </span><span id="ouHighlight__178_181TO184_191">escolher</span><span id="noHighlight_0.31003284659874975"> </span><span id="ouHighlight__183_185TO193_200">qualquer</span><span id="noHighlight_0.17357587947915787"> </span><span id="ouHighlight__187_190TO202_207">tarefa que lhe agrade e comece a contribuir</span><span id="noHighlight_0.470803195280464">.</span></div> -</div> -</div> - -<h3 id="Passo_3_Executar_a_tarefa">Passo 3: Executar a tarefa</h3> - -<p>Assim que decidir que tarefa é que pretende fazer, procure uma página específica, exemplo de código, etc., para trabalhar, e comece!</p> - -<p>Não se preocupe em ser perfecionista; outros colaboradores da MDN estão aqui para ajudar a corrigir eventuais erros. Para quem quiser experimentar com a edição na MDN antes de fazer algo "a sério", nós temos a página <em><strong><a href="/en-US/docs/Sandbox">Sandbox</a></strong></em> onde poderá testar livremente. Se entretanto tiver dúvidas, consulte a página da <a href="/en-US/docs/MDN/Community">Comunidade</a> para informação sobre contactos e canais de conversação onde poderá obter as suas respostas.</p> - -<p>Quando tiver terminado a tarefa escolhida, sinta-se livre para escolher outro item, ou consulte abaixo <a href="#Other_things_you_can_do_on_MDN">outras coisas que pode fazer na MDN.</a></p> - -<h2 id="Tarefas_disponíveis">Tarefas disponíveis</h2> - -<p>Existem várias formas possíveis para que possa contribuir para a MDN, dependendo do seu conjunto de habilidades e interesses. Mesmo que algumas tarefas possam ser assustadoras, nós temos muitas atividades simples disponíveis. Algumas delas apenas precisam de cinco minutos (ou menos!) do seu tempo. Abaixo, com a tarefa e respetiva breve descrição, encontrará o tempo aproximado que cada tarefa normalmente demora.</p> - -<h3 id="Opção_1_Eu_gosto_de_palavras">Opção 1: Eu gosto de palavras</h3> - -<p>Pode ajudar-nos a rever ou a editar documentos existentes, e aplicar as etiquetas corretas para os mesmos.</p> - -<ul> - <li><a href="/pt-PT/docs/MDN/Contribute/Howto/Como_definir_o_resumo_para_uma_pagina">Definir o resumo para uma página </a>(5 a 15 minutos)</li> - <li><a href="/pt-PT/docs/MDN/Contribute/Howto/fazer_revisão_editorial">Efetuar revisões editoriais</a> (5 a 30 minutos)</li> - <li><a href="/pt-PT/docs/MDN/Contribute/Howto/Como_escrever_uma_nova_entrada_no_Glossario">Escrever uma nova entrada no Glossário </a>(15 minutos a 1 hora)</li> - <li><a href="/pt-PT/docs/MDN/Contribute/Howto/Como_escrever_um_artigo_para_ajudar_as_pessoas_a_aprenderem_sobre_a_Web">Como escrever um artigo para ajudar as pessoas a aprenderem sobre a Web</a> (1 a 3 horas)</li> -</ul> - -<div class="note"><strong>Nota</strong>: se estiver a rever ou a escrever novos artigos, nós pedimos-lhe para, por favor, rever o '<a href="/pt-PT/docs/MDN/Contribute/linhas_diretrizes/Guia_de_estilo_de_escrita">Guia de Estilo</a>'. Isto irá ajudar a assegurar que os artigos sejam consistentes.</div> - -<h3 id="Opção_2_Eu_gosto_de_código">Opção 2: Eu gosto de código</h3> - -<p>Nós precisamos de mais exemplos de código! Também pode ajudar a criar a plataforma do nosso site, <a href="/en-US/docs/MDN/Kuma">Kuma</a>!</p> - -<ul> - <li><a href="/pt-PT/docs/MDN/Contribute/Howto/Como_converter_exemplos_de_codigo_para_ficarem_live">Converter exemplos de código para ficarem <em>live</em></a> (30 minutos)</li> - <li><a href="https://wiki.mozilla.org/Webdev/GetInvolved/developer.mozilla.org">Read the Getting Involved Guide</a> (30 minutes)</li> - <li><a href="http://kuma.readthedocs.org/en/latest/installation.html">Set up a Kuma build environment</a> (1 hour)</li> - <li><a href="https://github.com/mozilla/kuma#readme">Send your code patch to the Kuma codebase</a> (1 hour)</li> -</ul> - -<h3 id="Opção_3_Eu_gosto_de_palavras_e_código">Opção 3: Eu gosto de palavras e código</h3> - -<p>Nós temos tarefas que requerem competências técnicas e linguísticas, tais como escrever novos artigos, rever para uma correção técnica, ou adaptar documentos.</p> - -<ul> - <li><a href="/en-US/docs/MDN/Contribute/Howto/Tag_JavaScript_pages">Marcar páginas de JavaScript</a> (5 minutos)</li> - <li><a href="/en-US/docs/MDN/About/Promote">Promover a MDN na sua própria página web</a> (5 minutos)</li> - <li><a href="/en-US/docs/MDN/Contribute/Howto/Do_a_technical_review">Revisões técnicas</a> (30 minutos)</li> - <li><a href="/en-US/docs/MDN/Contribute/Howto/Create_and_edit_pages">Escrever um novo artigo sobre um tema com o qual se sente familiarizado</a> (1 hora ou mais)</li> - <li><a href="/en-US/docs/MDN/Contribute/Howto/Create_an_interactive_exercise_to_help_learning_the_web">Criar um exercício interativo para ajudar as pessoas a aprender sobre a web</a> (1 hora ou mais)</li> - <li><a href="/en-US/docs/MDN/Contribute/Howto/Resolve_a_mentored_developer_doc_request">Corrigir um erro de documentação</a> na <a href="http://www.joshmatthews.net/bugsahoy/?mdn=1">Categoria MDN do Bugs Ahoy</a> (1 hora ou mais)</li> -</ul> - -<h3 id="Opção_4_Eu_quero_a_MDN_no_meu_idioma">Opção 4: Eu quero a MDN no meu idioma</h3> - -<p>Todo o trabalho de localização e tradução feito na MDN é elaborado pela nossa incrível comunidade de voluntários.</p> - -<ul> - <li><a href="/pt-PT/docs/MDN/Contribute/Localize/Translating_pages">Traduzir páginas</a> (2 horas) (Ver <a href="/pt-PT/docs/MDN/Doc_status/l10nPrioridade">prioridades de topo</a>)</li> - <li>Interligar com outros localizadores listados nos <a href="/pt-PT/docs/MDN/Contribute/Localize/Projetos_localização">Projetos de Localização</a> (30 minutos)</li> -</ul> - -<h3 id="Opção_5_Eu_encontrei_alguma_informação_errada_mas_não_sei_como_corrigi-la">Opção 5: Eu encontrei alguma informação errada, mas não sei como corrigi-la</h3> - -<p>Pode comunicar problemas, <a class="external" href="https://bugzilla.mozilla.org/form.doc">preenchendo um formulário de erro na documentação</a> (EN) (5 minutos)</p> - -<h2 id="Outras_coisas_que_pode_fazer_na_MDN">Outras coisas que pode fazer na MDN</h2> - -<ul> - <li>Aderir à <a href="/pt-PT/docs/MDN/Comunidade">Comunidade da MDN</a>.</li> - <li><a href="https://developer.mozilla.org/pt-PT/profile">Preencha o seu perfil</a>, assim os outros podem saber mais sobre si.</li> - <li>Saiba mais sobre como <a href="/pt-PT/docs/MDN/Contribute">contribuir para a MDN</a>.</li> -</ul> diff --git a/files/pt-pt/mdn/contribute/howto/convert_code_samples_to_be_live/index.html b/files/pt-pt/mdn/contribute/howto/convert_code_samples_to_be_live/index.html deleted file mode 100644 index 309ae4f848..0000000000 --- a/files/pt-pt/mdn/contribute/howto/convert_code_samples_to_be_live/index.html +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Como converter exemplos de código para ficarem "live" -slug: MDN/Contribute/Howto/Convert_code_samples_to_be_live -tags: - - Como - - Metadados MDN - - Principiante -translation_of: MDN/Contribute/Howto/Convert_code_samples_to_be_live -original_slug: MDN/Contribute/Howto/Como_converter_exemplos_de_codigo_para_ficarem_live ---- -<div>{{MDNSidebar}}</div> - -<p class="summary">MDN tem um sistema de "<a href="/pt-PT/docs/MDN/Contribute/Structures/Exemplos_live">exemplos <em>live</em></a>", onde o exemplo de código é mostrado numa página utilizada diretamente para exibir o resultado desse mesmo exemplo. Contudo, muitos artigos existentes tem exemplos de código que ainda não utilizam este sistema, e precisam de ser convertidos.</p> - -<p><span class="seoSummary">Exemplos <em>live</em>, permitem-lhe ver como é que é o exemplo de destino. Este guia fala sobre como utilizar os exemplos existentes e adicionar a funcionalidade "<em>live</em>" às mesmas.</span></p> - -<dl> - <dt>Onde é que isso precisa de ser feito<strong>?</strong></dt> - <dd>Artigos com a etiqueta <a href="/en-US/docs/tag/NeedsLiveSample">NeedsLiveSample</a></dd> - <dt><strong>O que precisa de saber para realizar a tarefa?</strong></dt> - <dd> - <ul> - <li>Conhecimentos em HTML, CSS e/ou JavaScript, dependendo da amostra de código.</li> - <li>Capacidade de usar macros <a href="/en-US/docs/MDN/Contribute/Tools/KumaScript">KumaScript</a> dentro dos artigos MDN.</li> - </ul> - </dd> - <dd><strong>Quais são os passos para realizar a tarefa?</strong></dd> - <dd> - <ol> - <li>Escolher um artigo da lista de artigos que estão marcados <a href="/en-US/docs/tag/NeedsLiveSample">NeedsLiveSample</a>, onde a amostra de código é para uma funcionalidade com que se sente familiarizado.</li> - <li>Converter a amostra de código para ser "live".</li> - <li>Eliminar qualquer código ou imagem que fosse previamente utilizada para demonstrar o <em>output </em>da amostra.</li> - </ol> - </dd> -</dl> - -<p>Para mais informação sobre a criação e edição de <u>Amostras <em>Live</em></u>, consulte <a href="/pt-PT/docs/MDN/Contribute/Structures/Exemplos_live">Utilizar o sistema de amostra <em>live</em></a></p> diff --git a/files/pt-pt/mdn/contribute/howto/create_and_edit_pages/index.html b/files/pt-pt/mdn/contribute/howto/create_and_edit_pages/index.html deleted file mode 100644 index 310334a95a..0000000000 --- a/files/pt-pt/mdn/contribute/howto/create_and_edit_pages/index.html +++ /dev/null @@ -1,182 +0,0 @@ ---- -title: Como criar e editar páginas -slug: MDN/Contribute/Howto/Create_and_edit_pages -tags: - - Guía - - Introdução - - MDN Meta - - Principiante -translation_of: MDN/Contribute/Howto/Create_and_edit_pages -original_slug: MDN/Contribute/Howto/Criar_e_editar_paginas ---- -<div>{{MDNSidebar}}</div> - -<p><span class="seoSummary">Este artigo introduz novos colaboradores ao processo de editar páginas existentes e criar novas páginas.</span></p> - -<h2 id="Editar_uma_página_existente">Editar uma página existente</h2> - -<p>Para editar uma página:</p> - -<ol> - <li>Clique no botão <strong>Editar</strong> perto do canto superior direito da página.</li> - <li>A página vai recarregar, com uma interface de edição onde podes acrescentar ou apagar informação diretamente.</li> - <li>Acrescente parágrafos, apague texto, insira títulos, e realize outras funções básicas envolvidas em escrever e editar.</li> -</ol> - -<p>Veja o guia do <a href="/en-US/docs/MDN/Contribute/Editor/Basics">Elementos da IU do editor</a>, no <a href="/en-US/docs/MDN/Contribute/Editor">Guia para o editor da IU da MDN</a>, para obter mais informação sobre a utilização do editor incorporado da <strong>MDN</strong>.</p> - -<h3 id="Pré-visualizar_alterações">Pré-visualizar alterações</h3> - -<p>Para ver o aspeto das suas alterações:</p> - -<ul> - <li>Clique no botão <strong>Preview (Pré-visualizar)</strong>, dentro da função de edição na parte superior ou inferior da página.</li> - <li>Isto abre a página de pré-visualização, que mostra as edições numa nova janela ou separador.</li> - <li>De cada vez que carregar neste botão, a página de pré-visualização é atualizada para refletir as alterações mais recentes.</li> -</ul> - -<p>Tenha cuidado! Pré-visualizar uma página <strong>não guarda </strong>o seu progresso. Não feche o separador em que está a editar até ter guardado o seu trabalho.</p> - -<h3 id="Comentário_de_revisão">Comentário de revisão</h3> - -<p>Depois de pré-visualizar as alterações, vai querer <em>guardar a sua revisão</em>. Antes de <strong>guardar</strong>, procure a caixa do comentário de revisão, por baixo da caixa de edição, e deixe um comentário para informar outros colaboradores de porque é que fez alterações. Diga, por exemplo, se acrescentou uma secção nova, mudou algumas palavras para tornar a terminologia mais consistente, reescreveu um parágrafo para esclarecer a linguagem, ou removeu informação redundante.</p> - -<h3 id="Índice">Índice</h3> - -<p>A secção "Neste artigo", é uma lista, gerada automaticamente, de ligações para os títulos numa página. Estes podem ser modificados através dos títulos. Também é possível remover um índice ou reduzir o número de ligações ao selecionar "Editar o Título e Propriedades da Página" e mudar o valor na caixa de seleção "TOC" (Table of contents / Índice).</p> - -<h3 id="Etiquetas_(Tags)">Etiquetas (Tags)</h3> - -<p>Pode adicionar ou remover etiquetas, que descrevem o conteúdo e propósito da página, por baixo da secção de edição. Veja <a href="/en-US/docs/MDN/Contribute/Tagging">Como etiquetar devidamente as páginas</a> para obter informação sobre as etiquetas que deve utilizar.</p> - -<h3 id="Necessita_de_revisão">Necessita de revisão?</h3> - -<p>Se um colaborador perito ou experiente deve rever as suas edições, por favor peça uma revisão técnica (de código, API, ou tecnologias), e/ou uma revisão editorial (de prosa, gramática, e conteúdo), certificando-se de que a caixa adequada tem um visto antes de guardar.</p> - -<h3 id="Anexar_ficheiro">Anexar ficheiro</h3> - -<p>Se pretende <strong>anexar um ficheiro</strong><em> </em>a uma página existente, ou acrescentar uma ilustração para dar melhores esclarecimentos, o mesmo pode ser acrescentado na margem inferiro da página. Quando envia uma imagem, por favor utilize uma ferramente de otimização de imagens para tornar o ficheiro o mais pequeno possível. Desta forma, reduz o tempo de carregamento da página e ajuda o desempenho geral da MDN. Utilize a sua ferramente preferida, se tiver uma; se não, sugerimos <a href="https://tinypng.com/">TinyPNG</a>, uma ferramenta Web acessível.</p> - -<h3 id="Publicar_Descartar_ou_Continuar_a_editar">Publicar, Descartar, ou Continuar a editar</h3> - -<p>Quando termina de editar e está contente com a pré-visualização, publique o seu trabalho e comentários com o botão <em>verde</em> <strong>Publicar</strong>, à direita do título da página, ou no fim da página. Se pretende continuar, clique em <strong>Publicar e cotinuar a editar</strong>, o qual publica as suas alterações e mantém a interface de edição aberta.</p> - -<p>Se mudar de ideias, pode descartar edições com o botão <em>vermelho</em> <strong>Descartar</strong>. Atenção que este botão descarta <em>permanentemente</em>.</p> - -<p>Premir a tecla <strong>Enter</strong> na caixa de Comentário de Revisão é equivalente a clicar em <strong>Publicar e cotinuar a editar</strong>.</p> - -<div class="note"> -<p>Nota: Se tentar guardar, mas as alterações são rejeitas como inválidas, e acha que o conteúdo é apropriado para a MDN, <a href="mailto:mdn-admins@mozilla.com?subject=MDN%3A%20Content%20Rejection%20Appeal&body=%3CDescribe%20the%20content%20you%20were%20trying%20to%20save%20and%20where%20you%20were%20trying%20to%20place%20it.%3E">envie um e-mail à equipa de administração da MDN</a> para obter assistência.</p> -</div> - -<h2 id="Getting_page-creation_permissions">Getting page-creation permissions</h2> - -<p>For security reasons, newly-created accounts don't have the ability to create new pages. If you try to do so, you'll see a page instructing you how to get the page created. There are two options:</p> - -<ul> - <li><strong>Ask for the page to be created for you.</strong> To do this, <a href="https://github.com/mdn/sprints/issues/new?template=issue-template.md&projects=mdn/sprints/2&labels=user-report">file a documentation request issue</a>, with the title "Create page: <page title>". Fill out the URL field of the template with the location on MDN where you'd like the page to go if you know where to place it. In the comment text, include information on why this page needs creating.</li> - <li><strong>Request page creation privileges.</strong> If you request page creation privileges, and they're granted to you, you'll be able to add new pages by following the instructions here. To request these privileges, <a href="mailto:mdn-admins@mozilla.org">email the MDN admin</a> team with your request. Include your username, why you would like to have the ability to create new pages. For instance, you're documenting a new API which involves many new pages, or you'd like to add new terms to the glossary. You should also have made useful contributions to this site's content, and been a contributor for some time. This length of time, and the other factors are collectively considered.</li> -</ul> - -<h2 id="Creating_a_new_page">Creating a new page</h2> - -<p>Once you have page-creation permission, you can begin creating pages.</p> - -<p>If you do not know where to place a new article, <strong>do not worry.</strong> Put it anywhere, we will find it, move to where it belongs, or merge it into existing content. Whatever makes the most sense. Do not worry about making it perfect. We have happy helper gnomes who help to make your content clean and rather luscious.</p> - -<p>There are a few ways to create a new page:</p> - -<ul> - <li><a href="#Missing_page_link">'Missing page' link.</a></li> - <li><a href="#New_page_without_link">New page without a link.</a></li> - <li><a href="#Subpage_of_an_existing_page">A subpage of an existing page.</a></li> - <li><a href="#Clone_of_an_existing_page">Clone of an existing page.</a></li> - <li><a href="#Link_from_an_existing_page">Link from an existing page.</a></li> -</ul> - -<h3 id="'Missing_page'_link">'Missing page' link</h3> - -<p>As with most wikis, it is possible to create a link to a page that is yet to exist. For example, an author might create a list of all the members of an API, before creating the pages for those members. On MDN, links to non-existent pages are typically displayed in red.</p> - -<p>To create a page from a 'missing page' link:</p> - -<ol> - <li>Log into MDN, and have page-creation permission. If not logged in, clicking a 'missing page' link results in a 404 (page not found) error.</li> - <li>Click the 'missing page' link. If you have page creation permission, the <a href="/en-US/docs/MDN/Contribute/Editor">MDN Editor UI</a> opens, ready for you to create the missing page.</li> - <li>Write the content of the page, and save it.</li> -</ol> - -<h3 id="New_page_without_link">New page without link</h3> - -<p><em>To create a new page without linking from another page</em>, enter a unique page name in the URL field of your browser. For example, if you enter:</p> - -<pre class="language-html">https://developer.mozilla.org/en-US/docs/FooBar</pre> - -<p>MDN Creates a new page, with the title "FooBar", opening the editor for you to add new content. Refer to the <a href="#Editing_an_existing_page">Editing an existing page</a> section of this article, for information on how to use the editor mode.</p> - -<p><em>To create a new page without linking from another page</em>:</p> - -<ol> - <li>Log in, and have page-creation permission.</li> - <li>Enter the following in the URL field of your browser:</li> -</ol> - -<pre class="language-html">https://developer.mozilla.org/en-US/docs/new</pre> - -<p>MDN Creates a new page, with a place for a title, opening the editor to add new content to this page. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for information on using editor mode.</p> - -<h3 id="Subpage_of_an_existing_page">Subpage of an existing page</h3> - -<p>To create a page you want to be below an existing page, in the page hierarchy:</p> - -<ol> - <li>On the 'parent' page, click the <strong>Advanced</strong> menu (the gear icon in the toolbar), then click <strong>New sub-page</strong>.</li> - <li>An editor view opens for creating a new document.</li> - <li>Add a title for this document, in the <strong>Title</strong> field.</li> - <li>Change the <strong>Slug</strong> field, if needed. For example, if the title is long, and a shorter URL seems appropriate. This field is automatically filled by the editor, substituting underscores for spaces found in the title, changing only the last part of the URL.</li> - <li>In the <strong>TOC</strong> field, select heading levels you want to be displayed in the table of contents for the page. Or select 'No table of contents', if one is not needed.</li> - <li>Write content of the page in the editor pane, saving your changes. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for further information on using editor mode.</li> -</ol> - -<h3 id="Clone_of_an_existing_page">Clone of an existing page</h3> - -<p>If there is an existing page, whose format you wish to use as a base for your new page, you can 'clone' that page, and then change its content.</p> - -<ol> - <li>On the original page, click the <strong>Advanced</strong> menu (the gear icon in the toolbar), and click <strong>Clone this page</strong>. An editor view opens, for creating a new document.</li> - <li>Change the <strong>Title</strong> of the page, as appropriate for the new content. The <strong>Slug</strong> field is updated automatically as you change the <strong>Title</strong> field.</li> - <li>Change the path portion of the <strong>Slug</strong> field, as needed, to put the new document in a different location in the document hierarchy. In most cases, this is not needed. A cloned page often has similar content to its original, and need to be in a similar location.</li> - <li>In the <strong>TOC</strong> field, select the heading levels you want to be automatically displayed in the table of contents for this page. Or select 'No table of contents', if one is not needed.</li> - <li>Write your content in the editor pane, saving your changes. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for more information on using editor mode.</li> -</ol> - -<h3 id="Link_from_an_existing_page">Link from an existing page</h3> - -<p>This is a bit of a hybrid. You can create a link on another page, then click the link you just inserted, to create the new page:</p> - -<ol> - <li>Enter the name of your new page, anywhere that makes sense in the text of an existing page.</li> - <li>Highlight this new name, and <strong>click the Link icon (<img alt="" src="https://developer.mozilla.org/files/3810/link-icon.png" style="height: 28px; width: 29px;">) </strong>in the editor's toolbar. The <strong>'Update Link'</strong> dialog opens, with the highlighted text in the <strong>'Link To'</strong> field.</li> - <li>"/en-US/docs/" is inserted by default, to the beginning of the URL field.<em> Enter the name </em>of the page after "/en-US/docs/". The page name does not have to be the same as the link text.</li> - <li>Click OK, to create and insert the link.</li> -</ol> - -<p>If the page does not yet exist, the link is displayed in red. If the page <em>does</em> exist, the link is displayed blue. If you want to create a new page, but the page title you desire is already taken, check if it makes sense helping edit and improve the page already there. Otherwise, think of a unique title for your new page, and create a link for it. Refer to <a href="https://developer.mozilla.org/Project:en/Page_Naming_Guide" title="Project:en/Page_Naming_Guide">page naming guide</a> for guidelines.</p> - -<p>To add content to your new page, click on the red link you just created, after saving and closing the editor. The new page opens in editor mode, enabling you to start writing. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for further information on using editor mode.</p> - -<h2 id="Refreshing_page_content">Refreshing page content</h2> - -<p>MDN support of KumaScript macros, and integration of content from other pages can sometimes be hampered by the need for caching of pages, for performance reasons. Pages are built from their source, and this output is cached for future requests. From that moment on, any macros (templates), or integrations (using the macro<span class="templateLink"><code><a href="https://developer.mozilla.org/en-US/docs/Template:Page">Page</a></code></span>), will not reflect later changes made to the macro, its output, or the contents of the integrated material.</p> - -<ul> - <li>To manually update a page, force-refresh your Web browser. MDN detects this, triggering a page rebuild, pulling in updated macro output, and integrating page content.</li> - <li>You can also configure pages to periodically rebuild, automatically. This should not be done unless you expect the page to update frequently. See <a href="/en-US/docs/MDN/Contribute/Tools/Page_regeneration">Page regeneration</a>, for detailed information.</li> -</ul> - -<h2 id="See_also">See also</h2> - -<ul> - <li><a href="/en-US/docs/MDN/Contribute/Editor">MDN editor guide</a></li> - <li><a href="/en-US/docs/MDN/Contribute/Content/Style_guide">MDN style guide</a></li> -</ul> diff --git a/files/pt-pt/mdn/contribute/howto/index.html b/files/pt-pt/mdn/contribute/howto/index.html deleted file mode 100644 index 08ce3855be..0000000000 --- a/files/pt-pt/mdn/contribute/howto/index.html +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Guias de Como... -slug: MDN/Contribute/Howto -tags: - - Landing - - Metadados MDN -translation_of: MDN/Contribute/Howto ---- -<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/pt-PT/docs/MDN")}}</div> - -<p>Estes artigos proporcionam guias passo-a-passo para a realização de objetivos específicos quando contribui para a MDN.</p> - -<p>{{LandingPageListSubpages}}</p> diff --git a/files/pt-pt/mdn/contribute/howto/report_a_problem/index.html b/files/pt-pt/mdn/contribute/howto/report_a_problem/index.html deleted file mode 100644 index 8145a208c9..0000000000 --- a/files/pt-pt/mdn/contribute/howto/report_a_problem/index.html +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Como comunicar um problema na MDN -slug: MDN/Contribute/Howto/Report_a_problem -tags: - - Como... - - Guía - - Metadados MDN -translation_of: MDN/Contribute/Howto/Report_a_problem -original_slug: MDN/Contribute/Howto/Comunicar_um_problema ---- -<div>{{MDNSidebar}}</div> - -<p>De vez em quando, pode encontrar problemas ao utilizar a MDN. Se é um problema com a infra-estrutura do site ou um erro no conteúdo da documentação, pode tentar corrigi-lo ou comunicar o problema. Enquanto o primeiro é o preferido, o último é às vezes o melhor que pode gerir, e isso também está bem.</p> - -<h2 id="Erros_de_documentação_ou_pedidos">Erros de documentação ou pedidos</h2> - -<p>Obviously, since MDN is a wiki, the best thing you can possibly do is fix problems you spot yourself. But maybe you don't know the answer or are in the middle of a deadline on your own project or something, and need to jot down the problem so someone can look at it later.</p> - -<p>As is the case with all things Mozilla, you report a documentation problem by filing a bug. That's when filing a <a href="https://bugzilla.mozilla.org/form.doc">documentation request bug</a> comes in. The documentation request form gathers the information needed to get us started on fixing the issue.</p> - -<p>Of course, our writing community is busy, so sometimes the quickest way to see a documentation problem resolved is to fix it yourself. See <a href="/en-US/docs/MDN/Contribute/Howto/Create_and_edit_pages" title="/en-US/docs/Project:MDN/Contributing/Creating_and_editing_pages">How to create and edit pages</a> for details.</p> - -<h2 id="Erros_bugs_do_site_ou_pedidos_de_funcionalidades">Erros (bugs) do site ou pedidos de funcionalidades</h2> - -<p><a href="/en-US/docs/MDN/Kuma" title="/en-US/docs/Project:MDN/Kuma">Kuma</a>, the Mozilla-developed platform used for the MDN web site, is in a state of continuous development. Our developers—as well as a number of volunteer contributors—are constantly making improvements. If you see a bug, or have a problem with the site, or even have a suggestion for something that could make the software more awesome, you can use the <a href="https://github.com/mdn/kuma/issues/new">Kuma bug form</a> to file a report. You can also use this form to report performance problems with the site, though odds are that performance-monitoring tools have already notified the appropriate people.</p> diff --git a/files/pt-pt/mdn/contribute/howto/tag/index.html b/files/pt-pt/mdn/contribute/howto/tag/index.html deleted file mode 100644 index fe8f43b2c0..0000000000 --- a/files/pt-pt/mdn/contribute/howto/tag/index.html +++ /dev/null @@ -1,376 +0,0 @@ ---- -title: Como etiquetar devidamente as páginas -slug: MDN/Contribute/Howto/Tag -tags: - - Como - - Glossário - - Guía - - Introdução - - Metadados da MDN - - Principiante - - Tutorial - - contribuir -translation_of: MDN/Contribute/Howto/Tag -original_slug: MDN/Contribute/Howto/Etiqueta ---- -<div>{{MDNSidebar}}</div> - -<p class="summary">As <strong><em>tags</em> de artigo</strong> são uma maneira importante de colocar os visitantes em contacto com conteúdo útil. Cada página normalmente deverá ter várias <em>tags</em> para ajudar a manter o conteúdo organizado. Esta página explica a melhor maneira para etiquetar as páginas, e assim os nossos leitores podem encontrar a informação e nós podemos manter-nos organizados.</p> - -<p>Para obter ajuda com a interface do utilizador para editar <em>tags</em>, consulte a <a href="/pt-PT/docs/MDN/Contribute/Editor/Basicos">secção de etiquetagem</a> no nosso guia do editor.</p> - -<p>Por favor, utilize as <em>tags</em> devidamente como explicado em baixo. Se não o fizer, as nossas ferramentas automatizadas não irão gerar corretamente as listas de conteúdo, as páginas de destino, e ligação dos artigos.</p> - -<h2 id="Como_é_que_a_MDN_utiliza_as_tags_etiquetas">Como é que a MDN utiliza as <em>tags </em>(etiquetas) </h2> - -<p>As <em>tags</em> são utilizadas de vários modos na MDN:</p> - -<dl> - <dt>Categorização do documento</dt> - <dd>What type of document is it? Is it a reference? A tutorial? A landing page? Our visitors can use these tags to filter searches, so they're really important!</dd> - <dt>Identificação do tópico</dt> - <dd>What is the article about? Is it about an API? The DOM? Graphics? Again, these tags are important because they can filter searches.</dd> - <dt>Estado da tecnologia</dt> - <dd>What's the status of the technology? Is it non-standard? Obsolete or deprecated? Experimental?</dd> - <dt>Nível de proficiência</dt> - <dd>For tutorials and guides, how advanced is the material covered by the article?</dd> - <dt>Metadados do documento</dt> - <dd>The writing community uses tags to keep track of which pages need what kind of work.</dd> -</dl> - -<h2 id="Guia_do_tipo_de_tag">Guia do tipo de <em>tag</em></h2> - -<p>Here's a quick guide to the types of tags and possible values for them.</p> - -<h3 id="Categoria_do_documento">Categoria do documento</h3> - -<p>When you tag an article with one of these categories, you help the automated tools more accurately generate landing pages, tables of contents, and so on. Our new search system will also use these terms so that our visitors can locate reference or guide information at will.</p> - -<p>We use the following category names as standard tagging terms:</p> - -<dl> - <dt><code>{{Tag("Intro")}}</code></dt> - <dd>The article provides introductory material about a topic. Ideally each technology area should have only one "Intro".</dd> - <dt><code>{{Tag("Featured")}}</code></dt> - <dd>The article is critical and will display prominently on landing pages. Use this tag sparingly (never more than three documents in each documentation area).</dd> - <dt><code>{{Tag("Reference")}}</code></dt> - <dd>The article contains reference material about an API, element, attribute, property, or the like.</dd> - <dt><code>{{Tag("Landing")}}</code></dt> - <dd>The page is a landing page.</dd> - <dt><code>{{Tag("Guide")}}</code></dt> - <dd>The article is a how-to or guide page.</dd> - <dt><code>{{Tag("Example")}}</code></dt> - <dd>The article is a code sample page, or has code samples (that is, actual snippets of useful code, not one-line "syntax examples").</dd> -</dl> - -<h3 id="Tópico">Tópico</h3> - -<p>By identifying the article's topic area, you are helping generate better search results (and landing pages and navigation as well).</p> - -<p>While there's some room for flexibility here as we identify new topic areas, we try to limit ourselves to the names of APIs or technologies. Some useful examples:</p> - -<ul> - <li><code>{{Tag("HTML")}}</code></li> - <li><code>{{Tag("CSS")}}</code></li> - <li><code>{{Tag("JavaScript")}}</code> (notice the capital "S"!)</li> - <li><code>{{Tag("Document")}}</code></li> - <li><code>{{Tag("DOM")}}</code></li> - <li><code>{{Tag("API")}}</code> for each interface, method and property.</li> - <li><code>{{Tag("Method")}}</code> for each method of an API</li> - <li><code>{{Tag("Property")}}</code> for each property of an API</li> - <li><code>{{Tag("Graphics")}}</code></li> - <li><code>{{Tag("SVG")}}</code></li> - <li><code>{{Tag("WebGL")}}</code></li> - <li><code>{{Tag("Tools")}}</code></li> - <li><code>{{Tag("Web")}}</code></li> - <li><code>{{Tag("Element")}}</code></li> - <li><code>{{Tag("Extensions")}}</code> and <code>{{Tag("WebExtensions")}}</code> for WebExtension documentation.</li> -</ul> - -<p>In general, your topic identification tag should be the name of an interface with a number of related pages (like <a href="/en-US/docs/Web/API/Node" title="/en-US/docs/Web/API/Node">Node</a>, which has many pages for its various properties and methods), or the name of an overall technology type. You might tag a page about WebGL with <code>Graphics</code> and <code>WebGL</code>, for example, but a page about {{HTMLElement("canvas")}} with <code>HTML</code>, <code>Element</code>, <code>Canvas</code>, and <code>Graphics</code>.</p> - -<h4 id="Conteúdo_específico_da_Mozilla">Conteúdo específico da Mozilla</h4> - -<p>Estas <em>tags</em> são utilizadas apenas no conteúdo especifico da Mozilla:</p> - -<ul> - <li><code>{{Tag("Mozilla")}}</code></li> - <li><code>{{Tag("Firefox")}}</code></li> - <li><code>{{Tag("Firefox OS")}}</code></li> - <li><code>{{Tag("Gecko")}}</code></li> - <li><code>{{Tag("XUL")}}</code></li> - <li><code>{{Tag("XPCOM")}}</code></li> -</ul> - -<h3 id="Identificação_de_API">Identificação de API</h3> - -<p>Within the API reference, each article should identify which part of the API it covers:</p> - -<dl> - <dt><code>{{tag("Interface")}}</code></dt> - <dd>The main article for an interface should have this tag. For example, {{domxref("RTCPeerConnection")}}.</dd> - <dt><code>{{tag("Constructor")}}</code></dt> - <dd>Each interface may have up to one page tagged "Constructor"; this is the interface's constructor. The page should have the same name as the interface, like {{domxref("RTCPeerConnection.RTCPeerConnection()")}}.</dd> - <dt><code>{{tag("Property")}}</code></dt> - <dd>Every article describing a particular property within an interface needs this tag. See {{domxref("RTCPeerConnection.connectionState")}}, for example.</dd> - <dt><code>{{tag("Method")}}</code></dt> - <dd>Each article documenting an interface method needs this tag. See {{domxref("RTCPeerConnection.createOffer()")}} for example.</dd> -</dl> - -<p>In addition, the reference pages need to include interface, property, and method names among their tags. Some examples:</p> - -<dl> - <dt>The interface {{domxref("RTCPeerConnection")}}</dt> - <dd>Include the tag "RTCPeerConnection" along with the other relevant tags ("Interface", "WebRTC", "WebRTC API", "API", "Reference", and so forth).</dd> - <dt>The method {{domxref("RTCPeerConnection.createOffer()")}}</dt> - <dd>Include the tags "RTCPeerConnection" and "createOffer" (note <em>no</em> parentheses in tag names!) along with the other relevant tags, including "WebRTC", "WebRTC API", "API", "Reference", and so forth. Consider including things like "Offer" and "SDP", which are also relevant here.</dd> - <dt>The property {{domxref("RTCPeerConnection.iceConnectionState")}}</dt> - <dd>Include the tags "RTCPeerConnection" and "iceConnectionState" along with the other relevant tags, including "WebRTC", "WebRTC API", "API" and "Reference". Also consider including "ICE".</dd> -</dl> - -<h3 id="Estado_da_tecnologia">Estado da tecnologia</h3> - -<p>To help the reader understand how viable a technology is, we use tags to label pages as to the status of the technology's specification. This isn't as detailed as actually explaining what the spec is and how far the technology has come in the specification process (that's what the Specifications table is for), but it helps the reader judge, at a glance, whether it's a good idea to use the technology described in the article.</p> - -<p>Here are possible values for these tags:</p> - -<dl> - <dt><code>{{Tag("Read-only")}}</code></dt> - <dd>Apply this tag to reference pages which describe a property or attribute which is read-only.</dd> - <dt><code>{{Tag("Non-standard")}}</code></dt> - <dd>Indicates that the technology or API described on the page is not part of a standard, whether it's stable or not in any browsers which implement it (if it's not stable, it should also be {{Tag("Experimental")}}). If you don't use this tag, your readers will assume the technology is standard. The compatibility table on the page should clarify which browser(s) support this technology or API.</dd> - <dt><code>{{Tag("Deprecated")}}</code></dt> - <dd>The technology or API covered on the page is marked as deprecated in the specification, and is likely to eventually be removed, but is generally still available in current versions of browsers.</dd> - <dt><code>{{Tag("Obsolete")}}</code></dt> - <dd>The technology or API has been deemed obsolete and has been removed (or is actively being removed) from all or most current browsers.</dd> - <dt><code>{{Tag("Experimental")}}</code></dt> - <dd>The technology is not standardized, and is an experimental technology or API that may or may not ever become part of a standard. It is also subject to change in the browser engine (typically only one) that implements it. If the technology isn't part of any specification (even in draft form), it should also have the {{tag("Non-standard")}} tag.</dd> - <dt><code>{{Tag("Needs Privileges")}}</code></dt> - <dd>The API requires privileged access to the device on which the code is running.</dd> - <dt><code>{{Tag("Certified Only")}}</code></dt> - <dd>The API only works in certified code.</dd> -</dl> - -<p>These tags are no excuse to leave out the <a href="/en-US/docs/Project:Compatibility_tables">compatibility table</a> in your article! That should always be present.</p> - -<h3 id="Nível_de_competência_técnica">Nível de competência técnica</h3> - -<p>Use the skill-level tag type only for guides and tutorials (that is, pages tagged <code>Guide</code>) to help users choose tutorials based on how familiar they are with a technology. There are three values for this:</p> - -<dl> - <dt><code>{{Tag("Beginner")}}</code></dt> - <dd>Articles designed to introduce the reader to a technology they've never used or have only a passing familiarity with.</dd> - <dt><code>{{Tag("Intermediate")}}</code></dt> - <dd>Articles for users who have gotten started with the technology but aren't experts.</dd> - <dt><code>{{Tag("Advanced")}}</code></dt> - <dd>Articles about stretching the capabilities of a technology and of the reader.</dd> -</dl> - -<h3 id="Metadados_de_documento">Metadados de documento</h3> - -<p>The writing community uses tags to label articles as requiring specific types of work. Here's a list of the ones we use most:</p> - -<dl> - <dt><code>{{Tag("Draft")}}</code></dt> - <dd>The article is not complete, and is at least in theory still actively being updated (although it's also possible it's been forgotten about). Try to check with the most recent contributors before making changes, in order to avoid potential content collisions.</dd> - <dt><code>{{Tag("NeedsCompatTable")}}</code></dt> - <dd>The article needs a table to specify compatibility of a feature across browsers. <a href="/en-US/docs/MDN/Contribute/Structures/Compatibility_tables">See here</a> for a guide on contributing to browser compatibility.</dd> - <dt><code>{{Tag("NeedsContent")}}</code></dt> - <dd>The article is a stub, or is otherwise lacking information. This tag means that someone should review the content and add more details and/or finish writing the article.</dd> - <dt><code>{{Tag("NeedsExample")}}</code></dt> - <dd>The article needs one or more examples created to help illustrate the article's point. These examples should use the <a href="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples">live sample system</a>.</dd> - <dt><code>{{Tag("NeedsLiveSamples")}}</code></dt> - <dd>The article has one or more examples that need to be updated to use the <a href="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples">live sample system</a>.</dd> - <dt><code>{{Tag("NeedsSpecTable")}}</code></dt> - <dd>The article needs a table to indicate on which specification document(s) the feature was defined.</dd> - <dt><code>{{Tag("NeedsUpdate")}}</code></dt> - <dd>The content is out of date and needs to be updated.</dd> - <dt><code>{{Tag("l10n:exclude")}}</code></dt> - <dd>The content is not really worth localizing and will not appear on localization status pages.</dd> - <dt><code>{{Tag("l10n:priority")}}</code></dt> - <dd>The content is important and should be marked as a priority for MDN translators. Shows up in an extra priority table on localization status pages.</dd> -</dl> - -<h2 id="Unindo_tudo">Unindo tudo</h2> - -<p>Portanto, para cada página que atribui <em>tags</em> de vários tipos de <em>tag</em>, por exemplo:</p> - -<dl> - <dt>A tutorial about WebGL for beginners</dt> - <dd><code>WebGL</code>, <code>Graphics</code>, <code>Guide</code>, <code>Beginner</code></dd> - <dt>Reference page for {{HTMLElement("canvas")}}</dt> - <dd><code>Canvas</code>, <code>HTML</code>, <code>Element</code>, <code>Graphics,</code> <code>Reference</code></dd> - <dt>A landing page for Firefox OS developer tools</dt> - <dd><code>Tools</code>, <code>Firefox OS</code>, <code>Landing</code></dd> -</dl> - -<h2 id="Filtros_de_tag_e_pesquisa">Filtros de <em>tag </em>e pesquisa</h2> - -<p>Search filters won't work properly unless we tag MDN pages properly. Here's a table of search filters and which tags they look for.</p> - -<div class="note"> -<p><strong>Nota:</strong> If multiple tags are listed under "Tag name," that means any one or more of these tags must be present for the article to match.</p> -</div> - -<table class="standard-table"> - <thead> - <tr> - <th scope="col">Grupo de filtro</th> - <th scope="col">Nome do filtro de pesquisa</th> - <th scope="col">Nome da <em>tag</em></th> - </tr> - </thead> - <tbody> - <tr> - <th rowspan="22" scope="row" style="vertical-align: baseline;">Tópico</th> - <td>APIs and DOM</td> - <td>{{Tag("API")}} || {{Tag("DOM")}} {{Deprecated_Inline}}</td> - </tr> - <tr> - <td>Add-ons & Extensions {{Deprecated_Inline}}</td> - <td>{{Tag("Add-ons")}} || {{Tag("Extensions")}} || {{Tag("Plugins")}} || {{Tag("Themes")}} || {{Tag("WebExtensions")}}</td> - </tr> - <tr> - <td>CSS</td> - <td>{{Tag("CSS")}}</td> - </tr> - <tr> - <td>Canvas</td> - <td>{{Tag("Canvas")}}</td> - </tr> - <tr> - <td>Firefox</td> - <td>{{Tag("Firefox")}}</td> - </tr> - <tr> - <td>Firefox OS</td> - <td>{{Tag("Firefox OS")}}</td> - </tr> - <tr> - <td>Games</td> - <td>{{Tag("Games")}}</td> - </tr> - <tr> - <td>HTML</td> - <td>{{Tag("HTML")}}</td> - </tr> - <tr> - <td>HTTP</td> - <td>{{Tag("HTTP")}}</td> - </tr> - <tr> - <td>JavaScript</td> - <td>{{Tag("JavaScript")}}</td> - </tr> - <tr> - <td>Marketplace {{Non-standard_Inline}}</td> - <td>{{Tag("Marketplace")}}</td> - </tr> - <tr> - <td>MathML</td> - <td>{{Tag("MathML")}}</td> - </tr> - <tr> - <td>Mobile</td> - <td>{{Tag("Mobile")}}</td> - </tr> - <tr> - <td>Open Web Apps {{Non-standard_Inline}}</td> - <td>{{Tag("Apps")}}</td> - </tr> - <tr> - <td>SVG</td> - <td>{{Tag("SVG")}}</td> - </tr> - <tr> - <td>Web Development</td> - <td>{{Tag("Web Development")}}</td> - </tr> - <tr> - <td>Web Standards</td> - <td>{{Tag("Web")}}</td> - </tr> - <tr> - <td>WebExtensions</td> - <td>{{Tag("WebExtensions")}}</td> - </tr> - <tr> - <td>WebGL</td> - <td>{{Tag("WebGL")}}</td> - </tr> - <tr> - <td>Writing Documentation</td> - <td>{{Tag("MDN Meta")}}</td> - </tr> - <tr> - <td>XPCOM {{Non-standard_Inline}}</td> - <td>{{Tag("XPCOM")}}</td> - </tr> - <tr> - <td>XUL {{Non-standard_Inline}}</td> - <td>{{Tag("XUL")}}</td> - </tr> - <tr> - <th rowspan="3" scope="row" style="vertical-align: baseline; white-space: nowrap;">{{anch("Skill level")}}</th> - <td>I'm an Expert</td> - <td>{{Tag("Advanced")}}</td> - </tr> - <tr> - <td>Intermediate</td> - <td>{{Tag("Intermediate")}}</td> - </tr> - <tr> - <td>I'm Learning</td> - <td>{{Tag("Beginner")}}</td> - </tr> - <tr> - <th rowspan="7" scope="row" style="vertical-align: baseline; white-space: nowrap;">Tipo de documento</th> - <td>Docs</td> - <td><em>This restricts the search to docs content, leaving out Hacks and other MDN content.</em></td> - </tr> - <tr> - <td>Demos</td> - <td><em>This includes Demo Studio content in the search results.</em></td> - </tr> - <tr> - <td>Tools</td> - <td>{{Tag("Tools")}}</td> - </tr> - <tr> - <td>Code Samples</td> - <td>{{Tag("Example")}}</td> - </tr> - <tr> - <td>How-To & Tutorial</td> - <td>{{Tag("Guide")}}</td> - </tr> - <tr> - <td>Developer Profiles</td> - <td><em>This includes developer profiles from the MDN site in the search results.</em></td> - </tr> - <tr> - <td>External Resources</td> - <td><em>The dev team is still figuring this out...</em></td> - </tr> - </tbody> -</table> - -<h2 id="Problemas_de_etiquetagem_que_pode_corrigir">Problemas de etiquetagem que pode corrigir</h2> - -<p>There are several kinds of tag problems you can help fix:</p> - -<dl> - <dt>No tags</dt> - <dd>Generally articles should have at <em>least</em> a "{{anch("Document category", "category")}}" tag and a "{{anch("Topic", "topic")}}" tag. Usually other tags are appropriate as well, but if you can help us ensure that the minimum tags are present, you'll be a documentation hero!</dd> - <dt>Tags that don't follow our tagging standards</dt> - <dd>Please fix any documents whose tags don't follow the standards on this page.<br> - Note that you may occasionally see some localized tags (such as <code>Référence</code>) showing up on some English pages. This was due to a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=776048">bug in Kuma</a>, which caused the tags to reappear even if they were deleted. That bug has <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=776048#c37">since been fixed</a>, so any remaining localized tags can be cleaned up if they're spotted.</dd> - <dt>Incorrect tags</dt> - <dd>If you're looking at an article about HTML and it's tagged "JavaScript", that's probably wrong! Likewise, if an article discusses Mozilla internals but has a "Web" tag, that's probably wrong too. Remove these tags and add the right tags if they aren't already there. Please also correct misspelled tags (e.g., "Javascript" will still match, since tags are case-insensitive, but let's not be sloppy!).</dd> - <dt>Missing tags</dt> - <dd>If an article has some but not all of the tags it needs, feel free to add more. For example, if a page in JavaScript reference is (correctly) tagged "JavaScript" but nothing else, you're invited to tag the page "Reference" as well!</dd> - <dt>Tag spam</dt> - <dd>This insidious beast is the most revolting tag problem of all: some Web vermin has deposited its droppings in the page tags (like "Free warez!" or "Hey I was browsing your site and wanted to ask you if you could help me solve this problem I'm having with Flash crashing all the time"). We've got to delete these right away! They're ugly, they're hard to manage if they're allowed to linger too long, and they're terrible for {{Glossary("SEO")}}.</dd> -</dl> - -<p>If you see one (or more) of these problems, please <a href="/en-US/docs/Project:MDN/Contributing/Getting_started#Logging_into_MDN">log into MDN</a> and click EDIT at the top right of the MDN window. Once the editor loads up, scroll down to the bottom of the page, where you'll see the tag box. For more details on the tagging interface, see "<a href="/en-US/docs/Project:MDN/Contributing/Editor_guide#The_tags_box">The tags box</a>" in the <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide">MDN editor guide</a>.</p> diff --git a/files/pt-pt/mdn/contribute/howto/write_a_new_entry_in_the_glossary/index.html b/files/pt-pt/mdn/contribute/howto/write_a_new_entry_in_the_glossary/index.html deleted file mode 100644 index 4284498481..0000000000 --- a/files/pt-pt/mdn/contribute/howto/write_a_new_entry_in_the_glossary/index.html +++ /dev/null @@ -1,115 +0,0 @@ ---- -title: Como escrever e referenciar uma entrada no glossário -slug: MDN/Contribute/Howto/Write_a_new_entry_in_the_Glossary -tags: - - Como... - - Glossário - - Guia(2) - - Metadados da MDN -translation_of: MDN/Contribute/Howto/Write_a_new_entry_in_the_Glossary -original_slug: MDN/Contribute/Howto/Como_escrever_uma_nova_entrada_no_Glossario ---- -<div>{{MDNSidebar}}</div> - -<p>O <a href="/pt-PT/docs/Gloss%C3%A1rio">glossário</a> da MDN é o local onde nós definimos toda a terminologia, gíria, e abreviações utilizadas na documentação e programação. Contribuir para o glossário é uma maneira simples de tornar a Web mais fácil para todos entenderem. Você não precisa de um alto nível de habilidade técnica para escrever entradas de glossário porque elas devem permanecer simples e diretas.</p> - -<h2 id="Como_escrever_uma_entrada">Como escrever uma entrada</h2> - -<p>Se você está procurando por tópicos que precisam de uma entrada de glossário, verifique a lista de termos não documentados no final da página de destino do Glossário; clique em qualquer um desses links para iniciar uma nova página do Glossário para o item que você clicou; então siga os passos abaixo.</p> - -<p>Se você tem uma ideia para um nova entrada de glossário, basta abrir o botão em uma nova aba, e então siga os passos abaixo do botão.</p> - -<p></p><div class="align-center"><a class="button ignore-external mega positive" href="/pt-PT/docs/new?parent=4391">Adicionar Nova Entrada ao Glossário<div></div></a></div><p></p> - -<p> </p> - -<h3 id="Passo_1_Escreva_um_resumo">Passo 1: Escreva um resumo</h3> - -<p>The first paragraph of any glossary page is a simple and short description of the term (preferably no more than two sentences). Make sure anyone reading the description can understand the defined term immediately.</p> - -<div class="note"> -<p><strong>Nota:</strong> Please don't copy-and-paste definitions from elsewhere (especially not Wikipedia, since its range of license versions is smaller, and thus incompatible with that of MDN). It's really important to make sure this content is simple and easy to understand. It's worth spending some time on it rather than stealing content blindly. This glossary should be useful new content, not repeating things from elsewhere.</p> -</div> - -<p>Links to the glossary entry will use these summaries inside their tooltips, so that readers can see the definitions without navigating away from the page they're on. (See below how to insert links to glossary entries with the \{{Glossary}} macro.)</p> - -<p>If you must, you can add a few extra paragraphs, but it's very easy to find yourself writing a whole article. Writing a whole article is fine, but please don't put it in the glossary. If you aren't sure where to put your article, feel free to <a href="/en-US/docs/MDN/Community#Join_our_mailing_lists">reach out to discuss it</a>.</p> - -<h3 id="Passo_2_Expanda_com_hiperligações">Passo 2: Expanda com hiperligações</h3> - -<p>Finally, a glossary entry should always end with a "Learn more" section. This section should contain links to help the reader move forward: discovering more details, learning to use the relevant technology, and so on.</p> - -<p>We recommend that you sort the links into at least these three groups:</p> - -<dl> - <dt>Conhecimento geral</dt> - <dd>Links that provide more general information; for example, a link to <a href="https://pt.wikipedia.org/wiki/Wikip%C3%A9dia:P%C3%A1gina_principal">Wikipedia</a> is a good starting point.</dd> - <dt>Referência técnica</dt> - <dd>Links to more in-depth technical information, on MDN or elsewhere.</dd> - <dt>Saber sobre a mesma</dt> - <dd>Hiperligações para tutoriais, exercícios, quaisquer outros materiais que ajudem o leitor a saber como utilizar a tecnologia por de trás do termo definido.</dd> -</dl> - -<h2 id="Termos_sugeridos">Termos sugeridos</h2> - -<p>So you want to contribute but you don't know which terms need to be defined? <a href="https://developer.mozilla.org/en-US/docs/Glossary#Contribute_to_the_glossary">Here's</a> a list of suggestions. Click one and get started!</p> - -<h2 id="Lidar_com_a_desambiguação">Lidar com a desambiguação</h2> - -<p>Sometimes, a term has several meanings depending on the context. To resolve the ambiguities, you must follow those guidelines:</p> - -<ul> - <li>The term's main page must be a disambiguation page containing the {{TemplateLink("GlossaryDisambiguation")}} macro.</li> - <li>The term has subpages that define the term for a given context.</li> -</ul> - -<p>Let's illustrate that with an example. The term <em>signature</em> can have different meanings in at least three different contexts: <em>security</em>, <em>function</em> and <em>email</em>.</p> - -<ol> - <li>A página de <a href="/pt-PT/docs/Gloss%C3%A1rio/Assinatura">Glossário/Assinatura</a> é a página de desambiguação como a {{TemplateLink("GlossaryDisambiguation")}} macro.</li> - <li>The page <a href="/en-US/docs/Glossary/Signature/Security">Glossary/Signature/Security</a> is the page defining a signature in a security context.</li> - <li>The page <a href="/en-US/docs/Glossary/Signature/Function">Glossary/Signature/Function</a> is the page defining a function signature.</li> - <li>The page <a href="/en-US/docs/Glossary/Signature/Email">Glossary/Signature/Email</a> is the page defining email signature.</li> -</ol> - -<h2 id="Como_utilizar_a_macro_Glossary">Como utilizar a macro \{{Glossary}}</h2> - -<p>The glossary is much more useful when people can access the definitions from another document without navigating away from what they're reading. Therefore we urge you to link to the glossary whenever you can, using the {{TemplateLink("Glossary")}} macro:</p> - -<table class="standard-table"> - <thead> - <tr> - <th scope="col">Macro</th> - <th scope="col">Resultado</th> - <th scope="col">Nota</th> - </tr> - </thead> - <tbody> - <tr> - <td>\{{Glossary("browser")}}</td> - <td>{{Glossary("browser")}}</td> - <td>When a text matches the term to be defined, just use the macro as is (it's case insensitive)</td> - </tr> - <tr> - <td>\{{Glossary("browser", "Web browser")}}</td> - <td>{{Glossary("browser","Web browser")}}</td> - <td>To display an alternative text, use the second argument to specify that text</td> - </tr> - <tr> - <td>\{{Glossary("browser", "Web browser", 1)}}</td> - <td>{{Glossary("browser","Web browser",1)}}</td> - <td>Specify <code>1</code> as an optional third argument to display the link as a regular link rather than a subtle hint</td> - </tr> - </tbody> -</table> - -<p>Links created with the \{{Glossary}} macro always display a tooltip containing the glossary entry's summary paragraph.</p> - -<h3 id="Utilização_das_linhas_diretrizes">Utilização das linhas diretrizes</h3> - -<p>In many cases, it's perfectly safe to use that macro everywhere on MDN. However, there are a few cases you should handle with care:</p> - -<ul> - <li>If a term is already linked to another part of MDN, leave it that way and do not use the \{{Glossary}} macro.</li> - <li>Within an article section, use the \{{Glossary}} macro only once for the same term (<em>hint: a section always starts with a title</em>).</li> -</ul> diff --git a/files/pt-pt/mdn/contribute/howto/write_an_api_reference/sidebars/index.html b/files/pt-pt/mdn/contribute/howto/write_an_api_reference/sidebars/index.html deleted file mode 100644 index 63a34dd7fe..0000000000 --- a/files/pt-pt/mdn/contribute/howto/write_an_api_reference/sidebars/index.html +++ /dev/null @@ -1,110 +0,0 @@ ---- -title: Barras laterais de referência da API -slug: MDN/Contribute/Howto/Write_an_API_reference/Sidebars -tags: - - API - - Guía - - Referencia - - barras laterais - - groupdata - - onboarding -translation_of: MDN/Structures/API_references/API_reference_sidebars -original_slug: MDN/Structures/API_references/Barras_laterais_de_referencia_da_API ---- -<div>{{MDNSidebar}}</div><p class="summary">Pode incluir uma barra lateral personalizada nas páginas de referência da API para exibir as hiperligações para as 'Interfaces' relacionadas, tutoriais, e outros recursos relevantes, apenas para essa API. Este artigo explica como.</p> - -<h2 id="O_que_precisa_de_fazer">O que precisa de fazer?</h2> - -<p>You need to take the following three steps to create your API sidebar:</p> - -<ol> - <li>Create your API reference pages.</li> - <li>Add an entry for your particular API into the <a href="https://github.com/mdn/kumascript">KumaScript repo</a>'s GroupData.json data file.</li> - <li>Use the \{{APIRef}} macro to insert the sidebar into each page you want to display it on.</li> -</ol> - -<p>Let's run through each of these steps in turn. The example we'll refer to in this article is the <a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a>.</p> - -<h3 id="Criar_páginas_de_referência_da_sua_API">Criar páginas de referência da sua API</h3> - -<p>Before you can add sidebars to your pages, you'll need to create the pages themselves (see our <a href="/en-US/docs/MDN/Contribute/Structures/API_references/What_does_an_API_reference_need">What does an API reference need?</a> guide for more guidance).</p> - -<h3 id="Adicionar_uma_entrada_para_GroupData.json">Adicionar uma entrada para GroupData.json</h3> - -<p>The <a href="https://github.com/mdn/kumascript/blob/master/macros/GroupData.json">GroupData.json</a> file holds all the data relating to what links should appear in API reference sidebars. When invoked, the \{{APIRef}} macro takes an API name given to it as a parameter, looks up that name in GroupData.json, builds a sidebar as appropriate, and inserts it in the page.</p> - -<p>To add an entry to GroupData.json, you need to:</p> - -<ol> - <li>Make sure you have a <a href="https://github.com/">GitHub</a> account.</li> - <li>Fork the KumaScript repo, create a new branch to contain your changes, and clone the repo locally.</li> - <li>Checkout your new branch before starting work, and make sure you push changes to it after finishing.</li> - <li>Create a pull request so that the MDN team can review your work, and ask for changes if necessary.</li> -</ol> - -<p>If you need help with using GitHub, a more detailed guide can be found at our <a href="/en-US/docs/MDN/Contribute/Structures/Compatibility_tables#The_new_way_The_browser_compat_data_repo_and_dynamic_tables">compatibility tables guide</a>.</p> - -<p>The <a href="https://github.com/mdn/kumascript/blob/master/macros/GroupData.json">GroupData.json</a> file can be found inside the macros directory of the KumaScript repo. Looking at it, you'll see a giant JSON structure, with each API having its own member. The name is the API name, and the value is an object containing several submembers defining the sidebar links to be created.</p> - -<p>For example, look at the <a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a> page on MDN. The corresponding entry in GroupData.json looks like this:</p> - -<pre class="brush: json notranslate">"Fetch API": { - "overview": [ "Fetch API"], - "interfaces": [ "Body", - "Headers", - "Request", - "Response", - "FetchController", - "FetchObserver", - "FetchSignal", - "ObserverCallback" ], - "methods": [ "WindowOrWorkerGlobalScope.fetch()" ], - "properties": [], - "events": [] -},</pre> - -<p>As you can see, we've used "Fetch API" for the name, and inside the object value we include a number of submembers.</p> - -<h4 id="Submembers_to_include_inside_a_GroupData_entry">Submembers to include inside a GroupData entry</h4> - -<p>This section lists all the submembers you could include in a GroupData entry.</p> - -<p>Note that Most of the values included inside the listed submembers equate to both the link text, and slugs appended to the end of the main API index page — https://developer.mozilla.org/<em><language-code></em>/docs/Web/API — to create the final URL for the displayed link. So for example, "Body" will result in a link being created like so in the <em>en-US</em> locale:</p> - -<pre class="brush: html notranslate"><li><a href="https://developer.mozilla.org/en-US/docs/Web/API">Body</a></li></pre> - -<p>There are a few exceptions. For example the "guides" submember contains one or more sets of link information (title and slug) that defines links to associated guides/tutorials. In this case the slugs are appended to the end of the MDN docs root — https://developer.mozilla.org/<em><language-code></em>/docs — allowing an article anywhere on MDN to be included.</p> - -<p>Here are the available members. In each case, an example is included that assumes that the local is <em>en-US</em>.</p> - -<ol> - <li> - <p>"overview" — the value is an array, inside of which you include the slug of the API overview page, if there is one. "Fetch API" results in a link being made to <a href="/en-US/docs/Web/API/Fetch_API">https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API</a>.</p> - </li> - <li> - <p>"interfaces" — the value is an array in which you should list all of the interfaces that form part of that API. "Body" results in a link being made to <a href="/en-US/docs/Web/API/Body">https://developer.mozilla.org/en-US/docs/Web/API/Body</a>.</p> - </li> - <li> - <p>"methods" — the value is an array that should contain all of the methods associated with the API. This can include methods that are members of interfaces defined in the API spec, and methods the API defines on other interfaces. If there are a huge number of methods, you might want to consider only listing the most popular ones, or putting them first in the list. "WindowOrWorkerGlobalScope.fetch()" results in a link being made to <a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/fetch">https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/fetch</a>.</p> - </li> - <li> - <p>"properties" — the value is an array that should contain all of the properties associated with the API. This can include properties that are members of interfaces defined in the API spec, and properties the API defines on other interfaces. If there are a huge number of properties, you might want to consider only listing the most popular ones, or putting them first in the list. "Headers.append" results in a link being made to <a href="/en-US/docs/Web/API/Headers/append">https://developer.mozilla.org/en-US/docs/Web/API/Headers/append</a>.</p> - </li> - <li> - <p>"events" — the value is an array that should contain all of the events associated with the API, defined in the API spec, or elsewhere. If there are a huge number of events, you might want to consider only listing the most popular ones, or putting them first in the list. "animationstart" results in a link being made to <a href="/en-US/docs/Web/Events/animationstart">https://developer.mozilla.org/en-US/docs/Web/Events/animationstart</a>.</p> - </li> - <li> - <p>"guides" — the value is an array containing one or more objects that define links to guides explain how to use the API. Each object contains two submembers — "url", which contains the partial URL pointing to the guide article, and "title", which defines the link test for the link. As an example, the following object:</p> - - <pre class="brush: json notranslate">{ "url": "/docs/Web/API/Detecting_device_orientation", -"title": "Detecting device orientation" }</pre> - - <p>Creates a link with the title "Detecting device orientation", which points to <a href="/en-US/docs/Web/API/Detecting_device_orientation">https://developer.mozilla.org/en-US/docs/Web/API/Detecting_device_orientation</a>.</p> - </li> -</ol> - -<h3 id="Inserir_a_barra_lateral_nas_suas_páginas">Inserir a barra lateral nas suas páginas</h3> - -<p>Once you've added an entry for your API into GroupData.json, submitted it as a pull request and had the change accepted into the main repo, you can include it in your API reference pages using the \{{APIRef}} macro, which takes the name you used for your API in GroupData as a parameter. As an example, the <a href="/en-US/docs/Web/API/WebVR_API">WebVR API</a>'s sidebar is included in its pages with the following:</p> - -<p>\{{APIRef("WebVR API")}}</p> diff --git a/files/pt-pt/mdn/contribute/index.html b/files/pt-pt/mdn/contribute/index.html deleted file mode 100644 index 151975c88c..0000000000 --- a/files/pt-pt/mdn/contribute/index.html +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Contribuir para a MDN -slug: MDN/Contribute -tags: - - Guía - - Landing - - Metadados MDN -translation_of: MDN/Contribute ---- -<div>{{MDNSidebar}}</div> - -<header> </header> - -<div class="boxed translate-rendered"> -<div>{{IncludeSubnav("/pt-PT/docs/MDN")}}</div> -</div> - -<p>Bem-vindo! Ao visitar esta página, efetuou o primeiro passo para se tornar em um colaborador na MDN.</p> - -<p><span class="seoSummary">Estes guias listados aqui abrangem todos os aspetos da contribuição na MDN, incluindo os guias de estilo, guias para a utilização do nosso editor e ferramentas, e muito mais. Por favor, certifique-se que lê (e que concorda com) os <a href="https://www.mozilla.org/en-US/about/legal/terms/mozilla/">Termos da Mozilla </a>(EN) antes de editar ou criar quaisquer páginas. </span></p> - -<p>Se ainda não contribuiu na MDN, o guia de <a href="https://developer.mozilla.org/pt-PT/docs/MDN/Intrudução">Iniciação na MDN</a> pode ajudá-lo a escolher uma tarefa para inciar e ajudar.</p> - -<p>{{LandingPageListSubPages()}}</p> |