11 comments

  • Sharon HillSharon Hill, 4 months ago

    It was very helpful. Thanks for sharing this.

    1 point
  • James Mikrut, 4 months ago

    I'd be interested to hear about your tech stack on the frontend. I'm currently building a headless CMS called Payload with a few partners and ours has arisen due to the difficulties and nature of polling a third party CMS for our content, when it could be located on the same server that's hosting the frontend.

    Payload is not out yet but here's a link if you're interested - Google has not picked up the domain yet. I'd love to hear any feedback you might have with your frontend and how it polls Prismic's third party API.

    https://payloadcms.com/

    0 points
    • , 4 months ago

      Blogs, legals & FAQs are pretty static, so we don't need to do any polling. We do render the content server side for social media rich cards. I can imagine if you are building something with more IO, it could become cumbersome using a third party CMS.

      1 point
      • James Mikrut, 4 months ago

        Well, even fetching that initial content for social media cards before returning a response from the server will introduce hundreds of milliseconds of latency, right?

        0 points
    • Tom GantzerTom Gantzer, 4 months ago

      Awesome idea. I looked at Prismic, Contentful and some other smaller offerings for third parties but didn't like the external cloud hosting they offered for my small portfolio site. In the end, I begrudgingly used a combination of Wordpress for my CMS, and using the JSON API plugin. I then created a script for my server to call and cache common endpoints every few minutes, which created a local "live" JSON file for my frontend to load.

      This made performance a breeze, without worrying about the bloat of Wordpress plugins to improve the admin experience.

      One day though I dreamed that someone would create a locally-stored headless CMS! Please keep me up to date with this, it sounds very promising!

      1 point
      • James Mikrut, 4 months ago

        I have done the exact same thing as you, literally. WP REST API and all. Got sick of it, decided to create Payload!

        You can subscribe for email updates through the site if you'd like as we will send out an email update every few months with development progress. We are about 4-6m out from completion as of now.

        1 point
        • Tom GantzerTom Gantzer, 4 months ago

          Interesting to see more people using that setup. I have signed up for email updates. Good luck with the development!

          0 points
      • Spencer Bigum, 4 months ago

        Have you tried Next.js? They have a static site generator that’s pretty amazing. You can set it up so that every time you update Wordpress content, it re-exports a new version of the site with updated content. Then you only ping your sever when you export a new version, or anything super dynamic that happens after the user is on the page.

        0 points
      • Stuart McCoyStuart McCoy, 4 months ago

        I just used Craft CMS for my portfolio. Craft CMS 3 is out now and my site could do with a refresh. The backend stores the content and the front-end is left up to the designer/developer. It uses Twig to make it easy to flexible, DRY, reusable front-end templates. It also lacks the bloat inherent with a Wordpress site.

        0 points
  • Shahraz Khan, 4 months ago

    I'd be interested to hear about your tech stack on the frontend. I'm currently building a headless CMS called Payload with a few partners and ours has arisen due to the difficulties and nature of polling a third party CMS for our content, when it could be located on the same server that's hosting the frontend.

    Payload is not out yet but here's a link if you're interested - Google has not picked up the domain yet. I'd love to hear any feedback you might have with your frontend and how it polls Prismic's third party API. https://www.inlogic.ae/services/

    0 points