The all-new Kirby 3.0(getkirby.com)

over 4 years ago from Jonathan Simcoe, Co-Founder → A Kids Book About

Mattan Ingram, over 4 years ago
Looks nice, but it appears tied to its templating system which kind of kills its utility to me. I want a headless CMS that I can use to manage content for any templating system I want to switch it to.
1 point
- Jonathan Simcoe, over 4 years ago
  One of the beautiful things about 3.0 is that you can use it as a headless CMS:
  Instead of using Kirby's front-end templates, you can use it to generate a JSON API that can be consumed by a static front-end like Gatsby or Next.js.
  4 points
  - Mattan Ingram, over 4 years ago
    Ohhhh I missed that part, very nice! Definitely going to look into it now.
    0 points
- Florian Karsten, over 4 years ago
  This has been always possible with kirby.
  Working with kirby is very much like if you were working with nosql db where every record by default is also URL/route endpoint (it does not have to be you can have all routing you want).
  You don't have to output HTML. Kirby does not enforce templating engine so you can straight up output json on those routes.
  But there might be even better ways
  - Make your own route endpoints https://getkirby.com/docs/guide/routing this is almost identical to how you do it in expressjs or slim
  - Content representations - https://getkirby.com/docs/guide/templates/content-representations - you might output multiple things at once. /calendar will be html page /calendar.json will be the same thing in json.
  0 points

Now playing