Victor Engmark wrote:
> 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.
I like that idea: two user interfaces: output HTML and RSS. However,
about XHTML, does it conflict with the mobile devices support goal?. Could
we get all this fitting together?. Again, the same questions?. :)
> > - 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.
Please, add a Savannah task which explain we must try this idea.
OK, done!
> (besides, I think the contact information should be public).
From my experience, if we allow the employer expose her/his email,
[snipped a lot]
I'm sorry I didn't clarify this, but I was not referring to company / user contact info, but the
GNU Herds contact information. That's what I think should be public, and it's for that I'm wondering whether we should just show the email address (a bit more hassle to use a separate program for email) or use a form (more implementation for us, but can
perhaps be better protected against spam).
> > - 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.
Please, add a Savannah task for the Logo idea. You can copy and paste the
above sentences.
OK, done!
> 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).
OK. Link only for the image/logo, not for the title.
Please, add a Savannah task.
OK, done.
> > 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?.
>
> Yes. Our "Timeline" page does the job pretty well already, and we could add
> bits and pieces as we go along. If we add those bits to an Atom feed file
> (or create an Atom file from the database), I already have XSLT to make a
> web page from that.
Cool. Add a Savannah task. As we have a lot of thing to do, I think it is
good we add Savannah tasks to do not forget it.
OK, done!
How to manage all this work, I propose follow the below steps:
1. Convert the webapp to <div>s + CSS, as we have already begun to do,
realizing too small modifications, as the hackers index grouping,
etc. but avoiding huge redesign.
2. Check that it is HTML
4.01 Strict,
and move it to production.
3. Realize the needed translations.
Shouldn't this be done after the redesign? After all, a lot of text will presumably be changed.
4. Carry out the huge redesign.
5. Coordinate with the proposed Klaus' architecture.