When we talk about the image there is no issue with handbars usage - you need to provide image url and description. Your service can responsd with:
{
"banner": {
"url": "http://domain/path_to_image",
"description": "Some description"
}
}Then you can simply consume the service response in your html template (which is fetched from remote repository):
<script data-knotx-knots="services,handlebars"
data-knotx-service="targetservice"
type="text/knotx-snippet">
<img src="{{_result.url}}" alt="{{_result.description}}"
</script>Look at http://knotx.io/blog/hello-rest-service/ where you have nice step by step description.
If we talk about providing full HTML markup for your banner or other targeted component I recommend you to write dedicated extension (called Knot: https://github.com/Cognifide/knotx/wiki/Knot#how-to-implement-your-own-knot). It can call the targeting service which responds with HTML (not JSON) and then put it as fragment content (simply replace fragment markup). To be honest we have a similar solution in our plans. We have the dedicated repository for that extensions: https://github.com/Knotx/knotx-extensions.
Could you please create an issue in this repository and describe your use case in details. It will help us when we will prepare backlog for the next milestone.
"knotx:io.knotx.FilesystemRepositoryConnector": {
"options": {
"config": {
"catalogue": "./library/"
}
}
}
"knotx:io.knotx.HttpRepositoryConnector": {
"options": {
"config": {
"clientDestination": {
"domain": "localhost",
"port": 80
}
}
}
} "knotx:io.knotx.KnotxServer": {
"options": {
"config": {
"repositories": [
{
"path": "/content/.*",
"address": "knotx.core.repository.http"
},
//routing, etc.1.0.0 documentation is here: https://github.com/Cognifide/knotx/wiki/Documentation-1.0.0
there might be small differences - not much changes were since we released 1.0 but there was change in FilesystemRepository (https://github.com/Cognifide/knotx/blob/master/CHANGELOG.md)
