FYI: Another feed reader I built (called pluto with sqlite as feed / data storage) see https://github.com/feedreader - used by OpenStreetMaps Blogs, Planet KDE, and others.
PS: For the (ongoing) struggle (trying) to "normalize" the RSS and ATOM feed formats (or JSON Feeds) see the feedparser gem - https://github.com/rubycocos/feedparser
For more context let me add / point out the side-by-side samples (texti vs markdown vs latex vs wikipedia markup), see https://github.com/texti/texti.github.io/tree/master/samples using the Wikipedia article on markup as an real-world sample.
FYI: New ideas first presented are always very confusing. Let it sink in. Note: The page is public - thus, if I may return the favor - change the confusing private to public in your sentence (or is that "knee jerk private commentary?").
PS: Let me add more context - The top-linked Textile Markup Language is a documentation website. Textile markup/down is history and FAILED - thus - the next step is what can we learn from the fail - what are the good, bad and ugly parts? what was missing and so on. Now how do you "fix" textile (or markdown)?
Thanks. Note this text is not a commercial or ad. My philosophy is function over form wins. Period. Comments and critique always welcome. If I may return the favor - do NOT use the word modern - as in say 5 or 10 years - that may read different. Do NOT upcase markdown - it is today a generic term / word. The had a baby "idea" is stupid. The idea is about evolution and adding AND yes, deleting and forever changing and so on. Anyways, here's the source (w/ public domain - no rights reserved dedication) - https://raw.githubusercontent.com/texti/texti.github.io/mast... you are more than welcome to publish your own teaser / promo / analysis / opinion.
Why not latex? Why not the best of both worlds? Anyways, see latext and markdown compared - https://github.com/mundimark/markdown-vs-latex In evolution simpler wins. The beauty of the paragraph syntax is an empty line, for example! And yeah for sure - the image syntax in markdown is a big FAIL and there are easier alternatives upcoming (out there waiting for the big time) - see https://texti.github.io - and image and figure "macros" - that is - built-in templates, for example.
May I introduce Texti (Markup Language) - Text with Instructions (.texti) - Structured Documents in Text with Formatting Conventions - that tries to offer the best of all worlds - that is - markdown / textile / mediawiki markup/down / latex and more. See https://texti.github.io PS: An "important" building block missing in markdown / textile is built-in templates a la mediawiki markup/down. Lets you add "macros" for images or figures and so on (and much more). Extension and evolution is key - as always - and wins out in the long run.
Here's a real-world story of getting "exited" of my humble self - more a programmer (or code monkey) than an "engineer" really - see The Strange Case of Mammad Kabiri @ Uniqa Software Service. [1]
FYI: I help out with the Ruby Pixel Art Week 2021, April 19th to April 25th - 7 Days of Ruby (Graphics) Gems.
The Ruby Pixel Art Week 2021 presents a new Ruby graphics library every day from April 19th to April 25th, see https://planetruby.github.io/gems
FYI: Here's my little minimialist starter kit called Hello, Minima! - Get Started w/ GitHub Pages (Jekyll) in 60 Seconds using the Minima (Gem-Packaged) Theme [1].
If you want to get rich selling books than you have to write about getting rich. These crypto books or self-help books are best sellers. If you write an anti-corruption book, good luck finding readers or someone that believes in your narrative of have fun staying poor.
PS: For the (ongoing) struggle (trying) to "normalize" the RSS and ATOM feed formats (or JSON Feeds) see the feedparser gem - https://github.com/rubycocos/feedparser