A Comprehensive Guide to Markdown Elements in CMS Duniai: Buttons, Tables, Notes, and More

Markdown helps arrange articles with consistent formatting without needing to write HTML. In the CMS Duniai editor, you can use basic Markdown and some special elements like buttons, tables, checklists, and information boxes. This article shows the syntax that can be directly tried in the editor. The imported status is draft so you can check the display and links before publishing.

1. Arrange Articles with Headings

Use headings to divide articles into easily scannable sections. The main article title is already an H1, so the article content should start from H2 (##), then use H3 (###) or H4 (####) for sub-sections.

Example:

```text
## Persiapan

Periksa kebutuhan

#### Catatan tambahan
```

Avoid choosing headings solely because of their size. Headings indicate topic hierarchy, while bold and italic are used for emphasis within paragraphs.

2. Format Text and Insert Code

Commonly used formats:

• teks tebal becomes bold text.
• teks miring becomes italic text.
• teks dicoret becomes strikethrough text.
• ` nama-file.zip ` denotes code or file name within a sentence.
• Ctrl+S displays a keyboard button like Ctrl+S.
• Panduan displays a small label like Panduan.

For multi-line code, use three backticks and specify the code language if known:

```js
const status = 'siap';
console.log(status);

```

Code blocks are displayed as text and not executed on the page. Use this element for example configurations or code snippets that need to be copied.

3. Add Links and Images

Markdown links are written in the format [teks yang menjelaskan tujuan](URL). For example, halaman Tentang creates an internal link to the About page. For other sites, use HTTPS addresses and choose link text that provides a clear description to readers.

Download links can be written as regular links. If you want a download button, use the correct file address and do not change the URL:

```text
[button text="Unduh panduan" url="https://alamat-asli-berkas.example/panduan.zip" style="primary"]

```

The syntax in the code block above is just an example. Replace the example address with your download URL before making the button active. Buttons accept styles primary, secondary, outline, or danger.

For images, upload the file through Media first, then use the CMS media URL:

```text

```

Write a brief and relevant alt text. Do not include many keywords in the image description.

4. Create Step-by-Step Guides and Checklists

Numbered lists are suitable for sequential actions:

1. Open the article in the editor.
2. Add headings and required content.
3. Preview, then save as a draft.

Unordered lists are suitable for items that do not need to be in order:

• Check the title and summary.
• Ensure the image URL can be opened.
• Try each download button.

Checklists use [ ] for incomplete tasks and [x] for completed tasks:

• Check external links.
• Review the heading structure.

Checklists only show status to readers; checking items in the editor visually does not perform automatic actions.

5. Add Notes, Tips, and Warnings

Information boxes use a quote format with special markers. Write the content line with the prefix > :

There are also old markers [!INFO], [!SUCCESS], and [!DANGER]. Choose the type of box according to the meaning; do not make every paragraph a warning.

6. Present Comparisons with Tables

Use tables when readers need to compare several attributes. The second row contains a horizontal line. Colons (:) align columns: :--- left alignment, :---: center alignment, and ---: right alignment.

Ensure the header row is clear and cell content is concise. On small screens, tables can be scrolled horizontally. If the table only repeats paragraphs, use a list for easier reading.

7. Use Quotes and Horizontal Lines

Regular quotes start with >:

Write relevant quotes, provide context, and include sources if you're quoting someone else.

Horizontal lines use three horizontal lines. Use them sparingly to separate sections that are genuinely different:

8. Check the Result Before Publishing

Use the preview to check headings, lists, tables, notes, images, and buttons. Click external links and download buttons to ensure their addresses are correct. Open the mobile view to see if the table is still easy to use and paragraphs are not too long.

To maintain SEO quality, answer reader questions from the start, use descriptive headings, and write a summary that matches the actual content. Add experiences or sources only if they are truly available; do not make claims of testing or quotes that were not done. Markdown elements help presentation, but the accuracy of information still determines the quality of the article.

9. Frequently Asked Questions About Markdown Duniai

Can I paste all HTML into the editor?

No. The CMS secures content by displaying HTML code as text, not executing it. Use Markdown and available special markup, such as [button ...], [!NOTE], or code blocks. This approach makes the format more consistent and reduces the risk of active scripts in articles.

Why do buttons or tables look like code?

Ensure the syntax is outside the code block. If the entire shortcode is wrapped in three backticks, the CMS will display it as a text example. For tables, make sure the horizontal line has the same number of columns as the header. Then, open the preview to check the result.

How do I keep download links functional?

Use the complete URL of the correct file storage, then test the link in the preview. The button text should describe the action and file content, such as “Download PDF guide.” Avoid copying placeholder URLs from this example. If the download URL changes, update the button in the editor and try again before publishing.

When should I use tables?

Use tables to compare several options with the same attributes, such as names, formats, or system requirements. If each item needs a long explanation, a list with subheadings is often easier to read on mobile and clearer for readers and search engines.

Before publication, read the article from start to finish. Ensure each heading explains the next section, each note has a purpose, and tables do not hide important information on small screens. Complete alternative text for images, check links, and make sure the SEO description accurately describes the available content.

If you want to try an active button without leaving the site, use the following example:

Save the article as a draft, preview it, and then publish it after checking all elements and links.