Jump to content
clsource

Processwire as a Headless CMS

Recommended Posts

Hello,

Upon reading these articles

https://dev.to/maxlaboisson/an-introduction-to-api-first-cms-with-directus-open-source-headless-cms-9f6

https://snipcart.com/blog/jamstack-clients-static-site-cms

I was thinking that PW can be used for a Jamstack or Headless CMS with no changes at all.

You can easily create  REST Api with PW or use the GraphQL module

https://github.com/dadish/ProcessGraphQL

 

So ProcessWire is an Open Source Headless CMS since 2010 :)

  • Like 9

Share this post


Link to post
Share on other sites

Maybe I don't fully understand the term headless, but I would have thought that PW is ALWAYS headless, even with our typical way of using the API.

Surely headless doesn't just mean delivery via JSON etc, but rather simply no forced output. I have used PW in the "regular" way for websites, but also as a JSON source for SPA web apps and mobile apps. In my mind, these are all headless, but maybe I I still don't get it, or maybe that is actually what you are saying anyway :)

  • Like 5
  • Thanks 1
  • Haha 1

Share this post


Link to post
Share on other sites
5 hours ago, adrian said:

Maybe I don't fully understand the term headless, but I would have thought that PW is ALWAYS headless, even with our typical way of using the API.

I'd say that technically ProcessWire probably isn't a headless CMS – but it can of course be used as one, and quite effectively for that matter :)

ProcessWire is very much a border case, but my impression is that if you can build a front-end with(in) a CMS, it's no longer strictly speaking a headless CMS. And you can build a front-end with ProcessWire. Sure, you interact with an API, but it's a "local" or "in-app" API, not (only) an external one.

Hope that makes sense. And, mind you, I'm not saying that ProcessWire is worse than a "real" headless CMS – in fact I'd argue that it's a better choice for many use cases, but that's obviously up to debate :P

  • Like 6

Share this post


Link to post
Share on other sites

ProcessWire is even more, it has capabilities to be a

  • conventional CMS with highly configurable Administration Interfaces, Templatesystem, Database Mangement/ Access and render tools for the output of dynamic markup
  • headless CMS providing content data via API (JSON, GraphQL) and optionally static HTML + JavaScript (HUGO/ Jekyll)
  • WAF (Web Application Framework) a platform to build a headless CMS or other App/ SaaS on top of fit

Make your choice! :rolleyes:

 

  • Like 7

Share this post


Link to post
Share on other sites

... and don't forget to read this

 

  • Like 1

Share this post


Link to post
Share on other sites

sigh... I must say some folks are quite good at marketing. I don't blame them. It's a free market. There's nothing I saw in this article that wouldn't be possible with PW (and without any extra modules either), more or less out of the box. What Magnolia calls fragments is apparently nothing more than PW's fields. But I have to hand it to them, they seem to know how to translate all that tech lingo to marketing speak.

 

  • Like 4

Share this post


Link to post
Share on other sites

OMG, not again... https://www.pilcro.com/blog/headless-cms

Quote

So what is it? Headless CMS is a Content Management System without a front-end. There is no theme to choose, no pages or UI to build your web pages. Its Wordpress but you provide the webpage.

There is no presentation layer.

You create the content, but you don’t specify where it is presented. The content itself is only available as raw content that can be requested by apps via a programmatic API.

By that definition, PW is most definitely a HCMS...

  • Like 4

Share this post


Link to post
Share on other sites

I thought about different cms/f and headless cms (for example directus, cockpit). 

Processwire can be used as headless cms out of the box (response with json) or with a rest api module.  Directus / cockpit looks great, but it would be so much easier to use processwire with custom code / modules to add some server side features I think?

Will PW as headless cms bloated by template system and some more non-headless features? Maybe best would be a rest api module with a process module? Would that skip some not needed core parts like template parser? Will that reduce overhead or maybe there isn't really overhead by not needed core features?

Share this post


Link to post
Share on other sites

I know that headless cms has been a hot topic for a while. I've experimented with several frontend frameworks (Angular, React, Vue, etc) and I just don't get it. Maybe for huge corporations with multiple dev teams and big budgets, OK. For 95+% of use cases however, I find headless cms/js frontend to be a major pain with no discernible benefits. From a frontend web UX, they're often slower than a well built PW site with caching (eg ProCache).

For native apps, something like api calls to/from PW/Dart via json would do the job.

Am I missing something other than a desire for JS devs to earn extra $$$?

  • Like 4

Share this post


Link to post
Share on other sites

Personally I'd only do headless cms's with static sites. Where the static site generator pulls from the external cms for building its content. This is great because the cms is only concerned with providing data and the static site generator is concerned with rendering those into html. 

  • Like 1

Share this post


Link to post
Share on other sites

I've used PW in mostly headless mode for a recent project at work.

A new client needed to add a map of case studies to an existing bespoke site that was built by another party, and an easy way to manage them.

I set up a new PW site to manage the case studies, added a basic JSON API as the only bit of front-end, and made a simple Vue app (to be embedded on the client's site) to fetch the data, filter items, and render the map/markers and detail view.

Didn't take all that long to build, and the client is happy with the functionality. Each case study is associated with other bits of information, like contacts, keywords, sectors, location - and PW really made this easy.

  • Like 2

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By JeevanisM
      Hello All,
      Recently I have read a series of articles about some new terms like Headless CMS, Hybrid CMS and Digital Experience Platforms ( DXP). I cannot get a clear picture of these but I could understand that these are different from the traditional CMS as we use now, at least in theoretical level. Does any one here have any better understanding on these topics ? may be what / how we can apply these on the processwire CMS ?
       
      just for the talk
       
    • By HerzBlut
      Hello, 
      I'm looking for a developer to write me an extension for "https://modules.processwire.com/modules/process-graph-ql/". It's about Custom Fields (Repeater and Pro Repeater Matrix). So that I can connect and read them via GraphQL with React. It must be possible to read the different fields of the matrix and get their type (e.g. news, slider, blog etc.).
      If you are interested just leave Skype or e-mail. I am looking forward to possible inquiries
    • By ttttim
      Hi,
      I'm working on a website where in the back-end in one template i have multiple page reference fields using the same conditions (parent and template). Is there a way if i selected a page in field A it won't show up anymore in the list of field B or field C etc?
      I was looking at creating a custom string but i couldn't wrap my head around it.
    • By MischaK
      I'm someone who has been developing websites for a while, mostly doing full stack .NET development and ASP scripting before that, while using Silverstripe and some other PHP frameworks for some smaller projects which worked well enough for quite some time. 
      Now I have some time on my hands and decided to evaluate some different CMS options. 
      Diving in as a newbie into: 
      Wordpress 
      Processwire 
      CraftCMS
      After a short while I decided that Wordpress was out while I'm still evaluating Craft and Processwire. 
      My question is, is there any interest here in reading about my experiences in trying to get the feature set I want up and running, with these other systems?
    • By EyeDentify
      I as have been a bit confused for some time about how the "Markup Regions" functionality in Processwire worked.
      But i have know read a bit more and think that i am getting to grips with it. And Markup Regions is going to be huge.

      To aid me in understanding Markup Regions better i started to read the Source code for the new "Regular" theme in conjunction with the Blog about the markup regions.
      It helped me a great deal to understand the basics and more fine details of it.

      A tip is to open both links and use the Source code of the "Regular" theme while reading the blog post.
       
      The Source code:
      https://github.com/processwire/processwire/blob/dev/site-regular/templates/_main.php
      The Blog post:
      https://processwire.com/blog/posts/processwire-3.0.62-and-more-on-markup-regions/
       
      I hope this could help others starting out with markup regions.
      Just take it slow and read it a couple a times and soon you will see the greatness of markup regions.

      /EyeDentify 
×
×
  • Create New...