{"posts":[{"slug":"render-markdown-to-html","content":"

Markdown is a lightweight markup language, and the syntax is supported by lots of web and desktop applications, such as Notion, Github and Slack. In comparison to HTML, it's easier to write, format, and read your content in markdown.

In saying that, using markdown for all my blog posts will give me a simplistic blogging experience.

The challenge now is rendering the Markdown content to the browser. There are many popular markdown processors out there, and for this blog I decided to go with remark.

The great thing about remark is being part of a UnifiedJS ecosystems. This allows us to chain different packages as a plugin to help extracting and manipulating content. It does this by taking Markdown, HTML or plain text and turning it into a AST (abstract syntax tree) data structure that the plugins within the ecosystem can consume.

Here are simple steps to converting a markdown file into HTML string that I use for my blog.

// process-markdown.ts\n\nimport toVFile, { VFile } from 'to-vfile';\nimport unified from 'unified';\nimport remarkParse from 'remark-parse';\nimport remark2rehype from 'remark-rehype';\nimport rehypeStringify from 'rehype-stringify';\n\nconst processor = unified()\n  .use(remarkParse)\n  .use(remark2rehype)\n  .use(rehypeStringify);\n\nexport async function processMarkdown(filename: string): Promise<VFile> {\n  const file = await toVFile.read(filename);\n  const data = await processor.process(file);\n\n  return { content: data.contents };\n}\n

As you can notice, I imported three plugins to do these 3 things:

remark-parse - Parses markdown into to a syntax tree.
remark-rehype - Convert syntax tree into HTML syntax tree.
rehype-stringify - Turn HTML syntax tree into HTML string.

Let's say you have the following markdown file.

# Test Post\n\nThis is a test post.\n

If I reference the above file path to the processMarkdown function, the return value should look similar to below.

{ content: \"<h1>Test Post</h1>\\n<p>This is a test post.</p>\" }\n

Adding Metadata

Next, I want to add metadata on top of the markdown file. This is where I want to record the list of tags and the date created of each blog post. I also want to move the title there so that I can use it in two places. As a <h1> in the <body> and a <title> within the <head>.

The metadata format should look like this.

---\ntitle: Test Post\ndate: 08/28/2021\ntags: \n - Markdown\n - HTML\n - JavaScript\n---\n\nThis is a test post.\n

The update I want to make in processMarkdown is to split the metadata from the rest of the markdown content.

// process-markdown.ts\n\nimport toVFile, { VFile } from 'to-vfile';\nimport unified from 'unified';\nimport remarkParse from 'remark-parse';\nimport remark2rehype from 'remark-rehype';\nimport rehypeStringify from 'rehype-stringify';\nimport remarkFrontmatter from 'remark-frontmatter';\nimport jsyaml from 'js-yaml';\nimport dayjs from 'dayjs';\n\nconst parser = unified()\n  .use(remarkParse)\n  .use(rehypeStringify)\n  .use(remarkFrontmatter, [\"yaml\"]);\n\nconst processor = unified()\n  .use(remark2rehype)\n  .data('settings', { fragment: true })\n  .use(rehypeStringify);\n\nexport async function processMarkdown(filename: string): Promise<VFile> {\n  const file = await toVFile.read(filename);\n  const tree = parser.parse(file);\n  const [metadata, ...body] = tree.children;\n\n  if (!metadata || metadata.type !== \"yaml\") {\n    throw new Error(\"Missing metadata inside the markdown file\");\n  }\n\n  const { title, date, tags } = jsyaml.load(metadata.value);\n  tree.children = body;\n\n  const nodes = await processor.run(tree);\n  const content = processor.stringify(nodes);\n\n  return {\n    content,\n    metadata: {\n      title,\n      date: dayjs(date).format(\"DD MMM, YYYY\"),\n      tags,\n    }\n  };\n}\n

The above change may look complex, but it's not at all, let's break it down.

In the first iteration of processMarkdown, the processor.process was used and it internally ran these three methods, parse, run and stringify.

Since I want to take the metadata out from the rest of the content. I need to independently run the parse method first to create the syntax tree and then remove the first child node from the tree.

I want to point out the metadata syntax type is in YAML and I added remark-frontmatter plugin to easily recognise and format any YAML syntax inside the tree. Then I used jsyaml to convert the node value string into JSON.

Once the metadata is removed, I run the remaining run and stringify methods. The updated return value should have metadata along with the HTML string.

{\n  metadata: {\n    title: \"Test Post\",\n    date: \"28 Aug, 2021\",\n    tags: [\"Markdown\", \"HTML\", \"JavaScript\"]\n  },\n  content: \"<p>This is a test post.</p>\"\n}\n

Rendering Code Block

Finally, It's not a developer blog post without a stylish syntax highlight for the code block. One of the most popular syntax highlighting library is highlight.js.

Luckily there is a UnifiedJS plugin to integrate highlight.js into the transform process, rehype-highlight.

Let's add the plugin to the processMarkdown.

// process-markdown.ts\n\nconst processor = unified()\n  .use(remark2rehype)\n  .use(rehypeHighlight)\n  .use(rehypeStringify);\n

highlight.js already provides you with different stylings you can use, all you have to do is import the css file of your choosing to the project. I am currently using Atom One Light theme.

import 'highlight.js/styles/atom-one-light.css';\n

To finalise the markdown file we have been referencing for this post, let's insert a JavaScript code block to it.

---\ntitle: Test Post\ndate: 08/28/2021\ntags:\n - Markdown\n - HTML\n - JavaScript\n---\n\nThis is a test post.\n\n```JavaScript\nconst greeting = 'Hello World';\n```\n

...and this is the final view.

$\"Final$

","metadata":{"tags":["Markdown","HTML","JavaScript"],"title":"Render Markdown To HTML","date":"22 Aug 2022"}},{"slug":"blog-init","content":"

Ohh hey there. ✌️\n\nFinally, my blog is up and running!\n\nI will use this space to document my learning and a place where I can share my thoughts and general progression over time as a developer.\n\nI would say the primary audience of this site will be myself, although hopefully, someday, I can help and inspire someone else.\n\nLet's see how this goes.\n\n- Firman\n

","metadata":{"tags":[],"title":"Blog init","date":"08 Aug 2022"}}]}

Hi all, I'm Firman.👋

Recent Posts