-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layout #60
Labels
Comments
Closed
drewroberts
added a commit
that referenced
this issue
Apr 2, 2021
drewroberts
added a commit
that referenced
this issue
Apr 2, 2021
drewroberts
added a commit
that referenced
this issue
Apr 2, 2021
drewroberts
added a commit
that referenced
this issue
Apr 7, 2021
drewroberts
added a commit
that referenced
this issue
Apr 7, 2021
drewroberts
added a commit
that referenced
this issue
Apr 7, 2021
drewroberts
added a commit
that referenced
this issue
Apr 7, 2021
drewroberts
added a commit
that referenced
this issue
Apr 7, 2021
@pdbreen These are really Single-Page Layouts, should I change the name to Template instead of Layout to avoid confusion in the terminology? |
@drewroberts i think layout is fine, but really have no strong opinion towards one vs the other. |
drewroberts
added a commit
that referenced
this issue
Apr 9, 2021
drewroberts
added a commit
that referenced
this issue
Apr 9, 2021
drewroberts
added a commit
that referenced
this issue
Apr 9, 2021
View Layouts for Frontend Pages #60
drewroberts
added a commit
that referenced
this issue
Apr 10, 2021
drewroberts
added a commit
that referenced
this issue
Apr 10, 2021
…-relationships Layout Relationships #60
drewroberts
added
model description
Description of a model
Perpetual
Never ending issues
labels
Apr 10, 2021
This was referenced Apr 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 (#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: