toonvandenbos
commented
5 years ago Hi @DCReddish97,
I like the idea, but it causes an architectural problem with the routes binding the package provides in its current state.
Right now, static pages are always linked to existing routes. I understand your suggestion for dynamic routes, but it requires a little bit more digging before defining the feature because it could break some existing setups.
Just a little side note on your suggested roadmap: I don't see why the package should create a new blade template when creating a new page. Why would you extend an existing template instead of using it directly from a controller? The fields could be made available using the existing solutions.
I'm curious to hear more about the community's insights on this matter.
ArtMin96
nickbluestone98
It would be good if there was a create page function so you can create new pages in the admin panel, and assign it to a specific template through a dropdown thats pull's through all the templates thats have been made.
When a new page is made it'll create a new blade templates that just have a @extend layout in there, and all the page fields will be added to the layout file. I currently have mine set in the layout file and then I use select fields to define which block I want to create so the client can go in and edit a page by selecting the component they want and in the order they want it to display.
Then we would set up a dynamic routes to auto assign the new created pages to a route without having to manual add the routes.