From b0b26d2a9dcd4944d9aae90480591793691730c1 Mon Sep 17 00:00:00 2001 From: s-ol Date: Sun, 29 Dec 2019 18:56:23 +0100 Subject: marginnote embedding --- root/articles/mmmfs/framework/text$markdown+sidenotes.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'root/articles/mmmfs/framework') diff --git a/root/articles/mmmfs/framework/text$markdown+sidenotes.md b/root/articles/mmmfs/framework/text$markdown+sidenotes.md index 0e4d9a3..48e6a2c 100644 --- a/root/articles/mmmfs/framework/text$markdown+sidenotes.md +++ b/root/articles/mmmfs/framework/text$markdown+sidenotes.md @@ -56,9 +56,10 @@ content transclusion The strengths of modular architectures should similarily also extend into the way the system will be used by users. If users are to store their information and customized behaviour in such an architecture, then powerful tools need to be present in order to assemble more complex solutions out of such parts. Therefore static content should be able to be -linked to (as envisioned for the *Memex*, see above), but also to be The term transclusion -refers to the concept of including content from a separate document, possibly stored remotely, by reference rather than -by duplication. See also *transcluded*, +linked to (as envisioned for the *Memex*, see above), but also to be The term transclusion refers to the concept of including content from a +separate document, possibly stored remotely, by reference rather than by duplication. See also +*transcluded*, to facilitate the creation of flexible data formats and interactions, such that e.g. a slideshow slide can include content in a variety other formats (such as images and text) from anywhere else in the system. Behaviours also should be able to be transcluded and reused to facilitate the creation of ad-hoc sytems and applets based on user needs. For -- cgit v1.2.3