Transition from Svelte to Sveltekit

[KnightChaser]

Since KCX was designed as a multi-page web application, using Sveltekit rather than Svelte is highly encouraged. However, when I was making this website while learning Svelte and other modern web frameworks for the first time, I just used Svelte and developed like no one could stop me while not knowing which consequences would emerge for me.

It's time to pay off.

• Separate frontend and backend stuff in a separate folder (completed)
• Move the frontend framework Svelte to Sveltekit
• Remove svelte-spa-router stuff, readjust the route (To use Sveltekit routing)
• Inspect and modify all utility Svelte/JavaScript files while removing legacy and inefficient components
• Move the styling components from Flowbite to Svelte-Flowbite

Additional thing

• Email verification when signing in
• Captcha(automatic or invisible)
• User management page(change password, email, profile pictures, etc...)

[KnightChaser]

While transitioning to Sveltekit, the website service design will be refurbished while using Svletekit. Note that countup.js and its extension plugin odometer_countup, which provides some fancy number counting animation seem to be unavailable in Sveltekit, so removed. (Further, I'm willing to add it after stabilization, even if I have to use alternative.)

[KnightChaser]

It looks like AWS Lightsail is excessively expensive. I'd rather use cheaper VPC services providing almost the same server usage experiences such as Hetzner Cloud, which is based in Germany. Moving the website hosting company is also my consideration and I expect this will be done at the final step after service development stabilization.

[KnightChaser]

I hope there will be some floating popovers such as Twitter when the user hovers a row in the leaderboard... for fancy purposes. Such as

• User profile picture
• Username
• User status (customizable quote) - Be aware that user DB table schema should be expanded
• The fund gap between +1 / -1 ranked user