The name of the input field inside the input field.

[eveneme]

Nested input field naming for improved design and space efficiency. In my opinion, there's no need to describe the input field above and then repeat the description inside. Why duplicate information?

Examples:

This would save a lot of space and enhance the appearance.

[mutec]

Using placeholders as definition of a field is pretty bad since you can't see the text after filling that field. Placeholders should contain examples only.

[eveneme]

On the attached examples, it can be seen that the text from the input moves up above the input. This takes up significantly less space than the text located above the input. Examples:

[eveneme]

In my opinion, the best solution would be an input in this style, like a conceptual sketch. Such an input looks much more aesthetic, takes up less space, and serves the same functions as a regular one.

[eveneme]

Suggestion 2:

[eveneme]

On WoltLab, there are numerous inputs that influence the appearance of individual sections. In my opinion, we should move away from the standard, less aesthetic input in favor of a more efficient solution, providing not only a visually pleasing effect but also occupying less space.

In my opinion, a model like this would work best:

You can see versions of various inputs here: https://mui.com/material-ui/react-text-field/

[eveneme]

I’ve reviewed numerous inputs, and I believe the one for WoltLab would be the best option. It’s an input similar to what Google uses. You can see it here: https://mui.com/material-ui/react-text-field/

It’s aesthetically pleasing, takes up very little space, and is fully functional. I think that along with the template redesign in version 7.0, the inputs should also be refreshed. The user interface needs to be inviting and aesthetically pleasing.