sneek_

5 ms·

1.
by sneek_ 2y ago
WP made me want to pull my hair out
2.
by sneek_ 2y ago
Check out Payload - fully OSS, modeled after the … few good parts of WP https://payloadcms.com I built it because I was in the same situation as you.
3.
by sneek_ 2y ago
now that we're built on Next.js (3.0 beta), we now use Next.js as an optional head you can still use Payload headless of course with any frontend but out of the box you have everything you need. it's pretty nifty
4.
by sneek_ 2y ago
100%. We are actually working on a little "badge" style thing. Needed bad.
5.
by sneek_ 2y ago
Hmm, one clarification - there is no enterprise Payload version. All of our enterprise features are just plugins - which anyone could build. In this way, would you consider WordPress to be open-core as well, considering the amount of paid p
6.
by sneek_ 2y ago
Fair. Good feedback. For what it's worth, we are actively looking at our licensing model trying to make it easier for situations exactly like yours. Might have some updates for you soon.
7.
by sneek_ 2y ago
Happy to hear this! Thank you for chiming in here. Hope to see you around the community.
8.
by sneek_ 2y ago
Hey! Would love to hear more about this. Performance problems are usually something related to maybe missing indexes in your database for fields that you query on often, or similar. Payload itself is super thin. Can you give me an example o
9.
by sneek_ 2y ago
Payload has a form builder plugin - https://payloadcms.com/docs/plugins/form-builder#form-builde... have you seen that?
10.
by sneek_ 2y ago
Hey there - small to medium orgs can use one of the available community, open source SSO plugins, with the only caveat that they are not officially supported by Payload. Or you could build your own! Question - does the word "enterprise
11.
by sneek_ 2y ago
I think server components have been very badly marketed. They're totally opt-in, so I don't see how this would make React instantly a terrible framework. I for one think they represent a lot of value. If you don't use them, t
12.
by sneek_ 2y ago
Hey! I'm CEO of Payload and want to make sure we resolve any bugs you found. Pretty much the whole team is focused on closing issues right now as we work toward 3.0 stable so depending on when you were trying out Payload, I'd imag
13.
by sneek_ 3y ago
We have a package that allows you to deploy Payload in a NextJS app serverlessly, and it works great. I actually tried bundling as one endpoint early on while exploring with the NextJS approach and it seemed to work perfectly. But honestly
14.
by sneek_ 3y ago
Thank you! That’s one of my favorite features too. Pretty straightforward to implement too. We’ve got some examples in the docs and the repo if you’re interested.
15.
by sneek_ 3y ago
Honestly you nailed the reason why Payload exists. Both the editor AND developer experience are important and when you have both, you end up with a better project. If you need anything as you build, let us know and we will make it happen! E
16.
by sneek_ 3y ago
Awesome to hear! Thank you for your comments!
17.
by sneek_ 3y ago
Hey Sanju - would love to know what you think about Payload ( https://payloadcms.com ). We were in YC S22 and we've done a lot of what you've mentioned. Our ambitions are the same as yours. Maybe we could collaborate?
18.
by sneek_ 3y ago
Hey there - I'm CEO of Payload (YC S22) [1] and you're speaking my language. We're an open-source CMS where you completely own your database. Right now we're MongoDB-only, but we are actively working on adding Postgres s
19.
by sneek_ 3y ago
Don't worry, I've been a designer for 15 years and I know intimately that I can't please everyone. It's hard to get under my skin. That's actually I think what your takeaway should be here - - you can't please
20.
by sneek_ 3y ago
Hi, I made the Payload site Apparently it triggers you. I don't claim that it's perfect by any means (actually I think some of what you're saying is right).
21.
by sneek_ 4y ago
Payload (YC S22) uses GitHub issues solely for bugs—no feature requests, RFCs, enhancements, good first issues, etc. It helps us prioritize, stay efficient, and provide an accurate picture of what a developer can expect to run into at any g
22.
by sneek_ 4y ago
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.
23.
by sneek_ 4y ago
100%. This is very good insight and I will take it to heart.
24.
by sneek_ 4y ago
Thank you! I agree!
25.
by sneek_ 4y ago
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 w
26.
by sneek_ 4y ago
Yeah! That is, Chiselstrike with a purpose-built admin UI that accompanies your backend. That's a big one-up for Payload.
27.
by sneek_ 4y ago
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 s
28.
by sneek_ 4y ago
I totally hear what you're saying. One thing I can say extremely confidently is that while my agency was eating our own dogfood with Payload during 2020/2021, we released some large projects on Payload and have kept Payload update
29.
by sneek_ 4y ago
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!
30.
by sneek_ 4y ago
Thank you! We would love to help support you in your first Payload project if you need a hand. We're super active on Discord. Stop by if you need anything!

More ›