The official HighWire website is http://highwire.atari-users.net/ . However, if you are looking for uptodate web browser proto-types & test builds, sources & developer documentation, or tools & libraries, then proceed to this websites main page.

Neither this website and nor its contents are endorsed by either the current maintainers of the Official HighWire website or the Official HighWire CVS . You can partition for changes in this respect by posting on the Official HighWire Developers Mailing list. If you are not currently on the mailing list, you can try reading the mailing list archives first. For an outline of the content to be provided to the official highwire project, see this document.
 

The content and layout of this website is maintained in a format consistant with the current HighWire website layout simply because that when the time comes to add them to the official website, no work is involved in moving the content or linking to pages across web servers. To contribute content currently made available only by this website, an outline of its structure and what is needed, is available here.
 

The need for a web browser development site for Atari ST compatibles is based on the discussions in this German thread and this English thread .
 
HighWire is, at time of writing, the only open source web browser for Atari ST compatibles currently in active development and is in desperate need of work in key areas. However it is not the only web browser available in source form, with some of the key componants currently lacking in HighWire, there is overlap into ofter areas of development. These inter-related areas are all in need of a centralized home on the internet due to the shear lack of developers available for any one Atari ST based project, and the fact that web browser technology covers a rather vast set of disciplines.
 
The addition of related development material & files, discussions & help made available on this website for those wishing to develop HighWire, is supplimented by the inclusion of references, breakdowns of, and direct links to other web browsers for Atari ST compatibles, including a number of other open source projects considered viable for porting to any MiNT/TOS based platform. This would be out of place in the development of a normal project, where inclusion of anything from the opposition is excluded in one way or another, except for portal sites.
 
The truth of the matter is, as apparent from mailing list and web sites, that there are just not enough people in the Atari ST world to go around all the projects that are in demand of there services, weather they are programers, designers, or text engineers. For anyone wanting to gauge an idea of how things are, look around at the most popular, commonly used and newer projects and developments, by reading there Changelogs, and you will see, for example over the last 10-15 year period, the same names keep coming up, and that project developments have stopped in their track when maintainers and administrators have become inactive. This is reflected in the push to open source as many Atari ST applications as possible over the last few years.
 
One of the main aims of this web site is to prove the viability of centralized developer information for projects at a generic level, as a hub, in this case web browser development for various GNU GCC and native developemnt setups, provided in such a way that there is not stalling in the required administrative processes and public availablity due to a lack of people with administrative rights. Because of the way this project and its website is set up it also provides for things which is strictly outside the main and official project development, yet are tightly linked to source code and developer material. The best way to view this relationship is as a sister site to the main project, where child development happens, and anything worth redeming is abosorbed back into the parent project.
 
This website achieves a second goal of providing an offsite CVS backup of sources. One side affect of this service is that it provides greater exposure of the HighWire project in general. Another side affect is that it can also be used to provide CVS branches to anyone who has a Sourceforge user name, and wishes their development and files to be placed in a central point open to the public domain, particularly where those developments may be outside the scope of current maintainers or official website inclusion.
 
The hope is that other projects will adopt a similar all inclusive approach, and that other hub sites will be spawned to provide as many inter-connected access points through the internet for both developers & users, including those long time Atari ST fans & and people new to the MiNT/TOS platform. As it turns out a lot of content needs to be updated, fixed or pulled from achive sources in order for this to be fully realised, and before any enhancements can seriously be considered for TOS & GEM platforms. GEM in itself extends out into the Intel x86 field, which is also where the majority of Linux and Posix based ports are, so it should be obvious why develop documentation in particular needs to be centralized in many places.