section intros

6 files changed, 42 insertions, 25 deletions

diff --git a/root/articles/mmmfs/conclusion/text$markdown+sidenotes.md b/root/articles/mmmfs/conclusion/text$markdown+sidenotes.md
index 0780b23..55052be 100644
--- a/root/articles/mmmfs/conclusion/text$markdown+sidenotes.md
+++ b/root/articles/mmmfs/conclusion/text$markdown+sidenotes.md
@@ -1,3 +1,14 @@
 # 7. conclusion
 
 <div class="well well-warning">[section under construction]</div>
+
+In the beginning of this thesis multiple downsides of the most widely used end-user computing systems have been
+demonstrated and attributed to an over-reliance on a set of design paradigms that do not align well with the goal of
+empowering users. On the other hand, it has been shown that many well-recognized historic systems were designed with
+this goal in mind.
+
+Based on the aspirations and appraoches of these historic systems, a framework for the evaluation of empowering end-user
+computing systems was developed alongside one such system itself. While the proposed system has been shown to have many
+flaws and limitations of its own, and is not currently viable as a tool for end-users, it serves to demonstrate the
+feasiblity of type coercion and the file system as a focus point for new end-user computing systems, and provides a
+reference point for further research.
diff --git a/root/articles/mmmfs/evaluation/text$markdown+sidenotes.md b/root/articles/mmmfs/evaluation/text$markdown+sidenotes.md
index 27181a8..2eb3acf 100644
--- a/root/articles/mmmfs/evaluation/text$markdown+sidenotes.md
+++ b/root/articles/mmmfs/evaluation/text$markdown+sidenotes.md
@@ -1,28 +1,24 @@
 # 6. evaluation
+In this section I will first take a look at the implementations of the examples for the use cases outlined above,
+and evaluate them with regard to the framework derived in the corresponding section above. After that, some general
+concerns and insights that have become apparent while developing the system and working with it will be reviewed.
 
 ## 6.1 examples
-In this section I will take a look at the implementations of the example for the use cases outlined above,
-and evaluate them with regard to the framework derived in the corresponding section above.
-
 ### 6.1.1 publishing and blogging
-Since mmmfs has grown out of the need for a versatile CMS for a personal publishing website, it is not surprising to
-see that it is still up to that job. Nevertheless it is worth taking a look at its strengths and weaknesses in this
-context:
+Since mmmfs has grown out of the need for a versatile content-management system for a personal website and blog, it is
+not surprising to see that it is still up to that job. Nevertheless it is worth taking a look at its strengths and
+weaknesses in this context:
 
 The system has proven itself perfect for publishing small- and medium-size articles and blog posts, especially for its
 ability to flexibly transclude content from any source. This includes diagrams (such as in this thesis),
 videos (as in the documentation in the appendix), but also less conventional media such as
 interactive diagrams<mmm-embed path="../references/aspect-ratios" wrap="sidenote"></mmm-embed> or twitter postings.
 
-<!-- @TODO -->
 On the other hand, the development of the technical framework for this thesis has posed greater challenges.
-In particular, the implementation of the reference and sidenote systems are brittle and uninspiring.
-
+While the reference and sidenote systems integrated well with the rest of the system, some features like automated
+table-of-contents and section numbering were less obvious to tackle and finally completed manually.
 This is mostly due to the approach of splitting up the thesis into a multitude of fileders, and the current lack of
-mechanisms to re-capture information spread throughout the resulting history effectively.
-Another issue is that the system is currently based on the presumption that content can and should be interpreted
-separately from its parent and context in most cases. This has made the implementation of sidenotes less idiomatic
-than initially anticipated.
+mechanisms to re-capture information spread throughout the resulting hierarchy effectively.
 
 ### 6.1.2 pinwall
 The pinwall example shows some strengths of the mmmfs system pretty convincingly.
@@ -73,8 +69,8 @@ more general `mmm/dom` type-interface, allowing for a greater variety of types o
 ## 6.2 general concerns
 While the system has proven pretty successful and moldable to the different use-cases that it has been tested in,
 there are also limitations in the proposed system that have become obvious in developing and working with the system.
-Some of these have been anticipated for some time and concrete research directions for solutions are apparent,
-while others may be intrinsic limitations in the approach taken.
+In this section these limitations will be discussed individually, and directions for further research and solutions will
+be given where apparent.
 
 ### 6.2.1 global set of converts
 In the current system, there is only a single, global set of *converts* that can be potentially applied to facets
diff --git a/root/articles/mmmfs/framework/text$markdown+sidenotes.md b/root/articles/mmmfs/framework/text$markdown+sidenotes.md
index 0df28c4..e85bf42 100644
--- a/root/articles/mmmfs/framework/text$markdown+sidenotes.md
+++ b/root/articles/mmmfs/framework/text$markdown+sidenotes.md
@@ -1,8 +1,10 @@
 # 3. evaluation framework
 
-In the following section, I will collect approaches and reviews of different end-user software systems from current
-literature, as well as derive and present my own requirements and guiding principles for the development of a new
-system.
+In this section, I will collect approaches and reviews of different end-user software systems from current literature,
+as well as derive and present my own requirements and guiding principles for the development of a new system.
+
+Firstly, I will take a look at a framework for evaluating end-user computing systems from literature, before presenting
+three concrete design principles and components for a new system.
 
 3.1 qualities of successful end-user computing
 ----------------------------------------------
diff --git a/root/articles/mmmfs/mmmfs/text$markdown+sidenotes.md b/root/articles/mmmfs/mmmfs/text$markdown+sidenotes.md
index 883af51..2b2263e 100644
--- a/root/articles/mmmfs/mmmfs/text$markdown+sidenotes.md
+++ b/root/articles/mmmfs/mmmfs/text$markdown+sidenotes.md
@@ -1,16 +1,18 @@
 # 4. system description
 
-`mmmfs` is a newly developed personal data storage and processing system. It was developed first as a tool for
-generating static websites, but has been extended with live interaction and introspection, as well as embedded
-editing capabilities as part of this work.
+Alongside this thesis a new end-user computing system has been developed together with the framework presented above.
+The system, `mmmfs`, is a personal data storage and processing system that was initially developed as a tool for
+generating static websites, but has now been extended with capabilities for live interaction and introspection, as well
+as embedded editing, as part of this work.
 
 mmmfs has been designed with a focus on data ownership for users. One of the main driving ideas is to unlock data
 from external data silos and file formats by making data available uniformly across different storage systems and
-formats. Secondly, computation and interactive elements are also integrated in the paradigm, so that mmmfs can be
-seamlessly extended and molded to the users needs.
+formats. Secondly, computation and interactive elements are also integrated in this paradigm, so that mmmfs can be
+seamlessly extended and molded to the user's needs.
 
 The abstraction of data types is accomplished using two major components, the *Type System and Coercion Engine* and
-the *Fileder Unified Data Model* for unified data storage and access.
+the *Fileder Unified Data Model* for unified data storage and access. In the next sections the design and implementation
+of these two components will be described in detail.
 
 ## 4.1 data storage model
 The Fileder Model is the underlying unified data storage model.
diff --git a/root/articles/mmmfs/motivation/text$markdown+sidenotes.md b/root/articles/mmmfs/motivation/text$markdown+sidenotes.md
index e2e6550..9433e74 100644
--- a/root/articles/mmmfs/motivation/text$markdown+sidenotes.md
+++ b/root/articles/mmmfs/motivation/text$markdown+sidenotes.md
@@ -1,5 +1,9 @@
 # 1. motivation
 
+The project that this thesis accompanies was created out of a frustration with the computing systems that are currently
+popular and widely available to end-users. The following sections document and exemplify the perceived shortcomings that
+these systems exhibit, as attributed to specific concepts or paradigms that the systems seem to be designed around. 
+
 1.1 application-centric design
 ------------------------------
 
@@ -9,7 +13,8 @@ using the mainstream operating systems Apple iOS and Mac&nbsp;OS&nbsp;X, Microso
 <mmm-embed path="app-types" wrap="marginnote"></mmm-embed>
 All of these operating systems share the concept of *Applications* (or *Apps*) as one of the core pieces of their
 interaction model. Functionality and capabilities of the digital devices are bundled in, marketed, sold and distributed
-as applications. This focus on applications as the primary unit of systems can be seen as the root cause of multiple problems.
+as applications. This focus on applications as the primary unit of systems can be seen as the root cause of multiple
+problems.
 
 For one, since applications are produced by private companies on the software market,
 developers compete on features integrated into their applications. To stay relevant, monolithic software or software
diff --git a/root/articles/mmmfs/table-of-contents/text$html+frag.html b/root/articles/mmmfs/table-of-contents/text$html+frag.html
index 10004f0..911d8b8 100644
--- a/root/articles/mmmfs/table-of-contents/text$html+frag.html
+++ b/root/articles/mmmfs/table-of-contents/text$html+frag.html
@@ -34,6 +34,7 @@
   <ol style="list-style: none;">
       <li><a href="#abstract">abstract</a></li>
       <li><a href="#table-of-contents">table of contents</a></li>
+      <li><a href="#overview">overview</a></li>
       <li><a href="#1-motivation">1. motivation</a></li>
       <ol style="list-style: none;">
           <li><a href="#11-application-centric-design">1.1 application-centric design</a></li>