Laravel Pagebuilder Multi-Template Integration
Budget: $10 – $30 USD
I am running the Qixer multi-vendor service marketplace on Laravel (see: https://codecanyon.net/item/qixer-multivendor-on-demand-service-marketplace-and-service-finder/36475708). Alongside the default look, I have purchased two complete design packs that I want to turn into selectable themes inside the script’s built-in page-builder:
• Service Finder WordPress theme – 11 individual templates
• Service Finder HTML template – 2 individual templates
Both packs need to be treated with equal priority. Every standalone layout, block, or widget shipped in those packs should appear inside the Laravel page-builder as its own draggable “addon,” ready for use across any page. When I’m in the admin panel I want to:
1. Switch the active site theme between any of the 13 templates without touching code.
2. Mix-and-match their blocks inside the drag-and-drop builder exactly as I do with the native Qixer elements.
3. See all styling, scripts, and responsive behaviour load correctly, with no conflicts or broken views.
Please bring across any demo data, JS/CSS dependencies, or Blade partials required so the templates render perfectly. Keep the integration clean and update-safe, ideally by encapsulating themes and addons in their own folders or service providers.
Delivery is time-sensitive, so let me know how quickly you can have a first test environment ready and what information you need from my side (server, repo access, etc.).
• Service Finder WordPress theme – 11 individual templates
• Service Finder HTML template – 2 individual templates
Both packs need to be treated with equal priority. Every standalone layout, block, or widget shipped in those packs should appear inside the Laravel page-builder as its own draggable “addon,” ready for use across any page. When I’m in the admin panel I want to:
1. Switch the active site theme between any of the 13 templates without touching code.
2. Mix-and-match their blocks inside the drag-and-drop builder exactly as I do with the native Qixer elements.
3. See all styling, scripts, and responsive behaviour load correctly, with no conflicts or broken views.
Please bring across any demo data, JS/CSS dependencies, or Blade partials required so the templates render perfectly. Keep the integration clean and update-safe, ideally by encapsulating themes and addons in their own folders or service providers.
Delivery is time-sensitive, so let me know how quickly you can have a first test environment ready and what information you need from my side (server, repo access, etc.).