Re: New MCF pages

Sorry, I sent it to the wrong address.

En réponse à ChristianHJW <[email protected]>:
> > - place some title and/or alt text informations when you includes
> images
> >   on a web page
> 
> Sorry for my stupid question, but what is the reason to do that ?

For the next reason I give ;)
Actually if you try to validate your HTML code on the W3C validator it will
tell
you that putting an alt information on every image is mandatory. (at least for
strict (X)HTML). And the title one help to display a text information (Mozilla
handle the Title one, not Alt) when you pass over an image. This is also VERY
important for text based browsers (no pictures, so each picture has to be
described) or blind people.
 
> > - test the pages in lynx (or links) to make sure all valuable
> > informations are available.
> 
> We had a few people browsing the pages with Mozilla and all were happy,
> so
> we should be fine i guess.

Mozilla, as MSIE, is error compliant. If there are some mistakes in the code,
the page will still render normally.

> > - I see that all the pages have URLs like
> > http://mcf.sourceforge.net/newpage/?content=Project Page
(notice the
> > blank space in the URL :( ) . This is not acceptable for various
> reasons :
> 
> The decision to make standard design available in a php script was done
> by
> mf and myself, and i fully back it up. The main reason to do this was to
> be
> able to update the content easily, without having to change the whole
> page

Well, I assume that the site update will be done from a Web Form... That makes
working offline on the site a hell. Especially when you work without the
original design locally. If you can explain me how it can make things easier...

> all the time, especially with respect to updating content from CVS one
> day.

You can update the site from CVS with static HTML pages. PHP is worth if you
have a database behind, not a CVS. (copying the submitted HTML pages to the
website on each check-in should be possible)

> After all the work that has been invested from mf and hikke to get it
> up
> this way i dont recomment to change it now.

I think it's time NOW that is not launched. After it will be a bigger work.

> > * many search engines don't collect informations on dynamic pages.
> And
> > we definitely want to be searchable in a good way
> 
> There is a simple solution to that i guess, we should setup a normal
> HTML
> page also containing all the important expressions surrounding MCF, and
> then
> link from this page to the other ( dynamic ) pages .

So what's the use of dynamic pages if you have the same static ones ?
I'm sure the specs and many other sections don't need to be dynamic.
If you want something efficient that can be updated with a web form daily
easily, you can have the result of the form produce different static HTML
pages.
That will be the only needed dynamic part on the site (only available to
admins).

> > * using one page for a whole site (index.php ?) can look sexy from a
> > coders point of view. But it's a hell to maintain (especially for
> people
> > using Dreamweaver or who don't know PHP).
> 
> I thought its easier to update the content once its done ?

It's equal, if not worse.

> > * there is no need for dynamic content on most of this pages. This
> would
> > be MUCH easier to use simple static (X)HTML in this case. Design
> > consistency can be enforced with CSS Stylesheets and maybe SSI
> includes
> > (don't know if Sourceforge support that).
> 
> We decided to use php for this and i hope you can live with that.

But don't make a whole site in 1 page !!!! Especially if 90% of the site only
need static pages.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf