The biggest OMG when you look at Drupal 7's db at first is: "why there are so many tables?". There were lots of debates regarding Drupal db schema, but if backdrop's target is small to mid projects and better performance, there should be a movement towards getting rid of current "table per field" approach.
There can be something similar to Drupal 6 CCK approach: table per bundle and if field is multivalued it lives in a separate table. There was a project called "PBS" (https://drupal.org/project/pbs) that tried to accomplish that goal but it didn't work out for some reasons.
So what do you things about such a feature?
Recent comments
Thanks! Yes, You can check out the dev branch on GitHub here: https://github.com/shabib-m/tailwindcss/tree/dev Note: I’ve just pushed an update to the dev branch adding the Dark Mode...
Free Backdrop Theme built on Tailwind CSS v3 (Based on Basis) - Seeking Feedback & Ideas!
Looking good. I'm curious if you have a public repository where we can see the progress in the code?
Free Backdrop Theme built on Tailwind CSS v3 (Based on Basis) - Seeking Feedback & Ideas!
Hi, so working through Amilenkov's useful suggestions in turn unpublished? - I can see the page itself when not logged in. I did then edit and added a menu link from the page...
menu partially working