The publisherIntegration strategy requires quite some effort on the side of a publisher; the CMS needs to be extended, and from then on editors have to select Kalooga widget content with an article. By using the autocreate feature, overloaded widgets can be used in a site without without CMS adaption. As a consequence, content editors don't select widget content with an article. This task can be deferred to other people, or an automated process.
The concept works as follows; just like without auto-creation, the publisher sets up a base widget in which settings like colors and dimensions are tailored to suit the publisher site template. The site template is extended with HTML code which retrieves a widget, and this code contains the publisher id and a content id that uniquely identifies an article, blog post or page for a publisher. Now, if a new article is published, and its page is first retrieved by a browser, an overloaded widget is created, but nothing will be shown (no content has been selected). Kalooga will assure a process is set up to fill these automatically created widgets with content, either manually or automatically. After the autocreated widgets are filled with content, the page will display them properly.
The HTML code typically that needs to be put in a site template typically looks like:
<script src="http://publishing.kalooga.com/overloadWidget
?publisherId=123456&overloadId=${content_id}
&autocreate=1"/>