I've been working hard on the preview release of gloss.io which is now up for public scrutiny. Aloog the way I've been learning more about the problem domain and many of the req's are solidifying nicely. Meanwhile Eric Evans book on Domain Driven Design which:- has many resonances with my keydrivers for gloss.io - i.e. developing contextual language as a core part of the solution lifecycle, and
- captures many useful design principles in a way that I'm going to explore in the next pyglos release (blue-bottle)

While the following UML Class diagram illustrates the relationship between gloss.io domains for content subscription - such that a dependent domain ( one that reuses content from another domain ) can be notified of changes to the source content.

Both these models form part of the design make-over that I'm busy with right now.
One more thing, I've just found the Google MyLibrary service and have started to capture my professional library - this is a lot richer and easier to manage than my old wiki version of the same. Great work Google!