Hi Gio. Setting aside for a moment Markdeep's perplexing .md.html file extension choice… In Pelican's nearly decade-long existence, I'm not aware of anyone voicing a need for compound file extensions. In other words, this is an edge case that Pelican maintainers most likely cannot allocate time to implement. Is this a feature you would like to work on?

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.

This should not be closed. It is an open enhancement that can be done. I'd be happy to do it myself if I get the time.

Regardless, unless the decision has been actively made that this shouldn't be added, this shouldn't be closed.

I understand your perspective. From a maintainer point-of-view, leaving issues open indefinitely when nobody has expressed an interest in working on them leads to a repository full of ancient, dusty, and forgotten issues. Those accumulated dead issues eventually impose a significant maintenance burden on maintainers, and that's why the stale bot was put into service.

I understand that you would like to see Pelican support compound file extensions, and if you would like to work on implementing that functionality (including documentation, tests, etc.), we would be happy to receive and review your contribution to that end. 💫

I'm looking to make a contribution, but I'm still getting familiar with Pelican. I'd be happy to work on this issue once I'm more up to speed. Would you still accept a pull request for this issue? Assuming it includes documentation, tests, etc.

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.