So we got the Mozilla Developer Center upgrade done last night, thanks to the awesome dudes in IT! Over the next few days, I’ll be blogging a bit about the things we gain from this upgrade, from the major stuff to the little stuff (and not necessarily in that order).
Things that need doing still
There are a few things left to do; I’ll be revamping our editor toolbar today to make the editor more convenient to use. I’ve got a better feel now for which features we use and which we don’t, so I can make a better toolbar than the one we currently have.
There are some skin changes I need to make to support new features; for example, we currently don’t support the new notification system because our skin doesn’t expose it to the user. That’s an oversight on my part; I forgot to add support for that to the skin before the upgrade, but I’ll be working on that over the next few days.
In addition, there’s a new tag editor that in theory provides a nicer interface for editing tags, but at present looks awful because we haven’t skinned it yet. I’ll be dealing with that too.
Also, some under-the-hood changes have been made to how custom string resources are stored; previously, we had to manually append our custom strings to the standard resource files every time we updated the software. Now they’re kept in separate files. We haven’t moved them into their own files yet, because we weren’t aware of this capability at the time. We’ll be doing that sometime in the next week or two, once we work through the other stuff that needs doing.
A few improvements
A much-requested improvement that we have now is that the version comparison page now shows you the two versions side-by-side, instead of intermingled and hard to read. The RSS feed still does it the old way, but this is definite progress!
Another helpful improvement is that when you’re editing, there’s now an “Edit summary” box at the bottom, where you can enter an explanation of what you’re changing and why. This is a much-requested feature that we definitely missed when we switched away from MediaWiki, and I’m thrilled to have it now!
One small but pleasant change is that, finally, when you enter edit mode, there’s no longer a spurious extra scroll bar. Instead, the edit box is scrolled along with the rest of your content using the main scroll bar on the browser window. In addition, the edit box more reliably resizes along with the content you’re editing. This will make the editing experience much more pleasant, I think.
There is now a “View page” link on Talk pages that takes you back to the main article; currently, it’s being drawn dimmed as if it’s disabled (due to a minor MindTouch bug that I’ve filed a ticket for), but the button does actually work.
I’ve also configured the table of contents that draws in the top-right corner of pages to only show the top three levels of headings; this prevents certain pages — especially interface references — from having unreasonably long tables of contents, leaving them much easier to navigate.
The RSS feed for new changes on the wiki now only shows the blocks that have changed, instead of embedding the entire article. It also calls out each individual edit, instead of lumping all edits together, leaving you to guess who made what changes.
One thing you can do — which I think you were actually able to do in the previous version, but I never mentioned before — is subscribe to RSS feeds for individual pages and subtrees of the site; click the RSS feed icon in your location bar, and the popup that appears lets you choose between the “What’s new feed” (for all changes on the wiki), the “Page and subpages changes feed” (for all changes in the subtree of the site rooted at the page you’re looking at), and the “Page changes feed” (which only covers changes to the page you’re looking at).
That’s not the same as the excellent notification system that we’ll expose soon, but it’s still a handy feature.
But wait, there’s more…
There are other changes, too, but these are the ones that come immediately to mind. I’ll go into more detail, and discuss other changes, in future blog posts over the coming days and weeks. But this should get you started exploring the improved Mozilla Developer Center!