Main server updated

The MusicBrainz web pages have been polished and cleaned to be web standards compliant. We proudly serve the pages in XHTML 1.1, CSS 2.0 compliant mode.

The user interface has been given a face lift and a cleaner look.

We have made great steps on the terminology changes, which had hung in limbo for quite some time. From now on, the term ”album” is reserved for release attributes. The albums are now called ”releases”. The same is true for the term ”moderation”: we replaced this with the more appropriate term ”edit”.

Lots of static pages have been replaced with WikiDocs pages. This means that most of the documentation pages displayed on this very server are no longer static html pages, but are instead content transcluded from the MusicBrainz Wiki. For each of these pages, a given revision is labeled as “official content”, and is displayed inside the MusicBrainz site. (For example, compare http://musicbrainz.org/doc/ContactUs to http://wiki.musicbrainz.org/ContactUs). If the content is not labelled as official, it can still be browsed in the same way, but will be labelled as unofficial content. WikiDocs is a huge project, and some parts will always be in the works. Please talk to the Wikizens if you’d like to contribute!

New features

The “Release Editor” (nicknamed “The edit page to rule them all”) replaces the FreeDB Import, the CD-Lookup as well as the “Edit all” workflows. It supports all the edit types usually applied to core entities (artist/release/tracks), including single artist conversions, various artist conversions, but also explicit changes to one track artist of a single artist release. This will allow us to more flexibly edit releases to conform to the new ReleaseArtistStyle, all in one go.

One note – the Nabble forums are still showing the old top/left frames; see http://www.nabble.com/MusicBrainz-f2885.html – it’s not entirely clear how they are getting that, but it would be nice to update the version they show as well.

Nathan: I do believe that you’re right: my copy of the tagger is inoperable. I can’t even search. I love most everything about this switch—I was entering some stuff earlier today and was really impressed with the new Release Editor!—but breaking the classic tagger without warning is a downer. I’ve been working Picard into my workflow, but now I guess that I have to massively accelerate that.

Thanks all for your nice feedback, i thrive on that… and sorry for breaking the tagger, this wasn’t intentional at all (hopefully we avoided nervous breakdowns with the fixes we added a couple of hours ago)