Add blog post v0.54.0

docs/blog/posts/v0.53.0.md

@@ -1,5 +1,5 @@
 ---
-date: 2026-02-26
+date: 2026-01-31
 categories:
   - Release notes
 ---
@@ -9,15 +9,15 @@ categories:
 Welcome to Perses v0.53.0! In this release, on top of many improvements and bug fixes, we have introduced several
 changes that break the compatibility with previous versions.
 
-These changes have been thought through carefully to improve the overall user experience and maintainability of Perses. We hope
+These changes have been thinking carefully to improve the overall user experience and maintainability of Perses. We hope
 even if it will make the upgrade process a bit more complex, you will stay with us and enjoy the benefits of these
 improvements.
 
 While you can read this blog post to have details about the changes and how to upgrade, we are also providing a
 [migration guide](https://perses.dev/perses/docs/upgrade-guide/) that is more condensed and focused on the steps
 required to upgrade from previous versions to v0.53.0.
 
-On a different topic, we are happy to be able to list [Logz.io](https://logz.io/) as a new official company using
+On a different topic, we are happy to being able to list [Logz.io](https://logz.io/) as a new officially company using
 Perses in production. Welcome to the Perses community!
 
 If you are a company using Perses or contributing to it and want to be listed as an adopter, please follow
@@ -52,7 +52,7 @@ the plugin.
 
 This change is important as it will allow in the future to manage multiple versions of the same plugin and facilitate
 the migration from one version to another. We are planning to introduce automatic migration tools in future releases to
-help users upgrade their plugins seamlessly. Except if a plugin is introducing breaking changes that cannot be
+help users upgrade their plugins seamlessly. Excepting if a plugin is introducing breaking changes that cannot be
 automatically handled, the upgrade process will be handled by the Perses backend using cuelang script contained in the
 plugin package.
 
@@ -93,11 +93,11 @@ max_version -> maxVersion
 
 In order to simplify the build of the docker image, we have changed the default user used in the container from `nobody`
 to `nonroot`. As a based image we are using now `gcr.io/distroless/static-debian12:non-root` instead of
-`gcr.io/distroless/static-debian12:latest`, which gives us a non-root user by default.
+`ggcr.io/distroless/static-debian12:latest`, which gives us a non-root user by default.
 
 ### What does it change?
 
-This change can impact users who are using as a database the file system inside the container, specially when running
+This change can impact users that is using as a database the file system inside the container, specially when running
 the container with docker (not within Kubernetes). In that case, you should ensure that the `nonroot` user has the right
 permissions to read and write into the database folder. If this is not the case, when upgrading the image, you will face
 permission errors when Perses is trying to load the data coming from the file system.
@@ -256,7 +256,7 @@ languages and provide a better experience for non-English speaking users. The i1
 used `react-i18next` library, which provides a powerful and flexible solution for managing translations in React
 applications.
 
-For the moment, the i18n is really limited as it only contains a few translations for few languages. The main goal of
+For the moment, the il8n is really limited as it only contains a few translations for few languages. The main goal of
 this change is mainly to get the i18n support in place and have a framework to easily add new translations in the
 future.
 
@@ -324,58 +324,16 @@ security:
 - `plugin start` is now able to discover the port used by rspack to serve the plugin in development mode, so you don't
   need to provide it anymore.
     - There was also an issue when loading a plugin in development with no schema defined, it is now fixed.
-    - When stopping the command, there was some orphan process left, it is now fixed.
+    - When stoping the command, there was some orphan process left, it is now fixed.
     - As mentioned before, the CLI has been updated to be compatible with the new dev plugin API introduced in this
       release.
 - `lint`: when you were using local plugin to validate the dashboards, it was mandatory to have the plugins extracted in
   a folder. Now you can also provide the plugins as an archive like it is the case for the Perses server. The command
   will extract the plugins before starting validating any data.
 
-## Support of Dashboard Tags
-
-This release adds support for dashboard tags, allowing users to organize and categorize their dashboards more
-effectively. Tags provide a convenient way to search for and filter dashboards. You can assign multiple tags to any
-dashboard and use them to quickly find related dashboards across your Perses instance.
-
-![Perses Tags](../../assets/images/blog/v053/perses-tags.gif)
-
-## Timezone selector
-
-Thanks to [Christoph Richter](https://github.com/christophrichtersap) from the community, a timezone selector has been
-added to the dashboard settings, allowing users to choose the timezone for their dashboards.
-
-This is a long time wanted feature that is finally available in this release. The work was started initially
-by [Aditya Pimpalkar](https://github.com/AdityaPimpalkar) and then completed by Christoph. Thanks to both of them for
-their contribution!
-
-The timezone selector is available in the dashboard time settings. By default, the timezone is set to "Local", which
-means that the dashboard will use the local timezone of the user's browser. However, users can change it to any timezone
-they want, and the dashboard will display the data accordingly.
-
-In case you are changing the timezone and then you are sharing the link of the dashboard, the timezone will be preserved
-in the URL, so the person who is opening the link will see the dashboard in the same timezone as the one who shared it.
-
-![Timezone selector](../../assets/images/blog/v053/timezone-selector.png)
-
 ## Plugin improvements
 
-### Table plugins actions and selections
-
-This release adds support for table actions, allowing users to perform custom defined actions based on table data
-either in bulk or individually with a new selection provider. These are the supported action types:
-
-- *Webhook*: Makes an HTTP request to a specified URL with the configured method.
-- *Event*: Triggers a custom Javascript event with the selected data as the payload.
-
-Action payloads are defined as templates, and use the same variable replacement syntax allowing flexible integrations.
-
-This change was added to all the table plugins including: *Table*, *TimeSeriesTable*, *LogsTable* and *TraceTable*.
-
-The following configuration will allow to execute actions in bulk for the selected rows, this is possible
-clicking on the action on the panel header. The action can also be executed in individual rows clicking on the action
-icon for each row.
-
-![Perses Tags](../../assets/images/blog/v053/table-selection-actions.gif)
+// TODO list of improvements, ideally give major changes and improvements for each plugin.
 
 ### GO-SDK Change in the way to define a query plugin
 
@@ -447,8 +405,10 @@ Celsius (°C) and Fahrenheit (°F) temperature units are now available for panel
 On top of that, this release is also introducing two new data-sources: VictoriaLogs and ClickHouse provided directly by
 the community.
 
+// TODO: write more about these two data-sources, highlight their features, and who did it.
+
 Note that since these two data-sources are provided by the community, they are not officially supported by the Perses
 team.
 And as such, soon we will come with a governance model to manage community plugins. In later release, these plugins
-might be removed from the main images, depending on the governance adopted. You will still be able to use them by
+might be removed in the main images, depending on the governance adopted. You will still be able to use them by
 installing the datasources in your Perses instance.