Add 14 Solid apps to the apps list

[jeswr]

Summary

Adds 14 verified-live Solid apps that work with any Solid-OIDC provider (including solidcommunity.net) to /apps:

App	Category	Author
Liqid Chat	Chat	Jackson Morgan (o-team)
PodCal	Scheduling	Zero Limit
SolidOS Databrowser	Pod Management	SolidOS team
Synara AI	Productivity	PrivateDataPod
Pod Drive	Pod Management	PrivateDataPod
Pod Resume	Productivity	PrivateDataPod
HomeVault	Productivity	PrivateDataPod
VitalStats	Health	PrivateDataPod
InnerPod	Health	ANU SII
MSFatigue	Health	ANU SII
FilePod	Pod Management	ANU SII
KeyPod	Security	ANU SII
GeoPod	Location	ANU SII
SecureDialog	Health	ANU SII

Adds new filter categories to the dropdown: Chat, Location, Scheduling, Security.

How candidates were found

Researched across: the Solid Forum, github.com/anusii (ANU SII ecosystem), Noel de Martin, Vincent Tunru, PodOS, SolidOS, ActivityPods, PrivateDataPod, and Stucco directories. Initial list was 19 candidates.

Verification

• Liveness: all 14 URLs return HTTP 200 (verified via curl).
• Works with solidcommunity.net / standard Solid OIDC:
  • PodCal documentation explicitly states "Works with any Solid OIDC provider".
  • ANU SII apps (InnerPod, MSFatigue, FilePod, KeyPod, GeoPod, SecureDialog) all use the same anusii/solidpod Flutter package as NotePod / HealthPod / MovieStar (already on the apps page), which presents a provider-selection screen at login.
  • PrivateDataPod apps present a standard Solid OIDC login accepting arbitrary providers.
  • SolidOS Databrowser is the reference Solid client — supports every Solid OIDC provider.
  • Liqid Chat uses @ldo/solid, which accepts any Solid OIDC issuer.
• Excluded (for the record):
  • Pocket Change — Playwright check confirmed it force-redirects to login.stucco.software with no way to specify another provider.
  • Stucco App Directory — same infrastructure pattern as Pocket Change (likely provider-locked).
  • Mastopod, Welcome to my place, Mutual Aid — tied to ActivityPods-hosted infra, not standard Solid OIDC.

Test plan

• New tiles render under /apps without layout regressions
• New Chat, Location, Scheduling, Security categories each filter to the expected apps
• Click-through from a sample of tiles opens the hosted app
• Embedded "source code" external-link spans open the correct GitHub repos

Logos were intentionally omitted — several existing tiles (Penny, Booklice, 0data Hello, Solid File Manager) ship without logos, and any maintainer/author can easily add one in a follow-up.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for musical-sawine-26ffa9 ready!

Name	Link
🔨 Latest commit	cf8a107
🔍 Latest deploy log	https://app.netlify.com/projects/musical-sawine-26ffa9/deploys/69ea63cb82f5ba0009dd295f
😎 Deploy Preview	https://deploy-preview-956--musical-sawine-26ffa9.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

Adds 14 additional Solid-OIDC-compatible applications to the /apps launcher page and expands the category filter to include new app categories.

Changes:

• Added 14 new app tiles (with categories and several source-code “external-link” entries).
• Added new category filter options: Chat, Location, Scheduling, Security.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The category filter dropdown is now updated, but it still doesn't include all categories that exist in the tiles (e.g., there are tiles with data-category="Browser" and data-category="Travel"). This makes it impossible to filter to those apps. Consider either adding missing categories to the dropdown or aligning the affected tiles to one of the available categories so the filter reflects the full set.

[Copilot]

These newly added apps aren't included in the JavaScript "defaultOrder" list that's used when the user selects "Default Order" sorting. Because indexOf() returns -1 for unlisted apps, choosing Default Order can produce unpredictable ordering. Consider capturing the original DOM order on page load (or keeping the defaultOrder list complete) so Default Order restores reliably.

[jeswr]

@copilot none of the apps have icons. Please add icons based on the favicon of the website if it has one.

Please remove liquidchat for now. It does not seem to be working correctly

[gjwgit]

Hi @jeswr This is not the best way to add to the PR, but would you consider adding the following recent productivity apps from AU Solid Community to the apps list. Thanks

      <li data-name="TodoPod" data-category="Productivity">
        <a href="https://todopod.solidcommunity.au">
          <div class="tile-header">
            <h3>TodoPod</h3>
          </div>
          <p>An app to manage your tasks with all data securely and
            privately stored encrypted on your own personal online
            data store (Pod) hosted on a Solid Server. Built by
            <a href="https://togaware.com">Togaware</a>. Source code is
            available <span class="external-link" role="link"
            tabindex="0" aria-label="Open TodoPod source on GitHub"
            onclick="event.preventDefault(); event.stopPropagation();
            window.location.assign('https://github.com/gjwgit/todopod');
            return false;"
            onkeydown="if(event.key==='Enter'||event.key===' '){
            event.preventDefault(); event.stopPropagation();
            window.location.assign('https://github.com/gjwgit/todopod');
            }">here</span>.</p>
        </a>
      </li>
      <li data-name="RoloPod" data-category="Productivity">
        <a href="https://rolopod.solidcommunity.au">
          <div class="tile-header">
            <h3>RoloPod</h3>
          </div>
          <p>A tool to collect your contacts into an address book in
	    one secure and private place. You can selectively share
	    any parts of your address book with others. Or make phone
	    calls on your mobile device (for the Android and iOS
	    versions). Built by
            <a href="https://togaware.com">Togaware</a>. Source code
	    is available <span class="external-link" role="link"
	    tabindex="0" aria-label="Open RoloPod source on GitHub"
	    onclick="event.preventDefault(); event.stopPropagation();
	    window.location.assign('https://github.com/gjwgit/rolopod');
	    return false;"
	    onkeydown="if(event.key==='Enter'||event.key===' '){
	    event.preventDefault(); event.stopPropagation();
	    window.location.assign('https://github.com/gjwgit/rolopod');
	    }">here</span>.</p>
        </a>
      </li>
      <li data-name="KonaPod" data-category="Productivity">
        <a href="https://konapod.solidcommunity.au">
          <div class="tile-header">
            <h3>KonaPod</h3>
          </div>
          <p>Collect your Hyundai vehicle data in one secure and
	    private place. You can selectively share any parts of your
	    data with others. The app presents the data and analyses
	    of the data. Built by
            <a href="https://togaware.com">Togaware</a>. Source code is
            available <span class="external-link" role="link"
            tabindex="0" aria-label="Open KonaPod source on GitHub"
            onclick="event.preventDefault(); event.stopPropagation();
            window.location.assign('https://github.com/gjwgit/konapod');
            return false;"
            onkeydown="if(event.key==='Enter'||event.key===' '){
            event.preventDefault(); event.stopPropagation();
            window.location.assign('https://github.com/gjwgit/konapod');
            }">here</span>.</p>
        </a>
      </li>
      <li data-name="BilliPod" data-category="Productivity">
        <a href="https://billipod.solidcommunity.au">
          <div class="tile-header">
            <h3>BilliPod</h3>
          </div>
          <p>Manage you bills, upcoming, scheduled, and past. The app
            analyses your bill history to generate reminders to avoid
            missing the all important bill payments. Built by
            <a href="https://togaware.com">Togaware</a>. Source code
            is available <span class="external-link" role="link"
            tabindex="0" aria-label="Open BilliPod source on GitHub"
            onclick="event.preventDefault(); event.stopPropagation();
            window.location.assign('https://github.com/gjwgit/billipod');
            return false;"
            onkeydown="if(event.key==='Enter'||event.key===' '){
            event.preventDefault(); event.stopPropagation();
            window.location.assign('https://github.com/gjwgit/billipod');
            }">here</span>.</p>
        </a>
      </li>

[csarven]

Dear @copilot , taking the following existing markup and content as an example in the apps.html document:

<p>This application provides a user-friendly interface for managing files and folders in Solid Pods. Source code is available <span class="external-link" role="link" tabindex="0" aria-label="Open The ODI Solid File Manager desktop build on GitHub" onclick="event.preventDefault(); event.stopPropagation(); window.location.assign('https://github.com/solid/solid-file-manager'); return false;" onkeydown="if(event.key==='Enter'||event.key===' '){ event.preventDefault(); event.stopPropagation(); window.location.assign('https://github.com/solid/solid-file-manager'); }">here</span>.</p>

please take the following feedback, that is generated by another LLM, into account, and consider updating all markup following that pattern in the document as well as new markup and content that is being introduced in this PR, if and only if, your overlords approve.

---

tl;dr: A <span> is doing the job of an <a>. Throw it out and use the right element. Everything else follows from that mistake.

Issues

Markup

1. <span role="link"> instead of <a href>
This is the root cause of nearly every other problem. A <span> is a generic, non-interactive element. The role="link" partially patches the semantics via ARIA, but it cannot replicate everything a native <a> provides, e.g., browser history integration, right-click context menus ("Open in new tab"), href being readable by assistive technology, and default keyboard handling.

2. window.location.assign(...) in onclick
<a href="..."> is declarative navigation. Replacing it with imperative JavaScript breaks the aforementioned browser affordances and adds unnecessary fragility.

3. return false in the onclick handler
In an inline onclick attribute, return false only suppresses the element's default action. A <span> has no default action, so this line does nothing meaningful here. It is not equivalent to event.preventDefault() plus event.stopPropagation() in all contexts.

4. tabindex="0"
This is a manual workaround to make the <span> focusable, which <a href> provides automatically. It is redundant once you use the correct element.

---

Accessibility

5. Violation of the First Rule of ARIA
The WAI-ARIA specification states: "If you can use a native HTML element or attribute with the semantics and behaviour you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so." Using <span role="link"> when <a> exists violates this directly.

6. Space key activation on a link role
The onkeydown handler activates navigation on both Enter and Space. Per the WAI-ARIA Authoring Practices Guide, the link role should only be activated by Enter. Space activation is the pattern for button. Applying it to a link role creates inconsistent keyboard interaction that can confuse users of assistive technology.

7. Vague link text ("here")
WCAG 2.1 Success Criterion 2.4.4 (Link Purpose, In Context) requires that the purpose of a link can be determined from the link text alone, or from the link text together with its programmatic context. "Here" fails the stricter SC 2.4.9 (Link Purpose, Link Only). The aria-label patches this for screen reader users but leaves sighted users without a descriptive label. The better fix is descriptive visible text, removing the need for an aria-label override.

---

UX

8. Loss of standard browser affordances
Because navigation is handled via onclick with window.location.assign, users cannot right-click to open the link in a new tab or window, middle-click to open in a background tab, or use browser link prefetching. These are fundamental affordances of the <a> element.

9. Vague visible link text
"Here" provides no context to sighted users scanning the page. Descriptive link text benefits all users, not just those using assistive technology.

---

Corrected Markup

<p>This application provides a user-friendly interface for managing files and folders in Solid Pods. Source code is available on <a href="https://github.com/solid/solid-file-manager" class="external-link" rel="noopener noreferrer">GitHub (ODI Solid File Manager)</a>.</p>

Notes on the correction:

• <a href> replaces the <span role="link"> construct entirely, restoring all native browser and assistive technology behaviour.
• Descriptive visible text replaces "here", satisfying WCAG 2.4.4 and 2.4.9 without an aria-label override.
• rel="noopener noreferrer" is included as a best practice for external links, mitigating the window.opener security concern even when not using target="_blank".
• All JavaScript event handlers are removed, as they are no longer needed.
• aria-label is removed because the visible text is now self-describing.

---

Specification References

• First Rule of ARIA (do not use ARIA when a native element suffices): https://www.w3.org/TR/using-aria/#rule1
• WAI-ARIA 1.2, link role (Enter key only for activation): https://www.w3.org/TR/wai-aria-1.2/#link
• WAI-ARIA Authoring Practices Guide, Link Pattern: https://www.w3.org/WAI/ARIA/apg/patterns/link/
• WCAG 2.1 SC 2.4.4, Link Purpose (In Context) (Level AA): https://www.w3.org/TR/WCAG21/#link-purpose-in-context
• WCAG 2.1 SC 2.4.9, Link Purpose (Link Only) (Level AAA): https://www.w3.org/TR/WCAG21/#link-purpose-link-only
• HTML Living Standard, the <a> element: https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element
• HTML Living Standard, rel=noopener: https://html.spec.whatwg.org/multipage/links.html#link-type-noopener

[jeswr]

Thanks all for the feedback. This PR now folds in @csarven's a11y review, @jeswr's own icon/Liqid-Chat notes, @gjwgit's four Togaware apps, and (newly) the contents of #954 so both apps-list batches land together. Each discussion is addressed in a dedicated commit on this branch:

Discussion	Resolved in
@csarven — replace <span role="link"> + inline JS with native <a href>, descriptive link text (WCAG 2.4.4 / 2.4.9), rel="noopener noreferrer", First Rule of ARIA	9244da4 (initial refactor) + b69f370 (follow-up: reset .tiles.tile-links a styles leaking onto the new .app-source > a)
@jeswr — remove Liqid Chat (not working correctly)	f860f46 — tile removed; "Chat" filter option removed alongside it (later re-added in eb66491 when LibreChat joined)
@jeswr — add favicons for the new apps	4ad3bf2 — 11 tiles get favicon-based logos (SVGs for PodCal / the PrivateDataPod suite, 192×192 PNGs for the anusii Flutter apps). Pod Resume and SolidOS Databrowser are intentionally left without a tile image: Pod Resume ships only the default Vite favicon, and mashlib declares no favicon at all. That matches the precedent of existing tiles (Penny, Booklice, 0data Hello, Solid File Manager) that also ship without logos.
@gjwgit — add TodoPod, RoloPod, KonaPod, BilliPod	37ecd80 (initial add) + 4e78711 (follow-up: move the Built by <a href="https://togaware.com">Togaware</a> byline out of the outer tile anchor so nothing is nested). Rewritten into the corrected <a href> markup pattern from 9244da4.
#954 — add Portable LibreChat	eb66491 — tile and librechat.svg asset from #954, rewritten into the corrected <a href> pattern; "Chat" filter option re-added.

Every commit was independently reviewed locally with GitHub Copilot (model gpt-5.4) before push; the two medium-severity findings raised (CSS regression on the new inline links, and the Togaware nested-anchor) are the reason there are two follow-up commits above.

The branch intentionally keeps each concern on its own commit so reviewers can land / reject pieces independently if needed. Happy to squash on merge.

[jeswr]

Follow-up to the resolution-mapping comment above: caught during post-push review that 9 tiles were still rendering without any logo (3 pre-existing — Penny, Booklice, Solid File Manager — plus SolidOS Databrowser and Pod Resume from my earlier commits, and the four new Togaware tiles).

Discussion	Resolved in
@jeswr — "Some apps still appear to be missing logos"	9aee526 (add logos to all 9 remaining tiles) + 77cb025 (follow-up: swap Penny's low-res 48×48 .ico for the existing /assets/img/solid-emblem.svg, which is what Penny itself uses on its own site — vector-sharp at any DPI, matches Pod Pro / SolidOS Databrowser / Pod Resume precedent)

Every tile in the grid now has an image. Sources:

• Booklice — apple-touch-icon-152x152.png from the live site.
• Solid File Manager — site's favicon.ico (contains a 64×64 frame, larger than the 60×60 tile slot so no upscaling).
• TodoPod / RoloPod / KonaPod / BilliPod — each app's /<slug>/icons/Icon-192.png, same pattern as the other anusii Flutter apps in this PR. BilliPod currently ships the generic Flutter-template favicon upstream (byte-identical to MSFatigue / SecureDialog); using it keeps the grid complete until the authors ship a custom one.
• Penny / Pod Resume / SolidOS Databrowser — /assets/img/solid-emblem.svg. Penny already uses it on its own site, and the other two have no real favicon of their own.

Both follow-up commits were reviewed locally by Copilot / GPT-5.4 (roborev) with no findings. Branch pushed.

[jeswr]

Icon quality follow-up. The earlier favicon pulls for three of the Flutter-stack tiles turned out to be generic Flutter templates, not real brand icons, so I went to the source repos as suggested.

Discussion	Resolved in
@jeswr — "for apps like billipod, please look at the source code"	ee4ac9c — swap all 10 anusii/gjwgit/kimishidairessha tile logos for each repo's authoritative icon (mostly dev/assets/images/app_icon.png; KeyPod has no app_icon.png so it uses the largest Android mipmap; SecureDialog uses the iOS AppIcon.appiconset). The previous BilliPod/MSFatigue/SecureDialog triplet that all shared the generic Flutter template are now 3 distinct images.
(roborev follow-up) Page-weight regression from upstream 1024×1024 PNGs	fb2684a — sips --resampleHeightWidthMax 120 shrinks the 10 updated assets from ~1.49 MB combined to ~158 KB (9.4× smaller) while still giving 2× retina density for the 60×60 tile slot.
@jeswr — "update the icons for Pod Resume, MsFatigue, SecureDialog"	e15181e — re-pick the better source-repo variants: SecureDialog → ios/Runner/Assets.xcassets/AppIcon.appiconset/Icon-App-1024x1024@1x.png (the real egg-smiley brand, not the Flutter-web template); MSFatigue → assets/images/logo.png (brain-with-batteries marketing logo, more readable at tile size than the thin pink-star app_icon.png). Pod Resume is intentionally not updated in this commit — its live site only serves /vite.svg under every asset path (all other /icons/… requests fall through to the 621-byte SPA shell), icons.privatedatapod.com is auth-walled, and no public source repo for the app is discoverable. It stays on /assets/img/solid-emblem.svg until an upstream icon exists.

Each of the three follow-up commits was independently reviewed locally by Copilot / GPT-5.4 (roborev); all clean. Branch pushed.

[csarven]

Just to be transparent, my comment was (obviously) generated by an LLM. When I noticed that Graham was only following the strange markup pattern from the website (with some of the example apps), I gave the following as input and it seemed to be aligned with my thinking about the concerns, so I shared. I didn't feel like manually typing out an explanation and the robot's answer seemed adequate for another robot.

What's wrong with this markup, accessibility, and UX concerns? Provide corrected markup. Provide references to specifications related to the corrections.