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
In order to better organize content as the amount of content scales, I'd like to be able to place the posts in sub-directories within the content/ folder. empress-blog should continue to be able to load these posts, since all necessary metadata is contained within the headers of the posts themselves and file structure is unimportant to the generation of the blog.
However, if you try to do this, it throws an error attempting to build the app. It appears that empress-blog is built upon the assumption of a flat content/ file structure at this time.
The text was updated successfully, but these errors were encountered:
We chatted about this on Discord, I would be curious to know that the error is (if it's a build error and where it comes from etc.) because as far as I'm aware there should be nothing explicitly disallowing the use of folders 🤔 it should "just work" but the ids of the posts would have a / in them and I don't know what that would do for direct URLs 🤔
Build Error (AuthorsArray)
ENOENT: no such file or directory, open '/var/folders/2c/f1fdc1s97n5g0vq2068hggww0000gn/T/broccoli-64172uIIfLarRRkg1/out-293-authors_array/issue-4/ada-lockwood-for-state-representative.md'
Stack Trace and Error Report: /var/folders/2c/f1fdc1s97n5g0vq2068hggww0000gn/T/error.dump.ef0cb802a76d16dd871d294ef2270c7d.log
In order to better organize content as the amount of content scales, I'd like to be able to place the posts in sub-directories within the
content/
folder.empress-blog
should continue to be able to load these posts, since all necessary metadata is contained within the headers of the posts themselves and file structure is unimportant to the generation of the blog.However, if you try to do this, it throws an error attempting to build the app. It appears that
empress-blog
is built upon the assumption of a flatcontent/
file structure at this time.The text was updated successfully, but these errors were encountered: