Cracking Drupal®: A Drop in the Bucket

B.2. Step 2: Designing and Building the Architecture

At this point, you can start with a bilingual site, from the point of view of both l10n and of i18n, and build a functional foundation for the application you have in mind.

Let's take a quick look at the functional scope and then map that to a domain model, including business objects and Drupal modules.

B.2.1. Application Scope and Domain

Before attempting to build any website, it is very important to follow a certain workflow. Mapping out the scope and domain will allow for the production of a very significant amount of cheap (mental) development and will simplify the whole process, since that process concretely comprises a series of implementation steps involving design and implementation. This is in opposition to the expensive kind of development, which you need to avoid like the plague, because it involves doing work and then throwing it away as a substitute for thinking and dialog, as well as building without a plan and changing high-impact architectural components during or even after implementation.

A little scope and domain work clarifies things and simplifies development.

Figure B-7 shows the scope and functionality of what is required for the mini-application.

Figure B-8 shows the domain of classes and objects required to implement the mini-application, relating these in general to Drupal modules.

Figure B.7. Figure B-7

Figure B.8. Figure B-8

B.2.2. Creating Roles and Users

The following best practices make ...