DokuWiki Newsletter Archive

Security Alert: Hosted Wikis Temporarily Offline

Wed, 21 Oct 2026 00:00:00 GMT

Hello Subscriber

This morning, we learned about two critical security vulnerabilities in PHP, the programming language that runs your DokuWiki. These vulnerabilities affect PHP itself, not just DokuWiki, and could allow attackers to execute arbitrary code on affected servers. This could be used to steal sensitive data, run malicious software, send spam, or delete data.

As a precaution, we have temporarily taken all wikis hosted by CosmoCode offline. We took this step to protect your data while the vulnerabilities remain unpatched.

The PHP security team has announced that security updates are scheduled for today at 14:00 UTC (16:00 CEST). We are monitoring the situation closely and will install the necessary updates as soon as they become available. We will restore access to your wikis as soon as we can do so safely.

If you operate DokuWiki or any other PHP-based applications on your own servers, we strongly urge you to take immediate action. Prepare to install the security updates as soon as they are released. If you cannot apply the updates promptly, consider temporarily isolating affected services from the internet.

Further information:

Your CosmoCode DokuWiki Team

Make your Wiki accessible to external AI Agents with MCP

Wed, 19 Aug 2026 00:00:00 GMT

Hello Subscriber,

Welcome to another DokuWiki Newsletter. AI agents are becoming increasingly useful because they can do more than just answer questions. Their ability to use tools allows agents to go beyond what they already know, access information from other sources, and take action on your behalf.

In our previous newsletters, we have focused on our AI Agent plugin for DokuWiki, which brings these capabilities directly into the wiki.

In this issue, we’re looking into using the Model Context Protocol (MCP) to connect DokuWiki to external AI agents and how MCP enables them to retrieve, combine, and act on information from multiple systems.

We hope you enjoy this issue and find it useful.

Your CosmoCode DokuWiki Team

DokuWiki as part of an AI workflow

AI agents become particularly useful when they can work with several systems at the same time.

Consider a support employee working on a customer ticket. The ticketing system contains the customer’s problem, the CRM contains information about the customer, and DokuWiki contains the relevant troubleshooting procedures and product documentation.

An AI agent can combine these sources. It can look at the ticket, find the customer’s information, search DokuWiki for the appropriate procedure, and help the employee work through the issue.

The same principle can be applied to many other workflows. A salesperson can combine an opportunity from the CRM with product information and sales guidelines from DokuWiki. An IT agent can use an alert from a monitoring system to find the corresponding runbook in DokuWiki. Developers may use Claude Code to work with both a source code repository and the documentation in DokuWiki.

Each individual system remains responsible for its own information and applies its own strengths to maintaining that information. The AI agent’s tool use brings the information together as needed.

What is MCP?

MCP, short for Model Context Protocol, is a standardized way of making software accessible to AI systems. It provides the agent with tools specific to the system it shall interact with: an “openTicket” for an issue tracker, a “searchCustomer” for a CRM, or a “readPage” for DokuWiki.

An AI system can connect to several MCP servers and use the tools they provide. This allows it to work with information from different systems as part of the same task. And since tools can not only be used for information retrieval, the agent can also use these tools to change or update information — all it takes is a “closeTicket” or “writePage” tool.

The DokuWiki MCP Plugin

As you probably expected, MCP functionality can simply be added via a DokuWiki plugin. A first prototype of the plugin was released early last year. It provides the basic functionality you’d expect. DokuWiki’s remote API mechanisms are exposed as MCP tools, and authentication is based on the user’s access token — the agent acts on behalf of the authenticated user. This means the same ACLs apply to the agent as they do to the user.

This worked fine for personal use. However, for business use, there were a few shortcomings, which have been addressed in the version recently released in Early Access to our DokuWiki Business Plugin partners.

Connecting to central AI systems

In an enterprise context, you’re probably providing AI access to your employees via a central system such as Microsoft 365 Copilot Cowork, Claude, or ChatGPT. Connecting such a system to DokuWiki raises the question of how to authenticate individual users.

The solution to that is OAuth authentication. The administrator sets up the connection between the AI system and the wiki once. When a user first wants to use the wiki through their AI agent, they are asked to log in to the wiki in their usual browser and authorize the agent to access it on their behalf. The agent then acts with that user’s permissions. All the technical details are handled automatically. This works independently of how users authenticate to the wiki — whether through plain auth, Active Directory, two-factor authentication, or SSO.

Besides making this kind of “connect-once, serve-many-users” scenario possible, the new plugin version also allows administrators to fine-tune which tools shall be available to authenticated agents. You might want to start with read-only tools and only enable write access once you have gained confidence in how your agents behave. Regardless of the enabled tools, ACLs are always honored, of course.

Finally, because Microsoft tends to do things a little differently, we added another feature to the plugin. To add an MCP endpoint to Cowork, you need a special app package that has to be uploaded before users can use the MCP connection. Our plugin provides a convenient way to create the required package right from the admin interface.

MCP or DokuWiki AI Agent?

So, does MCP make the DokuWiki AI Agent plugin obsolete? Not at all. In fact, using both can make a lot of sense.

The AI Agent provides a convenient way to interact with the wiki directly, while an MCP connection can bring your wiki’s knowledge and functionality into other workflows. Actually, the AI Agent’s own tools, like semantic vector search (RAG), can be made available via MCP to let external agents search the wiki even more effectively.

DokuWiki Release "Mort" available

Tue, 21 Jul 2026 00:00:00 GMT

Hello Subscriber,

Welcome to another DokuWiki Newsletter. We are happy to share the latest updates and improvements from the DokuWiki ecosystem with you.

If you find this newsletter helpful, please help us spread the word. Let a colleague or friend know. They can subscribe for free.

Your CosmoCode DokuWiki Team

DokuWiki “Mort”

The new DokuWiki version, nicknamed “Mort”, has been released. As always, it includes many bug fixes, including a few security fixes, as well as several improvements. One notable addition is a new “Copy” button that allows users to copy code blocks directly to the clipboard.

A major refactoring of the search index has also been completed. The result is a more robust and faster search. In addition, the indexing mechanism can now be reused by plugins. This improvement is already being leveraged by the new DocSearch plugin described below.

The biggest change, however, is the option to parse Markdown. Markdown has become the de facto markup standard and is used in countless systems. It is also the default format for most AI chat tools. With this release, wiki administrators can decide how page syntax is handled: classic DokuWiki syntax, Markdown, or a mix of both. The mixed mode will likely be the most practical option for wikis with existing content.

Our hosting customers will receive the update automatically over the next few weeks. If you need assistance with updating, just let us know. We are happy to help.

Document Search

By default, DokuWiki indexes only page content. The contents of uploaded files such as Word or PDF documents are not included in the standard search.

One way to enable searching within media files is the ElasticSearch plugin combined with a document to text converter such as Apache Tika. This is a powerful solution that delivers excellent results. However, unless you are using our Pro Hosting offer or running your own server, setting it up can be challenging. On many low cost hosting environments, it is simply not possible.

In the past, the DocSearch plugin provided a lighter alternative. However, its setup still required command line text conversion tools and relied on a rather fragile method to maintain an index of media file contents.

With the indexing refactoring introduced in Mort, these workarounds are no longer necessary. We completely overhauled the plugin, modernized the codebase, improved the results interface, and integrated it with the new indexing system. In addition, we implemented the ToText plugin, a document to text conversion plugin written entirely in PHP. This means it has no external dependencies.

The new DocSearch plugin is currently available to our DokuWiki Business Plugin Partners.

AI Agent Tools

There is also news regarding our AI Agent plugin. The plugin already provides powerful functionality, giving you direct access to the knowledge stored in your wiki. However, not all relevant information may reside there. For this reason, we expanded the mechanism for adding custom tools to the agent.

For our own wiki, we implemented web search to enrich answers with publicly available information. We also added a tool to search and read files in our GitLab instance. This enables the AI Agent to answer detailed questions about a service’s Kubernetes setup, for example, by combining information from the wiki, public Kubernetes documentation, and configuration files stored in our GitLab repositories.

This is just one example. Custom tools make it easy to integrate AI into your internal and external documentation systems, whether they are ticket systems, CRMs, or custom built solutions.

Talk to us if you would like to discuss custom tool integrations.

Plugin Updates

Several plugins received updates with bug fixes and maintenance tasks as part of our DokuWiki Business Plugin Partner Program. If you would like to support our work, benefit from well maintained plugins, and gain access to exclusive early access plugins and other advantages, please join the program.

Thoughts on "LLM Wikis"

Wed, 15 Apr 2026 00:00:00 GMT

Hello Subscriber

this newsletter is a bit different, Instead of presenting what’s new in the world of DokuWiki, this more of a think piece. What does the advent of AI agents mean for the future of wikis and knowledge management?

We’d love to hear your thoughts on the topic.

Andreas Gohr

BTW: if you haven’t seen what an AI agent integration already can look like, have a look at our video showing the AI Agent plugin in action.

Thoughts on LLM Wikis

The idea of an LLM Wiki as postulated by Andrej Karpathy is currently making the rounds on LinkedIn and in other circles.

The idea is simple: instead of manually managing your wiki, creating pages, interlinking them, making sure the documentation is up-to-date and consistent, you just let an AI agent handle it. The “wiki” becomes a bunch of interlinked pages, read and written primarily by the agent. The interface to the information is the agent itself.

To add information, you dump documents, emails, or snippets into an “ingest” agent. A periodic “lint” agent takes on the role of the wiki gardener, and to get information from the system you talk to the “query” agent.

It sounds magical. Finally, the largest hurdle of wiki adoption is solved: nobody has to write anything down anymore.

When I presented the DokuWiki AI Agent plugin (see last newsletter) to my colleagues, their thinking went in the same direction. But I think the idea rests on a misunderstanding: collecting information is not the same as creating knowledge. A useful wiki is not just a storage layer an agent can read and write, but a shared, collaborative structure that humans can understand, navigate, and trust.

Information is not Knowledge

The goal of a wiki is to aggregate and synthesize knowledge from information. Karpathy hints at the issue when he describes how he runs the “ingest” phase:

Personally I prefer to ingest sources one at a time and stay involved — I read the summaries, check the updates, and guide the LLM on what to emphasize.

Without this close supervision and guidance, you’re basically “vibe coding” your knowledge base. In case you’re not familiar with the term, “vibe coding” refers to the process of creating software using an AI coding agent without ever looking at the created code (sometimes not even knowing how to program). The results can be impressive for a short time, but the larger the scope and the longer the project development, the more vibe-coded software turns into unmaintainable spaghetti code with lots of duplicate code, unexpected bugs, and side effects.

It’s the same with knowledge management: dump ten years of project emails into an ingest pipeline and you’ll get summaries of conversations, but not institutional know-how. Knowledge requires human synthesis and perspective, the LLM can’t do that alone.

What Karpathy actually hints at, when describing how he uses the ingest phase, is not automation without oversight. His approach is less “vibe coding” and more “vibe engineering”. In software development, this describes working with an AI agent where every output is reviewed, refined, and iterated until approved by an experienced human software engineer. It is a different kind of software development, but it is not necessarily faster or easier than traditional development. The human’s role shifts from developer towards architect and QA manager.

In the case of an “LLM Wiki”, it means that unless you want your knowledge base turning into an unknowable black box, you need to keep a very close eye on how the agent organizes the information and what knowledge is synthesized from it, and permanently steer and correct it.

As explained above, you want to keep an eye on what the agents do with the information you feed them. This is made difficult by the system Karpathy suggests. His “wiki” consists of hundreds of markdown files sitting side by side in one directory, with a single index.md providing one-line descriptions and optional categories. He’s explicit: you’re not meant to touch anything here: “The LLM owns this [storage] layer entirely”.

The result is a kind of digital dumping ground: technically searchable, but cognitively opaque. Even with Obsidian providing a graph view or backlink visualization, there’s no real overview, no curated entry points, no intentional hierarchy. Once the number of files crosses a certain threshold, orientation becomes difficult - you can’t easily tell what’s missing, what’s redundant, or where to start exploring.

Traditional wiki gardening solves this by emphasizing human navigation design: choosing page titles, linking paths, organizing namespaces, and summaries that guide the reader. It’s less about storage and more about providing a common thread. Without that human editorial layer, the “wiki” devolves into a bag of loosely connected text fragments - accessible to the LLM perhaps, but exhausting for people to read and trust.

Personal Systems are not Collaborative Wikis

What most people seem to miss in their excitement is the very first sentence of Karpathy’s article: “A pattern for building personal knowledge bases using LLMs.” (emphasis mine).

I have no doubt this system is working great for him. He seems to invest a lot of time into maintaining and refining the data in it. I feel like he’d be great at using a traditional wiki as well.

What his “pattern” is lacking, though, is any notion of how it would work with multiple users. How would the system evolve when prompted by different users with different needs? How can anyone trust the information in the wiki? Who are edits attributed to when agents potentially edit and rewrite whole sections of the wiki at any time? Hallucinations have become rarer with modern models, but they still exist.

Use in a corporate context is even more questionable. There is no notion of ownership, permissions, or approvals at all. While I personally would celebrate the adoption of the “wiki way” where everyone is allowed to see and edit everything, it is very rare for enterprises to adopt that mindset fully.

AI can help, but not Replace Stewardship

The recent hype around OpenClaw illustrates a similar dynamic. OpenClaw promises a personal assistant that manages your email, files, and workflows across every messaging platform you use. And for technically savvy users who take the time to isolate it, restrict its permissions, and audit third-party skills, it delivers. But the vast majority of adopters don’t do any of that. The result: tens of thousands of misconfigured instances exposed to the internet, a skills marketplace flooded with malicious plugins, and critical vulnerabilities that allowed entire agent takeovers from a single website visit.

I fear the pattern will be similar with LLM Wikis: agentic systems promise to remove the hard, tedious parts of a task - but that tedious work is what makes the result useful. Take away the expert supervision and you don’t get magic, you get a mess that’s harder to clean up than what you started with.

I think there are many interesting aspects in Karpathy’s pattern, and I am sure we will see many of them implemented in future wikis, but I don’t think it will magically solve the “issue” of knowledge management being work. Wikis rise and fall with people participating and shaping the information stored in them into knowledge. AI agents can help a lot with that, but they can’t (and shouldn’t) think for you.

Artificial Intelligence times 3

Wed, 25 Mar 2026 00:00:00 GMT

Hello Subscriber

A quarter of the new year has already passed, and artificial intelligence continues to keep us busy. In this issue, it appears not just once but three times.

As always, we’re here to help with any questions using our own kind of intelligence 😉.

Your CosmoCode DokuWiki Team

AI‑Assisted Editing

Editing a wiki page is actually easy, yet many users still hesitate to jump in. A request we hear often is: “Couldn’t we just leave comments instead?”. That approach sounds tempting, but we usually advise against it. When important information becomes outdated and the right details are buried among many comments, a wiki quickly loses its value.
One of our partners came up with a great idea. Why not create a system that feels like a comment feature but actually keeps the content up to date? The result: highlight part of the text, leave a short note, and a language model (LLM) automatically updates that section based on your feedback. As simple as a comment, but with the benefit of real content improvement.

Together with our partner, we developed a plugin based on this concept, tested it, and now offer it as an early‑access version for our Business Partners.

AIAgent – The Next Step After AIChat

AI agents represent the latest stage in artificial intelligence. Instead of answering a single question, a language model receives a task and a list of tools it can use. The model decides on its own which tools to apply and works until it reaches a result. This gives it a kind of agency - turning it into an agent.

While developing our AI‑assisted editing plugin, our team asked whether this concept could also work with our chat functionality. The answer was yes, and that led to the new AIAgent Plugin.

Its interface looks familiar to users of the AIChat plugin, but a lot more is happening under the hood. The AIAgent has two modes: Chat and Edit. In Chat Mode, it behaves as you would expect: ask questions and get answers from the wiki, including semantic search. But the agent can also read pages, list namespaces, or check tables of contents on its own. In Edit Mode, the AI assistant can add or update page content directly while you chat with it.

The new plugin is more flexible in its configuration, too. You can assign different models to different modes, adjust parameters such as reasoning levels for modern models, or create your own modes with custom prompts and tools. All DokuWiki API endpoints can be used as tools, including those of other plugins.

You’ll find a detailed description in the documentation on DokuWiki.org. The plugin is currently available in early access for our business plugin partners.

With AIAgent, we’re introducing the next generation of our AI plugins. AIChat and AIEditor will remain for now - AIChat for knowledge dialogues and AIEditor for targeted edits. In the future, our main development focus will shift to AIAgent, which combines the best of both worlds. The particularly accessible interface of AIEditor might even serve as an alternative entry point to AIAgent later on.

Defending Against AI Bots

LLMs open up entirely new ways to interact with a wiki but also bring new challenges.

Training large language models requires huge amounts of text. To collect it, AI labs large and small automatically crawl the web. Unfortunately, some ignore established standards like robots.txt.

The result can be a surge in server load and traffic until the wiki becomes almost unreachable for regular visitors. Some of these bots use thousands of IP addresses at once, effectively acting like a DDoS attack.

DokuWiki lead developer and CosmoCode team member Andreas Gohr has experienced these problems himself and introduced two possible solutions:

If you need similar protection mechanisms for a wiki or another website, we’ll be happy to help you implement them.

Other Updates

Our website recently received a technical upgrade, and if everything’s working as planned, you won’t notice a thing. Behind the scenes, we’ve moved from Grav CMS to Astro. The static‑site approach fits perfectly with our developer‑focused way of managing content. Of course, we didn’t stop at the standard setup - we extended Astro and customized it to fit our workflow.

A wiki isn’t an Excel spreadsheet, and it shouldn’t be. Still, sometimes it’s useful to perform small calculations within DokuWiki tables. DokuWiki user Sherry Wheeler created the AV Math Table plugin to make that possible.

The next DokuWiki release will require at least PHP 8.2. A corresponding pull request was recently merged. If you need help upgrading your PHP version, we’re here to assist.

DokuWiki Plugin Updates and a Happy New Year! 🥂

Mon, 08 Dec 2025 00:00:00 GMT

Hello Subscriber

The year is coming to a close, and we hope you had a productive one thanks to your wiki. We have a few final DokuWiki-related news items for you before we say: happy holidays and a wonderful new year!

Until next year,
your CosmoCode DokuWiki Team 🥂

DW2PDF Refactoring

The dw2pdf Plugin allows you to export one or more wiki pages as PDFs, optionally with your own CI design. It is one of the most popular plugins — about a quarter of all DokuWiki installations include it. It was initially released by Luigi Micco in 2010 and has since been maintained by the community, most notably by Gerrit Uitslag and Andreas Gohr.

Unfortunately, with the new features and changes introduced over the years, maintaining it became increasingly difficult. When one of our customers requested a way to integrate the IndexMenu sorting feature with PDF exports, it became clear that the time for refactoring had come.

The plugin’s monolithic approach (aka “spaghetti code” 😉) has been restructured into a class-based design that cleanly separates different concerns. During this process, several subtle bugs in rendering and caching were discovered and fixed. A whole set of new unit tests has been added to make future changes more robust. The plugin now also uses the updated mpdf library and is PHP 8.4 compatible. And last but not least, a new plugin event was introduced to address our customer’s request for IndexMenu integration.

The changes are currently being reviewed in a pull request. Our Business Plugin Partners can already try out the new version through our CosmoCode Plugin.

Plugin Maintenance

One goal of the DokuWiki Business Plugin Partner Program is to co-finance the maintenance of the many plugins we have released for DokuWiki over the years. The following plugins received smaller cleanups and updates in the last few months:

Tagging Plugin (keyword tagging for DokuWiki pages)
- fixed cloud display
- replaced the use of deprecated SQLite plugin methods
ImgPaste Plugin (upload new images via copy & paste)
- added support for images when pasting HTML into the Prosemirror Plugin editor
Diagrams Plugin (edit diagrams directly in DokuWiki)
- fixed issues with ACL handling and external images
- fixed issues with PDF export
StructNotification Plugin (email notifications based on struct data)
- added filter mechanism
- fixed issues with command-line support
Farmer Plugin (one DokuWiki installation to run multiple wikis)
- improved animal detection and handling of missing animals
- dependency updates
QuickSubscribe Plugin (one-click email page subscriptions)
- Librarian compatibility fixes

In addition to these code changes, we reviewed and triaged dozens of issues and pull requests.

If you’re reading this newsletter, you’re likely a current or former CosmoCode customer or have been in contact with us about DokuWiki at some point. We believe this newsletter is useful to keep you up to date on our DokuWiki work — and it might also be valuable to people we haven’t yet been in contact with.

That’s why we’ve decided to open up the subscription to anyone interested. So if you know someone who might benefit from this little newsletter, feel free to share our Subscription Form.

And if you missed previous issues or want to revisit a past one, you can now find them all in the archive on our website.

And whether you’re new here or not: if you have any suggestions or feedback for the newsletter, just hit reply and let us know!

General Availability of Plugins

When we started the Business Partner Program, we promised that larger updates and new plugins would be released to our partners first and made generally available later. Since our last newsletter, two such public releases have been made:

The AIChat Plugin received a major update including better support for local LLMs and third-party OpenAI-compatible APIs, as well as new mechanisms to influence context: “current page only” and “full page per matching chunk.” The latter, in particular, has proven quite useful with large-context LLMs.

Apropos local models: we recently set up the AIChat plugin using Ollama at a customer’s location. Experimentation with different models revealed gpt-oss:20b as our favorite in regards to performance and capability.

We also released our full rewrite of the Statistics Plugin, which we presented in the last newsletter. The plugin is now SQLite-based and thus much easier to install — no external dependencies or database setup required.

So if you’re not yet a partner, enjoy these updates — and consider joining!

Add analytics to your Wiki 📊

Wed, 27 Aug 2025 00:00:00 GMT

Hello Subscriber,

Welcome to the latest edition of our DokuWiki newsletter. We hope you find the updates and information useful. As always, please don’t hesitate to get in touch if you’d like to discuss anything.

Your CosmoCode DokuWiki Team

Statistics Plugin

When rolling out a wiki, it makes sense to keep an eye on how it’s used. A big part of that is paying close attention to the recent changes page and having one or more dedicated wiki gardeners.

A “wiki gardener” is someone who maintains and organizes the knowledge base by updating content, fixing formatting, and ensuring consistency and accuracy. Their work helps keep the wiki clean, easy to navigate, and relevant, preventing outdated or duplicated information from accumulating. By doing so, wiki gardeners enhance the wiki’s usefulness as a reliable resource for employees, supporting better collaboration, productivity, and knowledge sharing across the organization.

But there’s also a more technical way to look at wiki use: through access statistics. Seeing which pages are frequently visited, what people search for, or even which user groups are most active can help you understand your wiki better.

For a long time, there was no adequate mechanism to do so.

One option is the statdisplay plugin. It can analyze your web server logs and show some basic statistics and graphs. However, it does not put a specific focus on wiki interactions.
Another option is plugins like googleanalytics or numatomo, which use an external analytics tool to log visitor information. Again, these tools are more focused on public website analytics than wiki use.
The third option was the no longer maintained statistics plugin. The plugin tracks typical website analytics metrics like referring links, visitors, and browsers, but it also focuses on wiki specifics like editors vs. readers, search phrases, logins, etc.

We’re happy to announce that CosmoCode has adopted the statistics plugin and given it a proper overhaul. It is now much easier to install since it no longer relies on an external MySQL database - all data is stored in SQLite. The underlying data schema has been improved and the outdated graphing library replaced. In addition, the plugin now offers fine-grained privacy options to adjust it to your individual requirements (for example, GDPR or your works council). It also includes support for typical UTM parameters to track individual marketing campaigns.

The new plugin is available as a preview to all our DokuWiki Business Plugin Partnership partners.

Plugin Updates

We made some smaller updates to various plugins:

structpublish - we now properly differentiate between editors (people who may write in a namespace) and publishers (people who approve changes), which makes the setup a bit easier and more in line with users’ expectations.
farmer - improvements in handling Animal URLs when running command-line plugins.
sprintdoc - better print styles and several minor CSS adjustments.
dbquery - new placeholders in the config allow for more complex setups when using a wiki farm.
tagging - compatibility fixes for modern PHP and the latest DokuWiki release.

If you use any of these plugins, make sure to update to access these new features and fixes. Feel free to contact us if you want to learn more about using these or other plugins in your wiki.

Spotlight on TYPO3: Viridium Group

At CosmoCode, we not only support DokuWiki but also execute a wide range of complex web projects for our clients. We thought you might be interested in reading about one of them.

Our colleagues from the TYPO3 CMS team recently completed a major relaunch and refactoring project for the Viridium Group. After Viridium acquired several insurance companies, both their own website and those of their new subsidiaries required a complete overhaul. The existing TYPO3 system was upgraded to the latest release, the site structure was reorganized, and the subsidiaries were integrated into the main instance - much like a wiki farm.

Custom Content Elements were developed to enable editors to reuse content across different navigation elements and sites, significantly improving both efficiency and consistency. The design was created in close cooperation with Viridium’s brand agency, ensuring a consistent message throughout.

A key focus of the refactoring was the integration of a third-party remote API by Morningstar, a leading provider of financial research and analysis. Completely redesigned form mechanisms now allow customers to modify their life insurance fund allocations based on Morningstar data. This feature required close collaboration with various Viridium departments and obtained approval from Germany’s financial regulatory authority, BaFin.

Contact us if you could benefit from CosmoCode’s TYPO3 expertise, whether you are starting a new project or planning to relaunch or upgrade an existing site.

DokuWiki Partner Exclusive: Move Plugin PR Bundle

Thu, 22 May 2025 00:00:00 GMT

Hello Subscriber,

Every update carries the potential for incompatibilities, and this is also true for DokuWiki. To avoid issues with plugins during updates, DokuWiki’s internal programming interfaces are kept relatively stable. Changes that may affect plugins or templates are usually marked as deprecated first, before being removed after at least two DokuWiki releases.

The latest DokuWiki release has removed some code components that had long been marked as deprecated. Most plugins continue to work as usual, but some require minor or more significant adjustments.

One such plugin is the move plugin, which is used by many of our DokuWiki Business Plugin Partners. Therefore, we have made the necessary adjustments to this plugin as part of the program and provided them to the plugin’s author as a pull request.

Until these changes are accepted, we are offering our partners the option to install the plugin via our CosmoCode Plugin. We are providing a complete bundle of features that are currently still waiting for review as pull requests in the original repository:

Compatibility adjustments for DokuWiki “Librarian”

This includes not only replacing the removed code calls, but also making adjustments for code that has already been marked as deprecated but not yet removed.
Bugfix for lock file storage

A small fix, but it ensures correct usage of the data directory.
Remote API support

Through DokuWiki’s Remote API, pages and media files can now also be renamed or moved.
Move media and pages together

In many wikis, media files are managed in the same namespace hierarchy as pages. Media files are rarely used across namespace boundaries. In such cases, it is desirable to move the media contained within a page together with the page itself. This feature enables that — both via the rename dialog and a completely rewritten tree manager. In the new tree manager, it is now possible to switch between two separate or a combined tree for media and pages.

The move plugin can now be installed as usual via the partner tab in the CosmoCode Plugin.

If you are interested in our Partner Program, please don’t hesitate to contact us.

Your CosmoCode DokuWiki Team

🦧DokuWiki Release "Librarian" now available

Tue, 20 May 2025 00:00:00 GMT

Hello Subscriber,

Welcome to our latest newsletter! We’re pleased to bring you the latest news and updates on DokuWiki and its ecosystem.

New DokuWiki Release

The latest version of DokuWiki, nicknamed “Librarian”, has been released. This update comes with the usual bug fixes and minor improvements, along with a significant new feature: a revamped Extension Manager for installing and updating plugins and templates.

With this release, you can now access the same update functionality via GUI, command line, and remote API. The API is particularly useful for users managing multiple wikis, as it simplifies automatic updates to extensions from remote locations.

Additionally, the manager now handles dependencies automatically—such as including the sqlite plugin when installing the struct plugin—making plugin management easier. It also provides warnings on incompatibilities, enhancing safety.

You can download the new release from download.dokuwiki.org. We’ll be updating the hosted wikis for our customers soon. If you need assistance with your wiki upgrade, please contact us.

Did you know? DokuWiki releases are named after chararacters from the Terry Pratchett “Discworld” novels. The names are alphabetically ordered, so you immeadiately know that “Librarian” is newer than “Kaos”.

AIChat Update

As part of our DokuWiki Business Partner Program, we’re offering early access to an updated version of our AIChat plugin. With this update, you can now chat directly in the context of the page you’re viewing. This is useful if you’ve already found the documentation you need, but still have questions or want help from the LLM. For example, one customer uses the chatbot to generate a specific configuration file based on the details found on the relevant documentation page.

This update also lets you configure any “generic” LLM provider, as long as they offer an OpenAI-compatible API. This feature might be of particular interest to our European customers, as we’ve configured the AI API offered by IONOS using this new mechanism — a great option for using AI models without sending data to the US.

Interested in becoming a partner? Our partner program offers exclusive benefits like early access to features, preferred support, and opportunities to influence future development. Learn more about the program here.

GoLocal Update

A while ago, we introduced the golocal plugin, which helps linking to local file server resources from within the browser. It does this by setting up a registered protocol handler, so links to local resources work even with modern browser restrictions.

The plugin has proven helpful for several customers and has recently received a few compatibility updates. If you haven’t seen it yet, you can find more details here.

SimpleNavi Update

SimpleNavi remains one of the recommended plugins for creating automatic navigation in DokuWiki, based on namespace and page structure. With the new TreeBuilder mechanism introduced in the “Librarian” release, we’ve made SimpleNavi more flexible—especially for wikis with complex access permissions.

A common challenge is making sure users only see pages and namespaces they are allowed to view. This can get tricky when permissions are nested.

For example: If you have a namespace for each customer like customer:company1:, you may not want every customer to see the full customer: namespace, just their own section. Traditional tree based navigation plugins have trouble here, since they can’t provide access to customer:company1: without access to the customer: level.

This is where the new peek option comes in. SimpleNavi can now look ahead into a namespace to check if there are readable pages further down. In the example above, setting a peek value of 1 allows users to directly access their own namespace, even if they can’t see the top-level customer: entry.

Sounds complicated, but in the end it’s exactly what the name “SimpleNavi” promises: simple navigation that just works.

We hope, this newsletter gave you some inspiration for your daily work with DokuWiki. For questions, feedback or support requests please contact us any time.

Your CosmoCode DokuWiki team

Start 2025 with Smarter DokuWiki Search and more…

Tue, 28 Jan 2025 00:00:00 GMT

Dear Subscriber,

Happy New Year 2025! We hope this year brings you success and innovation in all your endeavors. And speaking of innovation, we’re starting the year with a couple of improvements to help you get even more out of your DokuWiki installation.

🛠 RenderRevisions Plugin: Smarter Change Detection

Do you use approval or review workflows in your wiki? Then you might have encountered this challenge: While DokuWiki tracks changes when someone edits a page directly, it doesn’t detect when content changes automatically - for example, when pages include dynamic content from databases, external sites, or other wiki pages.

Our new RenderRevisions plugin solves this by automatically incrementing the page revision number whenever the rendered content changes, even if nobody edited the source directly. This signals to other plugins and users that the content needs attention - perfect for:

Triggering review workflows when included content has changed
Ensuring approval processes catch all relevant content updates
Maintaining compliance by making sure no changes slip through unnoticed

🔍 ElasticSearch Plugin: Next Level Search

The ElasticSearch plugin takes your wiki’s search capabilities to the next level by replacing DokuWiki’s built-in search with enterprise-grade technology. Unlike the standard search, ElasticSearch understands the natural structure of language - for example, it knows that “running,” “ran,” and “runs” are all forms of the same word, making your searches more intelligent and comprehensive. It presents results in easy-to-navigate pages and shows relevant text snippets for all results, helping users quickly find what they’re looking for.

One of its most powerful features is the ability to search within uploaded documents. Whether you have PDFs, Word documents, or other file types in your wiki, together with Apache Tika, ElasticSearch can index and search their complete content, making them as accessible as your wiki pages.

We’re excited to announce significant improvements now available through our Business Plugin Partner Program. The plugin has been completely refactored for better maintainability, and comes with powerful new features:

Smart Search Assistance:
- Autocompletion suggests search terms as you type
- Automatic spelling correction helps users find what they need even when they make typos
- Support for the familiar @namespace syntax to narrow down your search scope
Enhanced Search Experience:
- Filter results by file type (including PDFs and PowerPoint documents)
- Improved filter interface shows active filters at a glance
- Cleaner search results with visible attributes like language and tags
- Preview thumbnails for image search results

These improvements have been made possible in part through the support of our valued partners, which is why these new features are available to Business Plugin Partner Program members first. By becoming a partner, you not only gain immediate access to these advanced capabilities but also directly support the development of future innovations like this.

🌐 Professional DokuWiki Hosting & Setup

While the ElasticSearch plugin brings powerful search capabilities to your wiki, setting up and maintaining ElasticSearch and Apache Tika properly requires additional server expertise. Tika is the technology that enables ElasticSearch to extract and index content from your uploaded documents - it processes text and metadata from PDFs, Word documents, and even recognizes text in images. Together, these tools create a powerful search experience, but they need proper setup and maintenance.

If you’d rather focus on your content than server administration, we can help in two ways:

Fully Managed Hosting
Leave the heavy lifting to us. With our professional hosting service, we handle your entire DokuWiki infrastructure—including expertly configuring ElasticSearch and Tika. Here’s what you get:
- Automatic backups and updates
- Professional maintenance and monitoring
- Optional AI-powered features
- Everything professionally set up and maintained by our expert team
Custom Setup Support
Prefer to keep your wiki on-premises? Our team can assist with a tailored setup of ElasticSearch and Tika on your own servers, ensuring everything runs smoothly from the start.

📄 DokuWiki Word Import, Partner Program and more...

Tue, 26 Nov 2024 00:00:00 GMT

Hello Subscriber,

In this newsletter, we’ve once again compiled some interesting updates about our DokuWiki plugins for you. Perhaps there’s a new feature or two that might pique your interest. Additionally, we have news about the DokuWiki Business Plugin Partner Program.

If you have any questions or require any of our DokuWiki services, please do not hesitate to contact us.

We wish you happy holidays and a happy new year! 🎄🥳

Your CosmoCode DokuWiki Team

Word Import: Efficient Transfer of Documents to the Wiki

Ideally, all the accumulated knowledge of your company should be documented in the wiki. However, in practice, this often isn’t the case, as transferring existing content can be a tedious task.

With our Word Import Plugin, we’ve developed a solution to simplify this process. The plugin enables the import of .docx files into the wiki, automatically converting the content and formatting into DokuWiki syntax. Images embedded in Word documents are also extracted and made available directly in the DokuWiki Media Manager.

The current public version of the plugin already supports importing basic Word files. DokuWiki Business Plugin Partners additionally benefit from an Early Access version with extended functionalities, including enhanced handling of Word formatting, image alignments, links, and even support for mathematical formulas. Furthermore, this version enables bulk importing of entire folders of Word documents, further increasing efficiency.

AI Chat with Local Models and Google Gemini

Our AI Chat Plugin has received some minor updates. Google has now made its Gemini model available in Europe. The AI Chat Plugin can now utilize this large language model (LLM) as well. Additionally, the latest models from OpenAI, Anthropic, and Groq have been added.

For those who prefer not to transfer their data to the cloud, there’s the option to run pre-trained large language models locally—provided appropriate hardware is available. The simplest way to achieve this is through the open-source project Ollama. Our Chat Plugin can now be configured to communicate with an Ollama instance.

ProseMirror: Copy & Paste for Images and HTML

Uploading images via copy & paste into the wiki has long been possible thanks to the imgpaste Plugin, but only with the standard DokuWiki editor.

With a new update to the plugin, this functionality is now also available for users of the ProseMirror WYSIWYG Editor. But that’s not all: In addition to individual images, you can now paste longer HTML texts—for instance, when copying content from a website. Linked images contained in the HTML are automatically downloaded and saved in the DokuWiki Media Manager.

DokuWiki Business Partner Program Launched

As announced in previous newsletters, our DokuWiki Business Plugin Partner Program aims to explore ways to create a stable, future-ready foundation for the DokuWiki ecosystem.

Through the partner program, we can ensure the continuous maintenance and development of critical DokuWiki plugins. Our partners gain exclusive early access to new features and updates before they are publicly available.

We are thrilled to have already welcomed our first partners, who can now take advantage of the Early Access version of our Word Import Plugin. If you’re also interested in a partnership, don’t hesitate to reach out to us!

Frequently Asked Questions from Our Readers

Thank you to everyone who provided valuable feedback following our last newsletters. Some questions tend to come up frequently, so we’d like to address them briefly here:

“I want to support the program but have trouble securing a budget for it.”
The partner program works similarly to a traditional software license. If your company already has a budget for software licenses, the partner program should fit right into that.

“How does Early Access work?”
As a partner, you’ll receive a license key (token), which you can enter in the CosmoCode Plugin. The plugin will then display all available Early Access versions, which you can install with just a click.

“I don’t currently need new features. Does the partner program still make sense for me?”
Absolutely! Even if you don’t currently require new features, the partner program enables the ongoing maintenance and compatibility of existing plugins. This provides the regular updates that improve the stability and security of your installation.

“Does the partner program replace CosmoCode’s support?”
No, CosmoCode will continue offering all regular services related to DokuWiki, including installation and configuration, troubleshooting, and the development or customization of plugins based on your needs. The partner program complements these services by supporting the long-term stability and security of your DokuWiki installation in the background.

“Which plugins are supported under the partner program?”
The selection depends on the needs of our partners. We focus on plugins that are most commonly used and in high demand. Currently, our primary focus is on complex and widespread plugins, like the Bureaucracy Plugin and the ProseMirror Plugin. The scope of support will also depend on the number of participating partners.

📯 Reminder: Feedback on DokuWiki Plugin Partner Program

Mon, 07 Oct 2024 00:00:00 GMT

Hello Subscriber,

Recently, we introduced you to our new DokuWiki Business Plugin Partner Program, and today we’d like to follow up to gather your feedback. We’ve already received some valuable responses, and we’d like to kindly remind those who haven’t shared their thoughts yet to do so. Your feedback is crucial in helping us tailor the program to best serve the needs of the DokuWiki community.

For nearly two decades, CosmoCode has actively supported the DokuWiki community by developing a wide range of plugins and contributing to the DokuWiki core. Thanks to these ongoing efforts, DokuWiki has grown into a platform that is just as robust and capable as commercial software.

With the new partner program, we aim to take innovative steps toward ensuring the long-term stability and growth of the DokuWiki ecosystem. Even if you’re not currently interested in the program, a brief response would be highly appreciated. Your feedback is essential in helping us chart the best path forward for future development.

You can still find all the details and conditions on our website: DokuWiki Business Plugin Partner Program.

Best regards,

Your CosmoCode DokuWiki Team

⚛️ DokuWiki Business Plugin Partner Program

Tue, 24 Sep 2024 00:00:00 GMT

Hello Subscriber,

Plugins allow you to customize DokuWiki to fit the specific processes and requirements of your company. Like DokuWiki itself, the plugins are Open Source and therefore generally available for free. However, the development and maintenance of plugins requires a significant amount of time and resources.

In the past, we have developed numerous DokuWiki plugins from scratch or adapted existing ones to meet our clients’ needs. However, ongoing maintenance and further development of these plugins are only feasible if adequate funding is secured. This is particularly true for complex plugins, such as the Bureaucracy Plugin, where the costs can be substantial – expenses that often do not justify the investment for a single company.

For this reason, we would like to introduce you to our DokuWiki Business Plugin Partnership Program today. With this program, you can support the maintenance and further development of essential DokuWiki plugins and co-finance them together with other companies.

Your benefits as a partner:

Early access to new features and updates
Influence on the development and prioritization of plugins
Ongoing maintenance and compatibility updates
Priority support for reported bugs and inquiries

We plan to launch the partnership program in the 4th quarter of 2024. Until then, we would love to learn more about your needs as a potential partner and are very interested in your feedback:

Would you like to participate in our partnership program?
Which plugins are particularly important to you?
Are there any aspects you would like to see in such a program?
Are there any points that are unclear or that you would like to have explained in more detail?

Simply reply to this email or schedule an appointment for a personal conversation. We look forward to your feedback!

You can find all the details and conditions on our website: DokuWiki Business Plugin Partnership Program.

Your CosmoCode DokuWiki Team

🧩 DokuWiki Plugin News

Thu, 27 Jun 2024 00:00:00 GMT

Hello Subscriber,

As part of our DokuWiki support, we handle requests from customers across various industries and applications. In doing so, we constantly create new plugins and further develop existing ones, always driven by our customers’ requirements. Below, we would like to briefly introduce some of these developments. Perhaps one or more of these solutions might be suitable for your needs?

We would be delighted to support you with your DokuWiki usage as well. Whether with one of the plugins mentioned below, update support, or consultation and programming. Feel free to contact us.

Best regards,
Your CosmoCode DokuWiki Team

AIChat

Our AIChat Plugin continues to be very popular - no wonder: it provides a completely new approach to the knowledge that lies dormant in your wiki. We’ve made some smaller internal updates to the plugin.

The biggest innovation is how the plugin generates the index for the Large Language Model. Instead of indexing raw wiki syntax as before, pages are now converted into a formatted text format using a special renderer. This allows the LLM to access the output of plugins, and also ensures compatibility with the include Plugin.

The new format also supplements the indexed data with structural information such as the current namespace and the titles of the parent namespaces. This gives the LLM additional context when interpreting the information.

Surveys

Our new Questionnaire Plugin allows you to create simple surveys within the wiki. Questions and possible answers can be defined in the wiki syntax, and all registered users can fill out the corresponding questionnaire.

Administrators can approve questionnaires and end surveys as well. The collected data can then be downloaded as a CSV file. The plugin provides a simple alternative to much more complex tools like Google Forms or Survey Monkey. The advantage: all data remains on your wiki server and does not end up on third-party servers.

In homogeneous networks, users often have access to shared file storage on one or more central file servers. It is desirable to be able to link to files stored there easily within the wiki. This used to be very simple, but in modern browsers, linking to local resources is no longer possible for security reasons.

A few years ago, we discussed the possibilities in a post and mentioned a theoretical new option: the use of a so-called protocol handler. Here, the browser informs a locally installed program about the link to be opened, and this program then loads the requested resource. Our new Plugin golocal implements this approach, creating a new way to integrate DokuWiki with the rest of the company infrastructure.

User Authentication via Database

It is well known that DokuWiki can work not only with local users but also utilize other sources for authentication if needed. Setting up an ActiveDirectory connection is certainly one of the most common services we offer as part of our DokuWiki support, but oAuth connections are also becoming increasingly popular.

Another method that should not be overlooked is authentication against an existing, classic relational database like MySQL, MariaDB, or PostgreSQL. Especially public wikis in particular, often do not operate alone but are complemented by other community tools. Be it forum software, an existing login area on the website, or even a CRM. With the authPDO Plugin included with DokuWiki, such user databases can easily be used in DokuWiki. We are happy to help with the configuration of the necessary SQL statements.

Documenting Software Versions

Some of our customers use DokuWiki to document their own software products. Where this software follows a classic release cycle, there is often a desire to separate the documentation into corresponding software releases. One approach is to use a namespace per version, which is copied into a new namespace upon release. This approach is relatively simple but presents some practical challenges. Two of our new plugins address this.

The VersionSwitch Plugin implements a simple switch that allows users to switch between documented software releases at any time. Similar to how the Translation Plugin allows switching between different languages. The plugin can be easily integrated into the sidebar using its syntax. The configuration ensures that the switcher is only displayed when you are in the software documentation. Of course, this also works for multiple products in different namespaces.

The SearchNS Plugin allows the standard search box of the wiki to be extended with a dropdown for namespace selection. This way, users can restrict their search to a specific product or product version.

🧠💬 DokuWiki AI Chat Updates

Wed, 03 Apr 2024 00:00:00 GMT

Introducing the new AI Chat Plugin

Last November, we introduced our first version of the DokuWiki AI Chat plugin. This tool uses OpenAI’s ChatGPT large language models (LLM) to make your wiki more interactive.

The plugin offers a fresh way for users to find information on your wiki, alongside the usual navigation and search options. Users can simply ask questions, just like they would to a colleague, and get the information they need! The plugin uses modern vector-based similarity search techniques to find the right wiki pages and uses them to provide relevant context to the LLM when answering users’ questions.

A lot has changed in the world of language models since last year, and we’re pleased to announce the release of a new version of the plugin with several improvements reflecting these changes.

The plugin now supports models provided by OpenAI, Anthropic, and Mistral, expanding the choice of chat models from two to eleven. Adding new model providers and models in the future is straightforward. For example, when Google decides to make their Gemini model accessible in Europe, we can easily incorporate it. Additionally, we’ve begun experimenting with using local or self-hosted models, which could offer future usage options where data sharing with external providers must be avoided entirely.

The decision on which model to use depends on various factors such as speed, reasoning abilities, supported languages, pricing, and the content you’re dealing with. There isn’t a one-size-fits-all solution. We’ve found it’s best to test out the content of the specific wiki and the usual questions users ask to figure out which model mix works best for each case.

In this new release, administrators will discover an expanded array of settings to manage the interaction between the plugin and the language model and how relevant context is selected. Moreover, administrators can now restrict the use of source material by namespace. Users of the Struct Plugin will be pleased to learn that the AI chat plugin will now use struct page data to identify relevant sources.

We’ve also implemented some minor updates to improve the design and layout of the chat interface. Notably, we’ve expanded the input area to encourage users to ask longer and more complex questions.

We believe this plugin to be an excellent way to improve the usefulness of your wiki in your organization. It’s an easy first step into the new world of AI. If you’re interested in implementing the AI Chat plugin in your wiki, please feel free to reach out to us for assistance. We’re happy to help!

🆕 New DokuWiki Release "Kaos" available

Wed, 14 Feb 2024 00:00:00 GMT

Hello Subscriber!

As you may have already noticed, a new release of DokuWiki has recently been published: Version 2024-02-06a, Code Name “Kaos”.

In addition to the usual bug fixes and improvements in code quality, this version offers even better compatibility with the latest PHP versions (the minimum requirement is now 7.4). The remote API has been completely modernized and now supports JSONRPC. Old log files are now automatically deleted to save space. You can view all the changes on the official DokuWiki website: Release Changes

As always, we recommend updating as soon as possible. Only by using the latest software can you ensure that your data remains secure and that you can benefit from all the new features and plugins.

If you have booked a hosting package with Wiki updates at CosmoCode, we will update your Wiki to the new release in the coming days. No action is required from you.

If updates are not included in your hosting package, or if you operate the Wiki in your private network, you are welcome to contact us. We support you with the update and all issues related to DokuWiki, including programming and consulting.

👋 Greetings from Berlin
Your CosmoCode DokuWiki Team

Happy Holidays from the CosmoCode DokuWiki Team 🎅🎄☃️

Wed, 20 Dec 2023 00:00:00 GMT

Hello Subscriber,

As the year draws to a close, the DokuWiki team at CosmoCode would like to extend warm wishes for a relaxing holiday season and a joyous New Year. 🥂

Throughout this year, we have continued to implement numerous exciting wiki solutions for our clients, along with the development and enhancement of various plugins. We would like to take a moment to showcase a small selection below. Perhaps one or two may pique your interest?

In the coming year, we would be thrilled to continue supporting you in your use of DokuWiki. Whether it is about one of the mentioned plugins, update assistance, or consulting and programming services, please don’t hesitate to reach out.

We wish you a wonderful holiday season and are looking forward to working with you in the upcoming year.

Yours sincerely,
Your CosmoCode DokuWiki Team

🤖 AIChat

The AI Chat Plugin was developed as part of our ongoing research project, WiWien. This plugin seamlessly integrates a chatbot into your wiki, capable of comprehending natural language and providing answers to any inquiries regarding your wiki’s content.

AI Chat Plugin

🔐 Encrypted Passwords

Do you need more security for some sensitive content in your wiki, such as passwords, beyond the access control lists (ACLs)? If so, EncryptedPasswords might be the solution for you. True to its name, this feature enables an additional layer of encryption for specific content.

EncryptedPasswords Plugin

📊 Diagrams

You can use the Diagrams plugin to generate graphics and diagrams directly within DokuWiki, such as flowcharts, organization charts, timelines, or other infographics. Individual elements can be linked to specific wiki pages, thus adding more context. For more demanding usage scenarios, we have introduced an embed mode, in which diagrams are seamlessly incorporated into the source text of the page, providing full integration into the page’s history.

Diagrams Plugin

🔍 ElasticSearch

The ElasticSearch plugin serves as a replacement for the native DokuWiki search, introducing a professional search engine. Beyond standard features like pagination, result previews, and word stemming commonly found in internet search engines, this plugin extends its functionality to include searches within uploaded files, such as Word and PDF documents. Furthermore, if you employ the translation or tagging plugins, the search takes into account your translations and keywords, enhancing the overall search experience.

Elastic Search Plugin

🗃️ Struct

The Struct plugin allows you to manage structured data in the wiki. Data is entered via forms based on predefined schemas. Of course, this data can be linked to regular wiki pages and used as additional metadata. Once entered, data can be aggregated and filtered. The plugin is particularly popular with our customers in quality management. Process descriptions, instructions and document control can be managed much better with this plugin than with on-board tools alone. In special cases, other, often independently developed, struct modules can also help.

Struct Plugin

✅ Struct Publish

The Struct Publish plugin is an extension for the Struct plugin mentioned earlier, serving as a modern iteration of the widely-used Publish plugin. It encompasses nearly the entire spectrum of functions provided by Publish. Moreover, it enables the definition of distinct release workflows tailored to specific wiki areas (e.g., namespaces), and provides the flexibility to assign version numbers or names. Looking ahead, the plugin is intended to support workflows based on stored structured data.

Struct Publish Plugin

🔑 oAuth

The oAuth plugin facilitates authentication on DokuWiki through external services, whether it’s a Google Workspace account or an Azure Directory. This streamlines the process of centralizing user management for your wiki.

oAuth Plugin

DokuWiki Newsletter Archive

Security Alert: Hosted Wikis Temporarily Offline

Make your Wiki accessible to external AI Agents with MCP

DokuWiki as part of an AI workflow

What is MCP?

The DokuWiki MCP Plugin

Connecting to central AI systems

MCP or DokuWiki AI Agent?

DokuWiki Release "Mort" available

DokuWiki “Mort”

Document Search

AI Agent Tools

Plugin Updates

Thoughts on "LLM Wikis"

Thoughts on LLM Wikis

Information is not Knowledge

Opaque Storage is not Navigation

Personal Systems are not Collaborative Wikis

AI can help, but not Replace Stewardship

Artificial Intelligence times 3

Hello Subscriber

AI‑Assisted Editing

AIAgent – The Next Step After AIChat

Defending Against AI Bots

Other Updates

DokuWiki Plugin Updates and a Happy New Year! 🥂

Hello Subscriber

DW2PDF Refactoring

Plugin Maintenance

Newsletter and Archive Available to the Public

General Availability of Plugins

Add analytics to your Wiki 📊

Statistics Plugin

Plugin Updates

Spotlight on TYPO3: Viridium Group

DokuWiki Partner Exclusive: Move Plugin PR Bundle

🦧DokuWiki Release "Librarian" now available

New DokuWiki Release

AIChat Update

GoLocal Update

SimpleNavi Update

Start 2025 with Smarter DokuWiki Search and more…

🛠 RenderRevisions Plugin: Smarter Change Detection

🔍 ElasticSearch Plugin: Next Level Search

🌐 Professional DokuWiki Hosting & Setup

📄 DokuWiki Word Import, Partner Program and more...

Hello Subscriber,

Word Import: Efficient Transfer of Documents to the Wiki

AI Chat with Local Models and Google Gemini

ProseMirror: Copy & Paste for Images and HTML

DokuWiki Business Partner Program Launched

Frequently Asked Questions from Our Readers

📯 Reminder: Feedback on DokuWiki Plugin Partner Program

⚛️ DokuWiki Business Plugin Partner Program

🧩 DokuWiki Plugin News

Hello Subscriber,

AIChat

Surveys

Windows File Share Links with golocal

User Authentication via Database

Documenting Software Versions

🧠💬 DokuWiki AI Chat Updates

Introducing the new AI Chat Plugin

🆕 New DokuWiki Release "Kaos" available

Happy Holidays from the CosmoCode DokuWiki Team 🎅🎄☃️

Hello Subscriber,

🤖 AIChat

🔐 Encrypted Passwords

📊 Diagrams

🔍 ElasticSearch

🗃️ Struct

✅ Struct Publish

🔑 oAuth