Active
Project:
Commerce Core
Version:
3.3.13
Component:
User experience
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
29 Oct 2026 at 09:27 UTC
Updated:
1 Nov 2026 at 10:44 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
f0ns commentedComment #3
f0ns commentedComment #4
f0ns commentedHere is a concept page that breathes the quality of Commerce more. It's based on the new core admin theme and keeps all current information, only presented differently.
But you know what they say: one man's meat is another man's poison.
I'd like to hear some thoughts or feedback before I start working on an MR.
Note: "Releases" is a custom entry on this custom project of mine that I used to create a mock-up / proof of concept on. You can ignore this entry.
Comment #5
f0ns commentedComment #6
jsacksick commentedHm, why is that a bug report though? Shouldn't that be a feature request?
Comment #7
jsacksick commentedComment #8
f0ns commentedYes that might be a better qualification.
In my mind it started as a bug as I noticed the active state first (not readable) and then it grew to the whole page.
Feature or feedback/advice request it is!
Comment #9
afagioliI like your positive energy here, f0ns.
On Drupal.org, it’s quite common to get bureaucratic replies that come with no empathy or encouragement. I’m not sure whether that’s right or wrong, but that’s how it is.
Speaking as someone who has used Drupal Commerce for years with my BeeHotel, I really want to encourage you.
Commerce—just like Drupal—isn’t much to look at, but it’s extremely powerful to use. Your UI suggestions are genuinely valuable to me.
Thumbs up for you.
Comment #10
f0ns commentedThanks for the kind message!
Comment #11
jsacksick commented@f0ns: I actually wanted to circle back to this at later point. Thank's al lot for working on this, It looks really nice!
@afagioli: You're right, whenever I replied I was multitasking and once again was supposed to come back to his.
@f0ns: I apologize if that sounded like a bureautraic reply :).
I pinged our internal frontend developer to have a look earlier at this.