NGSTACK-474 update "Site API Content views" section of the docs #43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r Twig templates, extended view config and redirections docs
pspanja
reviewed
Oct 14, 2025
| <h1>Content ID: {{ content.innerContent.id }}</h1> | ||
| <h2>Location ID: {{ location.innerLocation.id }}</h2> | ||
| <h3>Field ID: {{ field.innerField.id }}</h3> | ||
| <h4>Inner Content Info: {{ contentInfo.innerContentInfo }}</h4> |
There was a problem hiding this comment.
These are objects, there should be an example with the property that can be rendered this way.
pspanja
reviewed
Oct 14, 2025
| This template is used for fallback from Site API to Ibexa CMS views. In the following example | ||
| it's used to configure fallback for ``line`` view of ``article`` ContentType: | ||
| Extending configuration from some Content view |
There was a problem hiding this comment.
...from an existing Content view*
pspanja
reviewed
Oct 14, 2025
| It is possible to configure a Content view to **extend** the configuration of another Content view. | ||
| Let's say that you have defined two views that both render a list of items. In one view, | ||
| you want to render them without intro, and in the other one, you want to render them with intro. | ||
| In order to not need the same configuration twice, you can set that one Content view **extends** |
There was a problem hiding this comment.
...In order to do define basically the same configuration twice...*
...you can extend existing view Configuration from another one - using...
pspanja
reviewed
Oct 14, 2025
| params: | ||
| with_intro: true | ||
| This enables you to define the configuration only once and have it be extended to |
There was a problem hiding this comment.
This enables defining the configuration once and extending it in multiple other Content views, overriding the parameters sent (key params) to the Twig template*
pspanja
reviewed
Oct 14, 2025
| This template is used for fallback from Site API to Ibexa CMS views. In the following example | ||
| it's used to configure fallback for ``line`` view of ``article`` ContentType: | ||
| Extending configuration from some Content view | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
There was a problem hiding this comment.
This should be one level bigger, so it shows up in the left side navigation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated "Site API Content views" section of the docs with the following:
content_typeextendskey when wanting to extend the configuration of some Content viewAlso fixed a few typos along the way.