Closed kungfooman closed 1 year ago
That's definitely the right thing to do in the long run. In the beginning I just wanted to keep it as simple as possible for anyone to download the index.html.
There is actually a function for downloading the entire file with one click which would be more complicated to do if you have everything (properly) separated.
My initial plan was to allow everyone with
and without internet connection, to perform local semantic search. The user would simply download the model and enter the path e.g. with filepicker. Note that if you just load index.html with your browser you don't even need a server running, which is quite convenient.
I don't know whether webpack or similar tools might allow a convenient "one-file" html export. If so, I'd propose to continue as follows:
Would make it easier for debugging and development, totally agree!
If the one-file build is not feasible, I'd just keep a one-file version on my homepage but still go the "proper" way.
Also, in the coming week I want to activate CI and GitHub pages, making it easier for development and properly separating the repo from my blog.
I added a PR that does just that.
I could easily add and commit the dist directory, if you'd like me to!
Yes that would be great too!
Can you create separate files called
index.js
andindex.css
?