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.com/

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 super hard to build right but it's very important for a good admin experience.

- Payload gives you a local Node API (note: not HTTP / REST / GraphQL.) Contentful does not. With Payload's local API, you can do lots of awesome things within hooks, access control, etc. - and even reuse it in your own endpoints. All of this is impossible with Contentful without going through their HTTP layer

- Payload lets you add your own admin UI views

- Payload has no usage limits

- Payload is code-first, Contentful is "point and click"

Phew. There's a lot more. This all is just top-of-mind word vomit.

Our enterprise offering can either be self-hosted or it can leverage Payload Cloud, once we have it built. Some enterprises opt to manage Payload on their own infrastructure, and just pay us for SLA and premium features like SSO, audit logs, etc. But we do have enterprises in line to use our managed infrastructure as well... so basically, the answer is "both".

Does that help answer your questions?

for what its worth - would take this "word vomit" and polish it up and post it somewhere. Coherence does a great job of this: https://docs.withcoherence.com/docs/coherence-vs-other-softw...

most people wont read it, but the serious people will. and better to claim your narrative than leave it in the hands of users who know less than you about your own market.

That is all useful info, thanks.

For the enterprise offering can you give a rough idea of pricing without having to book a demo etc.?

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-tier SLA, you'd pay a few thousand a month.

For hundreds of seats, with a more robust SLA, your costs would scale linearly, but it's entirely based on what you need.

Does that help?

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.

As Graydon Hoare notes in the comments on GitHub this wasn't the first repo so the real history goes back even further. He's also shared a "prehistory" repo [1] which is interesting to browse. The first commit [2] in _that_ repo is from 2008 but Graydon mentions starting work back in 2006.

Anyway in a sense this repo represents Rust in the real world rather than in gestation, so seems apt to call it the birthday.

[1] https://github.com/graydon/rust-prehistory

[2] https://github.com/graydon/rust-prehistory/commit/1969e085e3...

Gource is great indeed, it can be really mesmerising watching projects with long histories.

To add a couple of "pretty" alternatives (full disclosure: both mine):

- Repography[0] makes posters from the same data, with a few different designs

- Work/Artwork[1] is the same concept but even more abstract

[0]: https://repography.com/

[1]: https://workartwork.org/

Very nice!

I likewise couldn't resist doing something silly with an SVG animation on my profile [1], and I also have a micro startup [2] generating such SVGs periodically to serve as dashboards you can embed in your README.md. I'm interested in more of your predictions!

[1] https://github.com/arraypad/

[2] https://repography.com/

Haha love it!

The SVG posters are cool, if you're looking for some feedback try to find some way to reduce the lag on the site when previewing them. In Safari on a M1 the site slows to a crawl once the poster SVG is loaded, each click takes several seconds to register. Maybe you could do a low res server side rendered version? That could you let users preview their repos without them being able to just right-click the SVG as well

[1] at first I was like ... okay Head is going to the middle and „explode“ to spider view of commits and then I was like oh god yes he did it. The dvd thing.

Hahaha. Great work.

That was my motivation too. Usually with a few seconds of figuring out which bits of the page are ads and what I can safely select and copy!

Great idea, I definitely see the value in having a way to surface content you're not actively looking for.

They appear to cover similar ground, although Plex seems to incorporate other sources of content - not really a point of interest for me.

Would you recommend one over the other if I'm only interested in my own content collection?

I’ve only tried Plex TV and I only use it for my own content collection (to me, the new additions are no-op). I like it and recommend it. It’s free if you don’t want to do hardware transcoding and a few other things. I bought it for $75 lifetime at some point.

So, I can recommend Plex over null. For me, having it automatically lookup meta data and cover art is useful, but it’s by no means unique there.

There are good apps for FireTV and a basic web player. I have an iOS app as well, but I can’t recall ever using it except to browse the library.

A couple of my own projects might also be of interest. Repography [1] creates posters with more of an aesthetic focus, and Work/Artwork [2] takes this even further, creating modern art.

[1] https://repography.com/app/0/neovim/neovim/trunk/poster-surf...

[2] https://workartwork.org/design/mountain

I’d never read the original and I find it fascinating and inspiring.

It’s striking to think that 74 years ago, in the shadow of the last world war, there was such sincere optimism.

It’s shocking how many of these points are still contentious now, even in countries we view otherwise as free and modern.

In this case I think you could use a .mailmap [1] in the repo to associate the old email addresses with current, verified addresses.

[1] https://git-scm.com/docs/gitmailmap

Interesting. One never stops learning new git features...

However, while this works for git (i.e., maps old address to new address in "git log" for example), GitHub does not seem to honor this file.

Well, yes, but maybe they should? It doesn't seem like a huge feature...

Now which commit's mailmap file should be used for the association? Whatever is on the "default" branch currently?

Whatever is in the branch you are looking at? Seems fairly straightforward.

Viewing a specific commit or viewing the repositories' statistics ("insights" tab) both have no attached branch.

in Github or in Git itself? While possible, I don't believe there's many floating commits around.

The other issue of course is that at this point in time, there would not be a .mailmap. Of course, github can then fall back to a .mailmap file in the latest commit of the main branch.

Commits are not usually floating but are very commonly in more than one branch.

What about if somebody clones a repo, then adds a .mailmap pointing all the addresses in the history to their own?

If somebody clones the repo they can even rewrite history. But that is not the same as them being able to claim the ownership of a commit in the original repo.

Then in their clone, they made all the commits. But who cares about their clone?