A) Anchor text links
For a while I've been trying to argue that form and content aren't truly separate in html composition because it's nothing like paper. How could I have forgotten one of the best ways to prove that: Text anchors.
If being able to link within the page is an integral part of how the page will "work," plan ahead for that please. However, if you're composing in html right now and you try to add them at this stage the "links"may change as the file's name or position changes. Fixing it shouldn't be too difficult, though.
B)gif. problem solved?
I've found that saving .gifs with Fireworks makes for higher-quality .gifs. Adobe products could likely do even better. Just something to keep in mind, that's all.
Monday, July 14, 2008
Thursday, July 10, 2008
Minutes for July 10th, 2008
The ULMLWPC had a meeting on July 10th which began at about 11:37 and ended at about 12:15pm. In attendance were:
CH
KC
ML
MMag
MW
LJ
KN
(did I miss anyone?)
-- The committee decided to focus on sub-page content today
-- "Design" issues are not priority right now. There is still some confusion as to who exactly will be responsibile for that, but it will certainly involve Rob Glaze, Mike Magee, and Karen Niemla, at least.
[This process will begin as soon as it possible.]
-- The committee decided to assign pages to be developed so that the content will be ready [guidelines to follow]
-- The assignments are...
CH:
Databases by name
Databases by Subject
newspapers
MW:
Off-campus access
The Reference Desk
Contact
Distance Learning
Purchase requests
Job Opportunities
KN:
Tutorials
For faculty/Staff
For Students
Comments
ML:
Ask A Librarian
Subject Librarians
Style Guides
Staff and Departments
Interlibrary Loan [will no longer simply link to Iliad]
Tours and Instruction
copying/printing
KC:
Visitor Information
History [um, of the library]
For the Community
CR:
Friends of the Library
MM:
Computer Lab [not marked on sheet, but I assume it's his]
Orphans:
[these links don't truly need anything new in terms of content or will be handled in a special way. If they do later, we can arrange something]
FAQs
Subject Guides
Floor Plan
Blog
Annual report
Policy
Privacy
[Did I miss anything?]
Everyone who has been assigned pages, please stand by for further instructions.
0. No images, no cells. Just plain text or plain html text. If you have pictures that must be included, have them ready for later but not actually in the document.
1. If, during the course of your composition, you start to feel that your page may be too big or if you're not sure what your page is for, you may post to the blog (or email me/us) and ask about eliminating or splitting up that subject link.
2. Very small page content is O.K. as long as the page is needed because hopefully the design will allow it. This is one situation where the two blend (I've explained this before: http://ulmlwpc.blogspot.com/2008/01/small-is-good.html )
3. If you compose in Word or something like that, any formatting you do (italics, bold, lines, etc.) will be lost because it will be converted to plain text first.
If you want to use formatting and keep it, you may if you use Seamonkey or another html composer. Then using your copy later will be easy because part of the work will already be done. I highly recommend it (having learned the hard way).
But if all this is too confusing... just go to your computer and click start => programs => accessories => Notepad. This makes clean plain text all the time, every time.
4. Is your page going to link to another page in the text? Make a note of it, and it can be added later.
5. Is your page going to reside on the ulm.edu/reference/ directory? If so, you do not need to wait. You likely have ftp access to this directory and may upload any pages you deem suitable as long as the rest of the reference staff is O.K. with it. However, "design" is subject to change, and just because the page is there doesn't mean that anyone is acutally linking to it.
6. Deadline: August 7th.
If you have questions before then, post to the blog or email someone else on the committee. (I'll mention again that if you don't have a Gmail account, you may email your message to me and I'll post it for you)
CH
KC
ML
MMag
MW
LJ
KN
(did I miss anyone?)
-- The committee decided to focus on sub-page content today
-- "Design" issues are not priority right now. There is still some confusion as to who exactly will be responsibile for that, but it will certainly involve Rob Glaze, Mike Magee, and Karen Niemla, at least.
[This process will begin as soon as it possible.]
-- The committee decided to assign pages to be developed so that the content will be ready [guidelines to follow]
-- The assignments are...
CH:
Databases by name
Databases by Subject
newspapers
MW:
Off-campus access
The Reference Desk
Contact
Distance Learning
Purchase requests
Job Opportunities
KN:
Tutorials
For faculty/Staff
For Students
Comments
ML:
Ask A Librarian
Subject Librarians
Style Guides
Staff and Departments
Interlibrary Loan [will no longer simply link to Iliad]
Tours and Instruction
copying/printing
KC:
Visitor Information
History [um, of the library]
For the Community
CR:
Friends of the Library
MM:
Computer Lab [not marked on sheet, but I assume it's his]
Orphans:
[these links don't truly need anything new in terms of content or will be handled in a special way. If they do later, we can arrange something]
FAQs
Subject Guides
Floor Plan
Blog
Annual report
Policy
Privacy
[Did I miss anything?]
Everyone who has been assigned pages, please stand by for further instructions.
Guidelines to Make Life Easier:
0. No images, no cells. Just plain text or plain html text. If you have pictures that must be included, have them ready for later but not actually in the document.
1. If, during the course of your composition, you start to feel that your page may be too big or if you're not sure what your page is for, you may post to the blog (or email me/us) and ask about eliminating or splitting up that subject link.
2. Very small page content is O.K. as long as the page is needed because hopefully the design will allow it. This is one situation where the two blend (I've explained this before: http://ulmlwpc.blogspot.com/2008/01/small-is-good.html )
3. If you compose in Word or something like that, any formatting you do (italics, bold, lines, etc.) will be lost because it will be converted to plain text first.
If you want to use formatting and keep it, you may if you use Seamonkey or another html composer. Then using your copy later will be easy because part of the work will already be done. I highly recommend it (having learned the hard way).
But if all this is too confusing... just go to your computer and click start => programs => accessories => Notepad. This makes clean plain text all the time, every time.
4. Is your page going to link to another page in the text? Make a note of it, and it can be added later.
5. Is your page going to reside on the ulm.edu/reference/ directory? If so, you do not need to wait. You likely have ftp access to this directory and may upload any pages you deem suitable as long as the rest of the reference staff is O.K. with it. However, "design" is subject to change, and just because the page is there doesn't mean that anyone is acutally linking to it.
6. Deadline: August 7th.
If you have questions before then, post to the blog or email someone else on the committee. (I'll mention again that if you don't have a Gmail account, you may email your message to me and I'll post it for you)
Wednesday, July 9, 2008
Yeah, Those pages I was talking about...
I'm keeping my work in this directory on my site:
http://bambam.info/webexp/
I probably should've posted more things sooner, and I'm still working on these, of course.
There's a no-no on some of those pages... transparent PNGs! I've tried to achieve the same effects using .gifs, but the results are ugly (cannot use gradients at all). I've heard that there's a way to create high-quality .gifs with lots of colors. If anyone knows how that can be done, please let me know!
Only IE6 has any problems rendering transparent PNG pixels (they appear as solid gray and do not interfere with content, but it looks bad).
And there's also, of course, the other page I've already made, too.
Please post anything you-all have come up with.
http://bambam.info/webexp/
I probably should've posted more things sooner, and I'm still working on these, of course.
There's a no-no on some of those pages... transparent PNGs! I've tried to achieve the same effects using .gifs, but the results are ugly (cannot use gradients at all). I've heard that there's a way to create high-quality .gifs with lots of colors. If anyone knows how that can be done, please let me know!
Only IE6 has any problems rendering transparent PNG pixels (they appear as solid gray and do not interfere with content, but it looks bad).
And there's also, of course, the other page I've already made, too.
Please post anything you-all have come up with.
Tuesday, July 1, 2008
Edinboro U changes web page too
Many many many months ago I believe I showed you-all Baron-Forness Library page as an example of a bad web page. I went back there to see what databases they had while I was evaluating one, and found out that they've completely changed it. And guess what they did?
http://cms.edinboro.edu/departments/library/
The same thing we're doing! It's still not that great, but it's waaaaaaaaaaaay better than it was. Hooray for 'Boro.
Here also is a picture of one of my prototype pages at 800x600 resolution. I'm surprised how much room that really is.
http://cms.edinboro.edu/departments/library/
The same thing we're doing! It's still not that great, but it's waaaaaaaaaaaay better than it was. Hooray for 'Boro.
Here also is a picture of one of my prototype pages at 800x600 resolution. I'm surprised how much room that really is.
Thursday, June 5, 2008
The IRS site
http://www.irs.gov/index.html
I stopped by the IRS site today to find out about stimulus checks, and I noticed that their site looks similar to UNF's, but even more boring. The look is simple to implement, looks neat, and is fairly easy to navigate. Not all government sites can say the same.
I stopped by the IRS site today to find out about stimulus checks, and I noticed that their site looks similar to UNF's, but even more boring. The look is simple to implement, looks neat, and is fairly easy to navigate. Not all government sites can say the same.
Monday, June 2, 2008
Some things that we do know
To lessen confusion, here's a list of things that we actually do know already:
0. Everything we do should look good in all major browsers
This is a requirement of all web designers. It is also rather difficult.
1. No transparent PNGs
PNG images are far, far superior to GIF images in almost every way (for stills). Yet we can't use them for transparent pixels and it's all IE6's fault. Transparent pixels in PNGs will simply not display in IE6 (but will in GIFs). Why care about IE6 when there's IE7? Because Microsoft is mean and won't let anyone without XP or higher use IE7 at all. I know this because I have Windows 2000, which I refuse to part with because I love it so much. I use Firefox, but not everyone knows to do that. So if some of our users still have Windows 98 or something, it simply won't work out.
( EDIT: I really, really want to break this rule whenever possible. PNG is superior.)
2. Will all sub-pages need to follow the look of the home page?
Sometimes yes, and sometimes no. What is appropriate for each page will be used. Quite actually, I like the idea of mass unification better. Which means that I wouldn't mind changing the reference page to something new. Yet the upcoming "for students" page (which is yet to be made) would look nice if it were similar to what the reference page is now. However, this doesn't need to be decided right away.
3. Breadcrumbs
As I've said before, this is not only a good idea, but is essential. When I brought this up at a meeting, I recall that everyone agreed.
How this is to be implemented, however, is debatable. I'm still in favor of a table at the top of the page (like our site has right now) with the breadcrumb links put right into it.
4. Slim, centered tables are good
So elegant:
http://www.unf.edu/library/
If we borrow anything from UNF, it's the table size. Very neat, and it looks more or less the same at all common resolutions. (Anyone with less than 800x600 should by now be used to absolutely nothing ever looking right). I know we've talked about this at a meeting before.
5. ULM has standard colors
This makes life quite a bit easier. The page colors I use the most are:
That's all from the old blog. In fact, now that I think of it, the old Blog was almost entirely about making pages. So it could be worth a look. Or not. http://www.ulm.edu/%7Eniemla/webpages.htm
6. CSS?
I've used a teeny bit of CSS in some things I've made. But entirely tableless CSS? I have no idea. If anyone else knows how to compose something this way and make it look good on all major browsers, I'm all for it.
7. Do not compose in Word
Word makes a mess of your markup. I learned the hard way. Use something else, like Seamonkey.
...Does anyone have anything to add to this list that I have forgotten?
0. Everything we do should look good in all major browsers
This is a requirement of all web designers. It is also rather difficult.
1. No transparent PNGs
PNG images are far, far superior to GIF images in almost every way (for stills). Yet we can't use them for transparent pixels and it's all IE6's fault. Transparent pixels in PNGs will simply not display in IE6 (but will in GIFs). Why care about IE6 when there's IE7? Because Microsoft is mean and won't let anyone without XP or higher use IE7 at all. I know this because I have Windows 2000, which I refuse to part with because I love it so much. I use Firefox, but not everyone knows to do that. So if some of our users still have Windows 98 or something, it simply won't work out.
( EDIT: I really, really want to break this rule whenever possible. PNG is superior.)
2. Will all sub-pages need to follow the look of the home page?
Sometimes yes, and sometimes no. What is appropriate for each page will be used. Quite actually, I like the idea of mass unification better. Which means that I wouldn't mind changing the reference page to something new. Yet the upcoming "for students" page (which is yet to be made) would look nice if it were similar to what the reference page is now. However, this doesn't need to be decided right away.
3. Breadcrumbs
As I've said before, this is not only a good idea, but is essential. When I brought this up at a meeting, I recall that everyone agreed.
How this is to be implemented, however, is debatable. I'm still in favor of a table at the top of the page (like our site has right now) with the breadcrumb links put right into it.
4. Slim, centered tables are good
So elegant:
http://www.unf.edu/library/
If we borrow anything from UNF, it's the table size. Very neat, and it looks more or less the same at all common resolutions. (Anyone with less than 800x600 should by now be used to absolutely nothing ever looking right). I know we've talked about this at a meeting before.
5. ULM has standard colors
This makes life quite a bit easier. The page colors I use the most are:
#e5e5cd
#a39058
#cfad46
#660000
6. CSS?
I've used a teeny bit of CSS in some things I've made. But entirely tableless CSS? I have no idea. If anyone else knows how to compose something this way and make it look good on all major browsers, I'm all for it.
7. Do not compose in Word
Word makes a mess of your markup. I learned the hard way. Use something else, like Seamonkey.
...Does anyone have anything to add to this list that I have forgotten?
Sunday, June 1, 2008
May 29th minutes
(there is no real explanation for the lateness of these minutes)
The ULMLWPC had a meeting on May 29th which began at about 11:40 and ended at about 12:00pm. In attendance were:
CA
CH
KC
CR
ML
MMag
MW
LJ
KN
(did I miss anyone?)
(As I expected) This meeting did not go anywhere, as the most difficult part of the process is coming.
-- everyone seems to be happy with the category names and link names for the time being
-- Mike said that Rob will be making the new pages
-- Karen C. suggested that we make more demo-version pages and then decide what we want
-- so we've decided to think more about what sort of page we want
The ULMLWPC had a meeting on May 29th which began at about 11:40 and ended at about 12:00pm. In attendance were:
CA
CH
KC
CR
ML
MMag
MW
LJ
KN
(did I miss anyone?)
(As I expected) This meeting did not go anywhere, as the most difficult part of the process is coming.
-- everyone seems to be happy with the category names and link names for the time being
-- Mike said that Rob will be making the new pages
-- Karen C. suggested that we make more demo-version pages and then decide what we want
-- so we've decided to think more about what sort of page we want
Subscribe to:
Posts (Atom)