[WIP] Design modernization

Feature Concepts
#1

Usually I am not a big fan of redesigns, because it is just a lot of effort and does not provide a lot of value. But I would like to improve a few things around navigation to be ready for a future responsive design and a modernize the UI a little bit.

In this topic you can see a few low fidelity mockups. The goal is to freshen the design a little bit without changing too much and spending too much effort into it.

Your feedback is very welcome. If you have topics you would like to see changed, please don’t hold back.

The icons are just placeholders.

Apps
Apps.png2531Ă—1463 116 KB

Content
Content.png2531Ă—1463 170 KB

Contents
Contents.png2531Ă—1463 216 KB

Schemas
Schemas.png2531Ă—1463 199 KB

Settings
Settings.png2531Ă—1463 207 KB

Feedback:

2 Likes
#2

I have added more designs to an invision board. You can also leave your comments there.

https://projects.invisionapp.com/boards/7340TY2VCAJ/

I have also implemented a prototype:

image
image.png1518Ă—937 50 KB

It looks rubbish, but it is a more a prototype and an analysis how long it would take to implement that. The actual estimation is around 2 weeks when the theme itself is ready. But this is something for a professional designer.

1 Like
Reference field UI only listing first schema type even though multiple types are allowed
#3

Hello, I do not want to create a new thread because it may fit this feature concept (feel free to remove it if not).

During content editing, we are too often face accidentally removing reference, when we want to actually edit it.

image

Hover
image

It may be, better to switch the order of icons as fast fix (because if it is accidentally clicking to edit it, closing the new tab is faster than re-assign the reference).

And by the way, refreshed UI looks nicer!

#4

Close or delete is always on the right side. But the close button has a confirm dialog now…

1 Like
#5

Hi,

the screen designs for design modernization are available here: https://projects.invisionapp.com/share/YVZWRXTKCR8

Feedback is very welcome.

1 Like
#6

WOW looks nice!

I really like option for collapsing nested field in scheme page. From screens i do not notice if same will be apply for “UI separator”. It would be nice to (and if it can look more like it is look in new content prototype page even in scheme page it will be even better, currently it help just in content page, but in scheme editor not so much).

I already like squidex UI, it looks nice, but this lift the bar even more.

#7

I understand what you mean, but I would actually like to change the schemas a little bit. The current problem is ordering of fields and that groups are managed with separators. What I would like to do is to have a separate config for the structure of fields for the UI, e.g. the json representation could be:

tabs:[{
   "name": "common",
   "label": { 
    "en": "Common"
   },
   "sections": [{
     "name": "section1",
     "label": { 
      "en": "Section1"
     },
     "fields": [
       "slug",
       "name"
     ]
   }, {
     "name": "section2",
     "label": { 
      "en": "Section2"
     },
     "fields": [
       "slug",
       "name"
     ]
   }]
]

This would make your problem unsolvable. Unfortunately I don’t know how to apply it to array fields yet.

#8

I agree ui section should be threat differently from another field (in the end it already does, because it wasn’t visible in api). I do not think it collide with my proposal; I care about option to collapse UI section in scheme design in portal. Currently this option is available just in “content” section.

This is for raw illustration what I mean.

image
image2460Ă—1402 274 KB

For array fields isn’t possible to add filed with sections too. Like this? Or I missing something.

{
  "name": "arrayItems",
  "properties": {
    "fieldType": "Array"
  },
  "partitioning": "invariant",
  "nested": [
      {
          "name": "name1"
      },
      {
          "name": "name2"
      }
    ],
  "sections": [{
     "name": "section1",
     "label": { 
      "en": "Section1"
     },
     "fields": [
       "name1",
       "name2"
     ]
   }, {
     "name": "section2",
     "label": { 
      "en": "Section2"
     },
     "fields": [
       "name1",
       "name2"
     ]
   }]
}

With Array field i have, also small issue with, partitioning, even if I want translation just for one field i am force to mark as translated all field (or any). But this isn’t related to UI modernization

#9

Perhaps I don’t understand what you mean with collapsible sections. The left menu and the right sidebar can always be hidden.

#10

I mean this.

image
image3246Ă—1848 394 KB

Block of the fields in “Schemes” in the portal. This “block” can be collapse in “Content” editor (view,edit,add). But not during editing schema.

#11

Lol, I have not seen it in your first screenshot. My idea was to separate the technical schema from the UI but then this would not be possible.

#12

Wow! This is a significant upgrade. Well done!

Agree that the UI separator can be a bit different hinting that it’s not going to look like a field (or at all). It’s a nice to have, not a must.

The updated UI is clean and organized, I’m a fan.

1 Like
#13

Looks good Sebastian!

Do you also plan to make it as responsive as possible or is that not profitable enough (like the time to create it and the value it creates)?

#14

Not for now, the value is too low. I asked a few big customers but nobody wanted to invest in it.

1 Like