Feature Request SEBLOD 4 - content type aware SEBLOD HTML Editor, placeable Fields and universal Fields (SEBLOD widgets)

[creative-resort]

observation:

Articles and Blog Posts predominantly consist of body text, which currently is rather monolithic and doesn't allow usage of SEBLOD features within the Body Text HTML Editor. Content-Type data and Fields can not be placed within body text flexibly.

proposal:

1. A SEBLOD HTML editor
   • that is aware of the content type and its fields and allows placement of fields and groups of fields within the editor area, independent of whether those fields are already used in the content type template or not.
2. Use of Content Type specific fields
   • within the SEBLOD HTML editor area (like reusable variables).
3. SELOD widgets / Universal Fields & Groups / content partials,
   • that are not pre-defined fields in the content type but provide a more universally usable structure of data just as fields and groups of fields, and can be placed using the SEBLOD HTML editor.
   • These fields are optional and can be added to a particular Joomla! content (e.g. article,) anytime on the fly.
   • While they are not mandatory for the content-type, they may be enabled or disabled, as well as overridden (customized) for a content type.
   • A backend and frontend view can be defined for this widget, just like for a content type.

Example for 2: In an article, a variable-like piece of data, like a version number, product name, article title, etc needs to be placed within the body text (HTML areas) multiple times at random positions. This is done by using a field defined in the content type.. As soon as the field content is updated in the article editor on the backend, all instances of the field within the HTML Editor area(s) reflect this change automatically.

Another Example for 2: On a product page, data associated with the product and entered using a SEBLOD Field needs to be used within the description (HTML Edotor area) and update automatically once e.g. the data changes.

Example for 3: In a blog post, within the post text, an image is placed. This image together with additional metadata and e.g. image quality options is uploaded through a universal field type mechanism provided by SEBLOD just like any other field that is an intrinsic part of the content type, validated and postprocessed, before being placed at an arbitrary position within the SEBLOD HTML Editor. Upon recall of the post on the frontend, it is also rendered for output on the frontend just like any other usual field, displaying the metadata as defined by the view of this field / SEBLOD widget.

Another Example for 3: In a blog post, within the post text, a quote is to be shown. A SEBLOD widget with fields for Quote text, author name and a URL to the origin of the citation is created within the SEBLOD HTML Editor and placed in the Post Body Text at a random position. On the frontend, the quote is rendered with formatting, styling etc as defined in the frontend view of this SEBLOD widget.