[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"technology-en-mysql":3,"technology-projects-en-mysql":29,"mdc--pgoe3p-key":99},{"id":4,"title":5,"category":6,"content":7,"description":8,"extension":9,"faq":10,"icon":11,"links":12,"meta":21,"projects":22,"since":25,"stem":26,"updated":27,"__hash__":28},"technologies_en\u002Fen\u002Ftechnologies\u002Fmysql.yml","MySQL","database","MySQL is a relational database that I use with Laravel applications and WordPress websites. In DigiSpace, it stores the content behind the company website and CMS; DigiSpace Studio also uses it as part of its WordPress stack.\n\n## What database work involves\n\n- **Schema design** — model pages, menus and related records with appropriate keys and constraints.\n- **Query analysis** — inspect slow queries and execution plans before changing indexes or adding resources.\n- **Migrations** — plan schema changes with existing data and deployment order in mind.\n\n## MySQL and WordPress\n\nMySQL is a common WordPress database choice, but it is not the only supported engine: WordPress also supports MariaDB. Hosting compatibility, existing data and operational experience all influence the choice. Changing database engines needs testing rather than an assumption of identical behavior.\n\n## MySQL or PostgreSQL?\n\nI work with both. An established MySQL application may have no reason to migrate, while another project may benefit from PostgreSQL's data types or indexing options. For either engine, sound queries, backups and tested recovery matter more than a general claim that one database is always faster.\n","MySQL for Laravel and WordPress: database design, query optimization and content storage in DigiSpace and DigiSpace Studio.","yml",null,"i-simple-icons-mysql",[13,18],{"label":14,"to":15,"color":16,"icon":17},"mysql.com","https:\u002F\u002Fwww.mysql.com","neutral","i-heroicons-arrow-top-right-on-square",{"label":19,"to":20,"color":16,"icon":17},"Technical reference","https:\u002F\u002Fwordpress.org\u002Fabout\u002Frequirements\u002F",{},[23,24],"digispace","digispace-studio","2017","en\u002Ftechnologies\u002Fmysql","2026-09-20","ygAvsAwqaxylqZvTTJhhvH6PTMgNKgv5sVsAZIU1puQ",[30,76],{"id":31,"title":32,"content":33,"date":34,"description":35,"extension":9,"featured":36,"image":37,"links":38,"meta":47,"stack":48,"stem":71,"tags":72,"url":41,"__hash__":75},"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",[39,43],{"label":40,"to":41,"color":42,"icon":17},"Live Demo","https:\u002F\u002Fdigispace.pro","primary",{"label":44,"to":45,"color":16,"icon":46},"GitHub","https:\u002F\u002Fgithub.com\u002FYurij2015\u002FDigiSpace","i-simple-icons-github",{},[49,52,55,58,61,62,65,68],{"name":50,"icon":51},"Laravel","i-simple-icons-laravel",{"name":53,"icon":54},"Inertia","i-simple-icons-inertia",{"name":56,"icon":57},"Vue","i-simple-icons-vuedotjs",{"name":59,"icon":60},"Vite","i-simple-icons-vite",{"name":5,"icon":11},{"name":63,"icon":64},"Tailwind CSS","i-simple-icons-tailwindcss",{"name":66,"icon":67},"Filament","i-simple-icons-filament",{"name":69,"icon":70},"CMS","i-heroicons-document-text","en\u002Fprojects\u002Fdigispace",[50,66,53,56,73,74],"i18n","SEO","dtWB-9st6fApdLs4qomkqmMQVq9PBqeHoPzR0Ywgu0I",{"id":77,"title":78,"content":79,"date":80,"description":81,"extension":9,"featured":36,"image":82,"links":83,"meta":86,"stack":87,"stem":95,"tags":96,"url":85,"__hash__":98},"projects_en\u002Fen\u002Fprojects\u002Fdigispace-studio.yml","DigiSpace Studio","Marketing site for DigiSpace Studio — a specialized web studio for veterinary clinics and pet brands. Built on WordPress with the Blocksy theme and Stackable\u002FGutenberg blocks, a child theme for customization, a blog, and lead capture through contact forms.\n\n## Key Features\n\n- **Niche positioning** — the site speaks directly to vet clinics and pet brands, not a generic agency pitch\n- **Block-based editing** — Stackable and Ultimate Gutenberg blocks let non-developers build new landing pages without touching code\n- **Child theme** — customizations live in a Blocksy child theme, so theme updates never wipe the design\n- **Blog + lead capture** — content marketing for SEO with Contact Form 7 for inquiries\n","2024-06-27","Marketing site for a niche IT studio for veterinary clinics and pet brands — WordPress with Blocksy theme and Gutenberg blocks","\u002Fhero\u002Fdigispace-studio.avif",[84],{"label":40,"to":85,"color":42,"icon":17},"https:\u002F\u002Fdigispace.studio",{},[88,91,94],{"name":89,"icon":90},"WordPress","i-simple-icons-wordpress",{"name":92,"icon":93},"PHP","i-simple-icons-php",{"name":5,"icon":11},"en\u002Fprojects\u002Fdigispace-studio",[89,97,74],"Marketing","lUBO_S2U81n4IZSar2nv_fcR4Tt9yqbTz0I0wnYI1_c",{"data":100,"body":101},{},{"type":102,"children":103},"root",[104,112,119,155,161,166,172],{"type":105,"tag":106,"props":107,"children":108},"element","p",{},[109],{"type":110,"value":111},"text","MySQL is a relational database that I use with Laravel applications and WordPress websites. In DigiSpace, it stores the content behind the company website and CMS; DigiSpace Studio also uses it as part of its WordPress stack.",{"type":105,"tag":113,"props":114,"children":116},"h2",{"id":115},"what-database-work-involves",[117],{"type":110,"value":118},"What database work involves",{"type":105,"tag":120,"props":121,"children":122},"ul",{},[123,135,145],{"type":105,"tag":124,"props":125,"children":126},"li",{},[127,133],{"type":105,"tag":128,"props":129,"children":130},"strong",{},[131],{"type":110,"value":132},"Schema design",{"type":110,"value":134}," — model pages, menus and related records with appropriate keys and constraints.",{"type":105,"tag":124,"props":136,"children":137},{},[138,143],{"type":105,"tag":128,"props":139,"children":140},{},[141],{"type":110,"value":142},"Query analysis",{"type":110,"value":144}," — inspect slow queries and execution plans before changing indexes or adding resources.",{"type":105,"tag":124,"props":146,"children":147},{},[148,153],{"type":105,"tag":128,"props":149,"children":150},{},[151],{"type":110,"value":152},"Migrations",{"type":110,"value":154}," — plan schema changes with existing data and deployment order in mind.",{"type":105,"tag":113,"props":156,"children":158},{"id":157},"mysql-and-wordpress",[159],{"type":110,"value":160},"MySQL and WordPress",{"type":105,"tag":106,"props":162,"children":163},{},[164],{"type":110,"value":165},"MySQL is a common WordPress database choice, but it is not the only supported engine: WordPress also supports MariaDB. Hosting compatibility, existing data and operational experience all influence the choice. Changing database engines needs testing rather than an assumption of identical behavior.",{"type":105,"tag":113,"props":167,"children":169},{"id":168},"mysql-or-postgresql",[170],{"type":110,"value":171},"MySQL or PostgreSQL?",{"type":105,"tag":106,"props":173,"children":174},{},[175],{"type":110,"value":176},"I work with both. An established MySQL application may have no reason to migrate, while another project may benefit from PostgreSQL's data types or indexing options. For either engine, sound queries, backups and tested recovery matter more than a general claim that one database is always faster."]