Site Development Notification and Feedback Thread

It still doesn’t look good, even when I have a look at it against the ‘vanilla’ site:
 
Off:  

 
On:  

Is it me or the preview images are smaller that usual now? In the front page.

@The Luna Fan  
Nothing changed.

@Princess Luna  
It must had been chrome being chrome, now it’s back to normal…

@evan555alpha  
It should look better now after I fixed its line-height.
 
On another note, I’m putting in some minor changes from the splitting of tags and source editing early, adding icons to things. This also includes two extra edit buttons for tags/source, to try to not go immediately to them being the only options. The plan is to later remove the “Edit tags/source” button, then later on, actually deploy what makes the two forms separate, after people have gotten used to using the edit button next to “Tags:”.

@Princess Luna  
But why not just have the edit tags and edit source buttons next to each other? Moving it around seems pointless.

The edit tags button being above the tags like that kinda stands out as awkward. It’s the only thing on that line, and seems unnecessary to add that extra line between the description and the tags.
 
If it is better code-wise for the edit tags/source button to be two separate things, then I’d say keep the edit tags button down next to edit source button. It would be consistent [Both metadata editing buttons on the same line] While also not adding in an extra area solely for 1 button.
 
So, keeping the edit tags button and edit source button on the same line as the edit tags/source button is now.

The formatting toolbar looks kinda wonky on mobile:  

@Zeb  
This is not possible to do without incredible complication in the UI. Our AJAX updating methodology is to have a form and a non-form (the edit button unhides the form and hides the non-form its in) and when the form submits, the response is used to replace a specific ID that encompasses both to reset things.  
If we made the buttons in a different area, we would thus need to respond with a larger area encompassing everything, which would then replace the other area with its default state too. We would have to do a complete overhaul of the JS to only reset the one area and the one button; that is not happening.

@Princess Luna  
I’m not fully sure I understand what you’re saying.
 
From what I can gather: You’re saying that keeping the edit tags button and the edit source button on the same line would cause the code to shit itself?  
Like, since clicking the “change tags/source” button currently changes that area to have the “save changes” and “cancel” buttons, If you did that with the change source/tags being two separate buttons, it would be extremely complicated and screwy with the code.
 
Correct?

@Zeb  
Two buttons is fine, their ability to submit and reset the forms independently while being across a div from what they do is not. You can only reset one area with the AJAX.  
Basically, while I can make it such that “Edit Source” only opens the source form for editing, and “Edit tags” only opens the tag form for editing, submission of either one would need to reset tags, source, and both buttons.

And now, the row below source has been cut up and distributed where the buttons logically belong. I’m sure that the history buttons aren’t in the optimal positions; might need spacing out later.  
This is pretty much the final frontend look for things. The hope is to get people used to using the edit button up top before the one down low only does source editing.

@Princess Luna  
The edit buttons are extremely tiny (easy fix: include “tags:” and “source:” in the button itself); and “logically belong” is an exceptionally poor reason to mess with established ergonomics. Especially after you admitted yourself that it doesn’t matter whether the button is below or above tags (also, the “logically belong” is “next to”, not specifically “above”, and the only “modify” buttons on the whole site that were above the content are “edit description” and gallery controls).

@Barhandar  
Wholly agreed. Moving one of them around was not needed at all.

@Barhandar  
Ya, they definitely look really ugly, and aren’t readily apparent as the way to edit the tags/source.

@GyroTech  

 
^This.
 
I also agree on it being awkward having the button being above the tags. But that part especially.

@GyroTech  
@Zeb  
These are legit concerns as well; removing readable-by-all-site-users “Edit” in favor of an icon that many will not understand without having to learn what it means (and some of the particularily disabled won’t ever understand until explained because they can’t connect “pencil and square” to “edit”) - moreso when all other major buttons on site have icon AND text to avoid the issue and provide redundancy - is a bad idea.

Teeny tiny buttons with no words are super not cool from both a UX and an accessibility standpoint. Please fix.

Also being after follows the natural fluid editing tags. You have to read they’ll know that you have to add one. And on Mobile or on longer lists you’ll have to scroll back up.

@Barhandar  
The final design includes the whole word inside the button. It was just a more intermediate change to leave the edit button next to the word (like Description has been doing for the last 2 or 3 years).  
Putting the edit button below tags would make it right above Source’s edit button. And we do have to separate them, or else the AJAX form replacement won’t be separable between them once the forms are actually split.

@Princess Luna  
What if you placed the tag change button below the tags, and the source change button below the source instead of next to it?  
Then they’d both be below their respective fields, and have something separating them.

@Princess Luna  
Although the change is kinda jarring, it’s not a bad change. It’ll just take some getting used to.

I just wish there was a per-user option to hide the buttons I don’t want to see. I probably use less than ~20% of them at all, ever, and as I’ve gotten older, the more buttons something has, the less I want to use it.

@Zeb  
Maybe, although this comes with using a lot more vertical space on sources.  
One thing I’m considering is if it’d be best to swap the tag-related buttons with the whole source row. However, I currently don’t think it’d be correct to do so.
 
@BigBuggyBastage  
Hmm, I can’t think of any buttons I’d ever want to perma-hide personally. I think it’s best to just make things less intrusive. I would like to note that I’m trying to keep amount of buttons down; I think we might have a few too many too close together at the moment, and this is at least a mild improvement.

@Princess Luna  
Thanks for the response. :) I agree that it’s a ‘density’ issue too, and appreciate your wanting to keep things neat.