WEBSTANDARDS Archives

UofMN Web Standards

WEBSTANDARDS@LISTS.UMN.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
UofMN CSS Web Development <[log in to unmask]>
Date:
Wed, 27 Jan 2010 14:59:10 -0600
Reply-To:
UofMN CSS Web Development <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset=ISO-8859-1; format=flowed
From:
Zachary Johnson <[log in to unmask]>
Parts/Attachments:
text/plain (36 lines)
Valid point... and to support what both you and Andre have said, maybe 
we need the opportunity to setup landing pages for relevant content more 
automatically...

umn.edu/H1N1 could bring users to a page with important content and 
links to other UMN sites for more details.

something like that?


Brian Hayden wrote:
> On Jan 27, 2010, at 2:52 PM, Zachary Johnson wrote:
> 
>> There could be 10 departments who want to promote content about 
>> H1N1... if boynton grabs umn.edu/h1n1 first... what are all those 
>> other departments to do?  boynton.umn.edu/h1n1, medical.umn.edu/h1n1, 
>> cla.umn.edu/h1n1 is a nice solution to the problem.
> 
> I'd agree with everything you said except this. Having info spread among 
> all these sites is a bug, not a feature, and it's one that afflicts the 
> University badly.
> 
> (Obviously this doesn't apply to, say, a site for a study that the SPH 
> might do on H1N1--that is rightfully segregated--but for info that is of 
> general interest we need less fragmentation and duplication of effort, 
> not more.)
> 
> -Brian

-- 
______________________________
Zachary Johnson * Web Manager
Student Unions & Activities
(612) 624 - 7270
http://www.sua.umn.edu/

ATOM RSS1 RSS2