You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been looking at whether migrating to Hugo could solve some performance issues we have on a fairly large (and growing) Jekyll-based site. As part of my testing I simply copied across about 1000 pages from the existing Jekyll site and placed them inside the Hugo site.
Basically: all folders (regardless of depth) contained "index.md" files, which is perfectly valid in Jekyll and other systems, but these stopped the child leaf bundles from being rendered. I documented the exact problem here: https://discourse.gohugo.io/t/content-depth-migrating-from-jekyll/26635/6
As a newbie I found the content provided by Joe Mooring (see the "explanation" section) very useful. I feel that incorporating it - or something similar - would help a lot of people who are testing out Hugo.
Apologies if I've misused some terminology above.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If you still think this is important, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.
I have been looking at whether migrating to Hugo could solve some performance issues we have on a fairly large (and growing) Jekyll-based site. As part of my testing I simply copied across about 1000 pages from the existing Jekyll site and placed them inside the Hugo site.
Basically: all folders (regardless of depth) contained "index.md" files, which is perfectly valid in Jekyll and other systems, but these stopped the child leaf bundles from being rendered. I documented the exact problem here: https://discourse.gohugo.io/t/content-depth-migrating-from-jekyll/26635/6
The current documentation (https://gohugo.io/content-management/organization) does show site samples with this naming convention, but the impact of an incorrectly-named file is not called out.
As a newbie I found the content provided by Joe Mooring (see the "explanation" section) very useful. I feel that incorporating it - or something similar - would help a lot of people who are testing out Hugo.
Apologies if I've misused some terminology above.
The text was updated successfully, but these errors were encountered: