Magento 2 - CMS Specific page_layout XML and Dedicated page_layouts in general?
I'm looking for some BEST PRACTICES insight into using page_layout.xml. Is it a good idea to try and decouple the non-shared resources on Product Pages, Category Pages and CMS Pages? If so, what's the best way to do this? Recently found myself creating a bunch of CMS specific CSS rules for our CSM pages and I knew the CSS rules may continue to grow a bit so I decided to create a dedicated layout file (Magento_Themepage_layoutcms_layout.xml). To achieve this, I created a new page_layout but also had to make a plugin beforeRenderResult() to load in in <body> BOTH the standard class page-layout-2columns-left and the new class page-layout-cms-layout. If I didn't do this, I would have had to modify a lot of CSS.
Some of the benefits I think I'm realizing are:
- (Maintenance) I no longer have to manage a lot of
Content > Page >content. I can just change the "Layout" dropdown to the CMS Specific Layout.
Design > Layout Update XML - (Slight Performance) I don't have to load the CSS for the CMS pages
on the Product Pages and Category Pages
Next up - might be to look at some of the heavy UI JS/CSS being used on Product Pages and not have that being loaded on Category Pages? Does this situation make sense to experiences Magento Developers OR should I provide more clarity?
I'm pretty certain I'm not making any big performance gains with this particular situation but I am curious whats "Best Practice". As it stands, it seems like Magento load the the entire websites resources on every page, no matter how big or small (Category JS/CSS, Details JS/CSS, Checkout JS/CSS, etc). I'm not sure that's great either.
layout css performance plugin page-layouts
asked 4 mins ago
JustinPJustinP
369415
add a comment |
I'm looking for some BEST PRACTICES insight into using page_layout.xml. Is it a good idea to try and decouple the non-shared resources on Product Pages, Category Pages and CMS Pages? If so, what's the best way to do this? Recently found myself creating a bunch of CMS specific CSS rules for our CSM pages and I knew the CSS rules may continue to grow a bit so I decided to create a dedicated layout file (Magento_Themepage_layoutcms_layout.xml). To achieve this, I created a new page_layout but also had to make a plugin beforeRenderResult() to load in in <body> BOTH the standard class page-layout-2columns-left and the new class page-layout-cms-layout. If I didn't do this, I would have had to modify a lot of CSS.
Some of the benefits I think I'm realizing are:
- (Maintenance) I no longer have to manage a lot of
Content > Page >content. I can just change the "Layout" dropdown to the CMS Specific Layout.
Design > Layout Update XML - (Slight Performance) I don't have to load the CSS for the CMS pages
on the Product Pages and Category Pages
Next up - might be to look at some of the heavy UI JS/CSS being used on Product Pages and not have that being loaded on Category Pages? Does this situation make sense to experiences Magento Developers OR should I provide more clarity?
I'm pretty certain I'm not making any big performance gains with this particular situation but I am curious whats "Best Practice". As it stands, it seems like Magento load the the entire websites resources on every page, no matter how big or small (Category JS/CSS, Details JS/CSS, Checkout JS/CSS, etc). I'm not sure that's great either.
layout css performance plugin page-layouts
asked 4 mins ago
JustinPJustinP
369415
add a comment |
I'm looking for some BEST PRACTICES insight into using page_layout.xml. Is it a good idea to try and decouple the non-shared resources on Product Pages, Category Pages and CMS Pages? If so, what's the best way to do this? Recently found myself creating a bunch of CMS specific CSS rules for our CSM pages and I knew the CSS rules may continue to grow a bit so I decided to create a dedicated layout file (Magento_Themepage_layoutcms_layout.xml). To achieve this, I created a new page_layout but also had to make a plugin beforeRenderResult() to load in in <body> BOTH the standard class page-layout-2columns-left and the new class page-layout-cms-layout. If I didn't do this, I would have had to modify a lot of CSS.
Some of the benefits I think I'm realizing are:
- (Maintenance) I no longer have to manage a lot of
Content > Page >content. I can just change the "Layout" dropdown to the CMS Specific Layout.
Design > Layout Update XML - (Slight Performance) I don't have to load the CSS for the CMS pages
on the Product Pages and Category Pages
Next up - might be to look at some of the heavy UI JS/CSS being used on Product Pages and not have that being loaded on Category Pages? Does this situation make sense to experiences Magento Developers OR should I provide more clarity?
I'm pretty certain I'm not making any big performance gains with this particular situation but I am curious whats "Best Practice". As it stands, it seems like Magento load the the entire websites resources on every page, no matter how big or small (Category JS/CSS, Details JS/CSS, Checkout JS/CSS, etc). I'm not sure that's great either.
layout css performance plugin page-layouts
asked 4 mins ago
JustinPJustinP
369415
I'm looking for some BEST PRACTICES insight into using page_layout.xml. Is it a good idea to try and decouple the non-shared resources on Product Pages, Category Pages and CMS Pages? If so, what's the best way to do this? Recently found myself creating a bunch of CMS specific CSS rules for our CSM pages and I knew the CSS rules may continue to grow a bit so I decided to create a dedicated layout file (Magento_Themepage_layoutcms_layout.xml). To achieve this, I created a new page_layout but also had to make a plugin beforeRenderResult() to load in in <body> BOTH the standard class page-layout-2columns-left and the new class page-layout-cms-layout. If I didn't do this, I would have had to modify a lot of CSS.
Some of the benefits I think I'm realizing are:
- (Maintenance) I no longer have to manage a lot of
Content > Page >content. I can just change the "Layout" dropdown to the CMS Specific Layout.
Design > Layout Update XML - (Slight Performance) I don't have to load the CSS for the CMS pages
on the Product Pages and Category Pages
Next up - might be to look at some of the heavy UI JS/CSS being used on Product Pages and not have that being loaded on Category Pages? Does this situation make sense to experiences Magento Developers OR should I provide more clarity?
I'm pretty certain I'm not making any big performance gains with this particular situation but I am curious whats "Best Practice". As it stands, it seems like Magento load the the entire websites resources on every page, no matter how big or small (Category JS/CSS, Details JS/CSS, Checkout JS/CSS, etc). I'm not sure that's great either.
layout css performance plugin page-layouts
layout css performance plugin page-layouts
asked 4 mins ago
JustinPJustinP
369415
asked 4 mins ago
JustinPJustinP
369415
asked 4 mins ago
JustinPJustinP
369415
asked 4 mins ago
JustinPJustinP
369415
asked 4 mins ago
JustinPJustinP
369415
369415
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f258412%2fmagento-2-cms-specific-page-layout-xml-and-dedicated-page-layouts-in-general%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f258412%2fmagento-2-cms-specific-page-layout-xml-and-dedicated-page-layouts-in-general%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
