Quasar frontend for directus

Hey everyone. I’ve been away for personal reasons but I’d like to share a bit about what I’m building at the moment.

Currently we’re using the Directus studio as our main product but we’re trying to change this as it doesn’t fit our needs.

So we started building a Quasar frontend that automatically generates an admin panel from the existing directus schema.

The process is completely dynamic as it simply loads the collections/fields/permissions endpoints then uses quasar components to build the tables and forms.

The reason for doing this was to have a more mobile friendly app that can be packaged as a PWA that also allows high degree of customization.

I’m still missing a bunch of features like versioning and settings / profile / user / files pages but this is what the front end currently does decently:

Uses quasar components to map almost all directus components.

Improves on some components e.g. copy/paste images is supported in html editor now and drag and drop files is seamless.

Improves on the search function of the tables.

Offers a responsive data table layout by default.

Caches / stores data aggressively.

There’s a bunch of things done wrong too e.g. the app assumes that the primary key is “id” etc.

I’ll be sharing screens but so far I can see that the app is very fast and responsive and very mobile friendly.

The whole point isnt to build a reusable wrapper but to build the framework that will be used for our own app.

Hit me up with questions and comments if you have any ideas on whether what I’m doing is a bad or good idea.

Thanks!

6 Likes

Welcome back and thanks for sharing! Looking forward to seeing the screen shots when they’re ready.

As I’m loving Quasar I’m also loving the idea of rewriting the Directus frontend using Quasar.

Quasar may not be the best looking but definitely most complete framework in terms of builtin components and component functionality in the Vue ecosystem.
It would definitely improve (extension) development working against a well documented framework and is a good chance to cleanup tech debt.

That said, my concern is, that no matter how good and useful it might be, it may never get merged because of the dependency on a framework that is basically maintained by a single person.
This may lead to the inconvenient situation of having to maintain two apps in parallel.

Anyway, if you happen to open source it someday I’ll definitely take a look.

1 Like