Feedback to author: The diagram and explanation took a beat longer than normal to scan, since this buries a bit that it's not about the beautiful source contro

Feedback to author: The diagram and explanation took a beat longer than normal to scan, since this buries a bit that it's not about the beautiful source control system called fossil shipped as a composition of modules: https://fossil-scm.org/home/doc/trunk/www/index.wiki https://fossil-scm.org/home/doc/trunk/www/index.wiki Great diagrams, so of course that's the first thing a reader will skim. Reader thinks people build things based on git all the time, the diagram looks like it's based on fossil, cool, scan more... Making it take a bit longer when scanning upwards from the diagram, the Mastodon client is introduced without naming it until an aside at the end of the paragraph: > Before the New Year I decided to hack on an idea. I wanted a social media client for Mastodon that displays my feed in a way that suits me ... I call it Fossil. If you missed that at the end and scan back down to the arch section, it mentions fossil without really saying it's the social media app: > With fossil plugins, it’s become straightforward to work on any part of the stack: - UI elements — write verbatim HTML or Jinja templates, packaged into a plugin - API endpoints — register them via a decorator API - DB tables — Create them during plugin initialization - AI algorithms — register them via the API - fossil > That’s neat. The whole stack. I'd edit three things: + "...social media client for Mastodon I call ‘Fossil’ that displays my feed..." + "With plugins for my Fossil app..." + "- fossil mobile app"