-
Notifications
You must be signed in to change notification settings - Fork 2
Allow indexPagePath to be an array #6
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
base: master
Are you sure you want to change the base?
Conversation
|
Hi there. Interesting change. Having multiple tag index pages may have some implications for |
|
good point. I think we can go a better way then. What do you think about: then using an optional I'd throw in another problem which I'm currently facing, the tagCloud. Usign contexts, that may be solved all together using metadata: then: as it comes almost for free, I'd support context to be an array as well: |
additionally allows context query for tagCloud and getTagurl
|
Applied some changes.
|
|
Looks pretty good, thanks. Will review and merge in a couple of days. I'm a bit slammed at the moment! |
|
Just letting you know I haven't forgotten about this. I went to write some tests a while ago to cover the additional functionality, but I ran into some problems. Will look into it again in the next couple of days hopefully. |
|
no problem 👍 |
Allows
indexPagePathto be a string or an array:indexPagePath: ["tags", "en/tags", "de/tags", "it/tags"]This allows the generation of multiple, filtered localized tags pages using some logic in the tags' layout.