Currently, we use grey-matter and remark to parse the blog post markdown content. Moving to next-mdx-remote will allow us to incorporate the custom components we need:
img
needs to map to the component offered by next/image (let's try to leverage some of the optimization tools)
new url should be generated for each to be displayed independently (similar to static path generation for blog posts)
those urls should be accessible from a getStaticPaths call on the /all route
Currently, we use grey-matter and remark to parse the blog post markdown content. Moving to next-mdx-remote will allow us to incorporate the custom components we need:
next/image
(let's try to leverage some of the optimization tools)getStaticPaths
call on the/all
route