Discussion

formatting test

by Potato - 4 months ago

test

Original post - 4 months ago

Markdown Test Post

This post is meant to test the site’s basic and extended Markdown rendering.
It includes normal forum text, long-form formatting, tables, footnotes, task lists, and a few edge cases.

Two spaces at the end of this line should create a hard line break.
This line should appear directly below it.

Basic Inline Formatting

Plain text should look normal.

Italic with asterisks and italic with underscores should both work.

Bold with asterisks and bold with underscores should both work.

Bold italic with asterisks and bold italic with underscores should both work.

Inline code should render like const speed = ship.velocity.length().

Escaped punctuation should show the literal character: *not italic*, # not a heading, and [not a link].

Valkyrien Skies on Modrinth should render as a link.

Raw URLs should autolink: https://www.valkyrienskies.org/

URLs in code should not autolink: https://www.valkyrienskies.org/

This image should render and scale inside the post:

Valkyrien Skies addon template icon

Headings

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Custom Heading ID

This link should jump to the custom heading ID.

Blockquotes

A single-level quote should render with a quote border.

Nested quotes should render too.

This is nested inside the first quote.

Back to the first quote level.

Lists

Unordered list:

  • Airship hull
  • Engine room
  • Balloon compartment
  • Control room

Ordered list:

  1. Place helm
  2. Assemble hull
  3. Add ballast
  4. Launch

Nested list:

  • Ship systems
    • Propulsion
      • Engines
      • Gearboxes
    • Control
      • Helm
      • Redstone inputs
  • World systems
    • Water
    • Terrain

Code

Indented code block:

val fileHeader = byteArrayOf(0x56, 0x44, 0x45, 0x58)

Fenced code block:

This is a fenced code block.
It should preserve whitespace.

Fenced code block with a language:

private val fileHeader = byteArrayOf(0x56, 0x44, 0x45, 0x58, 0x0D, 0x0A, 0x1A, 0x0A)

fun hasVdexHeader(bytes: ByteArray): Boolean {
    return bytes.take(fileHeader.size).toByteArray().contentEquals(fileHeader)
}

Horizontal Rules

The next line should render as a horizontal rule.


The content should continue after the rule.

Tables

Syntax Description Result
**bold** Bold text bold
*italic* Italic text italic
`code` Inline code code
[link](https://example.com) Link link

Escaped pipe in a table:

Input Output
A | B A | B

Definition Lists

Airship
A ship that can fly.
Contraption
A moving structure assembled from blocks.
This term has a second definition to test multiple definitions.

Strikethrough

This text should be struck through.

This sentence has removed text in the middle.

Task Lists

Emoji Shortcodes

Emoji shortcodes should render: 🚢 🚀 ✨ ⚠️ ✅

Copied Unicode emoji should also render normally: 🚢 ✨ ⚠️ ✅

Highlight, Subscript, And Superscript

This should be highlighted text.

Water should render with subscript: H2O.

Math-style power should render with superscript: X2.

You can combine them: Lift force FL = CL * V2.

Footnotes

This sentence has a short footnote.[1]

This sentence has a longer footnote with multiple lines.[2]

Raw HTML Safety Check

Raw HTML should not execute. This should display as text, not as active HTML:

<script>alert(“nope”)</script>

This raw mark tag should not be needed because ==highlight== is supported:

<mark>raw mark tag</mark>

Forum-Specific Schematic Embed Placeholder

Replace this UUID with a real approved schematic ID to test forum schematic embeds:


  1. This is the short footnote. ↩︎

  2. This is the longer footnote.
    It should stay attached to the footnote content.

    It can also contain another paragraph and inline code. ↩︎

Schematic Embed

Unavailable embed

[schematic:90f2ccc4-1c87-496a-a487-48aaf2a1c262]

End

If everything above renders cleanly, basic and extended Markdown support is working.

Replies

1

4 months ago

We need a way to copy the markdown of someones post, like what discord has, so you can see how they did the formatting

Sign in to reply.