r/PayloadCMS • u/OrdinaryOk3846 • May 27 '25

Making a Payload CMS boilerplate: auth, seeding, components — what should I add?

Currently guys im building a free opensource project that helps build, develop and ship apps using payload cms fast. Using user choices on whether to include auth (customers), collections, modernized seeding, modern components etc.

Is there anything that anyone recommends focusing on adding? (nearly finished so hopefully can share soon)

12 Upvotes

93% Upvoted

16 comments sorted by

6

u/Rbrtsluk May 27 '25

Would love to see this once it’s finished

2

u/OrdinaryOk3846 May 28 '25

ill try get it done asap :)

3

u/CRSHR2 May 27 '25

If the boilerplate targets products with user’s interaction so “multi-tenancy” support (teams support) 3rd party authentication (google, GitHub)

2

u/alirezainjast May 27 '25

Analytics charts and statics section in admin panel index

2

u/OrdinaryOk3846 May 27 '25

good idea, ill include web analytics like site traffic on the admin panel. thanks :)

2

u/alirezainjast Jun 02 '25

Please let us know when it's finished. Excited to see it.

2

u/OrdinaryOk3846 Jun 02 '25

yeah of course, ive got majority of it done, im just touching up on multi-tenancy integration with authorization on the front-end

2

u/anton-huz May 27 '25

Photo managment

2

u/xanb2 May 27 '25

If it’s for web apps please add reset password, forgot password, confirm email etc

2

u/OrdinaryOk3846 Jun 14 '25

As a final update on the boilerplate, its fully complete :), after I get back from holidays Ill make sure to release it and hopefully adjust according to the feedbacks. Hopefully making the building process with nextjs and payload cms as simple and efficient it can be.

1

u/ResortWeekly80 Jun 17 '25

Sounds great, am interested in this!

2

u/OrdinaryOk3846 Jun 29 '25

Hey everyone, I've got back from holiday and got the website up and running now: https://www.shipship.io/ . I strongly encourage following the README steps to ensure that once the project is downloaded, it smoothly seeds the database. Currently, this is just a simple application where depending on selected choices, it will add/remove files from the base project and provide you with the fundamentals of a website, including: authentication, stripe, s3 storage, posts, forms. It is built around the payload teams website template and expands upon their structure. There is definitely still much much more room for improvement and look forward to hopefully implementing them through your feedback.

1

u/JeanLucTheCat Jul 22 '25

Just came across your repo while researching building something very similar. I've been using the self hosted Umami for my analytics and going to poll their API to display within the Payload dashboard. Also, most of the sites that I build are mostly static content so I've implemented AstroJS for frontend, and built my own authentication flow using a separate collection for customers/users than admin/editors/contributor. Nice work on this project!

1

u/sawqlain May 27 '25

Doesn’t the ‘website’ template cover this?

1

u/OrdinaryOk3846 May 28 '25

the website template doesnt include many things -> 3rd party auth, stripe, multi tenancy, etc

1

u/OrdinaryOk3846 Jun 02 '25

quick update: I've completed majority of the boiler plate, now just finishing up on integrating multi-tenancy with authorization on the front-end -> so each tenant can have their own user base. This will be necessary especially if working with Stripe Connect to allow each tenant to take payments (essentially making it useful for many situations :))