You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Via #13 and after getting more library data added by the community, we can build a simple single-page website to show and search the libraries.
I'd love to use Svelte to do this, since it's very user friendly as far as front-end frameworks go. But we could also do raw JavaScript to reduce build tooling and make it more accessible for community contribution.
We could easily host on GitHub Pages, so that everything stays in the repo.
Any thoughts on the matter?
The text was updated successfully, but these errors were encountered:
It'd be good to have some guidance from YoYo as they have announced that they're looking into npm for package management for extensions/plugin releases. Wouldn't want to build anything that'll just become obsolete.
It'd be good to have some guidance from YoYo as they have announced that they're looking into npm for package management for extensions/plugin releases. Wouldn't want to build anything that'll just become obsolete.
If we're lucky the Yoyo solution will be so good that we don't even need this resource anymore 😜
But more seriously, I think that the problem domains are different enough that this thing will still have some utility, and/or could be expanded to make use of whatever Yoyo ends up doing.
Oh yeah, having our own curation for libraries/extensions/code snippets is still incredibly useful & good to have even if YoYo somehow manages to get it right.
I'm unfamiliar with Svelt, so I can't make a good comment on that.
But I will say that having a way to index and search for any of the libraries would be very handy.
Via #13 and after getting more library data added by the community, we can build a simple single-page website to show and search the libraries.
I'd love to use Svelte to do this, since it's very user friendly as far as front-end frameworks go. But we could also do raw JavaScript to reduce build tooling and make it more accessible for community contribution.
We could easily host on GitHub Pages, so that everything stays in the repo.
Any thoughts on the matter?
The text was updated successfully, but these errors were encountered: