The tool of markdown maybe have a bug.

[diguage]

I sent a PR for fixing a document style bug: fix markdown syntax by diguage · Pull Request #16452 · kubernetes/website

I review the render result, and I found the tool of Markdown maybe have a bug.

Before I fix the error:

    On Fedora, edit `/etc/kubernetes/kubelet` to include this line:

    ```
    KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --manifest-url=<manifest-url>`
    ```

Now, restart the kubelet. On Fedora, you would run:

    ```shell
    # Run this command on the node where the kubelet is running
    systemctl restart kubelet
    ```

https://kubernetes.io/docs/tasks/configure-pod-container/static-pod/

The four spaces shoud be render as the source code block. So the source code blocks in the four spacke block do not be render as the source code.

The blockquote tag should be used in the case.

After:

> On Fedora, edit `/etc/kubernetes/kubelet` to include this line:
>
> ```
> KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --manifest-url=<manifest-url>`
> ```
>
> Now, restart the kubelet. On Fedora, you would run:
>
> ```shell
> # Run this command on the node where the kubelet is running
> systemctl restart kubelet
> ```

https://deploy-preview-16452--kubernetes-io-master-staging.netlify.com/docs/tasks/configure-pod-container/static-pod/

But the blockquote tag does not be render in the right way.

Right render

But it should render like as following (Preview on VS Code):

[sftim]

The way I see it, the rendering via Hugo is canonical. Visual Studio Code's preview is a hint at how the source might get rendered.

Would you agree with
/triage support
@diguage?

[diguage]

@sftim

Visual Studio Code's preview is a hint at how the source might get rendered.

Sorry, I don't agress with the statement.

The > tags are a blockquote tag of Markdown.

There are two guides for Markdown which explains the syntax.

• Basic Syntax | Markdown Guide
• Mastering Markdown · GitHub Guides

[sftim]

/remove-triage support
Sounds like there's more to discuss.

[aimeeu]

Hi @diguage - I think Hugo is rendering the Markdown correctly.

Repeating part of the comment I left on your PR #16452:

Thanks for all the detail! Using blockquote '>' syntax: markdownguide.org's blockquotes with other elements section says "Blockquotes can contain other Markdown formatted elements. Not all elements can be used — you’ll need to experiment to see which ones work." So nesting code block syntax inside of blockquote syntax doesn't work.

---

For everyone reading this Issue: regarding the 4 spaces (or 1 tab) at the beginning of L135-139: if you want some text to show up exactly as you write it, without Markdown doing anything to it, indent every line by at least 4 spaces (or 1 tab).
Rendered:

Code:

Looking at the source code file, the 4 spaces (or 1 tab) at the beginning of each line 135-139 is a mistake. Those spaces should be removed - those lines should not be a blockquote.

If you install Hugo, you can test your changes locally. Hugo uses the BlackFriday Markdown processor.

[aimeeu]

/priority awaiting-more-evidence

[diguage]

I used to use the GitHub Format Markdown.
Markdown has too many dialects. There are many differences amount the dialects.
Let me learn the BlackFriday Markdown processor. 😆

[sftim]

@diguage are you OK to close this issue?