« VG Staff Update: Meddling With Moodle/Current News and Events | Main | potential interviewees »

Dreamweaver

Picture 1.jpg

The class I took this week confirmed for me that Dreamweaver is the way to go. If Dieter and 1-Help can help me figure out the current server situation, we can tell Dreamweaver to capture the VG site--pics, files, warts, and all. Once Dreamweaver captures it we can go to work making templates and cleaning it up.

Picture 2.jpg

So what goes into making the switch beyond the magic push of a button?

1) Planning and designing. Without getting too crazy, I think we should take this opportunity to improve the look and layout of the site. Everything from menus to color to navigation. If we do this part well, everything else will be fairly easy. And, when we've left VG to new folks, the transition will be smooth. Ideally the foundation of the site can be built for longevity even if nifty this-n-thats come and go.

2) Building templates accordingly (or stealing templates accordingly). The templates will really make the site consistent, yet with enough flexibility in the editable content areas for the inevitable variations. No more line by line coding. No cyberduck.

Picture 3.jpg

I think the challenge for us will be to figure out what needs improving, and more importantly, the best way to improve it.

The color panels in this post are from the great Adobe color site, Kuler . They have collections of color families and a tool to create your own color family. The ones here are from the top-rated collections. They are not suggestions, just show-and-tell on the tools and possibilities available for our little site.

TrackBack

TrackBack URL for this entry:
https://blog.lib.umn.edu/cgi-bin/mt-tb.cgi/66948

Post a comment

The views and opinions expressed in this page are strictly those of the page author. The contents of this page have not been reviewed or approved by the University of Minnesota.