Launch HN: Payload (YC S22) – Headless CMS for Developers • Hacker News Board

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

#121

Post by sneek_ » Thu, Sep 01, 2022, 4:36 PM UTC

5Qn8mNbc2FNCiVV wrote: post #111

Question: How are migrations handled? Can I rename fields without losing my data? Can I change a relation without losing the underlying data? Are there other edgecases where I lose my data?

Thanks to using MongoDB as a database layer, you will not lose your data if you rename fields. This is a huge benefit for NoSQL in general honestly and it is one of the reasons why we chose to move forward with Mongo initially. We will be supporting Postgres + others in the future, at which point we will be introducing a migrations pattern, but for now, you don't need to worry about that at all.

With Payload as it stands now, to migrate data from one field to another, you can make use of Payload's Local Node API to move data from one property to another with ease.

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

#122

Post by sneek_ » Thu, Sep 01, 2022, 4:38 PM UTC

rolisz wrote: post #105

Honestly, this sounds more like something like Chiselstrike than a traditional CMS

Yeah! That is, Chiselstrike with a purpose-built admin UI that accompanies your backend. That's a big one-up for Payload.

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

#123

Post by sneek_ » Thu, Sep 01, 2022, 4:39 PM UTC

rezonant wrote: post #98

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

Ha actually that is a mockup and I personally wrote that in in there to give peoples' brains a blue screen :)

Sort of an easter egg. I also worked in a bunch of references to Metal Gear Solid (so good) elsewhere in our screenshots as well. This is likely going to all be removed though as I really wouldn't want people to think this is a Payload bug!

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

#124

Post by sneek_ » Thu, Sep 01, 2022, 4:41 PM UTC

jimnotgym wrote: post #119

I surveyed the headless cms market a couple of years ago and I found some good platforms but the pricing just didn't work. I would much rather run our own like this. Good move, and goodluck

Thank you! I agree!

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

#125

Post by sneek_ » Thu, Sep 01, 2022, 4:42 PM UTC

Dwolb wrote: post #97

sneek_ wrote: post #77

Earlier quoted context omitted.

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.

100%.

This is very good insight and I will take it to heart.

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

#126

Post by spdustin » Thu, Sep 01, 2022, 9:15 PM UTC

> Consistent with Payload's goal of making you learn as little of Payload as possible, customizing and using the Rich Text Editor does not involve learning how to develop for a Payload rich text editor. Instead, you can invest your time and effort into learning Slate, an open-source tool that will allow you to apply your learnings elsewhere as well.

I have to say, this callout from the JSON-based Rich Text Field docs [0] really resonated with me. Rather than build out something yourself that would further lock folks into your platform (and force them to customize yet another bespoke tool), you leaned on an existing, mature, and capable framework for rich text editors, Slate [1]. And your stated reason—to “allow you to apply your learnings elsewhere as well”—was really appreciated. It shows a lot of respect for time and resources of the individuals using Payload.

I don’t have a specific need for a headless CMS right this second, but I can promise that Payload will be my first candidate to review when I do. Previously, it would’ve been Strapi, as I’ve used that tool already for several projects. But that one paragraph really struck me.

[0]: https://payloadcms.com/docs/fields/rich-text [1]: https://docs.slatejs.org/

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

#127

Post by sneek_ » Thu, Sep 01, 2022, 10:14 PM UTC

spdustin wrote: post #126

> Consistent with Payload's goal of making you learn as little of Payload as possible, customizing and using the Rich Text Editor does not involve learning how to develop for a Payload rich text editor. Instead, you can invest your time and effort into learning Slate, an open-source tool that will allow you to apply your learnings elsewhere as well. I have to say, this callout from the JSON-based Rich Text Field docs…

Ugh I am so happy that this paragraph resonated with you. I personally wrote it and it's so, so important to me. It represents the ethos of what we're trying to do with Payload. The whole team and I feel very strongly about this.

Thank you for your kind words and I would love to help you as you start your next project with Payload!

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

#128

Post by IYasha » Fri, Sep 02, 2022, 9:08 AM UTC

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…

I had most of this in the times of PostNuke and MD-Pro. How I miss them! :_(

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

#129

Post by predaytor » Fri, Sep 02, 2022, 11:52 AM UTC

perfection

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

#130

Post by IYasha » Fri, Sep 02, 2022, 1:18 PM UTC

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…

Wow. I was seriously considering Drupal as an option for an lod-style minimal-JS site (with mainly news+comments, gallery, wiki, statistics and stuff). Previous CMS I used was quite allright, but maintainers dropped it :( Can you suggest something besides Dripal and WP? (pls not JS)