13322e11cb
Replace the Svelte runtime, Vite plugin, Storybook adapter, and component files with Vue 3 equivalents while preserving the existing route table, page markup, styling, assets, deployment shape, and npm workflows. Move shared and page-level state onto Vue refs, computed values, lifecycle hooks, and script setup components. Recreate the custom async router and translation composable as Vue-native modules so navigation and bilingual content continue to work without introducing a router or state-management dependency. Adopt the maintained @lucide/vue package, remove the Svelte icon and map wrappers, and initialize MapLibre directly on the Helpdesk page. Replace the Svelte CSF story with a Vue Storybook story, remove obsolete aliases and generation/config files, and update the audited lockfile with no known vulnerabilities.
Lapikud External Website
Welcome! This is the public-facing website for Lapikud. It's a learning project. If something breaks, that's totally fine. You just get to learn more about git.
Materials and design files are on Google Drive → Lapikud → Tarkvara → Väliveeb
🙋 How to help
You don't need to write code to contribute!
Option 1 — Report something
Found a bug, typo, or something missing? Open an issue and describe what's wrong. That's already super helpful.
Option 2 — Fix something yourself
- Fork this repo (button in the top right on GitHub — it copies the project to your account)
- Make your changes
- Open a pull request back to this repo
🛠️ Setting up your dev environment
What you need first
- Node.js — v18 or higher, but grab the LTS version (currently v24) to be safe
Node.js comes with
npmincluded, so you don't need to install that separately.
Don't have a code editor yet?
If you don't have a preferred code editor, VSCode is a solid choice. Download and install it, and you're good to go.
Windows? Set up WSL first (recommended)
WSL lets you run Linux commands on Windows, which makes everything smoother.
📋 WSL setup steps
Step 1 — Enable WSL. Run these two commands in PowerShell as Administrator (this enables the necessary Windows features):
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
Step 2 — Set WSL to version 2 (the better one):
wsl --set-default-version 2
Step 3 — Install Ubuntu from the Microsoft Store
⚠️ If WSL doesn't work, check that Virtualization is enabled on your machine: open Task Manager → Performance tab → look for "Virtualization: Enabled"
Installation
1. Clone the repo — this downloads the project to your computer:
git clone https://github.com/Lapikud/lapikud.github.io.git
cd lapikud.github.io
2. Install dependencies — this installs all the packages the project needs:
npm install
3. Optimise images — the optimised image variants are not stored in the repo, so you need to generate them locally before running the site:
npm run optimise
You only need to run this once after cloning, and again whenever you add or change images in any
original/folder.
4. Start the dev server — this runs the site locally so you can see your changes live:
npm run dev
Then open the URL it gives you (usually http://localhost:5173) in your browser. 🎉
🖼️ Adding images
Place your original image files (PNG, JPG, etc.) into the appropriate public/assets/{category}/original/ folder, then run:
npm run optimise
The script will generate optimised WebP and JPG variants automatically. Do not commit anything inside optimised/ folders — those are generated and ignored by git.
SVGs don't need optimising — just place them directly where they're needed, no
original/folder required.
🚀 Deployment
Nothing to do here — GitHub automatically builds and deploys the site whenever something is pushed to the v2 branch. The optimised images are generated as part of the build, so you don't need to worry about that either.
It usually takes 2–5 minutes. You can watch it happen in the Actions tab.