Hi @kobra,
The Vanilla components are still on the roadmap, but their priority is low since I don’t need them for any of the current projects I’m working on, and there are other, more urgent tasks. However, it’s definitely something I want to tackle in the future.
EDIT:
I’d like to provide a bit more context about the current situation and how mGear development tasks are prioritized.
We have a general roadmap, but priorities shift based on the needs of current projects and clients. Changes and improvements for clients always take the highest priority, and most of these updates are shared in the public repository for the community (with some exceptions for custom development).
In addition, I work on new features and improvements when I have time, aiming to move forward with new tools and improve existing ones. Community contributions come next; however, I have no control over what the community decides to share. At this point, there aren’t any volunteers contributing on a regular basis (Except for @chrislesage that is the community manager 
) or asking for specific tasks to work on.
Regarding the Vanilla components, I’ve been asked about them a few times. However, this task is a large one, and I need to prioritize projects that pay the bills while continuing to develop other areas to future-proof mGear. As a result, I’ve been postponing it until I either have the time or a client sponsors the development. 
I hope this provides some clarity and transparency about mGear’s development. 
EDIT 2:
When I refer to “we,” I mean @SimonA and myself.
Simon is working with me at www.mcsgear.com and he is the lead engineer for ueGear, while I’m mainly in charge of mGear development and the design of ueGear.
) or asking for specific tasks to work on.
