Re:PayloadCMS: Open-Source, Fullstack Next.js Framework
by synergy20 on Monday October 14, 2024 @06:40PM
(#41842928)
how does it compare to Django as far as battery-included goes
[ Parent
| on HN ]
Re:PayloadCMS: Open-Source, Fullstack Next.js Framework
by marpstar on Monday October 14, 2024 @08:49PM
(#41843808)
NextJS instead of templates. Full-featured admin area. I'd say Payload is more akin to Wagtail than Django itself. It feels ridiculously modern compared to other CMSes I've touched, Wagtail included. Payload doesn't prescribe i18n like Django.
When you need to, you can step down into NextJS and write custom endpoints and the like.
Re:PayloadCMS: Open-Source, Fullstack Next.js Framework
by andybak on Tuesday October 15, 2024 @08:55AM
(#41848066)
> Payload doesn't prescribe i18n like Django.
Not sure what you mean?
> When you need to, you can step down into NextJS and write custom endpoints and the like.
I don't think you were necessarily implying otherwise but one of the Django mantras is "It's just Python" - i.e. you can bypass (nearly) everything Django provides and drop down to doing whatever you want with http requests.
Re:PayloadCMS: Open-Source, Fullstack Next.js Framework
by marpstar on Tuesday October 15, 2024 @11:00AM
(#41849328)
"Prescribe" perhaps wasn't the right word. "Bundle" is probably better. Payload has no official i18n package/module/plugin/whatever.
Re: the NextJS custom endpoint thing -- you're right in that I wasn't comparing to Django but referring to my parent comment about Ghost, which I'd say doesn't really "support" custom endpoints even if it's "possible" -- plus the .yaml routing config is kind of a drag.