Blade is one built-in feature of Laravel, known as Laravel Blade. It is known as the template engine of the framework. Due to the massive release of JS frameworks, Laravel works with VueJS and ReactJS. I am familiar with Laravel Blade and a fan of simple monolith architecture. I have a belief. I like decoupling Frontend and Backend completely rather than mixing them all. Why Decoupled CMS than WordPress or Drupal?

In API development, the best response time for API response is less than 150ms, according to Hubspot. That means your API response or the programming language you use for your API should be faster than 150ms. There is one question, will you use Laravel vs Lumen?

Blue-Green Development is an application release model to avoid bugs and seamless migration. Laravel Pennant is one of the features for Laravel applications to test features on specific persons. When Laravel Pennant is released, it acts as A-B testing among developers. This post mainly focuses on how we use Laravel Pennant on Blue-Green Development.

Laravel Folio is the newest package announced in LaraconUS. I am interested in it for two reasons. It already works in NextJS and now arrives in Laravel. We are PHP, and PHP has built-in file routing. In a typical PHP project, we can create index.php, web.php, and profile.php files, which can easily be accessed using the file path. So, why Laravel Folio?

Network Interface renames automatically in some cases. In the worst case, your web server will say 502 "Bad Gateway" or just 504 "Gateway Timeout", which means "Bye, I'm gone".

When I looked for the decoupled Drupal, it does have the documentation of decoupled CMS. REST export also plays well for decoupled Drupal, and I love it. Then I proudly chose decoupled Drupal.