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
your docs say that this should be possible. probably some omission or maybe its actually broken.
repro steps:
create a brand new elmstatic project
mkdir _posts/foo
mv _posts/2019-01-02-another-post.md _posts/foo
observe that elmstatic says ENOENT: no such file or directory, open '_site/foo/rss.xml'
elmstatic build
Building the site
Compiling layouts
Success!
Tag ──────┬──> elm.js
Page ─────┤
Photo ────┤
Photos ───┤
Post ─────┤
Posts ────┘
Generating pages
Generating posts
Generating tag pages
Cleaning out the output path (_site)
Writing HTML
Generating feeds
ENOENT: no such file or directory, open '_site/foo/rss.xml'
The text was updated successfully, but these errors were encountered:
having a bunch of dummy pages just to make the builder happy seems less than ideal. for example, i keep my posts organized by year so i have to create a page for each year. an about page isn't even relevant for this kind of thing. seems like it would be reasonable to have elmstatic create the foo directory in this case if it doesn't exist yet.
i can understand wanting to keep things simple and opinionated. i'm happy to contribute here, but if you'd prefer to keep things as they are i can go do my own thing instead.
I prefer to keep the current behaviour for now as it's nontrivial to combine arbitrary subdirs in _posts with the existing support for subsections. I'll keep this issue open as an enhancement for future reference.
alexkorban
changed the title
creating a directory under _posts results in an error
Allow posts to be organised in an arbitrary tree of subdirectories
Dec 10, 2019
your docs say that this should be possible. probably some omission or maybe its actually broken.
repro steps:
elmstatic
projectmkdir _posts/foo
mv _posts/2019-01-02-another-post.md _posts/foo
elmstatic
saysENOENT: no such file or directory, open '_site/foo/rss.xml'
The text was updated successfully, but these errors were encountered: