Wiki content at LiveSites Changed by someone at IP 62.220.217.5 :
@@ -1,42 +1,12 @@
<article>
<title>AxKit - Site List</title>
<section>
-
<para>
-Interested in who uses AxKit?
-</para>
-<para>
This page holds a list of sites that wish to let people know that they use
AxKit. It is by no means definitive, but if you are proud of a site you have
produced please feel free to add the details here by clicking on the "Edit this
page" link at the bottom of the page, and adding your details. The XML format
should be fairly intuitive ;-)
</para>
</section>
<section>
<title>
- <ulink url="http://81.102.75.26/";>Liquid Silicon
Developments</ulink>
- </title>
- <para>This is interesting in the fact this is running on Windows. No?
Yes!
- Current configuration is as follows :
- Apache/1.3.27 (Win32) AxKit/1.61 mod_ssl/2.8.14 OpenSSL/0.9.7b
mod_perl/1.27_01-dev PHP/4.3.2-RC2.
- I broke python unfortunately. This is running multple virtual servers,
footer contains links to
- a virtual server and an external site for project files.
- </para>
- <para>
- Any questions about the configuration, like 'How did you get it to
work?' email me
- at [EMAIL PROTECTED]
- </para>
- </section>
- <section>
- <title>
- <ulink url="http://www.nikki-site.com";>Nikki-Site</ulink>
- </title>
- <para>Nikki-Site is one of the oldest non-profit, volunteer
- based Japanese language web diary / blog portal that has been
- around since 1996. We've recently moved to an almost entirely
- AxKit-based site.</para>
- <para>Subscribe to [EMAIL PROTECTED] for discussion on AxKit
- in Japanese!</para>
- </section>
- <section>
- <title>
<ulink url="http://www.groveart.com";>Grove's Dictionary of
Art</ulink>
</title>
<para>
@@ -66,41 +36,50 @@
<ulink url="http://www.howlingfrog.com";>Howling Frog Internet
Development</ulink>
</title>
<para>
- Although our site (<ulink
url="http://www.howlingfrog.com/";>http://www.howlingfrog.com/</ulink>)
- is fairly simple, AxKit helped make it a WHOLE lot easier to keep
consistent.
- Although we'd used XPathScript in the past to do the majority of our
- transformations, we've moved on to using XSLT now for the majority
- of things. Although I'm sure we're not stressing AxKit or using all
- of the various features that it offers, we've been extremely happy
- with AxKit.
+ Although our site (<ulink
url="http://www.howlingfrog.com/";>http://www.howlingfrog.com/</ulink>) is
fairly simple, AxKit
+ helped make it a WHOLE lot easier to come up with and keep
+ consistent.
+ We're primarily using simple XPathScript to do the transformations
+ from
+ XML to HTML, and aren't using any of the super-cool features that
+ AxKit
+ gives us (e.g. different output styles from a single content-base),
+ but
+ have been extremely happy with AxKit.
</para>
<para>
- We knew we wanted something that'd let us keep our site content in XML
as
+ We knew we wanted something that'd let us keep our site content in XML
+ as
we've worked with too many customers in the past that ended up with
nothing but nightmares because their HTML designer did everything by
- hand and didn't use any sort of management tool/style.
+ hand
+ and didn't use any sort of management tool/style.
</para>
<para>
- One really nice thing that AxKit let us do is cascade our stylesheets
- together when doing transformations. Generally, we build up most
- of our content with a custom "page" XML schema that we use
- internally. For other types of pages though (e.g. "software"), we've
- use a separate stylesheet to take that "software" page and transform
- it into our custom "page" XML first, and then render that through to
- the final "page->HTML" transformation. This alone saved us tons of
- grief that'd otherwise be spent trying to maintain several separate
styles
- that all "look sorta the same". By the time we were done setting up
all
- of the styles, we had it to the point that if we wanted to update the
- "look+feel" of the site we were down to a single stylesheet that
needed to be
- updated; all of the others just rippled-through and picked up that
style on
- their way out.
+ The one "nice" thing that we've had AxKit do for us, is cascaded
+ XPathScript stylesheets. Generally, we build up most of the content
+ for
+ our site in a custom "page" XML schema that we use internally. For
+ other
+ types of pages though (e.g. "software"), we've got a stylesheet set up
+ that'll take the "software" page and then convert that to the standard
+ "page" XML first, then crank that through the end-result "page->HTML"
+ stylesheet, and we're done. This alone saved us tons of grief that'd
+ otherwise be spent trying to maintain several separate styles that all
+ "look sorta the same". By the time we were done setting up all of the
+ styles, we had it to the point that if we wanted to update the
+ "look+feel"
+ of the site we were down to a single stylesheet that needed to be
+ updated;
+ all of the others just rippled-through and picked up that style on
+ their
+ way out.
</para>
<para>
- Submitted by Graham TerMarsch at Fri Feb 01, 2002 08:10:22 PM.
- Updated on July 9, 2003 00:06:32 AM.
+ Submitted by Graham TerMarsch at Fri Feb 01, 2002 08:10:22 PM
</para>
</section>
@@ -122,7 +101,7 @@
</title>
<para>
All about satellite TV and Radio with
- <ulink url="http://www.internet-world.nu";>
+ <ulink url="http://www.satmania.com/eng/tvguide";>
up-to-date schedule
</ulink>
for more
@@ -130,7 +109,7 @@
</para>
<para>
- Site is build around AxKit, using Perl, XSLT, and Sessions. It
+ Site is build around AxKit, using Perl, <B
style="color:black;background-color:#A0FFFF">XSLT</B>, and Sessions. It
supports multiple browsers and interface languages. Currently only
<ulink url="http://www.satmania.com/eng";>English
@@ -149,16 +128,16 @@
<para>
Under AxKit transformation pipeline looks like this:
Apache::RegistryFilter >>> Apache::AxKit::Provider::Filter
>(XML)>
- AxKit first stage XSLT >(XML)> AxKit second stage XSLT
>(HTML)>
+ AxKit first stage <B
style="color:black;background-color:#A0FFFF">XSLT</B> >(XML)> AxKit
second stage <B style="color:black;background-color:#A0FFFF">XSLT</B>
>(HTML)>
</para>
<para>
- The key is two stage processing by AxKit. First stage XSLT is chosen
- on per-page basis. The second stage XSLT is the same for all pages. It
+ The key is two stage processing by AxKit. First stage <B
style="color:black;background-color:#A0FFFF">XSLT</B> is chosen
+ on per-page basis. The second stage <B
style="color:black;background-color:#A0FFFF">XSLT</B> is the same for all
pages. It
separates browser/internationalization support logic from interface
sprecifics. The browser type and language requested is chosen by Perl
script based on HTTP_USER_AGENT setting for browser and URI for
- language. So at the second stage XSLT adds (or removes) attributes
+ language. So at the second stage <B
style="color:black;background-color:#A0FFFF">XSLT</B> adds (or removes)
attributes
from HTML tags based on browser selected. And it removes all text,
which is in languages others than selected.
</para>
@@ -175,10 +154,10 @@
<section>
<title>
- <ulink url="http://www.upmystreet.com/";>upmystreet.com</ulink>
+ <ulink url="http://www.<B
style="color:black;background-color:#ffff66">upmystreet</B>.com/"><B
style="color:black;background-color:#ffff66">upmystreet</B>.com</ulink>
</title>
<para>
- We <ulink url="http://www.upmystreet.com";>(upmystreet.com)</ulink>
+ We <ulink url="http://www.<B
style="color:black;background-color:#ffff66">upmystreet</B>.com">(<B
style="color:black;background-color:#ffff66">upmystreet</B>.com)</ulink>
use AxKit to drive our Sky Digital
WapTV service. We use our own XSP taglibs built using TagLibHelper
to interface into our pre existing perl libraries. The XML
@@ -199,7 +178,7 @@
</para>
<para>
- Submitted by Mike Chamberlain, Senior Systems Engineer,
Upmystreet.com at Fri Feb 1 11:47:45 EST 2002
+ Submitted by Mike Chamberlain, Senior Systems Engineer, <B
style="color:black;background-color:#ffff66">Upmystreet</B>.com at Fri Feb 1
11:47:45 EST 2002
</para>
</section>
@@ -220,6 +199,9 @@
delays or troubles serving 850,000+ hits per day.
</para>
+ <para>
+ Submitted by Michael Kröll at Tue Feb 5 11:17:43 EST 2002
+ </para>
</section>
<section>
<title>
@@ -243,68 +225,4 @@
of this year...
</para>
</section>
- <section>
+</article>
- <title>
- <ulink
url="http://latitudes.walkerart.org";>latitudes.walkerart.org</ulink>
- </title>
- <para>
- This on-line companion to the Walker Art Center's recent show 'How
Latitudes Become Forms' was developed over a month's time and was the Walker's
first use of AxKit. We found the separation of the site's design (using XSLT
files) and programming (mostly via TaglibHelper-based taglibs) to be very
efficient, and the site's performance under load has been very satisfactory.
Based on this experience, AxKit has been selected as the technology that will
be used to rebuild the Walker's main website.
- </para>
- </section>
- <section>
- <title>
- <ulink url="http://today.icantfocus.com/blog/";>I Can't
Focus</ulink>
- </title>
- <para>
-<a href="http://today.icantfocus.com/blog/";>I Can't Focus</a><img
src="/img/out.png" /> is the personal website of me (Christopher H. Laco). It
is built using AxKit for both the static pages as well as a wrapper around my
weblog using Apache::Filter and Movable Type.
- </para>
- </section>
- <section>
- <title>
- <ulink url="http://www.distortedcerebration.net";>Distorted
Cerebration</ulink>
- </title>
- <para>
- Distorted Cerebration is just a little blog I put together so that
I could learn AxKit (and web design in general). The site is completly dont
using AxKit. (<ulink
url="http://www.distortedcerebration.net/entry/Dissecting_This_Web_Site";>Read
more here</ulink>)
- </para>
- </section>
- <section>
- <title>
- <ulink url="http://crew.ccs.neu.edu/";>CCIS Crew</ulink>
- </title>
- <para>
- The Northeastern University College of Computer Science Volunteer
Systems Group uses AxKit to produce much of its content. Most of our site is
handled by the <ulink
url="http://search.cpan.org/author/MSERGEANT/AxKit-XSP-Wiki-0.06/lib/AxKit/XSP/Wiki.pm";>AxKit::XSP::Wiki</ulink>
wiki and custom XSLT style sheets for the quotes page, FAQs, etc. We also use
XSP to manage the registration and team reports for our <ulink
url="http://crew.ccs.neu.edu/ctf/";>Capture the Flag</ulink> contest.
- </para>
- </section>
- <section>
- <title>
- <ulink url="http://topicmaps.bond.edu.au/";>TopicMaps @ Bond
University</ulink>
- </title>
- <para>
- Website serving DocBook articles for TopicMap related via AxKit. It
uses AxKit::XSP::Blog for displaying blog information.
- </para>
- </section>
- <section>
- <title>
- <ulink url="http://www.freedomoflanguage.com/";>Freedom of
Language</ulink>
- </title>
- <para>
- The start of a Multilingual Portal Content Management system. The
first content is an English course but watch this space.
- </para>
- </section>
- <section>
- <title>
- <ulink
url="http://www.hek.uni-karlsruhe.de/";>Hermann-Ehlers-Kolleg</ulink>
- </title>
- <para>
- Hermann-Ehlers-Kolleg is a student hostel in Karlsruhe, Germany. We
use AxKit to transform our XML/XSP-based website with LibXSLT to XHTML1.0 with
CSS.
- </para>
- </section>
- <section>
- <title>
- <ulink url="http://aom.nachbaur.com/";>Mozilla AOM Reference</ulink>
- </title>
- <para>
- This online reference was created to fill the gaping hole in the
available Mozilla developer documentation. It documents Mozilla's Application
Object Model, describing each object, method and property a developer has
access to, with examples and descriptions. Though no fancy AxKit features are
used other than straight-up XSLT, it shows just how rich of a site can be
created by merging multiple XML data sources (especially the tool-tip prototype
definitions in source-code samples).
- </para>
- </section>
-</article>
