I think I need to be constantly reading biographies to stay truly motivated.
I hate places where there is a focus on just a single thing. My mind craves diversity and maybe that my view towards life and work. That’s maybe the reason I work this way.
Interface Based Relations in Hyper Documents
Web Allows for “Linking” pages. That is “Referencing” a page in another page.
In the Markdown extensions exists the idea of “Front-Matter”; Or attributes that are attached to Markdown text. The product “Notion” goes further and makes this into a database with Documents as the base of what is stored.
Ted Nelson believed in “Transclusion” that is quoting by referencing exact positions in the mother data and taking something out of that place.
- I don’t want a webpage system; But 3 different things combined together:
- A document
- A database
- A Software.
In the archives; I have the data living as source code in the software; in the pages of the Archive, I have all sorts of data coming and joining together.
A quote for example can reference anything “that provides the means to be a source.”
The world of software usually is all about “strictness”. There are every sort of automation in there to condition the user; that is not acceptable in the way we do our messy crafting.
Systems like Self; believed that by the notion of “Prototypes”; the user can be free from all sorts of strictness; that was as well inside the Smalltalk system that already used messaging for similar means.
In the archives; I wish to have different things: A) A document that has content and attributes. B) A document transcluded into another (quotes) C) The host system; querying info from transcluded data; say the quote requesting anything that can have “Source protocol”; so for example:

Having quotes like this requires the reference to be generic and accept anything that is exposing a certain protocol/interface.
This is radically different from the way a relational database works; and also from the ideas of Hypertext.
Certain things can have specialized views as well in this system. So; for example: Maybe a quote wishes to be programmatic.
In this case maybe it also is worth having prototypes in the system: To require certain data to be overridden and programmatically changed.
This creates a new question: How should the software look like here? How should the document?
And when thinking about the document; I think about something visually rich; like a DK book; full of amazing layouts and stunning looks; it has to be possible as well.
[
[
[