What are the minimal text specs we require for the Hitchhikers Project? At the dawn of time H2G2.com defined GuideML. Federated wiki follows its own minimal path for text and markdown, while Obsidian, Github and the rest define exttnsions to the common markdown]] spec. Which should we choose and why?
# Opinionated Minimal Markdown Here we learn from Federated Wiki Markdown and Obsidian Markdown. we keep the sepcification as minimal as possible. So: - No Tables - One Level of Titles - Internal Wiki Links - External Wiki Links - Basic Formatting (Bold, Italic)
And nothing else. Our focus is on text. On writing. Image, Video, Sound, are supportend by using their own elements outside of the text specification. That is there is no layout of media - they simply occupy the full width of the miller column. Reasonable defaults can be established for their placement in markdown.
So we support the equivalent of the federated wiki plugin for: - Image Plugin - Video Plugin - Audio Plugin
Other than this: > We do not care about formatting or layout.
# Fancy stuff Everything else I believe we can forget. Checkboxes, html, other plugins we have no need to support. Our interest is simply on supporting authors.
# Frames and Plugins
As an experimental space, we can explore with other platforms how we can standardise - or more modestly make easy - the process of implementing common fedwiki-style plugins.
This may be as simple as enabling sandboxed frames that display sandboxed HTML elements. These elements can include vibe coded visualisation of data pulled from the context of the wiki page via a minimal but standardised api.
Similarly we may look at the web component standars, and using wasm within the frame of plugin context. But all of this is an experimental "play" space and not a requirement for collaboration on content.
# See - Wiki Link Metadata - Round Robin Content