One of Tiki’s strengths is its ability to manage large volumes of structured and unstructured content trackers, wiki pages, articles, etc. However, as the amount of content grows, organizing it efficiently becomes a real challenge.
Leveraging NLP to automatically suggest tags or categories when users create or edit content would be a huge help (Tiki Syntax)

I find it a little weird to ask if "integrating AI into our beloved Tiki CMS is a good idea" as the very previous line affirm it's already done =)

Perhaps it would be possible to avoid some of the controversy by focusing the discussion on the new functionalities expected, without specifically mentioning AI. AI means everything and nothing at the same time.

And as for generative AIs, I think they should be avoided like the plague. It's non-deterministic, essentially based on non-free datasets, consumes a huge amount of resources, and distracts us from what's essential: making useful and reliable softwares.

Talking about ideas for integrating AI into Tiki CMS, I think you’re referring to generative AI.
Tiki is open-source, and yes, our goal is to deliver software that truly solves real client problems. But we also can’t ignore innovation. Generative AI is growing fast, and I’m convinced that in the coming years, it will become a normal part of most tools.
Many popular apps we use every day like Gmail, Google Sheets, Notion, Figma, Canva already include generative AI features. Personally, I find it very useful, and I believe that eventually, almost every app will include some form of it because users will expect it.

Now, about adding generative AI to Tiki: I think it’s a great idea to start thinking about this early. I’m still learning about Tiki, but I believe AI should be added as an optional layer. The user can choose to activate it. If they do, we should clearly explain the cost in terms of resources.

Models:
There are many open-source AI models available. Some are lightweight and can be fine-tuned using prompt engineering to suit our needs. For example, there's https://ollama.com/, an open-source tool, and Hugging Face hosts a large collection of models: https://huggingface.co/models

Features:
Here are a few ways generative AI could be useful in Tiki:

• Help me write: A small button in the WIKI page editor that lets the user ask for help writing content. The AI can use the context of what's already written to generate useful text.

• Narrative report generation: If we give the AI some data and well-crafted prompts, it can generate high-quality narrative reports or even analyze data, similar to how Gemini works in Google Sheets.

• Chatbot for documentation: This could be a bot that uses the current page as context. Users could ask it questions about the page instead of reading everything. With a bit of RAG (Retrieval-Augmented Generation), the bot could even search the database if the question is about something not on the page.

Security:
The key is to let users run everything locally, either on their intranet or on a private server.

Just to clarify and to start with, in the context of a CMS:

• AI enhances CMS functionality through smart automation and personalization
  • Content recommendations (e.g., suggesting articles based on user behavior)
  • SEO optimization tools
  • Image recognition for media categorization
  • Chatbots for user support
  • Spam detection for comments or forms
• LLMs focus on natural language tasks like writing, editing, and answering questions within the CMS
  • Auto-generating blog posts, summaries, or product descriptions
  • Answering user queries using a chatbot
  • Improving grammar or tone of written content
  • Translating text or localizing content

With a chatbot we could:
- Implement/Improve online documentation for user/admin support
- Answering user search queries, a chatbot could use elements like Wiki page, Article, Trackeritems content, etc.

As an exemple, during Lyon JDLL we've seen and tested ChatMD.
This tools would be able (through conversion script) to have the content of all or part of a Tiki inside a mardown formatted file.
It can be used without external AI (some intranet or companies want to stay aways for external AI) and it can be used in conjunction of an external AI engine.

This is just an example, there may be other similar tools we could use.
Once we have a good recipes, I guess we can reuse for translation and auto-generation of content.

Artificial intelligence is a very large topic.

Particularly Generative AI have made it easy to achieve so many tasks out there. They are trained to be generic. I may be wrong but previously; models were trained to perform only set of predefined tasks but now prompting is the new way to get what we want.

Adoption of new technology come with a lot of frictions and many aspects need to be taken into account before diving deep into any technical implementation.

AI have lot of use cases and each depending of everyone constrains and goals. Tiki Being an open source solution we cannot spend so much time on things our users did not request but we can try to offer them a way to benefit from this AI into their projects, and that benefit can be in any form : automation, content generation, moderation, business intelligence, analytics etc... plus everything is optional; everyone use what he wants. Of course we may not gain any specific reward out of the box but having an integration of any kind may maintain our users and keep them using our CMS. We are in 2025, we cannot "just" ignore this AI topic without any clear "why", we can do something i believe so, let's brainstorm to know what kind of thing can it be...

As for example we were setting up Tiki Hosting, we can have IA as an internal tool that help people generate a tiki theme ONLY when they purchase a hosting space

At the August roundtable meeting, we talked about the idea of using a chatbot at dev.tiki.org as a guide for submitting a bug report. This could be helpful especially for first-timers or other people who don't submit reports often and aren't that familiar with the form fields. The chatbot would ask questions or give instructions like "What version of Tiki are you using?", "Please describe the problem" and so on. The purpose would be to have a more personable interaction. It would also be good dogfooding because hopefully the code could be generalized to be a new interface for submitting tracker data. PluginChatbot?

Maybe this interface could also be opened from Tiki sites' admin dashboard so people wouldn't even have to go to dev.t.o to access it.

I've had good experiences with hostinger.com's AI chatbot, Kodee. I just checked and found that it's open source: https://github.com/hostinger/kodee-demo, so could be useful as a model or to use the code itself. Also, more information here: https://www.hostinger.com/blog/building-kodee .

WordPress’s vibe-coding experiment, Telex, has already been put to real-world use

An AI-powered contextual assistant for Tiki administrators and editors, built exclusively on official Tiki documentation, that helps users understand and configure plugins, trackers, and permissions based on the current page or admin screen.

The assistant would provide explainable answers with references, remain optional, and focus on reducing the learning curve rather than generating content or making automatic decisions.

About project documentation and AI (LLMs), this video about the Tailwind CSS framework is interesting: https://youtu.be/ncAqYntEDGE?si=WtxFsyBfVNTyCzu9. Basically, AI bots scraping the Tailwind documentation have reduced the number of visits by real people to the Tailwind site and so have cut people's exposure to the Tailwind paid products, causing project income to fall and the number of paid devs to be reduced by 75% (well, 3 out of 4 were let go).

So, AI agents can help spread information about a project, help users with their questions, but also come between the project website and the users, to the detriment of the project. This of course is the obvious threat of AI to every content provider on the internet but the details in the case of Tailwind really bring it home.

Since we want to advertise on Tiki for consultant services, etc., this is a problem for our project, too. I haven't yet looked into how content creators, etc. are responding to this.