Date: Mon, 24 Jul 2006 18:37:43 +0200 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: Hiroki Sato <hrs@FreeBSD.org> Cc: roberto@keltia.freenix.fr, doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, joel@FreeBSD.org Subject: Re: cvs commit: www/en/projects projects.sgml Message-ID: <20060724163742.GE1091@zaphod.nitro.dk> In-Reply-To: <20060725.005910.21928068.hrs@allbsd.org> References: <200607141802.k6EI2L2D019407@repoman.freebsd.org> <20060724153822.GA5102@tara.freenix.org> <20060725.005910.21928068.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006.07.25 00:59:10 +0900, Hiroki Sato wrote: > Ollivier Robert <roberto@keltia.freenix.fr> wrote > in <20060724153822.GA5102@tara.freenix.org>: > > ro> According to Joel Dahl: > ro> > Log: > ro> > Update the projects page a bit. I've removed a bunch of links, some of them > ro> > were dead and some of them linked to unmaintained projects. This is just > ro> > the first step though -- I'm working on a complete rewrite of the projects > ro> > page. > ro> > ro> What about splitting it into a two steps process, one to put data into a > ro> to-be-specified format (YAML?) and the other that generate the SGML? > ro> > ro> That would make it easier to add/remove/edit w/o having to write (and > ro> check) the full SGML/XML "page"... > > I also think that idea is reasonable. We are already using some XML > databases for the purpose, and splitting the page into design and > its contents should make the maintenance easy (and also the > translators happy by using the existing usergroups.xml model, for > example). Considering it's just a long list with a few sections which is only displayed in one place isn't that a bit overkill? I'm not going to complain if anyone does it, but it just seems a bit like overkill to me. -- Simon L. Nielsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060724163742.GE1091>