ProcessWire VS fastify

Bottom one looks better. First one reminds me of ProcessWire.

ProcessWireProcessWire is a fantastic CMS/CMF (content management framework) and I think it is a good fit for your skills. Works with any front end CSS although my personal preference is UIkitUIkit.

Over the years I have tried different frameworks, mostly in PHP, like Code Igniter (2010), ProcessWire (2014) and Laravel (2015).

The idea of tons of 3rd-party plugins, with WordPress and also Drupal, is just disastrous for security.

Anyone with any ability to write a little PHP would be far far better off building their site in a CMS like ProcessWire [1], which has a very small core, but a extremely powerful content (PHP) API [2], which means you can replicate pretty much everything you have in Wordpress and Drupal with a few API calls in your templates.

This means you build your listing and presentation-logic custom made with the minimal amount of code needed, and the attack vector shrinks to pretty much nothing, as long as you don't voluntarily do something stupid.

[1] https://processwire.com/

[2] https://cheatsheet.processwire.com/

It is incredibly rare that I see anyone mention ProcessWire. I used to use it years ago and still subscribe to regular emails. It is indeed a great CMS/CMF. https://processwire.com/

ProcessWire is one option.

Regardless of that, I'd like to throw in ProcessWire as an option. You basically define all your fields and templates you want to have in the admin, and then you create your templates. You can also use Page Classes to extend functions for a specific template. Your application sits in the "sites" folder and is separated from core. I'm running two websites with that one.

If you're a PHP user, check out ProcessWire.

I'm looking for a headless CMS solution that offers a good content editing strategy. I'm used to working with Statamic and Processwire, both of which allow you to create your own "Content blocks", which can be re-used by the editor / user and are set up in ways which allow you to define them.

For example, Fastify removed the instanceof operatorfrom its codebase because it was causing problems for those developers that rely on jest as a testing framework.

Both are frameworks but NextJs is for Forntend (web app in browser that use ReactJs under the hood) and NestJs is for Backend (server app running on a server witch use Express or Fastify). The only thing similar between them is the typed language in which they were written.

Restify & Fastify Hapi

Let's create a sample Node API project we can work with throughout to build a new docker image. We will leverage Fastify to create an API that we configure via the fastify-cli.

Fastify

In setting out to build this service, we wanted to use gRPC for its APIs. We’ve been reaching for REST when building APIs so far, primarily out of necessity, i.e., our public APIs needed auto-generated client SDKs and docs for developers working with them. We built those APIs with Fastify and Typebox but felt burned by a code-first approach to generating an OpenAPI spec. I’ll spare you the details and save that experience/learning for another article. Suffice it to say we love gRPC’s schema-first approach. This blog post summarizes our feelings well

Fastify – Fast and Low overhead web framework

Custom Functions are powered by Fastify (a light-weight Node.js framework that claims to be faster than Express.js), so they’re extremely flexible.