winter VS Next.js

Beside Symfony there is Laravel Framework , I will not go into deep difference between this frameworks as it really is just taste of what your team likes more (active record vs datamapper, facade/helpers vs dependency injection, blade vs twig, ...), as already mention above this kind of CMS make sense if Website is just one part of your application and you have to build more then just a simple digital business card / website. In Laravel world there are CMS like October CMS / Winter CMS, which target the same providing a CMS based on the Full Stack Larave framework and give you all features of that framework. Another already mention CMS in Laravel world is Statmatic.

Chances are a lightweight CMS already exists. Winter CMS is one such option.

Or Winter CMS (https://wintercms.com/) ;)

As someone who dabbled in PHP but is mostly a self-taught JS hobbyist dev, I have been using and loving Directus (https://directus.io) since around the time they switched to Node. Development velocity is exceptional with new features released every couple of weeks and bugfixes/enhancements even more frequent, the community and core team is fantastic, and I like the fact that if I ever decide to switch to another CMS for some reason, there's no real import/export process, I just delete the directus_tables in my database, and done.

Pocketbase (https://pocketbase.io/) piqued my interest after seeing it here and on ProductHunt, but I don't think it would be the right call for a client before it hits a stable release.

I also very much enjoyed OctoberCMS (although it has its quirks), but there was a fairly acrimonious split in the community there, and OctoberCMS is no longer open source, and I haven't used the fork (WinterCMS: https://wintercms.com/)

I enjoyed using Apostrophe (https://apostrophecms.com/) for a while, but ultimately I felt like I was doing a lot of stuff in a way that didn't come naturally to me, and although Mongo seems a logical choice when you look at Apostrophe's page model, it worried me a bit that the data would not be easy to move if I ever wanted to.

I'm biased, but it might be worth taking a look at Winter CMS. It's built on Laravel, so you get everything you would with Laravel but it also has some pretty powerful features on top of what you get out of the box with Laravel. Its plugin system and extensibility is also second to none. It's different from a few of the other options though in that you don't add it to an existing project, you build your projects from the start in it.

Winter CMS is an open source fork of OctoberCMS. They've just put Laravel 9 support in place as well.

If you're looking at October I'd give Winter a look too (https://wintercms.com), October is no longer open source and Winter is the open source fork of October. (Disclaimer: I'm the lead maintainer for Winter CMS)

Winter CMS? Laravel based and very developer friendly! https://wintercms.com/

If you're thinking of using Bolt but would also like to have access to the power of Laravel, I'd recommend taking a look at Winter CMS (open source fork of October CMS, built on Laravel / Symfony): https://wintercms.com

Have you ever looked at Winter CMS? https://wintercms.com it's a CMS built on Laravel that's super easy to customize and add your exact needs to.

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.