Before you set up your r3 project, there are several things to consider:
Directory structure can be flat or grouped by common items. If grouped by common items you can share translations and templates.
Amount of translation needing to be done
Separation of application logic and view. r3 is agnostic about the whether your view layer is separated from the your application logic, but structurally, r3 best suits a system that has a clean distinction between application and view logic.
This and the following chapter show how to use r3 using the example of creating a simple r3 project. r3 is to be able to manage multiple websites in multiple languages, so our example project creates three separate (but related) web products in four different languages.
Our example consists of the following products:
cookery
wine
cars
The products are built for the following countries (intls):
USA (us)
French Canada (ca)
France (fr)
Japan (jp)
There is a good deal of interrelationship between some of these
products and international sites (intls). For example, wine and
cookery, can share similar styles (one could be a sub site of
the other). Concerning intl, ca shares its language with
fr and much of its culture with us. However,
cars and cookery have little in common, as is the
case with ca and jp.
Combining these two axes gives us 3 * 4 = 12 web sites to build:
cookery/us
cookery/ca
cookery/fr
cookery/jp
wine/us
wine/ca
wine/fr
wine/jp
cars/us
cars/ca
cars/fr
cars/jp
To reduce complexity, each website will use R3 on a sngle page. Each page shares a simple, common structure:
Each component of that page has its own template:
With this structure in mind, the next chapter, Using the r3 Command Line Interface, explains how to use the command-line interface.