Multiple content paths.

[stuaxo]

I'd like to request a feature for multiple content paths.

The use case, is that I want to separate content I write in markdown, from content exported from my old wordpress site.

I like to re-export the wordpress ocassionally (I have my old site in docker), when I fix issues in WP itself, or the exporter - but I'd like those to live in their own directory.

I realise having PATH optionally take a list of paths might seem strange, but could be best for compatibility.

[stuaxo]

You can imagine a use case using multiple directories to enforce permissions - allow users to edit files in their own directory, and it all gets amalgamated by pelican.

Anyway, if this sounds sane enough, I'm up for having a go.

[avaris]

Why not just amalgamate stuff with symlinks under a folder and use that as PATH?

[stuaxo]

I do have a script to do something like this, but was it would be nice to have support from pelican itself, so I didn't have to remember to run my script.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your participation and understanding.

[stuaxo]

Is it churlish to comment here to keep this open ?

Next time I try update my website on pelican I'm bound to want to still want this

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your participation and understanding.

[justinmayer]

Hi @stuaxo. I assume this is something you're interested in working on and implementing for Pelican at some point, so I'm going to mark this as assigned in order to prevent it from being automatically closed.

[stuaxo]

Ah, thanks - I think I need to make a reminder of all my old tickets.

Yep, this is something intend to look at when I next look at my website. :)