<!DOCTYPE html><htmllang="ro"><head><metacharSet="utf-8"/><metahttp-equiv="X-UA-Compatible"content="IE=edge"/><title>Markdown Features · Docusaurus</title><metaname="viewport"content="width=device-width"/><metaname="generator"content="Docusaurus"/><metaname="description"content="Docusaurus uses [GitHub Flavored Markdown (GFM)](https://guides.github.com/features/mastering-markdown/). Find out more about Docusaurus-specific fields when writing Markdown."/><metaname="docsearch:version"content="1.13.0"/><metaname="docsearch:language"content="ro"/><metaproperty="og:title"content="Markdown Features · Docusaurus"/><metaproperty="og:type"content="website"/><metaproperty="og:url"content="https://docusaurus.io/"/><metaproperty="og:description"content="Docusaurus uses [GitHub Flavored Markdown (GFM)](https://guides.github.com/features/mastering-markdown/). Find out more about Docusaurus-specific fields when writing Markdown."/><metaproperty="og:image"content="https://docusaurus.io/img/docusaurus.png"/><metaname="twitter:card"content="summary"/><metaname="twitter:image"content="https://docusaurus.io/img/docusaurus.png"/><linkrel="shortcut icon"href="/img/docusaurus.ico"/><linkrel="stylesheet"href="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css"/><linkrel="stylesheet"href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/atom-one-dark.min.css"/><linkrel="alternate"type="application/atom+xml"href="https://docusaurus.io/blog/atom.xml"title="Docusaurus Blog ATOM Feed"/><linkrel="alternate"type="application/rss+xml"href="https://docusaurus.io/blog/feed.xml"title="Docusaurus Blog RSS Feed"/><script>
function createToggler(togglerSelector, targetSelector, className) {
var toggler = document.querySelector(togglerSelector);
var target = document.querySelector(targetSelector);
if (!toggler) {
return;
}
toggler.onclick = function(event) {
event.preventDefault();
target.classList.toggle(className);
};
}
});
</script></nav></div><divclass="container mainContainer"><divclass="wrapper"><divclass="post"><headerclass="postHeader"><aclass="edit-page-link button"href="https://crowdin.com/project/docusaurus/ro"target="_blank"rel="noreferrer noopener">Translate</a><h1class="postHeaderTitle">Markdown Features</h1></header><article><div><span><p>Docusaurus uses <ahref="https://guides.github.com/features/mastering-markdown/">GitHub Flavored Markdown (GFM)</a>. Find out more about Docusaurus-specific fields when writing Markdown.</p>
<p>Documentele utilizează următoarele câmpuri markdown header ce sunt anexate printr-o linie <code>---</code> pe orice parte:</p>
<p><code>id</code>: A unique document id. If this field is not present, the document's <code>id</code> will default to its file name (without the extension).</p>
<p><code>title</code>: The title of your document. If this field is not present, the document's <code>title</code> will default to its <code>id</code>.</p>
<p><code>hide_title</code>: Whether to hide the title at the top of the doc.</p>
<p><code>sidebar_label</code>: The text shown in the document sidebar and in the next/previous button for this document. If this field is not present, the document's <code>sidebar_label</code> will default to its <code>title</code>.</p>
<p>Documentele cu versiuni au id-urile alterate pentru a include numărul versiunii când este copiat. Noul <code>id</code> este <code>versiune-${version}-${id}</code> unde <code>${version}</code> este numărul versiunii acelui document și <code>${id}</code> este <code>id</code>-ul original. Adițional, documentele cu versiuni au un câmp <code>original_id</code> adăugat cu id-ul original al documentului.</p>
<p><code>custom_edit_url</code>: The URL for editing this document. If this field is not present, the document's edit URL will fall back to <code>editUrl</code> from optional fields of <code>siteConfig.js</code>. See <ahref="/docs/ro/site-config">siteConfig.js</a> docs for more information.</p>
<p>Blog posts use the following markdown header fields that are enclosed by a line <code>---</code> on either side:</p>
<p><code>titlu</code>: Titlul acestui post pentru blog.</p>
<p><code>author</code>: The author of this blog post. If this field is omitted, no author name will be shown.</p>
<p><code>authorURL</code>: A page to link to when a site user clicks the author's name. If this field is omitted, the author's name will not link to anything.</p>
<p><code>autorFBID</code>: Id-ul de Facebook al autorului, folosit doar pentru a lua poza de profil a autorului pentru a fi afișată odată cu post-area de pe blog. Dacă acest câmp este omis, autorul nu va avea nici o imagine afișată pentru post-area de pe blog.</p>
<p>You can use relative URLs to other documentation files which will automatically get converted to the corresponding HTML links when they get rendered.</p>
<p>Exemplu:</p>
<pre><codeclass="hljs css language-md">[<spanclass="hljs-string">Acesta link-uiește către alt document</span>](<spanclass="hljs-link">celălalt-document.md</span>)
</code></pre>
<p>Acest markdown va fi convertit automat într-un link pentru <code>/documente/celălalt-document.html</code> (sau la link-ul cu traducerea/versiunea corespunzătoare) odată ce va fi redată.</p>
<p>This can help when you want to navigate through docs on GitHub since the links there will be functional links to other documents (still on GitHub), but the documents will have the correct HTML links when they get rendered.</p>
<p>Static assets can be linked to in the same way that documents are, using relative URLs. Asset-urile statice utilizate în documente și bloguri ar trebuii să se ducă în <code>documente/asset-uri</code> și <code>siteweb/blog/asset-uri</code>, respectiv. Markdown-ul va fi convertit în căile correcte ale link-urilor astfel încât aceste căi vor funcționa pentru documente în toate limbile și versiunile.</p>
<p>You can make an auto-generated list of links, which can be useful as a table of contents for API docs.</p>
<p>In your markdown file, insert a line with the text ``. Scrie-ți documentația folosind header-e <code>h3</code> pentru fiecare funcție în interiorul unui bloc de cod. These will be found by Docusaurus and a list of links to these sections will be inserted at the text <code><AUTOGENERATED_TABLE_OF_CONTENTS></code>.</p>
<p>Display code in multiple programming languages using code tabs. First, mark the start and end of a code tabs group, by using <code><!-- DOCUSAURUS_CODE_TABS --></code> and <code><!-- END_DOCUSAURUS_CODE_TABS --></code> respectively in your markdown. Then start each tab with <code><!--[TAB_TITLE]--></code>.</p>
<p>Adding the following code to your Markdown file:</p>
<p>Syntax highlighting is enabled by default on fenced code blocks. The language should be detected automatically, but you can sometimes get better results by specifying the language. You can do so using an <ahref="https://github.github.com/gfm/#example-111">info string</a>, following the three opening backticks. The following JavaScript example...</p>
<p>Highlighting is provided by <ahref="https://highlightjs.org">Highlight.js</a> using the theme specified in your <code>siteConfig.js</code> file as part of the <code>highlight</code> key:</p>
<p>You can find the full list of supported themes in the Highlight.js <ahref="https://github.com/isagalaev/highlight.js/tree/master/src/styles"><code>styles</code></a> directory.</p>
<p>While Highlight.js provides support for <ahref="https://highlightjs.org/static/demo/">many popular languages out of the box</a>, you may find the need to register additional language support. For these cases, we provide an escape valve by exposing the <code>hljs</code> constant as part of the <code>highlight</code> config key. This in turn allows you to call <ahref="http://highlightjs.readthedocs.io/en/latest/api.html#registerlanguage-name-language"><code>registerLanguage</code></a>:</p>
<p>You can also opt to use Prism to syntax highlight certain languages available in the list <ahref="https://github.com/PrismJS/prism/tree/master/components">here</a>. Include those languages in <code>usePrism</code> field in your <ahref="/docs/ro/site-config">siteConfig.js</a></p>
<p>Exemplu:</p>
<pre><codeclass="hljs">// siteConfig.js
usePrism: ['jsx']
</code></pre>
<p>Notice that the code block below uses JSX syntax highlighting from Prism.</p>
<p>Docusaurus allows for adding buttons to copy the code within fenced code blocks. Please follow the instructions <ahref="https://gist.github.com/yangshun/55db997ed0f8f4e6527571fc3bee4675">here</a> to add "Copy" buttons to your code blocks.</p>
</span></div></article></div><divclass="docs-prevnext"><aclass="docs-prev button"href="/docs/ro/commands"><spanclass="arrow-prev">← </span><span>CLI Commands</span></a><aclass="docs-next button"href="/docs/ro/api-pages"><span>Pages and Styles</span><spanclass="arrow-next"> →</span></a></div></div></div><navclass="onPageNav"><ulclass="toc-headings"><li><ahref="#head-ere-markdown">Head-ere Markdown</a><ulclass="toc-headings"><li><ahref="#documente">Documente</a></li><li><ahref="#post-uri-pentru-blog">Post-uri pentru Blog</a></li></ul></li><li><ahref="#caracteristici-suplimentare">Caracteristici suplimentare</a><ulclass="toc-headings"><li><ahref="#link-uirea-cu-alte-documente">Link-uirea cu alte Documente</a></li><li><ahref="#link-uirea-către-imagini-sau-alte-asset-uri">Link-uirea către Imagini sau Alte Asset-uri</a></li><li><ahref="#generand-cuprinsul">Generând Cuprinsul</a></li><li><ahref="#language-specific-code-tabs">Language-specific Code Tabs</a></li></ul></li><li><ahref="#syntax-highlighting">Syntax Highlighting</a><ulclass="toc-headings"><li><ahref="#registering-additional-languages">Registering additional languages</a></li><li><ahref="#using-prism-as-additional-syntax-highlighter">Using Prism as additional syntax highlighter</a></li><li><ahref="#adding-copy-code-buttons">Adding Copy Code Buttons</a></li></ul></li></ul></nav></div><footerclass="nav-footer"id="footer"><sectionclass="sitemap"><ahref="/"class="nav-home"><imgsrc="/img/docusaurus_monochrome.svg"alt="Docusaurus"width="66"height="58"/></a><divclass="footerSection"><h5>Docs</h5><ahref="
