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

Fulltext Search vs. Pagetypes, how to set up a Pagetree #13

Open
effkay opened this issue Mar 18, 2015 · 4 comments
Open

Fulltext Search vs. Pagetypes, how to set up a Pagetree #13

effkay opened this issue Mar 18, 2015 · 4 comments

Comments

@effkay
Copy link
Member

effkay commented Mar 18, 2015

The fulltext search is scoped to search in content pages only.
As we set up sites, usually the home page is a navigation page and would get ignored.
Also, It is not clear wether using home as a navigation page is the best way to go.

@effkay
Copy link
Member Author

effkay commented Mar 18, 2015

... in general, we are lacking clear instruction on what the page types do, and how to best set up a website with qBrick.

@effkay
Copy link
Member Author

effkay commented Mar 25, 2015

Current situation of page types:

  • redirect pages redirect somewhere, do not appear in search results
  • navigation pages are used as top level of a page tree hierarchy. Slug does not appear in children's urls, and navigation pages are also not present in search results
  • content default page type
  • custom: used for mixing custom controller with qbrick page

@effkay
Copy link
Member Author

effkay commented Mar 25, 2015

Suggestion:

Navigation page only makes sense like it is implemented right now at the root level, so:

  • make navigation page pass down slug except when it is in the root level
  • when reaching a navigation page not on the root level, it redirects to its first child page
  • include top level navigation pages in fulltext search scope

@effkay
Copy link
Member Author

effkay commented Mar 25, 2015

😄 🔫 this needs more discussion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant