webschuur.com

In many database driven applications (web-apps) you need some sort of user-system. A system to manage log-in facilities and rights management etceteras. A general “mistake” I see all over the place is that a user equals a person, in these systems. I decided to make a decent normalised concept for this and document it for once :).

The idea is that there are two separate entities: a user and a person. You may, or may not couple them, either now, or later. The benefit is that, using this concept, you have a choice:

This is a morphological overview, to display all te options for deploying a Drupal (and/ or Joomla!! or any other CMS) hosting system.

The way one should read it

In the first vertical column all “tasks” we need to perform are listed, chopped up into the smallest possible unit. Then next to each of these we render all possible tools and solutions for each task, without taking in consideration how ill-suited these tools may be, nor how well they can, or will co-operate. By refusing to look at possible solutions yet, we can make sure that we actually list all options.

Codename kiss. (Because a kiss turns the frog into a prince.)

To develop a theme system for Railfrog, we need to look at other systems, reuse existing libraries, but most of all, DoI It Right and Futureproof.
Themes must be easy to develop for designers, powerful to use for overriding defaults, and most of all it must look gorgeaus and be very accessible. The engine, or theme system, should at the very least allow this beauty and accessibilty, but if possible, should make developing such themes simple!

See the attached PDF for the full proposal.