5
11
Fork
You've already forked tomato
1

Start to remove material from admin layout #97

Merged
edwardloveall merged 6 commits from el-no-material-layout into main 2026年02月19日 15:15:30 +01:00

The goal is to not be on the design framework treadmill. I find those design systems both unhelpful and discouraging of accessibility and good design. Inevitably, you'll need to make some custom page/component and will struggle to extend someone else's system. Conversely, these pre-built systems come with functionality that we will never need making them somewhat wasteful. Finally, these systems will never cater to our interests as well as we can.

I admit that this is some not-invented-here syndrome, but I think to make a robust, long-lasting website it needs to use external dependencies wisely. Given how far modern css and html have come, there's less of a need to rely on these frameworks.

So here, I've done a few things to lessen our reliance on material UI/material componenets:

  • The main and session layouts now use very little material while keeping their look
  • Session forms have been converted from slim to erb and use simple form inputs
  • The material css and js now exist in the repo instead of being downloaded from unpkg
    • I noticed that sometimes pages would take a couple seconds to load, randomly. This was at least sometimes because unpkg was slow to respond.
The goal is to not be on the design framework treadmill. I find those design systems both unhelpful and discouraging of accessibility and good design. Inevitably, you'll need to make some custom page/component and will struggle to extend someone else's system. Conversely, these pre-built systems come with functionality that we will never need making them somewhat wasteful. Finally, these systems will never cater to our interests as well as we can. I admit that this is some not-invented-here syndrome, but I think to make a robust, long-lasting website it needs to use external dependencies wisely. Given how far modern css and html have come, there's less of a need to rely on these frameworks. So here, I've done a few things to lessen our reliance on material UI/material componenets: * The main and session layouts now use very little material while keeping their look * Session forms have been converted from slim to erb and use simple form inputs * The material css and js now exist in the repo instead of being downloaded from unpkg * I noticed that sometimes pages would take a couple seconds to load, randomly. This was at least sometimes because unpkg was slow to respond.
edwardloveall force-pushed el-no-material-layout from 6d284953f1
All checks were successful
Setup Successful
Jest Successful
RSpec Successful
Static Analysis Successful
to 026fd58129
All checks were successful
Setup Successful
Jest Successful
Static Analysis Successful
RSpec Successful
2026年02月17日 16:24:35 +01:00
Compare
thetizzo left a comment
Copy link

Looks good, I agree with the general theory of not being on the design framework treadmill. My experience has been similar to what you've said here in terms of maintenance overhead.

Looks good, I agree with the general theory of not being on the design framework treadmill. My experience has been similar to what you've said here in terms of maintenance overhead.
edwardloveall deleted branch el-no-material-layout 2026年02月19日 15:15:32 +01:00
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rootable/tomato!97
Reference in a new issue
rootable/tomato
No description provided.
Delete branch "el-no-material-layout"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?