Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ETK Website #136

Open
gzanitti opened this issue Dec 12, 2023 · 2 comments
Open

ETK Website #136

gzanitti opened this issue Dec 12, 2023 · 2 comments

Comments

@gzanitti
Copy link
Contributor

Hi @SamWilsn and @lightclient .
This is not really an issue but it is the easiest way I found to be in contact with both of you at the same time.
I took the liberty to start a project to have a small ETK web site (including the playground that Sam asked for).

Many links are broken, or point to temporary places (install for example leads directly to github and should be replaced by a real guide) and even the design is quite "simple" (you can notice it in the playground that is just two painted textarea haha), but I thought it's good that you are aware of it and to have a place where we can discuss ideas.

By the way, I also made a logo for ETK :).
The temporary link to the site is this: https://etk-web.vercel.app/

I hope you like it and do not hesitate to ask for all the features you consider necessary.

P.S: If you have more resources (like https://github.com/quilt/vim-etk) or examples that you have written using ETK and can be added to the resources section, feel free to mention them here and I will add them as soon as I I write that section.

@SamWilsn
Copy link
Contributor

This is so cool! Really love it 💕 Does it require and active backend, or can we push it to GitHub Pages? Is ETK compiled to WASM?

@gzanitti
Copy link
Contributor Author

Hi Sam. Yes, ETK is compiled to WASM, but for the moment it is compiled by hand inside the same project and exported, because it points to a branch of ETK that I built where it is possible to pass strings instead of files to the ingester. After fixing that problem and having everything merge in master, I would like to publish it in npm.

Regarding the site, it doesn't use any backend, it's just a bit of HTML, CSS and JS, so I understand that there would be no problem to migrate it to Github Pages (I don't know its particularities because I've never used it, but I doubt there would be any inconvenience).

In the next days I will finish the missing sections.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants