Feature request: Describe each app. At least what it does (beyond just the category)
Android
A place to discuss anything related to Android or Android adjacent.
INFO:
-
No attacking others based on their phone preferences. Criticizing OEMs/devices is allowed. Attacking users because a different brand/device works for them isn't.
-
Obvious spam will be removed.
-
Anything directly or indirectly related to Android is allowed.
Check Out Our Partner Communities:
I tried to have this list as concise as possible. Probably it shouldn't even scale vertically - better horizontally, preferably with responsive design. However, how would you like it implemented? Every so often, I add necessary comments:
Like this
See Trackers for example.
So in the end I just wanted to create a list that if someone is interested in some app, he can click links and read about this app in Source Code repo or F-Droid. Yet, I was thinking of maybe F-Droid information dynamically scrapped into static site with "approved" apps but idk.
Those comments in the tracker section are good, just a one line summary kind of thing for all of them would be a nice improvement.
I'm not asking for full F-Droid information (but if you want to include it, maybe put it in a tap-to-show sliding thing (sorry, I don't do web dev) )
Yeah but sometimes it is hard but good idea. :) Me neither haha that's why I do MarkDown
Github accepts the details HTML tag as part of Markdown. You could use that to put there a description and it would only be visible if you expand it.
Yeah, I know that, but maybe it's my personal preference that I try to use pure MarkDown when HTML is unclean with a mix of it. You probably meant something like here:
<details open="open">
<summary>Table of Contents</summary>
<ol>
<li><a href="#installing">Installing</a></li>
<li><a href="#shortcuts">Shortcuts</a></li>
<li><a href="#features">Features</a></li>
<li><a href="#dependencies">Dependencies</a></li>
<li><a href="#usage">Usage</a></li>
<li><a href="#building">Building</a></li>
<li><a href="#translating">Translating</a></li>
<li><a href="#supported-languages">Supported Languages</a></li>
<li><a href="#license">License</a></li>
</ol>
</details>
Yeah, that's exactly what I meant. But I get that you want to avoid HTML if possible.
If you find a pure markdown alternative, let me know, I was looking at options a while back for a repo and settled on the HTML tag.