We Decided to Build It Ourselves
Many early-stage startups outsource their website, but as a tech company, Dartwork chose to build it in-house. After all, it’s our first portfolio piece showcasing our engineering capabilities.
Choosing the Tech Stack
After evaluating several frameworks, we settled on the following stack:
- SvelteKit — A full-stack framework built on Svelte 5. Compile-time optimizations keep the bundle small and the developer experience excellent.
- Tailwind CSS v4 — Utility-first CSS. The CSS-first configuration in v4 makes the setup more intuitive than ever.
- Paraglide v2 — A compile-time i18n library. Automatic tree-shaking ensures unused translations never make it into the bundle.
- mdsvex — A preprocessor that lets you use Svelte components inside Markdown. We use it to manage blog posts, news, and IR content.
Internationalization
We support two languages: English and Korean. The locale lives in the URL — English is the default at /, and Korean sits under /kr/.... Paraglide v2 needs no wrapper component: its server middleware (paraglideMiddleware in hooks.server.ts) reads the locale from each request’s URL, and a reroute hook (hooks.ts) strips the /kr prefix so both languages share the same SvelteKit routes. Links pass through localizeHref, so switching languages simply moves you to the same page’s other URL.
Content files are organized into src/content/ko/ and src/content/en/ directories for clean separation.
Content System
Using mdsvex, we manage blog posts, news, and IR materials as Markdown files. Each piece of content lives in its own folder (index.svx + related assets), allowing us to co-locate images and other assets alongside the content.
Wrapping Up
There’s still plenty of room for improvement, and we plan to iterate continuously. We’ll share our technical challenges and learnings through this blog.