-Just in case you want to touch the Kephra sources - this document explains
-you where to find what and how it does work together.
+If you want to touch the Kephra sources -
+this document explains where to find what and how does it all work together.
+In case you learn better by code - start at Kephra::API.
+In each file is only one package with exactly the name as the files.
+With every directory you go deeper into the tree the modules will get more
+specific. Thats why the directory Kephra has only the most common tools
+* API - API for plugins, most cross module calls, central data structures
+* Bar - visual units made of one widget
+* Editor - editor window helper
+* Panel - with sizer assembled visual parts
+* Part - functional units
+* Default - built in fall back configs when certain files are in trouble
+* Document - document properties
+* Edit - text manipulation functions
+* Files - all sorts of IO
+* Plugins - namespace of users extentions
If you want to leave the recommended ways as proposed by the API and call
functions or data directly (or even better you want to help to develope Kephra) ...
=head3 Explained In Detail
contains just the init process: