From afbb5da3b8ecb56574f2c477e123991d8216f447 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Fri, 10 Mar 2023 05:27:51 +0000
Subject: [PATCH 1/3] Bump nokogiri from 1.8.4 to 1.8.5

Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.8.4 to 1.8.5.
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md)
- [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.8.4...v1.8.5)

---
updated-dependencies:
- dependency-name: nokogiri
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
---
 Gemfile.lock | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Gemfile.lock b/Gemfile.lock
index e2337cd348..6690698e29 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -246,7 +246,7 @@ GEM
       jekyll-seo-tag (~> 2.1)
     minitest (5.11.3)
     multipart-post (2.0.0)
-    nokogiri (1.8.4)
+    nokogiri (1.8.5)
       mini_portile2 (~> 2.3.0)
     octokit (4.12.0)
       sawyer (~> 0.8.0, >= 0.5.3)

From bdca09419451e2a1d2ef9c9eda746b06e1d04e4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nils=20Bre=C3=9Fler?= <n.bressler@b3-it.de>
Date: Mon, 29 Jan 2024 11:48:32 +0100
Subject: [PATCH 2/3] B3-IT: Update/change php developer guide and frontend
 developer guide, update links

---
 Gemfile                                       |    1 +
 Gemfile.lock                                  |  429 +++---
 _config.yml                                   |   21 +-
 common/css/stylesheet.css                     |  885 +++++++----
 guides/m1x/magefordev/mage-for-dev-1.html     | 1295 ++++++++++-------
 guides/m1x/magefordev/mage-for-dev-2.html     |  718 ++++++---
 guides/m1x/magefordev/mage-for-dev-3.html     |  903 ++++++++----
 guides/m1x/magefordev/mage-for-dev-4.html     | 1220 ++++++++++------
 guides/m1x/magefordev/mage-for-dev-5.html     | 1168 +++++++++------
 guides/m1x/magefordev/mage-for-dev-6.html     | 1089 +++++++++-----
 guides/m1x/magefordev/mage-for-dev-7.html     |  686 ++++++---
 guides/m1x/magefordev/mage-for-dev-8.html     |  618 +++++---
 .../magefordev/mage-for-frontend-dev-1.html   |  421 ++++++
 .../magefordev/mage-for-frontend-dev-10.html  |  335 +++++
 .../magefordev/mage-for-frontend-dev-2.html   |  350 +++++
 .../magefordev/mage-for-frontend-dev-3.html   |  380 +++++
 .../magefordev/mage-for-frontend-dev-4.html   |  348 +++++
 .../magefordev/mage-for-frontend-dev-5.html   |  351 +++++
 .../magefordev/mage-for-frontend-dev-6.html   |  569 ++++++++
 .../magefordev/mage-for-frontend-dev-7.html   |  646 ++++++++
 .../magefordev/mage-for-frontend-dev-8.html   |  378 +++++
 .../magefordev/mage-for-frontend-dev-9.html   |  440 ++++++
 index.html                                    |   37 +-
 23 files changed, 10015 insertions(+), 3273 deletions(-)
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-1.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-10.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-2.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-3.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-4.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-5.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-6.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-7.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-8.html
 create mode 100644 guides/m1x/magefordev/mage-for-frontend-dev-9.html

diff --git a/Gemfile b/Gemfile
index 1cb3ba0f00..46c0e1bf71 100644
--- a/Gemfile
+++ b/Gemfile
@@ -3,6 +3,7 @@ source 'https://rubygems.org'
 gem 'github-pages'
 gem 'jekyll-last-modified-at'
 gem 'devdocs', :git => 'https://github.com/magento-devdocs/devdocs-theme.git', :branch => 'devdocs-stable'
+gem "webrick", "~> 1.8"
 
 gem 'wdm' if Gem.win_platform?
 
diff --git a/Gemfile.lock b/Gemfile.lock
index 6690698e29..41e3c20189 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,6 +1,6 @@
 GIT
   remote: https://github.com/magento-devdocs/devdocs-theme.git
-  revision: f864973ba8a063a7ad3da4ecfe47fa978a230f17
+  revision: edabd815ee3ead3efffe983be5cb6961c3543aae
   branch: devdocs-stable
   specs:
     devdocs (0.0.1)
@@ -9,283 +9,332 @@ GIT
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.2.10)
-      i18n (~> 0.7)
-      minitest (~> 5.1)
-      thread_safe (~> 0.3, >= 0.3.4)
-      tzinfo (~> 1.1)
-    addressable (2.5.2)
-      public_suffix (>= 2.0.2, < 4.0)
-    algolia_html_extractor (2.6.1)
+    Ascii85 (1.1.0)
+    activesupport (7.1.2)
+      base64
+      bigdecimal
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      connection_pool (>= 2.2.5)
+      drb
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      mutex_m
+      tzinfo (~> 2.0)
+    addressable (2.8.6)
+      public_suffix (>= 2.0.2, < 6.0)
+    afm (0.2.2)
+    algolia_html_extractor (2.6.4)
       json (~> 2.0)
-      nokogiri (~> 1.8.2)
-    algoliasearch (1.23.2)
+      nokogiri (~> 1.10)
+    algoliasearch (1.27.5)
       httpclient (~> 2.8, >= 2.8.3)
       json (>= 1.5.1)
+    async (2.8.0)
+      console (~> 1.10)
+      fiber-annotation
+      io-event (~> 1.1)
+      timers (~> 4.1)
+    base64 (0.2.0)
+    bigdecimal (3.1.5)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
     coffee-script-source (1.11.1)
     colorator (1.1.0)
-    colorize (0.8.1)
-    commonmarker (0.17.13)
-      ruby-enum (~> 0.5)
-    concurrent-ruby (1.0.5)
-    dnsruby (1.61.2)
-      addressable (~> 2.5)
-    em-websocket (0.5.1)
+    commonmarker (0.23.10)
+    concurrent-ruby (1.2.2)
+    connection_pool (2.4.1)
+    console (1.23.3)
+      fiber-annotation
+      fiber-local
+    dnsruby (1.70.0)
+      simpleidn (~> 0.2.1)
+    drb (2.2.0)
+      ruby2_keywords
+    em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0.6.0)
-    ethon (0.11.0)
-      ffi (>= 1.3.0)
+      http_parser.rb (~> 0)
+    ethon (0.16.0)
+      ffi (>= 1.15.0)
     eventmachine (1.2.7)
-    execjs (2.7.0)
-    faraday (0.15.3)
-      multipart-post (>= 1.2, < 3)
-    ffi (1.9.25)
+    execjs (2.9.1)
+    faraday (2.9.0)
+      faraday-net_http (>= 2.0, < 3.2)
+    faraday-net_http (3.1.0)
+      net-http
+    ffi (1.16.3-x64-mingw-ucrt)
+    fiber-annotation (0.2.0)
+    fiber-local (1.0.0)
     filesize (0.2.0)
     forwardable-extended (2.6.0)
-    gemoji (3.0.0)
-    github-pages (192)
-      activesupport (= 4.2.10)
-      github-pages-health-check (= 1.8.1)
-      jekyll (= 3.7.4)
-      jekyll-avatar (= 0.6.0)
+    gemoji (3.0.1)
+    github-pages (228)
+      github-pages-health-check (= 1.17.9)
+      jekyll (= 3.9.3)
+      jekyll-avatar (= 0.7.0)
       jekyll-coffeescript (= 1.1.1)
-      jekyll-commonmark-ghpages (= 0.1.5)
+      jekyll-commonmark-ghpages (= 0.4.0)
       jekyll-default-layout (= 0.1.4)
-      jekyll-feed (= 0.10.0)
+      jekyll-feed (= 0.15.1)
       jekyll-gist (= 1.5.0)
-      jekyll-github-metadata (= 2.9.4)
-      jekyll-mentions (= 1.4.1)
-      jekyll-optional-front-matter (= 0.3.0)
+      jekyll-github-metadata (= 2.13.0)
+      jekyll-include-cache (= 0.2.1)
+      jekyll-mentions (= 1.6.0)
+      jekyll-optional-front-matter (= 0.3.2)
       jekyll-paginate (= 1.1.0)
-      jekyll-readme-index (= 0.2.0)
-      jekyll-redirect-from (= 0.14.0)
-      jekyll-relative-links (= 0.5.3)
-      jekyll-remote-theme (= 0.3.1)
+      jekyll-readme-index (= 0.3.0)
+      jekyll-redirect-from (= 0.16.0)
+      jekyll-relative-links (= 0.6.1)
+      jekyll-remote-theme (= 0.4.3)
       jekyll-sass-converter (= 1.5.2)
-      jekyll-seo-tag (= 2.5.0)
-      jekyll-sitemap (= 1.2.0)
-      jekyll-swiss (= 0.4.0)
-      jekyll-theme-architect (= 0.1.1)
-      jekyll-theme-cayman (= 0.1.1)
-      jekyll-theme-dinky (= 0.1.1)
-      jekyll-theme-hacker (= 0.1.1)
-      jekyll-theme-leap-day (= 0.1.1)
-      jekyll-theme-merlot (= 0.1.1)
-      jekyll-theme-midnight (= 0.1.1)
-      jekyll-theme-minimal (= 0.1.1)
-      jekyll-theme-modernist (= 0.1.1)
-      jekyll-theme-primer (= 0.5.3)
-      jekyll-theme-slate (= 0.1.1)
-      jekyll-theme-tactile (= 0.1.1)
-      jekyll-theme-time-machine (= 0.1.1)
-      jekyll-titles-from-headings (= 0.5.1)
-      jemoji (= 0.10.1)
-      kramdown (= 1.17.0)
-      liquid (= 4.0.0)
-      listen (= 3.1.5)
+      jekyll-seo-tag (= 2.8.0)
+      jekyll-sitemap (= 1.4.0)
+      jekyll-swiss (= 1.0.0)
+      jekyll-theme-architect (= 0.2.0)
+      jekyll-theme-cayman (= 0.2.0)
+      jekyll-theme-dinky (= 0.2.0)
+      jekyll-theme-hacker (= 0.2.0)
+      jekyll-theme-leap-day (= 0.2.0)
+      jekyll-theme-merlot (= 0.2.0)
+      jekyll-theme-midnight (= 0.2.0)
+      jekyll-theme-minimal (= 0.2.0)
+      jekyll-theme-modernist (= 0.2.0)
+      jekyll-theme-primer (= 0.6.0)
+      jekyll-theme-slate (= 0.2.0)
+      jekyll-theme-tactile (= 0.2.0)
+      jekyll-theme-time-machine (= 0.2.0)
+      jekyll-titles-from-headings (= 0.5.3)
+      jemoji (= 0.12.0)
+      kramdown (= 2.3.2)
+      kramdown-parser-gfm (= 1.1.0)
+      liquid (= 4.0.4)
       mercenary (~> 0.3)
-      minima (= 2.5.0)
-      nokogiri (>= 1.8.2, < 2.0)
-      rouge (= 2.2.1)
+      minima (= 2.5.1)
+      nokogiri (>= 1.13.6, < 2.0)
+      rouge (= 3.26.0)
       terminal-table (~> 1.4)
-    github-pages-health-check (1.8.1)
+    github-pages-health-check (1.17.9)
       addressable (~> 2.3)
       dnsruby (~> 1.60)
       octokit (~> 4.0)
-      public_suffix (~> 2.0)
+      public_suffix (>= 3.0, < 5.0)
       typhoeus (~> 1.3)
-    html-pipeline (2.8.4)
+    hashery (2.1.2)
+    html-pipeline (2.14.3)
       activesupport (>= 2)
       nokogiri (>= 1.4)
-    html-proofer (3.9.2)
-      activesupport (>= 4.2, < 6.0)
+    html-proofer (5.0.8)
       addressable (~> 2.3)
-      colorize (~> 0.8)
-      mercenary (~> 0.3.2)
-      nokogiri (~> 1.8.1)
-      parallel (~> 1.3)
+      async (~> 2.1)
+      nokogiri (~> 1.13)
+      pdf-reader (~> 2.11)
+      rainbow (~> 3.0)
       typhoeus (~> 1.3)
       yell (~> 2.0)
-    http_parser.rb (0.6.0)
+      zeitwerk (~> 2.5)
+    http_parser.rb (0.8.0)
     httpclient (2.8.3)
-    i18n (0.9.5)
+    i18n (1.14.1)
       concurrent-ruby (~> 1.0)
-    jekyll (3.7.4)
+    io-event (1.4.1)
+    jekyll (3.9.3)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
-      i18n (~> 0.7)
+      i18n (>= 0.7, < 2)
       jekyll-sass-converter (~> 1.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 1.14)
+      kramdown (>= 1.17, < 3)
       liquid (~> 4.0)
       mercenary (~> 0.3.3)
       pathutil (~> 0.9)
       rouge (>= 1.7, < 4)
       safe_yaml (~> 1.0)
-    jekyll-algolia (1.4.7)
+    jekyll-algolia (1.7.1)
       algolia_html_extractor (~> 2.6)
-      algoliasearch (~> 1.18)
+      algoliasearch (~> 1.26)
       filesize (~> 0.1)
-      jekyll (~> 3.0)
+      jekyll (>= 3.6, < 5.0)
       json (~> 2.0)
       nokogiri (~> 1.6)
       progressbar (~> 1.9)
       verbal_expressions (~> 0.1.5)
-    jekyll-avatar (0.6.0)
-      jekyll (~> 3.0)
+    jekyll-avatar (0.7.0)
+      jekyll (>= 3.0, < 5.0)
     jekyll-coffeescript (1.1.1)
       coffee-script (~> 2.2)
       coffee-script-source (~> 1.11.1)
-    jekyll-commonmark (1.2.0)
-      commonmarker (~> 0.14)
-      jekyll (>= 3.0, < 4.0)
-    jekyll-commonmark-ghpages (0.1.5)
-      commonmarker (~> 0.17.6)
-      jekyll-commonmark (~> 1)
-      rouge (~> 2)
+    jekyll-commonmark (1.4.0)
+      commonmarker (~> 0.22)
+    jekyll-commonmark-ghpages (0.4.0)
+      commonmarker (~> 0.23.7)
+      jekyll (~> 3.9.0)
+      jekyll-commonmark (~> 1.4.0)
+      rouge (>= 2.0, < 5.0)
     jekyll-default-layout (0.1.4)
       jekyll (~> 3.0)
-    jekyll-feed (0.10.0)
-      jekyll (~> 3.3)
+    jekyll-feed (0.15.1)
+      jekyll (>= 3.7, < 5.0)
     jekyll-gist (1.5.0)
       octokit (~> 4.2)
-    jekyll-github-metadata (2.9.4)
-      jekyll (~> 3.1)
+    jekyll-github-metadata (2.13.0)
+      jekyll (>= 3.4, < 5.0)
       octokit (~> 4.0, != 4.4.0)
-    jekyll-last-modified-at (1.0.1)
-      jekyll (~> 3.3)
+    jekyll-include-cache (0.2.1)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-last-modified-at (1.3.0)
+      jekyll (>= 3.7, < 5.0)
       posix-spawn (~> 0.3.9)
-    jekyll-mentions (1.4.1)
+    jekyll-mentions (1.6.0)
       html-pipeline (~> 2.3)
-      jekyll (~> 3.0)
-    jekyll-optional-front-matter (0.3.0)
-      jekyll (~> 3.0)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-optional-front-matter (0.3.2)
+      jekyll (>= 3.0, < 5.0)
     jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.2.0)
-      jekyll (~> 3.0)
-    jekyll-redirect-from (0.14.0)
-      jekyll (~> 3.3)
-    jekyll-relative-links (0.5.3)
-      jekyll (~> 3.3)
-    jekyll-remote-theme (0.3.1)
-      jekyll (~> 3.5)
-      rubyzip (>= 1.2.1, < 3.0)
+    jekyll-readme-index (0.3.0)
+      jekyll (>= 3.0, < 5.0)
+    jekyll-redirect-from (0.16.0)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-relative-links (0.6.1)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-remote-theme (0.4.3)
+      addressable (~> 2.0)
+      jekyll (>= 3.5, < 5.0)
+      jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0)
+      rubyzip (>= 1.3.0, < 3.0)
     jekyll-sass-converter (1.5.2)
       sass (~> 3.4)
-    jekyll-seo-tag (2.5.0)
-      jekyll (~> 3.3)
-    jekyll-sitemap (1.2.0)
-      jekyll (~> 3.3)
-    jekyll-swiss (0.4.0)
-    jekyll-theme-architect (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-seo-tag (2.8.0)
+      jekyll (>= 3.8, < 5.0)
+    jekyll-sitemap (1.4.0)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-swiss (1.0.0)
+    jekyll-theme-architect (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-cayman (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-cayman (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-dinky (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-dinky (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-hacker (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-hacker (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-leap-day (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-leap-day (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-merlot (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-merlot (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-midnight (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-midnight (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-minimal (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-minimal (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-modernist (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-modernist (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-primer (0.5.3)
-      jekyll (~> 3.5)
+    jekyll-theme-primer (0.6.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-github-metadata (~> 2.9)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-slate (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-slate (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-tactile (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-tactile (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-time-machine (0.1.1)
-      jekyll (~> 3.5)
+    jekyll-theme-time-machine (0.2.0)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-titles-from-headings (0.5.1)
-      jekyll (~> 3.3)
-    jekyll-watch (2.0.0)
+    jekyll-titles-from-headings (0.5.3)
+      jekyll (>= 3.3, < 5.0)
+    jekyll-watch (2.2.1)
       listen (~> 3.0)
-    jemoji (0.10.1)
+    jemoji (0.12.0)
       gemoji (~> 3.0)
       html-pipeline (~> 2.2)
-      jekyll (~> 3.0)
-    json (2.1.0)
-    kramdown (1.17.0)
-    launchy (2.4.3)
-      addressable (~> 2.3)
-    liquid (4.0.0)
-    listen (3.1.5)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-      ruby_dep (~> 1.2)
+      jekyll (>= 3.0, < 5.0)
+    json (2.7.1)
+    kramdown (2.3.2)
+      rexml
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
+    launchy (2.5.2)
+      addressable (~> 2.8)
+    liquid (4.0.4)
+    listen (3.8.0)
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
     mercenary (0.3.6)
-    mini_portile2 (2.3.0)
-    minima (2.5.0)
-      jekyll (~> 3.5)
+    minima (2.5.1)
+      jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.11.3)
-    multipart-post (2.0.0)
-    nokogiri (1.8.5)
-      mini_portile2 (~> 2.3.0)
-    octokit (4.12.0)
-      sawyer (~> 0.8.0, >= 0.5.3)
-    parallel (1.12.1)
-    pathutil (0.16.1)
+    minitest (5.21.1)
+    mutex_m (0.2.0)
+    net-http (0.4.1)
+      uri
+    nokogiri (1.16.0-x64-mingw-ucrt)
+      racc (~> 1.4)
+    octokit (4.25.1)
+      faraday (>= 1, < 3)
+      sawyer (~> 0.9)
+    pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    posix-spawn (0.3.13)
-    progressbar (1.10.0)
-    public_suffix (2.0.5)
-    rb-fsevent (0.10.3)
-    rb-inotify (0.9.10)
-      ffi (>= 0.5.0, < 2)
-    rouge (2.2.1)
-    ruby-enum (0.7.2)
-      i18n
-    ruby_dep (1.5.0)
-    rubyzip (1.2.2)
-    safe_yaml (1.0.4)
-    sass (3.6.0)
+    pdf-reader (2.12.0)
+      Ascii85 (~> 1.0)
+      afm (~> 0.2.1)
+      hashery (~> 2.0)
+      ruby-rc4
+      ttfunk
+    posix-spawn (0.3.15)
+    progressbar (1.13.0)
+    public_suffix (4.0.7)
+    racc (1.7.3)
+    rainbow (3.1.1)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.10.1)
+      ffi (~> 1.0)
+    rexml (3.2.6)
+    rouge (3.26.0)
+    ruby-rc4 (0.1.5)
+    ruby2_keywords (0.0.5)
+    rubyzip (2.3.2)
+    safe_yaml (1.0.5)
+    sass (3.7.4)
       sass-listen (~> 4.0.0)
     sass-listen (4.0.0)
       rb-fsevent (~> 0.9, >= 0.9.4)
       rb-inotify (~> 0.9, >= 0.9.7)
-    sawyer (0.8.1)
-      addressable (>= 2.3.5, < 2.6)
-      faraday (~> 0.8, < 1.0)
+    sawyer (0.9.2)
+      addressable (>= 2.3.5)
+      faraday (>= 0.17.3, < 3)
+    simpleidn (0.2.1)
+      unf (~> 0.1.4)
     terminal-table (1.8.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
-    thread_safe (0.3.6)
-    typhoeus (1.3.0)
+    timers (4.3.5)
+    ttfunk (1.7.0)
+    typhoeus (1.4.1)
       ethon (>= 0.9.0)
-    tzinfo (1.2.5)
-      thread_safe (~> 0.1)
-    unicode-display_width (1.4.0)
+    tzinfo (2.0.6)
+      concurrent-ruby (~> 1.0)
+    unf (0.1.4)
+      unf_ext
+    unf_ext (0.0.9.1-x64-mingw-ucrt)
+    unicode-display_width (1.8.0)
+    uri (0.13.0)
     verbal_expressions (0.1.5)
-    yell (2.0.7)
+    wdm (0.1.1)
+    webrick (1.8.1)
+    yell (2.2.2)
+    zeitwerk (2.6.12)
 
 PLATFORMS
-  ruby
+  x64-mingw-ucrt
 
 DEPENDENCIES
   devdocs!
@@ -294,6 +343,8 @@ DEPENDENCIES
   jekyll-algolia (~> 1.0)
   jekyll-last-modified-at
   launchy
+  wdm
+  webrick (~> 1.8)
 
 BUNDLED WITH
-   1.16.5
+   2.5.4
diff --git a/_config.yml b/_config.yml
index 806c3b871c..727bd755bc 100644
--- a/_config.yml
+++ b/_config.yml
@@ -33,10 +33,14 @@ defaults:
       feedback_link: true
   -
     scope:
-      path: guides/m1x
+      path: guides/v19.x
+    values:
+      layout: null
+  -
+    scope:
+      path: guides/v1.8
     values:
       layout: null
-
   -
     scope:
       path: mftf/2.2
@@ -94,8 +98,8 @@ algolia:
   index_name: devdocs
   api_key: d2d0f33ab73e291ef8d88d8b565e754c
   files_to_exclude:
-    - guides/m1x/**/*.html
-    - guides/m1x/**/*.md
+    - guides/v19.x/**/*.html
+    - guides/v19.x/**/*.md
     - swagger
     - redoc
 
@@ -111,8 +115,12 @@ check_links: true
 #############
 #
 # 1.x variables
-m1xgdeurl: /guides/m1x/
-m1xgithuburl: https://github.com/OpenMage/devdocs/blob/master/
+
+v1xgdeurl: /guides/v19.x
+v1xgithuburl: https://github.com/OpenMage/devdocs/tree/master
+v18xgdeurl: /guides/v1.8/
+
+gdeurl23: https://devdocs.magento.com/redoc/2.3/
 
 ##########
 # Ignore #
@@ -136,3 +144,4 @@ exclude:
   - rakelib
   - README.md
   - _plugins
+
diff --git a/common/css/stylesheet.css b/common/css/stylesheet.css
index d32d22ff92..750762b747 100644
--- a/common/css/stylesheet.css
+++ b/common/css/stylesheet.css
@@ -2,216 +2,398 @@
 /* CSS Document */
 
 body {
-	 background-color: #ffffff;  margin: 0 auto; font-size:15px; font: 15px/22px 'Poppins' , Arial, sans-serif; color:#5A5A5A; font-weight:normal; width:1024px;
-	}
+    background-color: #ffffff;
+    /*margin: 0 5vw;*/
+    font-size: 15px;
+    font: 15px/22px 'Poppins', Arial, sans-serif;
+    color: #5A5A5A;
+    font-weight: normal;
+}
 
 /* containers */
-#container { width:940px; margin:0; }
-#content { width:940px; margin:15px 45px 0 45px; }
+#container {
+    width: 940px;
+    margin: 0;
+}
+
+#content {
+    width: 100%;
+    margin: 15px 45px 0 45px;
+}
 
 /* left nav style */
 .show {
-	display:block;  position: relative;
+    display: block;
+    position: relative;
     top: -15px;
 }
-.hide{
-	display:none; position: relative;
+
+.hide {
+    display: none;
+    position: relative;
     top: -15px;
 }
-#container-2 { width:940px; margin:10px 0 0 45px; }
-#left-nav { float:left; width:220px; margin-right:20px; display:block; }
-#left-nav  ul { margin:10px 0 8px; }
-#left-nav li { border-bottom:2px dotted #dddddd; list-style: none;
-	padding: 10px 5px; margin: 10px 0; }
-#content-2 { float:right; width:700px; }
-#left-nav h4 { color:#666666; border-bottom:2px dotted #dddddd; padding:5px; }
+
+#container-2 {
+    width: 940px;
+    margin: 10px 0 0 45px;
+}
+
+#left-nav {
+    float: left;
+    width: 220px;
+    margin-right: 20px;
+    display: block;
+}
+
+#left-nav ul {
+    margin: 10px 0 8px;
+}
+
+#left-nav li {
+    border-bottom: 2px dotted #dddddd;
+    list-style: none;
+    padding: 10px 5px;
+    margin: 10px 0;
+}
+
+#content-2 {
+    float: right;
+    width: 1024px;
+}
+
+#left-nav h4 {
+    color: #666666;
+    border-bottom: 2px dotted #dddddd;
+    padding: 5px;
+}
+
 #left-nav li.highlight a:link, #left-nav li.highlight a:visited {
     color: #FB0E70;
     text-decoration: none;
 }
+
 #left-nav ul.related-documents li {
-	font-size:13px; border:0; padding: 5px; margin: 5px 0 5px 5px;
-	background-image: url(".bullet-round-orange.png");
-	background-repeat: no-repeat;
-	background-position: 0 9px;
-	padding-left: 16px;
-	}
+    font-size: 13px;
+    border: 0;
+    padding: 5px;
+    margin: 5px 0 5px 5px;
+    background-image: url(".bullet-round-orange.png");
+    background-repeat: no-repeat;
+    background-position: 0 9px;
+    padding-left: 16px;
+}
 
 /* end left nav styles */
 
 /* HEADINGS */
-h1, h2 { font-weight:100; margin:30px 0 10px 0; }
+h1, h2 {
+    font-weight: 100;
+    margin: 30px 0 10px 0;
+}
 
-h3, h4, h5, h6 { font-weight:100; color:#444444; margin:25px 0 2px 0; }
+h3, h4, h5, h6 {
+    font-weight: 100;
+    color: #444444;
+    margin: 25px 0 2px 0;
+}
 
-h1 { font: 36px/46px 'Poppins', Helvetica, sans-serif; letter-spacing: 0; }
+h1 {
+    font: 36px/46px 'Poppins', Helvetica, sans-serif;
+    letter-spacing: 0;
+}
 
-h2 { font: 31px/41px 'Poppins', Helvetica, sans-serif; color:#A447A4; }
+h2 {
+    font: 31px/41px 'Poppins', Helvetica, sans-serif;
+    color: #A447A4;
+}
 
-h3 { font: 27px/37px 'Poppins', Helvetica, sans-serif; letter-spacing: 0;}
+h3 {
+    font: 27px/37px 'Poppins', Helvetica, sans-serif;
+    letter-spacing: 0;
+}
 
-h4 { font: 23px/37px 'Poppins', Helvetica, sans-serif; letter-spacing: 0; }
+h4 {
+    font: 23px/37px 'Poppins', Helvetica, sans-serif;
+    letter-spacing: 0;
+}
 
-h5 { font: 17px/27px 'Poppins', Helvetica, sans-serif; letter-spacing: 0; font-weight:bold; margin-top:25px; }
+h5 {
+    font: 17px/27px 'Poppins', Helvetica, sans-serif;
+    letter-spacing: 0;
+    font-weight: bold;
+    margin-top: 25px;
+}
 
-h6 { font: 14px/24px 'Poppins', Helvetica, sans-serif; letter-spacing: 0; font-weight:bold; margin-top:25px; }
+h6 {
+    font: 14px/24px 'Poppins', Helvetica, sans-serif;
+    letter-spacing: 0;
+    font-weight: bold;
+    margin-top: 25px;
+}
 
 /* TOC */
-div.toc { background: url(blend-toc.png) repeat-x; border-left:1px solid #effbfd; padding:0 10px; margin-bottom:20px; }
-div.section.toc { position:relative; top:-15px; }
-h4.toc { font-weight:300; padding: 10px 0 10px ; }
-p.toc { color: #cccccc; margin-bottom:10px; }
-p.toc a { padding: 0 5px 0 5px; }
-p.toc a.first { padding-left: 0; }
+div.toc {
+    background: url(blend-toc.png) repeat-x;
+    border-left: 1px solid #effbfd;
+    padding: 0 10px;
+    margin-bottom: 20px;
+}
+
+div.section.toc {
+    position: relative;
+    top: -15px;
+}
+
+h4.toc {
+    font-weight: 300;
+    padding: 10px 0 10px;
+}
+
+p.toc {
+    color: #cccccc;
+    margin-bottom: 10px;
+}
+
+p.toc a {
+    padding: 0 5px 0 5px;
+}
+
+p.toc a.first {
+    padding-left: 0;
+}
 
 /*PARAGRAPHS */
-p { letter-spacing: 0.05px; color:#555555; line-height:20px; margin: 8px 0 17px;}
+p {
+    letter-spacing: 0.05px;
+    color: #555555;
+    line-height: 20px;
+    margin: 8px 0 17px;
+}
 
 /* LINKS */
-a:link, a:visited { color:#A447A4; text-decoration:none; }
-a:hover{ color:#FB0E70; }
-a:active{ color:#FB0E70; }
+a:link, a:visited {
+    color: #A447A4;
+    text-decoration: none;
+}
+
+a:hover {
+    color: #FB0E70;
+}
+
+a:active {
+    color: #FB0E70;
+}
 
 /* NOTES TIPS ETC. */
 
 .msg-box, .sm-note-box {
-    margin:2px 0 15px 0;
-	width:85%;
-	border-radius: 8px 0 8px 0;
-	font-size:14px;
-	color:#777777;
+    margin: 2px 0 15px 0;
+    width: 85%;
+    border-radius: 8px 0 8px 0;
+    font-size: 14px;
+    color: #777777;
     padding: 8px 12px 8px 0;
     text-shadow: 0 1px 0 rgba(255, 255, 255, 0.5);
-	min-height:35px; }
+    min-height: 35px;
+}
 
 .sm-note-box {
-	min-height:15px;
+    min-height: 15px;
     background-color: rgba(0, 0, 0, 0.025);
-	border:1px solid #888888;
-	border-left: 3px solid #888888; }
+    border: 1px solid #888888;
+    border-left: 3px solid #888888;
+}
 
-.sm-note-box span { padding: 0 10px 0 10px; }
+.sm-note-box span {
+    padding: 0 10px 0 10px;
+}
 
-.msg-text { color:#777777; font-size:14px; }
+.msg-text {
+    color: #777777;
+    font-size: 14px;
+}
 
 .caution {
     background-color: rgba(240, 171, 0, .05);
     border: 1px solid #f7941d;
-	border-left: 5px solid #f7941d; }
+    border-left: 5px solid #f7941d;
+}
 
 .important {
     background-color: rgba(251, 14, 112, 0.04);
-	border:1px solid #FB0E70;
-	border-left: 5px solid #FB0E70; }
+    border: 1px solid #FB0E70;
+    border-left: 5px solid #FB0E70;
+}
 
 .note {
     background-color: rgba(0, 0, 0, 0.025);
-	border:1px solid #888888;
-	border-left: 5px solid #888888; }
+    border: 1px solid #888888;
+    border-left: 5px solid #888888;
+}
 
 .tip {
     background-color: rgba(246, 220, 27, .05);
-	border:1px solid #fbe841;
-	border-left: 5px solid #fbe841; }
+    border: 1px solid #fbe841;
+    border-left: 5px solid #fbe841;
+}
+
+.msg-box span {
+    position: relative;
+    left: 10px;
+    padding-right: 5px;
+}
+
+.msg-box img {
+    position: relative;
+    top: -3px;
+    left: 5px;
+    width: 30px
+}
+
 
-.msg-box span { position:relative; left:10px; padding-right:5px; }
-.msg-box img { position:relative; top:-3px; left:5px; width:30px }
+pre {
+    font-size: 14px;
+    line-height: 20px;
+    overflow: auto;
+}
 
+pre strong {
+    color: #333333;
+}
 
-pre { font-size:14px; line-height:20px; overflow: auto; }
-pre strong{ color:#333333; }
-pre, .link-callout { padding:10px; margin:0 0 20px;
-	background-color: #F3F6F9; border:1px solid #ebeff2; border-radius: 4px; }
+pre, .link-callout {
+    padding: 10px;
+    margin: 0 0 20px;
+    background-color: #F3F6F9;
+    border: 1px solid #ebeff2;
+    border-radius: 4px;
+}
 
-.link-callout {  width:450px; color:#666666;  }
+.link-callout {
+    width: 450px;
+    color: #666666;
+}
 
 
 /* LISTS */
-ul, ol ul li, ul ol li, ol li ol li ul.level1 li
-{
-	list-style-type: none;
-	padding: 0;
-	margin: 0;
+ul, ol ul li, ul ol li, ol li ol li ul.level1 li {
+    list-style-type: none;
+    padding: 0;
+    margin: 0;
 }
 
 ul li li, ul li li li, ol li li {
-	margin-left: 5px;
+    margin-left: 5px;
 }
- ul li li li {
-	margin-left: 10px;
+
+ul li li li {
+    margin-left: 10px;
 }
 
-ul.level1 li, ul li.level1, ol li ol li ul.level1 li
-{
-	background-image: url("bullet-round-orange.png");
-	background-repeat: no-repeat;
-	background-position: 0 7px;
-	padding-left: 16px;
-	margin-bottom:6px;
+ul.level1 li, ul li.level1, ol li ol li ul.level1 li {
+    background-image: url("bullet-round-orange.png");
+    background-repeat: no-repeat;
+    background-position: 0 7px;
+    padding-left: 16px;
+    margin-bottom: 6px;
+}
+
+ul.level2 li, ul li.level2, ol li ol li ul.level2 li {
+    background-image: url("bullet-round-gold.png");
+    background-repeat: no-repeat;
+    background-position: 0 6px;
+    padding-left: 16px;
+    margin-bottom: 6px;
 }
-ul.level2 li, ul li.level2, ol li ol li ul.level2 li
-{
-	background-image: url("bullet-round-gold.png");
-	background-repeat: no-repeat;
-	background-position: 0 6px;
-	padding-left: 16px;
-	margin-bottom:6px;
+
+ul.level3 li, ul li.level3, ol li ol li ul.level3 li {
+    background-image: url("bullet-round-gray.png");
+    background-repeat: no-repeat;
+    background-position: 0 6px;
+    padding-left: 16px;
+    margin-bottom: 6px;
 }
-ul.level3 li, ul li.level3, ol li ol li ul.level3 li
-{
-	background-image: url("bullet-round-gray.png");
-	background-repeat: no-repeat;
-	background-position: 0 6px;
-	padding-left: 16px;
-	margin-bottom:6px;
+
+ol li, ul ol li {
+    list-style: decimal outside none;
+    background-image: none;
 }
-ol li, ul ol li { list-style: decimal outside none; background-image:none; }
-ol li { margin-bottom:8px; }
-li p { margin:2px 0 8px; font-size:14px; }
 
-dl dd { padding: 5px 0 6px 0; margin-left:24px }
-dd p { margin:4px 0 0; }
+ol li {
+    margin-bottom: 8px;
+}
 
-dl, ul, ol { margin:10px 0 8px 20px; }
+li p {
+    margin: 2px 0 8px;
+    font-size: 14px;
+}
 
-ol ol, ul ol  { margin:10px 0 8px 5px; }
+dl dd {
+    padding: 5px 0 6px 0;
+    margin-left: 24px
+}
 
-ol ol li, ul li ol li { list-style-type:lower-alpha; }
-ol ol ol li, ul li ol li ol li { list-style-type:lower-roman; padding-left:2px; }
+dd p {
+    margin: 4px 0 0;
+}
 
-dl { margin-left:0; }
+dl, ul, ol {
+    margin: 10px 0 8px 20px;
+}
 
-/* list overrides - SRJ */
+ol ol, ul ol {
+    margin: 10px 0 8px 5px;
+}
 
+ol ol li, ul li ol li {
+    list-style-type: lower-alpha;
+}
+
+ol ol ol li, ul li ol li ol li {
+    list-style-type: lower-roman;
+    padding-left: 2px;
+}
+
+dl {
+    margin-left: 0;
+}
+
+/* list overrides - SRJ */
 
 
 /* This sort of works */
 
-ul li
-{
-  background-image: url("bullet-round-orange.png");
-  background-repeat: no-repeat;
-  background-position: 0 7px;
-  padding-left: 16px;
-  margin-bottom:6px;
-  margin-left: 5px;
+ul li {
+    /*
+    background-image: url("bullet-round-orange.png");
+    background-repeat: no-repeat;
+    background-position: 0 7px;
+     */
+    padding-left: 16px;
+    margin-bottom: 6px;
+    margin-left: 5px;
 }
-ul li, ul li
-{
-  background-image: url("bullet-round-gold.png");
-  background-repeat: no-repeat;
-  background-position: 0 6px;
-  padding-left: 16px;
-  margin-bottom:6px;
-  margin-left: 10px;
+
+ul li, ul li {
+    /*
+    background-image: url("bullet-round-gold.png");
+    background-repeat: no-repeat;
+    background-position: 0 6px;
+     */
+    padding-left: 16px;
+    margin-bottom: 6px;
+    margin-left: 10px;
 }
-ul li, ul li, ul li
-{
-  background-image: url("bullet-round-gray.png");
-  background-repeat: no-repeat;
-  background-position: 0 6px;
-  padding-left: 16px;
-  margin-bottom:6px;
+
+ul li, ul li, ul li {
+    /*
+    background-image: url("bullet-round-gray.png");
+    background-repeat: no-repeat;
+    background-position: 0 6px;
+     */
+    padding-left: 16px;
+    margin-bottom: 6px;
 }
 
 ol li ul li {
@@ -246,25 +428,49 @@ ul:nth-child(3) li {
 
 /* NUMBERED CODE */
 
-pre.lineCount { background: #F3F6F9 url("gutter.png") 2.1em 0 repeat-y;
-	border:1px solid #ebeff2; line-height:0; margin:0; padding:0; }
+pre.lineCount {
+    background: #F3F6F9 url("gutter.png") 2.1em 0 repeat-y;
+    border: 1px solid #ebeff2;
+    line-height: 0;
+    margin: 0;
+    padding: 0;
+}
 
 ol.listLineCount {
-	overflow:auto;
-	margin:0;
-	padding-left: 32px;
-	color:#ffffff;
-	line-height:5px;
+    overflow: auto;
+    margin: 0;
+    padding-left: 32px;
+    color: #ffffff;
+    line-height: 5px;
 }
 
-.lineCount ol li { color:#333333; font-weight:400; }
-.lineCount ol li.odd { background-color:#F3F6F9; }
+.lineCount ol li {
+    color: #333333;
+    font-weight: 400;
+}
+
+.lineCount ol li.odd {
+    background-color: #F3F6F9;
+}
 
-pre.lineCount li code { color:#333333; line-height:15px;}
+pre.lineCount li code {
+    color: #333333;
+    line-height: 15px;
+}
 
-caption, p.caption { font-family:Georgia, "Times New Roman", Times, serif; color:#787878; font-size: 14px; font-style:italic; padding:0; margin:10px 0 15px 3px;}
+caption, p.caption {
+    font-family: Georgia, "Times New Roman", Times, serif;
+    color: #787878;
+    font-size: 14px;
+    font-style: italic;
+    padding: 0;
+    margin: 10px 0 15px 3px;
+}
 
-caption {margin:0px 0 2px 0; padding:20px 0 5px 0; }
+caption {
+    margin: 0px 0 2px 0;
+    padding: 20px 0 5px 0;
+}
 
 /* TABLE */
 
@@ -272,10 +478,12 @@ table {
     border-collapse: collapse;
     text-align: left;
     width: 100%;
-	color:#555555;
+    color: #555555;
 }
+
 table td, table th, table tr, table tr th {
-	padding:8px;}
+    padding: 8px;
+}
 
 table tr:nth-child(odd) { /*(odd) or (2n 1)*/
     background-color: #F3F6F9;
@@ -288,6 +496,7 @@ table tr:nth-child(odd) { /*(odd) or (2n 1)*/
     color: #222222;
     vertical-align: top;
 }
+
 table tr:nth-child(even) { /*(even) or (2n 0)*/
     border-bottom: medium none;
     border-color: transparent #ffffff;
@@ -298,14 +507,16 @@ table tr:nth-child(even) { /*(even) or (2n 0)*/
     color: #222222;
     vertical-align: top;
 }
+
 table th {
     border: #dce5ed 1px solid;
     color: #444444;
     font-weight: 600;
     padding: 5px;
     vertical-align: top;
-	font-size:13px;
+    font-size: 13px;
 }
+
 /*table .table-headings th {
 	background-color: rgba(220, 229, 237, .50);
     border:1px solid #dce5ed;
@@ -332,10 +543,10 @@ tr.even, tr.odd {
     padding: 0.1em 0.6em;
 }*/
 td {
-    border:1px solid #dce5ed;
+    border: 1px solid #dce5ed;
     color: #555555;
     padding: 10px;
-	font-size:13px;
+    font-size: 13px;
 }
 
 /* Back to Top */
@@ -343,255 +554,301 @@ td {
 p.btt a:link, p.btt a:active, p.btt a:visited {
     background: url("btt.png") no-repeat scroll 0 2px transparent;
     float: right;
-	position:relative;
-	top:-35px;
+    position: relative;
+    top: -35px;
     font-size: 12px;
     padding: 0 0 0 15px;
     text-decoration: none;
 }
-p.btt.last {position:relative;top:40px;}
+
+p.btt.last {
+    position: relative;
+    top: 40px;
+}
 
 /* paging */
 p.paging {
     float: right;
-	position:relative;
-	top:-42px;
+    position: relative;
+    top: -42px;
     font-size: 12px;
-	font-weight:600;
-	color:#777777;
+    font-weight: 600;
+    color: #777777;
     padding: 0 0 0 15px;
     text-decoration: none;
 }
-p.paging span { padding:5px; }
+
+p.paging span {
+    padding: 5px;
+}
+
 p.paging a {
-	font-weight:100; padding:5px; }
+    font-weight: 100;
+    padding: 5px;
+}
+
 p.paging.bottom {
-	position:relative;
-	top:42px; }
+    position: relative;
+    top: 42px;
+}
 
 /* Rules */
-.dotted-rule { border-top: 2px dotted #dddddd; margin: 15px 0 15px 0; }
-hr { border: 0; color: #e2e2e2; background-color: #e2e2e2; height: 2px;  margin: 15px 0 15px 0; }
+.dotted-rule {
+    border-top: 2px dotted #dddddd;
+    margin: 15px 0 15px 0;
+}
+
+hr {
+    border: 0;
+    color: #e2e2e2;
+    background-color: #e2e2e2;
+    height: 2px;
+    margin: 15px 0 15px 0;
+}
 
 /* Images */
 
 .images {
-  margin-left: -20px;
-  list-style: none;
-  *zoom: 1;
+    margin-left: -20px;
+    list-style: none;
+    *zoom: 1;
 }
 
 .images:before,
 .images:after {
-  display: table;
-  content: "";
+    display: table;
+    content: "";
 }
 
 .images:after {
-  clear: both;
+    clear: both;
 }
 
 .row-fluid .images {
-  margin-left: 0;
+    margin-left: 0;
 }
 
 .images > li {
-  float: left;
-  margin-bottom: 5px;
-  margin-left: 20px;
+    float: left;
+    margin-bottom: 5px;
+    margin-left: 20px;
 }
 
 .image {
-  display: block;
-  margin-top:10px;
-  padding: 8px;
-  line-height: 1;
-  border: 1px solid #ddd;
-  -webkit-border-radius: 4px;
-     -moz-border-radius: 4px;
-          border-radius: 4px;
-  -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-     -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-          box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-}
-.image.medium { width:680px; }
-
-.image.large { width:920px; }
+    display: block;
+    margin-top: 10px;
+    padding: 8px;
+    line-height: 1;
+    border: 1px solid #ddd;
+    -webkit-border-radius: 4px;
+    -moz-border-radius: 4px;
+    border-radius: 4px;
+    -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+}
+
+.image.medium {
+    width: 680px;
+}
+
+.image.large {
+    width: 920px;
+}
 
 a.image:hover {
-  border-color: #0088cc;
-  -webkit-box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25);
-     -moz-box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25);
-          box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25);
+    border-color: #0088cc;
+    -webkit-box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25);
+    -moz-box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25);
+    box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25);
 }
 
 .image > img {
-  display: block;
-  max-width: 100%;
-  margin-right: auto;
-  margin-left: auto;
-}
-
-
-.expandimg img:hover
-{
-   -webkit-transform:scale(1.6);
-   -moz-transform:scale(1.6);
-   -o-transform:scale(1.6);
-   box-shadow:0 0 30px gray;
-   -webkit-box-shadow:0 0 30px gray;
-   -moz-box-shadow:0 0 30px gray;
-   opacity: 1;
-   margin-left: 145px;
-}
-
-.expandimg-border img:hover
-{
-   -webkit-transform:scale(1.6);
-   -moz-transform:scale(1.6);
-   -o-transform:scale(1.6);
-   border: 1px solid #ddd;
-   -webkit-border-radius: 4px;
-   -moz-border-radius: 4px;
-   border-radius: 4px;
-   -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-   -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-   box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-   opacity: 1;
-   margin-left: 195px;
-}
-
-.expandimg-thumb img:hover
-{
-   -webkit-transform:scale(2.5);
-   -moz-transform:scale(2.5);
-   -o-transform:scale(2.5);
-   border: 1px solid #ddd;
-   -webkit-border-radius: 4px;
-   -moz-border-radius: 4px;
-   border-radius: 4px;
-   -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-   -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-   box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-   opacity: 1;
+    display: block;
+    max-width: 100%;
+    margin-right: auto;
+    margin-left: auto;
+}
+
+
+.expandimg img:hover {
+    -webkit-transform: scale(1.6);
+    -moz-transform: scale(1.6);
+    -o-transform: scale(1.6);
+    box-shadow: 0 0 30px gray;
+    -webkit-box-shadow: 0 0 30px gray;
+    -moz-box-shadow: 0 0 30px gray;
+    opacity: 1;
+    margin-left: 145px;
+}
+
+.expandimg-border img:hover {
+    -webkit-transform: scale(1.6);
+    -moz-transform: scale(1.6);
+    -o-transform: scale(1.6);
+    border: 1px solid #ddd;
+    -webkit-border-radius: 4px;
+    -moz-border-radius: 4px;
+    border-radius: 4px;
+    -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    opacity: 1;
+    margin-left: 195px;
+}
+
+.expandimg-thumb img:hover {
+    -webkit-transform: scale(2.5);
+    -moz-transform: scale(2.5);
+    -o-transform: scale(2.5);
+    border: 1px solid #ddd;
+    -webkit-border-radius: 4px;
+    -moz-border-radius: 4px;
+    border-radius: 4px;
+    -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    opacity: 1;
 }
 
 
 .expandimg-border, .expandimg-thumb {
-   display: block;
-   margin-top:10px;
-   padding: 8px;
-   line-height: 1;
-   border: 1px solid #ddd;
-   -webkit-border-radius: 4px;
-   -moz-border-radius: 4px;
-   border-radius: 4px;
-   -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-   -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
-   box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    display: block;
+    margin-top: 10px;
+    padding: 8px;
+    line-height: 1;
+    border: 1px solid #ddd;
+    -webkit-border-radius: 4px;
+    -moz-border-radius: 4px;
+    border-radius: 4px;
+    -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
+    box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075);
 }
 
 /* TABS */
 .nav {
-  margin-bottom: 18px;
-  margin-left: 0;
-  list-style: none;
+    margin-bottom: 18px;
+    margin-left: 0;
+    list-style: none;
 }
 
 .nav > li > a {
-  display: block;
+    display: block;
 }
 
 .nav > li > a:hover {
-  text-decoration: none;
-  background-color: rgba(0, 144, 192, 0.03);
+    text-decoration: none;
+    background-color: rgba(0, 144, 192, 0.03);
 }
 
 
-.nav-tabs{
-  *zoom: 1;
+.nav-tabs {
+    *zoom: 1;
 }
 
 .nav-tabs:before,
-.nav-tabs:after{
-  display: table;
-  content: "";
+.nav-tabs:after {
+    display: table;
+    content: "";
 }
 
 .nav-tabs:after {
-  clear: both;
+    clear: both;
 }
 
 .nav-tabs > li {
-  float: left;
+    float: left;
 }
 
 .nav-tabs > li > a {
-  padding-right: 12px;
-  padding-left: 12px;
-  margin-right: 2px;
-  line-height: 14px;
+    padding-right: 12px;
+    padding-left: 12px;
+    margin-right: 2px;
+    line-height: 14px;
 }
 
 .nav-tabs {
-  border-bottom: 1px solid #ddd;
+    border-bottom: 1px solid #ddd;
 }
 
 .nav-tabs > li {
-  margin-bottom: -1px;
+    margin-bottom: -1px;
 }
 
 .nav-tabs > li > a {
-  padding-top: 8px;
-  padding-bottom: 8px;
-  line-height: 18px;
-  border: 1px solid transparent;
-  -webkit-border-radius: 4px 4px 0 0;
-     -moz-border-radius: 4px 4px 0 0;
-          border-radius: 4px 4px 0 0;
+    padding-top: 8px;
+    padding-bottom: 8px;
+    line-height: 18px;
+    border: 1px solid transparent;
+    -webkit-border-radius: 4px 4px 0 0;
+    -moz-border-radius: 4px 4px 0 0;
+    border-radius: 4px 4px 0 0;
 }
 
 .nav-tabs > li > a:hover {
-  border-color: #caecf3 #caecf3 #dddddd;
+    border-color: #caecf3 #caecf3 #dddddd;
 }
 
 .nav-tabs > .active > a,
 .nav-tabs > .active > a:hover {
-  color: #555555;
-  cursor: default;
-  background-color: #ffffff;
-  border: 1px solid #ddd;
-  border-bottom-color: transparent;
+    color: #555555;
+    cursor: default;
+    background-color: #ffffff;
+    border: 1px solid #ddd;
+    border-bottom-color: transparent;
+}
+
+.tab-content {
+    border-bottom: 1px solid #DDDDDD;
+    padding: 0 0 5px;
 }
 
-.tab-content { border-bottom: 1px solid #DDDDDD; padding: 0 0 5px; }
-.tab-content p { color:#777777; }
+.tab-content p {
+    color: #777777;
+}
 
 /* CODE COMMENTS AND MANDATORY STEPS */
-.comments { color:#339900 }
-.mandatory { color:#EE6933 }
+.comments {
+    color: #339900
+}
+
+.mandatory {
+    color: #EE6933
+}
 
 
 .soap-api-menu {
     float: left;
-    margin-left: -45px;
-    width: 250px;
+    width: 20%;
 }
+
 .soap-api-menu {
     border-bottom: 1px solid #cac2b5;
     padding-bottom: 10px;
     margin-top: 20px;
 }
+
+.soap-api-menu-header {
+    text-transform: uppercase;
+    font-weight: 700;
+    letter-spacing: 0.06em;
+    margin-top: 12px;
+}
+
 .soap-api-menu > ul {
     margin-left: 0;
 }
+
 .soap-api-menu ul {
     margin-top: 5px;
     margin-bottom: 5px;
 }
+
 .soap-api-menu > ul > ul {
     margin-left: 0;
 }
+
 .soap-api-menu ul li {
     background: none;
     margin-bottom: 0;
@@ -601,26 +858,32 @@ a.image:hover {
     overflow: hidden;
     font-size: 14px;
 }
+
 .soap-api-menu ul li a {
     color: #444;
 }
+
 .soap-api-menu ul li a:hover,
 .soap-api-menu ul li a.active {
     color: #FB0E70;
 }
+
 .soap-api-content {
-    float: right;
-    width: 750px;
+    float: left;
+    width: 70%;
     clear: right;
-    margin-right: -45px;
+    margin-left: 2vw;
 }
+
 .soap-api-menu li.parent,
 .soap-api-menu > ul > li {
     margin-bottom: 5px;
 }
+
 .soap-api-menu li.parent > ul {
     display: none;
 }
+
 .soap-api-menu li.parent > .arr {
     display: inline-block;
     width: 12px;
@@ -628,6 +891,7 @@ a.image:hover {
     position: relative;
     cursor: pointer;
 }
+
 .soap-api-menu li.parent > .arr:before {
     position: absolute;
     width: 0;
@@ -638,6 +902,7 @@ a.image:hover {
     border: 7px outset transparent;
     border-top: 7px solid #FB0E70;
 }
+
 .soap-api-menu li.parent > .arr:after {
     position: absolute;
     width: 0;
@@ -648,69 +913,75 @@ a.image:hover {
     border: 7px outset transparent;
     border-top: 7px solid #fff;
 }
+
 .soap-api-menu li.parent.open > .arr:before {
     border: 7px outset transparent;
     border-bottom: 7px solid #FB0E70;
     top: -3px;
 }
+
 .soap-api-menu li.parent.open > .arr:after {
     border: 7px outset transparent;
     border-bottom: 7px solid #fff;
     top: -1px;
 }
+
 .soap-api-menu li.parent > a,
 .soap-api-menu > ul > li > a {
     font-weight: bold;
 }
+
 .introduction-menu {
     background: #fdf2fd;
     margin-left: 0;
     padding: 20px;
     list-style: none;
 }
+
 .introduction-menu li {
     background: none;
     padding: 0;
 }
+
 .introduction-menu a {
     color: #A447A4
 }
+
 .introduction-menu a:hover {
     color: #FB0E70
 }
 
 .message-banner {
-	background: #FBEDD9;
-	border: 1px solid #C27500;
-	padding: 20px;
-	border-radius: 2px;
-	margin: 10px 0;
+    background: #FBEDD9;
+    border: 1px solid #FB0E70;
+    padding: 20px;
+    border-radius: 2px;
+    margin: 10px 0;
 }
 
 .message-banner h4 {
-	margin-top: 0;
+    margin-top: 0;
 }
+
 .message-banner p:last-child {
-	margin-bottom: 0;
+    margin-bottom: 0;
 }
 
-.site-title h4
-{
-  float:right;
+.site-title h4 {
+    width: 50%;
+    float: right;
 }
 
-#footer
-{
-  clear: both;
-  margin-top: 4em;
-  padding: 1em;
-  width:100%;
-  background-color: #000537;
-  box-sizing: border-box;
+#footer {
+    clear: both;
+    margin-top: 4em;
+    padding: 1em;
+    width: 100%;
+    background-color: #000537;
+    box-sizing: border-box;
 }
 
-#imprint
-{
-  position: absolute;
-  right: 1em; 
+#imprint {
+    position: absolute;
+    right: 1em;
 }
diff --git a/guides/m1x/magefordev/mage-for-dev-1.html b/guides/m1x/magefordev/mage-for-dev-1.html
index 395772e5a8..cf67075558 100644
--- a/guides/m1x/magefordev/mage-for-dev-1.html
+++ b/guides/m1x/magefordev/mage-for-dev-1.html
@@ -1,507 +1,806 @@
 ---
 ---
 <!DOCTYPE html>
-<html lang=en>
-
+<html lang="en" dir="ltr">
 <head>
-    <meta charset=utf-8>
-
-    <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
-    <link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
-    <link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <title>Magento for Developers: Part 1&mdash;Introduction to Magento</title>
-
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>OpenMage for Developers: Part 1&mdash;Introduction to OpenMage</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
 <!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
 <!-- magento-for-dev-part-1-introduction-to-magento -->
-
-<img src="{{ site.baseurl }}/guides/m1x/images/m1xheader.png" width="1024" alt="header" />
-{% include m1x/eol_message.html %}
-
-<div id="top"></div>
-
-<div id="content">
-<h1>Magento for Developers: Part 1&mdash;Introduction to Magento</h1>
-<p><em>by Alan Storm</em>, updated for Magento 1.12</p>
-<p><a href="{{ site.m1xgithuburl }}/magefordev/mage-for-dev-1.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>
-
-<!-- <style type="text/css">
-#kb-entry .series { float: right; width: 175px; margin-left: 10px; }
-#kb-entry .series ul { margin-left: 15px;}
-</style> 
-<div class="r-box-rss series"> -->
-<h4>Other articles in this series:</h4>
-<ul>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-1.html">Part 1&mdash;Introduction to Magento</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-2.html">Part 2&mdash;The Magento Config</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-3.html">Part 3&mdash;Magento Controller Dispatch</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-4.html">Part 4&mdash;Magento Layouts, Blocks and Templates</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">Part 5&mdash;Magento Models and ORM Basics</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Part 6&mdash;Magento Setup Resources</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">Part 7&mdash;Advanced ORM: Entity Attribute Value</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-8.html">Part 8&mdash;Varien Data Collections</a>
-</ul>
-
-<p class="para1">What is Magento?  It's the most powerful online eCommerce platform in the universe and is changing the face of eCommerce forever. :-)</p>
-
-<p>Of course, you already know that.  What you may not realize is Magento's also an object-oriented PHP Framework that can be used to develop modern, dynamic web applications that tap into Magento's powerful eCommerce features.</p>
-
-<p>This is the first in a series of articles in which we're going to go on a whirlwind tour of Magento's programming framework features. Don't worry if you don't follow everything immediately. As you study the system more everything in this article will start to make sense, and you'll soon be the envy of your colleagues stuck working with more primitive PHP systems.</p>
-
-<h4>In this article...</h4>
-<ul><li><a href="#1" title="Code Organized in Modules">Code Organized in Modules</a>
-<li><a href="#2" title="Configuration-Based MVC">Configuration-Based MVC</a>
-<li><a href="#3" title="Controllers">Controllers</a>
-<li><a href="#4" title="Context-Based URI Model Loading">Context-Based URI Model Loading</a>
-<li><a href="#5" title="Models">Models</a>
-<li><a href="#6" title="Helpers">Helpers</a>
-<li><a href="#7" title="Layouts">Layouts</a>
-<li><a href="#8" title="Observers">Observers</a>
-<li><a href="#9" title="Class Overrides">Class Overrides</a>
-<li><a href="#10" title="Wrap Up">Wrap Up</a>
-</ul>
-
-<p>Or for the more visually oriented <a href="{{ site.baseurl }}/guides/m1x/images/Magento_MVC.pdf">Magento_MVC.pdf</a>.</p>
-
-<hr/>
-<a name="1"></a>
-<h2>Code Organized in Modules</h2>
-
-<p>Magento organizes its code into individual Modules. In a typical PHP <a href="http://en.wikipedia.org/wiki/Model–view–controller" target="_new"><b>Model-View-Controller (MVC)</b></a> application, all the Controllers will be in one folder, all the Models in another, etc.  In Magento, files are grouped together based on functionality, which are called <b>modules</b> in Magento.</p>
-
-<h4>Magento's Code</h4>
-<p>For example, you'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's checkout functionality in</p>
-<pre>app/code/core/Mage/Checkout</pre>
-
-<p>You'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's Google Checkout functionality in</p>
-<pre>app/code/core/Mage/GoogleCheckout</pre>
-
-<h4>Your Code</h4>
-<p>When you want to customize or extend Magento, rather than editing core files directly, or even placing your new Controllers, Models, Helpers, Blocks, etc. next to Magento code, you'll create your own Modules in</p>
-<pre>app/code/local/Package/Modulename</pre>
-
-<p><b>Package</b> (also often referred to as a <b>Namespace</b>) is a unique name that identifies your company or organization. The intent is that each member of the world-wide Magento community will use their own Package name when creating modules in order to avoid colliding with another user's code.  </p>
-
-<p>When you create a new Module, you need to tell Magento about it.  This is done by adding an XML file to the folder:</p>
-<pre>app/etc/modules</pre>
-
-<p>There are two kinds of files in this folder, the first enables an individual Module, and is named in the form:</p>
-<tt>Packagename_Modulename.xml</tt>
-
-<p>The second is a file that will enable multiple Modules from a Package/Namespace, and is named in the form:</p>
-<tt>Packagename_All.xml</tt>. Note it is only used by the core team with the file <tt>Mage_All.xml</tt>. It is <b>not recommended</b> to activate several modules in a single file, as this breaks the modularity of your modules.
-
-<a name="2"></a>
-<h2>Configuration-Based MVC</h2>
-
-<p>Magento is a <b>configuration-based</b> MVC system.  The alternative to this would a <b>convention-based</b> MVC system.</p>
-
-<p>In a convention-based MVC system, if you wanted to add, say, a new Controller or maybe a new Model, you'd just create the file/class, and the system would pick it up automatically.</p>
-
-<p>In a configuration-based system, like Magento, in addition to adding the new file/class to the codebase, you often need to explicitly tell the system about the new class, or new group of classes. In Magento, each Module has a file named <tt>config.xml</tt>. This file contains all the relevant configuration for a Magento Module.  At runtime, all these files are loaded into one large configuration tree.</p>
-
-<p>For example, want to use Models in your custom Module?  You'll need to add some code to <tt>config.xml</tt> that tells Magento you want to use Models, as well as what the base class name for all your Models should be.</p>
-
-<pre>
-    &lt;models>
-         &lt;packagename>
-              &lt;class>Packagename_Modulename_Model&lt;/class>
-        &lt;/packagename>
-    &lt;/models>
-</pre>    
-<p>The same goes for Helpers, Blocks, Routes for your Controllers, Event Handlers, and more. Almost anytime you want to tap into the power of the Magento system, you'll need to make some change or addition to your config file.</p>
-
-<a name="3"></a>
-<h2>Controllers</h2>
-
-<p>In any PHP system, the main PHP entry point remains a PHP file.  Magento is no different, and that file is <tt>index.php</tt>.</p>
-
-<p>However, you never CODE in index.php. In an MVC system, index.php will contain code/calls to code that does the following:</p>
-<ol>
-<li><p>Examines the URL</p></li>
-<li><p>Based on some set of rules, turns this URL into a Controller class and an Action method (called Routing)</p></li>
-<li><p>Instantiates the Controller class and calls the Action method (called dispatching)</p></li>
-</ol>
-
-<p>This means the <strong>practical</strong> entry point in Magento (or any MVC-based system) is a method in a Controller file. Consider the following URL:</p>
-
-<pre>http://example.com/catalog/category/view/id/25</pre>
-
-<p>Each portion of the path after the server name is parsed as follows.</p>
-
-<h4>Front Name - <tt>catalog</tt></h4>
-<p>The first portion of the URL is called the front name.  This, more or less, tells magento which Module it can find a Controller in. In the above example, the front name is <em>catalog</em>, which corresponds to the Module located at:</p>
-<pre>app/code/core/Mage/Catalog</pre>
-
-<h4>Controller Name - <tt>category</tt></h4>
-<p>The second portion of the URL tells Magento which Controller it should use.  Each Module with Controllers has a special folder named 'controllers' which contains all the Controllers for a module. In the above example, the URL portion category is translated into the Controller file</p>
-<pre>app/code/core/Mage/Catalog/controllers/CategoryController.php</pre>
-
-<p>Which looks like</p>
-<pre>
-class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
-{
-}
-</pre>
-
-<p>All Controllers in the Magento cart application extend from Mage_Core_Controller_Front_Action.</p>
-
-<h4>Action Name - <tt>view</tt></h4>
-
-<p>Third in our URL is the action name.  In our example, this is "view".  The word "view"  is used to create the Action Method. So, in our example, "view" would be turned into "viewAction"</p>
-
-<pre>
-class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
-{
-    public function viewAction()
-    {
-        //main entry point
-    }
-}
-</pre>
-
-<p>People familiar with the Zend Framework will recognize the naming convention here.</p>
-
-<h4>Parameter/Value - <tt>id/25</tt></h4>
-
-<p>Any path portions after the action name will be considered key/value GET request variables.  So, in our example, the "id/25" means there will get a GET variable named "id", with a value of "25".</p>
-
-<p>As previously mentioned, if you want your Module to use Controllers, you'll need to configure them.  Below is the configuration chunk that enables Controllers for the Catalog Module</p>
-
-<pre>
-&lt;frontend>
-    &lt;routers>
-        &lt;catalog>
-            &lt;use>standard&lt;/use>
-            &lt;args>
-                &lt;module&gt;Mage_Catalog&lt;/module&gt;
-                &lt;frontName>catalog&lt;/frontName>
-            &lt;/args>
-        &lt;/catalog>
-    &lt;/routers>
-&lt;/frontend>
-</pre>
-
-<p>Don't worry too much about the specifics right now, but notice the</p>
-
-<tt>&lt;frontName&gt;catalog&lt;/frontName&gt;
-</tt>
-
-<p>This is what links a Module with a URL frontname.  Most Magento core Modules choose a frontname that is the same as their Module name, but this is not required.  </p>
-
-
-<h3>Multiple Routers</h3>
-
-<p>The routing described above is for the Magento cart application (often called the frontend).  If Magento doesn't find a valid Controller/Action for a URL, it tries again, this time using a second set of Routing rules for the Admin application.  If Magento doesn't find a valid <strong>Admin</strong> Controller/Action, it uses a special Controller named <tt>Mage_Cms_IndexController</tt>.</p>
-
-<p>The CMS Controller checks Magento's content Management system to see if there's any content that should be loaded.  If it finds some, it loads it, otherwise the user will be presented with a 404 page.  </p>
-
-<p>For example, the main magento "index" page is one that uses the CMS Controller, which can often throw newcomers for a loop.</p>
-
-<a name="4"></a>
-<h2>Context-Based URI Model Loading</h2>
-
-<p>Now that we're in our Action method entry point, we'll want to start instantiating classes that do things.  Magento offers a special way to instantiate Models, Helpers and Blocks using static factory methods on the global Mage class. For example:</p>
-
-<pre>
-Mage::getModel('catalog/product');
-Mage::helper('catalog/product');
-</pre>
-
-<p>The string 'catalog/product' is called a Grouped Class Name.  It's also often called a URI.  The first portion of any Grouped Class Name (in this case, catalog), is used to lookup which Module the class resides in.  The second portion ('product' above) is used to determine which class should be loaded.</p>
-
-<p>So, in both of the examples above, 'catalog' resolves to the Module <tt>app/code/core/Mage/Catalog</tt>.</p>
-
-<p>Meaning our class name will start with <tt>Mage_Catalog</tt>.</p>
-
-<p>Then, product is added to get the final class name</p>
-
-<pre>
-Mage::getModel('catalog/product');
-Mage_Catalog_Model_Product
-
-Mage::helper('catalog/product');
-Mage_Catalog_Helper_Product
-</pre>
-
-<p>These rules are bound by what's been setup in each Module's config file.  When you create your own custom Module, you'll have your own grouped classnames (also calles classgroups) to work with <tt>Mage::getModel('myspecialprefix/modelname');</tt>.</p>
-
-<p>You don't <strong>have</strong> to use Grouped Class Names to instantiate your classes.  However, as we'll learn later, there are certain advantages to doing so.</p>
-
-
-<a name="5"></a>
-<h2>Magento Models</h2>
-
-<p>Magento, like most frameworks these days, offers an Object Relational Mapping (ORM) system. ORMs get you out of the business of writing SQL and allow you to manipulate a datastore purely through PHP code. For example:</p>
-
-<pre>
-$model = Mage::getModel('catalog/product')-&gt;load(27);
-$price = $model-&gt;getPrice();
-$price += 5;
-$model-&gt;setPrice($price)-&gt;setSku('SK83293432');
-$model-&gt;save();
-</pre>
-
-<p>In the above example we're calling the methods "getPrice" and "setPrice" on our Product.  However, the Mage_Catalog_Model_Product class has no methods with these names. That's because Magento's ORM uses PHP's magic <em>__call</em> method to implement getters and setters.</p>
-
-<p>Calling the method <tt>$product-&gt;getPrice();</tt> will "get" the Model attribute "price".</p>
-
-<p>Calling <tt>$product-&gt;setPrice();</tt> will "set" the Model attribute "price".  All of this assumes the Model class doesn't already have methods named getPrice or setPrice.  If it does, the magic methods will be bypassed.  If you're interested in the implementation of this, checkout the Varien_Object class, which all Models inherit from.</p>
-
-<p>If you wanted to get all the available data on a Model, call <tt>$product-&gt;getData();</tt> to get an array of all the attributes.</p>
-
-<p>You'll also notice it's possible to chain together several calls to the  set method: </p>
-<tt>$model-&gt;setPrice($price)-&gt;setSku('SK83293432');</tt>
-
-<p>That's because each set method returns an instance of the Model.  This is a pattern you'll see used in much of the Magento codebase.</p>
-
-<p>Magento's ORM also contains a way to query for multiple Objects via a Collections interface.  The following would get us a collection of all products that cost $5.00</p>
-
-<pre>
-$products_collection = Mage::getModel('catalog/product')
-->getCollection()
-->addAttributeToSelect('*')
-->addFieldToFilter('price','5.00');
-</pre>
-
-<p>Again, you'll notice Magento's implemented a chaining interface here.  Collections use the PHP Standard Library to implement Objects that have array like properties.</p>
-
-<pre>
-foreach($products_collection as $product)
-{
-    echo $product-&gt;getName();
-}
-</pre>
-
-<p>You may be wondering what the "addAttributeToSelect" method is for. Magento has two broad types of Model objects. One is a traditional "One Object, One Table" Active Record style Model.  When you instantiate these Models, all attributes are automatically selected.</p>
-
-<p>The second type of Model is an Entity Attribute Value (EAV) Model.  EAV Models spread data across several different tables in the database.  This gives the Magento system the flexibility to offer its flexible product attribute system without having to do a schema change each time you add an attribute.  When creating a collection of EAV objects, Magento is conservative in the number of columns it will query for, so you can use addAttributeToSelect to get the columns you want, or addAttributeToSelect('*') to get all columns. </p>
-
-<a name="6"></a>
-<h2>Helpers</h2>
-
-<p>Magento's Helper classes contain utility methods that will allow you to perform common tasks on objects and variables. For example:</p>>
-<tt>$helper = Mage::helper('catalog');</tt>
-
-<p>You'll notice we've left off the second part of the grouped class name.  Each Module has a default Data Helper class.  The following is equivalent to the above:</p>
-<tt>$helper = Mage::helper('catalog/data');</tt>
-
-<p>Most Helpers inherit form Mage_Core_Helper_Abstract, which gives you several useful methods by default.</p>
-<pre>
-$translated_output =  $helper-&gt;__('Magento is Great'); //gettext style translations
-if($helper-&gt;isModuleOutputEnabled()): //is output for this module on or off?
-</pre>
-
-
-<a name="7"></a>
-<h2>Layouts</h2>
-
-<p>So, we've seen Controllers, Models, and Helpers.  In a typical PHP MVC system, after we've manipulated our Models we would </p>
-
-<ol>
-<li>Set some variables for our view</li>
-<li>The system would load a default "outer" HTML layout></li>
-<li>The system would then load our view inside that outer layout</li>
-</ol>
-
-<p>However, if you look at a typical Magento Controller action, you don't see any of this:</p>
-
-<pre>
-/**
- * View product gallery action
- */
-public function galleryAction()
-{
-    if (!$this-&gt;_initProduct()) {
-        if (isset($_GET['store']) && !$this-&gt;getResponse()-&gt;isRedirect()) {
-            $this-&gt;_redirect('');
-        } elseif (!$this-&gt;getResponse()-&gt;isRedirect()) {
-            $this-&gt;_forward('noRoute');
-        }
-        return;
-    }
-    $this-&gt;loadLayout();
-    $this-&gt;renderLayout();
-}
-</pre>
-
-<p>Instead, the Controller action ends with two calls</p>
-
-<pre>
-$this-&gt;loadLayout();
-$this-&gt;renderLayout();
-</pre>
-
-<p>So, the "V" in Magento's MVC already differs from what you're probably used to, in that you need to explicitly kick off rendering the layout.</p>
-
-<p>The layout itself also differs.  A Magento Layout is an object that contains a nested/tree collection of "Block" objects. Each Block object will render a specific bit of HTML.  Block objects do this through a combination of PHP code, and including PHP .phtml template files.</p>
-
-<p>Blocks objects are meant to interact with the Magento system to retrieve data from Models, while the phtml template files will produce the HTML needed for a page.</p>
-
-<p>For example, the page header Block <tt>app/code/core/Mage/Page/Block/Html/Head.php</tt> uses the head.phtml file <tt>page/html/head.phtml</tt>.</p>
-
-<p>Another way of thinking about it is the Block classes are almost like little mini-controllers, and the .phtml files are the view.</p>
-
-<p>By default, when you call</p>
-
-<pre>
-$this->loadLayout();
-$this->renderLayout();
-</pre>
-
-<p>Magento will load up a Layout with a skeleton site structure.  There will be Structure Blocks to give you your <tt>html</tt>, <tt>head</tt>, and <tt>body</tt>, as well as HTML to setup single or multiple columns of Layout. Additionally, there will be a few Content Blocks for the navigation, default welcome message, etc.</p>
-
-<p>"Structure" and "Content" are arbitrary designations in the Layout system.  A Block doesn't programmatically know if it's Structure or Content, but it's useful to think of a Block as one or the other.</p>
-
-<p>To add Content to this Layout you need to tell the Magento system something like</p>
-
-<pre>"Hey, Magento, add these additional Blocks under the "content" Block of the skeleton"</pre>
-
-or
-
-<pre>"Hey, Magento, add these additional Blocks under the "left column" Block of the skeleton"</pre>
-
-<p>This can be done programmatically in a Controller action</p>
-
-<pre>
-public function indexAction()
-{
-    $this-&gt;loadLayout();
-    $block = $this-&gt;getLayout()-&gt;createBlock('adminhtml/system_account_edit')
-    $this-&gt;getLayout()-&gt;getBlock('content')-&gt;append($block);
-    $this-&gt;renderLayout();
-}
-</pre>
-
-<p>but more commonly (at least in the frontend cart application), is use of the XML Layout system.</p>
-
-<p>The Layout XML files in a theme allow you, on a per Controller basis, to remove Blocks that would normally be rendered, or add Blocks to that default skeleton areas. For example, consider this Layout XML file: </p>
-
-<pre>
-&lt;catalog_category_default>
-    &lt;reference name="left">
-        &lt;block type="catalog/navigation" name="catalog.leftnav" after="currency" template="catalog/navigation/left.phtml"/>
-    &lt;/reference>
-&lt;/catalog_category_default>
-</pre>
-
-<p>It's saying in the catalog Module, in the category Controller, and the default Action, insert the catalog/navigation Block into the "left" structure Block, using the catalog/navigation/left.phtml template.</p>
-
-<p>One last important thing about Blocks.  You'll often see code in templates that looks like this:</p>
-<tt>$this-&gt;getChildHtml('order_items')</tt>
-
-<p>This is how a Block renders a nested Block.  However, a Block can only render a child Block if the child Block <strong>is included as a nested Block in the Layout XML file</strong>.  In the example above our catalog/navigation Block has no nested Blocks.  This means any call to $this->getChildHtml() in left.phtml will render as blank.</p>
-
-<p>If, however, we had something like:</p>
-<pre>
-&lt;catalog_category_default>
-    &lt;reference name="left">
-        &lt;block type="catalog/navigation" name="catalog.leftnav" after="currency" template="catalog/navigation/left.phtml">
-            &lt;block type="core/template" name="foobar" template="foo/baz/bar.phtml"/>
-        &lt;/block>
-    &lt;/reference>
-&lt;/catalog_category_default>
-</pre>
-
-<p>From the catalog/navigation Block, we'd be able to call </p>
-<tt>$this-&gt;getChildHtml('foobar');</tt><br/>
-
-
-<a name="8"></a>
-<h2>Observers</h2>
-
-<p>Like any good object-oriented system, Magento implements an Event/Observer pattern for end users to hook into.  As certain actions happen during a Page request (a Model is saved, a user logs in, etc.), Magento will issue an event signal. </p>
-
-<p>When creating your own Modules, you can "listen" for these events.  Say you wanted to get an email every time a certain customer logged into the store.  You could listen for the "customer_login" event (setup in config.xml)</p>
-
-<pre>
-&lt;events>
-    &lt;customer_login>
-        &lt;observers>
-            &lt;unique_name>
-                &lt;type>singleton&lt;/type>
-                &lt;class>mymodule/observer&lt;/class>
-                &lt;method>iSpyWithMyLittleEye&lt;/method>
-            &lt;/unique_name>
-        &lt;/observers>
-    &lt;/customer_login>
-&lt;/events>
-</pre>
-
-<p>and then write some code that would run whenever a user logged in:</p>
-
-<pre>
-class Packagename_Mymodule_Model_Observer
-{
-    public function iSpyWithMyLittleEye($observer)
-    {
-        $data = $observer-&gt;getData();
-        //code to check observer data for our user,
-        //and take some action goes here
-    }
-}
-</pre>
-
-<a name="9"></a>
-<h2>Class Overrides</h2>
-
-<p>Finally, the Magento System offers you the ability to replace Model, Helper and Block classes from the core modules with your own.  This is a feature that's similar to "Duck Typing" or "Monkey Patching" in a language like Ruby or Python.</p>
-
-<p>Here's an example to help you understand.  The Model class for a product is <tt>Mage_Catalog_Model_Product</tt>.</p>
-
-<p>Whenever the following code is called, a Mage_Catalog_Model_Product object is created</p>
-
-<pre>$product = Mage::getModel('catalog/product');</pre>
-
-<p>This is a factory pattern.  </p>
-
-<p>What Magento's class override system does is allow you to tell the system</p>
-
-<pre>"Hey, whenever anyone asks for a catalog/product, instead of giving them a Mage_Catalog_Model_Product,
-give them a Packagename_Modulename_Model_Foobazproduct instead".</pre>
-
-<p>Then, if you want, your Packagename_Modulename_Model_Foobazproduct class can extend the original product class</p>
-
-<pre>
-class Packagename_Modulename_Model_Foobazproduct extends Mage_Catalog_Model_Product
-{
-}
-</pre>
-
-<p>Which will allow you to change the behavior of any method on the class, but keep the functionality of the existing methods.</p>
-
-<pre>class Packagename_Modulename_Model_Foobazproduct extends Mage_Catalog_Model_Product
-{
-    public function validate()
-    {
-        //add custom validation functionality here
-        return $this;
-    }
-
-}
-</pre>
-
-<p>As you might expect, this overriding (or rewriting) is done in the config.xml file.</p>
-
-<pre>
-&lt;models>
-    &lt;!-- does the override for catalog/product-->
-    &lt;catalog>
-        &lt;rewrite>
-            &lt;product>Packagename_Modulename_Model_Foobazproduct&lt;/product>
-        &lt;/rewrite>
-    &lt;/catalog>
-&lt;/models>
-</pre>
-
-<p>One thing that's important to note here. Individual classes in <strong>your</strong> Module are overriding individual classes in <strong>other</strong> Modules.  You are not, however, overriding the entire Module.  This allows you to change specific method behavior without having to worry what the rest of the Module is doing.</p>
-
-
-<a name="10"></a>
-<h2>Wrap Up</h2>
-
-<p>We hope you've enjoyed this whirlwind tour of some of the features the Magento eCommerce system offers to developers.  It can be a little overwhelming at first, especially if this is your first experience with a modern, object-oriented PHP system. If you start to get frustrated, take a deep breath, remind yourself that this is new, and new things are hard, but at the end of the day it's just a different way of coding.  Once you get over the learning curve you'll find yourself loath to return to other, less powerful systems.</p>
-
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="active " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
+                                    Introduction to OpenMage
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
+                                    The OpenMage Config
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
+                                    OpenMage Controller Dispatch
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
+                                    OpenMage Layouts, Blocks and Templates
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
+                                    OpenMage Models and ORM Basics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
+                                    OpenMage Setup Resources
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">
+                                    Advanced ORM: Entity Attribute Value
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-8.html">
+                                    Varien Data Collections
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Introduction to OpenMage</h1>
+                    </section>
+                    <p class="para1">What is OpenMage? It's the most powerful online eCommerce platform in the universe
+                        and is changing the face of eCommerce forever. :-)
+                    </p>
+                    <p>Of course, you already know that. What you may not realize is Magento's also an object-oriented
+                        PHP Framework that can be used to develop modern, dynamic web applications that tap into
+                        Magento's powerful eCommerce features.
+                    </p>
+                    <p>This is the first in a series of articles in which we're going to go on a whirlwind tour of
+                        Magento's programming framework features. Don't worry if you don't follow everything
+                        immediately. As you study the system more everything in this article will start to make sense,
+                        and you'll soon be the envy of your colleagues stuck working with more primitive PHP
+                        systems.
+                    </p>
+                    <p>Or for the more visually oriented
+                        <a href="{{ site.baseurl }}{{ site.v1xgdeurl }}images/Magento_MVC.pdf">Magento_MVC.pdf</a>.
+                    </p>
+                    <hr/>
+                    <a name="1"></a>
+                    <h2>Code Organized in Modules</h2>
+                    <p>Magento organizes its code into individual Modules. In a typical PHP
+                        <a href="http://en.wikipedia.org/wiki/Model–view–controller" target="_new">
+                            <b>Model-View-Controller (MVC)</b>
+                        </a>
+                        application, all the Controllers will be in one folder, all the Models in another,
+                        etc. In Magento, files are grouped together based on functionality, which are called
+                        <b>modules</b> in Magento.
+                    </p>
+                    <h4>Magento's Code</h4>
+                    <p>For example, you'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's checkout
+                        functionality in
+                    </p>
+                    <pre>app/code/core/Mage/Checkout</pre>
+                    <p>You'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's Google Checkout
+                        functionality in
+                    </p>
+                    <pre>app/code/core/Mage/GoogleCheckout</pre>
+                    <h4>Your Code</h4>
+                    <p>When you want to customize or extend Magento, rather than editing core files directly, or even
+                        placing your new Controllers, Models, Helpers, Blocks, etc. next to Magento code, you'll create
+                        your own Modules in
+                    </p>
+                    <pre>app/code/local/Package/Modulename</pre>
+                    <p><b>Package</b> (also often referred to as a <b>Namespace</b>) is a unique name that identifies
+                        your company or organization. The intent is that each member of the world-wide Magento community
+                        will use their own Package name when creating modules in order to avoid colliding with another
+                        user's code. </p>
+                    <p>When you create a new Module, you need to tell Magento about it. This is done by adding an XML
+                        file to the folder:</p>
+                    <pre>app/etc/modules</pre>
+                    <p>There are two kinds of files in this folder, the first enables an individual Module, and is named
+                        in the form:</p>
+                    <tt>Packagename_Modulename.xml</tt>
+                    <p>The second is a file that will enable multiple Modules from a Package/Namespace, and is named in
+                        the form:</p>
+                    <tt>Packagename_All.xml</tt>. Note it is only used by the core team with the file
+                    <tt>Mage_All.xml</tt>. It is <b>not recommended</b> to activate several modules in a single file, as
+                    this breaks the modularity of your modules.
+                    <a name="2"></a>
+                    <h2>Configuration-Based MVC</h2>
+                    <p>Magento is a <b>configuration-based</b> MVC system. The alternative to this would a <b>convention-based</b>
+                        MVC system.</p>
+                    <p>In a convention-based MVC system, if you wanted to add, say, a new Controller or maybe a new
+                        Model, you'd just create the file/class, and the system would pick it up automatically.</p>
+                    <p>In a configuration-based system, like Magento, in addition to adding the new file/class to the
+                        codebase, you often need to explicitly tell the system about the new class, or new group of
+                        classes. In Magento, each Module has a file named <tt>config.xml</tt>. This file contains all
+                        the relevant configuration for a Magento Module. At runtime, all these files are loaded into one
+                        large configuration tree.</p>
+                    <p>For example, want to use Models in your custom Module? You'll need to add some code to <tt>config.xml</tt>
+                        that tells Magento you want to use Models, as well as what the base class name for all your
+                        Models should be.</p>
+                    <pre>
+                    &lt;models>
+                             &lt;packagename>
+                                  &lt;class>Packagename_Modulename_Model&lt;/class>
+                            &lt;/packagename>
+                    &lt;/models>
+                    </pre>
+                    <p>The same goes for Helpers, Blocks, Routes for your Controllers, Event Handlers, and more. Almost
+                        anytime you want to tap into the power of the Magento system, you'll need to make some change or
+                        addition to your config file.</p>
+                    <a name="3"></a>
+                    <h2>Controllers</h2>
+                    <p>In any PHP system, the main PHP entry point remains a PHP file. Magento is no different, and that
+                        file is <tt>index.php</tt>.</p>
+                    <p>However, you never CODE in index.php. In an MVC system, index.php will contain code/calls to code
+                        that does the following:</p>
+                    <ol>
+                        <li><p>Examines the URL</p></li>
+                        <li><p>Based on some set of rules, turns this URL into a Controller class and an Action method
+                            (called Routing)</p></li>
+                        <li><p>Instantiates the Controller class and calls the Action method (called dispatching)</p>
+                        </li>
+                    </ol>
+                    <p>This means the <strong>practical</strong> entry point in Magento (or any MVC-based system) is a
+                        method in a Controller file. Consider the following URL:</p>
+                    <pre>http://example.com/catalog/category/view/id/25</pre>
+                    <p>Each portion of the path after the server name is parsed as follows.</p>
+                    <h4>Front Name - <tt>catalog</tt></h4>
+                    <p>The first portion of the URL is called the front name. This, more or less, tells magento which
+                        Module it can find a Controller in. In the above example, the front name is <em>catalog</em>,
+                        which corresponds to the Module located at:</p>
+                    <pre>app/code/core/Mage/Catalog</pre>
+                    <h4>Controller Name - <tt>category</tt></h4>
+                    <p>The second portion of the URL tells Magento which Controller it should use. Each Module with
+                        Controllers has a special folder named 'controllers' which contains all the Controllers for a
+                        module. In the above example, the URL portion category is translated into the Controller
+                        file</p>
+                    <pre>app/code/core/Mage/Catalog/controllers/CategoryController.php</pre>
+                    <p>Which looks like</p>
+                    <pre>
+                        class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
+                        {
+                        }
+                    </pre>
+                    <p>All Controllers in the Magento cart application extend from
+                        Mage_Core_Controller_Front_Action.</p>
+                    <h4>Action Name - <tt>view</tt></h4>
+                    <p>Third in our URL is the action name. In our example, this is "view". The word "view" is used to
+                        create the Action Method. So, in our example, "view" would be turned into "viewAction"</p>
+                    <pre>
+                        class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
+                        {
+                            public function viewAction()
+                            {
+                                //main entry point
+                            }
+                        }
+                    </pre>
+                    <p>People familiar with the Zend Framework will recognize the naming convention here.</p>
+                    <h4>Parameter/Value - <tt>id/25</tt></h4>
+                    <p>Any path portions after the action name will be considered key/value GET request variables. So,
+                        in our example, the "id/25" means there will get a GET variable named "id", with a value of
+                        "25".</p>
+                    <p>As previously mentioned, if you want your Module to use Controllers, you'll need to configure
+                        them. Below is the configuration chunk that enables Controllers for the Catalog Module</p>
+                    <pre>
+                        &lt;frontend>
+                            &lt;routers>
+                                &lt;catalog>
+                                    &lt;use>standard&lt;/use>
+                                    &lt;args>
+                                        &lt;module&gt;Mage_Catalog&lt;/module&gt;
+                                        &lt;frontName>catalog&lt;/frontName>
+                                    &lt;/args>
+                                &lt;/catalog>
+                            &lt;/routers>
+                        &lt;/frontend>
+                    </pre>
+                    <p>Don't worry too much about the specifics right now, but notice the</p>
+                    <tt>&lt;frontName&gt;catalog&lt;/frontName&gt;
+                    </tt>
+                    <p>This is what links a Module with a URL frontname. Most Magento core Modules choose a frontname
+                        that is the same as their Module name, but this is not required. </p>
+                    <h3>Multiple Routers</h3>
+
+                    <p>The routing described above is for the Magento cart application (often called the frontend). If
+                        Magento doesn't find a valid Controller/Action for a URL, it tries again, this time using a
+                        second set of Routing rules for the Admin application. If Magento doesn't find a valid <strong>Admin</strong>
+                        Controller/Action, it uses a special Controller named <tt>Mage_Cms_IndexController</tt>.</p>
+
+                    <p>The CMS Controller checks Magento's content Management system to see if there's any content that
+                        should be loaded. If it finds some, it loads it, otherwise the user will be presented with a 404
+                        page. </p>
+
+                    <p>For example, the main magento "index" page is one that uses the CMS Controller, which can often
+                        throw newcomers for a loop.</p>
+
+                    <a name="4"></a>
+                    <h2>Context-Based URI Model Loading</h2>
+
+                    <p>Now that we're in our Action method entry point, we'll want to start instantiating classes that
+                        do things. Magento offers a special way to instantiate Models, Helpers and Blocks using static
+                        factory methods on the global Mage class. For example:
+                    </p>
+                    <pre>
+                        Mage::getModel('catalog/product');
+                        Mage::helper('catalog/product');
+                    </pre>
+                    <p>The string 'catalog/product' is called a Grouped Class Name. It's also often called a URI. The
+                        first portion of any Grouped Class Name (in this case, catalog), is used to lookup which Module
+                        the class resides in. The second portion ('product' above) is used to determine which class
+                        should be loaded.
+                    </p>
+                    <p>So, in both of the examples above, 'catalog' resolves to the Module
+                        <tt>app/code/core/Mage/Catalog</tt>.
+                    </p>
+                    <p>Meaning our class name will start with <tt>Mage_Catalog</tt>.</p>
+                    <p>Then, product is added to get the final class name</p>
+                    <pre>
+                        Mage::getModel('catalog/product');
+                        Mage_Catalog_Model_Product
+
+                        Mage::helper('catalog/product');
+                        Mage_Catalog_Helper_Product
+                    </pre>
+                    <p>These rules are bound by what's been setup in each Module's config file. When you create your own
+                        custom Module, you'll have your own grouped classnames (also calles classgroups) to work with
+                        <tt>Mage::getModel('myspecialprefix/modelname');</tt>.
+                    </p>
+                    <p>You don't <strong>have</strong> to use Grouped Class Names to instantiate your classes. However,
+                        as we'll learn later, there are certain advantages to doing so.
+                    </p>
+                    <a name="5"></a>
+                    <h2>Magento Models</h2>
+                    <p>Magento, like most frameworks these days, offers an Object Relational Mapping (ORM) system. ORMs
+                        get you out of the business of writing SQL and allow you to manipulate a datastore purely
+                        through PHP code. For example:
+                    </p>
+                    <pre>
+                        $model = Mage::getModel('catalog/product')-&gt;load(27);
+                        $price = $model-&gt;getPrice();
+                        $price += 5;
+                        $model-&gt;setPrice($price)-&gt;setSku('SK83293432');
+                        $model-&gt;save();
+                    </pre>
+                    <p>In the above example we're calling the methods "getPrice" and "setPrice" on our Product. However,
+                        the Mage_Catalog_Model_Product class has no methods with these names. That's because Magento's
+                        ORM uses PHP's magic <em>__call</em> method to implement getters and setters.
+                    </p>
+                    <p>Calling the method <tt>$product-&gt;getPrice();</tt> will "get" the Model attribute "price".</p>
+                    <p>Calling <tt>$product-&gt;setPrice();</tt> will "set" the Model attribute "price". All of this
+                        assumes the Model class doesn't already have methods named getPrice or setPrice. If it does, the
+                        magic methods will be bypassed. If you're interested in the implementation of this, checkout the
+                        Varien_Object class, which all Models inherit from.
+                    </p>
+                    <p>If you wanted to get all the available data on a Model, call <tt>$product-&gt;getData();</tt> to
+                        get an array of all the attributes.
+                    </p>
+                    <p>You'll also notice it's possible to chain together several calls to the set method: </p>
+                    <tt>$model-&gt;setPrice($price)-&gt;setSku('SK83293432');</tt>
+                    <p>That's because each set method returns an instance of the Model. This is a pattern you'll see
+                        used in much of the Magento codebase.
+                    </p>
+                    <p>Magento's ORM also contains a way to query for multiple Objects via a Collections interface. The
+                        following would get us a collection of all products that cost $5.00
+                    </p>
+                    <pre>
+                        $products_collection = Mage::getModel('catalog/product')
+                        ->getCollection()
+                        ->addAttributeToSelect('*')
+                        ->addFieldToFilter('price','5.00');
+                    </pre>
+                    <p>Again, you'll notice Magento's implemented a chaining interface here. Collections use the PHP
+                        Standard Library to implement Objects that have array like properties.
+                    </p>
+                    <pre>
+                        foreach($products_collection as $product)
+                        {
+                            echo $product-&gt;getName();
+                        }
+                    </pre>
+                    <p>You may be wondering what the "addAttributeToSelect" method is for. Magento has two broad types
+                        of Model objects. One is a traditional "One Object, One Table" Active Record style Model. When
+                        you instantiate these Models, all attributes are automatically selected.
+                    </p>
+                    <p>The second type of Model is an Entity Attribute Value (EAV) Model. EAV Models spread data across
+                        several different tables in the database. This gives the Magento system the flexibility to offer
+                        its flexible product attribute system without having to do a schema change each time you add an
+                        attribute. When creating a collection of EAV objects, Magento is conservative in the number of
+                        columns it will query for, so you can use addAttributeToSelect to get the columns you want, or
+                        addAttributeToSelect('*') to get all columns.
+                    </p>
+                    <a name="6"></a>
+                    <h2>Helpers</h2>
+                    <p>Magento's Helper classes contain utility methods that will allow you to perform common tasks on
+                        objects and variables. For example:</p>
+                    <tt>$helper = Mage::helper('catalog');</tt>
+                    <p>You'll notice we've left off the second part of the grouped class name. Each Module has a default
+                        Data Helper class. The following is equivalent to the above:
+                    </p>
+                    <tt>$helper = Mage::helper('catalog/data');</tt>
+                    <p>Most Helpers inherit form Mage_Core_Helper_Abstract, which gives you several useful methods by
+                        default.
+                    </p>
+                    <pre>
+                        $translated_output =  $helper-&gt;__('Magento is Great'); //gettext style translations
+                        if($helper-&gt;isModuleOutputEnabled()): //is output for this module on or off?
+                    </pre>
+                    <a name="7"></a>
+                    <h2>Layouts</h2>
+                    <p>So, we've seen Controllers, Models, and Helpers. In a typical PHP MVC system, after we've
+                        manipulated our Models we would
+                    </p>
+                    <ol>
+                        <li>Set some variables for our view</li>
+                        <li>The system would load a default "outer" HTML layout></li>
+                        <li>The system would then load our view inside that outer layout</li>
+                    </ol>
+                    <p>However, if you look at a typical Magento Controller action, you don't see any of this:</p>
+                    <pre>
+                        /**
+                         * View product gallery action
+                         */
+                        public function galleryAction()
+                        {
+                            if (!$this-&gt;_initProduct()) {
+                                if (isset($_GET['store']) && !$this-&gt;getResponse()-&gt;isRedirect()) {
+                                    $this-&gt;_redirect('');
+                                } elseif (!$this-&gt;getResponse()-&gt;isRedirect()) {
+                                    $this-&gt;_forward('noRoute');
+                                }
+                                return;
+                            }
+                            $this-&gt;loadLayout();
+                            $this-&gt;renderLayout();
+                        }
+                    </pre>
+                    <p>Instead, the Controller action ends with two calls</p>
+                    <pre>
+                        $this-&gt;loadLayout();
+                        $this-&gt;renderLayout();
+                    </pre>
+                    <p>So, the "V" in Magento's MVC already differs from what you're probably used to, in that you need
+                        to explicitly kick off rendering the layout.
+                    </p>
+                    <p>The layout itself also differs. A Magento Layout is an object that contains a nested/tree
+                        collection of "Block" objects. Each Block object will render a specific bit of HTML. Block
+                        objects do this through a combination of PHP code, and including PHP .phtml template files.
+                    </p>
+                    <p>Blocks objects are meant to interact with the Magento system to retrieve data from Models, while
+                        the phtml template files will produce the HTML needed for a page.
+                    </p>
+                    <p>For example, the page header Block <tt>app/code/core/Mage/Page/Block/Html/Head.php</tt> uses the
+                        head.phtml file
+                        <tt>page/html/head.phtml</tt>.
+                    </p>
+                    <p>Another way of thinking about it is the Block classes are almost like little mini-controllers,
+                        and the .phtml files are the view.
+                    </p>
+                    <p>By default, when you call</p>
+                    <pre>
+                        $this->loadLayout();
+                        $this->renderLayout();
+                    </pre>
+                    <p>Magento will load up a Layout with a skeleton site structure. There will be Structure Blocks to
+                        give you your <tt>html</tt>, <tt>head</tt>, and <tt>body</tt>, as well as HTML to setup single
+                        or multiple columns of Layout. Additionally, there will be a few Content Blocks for the
+                        navigation, default welcome message, etc.
+                    </p>
+                    <p>"Structure" and "Content" are arbitrary designations in the Layout system. A Block doesn't
+                        programmatically know if it's Structure or Content, but it's useful to think of a Block as one
+                        or the other.
+                    </p>
+                    <p>To add Content to this Layout you need to tell the Magento system something like</p>
+                    <pre>"Hey, Magento, add these additional Blocks under the "content" Block of the skeleton"</pre>
+                    or
+                    <pre>"Hey, Magento, add these additional Blocks under the "left column" Block of the skeleton"</pre>
+                    <p>This can be done programmatically in a Controller action</p>
+                    <pre>
+                        public function indexAction()
+                        {
+                            $this-&gt;loadLayout();
+                            $block = $this-&gt;getLayout()-&gt;createBlock('adminhtml/system_account_edit')
+                            $this-&gt;getLayout()-&gt;getBlock('content')-&gt;append($block);
+                            $this-&gt;renderLayout();
+                        }
+                    </pre>
+                    <p>but more commonly (at least in the frontend cart application), is use of the XML Layout system.</p>
+                    <p>The Layout XML files in a theme allow you, on a per Controller basis, to remove Blocks that would
+                        normally be rendered, or add Blocks to that default skeleton areas. For example, consider this
+                        Layout XML file:
+                    </p>
+                    <pre>
+                        &lt;catalog_category_default>
+                            &lt;reference name="left">
+                                &lt;block type="catalog/navigation" name="catalog.leftnav" after="currency" template="catalog/navigation/left.phtml"/>
+                            &lt;/reference>
+                        &lt;/catalog_category_default>
+                    </pre>
+                    <p>It's saying in the catalog Module, in the category Controller, and the default Action, insert the
+                        catalog/navigation Block into the "left" structure Block, using the
+                        catalog/navigation/left.phtml template.
+                    </p>
+                    <p>One last important thing about Blocks. You'll often see code in templates that looks like this:</p>
+                    <tt>$this-&gt;getChildHtml('order_items')</tt>
+                    <p>This is how a Block renders a nested Block. However, a Block can only render a child Block if the
+                        child Block <strong>is included as a nested Block in the Layout XML file</strong>. In the
+                        example above our catalog/navigation Block has no nested Blocks. This means any call to
+                        $this->getChildHtml() in left.phtml will render as blank.
+                    </p>
+                    <p>If, however, we had something like:</p>
+                    <pre>
+                        &lt;catalog_category_default>
+                            &lt;reference name="left">
+                                &lt;block type="catalog/navigation" name="catalog.leftnav" after="currency" template="catalog/navigation/left.phtml">
+                                    &lt;block type="core/template" name="foobar" template="foo/baz/bar.phtml"/>
+                                &lt;/block>
+                            &lt;/reference>
+                        &lt;/catalog_category_default>
+                    </pre>
+                    <p>From the catalog/navigation Block, we'd be able to call </p>
+                    <tt>$this-&gt;getChildHtml('foobar');</tt>
+                    <br/>
+                    <a name="8"></a>
+                    <h2>Observers</h2>
+                    <p>Like any good object-oriented system, Magento implements an Event/Observer pattern for end users
+                        to hook into. As certain actions happen during a Page request (a Model is saved, a user logs in,
+                        etc.), Magento will issue an event signal.
+                    </p>
+                    <p>When creating your own Modules, you can "listen" for these events. Say you wanted to get an email
+                        every time a certain customer logged into the store. You could listen for the "customer_login"
+                        event (setup in config.xml)
+                    </p>
+                    <pre>
+                        &lt;events>
+                            &lt;customer_login>
+                                &lt;observers>
+                                    &lt;unique_name>
+                                        &lt;type>singleton&lt;/type>
+                                        &lt;class>mymodule/observer&lt;/class>
+                                        &lt;method>iSpyWithMyLittleEye&lt;/method>
+                                    &lt;/unique_name>
+                                &lt;/observers>
+                            &lt;/customer_login>
+                        &lt;/events>
+                    </pre>
+                    <p>and then write some code that would run whenever a user logged in:</p>
+                    <pre>
+                        class Packagename_Mymodule_Model_Observer
+                        {
+                            public function iSpyWithMyLittleEye($observer)
+                            {
+                                $data = $observer-&gt;getData();
+                                //code to check observer data for our user,
+                                //and take some action goes here
+                            }
+                        }
+                    </pre>
+                    <a name="9"></a>
+                    <h2>Class Overrides</h2>
+                    <p>Finally, the Magento System offers you the ability to replace Model, Helper and Block classes
+                        from the core modules with your own. This is a feature that's similar to "Duck Typing" or
+                        "Monkey Patching" in a language like Ruby or Python.
+                    </p>
+                    <p>Here's an example to help you understand. The Model class for a product is
+                        <tt>Mage_Catalog_Model_Product</tt>.
+                    </p>
+                    <p>Whenever the following code is called, a Mage_Catalog_Model_Product object is created</p>
+                    <pre>$product = Mage::getModel('catalog/product');</pre>
+                    <p>This is a factory pattern. </p>
+                    <p>What Magento's class override system does is allow you to tell the system</p>
+                    <pre>"Hey, whenever anyone asks for a catalog/product, instead of giving them a Mage_Catalog_Model_Product,
+                        give them a Packagename_Modulename_Model_Foobazproduct instead".
+                    </pre>
+                    <p>Then, if you want, your Packagename_Modulename_Model_Foobazproduct class can extend the original
+                        product class</p>
+                    <pre>
+                        class Packagename_Modulename_Model_Foobazproduct extends Mage_Catalog_Model_Product
+                        {
+                        }
+                    </pre>
+                    <p>Which will allow you to change the behavior of any method on the class, but keep the
+                        functionality of the existing methods.</p>
+                    <pre>class Packagename_Modulename_Model_Foobazproduct extends Mage_Catalog_Model_Product
+                        {
+                            public function validate()
+                            {
+                                //add custom validation functionality here
+                                return $this;
+                            }
+                        }
+                    </pre>
+                    <p>As you might expect, this overriding (or rewriting) is done in the config.xml file.</p>
+                    <pre>
+                        &lt;models>
+                            &lt;!-- does the override for catalog/product-->
+                            &lt;catalog>
+                                &lt;rewrite>
+                                    &lt;product>Packagename_Modulename_Model_Foobazproduct&lt;/product>
+                                &lt;/rewrite>
+                            &lt;/catalog>
+                        &lt;/models>
+                    </pre>
+                    <p>One thing that's important to note here. Individual classes in <strong>your</strong> Module are
+                        overriding individual classes in <strong>other</strong> Modules. You are not, however,
+                        overriding the entire Module. This allows you to change specific method behavior without having
+                        to worry what the rest of the Module is doing.
+                    </p>
+                    <a name="10"></a>
+                    <h2>Wrap Up</h2>
+                    <p>We hope you've enjoyed this whirlwind tour of some of the features the Magento eCommerce system
+                        offers to developers. It can be a little overwhelming at first, especially if this is your first
+                        experience with a modern, object-oriented PHP system. If you start to get frustrated, take a
+                        deep breath, remind yourself that this is new, and new things are hard, but at the end of the
+                        day it's just a different way of coding. Once you get over the learning curve you'll find
+                        yourself loath to return to other, less powerful systems.
+                    </p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
 </div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
 </html>
\ No newline at end of file
diff --git a/guides/m1x/magefordev/mage-for-dev-2.html b/guides/m1x/magefordev/mage-for-dev-2.html
index 3c94eee744..c4c7f0c0ed 100644
--- a/guides/m1x/magefordev/mage-for-dev-2.html
+++ b/guides/m1x/magefordev/mage-for-dev-2.html
@@ -1,237 +1,495 @@
 ---
 ---
 <!DOCTYPE html>
-<html lang=en>
-
+<html lang="en" dir="ltr">
 <head>
-    <meta charset=utf-8>
-
-    <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
-    <link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
-    <link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <title> Magento for Developers: Part 2&mdash;The Magento Config</title>
-
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>OpenMage for Developers: Part 2&mdash;The OpenMage Config</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-
-<img src="{{ site.baseurl }}/guides/m1x/images/m1xheader.png" width="1024" alt="header" />
-{% include m1x/eol_message.html %}
-
-<div id="content">
-<h1> Magento for Developers: Part 2&mdash;The Magento Config</h1>
-<p><em>by Alan Storm</em>, updated for Magento 1.12</p>
-<p><a href="{{ site.m1xgithuburl }}/magefordev/mage-for-dev-2.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>
-<!-- Magento for Developers: Part 2&mdash;The Magento Config -->
-<!-- magento-for-dev-part-2-the-magento-config -->
-
-<!-- <style type="text/css">
-#kb-entry .series {float: right; width: 175px; margin-left: 10px; font-size: 12px; }
-#kb-entry .series ul {margin-left: 15px;}
-</style>
-<div class="r-box-rss series"> -->
-<h5>Other articles in this series:</h5>
-<ul>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-1.html">Part 1&mdash;Introduction to Magento</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-2.html">Part 2&mdash;The Magento Config</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-3.html">Part 3&mdash;Magento Controller Dispatch</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-4.html">Part 4&mdash;Magento Layouts, Blocks and Templates</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">Part 5&mdash;Magento Models and ORM Basics</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Part 6&mdash;Magento Setup Resources</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">Part 7&mdash;Advanced ORM: Entity Attribute Value</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-8.html">Part 8&mdash;Varien Data Collections</a>
-</ul>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
+                                    Introduction to OpenMage
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
+                                    The OpenMage Config
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
+                                    OpenMage Controller Dispatch
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
+                                    OpenMage Layouts, Blocks and Templates
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
+                                    OpenMage Models and ORM Basics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
+                                    OpenMage Setup Resources
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">
+                                    Advanced ORM: Entity Attribute Value
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-8.html">
+                                    Varien Data Collections
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">The OpenMage Config</h1>
+                    </section>
+                    <p class="para1">The config is the beating heart of the Magento System. It describes, in whole,
+                        almost any module, model, class, template, etc. than you'll need to access. It's a level of
+                        abstraction that most PHP developers aren't used to working with, and while it adds development
+                        time in the form of confusion and head scratching, it also allows you an unprecedented amount of
+                        flexibility as far as overriding default system behaviors go. </p>
+                    <p>To start with, we're going to create a Magento module that will let us view the system config in
+                        our web browser. Follow along by copying and pasting the code below, it's worth going through on
+                        your own as a way to start getting comfortable with things you'll be doing while working with
+                        Magento, as well as learning key terminology.</p>
+                    <a name="1"></a>
+                    <h2>Setting up a Module Directory Structure</h2>
+                    <p>We're going to be creating a Magento module. A module is a group of php and xml files meant to
+                        extend the system with new functionality, or override core system behavior. This may meaning
+                        adding additional data models to track sales information, changing the behavior of existing
+                        classes, or adding entirely new features. </p>
+                    <p>It's worth noting that most of the base Magento system is built using the same module system
+                        you'll be using. If you look in </p>
+                    <pre>app/code/core/Mage</pre>
+                    <p>each folder is a separate module built by the Magento team. Together, these modules form the
+                        community shopping cart system you're using. Your modules should be placed in the following
+                        folder</p>
+                    <pre>app/code/local/Packagename</pre>
+                    <p>"Packagename" should be a unique string to Namespace/Package your code. It's an unofficial
+                        convention that this should be the name of your company. The idea is to pick a string that no
+                        one else in the world could possibly be using.</p>
+                    <pre>app/code/local/Microsoft</pre>
+                    <p>We'll use "Magentotutorial".</p>
+                    <p>So, to add a module to your Magento system, create the following directory structure</p>
+                    <pre>app/code/local/Magentotutorial/Configviewer/Block
+                    app/code/local/Magentotutorial/Configviewer/controllers
+                    app/code/local/Magentotutorial/Configviewer/etc
+                    app/code/local/Magentotutorial/Configviewer/Helper
+                    app/code/local/Magentotutorial/Configviewer/Model
+                    app/code/local/Magentotutorial/Configviewer/sql</pre>
+                    <p>You won't need all these folder for every module, but setting them all up now is a smart
+                        idea. </p>
+                    <p>Next, there's two files you'll need to create. The first, config.xml, goes in the etc folder you
+                        just created. </p>
+                    <pre>app/code/local/Magentotutorial/Configviewer/etc/config.xml</pre>
+                    <p>The second file should be created at the following location</p>
+                    <pre>app/etc/modules/Magentotutorial_Configviewer.xml</pre>
+                    <p>The naming convention for this files is Packagename_Modulename.xml.</p>
+                    <p>The config.xml file should contain the following XML. Don't worry too much about what all this
+                        does for now, we'll get there eventually</p>
+                    <pre>
+                    &lt;config>
+                        &lt;modules>
+                            &lt;Magentotutorial_Configviewer>
+                                &lt;version>0.1.0&lt;/version>
+                            &lt;/Magentotutorial_Configviewer>
+                        &lt;/modules>
+                    &lt;/config>
+                    </pre>
+                    <p>Finally, Magentotutorial_Configviewer.xml should contain the following xml.</p>
+                    <pre>
+                    &lt;config>
+                        &lt;modules>
+                            &lt;Magentotutorial_Configviewer>
+                                &lt;active>true&lt;/active>
+                                &lt;codePool>local&lt;/codePool>
+                            &lt;/Magentotutorial_Configviewer>
+                        &lt;/modules>
+                    &lt;/config>
+                    </pre>
+                    <p>That's it. You now have a bare bones module that won't do anything, but that Magento will be
+                        aware of. To make sure you've done everything right, do the following:
+                    <ol>
+                        <li>Clear your Magento cache</li>
+                        <li>In the Magento Admin, go to <strong>System->Configuration->Advanced</strong></li>
+                        <li>In the "Disable modules output" panel verify that Magentotutorial_Configviewer shows up</li>
+                    </ol>
+                    <p>Congratulations, you've built your first Magento module!</p>
+                    <a name="2"></a>
+                    <h2>Creating a Module Config</h2>
+                    <p>Of course, this module doesn't do anything yet. When we're done, our module will
+                    <ol>
+                        <li>Check for the existence of a "showConfig" query string variable</li>
+                        <li>If showConfig is present, display our Magento config and halt normal execution</li>
+                        <li>Check for the existence of an additional query string variable, showConfigFormat that will
+                            let us specify text or xml output.
+                        </li>
+                    </ol>
+                    <p>First, we're going to add the following &lt;global&gt; section to our config.xml file.</p>
+                    <pre>
+                    &lt;config>
+                        &lt;modules>...&lt;/modules>
+                        &lt;global>
+                            &lt;events>
+                                &lt;controller_front_init_routers>
+                                    &lt;observers>
+                                        &lt;Magentotutorial_configviewer_model_observer>
+                                            &lt;type>singleton&lt;/type>
+                                            &lt;class>Magentotutorial_Configviewer_Model_Observer&lt;/class>
+                                            &lt;method>checkForConfigRequest&lt;/method>
+                                        &lt;/Magentotutorial_configviewer_model_observer>
+                                    &lt;/observers>
+                                &lt;/controller_front_init_routers>
+                            &lt;/events>
+                        &lt;/global>
+                    &lt;/config>
+                    </pre>
+                    <p>Then, create a file at </p>
+                    <pre>Magentotutorial/Configviewer/Model/Observer.php</pre>
+                    <p>and place the following code inside</p>
+                    <pre>
+                    &lt;?php
+                        class Magentotutorial_Configviewer_Model_Observer {
+                            const FLAG_SHOW_CONFIG = 'showConfig';
+                            const FLAG_SHOW_CONFIG_FORMAT = 'showConfigFormat';
+
+                            private $request;
+
+                            public function checkForConfigRequest($observer) {
+                                $this-&gt;request = $observer-&gt;getEvent()-&gt;getData('front')-&gt;getRequest();
+                                if($this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG} === 'true'){
+                                    $this-&gt;setHeader();
+                                    $this-&gt;outputConfig();
+                                }
+                            }
+
+                            private function setHeader() {
+                                $format = isset($this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG_FORMAT}) ?
+                                $this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG_FORMAT} : 'xml';
+                                switch($format){
+                                    case 'text':
+                                        header("Content-Type: text/plain");
+                                        break;
+                                    default:
+                                        header("Content-Type: text/xml");
+                                }
+                            }
+
+                            private function outputConfig() {
+                                die(Mage::app()-&gt;getConfig()-&gt;getNode()-&gt;asXML());
+                            }
+                        }
+                    </pre>
+                    <p>That's it. Clear your Magento cache again and then load any Magento URL with a <tt>showConfig=true</tt>
+                        query string</p>
+                    <pre>http://magento.example.com/?showConfig=true</pre>
+                    <a name="3"></a>
+                    <h2>What am I looking at?</h2>
+                    <p>You should be looking at a giant XML file. This describes the state of your Magento system. It
+                        lists all modules, models, classes, event listeners or almost anything else you could think
+                        of.</p>
+                    <p>For example, consider the config.xml file you created above. If you search the XML file in your
+                        browser for the text <tt>Configviewer_Model_Observer</tt> you'll find your class listed. Every
+                        module's config.xml file is parsed by Magento and included in the global config.</p>
+                    <a name="4"></a>
+                    <h2>Why Do I Care?</h2>
+                    <p>Right now this may seem esoteric, but this config is key to understanding Magento. Every module
+                        you'll be creating will add to this config, and anytime you need to access a piece of core
+                        system functionality, Magento will be referring back to the config to look something up. </p>
+                    <p>A quick example: As an MVC developer, you've likely worked with some kind of helper class,
+                        instantiated something like </p>
+                    <pre>
+                    $helper_sales = new HelperSales();
+                    </pre>
+                    <p>One of the things Magento has done is abstract away PHP's class declaration. In Magento, the
+                        above code looks something like </p>
+                    <pre>
+                    $helper_sales = Mage::helper('sales');
+                    </pre>
+                    <p>In plain english, the static helper method will:
+                    <ol>
+                        <li>Look in the &lt;helpers /&gt; section of the Config.</li>
+                        <li>Within &lt;helpers /&gt;, look for a &lt;sales /&gt; section</li>
+                        <li>Within the &lt;sales /&gt; section look for a &lt;class /&gt; section</li>
+                        <li>Append the part after the slash to the value found in #3 (defaulting to <tt>data</tt> in
+                            this case)
+                        </li>
+                        <li>Instantiate the class found in #4 (Mage_Sales_Helper_Data)</li>
+                    </ol>
+                    <p>While this seems like a lot of work (and it is), the key advantage is by always looking to the
+                        config file for class names, we can override core Magento functionality <strong>without</strong>
+                        changing or adding to the core code. This level of meta programming, not usually found in PHP,
+                        allows you to cleanly extend only the parts of the system you need to.</p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
 </div>
-<p class="para1">The config is the beating heart of the Magento System.  It describes, in whole, almost any module, model, class, template, etc. than you'll need to access.  It's a level of abstraction that most PHP developers aren't used to working with, and while it adds development time in the form of confusion and head scratching, it also allows you an unprecedented amount of flexibility as far as overriding default system behaviors go.  </p>
-
-<p>To start with,  we're going to create a Magento module that will let us view the system config in our web browser.  Follow along by copying and pasting the code below, it's worth going through on your own as a way to start getting comfortable with things you'll be doing while working with Magento, as well as learning key terminology.</p>
-
-<h5>In this article...</h5>
-<ul><li><a href="#1" title="Setting up a Module Directory Structure">Setting up a Module Directory Structure</a>
-<li><a href="#2" title="Creating a Module Config">Creating a Module Config</a>
-<li><a href="#3" title="What Am I Looking at?">What Am I Looking at?</a>
-<li><a href="#4" title="Why Do I Care?">Why Do I Care?</a>
-</ul>
-
-<a name="1"></a>
-<h2>Setting up a Module Directory Structure</h2>
-
-<p>We're going to be creating a Magento module.  A module is a group of php and xml files meant to extend the system with new functionality, or override core system behavior.  This may meaning adding  additional data models to track sales information, changing the behavior of existing classes, or adding entirely new features.  </p>
-
-<p>It's worth noting that most of the base Magento system is built using the same module system you'll be using.  If you look in </p>
-
-<pre>app/code/core/Mage</pre>
-
-<p>each folder is a separate module built by the Magento team.  Together, these modules form the community shopping cart system you're using.  Your modules should be placed in the following folder</p>
-
-<pre>app/code/local/Packagename</pre>
-
-<p>"Packagename" should be a unique string to Namespace/Package your code.  It's an unofficial convention that this should be the name of your company.  The idea is to pick a string that no one else in the world could possibly be using.</p>
-
-<pre>app/code/local/Microsoft</pre>
-
-<p>We'll use "Magentotutorial".</p>
-
-<p>So, to add a module to your Magento system, create the following directory structure</p>
-
-<pre>app/code/local/Magentotutorial/Configviewer/Block
-app/code/local/Magentotutorial/Configviewer/controllers
-app/code/local/Magentotutorial/Configviewer/etc
-app/code/local/Magentotutorial/Configviewer/Helper
-app/code/local/Magentotutorial/Configviewer/Model
-app/code/local/Magentotutorial/Configviewer/sql</pre>
-
-<p>You won't need all these folder for every module, but setting them all up now is a smart idea. </p>
-
-<p>Next, there's two files you'll need to create.  The first, config.xml, goes in the etc folder you just created.  </p>
-
-<pre>app/code/local/Magentotutorial/Configviewer/etc/config.xml</pre>
-
-<p>The second file should be created at the following location</p>
-
-<pre>app/etc/modules/Magentotutorial_Configviewer.xml</pre>
-
-<p>The naming convention for this files is Packagename_Modulename.xml.</p>
-
-<p>The config.xml file should contain the following XML.  Don't worry too much about what all this does for now, we'll get there eventually</p>
-
-<pre>
-&lt;config>
-    &lt;modules>
-        &lt;Magentotutorial_Configviewer>
-            &lt;version>0.1.0&lt;/version>
-        &lt;/Magentotutorial_Configviewer>
-    &lt;/modules>
-&lt;/config>
-</pre>
-
-<p>Finally, Magentotutorial_Configviewer.xml should contain the following xml.</p>
-
-<pre>
-&lt;config>
-    &lt;modules>
-        &lt;Magentotutorial_Configviewer>
-            &lt;active>true&lt;/active>
-            &lt;codePool>local&lt;/codePool>
-        &lt;/Magentotutorial_Configviewer>
-    &lt;/modules>
-&lt;/config>
-</pre>
-
-<p>That's it. You now have a bare bones module that won't do anything, but that Magento will be aware of.  To make sure you've done everything right, do the following:
-<ol>
-<li>Clear your Magento cache</li>
-<li>In the Magento Admin, go to <strong>System->Configuration->Advanced</strong></li>
-<li>In the "Disable modules output" panel verify that Magentotutorial_Configviewer shows up</li>
-</ol>
-
-<p>Congratulations, you've built your first Magento module!</p>
-
-<a name="2"></a>
-<h2>Creating a Module Config</h2>
-
-<p>Of course, this module doesn't do anything yet.  When we're done, our module will
-<ol>
-<li>Check for the existence of a "showConfig" query string variable</li>
-<li>If showConfig is present, display our Magento config and halt normal execution</li>
-<li>Check for the existence of an additional query string variable, showConfigFormat that will let us specify text or xml output.</li>
-</ol>
-
-<p>First, we're going to add the following &lt;global&gt; section to our config.xml file.</p>
-
-<pre>
-&lt;config>
-    &lt;modules>...&lt;/modules>
-    &lt;global>
-        &lt;events>
-            &lt;controller_front_init_routers>
-                &lt;observers>
-                    &lt;Magentotutorial_configviewer_model_observer>
-                        &lt;type>singleton&lt;/type>
-                        &lt;class>Magentotutorial_Configviewer_Model_Observer&lt;/class>
-                        &lt;method>checkForConfigRequest&lt;/method>
-                    &lt;/Magentotutorial_configviewer_model_observer>
-                &lt;/observers>
-            &lt;/controller_front_init_routers>
-        &lt;/events>
-    &lt;/global>
-&lt;/config>
-</pre>
-
-<p>Then, create a file at </p>
-
-<pre>Magentotutorial/Configviewer/Model/Observer.php</pre>
-
-<p>and place the following code inside</p>
-
-<pre>
-&lt;?php
-    class Magentotutorial_Configviewer_Model_Observer {
-        const FLAG_SHOW_CONFIG = 'showConfig';
-        const FLAG_SHOW_CONFIG_FORMAT = 'showConfigFormat';
-
-        private $request;
-
-        public function checkForConfigRequest($observer) {
-            $this-&gt;request = $observer-&gt;getEvent()-&gt;getData('front')-&gt;getRequest();
-            if($this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG} === 'true'){
-                $this-&gt;setHeader();
-                $this-&gt;outputConfig();
-            }
-        }
-
-        private function setHeader() {
-            $format = isset($this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG_FORMAT}) ?
-            $this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG_FORMAT} : 'xml';
-            switch($format){
-                case 'text':
-                    header("Content-Type: text/plain");
-                    break;
-                default:
-                    header("Content-Type: text/xml");
-            }
-        }
-
-        private function outputConfig() {
-            die(Mage::app()-&gt;getConfig()-&gt;getNode()-&gt;asXML());
-        }
-    }
-</pre>
-
-<p>That's it.  Clear your Magento cache again and then load any Magento URL with a <tt>showConfig=true</tt> query string</p>
-
-<pre>http://magento.example.com/?showConfig=true</pre>
-
-<a name="3"></a>
-<h2>What am I looking at?</h2>
-
-<p>You should be looking at a giant XML file.  This describes the state of your Magento system.  It lists all modules, models, classes, event listeners or almost anything else you could think of.</p>
-
-<p>For example, consider the config.xml file you created above.  If you search the XML file in your browser for the text <tt>Configviewer_Model_Observer</tt> you'll find your class listed.  Every module's config.xml file is parsed by Magento and included in the global config.</p>
-
-<a name="4"></a>
-<h2>Why Do I Care?</h2>
-
-<p>Right now this may seem esoteric, but this config is key to understanding Magento.  Every module you'll be creating will add to this config, and anytime you need to access a piece of core system functionality, Magento will be referring back to the config to look something up.  </p>
-
-<p>A quick example:  As an MVC developer, you've likely worked with some kind of helper class, instantiated something like </p>
-
-<pre>
-$helper_sales = new HelperSales();
-</pre>
-
-<p>One of the things Magento has done is abstract away PHP's class declaration.  In Magento, the above code looks something like </p>
-
-<pre>
-$helper_sales = Mage::helper('sales');
-</pre>
-
-<p>In plain english, the static helper method will:
-<ol>
-<li>Look in the &lt;helpers /&gt; section of the Config.</li>
-<li>Within &lt;helpers /&gt;, look for a &lt;sales /&gt; section</li>
-<li>Within the &lt;sales /&gt; section look for a &lt;class /&gt; section</li>
-<li>Append the part after the slash to the value found in #3 (defaulting to <tt>data</tt> in this case)</li>
-<li>Instantiate the class found in #4 (Mage_Sales_Helper_Data)</li>
-</ol>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
 
-<p>While this seems like a lot of work (and it is), the key advantage is by always looking to the config file for class names, we can override core Magento functionality <strong>without</strong> changing or adding to the core code.  This level of meta programming, not usually found in PHP, allows you to cleanly extend only the parts of the system you need to.</p>
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
\ No newline at end of file
diff --git a/guides/m1x/magefordev/mage-for-dev-3.html b/guides/m1x/magefordev/mage-for-dev-3.html
index 5e09a7e138..c5ebee5f10 100644
--- a/guides/m1x/magefordev/mage-for-dev-3.html
+++ b/guides/m1x/magefordev/mage-for-dev-3.html
@@ -1,318 +1,599 @@
 ---
 ---
 <!DOCTYPE html>
-<html lang=en>
-
+<html lang="en" dir="ltr">
 <head>
-    <meta charset=utf-8>
-    <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
-    <link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
-    <link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <title>Magento for Developers: Part 3&mdash;Magento Controller Dispatch</title>
-
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>OpenMage for Developers: Part 3&mdash;OpenMage Controller Dispatch</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-
-<img src="{{ site.baseurl }}/guides/m1x/images/m1xheader.png" width="1024" alt="header" />
-{% include m1x/eol_message.html %}
-
-<div id="top"></div>
-
-<div id="content">
-<h1>Magento for Developers: Part 3&mdash;Magento Controller Dispatch</h1>
-<p><em>by Alan Storm</em>, updated for Magento 1.12</p>
-<p><a href="{{ site.m1xgithuburl }}/magefordev/mage-for-dev-3.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>
-
-<h5>Other articles in this series:</h5>
-<ul>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-1.html">Part 1&mdash;Introduction to Magento</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-2.html">Part 2&mdash;The Magento Config</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-3.html">Part 3&mdash;Magento Controller Dispatch</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-4.html">Part 4&mdash;Magento Layouts, Blocks and Templates</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">Part 5&mdash;Magento Models and ORM Basics</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Part 6&mdash;Magento Setup Resources</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">Part 7&mdash;Advanced ORM: Entity Attribute Value</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-8.html">Part 8&mdash;Varien Data Collections</a>
-</ul>
-</div>
-<p class="para1">The Model-View-Controller (MVC) architecture traces its origins back to the Smalltalk Programming language and Xerox Parc.  Since then, there have been many systems that describe their architecture as MVC. Each system is slightly different, but all have the goal of separating data access, business logic, and user-interface code from one another.</p>
-
-<p>The architecture of most PHP MVC frameworks will looks something <a href="http://alanstorm.com/2009/img/magento-book/php-mvc.png" class="magento-fig">like this</a>.  </p>
-
-<ol>
-<li>A URL is intercepted by a single PHP file (usually called a Front Controller).</li>
-<li>This PHP file will examine the URL, and derive a Controller name and an Action name (a process that's often called routing).</li>
-<li>The derived Controller is instantiated.</li>
-<li>The method name matching the derived Action name is called on the Controller.</li>
-<li>This Action method will instantiate and call methods on models, depending on the request variables.</li>
-<li>The Action method will also prepare a data structure of information. This data structure is passed on to the view.</li>
-<li>The view then renders HTML, using the information in the data structure it has received from the Controller.</li>
-</ol>
-
-<p>While this pattern was a great leap forward from the "each php file is a page" pattern established early on, for some software engineers, it's still an ugly  hack.  Common complaints are:</p>
-
-<ul>
-<li>The Front Controller PHP file still operates in the global namespace.</li>
-<li>Convention over configuration leads to less modularity.
-<ul>
-<li>URLs routing is often inflexible.</li>
-<li>Controllers are often bound to specific views.</li>
-<li>Even when a system offers a way to override these defaults, the convention leads to applications where it's difficult/impossible to drop in a new model, view, or Controller implementation without massive re-factoring.</li>
-</ul>
-</ul>
-
-<p>As you've probably guessed, the Magento team shares this world view and has created a more abstract MVC pattern that looks something <a href="http://alanstorm.com/2009/img/magento-book/magento-mvc.png">like this:</a>.
-
-<ol>
-<li>A URL is intercepted by a single PHP file.</li>
-<li>This PHP file instantiates a Magento application.</li>
-<li>The Magento application instantiates a Front Controller object.</li>
-<li>Front Controller instantiates any number of Router objects (specified in global config).</li>
-<li>Routers check the request URL for a "match".</li>
-<li>If a match is found, an Action Controller and Action are derived.</li>
-<li>The Action Controller is instantiated and the method name matching the Action Name is called.</li>
-<li>This Action method will instantiate and call methods on models, depending on the request.</li>
-<li>This Action Controller will then instantiate a Layout Object.</li>
-<li>This Layout Object will, based some request variables and system properties (also known as "handles"), create a list of Block objects that are valid for this request.</li>
-<li>Layout will also call an output method on certain Block objects, which start a nested rendering (Blocks will include other Blocks).</li>
-<li>Each Block has a corresponding Template file.  Blocks contain PHP logic, templates contain HTML and PHP output code.</li>
-<li>Blocks refer directly back to the models for their data.  In other words, <strong>the Action Controller does not pass them a data structure.</strong></li>
-</ol>
-
-<p>We'll eventually touch on each part of this request, but for now we're concerned with the <b>Front Controller -> Routers -> Action Controller</b> section.
-
-<hr />
-<h2>Hello World</h2>
-<p>Enough theory, it's time for Hello World. We're going to</p>
-<ol>
-<li>Create a Hello World module in the Magento system</li>
-<li>Configure this module with routes</li>
-<li>Create Action Controller(s) for our routes</li>
-</ol>
-
-<h3>Create Hello World Module</h3>
-
-<p>First, we'll create a directory structure for this module. Our directory structure should look as follows:
-
-<pre>app/code/local/Magentotutorial/Helloworld/Block
-app/code/local/Magentotutorial/Helloworld/controllers
-app/code/local/Magentotutorial/Helloworld/etc   
-app/code/local/Magentotutorial/Helloworld/Helper
-app/code/local/Magentotutorial/Helloworld/Model
-app/code/local/Magentotutorial/Helloworld/sql
-</pre>
-
-<p>Then create a configuration file for the module (at path <tt>app/code/local/Magentotutorial/Helloworld/etc/config.xml</tt>):
-<pre>
-&lt;config>    
-    &lt;modules>
-        &lt;Magentotutorial_Helloworld>
-            &lt;version>0.1.0&lt;/version>
-        &lt;/Magentotutorial_Helloworld>
-    &lt;/modules>
-&lt;/config>
-</pre>
-
-<p>Then create a file to activate the module (at path <tt>app/etc/modules/Magentotutorial_Helloworld.xml</tt>):
-<pre>
-&lt;config>
-    &lt;modules>
-        &lt;Magentotutorial_Helloworld>
-            &lt;active>true&lt;/active>
-            &lt;codePool>local&lt;/codePool>
-        &lt;/Magentotutorial_Helloworld>
-    &lt;/modules>
-&lt;/config>
-</pre>
-
-<p>Finally, we ensure the module is active:
-<ol>
-<li>Clear your Magento cache.</li>
-<li>In the Magento Admin, go to <strong>System-&gt;Configuration-&gt;Advanced</strong>.</li>
-<li>Expand "Disable Modules Output" (if it isn't already).</li>
-<li>Ensure that Magentotutorial_Helloworld shows up.</li>
-</ol>
-
-<h3>Configuring Routes</h3>
-
-<p>Next, we're going to configure a route.  A route will turn a URL into an Action Controller and a method.  Unlike other convention based PHP MVC systems, with Magento you need to explicitly define a route in the global Magento config.
-
-<p>In your config.xml file(at path app/code/local/Magentotutorial/Helloworld/etc/config.xml), add the following section:
-
-<pre>
-&lt;config>    
-    ...
-    &lt;frontend>
-        &lt;routers>
-            &lt;helloworld>
-                &lt;use>standard&lt;/use>
-                &lt;args>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
+                                    Introduction to OpenMage
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
+                                    The OpenMage Config
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
+                                    OpenMage Controller Dispatch
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
+                                    OpenMage Layouts, Blocks and Templates
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
+                                    OpenMage Models and ORM Basics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
+                                    OpenMage Setup Resources
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">
+                                    Advanced ORM: Entity Attribute Value
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-8.html">
+                                    Varien Data Collections
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">OpenMage Controller Dispatch</h1>
+                    </section>
+                    <p class="para1">The Model-View-Controller (MVC) architecture traces its origins back to the
+                        Smalltalk Programming language and Xerox Parc. Since then, there have been many systems that
+                        describe their architecture as MVC. Each system is slightly different, but all have the goal of
+                        separating data access, business logic, and user-interface code from one another.</p>
+                    <p>The architecture of most PHP MVC frameworks will looks something <a
+                            href="http://alanstorm.com/2009/img/magento-book/php-mvc.png" class="magento-fig">like
+                        this</a>. </p>
+                    <ol>
+                        <li>A URL is intercepted by a single PHP file (usually called a Front Controller).</li>
+                        <li>This PHP file will examine the URL, and derive a Controller name and an Action name (a
+                            process that's often called routing).
+                        </li>
+                        <li>The derived Controller is instantiated.</li>
+                        <li>The method name matching the derived Action name is called on the Controller.</li>
+                        <li>This Action method will instantiate and call methods on models, depending on the request
+                            variables.
+                        </li>
+                        <li>The Action method will also prepare a data structure of information. This data structure is
+                            passed on to the view.
+                        </li>
+                        <li>The view then renders HTML, using the information in the data structure it has received from
+                            the Controller.
+                        </li>
+                    </ol>
+                    <p>While this pattern was a great leap forward from the "each php file is a page" pattern
+                        established early on, for some software engineers, it's still an ugly hack. Common complaints
+                        are:</p>
+                    <ul>
+                        <li>The Front Controller PHP file still operates in the global namespace.</li>
+                        <li>Convention over configuration leads to less modularity.
+                            <ul>
+                                <li>URLs routing is often inflexible.</li>
+                                <li>Controllers are often bound to specific views.</li>
+                                <li>Even when a system offers a way to override these defaults, the convention leads to
+                                    applications where it's difficult/impossible to drop in a new model, view, or
+                                    Controller implementation without massive re-factoring.
+                                </li>
+                            </ul>
+                    </ul>
+                    <p>As you've probably guessed, the Magento team shares this world view and has created a more
+                        abstract MVC pattern that looks something <a
+                                href="http://alanstorm.com/2009/img/magento-book/magento-mvc.png">like this:</a>.
+                    <ol>
+                        <li>A URL is intercepted by a single PHP file.</li>
+                        <li>This PHP file instantiates a Magento application.</li>
+                        <li>The Magento application instantiates a Front Controller object.</li>
+                        <li>Front Controller instantiates any number of Router objects (specified in global config).
+                        </li>
+                        <li>Routers check the request URL for a "match".</li>
+                        <li>If a match is found, an Action Controller and Action are derived.</li>
+                        <li>The Action Controller is instantiated and the method name matching the Action Name is
+                            called.
+                        </li>
+                        <li>This Action method will instantiate and call methods on models, depending on the request.
+                        </li>
+                        <li>This Action Controller will then instantiate a Layout Object.</li>
+                        <li>This Layout Object will, based some request variables and system properties (also known as
+                            "handles"), create a list of Block objects that are valid for this request.
+                        </li>
+                        <li>Layout will also call an output method on certain Block objects, which start a nested
+                            rendering (Blocks will include other Blocks).
+                        </li>
+                        <li>Each Block has a corresponding Template file. Blocks contain PHP logic, templates contain
+                            HTML and PHP output code.
+                        </li>
+                        <li>Blocks refer directly back to the models for their data. In other words, <strong>the Action
+                            Controller does not pass them a data structure.</strong></li>
+                    </ol>
+                    <p>We'll eventually touch on each part of this request, but for now we're concerned with the <b>Front
+                        Controller -> Routers -> Action Controller</b> section.
+                    <hr/>
+                    <h2>Hello World</h2>
+                    <p>Enough theory, it's time for Hello World. We're going to</p>
+                    <ol>
+                        <li>Create a Hello World module in the Magento system</li>
+                        <li>Configure this module with routes</li>
+                        <li>Create Action Controller(s) for our routes</li>
+                    </ol>
+                    <h3>Create Hello World Module</h3>
+                    <p>First, we'll create a directory structure for this module. Our directory structure should look as
+                        follows:
+                    <pre>app/code/local/Magentotutorial/Helloworld/Block
+                    app/code/local/Magentotutorial/Helloworld/controllers
+                    app/code/local/Magentotutorial/Helloworld/etc
+                    app/code/local/Magentotutorial/Helloworld/Helper
+                    app/code/local/Magentotutorial/Helloworld/Model
+                    app/code/local/Magentotutorial/Helloworld/sql
+                    </pre>
+                    <p>Then create a configuration file for the module (at path <tt>app/code/local/Magentotutorial/Helloworld/etc/config.xml</tt>):
+                    <pre>
+                    &lt;config>
+                        &lt;modules>
+                            &lt;Magentotutorial_Helloworld>
+                                &lt;version>0.1.0&lt;/version>
+                            &lt;/Magentotutorial_Helloworld>
+                        &lt;/modules>
+                    &lt;/config>
+                    </pre>
+                    <p>Then create a file to activate the module (at path <tt>app/etc/modules/Magentotutorial_Helloworld.xml</tt>):
+                    <pre>
+                    &lt;config>
+                        &lt;modules>
+                            &lt;Magentotutorial_Helloworld>
+                                &lt;active>true&lt;/active>
+                                &lt;codePool>local&lt;/codePool>
+                            &lt;/Magentotutorial_Helloworld>
+                        &lt;/modules>
+                    &lt;/config>
+                    </pre>
+                    <p>Finally, we ensure the module is active:
+                    <ol>
+                        <li>Clear your Magento cache.</li>
+                        <li>In the Magento Admin, go to <strong>System-&gt;Configuration-&gt;Advanced</strong>.</li>
+                        <li>Expand "Disable Modules Output" (if it isn't already).</li>
+                        <li>Ensure that Magentotutorial_Helloworld shows up.</li>
+                    </ol>
+                    <h3>Configuring Routes</h3>
+                    <p>Next, we're going to configure a route. A route will turn a URL into an Action Controller and a
+                        method. Unlike other convention based PHP MVC systems, with Magento you need to explicitly
+                        define a route in the global Magento config.
+                    <p>In your config.xml file(at path app/code/local/Magentotutorial/Helloworld/etc/config.xml), add
+                        the following section:
+                    <pre>
+                    &lt;config>
+                        ...
+                        &lt;frontend>
+                            &lt;routers>
+                                &lt;helloworld>
+                                    &lt;use>standard&lt;/use>
+                                    &lt;args>
+                                        &lt;module&gt;Magentotutorial_Helloworld&lt;/module&gt;
+                                        &lt;frontName>helloworld&lt;/frontName>
+                                    &lt;/args>
+                                &lt;/helloworld>
+                            &lt;/routers>
+                        &lt;/frontend>
+                        ...
+                    &lt;/config>
+                    </pre>
+                    <p>We have a lot of new terminology here, let's break it down.</p>
+                    <h4>What is a &lt;frontend&gt;?</h4>
+                    <p>The &lt;frontend&gt; tag refers to a Magento Area. For now, think of Areas as individual Magento
+                        applications. The "frontend" Area is the public facing Magento shopping cart application. The
+                        "admin" Area is the private administrative console application. The "install" Area is the
+                        application you use to run though installing Magento the first time.</p>
+                    <h4>Why a &lt;routers&gt; tags if we're configuring individual routes?</h4>
+                    <p>There's a famous quote about computer science, often attributed to Phil Karlton:</p>
+                    <blockquote>
+                        <p>"There are only two hard things in Computer Science: cache invalidation and naming
+                            things"</p>
+                    </blockquote>
+                    <p>Magento, like all large systems, suffers from the naming problem in spades. You'll find there are
+                        many places in the global config, and the system in general, where the naming conventions seem
+                        unintuitive or even ambiguous. This is one of those places. Sometimes the
+                        <tt>&lt;routers&gt;</tt> tag will enclose configuration information about routers, other times
+                        it will enclose configuration information about the actual router objects that do the routing.
+                        This is going to seem counter intuitive at first, but as you start to work with Magento more and
+                        more, you'll start to understand its world view a little better. (Or, in the words of Han Solo,
+                        "Hey, trust me!").</p>
+                    <h4>What is a &lt;frontName&gt;?</h4>
+                    <p>When a router parses a URL, it gets separated as follows</p>
+                    <pre>http://example.com/frontName/actionControllerName/actionMethod/</pre>
+                    <p>So, by defining a value of "helloworld" in the &lt;frontName&gt; tags, we're telling Magento that
+                        we want the system to respond to URLs in the form of </p>
+                    <pre>http://example.com/helloworld/*</pre>
+                    <p>Many developers new to Magento confuse this frontName with the Front Controller object. They are
+                        <strong>not</strong> the same thing. The frontName belongs solely to routing.</p>
+                    <h4>What's the &lt;helloworld&gt; tag for?</h4>
+                    <p>This tag should be the lowercase version of you module name. Our module name is Helloworld, this
+                        tag is helloworld. Technically this tag defines our <em>route name</em></p>
+                    <p>You'll also notice our frontName matches our module name. It's a loose convention to have
+                        frontNames match the module names, but it's not a requirement. In your own modules, it's
+                        probably better to use a route name that's a combination of your module name and package name to
+                        avoid possible namespace collisions.</p>
+                    <h4>What's &lt;module&gt;Magentotutorial_Helloworld&lt;/module&gt; for?</h4>
+                    <p>This module tag should be the full name of your module, including its package/namespace name.
+                        This will be used by the system to locate your Controller files.</p>
+                    <h3>Create Action Controller(s) for our Routes</h3>
+                    <p>One last step to go, and we'll have our Action Controller. Create a file at
+                    <pre>app/code/local/Magentotutorial/Helloworld/controllers/IndexController.php</pre>
+                    <p>That contains the following
+                    <pre>
+                    &#60;&#63;php
+                    class Magentotutorial_Helloworld_IndexController extends Mage_Core_Controller_Front_Action {
+                        public function indexAction() {
+                            echo 'Hello World';
+                        }
+                    }
+                    </pre>
+                    <p>Clear your config cache, and load the following URL </p>
+                    <pre>http://example.com/helloworld/index/index</pre>
+                    <p>You should also be able to load</p>
+                    <pre>http://example.com/helloworld/index/
+                    http://example.com/helloworld/</pre>
+                    <p>You should see a blank page with the text "Hello World". Congratulations, you've setup your first
+                        Magento Controller!</p>
+                    <h4>Where do Action Controllers go?</h4>
+                    <p>Action Controllers should be placed in a module's <tt>controllers</tt> (lowercase c) folder. This
+                        is where the system will look for them.</p>
+                    <h4>How should Action Controllers be named?</h4>
+                    <p>Remember the &lt;module&gt; tag back in config.xml?
+                    <pre>
                     &lt;module&gt;Magentotutorial_Helloworld&lt;/module&gt;
-                    &lt;frontName>helloworld&lt;/frontName>
-                &lt;/args>
-            &lt;/helloworld>
-        &lt;/routers>  
-    &lt;/frontend>
-    ...
-&lt;/config>
-</pre>
-
-<p>We have a lot of new terminology here, let's break it down.</p>
-
-<h4>What is a &lt;frontend&gt;?</h4>
-
-<p>The &lt;frontend&gt; tag refers to a Magento Area.  For now, think of Areas as individual Magento applications.  The "frontend" Area is the public facing Magento shopping cart application.  The "admin" Area is the private administrative console application.  The "install" Area is the application you use to run though installing Magento the first time.</p>
-
-<h4>Why a &lt;routers&gt; tags if we're configuring individual routes?</h4>
-
-<p>There's a famous quote about computer science, often attributed to Phil Karlton:</p>
-<blockquote>
-  <p>"There are only two hard things in Computer Science: cache invalidation and naming things"</p>
-</blockquote>
-
-<p>Magento, like all large systems, suffers from the naming problem in spades.  You'll find there are many places in the global config, and the system in general, where the naming conventions seem unintuitive or even ambiguous.  This is one of those places.  Sometimes the <tt>&lt;routers&gt;</tt> tag will enclose configuration information about routers, other times it will enclose configuration information about the actual router objects that do the routing.  This is going to seem counter intuitive at first, but as you start to work with Magento more and more, you'll start to understand its world view a little better. (Or, in the words of Han Solo, "Hey, trust me!").</p>
-
-<h4>What is a &lt;frontName&gt;?</h4>
-
-<p>When a router parses a URL, it gets separated as follows</p>
-
-<pre>http://example.com/frontName/actionControllerName/actionMethod/</pre>
-
-<p>So, by defining a value of "helloworld" in the &lt;frontName&gt; tags, we're telling Magento that we want the system to respond to URLs in the form of </p>
-
-<pre>http://example.com/helloworld/*</pre>
-
-<p>Many developers new to Magento confuse this frontName with the Front Controller object.  They are <strong>not</strong> the same thing.  The frontName belongs solely to routing.</p>
-
-<h4>What's the &lt;helloworld&gt; tag for?</h4>
-
-<p>This tag should be the lowercase version of you module name.  Our module name is Helloworld, this tag is helloworld.  Technically this tag defines our <em>route name</em></p>
-
-<p>You'll also notice our frontName matches our module name.  It's a loose convention to have frontNames match the module names, but it's not a requirement. In your own modules, it's probably better to use a route name that's a combination of your module name and package name to avoid possible namespace collisions.</p>
-
-<h4>What's &lt;module&gt;Magentotutorial_Helloworld&lt;/module&gt; for?</h4>
-
-<p>This module tag should be the full name of your module, including its package/namespace name. This will be used by the system to locate your Controller files.</p>
-
-<h3>Create Action Controller(s) for our Routes</h3>
-
-<p>One last step to go, and we'll have our Action Controller.  Create a file at
-
-<pre>app/code/local/Magentotutorial/Helloworld/controllers/IndexController.php</pre>
-
-<p>That contains the following
-
-<pre>
-&#60;&#63;php
-class Magentotutorial_Helloworld_IndexController extends Mage_Core_Controller_Front_Action {        
-    public function indexAction() {
-        echo 'Hello World';
-    }
-}
-</pre>
-
-<p>Clear your config cache, and load the following URL </p>
-
-<pre>http://example.com/helloworld/index/index</pre>
-
-<p>You should also be able to load</p>
-
-<pre>http://example.com/helloworld/index/
-http://example.com/helloworld/</pre>
-
-<p>You should see a blank page with the text "Hello World".  Congratulations, you've setup your first Magento Controller!</p>
-
-
-<h4>Where do Action Controllers go?</h4>
-
-<p>Action Controllers should be placed in a module's <tt>controllers</tt> (lowercase c) folder.  This is where the system will look for them.</p>
-
-<h4>How should Action Controllers be named?</h4>
-
-<p>Remember the &lt;module&gt; tag back in config.xml?
-<pre>
-&lt;module&gt;Magentotutorial_Helloworld&lt;/module&gt;
-</pre>
-
-<p>An Action Controller's name will 
-<ol>
-<li>Start with this &lt;module&gt; string specified in config.xml (<tt>Magentotutorial_Helloworld</tt>)</li>
-<li>Be followed by an underscore (<tt>Magentotutorial_Helloworld_</tt>)</li>
-<li>Which will be followed by the Action Controller's name (<tt>Magentotutorial_Helloworld_Index</tt>)</li>
-<li>And finally, the word "Controller" (<tt>Magentotutorial_Helloworld_IndexController</tt>)</li>
-</ol>
-
-<p>All Action Controllers need <tt>Mage_Core_Controller_Front_Action</tt> as an ancestor.</p>
-
-<h4>What's that index/index nonsense?</h4>
-
-<p>As we previously mentioned, Magento URLs are routed (by default) as follows
-<pre>http://example.com/frontName/actionControllerName/actionMethod/</pre>
-
-<p>So in the URL 
-<pre>http://example.com/helloworld/index/index</pre>
-
-<p>the URI portion "helloworld" is the frontName, which is followed by index (The Action Controller name), which is followed by another index, which is the name of the Action Method that will be called. (an Action of index will call the method <tt>public function <strong>index</strong>Action(){...}</tt>.  </p>
-
-<p>If a URL is incomplete, Magento uses "index" as the default, which is why the following URLs are equivalent.
-<pre>
-http://example.com/helloworld/index
-http://example.com/helloworld
-</pre>
-
-<p>If we had a URL that looked like this</p>
-<pre>http://example.com/checkout/cart/add</pre>
-
-<p>Magento would</p>
-<ol>
-<li>Consult the global config to find the module to use for the frontName checkout (<tt>Mage_Checkout</tt>)</li>
-<li>Look for the cart Action Controller (<tt>Mage_Checkout_CartController</tt>)</li>
-<li>Call the <tt>addAction</tt> method on the cart Action Controller</li>
-</ol>
-
-<h4>Other Action Controller Tricks</h4>
-
-<p>Let's try adding a non-default method to our Action Controller.  Add the following code to IndexController.php</p>
-
-<pre>
-public function goodbyeAction() {
-    echo 'Goodbye World!';
-}
-</pre>
-
-<p>And then visit the URL to test it out:
-<pre>http://example.com/helloworld/index/goodbye </pre>
-
-<p>Because we're extending the <tt>Mage_Core_Controller_Front_Action</tt> class, we get some methods for free. For example, additional URL elements are automatically parsed into key/value pairs for us.  Add the following method to your Action Controller.
-
-<pre>
-public function paramsAction() {
-    echo '&lt;dl>';            
-    foreach($this->getRequest()->getParams() as $key=>$value) {
-        echo '&lt;dt>&lt;strong>Param:&lt;/strong>'.$key.'&lt;/dt>';
-        echo '&lt;dt>&lt;strong>Value: &lt;/strong>'.$value.'&lt;/dt>';
-    }
-    echo '&lt;/dl>';
-}
-</pre>
-
-<p>and visit the following URL</p>
-<pre>http://example.com/helloworld/index/params?foo=bar&amp;baz=eof</pre>
-
-<p>You should see each parameter and value printed out.</p>
-
-<p>Finally, what would we do if we wanted a URL that responded at 
-<pre>http://example.com/helloworld/messages/goodbye</pre>
-
-<p>Here our Action Controller's name is messages, so we'd create a file at 
-<pre>app/code/local/Magentotutorial/Helloworld/controllers/MessagesController.php</pre>
-
-<p>with an Action Controller named <tt>Magentotutorial_Helloworld_MessagesController</tt> and an Action Method that looked something like
-<pre>
-public function goodbyeAction()         
-{
-    echo 'Another Goodbye';
-}
-</pre>
+                    </pre>
+                    <p>An Action Controller's name will
+                    <ol>
+                        <li>Start with this &lt;module&gt; string specified in config.xml (<tt>Magentotutorial_Helloworld</tt>)
+                        </li>
+                        <li>Be followed by an underscore (<tt>Magentotutorial_Helloworld_</tt>)</li>
+                        <li>Which will be followed by the Action Controller's name
+                            (<tt>Magentotutorial_Helloworld_Index</tt>)
+                        </li>
+                        <li>And finally, the word "Controller" (<tt>Magentotutorial_Helloworld_IndexController</tt>)
+                        </li>
+                    </ol>
+                    <p>All Action Controllers need <tt>Mage_Core_Controller_Front_Action</tt> as an ancestor.</p>
+                    <h4>What's that index/index nonsense?</h4>
+                    <p>As we previously mentioned, Magento URLs are routed (by default) as follows
+                    <pre>http://example.com/frontName/actionControllerName/actionMethod/</pre>
+                    <p>So in the URL
+                    <pre>http://example.com/helloworld/index/index</pre>
+                    <p>the URI portion "helloworld" is the frontName, which is followed by index (The Action Controller
+                        name), which is followed by another index, which is the name of the Action Method that will be
+                        called. (an Action of index will call the method <tt>public function <strong>index</strong>Action(){...}</tt>.
+                    </p>
+                    <p>If a URL is incomplete, Magento uses "index" as the default, which is why the following URLs are
+                        equivalent.
+                    <pre>
+                    http://example.com/helloworld/index
+                    http://example.com/helloworld
+                    </pre>
+                    <p>If we had a URL that looked like this</p>
+                    <pre>http://example.com/checkout/cart/add</pre>
+                    <p>Magento would</p>
+                    <ol>
+                        <li>Consult the global config to find the module to use for the frontName checkout (<tt>Mage_Checkout</tt>)
+                        </li>
+                        <li>Look for the cart Action Controller (<tt>Mage_Checkout_CartController</tt>)</li>
+                        <li>Call the <tt>addAction</tt> method on the cart Action Controller</li>
+                    </ol>
+                    <h4>Other Action Controller Tricks</h4>
+                    <p>Let's try adding a non-default method to our Action Controller. Add the following code to
+                        IndexController.php</p>
+                    <pre>
+                    public function goodbyeAction() {
+                        echo 'Goodbye World!';
+                    }
+                    </pre>
+                    <p>And then visit the URL to test it out:
+                    <pre>http://example.com/helloworld/index/goodbye </pre>
+                    <p>Because we're extending the <tt>Mage_Core_Controller_Front_Action</tt> class, we get some methods
+                        for free. For example, additional URL elements are automatically parsed into key/value pairs for
+                        us. Add the following method to your Action Controller.
+                    <pre>
+                    public function paramsAction() {
+                        echo '&lt;dl>';
+                        foreach($this->getRequest()->getParams() as $key=>$value) {
+                            echo '&lt;dt>&lt;strong>Param:&lt;/strong>'.$key.'&lt;/dt>';
+                            echo '&lt;dt>&lt;strong>Value: &lt;/strong>'.$value.'&lt;/dt>';
+                        }
+                        echo '&lt;/dl>';
+                    }
+                    </pre>
+                    <p>and visit the following URL</p>
+                    <pre>http://example.com/helloworld/index/params?foo=bar&amp;baz=eof</pre>
+                    <p>You should see each parameter and value printed out.</p>
+                    <p>Finally, what would we do if we wanted a URL that responded at
+                    <pre>http://example.com/helloworld/messages/goodbye</pre>
+                    <p>Here our Action Controller's name is messages, so we'd create a file at
+                    <pre>app/code/local/Magentotutorial/Helloworld/controllers/MessagesController.php</pre>
+                    <p>with an Action Controller named <tt>Magentotutorial_Helloworld_MessagesController</tt> and an
+                        Action Method that looked something like
+                    <pre>
+                    public function goodbyeAction()
+                    {
+                        echo 'Another Goodbye';
+                    }
+                    </pre>
+                    <p>And that, in a nutshell, is how Magento implements the Controller portion of MVC. While it's a
+                        little more complicated than other PHP MVC framework's, it's a highly flexible system that will
+                        allow you build almost any URL structure you want.</p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
 
-<p>And that, in a nutshell, is how Magento implements the Controller portion of MVC. While it's a little more complicated than other PHP MVC framework's, it's a highly flexible system that will allow you build almost any URL structure you want.</p>
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
\ No newline at end of file
diff --git a/guides/m1x/magefordev/mage-for-dev-4.html b/guides/m1x/magefordev/mage-for-dev-4.html
index ec76055920..8040950668 100644
--- a/guides/m1x/magefordev/mage-for-dev-4.html
+++ b/guides/m1x/magefordev/mage-for-dev-4.html
@@ -1,487 +1,747 @@
 ---
 ---
 <!DOCTYPE html>
-<html lang=en>
-
+<html lang="en" dir="ltr">
 <head>
-    <meta charset=utf-8>
-
-    <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
-    <link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
-    <link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <title>Magento for Developers: Part 4&mdash;Magento Layouts, Blocks and Templates</title>
-
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>OpenMage for Developers: Part 4&mdash;OpenMage Layouts, Blocks and Templates</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-
-<img src="{{ site.baseurl }}/guides/m1x/images/m1xheader.png" width="1024" alt="header" />
-{% include m1x/eol_message.html %}
-
-<div id="top"></div>
-
-<div id="content">
-<h1>Magento for Developers: Part 4&mdash;Magento Layouts, Blocks and Templates</h1>
-<p><em>by Alan Storm</em>, updated for Magento 1.12</p>
-<p><a href="{{ site.m1xgithuburl }}/magefordev/mage-for-dev-4.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>
-
-
-<!-- Magento for Developers: Part 4&mdash;Magento Layouts, Blocks and Templates -->
-<!-- magento-for-dev-part-4-magento-layouts-blocks-and-templates 
-
-
-<style type="text/css">
-#kb-entry .series {float: right; width: 175px; margin-left: 10px; font-size: 12px; }
-#kb-entry .series ul {margin-left: 15px;}
-</style> 
-<div class="r-box-rss series">  -->
-
-<h5>Other articles in this series:</h5>
-<ul>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-1.html">Part 1&mdash;Introduction to Magento</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-2.html">Part 2&mdash;The Magento Config</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-3.html">Part 3&mdash;Magento Controller Dispatch</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-4.html">Part 4&mdash;Magento Layouts, Blocks and Templates</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">Part 5&mdash;Magento Models and ORM Basics</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Part 6&mdash;Magento Setup Resources</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">Part 7&mdash;Advanced ORM: Entity Attribute Value</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-8.html">Part 8&mdash;Varien Data Collections</a>
-</ul>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
+                                    Introduction to OpenMage
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
+                                    The OpenMage Config
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
+                                    OpenMage Controller Dispatch
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
+                                    OpenMage Layouts, Blocks and Templates
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
+                                    OpenMage Models and ORM Basics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
+                                    OpenMage Setup Resources
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">
+                                    Advanced ORM: Entity Attribute Value
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-8.html">
+                                    Varien Data Collections
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">OpenMage Layouts, Blocks and Templates</h1>
+                    </section>
+                    <p class="para1">Developers new to Magento are often confused by the Layout and View system. This
+                        article will take a look at Magento's Layout/Block approach, and show you how it fits into
+                        Magento MVC worldview.</p>
+                    <p>Unlike many popular MVC systems, Magento's Action Controller does <strong>not</strong> pass a
+                        data object to the view or set properties on the view object (with a few exceptions). Instead,
+                        the View component directly references system models to get the information it needs for
+                        display. </p>
+                    <p>One consequence of this design decision is that the View has been separated into Blocks and
+                        Templates. Blocks are PHP objects, Templates are "raw" PHP files (with a .phtml extension) that
+                        contain a mix of HTML and PHP (where PHP is used as a templating language). Each Block is tied
+                        to a single Template file. Inside a phtml file, PHP's <tt>$this</tt> keyword will contain a
+                        reference to the Template's Block object.</p>
+                    <br clear="all"/>
+                    <h2>A quick example</h2>
+                    <p>Take a look at the default product Template at the file at</p>
+                    <pre>app/design/frontend/base/default/template/catalog/product/list.phtml</pre>
+                    <p>You'll see the following PHP template code.</p>
+                    <pre>
+                    &lt;?php $_productCollection=$this->getLoadedProductCollection() ?>
+                    &lt;?php if(!$_productCollection->count()): ?> &lt;div class="note-msg">
+                        &lt;?php echo $this->__("There are no products matching the selection.") ?>
+                    &lt;/div> &lt;?php else: ?>
+                    ...
+                    </pre>
+                    <p>The <tt>getLoadedProductCollection</tt> method can be found in the Template's Block class, <tt>Mage_Catalog_Block_Product_List</tt>
+                        as shown:
+                    <pre>File: app/code/core/Mage/Catalog/Block/Product/List.php</pre>
+                    <pre>
+                    ...
+                    public function getLoadedProductCollection()
+                    {
+                        return $this->_getProductCollection();
+                    }
+                    ...
+                    </pre>
+                    <p>The block's <tt>_getProductCollection</tt> then instantiates models and reads their data,
+                        returning a result to the template.</p>
+                    <h2>Nesting Blocks</h2>
+                    <p>The real power of Blocks/Templates come with the <tt>getChildHtml</tt> method. This allows you to
+                        include the contents of a secondary Block/Template inside of a primary Block/Template. </p>
+                    <p>Blocks calling Blocks calling Blocks is how the entire HTML layout for your page is created. Take
+                        a look at the one column layout Template.</p>
+                    <pre>File: app/design/frontend/base/default/template/page/1column.phtml</pre>
+                    <pre>
+                    &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+                    &lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="&lt;?php echo $this->getLang() ?>" lang="&lt;?php echo $this->getLang() ?>">
+                    &lt;head>
+                    &lt;?php echo $this->getChildHtml('head') ?>
+                    &lt;/head>
+                    &lt;body class="page-popup &lt;?php echo $this->getBodyClass()?$this->getBodyClass():'' ?>">
+                        &lt;?php echo $this->getChildHtml('content') ?>
+                        &lt;?php echo $this->getChildHtml('before_body_end') ?>
+                        &lt;?php echo $this->getAbsoluteFooter() ?>
+                    &lt;/body>
+                    </pre>
+                    <p>The template itself is only 28 lines long. However, each call to
+                        <tt>$this->getChildHtml(...)</tt> will include and render another Block. These Blocks will, in
+                        turn, use <tt>getChildHtml</tt> to render other Blocks. It's Blocks all the way down.</p>
+                    <h2>The Layout</h2>
+                    <p>So, Blocks and Templates are all well and good, but you're probably wondering</p>
+                    <ol>
+                        <li>How do I tell Magento which Blocks I want to use on a page?</li>
+                        <li>How do I tell Magento which Block I should start rendering with?</li>
+                        <li>How do I specify a particular Block in <tt>getChildHtml(...)</tt>? Those argument strings
+                            don't look like Block names to me.
+                        </li>
+                    </ol>
+                    <p>This is where the Layout Object enters the picture. The Layout Object is an XML object that will
+                        define which Blocks are included on a page, and which Block(s) should kick off the rendering
+                        process.</p>
+                    <p><a href="mage-for-dev-3.html"
+                          title="Link to Magento for Developers: Part 3&mdash;Magento Controller Dispatch">Last time</a>
+                        we were echoing content directly from our Action Methods. This time let's create a simple HTML
+                        template for our Hello World module.</p>
+                    <p>First, create a file at</p>
+                    <pre>app/design/frontend/base/default/layout/local.xml</pre>
+                    <p>with the following contents</p>
+                    <pre>
+                    &lt;layout version="0.1.0">
+                        &lt;default>
+                            &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
+                        &lt;/default>
+                    &lt;/layout>
+                    </pre>
+                    <p>Then, create a file at </p>
+                    <pre>app/design/frontend/base/default/template/magentotutorial/helloworld/simple_page.phtml</pre>
+                    <p>with the following contents
+                    <pre>
+                    &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+                            "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+                    &lt;html xmlns="http://www.w3.org/1999/xhtml">
+                    &lt;head>
+                        &lt;title>Hello World&lt;/title>
+                        &lt;style type="text/css">
+                            body {
+                                background-color:#f00;
+                            }
+                        &lt;/style>
+                    &lt;/head>
+                    &lt;body>
+
+                    &lt;/body>
+                    &lt;/html>
+                    </pre>
+                    <p>Finally, each Action Controller is responsible for kicking off the layout process. We'll need to
+                        add two method calls to the Action Method.</p>
+                    <pre>
+                    public function indexAction() {
+                        //remove our previous echo
+                        //echo 'Hello Index!';
+                        $this->loadLayout();
+                        $this->renderLayout();
+                    }
+                    </pre>
+                    <p>Clear your Magento cache and reload your Hello World controller page. You should now see a
+                        website with a bright red background and an HTML source that matches what's in
+                        simple_page.phtml. </p>
+                    <h2>What's Going On</h2>
+                    <p>So, that's a lot of voodoo and cryptic incantations. Let's take a look at what's going on.</p>
+                    <p>First, you'll want to install the <a
+                            href="http://alanstorm.com/2005/projects/MagentoLayoutViewer.tar.gz">Layoutviewer</a>
+                        module. This is a module similar to the <a
+                                href="http://alanstorm.com/2005/projects/MagentoConfigViewer.tar.gz">Configviewer</a>
+                        module you built in the Hello World article that will let us peek at some of Magento's
+                        internals.</p>
+                    <p>Once you've installed the module (similar to how you setup the <a
+                            href="http://alanstorm.com/2005/projects/MagentoConfigViewer.tar.gz">Configviewer</a>
+                        module), go to the following URL</p>
+                    <pre>http://example.com/helloworld/index/index?showLayout=page</pre>
+                    <p>This is the layout xml for your page/request. It's made up of &lt;block /&gt;, &lt;reference /&gt;
+                        and &lt;remove /&gt; tags. When you call the <tt>loadLayout</tt> method of your Action
+                        Controller, Magento will </p>
+                    <ol>
+                        <li><p>Generate this Layout XML </p></li>
+                        <li><p>Instantiate a Block class for each &lt;block /&gt; tag, looking up the class using the
+                            tag's type attribute as a global config path and store it in the internal <tt>_blocks</tt>
+                            array of the layout object, using the tag's name attribute as the array key.</p></li>
+                        <li><p>If the &lt;block /&gt; tag contains an output attribute, its value is added to the
+                            internal <tt>_output</tt> array of the layout object.</p></li>
+                    </ol>
+                    <p>Then, when you call the <tt>renderLayout</tt> method in your Action Controller, Magento will
+                        iterate over all the Blocks in the <tt>_output</tt> array, using the value of the output
+                        attribute as a callback method. This is always <tt>toHtml</tt>, and means the starting point for
+                        output will be that Block's Template.</p>
+                    <p>The following sections will cover how Blocks are instantiated, how this layout file is generated,
+                        and finishes up with kicking off the output process.</p>
+                    <h2>Block Instantiation</h2>
+                    <p>So, within a Layout XML file, a &lt;block /&gt; has a "type" that's actually a Grouped Class Name
+                        URI</p>
+                    <pre>
+                    &lt;block type="page/html" ...
+                    &lt;block type="page/template_links" ...
+                    </pre>
+                    <p>The URI references a location in the (say it with me) global config. The first portion of the URI
+                        (in the above examples <tt>page</tt>) will be used to query the global config to find the page
+                        class name. The second portion of the URI (in the two examples above, <tt>html</tt> and <tt>template_links</tt>)
+                        will be appended to the base class name to create the class name Magento should instantiate.</p>
+                    <p>We'll go through <tt>page/html</tt> as an example. First, Magento looks for the global config
+                        node at file</p>
+                    <pre>app/code/core/Mage/Page/etc/config.xml</pre>
+                    <p>and finds
+                    <pre>
+                    &lt;page>
+                        &lt;class>Mage_Page_Block&lt;/class>
+                    &lt;/page>
+                    </pre>
+                    <p>This gives us our base class prefix <tt>Mage_Page_Block</tt>. Then, the second part of the URI
+                        (<tt>html</tt>) is appended to the class name to give us our final Block class name <tt>Mage_Page_Block_Html</tt>.
+                        This is the class that will be instantiated.</p>
+                    <p>If we create a block with the same name as an already existing block, the new block instance will
+                        replace the original instance. This is what we've done in our local.xml file from above.</p>
+                    <pre>
+                    &lt;layout version="0.1.0">
+                        &lt;default>
+                            &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
+                        &lt;/default>
+                    &lt;/layout>
+                    </pre>
+                    <p>The Block named <tt>root</tt> has been replaced with our Block, which points at a different phtml
+                        Template file.</p>
+                    <h2>Using references</h2>
+                    <p>&lt;reference name="" /&gt; will hook all contained XML declarations into an existing block with
+                        the specified name. Contained &lt;block /&gt; nodes will be assigned as child blocks to the
+                        referenced parent block.</p>
+                    <pre>
+                    &lt;layout version="0.1.0">
+                        &lt;default>
+                            &lt;block type="page/html" name="root" output="toHtml" template="page/2columns-left.phtml">
+                                &lt;!-- ... sub blocks ... -->
+                            &lt;/block>
+                        &lt;/default>
+                    &lt;/layout>
+                    </pre>
+                    <p>In a different layout file:</p>
+                    <pre>
+                    &lt;layout version="0.1.0">
+                        &lt;default>
+                            &lt;reference name="root">
+                                &lt;!-- ... another sub block ... -->
+                                &lt;block type="page/someothertype" name="some.other.block.name" template="path/to/some/other/template" />
+                            &lt;/reference>
+                        &lt;/default>
+                    &lt;/layout>
+                    </pre>
+                    <p>Even though the root block is declared in a separate layout XML file, the new block is added as a
+                        child block. Magento initially creates a <tt>page/html</tt> Block named <tt>root</tt>. Then,
+                        when it later encounters the reference with the same name (<tt>root</tt>), it will assign the
+                        new block <tt>some.other.block.name</tt> as a child of the root block.
+                    </p>
+                    <h2>How Layout Files are Generated</h2>
+                    <p>So, we have a slightly better understanding of what's going on with the Layout XML, but where is
+                        this XML file coming from? To answer that question, we need to introduce two new concepts;
+                        Handles and the Package Layout.</p>
+                    <h3>Handles</h3>
+                    <p>Each page request in Magento will generate several unique Handles. The Layoutview module can show
+                        you these Handles by using a URL something like</p>
+                    <pre>http://example.com/helloworld/index/index?showLayout=handles</pre>
+                    <p>You should see a list similar to the following (depending on your configuration)</p>
+                    <ol>
+                        <li><tt>default</tt></li>
+                        <li><tt>STORE_bare_us</tt></li>
+                        <li><tt>THEME_frontend_default_default</tt></li>
+                        <li><tt>helloworld_index_index</tt></li>
+                        <li><tt>customer_logged_out</tt></li>
+                    </ol>
+                    <p>Each of these is a Handle. Handles are set in a variety of places within the Magento system. The
+                        two we want to pay attention to are <tt>default</tt> and <tt>helloworld_index_index</tt>. The
+                        <tt>default</tt> Handle is present in <strong>every</strong> request into the Magento system.
+                        The <tt>helloworld_index_index</tt> Handle is created by combining the route name (helloworld),
+                        Action Controller name (index), and Action Controller Action Method (index) into a single
+                        string. This means each possible method on an Action Controller has a Handle associated with it.
+                    </p>
+                    <p>Remember that "index" is the Magento default for both Action Controllers and Action Methods, so
+                        the following request</p>
+                    <pre>http://example.com/helloworld/?showLayout=handles</pre>
+                    <p>Will also produce a Handle named <tt>helloworld_index_index</tt></p>
+                    <h2>Package Layout</h2>
+                    <p>You can think of the Package Layout similar to the global config. It's a large XML file that
+                        contains <strong>every possible layout configuration</strong> for a particular Magento install.
+                        Let's take a look at it using the Layoutview module</p>
+                    <pre>http://example.com/helloworld/index/index?showLayout=package</pre>
+                    <p>This may take a while to load. If your browser is choking on the XML rendering, try the text
+                        format</p>
+                    <pre>http://example.com/helloworld/index/index?showLayout=package&amp;showLayoutFormat=text</pre>
+                    <p>You should see a very large XML file. This is the Package Layout. This XML file is created by
+                        combining the contents of all the XML layout files for the current theme (or package). For the
+                        default install, this is at</p>
+                    <pre>app/design/frontend/base/default/layout/</pre>
+                    <p>Behind the scenes there are <strong>&lt;frontend&gt;&lt;layout&gt;&lt;updates /&gt;</strong> and
+                        <strong>&lt;adminhtml&gt;&lt;layout&gt;&lt;updates /&gt;</strong> sections of the global config
+                        that contains nodes with all the file names to load for the respective area. Once the files
+                        listed in the config have been combined, Magento will merge in one last xml file, local.xml.
+                        This is the file where you're able to add your customizations to your Magento install. </p>
+                    <h2>Combining Handles and The Package Layout</h2>
+                    <p>So, if you look at the Package Layout, you'll see some familiar tags such as &lt;block /&gt; and
+                        &lt;reference /&gt;, but they're all surrounded by tags that look like </p>
+                    <pre>
+                    &lt;default />
+                    &lt;catalogsearch_advanced_index />
+                    etc...
+                    </pre>
+                    <p>These are all Handle tags. The Layout for an individual request is generated by grabbing all the
+                        sections of the Package Layout that match any Handles for the request. So, in our example above,
+                        our layout is being generated by grabbing tags from the following sections</p>
+                    <pre>
+                    &lt;default />
+                    &lt;STORE_bare_us />
+                    &lt;THEME_frontend_default_default />
+                    &lt;helloworld_index_index />
+                    &lt;customer_logged_out />
+                    </pre>
+                    <p>There's one additional tag you'll need to be aware of in the Package Layout. The &lt;update /&gt;
+                        tag allows you to include another Handle's tags. For example</p>
+                    <pre>
+                    &lt;customer_account_index>
+                        &lt;!-- ... -->
+                        &lt;update handle="customer_account"/>
+                        &lt;!-- ... -->
+                    &lt;/customer_account_index>
+                    </pre>
+                    <p>Is saying that requests with a customer_account_index Handle should include &lt;blocks /&gt;s
+                        from the &lt;customer_account /&gt; Handle.</p>
+                    <h2>Applying What We've Learned</h2>
+                    <p>OK, that's a lot of theory. Lets get back to what we did earlier. Knowing what we know now,
+                        adding</p>
+                    <pre>
+                    &lt;layout version="0.1.0">
+                        &lt;default>
+                            &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
+                        &lt;/default>
+                    &lt;/layout>
+                    </pre>
+                    <p>to <tt>local.xml</tt> means we've overridden the "root" tag. with a different Block. By placing
+                        this in the &lt;default /&gt; Handle we've ensured that this override will happen for <strong>every
+                            page request</strong> in the system. That's probably not what we want. </p>
+                    <p>If you go to any other page in your Magento site, you'll notice they're either blank white, or
+                        have the same red background that your hello world page does. Let's change your
+                        <tt>local.xml</tt> file so it only applies to the hello world page. We'll do this by changing
+                        default to use the full action name handle (<tt>helloworld_index_index</tt>).</p>
+                    <pre>
+                    &lt;layout version="0.1.0">
+                        &lt;helloworld_index_index>
+                            &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
+                        &lt;/helloworld_index_index>
+                    &lt;/layout>
+                    </pre>
+                    <p>Clear your Magento cache, and the rest of your pages should be restored. </p>
+                    <p>Right now this only applies to our index Action Method. Let's add it to the goodbye Action Method
+                        as well. In your Action Controller, modify the goodbye action so it looks like</p>
+                    <pre>
+                    public function goodbyeAction() {
+                        $this->loadLayout();
+                        $this->renderLayout();
+                    }
+                    </pre>
+                    <p>If you load up the following URL, you'll notice you're still getting the default Magento
+                        layout.</p>
+                    <pre>http://example.com/helloworld/index/goodbye</pre>
+                    <p>We need to add a Handle for the full action name (<tt>helloworld_index_goodbye</tt>) to our
+                        local.xml file. Rather than specify a new &lt;block /&gt;, lets use the update tag to include
+                        the <tt>helloworld_index_index</tt> Handle.</p>
+                    <pre>
+                    &lt;layout version="0.1.0">
+                        &lt;!-- ... -->
+                        &lt;helloworld_index_goodbye>
+                            &lt;update handle="helloworld_index_index" />
+                        &lt;/helloworld_index_goodbye>
+                    &lt;/layout>
+                    </pre>
+                    <p>Loading the following pages (after clearing your Magento cache) should now produce identical
+                        results.</p>
+                    <pre>http://example.com/helloworld/index/index
+                    http://example.com/helloworld/index/goodbye</pre>
+                    <h2>Starting Output and getChildHtml</h2>
+                    <p>In a standard configuration, output starts on the Block named root (because it has an output
+                        attribute). We've overridden root's Template with our own</p>
+                    <pre>template="magentotutorial/helloworld/simple_page.phtml"</pre>
+                    <p>Templates are referenced from the root folder of the current theme. In this case, that's</p>
+                    <pre>app/design/frontend/base/default</pre>
+                    <p>so we need to drill down to our custom page. Most Magento Templates are stored in </p>
+                    <pre>app/design/frontend/base/default/templates</pre>
+                    <p>Combining this gives us the full path</p>
+                    <pre>app/design/frontend/base/default/templates/magentotutorial/helloworld/simple_page.phtml</pre>
+                    <h2>Adding Content Blocks</h2>
+                    <p>A simple red page is pretty boring. Let's add some content to this page. Change your <tt>&lt;helloworld_index_index
+                        /&gt;</tt> Handle in local.xml so it looks like the following</p>
+                    <pre>
+                    &lt;helloworld_index_index>
+                        &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml">
+                            &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
+                        &lt;/block>
+                    &lt;/helloworld_index_index>
+                    </pre>
+                    <p>We're adding a new Block nested within our root. This is a Block that's distributed with Magento,
+                        and will display a customer registration form. By nesting this Block within our root Block,
+                        we've made it available to be pulled into our <tt>simple_page.html</tt> Template. Next, we'll
+                        use the Block's getChildHtml method in our <tt>simple_page.phtml</tt> file. Edit <tt>simple_page.html</tt>
+                        so it looks like this</p>
+                    <pre>
+                    &lt;body>
+                        &lt;?php echo $this->getChildHtml('customer_form_register'); ?>
+                    &lt;/body>
+                    </pre>
+                    <p>Clear your Magento cache and reload the page and you should see the customer registration form on
+                        your red background. Magento also has a Block named top.links. Let's try including that. Change
+                        your simple_page.html file so it reads</p>
+                    <pre>
+                    &lt;body>
+                        &lt;h1>Links&lt;/h1>
+                        &lt;?php echo $this->getChildHtml('top.links'); ?>
+                    &lt;/body>
+                    </pre>
+                    <p>When you reload the page, you'll notice that your &lt;h1&gt;Links&lt;/h1&gt; title is rendering,
+                        but nothing is rendering for top.links. That's because we didn't add it to local.xml. The <tt>getChildHtml</tt>
+                        method can only include Blocks that are specified as sub-Blocks in the Layout. This allows
+                        Magento to only instantiate the Blocks it needs, and also allows you to set difference Templates
+                        for Blocks based on context.</p>
+                    <p>Let's add the top.links Block to our local.xml</p>
+                    <pre>
+                    &lt;helloworld_index_index>
+                        &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml">
+                            &lt;block type="page/template_links" name="top.links"/>
+                            &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
+                        &lt;/block>
+                    &lt;/helloworld_index_index>
+                    </pre>
+                    <p>Clear your cache and reload the page. You should now see the top.links module. </p>
+                    <h2>Time for action</h2>
+                    <p>There is one more important concept to cover before we wrap up this lesson, and that is the &lt;action
+                        /&gt; tag. Using the &lt;action /&gt; tag enables us to call public PHP methods of the block
+                        classes. So instead of changing the template of the root block by replacing the block instance
+                        with our own, we can use a call to <tt>setTemplate</tt> instead.</p>
+                    <pre>
+                    &lt;layout version="0.1.0">
+                        &lt;helloworld_index_index>
+                            &lt;reference name="root">
+                                &lt;action method="setTemplate">
+                                    &lt;template>magentotutorial/helloworld/simple_page.phtml&lt;/template>
+                                &lt;/action>
+                                &lt;block type="page/template_links" name="top.links"/>
+                                &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
+                            &lt;/reference>
+                        &lt;/helloworld_index_index>
+                    &lt;/layout>
+                    </pre>
+                    <p>This layout XML will first set the template property of the root block, and then will add the two
+                        blocks we use as child blocks. Once we clear the cache, the result should look just as before.
+                        The benefit of using the &lt;action /&gt; is the same block instance is used that was created
+                        earlier, and all other parent/child associations still exist. For that reason this is a more
+                        upgrade proof way of implementing our changes.</p>
+                    <p>All arguments to the action's method need to be wrapped in an individual child node of the &lt;action
+                        /&gt; tag. The name of that node doesn't matter, only the order of the nodes. We could have
+                        written the action node from the previous example as follows with the same effect.
+                    </p>
+                    <pre>
+                    &lt;action method="setTemplate">
+                        &lt;some_new_template>magentotutorial/helloworld/simple_page.phtml&lt;/some_new_template>
+                    &lt;/action>
+                    </pre>
+                    <p>This is just to illustrate that the action's argument node names are arbitrary.</p>
+                    <h2>Wrapup</h2>
+                    <p>That covers Layout fundamentals. We have covered the tags &lt;block /&gt;, &lt;reference /&gt;,
+                        &lt;update /&gt; and &lt;action /&gt;, and also layout update handles like &lt;default /&gt; and
+                        &lt;cms_index_index /&gt;. These make up most of the layout configuration used in Magento. If
+                        you found it somewhat daunting, don't worry, you'll rarely need to work with layouts on such a
+                        fundamental level. Magento provides a number of pre-built layouts which can be modified and
+                        skinned to meet the needs of your store. Understanding how the entire Layout system works can be
+                        a great help when you're trouble shooting Layout issues, or adding new functionality to an
+                        existing Magento system.</p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
 </div>
-<p class="para1">Developers new to Magento are often confused by the Layout and View system.  This article will take a look at Magento's Layout/Block approach, and show you how it fits into Magento MVC worldview.</p>
-
-<p>Unlike many popular MVC systems, Magento's Action Controller does <strong>not</strong> pass a data object to the view or set properties on the view object (with a few exceptions).  Instead, the View component directly references system models to get the information it needs for display.  </p>
-
-<p>One consequence of this design decision is that the View has been separated into Blocks and Templates.  Blocks are PHP objects, Templates are "raw" PHP files (with a .phtml extension) that contain a mix of HTML and PHP (where PHP is used as a templating language).  Each Block is tied to a single Template file.  Inside a phtml file, PHP's <tt>$this</tt> keyword will contain a reference to the Template's Block object.</p>
-<br clear="all" />
-
-<h2>A quick example</h2>
-
-<p>Take a look at the default product Template at the file at</p>
-
-<pre>app/design/frontend/base/default/template/catalog/product/list.phtml</pre>
-
-<p>You'll see the following PHP template code.</p>
-
-<pre>
-&lt;?php $_productCollection=$this->getLoadedProductCollection() ?>
-&lt;?php if(!$_productCollection->count()): ?> &lt;div class="note-msg">
-    &lt;?php echo $this->__("There are no products matching the selection.") ?>
-&lt;/div> &lt;?php else: ?>
-...
-</pre>
-
-<p>The <tt>getLoadedProductCollection</tt> method can be found in the Template's Block class, <tt>Mage_Catalog_Block_Product_List</tt> as shown:
-
-<pre>File: app/code/core/Mage/Catalog/Block/Product/List.php</pre>
-
-<pre>
-...
-public function getLoadedProductCollection()
-{
-    return $this->_getProductCollection();
-}
-...
-</pre>
-
-<p>The block's <tt>_getProductCollection</tt> then instantiates models and reads their data, returning a result to the template.</p>
-
-<h2>Nesting Blocks</h2>
-
-<p>The real power of Blocks/Templates come with the <tt>getChildHtml</tt> method.  This allows you to include the contents of a secondary Block/Template inside of a primary Block/Template.  </p>
-
-<p>Blocks calling Blocks calling Blocks is how the entire HTML layout for your page is created.  Take a look at the one column layout Template.</p>
-
-<pre>File: app/design/frontend/base/default/template/page/1column.phtml</pre>
-
-<pre>
-&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-&lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="&lt;?php echo $this->getLang() ?>" lang="&lt;?php echo $this->getLang() ?>">
-&lt;head>
-&lt;?php echo $this->getChildHtml('head') ?>
-&lt;/head>
-&lt;body class="page-popup &lt;?php echo $this->getBodyClass()?$this->getBodyClass():'' ?>">
-    &lt;?php echo $this->getChildHtml('content') ?>
-    &lt;?php echo $this->getChildHtml('before_body_end') ?>
-    &lt;?php echo $this->getAbsoluteFooter() ?>
-&lt;/body>
-</pre>
-
-<p>The template itself is only 28 lines long.  However, each call to <tt>$this->getChildHtml(...)</tt> will include and render another Block.  These Blocks will, in turn, use <tt>getChildHtml</tt> to render other Blocks.  It's Blocks all the way down.</p>
-
-<h2>The Layout</h2>
-
-<p>So, Blocks and Templates are all well and good, but you're probably wondering</p>
-
-<ol>
-<li>How do I tell Magento which Blocks I want to use on a page?</li>
-<li>How do I tell Magento which Block I should start rendering with?</li>
-<li>How do I specify a particular Block in <tt>getChildHtml(...)</tt>? Those argument strings don't look like Block names to me.</li>
-</ol>
-
-<p>This is where the Layout Object enters the picture.  The Layout Object is an XML object that will define which Blocks are included on a page, and which Block(s) should kick off the rendering process.</p>
-
-<p><a href="mage-for-dev-3.html" title="Link to Magento for Developers: Part 3&mdash;Magento Controller Dispatch">Last time</a> we were echoing content directly from our Action Methods.  This time let's create a simple HTML template for our Hello World module.</p>
-
-<p>First, create a file at</p>
-
-<pre>app/design/frontend/base/default/layout/local.xml</pre>
-
-<p>with the following contents</p>
-
-<pre>
-&lt;layout version="0.1.0">
-    &lt;default>
-        &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
-    &lt;/default>
-&lt;/layout>
-</pre>
-
-<p>Then, create a file at  </p>
-
-<pre>app/design/frontend/base/default/template/magentotutorial/helloworld/simple_page.phtml</pre>
-
-<p>with the following contents
-<pre>
-&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-&lt;html xmlns="http://www.w3.org/1999/xhtml">
-&lt;head>
-    &lt;title>Hello World&lt;/title>
-    &lt;style type="text/css">
-        body {
-            background-color:#f00;
-        }
-    &lt;/style>
-&lt;/head>
-&lt;body>
-
-&lt;/body>
-&lt;/html>
-</pre>
-
-<p>Finally, each Action Controller is responsible for kicking off the layout process.  We'll need to add two method calls to the Action Method.</p>
-
-<pre>
-public function indexAction() {
-    //remove our previous echo
-    //echo 'Hello Index!';
-    $this->loadLayout();
-    $this->renderLayout();
-}
-</pre>
-
-<p>Clear your Magento cache and reload your Hello World controller page.  You should now see a website with a bright red background and an HTML source that matches what's in simple_page.phtml.  </p>
-
-<h2>What's Going On</h2>
-
-<p>So, that's a lot of voodoo and cryptic incantations.  Let's take a look at what's going on.</p>
-
-<p>First, you'll want to install the <a href="http://alanstorm.com/2005/projects/MagentoLayoutViewer.tar.gz">Layoutviewer</a> module.  This is a module similar to the <a href="http://alanstorm.com/2005/projects/MagentoConfigViewer.tar.gz">Configviewer</a> module you built in the Hello World article that will let us peek at some of Magento's internals.</p>
-
-<p>Once you've installed the module (similar to how you setup the <a href="http://alanstorm.com/2005/projects/MagentoConfigViewer.tar.gz">Configviewer</a> module), go to the following URL</p>
-
-<pre>http://example.com/helloworld/index/index?showLayout=page</pre>
-
-<p>This is the layout xml for your page/request.  It's made up of &lt;block /&gt;, &lt;reference /&gt; and &lt;remove /&gt; tags.  When you call the  <tt>loadLayout</tt> method of your Action Controller, Magento will </p>
-
-<ol>
-<li><p>Generate this Layout XML </p></li>
-<li><p>Instantiate a Block class for each &lt;block /&gt; tag, looking up the class using the tag's type attribute as a global config path and store it in the internal <tt>_blocks</tt> array of the layout object, using the tag's name attribute as the array key.</p></li>
-<li><p>If the &lt;block /&gt; tag contains an output attribute, its value is added to the internal <tt>_output</tt> array of the layout object.</p></li>
-</ol>
-
-<p>Then, when you call the <tt>renderLayout</tt> method in your Action Controller, Magento will iterate over all the Blocks in the <tt>_output</tt> array, using the value of the output attribute as a callback method. This is always <tt>toHtml</tt>, and means the starting point for output will be that Block's Template.</p>
-
-<p>The following sections will cover how Blocks are instantiated, how this layout file is generated, and finishes up with kicking off the output process.</p>
-
-<h2>Block Instantiation</h2>
-
-<p>So, within a Layout XML file, a &lt;block /&gt; has a "type" that's actually a Grouped Class Name URI</p>
-<pre>
-&lt;block type="page/html" ...
-&lt;block type="page/template_links" ...
-</pre>
-
-<p>The URI references a location in the (say it with me) global config.  The first portion of the URI (in the above examples <tt>page</tt>) will be used to query the global config to find the page class name.  The second portion of the URI (in the two examples above, <tt>html</tt> and <tt>template_links</tt>) will be appended to the base class name to create the class name Magento should instantiate.</p>
-
-<p>We'll go through <tt>page/html</tt> as an example.  First, Magento looks for the global config node at file</p>
-
-<pre>app/code/core/Mage/Page/etc/config.xml</pre>
-
-<p>and finds
-<pre>
-&lt;page>
-    &lt;class>Mage_Page_Block&lt;/class>
-&lt;/page>
-</pre>
-
-<p>This gives us our base class prefix <tt>Mage_Page_Block</tt>. Then, the second part of the URI (<tt>html</tt>) is appended to the class name to give us our final Block class name <tt>Mage_Page_Block_Html</tt>. This is the class that will be instantiated.</p>
-
-<p>If we create a block with the same name as an already existing block, the new block instance will replace the original instance. This is what we've done in our local.xml file from above.</p>
-
-<pre>
-&lt;layout version="0.1.0">
-    &lt;default>
-        &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
-    &lt;/default>
-&lt;/layout>
-</pre>
-
-<p>The Block named <tt>root</tt> has been replaced with our Block, which points at a different phtml Template file.</p>
-
-<h2>Using references</h2>
-
-<p>&lt;reference name="" /&gt; will hook all contained XML declarations into an existing block with the specified name. Contained &lt;block /&gt; nodes will be assigned as child blocks to the referenced parent block.</p>
-
-<pre>
-&lt;layout version="0.1.0">
-    &lt;default>
-        &lt;block type="page/html" name="root" output="toHtml" template="page/2columns-left.phtml">
-            &lt;!-- ... sub blocks ... -->
-        &lt;/block>
-    &lt;/default>
-&lt;/layout>
-</pre>
-
-<p>In a different layout file:</p>
-
-<pre>
-&lt;layout version="0.1.0">
-    &lt;default>
-        &lt;reference name="root">
-            &lt;!-- ... another sub block ... -->
-            &lt;block type="page/someothertype" name="some.other.block.name" template="path/to/some/other/template" />
-        &lt;/reference>
-    &lt;/default>
-&lt;/layout>
-</pre>
-
-<p>Even though the root block is declared in a separate layout XML file, the new block is added as a child block. Magento initially creates a <tt>page/html</tt> Block named <tt>root</tt>.  Then, when it later encounters the reference with the same name (<tt>root</tt>), it will assign the new block <tt>some.other.block.name</tt> as a child of the root block.
-</p>
-
-<h2>How Layout Files are Generated</h2>
-
-<p>So, we have a slightly better understanding of what's going on with the Layout XML, but where is this XML file coming from?  To answer that question, we need to introduce two new concepts; Handles and the Package Layout.</p>
-
-<h3>Handles</h3>
-
-<p>Each page request in Magento will generate several unique Handles.  The Layoutview module can show you these Handles by using a URL something like</p>
-
-<pre>http://example.com/helloworld/index/index?showLayout=handles</pre>
-
-<p>You should see a list similar to the following (depending on your configuration)</p>
-
-<ol>
-<li><tt>default</tt></li>
-<li><tt>STORE_bare_us</tt></li>
-<li><tt>THEME_frontend_default_default</tt></li>
-<li><tt>helloworld_index_index</tt></li>
-<li><tt>customer_logged_out</tt></li>
-</ol>
-
-<p>Each of these is a Handle. Handles are set in a variety of places within the Magento system.  The two we want to pay attention to are <tt>default</tt> and <tt>helloworld_index_index</tt>.  The <tt>default</tt> Handle is present in <strong>every</strong> request into the Magento system.  The <tt>helloworld_index_index</tt> Handle is created by combining the route name (helloworld), Action Controller name (index), and Action Controller Action Method (index) into a single string.  This means each possible method on an Action Controller has a Handle associated with it.  </p>
-
-<p>Remember that "index" is the Magento default for both Action Controllers and Action Methods, so the following request</p>
-
-<pre>http://example.com/helloworld/?showLayout=handles</pre>
-
-<p>Will also produce a Handle named <tt>helloworld_index_index</tt></p>
-
-<h2>Package Layout</h2>
-
-<p>You can think of the Package Layout similar to the global config.  It's a large XML file that contains <strong>every possible layout configuration</strong> for a particular Magento install.  Let's take a look at it using the Layoutview module</p>
-
-<pre>http://example.com/helloworld/index/index?showLayout=package</pre>
-
-<p>This may take a while to load.  If your browser is choking on the XML rendering, try the text format</p>
-
-<pre>http://example.com/helloworld/index/index?showLayout=package&amp;showLayoutFormat=text</pre>
-
-<p>You should see a very large XML file.  This is the Package Layout.  This XML file is created by combining the contents of all the XML layout files for the current theme (or package).  For the default install, this is at</p>
-
-<pre>app/design/frontend/base/default/layout/</pre>
-
-<p>Behind the scenes there are <strong>&lt;frontend&gt;&lt;layout&gt;&lt;updates /&gt;</strong> and <strong>&lt;adminhtml&gt;&lt;layout&gt;&lt;updates /&gt;</strong> sections of the global config that contains nodes with all the file names to load for the respective area.  Once the files listed in the config have been combined, Magento will merge in one last xml file, local.xml.  This is the file where you're able to add your customizations to your Magento install. </p>
-
-<h2>Combining Handles and The Package Layout</h2>
-
-<p>So, if you look at the Package Layout, you'll see some familiar tags such as &lt;block /&gt; and &lt;reference /&gt;, but they're all surrounded by tags that look like </p>
-<pre>
-&lt;default />
-&lt;catalogsearch_advanced_index />
-etc...
-</pre>
-
-<p>These are all Handle tags. The Layout for an individual request is generated by grabbing all the sections of the Package Layout that match any Handles for the request.  So, in our example above, our layout is being generated by grabbing tags from the following sections</p>
-
-<pre>
-&lt;default />
-&lt;STORE_bare_us />
-&lt;THEME_frontend_default_default />
-&lt;helloworld_index_index />
-&lt;customer_logged_out />
-</pre>
-
-<p>There's one additional tag you'll need to be aware of in the Package Layout.  The &lt;update /&gt; tag allows you to include another Handle's tags.  For example</p>
-
-<pre>
-&lt;customer_account_index>
-    &lt;!-- ... -->
-    &lt;update handle="customer_account"/>
-    &lt;!-- ... -->
-&lt;/customer_account_index>
-</pre>
-
-<p>Is saying that requests with a customer_account_index Handle should include &lt;blocks /&gt;s from the &lt;customer_account /&gt; Handle.</p>
-
-
-<h2>Applying What We've Learned</h2>
-
-<p>OK, that's a lot of theory.  Lets get back to what we did earlier.  Knowing what we know now, adding</p>
-<pre>
-&lt;layout version="0.1.0">
-    &lt;default>
-        &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
-    &lt;/default>
-&lt;/layout>
-</pre>
-
-<p>to <tt>local.xml</tt> means we've overridden the "root" tag. with a different Block.  By placing this in the &lt;default /&gt; Handle we've ensured that this override will happen for <strong>every page request</strong> in the system.   That's probably not what we want.  </p>
-
-
-<p>If you go to any other page in your  Magento site, you'll notice they're either blank white, or have the same red background that your hello world page does.  Let's change your <tt>local.xml</tt> file so it only applies to the hello world page.  We'll do this by changing default to use the full action name handle (<tt>helloworld_index_index</tt>).</p>
-
-<pre>
-&lt;layout version="0.1.0">
-    &lt;helloworld_index_index>
-        &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
-    &lt;/helloworld_index_index>
-&lt;/layout>
-</pre>
-
-<p>Clear your Magento cache, and the rest of your pages should be restored.  </p>
-
-<p>Right now this only applies to our index Action Method.  Let's add it to the goodbye Action Method as well.  In your Action Controller, modify the goodbye action so it looks like</p>
-<pre>
-public function goodbyeAction() {
-    $this->loadLayout();
-    $this->renderLayout();
-}
-</pre>
-
-<p>If you load up the following URL, you'll notice you're still getting the default Magento layout.</p>
-
-<pre>http://example.com/helloworld/index/goodbye</pre>
-
-<p>We need to add a Handle for the full action name (<tt>helloworld_index_goodbye</tt>) to our local.xml file.  Rather than specify a new &lt;block /&gt;, lets use the update tag to include the <tt>helloworld_index_index</tt> Handle.</p>
-
-<pre>
-&lt;layout version="0.1.0">
-    &lt;!-- ... -->
-    &lt;helloworld_index_goodbye>
-        &lt;update handle="helloworld_index_index" />
-    &lt;/helloworld_index_goodbye>
-&lt;/layout>
-</pre>
-
-<p>Loading the following pages (after clearing your Magento cache) should now produce identical results.</p>
-
-<pre>http://example.com/helloworld/index/index
-http://example.com/helloworld/index/goodbye</pre>
-
-<h2>Starting Output and getChildHtml</h2>
-
-<p>In a standard configuration, output starts on the Block named root (because it has an output attribute).  We've overridden root's Template with our own</p>
-
-<pre>template="magentotutorial/helloworld/simple_page.phtml"</pre>
-
-<p>Templates are referenced from the root folder of the current theme. In this case, that's</p>
-
-<pre>app/design/frontend/base/default</pre>
-
-<p>so we need to drill down to our custom page.  Most Magento Templates are stored in </p>
-
-<pre>app/design/frontend/base/default/templates</pre>
-
-<p>Combining this gives us the full path</p>
-
-<pre>app/design/frontend/base/default/templates/magentotutorial/helloworld/simple_page.phtml</pre>
-
-<h2>Adding Content Blocks</h2>
-
-<p>A simple red page is pretty boring.  Let's add some content to this page.  Change your <tt>&lt;helloworld_index_index /&gt;</tt> Handle in local.xml so it looks like the following</p>
-
-<pre>
-&lt;helloworld_index_index>
-    &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml">
-        &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
-    &lt;/block>
-&lt;/helloworld_index_index>
-</pre>
-
-<p>We're adding a new Block nested within our root.  This is a Block that's distributed with Magento, and will display a customer registration form. By nesting this Block within our root Block, we've made it available to be pulled into our <tt>simple_page.html</tt> Template.  Next, we'll use the Block's getChildHtml method in our <tt>simple_page.phtml</tt> file.  Edit <tt>simple_page.html</tt> so it looks like this</p>
-
-<pre>
-&lt;body>
-    &lt;?php echo $this->getChildHtml('customer_form_register'); ?>
-&lt;/body>
-</pre>
-
-<p>Clear your Magento cache and reload the page and you should see the customer registration form on your red background.  Magento also has a Block named top.links.  Let's try including that.  Change your simple_page.html file so it reads</p>
-
-<pre>
-&lt;body>
-    &lt;h1>Links&lt;/h1>
-    &lt;?php echo $this->getChildHtml('top.links'); ?>
-&lt;/body>
-</pre>
-
-<p>When you reload the page, you'll notice that your &lt;h1&gt;Links&lt;/h1&gt; title is rendering, but nothing is rendering for top.links.  That's because we didn't add it to local.xml.  The <tt>getChildHtml</tt> method can only include Blocks that are specified as sub-Blocks in the Layout.  This allows Magento to only instantiate the Blocks it needs, and also allows you to set difference Templates for Blocks based on context.</p>
-
-<p>Let's add the top.links Block to our local.xml</p>
-
-<pre>
-&lt;helloworld_index_index>
-    &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml">
-        &lt;block type="page/template_links" name="top.links"/>
-        &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
-    &lt;/block>
-&lt;/helloworld_index_index>
-</pre>
-
-<p>Clear your cache and reload the page.  You should now see the top.links module.     </p>
-
-<h2>Time for action</h2>
-
-<p>There is one more important concept to cover before we wrap up this lesson, and that is the &lt;action /&gt; tag.  Using the &lt;action /&gt; tag enables us to call public PHP methods of the block classes.  So instead of changing the template of the root block by replacing the block instance with our own, we can use a call to <tt>setTemplate</tt> instead.</p>
-
-<pre>
-&lt;layout version="0.1.0">
-    &lt;helloworld_index_index>
-        &lt;reference name="root">
-            &lt;action method="setTemplate">
-                &lt;template>magentotutorial/helloworld/simple_page.phtml&lt;/template>
-            &lt;/action>
-            &lt;block type="page/template_links" name="top.links"/>
-            &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
-        &lt;/reference>
-    &lt;/helloworld_index_index>
-&lt;/layout>
-</pre>
-
-<p>This layout XML will first set the template property of the root block, and then will add the two blocks we use as child blocks. Once we clear the cache, the result should look just as before.  The benefit of using the &lt;action /&gt; is the same block instance is used that was created earlier, and all other parent/child associations still exist.  For that reason this is a more upgrade proof way of implementing our changes.</p>
-
-<p>All arguments to the action's method need to be wrapped in an individual child node of the &lt;action /&gt; tag.  The name of that node doesn't matter, only the order of the nodes.  We could have written the action node from the previous example as follows with the same effect.
-</p>
-
-<pre>
-&lt;action method="setTemplate">
-    &lt;some_new_template>magentotutorial/helloworld/simple_page.phtml&lt;/some_new_template>
-&lt;/action>
-</pre>
-
-<p>This is just to illustrate that the action's argument node names are arbitrary.</p>
-
-<h2>Wrapup</h2>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
 
-<p>That covers Layout fundamentals.  We have covered the tags &lt;block /&gt;, &lt;reference /&gt;, &lt;update /&gt; and &lt;action /&gt;, and also layout update handles like &lt;default /&gt; and &lt;cms_index_index /&gt;.  These make up most of the layout configuration used in Magento.  If you found it somewhat daunting, don't worry, you'll rarely need to work with layouts on such a fundamental level.  Magento provides a number of pre-built layouts which can be modified and skinned to meet the needs of your store. Understanding how the entire Layout system works can be a great help when you're trouble shooting Layout issues, or adding new functionality to an existing Magento system.</p>
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
\ No newline at end of file
diff --git a/guides/m1x/magefordev/mage-for-dev-5.html b/guides/m1x/magefordev/mage-for-dev-5.html
index d47c4189ec..8738ed8fe9 100644
--- a/guides/m1x/magefordev/mage-for-dev-5.html
+++ b/guides/m1x/magefordev/mage-for-dev-5.html
@@ -1,458 +1,726 @@
 ---
 ---
 <!DOCTYPE html>
-<html lang=en>
-
+<html lang="en" dir="ltr">
 <head>
-    <meta charset=utf-8>
-
-    <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
-    <link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
-    <link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <title>Magento for Developers: Part 5&mdash;Magento Models and ORM Basics</title>
-
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>OpenMage for Developers: Part 5&mdash;OpenMage Models and ORM Basics</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-
-<img src="{{ site.baseurl }}/guides/m1x/images/m1xheader.png" width="1024" alt="header" />
-{% include m1x/eol_message.html %}
-
-<div id="content">
-<h1>Magento for Developers: Part 5&mdash;Magento Models and ORM Basics</h1>
-<p><em>by Alan Storm</em>, updated for Magento 1.12</p>
-<p><a href="{{ site.m1xgithuburl }}/magefordev/mage-for-dev-5.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>
-
-
-<!-- Magento for Developers: Part 5&mdash;Magento Models and ORM Basics -->
-<!-- magento-for-dev-part-5-magento-models-and-orm-basics 
-
-<style type="text/css">
-#kb-entry .series {float: right; width: 175px; margin-left: 10px; font-size: 12px; }
-#kb-entry .series ul {margin-left: 15px;}
-</style> 
-<div class="r-box-rss series">  -->
-
-<h5>Other articles in this series:</h5>
-<ul>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-1.html">Part 1&mdash;Introduction to Magento</a></li>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-2.html">Part 2&mdash;The Magento Config</a></li>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-3.html">Part 3&mdash;Magento Controller Dispatch</a></li>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-4.html">Part 4&mdash;Magento Layouts, Blocks and Templates</a></li>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">Part 5&mdash;Magento Models and ORM Basics</a></li>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Part 6&mdash;Magento Setup Resources</a></li>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">Part 7&mdash;Advanced ORM: Entity Attribute Value</a></li>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-8.html">Part 8&mdash;Varien Data Collections</a></li>
-</ul>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
+                                    Introduction to OpenMage
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
+                                    The OpenMage Config
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
+                                    OpenMage Controller Dispatch
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
+                                    OpenMage Layouts, Blocks and Templates
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
+                                    OpenMage Models and ORM Basics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
+                                    OpenMage Setup Resources
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">
+                                    Advanced ORM: Entity Attribute Value
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-8.html">
+                                    Varien Data Collections
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">OpenMage Layouts, Blocks and Templates</h1>
+                    </section>
+                    <p class="para1">The implementation of a "Models Tier" is a huge part of any MVC framework. It
+                        represents the data of your application, and most applications are useless without data. Magento
+                        Models play an even bigger role, as they typically contain the "Business Logic" that's often
+                        relegated to the Controller or Helper methods in other PHP MVC frameworks.</p>
+                    <h2>Traditional PHP MVC Models</h2>
+                    <p>If the definition of MVC is somewhat fuzzy, the definition of a Model is even fuzzier. Prior to
+                        the wide adoption of the MVC pattern by PHP developers, data access was usually raw SQL
+                        statements and/or an SQL abstraction layer. Developers would write queries and not think too
+                        much about what objects they were modeling.</p>
+                    <p>In this day and age, raw SQL is mostly frowned upon, but many PHP frameworks are still SQL
+                        centric. Models will be objects that provide some layer of abstraction, but behind the scenes
+                        developers are still writing SQL and/or calling SQL like abstraction methods to read and
+                        write-down their data.</p>
+                    <p>Other frameworks eschew SQL and take the Object Relational Mapping (ORM) approach. Here, a
+                        developer is dealing strictly with Objects. Properties are set, and when a save method is called
+                        on the Object, the data is automatically written to the database. Some ORMs will attempt to
+                        divine object properties from the database, others require the user to specify them in some way,
+                        (usually in an abstract data language such as YAML). One of the most famous and popular
+                        implementations of this approach is ActiveRecord.</p>
+                    <p>This definition of ORM should suffice for now, but like everything Computer Science these days,
+                        the strict definition of ORM has blurred over the years. It's beyond the scope of this article
+                        to settle that dispute, but suffice it say we're generalizing a bit.</p>
+                    <h2>Magento Models</h2>
+                    <p>It should be no surprise that Magento takes the ORM approach. While the Zend Framework SQL
+                        abstractions are available, most of your data access will be via the built in Magento Models,
+                        and Models you build yourself. It should also come as no surprise that Magento has a highly
+                        flexible, highly abstract, concept of what a Model is.</p>
+                    <h3>Anatomy of a Magento Model</h3>
+                    <p>Most Magento Models can be categorized in one of two ways. There's a basic,
+                        ActiveRecord-like/one-object-one-table Model, and there's also an Entity Attribute Value (EAV)
+                        Model. Each Model also gets a Model Collection. Collections are PHP objects used to hold a
+                        number of individual Magento Model instances. The Magento team has implemented the PHP Standard
+                        Library interfaces of IteratorAggregate and Countable to allow each Model type to have it's own
+                        collection type. If you're not familiar with the PHP Standard Library, think of Model
+                        Collections as arrays that also have methods attached.</p>
+                    <p>Magento Models don't contain any code for connecting to the database. Instead, each Model uses a
+                        <tt>modelResource</tt> class, that is used to communicate with the database server (via one read
+                        and one write adapter object). By decoupling the logical Model and the code that talks to the
+                        database, it's theoretically possible to write new resource classes for a different database
+                        schemas and platforms while keeping your Models themselves untouched. </p>
+                    <h2>Enable developer mode</h2>
+                    <p>Something you should do in development&mdash;but <em>never</em> in production&mdash;is to enable
+                        Magento's <em>developer mode</em> which, among other things, displays exceptions in your
+                        browser. It's useful for debugging your code.</p>
+                    <p>Enable developer mode in any of the following ways:</p>
+                    <ul>
+                        <li>
+                            <a href="https://magento2.atlassian.net/wiki/display/m1wiki/How+to+Configure+a+Magento+1.x+Error+Page#display_errors_on_the_same_page_developer_mode">developer
+                                mode</a></li>
+                        <li>Edit the <code>.htaccess</code> in the Magento root directory file to add <code>SetEnv
+                            MAGE_IS_DEVELOPER_MODE "true"</code>
+                        </li>
+                    </ul>
+                    <h2>Creating a Basic Model</h2>
+                    <p>To begin, we're going to create a basic Magento Model. PHP MVC tradition insists we model a
+                        weblog post. The steps we'll need to take are</p>
+                    <ol>
+                        <li>Create a new "Weblog" module</li>
+                        <li>Create a database table for our Model</li>
+                        <li>Add Model information to the config for a Model named Blogpost</li>
+                        <li>Add Model Resource information to the config for the Blogpost Model</li>
+                        <li>Add a Read Adapter to the config for the Blogpost Model</li>
+                        <li>Add a Write Adapter to the config for the Blogpost Model</li>
+                        <li>Add a PHP class file for the Blogpost Model</li>
+                        <li>Add a PHP class file for the Blogpost Resource Model</li>
+                        <li>Instantiate the Model</li>
+                    </ol>
+                    <h3>Create a Weblog Module</h3>
+                    <p>You should be an old hat at creating empty modules at this point, so we'll skip the details and
+                        assume you can create an empty module named Weblog. After you've done that, we'll setup a route
+                        for an index Action Controller with an action named "testModel". As always, the following
+                        examples assume a Package Name of "Magentotutorial".</p>
+                    <p>In `Magentotutorial/Weblog/etc/config.xml`, setup the following route</p>
+                    <pre>
+                    &lt;frontend>
+                        &lt;routers>
+                            &lt;weblog>
+                                &lt;use>standard&lt;/use>
+                                &lt;args>
+                                    &lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;
+                                    &lt;frontName>weblog&lt;/frontName>
+                                &lt;/args>
+                            &lt;/weblog>
+                        &lt;/routers>
+                    &lt;/frontend>
+                    </pre>
+                    <p>And then add the following Action Controller in </p>
+                    <pre>
+                    class Magentotutorial_Weblog_IndexController extends Mage_Core_Controller_Front_Action {
+                        public function testModelAction() {
+                            echo 'Setup!';
+                        }
+                    }
+                    </pre>
+                    <p>at <tt>Magentotutorial/Weblog/controllers/IndexController.php</tt>. Clear your Magento cache and
+                        load the following URL to ensure everything's been setup correctly.</p>
+                    <pre>http://example.com/weblog/index/testModel</pre>
+                    <p>You should see the word "Setup" on a white background.</p>
+                    <h3>Creating the Database Table</h3>
+                    <p>Magento has a system for automatically creating and changing your database schemas, but for the
+                        time being we'll just manually create a table for our Model.</p>
+                    <p>Using the command-line or your favorite MySQL GUI application, create a table with the following
+                        schema</p>
+                    <pre>
+                    CREATE TABLE `blog_posts` (
+                      `blogpost_id` int(11) NOT NULL auto_increment,
+                      `title` text,
+                      `post` text,
+                      `date` datetime default NULL,
+                      `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
+                      PRIMARY KEY  (`blogpost_id`)
+                    )
+                    </pre>
+                    <p>And then populate it with some data </p>
+                    <pre>INSERT INTO `blog_posts` VALUES (1,'My New Title','This is a blog post','2010-07-01 00:00:00','2010-07-02 23:12:30');</pre>
+                    <h3>The Global Config and Creating The Model</h3>
+                    <p>There are three individual things we need to setup for a Model in our config.</p>
+                    <ol>
+                        <li>Enabling Models in our Module</li>
+                        <li>Enabling Model Resources in our Module</li>
+                        <li>Add an "entity" table configuration to our Model Resource.</li>
+                    </ol>
+                    <p>When you instantiate a Model in Magento, you make a call like this</p>
+                    <pre>$model = Mage::getModel('weblog/blogpost');</pre>
+                    <p>The first part of the URI you pass into get Model is the <a
+                            href="http://alanstorm.com/2009/img/magento-book/weblogGetModel.png">Model Group Name</a>.
+                        Because it is a good idea to follow conventions, this should be the (lowercase) name of your
+                        module, or to be safeguarded against conflicts use the packagename and modulename (also in
+                        lowercase). The second part of the URI is the lowercase version of your Model name.</p>
+                    <p>So, let's add the following XML to our module's `config.xml`.</p>
+                    <pre>
+                    &lt;global>
+                        &lt;!-- ... -->
+                        &lt;models>
+                            &lt;weblog>
+                                &lt;class>Magentotutorial_Weblog_Model&lt;/class>
+                                &lt;!--
+                                need to create our own resource, can't just
+                                use core_resource
+                                -->
+                                &lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;
+                            &lt;/weblog>
+                        &lt;/models>
+                        &lt;!-- ... -->
+                    &lt;/global>
+                    </pre>
+                    <p>The outer &lt;weblog /&gt; tag is your Group Name, which should match your module name. &lt;class
+                        /&gt; is the BASE name all Models in the weblog group will have, also called <strong>Class
+                            Prefix</strong>. The &lt;resourceModel /&gt; tag indicates which Resource Model that weblog
+                        group Models should use. We talk more about this later on in this page. For now, remember your
+                        Group Name and the literal string "resource".</p>
+                    <p>So, we're not done yet, but let's see what happens if we clear our Magento cache and attempt to
+                        instantiate a blogpost Model. In your `testModelAction` method, use the following code</p>
+                    <pre>
+                        public function testModelAction() {
+                            $blogpost = Mage::getModel('weblog/blogpost');
+                            echo get_class($blogpost);
+                        }
+                    </pre>
+                    <p>and reload your page. You should see an error like the following:</p>
+                    <pre>
+                    include(Magentotutorial/Weblog/Model/Blogpost.php) [function.include]: failed to open stream: No such file or directory
+                    </pre>
+                    <p>By attempting to retrieve a <tt>weblog/blogpost</tt> Model, you told Magento to instantiate a
+                        class with the name</p>
+                    <pre>
+                    Magentotutorial_Weblog_Model_Blogpost
+                    </pre>
+                    <p>Magento is trying to __autoload include this Model, but can't find the file. Let's create it!
+                        Create the following class at the following location</p>
+                    <pre>File: app/code/local/Magentotutorial/Weblog/Model/Blogpost.php</pre>
+                    <pre>
+                    class Magentotutorial_Weblog_Model_Blogpost extends Mage_Core_Model_Abstract
+                    {
+                        protected function _construct()
+                        {
+                            $this->_init('weblog/blogpost');
+                        }
+                    }
+                    </pre>
+                    <p>Reload your page, and the exception should be replaced with the name of your class. </p>
+                    <p>All basic Models that interact with the database should extend the
+                        <tt>Mage_Core_Model_Abstract</tt> class. This abstract class forces you to implement a single
+                        method named <tt>_construct</tt> (<strong>NOTE:</strong> this is not PHP's constructor <tt>__construct</tt>).
+                        This method should call the class's _init method with the same identifying URI you'll be using
+                        in the <tt>Mage::getModel</tt> method call.</p>
+                    <h3>The Global Config and Resources</h3>
+                    <p>So, we've setup our Model. Next, we need to setup our Model Resource. Model Resources contain the
+                        code that actually talks to our database. In the last section, we included the following in our
+                        config.</p>
+                    <pre>
+                    &lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;
+                    </pre>
+                    <p>The value in &lt;resourceModel /&gt; will be used to instantiate a Model Resource class. Although
+                        you'll never need to call it yourself, when any Model in the weblog group needs to talk to the
+                        database, Magento will make the following method call to get the Model resource</p>
+                    <pre>
+                    Mage::getResourceModel('weblog/blogpost');
+                    </pre>
+                    <p>Again, weblog is the Group Name, and blogpost is the Model. The <tt>Mage::getResourceModel</tt>
+                        method will use the <tt>weblog/blogpost</tt> URI to inspect the global config and pull out the
+                        value in &lt;resourceModel&gt; (in this case, <tt>weblog_resource</tt>). Then, a model class
+                        will be instantiated with the following URI</p>
+                    <pre>
+                    weblog_resource/blogpost
+                    </pre>
+                    <p>So, if you followed that all the way, what this means is, <strong>resource models are configured
+                        in the same section of the XML config as normal Models</strong>. This can be confusing to
+                        newcomers and old-hands alike.</p>
+                    <p>So, with that in mind, let's configure our resource. In our &lt;models&gt; section add</p>
+                    <pre>
+                    &lt;global>
+                        &lt;!-- ... -->
+                        &lt;models>
+                            &lt;!-- ... -->
+                            &lt;weblog_resource>
+                                &lt;class>Magentotutorial_Weblog_Model_Resource&lt;/class>
+                            &lt;/weblog_resource>
+                        &lt;/models>
+                    &lt;/global>
+                    </pre>
+                    <p>You're adding the &lt;weblog_resource /&gt; tag, which is the value of the &lt;resourceModel /&gt;
+                        tag you just setup. The value of &lt;class /&gt; is the base name that all your resource models
+                        will have, and should be named with the following format</p>
+                    <pre>
+                    Packagename_Modulename_Model_Resource
+                    </pre>
+                    <p>So, we have a configured resource, let's try loading up some Model data. Change your action to
+                        look like the following</p>
+                    <pre>
+                    public function testModelAction() {
+                        $params = $this->getRequest()->getParams();
+                        $blogpost = Mage::getModel('weblog/blogpost');
+                        echo("Loading the blogpost with an ID of ".$params['id']);
+                        $blogpost->load($params['id']);
+                        $data = $blogpost->getData();
+                        var_dump($data);
+                    }
+                    </pre>
+                    <p>And then load the following URL in your browser (after clearing your Magento cache)</p>
+                    <pre>http://example.com/weblog/index/testModel/id/1</pre>
+                    <p>You should see an exception something like the following</p>
+                    <pre>Warning: include(Magentotutorial/Weblog/Model/Resource/Blogpost.php) [function.include]: failed to open stream: No such file ....</pre>
+                    <p>As you've likely intuited, we need to add a resource class for our Model. <strong>Every</strong>
+                        Model has its own resource class. Add the following class at the following location</p>
+                    <pre>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Blogpost.php</pre>
+                    <pre>
+                    class Magentotutorial_Weblog_Model_Resource_Blogpost extends Mage_Core_Model_Resource_Db_Abstract{
+                        protected function _construct()
+                        {
+                            $this->_init('weblog/blogpost', 'blogpost_id');
+                        }
+                    }
+                    </pre>
+                    <p>Again, the first parameter of the init method is the URL used to identify the
+                        <strong>Model</strong>. The second parameter is the database field that uniquely identifies any
+                        particular column. In most cases, this should be the primary key. Clear your cache, reload, and
+                        you should see</p>
+                    <pre>Can't retrieve entity config: weblog/blogpost</pre>
+                    <p>Another exception! When we use the Model URI <tt>weblog/blogpost</tt>, we're telling Magento we
+                        want the Model Group <tt>weblog</tt>, and the <tt>blogpost</tt> <em>Entity</em>. In the context
+                        of simple Models that extend <tt>Mage_Core_Model_Resource_Db_Abstract</tt>, an entity
+                        corresponds to a table. In this case, the table named <tt>blog_post</tt> that we created above.
+                        Let's add that entity to our XML config.</p>
+                    <pre>
+                        &lt;models>
+                            &lt;!-- ... --->
+                            &lt;weblog_resource>
+                                &lt;class>Magentotutorial_Weblog_Model_Resource&lt;/class>
+                                &lt;entities>
+                                    &lt;blogpost>
+                                        &lt;table>blog_posts&lt;/table>
+                                    &lt;/blogpost>
+                                &lt;/entities>
+                            &lt;/weblog_resource>
+                        &lt;/models>
+                    </pre>
+                    <p>We've added a new &lt;entities /&gt; section to the resource Model section of our config. This,
+                        in turn, has a section named after our entity (&lt;blogpost /&gt;) that specifies the name of
+                        the database table we want to use for this Model.</p>
+                    <p>Clear your Magento cache, cross your fingers, reload the page and ...</p>
+                    <pre>Loading the blogpost with an ID of 1
+
+                    array
+                      'blogpost_id' => string '1' (length=1)
+                      'title' => string 'My New Title' (length=12)
+                      'post' => string 'This is a blog post' (length=19)
+                      'date' => string '2009-07-01 00:00:00' (length=19)
+                      'timestamp' => string '2009-07-02 16:12:30' (length=19)
+                    </pre>
+                    <p>Eureka! We've managed to extract our data and, more importantly, completely configure a Magento
+                        Model.</p>
+                    <h2>Basic Model Operations</h2>
+                    <p>All Magento Models inherit from the Varien_Object class. This class is part of the Magento system
+                        library and <strong>not</strong> part of any Magento core module. You can find this object at
+                    </p>
+                    <pre>lib/Varien/Object.php</pre>
+                    <p>Magento Models store their data in a protected _data property. The Varien_Object class gives us
+                        several methods we can use to extract this data. You've already seen <tt>getData</tt>, which
+                        will return an array of key/value pairs. This method can also be passed a string key to get a
+                        specific field.</p>
+                    <pre>
+                    $model->getData();
+                    $model->getData('title');
+                    </pre>
+                    <p>There's also a getOrigData method, which will return the Model data as it was when the object was
+                        initially populated, (working with the protected _origData method).</p>
+                    <pre>
+                    $model->getOrigData();
+                    $model->getOrigData('title');
+                    </pre>
+                    <p>The Varien_Object also implements some special methods via PHP's magic <tt>__call</tt> method.
+                        You can get, set, unset, or check for the existence of any property using a method that begins
+                        with the word get, set, unset or has and is followed by the camel cased name of a property.</p>
+                    <pre>
+                    $model->getBlogpostId();
+                    $model->setBlogpostId(25);
+                    $model->unsBlogpostId();
+                    if($model->hasBlogpostId()){...}
+                    </pre>
+                    <p>For this reason, you'll want to name all your database columns with lower case characters and use
+                        underscores to separate characters. </p>
+                    <h2>CRUD, the Magento Way</h2>
+                    <p>Magento Models support the basic Create, Read, Update, and Delete functionality of CRUD with <tt>load</tt>,
+                        <tt>save</tt>, and <tt>delete</tt> methods. You've already seen the load method in action. When
+                        passed a single parameter, the load method will return a record whose id field (set in the
+                        Model's resource) matches the passed in value.</p>
+                    <pre>$blogpost-&gt;load(1);</pre>
+                    <p>The save method will allow you to both INSERT a new Model into the database, or UPDATE an
+                        existing one. Add the following method to your Controller</p>
+                    <pre>
+                    public function createNewPostAction() {
+                        $blogpost = Mage::getModel('weblog/blogpost');
+                        $blogpost->setTitle('Code Post!');
+                        $blogpost->setPost('This post was created from code!');
+                        $blogpost->save();
+                        echo 'post with ID ' . $blogpost->getId() . ' created';
+                    }
+                    </pre>
+                    <p>and then execute your Controller Action by loading the following URL</p>
+                    <pre>http://example.com/weblog/index/createNewPost</pre>
+                    <p>You should now see an additional saved post in your database table. Next, try the following to
+                        edit your post</p>
+                    <pre>
+                    public function editFirstPostAction() {
+                        $blogpost = Mage::getModel('weblog/blogpost');
+                        $blogpost->load(1);
+                        $blogpost->setTitle("The First post!");
+                        $blogpost->save();
+                        echo 'post edited';
+                    }
+                    </pre>
+                    <p>And finally, you can delete your post using very similar syntax.</p>
+                    <pre>
+                    public function deleteFirstPostAction() {
+                        $blogpost = Mage::getModel('weblog/blogpost');
+                        $blogpost->load(1);
+                        $blogpost->delete();
+                        echo 'post removed';
+                    }
+                    </pre>
+                    <h2>Model Collections</h2>
+                    <p>So, having a single Model is useful, but sometimes we want to grab list of Models. Rather than
+                        returning a simple array of Models, each Magento Model type has a unique collection object
+                        associated with it. These objects implement the PHP IteratorAggregate and Countable interfaces,
+                        which means they can be passed to the <tt>count</tt> function, and used in <tt>for each</tt>
+                        constructs.</p>
+                    <p>We'll cover Collections in full in a later article, but for now let's look at basic setup and
+                        usage. Add the following action method to your Controller, and load it in your browser.</p>
+                    <pre>
+                    public function showAllBlogPostsAction() {
+                        $posts = Mage::getModel('weblog/blogpost')->getCollection();
+                        foreach($posts as $blogpost){
+                            echo '&lt;h3>'.$blogpost->getTitle().'&lt;/h3>';
+                            echo nl2br($blogpost->getPost());
+                        }
+                    }
+                    </pre>
+                    <p>Load the action URL, </p>
+                    <pre>http://example.com/weblog/index/showAllBlogPosts</pre>
+                    <p>and you should see a (by now) familiar exception.</p>
+                    <pre>Warning: include(Magentotutorial/Weblog/Model/Resource/Blogpost/Collection.php) [function.include]: failed to open stream</pre>
+                    <p>You're not surprised, are you? We need to add a PHP class file that defines our Blogpost
+                        collection. Every Model has a protected property named <tt>_resourceCollectionName</tt> that
+                        contains a URI that's used to identify our collection.</p>
+                    <pre>
+                      protected '_resourceCollectionName' =&gt; string 'weblog/blogpost_collection'
+                    </pre>
+                    <p>By default, this is the same URI that's used to identify our Resource Model, with the string
+                        "_collection" appended to the end. Magento considers Collections part of the Resource, so this
+                        URI is converted into the class name.</p>
+                    <pre>Magentotutorial_Weblog_Model_Resource_Blogpost_Collection</pre>
+                    <p>Add the following PHP class at the following location</p>
+                    <pre>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Blogpost/Collection.php</pre>
+                    <pre>
+                    class Magentotutorial_Weblog_Model_Resource_Blogpost_Collection extends Mage_Core_Model_Resource_Db_Collection_Abstract {
+                        protected function _construct()
+                        {
+                                $this->_init('weblog/blogpost');
+                        }
+                    }
+                    </pre>
+                    <p>Just as with our other classes, we need to init our Collection with the Model URI.
+                        (weblog/blogpost). Rerun your Controller Action, and you should see your post information.</p>
+                    <h2>Wrapup</h2>
+                    <p>Congratulations, you've created and configured your first Magento Model. In a later article we'll
+                        take a look at Magento's Entity Attribute Value Models (EAV), which expand on what we've learned
+                        here.</p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
 </div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
 
-<p class="para1">The implementation of a "Models Tier" is a huge part of any MVC framework. It represents the data of your application, and most applications are useless without data. Magento Models play an even bigger role, as they typically contain the "Business Logic" that's often relegated to the Controller or Helper methods in other PHP MVC frameworks.</p>
-
-<h2>Traditional PHP MVC Models</h2>
-
-<p>If the definition of MVC is somewhat fuzzy, the definition of a Model is even fuzzier. Prior to the wide adoption of the MVC pattern by PHP developers, data access was usually raw SQL statements and/or an SQL abstraction layer. Developers would write queries and not think too much about what objects they were modeling.</p>
-
-<p>In this day and age, raw SQL is mostly frowned upon, but many PHP frameworks are still SQL centric. Models will be objects that provide some layer of abstraction, but behind the scenes developers are still writing SQL and/or calling SQL like abstraction methods to read and write-down their data.</p>
-
-<p>Other frameworks eschew SQL and take the Object Relational Mapping (ORM) approach. Here, a developer is dealing strictly with Objects. Properties are set, and when a save method is called on the Object, the data is automatically written to the database. Some ORMs will attempt to divine object properties from the database, others require the user to specify them in some way, (usually in an abstract data language such as YAML). One of the most famous and popular implementations of this approach is ActiveRecord.</p>
-
-<p>This definition of ORM should suffice for now, but like everything Computer Science these days, the strict definition of ORM has blurred over the years. It's beyond the scope of this article to settle that dispute, but suffice it say we're generalizing a bit.</p>
-
-<h2>Magento Models</h2>
-
-<p>It should be no surprise that Magento takes the ORM approach. While the Zend Framework SQL abstractions are available, most of your data access will be via the built in Magento Models, and Models you build yourself. It should also come as no surprise that Magento has a highly flexible, highly abstract, concept of what a Model is.</p>
-
-<h3>Anatomy of a Magento Model</h3>
-
-<p>Most Magento Models can be categorized in one of two ways. There's a basic, ActiveRecord-like/one-object-one-table Model, and there's also an Entity Attribute Value (EAV) Model. Each Model also gets a Model Collection. Collections are PHP objects used to hold a number of individual Magento Model instances. The Magento team has implemented the PHP Standard Library interfaces of IteratorAggregate and Countable to allow each Model type to have it's own collection type. If you're not familiar with the PHP Standard Library, think of Model Collections as arrays that also have methods attached.</p>
-
-<p>Magento Models don't contain any code for connecting to the database. Instead, each Model uses a <tt>modelResource</tt> class, that is used to communicate with the database server (via one read and one write adapter object). By decoupling the logical Model and the code that talks to the database, it's theoretically possible to write new resource classes for a different database schemas and platforms while keeping your Models themselves untouched. </p>
-
-<h2>Enable developer mode</h2>
-<p>Something you should do in development&mdash;but <em>never</em> in production&mdash;is to enable Magento's <em>developer mode</em> which, among other things, displays exceptions in your browser. It's useful for debugging your code.</p>
-<p>Enable developer mode in any of the following ways:</p>
-<ul><li><a href="https://magento2.atlassian.net/wiki/display/m1wiki/How+to+Configure+a+Magento+1.x+Error+Page#display_errors_on_the_same_page_developer_mode">developer mode</a></li>
-    <li>Edit the <code>.htaccess</code> in the Magento root directory file to add <code>SetEnv MAGE_IS_DEVELOPER_MODE "true"</code></li>
-</ul>
-<h2>Creating a Basic Model</h2>
-
-<p>To begin, we're going to create a basic Magento Model. PHP MVC tradition insists we model a weblog post. The steps we'll need to take are</p>
-
-<ol>
-<li>Create a new "Weblog" module</li>
-<li>Create a database table for our Model</li>
-<li>Add Model information to the config for a Model named Blogpost</li>
-<li>Add Model Resource information to the config for the Blogpost Model</li>
-<li>Add a Read Adapter to the config for the Blogpost Model</li>
-<li>Add a Write Adapter to the config for the Blogpost Model</li>
-<li>Add a PHP class file for the Blogpost Model</li>
-<li>Add a PHP class file for the Blogpost Resource Model</li>
-<li>Instantiate the Model</li>
-</ol>
-
-<h3>Create a Weblog Module</h3>
-
-<p>You should be an old hat at creating empty modules at this point, so we'll skip the details and assume you can create an empty module named Weblog. After you've done that, we'll setup a route for an index Action Controller with an action named "testModel". As always, the following examples assume a Package Name of "Magentotutorial".</p>
-
-<p>In `Magentotutorial/Weblog/etc/config.xml`, setup the following route</p>
-
-<pre>
-&lt;frontend>
-    &lt;routers>
-        &lt;weblog>
-            &lt;use>standard&lt;/use>
-            &lt;args>
-                &lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;
-                &lt;frontName>weblog&lt;/frontName>
-            &lt;/args>
-        &lt;/weblog>
-    &lt;/routers>
-&lt;/frontend>
-</pre>
-
-<p>And then add the following Action Controller in </p>
-<pre>
-class Magentotutorial_Weblog_IndexController extends Mage_Core_Controller_Front_Action {
-    public function testModelAction() {
-        echo 'Setup!';
-    }
-}
-</pre>
-
-<p>at <tt>Magentotutorial/Weblog/controllers/IndexController.php</tt>. Clear your Magento cache and load the following URL to ensure everything's been setup correctly.</p>
-
-<pre>http://example.com/weblog/index/testModel</pre>
-
-<p>You should see the word "Setup" on a white background.</p>
-
-<h3>Creating the Database Table</h3>
-
-<p>Magento has a system for automatically creating and changing your database schemas, but for the time being we'll just manually create a table for our Model.</p>
-
-<p>Using the command-line or your favorite MySQL GUI application, create a table with the following schema</p>
-<pre>
-CREATE TABLE `blog_posts` (
-  `blogpost_id` int(11) NOT NULL auto_increment,
-  `title` text,
-  `post` text,
-  `date` datetime default NULL,
-  `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
-  PRIMARY KEY  (`blogpost_id`)
-)
-</pre>
-
-<p>And then populate it with some data </p>
-
-<pre>INSERT INTO `blog_posts` VALUES (1,'My New Title','This is a blog post','2010-07-01 00:00:00','2010-07-02 23:12:30');</pre>
-
-<h3>The Global Config and Creating The Model</h3>
-
-<p>There are three individual things we need to setup for a Model in our config.</p>
-
-<ol>
-<li>Enabling Models in our Module</li>
-<li>Enabling Model Resources in our Module</li>
-<li>Add an "entity" table configuration to our Model Resource.</li>
-</ol>
-
-<p>When you instantiate a Model in Magento, you make a call like this</p>
-
-<pre>$model = Mage::getModel('weblog/blogpost');</pre>
-
-<p>The first part of the URI you pass into get Model is the <a href="http://alanstorm.com/2009/img/magento-book/weblogGetModel.png">Model Group Name</a>. Because it is a good idea to follow conventions, this should be the (lowercase) name of your module, or to be safeguarded against conflicts use the packagename and modulename (also in lowercase). The second part of the URI is the lowercase version of your Model name.</p>
-
-<p>So, let's add the following XML to our module's `config.xml`.</p>
-<pre>
-&lt;global>
-    &lt;!-- ... -->
-    &lt;models>
-        &lt;weblog>
-            &lt;class>Magentotutorial_Weblog_Model&lt;/class>
-            &lt;!--
-            need to create our own resource, can't just
-            use core_resource
-            -->
-            &lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;
-        &lt;/weblog>
-    &lt;/models>
-    &lt;!-- ... -->
-&lt;/global>
-</pre>
-
-<p>The outer &lt;weblog /&gt; tag is your Group Name, which should match your module name. &lt;class /&gt; is the BASE name all Models in the weblog group will have, also called <strong>Class Prefix</strong>. The &lt;resourceModel /&gt; tag indicates which Resource Model that weblog group Models should use. We talk more about this later on in this page. For now, remember your Group Name and the literal string "resource".</p>
-
-<p>So, we're not done yet, but let's see what happens if we clear our Magento cache and attempt to instantiate a blogpost Model. In your `testModelAction` method, use the following code</p>
-<pre>
-    public function testModelAction() {
-        $blogpost = Mage::getModel('weblog/blogpost');
-        echo get_class($blogpost);
-    }
-</pre>
-
-<p>and reload your page. You should see an error like the following:</p>
-
-<pre>
-include(Magentotutorial/Weblog/Model/Blogpost.php) [function.include]: failed to open stream: No such file or directory
-</pre>
-
-<p>By attempting to retrieve a <tt>weblog/blogpost</tt> Model, you told Magento to instantiate a class with the name</p>
-
-<pre>
-Magentotutorial_Weblog_Model_Blogpost
-</pre>
-
-<p>Magento is trying to __autoload include this Model, but can't find the file. Let's create it! Create the following class at the following location</p>
-
-<pre>File: app/code/local/Magentotutorial/Weblog/Model/Blogpost.php</pre>
-<pre>
-class Magentotutorial_Weblog_Model_Blogpost extends Mage_Core_Model_Abstract
-{
-    protected function _construct()
-    {
-        $this->_init('weblog/blogpost');
-    }
-}
-</pre>
-
-<p>Reload your page, and the exception should be replaced with the name of your class. </p>
-
-<p>All basic Models that interact with the database should extend the <tt>Mage_Core_Model_Abstract</tt> class. This abstract class forces you to implement a single method named <tt>_construct</tt> (<strong>NOTE:</strong> this is not PHP's constructor <tt>__construct</tt>). This method should call the class's _init method with the same identifying URI you'll be using in the <tt>Mage::getModel</tt> method call.</p>
-
-<h3>The Global Config and Resources</h3>
-
-<p>So, we've setup our Model. Next, we need to setup our Model Resource. Model Resources contain the code that actually talks to our database. In the last section, we included the following in our config.</p>
-
-<pre>
-&lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;
-</pre>
-
-<p>The value in &lt;resourceModel /&gt; will be used to instantiate a Model Resource class. Although you'll never need to call it yourself, when any Model in the weblog group needs to talk to the database, Magento will make the following method call to get the Model resource</p>
-
-<pre>
-Mage::getResourceModel('weblog/blogpost');
-</pre>
-
-<p>Again, weblog is the Group Name, and blogpost is the Model. The <tt>Mage::getResourceModel</tt> method will use the <tt>weblog/blogpost</tt> URI to inspect the global config and pull out the value in &lt;resourceModel&gt; (in this case, <tt>weblog_resource</tt>). Then, a model class will be instantiated with the following URI</p>
-
-<pre>
-weblog_resource/blogpost
-</pre>
-
-<p>So, if you followed that all the way, what this means is, <strong>resource models are configured in the same section of the XML config as normal Models</strong>. This can be confusing to newcomers and old-hands alike.</p>
-
-<p>So, with that in mind, let's configure our resource. In our &lt;models&gt; section add</p>
-
-<pre>
-&lt;global>
-    &lt;!-- ... -->
-    &lt;models>
-        &lt;!-- ... -->
-        &lt;weblog_resource>
-            &lt;class>Magentotutorial_Weblog_Model_Resource&lt;/class>
-        &lt;/weblog_resource>
-    &lt;/models>
-&lt;/global>
-</pre>
-
-<p>You're adding the &lt;weblog_resource /&gt; tag, which is the value of the &lt;resourceModel /&gt; tag you just setup. The value of &lt;class /&gt; is the base name that all your resource models will have, and should be named with the following format</p>
-
-<pre>
-Packagename_Modulename_Model_Resource
-</pre>
-
-<p>So, we have a configured resource, let's try loading up some Model data. Change your action to look like the following</p>
-
-<pre>
-public function testModelAction() {
-    $params = $this->getRequest()->getParams();
-    $blogpost = Mage::getModel('weblog/blogpost');
-    echo("Loading the blogpost with an ID of ".$params['id']);
-    $blogpost->load($params['id']);
-    $data = $blogpost->getData();
-    var_dump($data);
-}
-</pre>
-
-<p>And then load the following URL in your browser (after clearing your Magento cache)</p>
-
-<pre>http://example.com/weblog/index/testModel/id/1</pre>
-
-<p>You should see an exception something like the following</p>
-
-<pre>Warning: include(Magentotutorial/Weblog/Model/Resource/Blogpost.php) [function.include]: failed to open stream: No such file ....</pre>
-
-<p>As you've likely intuited, we need to add a resource class for our Model. <strong>Every</strong> Model has its own resource class. Add the following class at the following location</p>
-
-<pre>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Blogpost.php</pre>
-<pre>
-class Magentotutorial_Weblog_Model_Resource_Blogpost extends Mage_Core_Model_Resource_Db_Abstract{
-    protected function _construct()
-    {
-        $this->_init('weblog/blogpost', 'blogpost_id');
-    }
-}
-</pre>
-
-<p>Again, the first parameter of the init method is the URL used to identify the <strong>Model</strong>. The second parameter is the database field that uniquely identifies any particular column. In most cases, this should be the primary key. Clear your cache, reload, and you should see</p>
-
-<pre>Can't retrieve entity config: weblog/blogpost</pre>
-
-<p>Another exception! When we use the Model URI <tt>weblog/blogpost</tt>, we're telling Magento we want the Model Group <tt>weblog</tt>, and the <tt>blogpost</tt> <em>Entity</em>. In the context of simple Models that extend <tt>Mage_Core_Model_Resource_Db_Abstract</tt>, an entity corresponds to a table. In this case, the table named <tt>blog_post</tt> that we created above. Let's add that entity to our XML config.</p>
-
-<pre>
-    &lt;models>
-        &lt;!-- ... --->
-        &lt;weblog_resource>
-            &lt;class>Magentotutorial_Weblog_Model_Resource&lt;/class>
-            &lt;entities>
-                &lt;blogpost>
-                    &lt;table>blog_posts&lt;/table>
-                &lt;/blogpost>
-            &lt;/entities>
-        &lt;/weblog_resource>
-    &lt;/models>
-</pre>
-
-<p>We've added a new &lt;entities /&gt; section to the resource Model section of our config. This, in turn, has a section named after our entity (&lt;blogpost /&gt;) that specifies the name of the database table we want to use for this Model.</p>
-
-<p>Clear your Magento cache, cross your fingers, reload the page and ...</p>
-
-<pre>Loading the blogpost with an ID of 1
-
-array
-  'blogpost_id' => string '1' (length=1)
-  'title' => string 'My New Title' (length=12)
-  'post' => string 'This is a blog post' (length=19)
-  'date' => string '2009-07-01 00:00:00' (length=19)
-  'timestamp' => string '2009-07-02 16:12:30' (length=19)
-</pre>
-
-<p>Eureka! We've managed to extract our data and, more importantly, completely configure a Magento Model.</p>
-
-<h2>Basic Model Operations</h2>
-
-<p>All Magento Models inherit from the Varien_Object class. This class is part of the Magento system library and <strong>not</strong> part of any Magento core module. You can find this object at</p>
-
-<pre>lib/Varien/Object.php</pre>
-
-<p>Magento Models store their data in a protected _data property. The Varien_Object class gives us several methods we can use to extract this data. You've already seen <tt>getData</tt>, which will return an array of key/value pairs. This method can also be passed a string key to get a specific field.</p>
-
-<pre>
-$model->getData();
-$model->getData('title');
-</pre>
-
-<p>There's also a getOrigData method, which will return the Model data as it was when the object was initially populated, (working with the protected _origData method).</p>
-
-<pre>
-$model->getOrigData();
-$model->getOrigData('title');
-</pre>
-
-<p>The Varien_Object also implements some special methods via PHP's magic <tt>__call</tt> method. You can get, set, unset, or check for the existence of any property using a method that begins with the word get, set, unset or has and is followed by the camel cased name of a property.</p>
-
-<pre>
-$model->getBlogpostId();
-$model->setBlogpostId(25);
-$model->unsBlogpostId();
-if($model->hasBlogpostId()){...}
-</pre>
-
-<p>For this reason, you'll want to name all your database columns with lower case characters and use underscores to separate characters. </p>
-
-<h2>CRUD, the Magento Way</h2>
-
-<p>Magento Models support the basic Create, Read, Update, and Delete functionality of CRUD with <tt>load</tt>, <tt>save</tt>, and <tt>delete</tt> methods. You've already seen the load method in action. When passed a single parameter, the load method will return a record whose id field (set in the Model's resource) matches the passed in value.</p>
-
-<pre>$blogpost-&gt;load(1);</pre>
-
-<p>The save method will allow you to both INSERT a new Model into the database, or UPDATE an existing one. Add the following method to your Controller</p>
-
-<pre>
-public function createNewPostAction() {
-    $blogpost = Mage::getModel('weblog/blogpost');
-    $blogpost->setTitle('Code Post!');
-    $blogpost->setPost('This post was created from code!');
-    $blogpost->save();
-    echo 'post with ID ' . $blogpost->getId() . ' created';
-}
-</pre>
-
-<p>and then execute your Controller Action by loading the following URL</p>
-
-<pre>http://example.com/weblog/index/createNewPost</pre>
-
-<p>You should now see an additional saved post in your database table. Next, try the following to edit your post</p>
-
-<pre>
-public function editFirstPostAction() {
-    $blogpost = Mage::getModel('weblog/blogpost');
-    $blogpost->load(1);
-    $blogpost->setTitle("The First post!");
-    $blogpost->save();
-    echo 'post edited';
-}
-</pre>
-
-<p>And finally, you can delete your post using very similar syntax.</p>
-
-<pre>
-public function deleteFirstPostAction() {
-    $blogpost = Mage::getModel('weblog/blogpost');
-    $blogpost->load(1);
-    $blogpost->delete();
-    echo 'post removed';
-}
-</pre>
-
-<h2>Model Collections</h2>
-
-<p>So, having a single Model is useful, but sometimes we want to grab list of Models. Rather than returning a simple array of Models, each Magento Model type has a unique collection object associated with it. These objects implement the PHP IteratorAggregate and Countable interfaces, which means they can be passed to the <tt>count</tt> function, and used in <tt>for each</tt> constructs.</p>
-
-<p>We'll cover Collections in full in a later article, but for now let's look at basic setup and usage. Add the following action method to your Controller, and load it in your browser.</p>
-
-<pre>
-public function showAllBlogPostsAction() {
-    $posts = Mage::getModel('weblog/blogpost')->getCollection();
-    foreach($posts as $blogpost){
-        echo '&lt;h3>'.$blogpost->getTitle().'&lt;/h3>';
-        echo nl2br($blogpost->getPost());
-    }
-}
-</pre>
-
-<p>Load the action URL, </p>
-
-<pre>http://example.com/weblog/index/showAllBlogPosts</pre>
-
-<p>and you should see a (by now) familiar exception.</p>
-
-<pre>Warning: include(Magentotutorial/Weblog/Model/Resource/Blogpost/Collection.php) [function.include]: failed to open stream</pre>
-
-<p>You're not surprised, are you? We need to add a PHP class file that defines our Blogpost collection. Every Model has a protected property named <tt>_resourceCollectionName</tt> that contains a URI that's used to identify our collection.</p>
-
-<pre>
-  protected '_resourceCollectionName' =&gt; string 'weblog/blogpost_collection'
-</pre>
-
-<p>By default, this is the same URI that's used to identify our Resource Model, with the string "_collection" appended to the end. Magento considers Collections part of the Resource, so this URI is converted into the class name.</p>
-
-<pre>Magentotutorial_Weblog_Model_Resource_Blogpost_Collection</pre>
-
-<p>Add the following PHP class at the following location</p>
-<pre>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Blogpost/Collection.php</pre>
-<pre>
-class Magentotutorial_Weblog_Model_Resource_Blogpost_Collection extends Mage_Core_Model_Resource_Db_Collection_Abstract {
-    protected function _construct()
-    {
-            $this->_init('weblog/blogpost');
-    }
-}
-</pre>
-
-<p>Just as with our other classes, we need to init our Collection with the Model URI. (weblog/blogpost). Rerun your Controller Action, and you should see your post information.</p>
-
-<h2>Wrapup</h2>
-
-<p>Congratulations, you've created and configured your first Magento Model. In a later article we'll take a look at Magento's Entity Attribute Value Models (EAV), which expand on what we've learned here.</p>
-
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
 </html>
\ No newline at end of file
diff --git a/guides/m1x/magefordev/mage-for-dev-6.html b/guides/m1x/magefordev/mage-for-dev-6.html
index bb1fbea0bb..157cf863c7 100644
--- a/guides/m1x/magefordev/mage-for-dev-6.html
+++ b/guides/m1x/magefordev/mage-for-dev-6.html
@@ -1,408 +1,693 @@
 ---
 ---
 <!DOCTYPE html>
-<html lang=en>
-
+<html lang="en" dir="ltr">
 <head>
-    <meta charset=utf-8>
-
-    <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
-    <link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
-    <link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <title>Magento for Developers: Part 6&mdash;Magento Setup Resources</title>
-
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>OpenMage for Developers: Part 6&mdash;OpenMage Setup Resources</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-
-<img src="{{ site.baseurl }}/guides/m1x/images/m1xheader.png" width="1024" alt="header" />
-{% include m1x/eol_message.html %}
-
-<div id="content">
-<h1>Magento for Developers: Part 6&mdash;Magento Setup Resources</h1>
-<p><em>by Alan Storm</em>, updated for Magento 1.12</p>
-<p><a href="{{ site.m1xgithuburl }}/magefordev/mage-for-dev-6.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>
-
-
-<!-- Magento for Developers: Part 6&mdash;Magento Setup Resources -->
-<!-- magento-for-dev-part-6-magento-setup-resources
-
-<style type="text/css">
-#kb-entry .series {float: right; width: 175px; margin-left: 10px; font-size: 12px; }
-#kb-entry .series ul {margin-left: 15px;}
-</style> 
-<div class="r-box-rss series">  -->
-
-<h5>Other articles in this series:</h5>
-<ul>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-1.html">Part 1&mdash;Introduction to Magento</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-2.html">Part 2&mdash;The Magento Config</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-3.html">Part 3&mdash;Magento Controller Dispatch</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-4.html">Part 4&mdash;Magento Layouts, Blocks and Templates</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">Part 5&mdash;Magento Models and ORM Basics</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Part 6&mdash;Magento Setup Resources</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">Part 7&mdash;Advanced ORM: Entity Attribute Value</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-8.html">Part 8&mdash;Varien Data Collections</a>
-</ul>
-
-
-<p class="para1">On any fast paced software development project, the task of keeping the development and production databases in sync become a sticky wicket. Magento offers a system to create versioned resource migration scripts that can help your team deal with this often contentious part of the development process.</p>
-
-<p><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">In the ORM article</a> we created a model for a weblog post.  At the time, we ran our <tt>CREATE TABLE</tt> statements directly against the database.  This time, we'll create a Setup Resource for our module that will create the table for us.  We'll also create an upgrade script for our module that will update an already installed module.  The steps we'll need to take are</p>
-
-<ol>
-<li>Add the Setup Resource to our config</li>
-<li>Create our resource class file</li>
-<li>Create our installer script</li>
-<li>Create our upgrade script</li>
-</ol>
-<br clear="all">
-
-<h2>Adding the Setup Resource</h2>
-<p>So, let's continue with the weblog module <a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">we created last time</a>.  In our &lt;global /&gt; section, add the following</p>
-
-<pre>
-&lt;global>
-    &lt;!-- ... -->
-    &lt;resources>
-        &lt;weblog_setup>
-            &lt;setup>
-                &lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;
-                &lt;class>Magentotutorial_Weblog_Model_Resource_Setup&lt;/class>
-            &lt;/setup>
-        &lt;/weblog_setup>
-    &lt;/resources>
-    &lt;!-- ... -->
-&lt;/global>
-</pre>
-
-<p>The <tt>&lt;weblog_setup&gt;</tt> tag will be used to uniquely identify this Setup Resource.  It's encouraged, but not necessary, that you use the <tt>modelname_setup</tt> naming convention.  The <tt>&lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;</tt> tag block should contain the <tt>Packagename_Modulename</tt> of your module.  Finally, <tt>&lt;class&gt;Magentotutorial_Weblog_Model_Resource_Setup&lt;/class&gt;</tt> should contain the name of the class we'll be creating for our Setup Resource.  For basic setup scripts it's not necessary to create a custom class, but by doing it now you'll give yourself more flexibility down the line.</p>
-
-<p>After adding the above section to your config, clear your Magento cache and try to load any page of your Magento site.  You'll see an exception something like</p>
-
-<pre>Fatal error: Class 'Magentotutorial_Weblog_Model_Resource_Setup' not found in</pre>
-
-<p>Magento just tried to instantiate the class you specified in your config, but couldn't find it.  You'll want to create the following file, with the following contents.</p>
-
-<p>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Setup.php</p>
-<pre>
-class Magentotutorial_Weblog_Model_Resource_Setup extends Mage_Core_Model_Resource_Setup {
-}
-</pre>
-
-<p>Now, reload any page of your Magento site.  The exception should be gone, and your page should load as expected.</p>
-
-<h2>Creating our Installer Script</h2>
-
-<p>Next, we'll want to create our installer script.  This is the script that will contain any <tt>CREATE TABLE</tt> or other SQL code that needs to be run to initialize our module.</p>
-
-<p>First, take a look at your config.xml file</p>
-
-<pre>
-&lt;modules>
-    &lt;Magentotutorial_Weblog>
-        &lt;version>0.1.0&lt;/version>
-    &lt;/Magentotutorial_Weblog>
-&lt;/modules>
-</pre>
-
-<p>This section is required in all config.xml files, and identifies the module as well as the its version number.  Your installer script's name will be based on this version number.  The following assumes the current version of your module is 0.1.0.  </p>
-
-<p>Create the following file at the following location</p>
-
-<p>File: <tt>app/code/local/Magentotutorial/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</tt></p>
-<pre>
-echo 'Running This Upgrade: '.get_class($this)."\n &lt;br /&gt; \n";
-die("Exit for now");
-</pre>
-
-<p>The <tt>weblog_setup</tt> portion of the path should match the tag you created in your config.xml file (<tt>&lt;weblog_setup /&gt;</tt>). The <tt>0.1.0</tt> portion of the filename should match the starting version of your module.  Clear your Magento cache and reload any page in your Magento site and you should see something like</p>
-
-<pre>
-Running This Upgrade: Magentotutorial_Weblog_Model_Resource_Setup
-Exit for now
- ...
-</pre>
-
-<p>Which means your update script ran.  Eventually we'll put our SQL update scripts here, but for now we're going to concentrate on the setup mechanism itself.  Remove the "die" statement from your script so it looks like the following</p>
-
-<pre>echo 'Running This Upgrade: '.get_class($this)."\n &lt;br /&gt; \n";</pre>
-
-<p>Reload your page.  You should see your upgrade message displayed at the top of the page.  Reload again, and your page should be displayed as normal.</p>
-
-<h2>Resource Versions</h2>
-
-<p>Magento's Setup Resources allow you to simply drop your install scripts (and upgrade scripts, which we'll get to in a bit) onto the server, and have the system  automatically run them.  This allows you to have all your database migrations scripts stored in the system in a consistent format.</p>
-
-<p>Using your favorite database client, take a look at the core_setup table</p>
-
-<pre>mysql> select * from core_resource;
-    +-------------------------+------------+--------------+
-    | code                    | version    | data_version |
-    +-------------------------+------------+--------------+
-    | adminnotification_setup | 1.6.0.0    | 1.6.0.0      |
-    | admin_setup             | 1.6.1.0    | 1.6.1.0      |
-    | api2_setup              | 1.0.0.0    | 1.0.0.0      |
-    | api_setup               | 1.6.0.0    | 1.6.0.0      |
-    | backup_setup            | 1.6.0.0    | 1.6.0.0      |
-    | bundle_setup            | 1.6.0.0.1  | 1.6.0.0.1    |
-    | captcha_setup           | 1.7.0.0.0  | 1.7.0.0.0    |
-    | catalogindex_setup      | 1.6.0.0    | 1.6.0.0      |
-    | cataloginventory_setup  | 1.6.0.0.2  | 1.6.0.0.2    |
-    | catalogrule_setup       | 1.6.0.3    | 1.6.0.3      |
-    | catalogsearch_setup     | 1.6.0.0    | 1.6.0.0      |
-    | catalog_setup           | 1.6.0.0.14 | 1.6.0.0.14   |
-    | checkout_setup          | 1.6.0.0    | 1.6.0.0      |
-    | cms_setup               | 1.6.0.0.1  | 1.6.0.0.1    |
-    | compiler_setup          | 1.6.0.0    | 1.6.0.0      |
-    | contacts_setup          | 1.6.0.0    | 1.6.0.0      |
-    | core_setup              | 1.6.0.2    | 1.6.0.2      |
-    | cron_setup              | 1.6.0.0    | 1.6.0.0      |
-    | customer_setup          | 1.6.2.0.1  | 1.6.2.0.1    |
-    | dataflow_setup          | 1.6.0.0    | 1.6.0.0      |
-    | directory_setup         | 1.6.0.1    | 1.6.0.1      |
-    | downloadable_setup      | 1.6.0.0.2  | 1.6.0.0.2    |
-    | eav_setup               | 1.6.0.0    | 1.6.0.0      |
-    | giftmessage_setup       | 1.6.0.0    | 1.6.0.0      |
-    | googleanalytics_setup   | 0.1.0      | 0.1.0        |
-    | googlecheckout_setup    | 1.6.0.1    | 1.6.0.1      |
-    | importexport_setup      | 1.6.0.2    | 1.6.0.2      |
-    | index_setup             | 1.6.0.0    | 1.6.0.0      |
-    | log_setup               | 1.6.0.0    | 1.6.0.0      |
-    | moneybookers_setup      | 1.6.0.0    | 1.6.0.0      |
-    | newsletter_setup        | 1.6.0.1    | 1.6.0.1      |
-    | oauth_setup             | 1.0.0.0    | 1.0.0.0      |
-    | paygate_setup           | 1.6.0.0    | 1.6.0.0      |
-    | payment_setup           | 1.6.0.0    | 1.6.0.0      |
-    | paypaluk_setup          | 1.6.0.0    | 1.6.0.0      |
-    | paypal_setup            | 1.6.0.2    | 1.6.0.2      |
-    | persistent_setup        | 1.0.0.0    | 1.0.0.0      |
-    | poll_setup              | 1.6.0.0    | 1.6.0.0      |
-    | productalert_setup      | 1.6.0.0    | 1.6.0.0      |
-    | rating_setup            | 1.6.0.0    | 1.6.0.0      |
-    | reports_setup           | 1.6.0.0.1  | 1.6.0.0.1    |
-    | review_setup            | 1.6.0.0    | 1.6.0.0      |
-    | salesrule_setup         | 1.6.0.3    | 1.6.0.3      |
-    | sales_setup             | 1.6.0.7    | 1.6.0.7      |
-    | sendfriend_setup        | 1.6.0.0    | 1.6.0.0      |
-    | shipping_setup          | 1.6.0.0    | 1.6.0.0      |
-    | sitemap_setup           | 1.6.0.0    | 1.6.0.0      |
-    | tag_setup               | 1.6.0.0    | 1.6.0.0      |
-    | tax_setup               | 1.6.0.3    | 1.6.0.3      |
-    | usa_setup               | 1.6.0.1    | 1.6.0.1      |
-    | weblog_setup            | 0.1.0      | 0.1.0        |
-    | weee_setup              | 1.6.0.0    | 1.6.0.0      |
-    | widget_setup            | 1.6.0.0    | 1.6.0.0      |
-    | wishlist_setup          | 1.6.0.0    | 1.6.0.0      |
-    | xmlconnect_setup        | 1.6.0.0    | 1.6.0.0      |
-    +-------------------------+------------+--------------+
-    55 rows in set (0.00 sec)
-</pre>
-
-<p>This table contains a list of all the installed modules, along with the installed version number.  You can see our module near the end</p>
-
-<pre>| weblog_setup            | 0.1.0      | 0.1.0        |</pre>
-
-<p>This is how Magento knows not to re-run your script on the second, and on all successive, page loads.  The <tt>weblog_setup</tt> is already installed, so it won't be updated. If you want to re-run your installer script (useful when you're developing), just delete the row for your module from this table.  Let's do that now, and actually add the SQL to create our table.  So first, run the following SQL.</p>
-
-<pre>DELETE from core_resource where code = 'weblog_setup';</pre>
-
-<p>We'll also want to drop the table we manually created in the <a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">ORM article</a>.  </p>
-
-<pre>DROP TABLE blog_posts;</pre>
-
-<p>Then, add the following code to your setup script.</p>
-
-<pre>$installer = $this;
-$installer->startSetup();
-$installer->run("
-    CREATE TABLE `{$installer->getTable('weblog/blogpost')}` (
-      `blogpost_id` int(11) NOT NULL auto_increment,
-      `title` text,
-      `post` text,
-      `date` datetime default NULL,
-      `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
-      PRIMARY KEY  (`blogpost_id`)
-    ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-    INSERT INTO `{$installer->getTable('weblog/blogpost')}` VALUES (1,'My New Title','This is a blog post','2009-07-01 00:00:00','2009-07-02 23:12:30');
-");
-$installer->endSetup();
-</pre>
-
-<p>Clear your Magento cache and reload any page in the system. You should have a new blog_posts table with a single row.</p>
-
-<h2>Anatomy of a Setup Script</h2>
-
-<p>So, let's go over the script line-by-line.  First, there's this (or is that $this?)</p>
-
-<pre>$installer = $this;</pre>
-
-<p>Each installer script is run from the context of a Setup Resource class, the class you created above.  That means any reference to <tt>$this</tt> from within the script will be a reference to an object instantiated from this class.  While not necessary, most setup scripts in the core modules will alias <tt>$this</tt> to a variable called installer, which is what we've done here.  While not necessary, it is the convention and it's always best to follow the convention unless you have a good reason for breaking it.</p>
-
-<p>Next, you'll see our queries are bookended by the following two method calls.  </p>
-
-<pre>$installer-&gt;startSetup();
-//...
-$installer-&gt;endSetup();
-</pre>
-
-<p>If you take a look at the <tt>Mage_Core_Model_Resource_Setup</tt> class in <tt>app/code/core/Mage/Core/Model/Resource/Setup.php</tt> (which your setup class inherits from) you can see that these methods do some basic SQL setup</p>
-
-<pre>
-    public function startSetup()
-    {
-        $this->getConnection()->startSetup()
-        return $this;
-    }
-
-    public function endSetup()
-    {
-        $this->getConnection()->endSetup();
-        return $this;
-    }
-</pre>
-
-<p>You can look into <tt>Varien_Db_Adapter_Pdo_Mysql</tt> in <tt>lib/Varien/Db/Adapter/Pdo/Mysql.php</tt> to find the real SQL setup executed for MySQL connections in the <tt>startSetup()</tt> and <tt>endSetup()</tt> methods.</p>
-
-<p>Finally, there's the call to the <tt>run</tt> method </p>
-
-<pre>$installer-&gt;run(...);</pre>
-
-<p>which accepts a string containing the SQL needed to setup your database table(s).  You may specify any number of queries, separated by a semi-colon.  You also probably noticed the following</p>
-
-<pre>$installer-&gt;getTable('weblog/blogpost')</pre>
-
-<p>The <tt>getTable</tt> method allows you to pass in a Magento Model URI and get its table name.  While not necessary, using this method ensures that your script will continue to run, even if someone changes the name of their table in the config file.  The <tt>Mage_Core_Model_Resource_Setup</tt> class contains many useful helper methods like this.  The best way to become familiar with everything that's possible is to study the installer scripts used by the core Magento modules.</p>
-
-<h2>RDBMS Agnostic Scripts</h2>
-
-<p>Since version 1.6, Magento (in theory) supports more database backends then only MySQL. Since our setup script contains raw SQL statements, it may not run correctly on a different database system, say MSSQL. For that reason the setup script name is prefixt with the string <tt>mysql4-</tt></p>
-
-<p>In order to make setup scripts cross-database compatible, Magento offers a DDL (Data Definition Language) Table object. Here is an alternative version of our setup script that would run on any supported RDBMS.</p>
-
-<p>File: <code>app/code/local/Magentotutorial/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</code></p>
-<pre>
-$installer = $this;
-$installer->startSetup();
-$table = $installer->getConnection()->newTable($installer->getTable('weblog/blogpost'))
-    ->addColumn('blogpost_id', Varien_Db_Ddl_Table::TYPE_INTEGER, null, array(
-        'unsigned' => true,
-        'nullable' => false,
-        'primary' => true,
-        'identity' => true,
-        ), 'Blogpost ID')
-    ->addColumn('title', Varien_Db_Ddl_Table::TYPE_TEXT, null, array(
-        'nullable' => false,
-        ), 'Blogpost Title')
-    ->addColumn('post', Varien_Db_Ddl_Table::TYPE_TEXT, null, array(
-        'nullable' => true,
-        ), 'Blogpost Body')
-    ->addColumn('date', Varien_Db_Ddl_Table::TYPE_DATETIME, null, array(
-        ), 'Blogpost Date')
-    ->addColumn('timestamp', Varien_Db_Ddl_Table::TYPE_TIMESTAMP, null, array(
-        ), 'Timestamp')
-    ->setComment('Magentotutorial weblog/blogpost entity table');
-$installer->getConnection()->createTable($table);
-
-$installer->endSetup();
-</pre>
-
-<p>As you can see, there is no raw SQL in this version of the setup script. So which version should you use? If you want your Modules to run on any RDBMS backend, use the new DDL style upgrade scripts. If you are concerned about backward compatibility, use the raw SQL flavor, that is still supported by Magento 1.6 and 1.7 (and probably will be supported by any 1.x Magento release).</p>
-
-<h2>Module Upgrades</h2>
-
-<p>So, that's how you create a script that will setup your initial database tables, but what if you want to alter the structure of an existing module?  Magento's Setup Resources support a simple versioning scheme that will let you automatically run scripts to <strong>upgrade</strong> your modules.  </p>
-
-<p>Once Magento runs an <em>installer</em> script for a module, it will <strong>never run another installer for that module again</strong> (short of manually deleting the reference in the <tt>core_resource</tt> table).  Instead, you'll need to create an upgrade script.  Upgrade scripts are very similar to installer scripts, with a few key differences.</p>
-
-<p>To get started, we'll create a script at the following location, with the following contents</p>
-
-<p>File: app/code/local/Magentotutorial/Weblog/sql/weblog_setup/upgrade-0.1.0-0.2.0.php:</p>
-<pre>
-echo 'Testing our upgrade script (upgrade-0.1.0-0.2.0.php) and halting execution to avoid updating the system version number <br />';
-die();
-</pre>
-
-<p>Upgrade scripts are placed in the same folder as your installer script, but named slightly differently.  First, and most obviously, the file name contains the word upgrade.  Secondly, you'll notice there are <strong>two</strong> version numbers, separated by a "-".  The first (<tt>0.1.0</tt>) is the module version that we're upgrading <strong>from</strong>.  The second (<tt>0.2.0</tt>) is the module version we're upgrading <strong>to</strong>.</p>
-
-<p>If we cleared our Magento cache and reloaded a page, our script wouldn't run.  We need to update the version number in our module's config.xml file to trigger the upgrade</p>
-
-<pre>
-&lt;modules>
-    &lt;Magentotutorial_Weblog>
-        &lt;version>0.2.0&lt;/version>
-    &lt;/Magentotutorial_Weblog>
-&lt;/modules>
-</pre>
-
-<p>With the new version number in place, we'll need to clear our Magento cache and load any page in our Magento site.  You should now see output from your upgrade script.  </p>
-
-<p>By the way, we also could have names our upgrade script <tt><strong>mysql4-</strong>upgrade-0.1.0-0.2.0.php</tt>. This would indicate our upgrade would contain MySQL specific SQL.</p>
-
-<p>Before we continue and actually implement the upgrade script, there's one important piece of behavior you'll want to be aware of.  Create another upgrade file at the following location with the following contents.</p>
-
-<p>File: app/code/local/Magentotutorial/Weblog/sql/weblog_setup/upgrade-0.1.0-0.1.5.php:</p>
-<pre>
-echo 'Testing our upgrade script (upgrade-0.1.0-0.1.5.php) and NOT halting execution &lt;br /&gt;';
-</pre>
-
-<p>If you reload a page, you'll notice you see BOTH messages.  When Magento notices the version number of a module has changed, it will run through <strong>all</strong> the setup scripts needed to bring that version up to date.  Although we never really created a version 0.1.5 of the Weblog module, Magento sees the upgrade script, and will attempt to run it.  Scripts will be run in order from lowest to highest.  If you take a peek at the <tt>core_resource</tt> table, </p>
-
-<pre>mysql> select * from core_resource where code = 'weblog_setup';
-+--------------+---------+--------------+
-| code         | version | data_version |
-+--------------+---------+--------------+
-| weblog_setup | 0.1.5   | 0.1.5        |
-+--------------+---------+--------------+
-1 row in set (0.00 sec)
-</pre>
-
-<p>you'll notice Magento considers the version number to be 1.5.  That's because we completed executing the 1.0 to 1.5 upgrade, but did not complete execution of the 1.0 to 2.0 upgrade.</p>
-
-<p>So, with all that out of the way, writing our actual upgrade script is identical to writing an installer script.  Let's change the <tt>0.1.0-0.2.0</tt> script to read</p>
-
-<pre>
-$installer = $this;
-$installer->startSetup();
-$installer->getConnection()
-    ->changeColumn($installer->getTable('weblog/blogpost'), 'post', 'post', array(
-        'type' => Varien_Db_Ddl_Table::TYPE_TEXT,
-        'nullable' => false,
-        'comment' => 'Blogpost Body'
-    )
-);
-$installer->endSetup();
-die("You'll see why this is here in a second");
-</pre>
-
-<p>Try refreshing a page in your Magento site and ... nothing.  The upgrade script didn't run.  The post field in our table still allows null values, and more importantly, the call to <tt>die()</tt> did not halt execution.  Here's what happened</p>
-
-<ol>
-<li>The weblog_setup resource was at version <tt>0.1.0</tt></li>
-<li>We upgraded our module to version <tt>0.2.0</tt></li>
-<li>Magento saw the upgraded module, and saw there were two upgrade scripts to run; <tt>0.1.0</tt> to <tt>0.1.5</tt> and <tt>0.1.0</tt> to <tt>0.2.0</tt></li>
-<li>Magento queued up both scripts to run</li>
-<li>Magento ran the <tt>0.1.0</tt> to <tt>0.1.5</tt> script</li>
-<li>The weblog_setup resource is now at version <tt>0.1.5</tt></li>
-<li>Magento ran the <tt>0.1.0</tt> to <tt>0.2.0</tt> script, execution was halted</li>
-<li>On the next page load, Magento saw weblog_setup at version <tt>0.1.5</tt> and did not see any upgrade scripts to run since both scripts indicated they should be run <strong>from</strong> <tt>0.1.0</tt></li>
-</ol>
-
-<p>The correct way to achieve what we wanted would have been to name our scripts as follows</p>
-
-<pre>upgrade-0.1.0-0.1.5.php #This goes from 0.1.0 to 0.1.5
-upgrade-0.1.5-0.2.0.php #This goes 0.1.5 to 0.2.0</pre>
-
-<p>Magento is smart enough to run both scripts on a single page load.  You can go back in time and give this a try by updating the <tt>core_resource</tt> table</p>
-
-<pre>UPDATE core_resource SET version = '0.1.0', data_version = '0.1.0' WHERE code = 'weblog_setup';
-...</pre>
-
-<p>It's one of the odd quirks of the Magento system that the updates will run as previously configured.  This means you'll want to be careful with multiple developers adding update scripts to the system.  You'll either want a build-meister/deployment-manager type in charge of the upgrade scripts or (heaven forbid) developers will need to talk to one another.</p>
-
-<h2>Wrap-up</h2>
-
-<p>You should now know the basics of how to use Magento Setup Resources to create versioned database migration scripts, as well as understand the scripts provided in the core modules.  Beyond having a standard way for developers to write migration scripts, Setup Resources become much more important when creating and modifying Entity Attribute Value models.</p>
-
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
+                                    Introduction to OpenMage
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
+                                    The OpenMage Config
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
+                                    OpenMage Controller Dispatch
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
+                                    OpenMage Layouts, Blocks and Templates
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
+                                    OpenMage Models and ORM Basics
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
+                                    OpenMage Setup Resources
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">
+                                    Advanced ORM: Entity Attribute Value
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-8.html">
+                                    Varien Data Collections
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">OpenMage Setup Resources</h1>
+                    </section>
+                    <p class="para1">On any fast paced software development project, the task of keeping the development
+                        and production databases in sync become a sticky wicket. Magento offers a system to create
+                        versioned resource migration scripts that can help your team deal with this often contentious
+                        part of the development process.</p>
+                    <p><a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">In the ORM article</a> we created a
+                        model for a weblog post. At the time, we ran our <tt>CREATE TABLE</tt> statements directly
+                        against the database. This time, we'll create a Setup Resource for our module that will create
+                        the table for us. We'll also create an upgrade script for our module that will update an already
+                        installed module. The steps we'll need to take are</p>
+                    <ol>
+                        <li>Add the Setup Resource to our config</li>
+                        <li>Create our resource class file</li>
+                        <li>Create our installer script</li>
+                        <li>Create our upgrade script</li>
+                    </ol>
+                    <br clear="all">
+                    <h2>Adding the Setup Resource</h2>
+                    <p>So, let's continue with the weblog module <a
+                            href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">we created last time</a>. In our
+                        &lt;global /&gt; section, add the following</p>
+                    <pre>
+                    &lt;global>
+                        &lt;!-- ... -->
+                        &lt;resources>
+                            &lt;weblog_setup>
+                                &lt;setup>
+                                    &lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;
+                                    &lt;class>Magentotutorial_Weblog_Model_Resource_Setup&lt;/class>
+                                &lt;/setup>
+                            &lt;/weblog_setup>
+                        &lt;/resources>
+                        &lt;!-- ... -->
+                    &lt;/global>
+                    </pre>
+                    <p>The <tt>&lt;weblog_setup&gt;</tt> tag will be used to uniquely identify this Setup Resource. It's
+                        encouraged, but not necessary, that you use the <tt>modelname_setup</tt> naming convention. The
+                        <tt>&lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;</tt> tag block should contain the <tt>Packagename_Modulename</tt>
+                        of your module. Finally, <tt>&lt;class&gt;Magentotutorial_Weblog_Model_Resource_Setup&lt;/class&gt;</tt>
+                        should contain the name of the class we'll be creating for our Setup Resource. For basic setup
+                        scripts it's not necessary to create a custom class, but by doing it now you'll give yourself
+                        more flexibility down the line.</p>
+                    <p>After adding the above section to your config, clear your Magento cache and try to load any page
+                        of your Magento site. You'll see an exception something like</p>
+                    <pre>Fatal error: Class 'Magentotutorial_Weblog_Model_Resource_Setup' not found in</pre>
+                    <p>Magento just tried to instantiate the class you specified in your config, but couldn't find it.
+                        You'll want to create the following file, with the following contents.</p>
+                    <p>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Setup.php</p>
+                    <pre>
+                    class Magentotutorial_Weblog_Model_Resource_Setup extends Mage_Core_Model_Resource_Setup {
+                    }
+                    </pre>
+                    <p>Now, reload any page of your Magento site. The exception should be gone, and your page should
+                        load as expected.</p>
+                    <h2>Creating our Installer Script</h2>
+                    <p>Next, we'll want to create our installer script. This is the script that will contain any <tt>CREATE
+                        TABLE</tt> or other SQL code that needs to be run to initialize our module.</p>
+                    <p>First, take a look at your config.xml file</p>
+                    <pre>
+                    &lt;modules>
+                        &lt;Magentotutorial_Weblog>
+                            &lt;version>0.1.0&lt;/version>
+                        &lt;/Magentotutorial_Weblog>
+                    &lt;/modules>
+                    </pre>
+                    <p>This section is required in all config.xml files, and identifies the module as well as the its
+                        version number. Your installer script's name will be based on this version number. The following
+                        assumes the current version of your module is 0.1.0. </p>
+                    <p>Create the following file at the following location</p>
+                    <p>File: <tt>app/code/local/Magentotutorial/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</tt>
+                    </p>
+                    <pre>
+                    echo 'Running This Upgrade: '.get_class($this)."\n &lt;br /&gt; \n";
+                    die("Exit for now");
+                    </pre>
+                    <p>The <tt>weblog_setup</tt> portion of the path should match the tag you created in your config.xml
+                        file (<tt>&lt;weblog_setup /&gt;</tt>). The <tt>0.1.0</tt> portion of the filename should match
+                        the starting version of your module. Clear your Magento cache and reload any page in your
+                        Magento site and you should see something like</p>
+                    <pre>
+                    Running This Upgrade: Magentotutorial_Weblog_Model_Resource_Setup
+                    Exit for now
+                     ...
+                    </pre>
+                    <p>Which means your update script ran. Eventually we'll put our SQL update scripts here, but for now
+                        we're going to concentrate on the setup mechanism itself. Remove the "die" statement from your
+                        script so it looks like the following</p>
+                    <pre>echo 'Running This Upgrade: '.get_class($this)."\n &lt;br /&gt; \n";</pre>
+                    <p>Reload your page. You should see your upgrade message displayed at the top of the page. Reload
+                        again, and your page should be displayed as normal.</p>
+                    <h2>Resource Versions</h2>
+                    <p>Magento's Setup Resources allow you to simply drop your install scripts (and upgrade scripts,
+                        which we'll get to in a bit) onto the server, and have the system automatically run them. This
+                        allows you to have all your database migrations scripts stored in the system in a consistent
+                        format.</p>
+                    <p>Using your favorite database client, take a look at the core_setup table</p>
+                    <pre>mysql> select * from core_resource;
+                        +-------------------------+------------+--------------+
+                        | code                    | version    | data_version |
+                        +-------------------------+------------+--------------+
+                        | adminnotification_setup | 1.6.0.0    | 1.6.0.0      |
+                        | admin_setup             | 1.6.1.0    | 1.6.1.0      |
+                        | api2_setup              | 1.0.0.0    | 1.0.0.0      |
+                        | api_setup               | 1.6.0.0    | 1.6.0.0      |
+                        | backup_setup            | 1.6.0.0    | 1.6.0.0      |
+                        | bundle_setup            | 1.6.0.0.1  | 1.6.0.0.1    |
+                        | captcha_setup           | 1.7.0.0.0  | 1.7.0.0.0    |
+                        | catalogindex_setup      | 1.6.0.0    | 1.6.0.0      |
+                        | cataloginventory_setup  | 1.6.0.0.2  | 1.6.0.0.2    |
+                        | catalogrule_setup       | 1.6.0.3    | 1.6.0.3      |
+                        | catalogsearch_setup     | 1.6.0.0    | 1.6.0.0      |
+                        | catalog_setup           | 1.6.0.0.14 | 1.6.0.0.14   |
+                        | checkout_setup          | 1.6.0.0    | 1.6.0.0      |
+                        | cms_setup               | 1.6.0.0.1  | 1.6.0.0.1    |
+                        | compiler_setup          | 1.6.0.0    | 1.6.0.0      |
+                        | contacts_setup          | 1.6.0.0    | 1.6.0.0      |
+                        | core_setup              | 1.6.0.2    | 1.6.0.2      |
+                        | cron_setup              | 1.6.0.0    | 1.6.0.0      |
+                        | customer_setup          | 1.6.2.0.1  | 1.6.2.0.1    |
+                        | dataflow_setup          | 1.6.0.0    | 1.6.0.0      |
+                        | directory_setup         | 1.6.0.1    | 1.6.0.1      |
+                        | downloadable_setup      | 1.6.0.0.2  | 1.6.0.0.2    |
+                        | eav_setup               | 1.6.0.0    | 1.6.0.0      |
+                        | giftmessage_setup       | 1.6.0.0    | 1.6.0.0      |
+                        | googleanalytics_setup   | 0.1.0      | 0.1.0        |
+                        | googlecheckout_setup    | 1.6.0.1    | 1.6.0.1      |
+                        | importexport_setup      | 1.6.0.2    | 1.6.0.2      |
+                        | index_setup             | 1.6.0.0    | 1.6.0.0      |
+                        | log_setup               | 1.6.0.0    | 1.6.0.0      |
+                        | moneybookers_setup      | 1.6.0.0    | 1.6.0.0      |
+                        | newsletter_setup        | 1.6.0.1    | 1.6.0.1      |
+                        | oauth_setup             | 1.0.0.0    | 1.0.0.0      |
+                        | paygate_setup           | 1.6.0.0    | 1.6.0.0      |
+                        | payment_setup           | 1.6.0.0    | 1.6.0.0      |
+                        | paypaluk_setup          | 1.6.0.0    | 1.6.0.0      |
+                        | paypal_setup            | 1.6.0.2    | 1.6.0.2      |
+                        | persistent_setup        | 1.0.0.0    | 1.0.0.0      |
+                        | poll_setup              | 1.6.0.0    | 1.6.0.0      |
+                        | productalert_setup      | 1.6.0.0    | 1.6.0.0      |
+                        | rating_setup            | 1.6.0.0    | 1.6.0.0      |
+                        | reports_setup           | 1.6.0.0.1  | 1.6.0.0.1    |
+                        | review_setup            | 1.6.0.0    | 1.6.0.0      |
+                        | salesrule_setup         | 1.6.0.3    | 1.6.0.3      |
+                        | sales_setup             | 1.6.0.7    | 1.6.0.7      |
+                        | sendfriend_setup        | 1.6.0.0    | 1.6.0.0      |
+                        | shipping_setup          | 1.6.0.0    | 1.6.0.0      |
+                        | sitemap_setup           | 1.6.0.0    | 1.6.0.0      |
+                        | tag_setup               | 1.6.0.0    | 1.6.0.0      |
+                        | tax_setup               | 1.6.0.3    | 1.6.0.3      |
+                        | usa_setup               | 1.6.0.1    | 1.6.0.1      |
+                        | weblog_setup            | 0.1.0      | 0.1.0        |
+                        | weee_setup              | 1.6.0.0    | 1.6.0.0      |
+                        | widget_setup            | 1.6.0.0    | 1.6.0.0      |
+                        | wishlist_setup          | 1.6.0.0    | 1.6.0.0      |
+                        | xmlconnect_setup        | 1.6.0.0    | 1.6.0.0      |
+                        +-------------------------+------------+--------------+
+                        55 rows in set (0.00 sec)
+                    </pre>
+                    <p>This table contains a list of all the installed modules, along with the installed version number.
+                        You can see our module near the end</p>
+
+                    <pre>| weblog_setup            | 0.1.0      | 0.1.0        |</pre>
+                    <p>This is how Magento knows not to re-run your script on the second, and on all successive, page
+                        loads. The <tt>weblog_setup</tt> is already installed, so it won't be updated. If you want to
+                        re-run your installer script (useful when you're developing), just delete the row for your
+                        module from this table. Let's do that now, and actually add the SQL to create our table. So
+                        first, run the following SQL.</p>
+                    <pre>DELETE from core_resource where code = 'weblog_setup';</pre>
+                    <p>We'll also want to drop the table we manually created in the <a
+                            href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">ORM article</a>. </p>
+                    <pre>DROP TABLE blog_posts;</pre>
+                    <p>Then, add the following code to your setup script.</p>
+                    <pre>$installer = $this;
+                    $installer->startSetup();
+                    $installer->run("
+                        CREATE TABLE `{$installer->getTable('weblog/blogpost')}` (
+                          `blogpost_id` int(11) NOT NULL auto_increment,
+                          `title` text,
+                          `post` text,
+                          `date` datetime default NULL,
+                          `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
+                          PRIMARY KEY  (`blogpost_id`)
+                        ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+                        INSERT INTO `{$installer->getTable('weblog/blogpost')}` VALUES (1,'My New Title','This is a blog post','2009-07-01 00:00:00','2009-07-02 23:12:30');
+                    ");
+                    $installer->endSetup();
+                    </pre>
+                    <p>Clear your Magento cache and reload any page in the system. You should have a new blog_posts
+                        table with a single row.</p>
+                    <h2>Anatomy of a Setup Script</h2>
+                    <p>So, let's go over the script line-by-line. First, there's this (or is that $this?)</p>
+                    <pre>$installer = $this;</pre>
+                    <p>Each installer script is run from the context of a Setup Resource class, the class you created
+                        above. That means any reference to <tt>$this</tt> from within the script will be a reference to
+                        an object instantiated from this class. While not necessary, most setup scripts in the core
+                        modules will alias <tt>$this</tt> to a variable called installer, which is what we've done here.
+                        While not necessary, it is the convention and it's always best to follow the convention unless
+                        you have a good reason for breaking it.</p>
+                    <p>Next, you'll see our queries are bookended by the following two method calls. </p>
+                    <pre>$installer-&gt;startSetup();
+                    //...
+                    $installer-&gt;endSetup();
+                    </pre>
+                    <p>If you take a look at the <tt>Mage_Core_Model_Resource_Setup</tt> class in <tt>app/code/core/Mage/Core/Model/Resource/Setup.php</tt>
+                        (which your setup class inherits from) you can see that these methods do some basic SQL setup
+                    </p>
+                    <pre>
+                        public function startSetup()
+                        {
+                            $this->getConnection()->startSetup()
+                            return $this;
+                        }
+
+                        public function endSetup()
+                        {
+                            $this->getConnection()->endSetup();
+                            return $this;
+                        }
+                    </pre>
+                    <p>You can look into <tt>Varien_Db_Adapter_Pdo_Mysql</tt> in
+                        <tt>lib/Varien/Db/Adapter/Pdo/Mysql.php</tt> to find the real SQL setup executed for MySQL
+                        connections in the <tt>startSetup()</tt> and <tt>endSetup()</tt> methods.</p>
+                    <p>Finally, there's the call to the <tt>run</tt> method </p>
+                    <pre>$installer-&gt;run(...);</pre>
+                    <p>which accepts a string containing the SQL needed to setup your database table(s). You may specify
+                        any number of queries, separated by a semi-colon. You also probably noticed the following</p>
+                    <pre>$installer-&gt;getTable('weblog/blogpost')</pre>
+                    <p>The <tt>getTable</tt> method allows you to pass in a Magento Model URI and get its table name.
+                        While not necessary, using this method ensures that your script will continue to run, even if
+                        someone changes the name of their table in the config file. The <tt>Mage_Core_Model_Resource_Setup</tt>
+                        class contains many useful helper methods like this. The best way to become familiar with
+                        everything that's possible is to study the installer scripts used by the core Magento modules.
+                    </p>
+                    <h2>RDBMS Agnostic Scripts</h2>
+                    <p>Since version 1.6, Magento (in theory) supports more database backends then only MySQL. Since our
+                        setup script contains raw SQL statements, it may not run correctly on a different database
+                        system, say MSSQL. For that reason the setup script name is prefixt with the string
+                        <tt>mysql4-</tt></p>
+                    <p>In order to make setup scripts cross-database compatible, Magento offers a DDL (Data Definition
+                        Language) Table object. Here is an alternative version of our setup script that would run on any
+                        supported RDBMS.</p>
+                    <p>File:
+                        <code>app/code/local/Magentotutorial/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</code></p>
+                    <pre>
+                    $installer = $this;
+                    $installer->startSetup();
+                    $table = $installer->getConnection()->newTable($installer->getTable('weblog/blogpost'))
+                        ->addColumn('blogpost_id', Varien_Db_Ddl_Table::TYPE_INTEGER, null, array(
+                            'unsigned' => true,
+                            'nullable' => false,
+                            'primary' => true,
+                            'identity' => true,
+                            ), 'Blogpost ID')
+                        ->addColumn('title', Varien_Db_Ddl_Table::TYPE_TEXT, null, array(
+                            'nullable' => false,
+                            ), 'Blogpost Title')
+                        ->addColumn('post', Varien_Db_Ddl_Table::TYPE_TEXT, null, array(
+                            'nullable' => true,
+                            ), 'Blogpost Body')
+                        ->addColumn('date', Varien_Db_Ddl_Table::TYPE_DATETIME, null, array(
+                            ), 'Blogpost Date')
+                        ->addColumn('timestamp', Varien_Db_Ddl_Table::TYPE_TIMESTAMP, null, array(
+                            ), 'Timestamp')
+                        ->setComment('Magentotutorial weblog/blogpost entity table');
+                    $installer->getConnection()->createTable($table);
+
+                    $installer->endSetup();
+                    </pre>
+                    <p>As you can see, there is no raw SQL in this version of the setup script. So which version should
+                        you use? If you want your Modules to run on any RDBMS backend, use the new DDL style upgrade
+                        scripts. If you are concerned about backward compatibility, use the raw SQL flavor, that is
+                        still supported by Magento 1.6 and 1.7 (and probably will be supported by any 1.x Magento
+                        release).</p>
+                    <h2>Module Upgrades</h2>
+                    <p>So, that's how you create a script that will setup your initial database tables, but what if you
+                        want to alter the structure of an existing module? Magento's Setup Resources support a simple
+                        versioning scheme that will let you automatically run scripts to <strong>upgrade</strong> your
+                        modules. </p>
+                    <p>Once Magento runs an <em>installer</em> script for a module, it will <strong>never run another
+                        installer for that module again</strong> (short of manually deleting the reference in the <tt>core_resource</tt>
+                        table). Instead, you'll need to create an upgrade script. Upgrade scripts are very similar to
+                        installer scripts, with a few key differences.</p>
+                    <p>To get started, we'll create a script at the following location, with the following contents</p>
+                    <p>File: app/code/local/Magentotutorial/Weblog/sql/weblog_setup/upgrade-0.1.0-0.2.0.php:</p>
+                    <pre>
+                    echo 'Testing our upgrade script (upgrade-0.1.0-0.2.0.php) and halting execution to avoid updating the system version number <br/>';
+                    die();
+                    </pre>
+                    <p>Upgrade scripts are placed in the same folder as your installer script, but named slightly
+                        differently. First, and most obviously, the file name contains the word upgrade. Secondly,
+                        you'll notice there are <strong>two</strong> version numbers, separated by a "-". The first
+                        (<tt>0.1.0</tt>) is the module version that we're upgrading <strong>from</strong>. The second
+                        (<tt>0.2.0</tt>) is the module version we're upgrading <strong>to</strong>.</p>
+                    <p>If we cleared our Magento cache and reloaded a page, our script wouldn't run. We need to update
+                        the version number in our module's config.xml file to trigger the upgrade</p>
+                    <pre>
+                    &lt;modules>
+                        &lt;Magentotutorial_Weblog>
+                            &lt;version>0.2.0&lt;/version>
+                        &lt;/Magentotutorial_Weblog>
+                    &lt;/modules>
+                    </pre>
+                    <p>With the new version number in place, we'll need to clear our Magento cache and load any page in
+                        our Magento site. You should now see output from your upgrade script. </p>
+                    <p>By the way, we also could have names our upgrade script <tt><strong>mysql4-</strong>upgrade-0.1.0-0.2.0.php</tt>.
+                        This would indicate our upgrade would contain MySQL specific SQL.</p>
+                    <p>Before we continue and actually implement the upgrade script, there's one important piece of
+                        behavior you'll want to be aware of. Create another upgrade file at the following location with
+                        the following contents.</p>
+                    <p>File: app/code/local/Magentotutorial/Weblog/sql/weblog_setup/upgrade-0.1.0-0.1.5.php:</p>
+                    <pre>
+                    echo 'Testing our upgrade script (upgrade-0.1.0-0.1.5.php) and NOT halting execution &lt;br /&gt;';
+                    </pre>
+                    <p>If you reload a page, you'll notice you see BOTH messages. When Magento notices the version
+                        number of a module has changed, it will run through <strong>all</strong> the setup scripts
+                        needed to bring that version up to date. Although we never really created a version 0.1.5 of the
+                        Weblog module, Magento sees the upgrade script, and will attempt to run it. Scripts will be run
+                        in order from lowest to highest. If you take a peek at the <tt>core_resource</tt> table, </p>
+                    <pre>mysql> select * from core_resource where code = 'weblog_setup';
+                    +--------------+---------+--------------+
+                    | code         | version | data_version |
+                    +--------------+---------+--------------+
+                    | weblog_setup | 0.1.5   | 0.1.5        |
+                    +--------------+---------+--------------+
+                    1 row in set (0.00 sec)
+                    </pre>
+                    <p>you'll notice Magento considers the version number to be 1.5. That's because we completed
+                        executing the 1.0 to 1.5 upgrade, but did not complete execution of the 1.0 to 2.0 upgrade.</p>
+                    <p>So, with all that out of the way, writing our actual upgrade script is identical to writing an
+                        installer script. Let's change the <tt>0.1.0-0.2.0</tt> script to read</p>
+                    <pre>
+                    $installer = $this;
+                    $installer->startSetup();
+                    $installer->getConnection()
+                        ->changeColumn($installer->getTable('weblog/blogpost'), 'post', 'post', array(
+                            'type' => Varien_Db_Ddl_Table::TYPE_TEXT,
+                            'nullable' => false,
+                            'comment' => 'Blogpost Body'
+                        )
+                    );
+                    $installer->endSetup();
+                    die("You'll see why this is here in a second");
+                    </pre>
+                    <p>Try refreshing a page in your Magento site and ... nothing. The upgrade script didn't run. The
+                        post field in our table still allows null values, and more importantly, the call to
+                        <tt>die()</tt> did not halt execution. Here's what happened</p>
+                    <ol>
+                        <li>The weblog_setup resource was at version <tt>0.1.0</tt></li>
+                        <li>We upgraded our module to version <tt>0.2.0</tt></li>
+                        <li>Magento saw the upgraded module, and saw there were two upgrade scripts to run;
+                            <tt>0.1.0</tt> to <tt>0.1.5</tt> and <tt>0.1.0</tt> to <tt>0.2.0</tt></li>
+                        <li>Magento queued up both scripts to run</li>
+                        <li>Magento ran the <tt>0.1.0</tt> to <tt>0.1.5</tt> script</li>
+                        <li>The weblog_setup resource is now at version <tt>0.1.5</tt></li>
+                        <li>Magento ran the <tt>0.1.0</tt> to <tt>0.2.0</tt> script, execution was halted</li>
+                        <li>On the next page load, Magento saw weblog_setup at version <tt>0.1.5</tt> and did not see
+                            any upgrade scripts to run since both scripts indicated they should be run
+                            <strong>from</strong> <tt>0.1.0</tt></li>
+                    </ol>
+                    <p>The correct way to achieve what we wanted would have been to name our scripts as follows</p>
+                    <pre>upgrade-0.1.0-0.1.5.php #This goes from 0.1.0 to 0.1.5
+                    upgrade-0.1.5-0.2.0.php #This goes 0.1.5 to 0.2.0</pre>
+                    <p>Magento is smart enough to run both scripts on a single page load. You can go back in time and
+                        give this a try by updating the <tt>core_resource</tt> table</p>
+                    <pre>UPDATE core_resource SET version = '0.1.0', data_version = '0.1.0' WHERE code = 'weblog_setup';
+                    ...</pre>
+                    <p>It's one of the odd quirks of the Magento system that the updates will run as previously
+                        configured. This means you'll want to be careful with multiple developers adding update scripts
+                        to the system. You'll either want a build-meister/deployment-manager type in charge of the
+                        upgrade scripts or (heaven forbid) developers will need to talk to one another.</p>
+                    <h2>Wrap-up</h2>
+                    <p>You should now know the basics of how to use Magento Setup Resources to create versioned database
+                        migration scripts, as well as understand the scripts provided in the core modules. Beyond having
+                        a standard way for developers to write migration scripts, Setup Resources become much more
+                        important when creating and modifying Entity Attribute Value models.</p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
 </div>
-</html>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
\ No newline at end of file
diff --git a/guides/m1x/magefordev/mage-for-dev-7.html b/guides/m1x/magefordev/mage-for-dev-7.html
index 0445954489..c7650ea4fc 100644
--- a/guides/m1x/magefordev/mage-for-dev-7.html
+++ b/guides/m1x/magefordev/mage-for-dev-7.html
@@ -1,64 +1,281 @@
 ---
 ---
 <!DOCTYPE html>
-<html lang=en>
-
+<html lang="en" dir="ltr">
 <head>
-    <meta charset=utf-8>
-
-    <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
-    <link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
-    <link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <title>Magento for Developers: Part 7&mdash;Advanced ORM: Entity Attribute Value</title>
-
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>OpenMage for Developers: Part 7&mdash;Advanced ORM: Entity Attribute Value</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-
-<img src="{{ site.baseurl }}/guides/m1x/images/m1xheader.png" width="1024" alt="header" />
-{% include m1x/eol_message.html %}
-
-<div id="content">
-<h1>Magento for Developers: Part 7&mdash;Advanced ORM: Entity Attribute Value</h1>
-<p><em>by Alan Storm</em>, updated for Magento 1.12</p>
-<p><a href="{{ site.m1xgithuburl }}/magefordev/mage-for-dev-7.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>
-
-
-<!--Magento for Developers: Part 7&mdash;Advanced ORM: Entity Attribute Value -->
-<!-- magento-for-dev-part-7-advanced-orm-entity-attribute-value 
-
-<style type="text/css">
-#kb-entry .series {float: right; width: 175px; margin-left: 10px; font-size: 12px; }
-#kb-entry .series ul {margin-left: 15px;}
-</style> 
-<div class="r-box-rss series">  -->
-
-<h5>Other articles in this series:</h5>
-<ul>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-1.html">Part 1&mdash;Introduction to Magento</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-2.html">Part 2&mdash;The Magento Config</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-3.html">Part 3&mdash;Magento Controller Dispatch</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-4.html">Part 4&mdash;Magento Layouts, Blocks and Templates</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">Part 5&mdash;Magento Models and ORM Basics</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Part 6&mdash;Magento Setup Resources</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">Part 7&mdash;Advanced ORM: Entity Attribute Value</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-8.html">Part 8&mdash;Varien Data Collections</a>
-</ul>
-</div>
-
-<p class="para1">In the <a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">first ORM article</a> we told you there were two kinds of Models in Magento.  Regular, or "simple" Models, and Entity Attribute Value (or EAV) Models.  We also told you this was a bit of a fib.  Here's where we come clean.</p>
-
-<p><strong>ALL</strong> Magento Models interacting with the database inherit from the <tt>Mage_Core_Model_Abstract</tt> / <tt>Varien_Object</tt> chain.  What makes something either a simple Model or an EAV Model is its <strong>Model Resource</strong>.  While all resources extend the base <tt>Mage_Core_Model_Resource_Abstract</tt> class, simple Models have a resource that inherits from <tt>Mage_Core_Model_Resource_Db_Abstract</tt>, and EAV Models have a resource that inherits from <tt>Mage_Eav_Model_Entity_Abstract</tt></p>
-
-<p>If you think about it, this makes sense.  As the end-programmer-user of the system you want a set of methods you can use to talk to and manipulate your Models.  You don't care what the backend storage looks like, you just want to get properties and invoke methods that trigger business rules.  </p>
-
-<h2>What is EAV</h2>
-
-<p><a href="http://en.wikipedia.org/wiki/Entity-attribute-value_model" target="_new">Wikipedia defines EAV</a> as </p>
-<blockquote>Entity-Attribute-Value model (EAV), also known as object-attribute-value model and open schema is a data model that is used in circumstances where the number of attributes (properties, parameters) that can be used to describe a thing (an "entity" or "object") is potentially very vast, but the number that will actually apply to a given entity is relatively modest. In mathematics, this model is known as a sparse matrix.</blockquote>
-
-<p>Another metaphor that helps me wrap my head around it is "EAV brings some aspects of normalization to the database <strong>table schema</strong>".  In a traditional database, tables have a fixed number of columns</p>
-
-<pre>+------------------+
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
+                                    Introduction to OpenMage
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
+                                    The OpenMage Config
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
+                                    OpenMage Controller Dispatch
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
+                                    OpenMage Layouts, Blocks and Templates
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
+                                    OpenMage Models and ORM Basics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
+                                    OpenMage Setup Resources
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">
+                                    Advanced ORM: Entity Attribute Value
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-8.html">
+                                    Varien Data Collections
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Advanced ORM: Entity Attribute Value</h1>
+                    </section>
+
+                    <p class="para1">In the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">first ORM article</a> we told you there were two kinds of Models in Magento.  Regular, or "simple" Models, and Entity Attribute Value (or EAV) Models.  We also told you this was a bit of a fib.  Here's where we come clean.</p>
+
+                    <p><strong>ALL</strong> Magento Models interacting with the database inherit from the <tt>Mage_Core_Model_Abstract</tt> / <tt>Varien_Object</tt> chain.  What makes something either a simple Model or an EAV Model is its <strong>Model Resource</strong>.  While all resources extend the base <tt>Mage_Core_Model_Resource_Abstract</tt> class, simple Models have a resource that inherits from <tt>Mage_Core_Model_Resource_Db_Abstract</tt>, and EAV Models have a resource that inherits from <tt>Mage_Eav_Model_Entity_Abstract</tt></p>
+
+                    <p>If you think about it, this makes sense.  As the end-programmer-user of the system you want a set of methods you can use to talk to and manipulate your Models.  You don't care what the backend storage looks like, you just want to get properties and invoke methods that trigger business rules.  </p>
+
+                    <h2>What is EAV</h2>
+
+                    <p><a href="http://en.wikipedia.org/wiki/Entity-attribute-value_model" target="_new">Wikipedia defines EAV</a> as </p>
+                    <blockquote>Entity-Attribute-Value model (EAV), also known as object-attribute-value model and open schema is a data model that is used in circumstances where the number of attributes (properties, parameters) that can be used to describe a thing (an "entity" or "object") is potentially very vast, but the number that will actually apply to a given entity is relatively modest. In mathematics, this model is known as a sparse matrix.</blockquote>
+
+                    <p>Another metaphor that helps me wrap my head around it is "EAV brings some aspects of normalization to the database <strong>table schema</strong>".  In a traditional database, tables have a fixed number of columns</p>
+
+                    <pre>+------------------+
 | products         |
 +------------------+
 | product_id       |
@@ -76,38 +293,38 @@ <h2>What is EAV</h2>
 +------------+----------------+------------------+---------+
 </pre>
 
-<p>Every product has a name, every product has a price, etc.  </p>
+                    <p>Every product has a name, every product has a price, etc.  </p>
 
-<p>In an EAV Model, each "entity" (product) being modeled has a <strong>different</strong> set of attributes.  EAV makes a lot of sense for a generic eCommerce solution.  A store that sells laptops (which have a CPU speed, color, ram amount, etc) is going to have a different set of needs than a store that sells yarn (yarn has a color, but no CPU speed, etc.).  Even within our hypothetical yarn store, some products will have length (balls of yarn), and others will have diameter (knitting needles). </p>
+                    <p>In an EAV Model, each "entity" (product) being modeled has a <strong>different</strong> set of attributes.  EAV makes a lot of sense for a generic eCommerce solution.  A store that sells laptops (which have a CPU speed, color, ram amount, etc) is going to have a different set of needs than a store that sells yarn (yarn has a color, but no CPU speed, etc.).  Even within our hypothetical yarn store, some products will have length (balls of yarn), and others will have diameter (knitting needles). </p>
 
-<p>There aren't many open source or commercial databases that use EAV by default.  There are none that are available on a wide variety of web hosting platforms.  Because of that, the Magento engineers have built an EAV system out of PHP objects that use MySQL as a data-store.  In other words, they've built an EAV database system <strong>on top of</strong> a traditional relational database.  </p>
+                    <p>There aren't many open source or commercial databases that use EAV by default.  There are none that are available on a wide variety of web hosting platforms.  Because of that, the Magento engineers have built an EAV system out of PHP objects that use MySQL as a data-store.  In other words, they've built an EAV database system <strong>on top of</strong> a traditional relational database.  </p>
 
-<p>In practice this means any Model that uses an EAV resource has its attributes spread out over a number of MySQL tables.<br/>
-<a href="http://alanstorm.com/2009/img/magento-book/eav.png" target="_blank"><img src="http://alanstorm.com/2009/img/magento-book/eav.png" width="700" height="463" style="border:1px solid #000;margin-left:40px"/></a>
+                    <p>In practice this means any Model that uses an EAV resource has its attributes spread out over a number of MySQL tables.<br/>
+                        <a href="http://alanstorm.com/2009/img/magento-book/eav.png" target="_blank"><img src="http://alanstorm.com/2009/img/magento-book/eav.png" width="700" height="463" style="border:1px solid #000;margin-left:40px"/></a>
 
-<p>The above diagram is a rough layout of the database tables Magento consults when it looks up an EAV record for the <tt>catalog_product</tt> entity.  Each individual product has a row in <tt>catalog_product_entity</tt>.  All the available attributes in the <strong>entire</strong> system (not just for products)  are stored in <tt>eav_attribute</tt>, and the actual attribute values are stored in tables with names like <tt>catalog_product_entity_varchar</tt>, <tt>catalog_product_entity_decimal</tt>, <tt>catalog_product_entity_<em>etc.</em></tt>.</p>
+                    <p>The above diagram is a rough layout of the database tables Magento consults when it looks up an EAV record for the <tt>catalog_product</tt> entity.  Each individual product has a row in <tt>catalog_product_entity</tt>.  All the available attributes in the <strong>entire</strong> system (not just for products)  are stored in <tt>eav_attribute</tt>, and the actual attribute values are stored in tables with names like <tt>catalog_product_entity_varchar</tt>, <tt>catalog_product_entity_decimal</tt>, <tt>catalog_product_entity_<em>etc.</em></tt>.</p>
 
-<p>Beyond the mental flexibility an EAV system gives you, there's also the practical benefit of avoiding ALTER TABLE statements.  When you add a new attribute for your products, a new row is inserted into <tt>eav_attribute</tt>.  In a traditional relational database/single-table system, you'd need to ALTER the actual database structure, which can be a time consuming/risky proposition for tables with large data-sets.</p>
+                    <p>Beyond the mental flexibility an EAV system gives you, there's also the practical benefit of avoiding ALTER TABLE statements.  When you add a new attribute for your products, a new row is inserted into <tt>eav_attribute</tt>.  In a traditional relational database/single-table system, you'd need to ALTER the actual database structure, which can be a time consuming/risky proposition for tables with large data-sets.</p>
 
-<p>The downside is there's no one single simple SQL query you can use to get at all your product data.  Several single SQL queries or one large join need to be made.  </p>
+                    <p>The downside is there's no one single simple SQL query you can use to get at all your product data.  Several single SQL queries or one large join need to be made.  </p>
 
-<h2>Implementing EAV</h2>
+                    <h2>Implementing EAV</h2>
 
-<p>That's EAV in a nutshell. The rest of this articles is a run-through of what's needed to create a new EAV Model in Magento.  It's the hairiest thing you'll read about Magento and it's something that 95% of people working with the system will never need to do.  However, understanding what it takes to build an EAV Model Resource will help you understand what's going on with the EAV Resources that Magento uses.</p>
+                    <p>That's EAV in a nutshell. The rest of this articles is a run-through of what's needed to create a new EAV Model in Magento.  It's the hairiest thing you'll read about Magento and it's something that 95% of people working with the system will never need to do.  However, understanding what it takes to build an EAV Model Resource will help you understand what's going on with the EAV Resources that Magento uses.</p>
 
-<p>Because the EAV information is so dense, we're going to assume you're already very familiar with Magento's MVC and grouped class name features.  We'll help you along the way, but training wheels are off.</p>
+                    <p>Because the EAV information is so dense, we're going to assume you're already very familiar with Magento's MVC and grouped class name features.  We'll help you along the way, but training wheels are off.</p>
 
-<h2>Weblog, EAV Style</h2>
+                    <h2>Weblog, EAV Style</h2>
 
-<p>We're going to create another Model for a weblog post, but this time using an EAV Resource.  To start with, setup and create a new module which responds at the following URL</p>
+                    <p>We're going to create another Model for a weblog post, but this time using an EAV Resource.  To start with, setup and create a new module which responds at the following URL</p>
 
-<pre>http://example.com/complexworld</pre>
+                    <pre>http://example.com/complexworld</pre>
 
-<p>If you're unsure how to do this, be sure you've mastered the concepts in the <a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">previous tutorials</a>.</p>
+                    <p>If you're unsure how to do this, be sure you've mastered the concepts in the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">previous tutorials</a>.</p>
 
-<p>Next, we'll create a new Model named Weblogeav. Remember, it's the <strong>Resource</strong> that's considered EAV.  We design and configure our Model the exact same way, so let's configure a Model similar to one <a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">we created in the first ORM article</a>.</p>
+                    <p>Next, we'll create a new Model named Weblogeav. Remember, it's the <strong>Resource</strong> that's considered EAV.  We design and configure our Model the exact same way, so let's configure a Model similar to one <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">we created in the first ORM article</a>.</p>
 
-<pre>
+                    <pre>
 &lt;global>
     &lt;!-- ... -->
     &lt;models>
@@ -122,11 +339,11 @@ <h2>Weblog, EAV Style</h2>
 &lt;/global>
 </pre>
 
-<p>You'll notice so far there is no difference to setting up a regular Model and flat table resource Model. </p>
+                    <p>You'll notice so far there is no difference to setting up a regular Model and flat table resource Model. </p>
 
-<p>We'll still need to let Magento know about this resource.  Similar to basic Models, EAV Resources are configured in the same <tt>&lt;model/&gt;</tt> node with everything else. </p>
+                    <p>We'll still need to let Magento know about this resource.  Similar to basic Models, EAV Resources are configured in the same <tt>&lt;model/&gt;</tt> node with everything else. </p>
 
-<pre>
+                    <pre>
 &lt;global>
     &lt;!-- ... -->
     &lt;models>
@@ -145,13 +362,13 @@ <h2>Weblog, EAV Style</h2>
 &lt;/global>
 </pre>
 
-<p>Again, so far this is setup similar to our regular Model Resource.  We provide a <tt>&lt;class/&gt;</tt> that configures a PHP class, as well as an <tt>&lt;entities/&gt;</tt> section that will let Magento know the base table for an individual Model we want to create. The <tt>&lt;eavblogpost/&gt;</tt> tag is the name of the specific Model we want to create, and its inner <tt>&lt;table/&gt;</tt> tag specifies the base table this Model will use (more on this later).</p>
+                    <p>Again, so far this is setup similar to our regular Model Resource.  We provide a <tt>&lt;class/&gt;</tt> that configures a PHP class, as well as an <tt>&lt;entities/&gt;</tt> section that will let Magento know the base table for an individual Model we want to create. The <tt>&lt;eavblogpost/&gt;</tt> tag is the name of the specific Model we want to create, and its inner <tt>&lt;table/&gt;</tt> tag specifies the base table this Model will use (more on this later).</p>
 
-<h2>Where Does That File Go?</h2>
+                    <h2>Where Does That File Go?</h2>
 
-<p>Until wide adoption of PHP 5.3 and namespaces, one of the trickier (and tedious) parts of Magento will remain remembering how <tt>&lt;classname/&gt;</tt>s relate to file paths, and then ensuring you create the correctly named directory structure and class files.  After configuring any <tt>&lt;classname/&gt;</tt>s or URIs, you may find it useful to attempt to instantiate an instance of the class in a controller <strong>without</strong> first creating the class files.  This way PHP will throw an exception telling me it can't find a file, along with the file location.  Give the following a try in your Index Controller.</p>
+                    <p>Until wide adoption of PHP 5.3 and namespaces, one of the trickier (and tedious) parts of Magento will remain remembering how <tt>&lt;classname/&gt;</tt>s relate to file paths, and then ensuring you create the correctly named directory structure and class files.  After configuring any <tt>&lt;classname/&gt;</tt>s or URIs, you may find it useful to attempt to instantiate an instance of the class in a controller <strong>without</strong> first creating the class files.  This way PHP will throw an exception telling me it can't find a file, along with the file location.  Give the following a try in your Index Controller.</p>
 
-<pre>
+                    <pre>
 public function indexAction() {
     $weblog2 = Mage::getModel('complexworld/eavblogpost');
     $weblog2->load(1);
@@ -159,25 +376,25 @@ <h2>Where Does That File Go?</h2>
 }
 </pre>
 
-<p>As predicted, a warning should be thrown</p>
+                    <p>As predicted, a warning should be thrown</p>
 
-<pre>
-Warning: include(Magentotutorial/Complexworld/Model/Eavblogpost.php) [function.include]: 
+                    <pre>
+Warning: include(Magentotutorial/Complexworld/Model/Eavblogpost.php) [function.include]:
 failed to open stream: No such file or directory  in /Users/username/Sites/magento.dev/lib/Varien/Autoload.php on line 93
 </pre>
 
-<p>In addition to telling us the path where we'll need to define the new resource class this also serves as a configuration check.  If we'd been warned with the following</p>
+                    <p>In addition to telling us the path where we'll need to define the new resource class this also serves as a configuration check.  If we'd been warned with the following</p>
 
-<pre>
-Warning: include(Mage/Complexworld/Model/Eavblogpost.php) [function.include]: 
+                    <pre>
+Warning: include(Mage/Complexworld/Model/Eavblogpost.php) [function.include]:
 failed to open stream: No such file or directory  in /Users/username/Sites/magento.dev/lib/Varien/Autoload.php on line 93
 </pre>
 
-<p>we'd know our Model was misconfigured, as Magento was looking for the Model in <tt>code/core/Mage</tt> instead of <tt>code/local/Magentotutorial</tt>.</p>
+                    <p>we'd know our Model was misconfigured, as Magento was looking for the Model in <tt>code/core/Mage</tt> instead of <tt>code/local/Magentotutorial</tt>.</p>
 
-<p>So, lets create our Model class</p>
-<p>File: <code>app/code/local/Magentotutorial/Complexworld/Model/Eavblogpost.php</code>:
-<pre>
+                    <p>So, lets create our Model class</p>
+                    <p>File: <code>app/code/local/Magentotutorial/Complexworld/Model/Eavblogpost.php</code>:
+                    <pre>
 class Magentotutorial_Complexworld_Model_Eavblogpost extends Mage_Core_Model_Abstract {
     protected function _construct()
     {
@@ -186,16 +403,16 @@ <h2>Where Does That File Go?</h2>
 }
 </pre>
 
-<p>Remember, the Model itself is resource independent.  A regular Model and an EAV Model both extend from the same class.  It's the resource that makes them different. </p>
+                    <p>Remember, the Model itself is resource independent.  A regular Model and an EAV Model both extend from the same class.  It's the resource that makes them different. </p>
 
-<p>Clear your Magento cache, reload your page, and you should see a <strong>new</strong> warning.</p>
+                    <p>Clear your Magento cache, reload your page, and you should see a <strong>new</strong> warning.</p>
 
-<pre>Warning: include(Magentotutorial/Complexworld/Model/Resource/Eavblogpost.php)</pre>
+                    <pre>Warning: include(Magentotutorial/Complexworld/Model/Resource/Eavblogpost.php)</pre>
 
-<p>As expected, we need to create a class for our Model's resource. Let's do it!</p>
+                    <p>As expected, we need to create a class for our Model's resource. Let's do it!</p>
 
-<p>File: app/code/local/Magentotutorial/Complexworld/Model/Resource/Eavblogpost.php:
-<pre>
+                    <p>File: app/code/local/Magentotutorial/Complexworld/Model/Resource/Eavblogpost.php:
+                    <pre>
 class Magentotutorial_Complexworld_Model_Resource_Eavblogpost extends Mage_Eav_Model_Entity_Abstract
 {
     protected function _construct()
@@ -210,21 +427,21 @@ <h2>Where Does That File Go?</h2>
 }
 </pre>
 
-<p>So, already we're seeing a few differences between a simple Model Resource and an EAV Model Resource. First off, we're extending the <tt>Mage_Eav_Model_Entity_Abstract</tt> class.  While <tt>Mage_Eav_Model_Entity_Abstract</tt> uses the same <tt>_construct</tt> concept as a regular Model Resource, there's no <tt>_init</tt> method.  Instead, we need to handle the init ourselves.  This means telling the resource what connection-resources it should use, and passing a unique identifier into the <tt>setType</tt> method of our object.</p>
+                    <p>So, already we're seeing a few differences between a simple Model Resource and an EAV Model Resource. First off, we're extending the <tt>Mage_Eav_Model_Entity_Abstract</tt> class.  While <tt>Mage_Eav_Model_Entity_Abstract</tt> uses the same <tt>_construct</tt> concept as a regular Model Resource, there's no <tt>_init</tt> method.  Instead, we need to handle the init ourselves.  This means telling the resource what connection-resources it should use, and passing a unique identifier into the <tt>setType</tt> method of our object.</p>
 
-<p>Another difference in <tt> Mage_Eav_Model_Entity_Abstract</tt> is <tt>_construct</tt> is <strong>not</strong> an abstract method, primarily for reasons of backwards compatibility with older versions of the system. </p>
+                    <p>Another difference in <tt> Mage_Eav_Model_Entity_Abstract</tt> is <tt>_construct</tt> is <strong>not</strong> an abstract method, primarily for reasons of backwards compatibility with older versions of the system. </p>
 
-<p>So, with that, let's clear the Magento cache and reload the page.  You should see a new exception which reads</p>
+                    <p>So, with that, let's clear the Magento cache and reload the page.  You should see a new exception which reads</p>
 
-<pre>Invalid entity_type specified: complexworld_eavblogpost</pre>
+                    <pre>Invalid entity_type specified: complexworld_eavblogpost</pre>
 
-<p>Magento is complaining that it can't find a entity_type named <tt>complexworld_eavblogpost</tt>.  This is the value you set above</p>
+                    <p>Magento is complaining that it can't find a entity_type named <tt>complexworld_eavblogpost</tt>.  This is the value you set above</p>
 
-<pre>$this->setType('complexworld_eavblogpost');</pre>
+                    <pre>$this->setType('complexworld_eavblogpost');</pre>
 
-<p>Every entity has a type.  Types will, among other things, let the EAV system know which attributes a Model uses, and allow the system to link to tables that store the values for attributes.  We'll need to let Magento know that we're adding a new entity type.  Take a look in the MySQL table named <tt>eav_entity_type</tt>.</p>
+                    <p>Every entity has a type.  Types will, among other things, let the EAV system know which attributes a Model uses, and allow the system to link to tables that store the values for attributes.  We'll need to let Magento know that we're adding a new entity type.  Take a look in the MySQL table named <tt>eav_entity_type</tt>.</p>
 
-<pre>
+                    <pre>
 mysql> select * from eav_entity_type;
 *************************** 1. row ***************************
           entity_type_id: 1
@@ -258,23 +475,23 @@ <h2>Where Does That File Go?</h2>
       increment_pad_char: 0
 </pre>
 
-<p>This table contains a list of all the entity_types in the system.  The unique identifier <tt>complexworld_eavblogpost</tt> corresponds to the <tt>entity_type_code</tt> column.</p>
+                    <p>This table contains a list of all the entity_types in the system.  The unique identifier <tt>complexworld_eavblogpost</tt> corresponds to the <tt>entity_type_code</tt> column.</p>
 
-<h2>Systems and Applications</h2>
+                    <h2>Systems and Applications</h2>
 
-<p>This illustrates the single most important Magento concept, one that many people struggle to learn.  </p>
+                    <p>This illustrates the single most important Magento concept, one that many people struggle to learn.  </p>
 
-<p>Consider the computer in front of you.  The OS (Mac OS X, Windows, Linux, etc.) is the software system.  Your web browser (Firefox, Safari, IE, Opera) is the application.  Magento <strong>is a system</strong> first, and an application second.  You build eCommerce applications using the Magento system.  What gets confusing is, there's a lot of places in Magento where the system code is exposed in a really raw form to the application code.  The EAV system configuration living in the same database as your store's data is an example of this.</p>
+                    <p>Consider the computer in front of you.  The OS (Mac OS X, Windows, Linux, etc.) is the software system.  Your web browser (Firefox, Safari, IE, Opera) is the application.  Magento <strong>is a system</strong> first, and an application second.  You build eCommerce applications using the Magento system.  What gets confusing is, there's a lot of places in Magento where the system code is exposed in a really raw form to the application code.  The EAV system configuration living in the same database as your store's data is an example of this.</p>
 
-<p>If you're going to get deep into Magento, you need to treat it like it's an old <a href="http://en.wikipedia.org/wiki/IBM_650" target="_new">Type 650</a> machine.  That is to say, it's the kind of thing you can't effectively program applications in unless unless you have a deep understanding of the system itself.</p>
+                    <p>If you're going to get deep into Magento, you need to treat it like it's an old <a href="http://en.wikipedia.org/wiki/IBM_650" target="_new">Type 650</a> machine.  That is to say, it's the kind of thing you can't effectively program applications in unless unless you have a deep understanding of the system itself.</p>
 
-<h2>Creating a Setup Resource</h2>
+                    <h2>Creating a Setup Resource</h2>
 
-<p>So, it's theoretically possible to manually insert the rows you'll need into the Magento database to get your Model working, but it's not recommended.  Fortunately, Magento provides a specialized <a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Setup Resource</a> that provides a number of helper method that will automatically create the needed records to get the system up and running.</p>
+                    <p>So, it's theoretically possible to manually insert the rows you'll need into the Magento database to get your Model working, but it's not recommended.  Fortunately, Magento provides a specialized <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">Setup Resource</a> that provides a number of helper method that will automatically create the needed records to get the system up and running.</p>
 
-<p>So, for starters, configure the Setup Resource like you would any other.</p>
+                    <p>So, for starters, configure the Setup Resource like you would any other.</p>
 
-<pre>
+                    <pre>
 &lt;global>
     &lt;!-- ... -->
     &lt;resources>
@@ -289,34 +506,34 @@ <h2>Creating a Setup Resource</h2>
 &lt;/global>
 </pre>
 
-<p>Next, create its class file.</p>
+                    <p>Next, create its class file.</p>
 
-<p>File: app/code/local/Magentotutorial/Complexworld/Model/Resource/Setup.php:
-<pre>
+                    <p>File: app/code/local/Magentotutorial/Complexworld/Model/Resource/Setup.php:
+                    <pre>
 class Magentotutorial_Complexworld_Model_Resource_Setup extends Mage_Eav_Model_Entity_Setup {
 }
 </pre>
 
-<p>Take note that we're extending from <tt>Mage_Eav_Model_Entity_Setup</tt> rather than <tt>Mage_Core_Model_Resource_Setup</tt>.</p>
+                    <p>Take note that we're extending from <tt>Mage_Eav_Model_Entity_Setup</tt> rather than <tt>Mage_Core_Model_Resource_Setup</tt>.</p>
 
-<p>Finally, we'll set up our installer script.  If you're not familiar with the naming conventions here, you'll want to review the <a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">setup resource tutorial</a> on Setup Resources.</p>
+                    <p>Finally, we'll set up our installer script.  If you're not familiar with the naming conventions here, you'll want to review the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">setup resource tutorial</a> on Setup Resources.</p>
 
-<p>File: app/code/local/Magentotutorial/Complexworld/sql/complexworld_setup/install-0.1.0.php:
-<pre>
+                    <p>File: app/code/local/Magentotutorial/Complexworld/sql/complexworld_setup/install-0.1.0.php:
+                    <pre>
 &lt;?php
 $installer = $this;
 throw new Exception("This is an exception to stop the installer from completing");
 </pre>
 
-<p>Clear your Magento Cache, reload you page, and the above exception should be thrown, meaning you've correctly configured your Setup Resource.</p>
+                    <p>Clear your Magento Cache, reload you page, and the above exception should be thrown, meaning you've correctly configured your Setup Resource.</p>
 
-<p><strong>NOTE:</strong> We'll be building up our install script piece by piece. If you've read the <a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">previous tutorial</a>, you'll know you need to remove the setup's row from the <tt>core_resource</tt> table and clear your cache to make an installer script re-run.  For the remainder of this tutorial, please remember that anytime we add or remove an item from our installer and re-run it, you'll need to remove this row from the database and clear your Magento cache.  Normally you would create this file and run it once, a tutorial is something of an edge case.</p>
+                    <p><strong>NOTE:</strong> We'll be building up our install script piece by piece. If you've read the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">previous tutorial</a>, you'll know you need to remove the setup's row from the <tt>core_resource</tt> table and clear your cache to make an installer script re-run.  For the remainder of this tutorial, please remember that anytime we add or remove an item from our installer and re-run it, you'll need to remove this row from the database and clear your Magento cache.  Normally you would create this file and run it once, a tutorial is something of an edge case.</p>
 
-<h2>Adding the Entity Type</h2>
+                    <h2>Adding the Entity Type</h2>
 
-<p>To begin, add the following to your Setup Resource installer script, and then run the script by loading any page (after removing the above exception)</p>
+                    <p>To begin, add the following to your Setup Resource installer script, and then run the script by loading any page (after removing the above exception)</p>
 
-<pre>
+                    <pre>
 $installer = $this;
 $installer->startSetup();
 $installer->addEntityType('complexworld_eavblogpost', array(
@@ -330,29 +547,29 @@ <h2>Adding the Entity Type</h2>
 $installer->endSetup();
 </pre>
 
-<p>We're calling the <tt>addEntityType</tt> method on our installer object.  This method allows us to pass in the entity type (<tt>complexworld_eavblogpost</tt>) along with a list of parameters to set its default values.  If you've run this script, you'll notice new rows in the <tt>eav_attribute_group</tt>, <tt>eav_attribute_set</tt>, and <tt>eav_entity_type</tt> tables.</p>
+                    <p>We're calling the <tt>addEntityType</tt> method on our installer object.  This method allows us to pass in the entity type (<tt>complexworld_eavblogpost</tt>) along with a list of parameters to set its default values.  If you've run this script, you'll notice new rows in the <tt>eav_attribute_group</tt>, <tt>eav_attribute_set</tt>, and <tt>eav_entity_type</tt> tables.</p>
 
-<p>So, with that in place, if we reload our complexworld page, we'll get a new error.</p>
+                    <p>So, with that in place, if we reload our complexworld page, we'll get a new error.</p>
 
-<pre>SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento.eavblog_posts' doesn't exist</pre>
+                    <pre>SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento.eavblog_posts' doesn't exist</pre>
 
-<h2>Creating the Data Tables</h2>
+                    <h2>Creating the Data Tables</h2>
 
-<p>So, we've told Magento about our new entity type.  Next, we need to add the MySQL tables that will be used to store all the entity values, as well as configure the system so it knows about these tables.</p>
+                    <p>So, we've told Magento about our new entity type.  Next, we need to add the MySQL tables that will be used to store all the entity values, as well as configure the system so it knows about these tables.</p>
 
-<p>Our EAV Setup Resource has a method named <tt>createEntityTables</tt> which will automatically setup the tables we need, as well as add some configuration rows to the system.  Let's add the following line to our setup resource.</p>
+                    <p>Our EAV Setup Resource has a method named <tt>createEntityTables</tt> which will automatically setup the tables we need, as well as add some configuration rows to the system.  Let's add the following line to our setup resource.</p>
 
-<pre>
+                    <pre>
 $installer->createEntityTables(
     $this->getTable('complexworld/eavblogpost')
 );
 </pre>
 
-<p>The <tt>createEntityTables</tt> method accepts two parameters.  The first is the base table name, the second is a list of options.  We're using the Setup Resource's <tt>getTable</tt> method to pull the table name from our config.  If you've been following along, you know this should resolve to the string <tt>eavblog_posts</tt>.  We've omitted the second parameter which is an array of options you'll only need to used it for advanced situations that are beyond the scope of this tutorial.</p>
+                    <p>The <tt>createEntityTables</tt> method accepts two parameters.  The first is the base table name, the second is a list of options.  We're using the Setup Resource's <tt>getTable</tt> method to pull the table name from our config.  If you've been following along, you know this should resolve to the string <tt>eavblog_posts</tt>.  We've omitted the second parameter which is an array of options you'll only need to used it for advanced situations that are beyond the scope of this tutorial.</p>
 
-<p>After running the above script, you should have the following new tables in your database</p>
+                    <p>After running the above script, you should have the following new tables in your database</p>
 
-<pre>
+                    <pre>
 eavblog_posts
 eavblog_posts_char
 eavblog_posts_datetime
@@ -362,9 +579,9 @@ <h2>Creating the Data Tables</h2>
 eavblog_posts_varchar
 </pre>
 
-<p>You'll also have an additional row in the <tt>eav_attribute_set</tt> table</p>
+                    <p>You'll also have an additional row in the <tt>eav_attribute_set</tt> table</p>
 
-<pre>mysql> select * from eav_attribute_set order by attribute_set_id DESC LIMIT 1 \G
+                    <pre>mysql> select * from eav_attribute_set order by attribute_set_id DESC LIMIT 1 \G
 *************************** 1. row ***************************
   attribute_set_id: 65
     entity_type_id: 37
@@ -372,23 +589,23 @@ <h2>Creating the Data Tables</h2>
         sort_order: 6
 </pre>
 
-<p>So, let's go back to our page and reload.  </p>
+                    <p>So, let's go back to our page and reload.  </p>
 
-<pre>http://example.com/complexworld</pre>
+                    <pre>http://example.com/complexworld</pre>
 
-<p>Success!  You should see no errors or warnings, and a dumped <tt>Magentotutorial_Complexworld_Model_Eavblogpost</tt> --- with no data.</p>
+                    <p>Success!  You should see no errors or warnings, and a dumped <tt>Magentotutorial_Complexworld_Model_Eavblogpost</tt> --- with no data.</p>
 
-<h2>Adding Attributes</h2>
+                    <h2>Adding Attributes</h2>
 
-<p>The last step we need to take in our Setup Resource is telling Magento what attributes we want our EAV Model to have.  This would be equivalent to adding new columns in a single database table setup.  Again, the Setup Resource will help us.  The method we're interested in is <tt>addAttribute</tt>.</p>
+                    <p>The last step we need to take in our Setup Resource is telling Magento what attributes we want our EAV Model to have.  This would be equivalent to adding new columns in a single database table setup.  Again, the Setup Resource will help us.  The method we're interested in is <tt>addAttribute</tt>.</p>
 
-<p>The code from the previous section was simply telling Magento about a <strong>type</strong> of entity that we add to the system.  These next bits of code are what will actually add possible attributes for our new type to the system.  </p>
+                    <p>The code from the previous section was simply telling Magento about a <strong>type</strong> of entity that we add to the system.  These next bits of code are what will actually add possible attributes for our new type to the system.  </p>
 
-<p>We do that with the method <tt>addAttribute</tt>. When we call <tt>addAttribute</tt>, Magento will need to do several things to install your entities.</p>
+                    <p>We do that with the method <tt>addAttribute</tt>. When we call <tt>addAttribute</tt>, Magento will need to do several things to install your entities.</p>
 
-<p>To start with, we'll give our Eavblogpost a single attribute named title.</p>
+                    <p>To start with, we'll give our Eavblogpost a single attribute named title.</p>
 
-<pre>
+                    <pre>
 /* ... */
 $this->addAttribute('complexworld_eavblogpost', 'title', array(
     //the EAV attribute type, NOT a MySQL varchar
@@ -407,19 +624,19 @@ <h2>Adding Attributes</h2>
 /* ... */
 </pre>
 
-<p>All right, that's a small pile of code.  Let's break it apart. </p>
+                    <p>All right, that's a small pile of code.  Let's break it apart. </p>
 
-<p>The first argument to <tt>addAttribute</tt> is the entity type code. It has to match the code specified when calling addEntityType. It tells Magento which entity we are adding the attribute to, in our example it is our <tt>complexworld_eavblogpost</tt> entity. To see other available entities that come shipped with Magento, remember you can look into the <tt>eav_entity_type</tt> table at the <tt>entity_type_code</tt> column.</p>
+                    <p>The first argument to <tt>addAttribute</tt> is the entity type code. It has to match the code specified when calling addEntityType. It tells Magento which entity we are adding the attribute to, in our example it is our <tt>complexworld_eavblogpost</tt> entity. To see other available entities that come shipped with Magento, remember you can look into the <tt>eav_entity_type</tt> table at the <tt>entity_type_code</tt> column.</p>
 
-<p>The second argument to <tt>addAttribute</tt> is the attribute code. It has to be unique within the given entity.</p>
+                    <p>The second argument to <tt>addAttribute</tt> is the attribute code. It has to be unique within the given entity.</p>
 
-<p>The third argument is where it get real interesting. This is an array of key value pairs, describing the attribute properties.  For the sake of simplicity we've chose to define a single attribute, but you could go on to define as many as you'd like, by adding additional addAttribute calls to the setup script.</p>
+                    <p>The third argument is where it get real interesting. This is an array of key value pairs, describing the attribute properties.  For the sake of simplicity we've chose to define a single attribute, but you could go on to define as many as you'd like, by adding additional addAttribute calls to the setup script.</p>
 
-<h2>Array of Key Value Pairs that Define the Attribute</h2>
+                    <h2>Array of Key Value Pairs that Define the Attribute</h2>
 
-<p>Finally, we have a long list of attribute properties.</p>
+                    <p>Finally, we have a long list of attribute properties.</p>
 
-<pre>
+                    <pre>
 //the EAV attribute type, NOT a MySQL varchar
 'type'              => 'varchar',
 'label'             => 'Title',
@@ -434,14 +651,14 @@ <h2>Array of Key Value Pairs that Define the Attribute</h2>
 'unique'            => false,
 </pre>
 
-<p>Most of these define how Magento would build a backend form element for this attribute, and probably you'll won't have to deal with the,. That said, the one important property you'll want to make note of is </p>
-<pre>
+                    <p>Most of these define how Magento would build a backend form element for this attribute, and probably you'll won't have to deal with the,. That said, the one important property you'll want to make note of is </p>
+                    <pre>
 'type' => 'varchar'
 </pre>
 
-<p>This defines the type of the value that the attribute will contain.  You'll recall that we added table for each attribute type</p>
+                    <p>This defines the type of the value that the attribute will contain.  You'll recall that we added table for each attribute type</p>
 
-<pre>
+                    <pre>
 eavblog_posts_datetime
 eavblog_posts_decimal
 eavblog_posts_int
@@ -449,11 +666,11 @@ <h2>Array of Key Value Pairs that Define the Attribute</h2>
 eavblog_posts_varchar
 </pre>
 
-<p>While these do not refer to the MySQL column types, (but instead the EAV attribute types), their names (varchar, datetime, etc.) are indicative of the values they'll hold.</p>
+                    <p>While these do not refer to the MySQL column types, (but instead the EAV attribute types), their names (varchar, datetime, etc.) are indicative of the values they'll hold.</p>
 
-<p>All of these attribute properties are optional, if we wouldn't have specified them, Magento would have used a default value. These default values are defined in the <tt>_prepareValues</tt> method of the <tt>Mage_Eav_Model_Entity_Setup</tt> class (inherited by our setup class).</p>
+                    <p>All of these attribute properties are optional, if we wouldn't have specified them, Magento would have used a default value. These default values are defined in the <tt>_prepareValues</tt> method of the <tt>Mage_Eav_Model_Entity_Setup</tt> class (inherited by our setup class).</p>
 
-<pre>
+                    <pre>
 // Mage_Eav_Model_Entity_Setup
 protected function _prepareValues($attr)
 {
@@ -480,13 +697,13 @@ <h2>Array of Key Value Pairs that Define the Attribute</h2>
 }
 </pre>
 
-<p>The second argument to the method calls to <tt>_getValue</tt> is the array key from our addAttribute argument array, and the third is the default value. So by default Magento would assume you are adding a varchar attribute with a text input.</p>
+                    <p>The second argument to the method calls to <tt>_getValue</tt> is the array key from our addAttribute argument array, and the third is the default value. So by default Magento would assume you are adding a varchar attribute with a text input.</p>
 
-<h2>Adding the other attributes</h2>
+                    <h2>Adding the other attributes</h2>
 
-<p>Lets add attributes for the blog post content and the post date. This is what the complete install script looks like.</p>
+                    <p>Lets add attributes for the blog post content and the post date. This is what the complete install script looks like.</p>
 
-<pre>
+                    <pre>
     $installer = $this;
     $installer->startSetup();
 
@@ -532,21 +749,21 @@ <h2>Adding the other attributes</h2>
     $installer->endSetup();
 </pre>
 
-<p>So, now that we have everything in place, lets refresh things one last time to run our installer script.  After calling <tt>addAttribute</tt>, we should have </p>
+                    <p>So, now that we have everything in place, lets refresh things one last time to run our installer script.  After calling <tt>addAttribute</tt>, we should have </p>
 
-<ol>
-<li>A new row in <tt>eav_entity_type</tt> for the <strong>complexworld_eavblogpost</strong> entity type</li>
-<li>A new row in <tt>eav_attribute</tt> for the <strong>title</strong> attribute</li>
-<li>A new row in <tt>eav_attribute</tt> for the <strong>content</strong> attribute</li>
-<li>A new row in <tt>eav_attribute</tt> for the <strong>date</strong> attribute</li>
-<li>A new row in <tt>eav_entity_attribute</tt></li>
-</ol>
+                    <ol>
+                        <li>A new row in <tt>eav_entity_type</tt> for the <strong>complexworld_eavblogpost</strong> entity type</li>
+                        <li>A new row in <tt>eav_attribute</tt> for the <strong>title</strong> attribute</li>
+                        <li>A new row in <tt>eav_attribute</tt> for the <strong>content</strong> attribute</li>
+                        <li>A new row in <tt>eav_attribute</tt> for the <strong>date</strong> attribute</li>
+                        <li>A new row in <tt>eav_entity_attribute</tt></li>
+                    </ol>
 
-<h2>Tying it all Together</h2>
+                    <h2>Tying it all Together</h2>
 
-<p>This is clearly the lamest.blogmodel.ever, but lets try adding some rows and iterating through a collection and get the heck out of here before our heads explode.  Add the following two actions to your Index Controller.</p>
+                    <p>This is clearly the lamest.blogmodel.ever, but lets try adding some rows and iterating through a collection and get the heck out of here before our heads explode.  Add the following two actions to your Index Controller.</p>
 
-<pre>
+                    <pre>
 public function populateEntriesAction() {
     for ($i=0;$i&lt;10;$i++) {
         $weblog2 = Mage::getModel('complexworld/eavblogpost');
@@ -576,13 +793,13 @@ <h2>Tying it all Together</h2>
 }
 </pre>
 
-<p>Let's populate some entries!  Load up the following URL</p>
+                    <p>Let's populate some entries!  Load up the following URL</p>
 
-<pre>http://magento.dev/index.php/complexworld/index/populateEntries</pre>
+                    <pre>http://magento.dev/index.php/complexworld/index/populateEntries</pre>
 
-<p>If you take a look at your database, you should see 10 new rows in the <tt>eavblog_posts</tt> table.</p>
+                    <p>If you take a look at your database, you should see 10 new rows in the <tt>eavblog_posts</tt> table.</p>
 
-<pre>
+                    <pre>
 mysql> SELECT * FROM eavblog_posts ORDER BY entity_id DESC;
 +-----------+----------------+------------------+--------------+-----------+----------+---------------------+---------------------+-----------+
 | entity_id | entity_type_id | attribute_set_id | increment_id | parent_id | store_id | created_at          | updated_at          | is_active |
@@ -600,9 +817,9 @@ <h2>Tying it all Together</h2>
 +-----------+----------------+------------------+--------------+-----------+----------+---------------------+---------------------+-----------+
 </pre>
 
-<p>as well as 10 new rows in the <tt>eavblog_posts_varchar</tt> table.</p>
+                    <p>as well as 10 new rows in the <tt>eavblog_posts_varchar</tt> table.</p>
 
-<pre>
+                    <pre>
 mysql> SELECT * FROM eavblog_posts_varchar ORDER BY value_id DESC;
 +----------+----------------+--------------+----------+-----------+------------------+
 | value_id | entity_type_id | attribute_id | store_id | entity_id | value            |
@@ -620,21 +837,21 @@ <h2>Tying it all Together</h2>
 +----------+----------------+--------------+----------+-----------+------------------+
 </pre>
 
-<p>Notice that <tt>eavblog_posts_varchar</tt> is linked to <tt>eavblog_posts</tt> by the <tt>entity_id</tt> column.</p>
+                    <p>Notice that <tt>eavblog_posts_varchar</tt> is linked to <tt>eavblog_posts</tt> by the <tt>entity_id</tt> column.</p>
 
-<p>Finally, let's pull our Models back out. Load the following URL in your browser</p>
+                    <p>Finally, let's pull our Models back out. Load the following URL in your browser</p>
 
-<pre>http://magento.dev/index.php/complexworld/index/showCollection</pre>
+                    <pre>http://magento.dev/index.php/complexworld/index/showCollection</pre>
 
-<p>This should give us a </p>
+                    <p>This should give us a </p>
 
-<pre>Warning: include(Magentotutorial/Complexworld/Model/Resource/Eavblogpost/Collection.php) [function.include]: 
+                    <pre>Warning: include(Magentotutorial/Complexworld/Model/Resource/Eavblogpost/Collection.php) [function.include]:
   failed to open stream: No such file or directory  in /Users/username/Sites/magento.dev/lib/Varien/Autoload.php on line 93</pre>
 
-<p><strong>So Close!</strong>  We didn't make a class for our collection object!  Fortunately, doing so is just as easy as with a regular Model Resource.  Add the following file with the following contents</p>
+                    <p><strong>So Close!</strong>  We didn't make a class for our collection object!  Fortunately, doing so is just as easy as with a regular Model Resource.  Add the following file with the following contents</p>
 
-<p>File: Magentotutorial/Complexworld/Model/Resource/Eavblogpost/Collection.php:
-<pre>
+                    <p>File: Magentotutorial/Complexworld/Model/Resource/Eavblogpost/Collection.php:
+                    <pre>
 class Magentotutorial_Complexworld_Model_Resource_Eavblogpost_Collection extends Mage_Eav_Model_Entity_Collection_Abstract
 {
     protected function _construct()
@@ -644,30 +861,85 @@ <h2>Tying it all Together</h2>
 }
 </pre>
 
-<p>This is just a standard Magento <tt>_construct</tt> method to initialize the Model. With this in place, reload the page, and we'll see all the titles and the content outputted. But notice, the date value is missing!</p>
+                    <p>This is just a standard Magento <tt>_construct</tt> method to initialize the Model. With this in place, reload the page, and we'll see all the titles and the content outputted. But notice, the date value is missing!</p>
 
-<h2>Which Attributes?</h2>
+                    <h2>Which Attributes?</h2>
 
-<p>Those of you with sharp eyes may have noticed something slightly different about the collection loading.</p>
+                    <p>Those of you with sharp eyes may have noticed something slightly different about the collection loading.</p>
 
-<pre>
+                    <pre>
 $entries = $weblog2->getCollection()
     ->addAttributeToSelect('title')
     ->addAttributeToSelect('content');
 </pre>
 
-<p>Because querying for EAV data can be SQL intensive, you'll need to specify which attributes it is you want your Models to fetch for you.  This way the system can make only the queries it needs. If you're willing to suffer the performance consequences, you can use a wild card to grab <strong>all</strong> the attributes</p>
-
-<pre>$entries = $weblog2->getCollection()->addAttributeToSelect('*');</pre>
-
-<h2>Jumping Off</h2>
-
-<p>So, that should give you enough information to be dangerous, or at least enough information so you're not drowning the next time you're trying to figure out why the yellow shirts aren't showing up in your store.  There's still plenty to learn about EAV; here's a few topics I would have liked to cover in greater detail, and may talk about in future articles</p>
-
-<ol>
-<li>EAV Attributes: Attributes aren't limited to datetime, decimal, int, text and varchar.  You can create your own class files to model different attributes.  This is what the <tt>attribute_model</tt> entity property is for.</li>
-<li>Collection Filtering: Filtering on EAV collections can get tricky, especially when you're dealing with the above mentioned non-simple attributes.  You need to use the <tt>addAttributeToFilter</tt> method on your collection before loading.</li>
-<li>The Magento EAV Hierarchy: Magento has taken their basic EAV Model and built up a hierarchy that's very tied to store functionality, as well as including strategies to reduce the number of queries an EAV Model generates (the concept of a <strong>flat</strong> Model, for example)</li>
-</ol>
+                    <p>Because querying for EAV data can be SQL intensive, you'll need to specify which attributes it is you want your Models to fetch for you.  This way the system can make only the queries it needs. If you're willing to suffer the performance consequences, you can use a wild card to grab <strong>all</strong> the attributes</p>
+
+                    <pre>$entries = $weblog2->getCollection()->addAttributeToSelect('*');</pre>
+
+                    <h2>Jumping Off</h2>
+
+                    <p>So, that should give you enough information to be dangerous, or at least enough information so you're not drowning the next time you're trying to figure out why the yellow shirts aren't showing up in your store.  There's still plenty to learn about EAV; here's a few topics I would have liked to cover in greater detail, and may talk about in future articles</p>
+
+                    <ol>
+                        <li>EAV Attributes: Attributes aren't limited to datetime, decimal, int, text and varchar.  You can create your own class files to model different attributes.  This is what the <tt>attribute_model</tt> entity property is for.</li>
+                        <li>Collection Filtering: Filtering on EAV collections can get tricky, especially when you're dealing with the above mentioned non-simple attributes.  You need to use the <tt>addAttributeToFilter</tt> method on your collection before loading.</li>
+                        <li>The Magento EAV Hierarchy: Magento has taken their basic EAV Model and built up a hierarchy that's very tied to store functionality, as well as including strategies to reduce the number of queries an EAV Model generates (the concept of a <strong>flat</strong> Model, for example)</li>
+                    </ol>
+
+                    <p>EAV Models are, without a doubt, the most complicated part of the Magento system that an ecommerce web developer will need to deal with.  Remember to take deep breaths and that, at the end of the day, its just programming.  Everything happens for a concrete reason, you just need to figure out why.</p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
 
-<p>EAV Models are, without a doubt, the most complicated part of the Magento system that an ecommerce web developer will need to deal with.  Remember to take deep breaths and that, at the end of the day, its just programming.  Everything happens for a concrete reason, you just need to figure out why.</p>
\ No newline at end of file
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
\ No newline at end of file
diff --git a/guides/m1x/magefordev/mage-for-dev-8.html b/guides/m1x/magefordev/mage-for-dev-8.html
index 130f445977..308226dc29 100644
--- a/guides/m1x/magefordev/mage-for-dev-8.html
+++ b/guides/m1x/magefordev/mage-for-dev-8.html
@@ -1,73 +1,289 @@
 ---
 ---
 <!DOCTYPE html>
-<html lang=en>
-
+<html lang="en" dir="ltr">
 <head>
-    <meta charset=utf-8>
-
-    <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
-    <link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
-    <link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
-    <title>Magento for Developers: Part 8&mdash;Varien Data Collections</title>
-
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>OpenMage for Developers: Part 8&mdash;Varien Data Collections</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-
-<img src="{{ site.baseurl }}/guides/m1x/images/m1xheader.png" width="1024" alt="header" />
-{% include m1x/eol_message.html %}
-
-<div id="content">
-<h1>Magento for Developers: Part 8&mdash;Varien Data Collections</h1>
-<p><em>by Alan Storm</em>, updated for Magento 1.12</p>
-<p><a href="{{ site.m1xgithuburl }}/magefordev/mage-for-dev-8.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>
-
-
-<!-- Magento for Developers: Part 8&mdash;Varien Data Collections -->
-<!-- magento-for-dev-part-8-varien-data-collections 
-
-<style type="text/css">
-#kb-entry .series {float: right; width: 175px; margin-left: 10px; font-size: 12px; }
-#kb-entry .series ul {margin-left: 15px;}
-</style> 
-<div class="r-box-rss series">  -->
-
-
-<h5>Other articles in this series:</h5>
-<ul>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-1.html">Part 1&mdash;Introduction to Magento</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-2.html">Part 2&mdash;The Magento Config</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-3.html">Part 3&mdash;Magento Controller Dispatch</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-4.html">Part 4&mdash;Magento Layouts, Blocks and Templates</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-5.html">Part 5&mdash;Magento Models and ORM Basics</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-6.html">Part 6&mdash;Magento Setup Resources</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-7.html">Part 7&mdash;Advanced ORM: Entity Attribute Value</a>
-<li><a href="{{ site.m1xgdeurl }}/magefordev/mage-for-dev-8.html">Part 8&mdash;Varien Data Collections</a>
-</ul>
-</div>
-
-<p class="para1">Originally, as a PHP programmer, if you wanted to collect together a group of related variables you had one choice, the venerable <a href="http://us.php.net/manual/en/language.types.array.php">Array</a>.  While it shares a name with C's array of memory addresses, a PHP array is a general purpose dictionary like object combined with the behaviors of a numerically indexed mutable array.</p>
-
-<p>In other languages the choice isn't so simple.  You have <a href="http://en.wikipedia.org/wiki/List_of_data_structures#Linear_data_structures">multiple data structures</a> to chose from, each offering particular advantages in storage, speed and semantics.  The PHP philosophy was to remove this choice from the client programmer and give them one useful data structure that was "good enough".  </p>
-
-<p>All of this is galling to a certain type of software developer, and PHP 5 set out to change the status quo by offering built-in classes and interfaces that allow you to create your own data structures.  </p>
-
-<pre>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
+                                    Introduction to OpenMage
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
+                                    The OpenMage Config
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
+                                    OpenMage Controller Dispatch
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
+                                    OpenMage Layouts, Blocks and Templates
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
+                                    OpenMage Models and ORM Basics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
+                                    OpenMage Setup Resources
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">
+                                    Advanced ORM: Entity Attribute Value
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-8.html">
+                                    Varien Data Collections
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Varien Data Collections</h1>
+                    </section>
+
+                    <p class="para1">Originally, as a PHP programmer, if you wanted to collect together a group of related variables you had one choice, the venerable <a href="http://us.php.net/manual/en/language.types.array.php">Array</a>.  While it shares a name with C's array of memory addresses, a PHP array is a general purpose dictionary like object combined with the behaviors of a numerically indexed mutable array.</p>
+
+                    <p>In other languages the choice isn't so simple.  You have <a href="http://en.wikipedia.org/wiki/List_of_data_structures#Linear_data_structures">multiple data structures</a> to chose from, each offering particular advantages in storage, speed and semantics.  The PHP philosophy was to remove this choice from the client programmer and give them one useful data structure that was "good enough".  </p>
+
+                    <p>All of this is galling to a certain type of software developer, and PHP 5 set out to change the status quo by offering built-in classes and interfaces that allow you to create your own data structures.  </p>
+
+                    <pre>
 $array = new ArrayObject();
 class MyCollection extends ArrayObject{...}
 $collection = new MyCollection();
 $collection[] = 'bar';
 </pre>
 
-<p>While this is still galling to a certain type of software developer, as you don't have access to low level implementation details, you do have the ability to create array-like Objects with methods that encapsulate specific functionality.  You can also setup rules to offer a level of type safety by only allowing certain kinds of Objects into your Collection.</p>
+                    <p>While this is still galling to a certain type of software developer, as you don't have access to low level implementation details, you do have the ability to create array-like Objects with methods that encapsulate specific functionality.  You can also setup rules to offer a level of type safety by only allowing certain kinds of Objects into your Collection.</p>
 
-<p>It should come as no surprise that Magento offers you a number of these Collections.  In fact, every Model object that follows the Magento interfaces gets a Collection type for free.  Understanding how these Collections work is a key part to being an effective Magento programmer.  We're going to take a look at Magento Collections, starting from the bottom and working our way up.  Set up a <a href="http://alanstorm.com/magento_controller_hello_world">controller action</a> where you can run arbitrary code, and let's get started.</p>
+                    <p>It should come as no surprise that Magento offers you a number of these Collections.  In fact, every Model object that follows the Magento interfaces gets a Collection type for free.  Understanding how these Collections work is a key part to being an effective Magento programmer.  We're going to take a look at Magento Collections, starting from the bottom and working our way up.  Set up a <a href="http://alanstorm.com/magento_controller_hello_world">controller action</a> where you can run arbitrary code, and let's get started.</p>
 
-<h2 id="a-collection-of-things">A Collection of Things</h2>
+                    <h2 id="a-collection-of-things">A Collection of Things</h2>
 
-<p>First, we're going to create a few new Objects.</p>
+                    <p>First, we're going to create a few new Objects.</p>
 
-<pre>
+                    <pre>
 $thing_1 = new Varien_Object();
 $thing_1->setName('Richard');
 $thing_1->setAge(24);
@@ -82,35 +298,35 @@ <h2 id="a-collection-of-things">A Collection of Things</h2>
 $thing_3->setAge(7);
 </pre>
 
-<p>The <tt>Varien_Object</tt> class defines the object all Magento Models inherit from.  This is a common pattern in object oriented systems, and ensures you'll always have a way to easily add methods/functionally to <strong>every</strong> object in your system without having to edit every class file.</p>
+                    <p>The <tt>Varien_Object</tt> class defines the object all Magento Models inherit from.  This is a common pattern in object oriented systems, and ensures you'll always have a way to easily add methods/functionally to <strong>every</strong> object in your system without having to edit every class file.</p>
 
-<p>Any Object that extends from <tt>Varien_Object</tt> has magic getter and setters that can be used to set data properties. Give this a try</p>
+                    <p>Any Object that extends from <tt>Varien_Object</tt> has magic getter and setters that can be used to set data properties. Give this a try</p>
 
-<pre>var_dump($thing_1->getName());</pre>
+                    <pre>var_dump($thing_1->getName());</pre>
 
-<p>If you don't know what the property name you're after is, you can pull out all the data as an array</p>
+                    <p>If you don't know what the property name you're after is, you can pull out all the data as an array</p>
 
-<pre>var_dump($thing_3->getData());</pre>
+                    <pre>var_dump($thing_3->getData());</pre>
 
-<p>The above will give you an array something like</p>
+                    <p>The above will give you an array something like</p>
 
 
-<pre>
+                    <pre>
 array
 'name' => string 'Spot' (length=4)
 'last_name' => string 'The Dog' (length=7)
 'age' => int 7
 </pre>
 
-<p>Notice the property named "last_name"?  If there's an underscore separated property, you camel case it if you want to use the getter and setter magic.</p>
+                    <p>Notice the property named "last_name"?  If there's an underscore separated property, you camel case it if you want to use the getter and setter magic.</p>
 
-<pre>$thing_1->setLastName('Smith');</pre>
+                    <pre>$thing_1->setLastName('Smith');</pre>
 
-<p>The ability to do these kinds of things is part of the power of PHP5, and the development style a certain class of people mean when they say "Object Oriented Programming".</p>
+                    <p>The ability to do these kinds of things is part of the power of PHP5, and the development style a certain class of people mean when they say "Object Oriented Programming".</p>
 
-<p>So, now that we have some Objects, let's add them to a Collection.  Remember, a Collection is like an Array, but is defined by a PHP programmer.  </p>
+                    <p>So, now that we have some Objects, let's add them to a Collection.  Remember, a Collection is like an Array, but is defined by a PHP programmer.  </p>
 
-<pre>
+                    <pre>
 $collection_of_things = new Varien_Data_Collection();
 $collection_of_things
     ->addItem($thing_1)
@@ -118,44 +334,44 @@ <h2 id="a-collection-of-things">A Collection of Things</h2>
     ->addItem($thing_3);
 </pre>
 
-<p>The <tt>Varien_Data_Collection</tt> is the Collection that most Magento data Collections inherit from.  Any method you can call on a <tt>Varien_Data_Collection</tt> you can call on Collections higher up the chain (We'll see more of this later)</p>
+                    <p>The <tt>Varien_Data_Collection</tt> is the Collection that most Magento data Collections inherit from.  Any method you can call on a <tt>Varien_Data_Collection</tt> you can call on Collections higher up the chain (We'll see more of this later)</p>
 
-<p>What can we do with a Collection?  For one, with can use <tt>foreach</tt> to iterate over it</p>
+                    <p>What can we do with a Collection?  For one, with can use <tt>foreach</tt> to iterate over it</p>
 
-<pre>
+                    <pre>
 foreach($collection_of_things as $thing)
 {
     var_dump($thing->getData());
 }
 </pre>
 
-<p>There are also shortcuts for pulling out the first and last items</p>
+                    <p>There are also shortcuts for pulling out the first and last items</p>
 
-<pre>
+                    <pre>
 var_dump($collection_of_things->getFirstItem()->getData());
 var_dump($collection_of_things->getLastItem()->getData());
 </pre>
 
-<p>Want your Collection data as XML?  There's a method for that</p>
+                    <p>Want your Collection data as XML?  There's a method for that</p>
 
-<pre>var_dump( $collection_of_things->toXml() );</pre>
+                    <pre>var_dump( $collection_of_things->toXml() );</pre>
 
-<p>Only want a particular field?</p>
+                    <p>Only want a particular field?</p>
 
-<pre>var_dump($collection_of_things->getColumnValues('name'));</pre>
+                    <pre>var_dump($collection_of_things->getColumnValues('name'));</pre>
 
-<p>The team at Magento have even given us some rudimentary filtering capabilities.</p>
+                    <p>The team at Magento have even given us some rudimentary filtering capabilities.</p>
 
-<pre>var_dump($collection_of_things->getItemsByColumnValue('name','Spot'));</pre>
+                    <pre>var_dump($collection_of_things->getItemsByColumnValue('name','Spot'));</pre>
 
-<p>Neat stuff.</p>
+                    <p>Neat stuff.</p>
 
-<h2 id="model-collections">Model Collections</h2>
-<p>So, this is an interesting exercise, but why do we care? </p>
+                    <h2 id="model-collections">Model Collections</h2>
+                    <p>So, this is an interesting exercise, but why do we care? </p>
 
-<p>We care because all of Magento's built in data Collections inherit from this object.  That means if you have, say, a product Collection you can do the same sort of things.  Let's take a look </p>
+                    <p>We care because all of Magento's built in data Collections inherit from this object.  That means if you have, say, a product Collection you can do the same sort of things.  Let's take a look </p>
 
-<pre>
+                    <pre>
 public function testAction()
 {
     $collection_of_products = Mage::getModel('catalog/product')->getCollection();
@@ -163,13 +379,13 @@ <h2 id="model-collections">Model Collections</h2>
 }
 </pre>
 
-<p>Most Magento Model objects have a method named <tt>getCollection</tt> which will return a collection that, by default, is initialized to return every Object of that type in the system.</p>
+                    <p>Most Magento Model objects have a method named <tt>getCollection</tt> which will return a collection that, by default, is initialized to return every Object of that type in the system.</p>
 
-<p><strong>A Quick Note:</strong>  Magento's Data Collections contain a lot of complicated logic that handles when to use an index or cache, as well as the logic for the EAV entity system.  Successive method calls to the same Collection over its life can often result in unexpected behavior.  Because of that, all the of the following examples are wrapped in a single method action.  I'd recommend doing the same while you're experimenting.  Also, <a href="http://xdebug.org/">XDebug's</a> <tt>var_dump</tt> is a godsend when working with Magento Objects and Collections, as it will (usually) intelligently short circuit showing hugely recursive Objects, but still display a useful representation of the Object structure to you.</p>
+                    <p><strong>A Quick Note:</strong>  Magento's Data Collections contain a lot of complicated logic that handles when to use an index or cache, as well as the logic for the EAV entity system.  Successive method calls to the same Collection over its life can often result in unexpected behavior.  Because of that, all the of the following examples are wrapped in a single method action.  I'd recommend doing the same while you're experimenting.  Also, <a href="http://xdebug.org/">XDebug's</a> <tt>var_dump</tt> is a godsend when working with Magento Objects and Collections, as it will (usually) intelligently short circuit showing hugely recursive Objects, but still display a useful representation of the Object structure to you.</p>
 
-<p>The products Collection, as well as many other Magento Collections, also have the <tt>Varien_Data_Collection_Db</tt> class in their ancestor chain. This gives us a lot of useful methods.  For example, if you want to see the select statement your Collection is using</p>
+                    <p>The products Collection, as well as many other Magento Collections, also have the <tt>Varien_Data_Collection_Db</tt> class in their ancestor chain. This gives us a lot of useful methods.  For example, if you want to see the select statement your Collection is using</p>
 
-<pre>
+                    <pre>
 public function testAction()
 {
     $collection_of_products = Mage::getModel('catalog/product')->getCollection();
@@ -177,9 +393,9 @@ <h2 id="model-collections">Model Collections</h2>
 }
 </pre>
 
-<p>The output of the above will be</p>
+                    <p>The output of the above will be</p>
 
-<pre>
+                    <pre>
 object(Varien_Db_Select)[94]
   protected '_bind' =>
     array
@@ -188,9 +404,9 @@ <h2 id="model-collections">Model Collections</h2>
 ...
 </pre>
 
-<p>Whoops! Since Magento is using the <tt>Zend</tt> database abstraction layer, your Select is also an Object.  Let's see that as a more useful string. </p>
+                    <p>Whoops! Since Magento is using the <tt>Zend</tt> database abstraction layer, your Select is also an Object.  Let's see that as a more useful string. </p>
 
-<pre>
+                    <pre>
 public function testAction()
 {
     $collection_of_products = Mage::getModel('catalog/product')->getCollection();
@@ -201,40 +417,40 @@ <h2 id="model-collections">Model Collections</h2>
 }
 </pre>
 
-<p>Sometimes this is going to result in a simple select</p>
+                    <p>Sometimes this is going to result in a simple select</p>
 
-<pre>'SELECT `e`.* FROM `catalog_product_entity` AS `e`'</pre>
+                    <pre>'SELECT `e`.* FROM `catalog_product_entity` AS `e`'</pre>
 
-<p>Other times, something a bit more complex</p>
+                    <p>Other times, something a bit more complex</p>
 
-<pre>
-string 'SELECT `e`.*, `price_index`.`price`, `price_index`.`final_price`, IF(`price_index`.`tier_price`, 
-LEAST(`price_index`.`min_price`, `price_index`.`tier_price`), `price_index`.`min_price`) AS `minimal_price`, 
-`price_index`.`min_price`, `price_index`.`max_price`, `price_index`.`tier_price` FROM `catalog_product_entity` 
-AS `e` INNER JOIN `catalog_product_index_price` AS `price_index` ON price_index.entity_id = e.entity_id AND 
+                    <pre>
+string 'SELECT `e`.*, `price_index`.`price`, `price_index`.`final_price`, IF(`price_index`.`tier_price`,
+LEAST(`price_index`.`min_price`, `price_index`.`tier_price`), `price_index`.`min_price`) AS `minimal_price`,
+`price_index`.`min_price`, `price_index`.`max_price`, `price_index`.`tier_price` FROM `catalog_product_entity`
+AS `e` INNER JOIN `catalog_product_index_price` AS `price_index` ON price_index.entity_id = e.entity_id AND
 price_index.website_id = '1' AND price_index.customer_group_id = 0'
 </pre>
 
-<p>The discrepancy depends on which attributes you're selecting, as well as the aforementioned indexing and cache.  If you've been following along with the other articles in this series,  you know that many Magento models (including the Product Model) use an <a href="http://en.wikipedia.org/wiki/EAV">EAV</a> system.  By default, a EAV Collection will not include all of an Object's attributes.  You can add them all by using the addAttributeToSelect method</p>
+                    <p>The discrepancy depends on which attributes you're selecting, as well as the aforementioned indexing and cache.  If you've been following along with the other articles in this series,  you know that many Magento models (including the Product Model) use an <a href="http://en.wikipedia.org/wiki/EAV">EAV</a> system.  By default, a EAV Collection will not include all of an Object's attributes.  You can add them all by using the addAttributeToSelect method</p>
 
-<pre>
+                    <pre>
 $collection_of_products = Mage::getModel('catalog/product')
     ->getCollection()
     ->addAttributeToSelect('*');  //the asterisk is like a SQL SELECT * FROM ...
 </pre>
 
-<p>Or, you can add just one</p>
+                    <p>Or, you can add just one</p>
 
-<pre>
+                    <pre>
 //or just one
 $collection_of_products = Mage::getModel('catalog/product')
     ->getCollection()
     ->addAttributeToSelect('meta_title');
 </pre>
 
-<p>or chain together several</p>
+                    <p>or chain together several</p>
 
-<pre>
+                    <pre>
 //or just one
 $collection_of_products = Mage::getModel('catalog/product')
     ->getCollection()
@@ -242,40 +458,40 @@ <h2 id="model-collections">Model Collections</h2>
     ->addAttributeToSelect('price');
 </pre>
 
-<h2 id="lazy-loading">Lazy Loading</h2>
+                    <h2 id="lazy-loading">Lazy Loading</h2>
 
-<p>One thing that will trip up PHP developers new to Magento's ORM system is <strong>when</strong> Magento makes its database calls.  When you're writing literal SQL, or even when you're using a basic ORM system, SQL calls are often made immediately when instantiating an Object.</p>
+                    <p>One thing that will trip up PHP developers new to Magento's ORM system is <strong>when</strong> Magento makes its database calls.  When you're writing literal SQL, or even when you're using a basic ORM system, SQL calls are often made immediately when instantiating an Object.</p>
 
-<pre>
+                    <pre>
 $model = new Customer();
 //SQL Calls being made to Populate the Object
 echo 'Done'; //execution continues
 </pre>
 
-<p>Magento doesn't work that way.  Instead, the concept of <a href="http://en.wikipedia.org/wiki/Lazy_loading">Lazy Loading</a> is used.  In simplified terms, Lazy loading means that no SQL calls are made until the client-programmer needs to access the data.  That means when you do something something like this</p>
+                    <p>Magento doesn't work that way.  Instead, the concept of <a href="http://en.wikipedia.org/wiki/Lazy_loading">Lazy Loading</a> is used.  In simplified terms, Lazy loading means that no SQL calls are made until the client-programmer needs to access the data.  That means when you do something something like this</p>
 
-<pre>
+                    <pre>
 $collection_of_products = Mage::getModel('catalog/product')
     ->getCollection();
 </pre>
 
-<p>Magento actually hasn't gone out to the database yet.  You can safely add attributes later</p>
+                    <p>Magento actually hasn't gone out to the database yet.  You can safely add attributes later</p>
 
-<pre>
+                    <pre>
 $collection_of_products = Mage::getModel('catalog/product')
     ->getCollection();
 $collection_of_products->addAttributeToSelect('meta_title');
 </pre>
 
-<p>and not have to worry that Magento is making a database query each time a new attribute is added.  The database query will not be made until you attempt to access an item in the Collection.</p>
+                    <p>and not have to worry that Magento is making a database query each time a new attribute is added.  The database query will not be made until you attempt to access an item in the Collection.</p>
 
-<p>In general, try not to worry too much about the implementation details in your day to day work.  It's good to know that there's s SQL backend and Magento is doing SQLy things, but when you're coding up a feature try to forget about it, and just treat the objects as block boxes that do what you need.  </p>
+                    <p>In general, try not to worry too much about the implementation details in your day to day work.  It's good to know that there's s SQL backend and Magento is doing SQLy things, but when you're coding up a feature try to forget about it, and just treat the objects as block boxes that do what you need.  </p>
 
-<h2 id="filtering-database-collections">Filtering Database Collections</h2>
+                    <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 
-<p>The most important method on a database Collection is <tt>addFieldToFilter</tt>.  This adds your <tt>WHERE</tt> clauses to the SQL query being used behind the scenes.  Consider this bit of code, run against the sample data database (substitute your own SKU is you're using a different set of product data)</p>
+                    <p>The most important method on a database Collection is <tt>addFieldToFilter</tt>.  This adds your <tt>WHERE</tt> clauses to the SQL query being used behind the scenes.  Consider this bit of code, run against the sample data database (substitute your own SKU is you're using a different set of product data)</p>
 
-<pre>
+                    <pre>
 public function testAction()
 {
     $collection_of_products = Mage::getModel('catalog/product')
@@ -288,21 +504,21 @@ <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 }
 </pre>
 
-<p>The first parameter of <tt>addFieldToFilter</tt> is the attribute you wish to filter by.  The second is the value you're looking for. Here's we're adding a <tt>sku</tt> filter for the value <tt>n2610</tt>.</p>
+                    <p>The first parameter of <tt>addFieldToFilter</tt> is the attribute you wish to filter by.  The second is the value you're looking for. Here's we're adding a <tt>sku</tt> filter for the value <tt>n2610</tt>.</p>
 
-<p>The second parameter can also be used to specify the <strong>type</strong> of filtering you want to do. This is where things get a little complicated, and worth going into with a little more depth.</p>
+                    <p>The second parameter can also be used to specify the <strong>type</strong> of filtering you want to do. This is where things get a little complicated, and worth going into with a little more depth.</p>
 
-<p>So by default, the following </p>
+                    <p>So by default, the following </p>
 
-<pre>$collection_of_products->addFieldToFilter('sku','n2610');</pre>
+                    <pre>$collection_of_products->addFieldToFilter('sku','n2610');</pre>
 
-<p>is (essentially) equivalent to </p>
+                    <p>is (essentially) equivalent to </p>
 
-<pre>WHERE sku = "n2610"</pre>
+                    <pre>WHERE sku = "n2610"</pre>
 
-<p>Take a look for yourself.  Running the following</p>
+                    <p>Take a look for yourself.  Running the following</p>
 
-<pre>
+                    <pre>
 public function testAction()
 {
     var_dump(
@@ -314,13 +530,13 @@ <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 }
 </pre>
 
-<p>will yield</p>
+                    <p>will yield</p>
 
-<pre>SELECT `e`.* FROM `catalog_product_entity` AS `e` WHERE (e.sku = 'n2610')'</pre>
+                    <pre>SELECT `e`.* FROM `catalog_product_entity` AS `e` WHERE (e.sku = 'n2610')'</pre>
 
-<p>Keep in mind, this can get complicated fast if you're using an EAV attribute.  Add an attribute</p>
+                    <p>Keep in mind, this can get complicated fast if you're using an EAV attribute.  Add an attribute</p>
 
-<pre>
+                    <pre>
 var_dump(
     (string)
     Mage::getModel('catalog/product')
@@ -331,9 +547,9 @@ <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 );
 </pre>
 
-<p>and the query gets gnarly.</p>
+                    <p>and the query gets gnarly.</p>
 
-<pre>
+                    <pre>
 SELECT `e`.*, IF(_table_meta_title.value_id>0, _table_meta_title.value, _table_meta_title_default.value) AS `meta_title`
 FROM `catalog_product_entity` AS `e`
 INNER JOIN `catalog_product_entity_varchar` AS `_table_meta_title_default`
@@ -345,15 +561,15 @@ <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 WHERE (IF(_table_meta_title.value_id>0, _table_meta_title.value, _table_meta_title_default.value) = 'my title')
 </pre>
 
-<p>Not to belabor the point, but try not to think too much about the SQL if you're on deadline.</p>
+                    <p>Not to belabor the point, but try not to think too much about the SQL if you're on deadline.</p>
 
-<h2 id="other-comparison-operators">Other Comparison Operators</h2>
+                    <h2 id="other-comparison-operators">Other Comparison Operators</h2>
 
-<p>I'm sure you're wondering "what if I want something other than an equals by query"?  Not equal, greater than, less than, etc.  The <tt>addFieldToFilter</tt> method's second parameter has you covered there as well.  It supports an alternate syntax where, instead of passing in a string, you pass in a single element Array.  </p>
+                    <p>I'm sure you're wondering "what if I want something other than an equals by query"?  Not equal, greater than, less than, etc.  The <tt>addFieldToFilter</tt> method's second parameter has you covered there as well.  It supports an alternate syntax where, instead of passing in a string, you pass in a single element Array.  </p>
 
-<p>The key of this array is the <strong>type</strong> of comparison you want to make.  The value associated with that key is the value you want to filter by.  Let's redo the above filter, but with this explicit syntax</p>
+                    <p>The key of this array is the <strong>type</strong> of comparison you want to make.  The value associated with that key is the value you want to filter by.  Let's redo the above filter, but with this explicit syntax</p>
 
-<pre>public function testAction()
+                    <pre>public function testAction()
 {
     var_dump(
         (string)
@@ -365,17 +581,17 @@ <h2 id="other-comparison-operators">Other Comparison Operators</h2>
 }
 </pre>
 
-<p>Calling out our filter</p>
+                    <p>Calling out our filter</p>
 
-<pre>addFieldToFilter('sku',array('eq'=>'n2610'))</pre>
+                    <pre>addFieldToFilter('sku',array('eq'=>'n2610'))</pre>
 
-<p>As you can see, the second parameter is a PHP Array.  Its key is <tt>eq</tt>, which stands for <em>equals</em>.  The value for this key is <tt>n2610</tt>, which is the value we're filtering on.</p>
+                    <p>As you can see, the second parameter is a PHP Array.  Its key is <tt>eq</tt>, which stands for <em>equals</em>.  The value for this key is <tt>n2610</tt>, which is the value we're filtering on.</p>
 
-<p>Magento has a number of these english language like filters that will bring a <a href="http://www.shlomifish.org/lecture/Perl/Newbies/lecture1/conditionals/string.html">tear of remembrance</a> (and perhaps pain) to any old perl developers in the audience.</p>
+                    <p>Magento has a number of these english language like filters that will bring a <a href="http://www.shlomifish.org/lecture/Perl/Newbies/lecture1/conditionals/string.html">tear of remembrance</a> (and perhaps pain) to any old perl developers in the audience.</p>
 
-<p>Listed below are all the filters, along with an example of their SQL equivalents.</p>
+                    <p>Listed below are all the filters, along with an example of their SQL equivalents.</p>
 
-<pre>
+                    <pre>
 array("eq"=>'n2610')
 WHERE (e.sku = 'n2610')
 
@@ -425,30 +641,30 @@ <h2 id="other-comparison-operators">Other Comparison Operators</h2>
 WHERE e.sku >= '10' and e.sku &lt;= '20'
 </pre>
 
-<p>Most of these are self explanatory, but a few deserve a special callout</p>
+                    <p>Most of these are self explanatory, but a few deserve a special callout</p>
 
-<h3>in, nin, find_in_set</h3>
+                    <h3>in, nin, find_in_set</h3>
 
-<p>The <tt>in</tt>, <tt>nin</tt> and <tt>finset</tt> conditionals allow you to pass in an Array of values.  That is, the value portion of your filter array is itself allowed to be an array.  </p>
+                    <p>The <tt>in</tt>, <tt>nin</tt> and <tt>finset</tt> conditionals allow you to pass in an Array of values.  That is, the value portion of your filter array is itself allowed to be an array.  </p>
 
-<pre>
+                    <pre>
 array("in"=>array('n2610','ABC123')
 WHERE (e.sku in ('n2610','ABC123'))
 </pre>
 
-<h3>notnull, null</h3>
+                    <h3>notnull, null</h3>
 
-<p>The keyword NULL is special in most flavors of SQL. It typically won't play nice with the standard equality (<tt>=</tt>) operator.  Specifying <tt>notnull</tt> or <tt>null</tt> as your filter type will get you the correct syntax for a NULL comparison while ignoring whatever value you pass in</p>
+                    <p>The keyword NULL is special in most flavors of SQL. It typically won't play nice with the standard equality (<tt>=</tt>) operator.  Specifying <tt>notnull</tt> or <tt>null</tt> as your filter type will get you the correct syntax for a NULL comparison while ignoring whatever value you pass in</p>
 
-<pre>
+                    <pre>
 array("notnull"=>true)
 WHERE (e.sku is NOT NULL)
 </pre>
 
-<h3>from - to filter</h3>
-<p>This is another special format that breaks the standard rule.  Instead of a single element array, you specify a two element array.  One element has the key <tt>from</tt>, the other element has the key <tt>to</tt>.  As the keys indicated, this filter allows you to construct a from/to range without having to worry about greater than and less than symbols</p>
+                    <h3>from - to filter</h3>
+                    <p>This is another special format that breaks the standard rule.  Instead of a single element array, you specify a two element array.  One element has the key <tt>from</tt>, the other element has the key <tt>to</tt>.  As the keys indicated, this filter allows you to construct a from/to range without having to worry about greater than and less than symbols</p>
 
-<pre>
+                    <pre>
 public function testAction
 {
     var_dump(
@@ -461,14 +677,14 @@ <h3>from - to filter</h3>
 }
 </pre>
 
-<p>The above yields</p>
-<pre>WHERE (_table_price.value >= '10' and _table_price.value &lt;= '20')'</pre>
+                    <p>The above yields</p>
+                    <pre>WHERE (_table_price.value >= '10' and _table_price.value &lt;= '20')'</pre>
 
-<h2 id="and-or-or">AND or OR, or is that OR and AND?</h2>
+                    <h2 id="and-or-or">AND or OR, or is that OR and AND?</h2>
 
-<p>Finally, we come to the boolean operators.  It's the rare moment where we're only filtering by one attribute.  Fortunately, Magento's Collections have us covered.  You can chain together multiple calls to <tt>addFieldToFilter</tt> to get a number of "AND" queries.</p>
+                    <p>Finally, we come to the boolean operators.  It's the rare moment where we're only filtering by one attribute.  Fortunately, Magento's Collections have us covered.  You can chain together multiple calls to <tt>addFieldToFilter</tt> to get a number of "AND" queries.</p>
 
-<pre>
+                    <pre>
 function testAction()
 {
     echo
@@ -481,15 +697,15 @@ <h2 id="and-or-or">AND or OR, or is that OR and AND?</h2>
 }
 </pre>
 
-<p>By chaining together multiple calls as above, we'll produce a where clause that looks something like the following</p>
+                    <p>By chaining together multiple calls as above, we'll produce a where clause that looks something like the following</p>
 
-<pre>WHERE (e.sku like 'a%') AND (e.sku like 'b%')</pre>
+                    <pre>WHERE (e.sku like 'a%') AND (e.sku like 'b%')</pre>
 
-<p>To those of you that just raised your hand, yes, the above example would always return 0 records. No sku can begin with BOTH an <tt>a</tt> and a <tt>b</tt>.  What we probably want here is an <tt>OR</tt> query.  This brings us to another confusing aspect of <tt>addFieldToFilter</tt>'s second parameter.</p>
+                    <p>To those of you that just raised your hand, yes, the above example would always return 0 records. No sku can begin with BOTH an <tt>a</tt> and a <tt>b</tt>.  What we probably want here is an <tt>OR</tt> query.  This brings us to another confusing aspect of <tt>addFieldToFilter</tt>'s second parameter.</p>
 
-<p>If you want to build an <tt>OR</tt> query, you need to pass an Array of filter Arrays in as the second parameter.  I find it's best to assign your individual filter Arrays to variables </p>
+                    <p>If you want to build an <tt>OR</tt> query, you need to pass an Array of filter Arrays in as the second parameter.  I find it's best to assign your individual filter Arrays to variables </p>
 
-<pre>
+                    <pre>
 public function testAction()
 {
     $filter_a = array('like'=>'a%');
@@ -497,8 +713,8 @@ <h2 id="and-or-or">AND or OR, or is that OR and AND?</h2>
 }
 </pre>
 
-<p>and then assign an array of all my filter variables</p>
-<pre>
+                    <p>and then assign an array of all my filter variables</p>
+                    <pre>
 public function testAction()
 {
     $filter_a = array('like'=>'a%');
@@ -512,13 +728,69 @@ <h2 id="and-or-or">AND or OR, or is that OR and AND?</h2>
 }
 </pre>
 
-<p>In the interest of being explicit, here's the aforementioned array of filter arrays.</p>
-<pre>array($filter_a, $filter_b)</pre>
-
-<p>This will gives us a WHERE clause that looks something like the following</p>
-
-<pre>WHERE (((e.sku like 'a%') or (e.sku like 'b%'))) </pre>
-
-<h2 id="wrap-up">Wrap Up</h2>
+                    <p>In the interest of being explicit, here's the aforementioned array of filter arrays.</p>
+                    <pre>array($filter_a, $filter_b)</pre>
+
+                    <p>This will gives us a WHERE clause that looks something like the following</p>
+
+                    <pre>WHERE (((e.sku like 'a%') or (e.sku like 'b%'))) </pre>
+
+                    <h2 id="wrap-up">Wrap Up</h2>
+
+                    <p>You're now a Magento developer walking around with some serious firepower.  Without having to write a single line of SQL you now know how to query Magento for any Model your store or application might need. </p>
+
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
 
-<p>You're now a Magento developer walking around with some serious firepower.  Without having to write a single line of SQL you now know how to query Magento for any Model your store or application might need. </p>
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
\ No newline at end of file
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-1.html b/guides/m1x/magefordev/mage-for-frontend-dev-1.html
new file mode 100644
index 0000000000..afbea55dff
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-1.html
@@ -0,0 +1,421 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Introduction</h1>
+                    </section>
+
+                    <p>Magento Enterprise Edition 1.14 and Magento Community Edition 1.9 come with a new theme named <tt>rwd</tt> that
+                        implements <a href="http://en.wikipedia.org/wiki/Responsive_web_design" target="_blank">Responsive Web Design
+                            (RWD) practices</a>. This guide discusses what you need to know when customizing your own responsive theme.
+                    </p>
+                    <p>Magento CE's and EE's responsive theme uses a number of new technologies:</p>
+                    <ul>
+                        <li><a href="http://beta.compass-style.org/" target="_blank">Sass/Compass</a>: A CSS pre-compiler that provides
+                            organizable, reusable CSS.
+                        </li>
+                        <li><a href="http://jquery.com/" target="_blank">jQuery</a>: Used for all custom JavaScript in the responsive
+                            theme. jQuery operates in <tt>noConflict()</tt> mode so it doesn't conflict with Magento's existing
+                            JavaScript library.
+                        </li>
+                        <li>Additional JavaScript libraries discussed in more detail in
+                            <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html#customize-theme-js">
+                                Working With JavaScript
+                            </a>.
+                        </li>
+                    </ul>
+                    <p>If you're not familiar with Sass or Compass, you should familiarize yourself with them before continuing with
+                        this guide.</p>
+                    <ul>
+                        <li>Sass
+                            <ul>
+                                <li><a href="http://sass-lang.com/guide" target="_blank">Quick-Start Guide</a></li>
+                                <li><a href="http://sass-lang.com/documentation/file.SASS_REFERENCE.html" target="_blank">Full
+                                    Documentation</a></li>
+                            </ul>
+                        </li>
+                        <li><a href="http://beta.compass-style.org/" target="_blank">Compass</a></li>
+                    </ul>
+                    <p>The new responsive theme code is contained in the following directories (relative to your Magento installation
+                        directory):</p>
+                    <ul>
+                        <li><tt>app/design/frontend/rwd</tt></li>
+                        <li><tt>skin/frontend/rwd</tt></li>
+                    </ul>
+                    <p>See one of the following sections for more information:</p>
+
+                    <h2>Intended Audience</h2>
+                    <p>This guide assumes that you have a good understanding of Magento frontend development and Responsive Web Design
+                        techniques.</p>
+
+                    <h2 id="intro-convention">Documentation Conventions and Assumptions</h2>
+                    <p>This section discusses some basic information that applies to this guide.</p>
+
+                    <h4>Documentation Conventions</h4>
+                    <p>This guide uses the names <tt>custompackage</tt> and <tt>customtheme</tt> for the design package and theme. When
+                        you build your own responsive theme, use a more descriptive name, such as the name of your company.</p>
+                    <p>The variable value <tt>[your Magento install dir]</tt> refers to the directory in which you installed Magento CE
+                        or EE. Typical values follow:</p>
+                    <ul>
+                        <li>Ubuntu: <tt>/var/www/magento</tt></li>
+                        <li>CentOS: <tt>/var/www/html/magento</tt></li>
+                    </ul>
+
+                    <h4>Assumption: How You Customize CSS</h4>
+                    <p>You have two choices to write your custom CSS styles:</p>
+                    <ul>
+                        <li>Write CSS in the Sass stylesheets using the same structure that the Magento responsive theme uses. This
+                            approach requires setting up a Compass compiler, but is <em>strongly</em> recommended. This guide assumes
+                            you'll use this approach.
+                        </li>
+                        <li>Directly modify the CSS files that ship with the responsive theme and ignore the Sass files. While this
+                            approach might be simpler in the short run, the CSS files in the responsive theme were output by the Sass
+                            compiler and are therefore not conducive to being customized directly. This approach is <em>not</em>
+                            recommended.
+                        </li>
+                    </ul>
+
+                    <h2>Exceptions to Responsive Web Design</h2>
+                    <p>Responsive design was <em>not</em> implemented for the following:</p>
+                    <ul>
+                        <li>Multiple address checkout</li>
+                        <li>Popular search terms page</li>
+                        <li>Popular search terms cloud</li>
+                        <li>Site map</li>
+                        <li>My Account&mdash;Billing Agreements</li>
+                        <li>My Account&mdash;Recurring Profiles</li>
+                        <li>E-mail templates</li>
+                        <li>Tags</li>
+                        <li>Polls</li>
+                        <li>Captcha</li>
+                        <li>The gift registry <em>(EE only)</em></li>
+                        <li>Multiple wishlists <em>(EE only)</em></li>
+                        <li>Place order by SKU <em>(EE only)</em></li>
+                    </ul>
+                    <div class="msg-box important"><img src="{{ site.baseurl }}{{ site.v1xgdeurl }}images/icon-note.png" alt="note" align="left"
+                                                        width="40"><span><strong>Note</strong>: Magento still supports other non-responsive themes as well. You don't need to use this guide to customize those themes. For more information, see the <a
+                            href="http://info.magento.com/rs/magentocommerce/images/MagentoDesignGuide.pdf" target="_blank">Designer's Guide to Magento</a>.
+    </span>
+                    </div>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-10.html b/guides/m1x/magefordev/mage-for-frontend-dev-10.html
new file mode 100644
index 0000000000..85e6d614c7
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-10.html
@@ -0,0 +1,335 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Getting Help With Your Theme</h1>
+                    </section>
+
+                    <p>If you encounter issues building a custom responsive theme, you can post your question on the community <a
+                            href="http://magento.stackexchange.com/questions/ask" target="_blank">magento.stackexchange.com</a> site and
+                        tag it with <tt>rwd-theme</tt>.</p>
+                    <p>To browse the list of questions, see <a href="http://magento.stackexchange.com/questions/tagged/rwd-theme"
+                                                               target="_blank">http://magento.stackexchange.com/questions/tagged/rwd-theme</a>.
+                    </p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-2.html b/guides/m1x/magefordev/mage-for-frontend-dev-2.html
new file mode 100644
index 0000000000..ab3583014a
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-2.html
@@ -0,0 +1,350 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Supported Devices and Browsers</h1>
+                    </section>
+
+                    <p>Magento's responsive theme was developed with full support for the following devices and browsers:</p>
+                    <ul>
+                        <li>Windows:
+                            <ul>
+                                <li>Internet Explorer 9 and later</li>
+                                <li>Latest stable version of Chrome</li>
+                                <li>Latest stable version of Firefox</li>
+                            </ul>
+                        </li>
+                        <li>OS X:
+                            <ul>
+                                <li>Latest stable version of Chrome</li>
+                                <li>Latest stable version of Firefox</li>
+                                <li>Latest stable version of Safari</li>
+                            </ul>
+                        </li>
+                        <li>iOs (iPhone and iPad): Safari on iOs 7</li>
+                        <li>Android: Chrome browser on Android 4.0+ (also known as Ice Cream Sandwich)</li>
+                    </ul>
+                    <p>Basic compatibility should be expected on Android 2.3+ (and other mobile devices) and Internet Explorer 8, but
+                        full support is not guaranteed.</p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-3.html b/guides/m1x/magefordev/mage-for-frontend-dev-3.html
new file mode 100644
index 0000000000..177b637e04
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-3.html
@@ -0,0 +1,380 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Understanding the Changes in the Responsive Theme</h1>
+                    </section>
+
+                    <p>The new responsive theme in EE 1.14 and CE 1.9 is based on the existing <tt>base/default</tt> theme. The new
+                        responsive theme has about 130 template files that have been modified to better handle the needs of responsive
+                        development. Following are some of the changes that have been made in these template files:</p>
+                    <ul>
+                        <li>Rearranged elements to work better with smaller viewports.</li>
+                        <li>Changed the <tt>Doctype</tt> to <tt>html</tt> to enable use of HTML5 elements. (To avoid large amounts of
+                            template modifications, HTML5 tags were implemented only when necessary.)
+                        </li>
+                        <li>Refactored attributes of <tt>&lt;input></tt> elements to HTML5 standards.</li>
+                        <li>Refactored product lists to show varying number of products per column.</li>
+                        <li>Removed all <tt>&lt;fieldset></tt> elements because they don't work well in a responsive context.</li>
+                    </ul>
+
+                    <h2>Changes to Layout Files</h2>
+                    <p>A number of the core layout files (<tt>catalog.xml</tt>, <tt>customer.xml</tt>) were slightly modified to account
+                        for responsive changes. There are only a few notable changes to the layout files:</p>
+                    <ul>
+                        <li><tt>
+                            <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html#intro-convention">
+                                [your Magento install dir]
+                            </a>
+                            /app/design/frontend/rwd/default/layout/page.xml</tt>
+                            was modified to include all of the new responsive assets.
+                        </li>
+                        <li>Because two and three column layouts collapse to a single column on smaller viewports, all content in the
+                            <tt>left</tt> block are displayed under the main content. This is a problem because blocks&mdash;like the
+                            navigation on all My Account pages&mdash;must display above the main content on smaller viewports. To
+                            address this, a new <tt>left_first</tt> block was added that looks like the left column on larger viewports,
+                            but on smaller viewports, it displays above the main content.
+                        </li>
+                    </ul>
+
+                    <h2>Using the New Theme/Layout Structure&mdash;<em>Magento EE only</em></h2>
+                    <p>If you've worked with a previous version of Magento EE, you're aware that the <tt>enterprise/default</tt> theme
+                        contains copies of <em>many</em> of the layout and template files from <tt>base/default</tt>&mdash;some with
+                        very minor changes. This is not an optimal approach because as it results in duplicated content.</p>
+                    <p>The Magento EE responsive theme's <tt>rwd/enterprise</tt> directory includes only template and layout files that
+                        contain Magento EE-only features.</p>
+                    <p>Instead of copying layout files as the <tt>enterprise/default</tt> theme does, <tt>rwd/enterprise</tt> isolates
+                        changes in their own layout files in <tt>[your Magento install
+                            dir]app/design/frontend/rwd/enterprise/layout/enterprise</tt></p>
+                    <p>The <tt>rwd/enterprise</tt> theme replaces the <tt>enterprise/default</tt> theme and contains <em>far</em> fewer
+                        files than its predecessor (156 compared to 280). This new approach makes it easier for you to see what
+                        functionality is unique to Magento EE.</p>
+
+                    <h2>Changes to Magento Theme Fallback</h2>
+                    <p>Magento CE 1.9 and EE 1.14 both introduce a theme configuration file named <tt>theme.xml</tt>. This file allows
+                        theme developers to specify a parent theme which results in a more predictable and useful fallback than earlier
+                        versions.</p>
+                    <p>For more information, see <a href="http://alanstorm.com/magento_parent_child_themes" target="_blank">Alan Storm's
+                        Parent/Child Theme article</a>.</p>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-4.html b/guides/m1x/magefordev/mage-for-frontend-dev-4.html
new file mode 100644
index 0000000000..7ff58c530c
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-4.html
@@ -0,0 +1,348 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Installing Compass and Sass</h1>
+                    </section>
+
+                    <p>Sass is a powerful CSS pre-compiler that extends CSS supports variables, mixins, and placeholders. Compass is a
+                        library for Sass that adds hundreds of useful mixins and functions to Sass&mdash;everything from color blending
+                        to sprite generation.</p>
+                    <p>Because the new Magento responsive theme uses the Compass library to compile its Sass files into CSS, you must
+                        install Compass in your development environment in any of the following ways:</p>
+                    <ul>
+                        <li><a href="http://beta.compass-style.org/install" target="_blank">Command line</a></li>
+                        <li>Using any of the following third-party applications:
+                            <ul>
+                                <li><a href="https://github.com/scout-app/scout-app" target="_blank">Scout</a></li>
+                                <li><a href="http://compass.kkbox.com" target="_blank">Compass App</a></li>
+                                <li><a href="https://codekitapp.com/" target="_blank">CodeKit</a></li>
+                            </ul>
+                        </li>
+                        <li>Compile using your code editor (PhpStorm, Sublime, and so on): Many code editors run Compass from the editor
+                            so that you don't have to use the command line to re-compile when you make changes. However, you must
+                            install Compass using the command line.
+                        </li>
+                    </ul>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-5.html b/guides/m1x/magefordev/mage-for-frontend-dev-5.html
new file mode 100644
index 0000000000..51c79a80d6
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-5.html
@@ -0,0 +1,351 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 id="disable-cache" class="page-heading">Disabling the Magento Cache</h1>
+                    </section>
+
+                    <p>A good practice during development on Magento is to disable Magento's cache. Although doing this adversely
+                        impacts performance, it frees you from having to manually clear the cache when you make changes to files or
+                        configuration settings that are being cached.</p>
+                    <p>You should always enable the cache in a production environment.</p>
+                    <p>To disable the cache:</p>
+                    <ol>
+                        <li>Log in to the Magento Admin Panel as an administrator.</li>
+                        <li>Click <strong>System</strong> > <strong>Configuration</strong> > <strong>Cache Management</strong>.</li>
+                        <li>On the Cache Management page, click <strong>Select All</strong>.<br/>
+                            <strong>Note</strong>: The <strong>Page Cache</strong> option at the bottom of the list is available only in
+                            Magento EE.
+                        </li>
+                        <li>From the <strong>Actions</strong> list in the upper right corner of the page, click <strong>Disable</strong>.
+                        </li>
+                        <li>Click <strong>Submit</strong>.<br/>
+                            The following figure shows an example.<br/>
+                            <img src="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/disable-cache.png" width="600px" height="173px"></li>
+                        <li>Click <strong>Submit</strong>.<br/>
+                            <p>The following figures shows all cache types disabled.<br/>
+                                <img src="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/disable-cache-confirm.png" width="600px" height="173px">
+                        </li>
+                    </ol>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-6.html b/guides/m1x/magefordev/mage-for-frontend-dev-6.html
new file mode 100644
index 0000000000..deac573fc8
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-6.html
@@ -0,0 +1,569 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 id="theme" class="page-heading">Copying Files to Create Your Custom Theme</h1>
+                    </section>
+
+                    <p>This section discusses how to start building a custom responsive theme. </p>
+
+                    <h2 id="theme-structure">Step 1: Creating a Directory Structure for Your Responsive Theme</h2>
+                    <p>You'll do your responsive theme development using a copy of the responsive theme provided with Magento CE and EE.
+                        This section discusses how to create new top-level directories for your theme and to copy files to those
+                        directories.</p>
+                    <p>The <tt>rwd/default</tt> theme falls back directly to the <tt>base/default</tt> theme, so themes in the <tt>default</tt>
+                        package will never be included as a part of the fallback chain.</p>
+                    <div class="msg-box important"><img src="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/icon-note.png" alt="note" align="left"
+                                                        width="40"><span><strong>Note</strong>: <em>Magento EE only.</em> The <tt>enterprise/default</tt> theme is completely replaced by <tt>rwd/enterprise</tt> and therefore, <tt>enterprise/default</tt> is not included as a part of the fallback chain.
+    </span>
+                    </div>
+
+                    <!-- <p>Magento CE 1.9 and Magento EE 1.14 have a new theme fallback structure that provides infinite levels of fallback. Learn more about this fallback structure in the <a href="#" style="color: red;">Magento Infinite Theme Fallback Structure</a> article.</p>
+                     -->
+                    <p>The top-level directories you'll need are:</p>
+                    <ul>
+                        <li><tt>[your Magento install dir]/app/design/frontend/custompackage/customtheme</tt></li>
+                        <li><tt>[your Magento install dir]/skin/frontend/custompackage/customtheme</tt></li>
+                    </ul>
+                    <p>To create those directories and to add your theme configuration:</p>
+                    <ol>
+                        <li>Using a command shell, log in to your Magento host as a user with privileges to write to the web server
+                            docroot. (Typically, this is the web server user.)
+                        </li>
+                        <li>Enter the following commands in the order shown:
+                            <pre>cd <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html#intro-convention">[your Magento install dir]</a>
+mkdir -p app/design/frontend/custompackage/customtheme
+mkdir -p skin/frontend/custompackage/customtheme</pre>
+                        </li>
+                        <li>Create another directory for your theme configuration and change to that directory:
+                            <pre>mkdir app/design/frontend/custompackage/customtheme/etc
+cd app/design/frontend/custompackage/customtheme/etc</pre>
+                        </li>
+                        <li>Use <tt>vim</tt> or another text editor to create your theme configuration file named <tt>theme.xml</tt>
+                            there:
+                            <pre>vim theme.xml</pre>
+                        </li>
+                        <li id="themexml"><tt>theme.xml</tt> must have different contents for Magento CE or Magento EE:
+                            <ul>
+                                <li>Magento CE:
+                                    <pre>
+                        <code>
+&lt;?xml version="1.0"?&gt;
+&lt;theme&gt;
+    &lt;parent&gt;rwd/default&lt;/parent&gt;
+&lt;/theme&gt;
+                        </code>
+                    </pre>
+                                </li>
+                                <li>Magento EE:
+                                    <pre>
+                        <code>
+&lt;?xml version="1.0"?&gt;
+&lt;theme&gt;
+    &lt;parent&gt;rwd/enterprise&lt;/parent&gt;
+&lt;/theme&gt;
+                        </code>
+                    </pre>
+                                </li>
+                                <div class="msg-box important"><img src="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/icon-important.png"
+                                                                    alt="important" align="left"
+                                                                    width="40"><span><strong>Important</strong>: It's very important you have a <tt>theme.xml</tt> in the <tt>app/design/frontend/custompackage/customtheme/etc</tt> directory with exactly the contents shown. Failure to configure <tt>theme.xml</tt> correctly prevents Magento from loading your theme.</span>
+                                </div>
+
+                            </ul>
+                        </li>
+                    </ol>
+
+                    <h2 id="theme-copyfiles">Step 2: Copying Files For Your Theme</h2>
+                    <p>Use the following commands to copy files for your custom theme:</p>
+                    <pre>cd <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html#intro-convention">[your Magento install dir]</a>
+cp -R skin/frontend/rwd/default/images skin/frontend/custompackage/customtheme
+cp -R skin/frontend/rwd/default/scss skin/frontend/custompackage/customtheme
+                        <!-- cp skin/frontend/rwd/default/scss/config.rb skin/frontend/custompackage/customtheme --></pre>
+                    <p>Copying the <tt>images</tt> directory is important because the CSS uses relative image paths. To avoid
+                        duplicating Sass files, review the information discussed in
+                        <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html#sass-fallback-structure">
+                            Sass Fallback Structure
+                        </a>.</p>
+                    <p>The following figure shows how your custom theme directory structure looks after copying these files and
+                        directories.</p>
+                    <img src="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/custom_skin-dir.png">
+
+                    <h3 id="theme-compass">Step 3: Configuring a Compass Watcher</h3>
+                    <p>You can configure Compass to watch your skin directories for changes to CSS and JavaScript and to compile them
+                        when something changes.</p>
+                    <p>You can do this in either of the following ways:</p>
+                    <ul>
+                        <li><em>(Recommended)</em> Using your PHP IDE. For example, if you use PhpStorm, see <a
+                                href="https://www.jetbrains.com/help/phpstorm/transpiling-compass-to-css.html"
+                                target="_blank">Working with Sass and SCSS in Compass Projects</a> and <a
+                                href="https://www.jetbrains.com/help/phpstorm/using-file-watchers.html" target="_blank">Using File
+                            Watchers</a>.
+                        </li>
+                        <li>Using following commands:
+                            <pre>cd <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html#intro-convention">[your Magento install dir]</a><em>/custom-theme-dir</em>/scss
+compass watch .</pre>
+                            For example, if Magento is installed in <tt>/var/www/html/magento</tt>, enter:
+                            <pre>cd /var/www/html/magento/skin/frontend/custompackage/customtheme/scss
+compass watch .</pre>
+                        </li>
+                    </ul>
+                    <p>For more information, see <a href="http://beta.compass-style.org/help/documentation/command-line/" target="_blank">Compass
+                        Command Line Documentation</a>.</p>
+
+                    <h4 id="theme-compass-success">Success Messages</h4>
+                    <p>Messages similar to the following display to indicate the command completed successfully:</p>
+                    <pre>>>> Change detected at 09:57:12 to: madisonisland-ie8.scss
+   create ./../css/madisonisland-ie8.css
+   create ./../css/styles.css
+   create ./../css/madisonisland.css
+   create ./../css/styles-ie8.css
+   create ./../css/scaffold-forms.css
+>>> Compass is polling for changes. Press Ctrl-C to Stop.
+</pre>
+
+                    <h4 id="theme-compass-fail">Failure Message</h4>
+                    <p>If the following message displays, it likely indicates that <tt>config.rb</tt> is not in the correct location:
+                    </p>
+                    <pre>Nothing to compile. If you're trying to start a new project, you have left off the directory argument.</pre>
+                    <p>Enter the following commands to verify you have <tt>config.rb</tt> in the correct location:</p>
+                    <pre>cd <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html#intro-convention">[your Magento install dir]</a>
+ls skin/frontend/custompackage/customtheme/scss</pre>
+                    <p>If there is no <tt>config.rb</tt> in that location, enter the following command:</p>
+                    <pre>cp skin/frontend/rwd/default/scss/config.rb skin/frontend/custompackage/customtheme/scss</pre>
+                    <p>Compass requires a <tt>config.rb</tt> file located in the directory from which you run this command. The sample
+                        provided with Magento CE and EE follows:</p>
+                    <pre><code>
+# note: this should never truly be referenced since we are using relative assets
+http_path = "/skin/frontend/rwd/default/"
+css_dir = "../css"
+sass_dir = "../scss"
+images_dir = "../images"
+javascripts_dir = "../js"
+relative_assets = true
+
+output_style = :expanded
+environment = :production
+        </code></pre>
+                    <p>After correcting the issue, try the <tt>compass watch</tt> commands discussed in <a href="#theme-compass">Step 3:
+                        Configuring a Compass Watcher</a>.</p>
+
+                    <h2>Step 4: Configuring Magento to Load Your Theme</h2>
+                    <p>This section discusses how to configure Magento to load your new theme.</p>
+                    <ol>
+                        <li>Log in to the Magento Admin Panel as an administrator.</li>
+                        <li>Click <strong>System</strong> > <strong>Configuration</strong> > GENERAL > <strong>Design</strong>.</li>
+                        <li>In the right pane, click <strong>Package</strong> to expand it.</li>
+                        <li>In the <strong>Current Package Name</strong> field, enter <tt>custompackage</tt></li>
+                        <li>In the right pane, expand <strong>Themes</strong>.</li>
+                        <li>In the <strong>Default</strong> field, enter <tt>customtheme</tt><br/>
+                            The following figure shows an example.<br/>
+                            <img src="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/admin-panel-custom-theme.png" width="600px" height="481px">
+                        </li>
+                        <li>In the top right corner of the page, click <strong>Save Config</strong>.<br/>
+                            If an error displays when you attempt to save the configuration, see <a href="#theme-admin-trouble">Troubleshooting
+                                Theme Configuration</a>.
+                        </li>
+                        <li>If prompted, flush the cache:
+                            <ol>
+                                <li>Click <strong>System</strong> > <strong>Configuration</strong> > <strong>Cache Management</strong>.
+                                </li>
+                                <li>At the top of the page, click <strong>Flush Magento Cache</strong>.</li>
+                            </ol>
+                        </li>
+                    </ol>
+
+                    <h2>Step 5: Verifying Your Custom Theme</h2>
+                    <p>To verify that Magento loads your theme:</p>
+                    <ol>
+                        <li>Navigate to your web store in a web browser.</li>
+                        <li>View the web page source.</li>
+                        <li>If you see a reference to <tt>/skin/frontend/custompackage/customtheme/css/styles.css</tt>, you are ready to
+                            begin building your new theme.
+                        </li>
+                    </ol>
+                    <div class="msg-box important"><img src="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/icon-note.png" alt="note" align="left"
+                                                        width="40"><span><strong>Note</strong>: If your theme fails to load properly, see the next section.
+    </span>
+                    </div>
+
+
+                    <h2 id="theme-admin-trouble">Troubleshooting Theme Configuration</h2>
+                    <p>See one of the following sections for troubleshooting assistance:</p>
+                    <ul>
+                        <li><a href="#theme-admin-trouble-table">General Troubleshooting</a></li>
+                        <li><a href="#theme-admin-trouble-files">Directory and File Reference</a></li>
+                    </ul>
+
+                    <h4 id="theme-admin-trouble-table">General Troubleshooting</h4>
+                    <p>The following sections assist you in determining the cause of errors you might experience after setting up your
+                        custom theme.</p>
+
+                    <h5>No formatting on the web store</h5>
+                    <p><em>Description</em>: Most likely an issue with <tt>theme.xml</tt>. You can confirm this by viewing the page
+                        source and searching for <tt>styles.css</tt>. If <tt>styles.css</tt> is loading from a path similar to the
+                        following, <tt>theme.xml</tt> is most likely not loading.</p>
+                    <pre>http://www.example.com/magento/skin/frontend/base/default/css/styles.css</pre>
+                    <p><em>Solution</em>: Enter the following command:</p>
+                    <pre>cat <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html#intro-convention">[your Magento install dir]</a>/app/design/frontend/custompackage/customtheme/etc/theme.xml</pre>
+                    <p>If the error <tt>No such file or directory</tt> displays, check your directory paths and create
+                        <tt>theme.xml</tt> as discussed in <a href="#theme-copyfiles">Step 2: Copying Files For Your Theme</a>.</p>
+                    <p>If you have a <tt>theme.xml</tt>, check to make sure it's configured <em>exactly</em> as shown <a
+                            href="#themexml">here</a>.</p>
+
+                    <h5>Error saving the custom package and theme in the Admin Panel</h5>
+                    <p><em>Symptom</em>: The following error displays:</p>
+                    <pre>An error occurred while saving this configuration: package with this name does not exist and cannot be set.</pre>
+                    <p><em>Description</em>: The package and theme names you entered in the Admin Panel must be directories in a
+                        specific location on the file system. These directories don't exist. (See the figure in <a
+                                href="#theme-admin-trouble-files">Directory and File Reference</a>.) Check the path and spelling.</p>
+                    <p><em>Solution</em>: Repeat the tasks discussed in <a href="#theme-structure">Step 1: Creating a Directory
+                        Structure for Your Responsive Theme</a>.</p>
+
+                    <h5>Wrong formatting in the web store</h5>
+                    <p><em>Symptom</em>: Examples:</p>
+                    <ul>
+                        <li>No images display</li>
+                        <li>Only a list of categories displays on the left side of the page, with images after the text</li>
+                    </ul>
+                    <p><em>Description</em>: There is a different <tt>theme.xml</tt> for CE and EE. You might have used an EE <tt>theme.xml</tt>
+                        with CE or vice versa.</p>
+                    <p>You can verify this using a web browser inspector:</p>
+                    <ul>
+                        <li><tt>styles.css</tt> loads from the correct directory</li>
+                        <li>Some HTTP 403 (Forbidden) errors loading images</li>
+                        <li>Some HTTP 404 (Not Found) errors loading images from <tt>skin/frontend/base/default/images/media</tt> (which
+                            doesn't exist)
+                        </li>
+                    </ul>
+                    <p><em>Solution</em>: Review the information discussed in <a href="#theme-copyfiles">Step 2: Copying Files For Your
+                        Theme</a>.</p>
+                    <p>Make sure <tt>theme.xml</tt> for CE or EE is configured <em>exactly</em> as shown <a href="#themexml">here</a>.
+                    </p>
+
+                    <h4 id="theme-admin-trouble-files">Directory and File Reference</h4>
+                    <p>The following figure shows the directory structure in a properly configured system, as well as the location of
+                        <tt>theme.xml</tt>, the custom theme configuration file.</p>
+                    <img src="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/custom-theme-dir-structure_image.png">
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-7.html b/guides/m1x/magefordev/mage-for-frontend-dev-7.html
new file mode 100644
index 0000000000..3f50c436c8
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-7.html
@@ -0,0 +1,646 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Responsive Theme Reference</h1>
+                    </section>
+
+                    <p>This section discusses information you need to customize the responsive theme you started in
+                        <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html#theme">Copying
+                        Files to Create Your Custom Theme</a>.</p>
+
+                    <h2>Basic Recommendations for Development</h2>
+                    <p>We recommend you do the following things when you start developing your responsive theme:</p>
+                    <ul>
+                        <li>Edit <tt>[your Magento install dir]/skin/frontend/custompackage/customtheme/scss/config.rb</tt> to change
+                            <tt>environment = &#58;production</tt> to <tt>environment = &#58;development</tt>.<br/>
+                            For more information about this setting, see <a
+                                    href="http://beta.compass-style.org/help/documentation/configuration-reference/" target="_blank">Compass
+                                Configuration Reference</a>.
+                        </li>
+                        <li>Disable the Magento cache as discussed in
+                            <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html#disable-cache">Disabling Magento's Cache</a>.</li>
+                    </ul>
+
+                    <h2>Understanding the Sass Structure</h2>
+                    <p>In previous versions of Magento, all CSS styles were grouped into a massive <tt>styles.css</tt> file that was
+                        cumbersome and difficult to navigate. The CSS in the responsive theme is organized into individual files
+                        referred to as <em>Sass partials</em>.</p>
+                    <p>When Compass compiles the Sass partials, the output is a set of CSS files that are loaded by the browser: <tt>styles-ie8.css</tt>
+                        is for Internet Explorer 8 and earlier, and <tt>styles.css</tt> is for all other browsers.</p>
+                    <p>Following is the directory structure of the <tt>skin/frontend/custompackage/customtheme</tt> directory.</p>
+                    <div class="msg-box important"><img src="{{ site.baseurl }}{{ site.v1xgdeurl }}images/icon-note.png" alt="note" align="left"
+                                                        width="40"><span><strong>Note</strong>: This structure does not include the sample data assets that you will <a
+                            href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html#remove-sample-content">remove later in this guide</a>.</span></div>
+                    <pre>
+&#x251C;&#x2500;&#x2500; css
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; scaffold-forms.css
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; styles-ie8.css
+&#x2502;&nbsp;&nbsp; &#x2514;&#x2500;&#x2500; styles.css
+&#x251C;&#x2500;&#x2500; images
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; ajax-loader.gif
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; bg_x.png
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; demo-logo.png
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; demo_logo.png
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; icon_sprite.png
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; icon_sprite@2x.png
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; logo.png
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; logo_small.png
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; opc-ajax-loader.gif
+&#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; social_icons.png
+&#x2502;&nbsp;&nbsp; &#x2514;&#x2500;&#x2500; social_icons@2x.png
+&#x2514;&#x2500;&#x2500; scss
+    &#x251C;&#x2500;&#x2500; _core.scss
+    &#x251C;&#x2500;&#x2500; _framework.scss
+    &#x251C;&#x2500;&#x2500; _var.scss
+    &#x251C;&#x2500;&#x2500; config.rb
+    &#x251C;&#x2500;&#x2500; content
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _category.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _home.scss
+    &#x251C;&#x2500;&#x2500; core
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _common.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _form.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _reset.scss
+    &#x2502;&nbsp;&nbsp; &#x2514;&#x2500;&#x2500; _table.scss
+    &#x251C;&#x2500;&#x2500; function
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _black.scss
+    &#x2502;&nbsp;&nbsp; &#x2514;&#x2500;&#x2500; _white.scss
+    &#x251C;&#x2500;&#x2500; layout
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _footer.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _global.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _header-account.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _header-cart.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _header-nav.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _header-search.scss
+    &#x2502;&nbsp;&nbsp; &#x2514;&#x2500;&#x2500; _header.scss
+    &#x251C;&#x2500;&#x2500; mixin
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _breakpoint.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _clearfix.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _if-resolution.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _image-replacement.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _loading-overlay.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _menu.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _not-selectable.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _toggle-content.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _triangle.scss
+    &#x2502;&nbsp;&nbsp; &#x2514;&#x2500;&#x2500; _typography.scss
+    &#x251C;&#x2500;&#x2500; module
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _account-reviews.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _catalog-compare.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _catalog-msrp.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _catalog-product.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _checkout-cart-minicart.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _checkout-cart.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _checkout-onepage.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _checkout-success.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _cms.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _configurableswatches.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _contacts.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _cookies.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _customer.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _paypal.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _pricing_conditions.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _product-list.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _review.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _search.scss
+    &#x2502;&nbsp;&nbsp; &#x251C;&#x2500;&#x2500; _slideshow.scss
+    &#x2502;&nbsp;&nbsp; &#x2514;&#x2500;&#x2500; _wishlist.scss
+    &#x251C;&#x2500;&#x2500; override
+    &#x2502;&nbsp;&nbsp; &#x2514;&#x2500;&#x2500; _plugin.scss
+    &#x251C;&#x2500;&#x2500; scaffold-forms.scss
+    &#x251C;&#x2500;&#x2500; styles-ie8.scss
+    &#x251C;&#x2500;&#x2500; styles.scss
+    &#x2514;&#x2500;&#x2500; vendor
+        &#x2514;&#x2500;&#x2500; _normalize.scss
+</pre>
+
+                    <p>This is an explanation of the files in the preceding list:</p>
+                    <ul>
+                        <li><tt>config.rb</tt>: Configuration values that tell Compass to look in the <tt>scss</tt> directory for Sass
+                            files and to export the CSS to the <tt>css</tt> directory. It also includes information about how Compass
+                            should format the compiled CSS.
+                        </li>
+                        <li><tt>scss/styles.scss</tt>: Wrapper that imports the <tt>framework.scss</tt> and <tt>core.scss</tt> files.
+                        </li>
+                        <li><tt>scss/styles-ie8.scss</tt>: Identical to <tt>styles.css</tt> file, except it does not include any media
+                            queries because Internet Explorer 8 and earlier don't support media queries. For more information, see <a
+                                    href="#breakpoint-ie8">Using the bp() mixin for older Internet Explorer Browser Versions</a>.
+                        </li>
+
+                        <li><tt>scss/_framework.scss</tt>: Imports all of the libraries, variables, functions, and mixins used by the
+                            other stylesheets. The files imported by <tt>framework.scss</tt> do not output any CSS on their own. Because
+                            of that, this file can be imported by other Sass files that are intended to compile directly to CSS
+                            files.<br/>
+                            For example, in Magento EE, the <tt>skin/frontend/rwd/enterprise/scss/enterprise.scss</tt> file imports <tt>skin/frontend/rwd/default/scss/_framework.scss</tt>
+                            so the Magento EE partials can use the common variables, mixins, and so on imported by
+                            <tt>framework.scss</tt>.
+                            <ul>
+                                <li><tt>scss/_var.scss</tt>: Contains variables like breakpoints, spacing, colors, and font styles that
+                                    are used by the other Sass partials. You should expect to modify this file heavily as you customize
+                                    your responsive theme.
+                                </li>
+                                <li><tt>scss/mixins/</tt>: This directory contains all of the mixins used by the responsive theme. You
+                                    should familiarize yourself with these mixins because they are useful for writing your custom
+                                    styles.
+                                </li>
+                                <li><tt>scss/function/</tt>: This directory contains functions that the responsive theme uses. Functions
+                                    are mixins that return simple values.
+                                </li>
+                            </ul>
+                        </li>
+                        <li><tt>scss/_core.scss</tt>: Imports all of the Sass partials that output CSS content:
+                            <ul>
+                                <li><tt>scss/core/</tt>: Partials that contain all of the global styles. Expect to heavily customize the
+                                    partials in this directory.
+                                </li>
+                                <li><tt>scss/layout/</tt>: Partials that define the structural layout of the responsive theme (header,
+                                    content, and footer). The <tt>scss/core/_common.scss</tt> partial also contains some layout styles&mdash;specifically
+                                    the one, two, or three column layouts.
+                                </li>
+                                <li><tt>scss/module/</tt>: Partials that contain styles grouped by module. While the correlation between
+                                    these module files and Magento core modules is close, it is not a 1:1 relationship. For example, the
+                                    <tt>_product-list.scss</tt> file contains styles for both the <tt>Mage_Catalog</tt> and <tt>Mage_CatalogSearch</tt>
+                                    modules.
+                                </li>
+                                <li><tt>scss/vendor/</tt>: This directory is intended for third-party CSS libraries like the <tt>_normalize.scss</tt>
+                                    partial that normalizes how browsers render elements.
+                                </li>
+                            </ul>
+                        </li>
+                        <li><tt>scss/scaffold-forms.scss</tt>: For more information, see
+                            <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html#scaffold-forms">Scaffold Forms</a>.
+                        </li>
+                    </ul>
+
+                    <h2>Adding Your Own Sass Partials</h2>
+                    <p>To customize styles for an existing Magento theme, you should edit existing Sass partials. However, if you are
+                        building a highly custom theme, you will likely want to create new partial files to contain styles for new
+                        functionality that you are introducing. Here is how to do that:</p>
+                    <ol>
+                        <li>Add your partials to a new file named <tt>skin/frontend/custompackage/customtheme/scss/module/<em>_new-module.scss</em></tt>.
+                        </li>
+                        <li>Create a new <tt>skin/frontend/custompackage/customtheme/scss/_custom_core.scss</tt> file with the following
+                            line to import your new partial:
+                            <pre>@import &quot;module/<em>new-module</em>&quot;;</pre>
+                            <strong>Note</strong>: Although you could edit <tt>core.scss</tt> to import your new partials, you should
+                            create <tt>_custom_core.scss</tt> to clearly distinguish which partial files are custom versus native.
+                        </li>
+                        <li>Add this line to the bottom of <tt>styles.scss</tt> and <tt>styles-ie8.scss</tt> files:
+                            <pre>@import &quot;custom_core&quot;;</pre>
+                        </li>
+                    </ol>
+                    <p>The contents of your new Sass partial will now be included in the output CSS files.</p>
+
+                    <h2>Using Media Query Breakpoints</h2>
+                    <p>The responsive theme has a set of <a href="https://github.com/at-import/breakpoint" target="_blank">breakpoints</a> it uses
+                        consistently (except for a few one-off breakpoints). These breakpoints are defined in both <tt>_var.scss</tt>
+                        and <tt>app.js</tt> so the CSS and JavaScript functionality stay in sync:</p>
+                    <pre>$bp-xsmall: 479px;
+$bp-small: 599px;
+$bp-medium: 770px;
+$bp-large: 979px;
+$bp-xlarge: 1199px;</pre>
+                    <p>A custom <tt>bp()</tt> mixin includes media query breakpoints. </p>
+                    <p>For example, this Sass:</p>
+                    <code><pre>
+@include bp(max-width, $bp-medium) {
+    /* These styles will only display on viewports smaller than or equal to 770px */
+}
+@include bp(min-width, $bp-medium+1) {
+    /* These styles will only display on viewports larger than or equal to 771px (770px + 1px) */
+}
+    </pre></code>
+                    <p>generates this CSS:</p>
+                    <code><pre>
+@media only screen and (max-width: 770px) {
+    /* These styles will only display on viewports smaller than or equal to 770px */
+}
+@media only screen and (min-width: 771px) {
+    /* These styles will only display on viewports larger than or equal to 771px (770px + 1px) */
+}
+    </pre></code>
+                    <p>The breakpoint variables are intended to be used with <tt>max-width</tt> by default. When you use the breakpoint
+                        with <tt>min-width</tt>, you should add a pixel <tt>($bp-medium+1)</tt> so the <tt>min-width</tt> and <tt>max-width</tt>
+                        styles don't both get applied to the same viewport size.</p>
+
+                    <h4 id="breakpoint-ie8">Using the bp() mixin for older Internet Explorer Browser Versions</h4>
+                    <p>It is important to use the <tt>bp()</tt> mixin for your media query breakpoints because Internet Explorer 8 and
+                        earlier do not support media queries. While you can use a polyfill like <a
+                                href="https://github.com/scottjehl/Respond" target="_blank">respond.js</a> to add media query support to IE
+                        versions 6&ndash;8, doing so will impact performance. Additionally, using a polyfill doesn't add much value because
+                        nearly all IE 6&ndash;8 users view web pages on a large screen device (1024px or larger), so those users won't
+                        benefit from media queries anyway.</p>
+                    <p>To address the fact that IE 6&ndash;8 doesn't support media queries, the <tt>styles-ie8.scss</tt> stylesheet
+                        defines a couple of variables:</p>
+                    <pre>$mq-support: false;
+$mq-fixed-value: 1024px;</pre>
+                    <p>With those variables defined, the <tt>bp()</tt> mixin outputs only the styles that would be visible on a 1024px+
+                        viewport <em>and</em> it does not wrap those styles in a media query so that the IE browsers always render those
+                        styles. Refer to <a href="#customizing-theme-sass-struct"><tt>_breakpoint.scss</tt></a> to see exactly how this
+                        is done.</p>
+                    <p>While it is acceptable to use the breakpoint variables defined by the responsive theme, when building your own
+                        responsive theme, your breakpoints should be specifically tailored to the content of your site. For example,
+                        let's say your main navigation only has four links and it fits nicely in a horizontal layout on viewports larger
+                        than 400px.</p>
+                    <p>The responsive theme changes the horizontal layout to a collapsed drop-down on viewports smaller than 771px.
+                        Rather than defaulting to how the theme collapses the navigation, you should change the navigation to break at
+                        about 400px so users on screens between 400px and 771px get to experience the benefit of viewing the horizontal
+                        navigation.</p>
+
+                    <h2>Working With Images</h2>
+                    <p>There are very few images in the responsive theme compared to the other Magento themes because CSS3 is used
+                        whenever possible to accomplish a visual effect.</p>
+
+                    <h4 id="customize-theme-images-logo">Working With the Header Logo</h4>
+                    <p>The responsive theme enables you to specify two different logos: one optimized for small screens (narrower than
+                        770px) and the other for large screens. Place your two logo files in <tt>skin/frontend/custompackage/customtheme/images</tt>
+                        and specify the path to both logos in the Magento Admin Panel:</p>
+
+                    <ol>
+                        <li>Log in to the Magento Admin Panel as an administrator.</li>
+                        <li>Click <strong>System</strong> > <strong>Configuration</strong> > GENERAL > <strong>Design</strong>.</li>
+                        <li>In the right pane, click <strong>Header</strong> to expand it.</li>
+                        <li>In the <strong>Logo Image Src</strong> field, enter the path of your primary logo. For example: <tt>images/logo.png</tt>.
+                        </li>
+                        <li>In the <strong>Small Logo Image Src</strong> field, enter the path of your logo for small viewports. For
+                            example: <tt>images/logo_small.png</tt>.
+                        </li>
+                        <li>In the top right corner of the page, click <strong>Save Config</strong>.</li>
+                        <li>If prompted, flush the cache:
+                            <ol>
+                                <li>Click <strong>System</strong> > <strong>Configuration</strong> > <strong>Cache Management</strong>.
+                                </li>
+                                <li>At the top of the page, click <strong>Flush Magento Cache</strong>.</li>
+                            </ol>
+                        </li>
+                    </ol>
+
+                    <h4 id="customize-theme-images-sprites">Working With Sprites</h4>
+                    <p>The responsive theme uses two sprites: one for general icons and the other for social icons.</p>
+                    <p>Both sprite images output at 1x and 2x resolutions (for high-resolution screens). Because sprite files are very
+                        difficult to edit without the source files, you should use these Photoshop files to change these sprites: <a
+                                href="{{ site.baseurl }}{{ site.v1xgdeurl }}images/RWD_icon_sprite.psd">RWD_icon_sprite.psd</a> and <a
+                                href="{{ site.baseurl }}{{ site.v1xgdeurl }}images/RWD_social_icons.psd">RWD_social_icons.psd</a>
+                    <p>Compass provides support for generating sprites from individual image files, but it was not used to generate
+                        sprites for the responsive theme. However, you might want to take advantage of that feature for your custom
+                        theme. Using this method requires knowledge of Compass.</p>
+
+                    <h2 id="customize-theme-js">Working With JavaScript</h2>
+                    <p>All of the custom JavaScript in the responsive theme is contained in <tt>skin/frontend/rwd/default/js/app.js</tt>.
+                        To customize the responsive theme's JavaScript, copy <tt>app.js</tt> to <tt>skin/frontend/custompackage/customtheme/js</tt>
+                        and edit it there.</p>
+                    <p>All custom JavaScript is based on jQuery (v1.10.2). In addition to jQuery, the following JavaScript libraries are
+                        included in the responsive theme:</p>
+                    <ul>
+                        <li><a href="https://wicky.nillia.ms/enquire.js/" title="Enquire.js Documentation" target="_blank">enquire.js</a>:
+                            Used to run JavaScript conditionally, based on viewport size.
+                        </li>
+                        <li><a href="https://github.com/desandro/imagesloaded" title="imagesloaded.js Github" target="_blank">imagesloaded.js</a>:
+                            Used to determine whether images are fully loaded on the product detail page before activating zoom.
+                        </li>
+                        <li><a href="https://jquery.malsup.com/cycle2/" title="Cycle2 Documentation"
+                               target="_blank">jquery.cycle2.min.js</a>: Powers the rotating banners on the homepage (requires Magento's
+                            sample data). This library can be removed if you aren't using the sample data. If you want to implement
+                            slide shows, <a href="https://owlgraphic.com/" target="_blank">Owl Carousel</a> is recommended
+                            over Cycle2, as it has true swipe support and has more options.
+                        </li>
+                        <li><tt>jquery.cycle2.swipe.min.js</tt>: Adds pseudo-swipe support to Cycle2.</li>
+                        <li><a href="https://jquery.com/" target="_blank">jquery-1.10.2.min.js</a>: jQuery library</li>
+                        <li><a href="https://github.com/paulirish/matchMedia.js" title="matchMedia.js Github" target="_blank">matchMedia.js
+                            and matchMedia.addListener.js</a>: Used by <tt>enquire.js</tt> to provide support for Internet Explorer 9.
+                        </li>
+                        <li><a href="https://modernizr.com/" target="_blank">modernizr.custom.min.js</a>: Adds classes to the <tt>&lt;html&gt;</tt>
+                            tag to indicate whether browser supports certain CSS3 features and whether device is touch-enabled. The <tt>.touch</tt>
+                            and <tt>.no-touch</tt> classes are used in the Sass partials. They provide a <tt>Modernizr.mq</tt> function
+                            to test a media query in a cross-browser manner.
+                        </li>
+                        <li><a href="http://selectivizr.com/" target="_blank">selectivizr.js</a>: Adds support for CSS3 selectors in IE
+                            6&#8211;8
+                        </li>
+                        <li><a href="https://github.com/elevateweb/elevatezoom"
+                               target="_blank">elevatezoom/jquery.elevateZoom-3.0.8.min.js</a>: Powers image zoom on product detail
+                            pages.
+                        </li>
+                    </ul>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-8.html b/guides/m1x/magefordev/mage-for-frontend-dev-8.html
new file mode 100644
index 0000000000..952f437871
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-8.html
@@ -0,0 +1,378 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 id="remove-sample-content" class="page-heading">Removing Sample Data Assets</h1>
+                    </section>
+
+                    <p>The responsive theme includes several assets that are intended to power Magento's sample data. We recommend you
+                        remove them before you build your custom theme.</p>
+                    <ol>
+                        <li>Remove the following files and directories:
+                            <pre>skin/frontend/custompackage/customtheme/images/media
+skin/frontend/custompackage/customtheme/scss/madisonisland.scss
+skin/frontend/custompackage/customtheme/scss/madisonisland-ie8.scss
+skin/frontend/custompackage/customtheme/scss/content/_category.scss
+skin/frontend/custompackage/customtheme/scss/content/_home.scss
+skin/frontend/custompackage/customtheme/css/madisonisland.css
+skin/frontend/custompackage/customtheme/css/madisonisland-ie8.css</pre>
+                        </li>
+                        <li>In your custom layout file (for example,
+                            <tt>app/design/frontend/custompackage/customtheme/layout/local.xml</tt>), add this XML:<br/>
+                            <code><pre>
+&lt;layout version="0.1.0"&gt;
+    &lt;default&gt;
+        &lt;reference name="head"&gt;
+            &lt;action method="removeItem"&gt;&lt;type&gt;skin_js&lt;/type&gt;&lt;name&gt;js/slideshow.js&lt;/name&gt;&lt;/action&gt;
+            &lt;action method="removeItem"&gt;&lt;type&gt;skin_js&lt;/type&gt;&lt;name&gt;js/lib/jquery.cycle2.min.js&lt;/name&gt;&lt;/action&gt;
+            &lt;action method="removeItem"&gt;&lt;type&gt;skin_js&lt;/type&gt;&lt;name&gt;js/lib/jquery.cycle2.swipe.min.js&lt;/name&gt;&lt;/action&gt;
+            &lt;action method="removeItem"&gt;&lt;type&gt;skin_css&lt;/type&gt;&lt;name&gt;css/madisonisland.css&lt;/name&gt;&lt;/action&gt;
+            &lt;action method="removeItem"&gt;&lt;type&gt;skin_css&lt;/type&gt;&lt;name&gt;css/madisonisland-ie8.css&lt;/name&gt;&lt;/action&gt;
+            &lt;action method="removeItem"&gt;&lt;type&gt;link_rel&lt;/type&gt;&lt;name&gt;//fonts.googleapis.com/css?family=Raleway:300,400,500,700,600&lt;/name&gt;&lt;/action&gt;
+        &lt;/reference&gt;
+    &lt;/default&gt;
+&lt;/layout&gt;
+            </pre></code>
+                            The preceding XML:
+                            <ul>
+                                <li>Removes the Madison Island CSS files</li>
+                                <li>Removes the Raleway font that is used as a part of the default theme</li>
+                                <li>Removes the jQuery Cycle plugin and the <tt>slideshow.js</tt> file that activates Cycle.</li>
+                            </ul>
+                        </li>
+                        <li>Update this line in <tt>skin/frontend/custompackage/customtheme/scss/_var.scss</tt> to reference whatever
+                            font you want to use for your custom site font:
+                            <pre>$f-stack-special: 'Raleway', 'Helvetica Neue', Verdana, Arial, sans-serif;</pre>
+                            <p>If you want to use a custom web font for your theme (such as a <a href="https://www.google.com/fonts"
+                                                                                                 target="_blank">Google Font</a>, add
+                                XML like this to the <tt>&lt;reference name=&quot;head&quot;&gt;</tt> section of <tt>layout.xml</tt>
+                                (see step 3). Customize the <tt>&lt;href></tt> value to the value that your custom web font provider
+                                gives you. It is recommended to include the same font weights that are referenced below
+                                (300,400,500,700,600) because the responsive theme uses each of those font weights.</p>
+                            <code><pre>
+&lt;action method="addLinkRel"&gt;&lt;rel&gt;stylesheet&lt;/rel&gt;&lt;href&gt;//fonts.googleapis.com/css?family=Raleway:300,400,500,700,600&lt;/href&gt;&lt;/action&gt;
+                </pre></code>
+                        </li>
+                    </ol>
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-9.html b/guides/m1x/magefordev/mage-for-frontend-dev-9.html
new file mode 100644
index 0000000000..73004e6926
--- /dev/null
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-9.html
@@ -0,0 +1,440 @@
+---
+---
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1"/>
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
+    <title>Frontend Developer Guide</title>
+    <meta name="description" content="OpenMage LTS Developer Documentation.">
+
+    <link rel="stylesheet" href="/assets/css/app.css"/>
+    <link rel="stylesheet" href="/assets/css/print.css" media="print"/>
+    <link rel="stylesheet" type="text/css" href="/common/css/stylesheet.css">
+
+    <link rel="stylesheet" href="/common/css/stylesheet-fonts.css" type="text/css">
+    <link rel="stylesheet" href="/common/css/devdocs.css"/>
+    <link rel="alternate" type="application/rss+xml" title="OpenMage DevDocs RSS" href="/feed.xml"/>
+
+    <script>
+        var baseUrl = "";
+        var algolia = {
+            id: "E642SEDTHL",
+            index: "devdocs",
+            key: "d2d0f33ab73e291ef8d88d8b565e754c"
+        };
+    </script>
+
+    <link rel="shortcut icon" type="image/x-icon" href="/common/css/favicon.ico">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
+    <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
+</head>
+<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
+<!-- magento-for-dev-part-1-introduction-to-magento -->
+<body class="layout-default">
+<header class="site-header">
+    <nav class="site-nav">
+        <div class="menu-btn">
+            <button id="menu-btn" class="menu-trigger menu-icon" aria-haspopup="true" aria-controls="nav-main"></button>
+        </div>
+        <div class="nav-container">
+            <a class="logo" href="/">
+                <svg width="257" height="63" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
+                    <defs>
+                        <style>.ba {
+                            fill: #fb0e70;
+                        }
+
+                        .bb {
+                            fill: #fff;
+                            font-size: 45px;
+                        }
+
+                        .bb, .bc {
+                            font-family: Poppins-SemiBold, Poppins;
+                            font-weight: 600;
+                            letter-spacing: -0.05em;
+                            fill: #F1F1F1
+                        }
+
+                        .bc {
+                            fill: #707070;
+                            font-size: 38px;
+                        }</style>
+                    </defs>
+                    <g class="layer">
+                        <title>OpenMage Magento</title>
+                        <path class="ba"
+                              d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
+                        <text class="bb" id="svg_2" x="0" y="47">
+                            <tspan x="0" y="47">m</tspan>
+                        </text>
+                        <text class="bc" transform="translate(56 40)">
+                            <tspan x="0" y="0">openmage</tspan>
+                        </text>
+                    </g>
+                </svg>
+                <span class="site-logo">DevDocs</span>
+            </a>
+            <div id="nav-main" class="nav-main-wrap" aria-labelledby="menu-btn">
+                <!-- Main Navigation -->
+                <ul class="nav-main" role="menubar">
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Setup</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class="active " role="menuitem">
+                                    <a href="/guides/v19.x/install-gde/install-flow-diagram.html">Installation Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/migration/bk-migration-guide.html">Migration Guide</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Information</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Development</span>
+                        <div class="nav-popup">
+                            <div class="nav-section">
+                                <div class="nav-section-title">Backend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Architecture</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">PHP Developer Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Extension Developer Best Practices</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Module Reference Guide</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Coding Standards</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="https://github.com/OpenMage/magento-lts">Contribute!</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">Frontend</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Frontend Developer Guide</a>
+                                    </li>
+                                </ul>
+                            </div>
+                            <div class="nav-section">
+                                <div class="nav-section-title">API</div>
+                                <ul>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
+                                    </li>
+                                    <li class=" " role="menuitem">
+                                        <a href="/guides/v19.x/api/soap-api-index.html">SOAP API Reference</a>
+                                    </li>
+                                </ul>
+                            </div>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Testing</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/mftf/2.3/introduction.html">Functional Acceptance Testing (MFTF)</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Functional Areas</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <span>Advanced Reporting</span>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/howdoi/checkout/checkout_overview.html">Checkout</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/inventory/index.html">Inventory Management</a>
+                                </li>
+                                <li class=" " role="menuitem">
+                                    <a href="http://omsdocs.magento.com/en/">Order Management</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                    <li class="nav-main-item" tabindex="0" role="menuitem" aria-haspopup="true">
+                        <span tabindex="-1">Old Documantation</span>
+                        <div class="nav-popup">
+                            <ul>
+                                <li class=" " role="menuitem">
+                                    <a href="/guides/v19.x/">Magento 1 Docs</a>
+                                </li>
+                            </ul>
+                        </div>
+                    </li>
+                </ul><!-- /.nav-main -->
+            </div>
+            <div class="search-btn">
+                <button class="search-trigger search-icon" aria-label="Search"></button>
+            </div>
+            <form class="quick-search" action="/search.html" method="get" novalidate="novalidate">
+                <input type="search" name="q" placeholder="Search"/>
+                <button class="quick-search-close" aria-label="Close Search">&times;</button>
+            </form>
+        </div>
+    </nav><!-- #site-nav -->
+    <div class="nav-main-fader"></div>
+</header>
+<div class="global-wrapper">
+    <div class="main-container">
+        <a id="main-content"></a>
+        <div class="content-container">
+            <!-- sidebar -->
+            <aside class="sidebar">
+                <a href="#" data-proofer-ignore class="toc-toggler">Table of Contents</a>
+                <div class="sidebar-wrapper">
+                    <h4 class="guide-title">Frontend Developer Guide</h4>
+                    <div class="collapsible-navigation">
+                        <ul>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">
+                                    Introduction
+                                </a>
+                            </li>
+                            <li class=" " role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-2.html">
+                                    Supported Devices and Browsers
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-3.html">
+                                    Understanding the Changes in the Responsive Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-4.html">
+                                    Installing Compass and Sass
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-5.html">
+                                    Disabling the Magento Cache
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html">
+                                    Copying Files to Create Your Custom Theme
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-7.html">
+                                    Responsive Theme Reference
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-8.html">
+                                    Removing Sample Data Assets
+                                </a>
+                            </li>
+                            <li class="active" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-9.html">
+                                    Advanced Topics
+                                </a>
+                            </li>
+                            <li class="" role="menuitem">
+                                <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-10.html">
+                                    Getting Help With Your Theme
+                                </a>
+                            </li>
+                        </ul>
+                    </div>
+                </div>
+            </aside>
+            <!-- /sidebar -->
+            <section class="content">
+                <div class="content-wrap">
+                    <!-- page-header -->
+                    <section class="page-intro">
+                        <h1 class="page-heading">Advanced Topics</h1>
+                    </section>
+
+                    <p>After you get familiar with the new structure, we encourage you to read these topics to fully take advantage of
+                        responsive web design.</p>
+
+                    <h4>Getting Your Theme Ready for Production</h4>
+
+                    <p>To prepare your responsive theme for production, you should update <tt>config.rb</tt> in your theme directory to
+                        use these values:</p>
+                    <pre>output_style = &#58;compressed
+environment = &#58;production</pre>
+
+                    <p>After you do this, you should recompile all of your Sass files&mdash;you can do this on the command line by
+                        running these commands inside your theme directory: <tt>compass clean</tt> and then <tt>compass compile</tt>.
+                        Finally, deploy the compiled CSS to your production system.</p>
+
+                    <h2 id="sass-fallback-structure">Sass Fallback Structure</h2>
+                    <p>We recommend copying all of the Sass files from <tt>skin/frontend/rwd/default/scss</tt> to <tt>skin/frontend/custompackage/customtheme/scss</tt>
+                        to make it easy to get started with custom theme development. The downside of this approach is that it results
+                        in duplicating many files that you never edit directly.</p>
+                    <p>In the end, your custom theme must include all Sass partials you want to override. There are at least two ways to
+                        do this:</p>
+                    <ul>
+                        <li>If you followed the setup instructions in <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-6.html#theme-structure">Step 1: Creating a Directory Structure
+                            for Your Responsive Theme</a>, you must delete some files from your custom theme.<br/>
+                            Delete the following directories to remove all the Sass partials that you copied from
+                            <tt>rwd/default</tt>:<br/>
+                            <pre>skin/frontend/custompackage/customtheme/scss/core/
+skin/frontend/custompackage/customtheme/scss/function/
+skin/frontend/custompackage/customtheme/scss/layout/
+skin/frontend/custompackage/customtheme/scss/mixin/
+skin/frontend/custompackage/customtheme/scss/module/
+skin/frontend/custompackage/customtheme/scss/override/
+skin/frontend/custompackage/customtheme/scss/vendor/</pre>
+                            The following files should now be located in <tt>skin/frontend/custompackage/customtheme/scss</tt>:<br/>
+                            <pre>_var.scss
+_core.scss
+styles-ie8.scss
+styles.scss
+scaffold-forms.scss
+_custom_core.scss
+_framework.scss</pre>
+                        </li>
+                        <li>If you're familiar with Magento theme development and you did <em>not</em> already copy Sass partials, copy
+                            <em>only</em> the Sass partials you want to override from <tt>rwd/default</tt> to <tt>skin/frontend/custompackage/customtheme/scss</tt>.
+                        </li>
+                    </ul>
+                    <p>Now you can set up a fallback structure:</p>
+                    <ol>
+                        <li>Add the following line to <tt>skin/frontend/rwd/default/config.rb</tt> (omit the first line if you're using
+                            CE):
+                            <pre>add_import_path &quot;../../../rwd/enterprise/scss&quot;
+add_import_path &quot;../../../rwd/default/scss&quot;</pre>
+                            The preceding causes Compass to look for Sass files in <tt>skin/frontend/rwd/enterprise/scss</tt> first and
+                            then in <tt>skin/frontend/rwd/default/scss</tt> if they can't be found in <tt>skin/frontend/custompackage/customtheme/scss</tt>.
+                        </li>
+                        <li>Following is what to do with copies of Sass files from <tt>rwd/default</tt>:<br/>
+                            <ul>
+                                <li><tt>styles.scss</tt>, <tt>styles-ie8.scss</tt>: You must copy these files into your custom theme so
+                                    that Compass knows which files to compile into CSS files.
+                                </li>
+                                <li><tt>_core.scss</tt>, <tt>framework.scss</tt>: You must copy these files into your custom theme so
+                                    Compass looks in the <tt>custompackage/customtheme</tt> directory for any of the files imported by
+                                    these two files.
+                                </li>
+                                <li><tt>_var.scss</tt>: You'll typically edit the values in this file for your custom theme.<br/>
+                                    If you don't like the idea of editing this file and want to override its values with a <tt>_var_custom.scss</tt>
+                                    file, make sure it gets imported immediately after <tt>_var.scss</tt>.
+                                </li>
+                            </ul>
+                        </li>
+
+                        <li>As a reminder, to override Sass partials in <tt>rwd/default</tt>, you must copy them into your custom theme
+                            so they'll get included by Compass.<br/>
+                            <strong>Note</strong>: If you're using <tt>compass watch</tt> to recompile your Sass, you must stop and
+                            restart Compass any time you copy a new Sass file into your custom theme. Otherwise, the Compass compiler
+                            won't know about the existence of the new file.<br/>
+                            To avoid having to stop and restart <tt>compass watch</tt>, start your project by copying all Sass files
+                            from <tt>rwd/default</tt> into your custom theme, and then delete all unchanged Sass files at the end of
+                            your project.
+                        </li>
+                    </ol>
+
+                    <h2 id="scaffold-forms">Scaffold Forms</h2>
+                    <p>The Magento responsive theme ships with <tt>skin/frontend/rwd/default/scss/scaffold-forms.scss</tt> that has
+                        styles that cause the labels of long forms (for example, the Billing Information step of checkout) to display to
+                        the left of their associated input on larger viewports (as opposed to on top). This layout is intended to make
+                        long forms seem less intimidating to users.</p>
+                    <p>However, these styles are not currently implemented because the Magento responsive theme must work well with
+                        internationalization (where the length of labels can vary greatly, thereby impacting the scaffold form
+                        layout).</p>
+                    <p>It's up to you whether or not to use these styles. To do so, move <tt>skin/frontend/rwd/default/scss/scaffold-forms.scss</tt>
+                        to <tt>core/_scaffold-forms.scss</tt> and edit <tt>scss/_core.scss</tt> to include it.</p>
+
+                    <h2>High-Definition Images</h2>
+                    <p>The responsive theme has no high-resolution image solution for product listing pages. Refer to <a
+                            href="https://speakerdeck.com/brendanfalkowski/responsive-ecommerce-part-two#114" target="_blank">slides
+                        starting at 114</a> of Brendan Falkowski's Imagine 2013 talk for implementation suggestions. For a 2x solution,
+                        PictureFill (or similar polyfill) could be used, although it would need to be integrated with ElevateZoom.</p>
+                    <div class="msg-box important"><img src="{{ site.baseurl }}{{ site.v1xgdeurl }}images/icon-note.png" alt="note" align="left"
+                                                        width="40"><span><strong>Note</strong>: Category banners and product detail pages use a 1.5x image solution.
+    </span>
+                    </div>
+
+                    <p>Magento does not resize the main product photo on product detail pages, so you must implement high-resolution
+                        support in your responsive theme. You must be careful with this if you have very large product photos because it
+                        could drastically impact performance.</p>
+                    <p>To constrain the size of your main product photo, open <tt>app/design/frontend/rwd/default/template/catalog/product/view/media.phtml</tt>
+                        and modify this line:
+                    <pre>&lt;?php echo $this-&gt;helper('catalog/image')-&gt;init($_product, 'image') ?&gt;</pre>
+                    to something like:
+                    <pre>src=&quot;&lt;?php echo $this-&gt;helper('catalog/image')-&gt;init($_product, 'image')-&gt;constrainOnly(true)-&gt;resize(1800); ?&gt;&quot;</pre>
+
+                </div>
+                <!-- /.content-wrap -->
+                <div class="page-info">
+                    <div class="github-link">
+                        <a class="improve-page"
+                           href="https://github.com/OpenMage/devdocs/blob/master/guides/v19.x/install-gde/install-flow-diagram.md"
+                           target="_blank">
+                            Edit this page on GitHub
+                        </a>
+                    </div>
+                    <div class="new-issue">
+                        <a href="https://github.com/OpenMage/devdocs/issues/new?title=Feedback on page: /guides/v19.x/install-gde/install-flow-diagram.html"
+                           target="_blank">
+                            Give us feedback
+                        </a>
+                    </div>
+                </div>
+            </section>
+            <!-- /.content -->
+        </div> <!-- /.content-container -->
+    </div>
+    <!-- /.main-container -->
+</div>
+<!-- /#gl-wrapper -->
+
+<!-- footer-->
+<div class="page-footer">
+    <div class="container">
+        <div class="copyright-links">
+            <ul class="nav footer-links">
+                <li class=" " role="menuitem">
+                    <a href="https://github.com/OpenMage/devdocs/blob/master/.github/CONTRIBUTING.md">Become a
+                        Contributor</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="https://glossary.magento.com/">Glossary</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/guides/v19.x/release-notes/bk-release-notes.html">Release Notes</a>
+                </li>
+                <li class=" " role="menuitem">
+                    <a href="/magento-third-party.html">Third-Party Licenses</a>
+                </li>
+            </ul>
+        </div>
+        <div class="copyright-date">&copy; 2024 OpenMage. All rights reserved.</div>
+    </div>
+</div>
+<!-- / #footer -->
+
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
+<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
+<script src="/assets/js/app.min.js"></script>
+</body>
+</html>
diff --git a/index.html b/index.html
index 8314908d56..9dc7f54228 100644
--- a/index.html
+++ b/index.html
@@ -1,6 +1,6 @@
 ---
 layout: home
-guide_version: 'm1x'
+guide_version: '19.x'
 ---
 
 <section class="home-features">
@@ -10,10 +10,9 @@
       <img src="{{ site.baseurl }}/i/icons/install.svg" alt="" />
       <h2 class="title">Setup</h2>
       <ul>
-        <li><a href="{{ site.baseurl }}/magento-system-requirements.html">System Requirements</a></li>
-        <li><a href="{{ page.baseurl }}/install-gde/bk-install-guide.html">Installation Guide</a></li>
-        <li><a href="{{ page.baseurl }}/config-guide/bk-config-guide.html">Configuration Guide</a></li>
-        <li><a href="{{ page.baseurl }}/cloud/bk-cloud.html">{{site.data.var.ece}}</a></li>
+        <li><a href="{{ site.baseurl }}/system-requirements.html">System Requirements</a></li>
+        <li><a href="{{ site.v1xgdeurl }}/install-gde/install-flow-diagram.html">Installation Guide</a></li>
+        <li><a href="{{ page.baseurl }}/">Configuration Guide</a></li>
       </ul>
     </div>
 
@@ -21,20 +20,20 @@ <h2 class="title">Setup</h2>
       <img src="{{ site.baseurl }}/i/icons/backend.svg" alt="" />
       <h2 class="title">Backend Development</h2>
       <ul>
-        <li><a href="{{ page.baseurl }}/extension-dev-guide/bk-extension-dev-guide.html">PHP Developer Guide</a></li>
-        <li><a href="{{ page.baseurl }}/b2b/bk-b2b.html">B2B Developer Guide</a></li>
-        <li><a href="{{ page.baseurl }}/coding-standards/bk-coding-standards.html">Coding Standards</a></li>
-        <li><a href="{{ page.baseurl }}/coding-standards/technical-guidelines.html">Technical Guidelines</a></li>
+        <li><a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">PHP Developer Guide</a></li>
+        <li><a href="{{ page.baseurl }}/">B2B Developer Guide</a></li>
+        <li><a href="{{ page.baseurl }}/">Coding Standards</a></li>
+        <li><a href="{{ page.baseurl }}">Technical Guidelines</a></li>
       </ul>
     </div>
     <div class="feature">
       <img src="{{ site.baseurl }}/i/icons/frontend.svg" alt="" />
       <h2 class="title">Frontend Development</h2>
       <ul>
-        <li><a href="{{ page.baseurl }}/frontend-dev-guide/bk-frontend-dev-guide.html">Frontend Developer Guide</a></li>
-        <li><a href="{{ page.baseurl }}/ui_comp_guide/bk-ui_comps.html">UI Components Guide</a></li>
-        <li><a href="{{ page.baseurl }}/javascript-dev-guide/bk-javascript-dev-guide.html">JavaScript Developer Guide</a></li>
-        <li><a href="{{ page.baseurl }}/pattern-library/bk-pattern.html">Admin Pattern Library</a></li>
+        <li><a href="{{ site.v1xgdeurl }}/magefordev/mage-for-frontend-dev-1.html">Frontend Developer Guide</a></li>
+        <li><a href="{{ page.baseurl }}/">UI Components Guide</a></li>
+        <li><a href="{{ page.baseurl }}/">JavaScript Developer Guide</a></li>
+        <li><a href="{{ page.baseurl }}/">Admin Pattern Library</a></li>
       </ul>
     </div>
 
@@ -44,7 +43,6 @@ <h2 class="title">Release Information</h2>
       <ul>
         <li><a href="{{ page.baseurl }}/release-notes/bk-release-notes.html">Release Notes</a></li>
         <li><a href="{{ site.baseurl }}/whats-new.html">What's New on DevDocs</a></li>
-        <li><a href="{{ page.baseurl }}/release-notes/backward-incompatible-changes/index.html">Backward Incompatible Changes</a></li>
         <li><a href="{{ site.baseurl }}/magento-techbull.html">Technical Bulletins</a></li>
       </ul>
     </div>
@@ -53,10 +51,9 @@ <h2 class="title">Release Information</h2>
       <img src="{{ site.baseurl }}/i/icons/api.svg" alt="" />
       <h2 class="title">Magento APIs</h2>
       <ul>
-        <li><a href="{{ page.baseurl }}/get-started/bk-get-started-api.html">Get Started with Magento APIs</a></li>
-        <li><a href="{{ page.baseurl }}/rest/bk-rest.html">REST API Reference (Static)</a></li>
-        <li><a href="{{ page.baseurl }}/rest/generate-local.html">REST API Reference (Local)</a></li>
-        <li><a href="{{ page.baseurl }}/graphql/index.html">GraphQL Developer Guide (New!)</a></li>
+        <li><a href="{{ page.baseurl }}/">Get Started with Magento APIs</a></li>
+        <li><a href="{{ page.baseurl }}/api/rest-api-index.html">REST API Reference (Static)</a></li>
+        <li><a href="{{ page.baseurl }}/api/soap-api-index.html">SOAP API Reference (Local)</a></li>
       </ul>
     </div>
 
@@ -65,8 +62,8 @@ <h2 class="title">Magento APIs</h2>
       <h2 class="title">Community</h2>
       <ul>
         <li><a href="{{ site.baseurl }}/community/resources/resources.html">Community Resources</a></li>
-        <li><a href="{{ page.baseurl }}/contributor-guide/contributing.html">Contributor Guide</a></li>
-        <li><a href="{{ page.baseurl }}/contributor-guide/contributing_dod.html">Magento Definition of Done</a></li>
+        <li><a href="{{ site.baseurl }}/">Contributor Guide</a></li>
+        <li><a href="{{ site.baseurl }}/">Magento Definition of Done</a></li>
       </ul>
     </div>
 

From f2a9d7fd46e8f3127294f6cf2bc3e524016ef533 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nils=20Bre=C3=9Fler?= <n.bressler@b3-it.de>
Date: Tue, 30 Jan 2024 14:47:16 +0100
Subject: [PATCH 3/3] B3-IT: Format pre tags, update links

---
 guides/m1x/magefordev/mage-for-dev-1.html     | 414 ++++++++--------
 guides/m1x/magefordev/mage-for-dev-2.html     | 216 ++++-----
 guides/m1x/magefordev/mage-for-dev-3.html     | 225 +++++----
 guides/m1x/magefordev/mage-for-dev-4.html     | 414 ++++++++--------
 guides/m1x/magefordev/mage-for-dev-5.html     | 427 ++++++++--------
 guides/m1x/magefordev/mage-for-dev-6.html     | 454 +++++++++---------
 guides/m1x/magefordev/mage-for-dev-7.html     | 386 ++++++++++-----
 guides/m1x/magefordev/mage-for-dev-8.html     | 193 ++++++--
 .../magefordev/mage-for-frontend-dev-7.html   |   4 +-
 .../magefordev/mage-for-frontend-dev-8.html   |   4 +-
 10 files changed, 1488 insertions(+), 1249 deletions(-)

diff --git a/guides/m1x/magefordev/mage-for-dev-1.html b/guides/m1x/magefordev/mage-for-dev-1.html
index cf67075558..e925834bcd 100644
--- a/guides/m1x/magefordev/mage-for-dev-1.html
+++ b/guides/m1x/magefordev/mage-for-dev-1.html
@@ -31,8 +31,6 @@
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
-<!-- magento-for-dev-part-1-introduction-to-magento -->
 <body class="layout-default">
 <header class="site-header">
     <nav class="site-nav">
@@ -65,7 +63,7 @@
                         }</style>
                     </defs>
                     <g class="layer">
-                        <title>OpenMage Magento</title>
+                        <title>OpenMage</title>
                         <path class="ba"
                               d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
                         <text class="bb" id="svg_2" x="0" y="47">
@@ -135,7 +133,7 @@
                                 <div class="nav-section-title">API</div>
                                 <ul>
                                     <li class=" " role="menuitem">
-                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                        <a href="/guides/v19.x/">Get Started with OpenMage Web APIs</a>
                                     </li>
                                     <li class=" " role="menuitem">
                                         <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
@@ -222,22 +220,22 @@ <h4 class="guide-title">Developer Guide</h4>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
-                                    OpenMage Controller Dispatch
+                                    Controller Dispatch
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
-                                    OpenMage Layouts, Blocks and Templates
+                                    Layouts, Blocks and Templates
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
-                                    OpenMage Models and ORM Basics
+                                    Models and ORM Basics
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
-                                    OpenMage Setup Resources
+                                    Setup Resources
                                 </a>
                             </li>
                             <li class="" role="menuitem">
@@ -264,50 +262,50 @@ <h1 class="page-heading">Introduction to OpenMage</h1>
                     <p class="para1">What is OpenMage? It's the most powerful online eCommerce platform in the universe
                         and is changing the face of eCommerce forever. :-)
                     </p>
-                    <p>Of course, you already know that. What you may not realize is Magento's also an object-oriented
+                    <p>Of course, you already know that. What you may not realize is OpenMage's also an object-oriented
                         PHP Framework that can be used to develop modern, dynamic web applications that tap into
-                        Magento's powerful eCommerce features.
+                        OpenMage's powerful eCommerce features.
                     </p>
                     <p>This is the first in a series of articles in which we're going to go on a whirlwind tour of
-                        Magento's programming framework features. Don't worry if you don't follow everything
+                        OpenMage's programming framework features. Don't worry if you don't follow everything
                         immediately. As you study the system more everything in this article will start to make sense,
                         and you'll soon be the envy of your colleagues stuck working with more primitive PHP
                         systems.
                     </p>
                     <p>Or for the more visually oriented
-                        <a href="{{ site.baseurl }}{{ site.v1xgdeurl }}images/Magento_MVC.pdf">Magento_MVC.pdf</a>.
+                        <a href="{{ site.baseurl }}{{ site.v1xgdeurl }}/images/Magento_MVC.pdf">OpenMage_MVC.pdf</a>.
                     </p>
                     <hr/>
                     <a name="1"></a>
                     <h2>Code Organized in Modules</h2>
-                    <p>Magento organizes its code into individual Modules. In a typical PHP
+                    <p>OpenMage organizes its code into individual Modules. In a typical PHP
                         <a href="http://en.wikipedia.org/wiki/Model–view–controller" target="_new">
                             <b>Model-View-Controller (MVC)</b>
                         </a>
                         application, all the Controllers will be in one folder, all the Models in another,
-                        etc. In Magento, files are grouped together based on functionality, which are called
-                        <b>modules</b> in Magento.
+                        etc. In OpenMage, files are grouped together based on functionality, which are called
+                        <b>modules</b> in OpenMage.
                     </p>
-                    <h4>Magento's Code</h4>
-                    <p>For example, you'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's checkout
+                    <h4>OpenMage's Code</h4>
+                    <p>For example, you'll find Controllers, Models, Helpers, Blocks, etc. related to OpenMage's checkout
                         functionality in
                     </p>
                     <pre>app/code/core/Mage/Checkout</pre>
-                    <p>You'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's Google Checkout
+                    <p>You'll find Controllers, Models, Helpers, Blocks, etc. related to OpenMage's Google Checkout
                         functionality in
                     </p>
                     <pre>app/code/core/Mage/GoogleCheckout</pre>
                     <h4>Your Code</h4>
-                    <p>When you want to customize or extend Magento, rather than editing core files directly, or even
-                        placing your new Controllers, Models, Helpers, Blocks, etc. next to Magento code, you'll create
+                    <p>When you want to customize or extend OpenMage, rather than editing core files directly, or even
+                        placing your new Controllers, Models, Helpers, Blocks, etc. next to OpenMage code, you'll create
                         your own Modules in
                     </p>
                     <pre>app/code/local/Package/Modulename</pre>
                     <p><b>Package</b> (also often referred to as a <b>Namespace</b>) is a unique name that identifies
-                        your company or organization. The intent is that each member of the world-wide Magento community
+                        your company or organization. The intent is that each member of the world-wide OpenMage community
                         will use their own Package name when creating modules in order to avoid colliding with another
                         user's code. </p>
-                    <p>When you create a new Module, you need to tell Magento about it. This is done by adding an XML
+                    <p>When you create a new Module, you need to tell OpenMage about it. This is done by adding an XML
                         file to the folder:</p>
                     <pre>app/etc/modules</pre>
                     <p>There are two kinds of files in this folder, the first enables an individual Module, and is named
@@ -320,31 +318,31 @@ <h4>Your Code</h4>
                     this breaks the modularity of your modules.
                     <a name="2"></a>
                     <h2>Configuration-Based MVC</h2>
-                    <p>Magento is a <b>configuration-based</b> MVC system. The alternative to this would a <b>convention-based</b>
+                    <p>OpenMage is a <b>configuration-based</b> MVC system. The alternative to this would a <b>convention-based</b>
                         MVC system.</p>
                     <p>In a convention-based MVC system, if you wanted to add, say, a new Controller or maybe a new
                         Model, you'd just create the file/class, and the system would pick it up automatically.</p>
-                    <p>In a configuration-based system, like Magento, in addition to adding the new file/class to the
+                    <p>In a configuration-based system, like OpenMage, in addition to adding the new file/class to the
                         codebase, you often need to explicitly tell the system about the new class, or new group of
-                        classes. In Magento, each Module has a file named <tt>config.xml</tt>. This file contains all
-                        the relevant configuration for a Magento Module. At runtime, all these files are loaded into one
+                        classes. In OpenMage, each Module has a file named <tt>config.xml</tt>. This file contains all
+                        the relevant configuration for a OpenMage Module. At runtime, all these files are loaded into one
                         large configuration tree.</p>
                     <p>For example, want to use Models in your custom Module? You'll need to add some code to <tt>config.xml</tt>
-                        that tells Magento you want to use Models, as well as what the base class name for all your
+                        that tells OpenMage you want to use Models, as well as what the base class name for all your
                         Models should be.</p>
                     <pre>
-                    &lt;models>
-                             &lt;packagename>
-                                  &lt;class>Packagename_Modulename_Model&lt;/class>
-                            &lt;/packagename>
-                    &lt;/models>
-                    </pre>
+&lt;models>
+    &lt;packagename>
+        &lt;class>Packagename_Modulename_Model&lt;/class>
+    &lt;/packagename>
+&lt;/models>
+</pre>
                     <p>The same goes for Helpers, Blocks, Routes for your Controllers, Event Handlers, and more. Almost
-                        anytime you want to tap into the power of the Magento system, you'll need to make some change or
+                        anytime you want to tap into the power of the OpenMage system, you'll need to make some change or
                         addition to your config file.</p>
                     <a name="3"></a>
                     <h2>Controllers</h2>
-                    <p>In any PHP system, the main PHP entry point remains a PHP file. Magento is no different, and that
+                    <p>In any PHP system, the main PHP entry point remains a PHP file. OpenMage is no different, and that
                         file is <tt>index.php</tt>.</p>
                     <p>However, you never CODE in index.php. In an MVC system, index.php will contain code/calls to code
                         that does the following:</p>
@@ -355,41 +353,41 @@ <h2>Controllers</h2>
                         <li><p>Instantiates the Controller class and calls the Action method (called dispatching)</p>
                         </li>
                     </ol>
-                    <p>This means the <strong>practical</strong> entry point in Magento (or any MVC-based system) is a
+                    <p>This means the <strong>practical</strong> entry point in OpenMage (or any MVC-based system) is a
                         method in a Controller file. Consider the following URL:</p>
                     <pre>http://example.com/catalog/category/view/id/25</pre>
                     <p>Each portion of the path after the server name is parsed as follows.</p>
                     <h4>Front Name - <tt>catalog</tt></h4>
-                    <p>The first portion of the URL is called the front name. This, more or less, tells magento which
+                    <p>The first portion of the URL is called the front name. This, more or less, tells OpenMage which
                         Module it can find a Controller in. In the above example, the front name is <em>catalog</em>,
                         which corresponds to the Module located at:</p>
                     <pre>app/code/core/Mage/Catalog</pre>
                     <h4>Controller Name - <tt>category</tt></h4>
-                    <p>The second portion of the URL tells Magento which Controller it should use. Each Module with
+                    <p>The second portion of the URL tells OpenMage which Controller it should use. Each Module with
                         Controllers has a special folder named 'controllers' which contains all the Controllers for a
                         module. In the above example, the URL portion category is translated into the Controller
                         file</p>
                     <pre>app/code/core/Mage/Catalog/controllers/CategoryController.php</pre>
                     <p>Which looks like</p>
                     <pre>
-                        class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
-                        {
-                        }
-                    </pre>
-                    <p>All Controllers in the Magento cart application extend from
+class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
+{
+}
+</pre>
+                    <p>All Controllers in the OpenMage cart application extend from
                         Mage_Core_Controller_Front_Action.</p>
                     <h4>Action Name - <tt>view</tt></h4>
                     <p>Third in our URL is the action name. In our example, this is "view". The word "view" is used to
                         create the Action Method. So, in our example, "view" would be turned into "viewAction"</p>
                     <pre>
-                        class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
-                        {
-                            public function viewAction()
-                            {
-                                //main entry point
-                            }
-                        }
-                    </pre>
+class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
+{
+    public function viewAction()
+    {
+        //main entry point
+    }
+}
+</pre>
                     <p>People familiar with the Zend Framework will recognize the naming convention here.</p>
                     <h4>Parameter/Value - <tt>id/25</tt></h4>
                     <p>Any path portions after the action name will be considered key/value GET request variables. So,
@@ -398,48 +396,48 @@ <h4>Parameter/Value - <tt>id/25</tt></h4>
                     <p>As previously mentioned, if you want your Module to use Controllers, you'll need to configure
                         them. Below is the configuration chunk that enables Controllers for the Catalog Module</p>
                     <pre>
-                        &lt;frontend>
-                            &lt;routers>
-                                &lt;catalog>
-                                    &lt;use>standard&lt;/use>
-                                    &lt;args>
-                                        &lt;module&gt;Mage_Catalog&lt;/module&gt;
-                                        &lt;frontName>catalog&lt;/frontName>
-                                    &lt;/args>
-                                &lt;/catalog>
-                            &lt;/routers>
-                        &lt;/frontend>
-                    </pre>
+&lt;frontend>
+    &lt;routers>
+        &lt;catalog>
+            &lt;use>standard&lt;/use>
+            &lt;args>
+                &lt;module&gt;Mage_Catalog&lt;/module&gt;
+                &lt;frontName>catalog&lt;/frontName>
+            &lt;/args>
+        &lt;/catalog>
+    &lt;/routers>
+&lt;/frontend>
+</pre>
                     <p>Don't worry too much about the specifics right now, but notice the</p>
                     <tt>&lt;frontName&gt;catalog&lt;/frontName&gt;
                     </tt>
-                    <p>This is what links a Module with a URL frontname. Most Magento core Modules choose a frontname
+                    <p>This is what links a Module with a URL frontname. Most OpenMage core Modules choose a frontname
                         that is the same as their Module name, but this is not required. </p>
                     <h3>Multiple Routers</h3>
 
-                    <p>The routing described above is for the Magento cart application (often called the frontend). If
-                        Magento doesn't find a valid Controller/Action for a URL, it tries again, this time using a
-                        second set of Routing rules for the Admin application. If Magento doesn't find a valid <strong>Admin</strong>
+                    <p>The routing described above is for the OpenMage cart application (often called the frontend). If
+                        OpenMage doesn't find a valid Controller/Action for a URL, it tries again, this time using a
+                        second set of Routing rules for the Admin application. If OpenMage doesn't find a valid <strong>Admin</strong>
                         Controller/Action, it uses a special Controller named <tt>Mage_Cms_IndexController</tt>.</p>
 
-                    <p>The CMS Controller checks Magento's content Management system to see if there's any content that
+                    <p>The CMS Controller checks OpenMage's content Management system to see if there's any content that
                         should be loaded. If it finds some, it loads it, otherwise the user will be presented with a 404
                         page. </p>
 
-                    <p>For example, the main magento "index" page is one that uses the CMS Controller, which can often
+                    <p>For example, the main OpenMage "index" page is one that uses the CMS Controller, which can often
                         throw newcomers for a loop.</p>
 
                     <a name="4"></a>
                     <h2>Context-Based URI Model Loading</h2>
 
                     <p>Now that we're in our Action method entry point, we'll want to start instantiating classes that
-                        do things. Magento offers a special way to instantiate Models, Helpers and Blocks using static
+                        do things. OpenMage offers a special way to instantiate Models, Helpers and Blocks using static
                         factory methods on the global Mage class. For example:
                     </p>
                     <pre>
-                        Mage::getModel('catalog/product');
-                        Mage::helper('catalog/product');
-                    </pre>
+Mage::getModel('catalog/product');
+Mage::helper('catalog/product');
+</pre>
                     <p>The string 'catalog/product' is called a Grouped Class Name. It's also often called a URI. The
                         first portion of any Grouped Class Name (in this case, catalog), is used to lookup which Module
                         the class resides in. The second portion ('product' above) is used to determine which class
@@ -451,12 +449,12 @@ <h2>Context-Based URI Model Loading</h2>
                     <p>Meaning our class name will start with <tt>Mage_Catalog</tt>.</p>
                     <p>Then, product is added to get the final class name</p>
                     <pre>
-                        Mage::getModel('catalog/product');
-                        Mage_Catalog_Model_Product
+Mage::getModel('catalog/product');
+Mage_Catalog_Model_Product
 
-                        Mage::helper('catalog/product');
-                        Mage_Catalog_Helper_Product
-                    </pre>
+Mage::helper('catalog/product');
+Mage_Catalog_Helper_Product
+</pre>
                     <p>These rules are bound by what's been setup in each Module's config file. When you create your own
                         custom Module, you'll have your own grouped classnames (also calles classgroups) to work with
                         <tt>Mage::getModel('myspecialprefix/modelname');</tt>.
@@ -465,20 +463,20 @@ <h2>Context-Based URI Model Loading</h2>
                         as we'll learn later, there are certain advantages to doing so.
                     </p>
                     <a name="5"></a>
-                    <h2>Magento Models</h2>
-                    <p>Magento, like most frameworks these days, offers an Object Relational Mapping (ORM) system. ORMs
+                    <h2>OpenMage Models</h2>
+                    <p>OpenMage, like most frameworks these days, offers an Object Relational Mapping (ORM) system. ORMs
                         get you out of the business of writing SQL and allow you to manipulate a datastore purely
                         through PHP code. For example:
                     </p>
                     <pre>
-                        $model = Mage::getModel('catalog/product')-&gt;load(27);
-                        $price = $model-&gt;getPrice();
-                        $price += 5;
-                        $model-&gt;setPrice($price)-&gt;setSku('SK83293432');
-                        $model-&gt;save();
-                    </pre>
+$model = Mage::getModel('catalog/product')-&gt;load(27);
+$price = $model-&gt;getPrice();
+$price += 5;
+$model-&gt;setPrice($price)-&gt;setSku('SK83293432');
+$model-&gt;save();
+</pre>
                     <p>In the above example we're calling the methods "getPrice" and "setPrice" on our Product. However,
-                        the Mage_Catalog_Model_Product class has no methods with these names. That's because Magento's
+                        the Mage_Catalog_Model_Product class has no methods with these names. That's because OpenMage's
                         ORM uses PHP's magic <em>__call</em> method to implement getters and setters.
                     </p>
                     <p>Calling the method <tt>$product-&gt;getPrice();</tt> will "get" the Model attribute "price".</p>
@@ -493,40 +491,40 @@ <h2>Magento Models</h2>
                     <p>You'll also notice it's possible to chain together several calls to the set method: </p>
                     <tt>$model-&gt;setPrice($price)-&gt;setSku('SK83293432');</tt>
                     <p>That's because each set method returns an instance of the Model. This is a pattern you'll see
-                        used in much of the Magento codebase.
+                        used in much of the OpenMage codebase.
                     </p>
-                    <p>Magento's ORM also contains a way to query for multiple Objects via a Collections interface. The
+                    <p>OpenMage's ORM also contains a way to query for multiple Objects via a Collections interface. The
                         following would get us a collection of all products that cost $5.00
                     </p>
                     <pre>
-                        $products_collection = Mage::getModel('catalog/product')
-                        ->getCollection()
-                        ->addAttributeToSelect('*')
-                        ->addFieldToFilter('price','5.00');
-                    </pre>
-                    <p>Again, you'll notice Magento's implemented a chaining interface here. Collections use the PHP
+$products_collection = Mage::getModel('catalog/product')
+    ->getCollection()
+    ->addAttributeToSelect('*')
+    ->addFieldToFilter('price','5.00');
+</pre>
+                    <p>Again, you'll notice OpenMage's implemented a chaining interface here. Collections use the PHP
                         Standard Library to implement Objects that have array like properties.
                     </p>
                     <pre>
-                        foreach($products_collection as $product)
-                        {
-                            echo $product-&gt;getName();
-                        }
-                    </pre>
-                    <p>You may be wondering what the "addAttributeToSelect" method is for. Magento has two broad types
+foreach($products_collection as $product)
+{
+    echo $product-&gt;getName();
+}
+</pre>
+                    <p>You may be wondering what the "addAttributeToSelect" method is for. OpenMage has two broad types
                         of Model objects. One is a traditional "One Object, One Table" Active Record style Model. When
                         you instantiate these Models, all attributes are automatically selected.
                     </p>
                     <p>The second type of Model is an Entity Attribute Value (EAV) Model. EAV Models spread data across
-                        several different tables in the database. This gives the Magento system the flexibility to offer
+                        several different tables in the database. This gives the OpenMage system the flexibility to offer
                         its flexible product attribute system without having to do a schema change each time you add an
-                        attribute. When creating a collection of EAV objects, Magento is conservative in the number of
+                        attribute. When creating a collection of EAV objects, OpenMage is conservative in the number of
                         columns it will query for, so you can use addAttributeToSelect to get the columns you want, or
                         addAttributeToSelect('*') to get all columns.
                     </p>
                     <a name="6"></a>
                     <h2>Helpers</h2>
-                    <p>Magento's Helper classes contain utility methods that will allow you to perform common tasks on
+                    <p>OpenMage's Helper classes contain utility methods that will allow you to perform common tasks on
                         objects and variables. For example:</p>
                     <tt>$helper = Mage::helper('catalog');</tt>
                     <p>You'll notice we've left off the second part of the grouped class name. Each Module has a default
@@ -537,9 +535,9 @@ <h2>Helpers</h2>
                         default.
                     </p>
                     <pre>
-                        $translated_output =  $helper-&gt;__('Magento is Great'); //gettext style translations
-                        if($helper-&gt;isModuleOutputEnabled()): //is output for this module on or off?
-                    </pre>
+$translated_output =  $helper-&gt;__('OpenMage is Great'); //gettext style translations
+if($helper-&gt;isModuleOutputEnabled()): //is output for this module on or off?
+</pre>
                     <a name="7"></a>
                     <h2>Layouts</h2>
                     <p>So, we've seen Controllers, Models, and Helpers. In a typical PHP MVC system, after we've
@@ -550,38 +548,38 @@ <h2>Layouts</h2>
                         <li>The system would load a default "outer" HTML layout></li>
                         <li>The system would then load our view inside that outer layout</li>
                     </ol>
-                    <p>However, if you look at a typical Magento Controller action, you don't see any of this:</p>
+                    <p>However, if you look at a typical OpenMage Controller action, you don't see any of this:</p>
                     <pre>
-                        /**
-                         * View product gallery action
-                         */
-                        public function galleryAction()
-                        {
-                            if (!$this-&gt;_initProduct()) {
-                                if (isset($_GET['store']) && !$this-&gt;getResponse()-&gt;isRedirect()) {
-                                    $this-&gt;_redirect('');
-                                } elseif (!$this-&gt;getResponse()-&gt;isRedirect()) {
-                                    $this-&gt;_forward('noRoute');
-                                }
-                                return;
-                            }
-                            $this-&gt;loadLayout();
-                            $this-&gt;renderLayout();
-                        }
-                    </pre>
+/**
+* View product gallery action
+*/
+public function galleryAction()
+{
+    if (!$this-&gt;_initProduct()) {
+        if (isset($_GET['store']) && !$this-&gt;getResponse()-&gt;isRedirect()) {
+            $this-&gt;_redirect('');
+        } elseif (!$this-&gt;getResponse()-&gt;isRedirect()) {
+            $this-&gt;_forward('noRoute');
+        }
+        return;
+    }
+    $this-&gt;loadLayout();
+    $this-&gt;renderLayout();
+}
+</pre>
                     <p>Instead, the Controller action ends with two calls</p>
                     <pre>
-                        $this-&gt;loadLayout();
-                        $this-&gt;renderLayout();
-                    </pre>
-                    <p>So, the "V" in Magento's MVC already differs from what you're probably used to, in that you need
+$this-&gt;loadLayout();
+$this-&gt;renderLayout();
+</pre>
+                    <p>So, the "V" in OpenMage's MVC already differs from what you're probably used to, in that you need
                         to explicitly kick off rendering the layout.
                     </p>
-                    <p>The layout itself also differs. A Magento Layout is an object that contains a nested/tree
+                    <p>The layout itself also differs. A OpenMage Layout is an object that contains a nested/tree
                         collection of "Block" objects. Each Block object will render a specific bit of HTML. Block
                         objects do this through a combination of PHP code, and including PHP .phtml template files.
                     </p>
-                    <p>Blocks objects are meant to interact with the Magento system to retrieve data from Models, while
+                    <p>Blocks objects are meant to interact with the OpenMage system to retrieve data from Models, while
                         the phtml template files will produce the HTML needed for a page.
                     </p>
                     <p>For example, the page header Block <tt>app/code/core/Mage/Page/Block/Html/Head.php</tt> uses the
@@ -593,10 +591,10 @@ <h2>Layouts</h2>
                     </p>
                     <p>By default, when you call</p>
                     <pre>
-                        $this->loadLayout();
-                        $this->renderLayout();
-                    </pre>
-                    <p>Magento will load up a Layout with a skeleton site structure. There will be Structure Blocks to
+$this->loadLayout();
+$this->renderLayout();
+</pre>
+                    <p>OpenMage will load up a Layout with a skeleton site structure. There will be Structure Blocks to
                         give you your <tt>html</tt>, <tt>head</tt>, and <tt>body</tt>, as well as HTML to setup single
                         or multiple columns of Layout. Additionally, there will be a few Content Blocks for the
                         navigation, default welcome message, etc.
@@ -605,32 +603,32 @@ <h2>Layouts</h2>
                         programmatically know if it's Structure or Content, but it's useful to think of a Block as one
                         or the other.
                     </p>
-                    <p>To add Content to this Layout you need to tell the Magento system something like</p>
-                    <pre>"Hey, Magento, add these additional Blocks under the "content" Block of the skeleton"</pre>
+                    <p>To add Content to this Layout you need to tell the OpenMage system something like</p>
+                    <pre>"Hey, OpenMage, add these additional Blocks under the "content" Block of the skeleton"</pre>
                     or
-                    <pre>"Hey, Magento, add these additional Blocks under the "left column" Block of the skeleton"</pre>
+                    <pre>"Hey, OpenMage, add these additional Blocks under the "left column" Block of the skeleton"</pre>
                     <p>This can be done programmatically in a Controller action</p>
                     <pre>
-                        public function indexAction()
-                        {
-                            $this-&gt;loadLayout();
-                            $block = $this-&gt;getLayout()-&gt;createBlock('adminhtml/system_account_edit')
-                            $this-&gt;getLayout()-&gt;getBlock('content')-&gt;append($block);
-                            $this-&gt;renderLayout();
-                        }
-                    </pre>
+public function indexAction()
+{
+    $this-&gt;loadLayout();
+    $block = $this-&gt;getLayout()-&gt;createBlock('adminhtml/system_account_edit')
+    $this-&gt;getLayout()-&gt;getBlock('content')-&gt;append($block);
+    $this-&gt;renderLayout();
+}
+</pre>
                     <p>but more commonly (at least in the frontend cart application), is use of the XML Layout system.</p>
                     <p>The Layout XML files in a theme allow you, on a per Controller basis, to remove Blocks that would
                         normally be rendered, or add Blocks to that default skeleton areas. For example, consider this
                         Layout XML file:
                     </p>
                     <pre>
-                        &lt;catalog_category_default>
-                            &lt;reference name="left">
-                                &lt;block type="catalog/navigation" name="catalog.leftnav" after="currency" template="catalog/navigation/left.phtml"/>
-                            &lt;/reference>
-                        &lt;/catalog_category_default>
-                    </pre>
+&lt;catalog_category_default>
+    &lt;reference name="left">
+        &lt;block type="catalog/navigation" name="catalog.leftnav" after="currency" template="catalog/navigation/left.phtml"/>
+    &lt;/reference>
+&lt;/catalog_category_default>
+</pre>
                     <p>It's saying in the catalog Module, in the category Controller, and the default Action, insert the
                         catalog/navigation Block into the "left" structure Block, using the
                         catalog/navigation/left.phtml template.
@@ -644,55 +642,55 @@ <h2>Layouts</h2>
                     </p>
                     <p>If, however, we had something like:</p>
                     <pre>
-                        &lt;catalog_category_default>
-                            &lt;reference name="left">
-                                &lt;block type="catalog/navigation" name="catalog.leftnav" after="currency" template="catalog/navigation/left.phtml">
-                                    &lt;block type="core/template" name="foobar" template="foo/baz/bar.phtml"/>
-                                &lt;/block>
-                            &lt;/reference>
-                        &lt;/catalog_category_default>
-                    </pre>
+&lt;catalog_category_default>
+    &lt;reference name="left">
+        &lt;block type="catalog/navigation" name="catalog.leftnav" after="currency" template="catalog/navigation/left.phtml">
+            &lt;block type="core/template" name="foobar" template="foo/baz/bar.phtml"/>
+        &lt;/block>
+    &lt;/reference>
+&lt;/catalog_category_default>
+</pre>
                     <p>From the catalog/navigation Block, we'd be able to call </p>
                     <tt>$this-&gt;getChildHtml('foobar');</tt>
                     <br/>
                     <a name="8"></a>
                     <h2>Observers</h2>
-                    <p>Like any good object-oriented system, Magento implements an Event/Observer pattern for end users
+                    <p>Like any good object-oriented system, OpenMage implements an Event/Observer pattern for end users
                         to hook into. As certain actions happen during a Page request (a Model is saved, a user logs in,
-                        etc.), Magento will issue an event signal.
+                        etc.), OpenMage will issue an event signal.
                     </p>
                     <p>When creating your own Modules, you can "listen" for these events. Say you wanted to get an email
                         every time a certain customer logged into the store. You could listen for the "customer_login"
                         event (setup in config.xml)
                     </p>
                     <pre>
-                        &lt;events>
-                            &lt;customer_login>
-                                &lt;observers>
-                                    &lt;unique_name>
-                                        &lt;type>singleton&lt;/type>
-                                        &lt;class>mymodule/observer&lt;/class>
-                                        &lt;method>iSpyWithMyLittleEye&lt;/method>
-                                    &lt;/unique_name>
-                                &lt;/observers>
-                            &lt;/customer_login>
-                        &lt;/events>
-                    </pre>
+&lt;events>
+    &lt;customer_login>
+        &lt;observers>
+            &lt;unique_name>
+                &lt;type>singleton&lt;/type>
+                &lt;class>mymodule/observer&lt;/class>
+                &lt;method>iSpyWithMyLittleEye&lt;/method>
+            &lt;/unique_name>
+        &lt;/observers>
+    &lt;/customer_login>
+&lt;/events>
+</pre>
                     <p>and then write some code that would run whenever a user logged in:</p>
                     <pre>
-                        class Packagename_Mymodule_Model_Observer
-                        {
-                            public function iSpyWithMyLittleEye($observer)
-                            {
-                                $data = $observer-&gt;getData();
-                                //code to check observer data for our user,
-                                //and take some action goes here
-                            }
-                        }
-                    </pre>
+class Packagename_Mymodule_Model_Observer
+{
+    public function iSpyWithMyLittleEye($observer)
+    {
+        $data = $observer-&gt;getData();
+        //code to check observer data for our user,
+        //and take some action goes here
+    }
+}
+</pre>
                     <a name="9"></a>
                     <h2>Class Overrides</h2>
-                    <p>Finally, the Magento System offers you the ability to replace Model, Helper and Block classes
+                    <p>Finally, the OpenMage System offers you the ability to replace Model, Helper and Block classes
                         from the core modules with your own. This is a feature that's similar to "Duck Typing" or
                         "Monkey Patching" in a language like Ruby or Python.
                     </p>
@@ -702,39 +700,39 @@ <h2>Class Overrides</h2>
                     <p>Whenever the following code is called, a Mage_Catalog_Model_Product object is created</p>
                     <pre>$product = Mage::getModel('catalog/product');</pre>
                     <p>This is a factory pattern. </p>
-                    <p>What Magento's class override system does is allow you to tell the system</p>
+                    <p>What OpenMage's class override system does is allow you to tell the system</p>
                     <pre>"Hey, whenever anyone asks for a catalog/product, instead of giving them a Mage_Catalog_Model_Product,
                         give them a Packagename_Modulename_Model_Foobazproduct instead".
                     </pre>
                     <p>Then, if you want, your Packagename_Modulename_Model_Foobazproduct class can extend the original
                         product class</p>
                     <pre>
-                        class Packagename_Modulename_Model_Foobazproduct extends Mage_Catalog_Model_Product
-                        {
-                        }
-                    </pre>
+class Packagename_Modulename_Model_Foobazproduct extends Mage_Catalog_Model_Product
+{
+}
+</pre>
                     <p>Which will allow you to change the behavior of any method on the class, but keep the
                         functionality of the existing methods.</p>
                     <pre>class Packagename_Modulename_Model_Foobazproduct extends Mage_Catalog_Model_Product
-                        {
-                            public function validate()
-                            {
-                                //add custom validation functionality here
-                                return $this;
-                            }
-                        }
-                    </pre>
+{
+    public function validate()
+    {
+        //add custom validation functionality here
+        return $this;
+    }
+}
+</pre>
                     <p>As you might expect, this overriding (or rewriting) is done in the config.xml file.</p>
                     <pre>
-                        &lt;models>
-                            &lt;!-- does the override for catalog/product-->
-                            &lt;catalog>
-                                &lt;rewrite>
-                                    &lt;product>Packagename_Modulename_Model_Foobazproduct&lt;/product>
-                                &lt;/rewrite>
-                            &lt;/catalog>
-                        &lt;/models>
-                    </pre>
+&lt;models>
+    &lt;!-- does the override for catalog/product-->
+    &lt;catalog>
+        &lt;rewrite>
+            &lt;product>Packagename_Modulename_Model_Foobazproduct&lt;/product>
+        &lt;/rewrite>
+    &lt;/catalog>
+&lt;/models>
+</pre>
                     <p>One thing that's important to note here. Individual classes in <strong>your</strong> Module are
                         overriding individual classes in <strong>other</strong> Modules. You are not, however,
                         overriding the entire Module. This allows you to change specific method behavior without having
@@ -742,7 +740,7 @@ <h2>Class Overrides</h2>
                     </p>
                     <a name="10"></a>
                     <h2>Wrap Up</h2>
-                    <p>We hope you've enjoyed this whirlwind tour of some of the features the Magento eCommerce system
+                    <p>We hope you've enjoyed this whirlwind tour of some of the features the OpenMage eCommerce system
                         offers to developers. It can be a little overwhelming at first, especially if this is your first
                         experience with a modern, object-oriented PHP system. If you start to get frustrated, take a
                         deep breath, remind yourself that this is new, and new things are hard, but at the end of the
diff --git a/guides/m1x/magefordev/mage-for-dev-2.html b/guides/m1x/magefordev/mage-for-dev-2.html
index c4c7f0c0ed..bf73edd1ce 100644
--- a/guides/m1x/magefordev/mage-for-dev-2.html
+++ b/guides/m1x/magefordev/mage-for-dev-2.html
@@ -31,8 +31,6 @@
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
-<!-- magento-for-dev-part-1-introduction-to-magento -->
 <body class="layout-default">
 <header class="site-header">
     <nav class="site-nav">
@@ -65,7 +63,7 @@
                         }</style>
                     </defs>
                     <g class="layer">
-                        <title>OpenMage Magento</title>
+                        <title>OpenMage</title>
                         <path class="ba"
                               d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
                         <text class="bb" id="svg_2" x="0" y="47">
@@ -135,7 +133,7 @@
                                 <div class="nav-section-title">API</div>
                                 <ul>
                                     <li class=" " role="menuitem">
-                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                        <a href="/guides/v19.x/">Get Started with OpenMage Web APIs</a>
                                     </li>
                                     <li class=" " role="menuitem">
                                         <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
@@ -222,22 +220,22 @@ <h4 class="guide-title">Developer Guide</h4>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
-                                    OpenMage Controller Dispatch
+                                    Controller Dispatch
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
-                                    OpenMage Layouts, Blocks and Templates
+                                    Layouts, Blocks and Templates
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
-                                    OpenMage Models and ORM Basics
+                                    Models and ORM Basics
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
-                                    OpenMage Setup Resources
+                                    Setup Resources
                                 </a>
                             </li>
                             <li class="" role="menuitem">
@@ -261,25 +259,25 @@ <h4 class="guide-title">Developer Guide</h4>
                     <section class="page-intro">
                         <h1 class="page-heading">The OpenMage Config</h1>
                     </section>
-                    <p class="para1">The config is the beating heart of the Magento System. It describes, in whole,
+                    <p class="para1">The config is the beating heart of the OpenMage System. It describes, in whole,
                         almost any module, model, class, template, etc. than you'll need to access. It's a level of
                         abstraction that most PHP developers aren't used to working with, and while it adds development
                         time in the form of confusion and head scratching, it also allows you an unprecedented amount of
                         flexibility as far as overriding default system behaviors go. </p>
-                    <p>To start with, we're going to create a Magento module that will let us view the system config in
+                    <p>To start with, we're going to create a OpenMage module that will let us view the system config in
                         our web browser. Follow along by copying and pasting the code below, it's worth going through on
                         your own as a way to start getting comfortable with things you'll be doing while working with
-                        Magento, as well as learning key terminology.</p>
+                        OpenMage, as well as learning key terminology.</p>
                     <a name="1"></a>
                     <h2>Setting up a Module Directory Structure</h2>
-                    <p>We're going to be creating a Magento module. A module is a group of php and xml files meant to
+                    <p>We're going to be creating a OpenMage module. A module is a group of php and xml files meant to
                         extend the system with new functionality, or override core system behavior. This may meaning
                         adding additional data models to track sales information, changing the behavior of existing
                         classes, or adding entirely new features. </p>
-                    <p>It's worth noting that most of the base Magento system is built using the same module system
+                    <p>It's worth noting that most of the base OpenMage system is built using the same module system
                         you'll be using. If you look in </p>
                     <pre>app/code/core/Mage</pre>
-                    <p>each folder is a separate module built by the Magento team. Together, these modules form the
+                    <p>each folder is a separate module built by the OpenMage team. Together, these modules form the
                         community shopping cart system you're using. Your modules should be placed in the following
                         folder</p>
                     <pre>app/code/local/Packagename</pre>
@@ -287,143 +285,145 @@ <h2>Setting up a Module Directory Structure</h2>
                         convention that this should be the name of your company. The idea is to pick a string that no
                         one else in the world could possibly be using.</p>
                     <pre>app/code/local/Microsoft</pre>
-                    <p>We'll use "Magentotutorial".</p>
-                    <p>So, to add a module to your Magento system, create the following directory structure</p>
-                    <pre>app/code/local/Magentotutorial/Configviewer/Block
-                    app/code/local/Magentotutorial/Configviewer/controllers
-                    app/code/local/Magentotutorial/Configviewer/etc
-                    app/code/local/Magentotutorial/Configviewer/Helper
-                    app/code/local/Magentotutorial/Configviewer/Model
-                    app/code/local/Magentotutorial/Configviewer/sql</pre>
+                    <p>We'll use "OpenMagetutorial".</p>
+                    <p>So, to add a module to your OpenMage system, create the following directory structure</p>
+                    <pre>
+app/code/local/OpenMagetutorial/Configviewer/Block
+app/code/local/OpenMagetutorial/Configviewer/controllers
+app/code/local/OpenMagetutorial/Configviewer/etc
+app/code/local/OpenMagetutorial/Configviewer/Helper
+app/code/local/OpenMagetutorial/Configviewer/Model
+app/code/local/OpenMagetutorial/Configviewer/sql
+</pre>
                     <p>You won't need all these folder for every module, but setting them all up now is a smart
                         idea. </p>
                     <p>Next, there's two files you'll need to create. The first, config.xml, goes in the etc folder you
                         just created. </p>
-                    <pre>app/code/local/Magentotutorial/Configviewer/etc/config.xml</pre>
+                    <pre>app/code/local/OpenMagetutorial/Configviewer/etc/config.xml</pre>
                     <p>The second file should be created at the following location</p>
-                    <pre>app/etc/modules/Magentotutorial_Configviewer.xml</pre>
+                    <pre>app/etc/modules/OpenMagetutorial_Configviewer.xml</pre>
                     <p>The naming convention for this files is Packagename_Modulename.xml.</p>
                     <p>The config.xml file should contain the following XML. Don't worry too much about what all this
                         does for now, we'll get there eventually</p>
                     <pre>
-                    &lt;config>
-                        &lt;modules>
-                            &lt;Magentotutorial_Configviewer>
-                                &lt;version>0.1.0&lt;/version>
-                            &lt;/Magentotutorial_Configviewer>
-                        &lt;/modules>
-                    &lt;/config>
-                    </pre>
-                    <p>Finally, Magentotutorial_Configviewer.xml should contain the following xml.</p>
+&lt;config>
+    &lt;modules>
+        &lt;OpenMagetutorial_Configviewer>
+            &lt;version>0.1.0&lt;/version>
+        &lt;/OpenMagetutorial_Configviewer>
+    &lt;/modules>
+&lt;/config>
+</pre>
+                    <p>Finally, OpenMagetutorial_Configviewer.xml should contain the following xml.</p>
                     <pre>
-                    &lt;config>
-                        &lt;modules>
-                            &lt;Magentotutorial_Configviewer>
-                                &lt;active>true&lt;/active>
-                                &lt;codePool>local&lt;/codePool>
-                            &lt;/Magentotutorial_Configviewer>
-                        &lt;/modules>
-                    &lt;/config>
-                    </pre>
-                    <p>That's it. You now have a bare bones module that won't do anything, but that Magento will be
+&lt;config>
+    &lt;modules>
+        &lt;OpenMagetutorial_Configviewer>
+            &lt;active>true&lt;/active>
+            &lt;codePool>local&lt;/codePool>
+        &lt;/OpenMagetutorial_Configviewer>
+    &lt;/modules>
+&lt;/config>
+</pre>
+                    <p>That's it. You now have a bare bones module that won't do anything, but that OpenMage will be
                         aware of. To make sure you've done everything right, do the following:
                     <ol>
-                        <li>Clear your Magento cache</li>
-                        <li>In the Magento Admin, go to <strong>System->Configuration->Advanced</strong></li>
-                        <li>In the "Disable modules output" panel verify that Magentotutorial_Configviewer shows up</li>
+                        <li>Clear your OpenMage cache</li>
+                        <li>In the OpenMage Admin, go to <strong>System->Configuration->Advanced</strong></li>
+                        <li>In the "Disable modules output" panel verify that OpenMagetutorial_Configviewer shows up</li>
                     </ol>
-                    <p>Congratulations, you've built your first Magento module!</p>
+                    <p>Congratulations, you've built your first OpenMage module!</p>
                     <a name="2"></a>
                     <h2>Creating a Module Config</h2>
                     <p>Of course, this module doesn't do anything yet. When we're done, our module will
                     <ol>
                         <li>Check for the existence of a "showConfig" query string variable</li>
-                        <li>If showConfig is present, display our Magento config and halt normal execution</li>
+                        <li>If showConfig is present, display our OpenMage config and halt normal execution</li>
                         <li>Check for the existence of an additional query string variable, showConfigFormat that will
                             let us specify text or xml output.
                         </li>
                     </ol>
                     <p>First, we're going to add the following &lt;global&gt; section to our config.xml file.</p>
                     <pre>
-                    &lt;config>
-                        &lt;modules>...&lt;/modules>
-                        &lt;global>
-                            &lt;events>
-                                &lt;controller_front_init_routers>
-                                    &lt;observers>
-                                        &lt;Magentotutorial_configviewer_model_observer>
-                                            &lt;type>singleton&lt;/type>
-                                            &lt;class>Magentotutorial_Configviewer_Model_Observer&lt;/class>
-                                            &lt;method>checkForConfigRequest&lt;/method>
-                                        &lt;/Magentotutorial_configviewer_model_observer>
-                                    &lt;/observers>
-                                &lt;/controller_front_init_routers>
-                            &lt;/events>
-                        &lt;/global>
-                    &lt;/config>
-                    </pre>
+&lt;config>
+    &lt;modules>...&lt;/modules>
+    &lt;global>
+        &lt;events>
+            &lt;controller_front_init_routers>
+                &lt;observers>
+                    &lt;OpenMagetutorial_configviewer_model_observer>
+                        &lt;type>singleton&lt;/type>
+                        &lt;class>OpenMagetutorial_Configviewer_Model_Observer&lt;/class>
+                        &lt;method>checkForConfigRequest&lt;/method>
+                    &lt;/OpenMagetutorial_configviewer_model_observer>
+                &lt;/observers>
+            &lt;/controller_front_init_routers>
+        &lt;/events>
+    &lt;/global>
+&lt;/config>
+</pre>
                     <p>Then, create a file at </p>
-                    <pre>Magentotutorial/Configviewer/Model/Observer.php</pre>
+                    <pre>OpenMagetutorial/Configviewer/Model/Observer.php</pre>
                     <p>and place the following code inside</p>
                     <pre>
-                    &lt;?php
-                        class Magentotutorial_Configviewer_Model_Observer {
-                            const FLAG_SHOW_CONFIG = 'showConfig';
-                            const FLAG_SHOW_CONFIG_FORMAT = 'showConfigFormat';
+&lt;?php
+    class OpenMagetutorial_Configviewer_Model_Observer
+    {
+        const FLAG_SHOW_CONFIG = 'showConfig';
+        const FLAG_SHOW_CONFIG_FORMAT = 'showConfigFormat';
 
-                            private $request;
+        private $request;
 
-                            public function checkForConfigRequest($observer) {
-                                $this-&gt;request = $observer-&gt;getEvent()-&gt;getData('front')-&gt;getRequest();
-                                if($this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG} === 'true'){
-                                    $this-&gt;setHeader();
-                                    $this-&gt;outputConfig();
-                                }
-                            }
+        public function checkForConfigRequest($observer)
+        {
+            $this-&gt;request = $observer-&gt;getEvent()-&gt;getData('front')-&gt;getRequest();
+            if($this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG} === 'true'){
+                $this-&gt;setHeader();
+                $this-&gt;outputConfig();
+            }
+        }
 
-                            private function setHeader() {
-                                $format = isset($this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG_FORMAT}) ?
-                                $this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG_FORMAT} : 'xml';
-                                switch($format){
-                                    case 'text':
-                                        header("Content-Type: text/plain");
-                                        break;
-                                    default:
-                                        header("Content-Type: text/xml");
-                                }
-                            }
+        private function setHeader()
+        {
+            $format = isset($this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG_FORMAT}) ?
+            $this-&gt;request-&gt;{self::FLAG_SHOW_CONFIG_FORMAT} : 'xml';
+            switch($format){
+                case 'text':
+                    header("Content-Type: text/plain");
+                    break;
+                default:
+                    header("Content-Type: text/xml");
+            }
+        }
 
-                            private function outputConfig() {
-                                die(Mage::app()-&gt;getConfig()-&gt;getNode()-&gt;asXML());
-                            }
-                        }
-                    </pre>
-                    <p>That's it. Clear your Magento cache again and then load any Magento URL with a <tt>showConfig=true</tt>
+        private function outputConfig()
+        {
+            die(Mage::app()-&gt;getConfig()-&gt;getNode()-&gt;asXML());
+        }
+    }
+</pre>
+                    <p>That's it. Clear your OpenMage cache again and then load any OpenMage URL with a <tt>showConfig=true</tt>
                         query string</p>
-                    <pre>http://magento.example.com/?showConfig=true</pre>
+                    <pre>http://openmage.example.com/?showConfig=true</pre>
                     <a name="3"></a>
                     <h2>What am I looking at?</h2>
-                    <p>You should be looking at a giant XML file. This describes the state of your Magento system. It
+                    <p>You should be looking at a giant XML file. This describes the state of your OpenMage system. It
                         lists all modules, models, classes, event listeners or almost anything else you could think
                         of.</p>
                     <p>For example, consider the config.xml file you created above. If you search the XML file in your
                         browser for the text <tt>Configviewer_Model_Observer</tt> you'll find your class listed. Every
-                        module's config.xml file is parsed by Magento and included in the global config.</p>
+                        module's config.xml file is parsed by OpenMage and included in the global config.</p>
                     <a name="4"></a>
                     <h2>Why Do I Care?</h2>
-                    <p>Right now this may seem esoteric, but this config is key to understanding Magento. Every module
+                    <p>Right now this may seem esoteric, but this config is key to understanding OpenMage. Every module
                         you'll be creating will add to this config, and anytime you need to access a piece of core
-                        system functionality, Magento will be referring back to the config to look something up. </p>
+                        system functionality, OpenMage will be referring back to the config to look something up. </p>
                     <p>A quick example: As an MVC developer, you've likely worked with some kind of helper class,
                         instantiated something like </p>
-                    <pre>
-                    $helper_sales = new HelperSales();
-                    </pre>
-                    <p>One of the things Magento has done is abstract away PHP's class declaration. In Magento, the
+                    <pre>$helper_sales = new HelperSales();</pre>
+                    <p>One of the things OpenMage has done is abstract away PHP's class declaration. In OpenMage, the
                         above code looks something like </p>
-                    <pre>
-                    $helper_sales = Mage::helper('sales');
-                    </pre>
+                    <pre>$helper_sales = Mage::helper('sales');</pre>
                     <p>In plain english, the static helper method will:
                     <ol>
                         <li>Look in the &lt;helpers /&gt; section of the Config.</li>
@@ -435,7 +435,7 @@ <h2>Why Do I Care?</h2>
                         <li>Instantiate the class found in #4 (Mage_Sales_Helper_Data)</li>
                     </ol>
                     <p>While this seems like a lot of work (and it is), the key advantage is by always looking to the
-                        config file for class names, we can override core Magento functionality <strong>without</strong>
+                        config file for class names, we can override core OpenMage functionality <strong>without</strong>
                         changing or adding to the core code. This level of meta programming, not usually found in PHP,
                         allows you to cleanly extend only the parts of the system you need to.</p>
                 </div>
diff --git a/guides/m1x/magefordev/mage-for-dev-3.html b/guides/m1x/magefordev/mage-for-dev-3.html
index c5ebee5f10..e47a42a9e6 100644
--- a/guides/m1x/magefordev/mage-for-dev-3.html
+++ b/guides/m1x/magefordev/mage-for-dev-3.html
@@ -31,8 +31,6 @@
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
-<!-- magento-for-dev-part-1-introduction-to-magento -->
 <body class="layout-default">
 <header class="site-header">
     <nav class="site-nav">
@@ -65,7 +63,7 @@
                         }</style>
                     </defs>
                     <g class="layer">
-                        <title>OpenMage Magento</title>
+                        <title>OpenMage</title>
                         <path class="ba"
                               d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
                         <text class="bb" id="svg_2" x="0" y="47">
@@ -135,7 +133,7 @@
                                 <div class="nav-section-title">API</div>
                                 <ul>
                                     <li class=" " role="menuitem">
-                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                        <a href="/guides/v19.x/">Get Started with OpenMage Web APIs</a>
                                     </li>
                                     <li class=" " role="menuitem">
                                         <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
@@ -215,29 +213,29 @@ <h4 class="guide-title">Developer Guide</h4>
                                     Introduction to OpenMage
                                 </a>
                             </li>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
                                     The OpenMage Config
                                 </a>
                             </li>
                             <li class="active" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
-                                    OpenMage Controller Dispatch
+                                    Controller Dispatch
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
-                                    OpenMage Layouts, Blocks and Templates
+                                    Layouts, Blocks and Templates
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
-                                    OpenMage Models and ORM Basics
+                                    Models and ORM Basics
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
-                                    OpenMage Setup Resources
+                                    Setup Resources
                                 </a>
                             </li>
                             <li class="" role="menuitem">
@@ -300,13 +298,13 @@ <h1 class="page-heading">OpenMage Controller Dispatch</h1>
                                 </li>
                             </ul>
                     </ul>
-                    <p>As you've probably guessed, the Magento team shares this world view and has created a more
+                    <p>As you've probably guessed, the OpenMage team shares this world view and has created a more
                         abstract MVC pattern that looks something <a
                                 href="http://alanstorm.com/2009/img/magento-book/magento-mvc.png">like this:</a>.
                     <ol>
                         <li>A URL is intercepted by a single PHP file.</li>
-                        <li>This PHP file instantiates a Magento application.</li>
-                        <li>The Magento application instantiates a Front Controller object.</li>
+                        <li>This PHP file instantiates a OpenMage application.</li>
+                        <li>The OpenMage application instantiates a Front Controller object.</li>
                         <li>Front Controller instantiates any number of Router objects (specified in global config).
                         </li>
                         <li>Routers check the request URL for a "match".</li>
@@ -335,98 +333,99 @@ <h1 class="page-heading">OpenMage Controller Dispatch</h1>
                     <h2>Hello World</h2>
                     <p>Enough theory, it's time for Hello World. We're going to</p>
                     <ol>
-                        <li>Create a Hello World module in the Magento system</li>
+                        <li>Create a Hello World module in the OpenMage system</li>
                         <li>Configure this module with routes</li>
                         <li>Create Action Controller(s) for our routes</li>
                     </ol>
                     <h3>Create Hello World Module</h3>
                     <p>First, we'll create a directory structure for this module. Our directory structure should look as
                         follows:
-                    <pre>app/code/local/Magentotutorial/Helloworld/Block
-                    app/code/local/Magentotutorial/Helloworld/controllers
-                    app/code/local/Magentotutorial/Helloworld/etc
-                    app/code/local/Magentotutorial/Helloworld/Helper
-                    app/code/local/Magentotutorial/Helloworld/Model
-                    app/code/local/Magentotutorial/Helloworld/sql
+                    <pre style="white-space: pre-line">
+                    app/code/local/OpenMagetutorial/Helloworld/Block
+                    app/code/local/OpenMagetutorial/Helloworld/controllers
+                    app/code/local/OpenMagetutorial/Helloworld/etc
+                    app/code/local/OpenMagetutorial/Helloworld/Helper
+                    app/code/local/OpenMagetutorial/Helloworld/Model
+                    app/code/local/OpenMagetutorial/Helloworld/sql
                     </pre>
-                    <p>Then create a configuration file for the module (at path <tt>app/code/local/Magentotutorial/Helloworld/etc/config.xml</tt>):
+                    <p>Then create a configuration file for the module (at path <tt>app/code/local/OpenMagetutorial/Helloworld/etc/config.xml</tt>):
                     <pre>
-                    &lt;config>
-                        &lt;modules>
-                            &lt;Magentotutorial_Helloworld>
-                                &lt;version>0.1.0&lt;/version>
-                            &lt;/Magentotutorial_Helloworld>
-                        &lt;/modules>
-                    &lt;/config>
-                    </pre>
-                    <p>Then create a file to activate the module (at path <tt>app/etc/modules/Magentotutorial_Helloworld.xml</tt>):
+&lt;config>
+    &lt;modules>
+        &lt;OpenMagetutorial_Helloworld>
+            &lt;version>0.1.0&lt;/version>
+        &lt;/OpenMagetutorial_Helloworld>
+    &lt;/modules>
+&lt;/config>
+</pre>
+                    <p>Then create a file to activate the module (at path <tt>app/etc/modules/OpenMagetutorial_Helloworld.xml</tt>):
                     <pre>
-                    &lt;config>
-                        &lt;modules>
-                            &lt;Magentotutorial_Helloworld>
-                                &lt;active>true&lt;/active>
-                                &lt;codePool>local&lt;/codePool>
-                            &lt;/Magentotutorial_Helloworld>
-                        &lt;/modules>
-                    &lt;/config>
-                    </pre>
+&lt;config>
+    &lt;modules>
+        &lt;OpenMagetutorial_Helloworld>
+            &lt;active>true&lt;/active>
+            &lt;codePool>local&lt;/codePool>
+        &lt;/OpenMagetutorial_Helloworld>
+    &lt;/modules>
+&lt;/config>
+</pre>
                     <p>Finally, we ensure the module is active:
                     <ol>
-                        <li>Clear your Magento cache.</li>
-                        <li>In the Magento Admin, go to <strong>System-&gt;Configuration-&gt;Advanced</strong>.</li>
+                        <li>Clear your OpenMage cache.</li>
+                        <li>In the OpenMage Admin, go to <strong>System-&gt;Configuration-&gt;Advanced</strong>.</li>
                         <li>Expand "Disable Modules Output" (if it isn't already).</li>
-                        <li>Ensure that Magentotutorial_Helloworld shows up.</li>
+                        <li>Ensure that OpenMagetutorial_Helloworld shows up.</li>
                     </ol>
                     <h3>Configuring Routes</h3>
                     <p>Next, we're going to configure a route. A route will turn a URL into an Action Controller and a
-                        method. Unlike other convention based PHP MVC systems, with Magento you need to explicitly
-                        define a route in the global Magento config.
-                    <p>In your config.xml file(at path app/code/local/Magentotutorial/Helloworld/etc/config.xml), add
+                        method. Unlike other convention based PHP MVC systems, with OpenMage you need to explicitly
+                        define a route in the global OpenMage config.
+                    <p>In your config.xml file(at path app/code/local/MOpenMagetutorial/Helloworld/etc/config.xml), add
                         the following section:
                     <pre>
-                    &lt;config>
-                        ...
-                        &lt;frontend>
-                            &lt;routers>
-                                &lt;helloworld>
-                                    &lt;use>standard&lt;/use>
-                                    &lt;args>
-                                        &lt;module&gt;Magentotutorial_Helloworld&lt;/module&gt;
-                                        &lt;frontName>helloworld&lt;/frontName>
-                                    &lt;/args>
-                                &lt;/helloworld>
-                            &lt;/routers>
-                        &lt;/frontend>
-                        ...
-                    &lt;/config>
-                    </pre>
+&lt;config>
+    ...
+    &lt;frontend>
+        &lt;routers>
+            &lt;helloworld>
+                &lt;use>standard&lt;/use>
+                &lt;args>
+                    &lt;module&gt;OpenMagetutorial_Helloworld&lt;/module&gt;
+                    &lt;frontName>helloworld&lt;/frontName>
+                &lt;/args>
+            &lt;/helloworld>
+        &lt;/routers>
+    &lt;/frontend>
+    ...
+&lt;/config>
+</pre>
                     <p>We have a lot of new terminology here, let's break it down.</p>
                     <h4>What is a &lt;frontend&gt;?</h4>
-                    <p>The &lt;frontend&gt; tag refers to a Magento Area. For now, think of Areas as individual Magento
-                        applications. The "frontend" Area is the public facing Magento shopping cart application. The
+                    <p>The &lt;frontend&gt; tag refers to a OpenMage Area. For now, think of Areas as individual OpenMage
+                        applications. The "frontend" Area is the public facing OpenMage shopping cart application. The
                         "admin" Area is the private administrative console application. The "install" Area is the
-                        application you use to run though installing Magento the first time.</p>
+                        application you use to run though installing OpenMage the first time.</p>
                     <h4>Why a &lt;routers&gt; tags if we're configuring individual routes?</h4>
                     <p>There's a famous quote about computer science, often attributed to Phil Karlton:</p>
                     <blockquote>
                         <p>"There are only two hard things in Computer Science: cache invalidation and naming
                             things"</p>
                     </blockquote>
-                    <p>Magento, like all large systems, suffers from the naming problem in spades. You'll find there are
+                    <p>OpenMage, like all large systems, suffers from the naming problem in spades. You'll find there are
                         many places in the global config, and the system in general, where the naming conventions seem
                         unintuitive or even ambiguous. This is one of those places. Sometimes the
                         <tt>&lt;routers&gt;</tt> tag will enclose configuration information about routers, other times
                         it will enclose configuration information about the actual router objects that do the routing.
-                        This is going to seem counter intuitive at first, but as you start to work with Magento more and
+                        This is going to seem counter intuitive at first, but as you start to work with OpenMage more and
                         more, you'll start to understand its world view a little better. (Or, in the words of Han Solo,
                         "Hey, trust me!").</p>
                     <h4>What is a &lt;frontName&gt;?</h4>
                     <p>When a router parses a URL, it gets separated as follows</p>
                     <pre>http://example.com/frontName/actionControllerName/actionMethod/</pre>
-                    <p>So, by defining a value of "helloworld" in the &lt;frontName&gt; tags, we're telling Magento that
+                    <p>So, by defining a value of "helloworld" in the &lt;frontName&gt; tags, we're telling OpenMage that
                         we want the system to respond to URLs in the form of </p>
                     <pre>http://example.com/helloworld/*</pre>
-                    <p>Many developers new to Magento confuse this frontName with the Front Controller object. They are
+                    <p>Many developers new to OpenMage confuse this frontName with the Front Controller object. They are
                         <strong>not</strong> the same thing. The frontName belongs solely to routing.</p>
                     <h4>What's the &lt;helloworld&gt; tag for?</h4>
                     <p>This tag should be the lowercase version of you module name. Our module name is Helloworld, this
@@ -435,50 +434,50 @@ <h4>What's the &lt;helloworld&gt; tag for?</h4>
                         frontNames match the module names, but it's not a requirement. In your own modules, it's
                         probably better to use a route name that's a combination of your module name and package name to
                         avoid possible namespace collisions.</p>
-                    <h4>What's &lt;module&gt;Magentotutorial_Helloworld&lt;/module&gt; for?</h4>
+                    <h4>What's &lt;module&gt;OpenMagetutorial_Helloworld&lt;/module&gt; for?</h4>
                     <p>This module tag should be the full name of your module, including its package/namespace name.
                         This will be used by the system to locate your Controller files.</p>
                     <h3>Create Action Controller(s) for our Routes</h3>
                     <p>One last step to go, and we'll have our Action Controller. Create a file at
-                    <pre>app/code/local/Magentotutorial/Helloworld/controllers/IndexController.php</pre>
+                    <pre>app/code/local/OpenMagetutorial/Helloworld/controllers/IndexController.php</pre>
                     <p>That contains the following
                     <pre>
-                    &#60;&#63;php
-                    class Magentotutorial_Helloworld_IndexController extends Mage_Core_Controller_Front_Action {
-                        public function indexAction() {
-                            echo 'Hello World';
-                        }
-                    }
-                    </pre>
+&#60;&#63;php
+    class OpenMagetutorial_Helloworld_IndexController extends Mage_Core_Controller_Front_Action {
+        public function indexAction() {
+            echo 'Hello World';
+        }
+    }
+</pre>
                     <p>Clear your config cache, and load the following URL </p>
                     <pre>http://example.com/helloworld/index/index</pre>
                     <p>You should also be able to load</p>
-                    <pre>http://example.com/helloworld/index/
-                    http://example.com/helloworld/</pre>
+                    <pre>
+http://example.com/helloworld/index/
+http://example.com/helloworld/
+</pre>
                     <p>You should see a blank page with the text "Hello World". Congratulations, you've setup your first
-                        Magento Controller!</p>
+                        OpenMage Controller!</p>
                     <h4>Where do Action Controllers go?</h4>
                     <p>Action Controllers should be placed in a module's <tt>controllers</tt> (lowercase c) folder. This
                         is where the system will look for them.</p>
                     <h4>How should Action Controllers be named?</h4>
                     <p>Remember the &lt;module&gt; tag back in config.xml?
-                    <pre>
-                    &lt;module&gt;Magentotutorial_Helloworld&lt;/module&gt;
-                    </pre>
+                    <pre>&lt;module&gt;OpenMagetutorial_Helloworld&lt;/module&gt;</pre>
                     <p>An Action Controller's name will
                     <ol>
-                        <li>Start with this &lt;module&gt; string specified in config.xml (<tt>Magentotutorial_Helloworld</tt>)
+                        <li>Start with this &lt;module&gt; string specified in config.xml (<tt>OpenMagetutorial_Helloworld</tt>)
                         </li>
-                        <li>Be followed by an underscore (<tt>Magentotutorial_Helloworld_</tt>)</li>
+                        <li>Be followed by an underscore (<tt>OpenMagetutorial_Helloworld_</tt>)</li>
                         <li>Which will be followed by the Action Controller's name
-                            (<tt>Magentotutorial_Helloworld_Index</tt>)
+                            (<tt>OpenMagetutorial_Helloworld_Index</tt>)
                         </li>
-                        <li>And finally, the word "Controller" (<tt>Magentotutorial_Helloworld_IndexController</tt>)
+                        <li>And finally, the word "Controller" (<tt>OpenMagetutorial_Helloworld_IndexController</tt>)
                         </li>
                     </ol>
                     <p>All Action Controllers need <tt>Mage_Core_Controller_Front_Action</tt> as an ancestor.</p>
                     <h4>What's that index/index nonsense?</h4>
-                    <p>As we previously mentioned, Magento URLs are routed (by default) as follows
+                    <p>As we previously mentioned, OpenMage URLs are routed (by default) as follows
                     <pre>http://example.com/frontName/actionControllerName/actionMethod/</pre>
                     <p>So in the URL
                     <pre>http://example.com/helloworld/index/index</pre>
@@ -486,15 +485,15 @@ <h4>What's that index/index nonsense?</h4>
                         name), which is followed by another index, which is the name of the Action Method that will be
                         called. (an Action of index will call the method <tt>public function <strong>index</strong>Action(){...}</tt>.
                     </p>
-                    <p>If a URL is incomplete, Magento uses "index" as the default, which is why the following URLs are
+                    <p>If a URL is incomplete, OpenMage uses "index" as the default, which is why the following URLs are
                         equivalent.
                     <pre>
-                    http://example.com/helloworld/index
-                    http://example.com/helloworld
-                    </pre>
+http://example.com/helloworld/index
+http://example.com/helloworld
+</pre>
                     <p>If we had a URL that looked like this</p>
                     <pre>http://example.com/checkout/cart/add</pre>
-                    <p>Magento would</p>
+                    <p>OpenMage would</p>
                     <ol>
                         <li>Consult the global config to find the module to use for the frontName checkout (<tt>Mage_Checkout</tt>)
                         </li>
@@ -505,41 +504,41 @@ <h4>Other Action Controller Tricks</h4>
                     <p>Let's try adding a non-default method to our Action Controller. Add the following code to
                         IndexController.php</p>
                     <pre>
-                    public function goodbyeAction() {
-                        echo 'Goodbye World!';
-                    }
-                    </pre>
+public function goodbyeAction() {
+    echo 'Goodbye World!';
+}
+</pre>
                     <p>And then visit the URL to test it out:
                     <pre>http://example.com/helloworld/index/goodbye </pre>
                     <p>Because we're extending the <tt>Mage_Core_Controller_Front_Action</tt> class, we get some methods
                         for free. For example, additional URL elements are automatically parsed into key/value pairs for
                         us. Add the following method to your Action Controller.
                     <pre>
-                    public function paramsAction() {
-                        echo '&lt;dl>';
-                        foreach($this->getRequest()->getParams() as $key=>$value) {
-                            echo '&lt;dt>&lt;strong>Param:&lt;/strong>'.$key.'&lt;/dt>';
-                            echo '&lt;dt>&lt;strong>Value: &lt;/strong>'.$value.'&lt;/dt>';
-                        }
-                        echo '&lt;/dl>';
-                    }
-                    </pre>
+public function paramsAction() {
+    echo '&lt;dl>';
+        foreach($this->getRequest()->getParams() as $key=>$value) {
+            echo '&lt;dt>&lt;strong>Param:&lt;/strong>'.$key.'&lt;/dt>';
+            echo '&lt;dt>&lt;strong>Value: &lt;/strong>'.$value.'&lt;/dt>';
+        }
+    echo '&lt;/dl>';
+}
+</pre>
                     <p>and visit the following URL</p>
                     <pre>http://example.com/helloworld/index/params?foo=bar&amp;baz=eof</pre>
                     <p>You should see each parameter and value printed out.</p>
                     <p>Finally, what would we do if we wanted a URL that responded at
                     <pre>http://example.com/helloworld/messages/goodbye</pre>
                     <p>Here our Action Controller's name is messages, so we'd create a file at
-                    <pre>app/code/local/Magentotutorial/Helloworld/controllers/MessagesController.php</pre>
-                    <p>with an Action Controller named <tt>Magentotutorial_Helloworld_MessagesController</tt> and an
+                    <pre>app/code/local/OpenMagetutorial/Helloworld/controllers/MessagesController.php</pre>
+                    <p>with an Action Controller named <tt>OpenMagetutorial_Helloworld_MessagesController</tt> and an
                         Action Method that looked something like
                     <pre>
-                    public function goodbyeAction()
-                    {
-                        echo 'Another Goodbye';
-                    }
-                    </pre>
-                    <p>And that, in a nutshell, is how Magento implements the Controller portion of MVC. While it's a
+public function goodbyeAction()
+{
+    echo 'Another Goodbye';
+}
+</pre>
+                    <p>And that, in a nutshell, is how OpenMage implements the Controller portion of MVC. While it's a
                         little more complicated than other PHP MVC framework's, it's a highly flexible system that will
                         allow you build almost any URL structure you want.</p>
                 </div>
diff --git a/guides/m1x/magefordev/mage-for-dev-4.html b/guides/m1x/magefordev/mage-for-dev-4.html
index 8040950668..0ad3dcbea9 100644
--- a/guides/m1x/magefordev/mage-for-dev-4.html
+++ b/guides/m1x/magefordev/mage-for-dev-4.html
@@ -31,8 +31,6 @@
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
-<!-- magento-for-dev-part-1-introduction-to-magento -->
 <body class="layout-default">
 <header class="site-header">
     <nav class="site-nav">
@@ -65,7 +63,7 @@
                         }</style>
                     </defs>
                     <g class="layer">
-                        <title>OpenMage Magento</title>
+                        <title>OpenMage</title>
                         <path class="ba"
                               d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
                         <text class="bb" id="svg_2" x="0" y="47">
@@ -135,7 +133,7 @@
                                 <div class="nav-section-title">API</div>
                                 <ul>
                                     <li class=" " role="menuitem">
-                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                        <a href="/guides/v19.x/">Get Started with OpenMage Web APIs</a>
                                     </li>
                                     <li class=" " role="menuitem">
                                         <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
@@ -215,29 +213,29 @@ <h4 class="guide-title">Developer Guide</h4>
                                     Introduction to OpenMage
                                 </a>
                             </li>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
                                     The OpenMage Config
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
-                                    OpenMage Controller Dispatch
+                                    Controller Dispatch
                                 </a>
                             </li>
                             <li class="active" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
-                                    OpenMage Layouts, Blocks and Templates
+                                    Layouts, Blocks and Templates
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
-                                    OpenMage Models and ORM Basics
+                                    Models and ORM Basics
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
-                                    OpenMage Setup Resources
+                                    Setup Resources
                                 </a>
                             </li>
                             <li class="" role="menuitem">
@@ -261,10 +259,10 @@ <h4 class="guide-title">Developer Guide</h4>
                     <section class="page-intro">
                         <h1 class="page-heading">OpenMage Layouts, Blocks and Templates</h1>
                     </section>
-                    <p class="para1">Developers new to Magento are often confused by the Layout and View system. This
-                        article will take a look at Magento's Layout/Block approach, and show you how it fits into
-                        Magento MVC worldview.</p>
-                    <p>Unlike many popular MVC systems, Magento's Action Controller does <strong>not</strong> pass a
+                    <p class="para1">Developers new to OpenMage are often confused by the Layout and View system. This
+                        article will take a look at OpenMage's Layout/Block approach, and show you how it fits into
+                        OpenMage MVC worldview.</p>
+                    <p>Unlike many popular MVC systems, OpenMage's Action Controller does <strong>not</strong> pass a
                         data object to the view or set properties on the view object (with a few exceptions). Instead,
                         the View component directly references system models to get the information it needs for
                         display. </p>
@@ -279,23 +277,23 @@ <h2>A quick example</h2>
                     <pre>app/design/frontend/base/default/template/catalog/product/list.phtml</pre>
                     <p>You'll see the following PHP template code.</p>
                     <pre>
-                    &lt;?php $_productCollection=$this->getLoadedProductCollection() ?>
-                    &lt;?php if(!$_productCollection->count()): ?> &lt;div class="note-msg">
-                        &lt;?php echo $this->__("There are no products matching the selection.") ?>
-                    &lt;/div> &lt;?php else: ?>
-                    ...
-                    </pre>
+&lt;?php $_productCollection=$this->getLoadedProductCollection() ?>
+&lt;?php if(!$_productCollection->count()): ?> &lt;div class="note-msg">
+    &lt;?php echo $this->__("There are no products matching the selection.") ?>
+&lt;/div> &lt;?php else: ?>
+...
+</pre>
                     <p>The <tt>getLoadedProductCollection</tt> method can be found in the Template's Block class, <tt>Mage_Catalog_Block_Product_List</tt>
                         as shown:
                     <pre>File: app/code/core/Mage/Catalog/Block/Product/List.php</pre>
                     <pre>
-                    ...
-                    public function getLoadedProductCollection()
-                    {
-                        return $this->_getProductCollection();
-                    }
-                    ...
-                    </pre>
+...
+public function getLoadedProductCollection()
+{
+    return $this->_getProductCollection();
+}
+...
+</pre>
                     <p>The block's <tt>_getProductCollection</tt> then instantiates models and reads their data,
                         returning a result to the template.</p>
                     <h2>Nesting Blocks</h2>
@@ -305,25 +303,25 @@ <h2>Nesting Blocks</h2>
                         a look at the one column layout Template.</p>
                     <pre>File: app/design/frontend/base/default/template/page/1column.phtml</pre>
                     <pre>
-                    &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-                    &lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="&lt;?php echo $this->getLang() ?>" lang="&lt;?php echo $this->getLang() ?>">
-                    &lt;head>
-                    &lt;?php echo $this->getChildHtml('head') ?>
-                    &lt;/head>
-                    &lt;body class="page-popup &lt;?php echo $this->getBodyClass()?$this->getBodyClass():'' ?>">
-                        &lt;?php echo $this->getChildHtml('content') ?>
-                        &lt;?php echo $this->getChildHtml('before_body_end') ?>
-                        &lt;?php echo $this->getAbsoluteFooter() ?>
-                    &lt;/body>
-                    </pre>
+&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+&lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="&lt;?php echo $this->getLang() ?>" lang="&lt;?php echo $this->getLang() ?>">
+&lt;head>
+    &lt;?php echo $this->getChildHtml('head') ?>
+&lt;/head>
+&lt;body class="page-popup &lt;?php echo $this->getBodyClass()?$this->getBodyClass():'' ?>">
+    &lt;?php echo $this->getChildHtml('content') ?>
+    &lt;?php echo $this->getChildHtml('before_body_end') ?>
+    &lt;?php echo $this->getAbsoluteFooter() ?>
+&lt;/body>
+</pre>
                     <p>The template itself is only 28 lines long. However, each call to
                         <tt>$this->getChildHtml(...)</tt> will include and render another Block. These Blocks will, in
                         turn, use <tt>getChildHtml</tt> to render other Blocks. It's Blocks all the way down.</p>
                     <h2>The Layout</h2>
                     <p>So, Blocks and Templates are all well and good, but you're probably wondering</p>
                     <ol>
-                        <li>How do I tell Magento which Blocks I want to use on a page?</li>
-                        <li>How do I tell Magento which Block I should start rendering with?</li>
+                        <li>How do I tell OpenMage which Blocks I want to use on a page?</li>
+                        <li>How do I tell OpenMage which Block I should start rendering with?</li>
                         <li>How do I specify a particular Block in <tt>getChildHtml(...)</tt>? Those argument strings
                             don't look like Block names to me.
                         </li>
@@ -332,50 +330,50 @@ <h2>The Layout</h2>
                         define which Blocks are included on a page, and which Block(s) should kick off the rendering
                         process.</p>
                     <p><a href="mage-for-dev-3.html"
-                          title="Link to Magento for Developers: Part 3&mdash;Magento Controller Dispatch">Last time</a>
+                          title="Link to OpenMage for Developers: Part 3&mdash;OpenMage Controller Dispatch">Last time</a>
                         we were echoing content directly from our Action Methods. This time let's create a simple HTML
                         template for our Hello World module.</p>
                     <p>First, create a file at</p>
                     <pre>app/design/frontend/base/default/layout/local.xml</pre>
                     <p>with the following contents</p>
                     <pre>
-                    &lt;layout version="0.1.0">
-                        &lt;default>
-                            &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
-                        &lt;/default>
-                    &lt;/layout>
-                    </pre>
+&lt;layout version="0.1.0">
+    &lt;default>
+        &lt;block type="page/html" name="root" output="toHtml" template="OpenMagetutorial/helloworld/simple_page.phtml" />
+    &lt;/default>
+&lt;/layout>
+</pre>
                     <p>Then, create a file at </p>
-                    <pre>app/design/frontend/base/default/template/magentotutorial/helloworld/simple_page.phtml</pre>
+                    <pre>app/design/frontend/base/default/template/OpenMagetutorial/helloworld/simple_page.phtml</pre>
                     <p>with the following contents
                     <pre>
-                    &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-                            "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-                    &lt;html xmlns="http://www.w3.org/1999/xhtml">
-                    &lt;head>
-                        &lt;title>Hello World&lt;/title>
-                        &lt;style type="text/css">
-                            body {
-                                background-color:#f00;
-                            }
-                        &lt;/style>
-                    &lt;/head>
-                    &lt;body>
+&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+&lt;html xmlns="http://www.w3.org/1999/xhtml">
+&lt;head>
+    &lt;title>Hello World&lt;/title>
+    &lt;style type="text/css">
+        body {
+            background-color:#f00;
+        }
+    &lt;/style>
+&lt;/head>
+&lt;body>
 
-                    &lt;/body>
-                    &lt;/html>
-                    </pre>
+&lt;/body>
+&lt;/html>
+</pre>
                     <p>Finally, each Action Controller is responsible for kicking off the layout process. We'll need to
                         add two method calls to the Action Method.</p>
                     <pre>
-                    public function indexAction() {
-                        //remove our previous echo
-                        //echo 'Hello Index!';
-                        $this->loadLayout();
-                        $this->renderLayout();
-                    }
-                    </pre>
-                    <p>Clear your Magento cache and reload your Hello World controller page. You should now see a
+public function indexAction()
+{
+    //remove our previous echo
+    //echo 'Hello Index!';
+    $this->loadLayout();
+    $this->renderLayout();
+}
+</pre>
+                    <p>Clear your OpenMage cache and reload your Hello World controller page. You should now see a
                         website with a bright red background and an HTML source that matches what's in
                         simple_page.phtml. </p>
                     <h2>What's Going On</h2>
@@ -384,7 +382,7 @@ <h2>What's Going On</h2>
                             href="http://alanstorm.com/2005/projects/MagentoLayoutViewer.tar.gz">Layoutviewer</a>
                         module. This is a module similar to the <a
                                 href="http://alanstorm.com/2005/projects/MagentoConfigViewer.tar.gz">Configviewer</a>
-                        module you built in the Hello World article that will let us peek at some of Magento's
+                        module you built in the Hello World article that will let us peek at some of OpenMage's
                         internals.</p>
                     <p>Once you've installed the module (similar to how you setup the <a
                             href="http://alanstorm.com/2005/projects/MagentoConfigViewer.tar.gz">Configviewer</a>
@@ -392,7 +390,7 @@ <h2>What's Going On</h2>
                     <pre>http://example.com/helloworld/index/index?showLayout=page</pre>
                     <p>This is the layout xml for your page/request. It's made up of &lt;block /&gt;, &lt;reference /&gt;
                         and &lt;remove /&gt; tags. When you call the <tt>loadLayout</tt> method of your Action
-                        Controller, Magento will </p>
+                        Controller, OpenMage will </p>
                     <ol>
                         <li><p>Generate this Layout XML </p></li>
                         <li><p>Instantiate a Block class for each &lt;block /&gt; tag, looking up the class using the
@@ -401,7 +399,7 @@ <h2>What's Going On</h2>
                         <li><p>If the &lt;block /&gt; tag contains an output attribute, its value is added to the
                             internal <tt>_output</tt> array of the layout object.</p></li>
                     </ol>
-                    <p>Then, when you call the <tt>renderLayout</tt> method in your Action Controller, Magento will
+                    <p>Then, when you call the <tt>renderLayout</tt> method in your Action Controller, OpenMage will
                         iterate over all the Blocks in the <tt>_output</tt> array, using the value of the output
                         attribute as a callback method. This is always <tt>toHtml</tt>, and means the starting point for
                         output will be that Block's Template.</p>
@@ -411,34 +409,34 @@ <h2>Block Instantiation</h2>
                     <p>So, within a Layout XML file, a &lt;block /&gt; has a "type" that's actually a Grouped Class Name
                         URI</p>
                     <pre>
-                    &lt;block type="page/html" ...
-                    &lt;block type="page/template_links" ...
-                    </pre>
+&lt;block type="page/html" ...
+&lt;block type="page/template_links" ...
+</pre>
                     <p>The URI references a location in the (say it with me) global config. The first portion of the URI
                         (in the above examples <tt>page</tt>) will be used to query the global config to find the page
                         class name. The second portion of the URI (in the two examples above, <tt>html</tt> and <tt>template_links</tt>)
-                        will be appended to the base class name to create the class name Magento should instantiate.</p>
-                    <p>We'll go through <tt>page/html</tt> as an example. First, Magento looks for the global config
+                        will be appended to the base class name to create the class name OpenMage should instantiate.</p>
+                    <p>We'll go through <tt>page/html</tt> as an example. First, OpenMage looks for the global config
                         node at file</p>
                     <pre>app/code/core/Mage/Page/etc/config.xml</pre>
                     <p>and finds
                     <pre>
-                    &lt;page>
-                        &lt;class>Mage_Page_Block&lt;/class>
-                    &lt;/page>
-                    </pre>
+&lt;page>
+    &lt;class>Mage_Page_Block&lt;/class>
+&lt;/page>
+</pre>
                     <p>This gives us our base class prefix <tt>Mage_Page_Block</tt>. Then, the second part of the URI
                         (<tt>html</tt>) is appended to the class name to give us our final Block class name <tt>Mage_Page_Block_Html</tt>.
                         This is the class that will be instantiated.</p>
                     <p>If we create a block with the same name as an already existing block, the new block instance will
                         replace the original instance. This is what we've done in our local.xml file from above.</p>
                     <pre>
-                    &lt;layout version="0.1.0">
-                        &lt;default>
-                            &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
-                        &lt;/default>
-                    &lt;/layout>
-                    </pre>
+&lt;layout version="0.1.0">
+    &lt;default>
+        &lt;block type="page/html" name="root" output="toHtml" template="OpenMagetutorial/helloworld/simple_page.phtml" />
+    &lt;/default>
+&lt;/layout>
+</pre>
                     <p>The Block named <tt>root</tt> has been replaced with our Block, which points at a different phtml
                         Template file.</p>
                     <h2>Using references</h2>
@@ -446,27 +444,27 @@ <h2>Using references</h2>
                         the specified name. Contained &lt;block /&gt; nodes will be assigned as child blocks to the
                         referenced parent block.</p>
                     <pre>
-                    &lt;layout version="0.1.0">
-                        &lt;default>
-                            &lt;block type="page/html" name="root" output="toHtml" template="page/2columns-left.phtml">
-                                &lt;!-- ... sub blocks ... -->
-                            &lt;/block>
-                        &lt;/default>
-                    &lt;/layout>
-                    </pre>
+&lt;layout version="0.1.0">
+    &lt;default>
+        &lt;block type="page/html" name="root" output="toHtml" template="page/2columns-left.phtml">
+            &lt;!-- ... sub blocks ... -->
+        &lt;/block>
+    &lt;/default>
+&lt;/layout>
+</pre>
                     <p>In a different layout file:</p>
                     <pre>
-                    &lt;layout version="0.1.0">
-                        &lt;default>
-                            &lt;reference name="root">
-                                &lt;!-- ... another sub block ... -->
-                                &lt;block type="page/someothertype" name="some.other.block.name" template="path/to/some/other/template" />
-                            &lt;/reference>
-                        &lt;/default>
-                    &lt;/layout>
-                    </pre>
+&lt;layout version="0.1.0">
+    &lt;default>
+        &lt;reference name="root">
+            &lt;!-- ... another sub block ... -->
+            &lt;block type="page/someothertype" name="some.other.block.name" template="path/to/some/other/template" />
+        &lt;/reference>
+    &lt;/default>
+&lt;/layout>
+</pre>
                     <p>Even though the root block is declared in a separate layout XML file, the new block is added as a
-                        child block. Magento initially creates a <tt>page/html</tt> Block named <tt>root</tt>. Then,
+                        child block. OpenMage initially creates a <tt>page/html</tt> Block named <tt>root</tt>. Then,
                         when it later encounters the reference with the same name (<tt>root</tt>), it will assign the
                         new block <tt>some.other.block.name</tt> as a child of the root block.
                     </p>
@@ -475,7 +473,7 @@ <h2>How Layout Files are Generated</h2>
                         this XML file coming from? To answer that question, we need to introduce two new concepts;
                         Handles and the Package Layout.</p>
                     <h3>Handles</h3>
-                    <p>Each page request in Magento will generate several unique Handles. The Layoutview module can show
+                    <p>Each page request in OpenMage will generate several unique Handles. The Layoutview module can show
                         you these Handles by using a URL something like</p>
                     <pre>http://example.com/helloworld/index/index?showLayout=handles</pre>
                     <p>You should see a list similar to the following (depending on your configuration)</p>
@@ -486,20 +484,20 @@ <h3>Handles</h3>
                         <li><tt>helloworld_index_index</tt></li>
                         <li><tt>customer_logged_out</tt></li>
                     </ol>
-                    <p>Each of these is a Handle. Handles are set in a variety of places within the Magento system. The
+                    <p>Each of these is a Handle. Handles are set in a variety of places within the OpenMage system. The
                         two we want to pay attention to are <tt>default</tt> and <tt>helloworld_index_index</tt>. The
-                        <tt>default</tt> Handle is present in <strong>every</strong> request into the Magento system.
+                        <tt>default</tt> Handle is present in <strong>every</strong> request into the OpenMage system.
                         The <tt>helloworld_index_index</tt> Handle is created by combining the route name (helloworld),
                         Action Controller name (index), and Action Controller Action Method (index) into a single
                         string. This means each possible method on an Action Controller has a Handle associated with it.
                     </p>
-                    <p>Remember that "index" is the Magento default for both Action Controllers and Action Methods, so
+                    <p>Remember that "index" is the OpenMage default for both Action Controllers and Action Methods, so
                         the following request</p>
                     <pre>http://example.com/helloworld/?showLayout=handles</pre>
                     <p>Will also produce a Handle named <tt>helloworld_index_index</tt></p>
                     <h2>Package Layout</h2>
                     <p>You can think of the Package Layout similar to the global config. It's a large XML file that
-                        contains <strong>every possible layout configuration</strong> for a particular Magento install.
+                        contains <strong>every possible layout configuration</strong> for a particular OpenMage install.
                         Let's take a look at it using the Layoutview module</p>
                     <pre>http://example.com/helloworld/index/index?showLayout=package</pre>
                     <p>This may take a while to load. If your browser is choking on the XML rendering, try the text
@@ -512,141 +510,143 @@ <h2>Package Layout</h2>
                     <p>Behind the scenes there are <strong>&lt;frontend&gt;&lt;layout&gt;&lt;updates /&gt;</strong> and
                         <strong>&lt;adminhtml&gt;&lt;layout&gt;&lt;updates /&gt;</strong> sections of the global config
                         that contains nodes with all the file names to load for the respective area. Once the files
-                        listed in the config have been combined, Magento will merge in one last xml file, local.xml.
-                        This is the file where you're able to add your customizations to your Magento install. </p>
+                        listed in the config have been combined, OpenMage will merge in one last xml file, local.xml.
+                        This is the file where you're able to add your customizations to your OpenMage install. </p>
                     <h2>Combining Handles and The Package Layout</h2>
                     <p>So, if you look at the Package Layout, you'll see some familiar tags such as &lt;block /&gt; and
                         &lt;reference /&gt;, but they're all surrounded by tags that look like </p>
                     <pre>
-                    &lt;default />
-                    &lt;catalogsearch_advanced_index />
-                    etc...
-                    </pre>
+&lt;default />
+&lt;catalogsearch_advanced_index />
+etc...
+</pre>
                     <p>These are all Handle tags. The Layout for an individual request is generated by grabbing all the
                         sections of the Package Layout that match any Handles for the request. So, in our example above,
                         our layout is being generated by grabbing tags from the following sections</p>
                     <pre>
-                    &lt;default />
-                    &lt;STORE_bare_us />
-                    &lt;THEME_frontend_default_default />
-                    &lt;helloworld_index_index />
-                    &lt;customer_logged_out />
-                    </pre>
+&lt;default />
+&lt;STORE_bare_us />
+&lt;THEME_frontend_default_default />
+&lt;helloworld_index_index />
+&lt;customer_logged_out />
+</pre>
                     <p>There's one additional tag you'll need to be aware of in the Package Layout. The &lt;update /&gt;
                         tag allows you to include another Handle's tags. For example</p>
                     <pre>
-                    &lt;customer_account_index>
-                        &lt;!-- ... -->
-                        &lt;update handle="customer_account"/>
-                        &lt;!-- ... -->
-                    &lt;/customer_account_index>
-                    </pre>
+&lt;customer_account_index>
+    &lt;!-- ... -->
+    &lt;update handle="customer_account"/>
+    &lt;!-- ... -->
+&lt;/customer_account_index>
+</pre>
                     <p>Is saying that requests with a customer_account_index Handle should include &lt;blocks /&gt;s
                         from the &lt;customer_account /&gt; Handle.</p>
                     <h2>Applying What We've Learned</h2>
                     <p>OK, that's a lot of theory. Lets get back to what we did earlier. Knowing what we know now,
                         adding</p>
                     <pre>
-                    &lt;layout version="0.1.0">
-                        &lt;default>
-                            &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
-                        &lt;/default>
-                    &lt;/layout>
-                    </pre>
+&lt;layout version="0.1.0">
+    &lt;default>
+        &lt;block type="page/html" name="root" output="toHtml" template="OpenMagetutorial/helloworld/simple_page.phtml" />
+    &lt;/default>
+&lt;/layout>
+</pre>
                     <p>to <tt>local.xml</tt> means we've overridden the "root" tag. with a different Block. By placing
                         this in the &lt;default /&gt; Handle we've ensured that this override will happen for <strong>every
                             page request</strong> in the system. That's probably not what we want. </p>
-                    <p>If you go to any other page in your Magento site, you'll notice they're either blank white, or
+                    <p>If you go to any other page in your OpenMage site, you'll notice they're either blank white, or
                         have the same red background that your hello world page does. Let's change your
                         <tt>local.xml</tt> file so it only applies to the hello world page. We'll do this by changing
                         default to use the full action name handle (<tt>helloworld_index_index</tt>).</p>
                     <pre>
-                    &lt;layout version="0.1.0">
-                        &lt;helloworld_index_index>
-                            &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml" />
-                        &lt;/helloworld_index_index>
-                    &lt;/layout>
-                    </pre>
-                    <p>Clear your Magento cache, and the rest of your pages should be restored. </p>
+&lt;layout version="0.1.0">
+    &lt;helloworld_index_index>
+        &lt;block type="page/html" name="root" output="toHtml" template="OpenMagetutorial/helloworld/simple_page.phtml" />
+    &lt;/helloworld_index_index>
+&lt;/layout>
+</pre>
+                    <p>Clear your OpenMage cache, and the rest of your pages should be restored. </p>
                     <p>Right now this only applies to our index Action Method. Let's add it to the goodbye Action Method
                         as well. In your Action Controller, modify the goodbye action so it looks like</p>
                     <pre>
-                    public function goodbyeAction() {
-                        $this->loadLayout();
-                        $this->renderLayout();
-                    }
-                    </pre>
-                    <p>If you load up the following URL, you'll notice you're still getting the default Magento
+public function goodbyeAction() {
+    $this->loadLayout();
+    $this->renderLayout();
+}
+</pre>
+                    <p>If you load up the following URL, you'll notice you're still getting the default OpenMage
                         layout.</p>
                     <pre>http://example.com/helloworld/index/goodbye</pre>
                     <p>We need to add a Handle for the full action name (<tt>helloworld_index_goodbye</tt>) to our
                         local.xml file. Rather than specify a new &lt;block /&gt;, lets use the update tag to include
                         the <tt>helloworld_index_index</tt> Handle.</p>
                     <pre>
-                    &lt;layout version="0.1.0">
-                        &lt;!-- ... -->
-                        &lt;helloworld_index_goodbye>
-                            &lt;update handle="helloworld_index_index" />
-                        &lt;/helloworld_index_goodbye>
-                    &lt;/layout>
-                    </pre>
-                    <p>Loading the following pages (after clearing your Magento cache) should now produce identical
+&lt;layout version="0.1.0">
+&lt;!-- ... -->
+    &lt;helloworld_index_goodbye>
+        &lt;update handle="helloworld_index_index" />
+    &lt;/helloworld_index_goodbye>
+&lt;/layout>
+</pre>
+                    <p>Loading the following pages (after clearing your OpenMage cache) should now produce identical
                         results.</p>
-                    <pre>http://example.com/helloworld/index/index
-                    http://example.com/helloworld/index/goodbye</pre>
+                    <pre>
+http://example.com/helloworld/index/index
+http://example.com/helloworld/index/goodbye
+</pre>
                     <h2>Starting Output and getChildHtml</h2>
                     <p>In a standard configuration, output starts on the Block named root (because it has an output
                         attribute). We've overridden root's Template with our own</p>
-                    <pre>template="magentotutorial/helloworld/simple_page.phtml"</pre>
+                    <pre>template="OpenMagetutorial/helloworld/simple_page.phtml"</pre>
                     <p>Templates are referenced from the root folder of the current theme. In this case, that's</p>
                     <pre>app/design/frontend/base/default</pre>
-                    <p>so we need to drill down to our custom page. Most Magento Templates are stored in </p>
+                    <p>so we need to drill down to our custom page. Most OpenMage Templates are stored in </p>
                     <pre>app/design/frontend/base/default/templates</pre>
                     <p>Combining this gives us the full path</p>
-                    <pre>app/design/frontend/base/default/templates/magentotutorial/helloworld/simple_page.phtml</pre>
+                    <pre>app/design/frontend/base/default/templates/OpenMagetutorial/helloworld/simple_page.phtml</pre>
                     <h2>Adding Content Blocks</h2>
                     <p>A simple red page is pretty boring. Let's add some content to this page. Change your <tt>&lt;helloworld_index_index
                         /&gt;</tt> Handle in local.xml so it looks like the following</p>
                     <pre>
-                    &lt;helloworld_index_index>
-                        &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml">
-                            &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
-                        &lt;/block>
-                    &lt;/helloworld_index_index>
-                    </pre>
-                    <p>We're adding a new Block nested within our root. This is a Block that's distributed with Magento,
+&lt;helloworld_index_index>
+    &lt;block type="page/html" name="root" output="toHtml" template="OpenMagetutorial/helloworld/simple_page.phtml">
+        &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
+    &lt;/block>
+&lt;/helloworld_index_index>
+</pre>
+                    <p>We're adding a new Block nested within our root. This is a Block that's distributed with OpenMage,
                         and will display a customer registration form. By nesting this Block within our root Block,
                         we've made it available to be pulled into our <tt>simple_page.html</tt> Template. Next, we'll
                         use the Block's getChildHtml method in our <tt>simple_page.phtml</tt> file. Edit <tt>simple_page.html</tt>
                         so it looks like this</p>
                     <pre>
-                    &lt;body>
-                        &lt;?php echo $this->getChildHtml('customer_form_register'); ?>
-                    &lt;/body>
-                    </pre>
-                    <p>Clear your Magento cache and reload the page and you should see the customer registration form on
-                        your red background. Magento also has a Block named top.links. Let's try including that. Change
+&lt;body>
+    &lt;?php echo $this->getChildHtml('customer_form_register'); ?>
+&lt;/body>
+</pre>
+                    <p>Clear your OpenMage cache and reload the page and you should see the customer registration form on
+                        your red background. OpenMage also has a Block named top.links. Let's try including that. Change
                         your simple_page.html file so it reads</p>
                     <pre>
-                    &lt;body>
-                        &lt;h1>Links&lt;/h1>
-                        &lt;?php echo $this->getChildHtml('top.links'); ?>
-                    &lt;/body>
-                    </pre>
+&lt;body>
+    &lt;h1>Links&lt;/h1>
+    &lt;?php echo $this->getChildHtml('top.links'); ?>
+&lt;/body>
+</pre>
                     <p>When you reload the page, you'll notice that your &lt;h1&gt;Links&lt;/h1&gt; title is rendering,
                         but nothing is rendering for top.links. That's because we didn't add it to local.xml. The <tt>getChildHtml</tt>
                         method can only include Blocks that are specified as sub-Blocks in the Layout. This allows
-                        Magento to only instantiate the Blocks it needs, and also allows you to set difference Templates
+                        OpenMage to only instantiate the Blocks it needs, and also allows you to set difference Templates
                         for Blocks based on context.</p>
                     <p>Let's add the top.links Block to our local.xml</p>
                     <pre>
-                    &lt;helloworld_index_index>
-                        &lt;block type="page/html" name="root" output="toHtml" template="magentotutorial/helloworld/simple_page.phtml">
-                            &lt;block type="page/template_links" name="top.links"/>
-                            &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
-                        &lt;/block>
-                    &lt;/helloworld_index_index>
-                    </pre>
+&lt;helloworld_index_index>
+    &lt;block type="page/html" name="root" output="toHtml" template="OpenMagetutorial/helloworld/simple_page.phtml">
+        &lt;block type="page/template_links" name="top.links"/>
+        &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
+    &lt;/block>
+&lt;/helloworld_index_index>
+</pre>
                     <p>Clear your cache and reload the page. You should now see the top.links module. </p>
                     <h2>Time for action</h2>
                     <p>There is one more important concept to cover before we wrap up this lesson, and that is the &lt;action
@@ -654,18 +654,18 @@ <h2>Time for action</h2>
                         classes. So instead of changing the template of the root block by replacing the block instance
                         with our own, we can use a call to <tt>setTemplate</tt> instead.</p>
                     <pre>
-                    &lt;layout version="0.1.0">
-                        &lt;helloworld_index_index>
-                            &lt;reference name="root">
-                                &lt;action method="setTemplate">
-                                    &lt;template>magentotutorial/helloworld/simple_page.phtml&lt;/template>
-                                &lt;/action>
-                                &lt;block type="page/template_links" name="top.links"/>
-                                &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
-                            &lt;/reference>
-                        &lt;/helloworld_index_index>
-                    &lt;/layout>
-                    </pre>
+&lt;layout version="0.1.0">
+    &lt;helloworld_index_index>
+        &lt;reference name="root">
+            &lt;action method="setTemplate">
+                &lt;template>OpenMagetutorial/helloworld/simple_page.phtml&lt;/template>
+            &lt;/action>
+            &lt;block type="page/template_links" name="top.links"/>
+            &lt;block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml"/>
+        &lt;/reference>
+    &lt;/helloworld_index_index>
+&lt;/layout>
+</pre>
                     <p>This layout XML will first set the template property of the root block, and then will add the two
                         blocks we use as child blocks. Once we clear the cache, the result should look just as before.
                         The benefit of using the &lt;action /&gt; is the same block instance is used that was created
@@ -676,20 +676,20 @@ <h2>Time for action</h2>
                         written the action node from the previous example as follows with the same effect.
                     </p>
                     <pre>
-                    &lt;action method="setTemplate">
-                        &lt;some_new_template>magentotutorial/helloworld/simple_page.phtml&lt;/some_new_template>
-                    &lt;/action>
-                    </pre>
+&lt;action method="setTemplate">
+    &lt;some_new_template>OpenMagetutorial/helloworld/simple_page.phtml&lt;/some_new_template>
+&lt;/action>
+</pre>
                     <p>This is just to illustrate that the action's argument node names are arbitrary.</p>
                     <h2>Wrapup</h2>
                     <p>That covers Layout fundamentals. We have covered the tags &lt;block /&gt;, &lt;reference /&gt;,
                         &lt;update /&gt; and &lt;action /&gt;, and also layout update handles like &lt;default /&gt; and
-                        &lt;cms_index_index /&gt;. These make up most of the layout configuration used in Magento. If
+                        &lt;cms_index_index /&gt;. These make up most of the layout configuration used in OpenMage. If
                         you found it somewhat daunting, don't worry, you'll rarely need to work with layouts on such a
-                        fundamental level. Magento provides a number of pre-built layouts which can be modified and
+                        fundamental level. OpenMage provides a number of pre-built layouts which can be modified and
                         skinned to meet the needs of your store. Understanding how the entire Layout system works can be
                         a great help when you're trouble shooting Layout issues, or adding new functionality to an
-                        existing Magento system.</p>
+                        existing OpenMage system.</p>
                 </div>
                 <!-- /.content-wrap -->
                 <div class="page-info">
diff --git a/guides/m1x/magefordev/mage-for-dev-5.html b/guides/m1x/magefordev/mage-for-dev-5.html
index 8738ed8fe9..9354f1c7ae 100644
--- a/guides/m1x/magefordev/mage-for-dev-5.html
+++ b/guides/m1x/magefordev/mage-for-dev-5.html
@@ -31,8 +31,6 @@
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
-<!-- magento-for-dev-part-1-introduction-to-magento -->
 <body class="layout-default">
 <header class="site-header">
     <nav class="site-nav">
@@ -65,7 +63,7 @@
                         }</style>
                     </defs>
                     <g class="layer">
-                        <title>OpenMage Magento</title>
+                        <title>OpenMage</title>
                         <path class="ba"
                               d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
                         <text class="bb" id="svg_2" x="0" y="47">
@@ -135,7 +133,7 @@
                                 <div class="nav-section-title">API</div>
                                 <ul>
                                     <li class=" " role="menuitem">
-                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                        <a href="/guides/v19.x/">Get Started with OpenMage Web APIs</a>
                                     </li>
                                     <li class=" " role="menuitem">
                                         <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
@@ -210,34 +208,34 @@
                     <h4 class="guide-title">Developer Guide</h4>
                     <div class="collapsible-navigation">
                         <ul>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
                                     Introduction to OpenMage
                                 </a>
                             </li>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
                                     The OpenMage Config
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
-                                    OpenMage Controller Dispatch
+                                    Controller Dispatch
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
-                                    OpenMage Layouts, Blocks and Templates
+                                    Layouts, Blocks and Templates
                                 </a>
                             </li>
                             <li class="active" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
-                                    OpenMage Models and ORM Basics
+                                    Models and ORM Basics
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
-                                    OpenMage Setup Resources
+                                    Setup Resources
                                 </a>
                             </li>
                             <li class="" role="menuitem">
@@ -262,7 +260,7 @@ <h4 class="guide-title">Developer Guide</h4>
                         <h1 class="page-heading">OpenMage Layouts, Blocks and Templates</h1>
                     </section>
                     <p class="para1">The implementation of a "Models Tier" is a huge part of any MVC framework. It
-                        represents the data of your application, and most applications are useless without data. Magento
+                        represents the data of your application, and most applications are useless without data. OpenMage
                         Models play an even bigger role, as they typically contain the "Business Logic" that's often
                         relegated to the Controller or Helper methods in other PHP MVC frameworks.</p>
                     <h2>Traditional PHP MVC Models</h2>
@@ -283,39 +281,39 @@ <h2>Traditional PHP MVC Models</h2>
                     <p>This definition of ORM should suffice for now, but like everything Computer Science these days,
                         the strict definition of ORM has blurred over the years. It's beyond the scope of this article
                         to settle that dispute, but suffice it say we're generalizing a bit.</p>
-                    <h2>Magento Models</h2>
-                    <p>It should be no surprise that Magento takes the ORM approach. While the Zend Framework SQL
-                        abstractions are available, most of your data access will be via the built in Magento Models,
-                        and Models you build yourself. It should also come as no surprise that Magento has a highly
+                    <h2>OpenMage Models</h2>
+                    <p>It should be no surprise that OpenMage takes the ORM approach. While the Zend Framework SQL
+                        abstractions are available, most of your data access will be via the built in OpenMage Models,
+                        and Models you build yourself. It should also come as no surprise that OpenMage has a highly
                         flexible, highly abstract, concept of what a Model is.</p>
-                    <h3>Anatomy of a Magento Model</h3>
-                    <p>Most Magento Models can be categorized in one of two ways. There's a basic,
+                    <h3>Anatomy of a OpenMage Model</h3>
+                    <p>Most OpenMage Models can be categorized in one of two ways. There's a basic,
                         ActiveRecord-like/one-object-one-table Model, and there's also an Entity Attribute Value (EAV)
                         Model. Each Model also gets a Model Collection. Collections are PHP objects used to hold a
-                        number of individual Magento Model instances. The Magento team has implemented the PHP Standard
+                        number of individual OpenMage Model instances. The OpenMage team has implemented the PHP Standard
                         Library interfaces of IteratorAggregate and Countable to allow each Model type to have it's own
                         collection type. If you're not familiar with the PHP Standard Library, think of Model
                         Collections as arrays that also have methods attached.</p>
-                    <p>Magento Models don't contain any code for connecting to the database. Instead, each Model uses a
+                    <p>OpenMage Models don't contain any code for connecting to the database. Instead, each Model uses a
                         <tt>modelResource</tt> class, that is used to communicate with the database server (via one read
                         and one write adapter object). By decoupling the logical Model and the code that talks to the
                         database, it's theoretically possible to write new resource classes for a different database
                         schemas and platforms while keeping your Models themselves untouched. </p>
                     <h2>Enable developer mode</h2>
                     <p>Something you should do in development&mdash;but <em>never</em> in production&mdash;is to enable
-                        Magento's <em>developer mode</em> which, among other things, displays exceptions in your
+                        OpenMage's <em>developer mode</em> which, among other things, displays exceptions in your
                         browser. It's useful for debugging your code.</p>
                     <p>Enable developer mode in any of the following ways:</p>
                     <ul>
                         <li>
-                            <a href="https://magento2.atlassian.net/wiki/display/m1wiki/How+to+Configure+a+Magento+1.x+Error+Page#display_errors_on_the_same_page_developer_mode">developer
+                            <a href="https://alanastorm.com/magento_log_and_developer_mode/">developer
                                 mode</a></li>
-                        <li>Edit the <code>.htaccess</code> in the Magento root directory file to add <code>SetEnv
+                        <li>Edit the <code>.htaccess</code> in the OpenMage root directory file to add <code>SetEnv
                             MAGE_IS_DEVELOPER_MODE "true"</code>
                         </li>
                     </ul>
                     <h2>Creating a Basic Model</h2>
-                    <p>To begin, we're going to create a basic Magento Model. PHP MVC tradition insists we model a
+                    <p>To begin, we're going to create a basic OpenMage Model. PHP MVC tradition insists we model a
                         weblog post. The steps we'll need to take are</p>
                     <ol>
                         <li>Create a new "Weblog" module</li>
@@ -332,48 +330,49 @@ <h3>Create a Weblog Module</h3>
                     <p>You should be an old hat at creating empty modules at this point, so we'll skip the details and
                         assume you can create an empty module named Weblog. After you've done that, we'll setup a route
                         for an index Action Controller with an action named "testModel". As always, the following
-                        examples assume a Package Name of "Magentotutorial".</p>
-                    <p>In `Magentotutorial/Weblog/etc/config.xml`, setup the following route</p>
+                        examples assume a Package Name of "OpenMagetutorial".</p>
+                    <p>In `OpenMagetutorial/Weblog/etc/config.xml`, setup the following route</p>
                     <pre>
-                    &lt;frontend>
-                        &lt;routers>
-                            &lt;weblog>
-                                &lt;use>standard&lt;/use>
-                                &lt;args>
-                                    &lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;
-                                    &lt;frontName>weblog&lt;/frontName>
-                                &lt;/args>
-                            &lt;/weblog>
-                        &lt;/routers>
-                    &lt;/frontend>
-                    </pre>
+&lt;frontend>
+    &lt;routers>
+        &lt;weblog>
+            &lt;use>standard&lt;/use>
+            &lt;args>
+                &lt;module&gt;OpenMagetutorial_Weblog&lt;/module&gt;
+                &lt;frontName>weblog&lt;/frontName>
+            &lt;/args>
+        &lt;/weblog>
+    &lt;/routers>
+&lt;/frontend>
+</pre>
                     <p>And then add the following Action Controller in </p>
                     <pre>
-                    class Magentotutorial_Weblog_IndexController extends Mage_Core_Controller_Front_Action {
-                        public function testModelAction() {
-                            echo 'Setup!';
-                        }
-                    }
-                    </pre>
-                    <p>at <tt>Magentotutorial/Weblog/controllers/IndexController.php</tt>. Clear your Magento cache and
+class OpenMagetutorial_Weblog_IndexController extends Mage_Core_Controller_Front_Action
+{
+    public function testModelAction() {
+        echo 'Setup!';
+    }
+}
+</pre>
+                    <p>at <tt>OpenMagetutorial/Weblog/controllers/IndexController.php</tt>. Clear your OpenMage cache and
                         load the following URL to ensure everything's been setup correctly.</p>
                     <pre>http://example.com/weblog/index/testModel</pre>
                     <p>You should see the word "Setup" on a white background.</p>
                     <h3>Creating the Database Table</h3>
-                    <p>Magento has a system for automatically creating and changing your database schemas, but for the
+                    <p>OpenMage has a system for automatically creating and changing your database schemas, but for the
                         time being we'll just manually create a table for our Model.</p>
                     <p>Using the command-line or your favorite MySQL GUI application, create a table with the following
                         schema</p>
                     <pre>
-                    CREATE TABLE `blog_posts` (
-                      `blogpost_id` int(11) NOT NULL auto_increment,
-                      `title` text,
-                      `post` text,
-                      `date` datetime default NULL,
-                      `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
-                      PRIMARY KEY  (`blogpost_id`)
-                    )
-                    </pre>
+CREATE TABLE `blog_posts` (
+ `blogpost_id` int(11) NOT NULL auto_increment,
+ `title` text,
+ `post` text,
+ `date` datetime default NULL,
+ `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
+ PRIMARY KEY  (`blogpost_id`)
+)
+</pre>
                     <p>And then populate it with some data </p>
                     <pre>INSERT INTO `blog_posts` VALUES (1,'My New Title','This is a blog post','2010-07-01 00:00:00','2010-07-02 23:12:30');</pre>
                     <h3>The Global Config and Creating The Model</h3>
@@ -383,7 +382,7 @@ <h3>The Global Config and Creating The Model</h3>
                         <li>Enabling Model Resources in our Module</li>
                         <li>Add an "entity" table configuration to our Model Resource.</li>
                     </ol>
-                    <p>When you instantiate a Model in Magento, you make a call like this</p>
+                    <p>When you instantiate a Model in OpenMage, you make a call like this</p>
                     <pre>$model = Mage::getModel('weblog/blogpost');</pre>
                     <p>The first part of the URI you pass into get Model is the <a
                             href="http://alanstorm.com/2009/img/magento-book/weblogGetModel.png">Model Group Name</a>.
@@ -392,55 +391,51 @@ <h3>The Global Config and Creating The Model</h3>
                         lowercase). The second part of the URI is the lowercase version of your Model name.</p>
                     <p>So, let's add the following XML to our module's `config.xml`.</p>
                     <pre>
-                    &lt;global>
-                        &lt;!-- ... -->
-                        &lt;models>
-                            &lt;weblog>
-                                &lt;class>Magentotutorial_Weblog_Model&lt;/class>
-                                &lt;!--
-                                need to create our own resource, can't just
-                                use core_resource
-                                -->
-                                &lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;
-                            &lt;/weblog>
-                        &lt;/models>
-                        &lt;!-- ... -->
-                    &lt;/global>
-                    </pre>
+&lt;global>
+    &lt;!-- ... -->
+    &lt;models>
+        &lt;weblog>
+            &lt;class>OpenMagetutorial_Weblog_Model&lt;/class>
+            &lt;!--
+            need to create our own resource, can't just
+            use core_resource
+            -->
+            &lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;
+        &lt;/weblog>
+    &lt;/models>
+    &lt;!-- ... -->
+&lt;/global>
+</pre>
                     <p>The outer &lt;weblog /&gt; tag is your Group Name, which should match your module name. &lt;class
                         /&gt; is the BASE name all Models in the weblog group will have, also called <strong>Class
                             Prefix</strong>. The &lt;resourceModel /&gt; tag indicates which Resource Model that weblog
                         group Models should use. We talk more about this later on in this page. For now, remember your
                         Group Name and the literal string "resource".</p>
-                    <p>So, we're not done yet, but let's see what happens if we clear our Magento cache and attempt to
+                    <p>So, we're not done yet, but let's see what happens if we clear our OpenMage cache and attempt to
                         instantiate a blogpost Model. In your `testModelAction` method, use the following code</p>
                     <pre>
-                        public function testModelAction() {
-                            $blogpost = Mage::getModel('weblog/blogpost');
-                            echo get_class($blogpost);
-                        }
-                    </pre>
+public function testModelAction() {
+    $blogpost = Mage::getModel('weblog/blogpost');
+    echo get_class($blogpost);
+}
+</pre>
                     <p>and reload your page. You should see an error like the following:</p>
-                    <pre>
-                    include(Magentotutorial/Weblog/Model/Blogpost.php) [function.include]: failed to open stream: No such file or directory
-                    </pre>
-                    <p>By attempting to retrieve a <tt>weblog/blogpost</tt> Model, you told Magento to instantiate a
+                    <pre>include(OpenMagetutorial/Weblog/Model/Blogpost.php) [function.include]: failed to open stream: No such file or directory</pre>
+                    <p>By attempting to retrieve a <tt>weblog/blogpost</tt> Model, you told OpenMage to instantiate a
                         class with the name</p>
-                    <pre>
-                    Magentotutorial_Weblog_Model_Blogpost
-                    </pre>
-                    <p>Magento is trying to __autoload include this Model, but can't find the file. Let's create it!
+                    <pre>OpenMagetutorial_Weblog_Model_Blogpost</pre>
+                    <p>OpenMage is trying to __autoload include this Model, but can't find the file. Let's create it!
                         Create the following class at the following location</p>
-                    <pre>File: app/code/local/Magentotutorial/Weblog/Model/Blogpost.php</pre>
+                    <pre>File: app/code/local/OpenMagetutorial/Weblog/Model/Blogpost.php</pre>
                     <pre>
-                    class Magentotutorial_Weblog_Model_Blogpost extends Mage_Core_Model_Abstract
-                    {
-                        protected function _construct()
-                        {
-                            $this->_init('weblog/blogpost');
-                        }
-                    }
-                    </pre>
+class OpenMagetutorial_Weblog_Model_Blogpost extends Mage_Core_Model_Abstract
+{
+    protected function _construct()
+    {
+        $this->_init('weblog/blogpost');
+    }
+}
+</pre>
                     <p>Reload your page, and the exception should be replaced with the name of your class. </p>
                     <p>All basic Models that interact with the database should extend the
                         <tt>Mage_Core_Model_Abstract</tt> class. This abstract class forces you to implement a single
@@ -451,140 +446,132 @@ <h3>The Global Config and Resources</h3>
                     <p>So, we've setup our Model. Next, we need to setup our Model Resource. Model Resources contain the
                         code that actually talks to our database. In the last section, we included the following in our
                         config.</p>
-                    <pre>
-                    &lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;
-                    </pre>
+                    <pre>&lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;</pre>
                     <p>The value in &lt;resourceModel /&gt; will be used to instantiate a Model Resource class. Although
                         you'll never need to call it yourself, when any Model in the weblog group needs to talk to the
-                        database, Magento will make the following method call to get the Model resource</p>
-                    <pre>
-                    Mage::getResourceModel('weblog/blogpost');
-                    </pre>
+                        database, OpenMage will make the following method call to get the Model resource</p>
+                    <pre>Mage::getResourceModel('weblog/blogpost');</pre>
                     <p>Again, weblog is the Group Name, and blogpost is the Model. The <tt>Mage::getResourceModel</tt>
                         method will use the <tt>weblog/blogpost</tt> URI to inspect the global config and pull out the
                         value in &lt;resourceModel&gt; (in this case, <tt>weblog_resource</tt>). Then, a model class
                         will be instantiated with the following URI</p>
-                    <pre>
-                    weblog_resource/blogpost
-                    </pre>
+                    <pre>weblog_resource/blogpost</pre>
                     <p>So, if you followed that all the way, what this means is, <strong>resource models are configured
                         in the same section of the XML config as normal Models</strong>. This can be confusing to
                         newcomers and old-hands alike.</p>
                     <p>So, with that in mind, let's configure our resource. In our &lt;models&gt; section add</p>
                     <pre>
-                    &lt;global>
-                        &lt;!-- ... -->
-                        &lt;models>
-                            &lt;!-- ... -->
-                            &lt;weblog_resource>
-                                &lt;class>Magentotutorial_Weblog_Model_Resource&lt;/class>
-                            &lt;/weblog_resource>
-                        &lt;/models>
-                    &lt;/global>
-                    </pre>
+&lt;global>
+    &lt;!-- ... -->
+    &lt;models>
+        &lt;!-- ... -->
+        &lt;weblog_resource>
+            &lt;class>OpenMagetutorial_Weblog_Model_Resource&lt;/class>
+        &lt;/weblog_resource>
+    &lt;/models>
+&lt;/global>
+</pre>
                     <p>You're adding the &lt;weblog_resource /&gt; tag, which is the value of the &lt;resourceModel /&gt;
                         tag you just setup. The value of &lt;class /&gt; is the base name that all your resource models
                         will have, and should be named with the following format</p>
-                    <pre>
-                    Packagename_Modulename_Model_Resource
-                    </pre>
+                    <pre>Packagename_Modulename_Model_Resource</pre>
                     <p>So, we have a configured resource, let's try loading up some Model data. Change your action to
                         look like the following</p>
                     <pre>
-                    public function testModelAction() {
-                        $params = $this->getRequest()->getParams();
-                        $blogpost = Mage::getModel('weblog/blogpost');
-                        echo("Loading the blogpost with an ID of ".$params['id']);
-                        $blogpost->load($params['id']);
-                        $data = $blogpost->getData();
-                        var_dump($data);
-                    }
-                    </pre>
-                    <p>And then load the following URL in your browser (after clearing your Magento cache)</p>
+public function testModelAction() {
+    $params = $this->getRequest()->getParams();
+    $blogpost = Mage::getModel('weblog/blogpost');
+    echo("Loading the blogpost with an ID of ".$params['id']);
+    $blogpost->load($params['id']);
+    $data = $blogpost->getData();
+    var_dump($data);
+}
+</pre>
+                    <p>And then load the following URL in your browser (after clearing your OpenMage cache)</p>
                     <pre>http://example.com/weblog/index/testModel/id/1</pre>
                     <p>You should see an exception something like the following</p>
-                    <pre>Warning: include(Magentotutorial/Weblog/Model/Resource/Blogpost.php) [function.include]: failed to open stream: No such file ....</pre>
+                    <pre>Warning: include(OpenMagetutorial/Weblog/Model/Resource/Blogpost.php) [function.include]: failed to open stream: No such file ....</pre>
                     <p>As you've likely intuited, we need to add a resource class for our Model. <strong>Every</strong>
                         Model has its own resource class. Add the following class at the following location</p>
-                    <pre>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Blogpost.php</pre>
+                    <pre>File: app/code/local/OpenMagetutorial/Weblog/Model/Resource/Blogpost.php</pre>
                     <pre>
-                    class Magentotutorial_Weblog_Model_Resource_Blogpost extends Mage_Core_Model_Resource_Db_Abstract{
-                        protected function _construct()
-                        {
-                            $this->_init('weblog/blogpost', 'blogpost_id');
-                        }
-                    }
-                    </pre>
+class OpenMagetutorial_Weblog_Model_Resource_Blogpost extends Mage_Core_Model_Resource_Db_Abstract{
+    protected function _construct()
+    {
+        $this->_init('weblog/blogpost', 'blogpost_id');
+    }
+}
+</pre>
                     <p>Again, the first parameter of the init method is the URL used to identify the
                         <strong>Model</strong>. The second parameter is the database field that uniquely identifies any
                         particular column. In most cases, this should be the primary key. Clear your cache, reload, and
                         you should see</p>
                     <pre>Can't retrieve entity config: weblog/blogpost</pre>
-                    <p>Another exception! When we use the Model URI <tt>weblog/blogpost</tt>, we're telling Magento we
+                    <p>Another exception! When we use the Model URI <tt>weblog/blogpost</tt>, we're telling OpenMage we
                         want the Model Group <tt>weblog</tt>, and the <tt>blogpost</tt> <em>Entity</em>. In the context
                         of simple Models that extend <tt>Mage_Core_Model_Resource_Db_Abstract</tt>, an entity
                         corresponds to a table. In this case, the table named <tt>blog_post</tt> that we created above.
                         Let's add that entity to our XML config.</p>
                     <pre>
-                        &lt;models>
-                            &lt;!-- ... --->
-                            &lt;weblog_resource>
-                                &lt;class>Magentotutorial_Weblog_Model_Resource&lt;/class>
-                                &lt;entities>
-                                    &lt;blogpost>
-                                        &lt;table>blog_posts&lt;/table>
-                                    &lt;/blogpost>
-                                &lt;/entities>
-                            &lt;/weblog_resource>
-                        &lt;/models>
-                    </pre>
+&lt;models>
+    &lt;!-- ... --->
+    &lt;weblog_resource>
+        &lt;class>OpenMagetutorial_Weblog_Model_Resource&lt;/class>
+        &lt;entities>
+            &lt;blogpost>
+                &lt;table>blog_posts&lt;/table>
+            &lt;/blogpost>
+        &lt;/entities>
+    &lt;/weblog_resource>
+&lt;/models>
+</pre>
                     <p>We've added a new &lt;entities /&gt; section to the resource Model section of our config. This,
                         in turn, has a section named after our entity (&lt;blogpost /&gt;) that specifies the name of
                         the database table we want to use for this Model.</p>
-                    <p>Clear your Magento cache, cross your fingers, reload the page and ...</p>
+                    <p>Clear your OpenMage cache, cross your fingers, reload the page and ...</p>
                     <pre>Loading the blogpost with an ID of 1
 
-                    array
-                      'blogpost_id' => string '1' (length=1)
-                      'title' => string 'My New Title' (length=12)
-                      'post' => string 'This is a blog post' (length=19)
-                      'date' => string '2009-07-01 00:00:00' (length=19)
-                      'timestamp' => string '2009-07-02 16:12:30' (length=19)
-                    </pre>
-                    <p>Eureka! We've managed to extract our data and, more importantly, completely configure a Magento
+array
+ 'blogpost_id' => string '1' (length=1)
+ 'title' => string 'My New Title' (length=12)
+ 'post' => string 'This is a blog post' (length=19)
+ 'date' => string '2009-07-01 00:00:00' (length=19)
+ 'timestamp' => string '2009-07-02 16:12:30' (length=19)
+</pre>
+                    <p>Eureka! We've managed to extract our data and, more importantly, completely configure a OpenMage
                         Model.</p>
                     <h2>Basic Model Operations</h2>
-                    <p>All Magento Models inherit from the Varien_Object class. This class is part of the Magento system
-                        library and <strong>not</strong> part of any Magento core module. You can find this object at
+                    <p>All OpenMage Models inherit from the Varien_Object class. This class is part of the OpenMage system
+                        library and <strong>not</strong> part of any OpenMage core module. You can find this object at
                     </p>
                     <pre>lib/Varien/Object.php</pre>
-                    <p>Magento Models store their data in a protected _data property. The Varien_Object class gives us
+                    <p>OpenMage Models store their data in a protected _data property. The Varien_Object class gives us
                         several methods we can use to extract this data. You've already seen <tt>getData</tt>, which
                         will return an array of key/value pairs. This method can also be passed a string key to get a
                         specific field.</p>
                     <pre>
-                    $model->getData();
-                    $model->getData('title');
-                    </pre>
+$model->getData();
+$model->getData('title');
+</pre>
                     <p>There's also a getOrigData method, which will return the Model data as it was when the object was
                         initially populated, (working with the protected _origData method).</p>
                     <pre>
-                    $model->getOrigData();
-                    $model->getOrigData('title');
-                    </pre>
+$model->getOrigData();
+$model->getOrigData('title');
+</pre>
                     <p>The Varien_Object also implements some special methods via PHP's magic <tt>__call</tt> method.
                         You can get, set, unset, or check for the existence of any property using a method that begins
                         with the word get, set, unset or has and is followed by the camel cased name of a property.</p>
                     <pre>
-                    $model->getBlogpostId();
-                    $model->setBlogpostId(25);
-                    $model->unsBlogpostId();
-                    if($model->hasBlogpostId()){...}
-                    </pre>
+$model->getBlogpostId();
+$model->setBlogpostId(25);
+$model->unsBlogpostId();
+if($model->hasBlogpostId()){...}
+</pre>
                     <p>For this reason, you'll want to name all your database columns with lower case characters and use
                         underscores to separate characters. </p>
-                    <h2>CRUD, the Magento Way</h2>
-                    <p>Magento Models support the basic Create, Read, Update, and Delete functionality of CRUD with <tt>load</tt>,
+                    <h2>CRUD, the OpenMage Way</h2>
+                    <p>OpenMage Models support the basic Create, Read, Update, and Delete functionality of CRUD with <tt>load</tt>,
                         <tt>save</tt>, and <tt>delete</tt> methods. You've already seen the load method in action. When
                         passed a single parameter, the load method will return a record whose id field (set in the
                         Model's resource) matches the passed in value.</p>
@@ -592,82 +579,80 @@ <h2>CRUD, the Magento Way</h2>
                     <p>The save method will allow you to both INSERT a new Model into the database, or UPDATE an
                         existing one. Add the following method to your Controller</p>
                     <pre>
-                    public function createNewPostAction() {
-                        $blogpost = Mage::getModel('weblog/blogpost');
-                        $blogpost->setTitle('Code Post!');
-                        $blogpost->setPost('This post was created from code!');
-                        $blogpost->save();
-                        echo 'post with ID ' . $blogpost->getId() . ' created';
-                    }
-                    </pre>
+public function createNewPostAction() {
+    $blogpost = Mage::getModel('weblog/blogpost');
+    $blogpost->setTitle('Code Post!');
+    $blogpost->setPost('This post was created from code!');
+    $blogpost->save();
+    echo 'post with ID ' . $blogpost->getId() . ' created';
+}
+</pre>
                     <p>and then execute your Controller Action by loading the following URL</p>
                     <pre>http://example.com/weblog/index/createNewPost</pre>
                     <p>You should now see an additional saved post in your database table. Next, try the following to
                         edit your post</p>
                     <pre>
-                    public function editFirstPostAction() {
-                        $blogpost = Mage::getModel('weblog/blogpost');
-                        $blogpost->load(1);
-                        $blogpost->setTitle("The First post!");
-                        $blogpost->save();
-                        echo 'post edited';
-                    }
-                    </pre>
+public function editFirstPostAction() {
+    $blogpost = Mage::getModel('weblog/blogpost');
+    $blogpost->load(1);
+    $blogpost->setTitle("The First post!");
+    $blogpost->save();
+    echo 'post edited';
+}
+</pre>
                     <p>And finally, you can delete your post using very similar syntax.</p>
                     <pre>
-                    public function deleteFirstPostAction() {
-                        $blogpost = Mage::getModel('weblog/blogpost');
-                        $blogpost->load(1);
-                        $blogpost->delete();
-                        echo 'post removed';
-                    }
-                    </pre>
+public function deleteFirstPostAction() {
+    $blogpost = Mage::getModel('weblog/blogpost');
+    $blogpost->load(1);
+    $blogpost->delete();
+    echo 'post removed';
+}
+</pre>
                     <h2>Model Collections</h2>
                     <p>So, having a single Model is useful, but sometimes we want to grab list of Models. Rather than
-                        returning a simple array of Models, each Magento Model type has a unique collection object
+                        returning a simple array of Models, each OpenMage Model type has a unique collection object
                         associated with it. These objects implement the PHP IteratorAggregate and Countable interfaces,
                         which means they can be passed to the <tt>count</tt> function, and used in <tt>for each</tt>
                         constructs.</p>
                     <p>We'll cover Collections in full in a later article, but for now let's look at basic setup and
                         usage. Add the following action method to your Controller, and load it in your browser.</p>
                     <pre>
-                    public function showAllBlogPostsAction() {
-                        $posts = Mage::getModel('weblog/blogpost')->getCollection();
-                        foreach($posts as $blogpost){
-                            echo '&lt;h3>'.$blogpost->getTitle().'&lt;/h3>';
-                            echo nl2br($blogpost->getPost());
-                        }
-                    }
-                    </pre>
+public function showAllBlogPostsAction() {
+    $posts = Mage::getModel('weblog/blogpost')->getCollection();
+    foreach($posts as $blogpost){
+        echo '&lt;h3>'.$blogpost->getTitle().'&lt;/h3>';
+        echo nl2br($blogpost->getPost());
+    }
+}
+</pre>
                     <p>Load the action URL, </p>
                     <pre>http://example.com/weblog/index/showAllBlogPosts</pre>
                     <p>and you should see a (by now) familiar exception.</p>
-                    <pre>Warning: include(Magentotutorial/Weblog/Model/Resource/Blogpost/Collection.php) [function.include]: failed to open stream</pre>
+                    <pre>Warning: include(OpenMagetutorial/Weblog/Model/Resource/Blogpost/Collection.php) [function.include]: failed to open stream</pre>
                     <p>You're not surprised, are you? We need to add a PHP class file that defines our Blogpost
                         collection. Every Model has a protected property named <tt>_resourceCollectionName</tt> that
                         contains a URI that's used to identify our collection.</p>
-                    <pre>
-                      protected '_resourceCollectionName' =&gt; string 'weblog/blogpost_collection'
-                    </pre>
+                    <pre>protected '_resourceCollectionName' =&gt; string 'weblog/blogpost_collection'</pre>
                     <p>By default, this is the same URI that's used to identify our Resource Model, with the string
-                        "_collection" appended to the end. Magento considers Collections part of the Resource, so this
+                        "_collection" appended to the end. OpenMage considers Collections part of the Resource, so this
                         URI is converted into the class name.</p>
-                    <pre>Magentotutorial_Weblog_Model_Resource_Blogpost_Collection</pre>
+                    <pre>OpenMagetutorial_Weblog_Model_Resource_Blogpost_Collection</pre>
                     <p>Add the following PHP class at the following location</p>
-                    <pre>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Blogpost/Collection.php</pre>
+                    <pre>File: app/code/local/OpenMagetutorial/Weblog/Model/Resource/Blogpost/Collection.php</pre>
                     <pre>
-                    class Magentotutorial_Weblog_Model_Resource_Blogpost_Collection extends Mage_Core_Model_Resource_Db_Collection_Abstract {
-                        protected function _construct()
-                        {
-                                $this->_init('weblog/blogpost');
-                        }
-                    }
-                    </pre>
+class OpenMagetutorial_Weblog_Model_Resource_Blogpost_Collection extends Mage_Core_Model_Resource_Db_Collection_Abstract {
+    protected function _construct()
+    {
+        $this->_init('weblog/blogpost');
+    }
+}
+</pre>
                     <p>Just as with our other classes, we need to init our Collection with the Model URI.
                         (weblog/blogpost). Rerun your Controller Action, and you should see your post information.</p>
                     <h2>Wrapup</h2>
-                    <p>Congratulations, you've created and configured your first Magento Model. In a later article we'll
-                        take a look at Magento's Entity Attribute Value Models (EAV), which expand on what we've learned
+                    <p>Congratulations, you've created and configured your first OpenMage Model. In a later article we'll
+                        take a look at OpenMage's Entity Attribute Value Models (EAV), which expand on what we've learned
                         here.</p>
                 </div>
                 <!-- /.content-wrap -->
diff --git a/guides/m1x/magefordev/mage-for-dev-6.html b/guides/m1x/magefordev/mage-for-dev-6.html
index 157cf863c7..e7315897a5 100644
--- a/guides/m1x/magefordev/mage-for-dev-6.html
+++ b/guides/m1x/magefordev/mage-for-dev-6.html
@@ -31,8 +31,6 @@
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
-<!-- magento-for-dev-part-1-introduction-to-magento -->
 <body class="layout-default">
 <header class="site-header">
     <nav class="site-nav">
@@ -65,7 +63,7 @@
                         }</style>
                     </defs>
                     <g class="layer">
-                        <title>OpenMage Magento</title>
+                        <title>OpenMage</title>
                         <path class="ba"
                               d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
                         <text class="bb" id="svg_2" x="0" y="47">
@@ -135,7 +133,7 @@
                                 <div class="nav-section-title">API</div>
                                 <ul>
                                     <li class=" " role="menuitem">
-                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                        <a href="/guides/v19.x/">Get Started with OpenMage Web APIs</a>
                                     </li>
                                     <li class=" " role="menuitem">
                                         <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
@@ -210,34 +208,34 @@
                     <h4 class="guide-title">Developer Guide</h4>
                     <div class="collapsible-navigation">
                         <ul>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
                                     Introduction to OpenMage
                                 </a>
                             </li>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
                                     The OpenMage Config
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
-                                    OpenMage Controller Dispatch
+                                    Controller Dispatch
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
-                                    OpenMage Layouts, Blocks and Templates
+                                    Layouts, Blocks and Templates
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
-                                    OpenMage Models and ORM Basics
+                                    Models and ORM Basics
                                 </a>
                             </li>
                             <li class="active" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
-                                    OpenMage Setup Resources
+                                    Setup Resources
                                 </a>
                             </li>
                             <li class="" role="menuitem">
@@ -262,7 +260,7 @@ <h4 class="guide-title">Developer Guide</h4>
                         <h1 class="page-heading">OpenMage Setup Resources</h1>
                     </section>
                     <p class="para1">On any fast paced software development project, the task of keeping the development
-                        and production databases in sync become a sticky wicket. Magento offers a system to create
+                        and production databases in sync become a sticky wicket. OpenMage offers a system to create
                         versioned resource migration scripts that can help your team deal with this often contentious
                         part of the development process.</p>
                     <p><a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">In the ORM article</a> we created a
@@ -282,68 +280,69 @@ <h2>Adding the Setup Resource</h2>
                             href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">we created last time</a>. In our
                         &lt;global /&gt; section, add the following</p>
                     <pre>
-                    &lt;global>
-                        &lt;!-- ... -->
-                        &lt;resources>
-                            &lt;weblog_setup>
-                                &lt;setup>
-                                    &lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;
-                                    &lt;class>Magentotutorial_Weblog_Model_Resource_Setup&lt;/class>
-                                &lt;/setup>
-                            &lt;/weblog_setup>
-                        &lt;/resources>
-                        &lt;!-- ... -->
-                    &lt;/global>
-                    </pre>
+&lt;global>
+    &lt;!-- ... -->
+    &lt;resources>
+        &lt;weblog_setup>
+            &lt;setup>
+                &lt;module&gt;OpenMagetutorial_Weblog&lt;/module&gt;
+                &lt;class>OpenMagetutorial_Weblog_Model_Resource_Setup&lt;/class>
+            &lt;/setup>
+        &lt;/weblog_setup>
+    &lt;/resources>
+    &lt;!-- ... -->
+&lt;/global>
+</pre>
                     <p>The <tt>&lt;weblog_setup&gt;</tt> tag will be used to uniquely identify this Setup Resource. It's
                         encouraged, but not necessary, that you use the <tt>modelname_setup</tt> naming convention. The
-                        <tt>&lt;module&gt;Magentotutorial_Weblog&lt;/module&gt;</tt> tag block should contain the <tt>Packagename_Modulename</tt>
-                        of your module. Finally, <tt>&lt;class&gt;Magentotutorial_Weblog_Model_Resource_Setup&lt;/class&gt;</tt>
+                        <tt>&lt;module&gt;OpenMagetutorial_Weblog&lt;/module&gt;</tt> tag block should contain the <tt>Packagename_Modulename</tt>
+                        of your module. Finally, <tt>&lt;class&gt;OpenMagetutorial_Weblog_Model_Resource_Setup&lt;/class&gt;</tt>
                         should contain the name of the class we'll be creating for our Setup Resource. For basic setup
                         scripts it's not necessary to create a custom class, but by doing it now you'll give yourself
                         more flexibility down the line.</p>
-                    <p>After adding the above section to your config, clear your Magento cache and try to load any page
-                        of your Magento site. You'll see an exception something like</p>
-                    <pre>Fatal error: Class 'Magentotutorial_Weblog_Model_Resource_Setup' not found in</pre>
-                    <p>Magento just tried to instantiate the class you specified in your config, but couldn't find it.
+                    <p>After adding the above section to your config, clear your OpenMage cache and try to load any page
+                        of your OpenMage site. You'll see an exception something like</p>
+                    <pre>Fatal error: Class 'OpenMagetutorial_Weblog_Model_Resource_Setup' not found in</pre>
+                    <p>OpenMage just tried to instantiate the class you specified in your config, but couldn't find it.
                         You'll want to create the following file, with the following contents.</p>
-                    <p>File: app/code/local/Magentotutorial/Weblog/Model/Resource/Setup.php</p>
+                    <p>File: app/code/local/OpenMagetutorial/Weblog/Model/Resource/Setup.php</p>
                     <pre>
-                    class Magentotutorial_Weblog_Model_Resource_Setup extends Mage_Core_Model_Resource_Setup {
-                    }
-                    </pre>
-                    <p>Now, reload any page of your Magento site. The exception should be gone, and your page should
+class OpenMagetutorial_Weblog_Model_Resource_Setup extends Mage_Core_Model_Resource_Setup
+{
+}
+</pre>
+                    <p>Now, reload any page of your OpenMage site. The exception should be gone, and your page should
                         load as expected.</p>
                     <h2>Creating our Installer Script</h2>
                     <p>Next, we'll want to create our installer script. This is the script that will contain any <tt>CREATE
                         TABLE</tt> or other SQL code that needs to be run to initialize our module.</p>
                     <p>First, take a look at your config.xml file</p>
                     <pre>
-                    &lt;modules>
-                        &lt;Magentotutorial_Weblog>
-                            &lt;version>0.1.0&lt;/version>
-                        &lt;/Magentotutorial_Weblog>
-                    &lt;/modules>
-                    </pre>
+&lt;modules>
+    &lt;OpenMagetutorial_Weblog>
+        &lt;version>0.1.0&lt;/version>
+    &lt;/MOpenMagetutorial_Weblog>
+ &lt;/modules>
+</pre>
                     <p>This section is required in all config.xml files, and identifies the module as well as the its
                         version number. Your installer script's name will be based on this version number. The following
                         assumes the current version of your module is 0.1.0. </p>
                     <p>Create the following file at the following location</p>
-                    <p>File: <tt>app/code/local/Magentotutorial/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</tt>
+                    <p>File: <tt>app/code/local/OpenMagetutorial/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</tt>
                     </p>
                     <pre>
-                    echo 'Running This Upgrade: '.get_class($this)."\n &lt;br /&gt; \n";
-                    die("Exit for now");
-                    </pre>
+echo 'Running This Upgrade: '.get_class($this)."\n &lt;br /&gt; \n";
+die("Exit for now");
+</pre>
                     <p>The <tt>weblog_setup</tt> portion of the path should match the tag you created in your config.xml
                         file (<tt>&lt;weblog_setup /&gt;</tt>). The <tt>0.1.0</tt> portion of the filename should match
-                        the starting version of your module. Clear your Magento cache and reload any page in your
-                        Magento site and you should see something like</p>
+                        the starting version of your module. Clear your OpenMage cache and reload any page in your
+                        OpenMage site and you should see something like</p>
                     <pre>
-                    Running This Upgrade: Magentotutorial_Weblog_Model_Resource_Setup
-                    Exit for now
-                     ...
-                    </pre>
+Running This Upgrade: OpenMagetutorial_Weblog_Model_Resource_Setup
+Exit for now
+...
+</pre>
                     <p>Which means your update script ran. Eventually we'll put our SQL update scripts here, but for now
                         we're going to concentrate on the setup mechanism itself. Remove the "die" statement from your
                         script so it looks like the following</p>
@@ -351,78 +350,78 @@ <h2>Creating our Installer Script</h2>
                     <p>Reload your page. You should see your upgrade message displayed at the top of the page. Reload
                         again, and your page should be displayed as normal.</p>
                     <h2>Resource Versions</h2>
-                    <p>Magento's Setup Resources allow you to simply drop your install scripts (and upgrade scripts,
+                    <p>OpenMage's Setup Resources allow you to simply drop your install scripts (and upgrade scripts,
                         which we'll get to in a bit) onto the server, and have the system automatically run them. This
                         allows you to have all your database migrations scripts stored in the system in a consistent
                         format.</p>
                     <p>Using your favorite database client, take a look at the core_setup table</p>
                     <pre>mysql> select * from core_resource;
-                        +-------------------------+------------+--------------+
-                        | code                    | version    | data_version |
-                        +-------------------------+------------+--------------+
-                        | adminnotification_setup | 1.6.0.0    | 1.6.0.0      |
-                        | admin_setup             | 1.6.1.0    | 1.6.1.0      |
-                        | api2_setup              | 1.0.0.0    | 1.0.0.0      |
-                        | api_setup               | 1.6.0.0    | 1.6.0.0      |
-                        | backup_setup            | 1.6.0.0    | 1.6.0.0      |
-                        | bundle_setup            | 1.6.0.0.1  | 1.6.0.0.1    |
-                        | captcha_setup           | 1.7.0.0.0  | 1.7.0.0.0    |
-                        | catalogindex_setup      | 1.6.0.0    | 1.6.0.0      |
-                        | cataloginventory_setup  | 1.6.0.0.2  | 1.6.0.0.2    |
-                        | catalogrule_setup       | 1.6.0.3    | 1.6.0.3      |
-                        | catalogsearch_setup     | 1.6.0.0    | 1.6.0.0      |
-                        | catalog_setup           | 1.6.0.0.14 | 1.6.0.0.14   |
-                        | checkout_setup          | 1.6.0.0    | 1.6.0.0      |
-                        | cms_setup               | 1.6.0.0.1  | 1.6.0.0.1    |
-                        | compiler_setup          | 1.6.0.0    | 1.6.0.0      |
-                        | contacts_setup          | 1.6.0.0    | 1.6.0.0      |
-                        | core_setup              | 1.6.0.2    | 1.6.0.2      |
-                        | cron_setup              | 1.6.0.0    | 1.6.0.0      |
-                        | customer_setup          | 1.6.2.0.1  | 1.6.2.0.1    |
-                        | dataflow_setup          | 1.6.0.0    | 1.6.0.0      |
-                        | directory_setup         | 1.6.0.1    | 1.6.0.1      |
-                        | downloadable_setup      | 1.6.0.0.2  | 1.6.0.0.2    |
-                        | eav_setup               | 1.6.0.0    | 1.6.0.0      |
-                        | giftmessage_setup       | 1.6.0.0    | 1.6.0.0      |
-                        | googleanalytics_setup   | 0.1.0      | 0.1.0        |
-                        | googlecheckout_setup    | 1.6.0.1    | 1.6.0.1      |
-                        | importexport_setup      | 1.6.0.2    | 1.6.0.2      |
-                        | index_setup             | 1.6.0.0    | 1.6.0.0      |
-                        | log_setup               | 1.6.0.0    | 1.6.0.0      |
-                        | moneybookers_setup      | 1.6.0.0    | 1.6.0.0      |
-                        | newsletter_setup        | 1.6.0.1    | 1.6.0.1      |
-                        | oauth_setup             | 1.0.0.0    | 1.0.0.0      |
-                        | paygate_setup           | 1.6.0.0    | 1.6.0.0      |
-                        | payment_setup           | 1.6.0.0    | 1.6.0.0      |
-                        | paypaluk_setup          | 1.6.0.0    | 1.6.0.0      |
-                        | paypal_setup            | 1.6.0.2    | 1.6.0.2      |
-                        | persistent_setup        | 1.0.0.0    | 1.0.0.0      |
-                        | poll_setup              | 1.6.0.0    | 1.6.0.0      |
-                        | productalert_setup      | 1.6.0.0    | 1.6.0.0      |
-                        | rating_setup            | 1.6.0.0    | 1.6.0.0      |
-                        | reports_setup           | 1.6.0.0.1  | 1.6.0.0.1    |
-                        | review_setup            | 1.6.0.0    | 1.6.0.0      |
-                        | salesrule_setup         | 1.6.0.3    | 1.6.0.3      |
-                        | sales_setup             | 1.6.0.7    | 1.6.0.7      |
-                        | sendfriend_setup        | 1.6.0.0    | 1.6.0.0      |
-                        | shipping_setup          | 1.6.0.0    | 1.6.0.0      |
-                        | sitemap_setup           | 1.6.0.0    | 1.6.0.0      |
-                        | tag_setup               | 1.6.0.0    | 1.6.0.0      |
-                        | tax_setup               | 1.6.0.3    | 1.6.0.3      |
-                        | usa_setup               | 1.6.0.1    | 1.6.0.1      |
-                        | weblog_setup            | 0.1.0      | 0.1.0        |
-                        | weee_setup              | 1.6.0.0    | 1.6.0.0      |
-                        | widget_setup            | 1.6.0.0    | 1.6.0.0      |
-                        | wishlist_setup          | 1.6.0.0    | 1.6.0.0      |
-                        | xmlconnect_setup        | 1.6.0.0    | 1.6.0.0      |
-                        +-------------------------+------------+--------------+
-                        55 rows in set (0.00 sec)
-                    </pre>
++-------------------------+------------+--------------+
+| code                    | version    | data_version |
++-------------------------+------------+--------------+
+| adminnotification_setup | 1.6.0.0    | 1.6.0.0      |
+| admin_setup             | 1.6.1.0    | 1.6.1.0      |
+| api2_setup              | 1.0.0.0    | 1.0.0.0      |
+| api_setup               | 1.6.0.0    | 1.6.0.0      |
+| backup_setup            | 1.6.0.0    | 1.6.0.0      |
+| bundle_setup            | 1.6.0.0.1  | 1.6.0.0.1    |
+| captcha_setup           | 1.7.0.0.0  | 1.7.0.0.0    |
+| catalogindex_setup      | 1.6.0.0    | 1.6.0.0      |
+| cataloginventory_setup  | 1.6.0.0.2  | 1.6.0.0.2    |
+| catalogrule_setup       | 1.6.0.3    | 1.6.0.3      |
+| catalogsearch_setup     | 1.6.0.0    | 1.6.0.0      |
+| catalog_setup           | 1.6.0.0.14 | 1.6.0.0.14   |
+| checkout_setup          | 1.6.0.0    | 1.6.0.0      |
+| cms_setup               | 1.6.0.0.1  | 1.6.0.0.1    |
+| compiler_setup          | 1.6.0.0    | 1.6.0.0      |
+| contacts_setup          | 1.6.0.0    | 1.6.0.0      |
+| core_setup              | 1.6.0.2    | 1.6.0.2      |
+| cron_setup              | 1.6.0.0    | 1.6.0.0      |
+| customer_setup          | 1.6.2.0.1  | 1.6.2.0.1    |
+| dataflow_setup          | 1.6.0.0    | 1.6.0.0      |
+| directory_setup         | 1.6.0.1    | 1.6.0.1      |
+| downloadable_setup      | 1.6.0.0.2  | 1.6.0.0.2    |
+| eav_setup               | 1.6.0.0    | 1.6.0.0      |
+| giftmessage_setup       | 1.6.0.0    | 1.6.0.0      |
+| googleanalytics_setup   | 0.1.0      | 0.1.0        |
+| googlecheckout_setup    | 1.6.0.1    | 1.6.0.1      |
+| importexport_setup      | 1.6.0.2    | 1.6.0.2      |
+| index_setup             | 1.6.0.0    | 1.6.0.0      |
+| log_setup               | 1.6.0.0    | 1.6.0.0      |
+| moneybookers_setup      | 1.6.0.0    | 1.6.0.0      |
+| newsletter_setup        | 1.6.0.1    | 1.6.0.1      |
+| oauth_setup             | 1.0.0.0    | 1.0.0.0      |
+| paygate_setup           | 1.6.0.0    | 1.6.0.0      |
+| payment_setup           | 1.6.0.0    | 1.6.0.0      |
+| paypaluk_setup          | 1.6.0.0    | 1.6.0.0      |
+| paypal_setup            | 1.6.0.2    | 1.6.0.2      |
+| persistent_setup        | 1.0.0.0    | 1.0.0.0      |
+| poll_setup              | 1.6.0.0    | 1.6.0.0      |
+| productalert_setup      | 1.6.0.0    | 1.6.0.0      |
+| rating_setup            | 1.6.0.0    | 1.6.0.0      |
+| reports_setup           | 1.6.0.0.1  | 1.6.0.0.1    |
+| review_setup            | 1.6.0.0    | 1.6.0.0      |
+| salesrule_setup         | 1.6.0.3    | 1.6.0.3      |
+| sales_setup             | 1.6.0.7    | 1.6.0.7      |
+| sendfriend_setup        | 1.6.0.0    | 1.6.0.0      |
+| shipping_setup          | 1.6.0.0    | 1.6.0.0      |
+| sitemap_setup           | 1.6.0.0    | 1.6.0.0      |
+| tag_setup               | 1.6.0.0    | 1.6.0.0      |
+| tax_setup               | 1.6.0.3    | 1.6.0.3      |
+| usa_setup               | 1.6.0.1    | 1.6.0.1      |
+| weblog_setup            | 0.1.0      | 0.1.0        |
+| weee_setup              | 1.6.0.0    | 1.6.0.0      |
+| widget_setup            | 1.6.0.0    | 1.6.0.0      |
+| wishlist_setup          | 1.6.0.0    | 1.6.0.0      |
+| xmlconnect_setup        | 1.6.0.0    | 1.6.0.0      |
++-------------------------+------------+--------------+
+55 rows in set (0.00 sec)
+</pre>
                     <p>This table contains a list of all the installed modules, along with the installed version number.
                         You can see our module near the end</p>
 
                     <pre>| weblog_setup            | 0.1.0      | 0.1.0        |</pre>
-                    <p>This is how Magento knows not to re-run your script on the second, and on all successive, page
+                    <p>This is how OpenMage knows not to re-run your script on the second, and on all successive, page
                         loads. The <tt>weblog_setup</tt> is already installed, so it won't be updated. If you want to
                         re-run your installer script (useful when you're developing), just delete the row for your
                         module from this table. Let's do that now, and actually add the SQL to create our table. So
@@ -433,22 +432,22 @@ <h2>Resource Versions</h2>
                     <pre>DROP TABLE blog_posts;</pre>
                     <p>Then, add the following code to your setup script.</p>
                     <pre>$installer = $this;
-                    $installer->startSetup();
-                    $installer->run("
-                        CREATE TABLE `{$installer->getTable('weblog/blogpost')}` (
-                          `blogpost_id` int(11) NOT NULL auto_increment,
-                          `title` text,
-                          `post` text,
-                          `date` datetime default NULL,
-                          `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
-                          PRIMARY KEY  (`blogpost_id`)
-                        ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+$installer->startSetup();
+$installer->run("
+    CREATE TABLE `{$installer->getTable('weblog/blogpost')}` (
+     `blogpost_id` int(11) NOT NULL auto_increment,
+     `title` text,
+     `post` text,
+     `date` datetime default NULL,
+     `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
+     PRIMARY KEY  (`blogpost_id`)
+    ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
 
-                        INSERT INTO `{$installer->getTable('weblog/blogpost')}` VALUES (1,'My New Title','This is a blog post','2009-07-01 00:00:00','2009-07-02 23:12:30');
-                    ");
-                    $installer->endSetup();
-                    </pre>
-                    <p>Clear your Magento cache and reload any page in the system. You should have a new blog_posts
+    INSERT INTO `{$installer->getTable('weblog/blogpost')}` VALUES (1,'My New Title','This is a blog post','2009-07-01 00:00:00','2009-07-02 23:12:30');
+    ");
+$installer->endSetup();
+</pre>
+                    <p>Clear your OpenMage cache and reload any page in the system. You should have a new blog_posts
                         table with a single row.</p>
                     <h2>Anatomy of a Setup Script</h2>
                     <p>So, let's go over the script line-by-line. First, there's this (or is that $this?)</p>
@@ -461,25 +460,25 @@ <h2>Anatomy of a Setup Script</h2>
                         you have a good reason for breaking it.</p>
                     <p>Next, you'll see our queries are bookended by the following two method calls. </p>
                     <pre>$installer-&gt;startSetup();
-                    //...
-                    $installer-&gt;endSetup();
-                    </pre>
+//...
+$installer-&gt;endSetup();
+</pre>
                     <p>If you take a look at the <tt>Mage_Core_Model_Resource_Setup</tt> class in <tt>app/code/core/Mage/Core/Model/Resource/Setup.php</tt>
                         (which your setup class inherits from) you can see that these methods do some basic SQL setup
                     </p>
                     <pre>
-                        public function startSetup()
-                        {
-                            $this->getConnection()->startSetup()
-                            return $this;
-                        }
+public function startSetup()
+{
+    $this->getConnection()->startSetup()
+    return $this;
+}
 
-                        public function endSetup()
-                        {
-                            $this->getConnection()->endSetup();
-                            return $this;
-                        }
-                    </pre>
+public function endSetup()
+{
+    $this->getConnection()->endSetup();
+    return $this;
+}
+</pre>
                     <p>You can look into <tt>Varien_Db_Adapter_Pdo_Mysql</tt> in
                         <tt>lib/Varien/Db/Adapter/Pdo/Mysql.php</tt> to find the real SQL setup executed for MySQL
                         connections in the <tt>startSetup()</tt> and <tt>endSetup()</tt> methods.</p>
@@ -488,151 +487,152 @@ <h2>Anatomy of a Setup Script</h2>
                     <p>which accepts a string containing the SQL needed to setup your database table(s). You may specify
                         any number of queries, separated by a semi-colon. You also probably noticed the following</p>
                     <pre>$installer-&gt;getTable('weblog/blogpost')</pre>
-                    <p>The <tt>getTable</tt> method allows you to pass in a Magento Model URI and get its table name.
+                    <p>The <tt>getTable</tt> method allows you to pass in a OpenMage Model URI and get its table name.
                         While not necessary, using this method ensures that your script will continue to run, even if
                         someone changes the name of their table in the config file. The <tt>Mage_Core_Model_Resource_Setup</tt>
                         class contains many useful helper methods like this. The best way to become familiar with
-                        everything that's possible is to study the installer scripts used by the core Magento modules.
+                        everything that's possible is to study the installer scripts used by the core OpenMage modules.
                     </p>
                     <h2>RDBMS Agnostic Scripts</h2>
-                    <p>Since version 1.6, Magento (in theory) supports more database backends then only MySQL. Since our
+                    <p>Since version 1.6, OpenMage (in theory) supports more database backends then only MySQL. Since our
                         setup script contains raw SQL statements, it may not run correctly on a different database
                         system, say MSSQL. For that reason the setup script name is prefixt with the string
                         <tt>mysql4-</tt></p>
-                    <p>In order to make setup scripts cross-database compatible, Magento offers a DDL (Data Definition
+                    <p>In order to make setup scripts cross-database compatible, OpenMage offers a DDL (Data Definition
                         Language) Table object. Here is an alternative version of our setup script that would run on any
                         supported RDBMS.</p>
                     <p>File:
-                        <code>app/code/local/Magentotutorial/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</code></p>
+                        <code>app/code/local/OpenMagetutorial/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</code></p>
                     <pre>
-                    $installer = $this;
-                    $installer->startSetup();
-                    $table = $installer->getConnection()->newTable($installer->getTable('weblog/blogpost'))
-                        ->addColumn('blogpost_id', Varien_Db_Ddl_Table::TYPE_INTEGER, null, array(
-                            'unsigned' => true,
-                            'nullable' => false,
-                            'primary' => true,
-                            'identity' => true,
-                            ), 'Blogpost ID')
-                        ->addColumn('title', Varien_Db_Ddl_Table::TYPE_TEXT, null, array(
-                            'nullable' => false,
-                            ), 'Blogpost Title')
-                        ->addColumn('post', Varien_Db_Ddl_Table::TYPE_TEXT, null, array(
-                            'nullable' => true,
-                            ), 'Blogpost Body')
-                        ->addColumn('date', Varien_Db_Ddl_Table::TYPE_DATETIME, null, array(
-                            ), 'Blogpost Date')
-                        ->addColumn('timestamp', Varien_Db_Ddl_Table::TYPE_TIMESTAMP, null, array(
-                            ), 'Timestamp')
-                        ->setComment('Magentotutorial weblog/blogpost entity table');
-                    $installer->getConnection()->createTable($table);
+$installer = $this;
+$installer->startSetup();
+$table = $installer->getConnection()->newTable($installer->getTable('weblog/blogpost'))
+    ->addColumn('blogpost_id', Varien_Db_Ddl_Table::TYPE_INTEGER, null, array(
+     'unsigned' => true,
+     'nullable' => false,
+     'primary' => true,
+     'identity' => true,
+    ), 'Blogpost ID')
+    ->addColumn('title', Varien_Db_Ddl_Table::TYPE_TEXT, null, array(
+     'nullable' => false,
+    ), 'Blogpost Title')
+    ->addColumn('post', Varien_Db_Ddl_Table::TYPE_TEXT, null, array(
+     'nullable' => true,
+    ), 'Blogpost Body')
+    ->addColumn('date', Varien_Db_Ddl_Table::TYPE_DATETIME, null, array(
+    ), 'Blogpost Date')
+    ->addColumn('timestamp', Varien_Db_Ddl_Table::TYPE_TIMESTAMP, null, array(
+    ), 'Timestamp')
+    ->setComment('OpenMagetutorial weblog/blogpost entity table');
+$installer->getConnection()->createTable($table);
 
-                    $installer->endSetup();
-                    </pre>
+$installer->endSetup();
+</pre>
                     <p>As you can see, there is no raw SQL in this version of the setup script. So which version should
                         you use? If you want your Modules to run on any RDBMS backend, use the new DDL style upgrade
                         scripts. If you are concerned about backward compatibility, use the raw SQL flavor, that is
-                        still supported by Magento 1.6 and 1.7 (and probably will be supported by any 1.x Magento
+                        still supported by OpenMage 1.6 and 1.7 (and probably will be supported by any 1.x OpenMage
                         release).</p>
                     <h2>Module Upgrades</h2>
                     <p>So, that's how you create a script that will setup your initial database tables, but what if you
-                        want to alter the structure of an existing module? Magento's Setup Resources support a simple
+                        want to alter the structure of an existing module? OpenMage's Setup Resources support a simple
                         versioning scheme that will let you automatically run scripts to <strong>upgrade</strong> your
                         modules. </p>
-                    <p>Once Magento runs an <em>installer</em> script for a module, it will <strong>never run another
+                    <p>Once OpenMage runs an <em>installer</em> script for a module, it will <strong>never run another
                         installer for that module again</strong> (short of manually deleting the reference in the <tt>core_resource</tt>
                         table). Instead, you'll need to create an upgrade script. Upgrade scripts are very similar to
                         installer scripts, with a few key differences.</p>
                     <p>To get started, we'll create a script at the following location, with the following contents</p>
-                    <p>File: app/code/local/Magentotutorial/Weblog/sql/weblog_setup/upgrade-0.1.0-0.2.0.php:</p>
+                    <p>File: app/code/local/OpenMagetutorial/Weblog/sql/weblog_setup/upgrade-0.1.0-0.2.0.php:</p>
                     <pre>
-                    echo 'Testing our upgrade script (upgrade-0.1.0-0.2.0.php) and halting execution to avoid updating the system version number <br/>';
-                    die();
-                    </pre>
+echo 'Testing our upgrade script (upgrade-0.1.0-0.2.0.php) and halting execution to avoid updating the system version number <br/>';
+die();
+</pre>
                     <p>Upgrade scripts are placed in the same folder as your installer script, but named slightly
                         differently. First, and most obviously, the file name contains the word upgrade. Secondly,
                         you'll notice there are <strong>two</strong> version numbers, separated by a "-". The first
                         (<tt>0.1.0</tt>) is the module version that we're upgrading <strong>from</strong>. The second
                         (<tt>0.2.0</tt>) is the module version we're upgrading <strong>to</strong>.</p>
-                    <p>If we cleared our Magento cache and reloaded a page, our script wouldn't run. We need to update
+                    <p>If we cleared our OpenMage cache and reloaded a page, our script wouldn't run. We need to update
                         the version number in our module's config.xml file to trigger the upgrade</p>
                     <pre>
-                    &lt;modules>
-                        &lt;Magentotutorial_Weblog>
-                            &lt;version>0.2.0&lt;/version>
-                        &lt;/Magentotutorial_Weblog>
-                    &lt;/modules>
-                    </pre>
-                    <p>With the new version number in place, we'll need to clear our Magento cache and load any page in
-                        our Magento site. You should now see output from your upgrade script. </p>
+&lt;modules>
+    &lt;OpenMagetutorial_Weblog>
+        &lt;version>0.2.0&lt;/version>
+    &lt;/OpenMagetutorial_Weblog>
+&lt;/modules>
+</pre>
+                    <p>With the new version number in place, we'll need to clear our OpenMage cache and load any page in
+                        our OpenMage site. You should now see output from your upgrade script. </p>
                     <p>By the way, we also could have names our upgrade script <tt><strong>mysql4-</strong>upgrade-0.1.0-0.2.0.php</tt>.
                         This would indicate our upgrade would contain MySQL specific SQL.</p>
                     <p>Before we continue and actually implement the upgrade script, there's one important piece of
                         behavior you'll want to be aware of. Create another upgrade file at the following location with
                         the following contents.</p>
-                    <p>File: app/code/local/Magentotutorial/Weblog/sql/weblog_setup/upgrade-0.1.0-0.1.5.php:</p>
-                    <pre>
-                    echo 'Testing our upgrade script (upgrade-0.1.0-0.1.5.php) and NOT halting execution &lt;br /&gt;';
-                    </pre>
-                    <p>If you reload a page, you'll notice you see BOTH messages. When Magento notices the version
+                    <p>File: app/code/local/OpenMagetutorial/Weblog/sql/weblog_setup/upgrade-0.1.0-0.1.5.php:</p>
+                    <pre>echo 'Testing our upgrade script (upgrade-0.1.0-0.1.5.php) and NOT halting execution &lt;br /&gt;';</pre>
+                    <p>If you reload a page, you'll notice you see BOTH messages. When OpenMage notices the version
                         number of a module has changed, it will run through <strong>all</strong> the setup scripts
                         needed to bring that version up to date. Although we never really created a version 0.1.5 of the
-                        Weblog module, Magento sees the upgrade script, and will attempt to run it. Scripts will be run
+                        Weblog module, OpenMage sees the upgrade script, and will attempt to run it. Scripts will be run
                         in order from lowest to highest. If you take a peek at the <tt>core_resource</tt> table, </p>
-                    <pre>mysql> select * from core_resource where code = 'weblog_setup';
-                    +--------------+---------+--------------+
-                    | code         | version | data_version |
-                    +--------------+---------+--------------+
-                    | weblog_setup | 0.1.5   | 0.1.5        |
-                    +--------------+---------+--------------+
-                    1 row in set (0.00 sec)
-                    </pre>
-                    <p>you'll notice Magento considers the version number to be 1.5. That's because we completed
+                    <pre>
+mysql> select * from core_resource where code = 'weblog_setup';
++--------------+---------+--------------+
+| code         | version | data_version |
++--------------+---------+--------------+
+| weblog_setup | 0.1.5   | 0.1.5        |
++--------------+---------+--------------+
+1 row in set (0.00 sec)
+</pre>
+                    <p>you'll notice OpenMage considers the version number to be 1.5. That's because we completed
                         executing the 1.0 to 1.5 upgrade, but did not complete execution of the 1.0 to 2.0 upgrade.</p>
                     <p>So, with all that out of the way, writing our actual upgrade script is identical to writing an
                         installer script. Let's change the <tt>0.1.0-0.2.0</tt> script to read</p>
                     <pre>
-                    $installer = $this;
-                    $installer->startSetup();
-                    $installer->getConnection()
-                        ->changeColumn($installer->getTable('weblog/blogpost'), 'post', 'post', array(
-                            'type' => Varien_Db_Ddl_Table::TYPE_TEXT,
-                            'nullable' => false,
-                            'comment' => 'Blogpost Body'
-                        )
-                    );
-                    $installer->endSetup();
-                    die("You'll see why this is here in a second");
-                    </pre>
-                    <p>Try refreshing a page in your Magento site and ... nothing. The upgrade script didn't run. The
+$installer = $this;
+$installer->startSetup();
+$installer->getConnection()
+    ->changeColumn($installer->getTable('weblog/blogpost'), 'post', 'post', array(
+        'type' => Varien_Db_Ddl_Table::TYPE_TEXT,
+        'nullable' => false,
+        'comment' => 'Blogpost Body'
+        )
+    );
+$installer->endSetup();
+die("You'll see why this is here in a second");
+</pre>
+                    <p>Try refreshing a page in your OpenMage site and ... nothing. The upgrade script didn't run. The
                         post field in our table still allows null values, and more importantly, the call to
                         <tt>die()</tt> did not halt execution. Here's what happened</p>
                     <ol>
                         <li>The weblog_setup resource was at version <tt>0.1.0</tt></li>
                         <li>We upgraded our module to version <tt>0.2.0</tt></li>
-                        <li>Magento saw the upgraded module, and saw there were two upgrade scripts to run;
+                        <li>OpenMage saw the upgraded module, and saw there were two upgrade scripts to run;
                             <tt>0.1.0</tt> to <tt>0.1.5</tt> and <tt>0.1.0</tt> to <tt>0.2.0</tt></li>
-                        <li>Magento queued up both scripts to run</li>
-                        <li>Magento ran the <tt>0.1.0</tt> to <tt>0.1.5</tt> script</li>
+                        <li>OpenMage queued up both scripts to run</li>
+                        <li>OpenMage ran the <tt>0.1.0</tt> to <tt>0.1.5</tt> script</li>
                         <li>The weblog_setup resource is now at version <tt>0.1.5</tt></li>
-                        <li>Magento ran the <tt>0.1.0</tt> to <tt>0.2.0</tt> script, execution was halted</li>
-                        <li>On the next page load, Magento saw weblog_setup at version <tt>0.1.5</tt> and did not see
+                        <li>OpenMage ran the <tt>0.1.0</tt> to <tt>0.2.0</tt> script, execution was halted</li>
+                        <li>On the next page load, OpenMage saw weblog_setup at version <tt>0.1.5</tt> and did not see
                             any upgrade scripts to run since both scripts indicated they should be run
                             <strong>from</strong> <tt>0.1.0</tt></li>
                     </ol>
                     <p>The correct way to achieve what we wanted would have been to name our scripts as follows</p>
-                    <pre>upgrade-0.1.0-0.1.5.php #This goes from 0.1.0 to 0.1.5
-                    upgrade-0.1.5-0.2.0.php #This goes 0.1.5 to 0.2.0</pre>
-                    <p>Magento is smart enough to run both scripts on a single page load. You can go back in time and
+                    <pre>
+upgrade-0.1.0-0.1.5.php #This goes from 0.1.0 to 0.1.5
+upgrade-0.1.5-0.2.0.php #This goes 0.1.5 to 0.2.0</pre>
+                    <p>OpenMage is smart enough to run both scripts on a single page load. You can go back in time and
                         give this a try by updating the <tt>core_resource</tt> table</p>
-                    <pre>UPDATE core_resource SET version = '0.1.0', data_version = '0.1.0' WHERE code = 'weblog_setup';
-                    ...</pre>
-                    <p>It's one of the odd quirks of the Magento system that the updates will run as previously
+                    <pre>
+UPDATE core_resource SET version = '0.1.0', data_version = '0.1.0' WHERE code = 'weblog_setup';
+...</pre>
+                    <p>It's one of the odd quirks of the OpenMage system that the updates will run as previously
                         configured. This means you'll want to be careful with multiple developers adding update scripts
                         to the system. You'll either want a build-meister/deployment-manager type in charge of the
                         upgrade scripts or (heaven forbid) developers will need to talk to one another.</p>
                     <h2>Wrap-up</h2>
-                    <p>You should now know the basics of how to use Magento Setup Resources to create versioned database
+                    <p>You should now know the basics of how to use OpenMage Setup Resources to create versioned database
                         migration scripts, as well as understand the scripts provided in the core modules. Beyond having
                         a standard way for developers to write migration scripts, Setup Resources become much more
                         important when creating and modifying Entity Attribute Value models.</p>
diff --git a/guides/m1x/magefordev/mage-for-dev-7.html b/guides/m1x/magefordev/mage-for-dev-7.html
index c7650ea4fc..c8b1cb3092 100644
--- a/guides/m1x/magefordev/mage-for-dev-7.html
+++ b/guides/m1x/magefordev/mage-for-dev-7.html
@@ -31,8 +31,6 @@
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
-<!-- magento-for-dev-part-1-introduction-to-magento -->
 <body class="layout-default">
 <header class="site-header">
     <nav class="site-nav">
@@ -65,7 +63,7 @@
                         }</style>
                     </defs>
                     <g class="layer">
-                        <title>OpenMage Magento</title>
+                        <title>OpenMage</title>
                         <path class="ba"
                               d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
                         <text class="bb" id="svg_2" x="0" y="47">
@@ -135,7 +133,7 @@
                                 <div class="nav-section-title">API</div>
                                 <ul>
                                     <li class=" " role="menuitem">
-                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                        <a href="/guides/v19.x/">Get Started with OpenMage Web APIs</a>
                                     </li>
                                     <li class=" " role="menuitem">
                                         <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
@@ -210,34 +208,34 @@
                     <h4 class="guide-title">Developer Guide</h4>
                     <div class="collapsible-navigation">
                         <ul>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
                                     Introduction to OpenMage
                                 </a>
                             </li>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
                                     The OpenMage Config
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
-                                    OpenMage Controller Dispatch
+                                    Controller Dispatch
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
-                                    OpenMage Layouts, Blocks and Templates
+                                    Layouts, Blocks and Templates
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
-                                    OpenMage Models and ORM Basics
+                                    Models and ORM Basics
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
-                                    OpenMage Setup Resources
+                                    Setup Resources
                                 </a>
                             </li>
                             <li class="active" role="menuitem">
@@ -262,18 +260,37 @@ <h4 class="guide-title">Developer Guide</h4>
                         <h1 class="page-heading">Advanced ORM: Entity Attribute Value</h1>
                     </section>
 
-                    <p class="para1">In the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">first ORM article</a> we told you there were two kinds of Models in Magento.  Regular, or "simple" Models, and Entity Attribute Value (or EAV) Models.  We also told you this was a bit of a fib.  Here's where we come clean.</p>
+                    <p class="para1">In the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">first ORM
+                        article</a> we told you there were two kinds of Models in OpenMage. Regular, or "simple" Models,
+                        and Entity Attribute Value (or EAV) Models. We also told you this was a bit of a fib. Here's
+                        where we come clean.</p>
 
-                    <p><strong>ALL</strong> Magento Models interacting with the database inherit from the <tt>Mage_Core_Model_Abstract</tt> / <tt>Varien_Object</tt> chain.  What makes something either a simple Model or an EAV Model is its <strong>Model Resource</strong>.  While all resources extend the base <tt>Mage_Core_Model_Resource_Abstract</tt> class, simple Models have a resource that inherits from <tt>Mage_Core_Model_Resource_Db_Abstract</tt>, and EAV Models have a resource that inherits from <tt>Mage_Eav_Model_Entity_Abstract</tt></p>
+                    <p><strong>ALL</strong> OpenMage Models interacting with the database inherit from the <tt>Mage_Core_Model_Abstract</tt>
+                        / <tt>Varien_Object</tt> chain. What makes something either a simple Model or an EAV Model is
+                        its <strong>Model Resource</strong>. While all resources extend the base <tt>Mage_Core_Model_Resource_Abstract</tt>
+                        class, simple Models have a resource that inherits from
+                        <tt>Mage_Core_Model_Resource_Db_Abstract</tt>, and EAV Models have a resource that inherits from
+                        <tt>Mage_Eav_Model_Entity_Abstract</tt></p>
 
-                    <p>If you think about it, this makes sense.  As the end-programmer-user of the system you want a set of methods you can use to talk to and manipulate your Models.  You don't care what the backend storage looks like, you just want to get properties and invoke methods that trigger business rules.  </p>
+                    <p>If you think about it, this makes sense. As the end-programmer-user of the system you want a set
+                        of methods you can use to talk to and manipulate your Models. You don't care what the backend
+                        storage looks like, you just want to get properties and invoke methods that trigger business
+                        rules. </p>
 
                     <h2>What is EAV</h2>
 
-                    <p><a href="http://en.wikipedia.org/wiki/Entity-attribute-value_model" target="_new">Wikipedia defines EAV</a> as </p>
-                    <blockquote>Entity-Attribute-Value model (EAV), also known as object-attribute-value model and open schema is a data model that is used in circumstances where the number of attributes (properties, parameters) that can be used to describe a thing (an "entity" or "object") is potentially very vast, but the number that will actually apply to a given entity is relatively modest. In mathematics, this model is known as a sparse matrix.</blockquote>
+                    <p><a href="http://en.wikipedia.org/wiki/Entity-attribute-value_model" target="_new">Wikipedia
+                        defines EAV</a> as </p>
+                    <blockquote>Entity-Attribute-Value model (EAV), also known as object-attribute-value model and open
+                        schema is a data model that is used in circumstances where the number of attributes (properties,
+                        parameters) that can be used to describe a thing (an "entity" or "object") is potentially very
+                        vast, but the number that will actually apply to a given entity is relatively modest. In
+                        mathematics, this model is known as a sparse matrix.
+                    </blockquote>
 
-                    <p>Another metaphor that helps me wrap my head around it is "EAV brings some aspects of normalization to the database <strong>table schema</strong>".  In a traditional database, tables have a fixed number of columns</p>
+                    <p>Another metaphor that helps me wrap my head around it is "EAV brings some aspects of
+                        normalization to the database <strong>table schema</strong>". In a traditional database, tables
+                        have a fixed number of columns</p>
 
                     <pre>+------------------+
 | products         |
@@ -293,36 +310,69 @@ <h2>What is EAV</h2>
 +------------+----------------+------------------+---------+
 </pre>
 
-                    <p>Every product has a name, every product has a price, etc.  </p>
-
-                    <p>In an EAV Model, each "entity" (product) being modeled has a <strong>different</strong> set of attributes.  EAV makes a lot of sense for a generic eCommerce solution.  A store that sells laptops (which have a CPU speed, color, ram amount, etc) is going to have a different set of needs than a store that sells yarn (yarn has a color, but no CPU speed, etc.).  Even within our hypothetical yarn store, some products will have length (balls of yarn), and others will have diameter (knitting needles). </p>
-
-                    <p>There aren't many open source or commercial databases that use EAV by default.  There are none that are available on a wide variety of web hosting platforms.  Because of that, the Magento engineers have built an EAV system out of PHP objects that use MySQL as a data-store.  In other words, they've built an EAV database system <strong>on top of</strong> a traditional relational database.  </p>
-
-                    <p>In practice this means any Model that uses an EAV resource has its attributes spread out over a number of MySQL tables.<br/>
-                        <a href="http://alanstorm.com/2009/img/magento-book/eav.png" target="_blank"><img src="http://alanstorm.com/2009/img/magento-book/eav.png" width="700" height="463" style="border:1px solid #000;margin-left:40px"/></a>
-
-                    <p>The above diagram is a rough layout of the database tables Magento consults when it looks up an EAV record for the <tt>catalog_product</tt> entity.  Each individual product has a row in <tt>catalog_product_entity</tt>.  All the available attributes in the <strong>entire</strong> system (not just for products)  are stored in <tt>eav_attribute</tt>, and the actual attribute values are stored in tables with names like <tt>catalog_product_entity_varchar</tt>, <tt>catalog_product_entity_decimal</tt>, <tt>catalog_product_entity_<em>etc.</em></tt>.</p>
-
-                    <p>Beyond the mental flexibility an EAV system gives you, there's also the practical benefit of avoiding ALTER TABLE statements.  When you add a new attribute for your products, a new row is inserted into <tt>eav_attribute</tt>.  In a traditional relational database/single-table system, you'd need to ALTER the actual database structure, which can be a time consuming/risky proposition for tables with large data-sets.</p>
-
-                    <p>The downside is there's no one single simple SQL query you can use to get at all your product data.  Several single SQL queries or one large join need to be made.  </p>
+                    <p>Every product has a name, every product has a price, etc. </p>
+
+                    <p>In an EAV Model, each "entity" (product) being modeled has a <strong>different</strong> set of
+                        attributes. EAV makes a lot of sense for a generic eCommerce solution. A store that sells
+                        laptops (which have a CPU speed, color, ram amount, etc) is going to have a different set of
+                        needs than a store that sells yarn (yarn has a color, but no CPU speed, etc.). Even within our
+                        hypothetical yarn store, some products will have length (balls of yarn), and others will have
+                        diameter (knitting needles). </p>
+
+                    <p>There aren't many open source or commercial databases that use EAV by default. There are none
+                        that are available on a wide variety of web hosting platforms. Because of that, the OpenMage
+                        engineers have built an EAV system out of PHP objects that use MySQL as a data-store. In other
+                        words, they've built an EAV database system <strong>on top of</strong> a traditional relational
+                        database. </p>
+
+                    <p>In practice this means any Model that uses an EAV resource has its attributes spread out over a
+                        number of MySQL tables.<br/>
+                        <a href="http://alanstorm.com/2009/img/magento-book/eav.png" target="_blank"><img
+                                src="http://alanstorm.com/2009/img/magento-book/eav.png" width="700" height="463"
+                                style="border:1px solid #000;margin-left:40px"/></a>
+
+                    <p>The above diagram is a rough layout of the database tables OpenMage consults when it looks up an
+                        EAV record for the <tt>catalog_product</tt> entity. Each individual product has a row in <tt>catalog_product_entity</tt>.
+                        All the available attributes in the <strong>entire</strong> system (not just for products) are
+                        stored in <tt>eav_attribute</tt>, and the actual attribute values are stored in tables with
+                        names like <tt>catalog_product_entity_varchar</tt>, <tt>catalog_product_entity_decimal</tt>,
+                        <tt>catalog_product_entity_<em>etc.</em></tt>.</p>
+
+                    <p>Beyond the mental flexibility an EAV system gives you, there's also the practical benefit of
+                        avoiding ALTER TABLE statements. When you add a new attribute for your products, a new row is
+                        inserted into <tt>eav_attribute</tt>. In a traditional relational database/single-table system,
+                        you'd need to ALTER the actual database structure, which can be a time consuming/risky
+                        proposition for tables with large data-sets.</p>
+
+                    <p>The downside is there's no one single simple SQL query you can use to get at all your product
+                        data. Several single SQL queries or one large join need to be made. </p>
 
                     <h2>Implementing EAV</h2>
 
-                    <p>That's EAV in a nutshell. The rest of this articles is a run-through of what's needed to create a new EAV Model in Magento.  It's the hairiest thing you'll read about Magento and it's something that 95% of people working with the system will never need to do.  However, understanding what it takes to build an EAV Model Resource will help you understand what's going on with the EAV Resources that Magento uses.</p>
+                    <p>That's EAV in a nutshell. The rest of this articles is a run-through of what's needed to create a
+                        new EAV Model in OpenMage. It's the hairiest thing you'll read about OpenMage and it's something
+                        that 95% of people working with the system will never need to do. However, understanding what it
+                        takes to build an EAV Model Resource will help you understand what's going on with the EAV
+                        Resources that OpenMage uses.</p>
 
-                    <p>Because the EAV information is so dense, we're going to assume you're already very familiar with Magento's MVC and grouped class name features.  We'll help you along the way, but training wheels are off.</p>
+                    <p>Because the EAV information is so dense, we're going to assume you're already very familiar with
+                        OpenMage's MVC and grouped class name features. We'll help you along the way, but training wheels
+                        are off.</p>
 
                     <h2>Weblog, EAV Style</h2>
 
-                    <p>We're going to create another Model for a weblog post, but this time using an EAV Resource.  To start with, setup and create a new module which responds at the following URL</p>
+                    <p>We're going to create another Model for a weblog post, but this time using an EAV Resource. To
+                        start with, setup and create a new module which responds at the following URL</p>
 
                     <pre>http://example.com/complexworld</pre>
 
-                    <p>If you're unsure how to do this, be sure you've mastered the concepts in the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">previous tutorials</a>.</p>
+                    <p>If you're unsure how to do this, be sure you've mastered the concepts in the <a
+                            href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-7.html">previous tutorials</a>.</p>
 
-                    <p>Next, we'll create a new Model named Weblogeav. Remember, it's the <strong>Resource</strong> that's considered EAV.  We design and configure our Model the exact same way, so let's configure a Model similar to one <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">we created in the first ORM article</a>.</p>
+                    <p>Next, we'll create a new Model named Weblogeav. Remember, it's the <strong>Resource</strong>
+                        that's considered EAV. We design and configure our Model the exact same way, so let's configure
+                        a Model similar to one <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">we created
+                            in the first ORM article</a>.</p>
 
                     <pre>
 &lt;global>
@@ -330,7 +380,7 @@ <h2>Weblog, EAV Style</h2>
     &lt;models>
         &lt;!-- ... -->
         &lt;complexworld>
-            &lt;class>Magentotutorial_Complexworld_Model&lt;/class>
+            &lt;class>OpenMagetutorial_Complexworld_Model&lt;/class>
             &lt;resourceModel&gt;complexworld_resource&lt;/resourceModel&gt;
         &lt;/complexworld>
         &lt;!-- ... -->
@@ -339,9 +389,11 @@ <h2>Weblog, EAV Style</h2>
 &lt;/global>
 </pre>
 
-                    <p>You'll notice so far there is no difference to setting up a regular Model and flat table resource Model. </p>
+                    <p>You'll notice so far there is no difference to setting up a regular Model and flat table resource
+                        Model. </p>
 
-                    <p>We'll still need to let Magento know about this resource.  Similar to basic Models, EAV Resources are configured in the same <tt>&lt;model/&gt;</tt> node with everything else. </p>
+                    <p>We'll still need to let OpenMage know about this resource. Similar to basic Models, EAV Resources
+                        are configured in the same <tt>&lt;model/&gt;</tt> node with everything else. </p>
 
                     <pre>
 &lt;global>
@@ -349,7 +401,7 @@ <h2>Weblog, EAV Style</h2>
     &lt;models>
         &lt;!-- ... -->
         &lt;complexworld_resource>
-            &lt;class>Magentotutorial_Complexworld_Model_Resource&lt;/class>
+            &lt;class>OpenMagetutorial_Complexworld_Model_Resource&lt;/class>
             &lt;entities>
                 &lt;eavblogpost>
                     &lt;table>eavblog_posts&lt;/table>
@@ -362,11 +414,21 @@ <h2>Weblog, EAV Style</h2>
 &lt;/global>
 </pre>
 
-                    <p>Again, so far this is setup similar to our regular Model Resource.  We provide a <tt>&lt;class/&gt;</tt> that configures a PHP class, as well as an <tt>&lt;entities/&gt;</tt> section that will let Magento know the base table for an individual Model we want to create. The <tt>&lt;eavblogpost/&gt;</tt> tag is the name of the specific Model we want to create, and its inner <tt>&lt;table/&gt;</tt> tag specifies the base table this Model will use (more on this later).</p>
+                    <p>Again, so far this is setup similar to our regular Model Resource. We provide a <tt>&lt;class/&gt;</tt>
+                        that configures a PHP class, as well as an <tt>&lt;entities/&gt;</tt> section that will let
+                        OpenMage know the base table for an individual Model we want to create. The <tt>&lt;eavblogpost/&gt;</tt>
+                        tag is the name of the specific Model we want to create, and its inner <tt>&lt;table/&gt;</tt>
+                        tag specifies the base table this Model will use (more on this later).</p>
 
                     <h2>Where Does That File Go?</h2>
 
-                    <p>Until wide adoption of PHP 5.3 and namespaces, one of the trickier (and tedious) parts of Magento will remain remembering how <tt>&lt;classname/&gt;</tt>s relate to file paths, and then ensuring you create the correctly named directory structure and class files.  After configuring any <tt>&lt;classname/&gt;</tt>s or URIs, you may find it useful to attempt to instantiate an instance of the class in a controller <strong>without</strong> first creating the class files.  This way PHP will throw an exception telling me it can't find a file, along with the file location.  Give the following a try in your Index Controller.</p>
+                    <p>Until wide adoption of PHP 5.3 and namespaces, one of the trickier (and tedious) parts of OpenMage
+                        will remain remembering how <tt>&lt;classname/&gt;</tt>s relate to file paths, and then ensuring
+                        you create the correctly named directory structure and class files. After configuring any <tt>&lt;classname/&gt;</tt>s
+                        or URIs, you may find it useful to attempt to instantiate an instance of the class in a
+                        controller <strong>without</strong> first creating the class files. This way PHP will throw an
+                        exception telling me it can't find a file, along with the file location. Give the following a
+                        try in your Index Controller.</p>
 
                     <pre>
 public function indexAction() {
@@ -379,23 +441,25 @@ <h2>Where Does That File Go?</h2>
                     <p>As predicted, a warning should be thrown</p>
 
                     <pre>
-Warning: include(Magentotutorial/Complexworld/Model/Eavblogpost.php) [function.include]:
+Warning: include(OpenMagetutorial/Complexworld/Model/Eavblogpost.php) [function.include]:
 failed to open stream: No such file or directory  in /Users/username/Sites/magento.dev/lib/Varien/Autoload.php on line 93
 </pre>
 
-                    <p>In addition to telling us the path where we'll need to define the new resource class this also serves as a configuration check.  If we'd been warned with the following</p>
+                    <p>In addition to telling us the path where we'll need to define the new resource class this also
+                        serves as a configuration check. If we'd been warned with the following</p>
 
                     <pre>
 Warning: include(Mage/Complexworld/Model/Eavblogpost.php) [function.include]:
 failed to open stream: No such file or directory  in /Users/username/Sites/magento.dev/lib/Varien/Autoload.php on line 93
 </pre>
 
-                    <p>we'd know our Model was misconfigured, as Magento was looking for the Model in <tt>code/core/Mage</tt> instead of <tt>code/local/Magentotutorial</tt>.</p>
+                    <p>we'd know our Model was misconfigured, as OpenMage was looking for the Model in
+                        <tt>code/core/Mage</tt> instead of <tt>code/local/OpenMagetutorial</tt>.</p>
 
                     <p>So, lets create our Model class</p>
-                    <p>File: <code>app/code/local/Magentotutorial/Complexworld/Model/Eavblogpost.php</code>:
+                    <p>File: <code>app/code/local/OpenMagetutorial/Complexworld/Model/Eavblogpost.php</code>:
                     <pre>
-class Magentotutorial_Complexworld_Model_Eavblogpost extends Mage_Core_Model_Abstract {
+class OpenMagetutorial_Complexworld_Model_Eavblogpost extends Mage_Core_Model_Abstract {
     protected function _construct()
     {
         $this->_init('complexworld/eavblogpost');
@@ -403,17 +467,19 @@ <h2>Where Does That File Go?</h2>
 }
 </pre>
 
-                    <p>Remember, the Model itself is resource independent.  A regular Model and an EAV Model both extend from the same class.  It's the resource that makes them different. </p>
+                    <p>Remember, the Model itself is resource independent. A regular Model and an EAV Model both extend
+                        from the same class. It's the resource that makes them different. </p>
 
-                    <p>Clear your Magento cache, reload your page, and you should see a <strong>new</strong> warning.</p>
+                    <p>Clear your OpenMage cache, reload your page, and you should see a <strong>new</strong> warning.
+                    </p>
 
-                    <pre>Warning: include(Magentotutorial/Complexworld/Model/Resource/Eavblogpost.php)</pre>
+                    <pre>Warning: include(OpenMagetutorial/Complexworld/Model/Resource/Eavblogpost.php)</pre>
 
                     <p>As expected, we need to create a class for our Model's resource. Let's do it!</p>
 
-                    <p>File: app/code/local/Magentotutorial/Complexworld/Model/Resource/Eavblogpost.php:
+                    <p>File: app/code/local/OpenMagetutorial/Complexworld/Model/Resource/Eavblogpost.php:
                     <pre>
-class Magentotutorial_Complexworld_Model_Resource_Eavblogpost extends Mage_Eav_Model_Entity_Abstract
+class OpenMagetutorial_Complexworld_Model_Resource_Eavblogpost extends Mage_Eav_Model_Entity_Abstract
 {
     protected function _construct()
     {
@@ -427,19 +493,31 @@ <h2>Where Does That File Go?</h2>
 }
 </pre>
 
-                    <p>So, already we're seeing a few differences between a simple Model Resource and an EAV Model Resource. First off, we're extending the <tt>Mage_Eav_Model_Entity_Abstract</tt> class.  While <tt>Mage_Eav_Model_Entity_Abstract</tt> uses the same <tt>_construct</tt> concept as a regular Model Resource, there's no <tt>_init</tt> method.  Instead, we need to handle the init ourselves.  This means telling the resource what connection-resources it should use, and passing a unique identifier into the <tt>setType</tt> method of our object.</p>
+                    <p>So, already we're seeing a few differences between a simple Model Resource and an EAV Model
+                        Resource. First off, we're extending the <tt>Mage_Eav_Model_Entity_Abstract</tt> class. While
+                        <tt>Mage_Eav_Model_Entity_Abstract</tt> uses the same <tt>_construct</tt> concept as a regular
+                        Model Resource, there's no <tt>_init</tt> method. Instead, we need to handle the init ourselves.
+                        This means telling the resource what connection-resources it should use, and passing a unique
+                        identifier into the <tt>setType</tt> method of our object.</p>
 
-                    <p>Another difference in <tt> Mage_Eav_Model_Entity_Abstract</tt> is <tt>_construct</tt> is <strong>not</strong> an abstract method, primarily for reasons of backwards compatibility with older versions of the system. </p>
+                    <p>Another difference in <tt> Mage_Eav_Model_Entity_Abstract</tt> is <tt>_construct</tt> is <strong>not</strong>
+                        an abstract method, primarily for reasons of backwards compatibility with older versions of the
+                        system. </p>
 
-                    <p>So, with that, let's clear the Magento cache and reload the page.  You should see a new exception which reads</p>
+                    <p>So, with that, let's clear the OpenMage cache and reload the page. You should see a new exception
+                        which reads</p>
 
                     <pre>Invalid entity_type specified: complexworld_eavblogpost</pre>
 
-                    <p>Magento is complaining that it can't find a entity_type named <tt>complexworld_eavblogpost</tt>.  This is the value you set above</p>
+                    <p>OpenMage is complaining that it can't find a entity_type named <tt>complexworld_eavblogpost</tt>.
+                        This is the value you set above</p>
 
                     <pre>$this->setType('complexworld_eavblogpost');</pre>
 
-                    <p>Every entity has a type.  Types will, among other things, let the EAV system know which attributes a Model uses, and allow the system to link to tables that store the values for attributes.  We'll need to let Magento know that we're adding a new entity type.  Take a look in the MySQL table named <tt>eav_entity_type</tt>.</p>
+                    <p>Every entity has a type. Types will, among other things, let the EAV system know which attributes
+                        a Model uses, and allow the system to link to tables that store the values for attributes. We'll
+                        need to let OpenMage know that we're adding a new entity type. Take a look in the MySQL table
+                        named <tt>eav_entity_type</tt>.</p>
 
                     <pre>
 mysql> select * from eav_entity_type;
@@ -475,19 +553,33 @@ <h2>Where Does That File Go?</h2>
       increment_pad_char: 0
 </pre>
 
-                    <p>This table contains a list of all the entity_types in the system.  The unique identifier <tt>complexworld_eavblogpost</tt> corresponds to the <tt>entity_type_code</tt> column.</p>
+                    <p>This table contains a list of all the entity_types in the system. The unique identifier <tt>complexworld_eavblogpost</tt>
+                        corresponds to the <tt>entity_type_code</tt> column.</p>
 
                     <h2>Systems and Applications</h2>
 
-                    <p>This illustrates the single most important Magento concept, one that many people struggle to learn.  </p>
+                    <p>This illustrates the single most important OpenMage concept, one that many people struggle to
+                        learn. </p>
 
-                    <p>Consider the computer in front of you.  The OS (Mac OS X, Windows, Linux, etc.) is the software system.  Your web browser (Firefox, Safari, IE, Opera) is the application.  Magento <strong>is a system</strong> first, and an application second.  You build eCommerce applications using the Magento system.  What gets confusing is, there's a lot of places in Magento where the system code is exposed in a really raw form to the application code.  The EAV system configuration living in the same database as your store's data is an example of this.</p>
+                    <p>Consider the computer in front of you. The OS (Mac OS X, Windows, Linux, etc.) is the software
+                        system. Your web browser (Firefox, Safari, IE, Opera) is the application. OpenMage <strong>is a
+                            system</strong> first, and an application second. You build eCommerce applications using the
+                        OpenMage system. What gets confusing is, there's a lot of places in OpenMage where the system code
+                        is exposed in a really raw form to the application code. The EAV system configuration living in
+                        the same database as your store's data is an example of this.</p>
 
-                    <p>If you're going to get deep into Magento, you need to treat it like it's an old <a href="http://en.wikipedia.org/wiki/IBM_650" target="_new">Type 650</a> machine.  That is to say, it's the kind of thing you can't effectively program applications in unless unless you have a deep understanding of the system itself.</p>
+                    <p>If you're going to get deep into OpenMage, you need to treat it like it's an old <a
+                            href="http://en.wikipedia.org/wiki/IBM_650" target="_new">Type 650</a> machine. That is to
+                        say, it's the kind of thing you can't effectively program applications in unless unless you have
+                        a deep understanding of the system itself.</p>
 
                     <h2>Creating a Setup Resource</h2>
 
-                    <p>So, it's theoretically possible to manually insert the rows you'll need into the Magento database to get your Model working, but it's not recommended.  Fortunately, Magento provides a specialized <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">Setup Resource</a> that provides a number of helper method that will automatically create the needed records to get the system up and running.</p>
+                    <p>So, it's theoretically possible to manually insert the rows you'll need into the OpenMage database
+                        to get your Model working, but it's not recommended. Fortunately, OpenMage provides a specialized
+                        <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">Setup Resource</a> that provides a
+                        number of helper method that will automatically create the needed records to get the system up
+                        and running.</p>
 
                     <p>So, for starters, configure the Setup Resource like you would any other.</p>
 
@@ -497,8 +589,8 @@ <h2>Creating a Setup Resource</h2>
     &lt;resources>
         &lt;complexworld_setup>
             &lt;setup>
-                &lt;module&gt;Magentotutorial_Complexworld&lt;/module&gt;
-                &lt;class>Magentotutorial_Complexworld_Model_Resource_Setup&lt;/class>
+                &lt;module&gt;OpenMagetutorial_Complexworld&lt;/module&gt;
+                &lt;class>OpenMagetutorial_Complexworld_Model_Resource_Setup&lt;/class>
             &lt;/setup>
         &lt;/complexworld_setup>
     &lt;/resources>
@@ -508,30 +600,41 @@ <h2>Creating a Setup Resource</h2>
 
                     <p>Next, create its class file.</p>
 
-                    <p>File: app/code/local/Magentotutorial/Complexworld/Model/Resource/Setup.php:
+                    <p>File: app/code/local/OpenMagetutorial/Complexworld/Model/Resource/Setup.php:
                     <pre>
-class Magentotutorial_Complexworld_Model_Resource_Setup extends Mage_Eav_Model_Entity_Setup {
+class OpenMagetutorial_Complexworld_Model_Resource_Setup extends Mage_Eav_Model_Entity_Setup {
 }
 </pre>
 
-                    <p>Take note that we're extending from <tt>Mage_Eav_Model_Entity_Setup</tt> rather than <tt>Mage_Core_Model_Resource_Setup</tt>.</p>
+                    <p>Take note that we're extending from <tt>Mage_Eav_Model_Entity_Setup</tt> rather than <tt>Mage_Core_Model_Resource_Setup</tt>.
+                    </p>
 
-                    <p>Finally, we'll set up our installer script.  If you're not familiar with the naming conventions here, you'll want to review the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">setup resource tutorial</a> on Setup Resources.</p>
+                    <p>Finally, we'll set up our installer script. If you're not familiar with the naming conventions
+                        here, you'll want to review the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">setup
+                            resource tutorial</a> on Setup Resources.</p>
 
-                    <p>File: app/code/local/Magentotutorial/Complexworld/sql/complexworld_setup/install-0.1.0.php:
+                    <p>File: app/code/local/OpenMagetutorial/Complexworld/sql/complexworld_setup/install-0.1.0.php:
                     <pre>
 &lt;?php
 $installer = $this;
 throw new Exception("This is an exception to stop the installer from completing");
 </pre>
 
-                    <p>Clear your Magento Cache, reload you page, and the above exception should be thrown, meaning you've correctly configured your Setup Resource.</p>
+                    <p>Clear your OpenMage Cache, reload you page, and the above exception should be thrown, meaning
+                        you've correctly configured your Setup Resource.</p>
 
-                    <p><strong>NOTE:</strong> We'll be building up our install script piece by piece. If you've read the <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">previous tutorial</a>, you'll know you need to remove the setup's row from the <tt>core_resource</tt> table and clear your cache to make an installer script re-run.  For the remainder of this tutorial, please remember that anytime we add or remove an item from our installer and re-run it, you'll need to remove this row from the database and clear your Magento cache.  Normally you would create this file and run it once, a tutorial is something of an edge case.</p>
+                    <p><strong>NOTE:</strong> We'll be building up our install script piece by piece. If you've read the
+                        <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">previous tutorial</a>, you'll know
+                        you need to remove the setup's row from the <tt>core_resource</tt> table and clear your cache to
+                        make an installer script re-run. For the remainder of this tutorial, please remember that
+                        anytime we add or remove an item from our installer and re-run it, you'll need to remove this
+                        row from the database and clear your OpenMage cache. Normally you would create this file and run
+                        it once, a tutorial is something of an edge case.</p>
 
                     <h2>Adding the Entity Type</h2>
 
-                    <p>To begin, add the following to your Setup Resource installer script, and then run the script by loading any page (after removing the above exception)</p>
+                    <p>To begin, add the following to your Setup Resource installer script, and then run the script by
+                        loading any page (after removing the above exception)</p>
 
                     <pre>
 $installer = $this;
@@ -547,7 +650,10 @@ <h2>Adding the Entity Type</h2>
 $installer->endSetup();
 </pre>
 
-                    <p>We're calling the <tt>addEntityType</tt> method on our installer object.  This method allows us to pass in the entity type (<tt>complexworld_eavblogpost</tt>) along with a list of parameters to set its default values.  If you've run this script, you'll notice new rows in the <tt>eav_attribute_group</tt>, <tt>eav_attribute_set</tt>, and <tt>eav_entity_type</tt> tables.</p>
+                    <p>We're calling the <tt>addEntityType</tt> method on our installer object. This method allows us to
+                        pass in the entity type (<tt>complexworld_eavblogpost</tt>) along with a list of parameters to
+                        set its default values. If you've run this script, you'll notice new rows in the <tt>eav_attribute_group</tt>,
+                        <tt>eav_attribute_set</tt>, and <tt>eav_entity_type</tt> tables.</p>
 
                     <p>So, with that in place, if we reload our complexworld page, we'll get a new error.</p>
 
@@ -555,9 +661,13 @@ <h2>Adding the Entity Type</h2>
 
                     <h2>Creating the Data Tables</h2>
 
-                    <p>So, we've told Magento about our new entity type.  Next, we need to add the MySQL tables that will be used to store all the entity values, as well as configure the system so it knows about these tables.</p>
+                    <p>So, we've told OpenMage about our new entity type. Next, we need to add the MySQL tables that will
+                        be used to store all the entity values, as well as configure the system so it knows about these
+                        tables.</p>
 
-                    <p>Our EAV Setup Resource has a method named <tt>createEntityTables</tt> which will automatically setup the tables we need, as well as add some configuration rows to the system.  Let's add the following line to our setup resource.</p>
+                    <p>Our EAV Setup Resource has a method named <tt>createEntityTables</tt> which will automatically
+                        setup the tables we need, as well as add some configuration rows to the system. Let's add the
+                        following line to our setup resource.</p>
 
                     <pre>
 $installer->createEntityTables(
@@ -565,7 +675,12 @@ <h2>Creating the Data Tables</h2>
 );
 </pre>
 
-                    <p>The <tt>createEntityTables</tt> method accepts two parameters.  The first is the base table name, the second is a list of options.  We're using the Setup Resource's <tt>getTable</tt> method to pull the table name from our config.  If you've been following along, you know this should resolve to the string <tt>eavblog_posts</tt>.  We've omitted the second parameter which is an array of options you'll only need to used it for advanced situations that are beyond the scope of this tutorial.</p>
+                    <p>The <tt>createEntityTables</tt> method accepts two parameters. The first is the base table name,
+                        the second is a list of options. We're using the Setup Resource's <tt>getTable</tt> method to
+                        pull the table name from our config. If you've been following along, you know this should
+                        resolve to the string <tt>eavblog_posts</tt>. We've omitted the second parameter which is an
+                        array of options you'll only need to used it for advanced situations that are beyond the scope
+                        of this tutorial.</p>
 
                     <p>After running the above script, you should have the following new tables in your database</p>
 
@@ -589,19 +704,26 @@ <h2>Creating the Data Tables</h2>
         sort_order: 6
 </pre>
 
-                    <p>So, let's go back to our page and reload.  </p>
+                    <p>So, let's go back to our page and reload. </p>
 
                     <pre>http://example.com/complexworld</pre>
 
-                    <p>Success!  You should see no errors or warnings, and a dumped <tt>Magentotutorial_Complexworld_Model_Eavblogpost</tt> --- with no data.</p>
+                    <p>Success! You should see no errors or warnings, and a dumped <tt>OpenMagetutorial_Complexworld_Model_Eavblogpost</tt>
+                        --- with no data.</p>
 
                     <h2>Adding Attributes</h2>
 
-                    <p>The last step we need to take in our Setup Resource is telling Magento what attributes we want our EAV Model to have.  This would be equivalent to adding new columns in a single database table setup.  Again, the Setup Resource will help us.  The method we're interested in is <tt>addAttribute</tt>.</p>
+                    <p>The last step we need to take in our Setup Resource is telling OpenMage what attributes we want
+                        our EAV Model to have. This would be equivalent to adding new columns in a single database table
+                        setup. Again, the Setup Resource will help us. The method we're interested in is <tt>addAttribute</tt>.
+                    </p>
 
-                    <p>The code from the previous section was simply telling Magento about a <strong>type</strong> of entity that we add to the system.  These next bits of code are what will actually add possible attributes for our new type to the system.  </p>
+                    <p>The code from the previous section was simply telling OpenMage about a <strong>type</strong> of
+                        entity that we add to the system. These next bits of code are what will actually add possible
+                        attributes for our new type to the system. </p>
 
-                    <p>We do that with the method <tt>addAttribute</tt>. When we call <tt>addAttribute</tt>, Magento will need to do several things to install your entities.</p>
+                    <p>We do that with the method <tt>addAttribute</tt>. When we call <tt>addAttribute</tt>, OpenMage
+                        will need to do several things to install your entities.</p>
 
                     <p>To start with, we'll give our Eavblogpost a single attribute named title.</p>
 
@@ -624,13 +746,21 @@ <h2>Adding Attributes</h2>
 /* ... */
 </pre>
 
-                    <p>All right, that's a small pile of code.  Let's break it apart. </p>
+                    <p>All right, that's a small pile of code. Let's break it apart. </p>
 
-                    <p>The first argument to <tt>addAttribute</tt> is the entity type code. It has to match the code specified when calling addEntityType. It tells Magento which entity we are adding the attribute to, in our example it is our <tt>complexworld_eavblogpost</tt> entity. To see other available entities that come shipped with Magento, remember you can look into the <tt>eav_entity_type</tt> table at the <tt>entity_type_code</tt> column.</p>
+                    <p>The first argument to <tt>addAttribute</tt> is the entity type code. It has to match the code
+                        specified when calling addEntityType. It tells OpenMage which entity we are adding the attribute
+                        to, in our example it is our <tt>complexworld_eavblogpost</tt> entity. To see other available
+                        entities that come shipped with OpenMage, remember you can look into the <tt>eav_entity_type</tt>
+                        table at the <tt>entity_type_code</tt> column.</p>
 
-                    <p>The second argument to <tt>addAttribute</tt> is the attribute code. It has to be unique within the given entity.</p>
+                    <p>The second argument to <tt>addAttribute</tt> is the attribute code. It has to be unique within
+                        the given entity.</p>
 
-                    <p>The third argument is where it get real interesting. This is an array of key value pairs, describing the attribute properties.  For the sake of simplicity we've chose to define a single attribute, but you could go on to define as many as you'd like, by adding additional addAttribute calls to the setup script.</p>
+                    <p>The third argument is where it get real interesting. This is an array of key value pairs,
+                        describing the attribute properties. For the sake of simplicity we've chose to define a single
+                        attribute, but you could go on to define as many as you'd like, by adding additional
+                        addAttribute calls to the setup script.</p>
 
                     <h2>Array of Key Value Pairs that Define the Attribute</h2>
 
@@ -651,12 +781,15 @@ <h2>Array of Key Value Pairs that Define the Attribute</h2>
 'unique'            => false,
 </pre>
 
-                    <p>Most of these define how Magento would build a backend form element for this attribute, and probably you'll won't have to deal with the,. That said, the one important property you'll want to make note of is </p>
+                    <p>Most of these define how OpenMage would build a backend form element for this attribute, and
+                        probably you'll won't have to deal with the,. That said, the one important property you'll want
+                        to make note of is </p>
                     <pre>
 'type' => 'varchar'
 </pre>
 
-                    <p>This defines the type of the value that the attribute will contain.  You'll recall that we added table for each attribute type</p>
+                    <p>This defines the type of the value that the attribute will contain. You'll recall that we added
+                        table for each attribute type</p>
 
                     <pre>
 eavblog_posts_datetime
@@ -666,9 +799,12 @@ <h2>Array of Key Value Pairs that Define the Attribute</h2>
 eavblog_posts_varchar
 </pre>
 
-                    <p>While these do not refer to the MySQL column types, (but instead the EAV attribute types), their names (varchar, datetime, etc.) are indicative of the values they'll hold.</p>
+                    <p>While these do not refer to the MySQL column types, (but instead the EAV attribute types), their
+                        names (varchar, datetime, etc.) are indicative of the values they'll hold.</p>
 
-                    <p>All of these attribute properties are optional, if we wouldn't have specified them, Magento would have used a default value. These default values are defined in the <tt>_prepareValues</tt> method of the <tt>Mage_Eav_Model_Entity_Setup</tt> class (inherited by our setup class).</p>
+                    <p>All of these attribute properties are optional, if we wouldn't have specified them, OpenMage would
+                        have used a default value. These default values are defined in the <tt>_prepareValues</tt>
+                        method of the <tt>Mage_Eav_Model_Entity_Setup</tt> class (inherited by our setup class).</p>
 
                     <pre>
 // Mage_Eav_Model_Entity_Setup
@@ -697,11 +833,14 @@ <h2>Array of Key Value Pairs that Define the Attribute</h2>
 }
 </pre>
 
-                    <p>The second argument to the method calls to <tt>_getValue</tt> is the array key from our addAttribute argument array, and the third is the default value. So by default Magento would assume you are adding a varchar attribute with a text input.</p>
+                    <p>The second argument to the method calls to <tt>_getValue</tt> is the array key from our
+                        addAttribute argument array, and the third is the default value. So by default OpenMage would
+                        assume you are adding a varchar attribute with a text input.</p>
 
                     <h2>Adding the other attributes</h2>
 
-                    <p>Lets add attributes for the blog post content and the post date. This is what the complete install script looks like.</p>
+                    <p>Lets add attributes for the blog post content and the post date. This is what the complete
+                        install script looks like.</p>
 
                     <pre>
     $installer = $this;
@@ -749,10 +888,13 @@ <h2>Adding the other attributes</h2>
     $installer->endSetup();
 </pre>
 
-                    <p>So, now that we have everything in place, lets refresh things one last time to run our installer script.  After calling <tt>addAttribute</tt>, we should have </p>
+                    <p>So, now that we have everything in place, lets refresh things one last time to run our installer
+                        script. After calling <tt>addAttribute</tt>, we should have </p>
 
                     <ol>
-                        <li>A new row in <tt>eav_entity_type</tt> for the <strong>complexworld_eavblogpost</strong> entity type</li>
+                        <li>A new row in <tt>eav_entity_type</tt> for the <strong>complexworld_eavblogpost</strong>
+                            entity type
+                        </li>
                         <li>A new row in <tt>eav_attribute</tt> for the <strong>title</strong> attribute</li>
                         <li>A new row in <tt>eav_attribute</tt> for the <strong>content</strong> attribute</li>
                         <li>A new row in <tt>eav_attribute</tt> for the <strong>date</strong> attribute</li>
@@ -761,7 +903,9 @@ <h2>Adding the other attributes</h2>
 
                     <h2>Tying it all Together</h2>
 
-                    <p>This is clearly the lamest.blogmodel.ever, but lets try adding some rows and iterating through a collection and get the heck out of here before our heads explode.  Add the following two actions to your Index Controller.</p>
+                    <p>This is clearly the lamest.blogmodel.ever, but lets try adding some rows and iterating through a
+                        collection and get the heck out of here before our heads explode. Add the following two actions
+                        to your Index Controller.</p>
 
                     <pre>
 public function populateEntriesAction() {
@@ -793,11 +937,12 @@ <h2>Tying it all Together</h2>
 }
 </pre>
 
-                    <p>Let's populate some entries!  Load up the following URL</p>
+                    <p>Let's populate some entries! Load up the following URL</p>
 
                     <pre>http://magento.dev/index.php/complexworld/index/populateEntries</pre>
 
-                    <p>If you take a look at your database, you should see 10 new rows in the <tt>eavblog_posts</tt> table.</p>
+                    <p>If you take a look at your database, you should see 10 new rows in the <tt>eavblog_posts</tt>
+                        table.</p>
 
                     <pre>
 mysql> SELECT * FROM eavblog_posts ORDER BY entity_id DESC;
@@ -837,7 +982,8 @@ <h2>Tying it all Together</h2>
 +----------+----------------+--------------+----------+-----------+------------------+
 </pre>
 
-                    <p>Notice that <tt>eavblog_posts_varchar</tt> is linked to <tt>eavblog_posts</tt> by the <tt>entity_id</tt> column.</p>
+                    <p>Notice that <tt>eavblog_posts_varchar</tt> is linked to <tt>eavblog_posts</tt> by the <tt>entity_id</tt>
+                        column.</p>
 
                     <p>Finally, let's pull our Models back out. Load the following URL in your browser</p>
 
@@ -845,14 +991,16 @@ <h2>Tying it all Together</h2>
 
                     <p>This should give us a </p>
 
-                    <pre>Warning: include(Magentotutorial/Complexworld/Model/Resource/Eavblogpost/Collection.php) [function.include]:
+                    <pre>Warning: include(OpenMagetutorial/Complexworld/Model/Resource/Eavblogpost/Collection.php) [function.include]:
   failed to open stream: No such file or directory  in /Users/username/Sites/magento.dev/lib/Varien/Autoload.php on line 93</pre>
 
-                    <p><strong>So Close!</strong>  We didn't make a class for our collection object!  Fortunately, doing so is just as easy as with a regular Model Resource.  Add the following file with the following contents</p>
+                    <p><strong>So Close!</strong> We didn't make a class for our collection object! Fortunately, doing
+                        so is just as easy as with a regular Model Resource. Add the following file with the following
+                        contents</p>
 
-                    <p>File: Magentotutorial/Complexworld/Model/Resource/Eavblogpost/Collection.php:
+                    <p>File: OpenMagetutorial/Complexworld/Model/Resource/Eavblogpost/Collection.php:
                     <pre>
-class Magentotutorial_Complexworld_Model_Resource_Eavblogpost_Collection extends Mage_Eav_Model_Entity_Collection_Abstract
+class OpenMagetutorial_Complexworld_Model_Resource_Eavblogpost_Collection extends Mage_Eav_Model_Entity_Collection_Abstract
 {
     protected function _construct()
     {
@@ -861,11 +1009,14 @@ <h2>Tying it all Together</h2>
 }
 </pre>
 
-                    <p>This is just a standard Magento <tt>_construct</tt> method to initialize the Model. With this in place, reload the page, and we'll see all the titles and the content outputted. But notice, the date value is missing!</p>
+                    <p>This is just a standard OpenMage <tt>_construct</tt> method to initialize the Model. With this in
+                        place, reload the page, and we'll see all the titles and the content outputted. But notice, the
+                        date value is missing!</p>
 
                     <h2>Which Attributes?</h2>
 
-                    <p>Those of you with sharp eyes may have noticed something slightly different about the collection loading.</p>
+                    <p>Those of you with sharp eyes may have noticed something slightly different about the collection
+                        loading.</p>
 
                     <pre>
 $entries = $weblog2->getCollection()
@@ -873,21 +1024,40 @@ <h2>Which Attributes?</h2>
     ->addAttributeToSelect('content');
 </pre>
 
-                    <p>Because querying for EAV data can be SQL intensive, you'll need to specify which attributes it is you want your Models to fetch for you.  This way the system can make only the queries it needs. If you're willing to suffer the performance consequences, you can use a wild card to grab <strong>all</strong> the attributes</p>
+                    <p>Because querying for EAV data can be SQL intensive, you'll need to specify which attributes it is
+                        you want your Models to fetch for you. This way the system can make only the queries it needs.
+                        If you're willing to suffer the performance consequences, you can use a wild card to grab
+                        <strong>all</strong> the attributes</p>
 
                     <pre>$entries = $weblog2->getCollection()->addAttributeToSelect('*');</pre>
 
                     <h2>Jumping Off</h2>
 
-                    <p>So, that should give you enough information to be dangerous, or at least enough information so you're not drowning the next time you're trying to figure out why the yellow shirts aren't showing up in your store.  There's still plenty to learn about EAV; here's a few topics I would have liked to cover in greater detail, and may talk about in future articles</p>
+                    <p>So, that should give you enough information to be dangerous, or at least enough information so
+                        you're not drowning the next time you're trying to figure out why the yellow shirts aren't
+                        showing up in your store. There's still plenty to learn about EAV; here's a few topics I would
+                        have liked to cover in greater detail, and may talk about in future articles</p>
 
                     <ol>
-                        <li>EAV Attributes: Attributes aren't limited to datetime, decimal, int, text and varchar.  You can create your own class files to model different attributes.  This is what the <tt>attribute_model</tt> entity property is for.</li>
-                        <li>Collection Filtering: Filtering on EAV collections can get tricky, especially when you're dealing with the above mentioned non-simple attributes.  You need to use the <tt>addAttributeToFilter</tt> method on your collection before loading.</li>
-                        <li>The Magento EAV Hierarchy: Magento has taken their basic EAV Model and built up a hierarchy that's very tied to store functionality, as well as including strategies to reduce the number of queries an EAV Model generates (the concept of a <strong>flat</strong> Model, for example)</li>
+                        <li>EAV Attributes: Attributes aren't limited to datetime, decimal, int, text and varchar. You
+                            can create your own class files to model different attributes. This is what the <tt>attribute_model</tt>
+                            entity property is for.
+                        </li>
+                        <li>Collection Filtering: Filtering on EAV collections can get tricky, especially when you're
+                            dealing with the above mentioned non-simple attributes. You need to use the <tt>addAttributeToFilter</tt>
+                            method on your collection before loading.
+                        </li>
+                        <li>The OpenMage EAV Hierarchy: OpenMage has taken their basic EAV Model and built up a hierarchy
+                            that's very tied to store functionality, as well as including strategies to reduce the
+                            number of queries an EAV Model generates (the concept of a <strong>flat</strong> Model, for
+                            example)
+                        </li>
                     </ol>
 
-                    <p>EAV Models are, without a doubt, the most complicated part of the Magento system that an ecommerce web developer will need to deal with.  Remember to take deep breaths and that, at the end of the day, its just programming.  Everything happens for a concrete reason, you just need to figure out why.</p>
+                    <p>EAV Models are, without a doubt, the most complicated part of the OpenMage system that an
+                        ecommerce web developer will need to deal with. Remember to take deep breaths and that, at the
+                        end of the day, its just programming. Everything happens for a concrete reason, you just need to
+                        figure out why.</p>
                 </div>
                 <!-- /.content-wrap -->
                 <div class="page-info">
diff --git a/guides/m1x/magefordev/mage-for-dev-8.html b/guides/m1x/magefordev/mage-for-dev-8.html
index 308226dc29..bd394e9f02 100644
--- a/guides/m1x/magefordev/mage-for-dev-8.html
+++ b/guides/m1x/magefordev/mage-for-dev-8.html
@@ -31,8 +31,6 @@
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="32x32">
     <link rel="icon" type="image/png" href="/common/images/openmage-touch-icon.png" sizes="96x96">
 </head>
-<!-- Magento for Developers: Part 1&mdash;Introduction to Magento -->
-<!-- magento-for-dev-part-1-introduction-to-magento -->
 <body class="layout-default">
 <header class="site-header">
     <nav class="site-nav">
@@ -65,7 +63,7 @@
                         }</style>
                     </defs>
                     <g class="layer">
-                        <title>OpenMage Magento</title>
+                        <title>OpenMage</title>
                         <path class="ba"
                               d="m11,3.25l34,0a8,8 0 0 1 8,8l0,34a0,0 0 0 1 0,0l-42,0a0,0 0 0 1 0,0l0,-42a0,0 0 0 1 0,0z"/>
                         <text class="bb" id="svg_2" x="0" y="47">
@@ -135,7 +133,7 @@
                                 <div class="nav-section-title">API</div>
                                 <ul>
                                     <li class=" " role="menuitem">
-                                        <a href="/guides/v19.x/">Get Started with Magento Web APIs</a>
+                                        <a href="/guides/v19.x/">Get Started with OpenMage Web APIs</a>
                                     </li>
                                     <li class=" " role="menuitem">
                                         <a href="/guides/v19.x/api/rest-api-index.html">REST API Reference</a>
@@ -210,34 +208,34 @@
                     <h4 class="guide-title">Developer Guide</h4>
                     <div class="collapsible-navigation">
                         <ul>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-1.html">
                                     Introduction to OpenMage
                                 </a>
                             </li>
-                            <li class=" " role="menuitem">
+                            <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-2.html">
                                     The OpenMage Config
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-3.html">
-                                    OpenMage Controller Dispatch
+                                    Controller Dispatch
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-4.html">
-                                    OpenMage Layouts, Blocks and Templates
+                                    Layouts, Blocks and Templates
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-5.html">
-                                    OpenMage Models and ORM Basics
+                                    Models and ORM Basics
                                 </a>
                             </li>
                             <li class="" role="menuitem">
                                 <a href="{{ site.v1xgdeurl }}/magefordev/mage-for-dev-6.html">
-                                    OpenMage Setup Resources
+                                    Setup Resources
                                 </a>
                             </li>
                             <li class="" role="menuitem">
@@ -262,11 +260,21 @@ <h4 class="guide-title">Developer Guide</h4>
                         <h1 class="page-heading">Varien Data Collections</h1>
                     </section>
 
-                    <p class="para1">Originally, as a PHP programmer, if you wanted to collect together a group of related variables you had one choice, the venerable <a href="http://us.php.net/manual/en/language.types.array.php">Array</a>.  While it shares a name with C's array of memory addresses, a PHP array is a general purpose dictionary like object combined with the behaviors of a numerically indexed mutable array.</p>
+                    <p class="para1">Originally, as a PHP programmer, if you wanted to collect together a group of
+                        related variables you had one choice, the venerable <a
+                                href="http://us.php.net/manual/en/language.types.array.php">Array</a>. While it shares a
+                        name with C's array of memory addresses, a PHP array is a general purpose dictionary like object
+                        combined with the behaviors of a numerically indexed mutable array.</p>
 
-                    <p>In other languages the choice isn't so simple.  You have <a href="http://en.wikipedia.org/wiki/List_of_data_structures#Linear_data_structures">multiple data structures</a> to chose from, each offering particular advantages in storage, speed and semantics.  The PHP philosophy was to remove this choice from the client programmer and give them one useful data structure that was "good enough".  </p>
+                    <p>In other languages the choice isn't so simple. You have <a
+                            href="http://en.wikipedia.org/wiki/List_of_data_structures#Linear_data_structures">multiple
+                        data structures</a> to chose from, each offering particular advantages in storage, speed and
+                        semantics. The PHP philosophy was to remove this choice from the client programmer and give them
+                        one useful data structure that was "good enough". </p>
 
-                    <p>All of this is galling to a certain type of software developer, and PHP 5 set out to change the status quo by offering built-in classes and interfaces that allow you to create your own data structures.  </p>
+                    <p>All of this is galling to a certain type of software developer, and PHP 5 set out to change the
+                        status quo by offering built-in classes and interfaces that allow you to create your own data
+                        structures. </p>
 
                     <pre>
 $array = new ArrayObject();
@@ -275,9 +283,17 @@ <h1 class="page-heading">Varien Data Collections</h1>
 $collection[] = 'bar';
 </pre>
 
-                    <p>While this is still galling to a certain type of software developer, as you don't have access to low level implementation details, you do have the ability to create array-like Objects with methods that encapsulate specific functionality.  You can also setup rules to offer a level of type safety by only allowing certain kinds of Objects into your Collection.</p>
+                    <p>While this is still galling to a certain type of software developer, as you don't have access to
+                        low level implementation details, you do have the ability to create array-like Objects with
+                        methods that encapsulate specific functionality. You can also setup rules to offer a level of
+                        type safety by only allowing certain kinds of Objects into your Collection.</p>
 
-                    <p>It should come as no surprise that Magento offers you a number of these Collections.  In fact, every Model object that follows the Magento interfaces gets a Collection type for free.  Understanding how these Collections work is a key part to being an effective Magento programmer.  We're going to take a look at Magento Collections, starting from the bottom and working our way up.  Set up a <a href="http://alanstorm.com/magento_controller_hello_world">controller action</a> where you can run arbitrary code, and let's get started.</p>
+                    <p>It should come as no surprise that OpenMage offers you a number of these Collections. In fact,
+                        every Model object that follows the OpenMage interfaces gets a Collection type for free.
+                        Understanding how these Collections work is a key part to being an effective OpenMage programmer.
+                        We're going to take a look at OpenMage Collections, starting from the bottom and working our way
+                        up. Set up a <a href="http://alanstorm.com/magento_controller_hello_world">controller action</a>
+                        where you can run arbitrary code, and let's get started.</p>
 
                     <h2 id="a-collection-of-things">A Collection of Things</h2>
 
@@ -298,13 +314,18 @@ <h2 id="a-collection-of-things">A Collection of Things</h2>
 $thing_3->setAge(7);
 </pre>
 
-                    <p>The <tt>Varien_Object</tt> class defines the object all Magento Models inherit from.  This is a common pattern in object oriented systems, and ensures you'll always have a way to easily add methods/functionally to <strong>every</strong> object in your system without having to edit every class file.</p>
+                    <p>The <tt>Varien_Object</tt> class defines the object all OpenMage Models inherit from. This is a
+                        common pattern in object oriented systems, and ensures you'll always have a way to easily add
+                        methods/functionally to <strong>every</strong> object in your system without having to edit
+                        every class file.</p>
 
-                    <p>Any Object that extends from <tt>Varien_Object</tt> has magic getter and setters that can be used to set data properties. Give this a try</p>
+                    <p>Any Object that extends from <tt>Varien_Object</tt> has magic getter and setters that can be used
+                        to set data properties. Give this a try</p>
 
                     <pre>var_dump($thing_1->getName());</pre>
 
-                    <p>If you don't know what the property name you're after is, you can pull out all the data as an array</p>
+                    <p>If you don't know what the property name you're after is, you can pull out all the data as an
+                        array</p>
 
                     <pre>var_dump($thing_3->getData());</pre>
 
@@ -318,13 +339,16 @@ <h2 id="a-collection-of-things">A Collection of Things</h2>
 'age' => int 7
 </pre>
 
-                    <p>Notice the property named "last_name"?  If there's an underscore separated property, you camel case it if you want to use the getter and setter magic.</p>
+                    <p>Notice the property named "last_name"? If there's an underscore separated property, you camel
+                        case it if you want to use the getter and setter magic.</p>
 
                     <pre>$thing_1->setLastName('Smith');</pre>
 
-                    <p>The ability to do these kinds of things is part of the power of PHP5, and the development style a certain class of people mean when they say "Object Oriented Programming".</p>
+                    <p>The ability to do these kinds of things is part of the power of PHP5, and the development style a
+                        certain class of people mean when they say "Object Oriented Programming".</p>
 
-                    <p>So, now that we have some Objects, let's add them to a Collection.  Remember, a Collection is like an Array, but is defined by a PHP programmer.  </p>
+                    <p>So, now that we have some Objects, let's add them to a Collection. Remember, a Collection is like
+                        an Array, but is defined by a PHP programmer. </p>
 
                     <pre>
 $collection_of_things = new Varien_Data_Collection();
@@ -334,9 +358,11 @@ <h2 id="a-collection-of-things">A Collection of Things</h2>
     ->addItem($thing_3);
 </pre>
 
-                    <p>The <tt>Varien_Data_Collection</tt> is the Collection that most Magento data Collections inherit from.  Any method you can call on a <tt>Varien_Data_Collection</tt> you can call on Collections higher up the chain (We'll see more of this later)</p>
+                    <p>The <tt>Varien_Data_Collection</tt> is the Collection that most OpenMage data Collections inherit
+                        from. Any method you can call on a <tt>Varien_Data_Collection</tt> you can call on Collections
+                        higher up the chain (We'll see more of this later)</p>
 
-                    <p>What can we do with a Collection?  For one, with can use <tt>foreach</tt> to iterate over it</p>
+                    <p>What can we do with a Collection? For one, with can use <tt>foreach</tt> to iterate over it</p>
 
                     <pre>
 foreach($collection_of_things as $thing)
@@ -352,7 +378,7 @@ <h2 id="a-collection-of-things">A Collection of Things</h2>
 var_dump($collection_of_things->getLastItem()->getData());
 </pre>
 
-                    <p>Want your Collection data as XML?  There's a method for that</p>
+                    <p>Want your Collection data as XML? There's a method for that</p>
 
                     <pre>var_dump( $collection_of_things->toXml() );</pre>
 
@@ -360,7 +386,7 @@ <h2 id="a-collection-of-things">A Collection of Things</h2>
 
                     <pre>var_dump($collection_of_things->getColumnValues('name'));</pre>
 
-                    <p>The team at Magento have even given us some rudimentary filtering capabilities.</p>
+                    <p>The team at OpenMage have even given us some rudimentary filtering capabilities.</p>
 
                     <pre>var_dump($collection_of_things->getItemsByColumnValue('name','Spot'));</pre>
 
@@ -369,7 +395,9 @@ <h2 id="a-collection-of-things">A Collection of Things</h2>
                     <h2 id="model-collections">Model Collections</h2>
                     <p>So, this is an interesting exercise, but why do we care? </p>
 
-                    <p>We care because all of Magento's built in data Collections inherit from this object.  That means if you have, say, a product Collection you can do the same sort of things.  Let's take a look </p>
+                    <p>We care because all of OpenMage's built in data Collections inherit from this object. That means
+                        if you have, say, a product Collection you can do the same sort of things. Let's take a
+                        look </p>
 
                     <pre>
 public function testAction()
@@ -379,11 +407,22 @@ <h2 id="model-collections">Model Collections</h2>
 }
 </pre>
 
-                    <p>Most Magento Model objects have a method named <tt>getCollection</tt> which will return a collection that, by default, is initialized to return every Object of that type in the system.</p>
+                    <p>Most OpenMage Model objects have a method named <tt>getCollection</tt> which will return a
+                        collection that, by default, is initialized to return every Object of that type in the system.
+                    </p>
 
-                    <p><strong>A Quick Note:</strong>  Magento's Data Collections contain a lot of complicated logic that handles when to use an index or cache, as well as the logic for the EAV entity system.  Successive method calls to the same Collection over its life can often result in unexpected behavior.  Because of that, all the of the following examples are wrapped in a single method action.  I'd recommend doing the same while you're experimenting.  Also, <a href="http://xdebug.org/">XDebug's</a> <tt>var_dump</tt> is a godsend when working with Magento Objects and Collections, as it will (usually) intelligently short circuit showing hugely recursive Objects, but still display a useful representation of the Object structure to you.</p>
+                    <p><strong>A Quick Note:</strong> OpenMage's Data Collections contain a lot of complicated logic that
+                        handles when to use an index or cache, as well as the logic for the EAV entity system.
+                        Successive method calls to the same Collection over its life can often result in unexpected
+                        behavior. Because of that, all the of the following examples are wrapped in a single method
+                        action. I'd recommend doing the same while you're experimenting. Also, <a
+                                href="http://xdebug.org/">XDebug's</a> <tt>var_dump</tt> is a godsend when working with
+                        OpenMage Objects and Collections, as it will (usually) intelligently short circuit showing hugely
+                        recursive Objects, but still display a useful representation of the Object structure to you.</p>
 
-                    <p>The products Collection, as well as many other Magento Collections, also have the <tt>Varien_Data_Collection_Db</tt> class in their ancestor chain. This gives us a lot of useful methods.  For example, if you want to see the select statement your Collection is using</p>
+                    <p>The products Collection, as well as many other OpenMage Collections, also have the <tt>Varien_Data_Collection_Db</tt>
+                        class in their ancestor chain. This gives us a lot of useful methods. For example, if you want
+                        to see the select statement your Collection is using</p>
 
                     <pre>
 public function testAction()
@@ -404,7 +443,8 @@ <h2 id="model-collections">Model Collections</h2>
 ...
 </pre>
 
-                    <p>Whoops! Since Magento is using the <tt>Zend</tt> database abstraction layer, your Select is also an Object.  Let's see that as a more useful string. </p>
+                    <p>Whoops! Since OpenMage is using the <tt>Zend</tt> database abstraction layer, your Select is also
+                        an Object. Let's see that as a more useful string. </p>
 
                     <pre>
 public function testAction()
@@ -431,7 +471,12 @@ <h2 id="model-collections">Model Collections</h2>
 price_index.website_id = '1' AND price_index.customer_group_id = 0'
 </pre>
 
-                    <p>The discrepancy depends on which attributes you're selecting, as well as the aforementioned indexing and cache.  If you've been following along with the other articles in this series,  you know that many Magento models (including the Product Model) use an <a href="http://en.wikipedia.org/wiki/EAV">EAV</a> system.  By default, a EAV Collection will not include all of an Object's attributes.  You can add them all by using the addAttributeToSelect method</p>
+                    <p>The discrepancy depends on which attributes you're selecting, as well as the aforementioned
+                        indexing and cache. If you've been following along with the other articles in this series, you
+                        know that many OpenMage models (including the Product Model) use an <a
+                                href="http://en.wikipedia.org/wiki/EAV">EAV</a> system. By default, a EAV Collection
+                        will not include all of an Object's attributes. You can add them all by using the
+                        addAttributeToSelect method</p>
 
                     <pre>
 $collection_of_products = Mage::getModel('catalog/product')
@@ -460,7 +505,9 @@ <h2 id="model-collections">Model Collections</h2>
 
                     <h2 id="lazy-loading">Lazy Loading</h2>
 
-                    <p>One thing that will trip up PHP developers new to Magento's ORM system is <strong>when</strong> Magento makes its database calls.  When you're writing literal SQL, or even when you're using a basic ORM system, SQL calls are often made immediately when instantiating an Object.</p>
+                    <p>One thing that will trip up PHP developers new to OpenMage's ORM system is <strong>when</strong>
+                        OpenMage makes its database calls. When you're writing literal SQL, or even when you're using a
+                        basic ORM system, SQL calls are often made immediately when instantiating an Object.</p>
 
                     <pre>
 $model = new Customer();
@@ -468,14 +515,17 @@ <h2 id="lazy-loading">Lazy Loading</h2>
 echo 'Done'; //execution continues
 </pre>
 
-                    <p>Magento doesn't work that way.  Instead, the concept of <a href="http://en.wikipedia.org/wiki/Lazy_loading">Lazy Loading</a> is used.  In simplified terms, Lazy loading means that no SQL calls are made until the client-programmer needs to access the data.  That means when you do something something like this</p>
+                    <p>OpenMage doesn't work that way. Instead, the concept of <a
+                            href="http://en.wikipedia.org/wiki/Lazy_loading">Lazy Loading</a> is used. In simplified
+                        terms, Lazy loading means that no SQL calls are made until the client-programmer needs to access
+                        the data. That means when you do something something like this</p>
 
                     <pre>
 $collection_of_products = Mage::getModel('catalog/product')
     ->getCollection();
 </pre>
 
-                    <p>Magento actually hasn't gone out to the database yet.  You can safely add attributes later</p>
+                    <p>OpenMage actually hasn't gone out to the database yet. You can safely add attributes later</p>
 
                     <pre>
 $collection_of_products = Mage::getModel('catalog/product')
@@ -483,13 +533,20 @@ <h2 id="lazy-loading">Lazy Loading</h2>
 $collection_of_products->addAttributeToSelect('meta_title');
 </pre>
 
-                    <p>and not have to worry that Magento is making a database query each time a new attribute is added.  The database query will not be made until you attempt to access an item in the Collection.</p>
+                    <p>and not have to worry that OpenMage is making a database query each time a new attribute is added.
+                        The database query will not be made until you attempt to access an item in the Collection.</p>
 
-                    <p>In general, try not to worry too much about the implementation details in your day to day work.  It's good to know that there's s SQL backend and Magento is doing SQLy things, but when you're coding up a feature try to forget about it, and just treat the objects as block boxes that do what you need.  </p>
+                    <p>In general, try not to worry too much about the implementation details in your day to day work.
+                        It's good to know that there's s SQL backend and OpenMage is doing SQLy things, but when you're
+                        coding up a feature try to forget about it, and just treat the objects as block boxes that do
+                        what you need. </p>
 
                     <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 
-                    <p>The most important method on a database Collection is <tt>addFieldToFilter</tt>.  This adds your <tt>WHERE</tt> clauses to the SQL query being used behind the scenes.  Consider this bit of code, run against the sample data database (substitute your own SKU is you're using a different set of product data)</p>
+                    <p>The most important method on a database Collection is <tt>addFieldToFilter</tt>. This adds your
+                        <tt>WHERE</tt> clauses to the SQL query being used behind the scenes. Consider this bit of code,
+                        run against the sample data database (substitute your own SKU is you're using a different set of
+                        product data)</p>
 
                     <pre>
 public function testAction()
@@ -504,9 +561,13 @@ <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 }
 </pre>
 
-                    <p>The first parameter of <tt>addFieldToFilter</tt> is the attribute you wish to filter by.  The second is the value you're looking for. Here's we're adding a <tt>sku</tt> filter for the value <tt>n2610</tt>.</p>
+                    <p>The first parameter of <tt>addFieldToFilter</tt> is the attribute you wish to filter by. The
+                        second is the value you're looking for. Here's we're adding a <tt>sku</tt> filter for the value
+                        <tt>n2610</tt>.</p>
 
-                    <p>The second parameter can also be used to specify the <strong>type</strong> of filtering you want to do. This is where things get a little complicated, and worth going into with a little more depth.</p>
+                    <p>The second parameter can also be used to specify the <strong>type</strong> of filtering you want
+                        to do. This is where things get a little complicated, and worth going into with a little more
+                        depth.</p>
 
                     <p>So by default, the following </p>
 
@@ -516,7 +577,7 @@ <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 
                     <pre>WHERE sku = "n2610"</pre>
 
-                    <p>Take a look for yourself.  Running the following</p>
+                    <p>Take a look for yourself. Running the following</p>
 
                     <pre>
 public function testAction()
@@ -534,7 +595,8 @@ <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 
                     <pre>SELECT `e`.* FROM `catalog_product_entity` AS `e` WHERE (e.sku = 'n2610')'</pre>
 
-                    <p>Keep in mind, this can get complicated fast if you're using an EAV attribute.  Add an attribute</p>
+                    <p>Keep in mind, this can get complicated fast if you're using an EAV attribute. Add an
+                        attribute</p>
 
                     <pre>
 var_dump(
@@ -565,9 +627,14 @@ <h2 id="filtering-database-collections">Filtering Database Collections</h2>
 
                     <h2 id="other-comparison-operators">Other Comparison Operators</h2>
 
-                    <p>I'm sure you're wondering "what if I want something other than an equals by query"?  Not equal, greater than, less than, etc.  The <tt>addFieldToFilter</tt> method's second parameter has you covered there as well.  It supports an alternate syntax where, instead of passing in a string, you pass in a single element Array.  </p>
+                    <p>I'm sure you're wondering "what if I want something other than an equals by query"? Not equal,
+                        greater than, less than, etc. The <tt>addFieldToFilter</tt> method's second parameter has you
+                        covered there as well. It supports an alternate syntax where, instead of passing in a string,
+                        you pass in a single element Array. </p>
 
-                    <p>The key of this array is the <strong>type</strong> of comparison you want to make.  The value associated with that key is the value you want to filter by.  Let's redo the above filter, but with this explicit syntax</p>
+                    <p>The key of this array is the <strong>type</strong> of comparison you want to make. The value
+                        associated with that key is the value you want to filter by. Let's redo the above filter, but
+                        with this explicit syntax</p>
 
                     <pre>public function testAction()
 {
@@ -585,9 +652,13 @@ <h2 id="other-comparison-operators">Other Comparison Operators</h2>
 
                     <pre>addFieldToFilter('sku',array('eq'=>'n2610'))</pre>
 
-                    <p>As you can see, the second parameter is a PHP Array.  Its key is <tt>eq</tt>, which stands for <em>equals</em>.  The value for this key is <tt>n2610</tt>, which is the value we're filtering on.</p>
+                    <p>As you can see, the second parameter is a PHP Array. Its key is <tt>eq</tt>, which stands for
+                        <em>equals</em>. The value for this key is <tt>n2610</tt>, which is the value we're filtering
+                        on.</p>
 
-                    <p>Magento has a number of these english language like filters that will bring a <a href="http://www.shlomifish.org/lecture/Perl/Newbies/lecture1/conditionals/string.html">tear of remembrance</a> (and perhaps pain) to any old perl developers in the audience.</p>
+                    <p>OpenMage has a number of these english language like filters that will bring a <a
+                            href="http://www.shlomifish.org/lecture/Perl/Newbies/lecture1/conditionals/string.html">tear
+                        of remembrance</a> (and perhaps pain) to any old perl developers in the audience.</p>
 
                     <p>Listed below are all the filters, along with an example of their SQL equivalents.</p>
 
@@ -645,7 +716,8 @@ <h2 id="other-comparison-operators">Other Comparison Operators</h2>
 
                     <h3>in, nin, find_in_set</h3>
 
-                    <p>The <tt>in</tt>, <tt>nin</tt> and <tt>finset</tt> conditionals allow you to pass in an Array of values.  That is, the value portion of your filter array is itself allowed to be an array.  </p>
+                    <p>The <tt>in</tt>, <tt>nin</tt> and <tt>finset</tt> conditionals allow you to pass in an Array of
+                        values. That is, the value portion of your filter array is itself allowed to be an array. </p>
 
                     <pre>
 array("in"=>array('n2610','ABC123')
@@ -654,7 +726,10 @@ <h3>in, nin, find_in_set</h3>
 
                     <h3>notnull, null</h3>
 
-                    <p>The keyword NULL is special in most flavors of SQL. It typically won't play nice with the standard equality (<tt>=</tt>) operator.  Specifying <tt>notnull</tt> or <tt>null</tt> as your filter type will get you the correct syntax for a NULL comparison while ignoring whatever value you pass in</p>
+                    <p>The keyword NULL is special in most flavors of SQL. It typically won't play nice with the
+                        standard equality (<tt>=</tt>) operator. Specifying <tt>notnull</tt> or <tt>null</tt> as your
+                        filter type will get you the correct syntax for a NULL comparison while ignoring whatever value
+                        you pass in</p>
 
                     <pre>
 array("notnull"=>true)
@@ -662,7 +737,10 @@ <h3>notnull, null</h3>
 </pre>
 
                     <h3>from - to filter</h3>
-                    <p>This is another special format that breaks the standard rule.  Instead of a single element array, you specify a two element array.  One element has the key <tt>from</tt>, the other element has the key <tt>to</tt>.  As the keys indicated, this filter allows you to construct a from/to range without having to worry about greater than and less than symbols</p>
+                    <p>This is another special format that breaks the standard rule. Instead of a single element array,
+                        you specify a two element array. One element has the key <tt>from</tt>, the other element has
+                        the key <tt>to</tt>. As the keys indicated, this filter allows you to construct a from/to range
+                        without having to worry about greater than and less than symbols</p>
 
                     <pre>
 public function testAction
@@ -682,7 +760,9 @@ <h3>from - to filter</h3>
 
                     <h2 id="and-or-or">AND or OR, or is that OR and AND?</h2>
 
-                    <p>Finally, we come to the boolean operators.  It's the rare moment where we're only filtering by one attribute.  Fortunately, Magento's Collections have us covered.  You can chain together multiple calls to <tt>addFieldToFilter</tt> to get a number of "AND" queries.</p>
+                    <p>Finally, we come to the boolean operators. It's the rare moment where we're only filtering by one
+                        attribute. Fortunately, OpenMage's Collections have us covered. You can chain together multiple
+                        calls to <tt>addFieldToFilter</tt> to get a number of "AND" queries.</p>
 
                     <pre>
 function testAction()
@@ -697,13 +777,18 @@ <h2 id="and-or-or">AND or OR, or is that OR and AND?</h2>
 }
 </pre>
 
-                    <p>By chaining together multiple calls as above, we'll produce a where clause that looks something like the following</p>
+                    <p>By chaining together multiple calls as above, we'll produce a where clause that looks something
+                        like the following</p>
 
                     <pre>WHERE (e.sku like 'a%') AND (e.sku like 'b%')</pre>
 
-                    <p>To those of you that just raised your hand, yes, the above example would always return 0 records. No sku can begin with BOTH an <tt>a</tt> and a <tt>b</tt>.  What we probably want here is an <tt>OR</tt> query.  This brings us to another confusing aspect of <tt>addFieldToFilter</tt>'s second parameter.</p>
+                    <p>To those of you that just raised your hand, yes, the above example would always return 0 records.
+                        No sku can begin with BOTH an <tt>a</tt> and a <tt>b</tt>. What we probably want here is an <tt>OR</tt>
+                        query. This brings us to another confusing aspect of <tt>addFieldToFilter</tt>'s second
+                        parameter.</p>
 
-                    <p>If you want to build an <tt>OR</tt> query, you need to pass an Array of filter Arrays in as the second parameter.  I find it's best to assign your individual filter Arrays to variables </p>
+                    <p>If you want to build an <tt>OR</tt> query, you need to pass an Array of filter Arrays in as the
+                        second parameter. I find it's best to assign your individual filter Arrays to variables </p>
 
                     <pre>
 public function testAction()
@@ -737,7 +822,9 @@ <h2 id="and-or-or">AND or OR, or is that OR and AND?</h2>
 
                     <h2 id="wrap-up">Wrap Up</h2>
 
-                    <p>You're now a Magento developer walking around with some serious firepower.  Without having to write a single line of SQL you now know how to query Magento for any Model your store or application might need. </p>
+                    <p>You're now a OpenMage developer walking around with some serious firepower. Without having to
+                        write a single line of SQL you now know how to query OpenMage for any Model your store or
+                        application might need. </p>
 
                 </div>
                 <!-- /.content-wrap -->
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-7.html b/guides/m1x/magefordev/mage-for-frontend-dev-7.html
index 3f50c436c8..2a28c4d496 100644
--- a/guides/m1x/magefordev/mage-for-frontend-dev-7.html
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-7.html
@@ -476,7 +476,7 @@ <h2>Using Media Query Breakpoints</h2>
 @include bp(min-width, $bp-medium+1) {
     /* These styles will only display on viewports larger than or equal to 771px (770px + 1px) */
 }
-    </pre></code>
+/pre></code>
                     <p>generates this CSS:</p>
                     <code><pre>
 @media only screen and (max-width: 770px) {
@@ -485,7 +485,7 @@ <h2>Using Media Query Breakpoints</h2>
 @media only screen and (min-width: 771px) {
     /* These styles will only display on viewports larger than or equal to 771px (770px + 1px) */
 }
-    </pre></code>
+</pre></code>
                     <p>The breakpoint variables are intended to be used with <tt>max-width</tt> by default. When you use the breakpoint
                         with <tt>min-width</tt>, you should add a pixel <tt>($bp-medium+1)</tt> so the <tt>min-width</tt> and <tt>max-width</tt>
                         styles don't both get applied to the same viewport size.</p>
diff --git a/guides/m1x/magefordev/mage-for-frontend-dev-8.html b/guides/m1x/magefordev/mage-for-frontend-dev-8.html
index 952f437871..07a745027e 100644
--- a/guides/m1x/magefordev/mage-for-frontend-dev-8.html
+++ b/guides/m1x/magefordev/mage-for-frontend-dev-8.html
@@ -299,7 +299,7 @@ <h1 id="remove-sample-content" class="page-heading">Removing Sample Data Assets<
         &lt;/reference&gt;
     &lt;/default&gt;
 &lt;/layout&gt;
-            </pre></code>
+</pre></code>
                             The preceding XML:
                             <ul>
                                 <li>Removes the Madison Island CSS files</li>
@@ -318,7 +318,7 @@ <h1 id="remove-sample-content" class="page-heading">Removing Sample Data Assets<
                                 (300,400,500,700,600) because the responsive theme uses each of those font weights.</p>
                             <code><pre>
 &lt;action method="addLinkRel"&gt;&lt;rel&gt;stylesheet&lt;/rel&gt;&lt;href&gt;//fonts.googleapis.com/css?family=Raleway:300,400,500,700,600&lt;/href&gt;&lt;/action&gt;
-                </pre></code>
+</pre></code>
                         </li>
                     </ol>
                 </div>