Tim/parature faq feed

Just to follow up on this: since you're not specifying specific analyzers for any fields, the "string" fields with use the [standard analyzer](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-standard-analyzer.html), which works quite well. In other indices we define a custom analyzer which includes the [snowball](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-snowball-tokenfilter.html) filter, which provides stemming (?q=puppies would return a doc containing "puppy" even if it didn't contain the exact "puppies" match). I suggest you add the same custom analyzer that can be found in other index settings (e.g. Australian trade leads) and configure field mappings accordingly.

Since you're using Nokogiri to remove HTML during the import process, you can remove the `char_filter: 'html_strip',`, although I'm interested to find out if this can help us generally.

Just to note: I'd like to replace all the various custom_analyzers that are dotted around the model dir with a single definition somewhere. This is low on my priority list at the moment though.