sneek_

8 ms·

31.
by sneek_ 4y ago
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
32.
by sneek_ 4y ago
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!
33.
by sneek_ 4y ago
Not yet. When we built the site, Payload's licensing and business model was built around a SaaS model, and was all baked into Payload's frontend. Of course, it does use Payload on the backend (including the entirety of our old Saa
34.
by sneek_ 4y ago
Thanks for the feedback! Our website has changed minimally since launch. In about a month or so, our focus will be shifting back toward sharpening our messaging and presence online. Yes—as you mentioned, Payload is self-hosted, open-source,
35.
by sneek_ 4y ago
Thank you! Yes, all of our first-party offerings are plugins and 100% of their functionality can be accomplished with Payload core itself. No need to fork or extend. Our plugin infrastructure runs incredibly deep and it's super straigh
36.
by sneek_ 4y ago
Well, at its core, Payload is a headless CMS / application framework. There are actually quite a few differences between either of those and a forum software like vBulletin which is deliberately geared toward creating online communitie
37.
by sneek_ 4y ago
Ahh thank you! You cherry-picked my favorite parts about Payload. So much went into having a proper custom block-based field type. That in specific is something that every single project I build has always needed and this is only the start.
38.
by sneek_ 4y ago
Ah awesome! Thanks for the comment! I'd absolutely like to trade experiences sometime. I will certainly send you a message. Looking forward to it!
39.
by sneek_ 4y ago
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 pro
40.
by sneek_ 4y ago
Seriously, it's liberating to -say-. We're so happy with the move. Credit to the community.
41.
by sneek_ 4y ago
Insanely simple. You can opt-in on a page by page basis with NextJS to any data source that you want to use. I LOVE NextJS' paradigms, and we've actually modeled a lot of what we do after its beautiful DX. Great question!
42.
by sneek_ 4y ago
Yep! As our cloud hosting is not yet launched, we don't have the pricing finalized for that but for our enterprise features and SLAs, it's all broken down based on what you need. For 20 seats, a few enterprise features and a lower
43.
by sneek_ 4y ago
You can absolutely do this. You can bake in any type of "review" workflow you can think of, and Payload comes with versions / drafts out of the box as well. It's easy to control who can update the "main" publis
44.
by sneek_ 4y ago
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 func
45.
by sneek_ 4y ago
Yep, but with a lot more admin-specific features like field conditional logic, block-based layout editors, customizable React components, localization, versions / diffs / drafts / preview / autosave, etc. Payload ships w
46.
by sneek_ 4y ago
Sharp eye - we threw it away and went MIT a few months ago! Basically.... we listened to our audience. And it was a great move. So, thank you for giving us the push if you commented or provided feedback in any way!
47.
by sneek_ 4y ago
In my original post, I've outlined our monetization strategy at a high level. And cloud hosting is certainly an aspect of our approach. It's true that some will self-host Payload, and that's awesome. But look at NextJS - you
48.
by sneek_ 4y ago
Just about anything CI-wise you can think of is completely doable with Payload. That's the beauty of being staunchly code-first. I would love to hear more about this at some point too, btw.
49.
by sneek_ 4y ago
Awww dang! Sorry to have missed you. I've used Contentful in a handful of projects in the past and our team's struggles were partially responsible for the creation of Payload. Keep us in mind for your next project - and best of lu
50.
by sneek_ 4y ago
Yeah! We've had a lot of people move to Payload from Netlify CMS. Those that have moved have given us a ton of great feedback in regards to our UX and dev experience comparatively.
51.
by sneek_ 4y ago
Drupal is obviously one of the longest-running content management systems available and they have done a much better job at keeping up with the moving target that is tech, when compared to Joomla / WP. Outside of being written in TypeS
52.
by sneek_ 4y ago
Nailed it. Payload's config is straight up TypeScript. Import a React component, pass it to your config, and boom — it shows up in your admin UI. Everything is written like that and this is certainly where we shine!
53.
by sneek_ 4y ago
Thank you! Yep, the fact that we ate our own dogfood for over a year really helped us fill in the "nice to haves" all over the place. How do you do your content nowadays? Git-based CMS? Markdown? Would love to know!
54.
by sneek_ 4y ago
I lolled at this - gonna cause me to do some introspection, huh. One goal of ours is to make this not the case - but you are 100% right. The whole notion of "app framework / headless CMS" doesn't have a good label so rig
55.
by sneek_ 4y ago
Yeah - Directus certainly provides a lot of value out of the box. We're a bit more razor-focused on a code-first approach vs. Directus, as the content model is stored directly in the database rather than being defined in a version-cont
56.
by sneek_ 4y ago
Hey there - we do have a set of comparisons on our site (linked in the footer of the site), but we don't have a comparison to Wagtail yet. Would be happy to add this to the list!
57.
by sneek_ 4y ago
Thank you! I totally agree. I've been using headless CMS since the start and have ridden along with a few of the options out there, but never trusted them enough to hit production.
58.
by sneek_ 4y ago
Hey, great question. Our target market is enterprise uses of Payload, where we can power critical content-based infrastructure, but that does not solely mean marketing websites. I think that your comment is pointing at one of the areas that
59.
by sneek_ 4y ago
Yeah! The other big difference with Sanity is that the API side of Sanity is 3rd-party. So you never truly have control over the API logic or backend side at all. Whereas with Payload, you control both the admin UI AND the entirety of your
60.
by sneek_ 4y ago
Thank you! WP is a blogging platform from the early 2000's that still uses many of the same code conventions that it started with. It does have a REST API, and you can extend it with plugins to work as a headless CMS, but it's rid

More ›