Findjango: A Django Search Vertical

March 9, 2009. Filed under django 72 springsteen 6 findjango 3

Ever since the first time I saw Yahoo! BOSS, I've been wanting to work on a Django-specific vertical search. Any moderately technical topic has a dozen RSS feed aggregators, but few have the necessary content and interest to sustain a search vertical, and fewer still have a targeted search that outperforms the search giants1.

I'm excited to announce the opening of findjango, a Django search vertical.

The first iteration of the Findjango SERP.

(If the site doesn't look like the above screenshot, try a hard refresh.)

Rather than a long-winded description of what it is, go ahead and try some queries:

  1. Search for test.
  2. Search for yahoo.
  3. Search for expire cache.

Sources of Content

An up-to-date list of sources is always accessible on Findjango itself. but currently it is taking advantage of five sources for search results as well as constructing a slender index of the Django documentation.

Those five sources are:

  1. Yahoo! BOSS web results, restricted to a handful of relevant sites.
  2. results, limited to those containing the django tag.
  3. results, again limited to the django tag.
  4. Tweets that contain the query term and the term django (the poor man's search vertical).
  5. Amazon book results that meet the query, contain the term django, and don't contain a handful of Jazz related terms.

This is definitely just the beginning in terms of content sources. Even if you only have a small blog, as long as you can filter for Django related content, I'd love to integrate your content here as well. All it takes is an externally accessible search api, preferably using the Springsteen Service format, but get in touch and we can discuss details.


Findjango's implementation is built on top of django-springsteen, and Springsteen does most of the heavy lifting. At this point there are only a few custom pieces:

  1. Reporting irrelevant terms.
  2. A Django specific relevancy and ranking algorithm.
  3. Indexing and matching queries against the Django documentation.
  4. Custom service wrappers to access this blog as well as

The Future

I have a handful of intertwined goals for Findjango:

  1. The first is to serve in the flagship fleet for django-springsteen as an example of a highly targeted search experience (Springsteen Search being the example of a non-targeted search experience).

  2. The next--although not less important--goal is for Findjango to be a genuinely useful resource for the Django community. A big part of this will be adding more resources, but also continued work on relevancy and other tweaks.

  3. Finally, and perhaps most exciting, in the upcoming days I'll be opening Findjango as an externally accessible api, which will allow other sites in the community to directly query Findjango and display the results in their own pages.

I'm excited to hear your feedback, and any suggestions on how to make FIndjango a more useful resource. Thanks for reading.

As a bonus tidbit, Josh Gourneau has implemented a MyCroft plugin, making Findjango usable from the Firefox and IE search box.

  1. I am aware of, but findjango and are attempting very different things. DS is an amalgamation of an RSS feed aggregator, a project listing and a Google Custom search.

    On the other hand, findjango is designed to harness existing community projects. For example, rather than hosting a project listing, findjango is working towards integrating with There are deeper more technical differences, but I think this is the most important distinction.