Note: To see the changes, you will be required to compile the assets. For compilation of assets NPM should be installed in your system.

Then go inside each of these packages(path from project's root):

1. packages\Webkul\Admin
2. packages\Webkul\Shop
3. packages\Webkul\Ui

Then you need to run command 'npm install' in each of the directories listed above.

Go to your project root again:

1. Find _variables.scss file by following this path in shop package:
   packages\Webkul\Shop\src\Resources\assets\sass\_variables.scss

In this file _variable.scss you will find all the colors values used in Shop package.

2. Find _variables.scss file by following this path in Ui package: packages\Webkul\Ui\src\Resources\assets\sass\_variables.scss

In this file _variable.scss you will find all the colors values used in Ui package.

But remember the colors in UI package file will affect colors in Admin panel also.

3. Find _variables.scss file by following this path in Admin package:
   packages\Webkul\Admin\src\Resources\assets\sass\_variables.scss

In this file _variable.scss you will find all the colors values used in Admin package.

Note: To compile these assets now, step into all these directories below:

1. packages\Webkul\Admin
2. packages\Webkul\Shop
3. packages\Webkul\Ui

And now run the command 'npm run prod' -> for production and 'npm run watch' -> for development.

Yeah you are absolutely right @cerahil in your site configuration which seems to be an Apache server your project path had to be till public directory not the root directory.

This is how it will work fine.

Hello @cerahil please read this guide we published, after it if you have problem then please ask us here.
We are glad to help you in any case.

https://bagisto.com/en/create-custom-theme-in-bagisto/

Firstly, that was not to be done, there are so many functions in Bagisto dependent on that directory.
You shouldn't delete any directory.

Public directory holds all assets such as js, css and images needed for Bagisto. And definitely nothing will work for you after that believe me.

Your project is on server or you are running locally?

No worries.
You can even take the same pattern for developing the theme for admin as i explained in shop.
Overriding existing views might be the key after you have implemented the above process carefully.

Hey @np glad you asked this.
I suggest you follow our core payment package of (vendor)Paypal, follow the same pattern as its made.
Breaking the process in simple steps:

1. Create a folder for your new payment gateway and use composer init command to initialize composer.json in it.
2. Make your own vendor payment's package by using a service provider.
3. Register the package in config/app.php.
4. Register your package in project's root composer.json file.
5. Follow the same declaration used in service provider file of Paypal in your own service provider also to turn up translations, migrations, views, assets.
   or follow laravel's own guide to create a package Guide
6. create an entry point of class for your own payment method by extending Bagisto's abstract class called Payment. Its present in packages/webkul/payments/payments
7. Define your own routes and controllers and then check the checkout process and use browser console for debugging the checkout process.

Kindly ask any issue, if you find some trouble in making a package.

Hello @murl1dhar Currently we have not implemented any type of event system that would be responsible adding the fields in admin section forms.

Yet, the same thing is not true for storefront i.e customer section. If you check the view files of shop package in Root\Webkul\packages\src\resources\views , you will find this type of syntax, check the screenshot below:

This type of syntax in the picture above can be found in almost all views of the shop package. And it serves the purpose of the question that you've asked for.
To use this functionality you have to just implement the event subscribers for adding any extra functionality that you want like adding fields, static information, any dynamic information, etc.

You have to wait shortly for this type of thing get added for admin views. As this will rollout in new releases.

But soon in later releases we will add the blade event system through which you can add the things that you have asked for.

I am damn sure if you have used Laravel then you know how to create static pages in Laravel.

Making custom pages is piece of cake.

Just follow these steps:

1. Goto your project's root find a folder called routes and there will be a file called web.php inside it.
   
   

2. You have to declare your route in this file.

3. Goto your project's root again and find resources folder and find views folder inside it.

4. Create your views or blade file inside it for content on the custom pages.

5. Use this type of route syntax:
   Route::view('your_route_verb', 'path_to_your_view_file');
   

Obviously, you can use GET route if you wanna pass some dynamic data in your routes.

That is how you gonna create custom pages in Bagisto.

Hello, ismael

I wanted to tell you that mariaDB and MySQL are same and there ain't no difference in DML of both databases.

I am afraid that your database version is older as support for json columns came late in 2016/7.

So please update the version of your database:
Please check out the system requirements also before installing Bagisto on https://github.com/bagisto/bagsito

This will be fixed in the next release.