Next Version of CMS API

Please continue development on the CMS API, basic things like filtering and sorting Items by API is missing and it doesn't make any sense not continuing work on the CMS API, because a lot of people are working with it through NodeJS or Zapier or Integromat or any other external service or backend code and more features would be gladly appreciated. Also being able to have the Item ID as a option to use in the Designer as a variable would be great to send CMS Item IDs through forms for example.

  • Yusuf Arslan
  • May 20 2021
  • Reviewed
API
  • Lyle Malone commented
    17 Dec, 2021 06:37am

    Thanks for the update. I'll be sure to keep an eye on this thread.


  • Jennifer Duran commented
    29 Oct, 2021 07:15am

    Just defining an API and gaining consensus is difficult enough, to say nothing of choosing implementation technologies for bindings (SOAP, ATOM, REST, etc.) But the difficulty is not the only issue. The other issue is that the standards have always been somewhat clunky and difficult to work with. This is likely a result of the committee-driven design process which is typically made up of vendors who by necessity bring their vendor-specific baggage and agendas to the process. More importantly, there’s no real-world litmus test for these standards until much later when the implementations materialize. The mediocre success of CMS standards is no surprise. We need an API standard for interacting with our CMS platforms that can go beyond the technical and political challenges faced by previous API(s) to reach a high level of adoption across the entire development community.

  • Edward Garcia commented
    5 Jul, 2021 09:33am

    The folks at Netlify created Netlify CMS to fill a gap in the static site generation pipeline. There were some great proprietary headless CMS options, but no real contenders that were open source and extensible—that could turn into a community-built ecosystem like WordPress or Drupal.

  • +167