librasn / librasn.github.io Goto Github PK

Right now the generated WASM is included in the repository. I think we should eventually change that to being built at build/compile time so that we don't have to manually compile it each time we make a new version.

I think we should refactor the index.html from being a bespoke static page, into using a framework.

Why use a framework for such a small website? Well there's a few reasons.

• Expanding the scope
  I think it would be a good idea to expand the scope of this from just being the compiler, to having the compiler as the landing page, and then having documentation included. Plus there may be features we want to add that might be complicated to maintain.
• Easier for a broader audience to contribute.
  As we build the site and the compiler and show it to a broader audience, we're likely to attract more contributors, having something more people are used to, will make it easier to contribute to.

If I can also propose a solution, I think it should be SvelteKit, because it provides a lot features, has a good developer experience, and natively has static generation.