You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the front end passes a query to the api of the application retrieving all posts or pages that are published and flagged for the front page. Additionally, the posts and pages are also ordered by a position on page attribute which denotes where on the front page a post/page should be rendered.
There is no mechanism to:
Prevent a user in keystone to assign a unique position for the content type i.e. he/she could flag a page and a post to appear in the first block of the home page.
Ensure that each post and/or page matching the query returned in the result set has a unique position i.e. if we retrieve 6 posts from the back end, any two or more posts should not have the same number denoting its position on the page.
The text was updated successfully, but these errors were encountered:
Currently the front end passes a query to the api of the application retrieving all posts or pages that are published and flagged for the front page. Additionally, the posts and pages are also ordered by a position on page attribute which denotes where on the front page a post/page should be rendered.
There is no mechanism to:
The text was updated successfully, but these errors were encountered: