Move public assets to public

[jrandolf]

No description provided.

[netlify]

✅ Deploy Preview for parsel ready!

Name	Link
🔨 Latest commit	15eb617
🔍 Latest deploy log	https://app.netlify.com/sites/parsel/deploys/6411eb488799ce0008a065fa
😎 Deploy Preview	https://deploy-preview-62--parsel.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[LeaVerou]

Fine to move CSS and unrelated JS files to a separate folder for tidyness, but moving the entire website to a separate folder means we now need to be building copies of Parsel, one for dist/ and one for the website itself. What is the advantage of this additional complexity?

(I'm less opposed to it as in other projects that don't depend on a build process as much, but I'm still not sure I see the value in it)

[jrandolf]

Hmm, I think the dist folder was removed in one of the PRs by accident. Nonetheless, because of #65, I started compiling a file specifically for the website. Moving all the website code in one place would just make the codebase tidier.

[LeaVerou]

Hmm, I think the dist folder was removed in one of the PRs by accident. Nonetheless, because of #65, I started compiling a file specifically for the website. Moving all the website code in one place would just make the codebase tidier.

It was not removed accidentally, it was removed very intentionally because build artifacts should not be in the repo.
See my comment here: #65 (comment)

[jrandolf]

Closing this in favor of just moving assets.