next-payload VS nextra

You can host payload within next.js itself on Vercel or similar https://github.com/payloadcms/next-payload

Next Payload Demo - https://github.com/payloadcms/next-payload-demo Next Payload Serverless - https://github.com/payloadcms/next-payload

If you host serverlessly like on vercel, then you have to provide your own db connection, email provider and S3 storage. See the bottom part of the next-payload readme here: https://github.com/payloadcms/next-payload

I've been building web apps for more than a decade. From an agency and consultancy perspective, developers can build truly amazing things on the web for any client need. The tools for building websites and apps have gotten better and better, the side-effect has been a mindblowing amount of complexity being introduced. You either end up with some no-code solution that is scoffed at by any serious engineer, or something built out that requires a senior engineer to maintain.

This ultimately is bad for the client and developers who have the resposibility of learning a dizzying amount of tooling just to make something that works. It shouldn't take a computer scientist to build a website.

To combat this we're excited to release a new package that simplifies your stack into a single repo with Next.js and Payload that can be run serverlessly. The beauty here is that there is very little devOps, generated typescript types unified across frontend and back, and the elimination of HTTP API calls between application and backend. https://github.com/payloadcms/next-payload

My co-founder of Payload, James Mikrut is doing a livestream with Vercel's Steven Tey to shed some more light on what we're seeing: https://www.youtube.com/watch?v=TWkR-OPXKRU

co-author here

we put in a lot of effort into our docs and we'd greatly appreciate any criticism or feedback! Langfuse is powerful but the docs should help beginners to quickly get started and then incrementally use more features.

docs are OSS, repo: https://github.com/langfuse/langfuse-docs

built using: https://github.com/shuding/nextra

However, this may just be due to the lack of proper documentation from the Nextra side of things (shoutout to Nextra though, regardless).

Nextra - Nextra is another option for creating documentation sites. While it might not be as well-known as Docusaurus, Nextra offers a modern and minimalist approach to building documentation. It is designed to be lightweight and user-friendly, making it a good choice for those who prefer a simple and clean documentation style. You can explore more about Nextra on their official website.

I have looked at https://nextra.site/ but that doesn't work with the app router yet. So I'm wondering if there's another alternative.

You could also have a look at Nextra. You can use mdx components to build your blog (including support for server-side fetching). I'm currently using their documentation template, but it seems they also have a blog template.

We write everything in Markdown, as it's the closest you'll get to a 'universal' format. Then, we use a static site generator to turn the docs into a website. Current projects are using Nextra for this. If you ever need to change site generators, you still have all the markdown docs and image files, so it's pretty easy to change.

https://nextra.site/ is nice

Today I found this tool for Next.js called Nextra. You can effortlessly create a blog post website or a documentation website. All you need is markdown. Simply export your markdown from Notion and utilize it with Nextra to enjoy all the cool features, including full-text search, syntax highlighting, dark/light mode, and even image support. Everything is generated at build time, making it a static website which is Blazingly fast. https://nextra.site/