While the `(made for static sites)` is probably meant as selling point, I'm afraid it can be a limiting factor. E.g. Stork can be used on your WordPress, Drupa

While the `(made for static sites)` is probably meant as selling point, I'm afraid it can be a limiting factor. E.g. Stork can be used on your WordPress, Drupal or whatever site, quite well I presume; I don't see why not. It would require hacks and some tradeoffs, sure. Many OOTB CMSes come with "search", but that search is poor, the performance problematic and the results are awfull (searching is hard; searching dynamic generic content even more so). I've helped many a Drupal and Wordpress site implement ElasticSearch or SOLR/Lucene back in the days. For the vast long-tail of websites such setups are not an option. Meilisearch is the first that gets closer to a viable option for those. Stork could get even closer. And (unfortunately) the amount of WordPress blogs that would need Stork (alike) for search is vastly bigger than static sites.