SilverStripe search service implementation

We require that when assets (Asset module) are published and unpublished, the silverstripe-search-service is able to work as expected (for Assets - publishes the Asset URL not the content). Assets are not supported out of the box with the silverstripe-search-service, and this is the work that we’re requesting. The plugin is located here: [login to view URL] Please note that we are not asking for a search ui, the silverstripe-search-service ONLY notices when changes have been made to objects, and makes the required calls to the Elastic AppSearch service. Please note that you don’t need to make the calls to the Elastic AppSearch api, you only need to provide an implementation that observes the Assets objects ( [login to view URL] ). Here is the guide for adding a new document type: [login to view URL] In a test environment we have been able to install and index pages when published/unpublished. This process took less than an hour. The module is configured in the site yaml file like so, ( this configures pages (SiteTree) to be indexed (this is provided out of the box)) SilverStripe\SearchService\Service\IndexConfiguration: indexes: myindex: includeClasses: SilverStripe\CMS\Model\SiteTree: fields: title: property: Title url: property: Url content: property: Content We’d expect (with the work that you’d do) that we’d add a config something like so SilverStripe\Assets\File: fields: url: property: Url And it is expected that when an asset is published or unpublished, that the silverstripe-search-service would perform the expected actions. The documentation states that you’ll need to implement 2 classes Notes: shouldIndex() - all assets will be sent to the search service – these will be assessed by another layer if they should be included for indexing. markIndexed() – this can be a noop To my experience developer (not SilverStripe) this seems fairly isolated (its just operating on Assets) and fairly generic (its just operating of Assets) and should be implementable on a vanilla test environment, then deployed into the clients UAT test environment.