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

91–100 of 139 posts

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

#91

Post by sneek_ »

sgammon wrote: post #90
sgammon wrote: post #89

Currently working on some SaaS, so I'd like to take a look at this and see if it fits. Curious if there are multi-tenancy features baked in, since you mentioned targeting SaaS companies? Really happy to see all the recent innovation in this space, congrats on the launch :)

For example, can the cloud version do sub-tenants? Is the admin panel exposable to end-users? That sort of thing

Yes! You can absolutely do both sub-tenant / multi-tenant architecture and you can definitely expose the admin panel to end-users.

Both are possible. Thank you for your kind words!

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

#92

Post by sneek_ »

sgammon wrote: post #88

Nit, but, "The most powerful TypeScript headless CMS there is." Should be "The most powerful headless CMS for TypeScript" Or something to that effect. The first time I read the headline, I thought "there is" was preparing for a followup sentence.

Fair enough. That whole headline needs to be rewritten IMO. Describing Payload in one sentence is super tricky and feels like buzzword soup.

We're on it. Actually I think the whole site needs to be redone but I'm never happy with my own work.

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

#94

Post by chimen »

Congrats on the launch. Always wanted something like this to be able to build a more opinionated CMS on top of it for all my projects. My first try was Qards (https://www.qards.io/) but the npm, exhaustingly breaking changes from js libraries + the painful experience I've had dealing with & integrating Netlify CMS into it just left me dry by the time I've actually launched. Was a cool project though and I'm thinking of reviving it one day, maybe with Payload.

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

#95

Post by sneek_ »

chimen wrote: post #94

Congrats on the launch. Always wanted something like this to be able to build a more opinionated CMS on top of it for all my projects. My first try was Qards ( https://www.qards.io/ ) but the npm, exhaustingly breaking changes from js libraries + the painful experience I've had dealing with & integrating Netlify CMS into it just left me dry by the time I've actually launched. Was a cool project though and I'm thinkin…

Oh I can intrinsically relate to what you're saying. I would love to see your project revived on Payload. If you need a hand, please do reach out on Discord!

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

#96

Post by sgammon »

sneek_ wrote: post #91
sgammon wrote: post #90

Earlier quoted context omitted.

For example, can the cloud version do sub-tenants? Is the admin panel exposable to end-users? That sort of thing

Yes! You can absolutely do both sub-tenant / multi-tenant architecture and you can definitely expose the admin panel to end-users. Both are possible. Thank you for your kind words!

One more question: is support for non-node environments on the way? We use a bit of node but we're mostly JVM. Kotlin would be clutch, all good if it's not yet in the cards.

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

#97

Post by Dwolb »

sneek_ wrote: post #77
tootie wrote: post #73

Earlier quoted context omitted.

This guy CMSes. I worked in consulting for many years doing a lot of CMS projects for Fortune 500s. They always bought their CMS products based on the marketing pitch to marketers. It was mostly bs, but the pitch was always focussed on engagement, testing, analytics, funnels, acquisition. I always came with the perspective that your CMS need not and usually should not be responsible for any of that and you can manage…

I resonate a lot with what you're saying. > I always came with the perspective that your CMS need not and usually should not be responsible for any of that and you can manage all of that in the application tier via a tag manager product or the like Totally agreed. A CMS should stick to managing content. And its flexibility should allow it to integrate with services that are purpose-built. In addition to those that yo…

Inbound developer interest = company intent (and segment intent).

Just make sure your growth motion doesn’t stop there and layers in a way to nab the buyer.

Standard way is to outright ask for introduction or outbound, but there’s usually a clever referral mechanism you can discover somewhere.

e.g. “Ask your marketer for demo content” prompt, but with better copy.

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

#99

Post by statictype »

rezonant wrote: post #98

February 37nd, 2022? [1] When did they add so many more days in February? [1] https://payloadcms.com/

I assume they are using date-fns - Saw this bug in that lib once when doing a demo and it was really embarrassing. You would expect a date processing library to somehow manage to not have bugs like this.

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

#100

Post by porker »

solardev wrote: post #34
zmz88 wrote: post #9

Looks like an interesting idea. Other than PHP-hate, why would someone choose this over something like Drupal?

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? :)

Post reply on HN