[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technology-en-vite":3,"technology-projects-en-vite":28,"mdc-9mu2yw-key":75},{"id":4,"title":5,"category":6,"content":7,"description":8,"extension":9,"faq":10,"icon":11,"links":12,"meta":21,"projects":22,"since":24,"stem":25,"updated":26,"__hash__":27},"technologies_en\u002Fen\u002Ftechnologies\u002Fvite.yml","Vite","frontend","Vite is a frontend development and build tool. I use it through Nuxt in VetCard and this portfolio, and with Laravel's frontend integration in DigiSpace.\n\n## During development\n\nThe development server updates supported modules through hot module replacement, so many edits can be reviewed without a full page reload. The actual feedback time depends on the project, plugins and machine; it is not an unconditional promise of instant updates.\n\n## For production\n\nThe build prepares frontend assets for deployment, including hashed filenames and code splitting where configured. Nuxt and Laravel supply their own integration around that output. The production bundler depends on the Vite version, so I check the installed toolchain when changing build configuration.\n\n## What I verify after a build\n\nA successful build does not prove that every route works. Asset URLs, environment variables, server rendering and browser behavior need checks in the target setup. I treat Vite as one part of the application's delivery process, with browser tests and runtime checks covering behavior beyond compilation.\n","Vite for Vue, Nuxt and Laravel frontends: development feedback, production assets and integration with application build workflows.","yml",null,"i-simple-icons-vite",[13,18],{"label":14,"to":15,"color":16,"icon":17},"vite.dev","https:\u002F\u002Fvite.dev","neutral","i-heroicons-arrow-top-right-on-square",{"label":19,"to":20,"color":16,"icon":17},"Technical reference","https:\u002F\u002Fvite.dev\u002Fguide\u002F",{},[23],"digispace","2021","en\u002Ftechnologies\u002Fvite","2026-09-20","pNzaecLvTAFL6UjS3RELeoyF06WN2W2qg9Hq648bYKc",[29],{"id":30,"title":31,"content":32,"date":33,"description":34,"extension":9,"featured":35,"image":36,"links":37,"meta":46,"stack":47,"stem":70,"tags":71,"url":40,"__hash__":74},"projects_en\u002Fen\u002Fprojects\u002Fdigispace.yml","DigiSpace","The production website behind digispace.pro — the agency's public site, admin panel and custom CMS in a single Laravel app, now fully multilingual (EN\u002FUK\u002FPL) with a Filament admin panel running alongside the legacy Inertia + Vue one. The same code that runs the live site is available on GitHub.\n\n## Key Features\n\n- **Filament admin panel** - a parallel `\u002Fcontrol` panel (24 resources) with a TipTap rich editor, straight-to-MinIO image uploads and content-first navigation, rolled out resource-by-resource next to the existing Inertia admin\n- **Multilingual by design** - both content and structural UI strings (menus, footer, buttons) are translated per locale, not just page text, with hreflang-aware localized routing\n- **SEO built in** - JSON-LD structured data, localized sitemaps and proper 404 handling across every locale\n- **Monolith done right** - public site and two admin surfaces live in one Laravel app, no separate API to maintain\n- **Self-managed content** - pages, services and portfolio entries are edited in the CMS — no deploy needed for a text or translation change\n- **Quality gates** - PHPUnit tests and PHPStan static analysis run in CI\n- **Source available** - the exact code serving digispace.pro is public on GitHub\n\n## Tech Stack\n\n- **Backend**: Laravel\n- **Admin**: Filament 5 (`\u002Fcontrol`) + legacy Inertia.js + Vue admin\n- **Frontend**: Vue.js, Vite\n- **Localization**: EN\u002FUK\u002FPL content and structure translations\n- **Architecture**: Custom CMS\n","2022-10-05","The agency's multilingual (EN\u002FUK\u002FPL) production site with a custom CMS — a Filament admin panel with a rich content editor, content translations, JSON-LD and localized sitemaps built in, alongside the legacy Inertia + Vue admin",true,"\u002Fhero\u002Fdigispace.avif",[38,42],{"label":39,"to":40,"color":41,"icon":17},"Live Demo","https:\u002F\u002Fdigispace.pro","primary",{"label":43,"to":44,"color":16,"icon":45},"GitHub","https:\u002F\u002Fgithub.com\u002FYurij2015\u002FDigiSpace","i-simple-icons-github",{},[48,51,54,57,58,61,64,67],{"name":49,"icon":50},"Laravel","i-simple-icons-laravel",{"name":52,"icon":53},"Inertia","i-simple-icons-inertia",{"name":55,"icon":56},"Vue","i-simple-icons-vuedotjs",{"name":5,"icon":11},{"name":59,"icon":60},"MySQL","i-simple-icons-mysql",{"name":62,"icon":63},"Tailwind CSS","i-simple-icons-tailwindcss",{"name":65,"icon":66},"Filament","i-simple-icons-filament",{"name":68,"icon":69},"CMS","i-heroicons-document-text","en\u002Fprojects\u002Fdigispace",[49,65,52,55,72,73],"i18n","SEO","dtWB-9st6fApdLs4qomkqmMQVq9PBqeHoPzR0Ywgu0I",{"data":76,"body":77},{},{"type":78,"children":79},"root",[80,88,95,100,106,111,117],{"type":81,"tag":82,"props":83,"children":84},"element","p",{},[85],{"type":86,"value":87},"text","Vite is a frontend development and build tool. I use it through Nuxt in VetCard and this portfolio, and with Laravel's frontend integration in DigiSpace.",{"type":81,"tag":89,"props":90,"children":92},"h2",{"id":91},"during-development",[93],{"type":86,"value":94},"During development",{"type":81,"tag":82,"props":96,"children":97},{},[98],{"type":86,"value":99},"The development server updates supported modules through hot module replacement, so many edits can be reviewed without a full page reload. The actual feedback time depends on the project, plugins and machine; it is not an unconditional promise of instant updates.",{"type":81,"tag":89,"props":101,"children":103},{"id":102},"for-production",[104],{"type":86,"value":105},"For production",{"type":81,"tag":82,"props":107,"children":108},{},[109],{"type":86,"value":110},"The build prepares frontend assets for deployment, including hashed filenames and code splitting where configured. Nuxt and Laravel supply their own integration around that output. The production bundler depends on the Vite version, so I check the installed toolchain when changing build configuration.",{"type":81,"tag":89,"props":112,"children":114},{"id":113},"what-i-verify-after-a-build",[115],{"type":86,"value":116},"What I verify after a build",{"type":81,"tag":82,"props":118,"children":119},{},[120],{"type":86,"value":121},"A successful build does not prove that every route works. Asset URLs, environment variables, server rendering and browser behavior need checks in the target setup. I treat Vite as one part of the application's delivery process, with browser tests and runtime checks covering behavior beyond compilation."]