Astrolabe: an ancient, handheld model of the universe with a wide range of applications, including the navigation of ships.
This document describes the overarching goal of a Rich Text Editor (RTE) for web applications. The editor should:
- Offer a basic set of out-of-the-box plugins for modern content creation experiences. Examples include: gif selectors, spoilers/content warnings on both text and block elements, custom emojis, mentions, embeds, and tumblr-style "photosets".
- Be extensible and customizable, and support presets that make it possible to create custom experiences for existing software. For example, projects should be able to restrict available plugins to "those that can emit markdown supported by GitHub" or "those whose output is compatible with Tumblr".
- Supports semantic output that can be further processed and built upon to allow compatibility and interoperability with (and extension by) other projects.
In particular, we'll develop the core set of plugins and semantic schemas with an a eye to the needs for online self-expression of transformational fandom.
Boba Editor Next is a a proof of concept and initial implementation of the design proposed in this document. Given that the current "Boba Editor" needs to be sunset quickly, this document will discuss any tradeoff necessary for its short-term launch.
While Astrolabe can be used as a standalone editor within a single project, ensuring compatibility with different input/output formats must be a core part of its design.
Content created with Astrolabe should support output in a format compatible with RSS and ActivityPub.
When a 1:1 representation of the output of a plugin is not possible, fallback representation should be provided. If supported by the protocol, the fallback representation should include extra semantic data that allows to reconstruct the original output.
Astrolabe should allow loading data as provided by a RSS item or ActivityPub message, with a best effort conversion. If extra semantic data is present and supported by an installed plugin, Astrolabe should attempt to reconstruct the original state.
MDX is a human-readable format that is gaining wide adoption in the CMS space. Publicized as "Markdown for the component era", MDX allows users to combine Markdown content with JSX, so they can embed custom HTML and advanced components within their content, while maintaing the ability to modify it through simple text editors. MDX is supported by many popular frameworks, including Astro, NextJS, Gatsby, and Docusaurus. GitHub is also currently experimenting with interactive, MDX-based READMEs.
In our experiementation within Fandom Coders, MDX has been widely appreciated by fandom folks as a format for creating portable online content. But while it is possible for people to write MDX on any textual editor, more widespread and casual usage will require the ability to also modify the content through a rich (and mobile-friendly) interface.
TODO: embed/link to research on similar, existing usage of MDX as an output format for visual editor.
With the proliferation of multiple online platforms (and the current push towards decentralization), it will be more and more important to enable crossposting the same content across different services, or creating custom interfaces compatible with existing ones.
For example, it should be possible to use Astrolable to create a BobaBoard contribution and extract a "GitHub-compatible" view of it, which can then be posted as an issue on GitHub. The actual posting mechanism (i.e. authentication handling and calls to the publish APIs) is out of scope for this project.
While the core use case of Astrolabe is the editor itself, it should be possible to leverage the associated plugin ecosystem to convert between each available input and output format, even if no intermediate visual editing is needed.