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
Updated developer documentation and support. We know that Webflow Developers have often been left to fend for themselves, so we’re excited to launch an updated developer site that not only contains all the reference materials you need, but also new user guides, code samples, and support channels for the developers in the Webflow community.
For more on our commitment to developers, watch the keynote from Webflow Conf 2022.
3
In progress
0
In progress
3
In progress
2
In progress
0
In progress
0
In progress
0
In progress
.svg){kind=logo}
Just having a proper sort and limit would be wonderful. We currently have to manually increment offset every time we publish a new blog post that we want featured in our app. Very crude.
You would think for performance sake Webflow would not want us to get every record in the collection just to parse it on our end rather than being able to filter the records on the call.
Yes to this a million times.
Please add a search or filter endpoint to the collections API.
For More Valuable Info Check Here: https://upserss.onl/
Listing out collection items desperately needs filter and sort. Otherwise it's pretty wasteful to get hundreds of items and filter manually.
Thanks for the update. I'll be sure to keep an eye on this thread.
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.
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.