eZ Platform features/extensions ideas

embed_video_fragment_fieldtype.md

EmbedVideoFragment FieldType

A FieldType that:

• stores a links to an embedded (youtube) video with maybe size and stuff
• stores a list of user submitted "chapters" (e.g. named time references)

Example:

• video: http://www.youtube.com/embed/youtubeid
• width: 640
• height: 480
• chapters:
  • intro: 0
  • installation: 60
  • conclusion: 120

A Custom XmlText tag that generates a linked text to one of the chapters above (if there's a UI, chapters can be visually selected). Example with a "steps" embed video fragment field definition: "see the <ezcustom:EmbedVideoFragment ezcustom:fieldIdentifier="steps" ezcustom:chapter="intro">.

Clicking the links in the rendered text pops up (overlay, maybe partial to keep the text readable if applicable) the video at the right chapter, and ideally stops playing before the next one. With the example above, playback starts at 0 and stops at 60 (start and end parameters of the embed link).

render_locations_as_queries.md

Render locations/content as queries.

Q: With the current named_queries feature, is it possible to easily show the Children of an existing Container ? A: It would require an override of the location_view template... hence: no, it is not.

Use-case

Render the contents of any container using a custom Query, without writing any custom controller.

Config proposal

What would it take to make that both possible and easy ? Could we somehow configure that with an override rule ? It would be easier:

ezpublish:
  default:
    location_view:
      articles:
        match:
          ContentType\Identifier: folder
          Section\Identifier: news
        location_query:
          identifier: latest_articles
          parameters:
            # map parameters from the query_type to data from the rendered location/content/item
            location_id: location.id
            content: content

Would render Folders from the News Section using the location_query controller, with the latest_articles QueryType. The rendered folder's location.id would be passed to the query as the location_id parameter.

The rendered location would also be made available to the location_query template, as "location" maybe, or the content as "content".

Sounds very good! People expect to have embedding capabilities similar to WordPress. I keep an account on wordpress.com, just so I know what the base line expectations for people using it for content entry. I would look at their interface for video embedding for details.