Most platforms treat folders as dumb containers. You upload files, you organize them into directories, and the platform shows you a file list. What happens next is your problem.
AppKask flips this. Every folder has a type, and the type determines what application opens when you navigate to it.
Think of it like your phone. You don’t open a “file viewer” and manually parse a .mp3 file. You tap a song and a music player opens. The file type determines the experience.
AppKask does this at the folder level:
Same workspace. Same files. Completely different user experience depending on the folder type.
If you’re running a consulting engagement, a single workspace can hold everything:
| Folder | Type | What the client sees |
|---|---|---|
/training | course | Structured lessons with video and quizzes |
/processes | bpmn-simulator | Interactive process diagrams they can simulate |
/media | media-server | Video library with adaptive streaming |
/website | yhm-site-data | Their branded website, built from the same content |
One workspace. One URL. Four completely different applications — all powered by the same underlying files.
Every folder-type application runs in two modes from the same code:
Embedded mode — inside the workspace browser. The authenticated user sees the full editing experience: upload, reorder, edit, delete.
Standalone mode — accessible via a clean URL with an access code. No login required. The external user sees a polished read-only experience: course viewer, media gallery, process diagram.
The same crate, the same templates, the same logic. Two audiences, zero duplication.
You’re not buying five separate tools and stitching them together. You’re deploying one platform where each folder becomes the right tool for the job. Training, media, processes, websites, and documentation — all managed in one place, all shareable with one access code.
New folder types can be added without touching the core platform. One crate, one registration line, and the workspace browser picks it up automatically.