You can now chose between different working modes :
1) The items are loaded server side from the list template as html
Filtering, sorting and paging is handled clientside par jplist framework.
2) The items are loaded clientside from a webapi as json and rendred from a client side template with handlebars js template for example.
Filtering, sorting and paging is handled serverside by the webapi. The data need to be indexed. OpenContent use Lucene for indexing.
When data is indexed, data can also be filtered, sorted and limit the number of recors from the Filter settings.
By default the detail page of a item is on the main module. But if needed you can now specify an other page.
This is done module menu item Change template.
Each item can have publishing fields : publishstatus (drapt, published), publishstartdate, publishenddate
They are automicaly managed by OpenContent (not published items are only visible in edit mode)
Templates can be defined in the manifest.json for url, page title, meta description and additional meta like open graph.
There is also an OpenUrlRewriter provider available.
In addition to the main data of the module, you can now manage additional data like the items needed in a dropdown list like for categories, tags, ...
For thiss you need to provide a schema.json and options.json and define it in the manifest.json
This is available for end users from the module actions menu.
Additional data : Introduction, Categories, Tags
For the selection of a icon in edit content forms, you have now the abaility to use the new IconField
DNN 8 indroduce breaking changes for razor.
This handled in OpenContent 2.1
Download OpenContent 2.1
List mode for great number of items powered by Lucene
New filter settings for list mode
Additional Data for user managed data like categories, tags, intro text, ...
Detail page selection for list mode
split template selection and template settings
Detail url in ML
Icon picker field (bootstrap glyphicons and fortawesome)
publish status and dates for each item