AfterStep is a window manager for the Unix X Window System. Originally based on the look and feel of the NeXTStep interface, it provides end users with a consistent, clean, and elegant desktop. The goal of AfterStep development is to provide for flexibility of desktop configuration, improving aestetics, and efficient use of system resources.

Please have a look at the news page to learn more about the upcoming releases of AfterStep 2.0. Latest Version 2.0 final was released on September 28, 2004!

Some of the distinguishing features of AfterStep compared to other window managers are its low usage of resources, stability and configurability.

These pages provide an introduction and reference to the wonderful world of AfterStep, and serves as a distribution point for the latest stable and development releases. We kindly invite you to explore AfterStep and hope you'll come to appreciates its power and potential.

This website was designed to mimick the default look of AfterStep 2.0 as close as possible. All graphics have been rendered using ascompose, supplied with the AfterStep distribution. The entire clipart used to render graphics was taken from actuall files supplied with AfterStep.

Note that the ability to change the colorscheme of this website is mimicking one of the most interesting new features in AfterStep 2.0 - Colorschemes.

The xml script used to render this site is available here.
Colorscheme definitions are availbale here : Crimson, Deep Red, Gold on Blue, Green Sea, Lime, NeXTish, Peru, Purple, Sea Water, Silver, Stormy Skies, Turquoise, Washed Blue,
Here is the script that could be used to interpret above xml files.
The entire source for this web site is available at our CVS repository, to get it do:

    cvs -z9 -d :pserver:anonymous@cvs.aftercode.net:/home/cvsroot login
    cvs -z9 -d :pserver:anonymous@cvs.aftercode.net:/home/cvsroot co www.afterstep.org

We really need help of webmasters, PR, documentation writers, and of course coders. Please e-mail Sasha Vasko, who's busy doing all of the above almost alone for now.
If you intend to send patches via email then remember that inlined diffs in email will most probably be broken during transfer or at time of viewing. If you want to avoid it and send patches compressed and as attachments then this could be handy.
    diff -Nur ... ... | bzip2 -9 > patchX.diff.bz2; mpack patchX.diff.bz2 sasha@aftercode.net