Magento Development Services

Magento is an open source e-commerce web application that was launched on March 31, 2008, under the name Bento. It was developed by Varian (now Magento a division of eBay) with help from the programmers within the open source community but is now owned solely by eBay Inc.Magento was built using parts of the Zend Framework. It uses the entity-attribute-value (EAV) database model to store data. In November 2013, W3Techs estimated that Magento was used by 0.9% of all websites

Magento has a wonderful architecture behind its system. It’s a very strict architecture that relies on us knowing where the files should be placed and how to structure our templates and modules. But this is part of what makes Magento a great system, in that it enforces these standards, each of these files and directories have a different purpose. We’ll go through them to ensure that we understand the function of each. This will help us later, if ever we need to find something specific, or when developing. It will also be helpful when we’ll be looking to place the files coming out of our new module into the appropriate directory

Each theme contains structural and content blocks. Structural blocks are the ones that lay out the theme into sections. Let’s take a look at a three-column layout.

The following are the structural blocks in a three-column layout:

• Header

• left

• Content

• Right

• Footer

In each of the structural blocks, we then have content blocks that give each structural block its content for output to the browser. Let’s take the right column; our content blocks set for this column on a standard theme could be: mini cart

Here we have a visual representation of these content blocks on top of the Magento

Demo store:

On receiving a request from a user connecting to our site to view the page:

1. Magento will load the structural areas

2. Each structural area will be processed through

3. Magento will gather the content blocks assigned to each structural area

4. It will then progress through the content block template for each structural area, to process the output

5. It sends all of this back as final output to the user, who then views the Magento page that was requested

To assign blocks to each of these structural blocks, Magento loads an XML layout file for each request. This XML layout file is called by the URL that the user is accessing the site. It declares all modules that are to be loaded in each structural area of the site. On top of this, we have a page .xml file, which is the default loader for all pages on the site.