Template header messed up
#11
Oh, a suggestion - given the jumping the gun here and in a certain other thread
It'd probably be a good idea to post a thread in Site Info announcing when you're going to make a change like this and lock it to admin (or whatever level) posting only so that it can then be updated when it's completed (or progress along the way even).
Just because not everyone views Site Info regularly enough to ensure people know about it in advance, I would think it's one of the first places people look when there IS something going on.
Communication's everything in an endeavour like this
It'd probably be a good idea to post a thread in Site Info announcing when you're going to make a change like this and lock it to admin (or whatever level) posting only so that it can then be updated when it's completed (or progress along the way even).
Just because not everyone views Site Info regularly enough to ensure people know about it in advance, I would think it's one of the first places people look when there IS something going on.
Communication's everything in an endeavour like this
#12
It's a work in progress. It's been posted several times that I've begun to transition to "v5" and that things will be under renovation for the next couple of months as I work through it. If you see something amiss that's the likely cause. I'm not keen on posting an update about every change because it adds administrative overhead to an already tendious and time-consuming process. I just want to get it finished and I'm lazy.
If you think it's worth the bother I can try but I've not convinced it's going to make any practical difference. Stuff is going to change pretty regularly. If I'm going to change something which changes the functionality or organization I would normally post something but for cosmetic changes I would think it makes any difference in the end. I can tell you the header design is going to change but it's still going to change just the same and getting used to those changes isn't going to be any easier.
Even I'm confused by it right now. There are some little details I see lacking with it I'm going to fix. It wasn't possible to plan it perfectly. Once the loose ends are tied up the new navigation should make intuitive sense (I hope).
If you think it's worth the bother I can try but I've not convinced it's going to make any practical difference. Stuff is going to change pretty regularly. If I'm going to change something which changes the functionality or organization I would normally post something but for cosmetic changes I would think it makes any difference in the end. I can tell you the header design is going to change but it's still going to change just the same and getting used to those changes isn't going to be any easier.
Even I'm confused by it right now. There are some little details I see lacking with it I'm going to fix. It wasn't possible to plan it perfectly. Once the loose ends are tied up the new navigation should make intuitive sense (I hope).
#13
Fair enough - I was aware of v5 stuff, didn't realise there were cosmetic changes though, hence not realising this was part of it.
I take your point that it was cosmetic but that's exactly the type of change that is going to attract attention due to its nature. Just look at the "Changes" thread in UK S2000 to see what it provoked.
I'm not suggesting you broadcast what every little change is, that would create a massive admin overhead, you're right. Something as obvious as changing the header though, particularly something that should you be interrupted (as it looks like you were) would look rather odd, I think it would be worth just a quick post to say it will be disrupted and then another when it's finished.
Ultimately it's just a judgement call really.
Hopefully I'm not teaching granny to suck eggs It's rare these days that I come across situations where my experience is applicable but IN my experience, communication is the most important aspect of change control. As long as people know what's going on, or at the very least that something is going on at all, then they don't get surprised or pissed off.
I take your point that it was cosmetic but that's exactly the type of change that is going to attract attention due to its nature. Just look at the "Changes" thread in UK S2000 to see what it provoked.
I'm not suggesting you broadcast what every little change is, that would create a massive admin overhead, you're right. Something as obvious as changing the header though, particularly something that should you be interrupted (as it looks like you were) would look rather odd, I think it would be worth just a quick post to say it will be disrupted and then another when it's finished.
Ultimately it's just a judgement call really.
Hopefully I'm not teaching granny to suck eggs It's rare these days that I come across situations where my experience is applicable but IN my experience, communication is the most important aspect of change control. As long as people know what's going on, or at the very least that something is going on at all, then they don't get surprised or pissed off.
#16
I guess I was just bored last night and decided to monkey around with it and then it was done...well partially done, done enough that it still worked even if it was ugly. Once I started I was commited. Had I planned ahead I probably would have said something.
Hours are tricky because daytime hours for me are the busiest times of the day. That leaves my evenings and weekends. The ideal time to do these things is 3:00AM but that's not practical. The trouble with being open 24/7 is you are never closed
Hours are tricky because daytime hours for me are the busiest times of the day. That leaves my evenings and weekends. The ideal time to do these things is 3:00AM but that's not practical. The trouble with being open 24/7 is you are never closed