Churn: An AI content editor for the Internet has been missing.

Why are we still using complex file formats? AI Models and Code Generators all speak Markdown, HTML, CSS, even Scalable Vector Graphics.
We can use HTML and CSS for layout design. We don't need Adobe or Affinity. We need to make it a Responsive Design and publish it to the web anyway. Emails and reports, fine okay.
Markdown editors are growing like crazy: Obsidian, Anytype, CraftDocs, Logseq,
We have open standards like WebGL.
We now have a next generation Cross-Platform framework to build Cross-Platform Applications

Features

Aliases: defaults to plural, singular, acronym, acronym plural. Show, hide HTML, CSS Apps and Plug-ins, Add-ons, Extensions Use Tailwind
Only deal with Extended Markdown,
Embedded AI Integrations for both Content Generation and Web Development.
Build once play anywhere Cross-Platform Applications with Rust using wgpu
Private notes Variants Versions

Header syntactial mods for subheaders and subtitles

In markdown there are by default 6 levels of headers. However, if you want to render a subheader or subtitle you can use syntax to render the remaining text in as a subheading, subtitle, or lede. For example,
  1. a double pipe (||)
  2. a double dash (--)
  3. a double colon (::)
  4. a double asterisk (**)
  5. a double equals (==)
  6. a double plus (++)
  7. surrounded by parenthesis (Heading (Text))
Jujutsu integration.
Auto path and backlink adjustment on changes in files.
uuid generation Split markdown file into two.

Citation Management Automation

Sources

Dependencies

Rust Elixir DuckDB wgpu Tailwind Glow Unified.js Remark.js

Inspiration Set

Quip Helix Notion Coda Obsidian Affinity Publisher Windsurf IDE Hygraph WebStudio GrapesJS Figma Jujutsu Retcon Obsidian Plugin Community Ditto Substack Plunk Pages

One Day

Collaborative Documents Contribution monitoring. Edits, amends, saves timestamps.