Switch to XSL for two reasons:

1. It allows us to put the McKinley die in the upper right corner of
   the page and thus make it part of the header. This is aesthetically
   more pleasing.
2. It makes it easier for us to add news entries.

Aside for point 1, the page is still the same as the previous index.
This commit is contained in:
Marcel Moolenaar 2004-09-25 17:36:31 +00:00
parent a92a2b9942
commit f8d1ca8d72
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=22472
5 changed files with 136 additions and 66 deletions

View file

@ -1,4 +1,4 @@
# $FreeBSD: www/en/platforms/ia64/Makefile,v 1.1 2003/01/19 09:50:31 marcel Exp $ # $FreeBSD: www/en/platforms/ia64/Makefile,v 1.2 2004/08/31 18:13:27 marcel Exp $
.if exists(../Makefile.conf) .if exists(../Makefile.conf)
.include "../Makefile.conf" .include "../Makefile.conf"
@ -7,7 +7,18 @@
.include "../Makefile.inc" .include "../Makefile.inc"
.endif .endif
DOCS= index.sgml machines.sgml refs.sgml todo.sgml DOCS= machines.sgml refs.sgml todo.sgml
DATA= mckinley-die.png merced-die.png DATA= mckinley-die.png merced-die.png
_GEN= index.html
DATA+= ${_GEN}
CLEANFILES+= ${_GEN}
index.html: index.xsl news.xml
${XSLTPROC} ${XSLTPROCOPTS:N-nonet} -o ${.TARGET} ${.ALLSRC}
.if !defined(NO_TIDY)
-${TIDY} ${TIDYOPTS} ${.TARGET}
.endif
.include "${WEB_PREFIX}/share/mk/web.site.mk" .include "${WEB_PREFIX}/share/mk/web.site.mk"

View file

@ -0,0 +1,10 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $FreeBSD$ -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:variable name="base" select="'../..'"/>
<xsl:variable name="email" select="'freebsd-ia64'"/>
<xsl:variable name="title" select="'FreeBSD/ia64 Project'"/>
</xsl:stylesheet>

View file

@ -1,64 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/platforms/ia64/index.sgml,v 1.5 2004/02/01 01:24:32 marcel Exp $">
<!ENTITY title "FreeBSD/ia64 Project">
<!ENTITY email 'freebsd-ia64'>
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<table width="100%">
<tr>
<td>
<hr>
<form action="http://www.FreeBSD.org/cgi/search.cgi" method="get">
<center>Search the ia64 mailing list archives:
<input type="text" name="words" size="50">
<input type="hidden" name="max" value="25">
<input type="hidden" name="source" value="freebsd-ia64">
<input type="submit" value="Go">
</center>
</form>
<hr>
</td>
<td>
<img src="mckinley-die.png" align="right" alt="McKinley die">
</td>
</tr>
</table>
<h3><a name="toc">Table Of Contents</a></h3>
<ul>
<li><a href="#intro">Introduction</a></li>
<li><a href="#status">Current status</a></li>
<li><a href="todo.html">What Needs To Be Done</a></li>
<li><a href="machines.html">Hardware List</a></li>
<li><a href="refs.html">References</a></li>
</ul>
<h3><a name="intro">Introduction</a></h3>
<p>The FreeBSD/ia64 project pages contain information about the FreeBSD
port to Intel's IA-64 architecture; officially known as the Intel Itanium&reg;
Processor Family (IPF). As with the port itself, these pages are still
mostly a work in progress.
</p>
<h3><a name="status">Current status</a></h3>
<p>The ia64 port is still considered a tier 2 platform. This boils down
to not being fully supported by our security officer, release engineers
and toolchain maintainers. In practice however the distinction between
a tier 1 platform (which is fully supported) and a tier 2 platform is not
as strict as it seems. In almost all aspects the ia64 port is a tier 1
platform.<br>
From a developer point of view there's an advantage to have the ia64
port be a tier 2 platform for a while longer. We still have a couple
of ABI breaking changes in the pipeline and having to maintain backward
compatibility this early in a ports life is less than ideal.</p>
&footer;
</html>

View file

@ -0,0 +1,85 @@
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:import href="../../includes.xsl"/>
<xsl:import href="includes.xsl"/>
<xsl:variable name="date" select="'$FreeBSD$'"/>
<xsl:output doctype-public="-//W3C//DTD HTML 4.01 Transitional//EN"
encoding="iso-8859-1" method="html"/>
<xsl:template match="/">
<html>
<xsl:copy-of select="$header1"/>
<body alink="#0000FF" bgcolor="#FFFFFF" link="#0000FF" text="#000000"
vlink="#840084">
<table cellpadding="0" cellspacing="0" width="100%">
<tr>
<td border="0">
<xsl:copy-of select="$header2"/>
</td>
<td>
<img align="right" alt="McKinley die" src="mckinley-die.png"/>
</td>
</tr>
</table>
<hr/>
<form action="http://www.FreeBSD.org/cgi/search.cgi" method="get">
<center>
Search the ia64 mailing list archives:
<input name="words" size="50" type="text"/>
<input name="max" type="hidden" value="25"/>
<input name="source" type="hidden" value="freebsd-ia64"/>
<input type="submit" value="Go"/>
</center>
</form>
<hr/>
<h3>
<a name="toc">Table Of Contents</a>
</h3>
<ul>
<li>
<a href="#intro">Introduction</a>
</li>
<li>
<a href="#status">Current status</a>
</li>
<li>
<a href="todo.html">What Needs To Be Done</a>
</li>
<li>
<a href="machines.html">Hardware List</a>
</li>
<li>
<a href="refs.html">References</a>
</li>
</ul>
<h3>
<a name="intro">Introduction</a>
</h3>
<p>
The FreeBSD/ia64 project pages contain information about the
FreeBSD port to Intel's IA-64 architecture; officially known as
the Intel Itanium&#174; Processor Family (IPF). As with the port
itself, these pages are still mostly a work in progress.
</p>
<h3>
<a name="status">Current status</a>
</h3>
<p>
The ia64 port is still considered a tier 2 platform. This boils
down to not being fully supported by our security officer, release
engineers and toolchain maintainers. In practice however the
distinction between a tier 1 platform (which is fully supported)
and a tier 2 platform is not as strict as it seems. In almost all
aspects the ia64 port is a tier 1 platform.
<br/>
From a developer point of view there's an advantage to have the ia64
port be a tier 2 platform for a while longer. We still have a couple
of ABI breaking changes in the pipeline and having to maintain
backward compatibility this early in a ports life is less than
ideal.
</p>
<xsl:copy-of select="$footer"/>
</body>
</html>
</xsl:template>
</xsl:stylesheet>

View file

@ -0,0 +1,28 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- Simple schema for FreeBSD Project news.
Divide time in to <year>, <month>, and <day> elements, each of which
has a <name>.
each <day> element contains one or more <event> elements.
Each <event> contains an optional <title>, and then a <p>. <p> elements
can contain <a> anchors. Within the "href" attribute of the anchor
$base will be replaced with the base URI necessary to reach the FreeBSD
document root, and should always be used to start URLs at www.FreeBSD.org
or one of the mirrors.
Use the <title> element if the <p> content is lengthy. When generating
synopses of this information (e.g., for syndication using RDF files),
the contents of <title> will be preferred over <p>.
-->
<news>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD$
</cvs:keyword>
</cvs:keywords>
</news>