If there are not enough placeholders for title, subtitle, and body for the content, this information will not be displayed.
This is a current specification, but it is unfriendly to users. It may be better to display a warning or render it somewhere.
For example, if the following Markdown is applied to the “TITLE_AND_BODY” style without subtitles instead of a complicated style, users may want the content other than the title to be merged into the body.
input
# CAP theorem
## Consistency
Every read receives the most recent write or an error.
## Availability
Every request received by a non-failing node in the system must result in a response.
## Partition tolerance
The system continues to operate despite an arbitrary number of messages being dropped (or delayed) by the network between nodes.
desired output

Currently, we can change the heading to h3 to display it this way, but it seems strange in terms of information structure, and I feel that it is a workaround.
If there are not enough placeholders for title, subtitle, and body for the content, this information will not be displayed.
This is a current specification, but it is unfriendly to users. It may be better to display a warning or render it somewhere.
For example, if the following Markdown is applied to the “TITLE_AND_BODY” style without subtitles instead of a complicated style, users may want the content other than the title to be merged into the body.
input
desired output
Currently, we can change the heading to h3 to display it this way, but it seems strange in terms of information structure, and I feel that it is a workaround.