From 0ca72040c7ed8d63ab368518bb9c15980cc85f9a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petar=20=C5=A0panja?= Date: Mon, 5 Nov 2018 14:10:42 +0100 Subject: [PATCH] More details about content view --- docs/introduction/index.rst | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/introduction/index.rst b/docs/introduction/index.rst index cf17436e..9c070dcb 100644 --- a/docs/introduction/index.rst +++ b/docs/introduction/index.rst @@ -228,10 +228,16 @@ configuration, available under ``ngcontent_view`` key: match: Identifier\ContentType: article -Aside from Query Type configuration described below, this is exactly the same as eZ Platform's view -configuration under ``content_view`` key. With this you can render a line view for an article by +Aside from Query Type configuration described below, the format is exactly the same as eZ Platform's +view configuration under ``content_view`` key. Separate view configuration is also needed because we +need to handle it with code that will inject Site API objects to the template, instead of standard +eZ Platform objects. Together with this we provide Site API version of the Content View object, +which is used by the default Content view controller and :doc:`custom controllers `. + +With the configuration from above you you will be able to render a line view for an article by executing a request to ``ng_content:viewAction``. However, that does not mean URL aliases will be -handled by the Site API view configuration. This needs to be explicitly enabled, per siteaccess: +handled by the Site API view configuration as well. This needs to be explicitly enabled, per +siteaccess: .. code-block:: yaml