# Why did you drop partials
**URL:** https://forum.pinegrow.com/t/why-did-you-drop-partials/3878
**Category:** Feature Request
**Tags:** feature-request
**Created:** [March 17, 2020, 2:43pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878 "2020-03-17T14:43:27Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@Tintin](https://forum.pinegrow.com/u/Tintin)
#### Post date: [March 17, 2020, 2:43pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/1 "2020-03-17T14:43:28Z")
This is one of the most important things!!! Why did you drop it?
---
### Author:  [@dcneuts](https://forum.pinegrow.com/u/dcneuts)
#### Post date: [March 17, 2020, 5:11pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/2 "2020-03-17T17:11:59Z")
Which version are you using? I have the WP version and I still see:
- Global Smart Actions -\> Reusable Template Part
- Template Parts -\> Define Template Part
- Template Parts -\> Include Template Part
Also, you can easily create one and manually insert the code.
---
### Author:  [@matjaz](https://forum.pinegrow.com/u/matjaz)
#### Post date: [March 18, 2020, 4:14am UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/3 "2020-03-18T04:14:35Z")
@Tintin can you please tell me more about how you (would) use partials?
I’m thinking about bringing them back but would like to get the features and usability right.
@dcneuts this refers to “Open as Partial” feature [http://docsbeta.pinegrow.com/working-with-partials/](http://docsbeta.pinegrow.com/working-with-partials/)
---
### Author:  [@dcneuts](https://forum.pinegrow.com/u/dcneuts)
#### Post date: [March 18, 2020, 2:45pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/4 "2020-03-18T14:45:39Z")
Thanks for the clarification on this. Partials are a big deal in a PHP and WP environment, so I’m also going to wait for an answer out of curiosity on this one. I’m all for strengthening PHP-based operations.
---
### Author:  [@Tintin](https://forum.pinegrow.com/u/Tintin)
#### Post date: [March 20, 2020, 2:15pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/5 "2020-03-20T14:15:34Z")
I use PG for Laravel projects and I set the PG project folder to Laravels “resources” directory.
I always disable PG’s backups because I use Git versioning.
I create a folder where I have my master design pages
Example:
./Resources/views/pinegrow/front.html
./Resources/views/pinegrow/admin.html
When they are ready I split them into multiple partials
LAYOUTS are where I attach the STYLES and JS.
They only contain the header, and body.
Example
./Resources/views/layouts/front.blade.php
./Resources/views/layouts/admin.blade.php
Another folder will contain partials:
Example:
./Resources/views/partials/front/top-menu.blade.php
./Resources/views/partials/admin/left-menu.blade.php
One folder will contain blade reusable components
Example
./Resources/views/components/forms/input.blade.php
./Resources/views/components/forms/wrapper.blade.php
./Resources/views/components/forms/buttons.blade.php
./Resources/views/components/datatable.blade.php
I can go on, but I think you get the picture.
After the initial design phase, all partials would be opened in a LAYOUT file.
This is the key to be able to use Pinegrow. If I cannot open the partials in a layout file, I have to attach a style sheet to every partial, which I manually have to remember to remove, every time I save it …
(I attach style.css from Laravels css folder and app.css from the public folder and use npm to watch for changes)
At the moment I solved this by having a master template in the “pinegrow” folder that I duplicate when I want to make a new partial, then I define the section I want to use in Laravel as a partial and export it to the correct folder.
**If you don’t want to reimplement the “open as partial…” feature, you could add a new css/js feature to be able to define css and js files as “design time only” so they never are attached in the code. That would cover the basic needs.**
In some cases where you work with more detailed partials, like a menu bar or input field component, I still miss the “open as partial …” feature.
I actually stopped using PineGrow with Laravel when this feature was dropped but started to use it again because PG plays very nice with Laravel 7 new blade component syntax.
[https://laravel.com/docs/7.x/blade#displaying-components](https://laravel.com/docs/7.x/blade#displaying-components)
---
### Author:  [@dcneuts](https://forum.pinegrow.com/u/dcneuts)
#### Post date: [March 24, 2020, 2:30pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/6 "2020-03-24T14:30:37Z")
Wow, you’re really in the weeds, I can see how this is important… never actually thought about using this with the Laravel framework. Makes sense, though. Let’s see if there’s any feedback from Pinegrow on this topic.
---
### Author:  [@billiemead](https://forum.pinegrow.com/u/billiemead)
#### Post date: [April 7, 2020, 8:35pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/7 "2020-04-07T20:35:00Z")
@Tintin Thank you… partials! what an excellent way to integrate Laravel with PG! I have been researching how to create a simple way (plugin?) to parse and ignore Laravel Blade directives, control structures and convert routes and links.
(no relation to DJ Tintin? eh? cheers)
---
### Author:  [@jonroc](https://forum.pinegrow.com/u/jonroc)
#### Post date: [April 8, 2020, 8:40pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/8 "2020-04-08T20:40:57Z")
In function what is the difference between partials and component items?
---
### Author:  [@matjaz](https://forum.pinegrow.com/u/matjaz)
#### Post date: [April 9, 2020, 10:30pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/9 "2020-04-09T22:30:53Z")
@Tintin support for partials was reinstated (and enhanced) in Pinegrow 5.95:
> **[Partials | Pinegrow Web Editor](https://pinegrow.com/docs/pinegrow-pro/partials/)**
>
> Partials are files with parts of HTML code or components. Pinegrow lets you edit them in the context of their parent page.
Let us know how it goes.
---
### Author:  [@jonroc](https://forum.pinegrow.com/u/jonroc)
#### Post date: [April 18, 2020, 6:05pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/10 "2020-04-18T18:05:28Z")
I’ve always wanted a way to control footer scripts across the site. Ideally you should only have the script\> tag in header\> or body\>. Partials would almost work to help keep footer scripts organized and controlled by one master file but (like component items) you’d have to put the script in a div\> or something which is not semantically correct. If the partials had an insert after (like WP php does) then I could insert my footer script\> tags after my highest div tag and they would come out clean. Would a adding before/after be hard for this element?
---
### Author:  [@Tintin](https://forum.pinegrow.com/u/Tintin)
#### Post date: [April 21, 2020, 9:25pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/11 "2020-04-21T21:25:42Z")
HURRAY!! Partials but better 🙂 Thank you for listening!
---
### Author:  [@CleanCoderFX](https://forum.pinegrow.com/u/CleanCoderFX)
#### Post date: [June 28, 2023, 4:40pm UTC](https://forum.pinegrow.com/t/why-did-you-drop-partials/3878/12 "2023-06-28T16:40:00Z")
Do you still use Laravel with Pinegrow? Is it worth picking it up? I’ve been spoiled with Filemakers Front-end design tools for internal business apps. Would love to have the easy of use with Laravel.