Mar 012013
 

It’s been two weeks since I last reviewed the recent changes to MDN’s Kuma platform. Let’s take a look at the more interesting improvements to the software since then!

  • Using the query ?summary on document URLs now returns just the summary of the page. If there’s content marked with the “SEO summary”, that content is returned. If there’s a section entitled “Summary”, that content is returned. Otherwise, all the text in the first block is returned.
  • The page summary is also available in the object returned by the wiki.getPage() KumaScript function.
  • Tables now default to the “standard-table” style, which is our preferred style, when created using the editor’s table editing interface.
  • The context menu when you right-click on links while in the editor now includes a “Launch” item, which lets you open the link. This is handy for reviewing content linked to in your article while you work.
  • Fonts and CSS files from Gaia’s user interface have been added so that they can be used from live samples in the Firefox OS and Gaia documentation.
  • Photoshop files may now be attached to articles; this is permitted in order to allow art resources for app templates and the like to be hosted on MDN.
  • A few bugs have been fixed here and there.
  • More code has landed as our team continues to work on integrating elastic search, which will eventually replace Google search on MDN, and will also eventually be used to implement other features.

Another round of nice little fixes. The summary stuff in particular is exciting to me, because we can use this to automatically generate landing pages. For example, the Firefox OS user experience guide’s “Building Blocks” documentation’s landing page makes use of this capability.

Obviously, all the hard work going on to build up the code for the switch to elastic search is keeping the guys busy. In addition, work is being done to prepare to upgrade from the version of the Django framework we currently use to version 1.4.2. I think they’re getting close to ready to roll that upgrade out. I don’t know what wins we get with that, but I know the team is looking forward to having it done.

 Posted by at 10:53 AM  Tagged with:

  One Response to “Kuma update: February 28, 2012”

  1. Upgrading to Django is kind of like getting a new water heater for your house. The old one still works mostly, but it’s really old. So, you never know when the bottom will fall out, flood your basement, and leave you with no hot water. So… basic household maintenance.