Development
Filtering and Searching In Visible Content With AngularJS (Part 2/2)
In a previous post I had illustrated that a regular AngularJS filter is seldom sufficient to implement a search because the data displayed differs significantly from the data stored in the application model. Today I will present a solution to the problem that applies the filter to exactly what the user sees.
Using Tags With Multilingual Jekyll Sites
The static site generator Jekyll stores tags site-wide. You need a little Ruby code if you want to want to maintain them per-language instead, as you would want on a multi-lingual site. In a previous post "Multilingual Web Sites with Jekyll" I had described how to set up a site with Jekyll supporting documents in multiple languages. One thing that was still missing was support for tags respectively keywords.
The imperia View Processor
The main motivation for developing the imperia view processor was frustration about the existing templating engines available for Perl at the time. None of them offered all of the features that I considered a must for the V in the imperia MVC framework. Some of the more important design decisions behind it are outlined below, giving you some insight into the anatomy of a modern template processor.
Filtering and Searching In Visible Content With AngularJS (Part 1/2)
With angular filters you can realize full text searches in small data sets with minimal efforts. This is at least what the documentation suggests. In real-world applications, a naïve application of filters to the data model usually leads to more or less arbitrary behavior.
Simple Content Negotiation For Nginx
Content negotiation is a key concept for multi language web sites. For Nginx it is only available as a patch. But negotiating the language is a rather trivial task for most sites. Instead of patching the web server, a couple of lines of Perl code will also do the job.