dragos-efy
commented
11 months ago I 100% agree and thanks for the feedback, ideas & links! My plan is in theory this (the steps are not in order necessarily):
- Make efy stable, fast, efficient and reliable (everything improved in efy will have improvements in apps that use it as well)
- Create good documentation for devs & users (I have a decent base on the site rn, but it needs to become more dynamic and reusable by other projects, like you said, and I need to add a lot more info, cuz now it's kinda empty)
- Create a public marketplace where users can upload & download their own themes or share them on a repo as well (this step will be HUGE imo, and the themes should work on all apps using efy)
- Create components that devs can reuse (like a calendar, timer, tabs, color picker, image gallery, video player etc)
- Make a visual builder that creates static apps & websites and reuses efy components (kinda like wordpress or grapes js, but fully static, offline, without the requirement of a backend or database (other than indexedDB)
So I basically want to make it easier for users to use efy, even if they don't want to customize things and just download a theme someone else made for example, and easier for devs to build things with efy, either by coding or mostly visually with a builder & components.
The biggest problem in all of this is time... or getting more help from other people with some tasks. Cuz I need money to survive, which means I have to waste time working on other stuff, which gives me a small window of time and energy left for efy currently, BUT even if slower, I'll still make all of this a reality, in fact the next update is coming soon and it will bring more efficiency, a bit of extra keyboard accessibility and a few more steps towards better color customization.
If you have other ideas about what we can do practically, for the site / app builder or how efy can be integrated with the ones you mentioned, let me know here or on matrix
codenyte
It would be really cool if there was a way to use EFY with static site generators like Hugo, Doks, Jekyll or documentation generators like Docusaurus and MkDocs. I know that an injector feature is coming, but dedicated integrated for the aforementioned frameworks would be nice to see. For example, Piped is currently migrating to EFY for the UI in their client. If this feature was implemented, they could also use the same coherent design system for all of their other stuff, like the documentation page.