eelkenet Posted August 21 Posted August 21 Maybe we can extend the site-wide search to include the body / description of modules as well, be it with less priority? This is an example of a use case: I knew a module exists that uses DeepL to translate site content, but when I searched for DeepL I got 0 results: https://processwire.com/search/?q=DeepL. However, DeepL gets mentioned 5 times in the body of this module page. It was only until I tried searching for terms like 'Translate' that I could find this module. Edit: there is another module that I missed and in my opinion should have popped up. 3
Sanyaissues Posted August 21 Posted August 21 That would be nice. To be honest, I never use forums or website search. By default, I just fire up Google. My usual suspects are /talk /blog /docs site:processwire.com/ deepl site:processwire.com/talk deepl site:processwire.com/blog languages site:processwire.com/docs $page 2
eelkenet Posted August 27 Author Posted August 27 @Sanyaissues Of course I could do that, and thank you for your pointers. But my main take away here is: if you offer a site-wide search, it should be a good search. This is even more important for a site like processwire.com, where you should use any opportunity to demonstrate why PW is a good CMS. The whole idea of users having to use external tools in order to find the content of a content management system website... is rather painful. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now