This document discusses a front-end perspective and approach for solving complex UI designs. It outlines a process for developing templates that allows incremental UI changes with minimal backend configuration. The process involves UX design, mobile strategy, template analysis, UI development, testing, and syncing the UI with the Magnolia CMS backend. It recommends tools like Grunt, Bower, and Yeoman for streamlining front-end development. The goal is to provide a UI sandbox that simplifies template configuration and reduces configuration issues.
47. .
âââ global
â  âââ areas
â  â  âââ footer.swig
â  â  âââ htmlHeader.swig
â  â  âââ logo.swig
â  â  âââ mainArea.swig
â  â  âââ navigation.swig
â  âââ components
â  â  âââ genericContent.swig
â  âââ macros
â  âââ calculator.swig
âââ layouts
â  âââ about.swig
â  âââ generic.swig
â  âââ homepage.swig
âââ pages
âââ homepage
âââ areas
â  âââ callout.swig
â  âââ features.swig
â  âââ products.swig
â  âââ welcome.swig
â  âââ whoWeAre.swig
âââ components
âââ featureItem.swig
68. 01
UX/Design
02
Mobile Strategy
03
Template Analysis
04
UI Development
05
UI Build / QA
06
UI-Magnolia Sync
07
Magnolia Development
08
Final Testing
A process to allow
incremental UI changes
with minimal conïŹguration
or backend changes
106. âConvention over conïŹguration is a software
design paradigm which seeks to decrease the
number of decisions that developers need to
make, gaining simplicity, but not necessarily
losing ïŹexibility.â