MIME-Types and dynamic loading of all content items with default config

[paulpestov]

Currently we are not able to display all content items with an arbitrary entrypoint URL (collection or manifest) without having a custom config. Although, we have got a default config which let's us display some content at all. We still cannot dynamically display relevant parts of the data like "all provided texts", though.

Also we don't allow to omit the type= declaration and using only the MIME-Type although it is stated in the TextAPI specs. The type= value is an additional specifier to distinguish between different types of content items. In Ahiqar and GFL projects we relied only on that. But other projects may completely omit it and just use the MIME-Type instead. So we need to implement the possibility to display content items by MIME-Type. In the first step, we may just display them without checking which MIME-Type is provided but rather display the ContentView for everything. Later we could display different View components depending on the MIME-Type.

This would provide a big step forward for generic TIDO instances.

AC:

• improve the logic of loading by type= and allow to load without type=:

  • the user config is crucial for that, if nothing declared in view options, we assume that no type= is used for this view
  • if type= is not present, just load the first content item

• for default config scenario:

  • discover all content array items at a TextAPI during app load time
  • display each content array item in a separate panel with a ContentView component
  • update the config in app state during load time so it is not the old default config anymore but a new dynamic version depending on the content provided from the API