Victor Engmark wrote:
> - "Job offers" feed (in <head>). Very little extra markup, but useful for
> anyone who doesn't want to use the site more than absolutely necessary.
I do not understand, any way, I add a task because it looks interesting.
Task: https://savannah.nongnu.org/task/index.php?6772
in <head>, users who prefer feeds (maybe they are using many job sites, and can't be bothered reading them unless necessary) can get all our job offers without even reading the front page.
Another idea wrt. this: We should provide job feeds for any and all searches. That should be relatively easy if we use the same PHP file to output HTML and RSS. Just add a "format" parameter (like in the <link> above). This is one place where XHTML is useful: We could use the same module to output markup for the web site and for feed items.
> - A <div> with new job offers could be useful for new users to gauge how
> much traffic we're getting, and for casual users who don't want to use RSS
> or email.
Well, such users can take a quick look at the JobOffers list, sorted by date.
Isn't it?.
Yes, but if we could show that on the front page, that's a lot of users which save one click. We'll just have to see if it's worth taking up the space.
> - Contact information could be useful, but we might want to use a form
> to avoid spam. Dunno which is most effective.
The View_Job_Offer pages are public, but they do not show contact information.
Anyway, I think we must check it.
The View_Qualifications pages are no public, only the JobOffer owner to which
such qualifications are subscribed can access it. It is by design of the
webapp, and checked by the Access Control Lists.
I don't think it's enough to make pages with email addresses non-public (besides, I think the contact information should be public). We'll have to have some spam filtering in place, or rely on the individuals on the list to filter themselves. The latter may even be most productive, since because we're using different filters, it's unlikely that everyone will get the same false positives.
> - Language switching.
We have language switching now at the heading. Do you mean something
different?.
No, just listed for completeness.
> - Logo + title linking to the front page.
Instead of the herds photo?. Good, very good point!.
I don't deserve credit for this - I just listed it for completeness, and used "Logo" instead of "Picture" :) But
you have a good point! Is there a good designer among us?
Logo ideas:
- Many copies of the gnu from the GNU logo in profile, repeated behind each other, fading towards one side to give the illusion that there are lots of unseen gnus, and that there is dust obscuring them.
- One or several gnus, seen stampeding in the direction of the user. Maybe a bit intimidating for a job site ;)
- A field of grazing gnus, from above or the side.
By the way, I know it's probably sacrilege at this point, but the name is very similar to GNU Hurd, and I don't think the ensuing confusion will help us. What do you think?
One comment: If we add a link to the title, it will change its color. Maybe
that will not be good for the look&feel. Therefore, is the link at the title
actually convenient?.
We could force the heading to be formatted not to look like a link, but you're right. Also, it should be enough to have a link on the logo; that's where users expect it (I'm pretty sure I read that in Jakob Nielsen's Alertbox).
> Things I think we should not include on the front page:
> - A <div> with site news. On a service site like this, most users
> won't care a bit whether we've changed languages, moved servers, or
> got a new developer. It could be served as a feed or a secondary
> page, however.
So, you propose to add a news page?.