> -----Original Message-----
> From: Christopher Lenz [mailto:[EMAIL PROTECTED]]
> Sent: 13 January 2003 11:07
> To: Cactus Developers List
> Subject: Re: New web site generation and organization
> 
> Vincent Massol wrote:
> [snip]
> >>Currently, there are a lot of broken links on the pages, because
they
> >>haven't been converted to the size:id/ext:id URL format yet... but I
> >>guess you're aware of that ;-)
> >
> > Could you tell me where? I've tried to convert almost all I knew.
BTW,
> > external links will work even when not converted to the ext:id
notation.
> 
> Really, there are many :-P
> Do a search for href="*.html", and sort the external links from the
> search results.

Oops... You're right. I had forgotten lots of places .... I have now
committed a modification to our stylesheet that reveals the problems.

> 
> If we want to enforce putting all internal and external links in the
> sitemap, the stylesheet could probably check for that and issue an
error
> if the contract is violated.

Yep. Done (first version).

> 
> >>Hmm, it'd be nice to have some link-crawling ant task as build step,
> >>to check for broken links...
> >
> > hehe... I knew this one was coming :-). It's actually one of the
reason
> > for the sitemap so that we can easily have all the links in one
place.
> 
> Yeah, but typos, or simply forgetting to put a new page in the sitemap
> still produce broken links. Some automated quality control would be
> nice, but of course we can do without - hey we could also do without
> unit tests ;-)
>

I have modified the stylesheet to report invalid ids, so typos should be
caught now.
 
> I would love to have such a task available anyway, maybe I'll be able
to
> work on it soon...
> 
> >>I also couldn't see the sub-menuing in action. A major revamp of the
> >>menus would probably have the most benefit for the documentation.
> >
> > Normal, I haven't used them yet in what I have committed :-). But
the
> > feature is there.
> 
> Okay, cool.
> 


-Vincent



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to