=head1 Complete Programming
+This document describes the method Kephra is developed with.
+Its highest aim is to have at all times a usable program with the
+highest quality at all levels while still letting programming be fun.
+I hate strict rules or when people tell me what to do and I make fun of them
+when they produce wild theories with three letter acronyms that try to be
+the answer to everything. But now I am standing here, trying to "sell" you
+yet another programming methodology. That irony, isn't it?
+Well, several reasons brought me there.
+1.) All methodologies I know of overlook several aspects of the product.
+ That includes even "documentation driven development",
+ which gave important impulses for the creation of CP.
+2.) I always wanted a sane balance between the old bureaucratic waterfall method
+ and the way too shortsighted, modern extreme or agile programming.
-Highest aim is the overall user experience.
+Highest aim is the overall user experience.
This means not only (almost) no bugs and good documentation,
+but also a coherent, consistent application that is a joy to use.
+=head2 Phases of Development
+=head3 Early Development
+=head3 Normal Development
-I coined the method we develope Kephra with, because its different enough
-from most other stuff that was written about.