react-postprocessing VS Gatsby

For the post processing I used @react-three/post-processing components, and to get the look just right I created a debug panel using Leva to adjust some values (like bokeh blur).

I'm attempting to implement custom post processing in react three fiber but I do not know how to go about it. I've tried to use these links as reference:https://github.com/pmndrs/react-postprocessing/blob/master/api.mdhttps://github.com/pmndrs/postprocessing/wiki/Custom-Passeshttps://github.com/pmndrs/postprocessing/wiki/Custom-Effects

Hi all I've been fiddling with three.js for some time now! and recently started using react-three-fiber just because it's easy to use and declarative. I was wondering if someone here could help me out creating a custom postprocessing effect for my r3f project. I have the shader code already and I have seen pmndrs' code to extend three.js effect class but I'm unable to implement it with the shader code I have. the link to pmndr's / paul Hanchel's code Here and shader code for lens distortion effect Here or on stack overflow here. please assume I know nothing! thanks in advance!

looks like an active bug when using three r135 and above https://github.com/pmndrs/react-postprocessing/issues/111

React Three Fiber with Drei and Postprocessing

The first time I started building static websites is when I discovered Gatsby. I built several projects using Gatsby and hosted it on Netlify free tier. It felt like a really robust architecture and I loved that it was free.

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications.

While Next.js is a powerful framework for building server-rendered React applications, it's not the only option for developers looking to create high-performance websites. One notable alternative is Gatsby, a static site generator that leverages React and GraphQL.

The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.

GatsbyjsCMS - Gatsby is the fast and flexible framework that makes building websites with any CMS, API, or database fun again. Build and deploy headless websites that drive more traffic, convert better, and earn more revenue!

GatsbyJS

Babel plugins are everywhere. From being used to remove unwanted exports from files in Gatsby to being used to disallow users from doing re-exports in Nextjs.

In terms of GitHub stars, SSGs like Next.js, Hugo, Gatsby, Docusaurus, Nuxt.js, and Jekyll top the list. Some popular SSGs even host conferences and workshops, providing resources and networking opportunities for those looking to explore more advanced topics in depth.

Flexibility : Developers have complete control over the frontend so they can use their preferred tools and frameworks like React, Next.js, Gatsby, or Remix.