Heads up! This article was written before Webiny 6.0 was released and may contain outdated information.
Webiny is the AI-programmable CMS that gives enterprises full control. Build, extend and automate your content operations with a platform designed to be shaped by both developers and AI agents.
We launched the Serverless Headless CMS on June 5th.
It’s been a week since we launched our Serverless Headless CMS and now we did another release with lots of features and bug fixes. 🚀
We encourage you to join our slack community team and show us your support by either contributing or starring(★) our repository. This is what keeps us going!
As always, let’s start the update by giving a shout out to our new contributors 👏
Kudos to these wonderful people:
We encourage everyone to get involved and contribute, regardless of their experience level. Take a look at our contributing guide and if you still run into problems, just give us a ping on Slack, we are here to help you! 🚀
Moving on, let’s take a look at this release’s changelog!
In previous versions, when you deployed your API, there was one really large resource (~25MB). It was an Image Transformer (part of the File Manager app) which depends on the sharp library to manipulate images. This caused serious problems to users with slower/unstable internet connection. So we came up with a little package that contains AWS Layers you can simply link to your Lambda functions. We host those layers for you in multiple AWS regions, so you don’t have to worry about it. This greatly increased the deployment speed and removed the problem for slower connections.
The other problem, and the main reason for slow deploys, was the fact that each Lambda was creating its own IAM Role. Now we deploy one single role, with the policy you can control yourself, and we simply link it with all the Lambda functions. This thing alone cut down deploy time by 50%!!!
Upon uploading files, by default, the File Manager app uses 25 MB as the max file size, and if that wasn’t enough, you couldn’t increment the limit in an easy way. But, thanks to jmrapp1, you can now set the minimum and maximum file upload size directly from the newly added File Manager settings.
Instead of a single “Save” button in the form footer, we’ve created dedicated “Save” and “Save & Publish” buttons, and placed them in the form header. Having two separate buttons is more clear to the user, and also, having them in the header is more practical, since the header is now always visible, even if you scroll to the bottom of the form.
You can now have a “multiple values” setting enabled for both Rich Text and Date/Time fields.
Via the header search bar, you can now easily search all of the created content. Just type in your query, select the content type, and press Enter. The search will automatically be performed across all content of selected content model type, including all available locales.
Hint: you can always bring up this search bar using the “/” shortcut.
With the help of one of our community members, Rahul Suresh, we managed to squash a very annoying bug with Security installation and password validation. Thank you for spending your weekend with us Rahul!
Along with the above-mentioned improvements, we also managed to get some bug fixes resolved as well. For example, deleting a content model will immediately refresh the GraphQL schema as expected (#988). Model and field names starting with a number will immediately be rejected (#988 — same PR) because otherwise, the GraphQL schema would become invalid. It’s also worth mentioning that content model fields get automatically unlocked once there are no existing content model entries in the system anymore (#978). This enables the user to change or remove content model fields that are no longer in use or ended up in the model by mistake.
You can create a new project using the regular procedure or upgrade your existing v4.0.2 projects by using our handy upgrade tool. See the instructions in the Github Release.