Why I am switching from Craft CMS to Payload CMS

Поділитися
Вставка
  • Опубліковано 13 вер 2024

КОМЕНТАРІ • 15

  • @jjaimealeman
    @jjaimealeman 11 годин тому

    I was in a similar boat: was seeking the "perfect CMS for my clients".
    As much as I liked Directus, the ability to create hard-coded Collections in PayloadCMS, and then use & duplicate those across projects, is what ultimately sold it me 👍🏻
    BTW: have you given Astro a try?
    It's become my new front-end framework. Some projects I deploy as SSG, and more recent ones are SSR with Payload.
    I've not been this excited about a CMS in a long long time!

  • @AnteZivkovic
    @AnteZivkovic 28 днів тому +3

    Informative video, brother. Look forward to your video about the meeting with the Payload team. I also recently switched to Payload 3.0 and am looking for anything on that topic since it's still in beta and I want a jump start.

    • @WestSideTechnologySolutions
      @WestSideTechnologySolutions  26 днів тому +1

      Thank for your feedback! I did have the meeting with the payload team. Their office is about a 10 minute drive for me! I don't think I'll end up making a video on the topic, but it was cool to meet them and I hope I get to work with them as I get more invested into Payload's system.
      I am also patiently waiting for 3.0. I have some big plans! Thanks for your comment and please let me know if there are any other specific topics you'd like to see regarding payload, or anything in general! Have a great day!

  • @user-ik7rp8qz5g
    @user-ik7rp8qz5g 22 дні тому +1

    I tried both while evaluating stack for one of projects. Made same choice, using it ever since.

    • @WestSideTechnologySolutions
      @WestSideTechnologySolutions  22 дні тому

      What ultimately made you make your decision? I am very curious to hear thoughts from someone who had the same decision to make!

    • @user-ik7rp8qz5g
      @user-ik7rp8qz5g 21 день тому

      @@WestSideTechnologySolutions I dismissed craft after it gave many errors on production hosting and fixing some gave even more (there were no errors in local development). As it was the best solution php could offer, I went to node to search alternatives and tried few. So ultimately I chose it because it had interface translations for admin panel (added couple weeks before I found it) and was easy to push local changes to production

    • @WestSideTechnologySolutions
      @WestSideTechnologySolutions  18 днів тому

      @@user-ik7rp8qz5g I am surprised to hear about the production only errors... What a headache though! Sounds like some very fortunate timing though. Thank you for sharing!

  • @Amitsarker
    @Amitsarker 21 день тому +1

    Payload CMS is excellent and very flexible.

  • @pisitch1
    @pisitch1 23 дні тому +1

    Big fan of Payload. Using it with my team in my full time job now. If you need UI for your client to update client, go with Payload. Otherwise, go with Astro with content collection. You can use fully typed json or TS to manage your contents in version control.

    • @WestSideTechnologySolutions
      @WestSideTechnologySolutions  23 дні тому

      Interesting, I am not familiar with Astro! I will definitely check it out! Thank you!
      I think its cool you use payload for your full time job. That's something I never got to do! Which CMS did you switch from? As you can see, I moved over from Craft CMS. I loved Craft, but payload is just such a better fit for me and much more affordable (open source vs license) for some of my customers!

    • @pisitch1
      @pisitch1 20 днів тому +1

      @@WestSideTechnologySolutions We switched from our proprietary system and was looking at WordPress as an alternative among other SaaS CMSes like Sanity and Prismic. Payload gives the best flexibility with the least vendor lock in.

  • @realitydesigners
    @realitydesigners 13 днів тому

    Sanity is the best