-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Need a way to treat a subdirectory as a new section, while rendering its index as a page #836
Comments
This isn't possible indeed but I think it's something worthwhile to add. We can now bikeshed the option name. |
Cool. :) Maybe |
@jwatt @Keats I found a workaround for doing that as described here: getzola/hyde#22 I suggest a new option on content like: +++
title = "about"
list_on_index = false # will not be listed on section index.
+++
# About my site
sfsdfsdf
|
Hi there! Just wondering if this was implemented / there's a canonical solution. I have a section I've side-stepped this issue by not including a |
No current optimal solution afaik. |
I would also love a solution to this. I want my root page to show paginated news items, and these are organized in a "news" sub-directory. I ended up doing the same as @philpax to avoid showing the rest of the site in the root page contents, but it's clunky and seems ripe for being accidentally broken by future "fixes". Edit: Actually, that doesn't work either because zola just skips rendering the rest of my site altogether. |
I also want to have a page at
The content of +++
title = "About Me"
path = "about"
+++
Hi, here's a little about myself... Technically that means I have an empty page at |
If I have a site example.com and I want to have a page at example.com/about/, I probably want to run the index file in 'about' with my standard page template (not a section template). However, I do not want it to turn up in the
section.pages
of the top-level section.As far as I can tell this isn't possible. If the about page is stored in
about/index.md
then it becomes a page of the top-level section. It's stored inabout/_index.md
then it's treated as a section and can't use the normal page template (objectpage
doesn't exist, etc.). I've tried having the page inabout/index.md
and also having anabout/_index.md
containing just:in an effort to create a new section. But
about/index.md
still ends up in thepages
object of the top-level section.The text was updated successfully, but these errors were encountered: