Support normal pages as well about jekyll-postfiles HOT 13 OPEN

@nhoizey has collections support been implemented yet? I'd be willing to implement it.

from jekyll-postfiles.

I'll get on it soon... may take a few weeks to get started (nearly christmas & all).

from jekyll-postfiles.

I'm not sure whether it'll work with #47 then. that patch specifically goes through files in collections.

from jekyll-postfiles.

Indeed. Work is already planned for collections, but having any page support would be great.

from jekyll-postfiles.

@mohkale I didn't make any progress yet unfortunately, so that's great that you're willing to implement it, thanks! 👍

from jekyll-postfiles.

No problem, you're the lead on this! 🙂

from jekyll-postfiles.

Finally got round to implementing collections support. Now all that's left should be normal pages... but I'm not really sure how to implement it or even whether there's a need to. Could you give me a use case of where unique grouping of assets for regular pages make sense?

from jekyll-postfiles.

@mohkale I've seen people, including me, group pages in a _pages folder and include it in their config, to get a cleaner root. But it looks like a special collection, looks like that kind of structure could be done now with #47 ?

_config.yml
_pages/
   about/
   index.md
   team.jpg
   404/
   index.md
   error.jpg
_posts/
_collections/
Gemfile
...

from jekyll-postfiles.

@DirtyF so _pages is a collection? I'm not sure whether it'll work with #47 because a postfile has to be at least one directory below the collection directory Sorry. the indentation with about/ and 404/ was off and that confused me. Yeah, that seems like a good solution.

from jekyll-postfiles.

@DirtyF though I've found a bug with #47 in that regard. It seems to me like it's outputting both the converted .html format files and the original unconverted markdown files. I'm not sure why. I'll look into it.

oh, I see, it's recognising the .md files as jekyll-postfiles... I'm curious why this isn't an issue with posts it isn't an issue with posts because posts match the file date format... I can see how to fix this.

Update: Okay, that should've fixed it.

from jekyll-postfiles.

@DirtyF I've got one issue with _pages. Is it already defined as a collection? I can't seem to add it to my collections hash in _config.yml and I also can't change the permalink for members of it.

Adding

defaults:
  - scope:
      type: pages
    values:
      permalink: /:title:output_ext

gets me: jekyll 3.8.6 | Error: Invalid argument @ rb_sysopen - mohkale.io/bin/:title.html. I truncated the path for simplicities purposes, but bin is my build directory for jekyll.

from jekyll-postfiles.

It's not a collection, just an included folder.

from jekyll-postfiles.

Just ran into a use case where this'd be convenient so it's probably worth considering how to implement it. We could just ask users to manually create a collection, _pages in this case and then use that with #47 ... but I'm not a big a fan of the whole _collection naming scheme & that'd force paths for files in the root of your site into at least one subdirectory below the root of your source directory, so I'd appreciate an alternative.

We could add a config option where users can specify paths and each matching path is considered the root for a postfiles directory. I.E.

site:

- about-me/
  - banner.png
  - index.md
- faq/
  - styles/
    - main.css
  - index.md
- _config.yml

_config.yml:

postfiles:
  include:
    - {about-me,faq}/

neither approach seems very intuitive.

from jekyll-postfiles.