Provide an Embeddable Widget option for Views aside from Page and Block. This will enable the view to be embedded to any website as Javascript, IFrame/FBML (Facebook support and similar), Google Gadget, or even Flash.
This looks like a neat Summer of Code project.
To ensure that a user actually owns a number we use a double opt-in process where a confirmation message is sent to the handset with a four digit code. The user is then asked to enter this code to confirm ownership.
In the month of June we enabled Google Analytics on Drupal.org as part of an effort to build a user experience toolkit. The toolkit was designed to provide insight on: what users were searching for, what traffic patterns and workflows vistors were following, and what usability feedback we can get from field studies
Here is a fast lesson on one of the many (many) ways of hosting and presenting video on your own Drupal website. The CCK Filefield and jQuery Media modules are a one-two knockout combination that allow users to upload media files to fields in your custom content types and then play back the media files in the correct player or handler. It's a great replacement for the video module and integrates nicely with any modules that like to do things with fields.
We are excited to announce that three key modules, Views, CCK, and Organic Groups, have published release candidates today, ready for testing. If you are interested in speeding the transition to a full release, install and test the Release Candidates (RC).
Hooray!
Serious content-producing organizations have evolved large-scale, specialized processes for their documents. Often they manage revisions and notes in Microsoft Word, then transfer content to PDF, and print with strict editorial guidelines. In contrast, traditional copy and paste web publishing interrupts the existing system. In the process of rethinking a current client's web workflow, we took an interest in this problem and devised a new solution: two modules, word2web and xslt_book, which together combine the advantages of Word and the power of Drupal. Here is a screencast showing the two new modules.
This is awesome.
In the beginning (2002), there was Image, and everyone could create images as nodes and all was good, if a bit simplistic. (There was even IPTC and EXIF metadata support). After a little bit of time, you could even attach images to nodes. By 2006, images could be attached to nodes. (By now, Flexinode had been around for a while and CCK had been around for a bit, too.) CCK became the predominant way of creating content types, as opposed to writing a new module for each individual content type. ImageField, a CCK add-on, (released in July 2006) allowed images to be handled by CCK. This, combined with other CCK fields let you do all sorts of neat things like set up an online store with one field being the name of the object your are selling, another field being the description and another three or four fields for uploading images of the product. Or you could be an online newspaper and have anywhere from zero to several images per article. Each page (whether online store or newspaper) could be themed to layout the information appropriately with ImageCache creating derivative (read: resized and/or cropped) images.
Fast forward to 2008 and there's primarily two ways to get images in your Drupal site, with Lullabot's Image vs. ImageField and ImageCache being the definitive comparison between the two. If you were fine with images as nodes and had simple needs (gallery, photoblog, etc.) you probably went with (or continued using from back in 2002) Image. On the other hand, if you were creating tons of content types thanks to CCK, you probably jumped ship to ImageField.
Now, there's talk about merging Image with ImageField (and ImageCache), with a script to migrate from Image to ImageField. But it was also pointed out that one field to handle all uploaded files, images or not, should be the way to go and that this would be the end of ImageField. FileField, combined with FileField Image would handle everyone's imge handling needs (as well as other file types as well).
While some people think images need special handling (and they are right to a degree and FileField Image takes care of this) there is also the consideration that other file types need special handling, such as videos. Just like images have a need for derivative images, so do videos (original high resolution, low resolution, stored as a flash file and a thumbnail screencap to display in the page). Having one unified way of uploading files would mean less code to maintain and there might even be a reasonable chance of getting file (and potentially image) handling in core, the CCK way.
(For these reasons, I've decided to postpone a D6 release of MAQUM.)
This screencast provides a 34 minute overview of the new features that Views 2 offers. This video shows off not all the new features, but it is a good starting point if you want to learn how to use Views 2
PBS Engage is a "social media" website designed to foster innovative interaction and connections between and among PBS's viewers and programs. Began as an experiment in 2007, PBS Engage allows users to keep updated and to comment on their favorite PBS shows. The site allows PBS a place to explore and develop new ways for PBS viewers to interact online.
The features list is impressive.
Sportswear manufacturer Nike is using Drupal for their Beijing Olympics website.
I've got several hundred photos offline that I've been meaning to upload, just never got around to it.
