-
Notifications
You must be signed in to change notification settings - Fork 986
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
Section that is nested under a page takes file path instead of URL path #2368
Comments
I just realised:
is not meant to work, you cannot nest sections under a page. |
I see, I think that mostly makes sense, but consider the following edge case. You have a post about your vacation, which has a commenting section. Let’s assume the comments are pages too. Without allowing sections nested under pages there’s no good way to paginate the comment section. Also, keep in mind that the above directory structure still works, as in it compiles, but it works in a way that defies how people expect it to behave. Once the date from a directory name is removed, it seems safe to assume that further nested parts of the path will descend as so. So, in conclusion, I get what you’re saying and I’ve never in the past needed sections nested within pages, but now that I’ve built a commenting system I do. (See: https://spenc.es/writing/email-as-a-commenting-system/#comments) PS: Also individual comments as pages would allow taxonomies based on the author of the comment, in addition to pagination. |
If we allow something like that, it should be a more general change, something like https://zola.discourse.group/t/proposal-deprecate-sections/1968 |
Bug Report
Note: more info from zola discourse page
Consider the following directory structure for the rest of the bug report.
EDIT: this is fixed in #2369
# The following files /content/posts/2013-06-02_my-vacation/index.md /content/posts/2013-06-02_my-vacation/comments/_index.md
Environment
Zola version: 0.17.2
Expected Behavior
The URL path for comments should be:
Current Behavior
It's currently this:
Step to reproduce
The text was updated successfully, but these errors were encountered: