You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Layout should define a model like Page (drewroberts/blog#15) or Market (TIPOFF/locations#41) and then define a blade file. The model can then have a belongsTo relationship with Layout and there can be a default set by the package in the config file for each model of that package that will be included in web routes. That blade template can be published and updated in the application and other variations could also be created both in the package and in the application (example: AMP validated layouts). Each entry in that model can then use the default layout or define its own.
The text was updated successfully, but these errors were encountered:
There should be a model named Layout that is used in a somewhat similar concept to WordPress' page layouts:
The Layout should define a model like Page (drewroberts/blog#15) or Market (TIPOFF/locations#41) and then define a blade file. The model can then have a
belongsTo
relationship with Layout and there can be a default set by the package in the config file for each model of that package that will be included in web routes. That blade template can be published and updated in the application and other variations could also be created both in the package and in the application (example: AMP validated layouts). Each entry in that model can then use the default layout or define its own.The text was updated successfully, but these errors were encountered: