Magento follows a pretty straight-forward templating structure. \u00a0Well, it’s straight forward once you get to know it. \u00a0It can be a little confusing at first to a html designer or someone who has worked in drupal or wordpress.<\/p>\n
The first thing to remember is that anything not defined falls back to base\/default. \u00a0So if you don’t define a template file, that’s OK, there’s a backup that will render the page for you. \u00a0This lets you know that every page in your magento store will work, assuming you didn’t break anything.<\/p>\n
First thing’s first, the package name in System->Configuration->Design. \u00a0You can set this on the global level, or a website, or even store view level. \u00a0This sets the package name that will be referenced in the next paragraph or two about the rest of the template structure. \u00a0For us, we always set that to evermoretech. \u00a0All the themes we develop are within that package. \u00a0Others will use their company name, the client name, or just work within default for their themes.<\/p>\n
Next up are the other 4 values you get to set. \u00a0Often, they are all set to one value. \u00a0(ie, MyStoreTheme), but the\u00a0flexibility\u00a0to set them individually allows for kinda cool theme development for magento. \u00a0I know I’m gonna take advantage of it. \u00a0The other 4 values in admin are:<\/p>\n
app\/design\/frontend\/package\/{value}\/layout\/<\/code>)
\nThe XML layout files that your theme uses.<\/li>\n- Templates<\/strong>\u00a0(located in\u00a0
app\/design\/frontend\/package\/{value}\/template\/<\/code>)
\nThese are PHTML files that contain (X)HTML markups and any necessary PHP tags to create logic for visual presentation.<\/li>\n- Locale<\/strong>\u00a0(located in\u00a0
app\/design\/frontend\/package\/{value}\/locale\/<\/code>)
\nThese are simple text documents organized on a per language basis that contain translations for store copy.<\/li>\n- Skins<\/strong>\u00a0(located in\u00a0
skin\/frontend\/package\/{value}\/<\/code>)
\nThese are block-specific Javascript and CSS and image files that compliment your (X)HTML.<\/li>\n<\/ul>\nThis information is documented at\u00a0http:\/\/www.magentocommerce.com\/design_guide\/articles\/magento-design-terminologies4#term-layouts<\/a>\u00a0and verified by Kevin Miles of Evermore Technologies as of Magento 1.6.1.0, the version I’m currently using for developing my stores.<\/div>\n","protected":false},"excerpt":{"rendered":"Magento follows a pretty straight-forward templating structure. \u00a0Well, it’s straight forward once you get to know it. \u00a0It can be a little confusing at first to a html designer or… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[29,22,7],"tags":[],"_links":{"self":[{"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/posts\/155"}],"collection":[{"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/comments?post=155"}],"version-history":[{"count":0,"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/posts\/155\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/media?parent=155"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/categories?post=155"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.evermoretechnologies.com\/blog\/wp-json\/wp\/v2\/tags?post=155"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}