next-mdx-remote VS next-seo

next-mdx-remote

We are going to be using next-mdx-remote for this tutorial. Let us install it -

So, i was reading the docs and Next/MDX looks exactly what i need for my blog. Well, not exactly because having hundreds of Markdown Pages doesn't look the best way to store the pages, and i was wondering if are any way to generate those pages from a DataBase full of Markdown pages. I read about next-MDX-remote but i was wondering if is there a native way to do that.

next-mdx-remote, a community package maintained by Hashicorp that allows you to use MDX from outside your project.

Do note that Code Hike also works with Next MDX Remote and MDX Bundler however, we are going to look at a simple example with the official MDX plugin for Next.js.

Refer the next-mdx-remote github to learn more the use of plugins and how awesome things could be done using MDX.

You could try storing mdx in wordpress somehow (I'm not a wordpress expert) and using next-mdx-remote to render that at runtime. MDX can contain both markdown and react components.

MDX is an extension on Markdown which, lets you import custom React components into your blog posts. To use MDX with Next.js you need to use a separate package. There are a few choices with MDX-remote being a popular one, but it has some drawbacks. For that reason, I chose to use mdx-bundler.

Sandpack is a live coding environment that runs on the browser. It is made by the team behind CodeSandbox/. The main objective here is to provide interactive examples to play around with, to users. I see it being widely used in things like blog posts and documentation (in fact the, work in progress, new React Docs is using Sandpack). In this article, we are going to look at how to add Sandpack to a React Application and then we will look at integrating it with Next MDX Remote in a NextJS Application.

The third one is Schema.org JSON-LD. I actually question the usefulness of this feature, but if it is relatively easy to implement without a glaring downside, just give it a shot I guess? In Next.js, there is next-seo package that greatly simplifies the implementation of Schema.org JSON-LD.

Next SEO

Next Seo GitHub Repository

I would recommend checking out https://github.com/garmeeh/next-seo. It does SEO for you. Additionally, going to recommend precisely what u/saarnav mentioned. https://vercel.com/docs/concepts/functions/edge-functions/og-image-generation

Any opinions on https://github.com/garmeeh/next-seo ?

To simplify this, we can use a package called next-seo. Next SEO makes managing SEO easier in your Next.js projects.

For SEO there is next-seo.

Meta tags exist in the head element of the page providing important information about the page that can used by search engines and social media sites. There are a variety of meta tags that represent different types of information for different search engines. A popular subset of standardized meta tags are described in the open graph protocol. Managing these tags for every page and generating them dynamically for blog pages has it’s own overhead. Thus for that reason, I have used the Next-SEO plugin. The Next-SEO plugin provides DefaultSEO component that contains tags that will be defined for all routes by default which subsequently can be overwritten at a page level by then using the NextSEO component. Below is the default SEO config used by me.

I have also used this package to make the SEO tag section easier to manage: https://github.com/garmeeh/next-seo

We will have to populate SEO-related meta tags with the relevant information for each page. To do so, we will use garmeeh/next-seo.