Release Management Case Study - Formerly "Styling Fixes"

Went at this some more today, and fixed a lot of problems. I think all the text should be readable now.
The personal details page was making me nuts, until I pulled out the background. If everything is too darn light, I say just make the background darker!



I also played around with the quote and code windows, and borrowed a box shadow or two from HWC.



One thing I still need to figure out is how to control the color of the user generated links, but I think I'm going to put this aside for awhile. So if you want to make changes, go right ahead and I'll start from this version next time I take another wack at this.

(This next version is 1.3.2 and ready for action.)

 

I removed the gradients from the Form-Type overlays to preserve their opacity as I discussed in Base Camp.

 

I made 1.3.2 the default style just now. I couldn't find any problems, and it's certainly better than the earlier version.

I'm still on the fence about the box shadows on the quotes. I like the way they look, but they might end up being too distracting.

 

I did something I should have not done wh

Yes, it is.

All this is really nice work.. there is so much of it too.

So I just switched to 1.3.1... but now I see 1.3.2!

 

So I am switching run whatever is the site default.

 

Yes, I made 1.3.2 the default yesterday. There are a lot of fixes in place now.

 

I can 't put a finger in the specific changes, but the overall effect is really good.

I am relieved that xf update did not cause problems, I hope that is the case.

 

I spent most of the weekend on this. There are a lot of very small but important changes, mostly in the area of making text contrast with the background. What a challenge!
The xf update gave me that outdated template message, but once I drilled down to find out which template was causing the problem and pasted a copy from dev into it by hand (they recommend merging manually) the error message went away. I will probably get that message every time I make changes in a version I copy from here and load up to dev, so at some point I need to upgrade my dev version. It doesn't look that hard to do, but if I do it myself I'd rather try that when you're not so busy in case I need help.

There was one small tweak I made today in the log in screen you get when you hit the page from email but aren't logged in.






I'll be on the lookout for places this new class screws up something else, but for now that problem is off my list.

 

I have been noticing it just keeps getting nicer.

 

Thanks, Dan.
I think all the glaring obvious problems have been corrected, but there are a few places I still need to make improvements. I think there will always be places I can make improvements-- the thing is though I get to a point where it might be more efficient to learn some new tricks before tackling it again. Or maybe I just want to catch my breath.

In the meantime we can sit tight on the Longview 1.3.2 version.

 

I made a small update today when I noticed that the link to toggle out of the bbcode mode was invisible. It seems faster to just take care of these things when I encounter them, instead of putting them on a list somewhere and never getting to it.
Here is the change:

 

I am glad you are giving yourself a break on this. It is deserved and bigger fish are starting to pile in the pantry.

This is a huge fish you made into a long term sushi supply.

This place is beautiful and amazingly original and innovative. You are a genius Kirsten.

 

This design is going to win awards as soon as we have a better pile of public content.