-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Solid.Drive is a file manager built on the Solid Protocol. Files live exclusively in the user’s own Solid Pod; the application never stores or proxies data. Authentication, storage, sharing, and access control are all handled through open Solid standards.
Try the live demo → http://demos.swe.htwk-leipzig.de:3000/
|
ℹ️
|
The live demo at demos.swe.htwk-leipzig.de:3000 is hosted on the HTWK Leipzig server and is only accessible from within the university network or via VPN. |
|
💡
|
New to Solid? Start with Solid & LDP Concepts before diving into the architecture. |
| Capability | Description |
|---|---|
File management |
Upload, download, preview, and delete files directly on your Solid Pod. Each file gets a dedicated LDP container with a semantic metadata document. |
Semantic classification |
MIME types are mapped to schema.org classes and written to RDF metadata, making your files queryable by any Solid-aware app. |
Sharing & access control |
Share files with contacts using Web Access Control (WAC). Per-contact shared catalogs keep discovery fast and private. |
Access requests |
Request and grant access to other users' files through a structured inbox-based workflow. |
Profile management |
View and edit your Solid profile: name, avatar, and contacts, without leaving the app. |
Internationalisation |
Switch between English and German at runtime. The selected language persists across sessions. |
Prerequisites, local setup, Docker, and available npm scripts. |
|
Layered architecture, feature map, infrastructure modules, and dependency rules. |
|
Pod layout, DCAT catalog, file metadata, ShEx shapes, and SHACL validation. |
|
Glossary of Solid, LDP, WAC, OIDC, and linked data terms for contributors new to the ecosystem. |
|
Step-by-step breakdowns of upload, delete, share, revoke, and access request flows. |
|
Running the test suite and the full manual QA checklist. |
|
Branching strategy, commit conventions, and the pull request process. |
|
Known limitations and their workarounds. |