Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Payload (YC S22) – Headless CMS for Developers

news.ycombinator.com

Post reply on HN
Print view View original

101–110 of 139 posts

Re: Launch HN: Payload (YC S22) – Headless CMS for Developers

#101

Post by solardev »

porker wrote: post #100
solardev wrote: post #34

Earlier quoted context omitted.

Personal opinion: Even as someone who used and loved PHP for a decade, Drupal is just awful. It's overengineered and bloated and the documentation is pretty sparse, not to mention it's hard to scale up. Its admin and editor UX is decades being modern headless CMSes. It is extremely powerful, but seemingly built to handle the most extreme edge cases rather than the most common use cases, and a lot of the power is just…

> I've never HATED a technology the way I hate Drupal, before or since. Did you ever work with Magento 1? :)

Lol, we briefly evaluated it and noped outta there quick as we could... phew, bullet dodged :)

Re: Launch HN: Payload (YC S22) – Headless CMS for Developers

#102

Post by cies »

Few things I really need in a CMS:

* allow me to create a localized content (you seem to have this covered).

* a good story for blobs (images, video, PDFs, etc).

* integrated full text search (I do not want to set up elastic search when using a headless CMS saas).

* fully spec'd API (when I have defined a content type, I need some API spec to be updated; openAPIv3 was good, GraphQL is better: so I can generate a client lib).

* some mechanism to know the API was updated (so I can show the "a new version is available, the version you run may no longer work in certain cases, please click here to use the newest version" message somewhere).

* a story on content blocks (say: text, image, text, quote, text, author card) vs embeddable content in text blocks (say: a text block with a way to embed images/etc into it); the latter is really hard to do right imho.

Re: Launch HN: Payload (YC S22) – Headless CMS for Developers

#103

Post by lucas_codes »

cies wrote: post #102

Few things I really need in a CMS: * allow me to create a localized content (you seem to have this covered). * a good story for blobs (images, video, PDFs, etc). * integrated full text search (I do not want to set up elastic search when using a headless CMS saas). * fully spec'd API (when I have defined a content type, I need some API spec to be updated; openAPIv3 was good, GraphQL is better: so I can generate a clie…

Have you ever found one that covers all of these well?

Re: Launch HN: Payload (YC S22) – Headless CMS for Developers

#104

Post by cies »

lucas_codes wrote: post #103
cies wrote: post #102

Few things I really need in a CMS: * allow me to create a localized content (you seem to have this covered). * a good story for blobs (images, video, PDFs, etc). * integrated full text search (I do not want to set up elastic search when using a headless CMS saas). * fully spec'd API (when I have defined a content type, I need some API spec to be updated; openAPIv3 was good, GraphQL is better: so I can generate a clie…

Have you ever found one that covers all of these well?

Nope. Not even close. And always a huuuuuge hassle to work around a missing bit when needed (obviously we can also change the requirements to meet deadline/budget)

Re: Launch HN: Payload (YC S22) – Headless CMS for Developers

#106

Post by jwhiles »

sneek_ wrote: post #49
arraypad wrote: post #48

As someone who's been actively looking for a headless CMS recently, I'm curious about how you compare yourselves to Contentful [1]? From a quick look the key difference is that Payload's backend can be self-hosted, but Contentful is SaaS only. You've said that you're targeting enterprise customers and mention an SLA in that respect. Does that mean your enterprise offering is also SaaS only? [1] https://www.contentful…

Hey there - your points are accurate! Here are a few more: - We are open source / MIT - You can re-use Payload's auth layer in your own apps and with Contentful you can't - Contentful has rigid RBAC, but Payload features function-based access control down to the field level - Payload supports field conditional logic, meaning "check a checkbox, see more fields, uncheck it, extra fields disappear". This is huge. And is…

I'm kind of curious what you mean by 'point and click' here? The contentful web interface is, of course, a web interface - but it's perfectly possible to interact with the API directly for people who want to do so.

Re: Launch HN: Payload (YC S22) – Headless CMS for Developers

#108

Post by adrianthedev »

Guys, amazing work you're doing with Payload. I think it's pushing the way we build apps forward. I love the energy, but you should communicate more sincerely. In your intro video you say "frameworks like Laravel and Rails can be great on building the back-end of your complex apps, but then you're stuck having to build the entirety of your admin panel completely by yourself", and that's untrue. There are solutions out there that help you not build it by yourself.

Again, great energy, but don't lie!

Re: Launch HN: Payload (YC S22) – Headless CMS for Developers

#110

Post by ThibWeb »

imjonse wrote: post #20

Nice. A page comparing this with existing solutions would be useful. In particular how does it compare to something like Wagtail which is a CMS but also has all of Django to fall back on for custom backend work.

I’d be really interested in this as well (disc. – I work on Wagtail). This feels so similar to our vision for the CMS aside for the fact the project has been running for a while and is in Python land.
Post reply on HN