Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Refactoring Milkdown to tightly align towards TTY.WTF usage 🍼 Plugin driven WYSIWYG markdown editor framework.

License

Notifications You must be signed in to change notification settings

mihailik/rest-milkdown

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Build

  1. Stick to raw DOM, no framework
  2. Index.html can embed pre-baked DOM, CSS and JS so it appears instant, would it work best?
  3. The rest would be an app using: 3.1. Milkdown 3.2. Ag-Grid (probably) 3.3. XLS parser (maybe?)

One part of the build would need to process some "core" part of the code and inject it into HTML.

Another part of the build would build the whole app into JS+CSS files.

Sample MD

GET http://google.com

Preview this:

[{ red: 1, green: 2, blue: 3},
{apple: 10, pear: 20, google: 30}]
previewThis.map(x => <div>{JSON.stringify(x, null, 2)</div>)

Parsing URLs

/http://*** (+ headers) --> code block with http go! language prefixed with GET

POST http://** (+headers, body) --> code block with http go! language

*** or txt:*** --> Markdown but show unicode formatting controls

fmt:*** --> Markdown with normal Markdown formatting

js:** --> code block with js go! language

Might be optional:

file:/path --> File manager

file:????? --> File manager use some funky compressed payload format

About

Refactoring Milkdown to tightly align towards TTY.WTF usage 🍼 Plugin driven WYSIWYG markdown editor framework.

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 51.8%
  • JavaScript 37.7%
  • CSS 9.6%
  • Other 0.9%