I generally put markdown in /docs. I don't uppercase filenames. Instead I make a documentation generator consume the files so I get a decent navigation in HTML/PDF builds.
We did put non-code into /src for a very long time: It was heredocs, multiline docs, etc. Actually my preference is to put texts close to code and only fallback to /docs/something.md at a conceptual level. Which is probably what the author proposes, given that he sees markdown as primary interface to code.
In terms of a documentation artifact, I love what `cargo doc` generates, but when I'm inside a source file, any plaintext solution seems so limiting.
I actually miss what I had when I was playing around in TempleOS. All text in the OS is rich (you can toggle between the markup and the standard WYSIWYG view), so comments could have formatting, colours, images (bitmap or vector, great for diagrams), hell, even (aggressively spinning) 3D models.
The thing I used most was the collapsible sections, think and in HTML. Although I appreciate plain text and would hate WYSIWYG rich text in my serious source code (not to mention binary data appended to the end of the source file for images and models), I can't help but pine for those features. Being able to just draw a real diagram and being able to edit it later in seconds as opposed to making some horrid ASCII art was awesome.
I have been a hardcore Konqueror user back in the days. Early dolphin felt like a back step. Nowadays, thought, it easily outshines Konqueror. I still miss a few KIOs which were showcased in Konqueror. I guess they were discontinued.
I am just delighted by the screenshots. I love this Win9x like interface aesthetica for being dense in font size/information, very stringent in optics. Even if this is not exactly the colors and shadows of Win9x, this aspect remains. There were a few Web toolkits in the past which also had this, but since the dawn of mobile UI sickering into the desktop, we somehow lost this art. Even the rather consistent KDE/Gnome UIs don't feel so "home" for me as these (frankly nostalgic) Win9x.
For portfolio and service only, virtually any GH alternative discussed here will do it. Even a self-hosted cgit or static page git browser will do it for read-only.
I've been collecting IPv6 data for a few weeks using my older v1 scanner. However, I just launched a v4 scanner for IPv4 (which is 10-12x faster with the same accuracy) and I'll be porting that over soon. You can already see some IPv6 details scattered across the site, but the full dataset will be live in the coming weeks.
We did put non-code into /src for a very long time: It was heredocs, multiline docs, etc. Actually my preference is to put texts close to code and only fallback to /docs/something.md at a conceptual level. Which is probably what the author proposes, given that he sees markdown as primary interface to code.