SPA?

[peterpeterparker]

Motivation

Is there a particular reason why this website / repo is a SPA? I thought about it but I cannot really find a technical or product reason that requires it, am I missing something? If not, I would suggest pre-rendering the site and the documentation it exposes.

For a similar reason, and again unless I'm missing something, I would also suggest hosting it on the IC since I'm already there.

[JoshDFN]

Great suggestion — you're right, there's no reason this needs to be an SPA. The site was stood up quickly from a previous project template so it shipped as one, but pre-rendering is the right call for static content like this.

Open to a PR if you'd like to take ownership of it, otherwise we'll get to it as we continue improving the site.

[JoshDFN]

How about this setup:

1. Next.js with static export — pre-renders each skill page to HTML at build time, file-based routing, built-in SEO/sitemap support
2. IC hosting — deploy the static output to an asset canister instead of GitHub Pages

Not sure on the best setup here — defer to you on what you think would work best or if you have any other suggestions.

[peterpeterparker]

How about this setup:

1. The setup is often to some extent a matter of taste. For this use case, I would personally say Astro would likely be a good fit. If navigation is needed, more documentation-style website, maybe even something like Starlight or VitePress? But ultimately, if the value is there, whatever the tool.

Every route gets pre-rendered as HTML but, the markdown files should likely also be made available statically alongside it.

I mean something like what I do on Juno:

• HTML: https://juno.build/docs/build/authentication/google aka https://juno.build/docs/build/authentication/google/index.html
• MD: https://juno.build/docs/build/authentication/google.md

I don't have proper statistics to prove that makes sense, but if feels it has become a common best practice to do so

2. Coolio 👍