publish VS next-seo

I feel the exact same way. I have some plugin ideas to smooth over the process as well. The built in publishing feature is a little rough and not optimized at all. I get the impression that logseq is investing a lot more energy on their own hosted solution than the self hosted publishing right now.

Despite the downsides, as someone who spent way too much time tweaking their own static site, it's really nice to be able to do just write and organize everything inside logseq and push my thoughts up at the end of the day. I was spending way to much time configuring and polishing the static site instead of just getting the notes out there.

Logseq had a tool to publish your notes as a static site, but it's out of date now unfortunately. https://github.com/logseq/publish

Since Logseq handles everything with plain text, some people are just generating a static site from those files directly, but you lose some of the advanced logseq features. I'm looking into doing this to make a "light" version of the notes as a static html site.

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.