[#11897] - [RFC] Article edit form layout
- Closed
- 2 Sep 2016
- Medium
- Build: master
- # 11897
Is there a particular reason for the edit form to be span9 span3 ??
So I was looking at the odd case that tags and notes are wider than the other fields on the right of the editor. (that's because they do have a class span12 and they shouldn't)
And I thought that scrolling (not necessary on big screens) to get a full width editor might be a better option than the 9/12 of the screen.
And some screenshots will explain better the situation here:
Current state (span9 and span3):
Reducing the right column to span2:
Move the right column above the editor area:
There might be other options here, but these are the obvious ones.
Recap: There are some wrong classes:
https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_content/models/forms/article.xml#L58
and
https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_content/models/forms/article.xml#L23
The width of the column (do we need a right column in the first place) can be smaller or eliminated altogether.
Definitely don't put it on top. We had that in 2.5 and it was hated as you
had to scroll to create / edit any content
Agree with both above.
That one is the most important one and should stay most prominent.
If so then there must be visible in all tabs, or not...
To me it's already big enough. Unless we're trying to make it a full screen editor, the most I'd say to do is switch to span10/2 (ensuring it doesn't cause any funny behaviors on smaller devices along the way).
If so then there must be visible in all tabs, or not...
No, if you switch tabs you are done with editing the content itself and want to adjust its metadata.
All wide (column) texts are hard to read so no need for a wider editor imo.
What is the problem you are trying to resolve
@mbabker I guess thats one of the reasons we use bootstrap's grid.
@Bakual ok
@brianteeman the whitespace on the right of the form could be eliminated/used for something else (editor) https://cloud.githubusercontent.com/assets/3889375/18214201/5e6b95de-7154-11e6-9c82-10c0fc948b9c.png
How about span10/span2:
@brianteeman @yild I hope that people actually use editor.css on their sites, to get the WYSIWYG out of the editor.
But anyway I don't want to argue on an obviously wrong implementation and try to prove that span3 should have been span2 right from the beginning. So let's stay with the random whitespace, if that works for most people
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-09-02 19:59:53 |
| Closed_By | ⇒ | dgt41 |
| Labels |
Added:
?
|
||
I certainly wouldn't put the fields above the text field. That one is the most important one and should stay most prominent. The sidebar is imho fine for that stuff.
As for the width, I guess it's to give more room for the text fields, so you can enter (and read) a bit more characters without scrolling. But I really don't know.