Site Development Notification and Feedback Thread

While I personal do prefer words instead of symbols for discoverability reasons, I don’t see an issue with the edit tag position being above the tag block.

@Princess Luna  
You’re using more vertical space anyway.
 
 
Why is AJAX form splitting necessary in the first place? Does refreshing both source and tags create unnecessary load on the server?

@Barhandar  
Well, technically it does, but it doesn’t matter compared to the problem of them being inseparable creating bugs that would be very complicated to fix without separating them.

@nirvash  
Muscle memory, mostly. People are used to the edit button being down the bottom, and there really isn’t that much of a reason to move it around.
 
I still think that having them next to each other on the same line would be the least intrusive option. That way, all the edit buttons that are view-able to the general public are grouped nicely with the other buttons, rather than having just the tag edit button off on its own.
 
In this instance I’m disregarding the description edit button, as that’s only relevant to the mods/uploader anyways, and it’s also been off on its own for as long as I can remember.

@Princess Luna  
Is it not possible to create invisible divs? Considering how the dupe reporter looked for me vs. everyone else right before its current iteration pretty sure it’s possible to create invisible divs.

Ok, now there’s a word on the button, but the word on the button isn’t the action that the button does. “Tags” is a description of the section, and it should be a header. There should be a button called “Edit” and a button called “History.” Parallel construction.

@Barhandar  
What purpose would invisible divs accomplish?

@Princess Luna  
Splitting the functional areas without touching the UX.

The image description currently just sits in a nondescript title-less box below the ad. Can be very easy to miss.
 
What’s wrong with giving the image description and tags/source a similar subheading comments have now? They could be “Description”, “Tags and source”, “Tools/sharing” (where dupe reporter lives in, for example), and “Comments”.
 
(But I really do like the new tag history button because it instantly comes visible and updates after saving the tags. I don’t have to reload the page anymore to make it visible (so I can check the actual changes). Whatever design you do next, please keep the history button like that.)

@JP  
Ah yes, I need to make the word still appear when you can’t edit, forgot about that when I put the word into the button.  
History instantly becoming visible is a side-effect of actually putting things localized, since our AJAX resets the whole area with up-to-date data after the form is submitted. While it was certainly possible to update that part too, it would’ve required quite the reshuffle.

I’m going to in a moment do as suggested with having the word “Edit” and the header separate.  
Preview:  

 
On a slightly different note, I’d like to change post/comment UI a bit so it’s more consistent with the rest of the site.  

@Princess Luna  
Looks terrible

@Princess Luna  
Don’t. Please. ‘Edit Tags’ and ‘Edit Source’ on the buttons were perfectly fine.
 
The comments don’t need to be changed, either. I think that they’re perfectly fine as they are.

Derpibuttons.org
 
^{Powered by the buttons-on-rails project - version 1.4.0-6663020 (master)  
Served by Mr. Mash (13.37ms)}

@Princess Luna  

 
I don’t understand what you mean by this.  
Nothing else on the page looks like those buttons until you made the comment refresh look like that.  
So how is it making it consistent when it’s making it look like nothing else on the page?
 
Really, my biggest criticism with a lot of these latest changes is that they make everything look more cluttered. More shapes, more lines, most stuff on the page.  
Visual clutter.

@Zeb  
We don’t use that text size anywhere else and we also don’t really use pure links as buttons anywhere else now.  
Meanwhile, we have buttons all over comments/posts in creating and editing them, as well as the image options area of course.

@Zeb  
Agreed.
 
@Princess Luna  
But why change them? They really do look fine as-is. I don’t know why you’re so hell-bent on making everything ‘uniform’. It’s good to have variation here and there. The comment buttons aren’t the main focus of the comments, so I don’t see why they need to be altered in such a way that they draw more attention to themselves.

@Princess Luna  
Personally, I never noticed anything about the text size.  
But setting that aside, I meant there’s nothing else on the page with the boxes around them.  
I don’t see how adding the surrounding boxes makes them “conform” to the page when nothing else is like that.

@Princess Luna  
First pic: I hope you’ll consider repositioning the Edit and/or History buttons for the tag and source fields, as I wouldn’t call the current [button][text][button] sandwich arrangement to be ideal, especially for the source field where the History button is affected by the variable length of the URL.
 
Second pic:  

 
The font size is consistent with the rest of comment footer, its size and current styling serves to visually de-emphasize it against the main comment body. In addition, I believe the component is prevalent enough throughout the site that it’s unique size could be justified.

Deleted image pages now show the tags, cause they were never really a secret. This should help remembering what something was.
 
Tag and source editing will be split very soon. For now, I’ll be trying to improve how source deals with very long sources.
 
After that, UI will probably not change much for a while, as there’s a lot of issues with third-party code to deal with that have accrued over the years, as well as some dev environment setup issues. Backend stuff that should have no real impact to users other than some small speedups; but we should be able to increase development capacity soon if it all works out well, which may mean being able to do overhauls down the line.
 
@Marker  
I think the font size is too small though. It’s not very user-friendly, especially the more you need to use that area.
 
@Zeb  
The post button has a box. There are quite a lot of actual buttons on Derpibooru. Comments/posts are unusual compared to the entire rest of the site. And not in a good way.

@Princess Luna  

THANK CELESTIALUNA, finally.

@Princess Luna  

 
Thank you.

@Princess Luna @Brokedownandmadeone  
I just thought about it. Would there be anything against also displaying the source, considering the idea that takedowns are usually due to “DNP anywhere else”? That way the image from its original source can still be viewed/saved on the artist’s posted page.

@Brokedownandmadeone  
The biggest problem is then we’d have to scrub sources on Rule #5 (and some Rule #1) images, which would then also mean we’d have to leave notes for ourselves to remember the sources if we need to check things later. Tags aren’t expected to ever be able to contain anything we can’t display to people.

@Princess Luna  
Oh, right. Forgot about Rule #5 takedowns.