[Manual] installer-manual on the website (was: release plans for website?)
On Mon, Aug 02, 2004 at 10:55:38PM -0400, Joey Hess wrote:
> Is there any plan for how the web site update will be handled for
> sarge's release? Besides just switching the names and links to sarge,
> I've been looking at what parts of the web site will need updating for
> the new installer and other missing bits. These include:
> - sarge/installmanual: doesn't exist. One possibility is to link to the
> sarge install manual in the debian archive on a mirror, which is
> updated whenever the images are updated. I don't know how the woody
> install manual is imported into the web site so maybe however it is
> manage is better.
This is how the installation manual was handled for boot-floppies (i.e.
potato and woody): The sources where checked out from the
boot-floppies CVS and were build locally.
I investigated a bit how to handle the sarge installation manual:
The installation manual doesn't build on woody AFAICT, so manual
build is probably no option until www-master is updated to sarge,
and I think nobody want rely on that. So linking to an external
resource like the archive or copying it from there would be better.
Some questions to consider:
- The boot-floppies manual was built as PDF, plain text and HTML.
I think at least plain text and HTML should be available for
sarge, too. Yet I don't see any generation of plain text
currently. Is this intentional?
- For usage on the website the files should be able to be handled
by content negotiation. This requires that there is only one directory
per arch with all translations in it and files named foo.<langcode>.html.
Would it be possible to generate the pages this way or should we write
a little script that solves this by renaming the current output files?
Frank Lichtenheld <email@example.com>