asciidoc/Developer-documentation.asciidoc

@@ -11,11 +11,20 @@ is for you.
 When invoking the generator, it will (roughly) perform the following actions:
 
 .Basic invocation workflow
-image::invocation_workflow.png[]
+image::invocation_workflow.png[width=90%, align=center, link={imagesdir}/invocation_workflow.png]
 
-On a coarse scale the generator is structured using the following packages:
+Each of these steps has a corresponding Scala class (called _Services_ hereafter) to take care of
+it. So, when extending the generator there are two basic approaches:
 
-image::architecture.png[]
+[loweralpha]
+. modifying one of the _Services_ (either directly or by means of subclassing)
+. intercepting the workflow by adding more _Services_
+
+To give you a rough idea of what _Services_ are available and where they will be located, here is an
+overview of the generator's architecture:
+
+.The coarse-scale architecture of the generator
+image::architecture.png[width=90%, align=center, link={imagesdir}/architecture.png]
 
 == The Scala abstract class representation