Author

Staff Writer

A 'nom de plume' for one of our talented wordsmiths...

thebattleofmagentos_banner

Are you ready to revolutionise the merchant experience even further? As retail market leaders do you seek next generation architecture delivering unrivalled functionality that effectively brings your digital vision to life? Well say goodbye to to what are currently doing and usher in the era of enhanced scalability with Magento’s latest suite of powerful omni-channel solutions via Magento 2.0

magento_2_commerce

To put it simply we have always loved Magento and Magento 2.0 is just another step in a fantastic journey we started in 2008. At March 2016 we have already been involved in 6 builds, Magento upgrades or migrations and the results are outstanding.

Magento 2.0 delivers engaging online experiences across every touch point, with accessible data, extensions, themes and customisations. Paul and the core team at Magento have enhanced and upgraded an industry leading open source digital commerce platform that has been simplified, scaled, and modularised. It has an elegant upgrade path that Mal and the developers at Balance Internet just love.

With the scale to support 3.5 million page views per hour and the capacity to catalogue over 250,000 orders per hour, how can you ensure your business maintains market share and a piece of the profitability pie? Do the visual aesthetics of the ‘Madison Island’ or ‘Luma’ theme complement your digital vision? And what are the main differences between Magento 1 and 2 in their theme and extension offerings?

Let’s take a look at 4 factors to consider….

#1. Extensions

Magento 1:

  • The code for extensions in Magento 1.X are segmented into 3 “code pools”; “core”, “community” and “local”. Then depending on the extension it could also have files in app/design, skin/frontend or js directories. This platform approach while effective, also presents challenges, as all files contained span across the entire install (depending on what’s included).
  • This configuration can make the removal of extensions a difficult process.

Magento 2:

  • Magento 2 contains all extensions within the same area, including extension code, template and layout files, JavaScript and CSS files. This enables you to locate required files both quickly and efficiently. This file structure has been efficiently modified from the first outing.
  • In the Magento 2.0, platform extensions in the app/code section are split into namespaces. This means all the core code is placed in the Magento folder and within that folder are all the core modules. Simple really! Check out our diagram which highlights, for example the Balance namespace, which is where we would place all of our customised extensions.

themingM1M2

 

#2. To Theme or not to Theme?

  • While themes are placed into the app/design/frontend area on both Magento 1.X and 2.0, the newest platform finds them split into a more modular fashion.
  • Select from infinite theme fallbacks in Magento 2.0 including the flagship Luma theme. Allowing you the option to make slight changes if necessary, you can create a new theme that falls back to the Luma theme, individually interchanging sections as required.
  • Create additional stores integrating all the changes from your previous theme while adding more, and with the ability to revert to your first customised theme if necessary. This truly is where creativity and customisation meet to deliver your desired outcome.
  • With unmatched flexibility at all stages you can fall back through as many themes as you like to the Luma theme.

#3. What’s in a Theme?

Magento boasts a powerful theme system, with an emphasis on efficiency and usability.

  • Layout (located in app/design/frontend/your_interface/your_theme/layout/), these are basic XML files that define block structure for different pages as well as control META information and page*
  • Templates (located in app/design/frontend/your_interface/your_theme/template/). These are PHTML files that contain (X)HTML markups and any necessary PHP tags to create logic for visual presentation*
  • Locale (located in app/design/frontend/your_interface/your_theme/locale/). These are simple text documents organised on a per language basis that contains translations for store copy*
  • Skins (located in skin/frontend/your_interface/your_theme/). These are block-specific Javascript and CSS and image files that compliment your (X) HTML*

#4. The Great Data Migration?

  • Magento 1.X is fantastic and it will be supported for years to come by Balance Internet and other gold SI’s globally. Now you can make an informed decision to assess the your Magento 1 platform and consider upgrading and migrating to the more productive, higher performing superior scalability of Magento 2.0.
  • The file structure within Magento 2.0 is cleaner, more streamlined and designed to expand your eCommerce capabilities with a less bloated installation process.
  • With new technologies under the hood, the battle between the Magento’s can only prove beneficial for the 240,000- online retailers currently offering this powerful, digital eCommerce platform worldwide.

In Australia, Magento has a 40% plus marketshare so the options for all those on Magento 1.X CE and EE are endless. You can stay on 1.X or consider migrating to Magento 2.0 . Boasting effective updates that improve query performance; Magento performance toolkit to verify and optimise system performance, Varnish cache to reduce server load and quicken page load, Magento have the eCommerce platform for you.

Call the team at Balance Internet today on 1300 624 368. We’ll show you the path to profitability, brand recognition and ROI that inspires!

Magento1vs2

 

Subscribe to our newsletter

Get updates, news, industry events and tips to increase conversion rate.

Top