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.
In this week’s release, we introduce a couple of improvements and fixes in different areas of Webiny. Let’s check them out!
Added refresh content button (a38b458)
A small but useful addition can be found in the content editing form. We added the refresh content button, which, as the name itself suggests, refreshes the content entry you’re currently looking at. This can be useful if for some reason the data isn’t up-to-date (for example, another user made updates on it in the meantime), and you want to get the latest data as quickly as possible, without refreshing the whole page.
Ref fields are always referencing the correct revision (#1204
Until now, every time a content entry would reference another content entry via the Reference field, it would always point to a specific content entry revision, even if new revisions of the referenced content entry were created. From now on, the reference field will, respectively, always point to the latest and published revisions, on READ (e.g. myApi.net/cms/read/production) and MANAGE (e.g. myApi.net/cms/manage/production) APIs.
Note that this new functionality will not work on previously saved content, meaning, ref fields on existing content entries will still behave like always — point to a specific content entry revision (instead of the latest / published, like described above). In order to “fix” those, you will need to open the entries that contain a value in the ref field save them. This will cause the links in the background to be updated, and from that point on, everything will work as expected for that particular entry. If you have a lot of data that needs to be updated, let us know, we might help you with creating a simple database script (it’s fairly simple).
Give Webiny a try by following our Quick Start, which will guide you through the initial setup steps.
If you have an existing Webiny project, you can upgrade your project by running yarn upgrade.
And, just in case you’ve missed it, check out the full changelog**.
Our CEO, Sven Al Hamad is invited to the UK Serverless event next Tuesday, September 8th at 12 pm! (GMT+1) 💢
Speaking about hidden pitfalls that come with having a serverless infrastructure and how to overcome them using an open-source framework for building full-stack serverless applications.
✅ Register here.
👍 Join the Meetup here.
CommodoThis week, we completed our 21-part video series that covers Commodo — Webiny’s #1 library of choice when it comes to data-modeling and working with the application data. In it, our lead developer and creator of the Commodo library, Adrian, shows you everything that there is to know about it and how to use it as efficiently as possible. 🥁
Learn the basics of Commodo from the Core Ideas, Data Validation, Nested Fields, Custom Higher-Order Functions, Dynamic Hooks, and Storage.
To advanced topics such as Storage — advanced queries, hooks. Reference fields many-to-one & one-to-one, one-to-many, many-to-many.
Our Lead Developer Adrian** **guides you through your Commodo journey ⚡
Show some 💛 by subscribing to our YouTube channel, hitting the like button, and leaving some comments along the way 🎉
In this tutorial, Webiny’s DevRel Albiona guides you through the tutorial to create a portfolio website to showcase your projects and your blogs using React, Webiny Headless CMS, and Apollo GraphQL. After setting up your portfolio website, you will be able to focus all of your creativity on the content for blogs and projects.
We encourage everyone to get involved and contribute, regardless of their experience level. Read the contributing guide, and if you still run into problems, just give us a ping on Slack, we will help you out.
Our development team is on standby to help your in-house team to learn and adopt Webiny — all free of cost!
We are looking for a member to join our team. If you are interested? Apply for the Full-Stack JavaScript Engineer role.
Since we are a small team, in this role, you’ll have a significant opportunity to directly influence the technical and product design choices we will make.