-
I'm just curious about the direction of the project after PayloadCMS decided to go all in for NextJS. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Indeed, the initial announcement at NextCon last year that PayloadCMS made us very nervous, and we have been following PayloadCMS 3's development closely since. I'm happy to report that we're confident that, while there are still some technical challenges to overcome, mana.wiki has a viable path to maintain on the latest PayloadCMS releases while remain on the Remix framework that we prefer. The mana.wiki team also maintains the popular Remix+Payload template RePay, and we have found solutions for the two frameworks to play nicely on a single server: https://github.com/manawiki/repay/tree/payload-v3 In fact, I figured out how to we can avoid the As the largest OSS project built on PayloadCMS, we are in regular communication with the Payload team on Discord, and that gave us confidence that they're on the right track and helped overcome our initial misgivings about the NextJS dependency. |
Beta Was this translation helpful? Give feedback.
Indeed, the initial announcement at NextCon last year that PayloadCMS made us very nervous, and we have been following PayloadCMS 3's development closely since.
payloadcms/payload#4202
I'm happy to report that we're confident that, while there are still some technical challenges to overcome, mana.wiki has a viable path to maintain on the latest PayloadCMS releases while remain on the Remix framework that we prefer.
The mana.wiki team also maintains the popular Remix+Payload template RePay, and we have found solutions for the two frameworks to play nicely on a single server: https://github.com/manawiki/repay/tree/payload-v3
In fact, I figured out how to we can avoid the
next
dependency alt…