decap-cms VS Next.js

Following one of the comments in this thread I reviewed two other products in this space - https://www.staticcms.org/ and https://decapcms.org/ - and it looks like the webpages are almost a direct copy of one another, one in dark mode and one in light mode.

I'm a technical product marketer, and I find these type of landing page copying amusing to no end.

Decap CMS, formerly Netlify CMS, is an extensible headless CMS built as a single-page React app. It’s an open source and completely free-to-use option that offers rich-text editing, real-time preview, and drag-and-drop media uploads.

You can look into a Git-based CMS, such as https://github.com/decaporg/decap-cms

These typically are designed to support static site generators.

I found https://decapcms.org/ which seems like an easy to use.

Did you consider https://decapcms.org/ (previously Netlify CMS)? I'm surprised it never really caught on as it seems a good fit for most small Markdown based sites. Looks like Smashing Magazine was using it before they moved to Tina CMS (https://www.smashingmagazine.com/2020/01/migration-from-word...).

Products like [decap CMS](https://github.com/decaporg/decap-cms) try to bridge that gap, but I agree that this space needs to be further developed. In fact I think there needs to be a bunch more work to allow mere mortals to use version control and branch workflows in day to day work.

I've thought of something similar! A git-based flow for a friend's static portfolio site, where he can make text edits and upload images, and the site builds that content with HTML templates.

Not sure how the GitHub markdown editor would feel for the user. It might be really great, even for uploading images.

I was imagining a static admin page, WYSIWYG, that makes git pushes on submit. These were the headless CMSs that seem to be able to accomplish that:

https://www.siteleaf.com/

https://decapcms.org/

And not git based, but similar idea: https://editable.website/

And this is what the admin edit page usually looks like: https://quick-edit-demo.vercel.app/admin/index.html#/collect...

But was taking a bit of work to configure.

Since I made my post, I've also discovered Decap CMS. This looks fairly close to what I was looking for - it deploys as a static SPA alongside the site on a /admin route, allows login with Github (and several other platforms), and builds the site using a choice of static site generator like Gatsby/Hugo/Jekyll etc. The templates are relatively rigid by default though - page layouts are defined up front, and to add a page with a different layout you need to manually add some files to the repo. It seems like there's a way to work around this and add flexibility, but it needs a bit of custom React development. It seems like this might be worth the time investment for me though, since it's the closest thing I've found to what I need so far.

If you've got the content in .md and .json files and you just need a way to add or modify that content, I would recommend you look into decap CMS (formerly netlify CMS)

https://github.com/vercel/next.js/discussions/27666 One of them said 'renaming folder to uppercase' might cause trouble. git might not recognize case-sensetive changes by default.

Next.js has long cemented itself as one of the front runners in the web framework world for JavaScript/TypeScript projects so we’re going to be using that. More specifically we’re going to be using V14 of Next.js which allows us to use some exciting new features like Server Actions and the App Router.

Web frameworks like Next.js will usually include this feature, but do check that they set the caching headers correctly!

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.

Would you like to elaborate on that?

In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.

For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/

Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/

Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main

Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/

React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.

Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.

Next.js: For the website and the admin dashboard

Until the time of writing, there is no official example of how to enable runtime environmental variables in a Dockerized Next.js app, as utilizing unstable_noStore would only dynamically evaluate variables on the server (node.js runtime). There is also an interesting discussion regarding this topic on GitHub.

next.js is a very popular React framework. remix-adonisjs includes more functionality through the AdonisJS backend ecosystem, and should be easier to self-host and self-manage.

Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.

For more information, check out this issue.