Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Home Page Content Retrieval #43

Open
tremainebuchanan opened this issue Feb 3, 2016 · 0 comments
Open

Home Page Content Retrieval #43

tremainebuchanan opened this issue Feb 3, 2016 · 0 comments

Comments

@tremainebuchanan
Copy link
Collaborator

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:

  1. 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.
  2. 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.
@paradoxxjm paradoxxjm changed the title Bug: Home Page Content Retrieval Home Page Content Retrieval Feb 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants