So we're now using drupal. Users, stories and links have been moved over. So many downloads were broken that we're just going to start from scratch with those. Everyone should submit useful files to the new downloads section. You can still get files from the old version of the site.

Some differences in drupal: You have a menu whose title is your user name. This menu lets you do lots of different things. In particular, it has a 'Create content' submenu where you can submit files, stories, links, polls or post in the forums.

Also important is the 'view submissions' item.

I've found a replacement for PostNuke called Drupal which is vastly superior. It may take a few weeks to get everything ported over, but the old version will remain until the new version is fully ready to go. You can check out the new version here.

I've been working on a couple new themes for the site. I made the Slashdot theme for practice, but I think it came out pretty well. The Miller theme doesn't really do justice to the design provided by Joshua Miller, but it's not bad. I'll work on refining it some more when I get time.

Because downloads need to be written by the web user, and sourceforge is a pain in the ass, the downloadable files were world writable. Some $%#!@ thought it would be cute do go around deleting other peoples' files.

Don't be shy about submitting news. Not all news has to go on the front page. Other news can be found in the 'Categories' menu on the right side of the main page. Submitting a news article is a good way to provide more information about a download you submit.

You can also submit tutorials and info for people working with particular programming languages; they can go in their own categories. If you think we need more categories for anything, feel free to ask. It's not hard for me to add more.

If you'd like to help out with the community site, that's good too.

Since loosing stuff is bad, we'll be implementing a new backup policy which will put a copy of all the important stuff in a nice safe place every night.

The only parts of the site really affected by this are the message boards and the wiki Please re-create any changes that have been lost once we are back on the main server.

The outage affected all projects that start with j, q, s, or y as well as all users whose login names start with c, i, r, or z.

We now have a wiki but currently it's almost completely unchanged from the default install. It's up to all the jEdit users to turn it into whatever you want it to be. Get a user name and go to work. Almost everypage can be edited by anyone. If you've never used a wiki before you can play around in the Sandbox web to try things out. Some content suggestions to get you started:

Configurations for working with java, C++, HTML, etc

Tips for people switching from Emacs, vi, bbedit, ...

Feature suggestions for jEdit or plugins

We're going to call the latest site update completed. Not everything we hoped to do has been finished, but everything that's here works. A few of the biggest changes:

Download submissions will be stored locally rather than on individual user's servers.

Much nicer forums. If feasible, the old messages will be ported over.

While only registered users can start new forum topics, anyone can read and respond to them

Outdated information has been removed

Hopefully we'll get a wiki up and running soon too. If you have ideas for further improving the

Does anyone want to help out a bit with the community site? It needs some outdated content removed (jEdit 4.0-era documentation). Also an update to the latest PostNuke release would be nice.

It seems the message boards section of this site is not being used very much, and I must admit I don't follow the postings much either. Perhaps this section should be shut down, and everyone encouraged to just use the mailing lists instead? Post your comments below.

I have redesigned the jEdit web site, thanks to Ollie Rutherfurd who submitted a mockup! Tell me what you think of the new look.

Currently, it contains a mode that performs additional syntax highlighting for Ant build.xml files. If you have written a mode which you think others might find useful, but which cannot be included in the core, submit it here. Modes like this include extended Java modes that have a list of all classes, or HTML modes that include a list of all HTML tags.

We are in the process of upgrading the content management software used by jEdit Community to the latest version (0.702) of Post-Nuke. During this period, many of the features of the site may not be available. Thanks for your patience; we should have everything up and running again soon.

The Web Links area of jEdit Community is intended to provide visitors with links to resources that may be of specific benefit to users of jEdit, most of whom are working programmers and many of whom are Java programmers. We don't need links to the major commercial vendors (you know who they are), but if you have come across a resource that is especially helpful to you in your work, particularly if the resource is an Open Source package or application, please submit a link listing and share your discovery with the thousands of people who visit jEdit Community.

I have created a PayPal account for accepting monetary donations to jEdit development. Note that this is entirely optional; jEdit is not, and will never become, shareware. You can use it as much as you want, guilt-free, without donating a single cent. Details here.

The jEdit home page needs some screenshots of jEdit 4.0; there aren't any there yet. Please e-mail me some jEdit 4.0 screenshots (PNG format only, please).

A few users have asked about the mechanics of submitting a macro script to our Downloads area. The easiest way to do this is to go to the Add download page of the Downloads area and fill out the form. If you want to upload your macro to the jEdit Community server instead of supplying your own link, leave the URL empty and send your source file as an email attachment to John Gellene. Now you have no excuse, so let's see your macros!

Some of the databases have been uploaded to the jEdit Community server, while others are available through download links posted by the person who compiled the database. Because the databases are not the conventional `type` of compiled binary, issues regarding licensing and distribution could be raised by the authors of the code base. We do not offer any view on whether those issues actually exist or how they might be resolved, but we have decided to take a conservative, practical approach to the uploading of CodeAid databases.

• We will accept for uploading CodeAid databases derived from software issued under an Open Source license.
• We will accept download links to other servers for CodeAid databases where the code base is subject a "community" `type` license or some other license that permits distribution of source code by parties other than the copyright holder.
• Ultimately It is the responsibility of the person mantaining the download link (and, of course, anyone downloading the database) to make sure that use of a database is permitted.

Notable changes from jEdit 3.2.2 include the new Buffer class (which is no longer derived from the Swing Document class) and changes in the Plugin API that will simplify the writing and maintenance of plugins.

The javadocs distribution will be updated with successive developement release of jEdit 4.0.