3 ms·
Agreed. Not least because you're more than likely going to want to pull CMS data into an existing site, or push it into Solr/elasticsearch, or customise the sit
by richmarr 11y ago
Agreed. Not least because you're more than likely going to want to pull CMS data into an existing site, or push it into Solr/elasticsearch, or customise the site in ways the CMS authors haven't allowed for.
I think I'd be more tempted to adopt a CMS library than a CMS framework.
- bryanrasmussen 11y agoI'm having a hard time visualizing what this CMS data would be like or how it would be any different than just having it in Solr/elasticsearch/couchdb to begin with.. Can you or someone else provide me examples of how it would work?
- vlangber 11y agoI'm not quite sure what he meant, but it is common to push data from a CMS to a search engine. Note that most "real" CMSs have a built-in search engine, so the data is pushed automatically. Most seem to use Lucene/SOLR or Elasticsearch. Why not put it in the search engine to start with? So the editors can edit the content. And the search engine is rarely the master of the data.
- 4lun 11y agoI believe they're referring to something like this: http://getcockpit.com/ http://getcockpit.com/