Site Development Notification and Feedback Thread

@evan555alpha  
Yeah, I don’t like this one either.

@LightningBolt  
Yeah.
 
Dunno why, but I don’t like the idea of the reporting tab being the standard visible one.

@Princess Luna  
I can understand why the reporting tab being visible by default would make sense since it’s a guaranteed size and, on average, the smallest of the 3 tabs, but honestly I think I’d prefer to make the Faves tab the default. It was next in line for a reason - it’s more useful and more used than the reporting tab.
 
But really, why not leave the first tab for history in general, even if you move the edit buttons up? The history links look really out of place.

@WingbeatPony  
I mean, I literally can’t remember the last time I’ve clicked the “Favouriters” tab, but I’ve definitely reported stuff (although that’s not particularly frequent either).
 
EDIT: Actually it seems I’ve only ever reported 3 actual images… which still means I’ve used it more than the Favouriters tab.

@evan555alpha  
Four reasons:  
1 - Together with the new description UI, it makes for a unified way to label and provide edit buttons for the different editable areas of an image.  
2 - Enter could save source trivially.  
3 - One less tab, so that UI for tags and source isn’t holding back visibility of the report buttons.  
4 - Disentangling tag updating with source updating, which would make for a cleaner frontend and backend.
 
@Lead Pie  
@WingbeatPony  
The favouriters tab is very expensive to render, can grow exceedingly large, and AFAIK is used about as often as most things in people’s attics.
 
Sharing is another contender, but I think it’s a little tall, I’d want to redo its layout before making it the default tab (the three on-site links could be in one row).

@Princess Luna  
I may have buried the lead on my comment. What I probably should have said is that, even if you move the edit buttons up to their respective categories, it’d still be preferable to have the tag/source history in one of the tabs below (as compared to the proposed awkward location adjacent to the tags and source).
 
I completely understand the desire to reduce the amount of space the tabs consume by default, as well as your point that the faves tab is easily the most complex, potentially longest of the four. However, I’m not a fan of the reporting tab being the first visible one, not only because it serves a negative purpose, but because it appears alarming in its default state. Without hard numbers to back me up, I can say anecdotally that the faves tab is more useful to me, as I am more likely to check if a friend (or fellow IRC member) has faved an image before linking it to them - not reason why it should be visible, necessarily, but rather why it takes precedence amongst the non-visible tabs.

@WingbeatPony  
100% agree. Having the reporting tab being the default frames the page in a different, negative light compared to the tags tab. Plus the tags tab is the shortest at 1 line. Best to leave the link to the tag/source history there, or have all tabs hidden by default.

@GyroTech  
This.  
Though hidden might be more complicated.

@GyroTech  
@Lead Pie  
What about the sharing tab, were it significantly more compact?  

@Princess Luna  
It still won’t be as compact as the tags single line.

@Princess Luna  
What that’s missing that it currently has is a way to differentiate what the various embed codes mean - Perhaps “copy small,” “copy thumbnail,” and “copy preview,” along with better spacing? Or simply move the existing titles inline, and leave them on individual lines? Either way, I’m not a fan of the BBcodes on the same line like that. It’d still be good to touch up the layout of that tab eventually, I just don’t think it’s a solution to the present problem.

@Princess Luna  
Honestly the red/yellow there is distracting me too much to really tell what’s going on in most of your screenshots ¯\_(ツ)_/¯

@SuperSupermario24  
I also love starlight glimmer and the grand revolution, but that’s too much :v

@SuperSupermario24  
Yellow->Azure (it’s the link color)  
Red->Grey (backgrounds, shading is same as dark theme approximately)

I removed a lot of excess stuff from the featured image box. It’s no longer (visually) a box!

@Princess Luna  
So the entire sidebar, New Images, and Watched Images sections on the homepage all get boxes, but featured doesn’t? It now sticks out like a sore thumb:  
 

 
It doesn’t fit in with the rest of the homepage, unless whatever it is you’ve done has broken something unintentionally.
 
And trust me, it looks even worse with my userscripts that add actual buttons back to the “minimalism” theme.

@evan555alpha  
This.
 
Why was there any need for removing stuff ? Boredom I suppose ?

@evan555alpha  

 
I think that was the point.

I’d actually like to make it bigger so it covers the full width of the sidebar. And yeah, it’s the featured image, it should stand out instead of blend in.

@Princess Luna  
I’m for it. Emphasis shouldn’t have to come at the expense of consistency.

@byte[]  
@Princess Luna  
Well yes, and while I agree, the way in which it was done doesn’t look good. There’s all that extra padding which does nothing but look useless, and isn’t consistent with the rest of the page.
 
You’re right, making the featured image bigger so that there isn’t all that padding would be the best way to go about it. It would, as WBP said, be more consistent.

@evan555alpha  
Made the featured image bigger.

I think it looked nicer when the “Featured image” had a blueish background, like the page number bar next to it and the “Trending images” title.

Did either f968723333 or 2b22e46cac do something to image sizes in the profile section?
 
The profile page used to show the last five image thumbnails in Artwork / Uploads / Favorites in a neat row, but now the fifth image is booted to a new line, which triples the area of the profile page. The thumbnail sizes on (my) gallery view are unchanged.

@Shayzorr  
Accidentally broke when refactoring, now fixed.