A few weeks ago I had the opportunity to meet the Nuclia team, and the first thing that crossed my mind was: with this technology we can put order in the WordPress Documentation.
And that’s what I explained to them, something they received willingly because they are open to collaborating with open-source projects, and more considering that they already have a WordPress plugin and that is the tool they usually use as a CMS.
The Search Engine
So, a Search Engine based on Artificial Intelligence (AI) has been created for WordPress Documentation because it can help to improve the search experience for WordPress users and developers. While there is a lot of documentation available for WordPress, it is often scattered across different websites and maintained by different teams. This can make it difficult to find the information you need, especially if you are new to WordPress.
By using AI, the WordPress Documentation Search Engine can provide a more personalized and relevant search experience. It can analyze user behavior and search queries to better understand what users are looking for and provide more accurate results. For example, if a user searches for “how to install a plugin”, the search engine can use AI to understand that the user is likely looking for step-by-step instructions and provide links to relevant documentation.
Another benefit of using AI in the WordPress Documentation Search Engine is that it can help to surface content that may not have been easily discoverable through traditional keyword-based search. AI can analyze the content of documents and provide more accurate and relevant results based on context and meaning.
Organizing the Sources
The first approach to Documentation has been that it had to be organized, at least, into 2 categories or filters.
The first approach is the type of documentation. Here, at first glance, I have come up with the following:
- HelpHub (End User / Consumer)
- DevHub (Power User / Developer)
- Handbook (Community)
- Team (Internal teams)
- Reference (Functions and Code)
As a second element when categorizing, we have the “team” that it affects. In this case, the list is longer:
- Accessibility
- Blocks
- CLI
- Community
- Core
- Design
- Documentation
- Events
- Hosting
- Internationalization (Locale teams)
- Marketing
- Meta
- Mobile
- Openverse
- Performance
- Photos
- Plugins
- Polyglots
- Security
- Support
- Test
- Themes
- TV
The first Sources batch
The list of sources is almost endless, so you had to start somewhere.
What is certain, for now, is surely excluded, are the support forums because that will require a more advanced classification work, since each locale has its organization. Although it is likely that the English version can be included earlier.
This list has no preference order for the URL / Sources.
Now, we need to wait until the big brain processes all the information.