Project status / roadmap?

[vsajip]

Hey, @mixxorz, I'm very grateful to you for this project, and I'm wondering what the roadmap for it is, if there is one. I completely understand if you now have other priorities and can't devote any time to this project; there's a growing number of open issues/feature requests and pull requests which apparently haven't been responded to by you (even to mark as invalid or close as not wanted). It may be that you see the project as complete and not needing any more features, and that's also of course your prerogative; but it would be good for users and potential contributors to get your take on this meta-issue of a roadmap for future changes.

Thanks again for Slippers - very comfy!

[mixxorz]

Hi everyone. Thanks for caring so much about this project. I honestly didn't think that much time has passed since I last worked on this, oh but how time flies.

To let everyone know, I do still personally use this project, and that would at least mean any game-breaking bugs will get resolved.

Features wise, I think I'm OK with the current feature set. I'm very open to adding more config options/new tags/behaviour changes, but I think the current baseline is pretty good.

Documentation can be improved. I don't like the way it's written, and I semi-regret not just using mkdocs for it. 🙃 Not to mention that typeguard and front matter python code is completely undocumented. (This was intentional, because I wasn't sure at the time whether I was happy with how that worked.)

The biggest thing I've been trying (and failing) to add to Slippers is IDE integration for VSCode (since it's popular) and NeoVim (since I use it). Syntax highlighting at the very least.

I'd like to hear everyone's thoughts on what they think should be prioritized.

[Thutmose3]

Thanks for the feedback @mixxorz, i use this repo too much and i am running into issues. The fact that this repo is not being improved and is being stale obliges me to fork this repo.
So i will create slippers2, the idea for this repo will be to pass down the parent context like discussed here:
#45

I have never managed a public lib, so volunteers are welcome to help manage this repo