January 19th, Updates
Here is the first release of Graasp for 2026! We made several small improvements and finally applied our policy about trashed items. Read on for the full list of changes.
Here is the first release of Graasp for 2026! We made several small improvements and finally applied our policy about trashed items. Read on for the full list of changes.
We're wrapping up the year with some small but useful updates to make your experience smoother. Also, please note the following notice:
Starting mid-January, items in the Trash that are older than 3 months will be permanently deleted. Please review or restore any important items before then.
Read on for the full list of changes.
We're reaching the end of the year, and we’ve been hard at work improving Graasp’s chatbot app and overall performance. Read further for more details.
Leafs are turning red, fall is well underway. With this new update we are delivering a new library home page, improvements to performance under others. Read below for more details.
With the start of the semester, we are working on some improvements to support your learning and teaching journey. This week we have made some improvements and fixed issues that were signaled by our users. You can find a detailed list of the changes below.
The Graasp team continues to improve the platform in different directions, focusing on consolidating the foundations, from the interfaces to server optimizations. You can find a more detailed list of the changes below.
The Graasp team continues to improve the platform in different directions, focusing on consolidating the foundations, from the interfaces to server optimizations. You can find a more detailed list of the changes below.
We introduce in this new release a range of improvements and fixes that make exporting smoother, as well as a full update of Graasp Library.
This update introduces a completed contact page, refined the import/export functionalities, and various backend optimizations and bug fixes for better performance and reliability. Read further for details.
A backend refactor has been implemented. Read further for details.