View Articles

With its 7.0 release, "Armstrong," WordPress brings artificial intelligence right into its core. The promise is appealing: connect an AI to your content in a few clicks. But that default path sends your knowledge off to models hosted by third parties.

That convenience carries a cost few users stop to weigh. Internal content, client files, strategic notes. Anything you hand to a hosted AI can be logged, reused, or placed under a foreign jurisdiction. There is another way, though, sovereign by design, and we will come to it by the end of this article.

Most Tiki Wiki maintenance tasks, from rebuilding the search index to sending notification digests, should never depend on someone remembering to click a button. The built-in Scheduler turns these chores into background jobs: set one cron entry on your server, then manage everything else from the Tiki interface.

The official documentation covers the basics in a few lines; this guide goes further, with the reasoning behind each setting and a set of tasks we actually deploy on client sites.

Your emails and online meetings contain most of your sensitive data: contracts, quotes, strategic discussions, and client files. They also represent your greatest point of exposure, and paradoxically, the area where regaining control delivers the highest return.

In this new installment of our series on digital sovereignty, we move from theory to practice.

The reality is clear. Every email sent through a U.S based service and every meeting hosted on a foreign platform falls under a legal jurisdiction that is not your own. Yet taking back control is far from an overwhelming task. Here's how to regain ownership of your communications, step by step, from simple actions anyone can take to solutions that genuinely keep your data under your control.

With the arrival of Tiki 30, the new Long Term Support release expected in summer 2026 and supported until 2031, your Tiki 27 enters the final stretch of its lifecycle. While it will keep receiving security fixes until 2029, there will be no more functional fixes or improvements. The time has come to plan your migration, without rushing, but without putting it off indefinitely.

Between the two releases, two versions (28 and 29) have deeply modernised Tiki. The list is very long, too long for a single, simple article, so we offer here a concise summary, along with all the links to read the details published by the Tiki community. Important good news: there is no abrupt technological break comparable to the PHP 7 to PHP 8 jump, because that work was already absorbed by Tiki 27. The developers, mindful of user's feedback after earlier, more "muscular" upgrades, have taken particular care to build bridges and update scripts that make it far more painless. In short, the road is clear.

Since our first update in February, the shift toward European digital sovereignty has accelerated faster than in the previous five years. While EU powers are migrating millions of workstations to Linux and Brussels targets opaque recommendation algorithms, the push for sovereign tools is no longer a theory—it is a massive public sector transition to assume European digital sovereignty. Yet, as governments pivot, data vulnerabilities are peaking: three accounts are compromised every second, and major national hacks are exposing tens of millions, making Europe a primary target for global cyber-threats. Governments are moving, which is progress. But where does that leave those without a ministerial budget?

This fourth article explores the rapid evolution of the European regulatory landscape during the past four months and maps out the escalating threats of 2026. Most importantly, it provides a concrete action checklist—categorized by time and effort—designed for professionals who need to protect their data and their clients’ trust without a dedicated IT department. These are simple, scalable measures you can implement right now, within your means and at your own scale.