days since this article was written, please be aware of its timeliness
This article demonstrates the Markdown rendering effects on GitHub. This link shows the rendering on the Craft Web client, where the differences between the two are quite noticeable.
TITLES
Title
Subtitle
Heading
CONTENT
Strong
Body
Caption
GROUPS
Page
This is an empty page!
Card
This is an empty Card!
TEXT STYLE
Bold
Italic
Strikethrough
InlineCode
- [ ] Todo
Toggle
-
Unordered List One
-
Unordered List Two
-
Ordered List One
-
Ordered List Two
Align Left
Align Center
Align Right
This is an indented sentence
DECORATIONS
Decorations Focus
Decorations Block
INSERT BLOCK
Plain Text
| Table | |
|---|---|
1 | |
1 | |
Divider👇🏻
NESTING
Decoration Focus & Block
-
Decoration Focus & List
-
Decoration Block & List
…too many to show
My Thoughts
Key Points:
-
Decorations, whether Focus or Block, should be converted to
blockquotein Markdown syntax. -
Captions have no direct Markdown equivalent and should render as Body text, not as H5.
-
Code blocks should include the language, like ```javascript.
-
Nested lists, not flat lists!
Minor Details:
-
Alignment can be ignored.
-
Indentation can be ignored.
-
Formulas… well, ignore those too.
My Plan?
I’ll create an npm package to accurately convert Craft data to GitHub Markdown 🤪.
Any suggestions?
-
Previous
My Blog Automation Workflow in 2022 -
Next
"Ace, CodeMirror, and Monaco: A Comparison of Web Code Editors"
I often wish that when facing some key decisions in life, someone could tell me the best course of action so that I would not waste my precious time. Putting myself in others' shoes, I therefore write blogs often, hoping to record in this tiny corner of the vast Internet the once-in-a-lifetime experiences that matter to me, and to help those who seek help.