So what will cover the new setup

• SEO witch is important for better finding the site on google (on the Laravel side)
• Google Analytics – to check visitors and see charts (on the Laravel side)
• Admin panel which is supported out-of-the-box from WP
• Some plugins like
  • WP Fastest Cache – for faster response on WP API
  • WP API SwaggerUI – documentation on the API
  • Under Construction – to disable the web part of the WP
  • MegaOptim Image Optimizer – for optimizing the images added from WP Admin
  • Loginizer – to prevent brute force logins in wp-admin
  • JWT Authentication for WP-API – to prevent (POST, PUT, DELETE) requests
  • Custom Post Type UI – to create new models. WP by default support posts with full CRUD operations by the Admin panel.
  • Advanced Custom Fields – to create new custom attributes for a specific model
  • ACF to REST API – to make Advanced Custom Fields visible in the REST API
• Laravel Cache – At the end, I did some benchmarks. The average load was more than 3.5 sec but with cache, I am getting 274 ms page load. Sounds nice right?
• Feedback and chat integration (on the Laravel side)

I am pretty amazed by what WP can offer. Basically, this is more than enough to make https://nankov.mk look cool and content-rich. But why did I decide to make this kind of setup?
Because I want to explore and find out that there is NO limitation on what I can do with these plugins.
And the power lies in “Custom Post Type UI” where you can create a model and for that model with “Advanced Custom Fields” and custom attributes where you can add them per created model. And the output is like you’re getting a new table with attributes where you can make CRUD operations by the WP Admin panel and with additional plugins you cover the same for REST.

I must say that for my setup populating the data took more time than creating the API. The API was like 2 hours of work. It’s crazy. So, the Laravel app was only an added value to make it all work and an additional setup for comments or taking feedback for the site.

For any awesome staff, there are also pros and cons.
So, from this perspective the cons will be:

• What if these plugins do not cover the new version of WP?
• What if some plugin got deprecated?
• We do not support version control to have some kind of history (git is missing)
• What about if we need to cover the UAT or PROD environment?

If we are looking for an enterprise, this is far away. The clients are ready to pay even more to get the best solution in the market and be ready to make it worth it or our projects are ongoing and we can’t cover WP there.

My opinion is that you can cover small or medium apps and for projects like portfolios, polls, promotions, magazines, small e-commerce, funding/donations, or only manage some content on the site with editable HTML (about us, contact, blog-post, articles). Even some shared content with a mobile app and the web page can be here and It’s totally fine.

Everything depends but it’s on you how you will organize the project or decide to go with an easy-misy setup. I hope that you find something useful and if you have any questions feel free to contact me.

Best,
Andrej

Laravel Compass is an elegant REST assistant for the Laravel framework that you can use to test API calls and create API documentation. it provides automatically endpoints for GET, POST, PUT/PATCH, DELETE, various auth mechanisms, and other utility endpoints based on Laravel routes in your project.

Laravel Compass require PHP 7.2 or higher and Laravel 6.0 or higher. You may use Composer to install Compass into your Laravel project:

composer require davidhsianturi/laravel-compass --dev

Once Composer is done, publish its assets using the compass:install Artisan command. After installing Compass, you should also run the migrate command:

php artisan compass:install

php artisan migrate

That’s it! Next, you should be able to visit the Compass UI at yourproject.test/compass in your browser.

UPDATING COMPASS

When updating Compass, you should re-publish the assets:

php artisan compass:publish

CONFIGURATION

After publishing Compass’s assets, its primary configuration file will be located at config/compass.php below is the default content of the config file:

return [
    /*
    |--------------------------------------------------------------------------
    | Compass Path
    |--------------------------------------------------------------------------
    |
    | This is the URI path where Compass will be accessible from. Feel free
    | to change this path to anything you like.
    |
    */

    'path' => env('COMPASS_PATH', 'compass'),

    /*
    |--------------------------------------------------------------------------
    | Laravel Routes
    |--------------------------------------------------------------------------
    |
    | This is the routes rules that will be filtered for the requests list. use
    | * as a wildcard to match any characters. note that the following array
    | list "exclude" must be referenced by the route name.
    | "base_uri" is a string value as a comparison for grouping the routes.
    |
    */

    'routes' => [
        'domains' => [
            '*',
        ],

        'prefixes' => [
            '*',
        ],

        'exclude' => [
            'compass.*',
            'debugbar.*',
        ],

        'base_uri' => '*',
    ],

    /*
    |--------------------------------------------------------------------------
    | Compass Storage Driver
    |--------------------------------------------------------------------------
    |
    | This configuration options determines the storage driver that will
    | be used to store your API calls and routes. In addition, you may set any
    | custom options as needed by the particular driver you choose.
    |
    */

    'driver' => env('COMPASS_DRIVER', 'database'),

    'storage' => [
        'database' => [
            'connection' => env('DB_CONNECTION', 'mysql'),
        ],
    ],

    /*
    |--------------------------------------------------------------------------
    | Compass Authenticator
    |--------------------------------------------------------------------------
    |
    | This options allow you to get all the "credentials" of users that you can
    | use to perform auth requests through the UI. when "enabled" set to "true"
    | you should adjust the authentication guard driver for your application to
    | support "token" or "sanctum".
    |
    */

    'authenticator' => [
        'enabled' => false,
        'guard' => 'api',
        'identifier' => 'email',
    ],

    /*
    |--------------------------------------------------------------------------
    | Compass Documenter Provider
    |--------------------------------------------------------------------------
    |
    | This configuration option determines the documenter provider that will be
    | used to create a beautiful API documentation. In addition, you may set
    | any custom options as needed by the particular provider you choose.
    |
    */

    'documenter' => 'documentarian',

    'provider' => [
        'documentarian' => [
            'output' => 'public/docs',
            'example_requests' => [
                'bash',
            ],
        ],
    ],
];

MIGRATION CUSTOMIZATION

If you are not going to use Compass’s default migrations, you should call the Compass::ignoreMigrations method in the register method of your AppServiceProvider. You may export the default migrations using the php artisan vendor:publish --tag=compass-migrations command.

AUTHENTICATOR

Compass authenticator using Laravel authentication guard driver to gather all the credentials of users automatically that can be used to perform auth requests through the UI.

Currently, Compass ships with a simple based Token guard driver and Laravel Sanctum guard driver; however, writing custom driver is simple and you are free to extend Compass Authenticator with your own guard implementations.

BUILD/REBUILD DOCUMENTATION

php artisan compass:build
php artisan compass:rebuild

Now, you should be able to visit the results at yourproject.test/docs/index.html in your browser.

Cheers !!!

https://davidhsianturi.com/laravel-compass/documenter/

FlightPHP – easy to use for microservices, small APIs, POC, and extremely easy and fast. A small community with a big impact, a framework that is patter and skeleton agnostic that gives you the power to control the app on your own. FlightPHP gives you only a small set of tools to make your app easy up and running. The whole app can be written in only a single file.

SlimPHP – microframework with awesome documentation that by generated skeleton follows Domain-Driven-Design but also can be customizable. Follows the psr-7 PHP standard and it’s mostly used to build APIs. The framework is easy to scale and supports nice documentation on how to integrate extra packages like ORM, template engine, csrf-protection, flash messages, caching, and many more. By itself contains manual DI container in v.3 and from v.4 you can you external DI container with auto-wiring. Also, documentation supports a nice setup for the deployment of the app. Nice framework for small teams.

Laravel – one of the most popular and tools reach frameworks. Some people say that begins to be the de-facto standard for building web APIs and apps. It’s the most popular among developers and everybody loves it. In the community around the world, developers begin to build packages that are only compatible with Laravel. And why is that? Because it has extremely easy documentation to read, a bunch of tutorials around, and a big community. The framework by itself follows the MVC design pattern and gives you tools to build apps extremely fast. With Laravel, you can develop things so fast that in other frameworks you will do something in days. Laravel gives more focus on business and less on code. Framework with awesome scale, an awesome framework for every PHP developer.

Lumen – In short if you know already Laravel this framework will be piece of cake. It’s driven by the same community and the main purpose is to be used for microservices and APIs. This framework has high compatibility with Laravel stand-alone packages, so most of the tools used in Laravel can be used here.

References:

https://bit.ly/3v4BvoH