Published At: 2026-04-20
Obsidian is a note-taking application suitable for creating a knowledge base for web application developers. Obsidian, especially when using many plugins, creates a very effective environment for writing, collecting, and searching for notes. If we want to publish these notes on a web blog, we need to solve the bridging between Obsidian and Laravel. One of the forms is to create a suitable export from Obsidian and solve the import into the resulting form when creating posts in...
Published At: 2026-04-08
Laravel already gives for web project several command surfaces: Artisan, Composer scripts, npm scripts, and even a small admin-facing interface for a restricted set of Artisan commands. So the obvious question is why this repository still keeps a top-level Makefile.
During development, many other commands are still needed, either as commands from the terminal or in the form of bash (zsh) scripts. The sum of all such commands and their structure brings...
Published At: 2026-03-23
Instead of fighting Vite's module bundler, the solution uses a hybrid approach: TinyMCE is loaded as a traditional global script, while only the configuration runs through Vite.
Download TinyMCE 8 Community (GPL) from the official download page and place the full distribution...
Published At: 2026-03-23
When migrating a Laravel blog application from Laravel 8 to Laravel 11, one of the most challenging frontend tasks is upgrading TinyMCE — the rich text editor used in the admin panel. This isn't a simple version bump. You're dealing with two simultaneous breaking changes:
Published At: 2026-03-04 Updated At: 2026-03-07
Part of Real-World CoreUI Migration: From Laravel 8 to Laravel 11
Laravel 11 dropped official Laravel Mix support. While Mix still works, the framework's asset tooling, documentation, and @vite() Blade directive assume Vite. The migration brings:
Published At: 2026-03-04 Updated At: 2026-03-07
Part of Real-World CoreUI Migration: From Laravel 8 to Laravel 11
Since this project kept c- prefixed layout classes from CoreUI, it needed a custom compatibility layer for Bootstrap 4 utility classes that were removed or renamed in Bootstrap 5:
// components/_layout.scss
// Styles for migration Bootstrap 4 to 5
// Bootstrap 4 spacing...
Published At: 2026-03-04 Updated At: 2026-03-07
Part of Real-World CoreUI Migration: From Laravel 8 to Laravel 11
CoreUI 3.4.0 was built on Bootstrap 4; CoreUI 5.1.2 is built on Bootstrap 5. This means two layers of breaking changes hit simultaneously — CoreUI's own API changes and Bootstrap's major version jump.
The SCSS import structure changed fundamentally....
Published At: 2026-03-04 Updated At: 2026-03-07
At the beginning, there was a simple requirement - to upgrade a small web blog from Laravel 8 to Laravel 11. In general, problems with upgrading Laravel versions are well known, but solutions for two areas:
Published At: 2023-06-24 Updated At: 2025-07-24
Often during the development of a Laravel application, there are cases where it is necessary to implement the debugged code on a live server. It takes a long time to transfer all the code (including packages and modules) even at a high transfer rate. The solution is to update only the latest, changed code files.
In the case when the (vendor) packages are unchanged, and we need to update the files of our own application, we can use the incremental file transfer using the git versioning...
Published At: 2023-06-21 Updated At: 2025-07-24
It is recommended to do an initial installation on hosted server without all dev packages and tools. The best approach is to prepare a local docker installation where it is possible to run composer and NPM. For this purpose, we can use an intermediate server for clean code generation in PHP and css/js. The server is also used for final testing of the application before a transfer of cleaned code to the live server.
In order to have the closest possible conditions for running the...